So I have a broken sd card port, which does not read my sd cards anymore. And I was already on scoot's latest android build, but what do you do when something is broken? Well, you go back to factory settings and for our blessed HTC Kaiser or in my case MDA Vario III, this means going back to the abomination called WM (and to make matters even worse it is tmobile themed). But it seems that this also doesn't fix the problem and the sd card is still not read. It does say it needs to format the sd card for it to work, which I then give the permission to do, but it is never able to finish the format.
So my question is fairly simple: how to flash android on your WM device with usb?
thanks in advance!
( I am really stupid, going back to WM )
**I have looked for other guides, but they all assume you to already have android installed on your phone**
It sounds like the ribbon cable is broken for the SD card. The only fix is to replace it, unless there is some other problem with the main board.
So how am I suppose to replace this "riboon cable" do I need to buy some extinct hardware specifically for the kaiser (which probably is impossible to get?) or can I do it some other way. And is there really no way to flash Android on the kaiser via usb, since I think I can manage with only a couple of apps on the internal storage...
Also I have already tried to flash android on my htc kaiser:
- I dragged and dropped the KAISIMG.NBG over the installer of my original t-mobile rom, but somehow it just installs the original rom again and not the KAISIMG.NBG
AFAIK, the only 2 ways to flash anything to a Kaiser is through the SD card or USB port. Noone (to my knowledge) has ever created a RUU-flashable Android package for the Kaiser or any other device, which would be your only option.
Given the constraints on the RAM built into the Kaiser, you would have to build a pretty small package for the install, maybe 55-60MB, use Oli's NBH creator and (hopefully) build an installable package that can be sent via USB with an unsigned RUU updater.
If someone wants to take on the task of stripping an androidinstall package, extracting it and repacking it into a RUU installable NBH, feel free. I know it can be done with a kernel package, but that is only 3MB and goes to the first partition. All the other files would have to go to the correct partitions as well (/system, /data, /cache, etc.).
So how am I suppose to make an installable package? I have the file to get WM to Android, the kernel, and scoots android install package, which I have stripped down to 67 mb.
What should I do with these files? Do you have some kind of instructions?
You would have to figure out how to not only partition the NAND, but direct the kernel and all files to their appropriate partitions.
Someone must have some info on how to do this...
Sent from this addictive thumb magnet...
Related
So I've flashed my Hermes more times than I can remember. But I'm reformatting my laptop to a minimal installation state. I don't want to install active sync unless I have to. The only thing I ever use it for is to flash my Hermes. So I'm going to try the SD Card method found here: http://wiki.xda-developers.com/index.php?pagename=Hermes_SDCardFlashing
My questions are:
Is this method still valid? Much has changed since this was posted, and I wanted to make sure that each step was still correct.
From the wiki: "SuperCID devices are able to flash any NBH image using this method." I have my Hermes with Hard-SPL-V7. That covers the SuperCID part right?
I will be flashing my Hermes to K's final 6.0 ROM. He has a feature to auto install cabs found on the SD card. I've done it before flawlessly. The wiki calls for a reformatting of the SD card. Is it ok if I still put cabs and the config file on there to auto install the cabs?
EDIT: Looks like I haven't been keeping up. Seems like this is now called User Customization and is pretty wide spread. So to rephrase, can an SD card be used to both flash and provide user customization?
This last question is just curiosity. I haven't tried any 6.1 roms yet. I was waiting for kin0kin to make a non beta one, but it looks like he's stopped development. Are the 6.1 Roms still unstable? Which one most resembles K's roms (stable, no bloat)? I never tried any other cooks outside of vp3g and kin0kin because it seemed like other cooks were more about making as many new roms, as quickly as possible rather than hammering out one very stable rom. Now that kin0kin isn't making a 6.1, who should I turn to?
You should be OK with Hard SPL ver 7 installed. And yes, you should still be able to put the auto config file on the sd card. I generally got the ****s with backing up my sd card to pc, formatting and then having to transfer EVERYTHING back onto the card so just usually put the .nbh file on my sd card AS IS... Never had a problem with flashing. I think we are told to reformat the card as a safety precaution but I've never had problems.
As for wm 6.1, It depends, as what is stable to one person insnt to another... Its common belief that if you flash a stock rom first you wont have any troubles... If you want to try there a few lean roms, FariaDrP clean rom, Hermes_ShadoW_2.1_CE, PV DVH G&C and the "unnamed" wm6.1 to name a few. A search on the forum should find these for you... Cheers, and happy flashing...
thanks for the response.
When you say AS IS, do you mean you don't rename it or anything. Or as in, just putting it on there without reformat AFTER the renaming.
For the 6.1, when I say stable I mean everything works as advertised. No adverse effects like hangs and shutdowns. Is the upgrade even worth it? Is it actually faster? I don't use IE, so that upgrade isn't really needed.
As you've already formatted the card fat 32 to use I just put the .nbh file onto the root directory BUT rename it "hermimg.nbh" otherwise it wont be recognised as a os flash. cheers...
Hey ya'll, I have a simple question.
I want to know if I can flash the ext rom from another HTC device onto my BA ext rom?
I just installed the 142 Tmo Uk rom, and was curious if I can grab the ext rom off of another Tmo USA device, so I have all the right settings and stuff?
TIA!
i wouldn't think so. may be able to do it, i wouldn't attempt it. i stripped my extrom, they don't actually have anything useful in them. just horrible themes and bad software.
you however could probably extract the extended rom from another device and copy the files and manually install them. that'd be easy enough i think.
yeah, flashing a rom from another device is not such a good idea, but since you are using wm2003, you can visit -=this tutorial=- and gain another 16mb of storage space and then just copy cabs that you want to the device or maybe even build you own extrom, to be copied to the sd card and installed automatically. to find out how that is done (actually pretty easy!) just use forum search and look for "cfg.txt" and Chef_Tony. i wrote some pretty long tutorials about that.
basicly it is just making an automated install routine for your most commonly used programs, so whenever you hard reset your device, the programs YOU want are installed, not those ridiculous t-mobile customizations, their pink dialer skin and things like that.
EDIT: btw. you should never take an entire extrom of another device. you never know, if maybe some of the things installed by the extrom are dependant of the display resolution or use device specific interfaces or mess around with device specific hardware buttons or drivers, you should extract the cabs and google their names, if you are not sure, what that actually does, so you can be sure, it will work on your blueangel!
have fun with that.
and @cerjam: don't be offended, your answer is completely right, i agree, just wanted to add a few little things
Perfect answers!
So, chef_tony, your telling me that it's ok to merge my extrom and storage in wm2003se? and then copy my cabs and write a cfg.txt of my own for an sd card?
I realize that I should do all the reading, but I'm the kinda guy who needs a generalized big picture before I start ripping apart all the details, so I'm looking for **** and jane/oversimplified answers.
Thanks, guys (and gals, if you are one)
does any one know of any android 2.0 cabs for vogue
There is a port but it has very limited functionality. Also, it does not come in cab. You have to place a bunch of files on the root of your SD card and run a program called haret.exe which will load the root file system as well as the kernel to run the OS.
Go to the general vogue section. You will have all the necessary info there. This section is only for WM upgrades.
every time in try it that way it wont work and i follow the insructions exactly and i did find a cab and it worked i tryed switching out the files but every time i try to run it it says failed to find system.img even though it named right and on the root of my sd
The cab version is probably a year old now. The files that were in that version will no longer work with current roms. There isn't a current all-in-one installer that I've come across that will run current versions of Android.
The new system images come with a .sqsh extension.
As the previous poster mentioned, the Vogue general forum has more Android related information.
Also, in case you guys are interested, dzo just came out with a flashable version of Android for the Vogue. In other words, you will install Android to the NAND rather than the SD card and wipe out WM in the process.
http://forum.xda-developers.com/showthread.php?t=593786
It would be nice if someone were to come up with a cab that installed android
But unfortunately it would be a lot of work and instead you have to run it on an sd card via haret (though its not that much more difficult)
And zen just came out with a new android 2.0 (eclair) build so you should go check that out!
kiwilime said:
It would be nice if someone were to come up with a cab that installed android
But unfortunately it would be a lot of work and instead you have to run it on an sd card via haret (though its not that much more difficult)
And zen just came out with a new android 2.0 (eclair) build so you should go check that out!
Click to expand...
Click to collapse
Someone did make a cab. http://www.myhtcphone.com/Android120208.CAB from here http://www.myhtcphone.com/ it is old but it has been done and it does work.
Hello,
I need some help. Install its Android OS, but after he reset my Kaiser again charged WinMo OS. My question is whether it is possible to choose which OS to load first or with any program or edit the file to indicate to launch the first Android.
Sorry for my bad english :S Use Google translator
If you have installed Android to SD card and use Haret.exe then it will always reboot to WM.
You must install to nand if you wish to boot to Android only, which will wipe WM totally and replace it with Android.
The guide stickied at the top of the forum is a good tutorial in doing this
That does bring a good point to my mind though, we could create an exe that loads at startup of wm to auto load haret and startup if the user doesn't cancel in so many seconds (like grub). I keep WM on my phone so I can easily change my droid version and also I know everything works including opening office files (actually that's the biggest sticking point for me keeping it).
Thanks for support. Today I try to flash via NAND method.
Kind Regards
Lybomir
I flash my Kaiser with latest zImage-2.6.32-froyo-09-09-10_21 from here http://it029000.massey.ac.nz/vogue/files/?C=M;O=D and my device loading Android OS very slow, and big problem is : Phone go in screensaver and I try to unlock and screeen stay only in white light, no picture, no widgets... total block. Only solution is it a use Soft reset button or remove batery
Maybe you choose the wrong panel type?
I can read in your signature Duo Boot so I guess you installed onto the SD and use Haret to run Android.
If so, you have to edit the default.txt file locate in ANDBOOT folder and modify the value following htckaiser.panel_type.
You can specify 1, 2 or 3 (most Kaisers use panel type 2)
Wrong panel type may lead to awake problems or wrong colors...
The excessive slowness may be due to a slow SD. Which class is it? Use at least class 4 SD.
---- EDIT -----
In case you already flashed to NAND, to change the panel type you have to choose the right kernel (the kaisimg file) or you can edit the one you flashed following instructions and links you can find in #4 at http://forum.xda-developers.com/showthread.php?t=680518
obviously you have to reflash the kaisimg.nbh but you don't need to flash Android again
I try with 1,2 and 3 but every time show me a this problem, and now i run HaRET and in 2 from 3 times phone block and not response only Soft reset work, and if case phone load complete Android and again in screen seaver system not respond... ;(
I flash my phone with ext2 partition on my sd card/ class 4 8 GB SDHC/ and try with system and data on sdcard an again freez white screen/
Sorry for my bad english
dlink.bg said:
I try with 1,2 and 3 but every time show me a this problem, and now i run HaRET and in 2 from 3 times phone block and not response only Soft reset work, and if case phone load complete Android and again in screen seaver system not respond... ;(
I flash my phone with ext2 partition on my sd card/ class 4 8 GB SDHC/ and try with system and data on sdcard an again freez white screen/
Sorry for my bad english
Click to expand...
Click to collapse
May you try to install a different build and see if you fall into the same problem?
BTW, just after installing, don't start playing soon with the device: initially skip all settings (touch the android, don't set google account and so on) and leave the phone quiet for at least 10-15 minutes: some builds need to copy file to the cache and playing with the device may interfere with this operation leading to unpredictable effects...
Let we know...
It is slow because you installed it on sdcard.. both partition.. if you are on nand. Try install both partition on nand partition.. and try hawks soad rls 3 as me.. its fastest build for kaiser.. and I haven't ever problem with white screen ata awake.. try it in that haws soad ion build.. you can finf it in that forun.. just find it
Sent from my HTC Kaiser Ion using XDA App
I find a solution! Later I post how find solution
Thanks on every in this thread to help me!
dlink.bg said:
I find a solution! Later I post how find solution
Thanks on every in this thread to help me!
Click to expand...
Click to collapse
You're welcome
And I'm waiting to know
Don't suppose any of you have actually seen this thread?
Gen.Y DualBOOT v1.0.6.0
Should work fine on Kaiser, certainly works fine on other devices, such as Diamond, Blackstone etc
zenity said:
Don't suppose any of you have actually seen this thread?
Gen.Y DualBOOT v1.0.6.0
Should work fine on Kaiser, certainly works fine on other devices, such as Diamond, Blackstone etc
Click to expand...
Click to collapse
Hi Zenity... Yes, know that piece of software.
But as You have to boot WinMo (Yes, I Know, not all the services need to be running but system must be loaded and started, GUI must be running and so on) in order to DualBOOT can start, I can guess it's only a partial time-save... isn't it? Did You tried it?
Have not tried it on my Kaiser, since it is Nand flashed, but I think it is what was being asked for really, a way to boot either WM, or straight into Android on SD.
I don't think it will ever be possible for both WM and Android to co-exist on nand, since there simply is not enough room on the internal memory for both.
It is a time saver on other devices I have tried it on, Diamond, Blackstone, however since neither of these devices is nand-flashable this is more what Gen-Y's dual boot was intended for.
If it was possible to run WM from SD then we might be able to truly Dual Boot, in a similar fashion to Windows/Linux on PC, but as far as I know this is not possible either.
zenity said:
Have not tried it on my Kaiser, since it is Nand flashed, but I think it is what was being asked for really, a way to boot either WM, or straight into Android on SD.
I don't think it will ever be possible for both WM and Android to co-exist on nand, since there simply is not enough room on the internal memory for both.
It is a time saver on other devices I have tried it on, Diamond, Blackstone, however since neither of these devices is nand-flashable this is more what Gen-Y's dual boot was intended for.
If it was possible to run WM from SD then we might be able to truly Dual Boot, in a similar fashion to Windows/Linux on PC, but as far as I know this is not possible either.
Click to expand...
Click to collapse
Yes, of course we haven't enough NAND to have both OSes!!!
What I was thinking to (but I'm a lot far to inspect WinMo booting sequence...) is if may be possible to wedge a sort of bootloader running BEFORE the OS loads or in the early booting process and letting we choose to boot WinMo (in NAND) of Android (on SD).
At present moment I've Android running from SD but kernel NANDed (I've got problems running out of NAND and no time to solve them so I'm using the solid build previously installed on SD) so Kaiser boots quickly... and this confirms it's possible boot SD Android without having to load WinMo or Haret. The more relevant matter I can see is that we have to find a way to wedge the bootloader without have to manual modify the WinMo ROM (virtualization is far from be considered on such devices...)
I suppose this is just a "mind exercise" (Sorry, I don't know how to correctly translate an Italian common saying...
Mind exercise describes it perfectly
Not sure why you would run out of space on nand, unless you are loading a lot of apps, and there are ways to run android that may help with that, such as apps2sd, or data on SD partition.
If you must have WM then your only choice would be using Haret.exe, and the most efficient way to dual boot we have at the moment is the Gen-Y solution, which is not ideal, but does offer at least part of what you seek.
The Android bootloader we use (tinboot.s) is not flexible enough to allow dual booting, but may have some information that may be of some use in this
tinboot thread
See what you think anyway
Sorry, I was not able to be clear... I apologize for my English...
When I said "I've got problems running out of NAND" I intended to say "I've got problems - very bad performances - when Android was running from NAND"!!!
Maybe we are a bit OT...
BTW, I was far from software developing for a long while and never developed low level software for Linux/Unix... but in the past I messed up with Z80, 65xx, 68K and x86 platforms's assembly
Recently I need to approach software developing again (but at a really different level...)
I'd like to have spare time to start again, as this world attracts me more. Maybe I'll give it a chance...
Let me understand... tinboot is actually used bootloader?
BTW, just to be clear... I don't need WinMo and I'm giving Android a chance to revive my Kaiser. I'm looking for a fast and stable build and actually I'm running VaniljEclair RLS11 (Yes, I know, I'd try your Polymod 2.1D build... )
Tinboot is the bootloader we use to get android in nand, not being a coder my understanding in limited, however I did think that thread may have useful information for anyone interested in the low level workings of out devices.
I assumed you meant running out of space on nand, lol, i see now what you mean, no need to apologise for you english, it's fine
zenity said:
--- CUT ----
however I did think that thread may have useful information for anyone interested in the low level workings of out devices.
Click to expand...
Click to collapse
And you're right... it's a useful starting point and I'll read it accurately...
Unluckly, I need a lot of spare time (and I don't, at present) to build a solid knowledge base and to start developing for Android.
yes there should be plenty of room for both oses on Nand, I still have over 90 mb on my wm6.5 nand install with come extra apps in there. So if you stripped down both oses you could easily fit them both on nand and still some space left. But then you need to have a boot loader that will be able to load both oses. I think I heard someone say somewhere they are using grub to boot android from nand, that can boot windows also with the right configuration, that would be where to start.
Is it possible to install Android on Kaiser without SD? Has anyone investigated bundling the /system partition with tinboot so the whole thing is installed with a single KAISIMG?
I ask because I have one Kaiser whose SD reader is broken. If I could install more than a kernel, I could try risky changes to fix the NAND driver. If I brick the phone or kill its flash, it's no big loss.
No, you can't do it now, maybe i can suggest you to look after a method do dump the nand after install and use it as kaiser image
Exactly what I was thinking, but how to negotiate the NAND into the proper size partitions? Write kernel for rom and hope you get the sizes right, or make a kernel that readjusts /system size based on install and leave remainder for /data?
PoXFreak said:
Exactly what I was thinking, but how to negotiate the NAND into the proper size partitions? Write kernel for rom and hope you get the sizes right, or make a kernel that readjusts /system size based on install and leave remainder for /data?
Click to expand...
Click to collapse
I don't think thats l1q1d idea... perhaps a complete nand dump, and reflash it to another kaiser.
The kernel and partitions must be configures before the dump...
I do intend to try, but have been distracted by Scoot's very stable kernel, and a very nice pre-beta that I'm testing on my HTC Wizards, Gandalf and Radagast.
This is possible, in fact there was a time where an empty img file was being incorporated into the NBH where on a windows NBH the system files would normally be copied. A windows NBH consists of a number of parts, I can't remember what they are all called right now, but they can all be merged using NBHmerge. I can't give you specific instructions but there's no reason why it can't be done, not sure it'll be much fun though!
n2rjt said:
I do intend to try, but have been distracted by Scoot's very stable kernel, and a very nice pre-beta that I'm testing on my HTC Wizards, Gandalf and Radagast.
Click to expand...
Click to collapse
pre-beta that you're testing on HTC What ??
daedric said:
pre-beta that you're testing on HTC What ??
Click to expand...
Click to collapse
HTC Wizard. I have two of them, which I have named Radagast and Gandalf. It's my all-time favorite smartphone, although it is obviously even more obsolete than the Kaiser. I use one of them as my primary phone whenever Android is giving me fits. Right now I'm testing H3r7 beta 2 preview where the cook has adeptly squeezed WM6.5 into a tiny, fast, stable package.
If I knew that I wouldn't have given my Wizard away...
I thought Ham3r was finished when he hit 6.1 but I stand corrected...pfft.
help androidinstall.tgz
please share for me : file androidinstall.tgz 2.1 or 2.2 but must run wifi and 3G.
Send for me by: [email protected] thanks i come from VietNam
I think with the proper memory map Android could be installed via FrankenKaiser or something of that sort. Something that addresses the NAND directly through OEMSBL, bypassing the need for a HardSPL. Of course the phone would have to be CID unlocked to do this, but I think it's possible to install via CustomRUU if the mapping was done beforehand.
I have read somewhere that NAND marked as bad in the map still gets "written" to, meaning whatever is supposed to go there is put there and never read. Once unmarked the written info comes back, but that requires a full format anyway.
I say very possible...
I have stopped trying to do this, but wanted to record my latest thoughts in case someone reads this in the future.
I think the best way to install Android on a Kaiser that can't read its sdcard is to edit the initrd then use recovery mode:
* install adbd so it gets started in recovery mode
* allow the menu when sdcard is not installed
* change scripts to look for /data/andboot
* change recovery mode to mount /data partition to usb
Then, of course, you boot the kernel, use the menu, enter recovery mode, transfer androidinstall.tgz and androidupdate.tgz to /data/andboot, then install system, install updates, clear data, and run. If something doesn't work, adb shell or adb push can help.
I think it's too much work to be worth it on this old phone.