I get after 1% of the progress bar after all the rest of the questions an error 244 on the athena. Can anyone help. This apparently is a "INVALID MODEL ID " and I can't see why this would be. I have tried the 12 AP 3an and 4 as well as the michy rom. All do the same
And yes I have seen "How to FIX INVALID MODEL ID after bad flashing " post but when I follow the thread through the forun I get to the fixing wifi using mtty, is this really all that needs doing. Does the mac address and wifi sort also fix the vendor ID?
btbill said:
I get after 1% of the progress bar after all the rest of the questions an error 244 on the athena. Can anyone help. This apparently is a "INVALID MODEL ID " and I can't see why this would be. I have tried the 12 AP 3an and 4 as well as the michy rom. All do the same
And yes I have seen "How to FIX INVALID MODEL ID after bad flashing " post but when I follow the thread through the forun I get to the fixing wifi using mtty, is this really all that needs doing. Does the mac address and wifi sort also fix the vendor ID?
Click to expand...
Click to collapse
from the readme doc in radio 1.58 upgrade
" ERROR [242] : INVALID LANGUAGE
ERROR [244] : INVALID MODEL ID
ERROR [294] : INVALID VENDER ID
ERROR [296] : UPGRADE ONLY
One of these error messages will appear when you use the wrong RUU to do the upgrade. RUU will check if the Model ID and Language ID are compatible with the device. Make sure you use the appropriate RUU tool to upgrade."
Have you unlocked the phone?
read this
http://forum.xda-developers.com/showthread.php?t=429013
Yep thanks, aware of that and already new it was invalid model ID hence why its in my post. It a freinds Athena running SPL1.2 Mine on 3.5. We have both tried a number of roms previously and this happened when going to michy 6.1 for SPL1.2. (Note I had no issues on the SPL 3.5 athena).
Its odd, but what I really wanted to know was why when you follow the forum thread through on how to fix this you end up getting to the mac address fix using mtty? Why would the MAC WiFi fix fix the invalid model ID?
The Invalid model ID that that thread was for was caused by trying to flash a 3.5 ROM on SPL1.2which messed up all sorts of things.
Have you tried flashing the ROM you were using before?
btbill said:
Yep thanks, aware of that and already new it was invalid model ID hence why its in my post. It a freinds Athena running SPL1.2 Mine on 3.5. We have both tried a number of roms previously and this happened when going to michy 6.1 for SPL1.2. (Note I had no issues on the SPL 3.5 athena).
Click to expand...
Click to collapse
more information is good,better than mind reading!
My point was as confucious pointed out , you need to flash the right SPL version
btbill said:
Its odd, but what I really wanted to know was why when you follow the forum thread through on how to fix this you end up getting to the mac address fix using mtty? Why would the MAC WiFi fix fix the invalid model ID?
Click to expand...
Click to collapse
The reason they are both together was that cmonex was talking people through fixing both these problems on irc and eventually got sick of this so wrote a script to fix both problems at once.
Have you checked your SPL from bootloader? Sometimes it is not what you think and you will be able to see if the model id is corrupted.
I don't know your level of knowledge and if you have tried to flash from bootloader or can boot into an OS and are trying to flash via active sync.
It would also help to know what radio you had installed and if you are using vista/xp withh the appropriate Dotnet package
When you see someone with only a few posts asking for help, most people assume you don't have a lot of experience flashing roms
Thanks for the notes. Yes I tried to reflash from the bootloader. This is the first thing I tried. This where It all looks good then as the rom is progressing in the update bar on the PC and the grey screen you get on the athena. It never gets past 1% and then comes up with the error as described, the 244 error. BTW I have just done MTTY stuff..... holding breath now as try to reflash with a SPL1.2 R5.1 Michy.
Hey Worked, good stuff! always nice to know why you are doing something. So now we have a ROM with SPL1.2 we are now going to load the officeal AP4 latest as I am using on mine and I love it.
AP4 is quite old now - have you thought about Michy's ROM which comes in 1.2?
Mac address
btbill said:
thanks for the notes. Yes i tried to reflash from the bootloader. This is the first thing i tried. This where it all looks good then as the rom is progressing in the update bar on the pc and the grey screen you get on the athena. It never gets past 1% and then comes up with the error as described, the 244 error. Btw i have just done mtty stuff..... Holding breath now as try to reflash with a spl1.2 r5.1 michy.
Hey worked, good stuff! Always nice to know why you are doing something. So now we have a rom with spl1.2 we are now going to load the officeal ap4 latest as i am using on mine and i love it.
Click to expand...
Click to collapse
hi there,
i wanted to know that i am facing the same problem that u faced earlier. And u figured out the way to exit that problem through mtty and mac address.
My athena is stuck the bootloader screen so how can i get the mac address of my athena?
Is it printed somewhere on the device or do it comes with the manuals?
Help needed in this regards.
ERMANO.ESTE said:
hi there,
i wanted to know that i am facing the same problem that u faced earlier. And u figured out the way to exit that problem through mtty and mac address.
My athena is stuck the bootloader screen so how can i get the mac address of my athena?
Is it printed somewhere on the device or do it comes with the manuals?
Help needed in this regards.
Click to expand...
Click to collapse
It should be printed on the label inside the battery door cover, if not then i think you can find a piece of network equipment that you no longer use on your network and use that mac address.
Related
Dear friends
I was tring to upgrade my iMate Pocket PC also know as Himalaya with windows2003 SE , while upgrading I faced problems, the upgarde failed and now I am just getting no display and OS too. The only message displayed is
Serial
v1.03
nothing is working please help
bye with regrads,
your unit is still okay; even better that the usb version is showing on the screen. it's simply stuck on bootloader mode. what kind of problems did you encounter resulting in the failed upgrade?
one suggestion i can give before you downgrade is to try and proceed with the upgrade to se. put your unit back on the cradle but don't expect activesync to "recognize" the device. just put it back on the cradle and rerun the upgrade to se.
same thing happened when i upgraded but to wm2005. the screen showed error and the only thing on the screen was the usb version. i simply cradled back the unit and ran the upgrade. worked.
cheers
Hi
Thanks a lot, i tired those steps before and even now I did but its not upgarding I am gettig following error as show i the attachment. Please let me know what to do
thanks a lot
yas
oh, it appears that you have the "wrong country" id issue. i'm not entirely sure as to how to avoid this but i believe it has something to do with the correct rom version (guys, correct me if i'm wrong). where did you get the rom you used for upgrading to se? downgrading might be the only trick if there is no rom for saudi-based users...but if any chaps presently living there and were successful in upgrading their units perhaps you could share the rom version/s you used?
cheers
yasirirfan said:
Hi
Thanks a lot, i tired those steps before and even now I did but its not upgarding I am gettig following error as show i the attachment. Please let me know what to do
thanks a lot
yas
Click to expand...
Click to collapse
To overcome the Country ID Error, first you need to install this tool...
ftp://xda:[email protected]/Tools/ER2003Edit_1_4_26.zip
Open the ROM file you want to upgrade, then change the appropriate 'Operator ID' code, after this click 'Save ROM image'.
Upgrade ur device. You will no longer face the error message.
All rite here we go, in advanced i thank u guys for trying to help me out here.
First, i'm a n00bie compared with the most of u guys.
My Device:
Tytn Herm 300
OS: Schaps Purple 3.30c
SPL: Hard-Spl 2.10 oli
Radio: 1.16.00.00 !Hmzz...that's the problem!
My phone functionallity sucks...some how it keep loosing connection while i see the phone indication bar up to 3 bars. So i decided to do something about it.
Beeing a noob i thought it got to do something with the OS. So i upgrade it to Schaps's wonderfull purple WM6 Hermes 3.30c and loaded the Hard SPL 2.10 oil V7. All went great, and my Hermes never looked so cool before.
But now i'm trying to upgrade my radio, which is still version 1.16.00.00, to what ever better version. I tried every radio upgrade possible from this list:
http://wiki.xda-developers.com/index...actedRadioRoms
Every single one starts well. passed the information retrieving from my phone. Confirmed the update, and then there was the installation progress bar....
All versions of the radio roms i downloaden get stuck in here. It doesn't even start..0% and error... And really i dun have any idea why.
So after re-flashing a gazillion times, i decided to ask help to the allmighty XDA community. So pls, if anybody there got a suggestion or the solution...i would be so thankfull and will slaughter a goat to worship you
If you've got schaps Rom and HardSPL on your phone then you obviously don't have problems flashing or with PC/phone comms.
When you try flashing the radio, how long do you wait before deciding it doesn't work? I've found that some of them can take what seems like a really long time and I'm tempted to unplug and start again.
Maybe try again, then go make yourself a cup of tee/coffee or get a beer then come back 10 minutes later. If the upgrade still hasn't worked we'll have to look a bit deeper
RaDeNRFX said:
- I am so sorry posting this twice in the wrong sections, it seems that i'm a really noobie forum user - But i finally found the rite section. So my humble excuses.
All rite here we go, in advanced i thank u guys for trying to help me out here.
First, i'm a n00bie compared with the most of u guys.
My Device:
Tytn Herm 300
OS: Schaps Purple 3.30c
SPL: Hard-Spl 2.10 oli
Radio: 1.16.00.00 !Hmzz...that's the problem!
My phone functionallity sucks...some how it keep loosing connection while i see the phone indication bar up to 3 bars. So i decided to do something about it.
Beeing a noob i thought it got to do something with the OS. So i upgrade it to Schaps's wonderfull purple WM6 Hermes 3.30c and loaded the Hard SPL 2.10 oil V7. All went great, and my Hermes never looked so cool before.
But now i'm trying to upgrade my radio, which is still version 1.16.00.00, to what ever better version. I tried every radio upgrade possible from this list:
http://wiki.xda-developers.com/index...actedRadioRoms
Every single one starts well. passed the information retrieving from my phone. Confirmed the update, and then there was the installation progress bar....
All versions of the radio roms i downloaden get stuck in here. It doesn't even start..0% and error... And really i dun have any idea why.
So after re-flashing a gazillion times, i decided to ask help to the allmighty XDA community. So pls, if anybody there got a suggestion or the solution...i would be so thankfull and will slaughter a goat to worship you
Click to expand...
Click to collapse
ach2 said:
If you've got schaps Rom and HardSPL on your phone then you obviously don't have problems flashing or with PC/phone comms.
When you try flashing the radio, how long do you wait before deciding it doesn't work? I've found that some of them can take what seems like a really long time and I'm tempted to unplug and start again.
Maybe try again, then go make yourself a cup of tee/coffee or get a beer then come back 10 minutes later. If the upgrade still hasn't worked we'll have to look a bit deeper
Click to expand...
Click to collapse
I waited till the Program says connection error...and send me to recovery proces. And i've been making hella tons of coffee after trying to flash that many Radio Roms. Any other suggestions? I'm so desperate
Ok, maybe some more info...
Do you see 'NO GSM' during the phone boot process?
Do you have no radio at all or just intermittent reception?
Are you running Vista?
What is the connection error number?
If you've lost the radio but have hard SPL it may just be a case of re-flashing an original manufacturers ROM (which will include the radio) then start your upgrading again afterwards. Don't forget to back-up data before flashing.
If you do flash a manufacturers shipped rom - check that you still have HardSPL afterwards.
ach2 said:
Ok, maybe some more info...
Do you see 'NO GSM' during the phone boot process?
Do you have no radio at all or just intermittent reception?
Are you running Vista?
What is the connection error number?
If you've lost the radio but have hard SPL it may just be a case of re-flashing an original manufacturers ROM (which will include the radio) then start your upgrading again afterwards. Don't forget to back-up data before flashing.
If you do flash a manufacturers shipped rom - check that you still have HardSPL afterwards.
Click to expand...
Click to collapse
Well the weird part is "No GSM" appeared occasionally...some times it shows it sometimes it's not showing it.
No...i'm a Vista hater. And dun have the original manufacturers ROM. I've got the "T-Mobile Vario II" from The Netherlands..so if anybody got a link for the original version i'd be thankfull.
The Radio it self is intermittent and very inpredictable...for example:
Radio indicator says i got full recieve:...but i can't call or recieve any.
Connection error: 262 (which is, if i'm not mistake a connection error.) Which is bull cuz i'm re-running every other ROM's upload with the same way and succeded/
Radio indicator says no reception and shows an exclamation mark:...and my GF just called me to hurry up and pick her up :/
But the weird part is...it seems that my radio ROM is locked somehow. I can upgrade or downgrade SPL's and OS ROM's but not the Radio ROM.
I've tried to use MTTY by now and followed the manual bellow: (Problem 5)
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems#problem5
But it began with invalid password. Procede as written and it didn't helped.
More suggestions are welcome
My bad...i didn't looked well enough. It is saying No GSM the whole time.
More information:
I've checked the Device information on the Hermes now some information are blank:
Radio: Blank
Protocol version: Blank
IMEI: Blank
All other information field are filled. Been spending hours reading tutorials and manuals...and nothing. HELP!
OK,
This isn't a problem I've had myself, but loads of other people have and there are quite a few threads on how to unbrick from here... you're going to have to do a bit of reading.
This page shows the different combinations of OS/radio/brick type etc and should point you in the right direction for the correct course of action http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick
Then read through this thread http://forum.xda-developers.com/showthread.php?t=286755 . It's got really long but read the beginning where POF describes the types of problem and also the solutions. Then it's probably best to jump to somewhere near the end and pick someone who has a similar problem.
It sounds to me as though you need to just flash a radio in nbh format, but please do some more reading before you do this to check my advice - as I said at the beginning, I haven't had this problem so I'm only giving advice from what others have written.
ach2 said:
It sounds to me as though you need to just flash a radio in nbh format, but please do some more reading before you do this to check my advice - as I said at the beginning, I haven't had this problem so I'm only giving advice from what others have written.
Click to expand...
Click to collapse
I am really thankfull of ur post. Unfortunately, i've been doing some reading. Including the link u gave me. The problem is that i can't upload/flash Radio in nhb format.
As i described in the first place, i can't load a nhb format radio in RUUWrapper.exe properly. It can start the proces..but it always end up with a connection error code 260/262 during the installation progres bar (0%).
The solutions some ppl tried in ur link is often not my case. And the similar cases i have tried where i end up with the same grumpfy situation.
have you tried to flash the radio using the SD card method? I too have a cable connection problem but I fear mine may be hardware failure.
Yap...and no luck
Hello, I am in serious trouble! I got a brand new HTC Athena with Windows Mobile 5.0. I succesfully upgrade it to Windows Mobile 6.0.
All was OK.
Than I was interested to move into Windows Mobile 6.1 and possibly 6.5. At first I did the Athena unlock (3 step process) and all went OK: Antenna 1.5.0, SPL 1.2 OLI....
THAN I DID MY ERROR! I try to upgrade my 6.0 ROM with the Micky 6.1 cooked file with SPL 3.5. After a 92 percent upgrade, the ROM crashed and now I always get a nasty black screen with few lines (No 3 color bands!). When I try to upgrade again the same ROM or ROM for SPL 1.2 I get an error (ID mismatching). I guess the only solution is a hard and full reset of the Windows. But doing only a hard reset with the PDA will NOT change my error message and I will keep see this nasty black screen and I cannot load the Windows ActiveSync application-
I am totally lost. Help please. Any tool for a true full restore/recover??? (I did NOT make any backup!).
This thread might hold a solution to your problem.
Hi
If you follow the instructions exactly in post 33, it will solve your problems. just click HERE
Jay
Hello, those links are basically for corrupted wifi antenna files.-
In my case my HTC Athena crashed the Windows 6 ROM while I was attempting to upgrade, after unlocking the phone, the Athena from version 6.0 to version 6.1
Are you sure I can use the post #33 also for my specific trouble?
Thank you in advance!
this is also to repair your bootloader-infos
if you look at your bootloaderscreen, you will see ATHE100, IPL, ATHE100, SPL. if not, you have to repair it
make sure you flashed the right rom, spl 1 or 3.5
How can the bootloader get repaired?
yes use that link, post #33. fixes both wifi and modelid problems and bootloader problems when you got stuck at 92% of the flashing process.
Cannot re flash ROM
Please help! I tried the unlocker and it failed at 92% and since then I have no WM6. Then I tried to flash the Michy WM6.5 and that failed. I was getting model id errors so I did the mtty and mac1 fix which was succesful. However all I can get now is a grey screen on boot-up. I can get to the bootloader screen and it displays ATHE100, IPL-v2.02, ATHE100, SPL-v1.20. Olipro. From what I have read on the forum at this stage I should run a RUU to flash a WM6 ROM but all that I try can't connect because no OS running to connect with Activesync? Is there a way to flash from the bootloader? The other option seems to be putting an image and flasher on a miniSD but I can't find clear instructions for this or which files?
Please ignore - my battery wasn't charged enough. Replaced battery and recovered device.
Still Major Problem! Help me! Have mercy!
Hello Responderman, all,
I have follow the link (thread 33)...., however, after I have typed lnbs filename.bin 75108000 (I have SPL 1.2), I got in mtty the "code entrypoint unknown" message, which should be ok......
However, after I have disconnected the usb cable of the Athena from the PC and try to reboot it, I got again the exact same, nasty, dark screen with blue strips.....:-( It means that my damaged firmware has NOT been fix and in fact I am still NOT able to boot WM successfully!
PLEASE HELP. It is 3 months with this problem and I cannot use my device.:-(
Still Major Problem! Help me! Have mercy!
Hello Responderman, all,
first, how can I get the mac address of my device? It is NOT written anywhere in the Athena parts (checked in the battery bay and so on.....), and so when I run mtty i am in trouble! I have used a mac address got from my company's manager, but not sure it is ok to use it with the Athena!
Anyway,......I have follow the post link (thread 33)...., and followed the various steps.- However, after I have typed lnbs filename.bin 75108000 (I have SPL 1.2), I got in mtty the "code entrypoint unknown" message, which should be ok......
However, after I have disconnected the usb cable of the Athena from the PC and try to reboot it, I got again the exact same, nasty, dark screen with blue strips.....:-( It means that my damaged firmware has NOT been fix and in fact I am still NOT able to boot WM successfully!
PLEASE HELP. It is 3 months with this problem and I cannot use my device.:-(
Solved!
Hi, problem done. I have follow the remarks, fixed my broken firmware and now I use well Athena with VM 6.5! Thanks all for your help!
puffo said:
Hi, problem done. I have follow the remarks, fixed my broken firmware and now I use well Athena with VM 6.5! Thanks all for your help!
Click to expand...
Click to collapse
Can you tell what you've actually done after you've changed ROM with Mtty?
I done the thing with Mtty but just as you described when I reset it now I still get the grey screen. And if I try to update ROM it fails again on 92%
where did you find the upgrade from wm5 to wm6?
the link I found on rapidshare seems not be availabel anymore
HI THERE,
I AM USING WM 6.0 WITH SPL 1.1. THE PROBLEM IS THE ERROR 270.
WHENEVER I TRY TO UPGRADE MY ROM TO WM6.1 OR WM6.5 OR EVEN WHEN I TRY TO UPGRADE MY RADIO TO VERSION 1.57, THE MOBILE SIMPLY GOES TO BOOTLOADER AND AFTER COMPLETING JUST 1% , IT RESTARTS AND THE PC SHOWS "ERROR 270 [UPDATE ERROR]- THE IMAGE FILE IS CORRUPTED. PLEASE CHECK YOUR UPDATE UTILITY".
I HAVE TRIED DOING HARD RESET BUT OF NO USE.
EVERYTHING ELSE (LIKE CALLS, GPRS, GPS) IS WORKING FINE. BUT I CANNOT UPGRADE THE ROM.
ANY SUGGESTION TO PREVIOUS POSTS OR NEW SOLUTIONS IS NEEDED.
ERMANO.ESTE said:
HI THERE,
I AM USING WM 6.0 WITH SPL 1.1. THE PROBLEM IS THE ERROR 270.
WHENEVER I TRY TO UPGRADE MY ROM TO WM6.1 OR WM6.5 OR EVEN WHEN I TRY TO UPGRADE MY RADIO TO VERSION 1.57, THE MOBILE SIMPLY GOES TO BOOTLOADER AND AFTER COMPLETING JUST 1% , IT RESTARTS AND THE PC SHOWS "ERROR 270 [UPDATE ERROR]- THE IMAGE FILE IS CORRUPTED. PLEASE CHECK YOUR UPDATE UTILITY".
I HAVE TRIED DOING HARD RESET BUT OF NO USE.
EVERYTHING ELSE (LIKE CALLS, GPRS, GPS) IS WORKING FINE. BUT I CANNOT UPGRADE THE ROM.
ANY SUGGESTION TO PREVIOUS POSTS OR NEW SOLUTIONS IS NEEDED.
Click to expand...
Click to collapse
Hi you need to unlock the phone
read the beginners guide in the sticky for WM6 section
Read first then flash
How to get mac address
lakeman said:
Hi you need to unlock the phone
read the beginners guide in the sticky for WM6 section
Read first then flash
Click to expand...
Click to collapse
Thanks alot lakeman for ur help.
SOLVED OUT THAT ISSUE, BUT FACED A NEW ONE.
I M STUCK AT BOOTLOADER SCREEN WHILE TRYING TO INSTALL WM6.5.
BUT I FIGURED OUT A WAY BY USING MAC AND MTTY FORMAT.
BUT I DONT KNOW HOW TO GET MY MAC ADDRESS WHILE THE ONLY THING I CAN ACCESS IS THE BOOTLOADER SCREEN?
IS IT PRINTED SOMEWHERE ON MY DEVICE OR MANUALS OR IS THERE ANY SPECIFIC COMMAND FOR THAT?
Hello friends, help me please.
I had a 1.66 HSPL.
After Hard Reset my HD2 won't swich on. It stops on HTC logo.
I did HR again - the same result.
Then I tried to flash it, all went fine but now instead of HTC logo i see only Bootloader screen and the name of the devise are corrupted.
in bootloader
1#MIBX? HX-BC
SPL-1.66. HSPL XE
0x05
CotullaHSPL 0x40
I can flash any SPL using the file "ModelIDCheckBypass.txt" on drive С: - same result.
but i cant flash even his own ROM because the name of the devise are corrupted. it stops on 1% with ERROR [244] INVALID MODEL ID
If i flash from microSD-card - 00058002 ERROR
How to bypass ID check????
What to do?? any ideas?
Xandr23 said:
Hello friends, help me please.
I had a 1.66 HSPL.
After Hard Reset my HD2 won't swich on. It stops on HTC logo.
I did HR again - the same result.
Then I tried to flash it, all went fine but now instead of HTC logo i see only Bootloader screen and the name of the devise are corrupted.
in bootloader
1#MIBX? HX-BC
SPL-1.66. HSPL XE
0x05
CotullaHSPL 0x40
I can flash any SPL using the file "ModelIDCheckBypass.txt" on drive С: - same result.
but i cant flash even his own ROM because the name of the devise are corrupted. it stops on 1% with ERROR [244] INVALID MODEL ID
If i flash from microSD-card - 00058002 ERROR
How to bypass ID check????
What to do?? any ideas?
Click to expand...
Click to collapse
Try with a goldcard. This skips the Model ID.
Go to bootloader and try to flash HSPL2 or HSPL3 and then flash a stock rom witch You can find on this site. This should help You.
xmoo said:
Try with a goldcard. This skips the Model ID.
Click to expand...
Click to collapse
but how to make goldcard if it does not swich on?
daniel81uk said:
Go to bootloader and try to flash HSPL2 or HSPL3 and then flash a stock rom witch You can find on this site. This should help You.
Click to expand...
Click to collapse
i tried each of SPL/HSPL but it won't fix id name - so the same result [244] INVALID MODEL ID
third thread i've read with screwed up dev id after flashing and/or task 29 in a week. making me nervous!
Xandr23 said:
but how to make goldcard if it does not swich on?
i tried each of SPL/HSPL but it won't fix id name - so the same result [244] INVALID MODEL ID
Click to expand...
Click to collapse
when I had a problem with ID ive fixed it with HSPL 2. If it worked for me so should work for You. remember HSPL2 OR HSPL3!
samsamuel said:
third thread i've read with screwed up dev id after flashing and/or task 29 in a week. making me nervous!
Click to expand...
Click to collapse
If You dont want to help dont write anything at all please . Not everyone know how to flash a phone and have to learn on their own mistakes. I learned this way myself.
daniel81uk said:
If You dont want to help dont write anything at all please . Not everyone know how to flash a phone and have to learn on their own mistakes. I learned this way myself.
Click to expand...
Click to collapse
i was actualy raising the point that there have been three threads in the past week where someone has been flashing and / or using task29, and now their bootloader shows corrupted model ID.
I wasnt being funny, or sarcastic, I was posting an observation. I worry about trends like three similar issues in a few days of each other (and between you and me i dont use task29, i dont trust it, it crops up in far too many 'can no longer flash'/'can no longer enter bootloader' threads,,,sorry doloop,,,mtty all the way for me) and i spent an hour earlier trying to find the thread where the guy posted a screenshot, and yes, the model ID is propper messed up, all strange characters and what not.
samsamuel said:
i was actualy raising the point that there have been three threads in the past week where someone has been flashing and / or using task29, and now their bootloader shows corrupted model ID.
I wasnt being funny, or sarcastic, I was posting an observation. I worry about trends like three similar issues in a few days of each other (and between you and me i dont use task29, i dont trust it, it crops up in far too many 'can no longer flash'/'can no longer enter bootloader' threads,,,sorry doloop,,,mtty all the way for me) and i spent an hour earlier trying to find the thread where the guy posted a screenshot, and yes, the model ID is propper messed up, all strange characters and what not.
Click to expand...
Click to collapse
Between You and me - I always use task29 b4 flashing and never had a problem with it. and Im flashing every 2-3 days If You do it in the right way, nothing should go wrong.
i agree, a very useful tool, all credit to doloop for hexing the ruu.
however the fact that it is doing a flash and then erasing it seems like an unneeded extra flash, and every time you flash there is an element of risk, albeit small, a chance it will go wrong for no apparent reason, and especially if you use the radio rom method, since it seems bad radio flashes are more damaging than rom flashes.
since we flash several times a week, (i've done a half dozen flashes just this evening, playing with my kitchen ) you are doubling that small chance of something going wrong. with mtty, you are issuing the command directly, no flash involved.
hey..
i actually have the same problem as you
can you please let me know if you find a way to fix
i got this problem because the updates of the roms are soo frequent
i jstu keep doing the flash and new rom with the task 29 becasue i thoguht that does likea smiilar task to formatting a comp.