Related
Ok, I've been trying to update my 8525 for hours...here is my problem. First, I tried to HardSPL-v7 but I kept getting an "Error [240] File open". I think this is preventing me from doing any ROM update. When I try to run the Cingular ROM update activesync shuts down and I get a connection error, I think it is "error [260]". I have wiped or cleaned out my 8525 so that I am back to day one. I have tried both ROM updates on 2 separate computers and I get same error messages on both computers. I have searched the Wiki's but have found nothing, so please help. As you can tell, I am a virgin to ROM updates so please go gently.
I should add, my present ver. ROM AKU 2.3 (1.34.502.7018.01H) SPL 1.06 IPL 1.01. Radio is 1.16.
have you taken a look at my Safe WM5 Upgrade Guide??
If you follow this guide EXACTLY, you should be fine.
mrvanx said:
have you taken a look at my Safe WM5 Upgrade Guide??
If you follow this guide EXACTLY, you should be fine.
Click to expand...
Click to collapse
I have, I have even tried the mtty "fix" but I had problems with that as well. I get a modem connection screen but there is nothing about a USB connection.
Bit more info would be nice, which ROM are downloading, and where from??
Also what procedure are you doing to update?? EXACT info please.
mrvanx said:
have you taken a look at my Safe WM5 Upgrade Guide??
If you follow this guide EXACTLY, you should be fine.
Click to expand...
Click to collapse
Ok, I just tried it 2 more times, Hard-SPL. It flashes to the 8525 and goes into bootloader and shows the following "HERM100 IPL-SSPL by Des HERM100 SPL-1.09.ds" at this point activesync 4.5 shuts down the 8525 is stuck in bootloader (it never reboots) and after a few minutes I get "Error [260] Upated Error". Hard SPL shuts down and the 8525 is stuck in bootloader mode. At this point I have been disconnecting the USB cable and doing a soft reset, once the phone is on, I go into bootloader and the old info shows up SPL 1.06 and IPL 1.01.
Let me have a think, firstly do you have the latest versions of the .net framework installed?
I was able to finally run HardSPLv7, I had to do it on another computer. Now, I would like to update to RUU_Hermes_CINGULAR_WWE_2.15.502.3_6275_1.40.30.00_108_Ship.exe. I assume I should use the same computer that I used to successfully run HardSPL. Do I need to rebuild the rom file with RUUWrapper.exe (CustomRUU by olipro) & Dutty's Good NBH Tool, before running the RUU_Hermes_CINGULAR_WWE_2.15.502.3_6275_1.40.30.00_108_Ship.exe update?
mrvanx said:
Let me have a think, firstly do you have the latest versions of the .net framework installed?
Click to expand...
Click to collapse
I have .Net 1 thru 3.5 (pre-release) installed on the computer that I can not get to run any ROM updates.
9
compudds said:
I was able to finally run HardSPLv7, I had to do it on another computer. Now, I would like to update to RUU_Hermes_CINGULAR_WWE_2.15.502.3_6275_1.40.30.00_108_Ship.exe. I assume I should use the same computer that I used to successfully run HardSPL. Do I need to rebuild the rom file with RUUWrapper.exe (CustomRUU by olipro) & Dutty's Good NBH Tool, before running the RUU_Hermes_CINGULAR_WWE_2.15.502.3_6275_1.40.30.00_108_Ship.exe update?
Click to expand...
Click to collapse
Yes if you carry on the guide past flashing hardspl you will get the radio updated aswell.
Can i ask, what is different on the computer you used???
mrvanx said:
Yes if you carry on the guide past flashing hardspl you will get the radio updated aswell.
Can i ask, what is different on the computer you used???
Click to expand...
Click to collapse
Off hand, the major difference would be Intel (worked) vs. AMD (failed) but I doubt that is the problem, you would be flooded with questions due to so many computers that have AMD chips. The USB cable was the same as well. I'll have to think about that...
Definatly check your "failed" computer is up to date with .net and everything else, most likely a software problem.
I have this problem as well..
AT&T 8525 windows moble 6 trying to install the hardspl v7.
v3.5 and 3.0 .net framework.
the RUUwrapper program gets to the 'verifiying info' screen then give me an erroe 240 message. 'the update utility can not open the requested file.'
any help would be great. Looking to add the touch it interface.
thanks,
Mike
Read the post Hard SPL at the top of this forum and go to page 116 ( I believe its post #1160) and use the sd card method. You don't need to use the pc at all. I generally flasah ALL os's using the sd card method as it seems to be safer then using the usb method. No "sync errors" to deal with.
Cheers...
I have the exact same problem..
When it goes to tri-color screen, the USB connection goes off and windows will pop up the search for driver dialogue box.. then afterward another dialogue box will appear saying Error [260].
I tried restarting my pc and device (even removing the battery) but still failure
Any help would be highly appreciated. Thanks.
blackphnx said:
I have the exact same problem..
When it goes to tri-color screen, the USB connection goes off and windows will pop up the search for driver dialogue box.. then afterward another dialogue box will appear saying Error [260].
I tried restarting my pc and device (even removing the battery) but still failure
Any help would be highly appreciated. Thanks.
Click to expand...
Click to collapse
I loaded it thru the sd card just as the post above suggested. It loaded the hardspl just fine. My PPC seems to run faster as well.
Thanks for the help! it is much appreciated.
blackphnx said:
I have the exact same problem..
When it goes to tri-color screen, the USB connection goes off and windows will pop up the search for driver dialogue box.. then afterward another dialogue box will appear saying Error [260].
I tried restarting my pc and device (even removing the battery) but still failure
Any help would be highly appreciated. Thanks.
Click to expand...
Click to collapse
One thing that i have learned from flashing my 8525 is to remove any USB device except the 8525. This has worked for me.
swimmy said:
One thing that i have learned from flashing my 8525 is to remove any USB device except the 8525. This has worked for me.
Click to expand...
Click to collapse
But my mouse is on USB. I might try on different computer and post back the results.
UPDATE
I tried using my friend's laptop and it installed without a problem. I think the issue is with the .NET framework. I installed the latest one before flashing and it worked fine. Hmmm.. Im not sure about this tho.
Hello.... Try the sd card method. You don't need the computer...
Sorry if I sound condescending, but, I seem to find a lot of people saying that they have sync problems. Solution, Take the pc out of the equation (except to load files onto sd card). It is SOOO much safer then using the pc, no "sync" problems, no chance of usb being disconnected, reset button being hit or , worst case scenario, power failure...
You have to either have little or no battery power or MANUALLY hit the reset button with the stylus to stop the flash...
And thats my 2 cents....
Refer to post #13 to find out how to use sd card method to flash hard spl...
Cheers...
sd card method???
how?
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.
I'm new on the forum, very informative but I could'nt find an answer to this situation. I have a HTC Advantage 7500 that originally came with mobile 5 on it and last year I successfully upgraded it to mobile 6. Couple of days ago I wanted to try something new so I upped it to 6.5 via a link on this site somewhere. The rom update went smoothly but I would like to go to 6.1 because for one the micro drive is not seen under the 6.5 that I have plus it has a slow response to screen manuvers and such. Now when I try to install mobile 6 or 6.1 it says please wait while the update takes place but my device restarts and the error #260 box comes up that says the update utility cannot connect to your PDA phone. Please check your USB connection. I would appreciate any help or suggestions. I know maybe I was wrong to try the mobile 6.5 on this. confused:
Since you are able to use 6.5, (it was a spl 3.5 version unless you
had found and used a spl 1.2) your phone should be having spl 3.5.
You need to search and download 6.1 spl 3.5 rom to change it.
Oh...Welcome!!
pdajoy said:
Since you are able to use 6.5, (it was a spl 3.5 version unless you
had found and used a spl 1.2) your phone should be having spl 3.5.
You need to search and download 6.1 spl 3.5 rom to change it.
Oh...Welcome!!
Click to expand...
Click to collapse
Thanks for your reply. I do now have the file 6.1 spl 3.5 but my device on 2 separate computers it just starts the update restarts my 7500 then the error message about USB connection. I didnt get this error the last 2 times I updated my device. Thanks in advance.
Taking it your pc (Windows XP) with anti virus and firewall disable.
Try flash back previous rom and have the device working first before going
any further.
Best to use same usb cable and port from same computer for your flashing. It helps to isolate problems in future.
Ensure device battery charge is above 60%, at least.
Remove SIM and memory cards before flashing.
I am sorry to hear that you're having problems with your device......however, the problem you've mentioned sounds quite familiar to me but I don't remember how I actually got mine fixed.
I have no idea what OS you're using but
try this:
re-installing activesync/device center then put your device in bootload mode (by holding down the camera button...fully....then press the reset button, keep holding camea button until the colored screen comes up. connect your phone to your computer and let it install the usb drivers.
after thats done, unplug, wait....replug and start up acticesync/device center make sure they're connected/synced then try changing the rom again.
hope that helps.
Thank you all so much. I did these things and it still restarts and goes right back in mobile 6.5 giving that same error message #260 box comes up that says the update utility cannot connect to your PDA phone. Please check your USB connection. Can it be a bad usb cable I'm using I wonder? Interesting my SPL version right now is 1.10.
that's the problem...your SPL should be 3.5 if you're on wm6.5. it is interesting that you got that instead of "invalid Model id" error. all in all I think the same method should solve your problem.
do a search for "invalid model id" and check out the post by cmonex she did a great job in creating a salutation. hopefully you had Hard SPLed your phone and that you had a home network that you had connected your phone so you can get back your phone's MAC address.
EDIT:
Also change your USB cable....I don't trust it, it's possible that it could be the problem. however, seen as your SPL isn't what it should be it the cable is not the problem (but change it anyway)
lennie said:
that's the problem...your SPL should be 3.5 if you're on wm6.5. it is interesting that you got that instead of "invalid Model id" error. all in all I think the same method should solve your problem.
do a search for "invalid model id" and check out the post by cmonex she did a great job in creating a salutation. hopefully you had Hard SPLed your phone and that you had a home network that you had connected your phone so you can get back your phone's MAC address.
EDIT:
Also change your USB cable....I don't trust it, it's possible that it could be the problem. however, seen as your SPL isn't what it should be it the cable is not the problem (but change it anyway)
Click to expand...
Click to collapse
Thanks so much! I will do this. I wonder why I have a spl 1.10? This is confusing with Win Mobile 6.5?
lennie said:
that's the problem...your SPL should be 3.5 if you're on wm6.5. it is interesting that you got that instead of "invalid Model id" error. all in all I think the same method should solve your problem.
do a search for "invalid model id" and check out the post by cmonex she did a great job in creating a salutation. hopefully you had Hard SPLed your phone and that you had a home network that you had connected your phone so you can get back your phone's MAC address.
EDIT:
Also change your USB cable....I don't trust it, it's possible that it could be the problem. however, seen as your SPL isn't what it should be it the cable is not the problem (but change it anyway)
Click to expand...
Click to collapse
I am using a new usb cable and the same thing happens. It says its starting to update the rom then it restarts my 7500 and error 260 comes up saying that it cannot connect to my device check your usb connection. I don't understand...
Hey guys...sorry if this has been covered. I tried searching the forums and can't seem to find anything on it.
All of the roms seem to be plug it in, install it and BLAM, you're ready to go.
My issue is that I get a communication error everytime I try to install any roms or the HardSPL. The exact error given is "The ROM Update Utility has encountered communication errors during the update process. The program will guide you step-by-step to recover from the error so you can continue with the update."
While performing the updates, I hear the sound as if my USB disconnects, then it reconnects after it restarts into the multi-colored screen. It shows "Security disabled" at the top of the screen. It proceeds to the loading bar and just sits at 0% until it comes up with the disconnect screen.
I'm using the HTC Touch Pro running WM6.1 on the Sprint network.
Again, sorry if this has already been discussed, I just couldn't find anything on it.
rceubanks said:
Hey guys...sorry if this has been covered. I tried searching the forums and can't seem to find anything on it.
All of the roms seem to be plug it in, install it and BLAM, you're ready to go.
My issue is that I get a communication error everytime I try to install any roms or the HardSPL. The exact error given is "The ROM Update Utility has encountered communication errors during the update process. The program will guide you step-by-step to recover from the error so you can continue with the update."
While performing the updates, I hear the sound as if my USB disconnects, then it reconnects after it restarts into the multi-colored screen. It shows "Security disabled" at the top of the screen. It proceeds to the loading bar and just sits at 0% until it comes up with the disconnect screen.
I'm using the HTC Touch Pro running WM6.1 on the Sprint network.
Again, sorry if this has already been discussed, I just couldn't find anything on it.
Click to expand...
Click to collapse
Your phone's cdma. This is a gsm forum. I'm assuming that you're trying to brick your phone with the gsm hard spl and not trying to flash the proper hard spl. Stop doing that, your phone is getting pissed at you. Go to ppcgeeks or the cdma (Herman, not Raphael) forum here.
haha leave it to me to find the wrong way to do something. I appreciate your heads up Ted!
rceubanks said:
Hey guys...sorry if this has been covered. I tried searching the forums and can't seem to find anything on it.
All of the roms seem to be plug it in, install it and BLAM, you're ready to go.
My issue is that I get a communication error everytime I try to install any roms or the HardSPL. The exact error given is "The ROM Update Utility has encountered communication errors during the update process. The program will guide you step-by-step to recover from the error so you can continue with the update."
While performing the updates, I hear the sound as if my USB disconnects, then it reconnects after it restarts into the multi-colored screen. It shows "Security disabled" at the top of the screen. It proceeds to the loading bar and just sits at 0% until it comes up with the disconnect screen.
I'm using the HTC Touch Pro running WM6.1 on the Sprint network.
Again, sorry if this has already been discussed, I just couldn't find anything on it.
Click to expand...
Click to collapse
Try here: CDMA Herman
same issue on GSM phone
Hi I have the same problem on a GSM phone.
I get the updating bar on my phone- it stays stuck at 0%.
then a communications error
Thanks in Advance
What is the problem with the RUU update?
I have searched for a solution to the RUU update/upgrade problem; none so far. Apparently, it is a major issue. I am interested in upgrading my Windows CE on my Xperia 6.1 to 6.5. I must have tried over a dozen times. The update process stops at 0% and Error [262] is reported. What can we do to resolve this? Is it compatibility or scalability issue? is it a problem with the software? The fact that it is working for some . . . and not for others is a source of concern about the stability of the software and this has potential implications; or it may well have to do with the hardware limitations of the PDA. Any ideas of a workaround?
You might try the Experia forum. You also might want to try Experia Roms.
I used to experience this issue as well. I simply go into communications and hit the USB to PC connection. Then remove the advanced functionality check. This has resolved many of the communication errors when playing with ROMS. This has been true with both GSM and CDMA devices.
I can confirm the issue. I have a 1st day release Fuze and flashed HardSPL no problem and have been making my roms ever since. But my cousin just got his new AT&T Fuze through his company and it refuses to HardSPL.
I went through several versions of the HardSPL and tried installing new drivers for the phone while in bootmode... all with no luck.
When connected through Activesync or Mobile Center, running the HardSPL brings up a confirmation windows on the phone, allowing reboots the device. It gets stuck at the black screen and times out. I've tried manually putting the phone in bootmode and trying it, but never gets past 0%.
I wonder if newer model TouchPro's are coming out with a revised bootloader?
Dunno if i can link to another forum. If not, appolgize and Admins remove the link than please.
For the 262 error, look here:
http://www.4winmobile.com/forums/windows-mobile-faq/13329-ruu-errors.html
player911 said:
I can confirm the issue. I have a 1st day release Fuze and flashed HardSPL no problem and have been making my roms ever since. But my cousin just got his new AT&T Fuze through his company and it refuses to HardSPL.
I went through several versions of the HardSPL and tried installing new drivers for the phone while in bootmode... all with no luck.
When connected through Activesync or Mobile Center, running the HardSPL brings up a confirmation windows on the phone, allowing reboots the device. It gets stuck at the black screen and times out. I've tried manually putting the phone in bootmode and trying it, but never gets past 0%.
I wonder if newer model TouchPro's are coming out with a revised bootloader?
Click to expand...
Click to collapse
Yes they are coming with a new bootloader. I just got my phone replaced from ATT and the new one came with 1.95 version while originals were 1.90. There is no HARD-SPL out for 1.95.
The way to do it now is to flash an old original AT&T rom with the 1.90 bootloader (since it's original, it won't require HardSPL). Then go ahead and everything should work as described in this forum/wiki.
Interseting. Sounds like a winner. Next time he comes around I'll try this.
Any idea where I can get a AT&T older rom that has the 1.90 HardSLP on it? I am having the same issue with the Error 262 update error.
Thanks
smicale said:
Any idea where I can get a AT&T older rom that has the 1.90 HardSLP on it? I am having the same issue with the Error 262 update error.
Thanks
Click to expand...
Click to collapse
You should probably go to your ATT store and tell them you'd like to get the official Hard SPL update.
I am really struggling with this. Do I have to the FLASH HardSPL or can I just go straight to the flashing my preferred ROM. I can not get get the FLASH HardSPL to work because of this Error 262. Please someone tell me where I am going wrong with this!!!! I am bout to pull my last hair out!
smicale said:
I am really struggling with this. Do I have to the FLASH HardSPL or can I just go straight to the flashing my preferred ROM. I can not get get the FLASH HardSPL to work because of this Error 262. Please someone tell me where I am going wrong with this!!!! I am bout to pull my last hair out!
Click to expand...
Click to collapse
If u want to use not the official rom made for ur provider and phone, hardspl is the only way. Any custom rom needs hardspl. Otherwise ur phone will not accept the rom.
But look here http://forum.xda-developers.com/showthread.php?t=410150
and flash the stock 1.90 SPL first, then u are ready for hardspl.
Description how to do stock spl is in this thread. Its normally meant for going back to stock for repair, but it should also solve ur issue.
NOT SHURE BECAUSE IN THE CDMA SECTION, IS UR PHONE CDMA OR GSM. MY SOLUTIUON IS FOR GSM !!!!!!
U SHOULD CHANGE THE POSTING SECTION IF ITS GSM !!!!!
Try doing the HardSPL in a Windows XP machine (needs .NET Framework 2.0 and ActiveSync). Goodluck.
i had the same problem as you and i maybe have a solution for you
go to your usb settings and look if you have a check box saying something about advanced networking. if it is indeed checked uncheck it and your problem will be gone hopefully
i did it on my telus touch pro and i am now able to upgrade my phone to winmo 6.5
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.