Related
How to update your rom to the latest I-mate version (with push email) and Radio 1.09.0 using the MaUpgradeUt_noID.exe method
1 – download the file “Universal_Upgrade_v1.30.68_radio_1.09.0.zip” from the ftp site (see bottom of post for details)
2 - double click the file and allow it to unpack into a folder
3 – right click on the active sync icon in your tasks tray on you pc (at the stage you should NOT have you universal plugged in)
4 – select connection setting then untick “allow USB connections”
5 – Now take your Universal and take out the SIM and MEMORY CARD
6 – Press light + power + reset with the phone on, this will place the universal into bootloader mode
7 – Connect your Universal via the USB cable to your computer directly i.e. not though a USB hub
8 – Now double click on the program called “MaUpgradeUt_noID.exe” (found in to folder from step 1) this will start the upgrade process, the first stage takes about 3 to 5 minutes to complete, you will then be presented with a screen showing a “Imate Jam” and some information about what you are upgrading to, don’t be worried if this screen does not show you the version numbers you have at present that is normal.
9 – Now continue with the process by clicking upgrade/next
10 – After sometime (about 20 minutes) you should be at the end screen tell you to unplug and reset you “jam” So now unplug your universal and reset it and that’s all there is to it!
Note that during the upgrade process you can follow the progress by also looking at your universal screen with a light source as the backlight will be off.
I hope this post helps someone as looking around the forum Im amazed by the amount of people asking “how do I upgrade my rom” or “I only get a “country id error” when trying to update”
The “Universal_Upgrade_v1.30.68_radio_1.09.0.zip” file can be found here
ftp://xda:[email protected]/Uploads/Universal/Universal_Upgrade_v1.30.68_radio_1.09.0.zip
This file contains the latest imate beta rom v1.30.68 and the latest radio 1.09.0 plus all the tools you need
Oh and if anyone thinks Ive missed something out please post and let me know!
File as been moved its now at :-
ftp://xda:[email protected]/Universal_Upgrade_v1.30.68_radio_1.09.0.zip
This file contains everything need to upgrade your universal
Thanks rat - very cool of you to post up a guide. How Nb is it to remove your SIM?
wamatt said:
Thanks rat - very cool of you to post up a guide. How Nb is it to remove your SIM?
Click to expand...
Click to collapse
No sure I understand the question however Ive updated before now with the sim card in however lots of people report that its important to remove both the memory & sim cards so Ive included it because its better to be safe than sorry
Thanks I'll play it sorry :/..
BTW do you have to use this NOID method if you have an IMATE too?
wamatt said:
BTW do you have to use this NOID method if you have an IMATE too?
Click to expand...
Click to collapse
No you should be ok using the orginal package, however this way will still work
I installed the ROM but after the installation is finished and I reset the device I only get a blank screen.
Piesang said:
I installed the ROM but after the installation is finished and I reset the device I only get a blank screen.
Click to expand...
Click to collapse
Blank screen but do you have the USB or SERIAL written on the Screen?
Rat didn't mention in his post but it comes out in the last screen that it is supposed to be a HARD RESET which will bring about a menu where you have to press 0 (Zero) to ahrd reset the device. hope this helps
Yip, sorry, That's correct. I get the screen that says I have to press 0 to reset or X to exit.
If I press 0 the screen goes blank and stays like that.
I've installed the previous ROM now and it is working perfectly. It's just the new ROM on this page doesn't want to work on my Jasjar.
Piesang said:
Yip, sorry, That's correct. I get the screen that says I have to press 0 to reset or X to exit.
If I press 0 the screen goes blank and stays like that.
I've installed the previous ROM now and it is working perfectly. It's just the new ROM on this page doesn't want to work on my Jasjar.
Click to expand...
Click to collapse
I downloaded it straight from the first post and it installed flawlessly...
Have you tried installing it from bootloader mode instead of direct update? And without SD card in the PDA? This might work.
BTW, I have returned to the older ROM.... advantages don't outweigh the disadvantages.
My phone keeps on hanging (for the 1st time ever after 5 months use and different ROMs) on the screen where it shows whose calling. I havent answered the call yet but it stops ringing. When i open the PDA it has ANSWER on the left softkey and pressing this doesn't do anything. Will wait for the release..
It is a lot faster thought (the test ROM)
Thanks for the info. I'm not gonna bother upgrading now. I'll wait for a decent ROM later.
Thanks m8
umm - stupid question I know.....
But what does this actually DO??
I understand that this will upgrade the radio stack and thus produce better reception etc - but what else will it do??
If I have an Orange M5000 will I still be able to use it on Orange's network?? Do i need to fill in any settings? Do I need to make notes of certain stuff beforehand? If so - what settings?
I assume this will totally rewrite the registry and what programs are on teh device - or will it??
I suppose a lot of this information is available on the forum - but tracking it down can take a lot of time for someone who's not necessarily that 'au fait' with the working of the device.
Riceburner said:
umm - stupid question I know.....
But what does this actually DO??
I understand that this will upgrade the radio stack and thus produce better reception etc - but what else will it do??
If I have an Orange M5000 will I still be able to use it on Orange's network?? Do i need to fill in any settings? Do I need to make notes of certain stuff beforehand? If so - what settings?
I assume this will totally rewrite the registry and what programs are on teh device - or will it??
I suppose a lot of this information is available on the forum - but tracking it down can take a lot of time for someone who's not necessarily that 'au fait' with the working of the device.
Click to expand...
Click to collapse
I also have an orange M5000 which I would like to get off Orange to use my Vodafone SIM - would installing this new ROM be the way to go ?
not if your phone is simlocked (or network locked). new rom is only the software.
Yeah, sorry
Just reading the other thread on this - sorry , am a relative newby.
It looks like MachineGod and Buzz are on the case though - and with their track record........
I wanted to confirm that Ratcom's file he linked to is good (not corrupt) and his method for upgrade works. Nice work, Ratcom.
ratcom said:
File as been moved its now at :-
ftp://xda:[email protected]/Universal_Upgrade_v1.30.68_radio_1.09.0.zip
This file contains everything need to upgrade your universal
Click to expand...
Click to collapse
Hi ,
Can let me know the speed of the Os did u face any problems after upgrade.
E.g Apps, Hanging , Memmory leaks. Etc. Cheers
I had no problems what so ever with this rom, the speed of the os was breathtaking.
ratcom said:
I had no problems what so ever with this rom, the speed of the os was breathtaking.
Click to expand...
Click to collapse
Does this rom work on dopod 900?
Is this is final release?
Cheers,
Well, school is out for the summer, so I can focus on putting out roms again. With this release, I made another WM6.5 rom to test a new compression type that I'm working with. With the original stock compression type (XPR), I didn't have enough space to fit all the goodness of WM6.5, so I switched to a new compression type (LZX) that lets me pack in more. I'm curious to know how the new compression type performs in comparison to the old one. Does anyone notice things are faster or slower?
Thanks to Makuu (for helping to get me started), Lenny, AstainHellbring (thank you for all the nightly help sessions), the creators of the tools I used to make this rom, and anyone else that I failed to mention in name who gave me the knowledge to complete this rom.
Asus Mypal A6x6 WM6.5 version 2
Windows CE version 5.2.21892 (Build 21892.5.0.89)
This was tested on an Asus Mypal A626 (and works). It should work with the A686/A696, but the other models were not tested. Any other models not metioned above WILL NOT WORK.
Updates
1. new compression type
2. os build
3. bug fixes
Additions
1. Windows Marketplace
2. File Dialogue Changer
3. MS Office Mobile
4. Remote Desktop Mobile (has been added again)
Removals (you can reinstall these via windows marketplace)
1. Windows Live
Removals (non-Windows Marketplace)
1. PsShutXP
download: http://www.easy-share.com/1910266747/Asus_A6x6_WM65_2.rar
At this time, this will be the only download link. Mirrors will be created in the future (after I give permission).
Instructions (I have included a txt file with same instructions for offline convenience)
Before you do anything, make sure you have at least a 256mb SD card and a card reader (you can get one at a place like Radio Shack or Office Depot). You also need to install winrar (found at http://www.win-rar.com/download.html). Your SD card must be formatted with the FAT16 file system.
To format your SD Card with the FAT16 file system
Step 1: To do this insert the SD Card into the reader and go to "My Computer".
Step 1a: BACKUP YOUR FILES before you start!!
Step 2: Right-click the drive letter of the SD Card reader (differs for each computer, probably either E:\ or F:\ or G:\) and click "Format".
Step 2a: Don't worry about any of the options except for file system, choose "FAT"
Step 3: Click "Start" and wait until it is done
Step 1: Get (OS) rom image
Step 2: Extract files to any folder on hard drive using Winrar
Step 3: Go to the folder where you extracted the files in the RAR archive
Step 4: Make sure that the filename is "CANNES_A_WM6.img"
Step 4a: if the img file it's not exactly "CANNES_A_WM6.img", rename it to that
Step 5: Format the SD card if you haven't already done so using the instructions above
Step 6: Copy the img file to the SD card, see step 6a
Step 6a: Make sure that the img file is the ONLY file on the SD card after formatting
Step 7: Take SD Card out of SD Card reader and put it in the a6x6
Step 8: Make sure that the a6x6 is plugged in via ac adapter before doing the next few steps
Step 9: activate SD Loader using the following instructions {
Step 9a: Hold down the power button and enter button (that's the button in the center of the d-pad)
Step 9b: Double tap the soft reset button while holding the other 2 buttons
Step 9c: After double tapping the soft reset button, keep the other 2 buttons held until a blue screen comes up that says something like Asus Cannes flashing utility
Step 9d: Wait until the process is finished (it's near the end when it says "writing private")
}
Step 10: At this point, your a6x6 should reboot on its own
Step 11: enjoy your updated rom
If you have any questions, feel free to just post or PM me.
As I release new roms, if you have a support question, please give me the rom version so I know what rom you are working with. You can get the rom version from the filename of the rom pack.
Example: Asus_A626_WM614_1
A626 = device (most often it will be A626, will rarely be different), WM614 = os version, 1 = release #
I only added MS Office Mobile this time because the new MS Office Mobile 2010 had not been released yet. For my next release, I am not including MS Office Mobile due to the fact that you can download the new version free from Marketplace.
My work is free for everyone's use, but if you feel compelled to give a donation towards my work (I am a full-time college student working on this in what little spare time I have), my paypal e-mail is "[email protected]"
Steven855 said:
I only added MS Office Mobile this time because the new MS Office Mobile 2010 had not been released yet. For my next release, I am not including MS Office Mobile due to the fact that you can download the new version free from Marketplace.
Click to expand...
Click to collapse
Some indication about free memory after 6.5 rom installation?
If something wrong, is possible to reinstall the official 6.1 rom?
Thanks
Massimo
maxambro said:
Some indication about free memory after 6.5 rom installation?
If something wrong, is possible to reinstall the official 6.1 rom?
Thanks
Massimo
Click to expand...
Click to collapse
Nothing is wrong with the rom. I would just like to find out if people notice a performance impact (good or bad) with the new compression type (that is supposed to give you more storage space) that I'm trying out with this rom. Iif there was something very wrong with this rom, I would never release it to the public (ok, perhaps I jumped the gun with the 1st WM6.5 rom, but I did put out warnings and a bug-fix rom to remedy some issues with the 1st rom). And yes, it's possible to downgrade to WM6.1 (just a note, Asus never put out an official WM6.1 stock rom, so I had to make it). The latest stock rom is WM6.
Appropriate to glorify
Steven855 said:
Nothing is wrong with the rom. I would just like to find out if people notice a performance impact (good or bad) with the new compression type (that is supposed to give you more storage space) that I'm trying out with this rom. Iif there was something very wrong with this rom, I would never release it to the public (ok, perhaps I jumped the gun with the 1st WM6.5 rom, but I did put out warnings and a bug-fix rom to remedy some issues with the 1st rom). And yes, it's possible to downgrade to WM6.1 (just a note, Asus never put out an official WM6.1 stock rom, so I had to make it). The latest stock rom is WM6.
Click to expand...
Click to collapse
Thank you so much for extraordinary job on rom ver. 2 !!!
I was intalled this on my ASUS 696 and it went smoothly without any problems.
In addition, it looks more faster as you mentioned beside rom ver. 1.
The current rom taking the sum of 29.53MB from a total of 53.35MB memory (what let us 23.82MB free at the program memory section).
Again you made a really holiness work due to the fact our mypals still relevant...
Steven855 said:
Nothing is wrong with the rom. I would just like to find out if people notice a performance impact (good or bad) with the new compression type (that is supposed to give you more storage space) that I'm trying out with this rom. Iif there was something very wrong with this rom, I would never release it to the public (ok, perhaps I jumped the gun with the 1st WM6.5 rom, but I did put out warnings and a bug-fix rom to remedy some issues with the 1st rom). And yes, it's possible to downgrade to WM6.1 (just a note, Asus never put out an official WM6.1 stock rom, so I had to make it). The latest stock rom is WM6.
Click to expand...
Click to collapse
Installed this ROM today, and performance on my A696 is not so good...
First – after reboot it was stuck on Windows startup screen for 4-5 minutes. I thought the flashing process went wrong, but eventually it booted up.
I haven't tested it thoroughly yet, but the first things I noticed – reaction to any user event (tapping, scrolling, etc.) is MUCH slower than on the WM6.1 I'd had before. Haven't tested the application performance yet.
Also, when I tap on the battery indicator nothing happens.
v.real said:
Installed this ROM today, and performance on my A696 is not so good...
First – after reboot it was stuck on Windows startup screen for 4-5 minutes. I thought the flashing process went wrong, but eventually it booted up.
I haven't tested it thoroughly yet, but the first things I noticed – reaction to any user event (tapping, scrolling, etc.) is MUCH slower than on the WM6.1 I'd had before. Haven't tested the application performance yet.
Also, when I tap on the battery indicator nothing happens.
Click to expand...
Click to collapse
Yeah, I forgot to mention that 1st boot time has increased with this rom. This is due to the new compression type. For the power icon, I just noticed your concern. Unfortunately, I don't have a fix for it right now. You can still view battery information by going into the settings.
If anyone knows how to flash a rom in a different language, please enlighten me. I have made an attempt at making an international rom (this time was German), but I can't get it to boot (I have an English version A626). I think the reason it won't boot is because I didn't configure the firmware right (the os is right though).
ROM working very good so far on my Asus A696. Looking forward to a German version but I could live with the US ROM. Thanks for your hard work.
You could also see battery level by using the ASUS Manager Icon on the Today Screen.
Good job
I would donate, for a Portuguese language rom. Thanks!
Problem with rom 2
Hi Steven,
I noticed in a one small problem of rom 2 after flashed on my asus 696.
The problem is that whenever i push the power button shortly and alternatively i'm trying to push it again to power on, it failes to succeed what leaves me to make an another resets for several times.
Can you resolve this issue during upcoming next rom?
Thanks for your good job!
Was a little slow and less responsive on the first startup, but after a soft reset it worked GREAT!
Once again beautiful work Steven, thank you very much!!!!!
dj.brudo said:
Hi Steven,
I noticed in a one small problem of rom 2 after flashed on my asus 696.
The problem is that whenever i push the power button shortly and alternatively i'm trying to push it again to power on, it failes to succeed what leaves me to make an another resets for several times.
Can you resolve this issue during upcoming next rom?
Thanks for your good job!
Click to expand...
Click to collapse
Same problem.
And a second issue: my A696 freezes if I work with the BT module (handsfree, file transfer)
Thanks for the ROM.
When I was making the rom, I was looking for a way to delete the MS Bluetooth stack to free up some space (which is perfectly fine). I'm not sure, but I think the problem could be caused by me deleting some dll file packages related to bluetooth that are shared between the MS Bluetooth stack and the stock Broadcom stack (which is better).
Finally got around to flashing the new ROM. It appears to be working fine. I mostly use the A626 as a music player so I've had no issues so far. There is one thing that I'm not sure if its just my A626 or if anybody else has the problem but when I plug in the external AC adapter it doesn't seem to recognize the external power source... it will charge the battery it doesn't use the screen brightness and timeout settings, it will stay using the settings as if it is running on battery. Anybody else notice this?
*******
Actually after playing around for a couple hours I have an issue where once the device blanks the screen out I cant wake it up by pushing on the screen or the power button. If I connect power and disconnect it and reconnect it I still can't wake it. I have to reset the device to get it back to functional. I've tried reflashing and still have the same issue.
*******
I switched to a different mini usb charger and now it is recgonizing that the external power is hooked up... must have a weird usb charger. I've also gone back to using 6.5 1a to see if I have the same stand by/blank screen issues.
Bluetooth handsfree
I found some registry entries in a french site, with these settings we can enable the bluetooth handsfree service. I attach this file, maybe Steven will integrate in the next ROM (this service can be disabled in the bluetooth settings like any other service if you don't use). The application (which is from asus \windows\bthandsfreedevice.exe) has a little bug: can't do the synchronization of the phonebook and calllog from the phone (I tried with nokia 6233). If anybody know about a newer version of bthandsfreedevice.exe or know another (better) bthandsfree application, maybe we can make a working handsfree device from A696.
brgds,
imre00
bmasephol said:
Finally got around to flashing the new ROM. It appears to be working fine. I mostly use the A626 as a music player so I've had no issues so far. There is one thing that I'm not sure if its just my A626 or if anybody else has the problem but when I plug in the external AC adapter it doesn't seem to recognize the external power source... it will charge the battery it doesn't use the screen brightness and timeout settings, it will stay using the settings as if it is running on battery. Anybody else notice this?
*******
Actually after playing around for a couple hours I have an issue where once the device blanks the screen out I cant wake it up by pushing on the screen or the power button. If I connect power and disconnect it and reconnect it I still can't wake it. I have to reset the device to get it back to functional. I've tried reflashing and still have the same issue.
*******
I switched to a different mini usb charger and now it is recgonizing that the external power is hooked up... must have a weird usb charger. I've also gone back to using 6.5 1a to see if I have the same stand by/blank screen issues.
Click to expand...
Click to collapse
I noticed these today as well, and re-flashed but wasn't able to resolve the problem. Will continue testing the ROM.
While I don't need the Microsoft entries (since they pertain to the MS bluetooth stack), but I will definitely take a look at the widcomm entries. I won't be able to work on rom building until the weekend, but I will take some time to test it (to tell you all the truth, I didn't really test bluetooth as much as I should have with this release).
bmasephol said:
*******
Actually after playing around for a couple hours I have an issue where once the device blanks the screen out I cant wake it up by pushing on the screen or the power button. If I connect power and disconnect it and reconnect it I still can't wake it. I have to reset the device to get it back to functional. I've tried reflashing and still have the same issue.
*******
Click to expand...
Click to collapse
It seems that the device can't wake up only when goes in standby after applying the screen lock. Without locking, it can be powered on with the power button.
Downgrading to rom version 1
Hi steven,
After several times i tried to discover what's appear to make the battery totally empty (due the fact i couldn't start my 696 on every time i shut it down or just pushed shortly the "power on" button just to make it sleeping mode) i figured that something in the rom version 2 caused the problem.
I alreasy noticed (my last reply) that even the battery still ok, during trying to make the 696 go to sleeping mode it's refuse after that to power on and forced me to make couple of resets (because even after some resets the 696 still stuck without any responding).
Finally i downgraded the 696 to rom version 1.
Hi there,
For those who take the time to read through this,
I'm a HTC TYTNII (Kaiser) user, and I have just installed Android on my phone's SD card (2gb, unpartitioned) and I boot it using HARET.exe
It works and I can do the usual and send sms'es and calendar stuff and web and market. And, as expected, it is somewhat slow in some areas.
The problem is, my mic doesn't work during calls. The camera doesn't work, the pictures are green data lines (what?what?) The mp3 player or media player doesn't work. The only time sound does work is during a call, but even then only on my side (receiver doesn't hear anything). And I am just about figuring out how the keys around/on the D-Pad work. (greenphone is Phone, redphone is power, left/right is volume, ok is back, windowskey is something like a options key, internet explorer is also a options key, etc.)
- -
So, Can aybody help me with this:
Mic problems (not working. calls or recording)
D-Pad Keys problems (don't know what they are)
Camera Problems (not taking pictures, just green data)
No file explorer to install apps. (how to upload apps on sdcard or from market)
Market browsing works, but cant download. (just says 'starting download' forever)
Can't brows SDCard (or any files for that matter)
Music can't play. (media player with slide album cover stuff, no play)
Can somebody please post up a definite link or site, where I can get working stable Kaiser Android (TYTNII) install files. (nothing fancy like themed or modified with grafiti or windows mobile features, simple Android 2.2)
*Tail
PS, not sure about the Radio, or whatever. I have "Radio Version: 1.27.15.32"
Does it need updating or new files? What does it effect?
ehhh.... read the forum.... READ
here You have 'how to'.. http://forum.xda-developers.com/showthread.php?t=680518
here NBH file (as You know, without this You can't install Android rom...) http://forum.xda-developers.com/showthread.php?t=660158
here is stable Android 2.1 I recommend http://forum.xda-developers.com/showthread.php?t=688880
Radio must be 1.70.18.02 or 1.70.19.09 ...
polymod_2.1 is Enclair Android, not Tattoo.
Thanks!
Yeah, about reading... I get very frustrated when I go through 50 pages of forum, and end up having 6 pages, all about the same thing, but with different file versions. Then I'm unsure of what to do.
Thanks again, I'll try these
You can also check out my thread in this forum (can't link it due to new user restrictions) which at the time of this posting is 5th from the stickies in the index.
I had various issues with my eclair (incubus's) and it was solved by upgrading using the official WM6.1 release, which upgraded my radio. Upping to the most recent radio (1.7x...) didn't help.
Also a point of order: all eclair builds have non-functional cameras and most have bluetooth issues (some can be fixed with patches). If you need a working camera and BT, you might want to try Myn's Warm Donut which is older but is also stable... And slow.
Incubus's Super Eclair is the fastest I have tried so far though it is buggy on my kaiser.
HTC_TYTNII_KAISER said:
Hi there,
Mic problems (not working. calls or recording)
D-Pad Keys problems (don't know what they are)
Camera Problems (not taking pictures, just green data)
No file explorer to install apps. (how to upload apps on sdcard or from market)
Market browsing works, but cant download. (just says 'starting download' forever)
Can't brows SDCard (or any files for that matter)
Music can't play. (media player with slide album cover stuff, no play)
Can somebody please post up a definite link or site, where I can get working stable Kaiser Android (TYTNII) install files. (nothing fancy like themed or modified with grafiti or windows mobile features, simple Android 2.2)
Click to expand...
Click to collapse
- Mine didn't either. Might have been fixed with the radio upgrade though I haven't checked it.
- Mine work fine... Can you explain a little more?
- Universal to eclair builds, fall back to donut if this is a deal-breaker.
- You need to get yourself one since android doesn't come with a free, standard. Search for "andexplorer" on your phone's browser and install it directly from the web, then you can grab all the packages you want and manually install them.
- Does your other wifi work?
- Andexplorer.
- Likely need a radio upgrade
Redundant, but hopefully it helps more than "go do some searching" or "go read through this 300 page thread".
Mr fosi refers to this thread : http://forum.xda-developers.com/showthread.php?t=690693&page=2
You will have to upgrade your radio, from experience on the forum I can tell you that anything lower than version 1.65.x.x will almost certainly cause a number of problems.
You will also have issues if running winmo 6.0, if you are using haret, you should go get at least a stock ROM that is winmo 6.1 and radio 1.65.x.x, yes you will lose all your data if you flash a new rom, so back up anything you really cannot live without.
And at the moment the highest version of Android available for kaiser is 2.1, 2.2 will take a little time to get to us here
again,
Thank you all,
You have been most helpful.
Up till now, I have been trying to find ways to refrain from overwriting WinMobile. (not that I prefer it, it's just I have a butload of stuff on it, and I dnt want to lose them)
@ mazz8y
Thanks for the innitial help
@ mr_fosi
Very helpfull, thanks!
@ zenity
Thank you too. But do you think it's better to overwrite? Or SDcard method?
PS, What can be used to backup everything of my current phone system? (WinMobile, calendar, contacts, messages, etc.)
I have diffuculty connecting my TYTNII to my pc via usb cable. Software related?
HTC_TYTNII_KAISER said:
Thank you all,
Up till now, I have been trying to find ways to refrain from overwriting WinMobile. (not that I prefer it, it's just I have a butload of stuff on it, and I dnt want to lose them)
Click to expand...
Click to collapse
Same as me. Plus, I do stuff for free on windows that I can't currently do for free under android... Like read my .txt and .doc books, play .wmv files, open and edit .xls files.... Etc.
HTC_TYTNII_KAISER said:
Thank you all,@ mr_fosi
Very helpfull, thanks!
Click to expand...
Click to collapse
No probs. Best way yo pay back is to pay forward.
HTC_TYTNII_KAISER said:
Thank you all,
@ zenity
Thank you too. But do you think it's better to overwrite? Or SDcard method?
Click to expand...
Click to collapse
I know this wasn't addressed to me but I'll weigh in: SD is great for versatility or "trying things out" but it isn't so good for speed or battery life. Replacing windows isn't a huge deal since you can put it right back but once you flash it off, you're somewhat committed to the android model.
Personally, I don't see going straight android right now b/c it would cost me an arm and a leg to buy apps to do what I already do on windows for free. Even then I wouldn't cover everything, just the most critical issues.
HTC_TYTNII_KAISER said:
Thank you all,
PS, What can be used to backup everything of my current phone system? (WinMobile, calendar, contacts, messages, etc.)
I have diffuculty connecting my TYTNII to my pc via usb cable. Software related?
Click to expand...
Click to collapse
Dunno about soft/hardware but the best thing to use might be PIM backup, which you can find with a quick search. I'd link it, but I can't. I don't actually use my kaiser as a phone but rather as a PDA/mobile PC so I can't help you with phone-related data. I generally use the Windows Mobile Device Center to keep all my contact, calender, notes, etc. data synced then keep everything else (like backups of installed software) on my SD. You can sync without a cable if you do it via BT. I bought a $0.25 (free shipping!) Hong Kong BT adapter for my lappy and it works great.
HTC_TYTNII_KAISER said:
@ zenity
Thank you too. But do you think it's better to overwrite? Or SDcard method?
Click to expand...
Click to collapse
If you refer to running Android, I'd recommend SD card method at first, that way you learn to install and use android with the safety net of Winmo available if things go wrong.
Haret is slower, but safer.
HTC_TYTNII_KAISER said:
PS, What can be used to backup everything of my current phone system? (WinMobile, calendar, contacts, messages, etc.)
I have diffuculty connecting my TYTNII to my pc via usb cable. Software related?
Click to expand...
Click to collapse
I have used SPB Backup a number of times for this, it will back up pretty much everything, and can backup to SD card.
zenity said:
Haret is slower, but safer.
Click to expand...
Click to collapse
It depends on what build you use (I never saw a difference, difficult to measure).
Hey, I'm gonna do this now:
"Ok that's one old radio, go here : cant link, get the 1.71.09.01 linked at the bottom of post #3, it's an nbh file, so just rename it to KAISimg.nbh, put it on SD and flash the same as the Nand nbh, it will not affect anything, just upgrades the radio."
But,
Are you refering to
can;t link page
post num #1
"Quote:Originally Posted by kletiz
I can't seem to get past step 5. I'm holding down Power and Camera at the same time and then briefly pressing the reset button. All it does it goes to the bootloader screen and then resets. Any suggestions? Its probably something simple...
Make sure your SD card is formatted FAT32, and that the NBH file is named KAISimg.nbh, and that it is on SD root, not in a folder."
When used for just updating/adding a new Radio (1.71.09.01),
Is it neccisarry to do the whole "NBH Editor" thing? Or can I just throw it in the SD root and then power+cam stylus tap reset flash thing.
So should I go from step 1 to 5 or what?
Sorry if I'm being a real bother, but I can't risk bricking my phone. I have no backup phone to use, or way of keeping contacts and calendar things.
EDIT: I have now! saw the references in your posts!
HTC_TYTNII_KAISER said:
Hey, I'm gonna do this now:
"Ok that's one old radio, go here : cant link, get the 1.71.09.01 linked at the bottom of post #3, it's an nbh file, so just rename it to KAISimg.nbh, put it on SD and flash the same as the Nand nbh, it will not affect anything, just upgrades the radio."
Click to expand...
Click to collapse
Respectfully, I wouldn't do that. Read further down the thread and you will see that a less-new radio may work better, unless you are already using WM6.1.
HTC_TYTNII_KAISER said:
Hey, I'm gonna do this now:
"Quote:Originally Posted by kletiz
When used for just updating/adding a new Radio (1.71.09.01),
Is it neccisarry to do the whole "NBH Editor" thing? Or can I just throw it in the SD root and then power+cam stylus tap reset flash thing.
Click to expand...
Click to collapse
Just throwing it (properly named) into the root of the SD, then booting to bootloader worked perfectly for me. Try the simple before the complex.
The radio update won't brick it, but it may change the behavior of the audio systems. Worse comes to worse and you'll need to go back to your old radio, which you can d/l beforehand if you are worried.
Be sure you put on a HardSPL before you try upping the radio. I used the prog and SPL found here in the zipfile in the OP: forum.xda-developers.com/showthread.php?t=334679 to put on (removed the http to get around the link restrictions).
Before you do any of this, boot into the bootloader mode: phone is off, press and hold the power and camera buttons resulting in the tricolor screen. Once there, report the version and whatnot displayed at the top left of the screen.
Ok I'm assuming you managed to flash a new radio, however I do think you'll also have to upgrade winmo to 6.1, which will mean backing up everything and reflashing with a stock ROM.
Best to get one from here : http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs, I'd get the HTC WM6.1 ROM at the top of the page, not the AT&T one, ( nothing against AT&T just prefer the HTC one and it has a 1.70 radio ).
Get a hold of SPB Backup from somewhere, backup everything you need to SD card, then you should be able to upgrade using the same method as the radio upgrade, that is rename RUU_Signed.nbh to KAISimg.nbh and put it on SD card.
You should not need HardSPL to flash Stock ROMS, however it is a good idea to get HardSPL anyway, you'll need it for flashing the Android NBH if you decide to go Nand.
zenity said:
... I'd get the HTC WM6.1 ROM at the top of the page, not the AT&T one, ( nothing against AT&T just prefer the HTC one and it has a 1.70 radio ).
Click to expand...
Click to collapse
I didn't know that... But then wouldn't he/I need the keyboard fix? Plus, that radio didn't fix the android audio on my device.
zenity said:
... then you should be able to upgrade using the same method as the radio upgrade, that is rename RUU_Signed.nbh to KAISimg.nbh and put it on SD card.
Click to expand...
Click to collapse
So you can upgrade ROMs, not just radios that way? Good to know.
zenity said:
You should not need HardSPL to flash Stock ROMS, however it is a good idea to get HardSPL anyway, you'll need it for flashing the Android NBH if you decide to go Nand.
Click to expand...
Click to collapse
It's also needed if he wants to try any cooked WM ROMs, ja?
zenity: Have you tried any of the WM6.5 kaiser ROMs? Is there any real reason to try any of the cooked WM6.1 ROMs in your opinion?
I rather like the base 6.1 and I don't use any phone features so it seems like there isn't much reason to use any cooked 6.1 ROMs.
@ mr Fosi
Kay, I tried the cam+powa keys thing, and I see the TriCol Gradient for a slpit second, then it flicks to a white screen with the small blue words "loading..." Then it stays there, nothing further... That's bad right? What's up
I just checked, I have:
Windows Mobile(R) 6 Professional
CE OS 5.2.1620 (Build 18125.0.4.2)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Not my pic, just close to this)
Ok, total safety n00b here,
So how exactly do I update the Radio, step by step?
I've WinMo 6 Pro (Build 18125.0.4.2) and downloaded Radio "KAIS_Radinly_1.70.19.09.zip"
Whats next? (And what of white screen blue text loading thing?)
HTC_TYTNII_KAISER said:
@ mr Fosi
Kay, I tried the cam+powa keys thing, and I see the TriCol Gradient for a slpit second, then it flicks to a white screen with the small blue words "loading..." Then it stays there, nothing further... That's bad right? What's up
Whats next? (And what of white screen blue text loading thing?)
Click to expand...
Click to collapse
Make sure your SD Card is formatted to FAT32. SDCard on FAT16 has been the reason behind flashing problems for some.
xPreSiDenT said:
Make sure your SD Card is formatted to FAT32. SDCard on FAT16 has been the reason behind flashing problems for some.
Click to expand...
Click to collapse
Hey, my SD is formatted FAT32, (lol, didn't know FAT16 was still in use)
It just stops at loading..., what is the average time it stops?
HTC_TYTNII_KAISER said:
@ mr Fosi
Kay, I tried the cam+powa keys thing, and I see the TriCol Gradient for a slpit second, then it flicks to a white screen with the small blue words "loading..." Then it stays there, nothing further... That's bad right? What's up
Click to expand...
Click to collapse
You were trying to update your radio only, yes? This is exactly what happened to me when I tried installing the 1.70 radio without first installing a HardSPL. It won't cause any damage to your phone (as I am sure you have discovered) but the stock SPL won't let you upgrade the radio in this way.
Instead, either install a HardSPL such as the one on thread I pseudo-linked in post #12 or grab an official AT&T WM6.1 update and apply it. The official update won't give you the 1.70 radio but it will give you (what in my opinion is) the next best thing: radio 1.65.21.18. I suggest you try the official update first, since the 1.70 radio broke the audio in WM6 and didn't fix the audio in android on my Tilt.
I found a list of official AT&T Tilt/Kaiser roms here: wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs. I am using ver. 3.57.502.2 right now and I am very happy with it. It's nicer than the stock WM6.0 and the new radio fixed the audio and some of the settings crashes in Android.
HTC_TYTNII_KAISER said:
Ok, total safety n00b here,
So how exactly do I update the Radio, step by step?
I've WinMo 6 Pro (Build 18125.0.4.2) and downloaded Radio "KAIS_Radinly_1.70.19.09.zip"
Whats next? (And what of white screen blue text loading thing?)
Click to expand...
Click to collapse
I am also a bit skittish about bricking my device and I am a fan of keeping things simple, so may I suggest you do what I did? Grab the official WM6.1 v. 3.57.502.2 and install it. Forget the HardSPL for now, forget the radio-only upgrade. If you decide you want to replace windows later or want to use some cooked WM ROMs, you can worry about HardSPL then. Just apply the official WM6.1 update and see if it does what you need.
The step-by-step procedure is easy, though you should fix your USB connectivity issues:
- Pull out the SD & SIM cards.
- Connect your Tilt to a PC and allow Activesync/WM Device Center to connect and fully sync it.
- Once the connection is idle (syncing all done), run (on the PC) the "RUU_Kaiser_CINGULAR_WWE_3.57.502.2_radio_sign_25.88.40.05_1.65.21.18_Ship.exe" that you d/l from that list of official releases.
- Follow the on-screen instructions.
- Once your device is done being flashed, it resets itself then boots into WM and arrives at the "Tap screen to setup your device", do a hard reset.
- Let it reboot and do the setup.
- As soon as you get past the calender primer and the "setup password" dialog, you will see the home screen for an instant before a dialog pops up and says "setting up your device in 3 sec". Before that 3-sec dialog pops up, do a soft reset. This will keep the AT&T bloatware from installing. If you miss the window, the soft reset will be have like a hard reset and you'll go through the setup again. Just make sure you hit it before that 3-sec dialog box pops up. If you want that AT&T stuff, let it go without the soft reset.
- All done! Go ahead and pop your SD card back in and copy back all the stuff you backed up before the update.
A few questions for you:
- What version of windows are you using on your PC?
- What connectivity software are you using on the PC-end?
- Can you describe the USB connectivity issues you are having?
Apologies people, have not had time to sit down and experiment with my phone, real life caught up with me again. Sorry,
mr_fosi said:
A few questions for you:
- What version of windows are you using on your PC?
- What connectivity software are you using on the PC-end?
- Can you describe the USB connectivity issues you are having?
Click to expand...
Click to collapse
I'm using Windows XP pro SP2
Connectivity software? That's a laugh... I got 2 discs with my tytn2, a HTC/WinMo Getting Started disc and a Application disc (which only has Sprite backup and Spb GPRS Monitor) No Htc phone kit or anything or activesynch whatever.
The only connection problem I have is the normal USB cable to the small (htc style) cable connection. But that could be coz of the software
Hope this info helps
Hello,
I have a Rhodium 100.
I install this version on my MicroSD : http://forum.xda-developers.com/showthread.php?t=951817
I run haret.exe.
All lines are here.
The screen with xdandroid is here.
But after reboot, the phone run on Windows Mobile.
The thing that I want is only to have android on my phone.
Any help ?
Thanks
tim91700 said:
Hello,
I have a Rhodium 100.
I install this version on my MicroSD : http://forum.xda-developers.com/showthread.php?t=951817
I run haret.exe.
All lines are here.
The screen with xdandroid is here.
But after reboot, the phone run on Windows Mobile.
The thing that I want is only to have android on my phone.
Any help ?
Thanks
Click to expand...
Click to collapse
It works for CDMA devices, and it getting fairly stable. There's still some work to be done before GSM folks can join the party. Patience.
Tim, it sounds like maybe you might be able to benefit from installing GenY dualboot. It will allow your phone to boot directly to the Android OS without you having to manually run Haret from inside WinMo each time. It loads partway into WinMo (just enough to get whatever files it needs to run) then gives you a boot screen where you can choose which OS or choose for it to automatically boot to either OS.
SgtMac02 said:
Tim, it sounds like maybe you might be able to benefit from installing GenY dualboot. It will allow your phone to boot directly to the Android OS without you having to manually run Haret from inside WinMo each time. It loads partway into WinMo (just enough to get whatever files it needs to run) then gives you a boot screen where you can choose which OS or choose for it to automatically boot to either OS.
Click to expand...
Click to collapse
This is good advice. It's pretty good software, simple & to-the-point.
With that said, ACL (the developer who is mainly working on NAND development) is getting a GSM RHOD donated to him soon (I think he said it's in mail...) so once he hashes out the basics for GSM, it should apply to all GSM devices and they'll be able to join the party. So it won't be tomorrow by any means, but this is very good news for GSM users.
I'm going to close this thread, it has no business being in this section anyways.
So I bought a new phone since my old Onyx (One+ X) died (cracked screen and charging port is getting iffy). And finally I decided on this one, a cheap Chinese docomo branded one off Ebay.
I was so exited when it arrived, the UPS truck was at my gate when I got home that day, ready to leave, but the driver was nice enough to wait and give me my package then and there. Pheew.
Well, now to my, bootloader unlocking, recovery flashing, after market os installation and rooting story...
Bootloader:
The phone was supposed to be unlocked, and I guess that only meant SIM unlocked, because the service menu read "Bootloader unlock allowed: no". Damn.
A few Duckduckgo searches later, turned up I needed the "S!Unlock tool" which I found a copy off online, but username/password fields needed to be filled in, and I think I found a pirated s/n which didn't seem to work, (might have if I had tried harder).
But since it was just over £22 at https://networkunlocking.com/ I thought I could spare that on the off chance it worked. I was very surprised when it finally did, truth, I needed a few tries. And it actually did turn that service menu's pesky "no" to a thumbs-up "yes". Yay!
So now, pulling the cable, holding "volume up" and inserting cable for that blue light goodness, and running the "flashtool.exe -i 0x???? oem unlock bootloader 0x????????????" comand.
Not so fast, that doesnät work with newer flashtool versions...
Finding the old one from my Xperia Arc days and runnning it again, Yay!
(Wish I had read ahead and done that temporary root trick to rip my DRM codes off my phone first. But I don't plan to revert to stock, and I gather (might be wrong) that the DRM is only needed for stock roms, and not Lineage OS and such.)
Recovery (TWRP):
Now the problems start for real, getting into recovery was a **** and a half. Most guides for the phone says to push "volume up" multiple times during the boot-process. This turns out to be plain wrong. The actual button combo is holding "volume down" and "power" button together atleast until the screen goes blank after the unlocked bootloader warning.
Now, I wanted 17.1 on the phone and the recommended TWRp is 3.1.1 or something, and this works to install lineage fine, but don't forget to erase /data partition as I did. Stupid mistake that made wifi fail miserably, and probably a lot of other stuff, that I never tried before noticing my mistake.
However trying to get my own set of ringtones on the phone turned out to be another issue, going back into recovery when I noticed my ringtone.zip had failed. Obviously the media folder had moved since los 15.1,so no wonder right? Turns out it wasn't the only problem. TWRP 3.1.1 (or something) failed to unencrypt the root partition, so changing anything via recovery was a lie. fortunately the latest recovery, 3.5.2_9 did. So after installing that everything was rosy peaches.
Rooting:
SuperSU? forget it.
Magisk? yeah, but how? No really good step by step guide out there, except download from the github page, but what version?
A little trial and error, tried with the arm64 version and it turned out to be the right one. (Sometimes you just get it right on the first try...)
Renamed the apk to .zip put it on the phones memory, entered recovery and installed the zip, et voi effing la, Magisk root installed.
Root checker verifies root status, TitaniumBackup and RootExplorer works. Yes, my phone is playing ball.
Final notes:
This above looks simple right? In fact this was a two day process since the guides are surely lacking for this phone, a lot of trial and error, the greatesthurdle was getting into Recovery, until I found the right button combo I accidently managed to enter it once making me believe I had the right combo and something was wrong with the phone. 4 hours or so wasted trying different versions rebooting and flashing. Getting back my Viber messages turned out to be a problem to, TitaniumBackup got the messages back, but the db had references to my old images on my old phone, and probable pointed at the wrong directory so trying to send images either from gallery or take new photos crashed the app. Solution, backup the messages to my google account, uninstall and reinstall viber and restore from that backup. TitaniumBAckup is good but no magic bullet, it's a ***** that we have to rely on Google for backups though, I am allergic to the cloud, something about it makes my skin crawl.
Otherwise I like the phone, it says docomo on the back, something I can live with. The Chinese vendor even supplied one glass screen protector for the phone and a clear soft plastic case, in case I wanted some extra protection. I only wish there was a screen protector that had the same surface as the one that was on the phone in the box, that slightly opaque cloudy feel was so nice on my finger.
Can I recommend this phone? Nah, if noone writes a step by step guide that will cut down the time I spent on making this phone palpatable, I can't. But if you, like me, don't mind to tinker and don't want a phablet or spend way too much for the privilege to get a screen size you don't want, then sure. But why do we have to get them from China?
My trusty xz1 compact is slowly dieing on me and i am looking for a replacement how much did you pay for yours and is a really new or just refurbished ?
"Final notes:
This above looks simple right? In fact this was a two day process since the guides are surely lacking for this phone, a lot of trial and error, the greatesthurdle was getting into Recovery, until I found the right button combo I accidently managed to enter it once making me believe I had the right combo and something was wrong with the phone"
This Phone is in the mobile Sphere already ancient. Don't expect to get any help here or newer hot to guides.
my biggest problem is the fastboot recognition of my Windows. If this would work reliable i could better flash the phone but getting the right driver is a kind of roulette for this phone.
muhschaf said:
my biggest problem is the fastboot recognition of my Windows. If this would work reliable i could better flash the phone but getting the right driver is a kind of roulette for this phone.
Click to expand...
Click to collapse
Also had a non-connecting fastboot issue on Windows until I ran into this guide showing me it was not about a driver but an installation method:
How to install Sony Xperia Drivers Manually (Super Easy Guide)
Step-by-Step guidelines to install Sony Xperia Drivers Manually (this method can be used on Windows XP, Vista, Windows 7, Windows 8, 8.1 and Windows 10).
xperiausbdriver.com
4qx said:
Also had a non-connecting fastboot issue on Windows until I ran into this guide showing me it was not about a driver but an installation method:
How to install Sony Xperia Drivers Manually (Super Easy Guide)
Step-by-Step guidelines to install Sony Xperia Drivers Manually (this method can be used on Windows XP, Vista, Windows 7, Windows 8, 8.1 and Windows 10).
xperiausbdriver.com
Click to expand...
Click to collapse
Handy cannot boot now anyway so i would probably not able to recover anyway.
muhschaf said:
cannot boot now anyway so i would probably not able to recover anyway.
Click to expand...
Click to collapse
The phone completely refuses to boot?
Do you have recovery installed? If not, are you able to install it via fastboot on linux?
4qx said:
The phone completely refuses to boot?
Do you have recovery installed? If not, are you able to install it via fastboot on linux?
Click to expand...
Click to collapse
okay i will explain.
i had this common issue with this running out of internal space (13GB pictures i could not find, only 300MB left) and after looking into it i figured, that, due to my constant app installing and deinstalling, i had literrally thousends of little images (thumbnails, icons, you name it) that got not deintalled for whatever reason and clogged up my internal memory. So i made a Backup and decided to completly wipe and flash the newest lilac from Modpunk (18.1) and did a big Mistake here. i go into recovery and wiped EVERYTHING...without checking that recovery is untouched. then during the same session i installed the ROM and rebooted...so far all nice and dandy. Setting up the Phone, then get the newsest Gapps and then try to reboot into recovery to install them...well did i mentioned that i had wiped EVERYTHING? Well, there was no recovery anymore. Not my first rodeo i headbutt myself into the desk and spun up ADB/fastboot...only to run into the same problem i run everytime due to improper intalled driver i forgot already about. Longs story short: after some time handy refused to boot also into system.
Phone is now unbootable into any state, but Black screen fastboot over hardware buttons...
i COULD still try to make a blind fastboot flash after following the driver install instruction from above, but consider my lucky or clumsyness i will **** this up too and only waste time. and due to my current covid recovery i have not the energy nor the patient to diddle around with this sorry excuse of an absolute restrictive Phone and rather get me a S5 mini or something else that has no bootlock whatsoever and let you flash it from the very start.
i am plain running out of patient with sonys harassment.
/€: Also the constant "cannot get root" on a rooted phone is plain BS³. having permanent trouble to install adaway or use my sdcard proper is so friggin annoying that i now will search for a android version that got rid of this bull**** and will buy any phone that is suported by that ROM.
It is MY phone, and not Goolge nor the the phone company will dictade what i can or cannot install on it. i decide and i carry the risk, period. and the biggest security reason holds the phone anyway.
@muhschaf okay so it doesn't seem bricked. Pretty sure you just need to flash the recovery through fastboot and flash a ROM. Try that on Windows with the driver method; if that fails boot a Linux distro e.g. EndeavourOS, even from a USB without installing no adb/fastboot driver is necessary for Linux, it just works. You can do it.
4qx said:
@muhschaf okay so it doesn't seem bricked. Pretty sure you just need to flash the recovery through fastboot and flash a ROM. Try that on Windows with the driver method; if that fails boot a Linux distro e.g. EndeavourOS, even from a USB without installing no adb/fastboot driver is necessary for Linux, it just works. You can do it.
Click to expand...
Click to collapse
i known, the question is more "i really want that?" like i said i struggle with this phone ever since. and i realized yesterday the problem is not the phone itself, it's the bull**** of androids security architecture. Google seems to be very prone to make sure that they can shove any amount of advertisements down your throat. Given that they earn their money with ad network it doesn't surprise me.
i came to the conclusion that in reality i want to have a reliable way to install ad away on any given phone i own. i archive similar things on my desktop with Firefox and umatrix and ublock. And what can is say: Having Advertisment fee Internet is a bliss and i not care a bit about "but the free stuff" and i incrisingly fury about my inability to archive similar things on my phone i rely quite a bit.
@muhschaf I get it but you know what they say: good things require effort. But I find that once I set my Android up, I'm happy to have done it.
In regards to ads, you can actually install uBO on Android Firefox now, and many other addons also.
So i gave it a try again and the result was that it detects now a "?" under fastboot but ADB can't see anything failing sucsequently to flash recovery. i am also seemingly unable to get even into hardware fastboot anymore. But could be quite possible that the battery is already drained again. so i recharge it the night.
4qx: i was going away from uBO several years ago. Wonder that he has survived the drain after his "whitelist" decision, but it seems like.
Adaway block advertisement in apps and this is mainly the feature i wanted, see advertisment have gotten out of the browser itself into the Base/apps systems (Android, Windows) and therefore the Adblocker have to go with it. under windows i can control the System itself pretty easy and throughoutly with Powershell and package debloating scripts or regedit. under Android i haven't this option and have to rely on app like adaway. This shortcoming is pretty frustraing for an "Open Source" OS
After nearly a Year i stumble upon something windows related and now i have finally my xz1c back:
Windows USB Hubs of ANY kind (Monitor USB Hubs, Powers external USB Hubs, hell sometimes even the PCH, that is technical also a USB Hub), can and sometime WILL prevent proper lowlevel access to devices like...USB Headsets (Logitech Pro X) and Mobile Phones in fastboot mode (xz1c).
To circumvent this you have to connect the phone to a USB Port on the Back of your PC Motherboard DIRECTLY. every other Port can have an USB Hub in between that alters your write or readout and therefore failed the flashing.