Jump to content


Photo

The Ultimate Pulse Owners Guide

* * * * * 3 votes

  • Please log in to reply
301 replies to this topic

#261
hunk74

hunk74

    Newbie

  • Members
  • Pip
  • 31 posts
  • Devices:Pulse, Samsung Galaxy S
Hello, new to this board.

So, yesterday I decided I´ve waited long enough and had a go at upgrading my pulse to froyo with cyanogen mod 6.
Flashed the recovery image (amon ra) and everything works fine. Lots of new options in the boot menu!
Since I already had the UK 2.1 installed I placed cm6-beta0.40 onto my sd card and selected flash.
But after awhile instalation aborts and the error message Error in /sdcard/CM6.1-Pulse-beta-0.40.zip pops up.

Tried reinstalling 2.1 from sdcard. Reinstall went well. Tried redownloading CM6 yet I still get the same error when attempting to flash?
What am I doing wrong?

edit: Yes, I did a backup and a wipe before attempting the above.

Edited by hunk74, 06 January 2011 - 09:37 AM.

  • 0

#262
hunk74

hunk74

    Newbie

  • Members
  • Pip
  • 31 posts
  • Devices:Pulse, Samsung Galaxy S
Update: FLB mod installs after just 1 attempt.
Which leads me to believe that after several download attempts and aborted installations the CM6-beta0.40 upload has somehow corrupted?

Anyone got a working rom lying around somewhere?

edit: Nevermind, I now realise I need Clockwork custom recovery instead of Amon Ra.

I r i diot.
Thank u forum, continue as you were.

Edited by hunk74, 06 January 2011 - 10:26 AM.

  • 0

#263
hunk74

hunk74

    Newbie

  • Members
  • Pip
  • 31 posts
  • Devices:Pulse, Samsung Galaxy S
Hurray, CM6 installed successfully.
Sadly, once up and running I get greeted with a barrage of error messages and FC´s.

Oh well, think I´ll stick to the official releases for now.

edit: Forgot to wipe to factory settings before install (duh).
It now works f*cking beautifuly (pardon my language)
Now only miss apps to SD.

Edited by hunk74, 07 January 2011 - 02:39 AM.

  • 0

#264
nikic

nikic

    Newbie

  • Members
  • Pip
  • 7 posts
  • Gender:Male
  • Location:Pula
  • Devices:T-mobile Pulse 1.5
  • Twitter:@nenikic

QUOTE(Jeroen van Dijk @ Dec 16 2010, 19:21) *
I try this now diferents times to install the Flibblesan's FLB MOD 1:
Espresso Style, Eclair 2.1
, it has installed succesfully and it works but not the apps2sd and i get manny errors when i open apps. also the app terminal emulator doesnt work!

maybe i do something wrong?


Did you wipe before installing the new rom?


I have similar problem... I read a lot and when I decide to flash my pulse, everything went smoothly with FLB 1.7 ROM... BUT...
When I try to open Terminal emulator, constantly I receive an error message and app is forced to close.
Then I find another terminal application on the market (ConnectBot) and it's working normally but when I tried to check my a2sd installation (a2sd check) long, long listing of "something" came up in the terminal. I installed few apps and I noticed (trough ES File Explorer) that amount of internal memory decreased and amount of free space on sd card stays the same...
How to check what is happening and how to correct errors?

Thanks!

Edited by nikic, 13 January 2011 - 06:46 AM.

  • 0

#265
kirmastili76

kirmastili76

    Newbie

  • Members
  • Pip
  • 6 posts
  • Location:Turkey
  • Interests:Digital devices like phones, PC, Operating Systems, 3d Graphic Softwares
  • Devices:HUAWEI U8230

Returning to the Official 1.5 Update



Please note that this portion of the Guide is only for those using a T-Mobile Pulse (U8220). This will NOT work for those using a U8320 or a U8220-6. Please check the label located under the battery to determine your version

You are able to downgrade to 1.5 from any rom (Custom or official)
Return to 1.5 if you are sick and tired of the bugs with the official 2.1 update.

Difficulty Level
1/5 (very easy)
Known Bugs

None at this time


What you will need:A Pulse
A Micro SD Card (Recommended to have at least 1gb free space)
A Micro USB Cable or An Micro SD Card Reader
A Word of Caution
Please note that installing this update will wipe everything off your phone. (Contacts, messages, apps etc.) Please ensure that you back them up if required. Your SD card will not be wiped before, during or after the update process.
Also please refer to the previous warning:
The Guide

Step 1: Prepare your phone, backup anything you need to the SD card or computer. Note that everything will be wiped off your phones internal memory.

Step 2: Download the Official 1.5 downgrade file from here:
http://www.huaweidev...25490/dload.zip

Step 3: Extract the contents of the ZIP file to any location on your computer. Place the entire "dload" folder onto the Root of your SD card
By "Root" I mean do not place the file in any subfolders

Step 4: Power off your Device. When the phone has fully powered off press and hold the following buttons: POWER + RED (End Call) + VOLUME UP
You may release these buttons when the message "Preparing Update" appears on your screen

Step 5: Confirm that you wish to update and allow the device to run it's course. The phone may get stuck on "Restarting" if so wait a few minutes then remove and re-insert the battery
If your phone "Fails to Update" Please refer to the FAQ [here]

Step 6: Download the "December Update" from here:
http://support.t-mob...th_Userdata.zip

Step 7: Extract the contents of the ZIP file to any location on your computer. Place the entire "dload" folder onto the Root of your SD card (Delete the Previous dLoad directory)
By "Root" I mean do not place the file in any subfolders

Step 8: Power off your Device. When the phone has fully powered off press and hold the following buttons: POWER + RED (End Call) + VOLUME UP
You may release these buttons when the message "Preparing Update" appears on your screen

Step 9: Confirm that you wish to update and allow the device to run it's course. The phone may get stuck on "Restarting" if so wait a few minutes then remove and re-insert the battery
If your phone "Fails to Update" Please refer to the FAQ [here]

It is entirely normal for your phone to experience a partial Boot-Loop. So don't be alarmed if it loops once.

Step 10: Allow your phone 5+ minutes to boot up for the first time.


Hello there,
I have U8230 and I tried what you described in the subject but I haver a problem now my phone doesnt open I just see black and white strips on the screen.

-When I first got the phone it was 1.5 then I installed 2.1 Redbull. It was quite ok for me but sd card and 3g problem was there.
-Then a friend gave me yoru link how to turn back 1.5 again...
-Last nite I exactly installed the first dload then it opened again. Then I sent the second dload folder to my sd card and I did power + volup+ end it installed. It stucked on restarting...
-As you mentioned ı waited a few minutes then i removed the battery but now this black and white strips stil there and the same way doesnt work to install it again...

Now I cant use my phone. I think in this position sd card doesnt work cause when i plug the usb there is no any info on pc....

Please can anyone help about this subject...I need your helps....

Thank you..

  • 0
Posted Image

Uploaded with ImageShack.us

#266
hepatitis

hepatitis

    Newbie

  • Members
  • Pip
  • 6 posts

Hey first of all thanks a lot for this guide. Honestly it was the only decent one I was able to find on the net.

Now prior to registering and asking for help in the first post right away, I actually did read a lot of info and did not find a direct answer to my question.

So to make a long story short; I was following the 'Installing A 2.1 / 2.2 Custom Rom' Guide and I'm stuck at Step 8.
I've got the u8230 with the stock 2.1 already pre-installed.

I took a shot of the error message it shows me.

Posted Image
Maybe one of you pro guys got an idea how to solve this? I'm really not eager to flash anything without a backup.
EDIT: Ok bed time soon, but I guess in this case finding a solution leaves room for even more questions. At least for me.

I ran across this thread:
http://android.modac...m-without-root/

This guy having exactly the same phone, operator and soft version as I do. Now since I haven't messed with droids too much yet, I honestly got no idea what to do with his .img.

All I want to do is:
- do a backup
- delete my stock rom
- install flb mod 1

Not asking for a step by step explanation, but pointing me in the right direction would be appreciated o//

Anybody know hot to solve, please. I dun know how to follow up as can't format system. thank you very much.

  • 0

#267
pepe24

pepe24

    Newbie

  • Members
  • Pip
  • 47 posts
  • Location:Serbia
  • Devices:RBM2
Hi,

Is there any way to boot to clockwork recovery if the phone is in boot-loop ? - MENU + Red bitton is not working.....

Thanks,

Pepe

  • 0

#268
AntonioPT

AntonioPT

    Addict

  • Members
  • PipPipPipPipPip
  • 645 posts
  • Gender:Male
  • Devices:Huawei U8230 (aka TMN a1)

Hi,

Is there any way to boot to clockwork recovery if the phone is in boot-loop ? - MENU + Red bitton is not working.....

Thanks,

Pepe


Flash it again using fastboot.

  • 0

#269
ChinoMoreno

ChinoMoreno

    Newbie

  • Members
  • Pip
  • 2 posts
  • Devices:U8320
Guys i bricked my U8230. I tryed to downgrade it to 1.5 as per guide. Now I see only freezed black and white stripes and nothing else. Can anyone help me to fix it? Thank you in advance!

Edited by ChinoMoreno, 29 March 2011 - 05:47 PM.

  • 0

#270
thelolguyXD

thelolguyXD

    Newbie

  • Members
  • Pip
  • 4 posts

Guys i bricked my U8230. I tryed to downgrade it to 1.5 as per guide. Now I see only freezed black and white stripes and nothing else. Can anyone help me to fix it? Thank you in advance!

I bricked my phone too but i upgrade it to 2.1 from RBM2 instead of the 1.5

  • 0

#271
zeljko211

zeljko211

    Newbie

  • Members
  • Pip
  • 11 posts
  • Devices:pulse

same for me, ive found all the drivers that need updating, and tried updating them via that 'olgy' guys driveer thread and it wont accept any of them telling me it doesnt contain any info on my hardware, and ive tried the drivers that came with the 2.1 hungarian thing which doesnt have anything for xp :'(

the only solution for me is to borrow my friends mac laptop and patch amon ra from it, then i can install whatever back on my piece o crap dell laptop running lowly xp


unfortunately I do not know anyone who has a mac and I do not know whether it is possible to send over the computer because i have xp

  • 0

#272
ciri59

ciri59

    Newbie

  • Members
  • Pip
  • 13 posts
This rom has the italian language?

Edited by ciri59, 17 April 2011 - 08:21 AM.

  • 0

#273
hellb0y

hellb0y

    Newbie

  • Members
  • Pip
  • 5 posts
  • Gender:Male
  • Devices:T-Mobile Pulse
Can someone give me a new link or reupload the dload.zip for "Returning to the Official 1.5 Update" because the one in the post it's not working :)

  • 0

#274
badgir

badgir

    Newbie

  • Members
  • Pip
  • 2 posts
  • Devices:T-Mobile Pulse (U8220)

Please note that this portion of the Guide is only for those using a T-Mobile Pulse (U8220).

Checked: U8220

You must have the Official 2.1 update installed BEFORE attempting to install a 2.1 custom rom.

Done. Installed the original 2.1 update from T-Mobile



Flibblesan's FLB MOD 2: [ALPHA]Credits to Tom G and the 2.2 DEV team!
True Vanilla, Froyo 2.2
http://android.modac...-froyo-testing/

prepared on the SD-Card.


Step 1: Download the "Custom Recover Image"

Done.

Step 2: Extract the ZIP anywhere on your computer and navigate into the "1.5.2-pulse-amonrarecovery" folder

Done.

Step 3: Power Off your device. Hold down the POWER + RED (End call) + VOLUME DOWN keys until a blue screen appears

Done. Reports:

USB Fastboot: V0.5
Machine ID: 100700 v0
Build Date: Oct 28 2010, 03:05:51

MSM Id: 16
MSM Version: 2.0
Modem Build Id: 76XXC-6383-SDCBALYM
Serial Number: UNKNOWN

ptn 0 name='boot' start=304 len=20
ptn 1 name='system' start=324 len=680
ptn 2 name='userdata' start=1004 len=842
ptn 3 name='cache' start=1846 len=160
ptn 4 name='recovery' start=2006 len=38
ptn 5 name='misc' start=2044 len=4


Step 4: Plug your device into your computer and wait for the drivers to be installed (Windows Only)

Plugged in the device. (PC with ubuntu)

Step 5: Open the "install-recovery-windows.bat" (Windows) or the "install-recovery-mac.sh" (Mac) or the "install-recovery-linux.sh" (Linux)
This will open and close very quickly. There is no visible indication that anything has happened on either the computer or the phone. If you get a "waiting for device" or an error refer to the FAQ [here]


Done.
On terminal window in ubuntu get the following messages:
sending 'recovery' (3768 KB)... OKAY
writing 'recovery'... OKAY


Step 6: Unplug your device, remove and re-insert the battery. Press and Hold down: "POWER + MENU + RED (End call) Keys until the "Custom recover image" screen appears
It may appear after the origonal Tmobile boot or between the android screen. If not remove the battery and try again.

Done, but this is where the process does not go further:
I press POWER+MENU+RED, the device shows first an unreadable mess (as ususal since 2.1 update), then Android screen and then T-Mobile boot screen, ending up by booting with previous version as if nothing has happened. It is only then that I leave the three buttons. I have repeated this operation many times but always with the same result: the device does not enter in Custom Recover Image screen but boots up as usual. Any idea?

I have never rooted the device nor done any other change except the 2.1 update which works normal.

The SD-card is 2 GB, the original one. I tried the operation also without the SD-Card inserted but the result is always the same.

  • 0

#275
ciri59

ciri59

    Newbie

  • Members
  • Pip
  • 13 posts
I followed the guide, everything fine until the installation of the ROM (flbmod_v1.7.zip) At this point everything stops and this appears:
E: Can't symlink/system/xbin/su
E: Failure at line 135:symlink/system/xbin/su SYSTEM:xbin/su
Installation aborted

and the phone not work.

any advice?

  • 0

#276
eiamhere

eiamhere

    Newbie

  • Members
  • Pip
  • 12 posts

I followed the guide, everything fine until the installation of the ROM (flbmod_v1.7.zip) At this point everything stops and this appears:
E: Can't symlink/system/xbin/su
E: Failure at line 135:symlink/system/xbin/su SYSTEM:xbin/su
Installation aborted

and the phone not work.

any advice?



I've been getting this error also. Tried to refrain from posting, did a lot of searching, but ultimately gave in.

Also after wiping data/ factory reset and wipe dalvik cache and get the following error run 'wipe dalvik' via adb!

I've restored my Pilse countless times with a nandroid backup, used z4 app to ensure I still had superuser.

I'll apologise for being a bit thick, I haven't root or done much at all with mobiles before.

These are the steps I took:

U8220 which I updated to 2.1 Uk

Installed drivers and did 'install-recovery-windows' for recovery mode.
Tried to install flb-mod v1.7 Placed in root of sd card (not extracted), I receive the same error as Ciri59
Tried Z4 app to ensure superuser, still the same error.

If I haven't provided enough info. please tell me what I'm missing

Thank you in advance if anyone can help

  • 0

#277
Bibbly

Bibbly

    Newbie

  • Members
  • Pip
  • 25 posts
  • Devices:T-Mobile Pulse

Checked: U8220
Done. Installed the original 2.1 update from T-Mobile
prepared on the SD-Card.
Done.
Done.
Done. Reports:

USB Fastboot: V0.5
Machine ID: 100700 v0
Build Date: Oct 28 2010, 03:05:51

MSM Id: 16
MSM Version: 2.0
Modem Build Id: 76XXC-6383-SDCBALYM
Serial Number: UNKNOWN

ptn 0 name='boot' start=304 len=20
ptn 1 name='system' start=324 len=680
ptn 2 name='userdata' start=1004 len=842
ptn 3 name='cache' start=1846 len=160
ptn 4 name='recovery' start=2006 len=38
ptn 5 name='misc' start=2044 len=4
Plugged in the device. (PC with ubuntu)
Done.
On terminal window in ubuntu get the following messages:
sending 'recovery' (3768 KB)... OKAY
writing 'recovery'... OKAY
Done, but this is where the process does not go further:
I press POWER+MENU+RED, the device shows first an unreadable mess (as ususal since 2.1 update), then Android screen and then T-Mobile boot screen, ending up by booting with previous version as if nothing has happened. It is only then that I leave the three buttons. I have repeated this operation many times but always with the same result: the device does not enter in Custom Recover Image screen but boots up as usual. Any idea?

I have never rooted the device nor done any other change except the 2.1 update which works normal.

The SD-card is 2 GB, the original one. I tried the operation also without the SD-Card inserted but the result is always the same.


I have exactly the same problem, I'm totally stumped :P

  • 0

#278
darkdevil1

darkdevil1

    Regular

  • Members
  • PipPip
  • 148 posts
  • Devices:T-Mobile Pulse
The 1.5 downgrade file 404s for me. Anyone have another link?

  • 0

#279
hoaletn

hoaletn

    Newbie

  • Members
  • Pip
  • 2 posts
  • Devices:T mobie Pulse
  • Twitter:@asas
Hi everybody

I have 2 sd cards

1/ a 8g class 2
2/ a 4g class 6

Which one i should choose?


thanks

  • 0

#280
Jay Man

Jay Man

    Newbie

  • Members
  • Pip
  • 1 posts
Hi :D

I'm trying to install my first custom rom (J-Mod Current Version: v1.4 Release Date: 02.10.2010) using the instructions from the first post (thanks btw) and I'm getting an error message when after choosing to flash the zip file:

E:Can't symlink /system/xbin/[
E: Failure at line 9:
symlink busybox SYSTEM:xbin/[

Installation aborted.

I've searched for this problem but all I could find is that the UK 2.1 official update makes the partition too small for the install to work properly but the instructions on the first post say to use the UK 2.1 not the Hungarian one.

Anyone know what I'm doing wrong?

Thanks :D

Edited by Jay Man, 05 June 2011 - 07:46 PM.

  • 0




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users