My Prophet has stopped reading SIM cards, and will need a warranty repair.
I can't take it in as it is, what with Jesters spash screen and all. I just assumed I could re-run a previous rom to have it install, but apparently you can't "downgrade".
I've tried looking for downgrade guides, but I haven't managed to find one. Ultimately, as long as I can get the splash screens to have it boot up to "Invalid or Missing Sim" I should be home free, but how do I get them out of the previous rom? Or, how do I edit the rom so it'll install on my device?
I've tried using TyphoonNBFtool to edit the image version, when I go to resave the rom, it only saves 2kb, so I'm obviously missing something here. I'm currently looking into ways to strip files from the rom itself.
Any ideas or suggestions here?
I have had (and still have) problems with my S200. I have installed the LVSW AKU2.3 ROM and I did not have any problems with the warranty.
They just check the image, OS, SW release and radio version and they all passed the warranty check.
So there is no need downgrading.
HappyFace said:
I have had (and still have) problems with my S200. I have installed the LVSW AKU2.3 ROM and I did not have any problems with the warranty.
They just check the image, OS, SW release and radio version and they all passed the warranty check.
So there is no need downgrading.
Click to expand...
Click to collapse
Well, half the reason I wanted to was to learn how to do it.
Which was successful!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://forum.xda-developers.com/showthread.php?t=271043
This thread had all the tools I was after, and a PDF with tutorial. Obviously I just substituted what I required, and whammo. I initially attempted to use the prophet RomUpdateUtility-No Vendor ID, but that didn't work. So I tried the Wizard one that was included in the tools, and it worked no hassles.
So yeah, I'll take it back tomorrow.
Summary: You can't downgrade roms because if the IPL or SPL version (primary and secondary boot sections, or something) is lower than the one you have installed on your phone, it won't let you install anything. "This NBF file cannot be used for your PDA phone. Please get newer NBF file." So you have to use the tools in the above thread to split the nbf up into it's appropriate sections (OS, Extended Rom, IPL, SPL, Phone splash, HTC splash and GSM), then re-combine them without the IPL and SPL using a Cooking Guide and then use a working Rom Update Utility (as I mentioned above, I had to use the Wizard one that came with the tools because the Prophet one kept saying it couldn't open the "required file") to install it onto your phone.
You can use this thread if you're only interested in changing your boot splashes.
Related
Hi,
I keep having problems upgrading to WM6
I've been able to upgrade to OS 2.26.10.2 (the love one) but I can't seem to upgrade to WM6...
The IPL/SPL stays at 2.17.0001
When I run the shelltool and I click on Get OS nothing comes in the screen... though I have the 3.0 nb.nbk in the shelltool directory... so upgrading via that way doesn't work either...
Any clues?
Well your IPL/SPL isn't the OS ROM version - its the bootloader code of the device. Seeing as you have a G4 you don't want to mess with the IPL/SPL as there are currently no known upgrades for the bootloader on G4s - if you see an upgrade it will be for a G4 and will almost certainly brick your device if you attempt to flash it. As for changing the OS shell tool you should have an nbf not an nbk so perhaps the problem. I recommend CID unlocking so you dont need the shell tool at www.imei-check.co.uk
Hi thanks for quick reply...
You say that if I see an upgrade, that it will be for a G4. But I have a G4. Or is it a typo and did you mean G3?
the nb.nbk that I said, was also a typo... It is a nk.nbf, so that should work.
furthermore I don't think my device is CID locked? (BTW How do you check that?) I have a Qtek that is not from one or another provider...
hey mate,
it doesnt matter whether it is for a G3 or G4 as long as you are only trying to flash the OS itself (no spalsh screen, no ext.rom...). I used Faria's RK and created a flash-file only with the OS and used the shell-tool to bring it on my device (still CID-Locked).
regards
IRM
I did this a million times the last 3 days with my g4. theres a guide on here, follow it, read it a million times, do what you gotta do. pretty much, do a fresh install of the tmo 2.26 rom, put this cert_spcs and enablerapi on your phone, reboot it, turn the radio off, open shelltool, put the nbk.nf or something file in the same directory as shelltool, extract the os, then push ok, wait for it to finish and thats it. (in a nutshell) like i said if you have questions, let me know, ive been doing this nonstop the last 2 days and overcame every error.
thanks a million everyone.
An CID unlocked seemed to help. I thought that since I didn't had a Qtek device and not a phone provider one...
Hey Guys......
Save yourself the hassle and buy my G3 that's fully inlocked.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm currently using the Samsung Blackjack & about to purchase the 8525 from at&t. I have 15 days to complete this, they give you 30 days to use and return without penalty.
After 2 days of messing with this and learning more about flashing ROMS than I ever wanted to it finally worked!!!
If you messed up by not SuperCID(ing) your phone before you flashed it because you didn't follow directions like me, here is a solution that i had to dig up from various forums and threads to get your phone back to WM5.
1. Downloaded the imate wm5 from here:
ftp://ftp.xda-developers.com/smartphones/Tornado/Shipped_Complete_Updates/I-mate
2. Downloaded the Typhoonnbftool...just google it. I used version .4.
3. Find out what your original CID id is by using the Ttermpro. (make sure the Allow USB Connections is unchecked in Activesync...i spent an hour trying to get ttermpro to work)
refer to this thread for more info: http://forum.xda-developers.com/showthread.php?t=319588
4. Now run the typhoonnbf tool. File > Open the .nbf file you downloaded in step 1. (imate wm5)
Tools > Edit Data Header
Change the Operator to match what your SuperCID id is (Step 3) and type in 99.99.99.99 (i'm sure any high number will work here) in the "Image Version" field as well as the "Secondary Version" in the header of the .nbf. (i'm not sure if the Secondary version is necessary, but i did it anyway to be safe)
Sample of what it should look like:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. Save the file under a different name in the same directory. Move the orignal .nbf file to a safe location. Rename the edited version to nk.nbf
6. Run the ROM update utility and it should work
Good Luck and don't give up hope.
Hi All... I didnt notice and i tried to run ((Artemis_Touch_Vanilla_4.02.zip)) this ROM on HTC touch and its got stuck on HTC logo screen and says OS 3.13.0.0 .... Please help me... i have tried to restart and tried what ever possible but nothing is working it comes back to same screen...Please help ...please
the thing is it does not go the three color screen...it straight comes to the HTC logo screen and then in about 3 or 4 seconds comes OS 3.13.0.0 and then thats it its on the screen for ever....I cant click on anything its does not even restart with the power button on top...i can reset or take out the battery to shut down.....what do i do now...please help me
512k nbf
Hi
After I edit the nk.nbf file the resulting file is only 512k so the rom updater won't load it.
What do I do?
try using another version of typhoonnbftools
1. Downloaded the imate wm5 from here:
ftp://ftp.xda-developers.com/smartph...Updates/I-mate
The link doesn't seem to work for me. It poped up "error 503: permission denied".
Does anyone have the same problem. Where else can I get an imate wm5? Thanks a lot
SupremeM said:
1. Downloaded the imate wm5 from here:
ftp://ftp.xda-developers.com/smartph...Updates/I-mate
The link doesn't seem to work for me. It poped up "error 503: permission denied".
Does anyone have the same problem. Where else can I get an imate wm5? Thanks a lot
Click to expand...
Click to collapse
Use ftp://[email protected]
you should be asked for login details, use xda as user + password
then navigate the folders starting with the smartphone then Tornado links, you should be able to find it from there.
New problem
I got another version of Typhoonnbftools and successfully edited the header of the file. Flash seemed to go fine right up until reboot. It restarted and displayed o2 splash screen (which should have been overwritten by the imate rom) and continues to bootloader.
Any more suggestions anyone?
wat i still dnt understand is that wen i run tera term pro i dnt no where to type the info 2
my problem now is how to know my tornado cid pffff
OK, i got past the Custom RUU issue that i had earlier, but now i got a differnt issue. I have installed Joshed Elite V10. Loaded, and it runs for about an hr, then i get something really strange happening. The system begins to rename the files in Windows, (Like Program Files went to ^12$& [] ) and i am trying to figure out a cure. I have built my own roms, and have flashed my phone about 50 times. It is a Kaiser 100, Radio 1.70.18.02, Hard SPL 1.01IOlied (it did not let me change this) Protocal 25.83.40.02H. Got it about two years ago. Any suggestions or help? Currently i have the ROM file on my SD.
Oh, something else came to mind, the CustomRUU that i am using is not a Kaiser RUU, but it was for the Blackstone. Is that possibly the problem? And if so, how do you revert it back, as it will not understand the Kaiser CustomRUU.
l
Vosberg1 said:
OK, i got past the Custom RUU issue that i had earlier, but now i got a differnt issue. I have installed Joshed Elite V10. Loaded, and it runs for about an hr, then i get something really strange happening. The system begins to rename the files in Windows, (Like Program Files went to ^12$& [] ) and i am trying to figure out a cure. I have built my own roms, and have flashed my phone about 50 times. It is a Kaiser 100, Radio 1.70.18.02, Hard SPL 1.01IOlied (it did not let me change this) Protocal 25.83.40.02H. Got it about two years ago. Any suggestions or help? Currently i have the ROM file on my SD.
Oh, something else came to mind, the CustomRUU that i am using is not a Kaiser RUU, but it was for the Blackstone. Is that possibly the problem? And if so, how do you revert it back, as it will not understand the Kaiser CustomRUU.
Click to expand...
Click to collapse
Ok first If you have built your own roms then you know that the wrong RUU could mess up your phone. That is most likely your problem. I cant believe it has worked for this long. Try to get the SPL to take or you will have issues. Here is what you do. First Go back and read the Flashing for noobs thread again. Then flash a SPL, Then a Stock Rom, Then download a Rom from the KAISER section and Flash that. It is really hard for me to buy that you have flashed soo many times with that set up and not Bricked your phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As zelendel says using the wrong RUU will cause major probs, i'd go back to basics and start from the beginning again.
[Resources] Flashing Your First Kaiser Rom (For Noobs)
Any problems then ask in the specific thread.
Thread closed.
My Focus 1.3 still wont detect the retail updates via zune so I am trying to use the manual update featured here: http://forum.xda-developers.com/showthread.php?t=1306415
However, after it does a bunch of installing and reboots my phone I get an error indicating 'two or more packages contain the same file' and cant figure out why it is doing this.
Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i had the same failure to the update 8107, i solved it that way, sending one by one cabs to the device... first one language, the 2ns 3rd 4th an so on... then the last update 8107 arm something... that solved my problem. but it can also be a ROM problem, if it is a custom rom... in the end if nothing works try a phone reset, then try to send this cab files.
Dinchy87 said:
i had the same failure to the update 8107, i solved it that way, sending one by one cabs to the device... first one language, the 2ns 3rd 4th an so on... then the last update 8107 arm something... that solved my problem. but it can also be a ROM problem, if it is a custom rom... in the end if nothing works try a phone reset, then try to send this cab files.
Click to expand...
Click to collapse
So are you saying I should remove all but one of the .cab files and run the utility? I havent done that but I'll give it a shot if that is ok to do.
Hmm, so I did this to the first .cab file and it updated me to 7.0.7403.0. However, so far the next one(s) in line will not go. They say "No applicable packages" and, of course, Zune still doesnt think I need any updates.
Edit: Actually, I think I see why. The first update which is supposed to take me to (7.0.7004.0) actually went all the way to 7403. Trying the 7403+ cab file now.
I started going one at a time and it got me partially updated but then one error out and basically bricked the phone (boot loop). I flashed back to 7004 and this time, for whatever reason, Zune detected the updates all the way up to Mango. The previous time I had flashed to 7004 it did not do that. I am now on 7.10.7720.68. I dont know if that is the 'latest' official release, but it appears to have the mango features at least.
Hello everyone,
This is my first message. I have never posted here before but I've read a lot; I always found all the information I needed (and I thank you all greatly for that). But this time, i'm out of clues.
I have a HTC Titan US AT&T and i'm trying to flash it to DFT Eternity Pearl Edition, mainly to have it updated past build 7720 (since AT&T decided to screw us all and stop shipping updates; the CAB sending method fails on it).
Info about the device:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Below is what I tried and the results I got:
1. flashing SPL from DFT_HSPL_WP7SG1 using RUU: gives "invalid model ID"
2. flashing it using the goldcard method: the phones displays "entering USB host mode", then "loading", then immediately reboots and goes to the SPL screen (above)
3. from there, plugging the phone to a computer, then trying to flash HSPL using the wizzard gives a communication error when trying from XP, and apparently succeeds when trying from Windows 7. But restarting after it's done gives the SPL screen which doesn't say HSPL anywhere.
4. then, trying to flash the actual ROM (DFT Eternity Pearl Edition) from RUU gives "invalid model ID" again
5. I also tried to flash the original ROM for my device, IMG_Eternity_Cingular_US_1.10.502.04_Radio_16.23.02.26_A_16.27.00.23_Signed_ETERNITY_RELEASE.nbh, hoping it would somehow downgrade the SPL and things would go well after that, using the goldcard method. That apparently worked:
But I then tried everything again and got the same exact symptoms.
6. Then, right now I tried flashing the DFT Eternity Pearl Edition using the goldcard method and it has been stuck on the "Loading..." screen for 20 minutes and still counting.
I'm out of ideas. To me 5. proves my goldcard setup works. I will, however, go out today and buy a SD card reader and try again as i've been using a flash drive. Would any one have any more idea?
Maybe one thing worth noting: that phone was originally a test phone, meaning a phone that AT&T would give companies who wanted to try new phones before buying a whole fleet of it. I don't know if they do anything to these phones.
I *promise* this is the only bump i'll make on that message. I bought a SD card reader but the damn thing doesn't even power up when plugged on a laptop so I have to return it.