Guest BigBearMDC Posted May 8, 2010 Report Posted May 8, 2010 Eclair lets you pull out battery and SIM Card without rebooting the device ... that's useful ... kind of :P
Guest DanWilson Posted May 8, 2010 Report Posted May 8, 2010 (edited) Because it is :P I can't reflash the dec update, that means I have to find a workaround for flashing the recovery image... Installing the update was a one-way-road, if I knew that earlier... Why cant you flash the recovery image with 2.1? Or have they fixed all flashing? This is sounding worse and worse... And how is it a one-way-road? :P Eclair lets you pull out battery and SIM Card without rebooting the device ... that's useful ... kind of :D Ermwut? :P Edited May 8, 2010 by DanWilson
Guest BigBearMDC Posted May 8, 2010 Report Posted May 8, 2010 (edited) Why cant you flash the recovery image with 2.1? Or have they fixed all flashing? This is sounding worse and worse... And how is it a one-way-road? :P I can flash everything, but the problem is that it seems like Huawei changed the partition layout. So when I want to flash the recovery image it works without problems, but it seems to overwrite the system or boot partition, and the device just drops me into the eclair recovery. So I have two (working) recovery partitions on my device, but a screwed system or boot partition :/ I have to find a way to flash those images with an specific offset, but I don't know how :D But the good thing is, that the new fastboot mode shows where those partitions start, and how long they are: ptn 0 name='boot' start=304 len=20 ptn 1 name='system' start=324 len=880 ptn 2 name='userdata' start=1204 len=642 ptn 3 name='cache' start=1846 len=160 ptn 4 name='recovery' start=2006 len=38 ptn 5 name='misc' start=2044 len=4[/code] It's a one-way-road because I can't flash any older ROM anymore :P Edited May 8, 2010 by BigBearMDC
Guest DanWilson Posted May 8, 2010 Report Posted May 8, 2010 I can flash everything, but the problem is that it seems like Huawei changed the partition layout. So when I want to flash the recovery image it works without problems, but it seems to overwrite the system or boot partition, and the device just drops me into the eclair recovery. So I have two (working) recovery partitions on my device, but a screwed system or boot partition :/ I have to find a way to flash those images with an specific offset, but I don't know how :P But the good thing is, that the new fastboot mode shows where those partitions start, and how long they are: ptn 0 name='boot' start=304 len=20 ptn 1 name='system' start=324 len=880 ptn 2 name='userdata' start=1204 len=642 ptn 3 name='cache' start=1846 len=160 ptn 4 name='recovery' start=2006 len=38 ptn 5 name='misc' start=2044 len=4 It's a one-way-road because I can't flash any older ROM anymore :D Any really big devs that can help you, or is there any way to rework the recovery flash into just, flashing to the right place? Or is this what your missing. I wish i knew at least something that could help you... :P
Guest BigBearMDC Posted May 8, 2010 Report Posted May 8, 2010 Any really big devs that can help you, or is there any way to rework the recovery flash into just, flashing to the right place? Or is this what your missing. I wish i knew at least something that could help you... :P That's what I'm trying to find out now. If I can manage to flash the recovery and boot images with that specific offset, everything should be fine. I think that the recovery image is located in /system/-something-/recovery?
Guest DanWilson Posted May 8, 2010 Report Posted May 8, 2010 That's what I'm trying to find out now. If I can manage to flash the recovery and boot images with that specific offset, everything should be fine. I think that the recovery image is located in /system/-something-/recovery? Have you tried XDA Devs?
Guest BigBearMDC Posted May 8, 2010 Report Posted May 8, 2010 Have you tried XDA Devs? Not yet, but I have another idea: I'll just open up the UPDATA.APP file, search for a version string, and replace it with the version string I currently have. I don't know .... I'm afraid this could brick my Pulse :P
Guest DanWilson Posted May 8, 2010 Report Posted May 8, 2010 Not yet, but I have another idea: I'll just open up the UPDATA.APP file, search for a version string, and replace it with the version string I currently have. I don't know .... I'm afraid this could brick my Pulse :P Is our recovery file actually compatible for 2.1, or is it 1.5 only?
Guest BigBearMDC Posted May 8, 2010 Report Posted May 8, 2010 Is our recovery file actually compatible for 2.1, or is it 1.5 only? I think with the right kernel it should work.
Guest DanWilson Posted May 8, 2010 Report Posted May 8, 2010 I think with the right kernel it should work. I have an idea! :D Go into a tmobile shop, armed with the pulse usb cable, and a laptop, ask for a "test-run" of a Pulse, then secretly flash it with your laptop, if it breaks just act all innocent and act really thick if they ask you how it happened! :P
Guest BigBearMDC Posted May 8, 2010 Report Posted May 8, 2010 (edited) I have an idea! :P Go into a tmobile shop, armed with the pulse usb cable, and a laptop, ask for a "test-run" of a Pulse, then secretly flash it with your laptop, if it breaks just act all innocent and act really thick if they ask you how it happened! :D Good idea :P But not necessary anymore, I tried it and the update failed :P I think there is a checksum that would have to be regenerated. @McSpoon Do you know where this checksum is? Edited May 8, 2010 by BigBearMDC
Guest DanWilson Posted May 8, 2010 Report Posted May 8, 2010 (edited) Good idea :P But not necessary anymore, I tried it and the update failed :P I think there is a checksum that would have to be regenerated. Ah, well, yes. Keep my idea in mind though. :D Unless I've missed you do it... Cant you just fastboot boot the recovery file and flash the December update / nandroid? Edited May 8, 2010 by DanWilson
Guest Azurren Posted May 8, 2010 Report Posted May 8, 2010 (edited) Bear doing anything else could brick your device.. Perhaps it would be best to try and get the devs of the custom recovery image to create a 2.1 version. I honestly think updating it wouldn't be to hard for the original decs :P Don't do anything stupid Edited May 8, 2010 by Azurren
Guest BigBearMDC Posted May 8, 2010 Report Posted May 8, 2010 I can install and flash any ROM I want, but the TS won't work. Also, the recovery image is working, but overwriting the boot or system partition :P I already have a rooted eclair update.zip ready since 3 days, and I'd like to flash it. But therefore I need to go back to december update, which isn't working. As I haven't got root acces it's also not possible to change the version string of the device itself, and editing the UPDATA.APP file does not work because I have to resign it somehow :D
Guest DanWilson Posted May 8, 2010 Report Posted May 8, 2010 I can install and flash any ROM I want, but the TS won't work. Also, the recovery image is working, but overwriting the boot or system partition :D I already have a rooted eclair update.zip ready since 3 days, and I'd like to flash it. But therefore I need to go back to december update, which isn't working. As I haven't got root acces it's also not possible to change the version string of the device itself, and editing the UPDATA.APP file does not work because I have to resign it somehow :P Sorry for the fail in knowledge, but what is the TS? :P
Guest DarkBytePH Posted May 8, 2010 Report Posted May 8, 2010 I can install and flash any ROM I want, but the TS won't work. Also, the recovery image is working, but overwriting the boot or system partition :P Maybe you should contact Amon_RA with your problem. I guess we need a newer version from the recovery to handle the partition layout of Eclair.
Guest BigBearMDC Posted May 8, 2010 Report Posted May 8, 2010 Yeah that's a good idea. TS = TouchScreen :P
Guest DanWilson Posted May 8, 2010 Report Posted May 8, 2010 Yeah that's a good idea. TS = TouchScreen :P Ahh. I see. I fail. :D
Guest eckengucker1 Posted May 8, 2010 Report Posted May 8, 2010 Hast du einfach mal die Karte rausgenommen und mit GParted formatiert? Did you try to take out the memorycard and formate using gparted?
Guest BigBearMDC Posted May 8, 2010 Report Posted May 8, 2010 Hast du einfach mal die Karte rausgenommen und mit GParted formatiert? Did you try to take out the memorycard and formate using gparted? I think you misunderstood something: I have problems with the partitions on the device, not the SD Card :D Thanks anyway :P
Guest Spooke Posted May 8, 2010 Report Posted May 8, 2010 Woah, Hope you get ur phone working again BigBear :P Yeah I agree with asking Amon_Ra to make a updated recovery, Im sure he could do it :D Good luck
Guest DarkBytePH Posted May 8, 2010 Report Posted May 8, 2010 Hast du einfach mal die Karte rausgenommen und mit GParted formatiert? Did you try to take out the memorycard and formate using gparted? Maybe i'm wrong, but from what we talked about here, the internal memory layout of Pulse is changed with the update to the Eclair ROM, so repartitioning the SD card will not help. Maybe BigBear can try to unsolder the Flash ROM chip and put it into some kind of modified card reader to edit the contents, but i don't think this is will happen. :P
Guest David Horvath Posted May 8, 2010 Report Posted May 8, 2010 Hast du einfach mal die Karte rausgenommen und mit GParted formatiert? Did you try to take out the memorycard and formate using gparted? The problem is with the internal partitions, not with the memory card. I was thinking about the same, but for that you would need a device powered up, without loading the OS and you would need direct (root) access to the partitions.
Guest Spooke Posted May 8, 2010 Report Posted May 8, 2010 BigBearMDC, Is the flashed rom saved in /system? As I found this if its any help to you.. http://www.pocketmagic.net/?p=757
Guest BigBearMDC Posted May 8, 2010 Report Posted May 8, 2010 BigBearMDC, Is the flashed rom saved in /system? As I found this if its any help to you.. http://www.pocketmagic.net/?p=757 Thanks, but if you look at it more briefly, it says "#mount [...]" - '#' means that you're root, and I am not :D I already tried that and it said: "root: permission denied". Thanks anyway :P
Recommended Posts