Guest Markus Arnold Posted September 17, 2010 Report Posted September 17, 2010 Hey guys, yesterday i killed my touchscreen trying to update my Pulse (U8220) from 1.5 to 2.1. And now every update i try fails. It came like this: I used a german guide for rooting and flashing ( http://www.android-hilfe.de/root-hacking-m...bile-pulse.html ). -So i rooted the device, falshed the recovery and booted that. - After that i did a nandroid backup (which doesnt work if i try to recover it) - then sd partitioning: no swap space, ext2 640mb - copied decemberupdate (source: t-mobile germany) on sd and did system and dalvik wipes. - restarted the pulse with vol+, red, power and flashed the decemberupdate. (here came the frist time: update failed, but at the third try it worked fine) -now i downloaded the official uk 2.1 update (like in the 'ultimate pulse owners guide') and put that on the sd. - again i tried to flash with vol+, red, power but it failed all the time already while unpacking. So i restarted the phone and instead of the first t-mobile (standard) boot screen i got blackandwhite line and pixels at the top. But it booted fine, but when i had to type the pin i realized that the Touchscreen wasn't working anymore. I retried the Decemberupdate: failed, failed, failed.. then tried a backup restore, but got: "error: run 'nandroid-mobile.sh restore' via adb!". I also tried that, didn't work. 2 of the files are obviously corrupt. Next try: Huawais Back to 1.5 update: that worked! but it got stuck at Restarting, so i took out the batt. So after that i had some hope and retried the Decemberupdate: failed again all the time. Tried 2.1 UK-> fails, tried 2.1 HU -> failed. -now i downloaded all the files again an retried it from the "back to 1.5" update on -> every update instead of "back to 1.5" fails. - changed the sd card, but same problem. but now i don't know what to do next.... hope you guys have some ideas! Cheers Markus
Guest Sh4d0w940 Posted September 17, 2010 Report Posted September 17, 2010 Have you tried the Time Machine? Sh4d0w940
Guest Markus Arnold Posted September 17, 2010 Report Posted September 17, 2010 Have you tried the Time Machine? Sh4d0w940 yes, thats what i mean with "back to 1.5"-update. I already tried two different versions of it, and the update itself works (it gets stuck at restarting, after i wait for 20 minutes i re-inserted the batt). But no other update did work afterwards....
Guest Markus Arnold Posted September 18, 2010 Report Posted September 18, 2010 did i brick my phone?? :lol: no other ideas?
Guest R_A_V Posted September 18, 2010 Report Posted September 18, 2010 did i brick my phone?? :lol: no other ideas? 1. wipe everything. do factory reset 2. flash time machine 3. flash December update from t-mobile cite 4. flash 2.1 update from t-mobile 5. install amonra and apply any custom firmware if you like
Guest Markus Arnold Posted September 18, 2010 Report Posted September 18, 2010 (edited) 1. wipe everything. do factory reset 2. flash time machine 3. flash December update from t-mobile cite 4. flash 2.1 update from t-mobile 5. install amonra and apply any custom firmware if you like Thanks, but already tried that 10 times... but did it once again: 1. wiped EVERYTHING (in recovermode: RA-pulse-v1.5.2) 2. flashed time machine: update complete but hangs at restarting -> batt out. 3. flash of Decemberupdate fails while unpacking (like 10 times before... :lol: ) ... other ideas? edit: the log file says: **** SD download log **** (fread_retry >= SD_FILE_RD_RETRY) failed! dload_sd_cp_and_chk_file_data failed! Edited September 18, 2010 by Markus Arnold
Guest Trebor Rude Posted September 18, 2010 Report Posted September 18, 2010 other ideas? edit: the log file says: **** SD download log **** (fread_retry >= SD_FILE_RD_RETRY) failed! dload_sd_cp_and_chk_file_data failed! Based on that error message, my guess would be to re-partition the SD card so it has only one FAT32 partition, then wipe everything possible and start from the time machine. Don't attempt anything unofficial until you've got the 2.1 update on.
Guest Markus Arnold Posted September 18, 2010 Report Posted September 18, 2010 Based on that error message, my guess would be to re-partition the SD card so it has only one FAT32 partition, then wipe everything possible and start from the time machine. Don't attempt anything unofficial until you've got the 2.1 update on. Thanks, but didn't work out as well.. what i did: in recoverymode: -partition sd: swap = 0mb, ext2 = 0mb. -all wipes, got error at dalvik and ext2-wipe, because of missing ext2-partition, but should be alright -then started from time machine on (like described above): : update complete but hangs at restarting -> batt out. - now flash of Decemberupdate: fails while unpacking -as always! now i tried to format the sd in windows, but didnt work out as well. and again same entry in logfile: **** SD download log **** (fread_retry >= SD_FILE_RD_RETRY) failed! dload_sd_cp_and_chk_file_data failed!
Guest Csöpi Posted September 18, 2010 Report Posted September 18, 2010 (edited) Thanks, but didn't work out as well.. what i did: in recoverymode: -partition sd: swap = 0mb, ext2 = 0mb. -all wipes, got error at dalvik and ext2-wipe, because of missing ext2-partition, but should be alright -then started from time machine on (like described above): : update complete but hangs at restarting -> batt out. - now flash of Decemberupdate: fails while unpacking -as always! now i tried to format the sd in windows, but didnt work out as well. and again same entry in logfile: **** SD download log **** (fread_retry >= SD_FILE_RD_RETRY) failed! dload_sd_cp_and_chk_file_data failed! how do you try to flash the time machine? within amon cervorey? Because you shouldn't do that. You should use the sound up+red button+power Edited September 18, 2010 by Csöpi
Guest Markus Arnold Posted September 18, 2010 Report Posted September 18, 2010 how do you try to flash the time machine? within amon cervorey? Because you shouldn't do that. You should use the sound up+red button+power I did it with vol+, red, power. in the meantime i also tried it within recovery but taht didnt work out eiter (e: no signature, e: verification failed)
Guest AdamBaker Posted September 18, 2010 Report Posted September 18, 2010 Thanks, but didn't work out as well.. what i did: in recoverymode: -partition sd: swap = 0mb, ext2 = 0mb. -all wipes, got error at dalvik and ext2-wipe, because of missing ext2-partition, but should be alright -then started from time machine on (like described above): : update complete but hangs at restarting -> batt out. - now flash of Decemberupdate: fails while unpacking -as always! now i tried to format the sd in windows, but didnt work out as well. and again same entry in logfile: **** SD download log **** (fread_retry >= SD_FILE_RD_RETRY) failed! dload_sd_cp_and_chk_file_data failed! Do you have a different micro SD card you can try? That error message looks as if it is failing reading the update from the SD card.
Guest twrock Posted September 18, 2010 Report Posted September 18, 2010 (edited) I would also try to partition and format your sd card on your computer. Copy both the time machine dload and the official 2.1 dload (name out it something else temporarily) folders on to the card while it's in the computer. Then try flashing time machine first, then change the folder names (via recovery/mount usb or by pulling the card out and doing it in your computer) and flash the 2.1 official updata. I would not try to flash anything via recovery until you have a working official rom. Maybe one of your updata files got corrupted. Good luck. Edited September 19, 2010 by twrock
Guest Markus Arnold Posted September 18, 2010 Report Posted September 18, 2010 Do you have a different micro SD card you can try? That error message looks as if it is failing reading the update from the SD card. Thanks, i already tried that, same problem: update fails. logfile on the other sd says the same: **** SD download log **** (fread_retry >= SD_FILE_RD_RETRY) failed! dload_sd_cp_and_chk_file_data failed! I would also try to partition and format your sd card on your computer. Copy both the time machine dload and the official 2.1 dload (name out something else temporarily) folders on to the card while it's in the computer. Then try flashing time machine first, then change the folder names (via recovery/mount usb or by pulling the card out and doing it in your computer) and flash the 2.1 official updata. I would not try to flash anything via recovery until you have a working official rom. Maybe one of your updata files got corrupted. Good luck. i don't have a micro sd cardreader, so i can't try that :lol: But i tried again to flash the official uk 2.1 after i had flashed the timemachine: update fails. Here as well the logfile says the same.
Guest twrock Posted September 19, 2010 Report Posted September 19, 2010 (edited) Thanks, i already tried that, same problem: update fails. logfile on the other sd says the same: **** SD download log **** (fread_retry >= SD_FILE_RD_RETRY) failed! dload_sd_cp_and_chk_file_data failed! i don't have a micro sd cardreader, so i can't try that :) But i tried again to flash the official uk 2.1 after i had flashed the timemachine: update fails. Here as well the logfile says the same. I think you seriously need to consider formatting your SD card on your computer with only one big fat32 partition and start over. I think it is well worth the minimal investment in a micro sd card reader. (Well, where I live, I can buy one at the local grocery store for the equivalent of US$1.50.) :lol: And redownload all the roms you are using. Don't assume you don't have a corrupted file. Run the checksums if you can. Just to try to give you some hope still, I have had problems with flashing roms at time. I have thought all was lost, only to finally get something working after many attempts to get things back to normal. But going back to the start and redoing everything from scratch, by the book, has eventually worked for me. What I mean by that is that I specifically don't use the "utilities" available on the phone such as custom recovery roms, etc., if I don't have to. I do it just the way that Huawei suggests by actually removing the card and doing all the partitioning, formatting, file copying, etc. on my computer. I did not use any custom recovery image during the process. I did not use recovery at all. I'm sure you've done it all already, but just try again. Particularly, make sure you delete one /dload folder before copying over the other, making sure there is no "mixing" of the files. For that matter, delete everything that is not necessary. Oh, and you do not need to flash the December update after the time machine. Try going straight to an official 2.1 rom. (Personally, I like the Tre rom, but then, I need the extra space in /system for my modified roms.) (Incidentally, just for the future reference for anyone reading this thread, the "time machine" seems to me to be nothing more than a small change to a setting in the phone that lets you then flash some other official rom. It isn't a full rom, and doesn't replace what you had. So if it wasn't working before you flash that, it isn't working after either; you still need to flash something else on there.) And, rarely does my phone reboot after a successful updata flash. No matter what it says it's doing, I almost always have to pull the battery. Also, while I'm grasping as straws, try the second time machine Huawei released. It probably won't do a thing for you, but until you try, you never know: http://android.modaco.com/content/t-mobile...w-time-machine/ I can't speak to what happens with this newer time machine. It might be really bad. I don't know; I haven't used it. Oh, I suspect it will boot into fastboot mode, right? (volumedown + endkey and you end up with a blue screen with some white text) If so, there are still other things to try if all else keeps failing. Finally, I'm no guru. I only know what I've done, and what has worked for me. But that means that my suggestions might end up making things worse. You have to decide for yourself if something is a good idea or not. I have had serious problems that somehow got resolved. I just kept trying. Edited September 19, 2010 by twrock
Guest Markus Arnold Posted September 19, 2010 Report Posted September 19, 2010 I think you seriously need to consider formatting your SD card on your computer with only one big fat32 partition and start over. I think it is well worth the minimal investment in a micro sd card reader. (Well, where I live, I can buy one at the local grocery store for the equivalent of US$1.50.) :lol: First of all: Thank you for your post! You really gave me some hope! :) Yeah, you're right, i'll buy one as soon as the stores open up again tomorrow morning (damn shopping hours - here in germany on sunday all shops which sell card readers are closed...). And redownload all the roms you are using. Don't assume you don't have a corrupted file. Run the checksums if you can. I did that at least 2 times per file but already start the downloads again :( . How can i run the checksums? (i'll google that later...) Just to try to give you some hope still, I have had problems with flashing roms at time. I have thought all was lost, only to finally get something working after many attempts to get things back to normal. But going back to the start and redoing everything from scratch, by the book, has eventually worked for me. What I mean by that is that I specifically don't use the "utilities" available on the phone such as custom recovery roms, etc., if I don't have to. I do it just the way that Huawei suggests by actually removing the card and doing all the partitioning, formatting, file copying, etc. on my computer. I did not use any custom recovery image during the process. I did not use recovery at all. Are there some specific settings/instructions for formatting the SD (working with windows 7)? I'm sure you've done it all already, but just try again. Particularly, make sure you delete one /dload folder before copying over the other, making sure there is no "mixing" of the files. For that matter, delete everything that is not necessary. Oh, and you do not need to flash the December update after the time machine. Try going straight to an official 2.1 rom. (Personally, I like the Tre rom, but then, I need the extra space in /system for my modified roms.) Yeah, i'll gice Tre a try. What did you mean with the /system space? (Incidentally, just for the future reference for anyone reading this thread, the "time machine" seems to me to be nothing more than a small change to a setting in the phone that lets you then flash some other official rom. It isn't a full rom, and doesn't replace what you had. So if it wasn't working before you flash that, it isn't working after either; you still need to flash something else on there.) And, rarely does my phone reboot after a successful updata flash. No matter what it says it's doing, I almost always have to pull the battery. Also, while I'm grasping as straws, try the second time machine Huawei released. It probably won't do a thing for you, but until you try, you never know: http://android.modaco.com/content/t-mobile...w-time-machine/ I can't speak to what happens with this newer time machine. It might be really bad. I don't know; I haven't used it. Good to know it's not just my pulse, which hangs at restarting everytime... I already have used the new time machine - no difference for me. Oh, I suspect it will boot into fastboot mode, right? (volumedown + endkey and you end up with a blue screen with some white text) If so, there are still other things to try if all else keeps failing. Yes, i can use all the features which dont need the touchscreen - such as fastboot mode (vol-, red, power), custom recovery mode (RA-pulse-v1.5.2 - directly with red, menu, power) and the update mode (vol+, red, power). Finally, I'm no guru. I only know what I've done, and what has worked for me. But that means that my suggestions might end up making things worse. You have to decide for yourself if something is a good idea or not. I have had serious problems that somehow got resolved. I just kept trying. Thanks a lot, man! You really gave me hope and something to work on. Cheers!
Guest Markus Arnold Posted September 19, 2010 Report Posted September 19, 2010 Really good news: I got Tre installed and the touchscreen works again!!! Great! I'm really reliefed not having bricked my pulse... :) Looks like everything is working really fine. (just once the touchscreen didn't work, but after a restart it was alright again) I think that was what you ment: I have just 40mb free space left on the internal memory. Is it possible to get app2sd or to install FLB on this ROM? What would you recommend (especially in my case with a history of failing updates :lol: )? Thanks to all of you how gave me advice!
Guest LorianNod Posted September 19, 2010 Report Posted September 19, 2010 You really need to try a different SD card too.
Guest Markus Arnold Posted September 19, 2010 Report Posted September 19, 2010 You really need to try a different SD card too. I tried 2 different sdcards and there was no difference. But finally it worked out (using my 16gb sd and the tre update)
Guest twrock Posted September 19, 2010 Report Posted September 19, 2010 (edited) Really good news: I got Tre installed and the touchscreen works again!!! Great! I'm really reliefed not having bricked my pulse... :) Looks like everything is working really fine. (just once the touchscreen didn't work, but after a restart it was alright again) I think that was what you ment: I have just 40mb free space left on the internal memory. Is it possible to get app2sd or to install FLB on this ROM? What would you recommend (especially in my case with a history of failing updates :) )? Thanks to all of you how gave me advice! SUCCESS!!!! :( I just love it when things work out. :lol: Yes, you see the difference between the Tre and UK roms (well, at least one of them). You have less free space with Tre. But, I need that extra /system space in the Tre rom to install the Chinese handwriting recognition software, so I only use the Tre update for my base system to work off of. The roms I've modified won't fit in the UK rom partitions. There are some rooted/a2sd roms based on the Tre rom (in particular in my case, I have modified the Tre rom to create the TWeak rom), but I suggest you look at FLB 1.6a (or FLB 1.5 if you have no intention of using swap). Yes, you can install any FLB or other UK based modified rom onto your phone even though you updated with Tre. You just have less user space. But the good news is that now that you have it working, you can flash the UK official rom if you prefer and if you dare. :( :lol: (But I don't remember if you have to do the time machine again or not.) Enjoy, and as Mr. Churchill once said, "Never give up." (Well, actually I think he said "Never give in," but that doesn't fit as well here, so I'll stick with the misquote.) Edited September 19, 2010 by twrock
Guest Markus Arnold Posted September 19, 2010 Report Posted September 19, 2010 yeah, always great if something works out when you wouldn't expect it anymore! Thanks alot for your help! Probably i'll give FLB1.6a a try, but first i' make 2 or 3 backups (and hope that one of them should work in case i get into trouble again :lol: - do you know if theres an easy way of checking a backup if it works? ) and get my sd partition ready for it. We'll see how it goes :) Cheers mate!
Guest AntonioPT Posted September 19, 2010 Report Posted September 19, 2010 yeah, always great if something works out when you wouldn't expect it anymore! Thanks alot for your help! Probably i'll give FLB1.6a a try, but first i' make 2 or 3 backups (and hope that one of them should work in case i get into trouble again :) - do you know if theres an easy way of checking a backup if it works? ) and get my sd partition ready for it. We'll see how it goes :( Cheers mate! Well, you can always make the backup and then restore it! If it works, then the backup is OK :lol:
Guest milinho Posted September 29, 2010 Report Posted September 29, 2010 Markus, could you tell me what exactly you did, because I have the same problem as you. Difference is that I have 1.5. and when I tried to install offical 2.1. T-Mobile UK ROM, the update failed, and touchscreen doesn't work anymore. So, could you give me some directions, because I'm afraid that something might go wrong.
Guest Markus Arnold Posted September 29, 2010 Report Posted September 29, 2010 Markus, could you tell me what exactly you did, because I have the same problem as you. Difference is that I have 1.5. and when I tried to install offical 2.1. T-Mobile UK ROM, the update failed, and touchscreen doesn't work anymore. So, could you give me some directions, because I'm afraid that something might go wrong. hey milinho, i couldn't get back to 1.5, BUT i could install 2.1 finally. I did it that way: -Flashed AmonRa Recovery, -wiped everything (data/factory and dalvik!), -put timemachine on sd (folder dload) -shut phone down (u can take the batt out) -started device with "vol+, red, power" into upgrade-mode -> should work, maybe it will get stuck at restarting, but thats all right, after some minutes just take out the batt -started again in recoverymode (if u have flashed amonra u can use "red, menu, power"-combination) -put TRE 2.1 update on sd -again turn phone off, -start update mode and hope for it to work. If if fails try update again. The TRE was the only update which didnt fail on my device, so hopefully its the same with yours. If you dont have the updates downloaded yet, just use the search function, shouldnt be to hard to find. :lol: Good Luck!
Guest milinho Posted September 29, 2010 Report Posted September 29, 2010 I did it, touchscreen works again :lol: B) Thanks Markus, you really helped me a lot. Funny thing, it didn't work with TRE ROM, but with UK ROM (after several attempts) update was succesfully installed.
Guest Markus Arnold Posted September 29, 2010 Report Posted September 29, 2010 I did it, touchscreen works again :lol: B) Thanks Markus, you really helped me a lot. Funny thing, it didn't work with TRE ROM, but with UK ROM (after several attempts) update was succesfully installed. great to hear that your phone works again!
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now