*SOLVED* THANKS EVERYONE!!
I rooted using this guide: hXXp://wiki.cyanogenmod.cXX/index.php?title=Full_Update_Guide_-_Rogers_Dream_911_Patched
Got danger SPL using this: wiki.cyanogenmod.cXX/index.php?title=DreamangerSPL
and installed cyanogenmod using this: hXXp://wiki.cyanogenmod.cXX/index.php?title=Dream:Installing_CyanogenMod_5%2B
The phone boots into cyanogen fine, I can use market and everything. The problem happens whenever I reboot. It will not boot back into cyanogen, stuck on Rogers screen. If I do a factory reset through amons recovery I can boot again but not reboot. I have tried wiping through fastboot, using wipedatacachesystem.zip and both in combination before flashing update-cm-6.0.0-DS-signed, bc-6.0.0-ebi1-signed, and gapps-mdpi-tiny-20100917-signed (in that order). I have also tried flashing without gapps to no avail.
I have also tried CyanogenMod 5.0.8-DS and same issue.
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA21000)
CPLD-4
RADIO-3.22.26.17
APR 20 2009, 15:30:43
Some trouble shooting help would be delightful!
coolloser said:
I rooted using this guide: hXXp://wiki.cyanogenmod.cXX/index.php?title=Full_Update_Guide_-_Rogers_Dream_911_Patched
Got danger SPL using this: wiki.cyanogenmod.cXX/index.php?title=DreamangerSPL
and installed cyanogenmod using this: hXXp://wiki.cyanogenmod.cXX/index.php?title=Dream:Installing_CyanogenMod_5%2B
The phone boots into cyanogen fine, I can use market and everything. The problem happens whenever I reboot. It will not boot back into cyanogen, stuck on Rogers screen. If I do a factory reset through amons recovery I can boot again but not reboot. I have tried wiping through fastboot, using wipedatacachesystem.zip and both in combination before flashing update-cm-6.0.0-DS-signed, bc-6.0.0-ebi1-signed, and gapps-mdpi-tiny-20100917-signed (in that order). I have also tried flashing without gapps to no avail.
I have also tried CyanogenMod 5.0.8-DS and same issue.
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA21000)
CPLD-4
RADIO-3.22.26.17
APR 20 2009, 15:30:43
Some trouble shooting help would be delightful!
Click to expand...
Click to collapse
Your radio is for 32A devices while it says 32B at the top. Maybe flashing the 32B radio will help. I can't guarantee that it'll work though..
I never flashed the radio...hmmm
Where would I find a compatible radio?
update
I've flash back to stock 1.5 and it will restart....starting again now
koreancanuck said:
your radio is for 32a devices while it says 32b at the top. Maybe flashing the 32b radio will help. I can't guarantee that it'll work though..
Click to expand...
Click to collapse
noooooooooooo
hopefully he sees my post before he bricks his phone...
@asb123
I haven't flashed a radio...I flash back to stock and am starting again. I (she) haven't done anything yet....do you have advice what steps I should take?
now my hboot says this
DREAM PVT 32B SHIP S-ON d
HBOOT-1.33.0009 (DREA21000)
CPLD-4
RADIO-3.22.20.17
MAY 12 2009, 17:05:58
(Running stock 1.5)
this happened to me before, hopefully its the same problem. what worked for me was wiping dalvik cache after you install the rom and reboot.
haven't tried that
Thanks for a sensible solution, that sounds like it should work. I will report back tomorrow with results.
It's my sisters phone and she's sleeping.She wants it to be like my mytouch3g
update
So I cleared both caches before second boot, it booted but had "the process android.process.acore has stopped unexpectedly. please try again." over and over and over.......... I watched the logcat a bit and kept seeing "java/lang/NoSuchFieldError".
I rebooted into recovery and ran fix_permissions and fix uid mismatch and cleared the cache again for good measure. I am still getting "the process android.process.acore has stopped unexpectedly. please try again."
logcat is attached
quick question and suggestion
coolloser said:
So I cleared both caches before second boot, it booted but had "the process android.process.acore has stopped unexpectedly. please try again." over and over and over.......... I watched the logcat a bit and kept seeing "java/lang/NoSuchFieldError".
I rebooted into recovery and ran fix_permissions and fix uid mismatch and cleared the cache again for good measure. I am still getting "the process android.process.acore has stopped unexpectedly. please try again."
logcat is attached
Click to expand...
Click to collapse
ok so you can boot into recovery, have you tried partitioning the sd card? i didnt really like the cyanogen install guide try theunlockr. com it is the page i found most useful for me, it provide downloads for the radio, spl and even a link back to the rom found on this site, just try following each step in this page and let me know how it works out
ok....
I will try this, but can I be assured that the radio with be compatible with mine?
And this guide wants me to flash the danger spl, I already have that...is it safe to do the spl again?
hxxp://theunlockr.cxx/2010/04/26/how-to-load-a-custom-rom-on-the-htc-g1-dream/
ah, no go "THIS PROCEDURE DOES NOT WORK ON THE ROGERS DREAM! DO NOT USE IT!"
Any other suggestions?
new one
coolloser said:
hxxp://theunlockr.cxx/2010/04/26/how-to-load-a-custom-rom-on-the-htc-g1-dream/
ah, no go "THIS PROCEDURE DOES NOT WORK ON THE ROGERS DREAM! DO NOT USE IT!"
Any other suggestions?
Click to expand...
Click to collapse
htcpedia . cxx/forum / showthread.php?t=287 here is one posted by haykuro
give this one a try
YAYYAYAYA
Followed the haykuro guide, tried cyanogen again 2 or 3 times no go....tried biff mod 2.0 (just released!) tried a couple times...no go....applied the workaround suggested by Shadow31 and bam! This 'ol G1 finally is running froyo.
I'm really liking the biff mod, seems smoother than cyanogen is n my mytouch. Got some extra features too....may flash it to my phone
Related
Mirror the similar thread in Dream forum, I started this thread as a constructive and positive place for those of us that have recently lost our MyTouch or Magic.
I am going to document the steps I took and hopefully reverse engineer this issue and also prevent other folks from doing the same mistake. This forum has been and good source of info. Thanks
What I did
Following [How-To] Root the T-Mobile myTouch 3G and I was able to flush to 2005 SPL and root successful as 32A rom.
Then I stop at "For Daredevils" and went with a different route.
I took the MT3G OTA (signed-opal-ota-150449.95700137.zip) and resigned it with test key and try to update it.
Update was done successfully and radio firmware updated at the same time and once reboot I got red screen of death.
What I got now
Red brick or Red screen of death
Power up while holding 'Back' button, volume down or any other button always result in Red Vodafone logo of death. I can't get to fastboot.
I can't get to recovery or fastboot which mean I can't do anything at all.
What I suspect
Flashing the radio (unclear what ver#) from MT3G OTA build (signed-opal-ota-150449.95700137.zip) might be that reason why it bricked.
Perhaps I probably should have followed the rest of the steps on "For Daredevils" and flash the ION radio and 32B RAv1.2.0G recovery, after that than trying to update with MT3G OTA without the radio.
I read somewhere in the forum (I forgot where), the reason why a bricked phone couldn't boot to SPL and not able to fastboot was because the radio firmware was loaded during SPL startup. Due to issue with loading radio firmware, SPL won't start properly.
Base on that, what we can try is to re-flash the radio firmware. How?
Maybe i can put the radio firmware as update.zip but how can i get the phone to load it when i can't fastboot
waacow said:
I read somewhere in the forum (I forgot where), the reason why a bricked phone couldn't boot to SPL and not able to fastboot was because the radio firmware was loaded during SPL startup. Due to issue with loading radio firmware, SPL won't start properly.
Base on that, what we can try is to re-flash the radio firmware. How?
Maybe i can put the radio firmware as update.zip but how can i get the phone to load it when i can't fastboot
Click to expand...
Click to collapse
It's my opinion. If there is a way, that probably (track ball)+(power), the only key combination we(?) can see .
Let's find a way!
waacow said:
What I suspect
Flashing the radio (unclear what ver#) from MT3G OTA build (signed-opal-ota-150449.95700137.zip) might be that reason why it bricked.
Perhaps I probably should have followed the rest of the steps on "For Daredevils" and flash the ION radio and 32B RAv1.2.0G recovery, after that than trying to update with MT3G OTA without the radio.
Click to expand...
Click to collapse
I think we have exactly same problem.
I'm sorry. I misunderstood. But I flashed ION radio. then...I got a pretty red brick!
I do not believe my phone is bricked but I believe it's pretty close...
My Rogers HTC Magic will not boot/load any recovery. I had a fully functional magic for several months using lots of different roms, however I developed a problem with one of the roms and after trying to install a new one, I can no longer boot any rom.
I can only boot into the fastboot screen, which says the following:
SAPPHIRE UNKNOWN 32A ENG S-OFF H
HBOOT-1.33.2005 (SAPP50000)
CPLD-12
RADIO-2.22.19.26I
Apr 20 2009,15:30:43
Everytime I try to either boot ANY (RA/cyan version) recoveries from either fastboot or flashing it, it does not want to start up.
I can flash just fine, however I do not know if anything is working correctly because only fastboot is accessible, everything else just sits at a rogers logo.
What should I do next?
drewX2 said:
I do not believe my phone is bricked but I believe it's pretty close...
My Rogers HTC Magic will not boot/load any recovery. I had a fully functional magic for several months using lots of different roms, however I developed a problem with one of the roms and after trying to install a new one, I can no longer boot any rom.
I can only boot into the fastboot screen, which says the following:
SAPPHIRE UNKNOWN 32A ENG S-OFF H
HBOOT-1.33.2005 (SAPP50000)
CPLD-12
RADIO-2.22.19.26I
Apr 20 2009,15:30:43
Everytime I try to either boot ANY (RA/cyan version) recoveries from either fastboot or flashing it, it does not want to start up.
I can flash just fine, however I do not know if anything is working correctly because only fastboot is accessible, everything else just sits at a rogers logo.
What should I do next?
Click to expand...
Click to collapse
fastboot flash radio <the correct radio>
Where do I find these radio files? And thanks for the help! I had no clue I needed to flash the radio
drewX2 said:
Where do I find these radio files? And thanks for the help! I had no clue I needed to flash the radio
Click to expand...
Click to collapse
you can get the radio img's from htc...
http://developer.htc.com/google-io-device.html
I have flashed the radio and still get only a rogers screen. I also have reflashed everything with original rogers magic files found on the forum (boot/system/userdata/recovery).
Still only have fastboot working
UPDATE: Got Recovery working. I flashed the radio/recovery from a givemeroot.zip I saw for those flashing the mt3g. I believe it can be used on this as well. Next step is to get a rom loaded
Flashed HardSPL and permabrick mt3g
I have been running Hero ROM's with no issues until today when I flashed a Hard SPL because I wanted to try Cyanogen latest. The new SPL bricked the phone, no power -splash- hboot, just a black screen.
The previous ROM's I have been flashing didn't need a new SPL. Are you not supposed to flash the SPL on the mt3g?
Thanks in advance for the input.
robotician said:
I think we have exactly same problem.
I'm sorry. I misunderstood. But I flashed ION radio. then...I got a pretty red brick!
Click to expand...
Click to collapse
Same thing happend to me too, followed the steps till the radio part, flashed the radio - red brick. luckily i manged to get mine exchanged.
edit: duh, sorry seemed to be a somewhat old post/topic
Any progress on this guys???
drewX2 said:
I do not believe my phone is bricked but I believe it's pretty close...
My Rogers HTC Magic will not boot/load any recovery. I had a fully functional magic for several months using lots of different roms, however I developed a problem with one of the roms and after trying to install a new one, I can no longer boot any rom.
I can only boot into the fastboot screen, which says the following:
SAPPHIRE UNKNOWN 32A ENG S-OFF H
HBOOT-1.33.2005 (SAPP50000)
CPLD-12
RADIO-2.22.19.26I
Apr 20 2009,15:30:43
Everytime I try to either boot ANY (RA/cyan version) recoveries from either fastboot or flashing it, it does not want to start up.
I can flash just fine, however I do not know if anything is working correctly because only fastboot is accessible, everything else just sits at a rogers logo.
What should I do next?
Click to expand...
Click to collapse
ummm... okay, I believe it could be easy goings here, if you go to one of the threads, which I believe you can find fairly easily, to switch radio/SPL through fastboot...
Rogers Magic should NOT use 2.22 radio, but either 3.22 or 6.35, unless of course you are using the dream, which is a different thing all together. Then, push the recovery you want (clockwork or amon RA), if after switch spl/radio, does not work. and voila, theres your fix
**NVM, didn't realize your question got answered
Mytouch 3G black (T-mobile)( rooting procedure source: theunlocker.com)
I have my touch 3g(old version 3.5 mm headphonejack)
I screwed it up while trying to load Cynogen ROM.
I have access to splash screen and it also loads into
Android Recobery Mode.
This is wht i have in the flash screen:
SAPPHIRE PVT 32B SHIP S-ON
HBOOT-1.33.0006 (SAPP30000)
CPLD-10
RADIO-2.22.19.261
HBoot Mode won't work as it says no image found or wrong image.
Is there anything i can do from Androids Recovery mode?
i've tried wipe data/factory resed but in vain. when i try to load the custom ROM, the process aborts and says it cudn't
open the ROM file. I accidentally installed wrong ROM or ROm update which
caused this problem.
Anybody willing to help..would really appreciate it.
All i can say is that you are not bricked.
as long as you can turn it on and access some sort of boot screen your okay. i think
good luck.
ps. i bricked my mytouch3g fender
You're not bricked. I would suggest downloading the ROM file again to be sure that it isn't corrupt. I've had several large files (including ROM updates) get corrupted when transferring them to an SD card. If you can, check the md5sum for the file and verify that it's correct. The CyanogenMod wiki has a ton of other useful troubleshooting tips.
If the custom ROM just won't work, then you should be able to re-flash the original HTC firmware to get the phone working again. It's available online. Good luck!
ChrisRai said:
Mytouch 3G black (T-mobile)( rooting procedure source: theunlocker.com)
I have my touch 3g(old version 3.5 mm headphonejack)
I screwed it up while trying to load Cynogen ROM.
I have access to splash screen and it also loads into
Android Recobery Mode.
This is wht i have in the flash screen:
SAPPHIRE PVT 32B SHIP S-ON
HBOOT-1.33.0006 (SAPP30000)
CPLD-10
RADIO-2.22.19.261
HBoot Mode won't work as it says no image found or wrong image.
Is there anything i can do from Androids Recovery mode?
i've tried wipe data/factory resed but in vain. when i try to load the custom ROM, the process aborts and says it cudn't
open the ROM file. I accidentally installed wrong ROM or ROm update which
caused this problem.
Anybody willing to help..would really appreciate it.
Click to expand...
Click to collapse
A brick will freez on the first screen to pop up and NOT boot into recovery... Like stated just re-download either cyanogen or a stock rom... do you have like amon recovery or stock? I suggest getting amons and do nan-back ups before you ever load a new rom to save time.
Hoping someone can help. I have a magic 32a. I was running cyanogen 6.0, or 6.1 I believe, and I thought it was time to change. In the mix of trying to install new ROM, I did an SD wipe and removed my backups....
I downloaded SDK tools and I have done everything I possibly can, so I'm looking for help.
SAPPHIRE PVT ENG S-OFF H
HBOOT-1.76.2007 (SAPP31000)
CPLD-13
RADIO-3.22.20.17
I had the old radio and SPL, but then I couldn't reboot into recovery. I FINALLY got the radio flashed, and it took my ability to enter recovery away( Amon Ra, don't remember what version).
Now I'm trying the new radio, but every time I try and flash the radio my phone freezes in the middle of the flash. The SPL flashed just fine, but now I can't even boot into recovery and even trying to boot it sticks on the mytouch screen.
My question is, do I have the wrong spl/radio combo, which one I might need, or any ideas on how to get my phone running again.
Thanks.
Alright I got the new radio to flash. Everytime I flash a recovery, it flashes no problem, but gets stuck when I try and boot into recovery....I don't get it.
Hi everyone!
I've been searching and reading around trying to solve a bootloop problem on my HTC Desire S/Saga (or at least I think it is a bootloop problem) but, so far, I've had no luck.
Here's what has happened and what's going on:
1) S-off and got hboot 6.98.1002 through revolutionary
2) phone worked normally for six months and suddenly, without any changes or flashes, it rebooted and started a boot loop, ie, I can't get into any in-OS menus.
3) Choosing recovery of factory settings from hboot menu just reboots the phone and restarts the loop.
4) I've tried flashing (both through fastboot and android flasher) the eng hboot 0.98.0000 and clockworkmod recovery images but neither had any effect.
Phone was vodafone-locked, running a vanilla Android 2.3.4.
hboot menu data:
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3822.10.08.04_M
eMMC-boot
I don't have any backup data from pre-revolutionary, either :|
I'm knocking my head against the walls, hoping that the phone's only temporarily bricked... any ideas?
Thanks in advance for helping a n00b...
Doesn't sound like a hboot problem you me, but that could just be me. And I don't think flashing the stock hboot will help.
Are you sure you are flashing the ENG hboot? It's 0.98.2000. 0.98.0000 is most likely your stock hboot and can't be flashed over revolutionary hboot in most cases.
So to get back to stock stock..... You will need to run your RUU after the new hboot has been flashed.
Another option is for you to install a custom ROM and avoiding the RUU. I still suggest you flash the ENG hboot though.
Head for this thread for help
http://forum.xda-developers.com/showthread.php?t=1488672
Thanks everybody!
I've been away for the last few days so I haven't been able to test anything, but tomorrow evening I'll test both suggestions and post feedback.
Thanks again!
So, I've trying out your suggestions and...
foX2delta said:
Doesn't sound like a hboot problem you me, but that could just be me. And I don't think flashing the stock hboot will help.
Are you sure you are flashing the ENG hboot? It's 0.98.2000. 0.98.0000 is most likely your stock hboot and can't be flashed over revolutionary hboot in most cases.
So to get back to stock stock..... You will need to run your RUU after the new hboot has been flashed.
Another option is for you to install a custom ROM and avoiding the RUU. I still suggest you flash the ENG hboot though.
Click to expand...
Click to collapse
So I tried to flash the ENG hboot from this thread, using android flasher and later using this method, but adb never lists my Saga.
Fastboot lists it correctly, though. I *think* I had USB debugging on, if I recall correctly.
Using androidflasher I get a flash ok notice and then the bootloop just restarts...
Any ideas?
mOh19973 said:
Head for this thread for help
http://forum.xda-developers.com/showthread.php?t=1488672
Click to expand...
Click to collapse
Thanks moh19973, I'll leave feedback at your thread (no luck, though..)
thanks again to everybody
Opalid said:
Hi everyone!
I've been searching and reading around trying to solve a bootloop problem on my HTC Desire S/Saga (or at least I think it is a bootloop problem) but, so far, I've had no luck.
Here's what has happened and what's going on:
1) S-off and got hboot 6.98.1002 through revolutionary
2) phone worked normally for six months and suddenly, without any changes or flashes, it rebooted and started a boot loop, ie, I can't get into any in-OS menus.
3) Choosing recovery of factory settings from hboot menu just reboots the phone and restarts the loop.
4) I've tried flashing (both through fastboot and android flasher) the eng hboot 0.98.0000 and clockworkmod recovery images but neither had any effect.
Phone was vodafone-locked, running a vanilla Android 2.3.4.
hboot menu data:
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3822.10.08.04_M
eMMC-boot
I don't have any backup data from pre-revolutionary, either :|
I'm knocking my head against the walls, hoping that the phone's only temporarily bricked... any ideas?
Thanks in advance for helping a n00b...
Click to expand...
Click to collapse
Your problem sounds exactly like the one on the thread linked below.... in which case, if you just try the steps from the concerned thread, and are still unable to fix your device, it can be written off as another dead eMMC...
Just follow the instructions on this thread...maybe you will have better luck than the OP?
http://forum.xda-developers.com/showthread.php?t=1507106
So did your hboot change or not? If hboot and recovery won't flash then I have to agree with above, fried emmc :-(
yeah it could be an emmc problem, you may want to check the sticky in the development forum, if this is the real problem there is a possibility for a fix, not necessarily emmc replacement
enigmaamit said:
Your problem sounds exactly like the one on the thread linked below.... in which case, if you just try the steps from the concerned thread, and are still unable to fix your device, it can be written off as another dead eMMC...
Just follow the instructions on this thread...maybe you will have better luck than the OP?
http://forum.xda-developers.com/showthread.php?t=1507106
Click to expand...
Click to collapse
Thanks, tried everything and had the exact same results. Fried eMMC, I guess..
This is really wierd, I got a phonecall, turned the call off, the phone rebooted and entered the bootloop.
Nothing fishy or wierd, no flashing erros, just a regular phonecall from my boss. Damn :|
If only I could get the normal hboot on I could repair it under warranty
Well, thanks everybody
Try going for warranty repair, for a few guys over here at xda no one checked (or din not care) whether the phone was rooted or s-off when they went to service their phone. Maybe you'll get lucky too. Good luck!
HELP!!
I've spent several days on this and I'm about to lose my mind. I really am not liking this mytouch4g slide POS.
I was able to use the kit to unlock the bootloader, but any other option within these forums has left me at the tmobile splash screen. I can get everything installed onto the phone, cleared evferything to clear, reset, etc., but can NOT get s-off nor can I get a new rom to load. I've tried many many methods found in these forums to no avail - could someone please assist? Below is my phone info - thanks in advance!
*** UNLOCKED ***
Doubleshot Pvt Ship s-ON RL
HBOOT-1.45.0013
Microp-0353
eMMC-boot
Nov 21, 2011, 20:20:47
HBOOT
ClockworkMod Recovery v5.0.2.7
rpm: 0x44569DDE
SB11: 0xEEAC61A
SB12: 0xA5ED4E3
SB13: 0x55166AZF
TZ: 0xC943A294
RADIO: 0xF2FC87B5
HBOOT: 0x2D40AF1C
BOOT: 0x7353F94
RECOVERY: 0xBA31F19F
SYSTEM: 0x91144DCF
Fastboot boot.img?
Sent from my Galaxy Nexus using Tapatalk 2
now new rom + ics, but still s-on
Thanks AgentCherryColla!!
I had tried that before, but it didn't work.
Maybe I just needed to read your magic words...but sure thing, it up and worked this morning. Absolute goodness - a totally new phone. amazing!
BUT - came to the need to restart and back into the stuck splash screen it went. booted into hboot and it's still s-on. Restoring from the recovery I just set...wanted to try not to have to wipe all the settings I just went through. Is there a perm fix for this, or every time I power off am I going to have to rework something?
Thanks again & in advance for help!
orl74d said:
Thanks AgentCherryColla!!
I had tried that before, but it didn't work.
Maybe I just needed to read your magic words...but sure thing, it up and worked this morning. Absolute goodness - a totally new phone. amazing!
BUT - came to the need to restart and back into the stuck splash screen it went. booted into hboot and it's still s-on. Restoring from the recovery I just set...wanted to try not to have to wipe all the settings I just went through. Is there a perm fix for this, or every time I power off am I going to have to rework something?
Thanks again & in advance for help!
Click to expand...
Click to collapse
Your phone should be rebooting fine, did you do a full wipe and fastboot the boot.img?
Fulle wipe is:
Format system
Format cache
Format data
Format sd EXT ( if you have an ext for a2sd, most users dont have an EXT partition )
Wipe dalvik cache
Flash ROM
Flash gapps ( if AOSP )
Fasboot flash boot.img
Finally reboot
Sent from my HTC MyTouch 4G Slide using Tapatalk 2
argh
Thanks, just followed every step of that bit by bit...now back stuck at splash screen. ???
orl74d said:
Thanks, just followed every step of that bit by bit...now back stuck at splash screen. ???
Click to expand...
Click to collapse
Is the boot.img fastbooting right?
*edit*
If that makes sense
Sent from my HTC MyTouch 4G Slide using Tapatalk 2
yeah
fastboot seems right - everything works great until restart or the like. s is still s-on. but ics pyro works great....
im stuck in the same place...got pg59img.zip and it wont load....can anyone help
curtisparker82 said:
im stuck in the same place...got pg59img.zip and it wont load....can anyone help
Click to expand...
Click to collapse
I'm not sure which PG59IMG file you're talking about but if you're having these many problems why don't ou just try to flash back to stock and start the process over? If you're S-On too you're going to need a signed copy which would be one of the Tmo OTA files they sent out. If you'll hit the "Blue6IX" Link in my signature and look at the last entries for the first post you'll see the ones for the appropriate Hboot software version you're running. With S-On it will only let you load the right one anyway if you don't know which one you're on. (...and I guess if you have S-Off, there IS no wrong one)