Jump to content

m2te

Members
  • Content Count

    42
  • Joined

  • Last visited

Community Reputation

0 Neutral

About m2te

  • Rank
    Newbie

Contact Methods

  • Website URL
    http://
  • ICQ
    0

Profile Information

  • Your Current Device(s)
    HTC Desire; T-Mo Pulse Mini
  1. My vibrate function seems to have stopped working after this. Maybe it happened as part of the bootloader unlocking, not sure. Anyone else got the same problem?
  2. Hi, I think gforums is on his hols so I'll chip in with some info, I was working through a lot of this around the same time as gforums and we helped each other out a bit, we both released a rom, mine which is more stock with all (most) of the T-Mobile pink removed and gforums with a similar base but more mods for eyecandy and features. First thing, where did we learn this? Reading every relevant forum post we could find. Where did I Start? I downloaded come custom roms for the Pulse then extracting the contents to try to understand what's in them, I needed to understand them to understand how to create them. I know it's not the same phone but it is similar enough. After that I needed to find a base rom for the custom rom. For most other phones this is easy as other clever people have got there first and done all the hard work for us but not for the Pulse Mini, or atleast I couldn't find it. So I downloaded the stock rom from the Huawei site then found a way to extract it. Once extracted my next step was to understand the file system, then creating an update.zip without making any changes and seeing if it works, once I understood how to build working update.zip files the modding began in earnest. Look at the Pulse forums, there is loads of good info in there including tools to extract the rom- http://android.modaco.com/content/t-mobile...at-youre-doing/ http://android.modaco.com/content/t-mobile...s/#entry1138862 Once you got the updata extracted you need to find which file is the img for the system then you'll need to unyaffs it to extract the contents. There's loads more to get your head around, some more links- http://android.modaco.com/content/t-mobile...e-official-rom/ http://android.modaco.com/content/t-mobile...e-2-1-lite-rom/ http://android.modaco.com/content/t-mobile...0/#entry1361510 http://theunlockr.com/2010/03/26/how-to-cr...up-the-kitchen/ http://theunlockr.com/2010/04/15/how-to-cr...your-first-rom/ http://android-dls.com/wiki/index.php?titl...ack_Boot_Images
  3. Have you searched and had a look at some of the other topics on this forum? Namely This Topic. It may help.
  4. I'm using Notepad++ http://notepad-plus-plus.org/ And the hex editor plugin from- http://sourceforge.net/projects/npp-plugins/files/ I open the boot.img file in Notepad++, change the view by clicking on the 'Plugins' menu follwed by 'HEX-Editor' then 'View in HEX'. You should get a view something like- Adress 0 1 2 3 4 5 6 7 8 9 a b c d e f Dump 00000000 41 4e 44 52 4f 49 44 21 d0 22 24 00 00 80 20 00 ANDROID!........ 00000010 08 8c 02 00 00 00 20 01 00 00 00 00 00 00 10 01 ................ 00000020 00 01 20 00 00 08 00 00 00 00 00 00 00 00 00 00 ................ I have been copying the first sixteen bytes (41 4e 44 52 4f 49 44 21 d0 22 24 00 00 80 20 00) from the working boot.img to the rebuilt boot.img and the four bytes as position 0x14 to 0x17 (00 00 20 01). Without doing this the boot.img doesn't seem to boot; for me anyway, I don't know how gforums got on with rebuilding the boot.img. For some reason the mkbootimg tool doesn't seem to get the header correct. You may not need to do any of this, you can try booting the boot.img from within fastboot without actually flashing it. Connect the phone to your computer, start it up in fastboot then use the command 'fastboot boot <boot.img file name>' on your computer. This should download the boot.img file to the phone and boot it, if it works flash it, if it doesn't try tweaking the boot.img file.
  5. Apologies, I will get around to answering you, I've got a spam problem at the moment though
  6. Windows 7 32bit. I am running adb-windows.exe from the 1.6.2-pulsemini-amonrarecovery package.
  7. Sorry for hijacking a thread, I'm just wondering what a task killer gives us? I'm new to Android but so far I have not experienced any problems that I could imagine a task killer would fix, Iv'e not suffered poor performance or memory errors.
  8. The Pulse Mini always seems a picky about ADB access, there is a post on this forum somewhere about it. Have you tried it when in 'recovery'? It works for me when I launch AmonRA Recovery 1.6.2, I'm able to remove, add files etc. Also when I reboot using the 'Reboot' option in the recovery console, ADB access seems to work once the pgone is booted.
  9. Easiest thing to do is install either one of the two custom roms available on this forum. Both have Busybox intregrated into the rom.
  10. Thanks for that, I'll roll some of your changes back in to my rom in a few days, namely the info we had from flibblesan and your fix for the Gallery FC as I suffer from the FCs as well. Stuck for time at the moment though. I'll won't add the a2sd scripts but I'll make the mods to the init.rc to make it compatible.
  11. I would be very interested for info on your kernel changes, I tried to download your latest pulse rom earlier to take a look but I couldn't download it for some reason. Good to know about the a2sd changes, I put the code right at the end of init.rc script. I'll change that for the next boot.img release. Thanks, Mike.
  12. Hmm, I think the zip file is about 67MB, the updata.app inside it is about 200 ish
  13. I'm not sure what that would be or do, it's only 403kb. I regularly flash the UPDATA.APP from U8110V100R001C85B215SP02TMOUK.zip I downloaded from the Huawai web site as I'm often screwing up my Pulse Mini. Installing that puts the device back in to a good working state, it's 218MB so it contains the full rom image. I got a perl script somewhere that can extract the contents of the UPDATA.APP, I try to run it over that file in a few days to see what it is.
  14. Thanks for the kind words. Understand what you are saying but I don't think we are in competition, we are both working on different elements in order to make a better rom for the Pulse Mini, I'm currently working on the kernel side of things, my goal being to build a clean working rom without all the pink, maybe add a few optimisations along the way. As I see it gforums is working more on the UI side of things with additional changes and apps for useability and eye candy. Combining the two efforts and we should get both a clean rom and an awesome feature packed rom B) I'll probably continue releasing my clean rom for anyone who wants it but I suspect once it has become stable I'll problaby slow down on the releases. We are both in the learning phase so please join in, an MGG rom would be cool :( Better still maybe we'll end up with a gforums, Gjole86, flibblesan, & mike rom.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.