U8220 Uncustomised ROM

[Guest nicox45]

I sacrificed my phone (lost touchscreen... heelp!!! :) ) and made a nandroid back up of my uncustomised u8220, here it is for you:

http://rapidshare.com/files/327281859/nand..._u8220.rar.html

someone please help me with the touchscreen!!

bye!

Edited December 29, 2009 by nicox45

[Guest BigBearMDC]

Good morning

have you tried to wipe your phone?

Greetings,

BigBearMDC

Edited December 29, 2009 by BigBearMDC

[Guest nicox45]

Good morning

have you tried to wipe your phone?

Greetings,

BigBearMDC

I did, but it's not working... i made a topic here, thanks!

[Guest BigBearMDC]

- moved to other Topic -

Edited December 29, 2009 by BigBearMDC

[Guest nicox45]

Okay

if your usb Port is working in bootloader mode than i would say try to get your factory image and copy the bootloader.img manually back on our phone using adb shell. The same way you installed superboot and the recovery image.

Greeetings,

BigBearMDC

I think tomorrow I'll go to Claro to change it, usb port is not working properly too.. anyway thanks for your help, I'm pretty tired, it's 4:40 AM here... byeee! thanks!!

[Guest rjm2k]

I think tomorrow I'll go to Claro to change it, usb port is not working properly too.. anyway thanks for your help, I'm pretty tired, it's 4:40 AM here... byeee! thanks!!

Hi there, thanks for uploading the backup of your device!

As for your problems, assuming you haven't installed the dec updated you should be able todo the following :-

1. power up the phone holding the vol -, red key to get into fastboot

2. connect to your pc and run fastboot-windows boot ra-recovery-pulse-v1.5.2.img to get into the recovery image

3. use the recovery image to restore your backup

Edited December 29, 2009 by rjm2k

[Guest rjm2k]

Ok, I tried to restore the U8220 backup, first time I've seen the moving android logo rather than the spinning tmobile logo! I believe that this backup was from a device which is pre the dec bootloader so it goes into a loop, failing to boot.

I suspect that if we stuff the post dec kernel plus RIL etc into the image, then we will have a fully working uncustomised U8220 ROM!

Edited December 29, 2009 by rjm2k

[Guest Dr Who]

Ok, I tried to restore the U8220 backup, first time I've seen the moving android logo rather than the spinning tmobile logo! I believe that this backup was from a device which is pre the dec bootloader so it goes into a loop, failing to boot.

I suspect that if we stuff the post dec kernel plus RIL etc into the image, then we will have a fully working uncustomised U8220 ROM!

Sweet. I wish I could help the development but currently I am clueless about how to do any of these things - if someone could post a link to a tutorial, or write their own, then I would try and get on it. Wouldn't need to be full, just a quick outline of what software and steps I need to do this on a Windows box.

Thanks to Nicox45 for posting this - hope we can help you fix your phone. The instructions by rjm2k sound like they should at least be able to get you to a permanent reboot cycle (which would at least be progress).

[Guest nicox45]

Ok, I tried to restore the U8220 backup, first time I've seen the moving android logo rather than the spinning tmobile logo! I believe that this backup was from a device which is pre the dec bootloader so it goes into a loop, failing to boot.

The build date is November 7... bye!!

[Guest rjm2k]

The build date is November 7... bye!!

Yes the dec update puts a bootloader dated 26th Nov on I think, have you tried using the recovery image to restore your backup?

[Guest nicox45]

Yes the dec update puts a bootloader dated 26th Nov on I think, have you tried using the recovery image to restore your backup?

Yes I did, but seems nothing is going to bring the touchscreen back :)

[Guest rjm2k]

Yes I did, but seems nothing is going to bring the touchscreen back :)

Odd, at least with your backup restored you should be ok taking it back to the shop, assuming the original recovery is on there too.

[Guest BigBearMDC]

i think i know something you could try

-put your pulse in fastboot mode (Volume Down + End Key + PWR Button)

-use the amonrecovery to get into the recovery menu

-then wipe evrything

-copy your stock rom to the sd card and install it

If that works you could try to do a nandroid backup.

Greetings,

BigBearMDC

[Guest nicox45]

i think i know something you could try

-put your pulse in fastboot mode (Volume Down + End Key + PWR Button)

-use the amonrecovery to get into the recovery menu

-then wipe evrything

-copy your stock rom to the sd card and install it

If that works you could try to do a nandroid backup.

Greetings,

BigBearMDC

I don't have my stock rom, I just have the nandroid backup I put before... thanks!

[Guest BigBearMDC]

I don't have my stock rom, I just have the nandroid backup I put before... thanks!

then you could try this one.

Greetings,

BigBearMDC

[Guest rjm2k]

then you could try this one.

Greetings,

BigBearMDC

No, that's for t-mobile.

Have you tried using the recovery image and selecting the reset to factory settings option?

[Guest Dr Who]

then you could try this one.

Greetings,

BigBearMDC

Have you tried any of the pre-December update ROMs as suggested, either MCR Stock TMob 1.5 or U8230 Vanilla Cupcake v1.1, or somewhere I think someone posted an image of the pre-December update available from the TMob UK website.

[Guest nicox45]

No, that's for t-mobile.

Have you tried using the recovery image and selecting the reset to factory settings option?

I did, but touchscreen doesn't work...

Have you tried any of the pre-December update ROMs as suggested, either MCR Stock TMob 1.5 or U8230 Vanilla Cupcake v1.1, or somewhere I think someone posted an image of the pre-December update available from the TMob UK website.

I installed both, I can't use the tmobile one because it says "Tap the android" :) ... TAP ;) ... mmm... in the vanilla cupcake rom I don't get touchscreen to work... thanks!

[Guest Dr Who]

I did, but touchscreen doesn't work...

I installed both, I can't use the tmobile one because it says "Tap the android" :) ... TAP ;) ... mmm... in the vanilla cupcake rom I don't get touchscreen to work... thanks!

So, just to make sure we know the sequence of events, you wrote this:

I first installed the recovery image, then I installed the superboot thing, the problem is (i think) it overwrites a file that only works with tmobile network, my network is Claro in my country ( Chile ) that is why the computer thinks it is a "tmobile 3g" device... doing those things I lost touchscreen and the usb port is failing (does not connect to the computer), also lost calling support, I dont know if those things are related to the superboot but everything started when I installed it, as a recommendation if you are not a user from the tmobile network dont install anything of those things... thank you!

Then

nice but i have another problem, I installed the tmobile custom rom, the problem is I cant get to the homescreen because it says tap the android, how can i open the restore thing now, help!!! :S??

So, this means you installed superboot and the touchscreen failed and the usb port failed. Assuming you are using Windows I assume the USB problem would be resolved by going into device manager and making sure all the instances of TMob phone have the drivers properly installed.

Subsequently you have installed all the available pre-December updates, which boot fine but still do not leave you with a working touch screen?

Just to be sure you are holding the phone in your hand when you are using it and not leaving it flat on a surface? (reports that the screen stops responding when it is flat on an insulating surface)

Seems strange - I know very little about it but looking at what superboot affects it doesn't seem to change the ROM image just add some extra files.

There was this advice on how to recover from a perpetual reboot cycle from user Zsolabola,

"Hi Paul

In that case you cannot restore the nandroid backup because you have never seen the Amon RA tool working, therefore you don't have a backup.

The only sollution for me was to put back the original ROM downloading the UPDATA.APP and update it vith vol up+red+power on"

Some stuff relating to UPDATA.APP http://android.modaco.com/index.php?act=Se...e=%2BUPDATA.APP

Otherwise I wonder whether it is just coincidence and you have experienced a hardware failure at the same time as the update? Seems strange you can flash ROMs, which boot perfectly but only have the touchscreen disabled?

[Guest nicox45]

Otherwise I wonder whether it is just coincidence and you have experienced a hardware failure at the same time as the update? Seems strange you can flash ROMs, which boot perfectly but only have the touchscreen disabled?

Maybe it's a hardware failure, anyway I'm now going to the provider to replace it, thanks for all your help guys!!

[Guest _Sebastian_]

Generic Build .... interesting ... Thanks again for sharing nicox45 might be really useful.

The TARGET_DEVICE is still U8220 but they use the System Properties from U8226.

I hope we get a rom with U8226 as TARGET_DEVICE in our hands too (would complete the collection).

[Guest Jan M]

Generic Build .... interesting ... Thanks again for sharing nicox45 might be really useful.

The TARGET_DEVICE is still U8220 but they use the System Properties from U8226.

I hope we get a rom with U8226 as TARGET_DEVICE in our hands too (would complete the collection).

will U8226 be released as a new physical device?

[Guest _Sebastian_]

will U8226 be released as a new physical device?

Take a look at init.qcom.sh:

.

.

.

target=`getprop ro.product.device`

case "$target" in

"msm7201a_ffa" | "msm7201a_surf")

echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

echo 90 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold

echo 60 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/down_threshold

echo 500000 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate

echo 245760 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

;;

"U8220" | "U8226" | "U8230")

.

.

.

At least there is a build with U8226 as TARGET_DEVICE

[Guest ian_tor]

hello all, I'm from Chile and I have a Huawei U8220 and I have the same problem.

The touch screen goes crazy and just start moving icons to the Trash. I have performed several tests:

- At first I thought it was some application, so let the phone by default, without positive results.

- I remove the screen protector and cleaning. The continuing problem.

- I update the android to version 2.0 and after a time the problem happened again.

So this thinking is not a software problem but rather hardware .. Anyone have any news?