Hi all,
I tried to flash my phone this morning with pretty bad results. For some reason it stopped during the flashing, giving me a 260 Error, and now I can only get to the boot loader.
This is what's currently displayed:
DIAM100 MFG 64M
SPL-1.40.OliNex
MicroP-Diam (LED) v11
PSOC-Diam STAGE_PVT v0x30
Upgrade ROM code error
Please try again
Now, some times when I connect the phone I will get it to register and the text on the display changes from "Serial" to "USB". Most of the time, however, I get an unknown device in Windows and it stays at Serial. I have the most luck when I leave the battery out for extended periods, and even better if I have a fresh reboot on my computer.
When I do get it to register properly in Windows I can upgrade the SSPL, but the boot loader doesn't reflect the new version (tried to "upgrade" to 1.93) even though it reaches 100%, says congrats, and the phone reboots. After that, however, I do not get straight into the boot loader any more.
The most luck I've had with an image is Shine On 2.4l, which got to 85% before stopping :S
I'm running Vista x64 on both my computers, and I've tried on both of them to be sure - same symptoms. The phone was first flashed right after it came on the marked, so I know it used to work.
Anyone got an idea on what to do?
I'm missing my phone...
1: try flashing on winXP
2: use another miniusb cord
SSPL? Definitely not for the diamond.
But yes, try returning to stock SPL and reflashing hard spl.
Related
Hi,
I download the new rom from http://www.htc.com/www/SupportDownload.aspx?p_id=133&cat=2&dl_id=483 but after upgrading rom the utility says:
Code:
ERROR [270]: UPDATE EROR.
The image file is corrupted. Please check your Update Utility.
I re-download couple of times and re-upgrade but always the same...
The 4 Coloured screen has some text on it:
Code:
DIAM100 64M
SPL-1.93.OliNex
MicroP-Diam (LED) v11
PSOC-Diam STAGE_PVT v0x30
Upgrade ROM code error
Please try again
Before the new official rom i have another cooked rom as you can see i have Olinex Hard-SPL...
Can someone help me about this? I have bootloader screen (4 coloured screen) but after trying times and times always the same. After completing the %100 the error occurs...
Code:
ERROR [270]: UPDATE EROR.
The image file is corrupted. Please check your Update Utility.
hmelihkara said:
Hi,
I download the new rom from http://www.htc.com/www/SupportDownload.aspx?p_id=133&cat=2&dl_id=483 but after upgrading rom the utility says:
Code:
ERROR [270]: UPDATE EROR.
The image file is corrupted. Please check your Update Utility.
I re-download couple of times and re-upgrade but always the same...
The 4 Coloured screen has some text on it:
Code:
DIAM100 64M
SPL-1.93.OliNex
MicroP-Diam (LED) v11
PSOC-Diam STAGE_PVT v0x30
Upgrade ROM code error
Please try again
Before the new official rom i have another cooked rom as you can see i have Olinex Hard-SPL...
Can someone help me about this? I have bootloader screen (4 coloured screen) but after trying times and times always the same. After completing the %100 the error occurs...
Code:
ERROR [270]: UPDATE EROR.
The image file is corrupted. Please check your Update Utility.
Click to expand...
Click to collapse
The new official rom's appear to be flashable only by using the "flash from internal storage card" method, so just search out those words & you shall find all info/ tut's on doing it m8
polllux said:
The new official rom's appear to be flashable only by using the "flash from internal storage card" method, so just search out those words & you shall find all info/ tut's on doing it m8
Click to expand...
Click to collapse
Or unzip the exe file and flash the .nbh file with udK.s Custom RUU
just start bootloader mode (reset and keep vol down till the tricolor appears.)
u'll see "serial" written on the bottom of the screen, just connect your diamond to the pc till "USB" appears instead of "serial".
now just follow the method that omaga mentioned erlier.
it's as easy
good luck!
doesn't work either way. i got the same error when i tried flashing the new rom. it doesn't work with the custom RUU, i gave up and flashed another one before trying to flash from storage.
my advice is to flash an older official ROM and try the flash from internal storage solution or try a cooked rom
I had exact the same problem. Tried twice to install the official but sith no luck.
Got bored and Installed Duttys.
Did not try the flash from card though.
Don't worry - when it happened to me I was scary too that I bricked phone- it's not bricked.To make it work just reflash your HARDSPL once again on that tree color screen use olinex 1.40 or 1,93. After that this rom starts working you don't have to reflash it again. I flashed this rom twice and always in the end it trows error bla bla bla . Reflash HARDSPL and it works with no problem even if you do HR.
Cheers guys
thanks friends, i install Dutty's last version (so i need at least one working system).
But i still want to upgrade to latest official, and don't know hot to do that safely?
pegaz: did u re-hardspl after new official rom or u'r talking about any rom suitable ?
Thanks.....
worked for me too.
hmelihkara said:
thanks friends, i install Dutty's last version (so i need at least one working system).
But i still want to upgrade to latest official, and don't know hot to do that safely?
pegaz: did u re-hardspl after new official rom or u'r talking about any rom suitable ?
Click to expand...
Click to collapse
this problem you're talking about happened ONLY with this official HTC SHIPPED 2.03 version. Any other rom's doesn't cause any problems such like that above
omaga said:
Or unzip the exe file and flash the .nbh file with udK.s Custom RUU
Click to expand...
Click to collapse
And put your phone in bootloader mode manualy.
Volume down + hold reset button down for a while= 4 colour mode should appear, wait for "serial" change to "usb" just as seatone posted before
Done this with all my previous HTC devices (bt-mode manually)= Problems with flash? 0 times
and a second very importent tip is that Read every thing about flashing the phone before doing it
Ok i just did this update and it did the same thing =( I got the same error and it doesn't seem to work. I did this upgrade from a 1.35 HTC ROM upgrade so it was stock all the way. What can I do to fix this? It's a UK phone and I live in Canada so I downloaded the US one when it asked where I live nearest to. Did I make a booboo?
Ok I did it a third time and it worked =\
Anyone find that the alarm clock function doesn't work? Even if it did like before, it doesn't go off when the phone is off which sucks! My older phones do!
just sharing = i've tried to update te new room 2.03.401.2 and got the same error as you(The image file is corrupted, 270)
Well i, tried to reflash with the same room and again got the same error. Then i downgrade to my previous room, in case 1.93, after did it i reflash hardspl olenix 1.93 ( cause i did not have it before). Done, i was completely safe again.
I did not give up and, again tried to flash the 2.03.401.2 official, but this time from the from the internal storage. Guided by this tuto = http://forum.xda-developers.com/showpost.php?p=2707841&postcount=4035
THATS IT, ITS TO EASY, First i thought it would be so hard, but the procedure its easy a lot.
SPECS @OFFCIAL Diamond_HTC_Europe_2.03.401.2_Radio_Signed_Diamond_52.51.25.26_1.09.25.23_Ship
The touchflo3d is VERY VERY VERY FASTER, as much as you/me/we/us thought. It also has included automatic regional settings from brazil, which before does not. It's to soon to tell more specs about it but i've soon until now its just great.
TNX GUYS, AND I HOPE HELPED.
Answer from HTC
This is the official answer to our problem about failed upgrade:
New Response From [ Edyta (Europe Support (Tech)) ]
Good Afternoon, Thank you for contacting HTC Europe. The www.htc.com Support site has not been working correctly on the day you tried to download the update, please try downloading the software for your device again. We apologize for any inconvenience.
yeah you are right, the site does not work properly since yesterday
Upgrade ROM code error
Please help me!!!!..I tried to upgrade also my diamond with the latest ROM released by HTC with SPL-1.40.olinex but after it reached 100%, the screen stays in tri color boot mode saying "Upgrade ROM code error please try again". What will I do now?...please help me!!!!
i dont know if this will work here but it worked for me when i flashed the wrong radio and got stuck in bootloader and couldnt get my phone to connect with my computer
http://forum.xda-developers.com/showpost.php?p=2420949&postcount=11
enriqueluis said:
Please help me!!!!..I tried to upgrade also my diamond with the latest ROM released by HTC with SPL-1.40.olinex but after it reached 100%, the screen stays in tri color boot mode saying "Upgrade ROM code error please try again". What will I do now?...please help me!!!!
Click to expand...
Click to collapse
I had the same problem yesterday.
So I just rebooted & installed the rom I had previously been using (latest official french one).
Then I followed the instructions for doing a flash from the internal storage :
Originally Posted by Teppic24 View Post
There is a problem installing these ROMs via an Activesync connection, which gives the "image file is corrupted" message. You need to flash from Internal Storage. Also, make sure you have HardSPL installed before you flash.
Instructions for flashing from internal storage:
Extract the RUU_Diamond_HTC_Europe_2.03.401.2_Radio_Signed_Dia mond_52.51.25.26_1.09.25.23_Ship.exe file (or whatever one you are wanting to flash) to a new directory on your PC
Find the RUU_signed.nbh file in this new directory and rename it to Diamimg.nbh
Copy Diamimg.nbh to the root of Internal Storage
Hold in the volume down button + the back button (thats the top right button on the front to the right of the big middle jog control) + soft reset
Follow instructions on screen
When the process is complete (it will say UPDATE SUCCESS) then reset
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=471699&page=8
Everything worked fine.
I also had changed the hspl to HSPL OliNex 1.93 as the phone came with a crappy operater ROM.
At first when the phone gets stuck in the tricolour band mode I thought I wouldn't be able to connect to the pc (no active sync) but at the base of the tri-colour bands you'll see 'USB' if your cable is connected ('SERIAL' if not), & then there's no problem executing the ROM installation.
So put the ROM you had before, then once done, follow the instructions from the quoted text above. It'll work & you'll breathe a sigh of relief.
Here's a decent explanation (visual) of how to do a hard reset : btw, hard reset clearly explained for newbies (such as me)
http://www.hardreset.eu/htc_touch_diamond_hard_reset_soft_reset_en.html
I'm having the same problem after unsuccesful update I'm getting 4 coloured screen with messege:
DIAM100 MGF 64M
SPL-1.24. Hard
MicroP-Diam (LED) v11
PSOC-Diam STAGE_PVT v0x32
Upgrade ROM code error
Please try again
Click to expand...
Click to collapse
Any solutions?, I'v tried already above with no success.
just flash with an older rom & once it's flashed follow the instructions on doing a flash from internal storage.
I have a major issue here. Please bear with me.
I flash my phone to the official 6.1 rom a few months back. Now I recently decided to try a custom rom by NFSFAN. So first thing was to flash the bootloader by IMCokeMan version 0.41. After doing that I flashed the custom rom. Once it booted up my phone kept reboot itself every few seconds or so. It turns out now that it was a battery issue, but I was sure the battery was fine and thought it was simply an incompatibility issue with the rom.
So I then tried to flash the official 6.1 rom back on, but it froze at 44% and then threw a 262 error after a minute or so. I then learned that I needed to flash the IMCokeMan 0.40 unlocker/relocker to get the official rom back on. So I did. Then tried the official rom again, and lone behold, froze at 44% and then gives the 262 error.
Then I thought I'd try the NFSFAN's rom again. So I flashed that. Once it successfully finished and started to load it freezes at the Telus splash screen and "No Radio" appears in red on the screen.
So this is where I'm at. I've tried to flash nearly every bootloader I could find and no matter what I do the bootloader always shows "SPL-0.41.coke". I can't flash any official rom including Telus, Bell or Sprint as they each freeze at different spots but consistently at the same spot individually (Telus at 44%, Bell at 30-some%, Sprint at 29%). I can flash custom roms as well as the beta wm6.5 rom but those don't fully load and give the "No Radio" error.
The ONLY rom I can successfully flash is an old 6.0 rom that someone dumped from a telus vogue. But in this rom under "Device Information" the rom is 1.11.661.1 and the radio version field is blank! And I cannot make data connections, as in I cannot connect to the internet, etc.
So my question to anyone that may know is: why am I having these issues with the radio version? How can I get rid of the SPL-0.41.coke bootloader?
And what can I do at this point? Any help from anyone is a thousand times over appreciated!
There's another copy of this thread at PPCGeeks.com:
http://forum.ppcgeeks.com/showthread.php?p=792095#post792095
-Chris
*********** bump-a-doo? *************
eeps! similar issue! did I brick it???
My symptoms are different, but the way I got there is pretty much the same:
I wanted to try NFSFAN's 1.28 Bell rom, so I unlocked with IMCokeMan's 2.31 unlocker (2.31 instead of 0.41 because I had previously upgraded to UTStarcom's Bell WM6.1 rom with the 3.42.50 radio when it came out). The unlock process went smoothly, and I had no problem flashing NFSFAN's 1.28 rom after that either.
NSFAN's RUU said I was successful, and my Vogue automatically restarted but got hung up on the "Bell" splash screen, I tried to let it work itself out for over 15 minutes before I tried a reset, but it still had the same problem. Tried a hard reset: same problem. I let it sit connected to the charger for a half week now and it still is hung at the "Bell" splash screen.
I'd try to flash the stock rom again, but I can't get the RUU to work without an activesync connection (right?).
Did I brick it? Any advice would be appreciated.
Here's everything my version-screen says if it helps at all:
M 03
B 01
P DCAAXOM-4350H
R 3.42.50
D 3NFS (is that NFSFAN's rom or an error?)
cbstryker said:
I then learned that I needed to flash the IMCokeMan 0.40 unlocker/relocker to get the official rom back on. So I did. Then tried the official rom again, and lone behold, froze at 44% and then gives the 262 error.
Click to expand...
Click to collapse
I've been reading through the ImCoKeMaN's unlocker sticky (http://forum.ppcgeeks.com/showthread.php?t=20370), and I noticed there is a "VERY IMPORTANT / Warning" referring to the 0.40 rom you used. Here's what it says:
If your carrier did not release a rom and you flash an exe of another carrier with the 0.40 unlocker you won't be able to flash ANY rom until unlocking again (this requires booting into WM)
Click to expand...
Click to collapse
then it points to this: ftp://up.ppcgeeks.com/Vogue/Users/ImCoKeMaN/Vogue_unlocker.exe
Hopefully that helps you out.
esskay said:
My symptoms are different, but the way I got there is pretty much the same:
I wanted to try NFSFAN's 1.28 Bell rom, so I unlocked with IMCokeMan's 2.31 unlocker (2.31 instead of 0.41 because I had previously upgraded to UTStarcom's Bell WM6.1 rom with the 3.42.50 radio when it came out). The unlock process went smoothly, and I had no problem flashing NFSFAN's 1.28 rom after that either.
NSFAN's RUU said I was successful, and my Vogue automatically restarted but got hung up on the "Bell" splash screen, I tried to let it work itself out for over 15 minutes before I tried a reset, but it still had the same problem. Tried a hard reset: same problem. I let it sit connected to the charger for a half week now and it still is hung at the "Bell" splash screen.
I'd try to flash the stock rom again, but I can't get the RUU to work without an activesync connection (right?).
Did I brick it? Any advice would be appreciated.
Here's everything my version-screen says if it helps at all:
M 03
B 01
P DCAAXOM-4350H
R 3.42.50
D 3NFS (is that NFSFAN's rom or an error?)
Click to expand...
Click to collapse
hey, I answered this question of yours already over here http://forum.xda-developers.com/showthread.php?p=3526872#post3526872
Detroit Doug
Thats the problem im having theres no way I know to get passed that screen that says no radio. So you can't even get into WM. So since it cant load into WM you can't run the unlocker. Most custom roms flash fine but its the radio thats missing it wont go past that.
Viper Matrix Wireless said:
Thats the problem im having theres no way I know to get passed that screen that says no radio. So you can't even get into WM. So since it cant load into WM you can't run the unlocker. Most custom roms flash fine but its the radio thats missing it wont go past that.
Click to expand...
Click to collapse
You do NOT need to be in WM to unlock, WM has nothing to do with it
Start phone in bootloader mode (power+camera+stylus in reset hole and hold this until the 3 color screen comes up) it will say serial at the bottom
Plug in the USB cable to your PC and it will change to say USB
Start the 2.31 Unlocker RUU.EXE (RomUpdateUtility.exe) file, follow the steps
then run your custom ROM when after it restarts do does it thing and reboots again by going back into bootloader mode and doubleclicking the RUU.exe file in the custom ROM folder you want to use
Once it runs through the setup after flashing and then the autorun and restarts - hard reset the phone (red+green+stylus in hole) until a gray screen comes up
Follow directions and then setup and autorun and reboot
Make sure you have a carrier cab and/or mms fix either on your PC to copy over to your phone or on your SD Card ahead of time and you should be set to go
Detroit Doug
Detroit_Doug said:
You do NOT need to be in WM to unlock, WM has nothing to do with it
Start phone in bootloader mode (power+camera+stylus in reset hole and hold this until the 3 color screen comes up) it will say serial at the bottom
Plug in the USB cable to your PC and it will change to say USB
Start the 2.31 Unlocker RUU.EXE (RomUpdateUtility.exe) file, follow the steps
then run your custom ROM when after it restarts do does it thing and reboots again by going back into bootloader mode and doubleclicking the RUU.exe file in the custom ROM folder you want to use
Once it runs through the setup after flashing and then the autorun and restarts - hard reset the phone (red+green+stylus in hole) until a gray screen comes up
Follow directions and then setup and autorun and reboot
Make sure you have a carrier cab and/or mms fix either on your PC to copy over to your phone or on your SD Card ahead of time and you should be set to go
Detroit Doug
Click to expand...
Click to collapse
I answered his question on his thread. You forgot one thing though Doug. He doesn't have a radio. He'll need to flash back to stock before he flashes a custom. Doesn't this get frustrating???
Dear Sir
My diamond got stuck up at the welcome screen or else in the alignment screen. I've flashed many roms number of times before but this time this happened after a hard reset- using Macadam 1.2 (latest).
My bootloader reads - Diam140 MFG 64M; SPL-1.40. Olinex. After this I've flashed back to the latest indian stock rom i.e. First to (RUU_Diamond_hTC_Asia_India_1.93.720.4_Radio_Signed_Diamond_52.62.25.34_1.13.25.24_ShiP) but know result & (RUU_Diamond_hTC_Asia_India_1.93.720.2_Radio_Signed_Diamond_52.29.25.12_1.00.25.07_Ship_R). After going through the forums- I understood that I've to step down to stock spl. But even after successful flashing, the boot loader shows the same- "SPL-1.40.OliNex".
I'm unable to use the jump SPL, because I can't pass through the alignment screen. Please help, is there any way to JUMP SPL without operating the phone.
Or else how can I come back to the stock spl.
Please Help.........................
Regards
Furthermore, I've tried using mtty to following the procedure:
Correct sequence is as follows:-
1. Launch ActiveSync on PC
2. Go to connection settings
3. Uncheck the Allow USB Connection
4. bring the device to bootloader. AND connect to the PC.
5. Now, run mtty1_1_.42_538 on PC.
6. CMD>task 29
7. Flash the ROM of your choice
Then flashed the stock rom again. But the problem remained.
jockyw2001 - suggested me on PM to do- "in mtty: set 16 0 then reboot'- but nothing happened. Or I didn't follow the correct steps... can anyone explain & help please....
[UPDATE]where do I get the commands for mtty
Can anyone tell me the link where I can get the commands to be used in mtty... Is there anyway to bypass the screen alignment part during start up after a hard reset.... how can I JumpSPL in a handset where the touch screen is not working.. but the screen is not completely dead, i.e. on tapping the "+" sign is moving after around 5 or 7 mins of the tap...
Please help guys.... I'm waiting to be rescued by some WM wizard from this great community.....
Regards
wizards- all'r failing or what- very few people with clear funda
cmonex please help....
hi man
i had the same problem, with all the rom around
than i understand that the problem was the radio rom
try to flash the lastest radio..i use the 1.13
Flash a Rom without screen alignment
Hi
If you on bootloader and you have 1.40olinex then flash a 1.13 radio then flash a Rom without Screen alignment process. It might help. Good luck
Hi all
OK, my screen alignment on HD is so messed up i went to downgrade my HD HTC (1.56 Olinex -W6.5Miri) back to its original Orange SPL and OS so i can send it back to HTC under warranty.
Foolishly I changed the HSPL first to original stock so it is now a SPL 1.14.000 (no olinex or anything) in bootloader.
I went to then flash ROM to latest Orange HTC OS release from xda (compatible with that SPL) and just got the 262 error.
So, I have a big problem...
1. I cannot flash any ROM - error 262 problem
2. I cannot cook a new HSPL in any way - error 262 problem
3. Ive got green screen and cannot in anyway load SSPL-Manual-TouchHD.zip and then run it (which normally fixes the 262 error)
4. Ive got green screen so my phone doesnt work
5. tried hard reset - now hangs on loading new OS in green screen
Is it bricked? Is there any software I can use to force load HSPL? I figure my aim is to get the phone back to 1.56 / W6.5 and start over again.
Very curious to see if folk out there have any ideas...
Cheers in advance
in addition
am using W7 on pc and have updated drivers for bootloader usb sync
EDIT: I have now moved this post to Blackstone/Blackstone/ thread.
http://forum.xda-developers.com/showthread.php?t=564409&highlight=bricked
Hi
I had my S620 aside, haven't used for 3 years.
Now I'm trying to give it to a friend and i need to put a Portuguese rom on it.
I know I've change the stock rom to the 3VO.2.80.092509 and now I want to flash the official portuguese rom.
I've downloaded it (RUU_Excalibur_BRIGHTSTAR_PTB_1.30.514.2_4.1.13.47_02.98.90_Ship Extract) from official rom's page but when I try to flash it, it gives me the Error [244]: Invalid model ID, at 3%.
Well, the rom is for Excalibur, i flashed a rom before long time ago, do i need to update the HSPL ?
What am i doing wrong?
Thks for your help.
Regards
My Excalibur especifications:
On Bootloader
Excalibur
ONBL 1.30.0000
SPL 1.30.0000
Windows Mobile 6.5
OS: CE OS 5.2.23004 (build 23005.5.3.0)
ROM: 3VO.2.80.092509
Radio version: 4.1.13.47_02.98.90
read carefully
i overclock mine and i solve it. go to windows mobile center and disable usb connection. press and hold sym while pluging in usb( this will take you to bootloader mode) and run uspl from the cid bypass after that run the original rom. if it does work go back to stock rom and run cid bypass and ru the rom you metion.
http://forum.xda-developers.com/showthread.php?t=329605
http://forum.xda-developers.com/showthread.php?t=328690&highlight=cid
XicoBombas said:
Hi
I had my S620 aside, haven't used for 3 years.
Now I'm trying to give it to a friend and i need to put a Portuguese rom on it.
I know I've change the stock rom to the 3VO.2.80.092509 and now I want to flash the official portuguese rom.
I've downloaded it (RUU_Excalibur_BRIGHTSTAR_PTB_1.30.514.2_4.1.13.47_02.98.90_Ship Extract) from official rom's page but when I try to flash it, it gives me the Error [244]: Invalid model ID, at 3%.
Well, the rom is for Excalibur, i flashed a rom before long time ago, do i need to update the HSPL ?
What am i doing wrong?
Thks for your help.
Regards
My Excalibur especifications:
On Bootloader
Excalibur
ONBL 1.30.0000
SPL 1.30.0000
Windows Mobile 6.5
OS: CE OS 5.2.23004 (build 23005.5.3.0)
ROM: 3VO.2.80.092509
Radio version: 4.1.13.47_02.98.90
Click to expand...
Click to collapse
so weird
Ratchewer said:
i overclock mine and i solve it. go to windows mobile center and disable usb connection. press and hold sym while pluging in usb( this will take you to bootloader mode) and run uspl from the cid bypass after that run the original rom. if it does work go back to stock rom and run cid bypass and ru the rom you metion.
http://forum.xda-developers.com/showthread.php?t=329605
http://forum.xda-developers.com/showthread.php?t=328690&highlight=cid
Click to expand...
Click to collapse
Hi
I did what you've told, ran uspl from cid paypass, all good till the screen stayed almost white.
When i tried to install PTB stock rom the flasing frooze at 0%.
Had to unplug the usb cable, and now each time i turn on the pda it goes to bootloader mode everytime.
Tried to flash through sd card all the stock roms i found without success. All the attempts through usb cable didnt passed 0%.
It starts to check the sd contents but then goes straight away to 3 colour bootloader mode without doing anything.
Then i remembered i had to install the original stock rom, which was the BT brand, that i found yesterday.
Now comes the weird part.
First time i try to flash the BT brand rom, it installed the rom (i didnt quite saw the whole process), and when it restarted it self, went again to bootloader mode.
Tried hardreset, tried to flash again, it goes straight to bootloader.
What the hell is going on???????
In my whole flashing history, i had 100% success over 50 flashes, and now its freaking weird.
Can you lead me again?
Thanks for everything.
Greetings
Try this here
ok go back to the original phone stock rom from the service provider and start over. use the usb bootloader mode after run the xda applicationunlocker file and do the cid bypas. then run the utilityupdate from the other rom ( not the one in the cid bypas file in the link) meaning do not click yes to the windows security prompt skip and run the romm u want to use
XicoBombas said:
Hi
I did what you've told, ran uspl from cid paypass, all good till the screen stayed almost white.
When i tried to install PTB stock rom the flasing frooze at 0%.
Had to unplug the usb cable, and now each time i turn on the pda it goes to bootloader mode everytime.
Tried to flash through sd card all the stock roms i found without success. All the attempts through usb cable didnt passed 0%.
It starts to check the sd contents but then goes straight away to 3 colour bootloader mode without doing anything.
Then i remembered i had to install the original stock rom, which was the BT brand, that i found yesterday.
Now comes the weird part.
First time i try to flash the BT brand rom, it installed the rom (i didnt quite saw the whole process), and when it restarted it self, went again to bootloader mode.
Tried hardreset, tried to flash again, it goes straight to bootloader.
What the hell is going on???????
In my whole flashing history, i had 100% success over 50 flashes, and now its freaking weird.
Can you lead me again?
Thanks for everything.
Greetings
Click to expand...
Click to collapse