Two bootimages visible.. - G1 Android Development

Hi there,
using a german device with JF 1.43 holiday..
I have no idea, but I get two different bootimages, first a big white G1 T-Mobile and then the "old" G1 with the magenta T-Mobile logo..
Booting itself is taking longer as before, round about twice the time..
Any ideas?
EDIT:
Okay.. Didn´t know there are two bootimages.. But booting is still a pain..

Related

Probs upgrading T-mob MDA Compact

A friend of mine recently took her T-mobile MDA Compact to a High St vendor to have it unlocked. Whatever they have done to it, they appear to have buggered it up properly.
She gave it to me to try and fix it.
When I got it, it would only turn on to the splash screen with the ROM versions displayed, and wouldn't load any further than that. It also wasn't detectable by Active Sync, so I had no choice but to put it into bootloader mode, and try to restore the ROM on the device in this way, as there was obviously something wrong with what was on it.
The upgrade started fine, using the ROM off the T-mobile web page, completing the Radio Rom upgrade fine. However, when it got to 10% of the Extended ROM, an error occured, and shut the program down:
ROMUpgradeUt.ex.exe has generated errors and will be closed by Windows.
You will need to restart the program.
An error log is being created
I tried this a couple of times with the T-mobile Rom, and got the same result, at exactly the same point.
I thought that perhaps there may have been a problem with the T-mobile UK version of ROM, so I thought as it was pretty messed up anyways, I would try loading another T-mobile ROM on to it. I trie both teh German, and the Dutch registered T-mobile ROM's, getting the exact same error during the upgrade, at exactly the same point.
I then changed computers to try and rule out any possible problem there, and the same result again.
I then proceded to try using the iMate ROM, changing the MaUpgradeUt file to the no ID one, as suggested earlier in this thread, and again got exactly the same result, with the second ROM upgrade stage stalling, and cancelling at exactly 10 again.
Can anybody offer me any assistance with this, or any ideas, or id it possible that the High St vendor has buggered it totally??????
And to boot, the store charged my friend £50 for buggering up her phone, when it is a pretty simple, 5 minute process to unlock one at home!!!!!
I'm no expert but just a thought, it is definately an mda compact and not an mda compact II isn't it? They look the same but are not.
pjam said:
I'm no expert but just a thought, it is definately an mda compact and not an mda compact II isn't it? They look the same but are not.
Click to expand...
Click to collapse
No, I am very sure that it is the original T-mobile UK MDA Compact. I actually have one of each of the Compact and Compact II myself.

Upgrading Problem. Is it a brick now??

First, my palm 750 was having the problem that it got stuck like always, and when it finally started working, i had no signal at all, radio on, turned off and back on, hard reset, soft reset, nothing. So then I saw that there was WM6 and upgrading sounded like a good idea. Started looking for the rom and i found the voda WM6 rom, followed the instructions and when it was upgrading the battery felt cuz I didn't put back the cover (my bad). After that, I tried to turn on the fone and all I got is the Bootloader screen, have read a lot and all the answers are to format the card to fat32, or to switch computers, I've used like 3 different cards, checked on 3 pc's, used another card reader and all I got is the boot screen, if I put the card in it says loading, press the end call botton, start updating and then got stuck after splash1 and bootloader says ok. What I'm wondering is if the it is a hardware problem was before the update I had no signal, and now it got stuck on the gsm part of the update. Any Ideas?? this is a really expensive paperweight!!!!!
A couple thoughts...first, when it gets to the GSM portion of the flash it takes significantly longer than the others, so you might just need to be a bit more patient. Run it again and leave it alone for 10 minutes.
If you can get to the bootloader screen, your device is not bricked. You didn't mention what carrier your device is from..is it a Vodafone device? If so, you might be able to just connect the device to your PC while it's in bootloader mode and run the full Vodafone updater on your PC. There's a chance that this method might not work if a partial flash has left your device in a state that the PC based updater can't identify.
pirulino23 said:
First, my palm 750 was having the problem that it got stuck like always, and when it finally started working, i had no signal at all, radio on, turned off and back on, hard reset, soft reset, nothing. So then I saw that there was WM6 and upgrading sounded like a good idea. Started looking for the rom and i found the voda WM6 rom, followed the instructions and when it was upgrading the battery felt cuz I didn't put back the cover (my bad). After that, I tried to turn on the fone and all I got is the Bootloader screen, have read a lot and all the answers are to format the card to fat32, or to switch computers, I've used like 3 different cards, checked on 3 pc's, used another card reader and all I got is the boot screen, if I put the card in it says loading, press the end call botton, start updating and then got stuck after splash1 and bootloader says ok. What I'm wondering is if the it is a hardware problem was before the update I had no signal, and now it got stuck on the gsm part of the update. Any Ideas?? this is a really expensive paperweight!!!!!
Click to expand...
Click to collapse
Thanks, and well it is a Cingular Treo, and I left the updater running several times for more than 3, 4 hours until the battery run out, and well, keep being stuck at gsm part, tried the tool that is on the update but after some % it got disconnected, any ideas???
im no expert. but if your using it with cingular (att) and you used a voda rom, i dont know how it would work in the first place without some sort of cid unlock? correct me if im wrong.
anyway. I would try that leaked att rom it it were me.
kapster said:
im no expert. but if your using it with cingular (att) and you used a voda rom, i dont know how it would work in the first place without some sort of cid unlock? correct me if im wrong.
anyway. I would try that leaked att rom it it were me.
Click to expand...
Click to collapse
Well First never do a rom update off the battery second I have a att/Cingular 750 had leaked att on it ran fine then moved to the voda rom still fine
If the ATT rom doesnt work search for a WM5 Rom I think someone said it was posted in here. If that doesnt work, the first rom update I screwed up killed my device I called ATT said I tried to install the audio update and it killed my device they sent a new one and then i up'ed the ATT rom GL.
mtty perhaps?

New Tilt - HardSPL will not install - WHITE SCREEN {SOLVED}

[SIZE=+2]SOLVED[/SIZE]
Thanks to jockyw2001 this is no longer an issue. Please see his sticky thread for the fix and directions...
[size=+1]http://forum.xda-developers.com/showthread.php?t=354061[/size]
Hello all...
First off, let me start by saying that this is not my device, it's a friend's at work... I have done the same process on pretty much all my friends' Tilts (like 10 or 12 of them) and haven't seen this issue until today.
When I try to install HardSPL to the device I get the normal pop-ups on the screen about security and then Pof's "continue" message and when it is supposed to go to the JumpSPL (tri-color) screen all I get is a white screen. This happens on my device too for just a moment before I get the tri-color but his device just sits there...
The plus side is that is doesn't actually do anything to the device, it boots fine with a soft reset.
So far I've tried flashing the AKU 0.4.4 ROM which does install so it doesn't appear to be a software issue (at least not OS level). I have also tried mtty and issuing a 'task 2a' but nothing happens I just get the
cmd>
prompt back after running it, no output to the screen whatsoever.
Anyways...I'm just starting this thread to see if there are any other NEW Tilt owners (or Kaiser in general) that might be experiencing this problem. And if you know of a fix...
Cheers,
From many years of working on people's computers, phones, etc. let me give you a friendly tip:
Don't ever touch someone else's device to make modifications to it.
By doing so you become the sole person responsible - the sole person who will be blamed 6 months down the road when something doesn't work, they have warranty issues, etc.
I've taken on the method of giving people everything they need, helping get them set up, explaining the risk, then making them push the button.
Just a thought..
appreciate the feedback... but I don't mind helping my friends and I let them know the risks prior to any mods.
There are those here that don't want their phones "upgraded" and I don't help them. Those who do and don't want to research, come to me.
Back on topic though... has anyone else seen this behavior?
I saw several threads in the Hermes forum concerning "white screen" but they were after flashing ROMs... this issue is before HardSPL actually gets flashed.
Thanks again!
I wonder if maybe your friend has a newer revision or something that includes a new bootloader.
Can you enter the boorloader manually and see what version it is?
gthing said:
I wonder if maybe your friend has a newer revision or something that includes a new bootloader.
Can you enter the boorloader manually and see what version it is?
Click to expand...
Click to collapse
Yah I was thinking that as well... I did check it and it showed:
KAIS1*0
SPL-1.56.0000
CPLD-8
Before I installed AKU 0.4.4... after which it now reads:
KAIS1*0
SPL-1.93.0000
CPLD-8
... still no love but at least its working, would like to get HardSPL on it though.
Interesting....
You might try hitting up the irc channel - Oli usually hangs out in there and might have some insight.
I had this on my TYTN - and that was due to some hardware failures or wrong .net version. Try to install the newest .net and see..
Martinhdk said:
I had this on my TYTN - and that was due to some hardware failures or wrong .net version. Try to install the newest .net and see..
Click to expand...
Click to collapse
well I wouldn't think it was .net since I managed to flash the AKU0.4.4 ROM (should be a new .net or at least a "reinstall" there). I tried it anyways and installed .NET CF 3.5 ... still no love, same white screen issue when running SSPL-KAIS.exe
I'll see if I can catch Oli on IRC. Can you point me to the server and channel?
sirsycho said:
well I wouldn't think it was .net since I managed to flash the AKU0.4.4 ROM (should be a new .net or at least a "reinstall" there). I tried it anyways and installed .NET CF 3.5 ... still no love, same white screen issue when running SSPL-KAIS.exe
I'll see if I can catch Oli on IRC. Can you point me to the server and channel?
Click to expand...
Click to collapse
irc.freenode.net
#xda-devs
Sirsycho... i answered you in the original thread. I had similar issue however i needed to remove the SIM card and the SD card. Then the white screen disappeared and the tri color one appeared. try removing the SIM and SD cards b4 installing. Also remember the issue with the AntiVirus...
asfoor said:
Sirsycho... i answered you in the original thread. I had similar issue however i needed to remove the SIM card and the SD card. Then the white screen disappeared and the tri color one appeared. try removing the SIM and SD cards b4 installing. Also remember the issue with the AntiVirus...
Click to expand...
Click to collapse
Good idea asfoor... I did actually remove the SD card but for some reason didn't think to remove the SIM. I'm home now and will have another opportunity to try again with his phone tomorrow. I'll post my results then.
Thanks again for the tip... makes me feel silly that I didn't think of it though
alright... I took out both SIM and SD this time, but still just the white screen. I really wish I could get the task 2a to work, I think it's probably a bad block issue that JumpSPL is attempting to access.
I'm having the exact same issue. I've read and searched, only finding your thread. Just hangs forever on the white screen, never getting to tricolor.
Anyone else having this issue?
ROM Version: 1.57.502.2
ROM Date: 08/25/07
Radio Version: 1.27.12.11
Protocol Version: 22.45.88.07H
plirky said:
I'm having the exact same issue. I've read and searched, only finding your thread. Just hangs forever on the white screen, never getting to tricolor.
Anyone else having this issue?
ROM Version: 1.57.502.2
ROM Date: 08/25/07
Radio Version: 1.27.12.11
Protocol Version: 22.45.88.07H
Click to expand...
Click to collapse
when did you get your device?
Out of sheer curiosity, check the manufacture date:
remove back cover... date should be just above the battery in the following format: MMDDYY
For example, mine which does work and which I have HardSPL on reports: 061107
I will get the date from the "broken" one tomorrow.
I just got it two days ago.
The manufacture date on mine is 080907.
weird...
Anyone else have any ideas?
"When I try to install HardSPL to the device I get the normal pop-ups on the screen about security and then Pof's "continue" message and when it is supposed to go to the JumpSPL (tri-color) screen all I get is a white screen."
Mine is 080907 and I remembered clearly that when I first tried the hardspl it frozed, so I just take the battery out and redid it again and it worked.. I also noticed I didn't follow the instruction as it was told earlier the first time: unplug the cable and replug it back in etc etc.
But right now I'm using Dutty's Tilt Rom Beta 2 and loving every minute of it. (I did disable the cube but kept everything else the same) so I can use transcriber.
So far, since a week ago, I am LOVING every minute of it.
Yeah...
I've got one of these bad boys, just came Friday with date of 181007 (which suggests it is DDMMYY, not MMDDYY) Code after date is (RC01). My previous Tilt (returned for continuous vibration glitch) had (RB01) code. I've tried all the suggestions here... no luck. Damn White screen forever....
NOT fun.
plirky said:
I just got it two days ago.
The manufacture date on mine is 080907.
weird...
Click to expand...
Click to collapse
What is inside the parenthesis just after the date of manufacture? (RB01), (RC01), other?
I'm having the same issue here. Just got the phone a week ago. MFG date: 181007. Any ideas would but very much appreciated.
dantegl36 said:
I'm having the same issue here. Just got the phone a week ago. MFG date: 181007. Any ideas would but very much appreciated.
Click to expand...
Click to collapse
Yep Same issue here, Got mine a few days ago: 181007 (RC01)
This sucks....

Flashing an Orange Kaiser - Success!

Hi all,
I've been reading your threads about flashing the ROM with the 6.1 version from HTC and read that everyone seems to be having issues with flashing the Orange Branded Kaiser.
I've managed to successfully flash mine with the HTC 6.1 update and get rid of all the orange stuff. I used Olipro's SIM/CID unlocker to unlock the device and success, it works!
I made sure that I had a copy of the radio ROM and the original Orange ROM, which are all available on here just incase. The first few times the phone just booted and locked up on the splash screen, so used camera, power and soft reset to boot into bootloader and reinstalled the orange ROM, all worked fine.
Probably teaching you all to suck eggs as you've all probably achieved it, but just wanted to let you know there is hope, I am a noobie yet managed it. Just wanted to say a big thanks to all of you at XDA, especially Olipro! So, cheers! Happy cooking
gratz mate, did mine last week after reading for a couple of weeks, using dutty's wm6.1 but having problems with forwarding text messages, keeps spamming everyone the same message lol......any chance you can upload the original orange rom and radio somewhere I never made a backup
I've been using an Orange TyTn and from day 1 I have been using cooked ROMs with not a single problem EVER... The only problem I came across was the Radio issues... And that was my mistake because I didn't put a 6.1 radio on my phone... All the people that do have problems are those who cannot or choose not to READ!!! Its by no means the simplest job to flash any ROM for the first time with a TyTn... But start reading the right things and taking it ALL in and you can't go wrong... Even if you do go wrong someone has done it too and posted a fix or a guide which explains everything you need to know to get back on track...
technocat said:
gratz mate, did mine last week after reading for a couple of weeks, using dutty's wm6.1 but having problems with forwarding text messages, keeps spamming everyone the same message lol......any chance you can upload the original orange rom and radio somewhere I never made a backup
Click to expand...
Click to collapse
I flashed my kaiser (was on Orange UK) but downloaded the Orange ROM as backup from here- it's in the sticky which points to the wiki
All5tars said:
I've been using an Orange TyTn and from day 1 I have been using cooked ROMs with not a single problem EVER... The only problem I came across was the Radio issues... And that was my mistake because I didn't put a 6.1 radio on my phone... All the people that do have problems are those who cannot or choose not to READ!!! Its by no means the simplest job to flash any ROM for the first time with a TyTn... But start reading the right things and taking it ALL in and you can't go wrong... Even if you do go wrong someone has done it too and posted a fix or a guide which explains everything you need to know to get back on track...
Click to expand...
Click to collapse
Hear, hear - the issues for Orange users are well known and very well documented here. The main issue of SIM lock has gone away thanks to the efforts of Jocky and co. making flashing our Orange devices a much more straightforward affair.
Some time ago I made a backup of the original Orange ROM which can be found in this thread;
http://forum.xda-developers.com/showpost.php?p=1586817&postcount=2
Note that this is the ROM and splash screen only - the Radio that Orange ships has never been released in a ROM package, there are other radios available with close(ish) version numbers - see the Radio ROM thread for more information.
we must be carefull with our rulings
mbucko said:
Hi all,
I've been reading your threads about flashing the ROM with the 6.1 version from HTC and read that everyone seems to be having issues with flashing the Orange Branded Kaiser.
Click to expand...
Click to collapse
I should certainly congratulate you for your successfully flashing a rom on your kaiser. This is the big news of the century ! Two big thums up
But I just don't understand how on earth you got to such all-embracing conclusion that "everyone seems to be having issues with flashing the Orange Branded Kaiser".
This is one of the strangest claims (made in someone's FIRST post) ever posted on kaiser rom dev thread.
As on Orange UK user who has flashed numerous roms on his orange branded TyTN_II (aka kaiser) with unspeakably "less" issues/problems than US/Australian/Malaysian/Germanan/Mars(!!) kaiser users , I have absolutely no idea what you're talking about mate !
Does that "everyone" include you and perhaps a friend of yours ? !!
no offence my friend, but don't you think it would be better to spend some time on the forum before shooting such generalization in the first post??
cheers
Yeah, fair enough that was a generalisation - my appologies! I'll put it down to my excitement of thinking i was a hero for fixing it after it was in bootloader for days! I just read that there seemed to be a lot of issues if you tried flashing it as there is a possibility that the phone will lock you out completely - I have heard of people entering their IMEI number in but not quite sure about it - and this seemed to be a general theme across forums...i probably just read old posts!
Anyway, it was just a thanks than any kind of technical advice! like i said in my post, i got all of the ROMS tools etc from XDA so cheers. There is also a radio rom, the original orange one is 1.65.16.65 which is on here too. I've read that this is the radio shipped with the HTC WM6.1 ROM and orange just used it in their build anyway?
The first time i tried flashing it I didn't want to risk trying Olipro's unlocker, no offence, as it said it changed the Radio which i read was the cause of the issues..but after being stuck in the splash screen for days that annoyingly said "smart mobility"..not so smart when it's a fancy paperweight.. i found out how to get into bootloader and i flashed the Original Orange rom back, and used the unlocker. All worked fine! The only issue was that i use a VPN for work and it wouldn't load the server web pages properly. Managed to fix this after somebody told me about using Schap's AdvancedConfig and changing the UserAgent. again, thanks!
So keep up the good work, you provide hope for plebs like me.
All5tars said:
I've been using an Orange TyTn and from day 1 I have been using cooked ROMs with not a single problem EVER... The only problem I came across was the Radio issues... And that was my mistake because I didn't put a 6.1 radio on my phone... All the people that do have problems are those who cannot or choose not to READ!!! Its by no means the simplest job to flash any ROM for the first time with a TyTn... But start reading the right things and taking it ALL in and you can't go wrong... Even if you do go wrong someone has done it too and posted a fix or a guide which explains everything you need to know to get back on track...
Click to expand...
Click to collapse
I have searched and searched no answers, am using the radio that was with duttys, no other problems apart from forwarding text messages, seems to spam, try it yourself??.....

Stuck on hardSPL bootloader screen

Hello all, my name is Jon and I am pretty new to this ROM business and didn't really come looking for this type of hobby but it found me. I bought a fuze from some guy who said he put 6.5 on it blah blah blah it worked good when I checked it out but after using it for a week it has been nothing but a mess.
Anyway I was reading the re-flash thread and decided to check the phone for hardSPL. 2 things i did wrong here
-my sim was in
-i didnt hold volume+enter, i held reset, then volume, then tapped reset.
It booted into the red green blue white screen, shows 1.90 which is good any everything but it is STUCK here. Regardless of what I do with the reset button it doesn't repsond. Press, hold, hold for a while, caress gently, etc.
Is it ok to take my battery out?
Also any recommendations for a RELIABLE ROM? Something lite sounds good too. I was thinking about
[ROM][CUSTOM]08.14.09 Bloat Free Official HTC Fuze ROM Update- Version 5.11.502.2 WWE
Thanks everyone
ok i pulled the battery and it's fine. let the proper rom flashing commence!
Moved to the Raphael subforum
soo.... is it still fubar and you need help? or are you good to go????

Categories

Resources