8525 help/queston - 8525, TyTN, MDA Vario II, JasJam Software Upgradin

So I'm trying to get my old 8525 running for kicks and realized at some point I must have partial bricked it. The phone function will not turn on and is completly unaccesable. I have no problem flashing the stipped ATT rom, and also have no problem updating/reinstalling the lastest hardspl 2.10. I am unable to flash any radio roms or the stock unmodified ATT rom. I feel there is some inconsistancy in the files on the wiki page and the forums, although I may just be mistaken. I'm wondering if maybe I need to replace the RUUwrapper for the radio as it seems to be an older one. I tried extracting the offical rom and flashing it with the new RUUwrapper but it gets stuck at 11%, same as with the original exe file. I'm doing this all from xp as well so that isn't the problem. I'm sure one of you guys knows whats going on.

Related

Fall Back to Original Rom (Tmobile)

Hi @ all...
so time has come i will return my phone to tmobile, because of the heavy problems with the slide-out-keyboard. i tried to solve my keyboard-problems with the orignal shipped rom, but i realised that it doesn't matter which rom i flash to my phone, the problem seems to be of hardware-ish nature...
so now my problem is: i want to fall back to the original state...
i want original IPL,SPL,OS,Radio, Boot, etc etc...
i tried to flash the "Original Shipped TMOB101" from the wiki, it flashed nice with CustomRUU...the original flash utility couldn't find my phone.
so i unpacked the exe and flashed the nbh with CustomRUU... flashed nicely, but didn't boot... first problem: whitescreen, second: hang on windows mobile screen, third: NOGSM... tried to flash newer GSM 1.43. this worked nice then, but isn't original... any idea how to get the 1.05.02 radio running? tried to reflash the complete tmobile nbh again, same result.
tried to flash with Vista, and also with XP, nothing changed...
next problem i assume is: how to downgrade SPL? and how to detect Bootversion? could it be, that i flashed some newer boot in between, because, i have always flashed newest radio roms, could it be that i flashed a boot together with a certain radio?
hope someone can help me... my device is also simunlocked, i hope they do not recognize it at tmobile. but i want to get everything else into original state before returning.
greetings
garfield
There is now an official wm6 update which you can use
it's available here:
http://forum.xda-developers.com/showthread.php?t=337163
If you're wondering if it's properly been released, it's also available on the t-mobile business site.
Shaks
shaks1979,
I have just been to the tmobile business site and I cannot find the WM6 update - please can you post a link to it?
many thanks,
Paul
the german t-mobile site dies not offer to download the upgrade yet.
flashed the new WM6 from t-mobile yesterday, and it works really great, but my keyboard isn't functional anyway...
has anyone an idea how to enable the flash-utility to overwrite the SPl and IPL? because my tri-color-screen reads IPL-1.01 and SPL-2.10-Olipro and this means, both of them have not been updated... any way to overwrite these rom-sections with the now tmobile ones?
so when finished upgrading (IPL and SPL have to be upgraded before i can go on) i will return my phone to a tcom store, they have to bother with my keyboard issue... my phone isn't a half year old by now... keyboard issues like this shouldn't be there i assume
greetings
and thanks for the new wm6 links.
garfield
Extract the nbh file from the T-Mobile ROM and flash it with CustomRUU. This will overwrite IPL / SPL
[...see reason]
which settings do i have to use with CustomRUU? do i have to select same radio-buttons as always? (SPL 2.10-Olipro/Is it HardSPL) ?
okay, so i found the option via try and error i had to use use: Force UNSAFE SSPL.
i have another question now:
as far as i know, t-mobile DE has not released this ROM to its customers via their website, so i have to flash my phone back to WM5 original rom, and bootloaders, because this new tmobile rom didn't make my problems with the keyboard go away.
my local store told me that they will send the device back to tmobile, and tmobile then will repair or exchange the device.
so if they send it back to tmobile, i uess i have to put it into original state, haven't i? cause flashing the rom causes loss of warranty, doesn't it? i hope they will not recognize, that i sim-unlocked it (did not touch the CID).
problem occurring: i extracted the nbh from the original shipped-archive and flashed it with CustomRUU but when booting NO GSM shows up, and windows stops booting during first bootsplash... sometime during second bootsplash... any idea? might it be that it was like this, because of olipros 2.10 SPL?
greetings
garfield
I wonder why you SIM unlocked your device?
The German Hermes never was SIM locked, so, there was no need to unlock it!
You will either have to Soft-CID-unlock or Hard-CID-unlock your device if you want to flash it otherwise it won't work!
What settings are you talking about? You simply copy the nbh file to the CustomRUU folder and run the UPDATE UTILITY in there! There are no settings, it works the same way as the utilities from shipped ROMs - simply follow the instructions on screen and do not plug out nor touch the device until the job is done!
So actually it is not a hermes, it is a MDA Vario 2 from tmobile, isn't it?
partly you're right, the device wasn't sim-locked, but net-locked, wich means i cannot use my second sim card from vodafone with it. so i had to unlock it.
(i tried without unlocking, the phone asked me for a certain code and no, it was not the pin-code from the vodafone-sim )
if you launch CustomRUU you are asked for the version of your SPL, at least this is what happens when i start it. if you cannot imagine what i am talking about, i will make a screenshot, for better understandings.
I had Hard-SPL installed, this is a form of SOFT-CID-unlocking?
with having Hard-SPL installed i could not boot the original shipped german TMOB101-rom from the wiki...
can i flash the old ipl/spl/radio/os without worries?
greetings
garfield
Within the CustomRUU folder you should see a file called ROMUpgradeUt.exe - this never ever asks for SPL, it is nothing but a modified FLASHING UTILITY.
i only have ruuwrapper.exe
i used this customruu v5.2 from olipro's thread
what customruu are you talking about? actually i never saw a file named ROMUpgradeUt.exe
where to find?
thanks for your help.
greetings
garfield
EDIT:
i have just found this:
NOTE: If your radio version is currently HIGHER than 1.27.00.00 then it is very likely the radio bootloader is version 0108, this WILL NOT allow the radio to be downgraded to a radio containing BL 0106 and will result in a "NO GSM" error. As with other downgrade guides this is NOT intended as a guide for claiming the warranty of the device having flashed components which are not authorised by the manufacturer or carrier.
Click to expand...
Click to collapse
on the WM5-Downgrade site over @mrvanx.org

stuck at HTC black screen after updating dcd

FIXED! Read below for details.
So i've been messing with my mogul for nearly 4 hours now trying to convert it to dcd's rom..and i've flashed it twice now and after it reboots from being 100% loaded it just sticks on the HTC black screen..I've read and read and searched and searched and cannot find a definite answer. Can anyone help?!
basics?
did you load the radio rom?
did you load the unlocker?
you may need to restart the phone to the boot loader and resend the rom
(press and hold camera and power and push reset button)
I did TRY and reload the radio and unlocker..now im stuck at the black htc screen where it says no radio though. bleh. i can't even get it back up and running. what do i do?
edit:
I'm at the multi color screen..ive tried running the unlocker RUU and then running dcd's ruu and it doesn't work..and the radio RUU does not run at this screen...I can't get the phone back to a working status! Argghhhh. It wont let me run the relocker unless im in activesync...but i can't be recognized in activesync unless the phone is up and functional..so..? how do i relock it to put hte stock rom on to try and unlock again?
I am kinda stuck in the same spot, but mine is is the verizon logo screen, i tryed doing the power,camera and hte reset button but its till stuck, i tryed the relocker but i need to be in active sync
any help?
what i dont get is..i flashed it with the unlocker, then the rom then the radio...isn't RUU just overwriting each one or something? it doesn't make sense to me. and all i can do is run RUU..i did the rom, then the radio and it was stuck in the bootloader so i used the exitbl and got out of it but then it just went back to going to the HTC black screen saying no radio. ..i'm gonna try and flash the rom from a sd card next..we'll see what happens..
jkrolcz said:
I am kinda stuck in the same spot, but mine is is the verizon logo screen, i tryed doing the power,camera and hte reset button but its till stuck, i tryed the relocker but i need to be in active sync
any help?
Click to expand...
Click to collapse
This just happened to me after flashing the ROM but not the RADIO yet. Flashing the Radio fixed the problem.
I've flashed the radio..then its stuck in the BL and i use the program to get me outta it then it just keeps saying i have no radio! what the hell..this sucks. i'm in the worst possible situation to have to buy a new phone
There are three parts to the "operating system" of your phone.
1. Bootloader (also called locker, unlocker, re-locker, SPL)
2. Radio
3. ROM
The three components are saved in discrete portions of the device's memory. Flashing one does not overwrite the others. All three must be compatible for the phone to operate properly. If you stop the upgrade process recommended by the ROM compiler prior to completion, your phone may not operate properly. If you flash the "leaked" 3.16 ROM package, it contains all three components.
To use the 3.16 stock OEM ROM, or a custom ROM based on the stock OEM 3.16 ROM, you must have a level 3.xx radio and a level 2.xx bootloader. The current implementations of those are the 3.27 radio and either the stock bootloader distributed with the "leaked" 3.16 ROM package, or the Olipro 2.40 unlocker.
If you are running a level 2.xx stock OEM ROM, or a custom ROM based on a stock 2.xx OEM ROM, you must have a level 1.xx bootloader and a level 1.xx radio.
Custom ROMs are not always named using the OEM convention, so you must research the custom ROM to determine whether it is based on a level 2.xx or 3.xx stock OEM ROM.
I hope this helps all of you get your phones back up and running.
FIXXXED!
So heres the best description I can give of what was going wrong for me..Its my first time trying flash to a different rom..and well it didn't go so well. First, I used the titan unlocker, then installed the radio (not sure which one) and then some form of the newer dcd rom and i was getting stuck on the black HTC smart mobility splash screen where it said "no radio". I had to have messed around for over 5 hours today at college trying to figure it out by doing different arrangements what order i installed the radio and unlocker and rom in. I couldn't get it to connect with activesync so i couldn't use the titanunlocker.exe..all i was going off of was RUU's. Im not sure whether or not what OS I was using effected it..I was playing in Vista earlier today but had done the correct steps to install the drivers, and now this last time i did it on XP. This last time I ran the 3.27 radio RUU as found.. here ( http://forum.xda-developers.com/showthread.php?t=362563 )...Theeen I ran this form of the newer sprint ROM. (I'm pretty sure they say it comes with a included in this RUU, but i'm just stating exactly what I did) the .651 rom can be found.. HERE ( http://forum.ppcgeeks.com/showthread.php?t=16806 ) He had a error when packing or something so you have to manually rename it to .exe because it was missing a e..I did this within winrar before extracting..ran that and about 10 minutes later it booted up and i've got service. I'm not going to promise that this is 100% functional all i'm saying is im out of that horrid black HTC screen where I can now go on to try and get the correct rom i wanted. Hope this helps..may be a bit confusing and probably did things wrong but this was my first time doing it all.

HELP

Hi I'm looking for some help. I tried upgrading my XV6800 to the windows 6.5 rom but I think I might of messed up. I tried to update my radio first but ran in to issues.
I used Oilpro 1.20 to try and tried to update the radio but along the way messed up while trying an older rom and I'm currently at a Verizon screen with the message "NO RADIO" at the bottom. I'm assuming the radio rom was erased. I might have gotten confused with the roms and used a rom without the appopriate Radio. When I try to flash that rom back to a stock Verizon upgrade it just ends 11% in to the flashing process and the rom update utility returns a Error 290 screen.
Currently I can get the oilpro 1.20 bootloader to still load up but I'm not sure what to do at this point. I tried updating the ROM to DCD's older 3.20 roms, which did complete but I still have that screen coming up. Can anyone give me some suggestions on what I should do next? Any help would be greatly appreciated.
Try using NueSPL 2.47 it's more current
Doesn't have have to be run on the phone itself once inside Windows? The only screen I can get up is the Verizon (splash) screen where it normally lists the rom and radio, or the oilpro boot loader screen. I actually can't get back in to windows to run the nueSPL 2.40.exe file.
Is there a way for me to flash the radio back from a bootloader screen and USB or SD card? The thing is I actually tried to take the 3.42.40 radio and use the Flash Rom Utility to see if it would flash the radio rom back on but even though the process completes successfully, I still get the no radio error so I guess it doesn't work. Thanks for the help, I think I may have been a few of the idiots out there who screwed things up and didn't make sure the radio was up before attempting any rom upgrade.
You should've changed the bootloader first. Your radios that you are trying are not compatible with your bootloader.
Flash an old stock rom via SD, then update your bootloader to 2.47 once you can get back into windows, then update your radio, and then your rom.
Yeah that was one of the first things I've tried a USB update back to the stock Verizon 6.1 ROM, but for some reason it prematurely ends at 11% with the PDA Phone Update Utility throwing a ERROR 290 message. This is the first time this has happened as I've flashed with this same rom tons of times. I've been looking online for the past hour on how to flash the ROM from a SD card if I can't get in to Windows. But all I could find was the USB update utility and it ends at 11% Am I doing it wrong? any ideas would be greatly appreciated.
If you can still get in the bootloader then you should be fine....I would put it manually in bootloader holding power and camera simultaneously and poke the hole to get it into bootloader.
Once you do that plug in the data cable and run Olipro 2.40 or Nue 2.47. It should be able to take after that.
Basics steps to flashing a phone:
correct unlocker-->stock ROM-->custom ROM
Most custom ROMs will not include Radios that why you would run the stock ROM first to install the radio and then run the custom ROM. Alot simpler then trying to update the Radio by itself.
AWESOME! I got it back up, thanks guys. For reference purposes I'm going to restate the problem and solution incase other noobs run in to the same issue.
PROBLEM:
I installed oilpro 1.2 during the process of installing a new radio then a rom. Along the way the rom install failed. I tried to reinstall a stock Verizon rom RUU 3.57 & 3.37 radio but it failed at 11%. I was then stuck at the splash screen with a message that said NO RADIO. I could still get in to the boot loader with the power and camera button. But the stock Verizon rom did not install anymore.
SOLUTION:
I used titan_exitbl.exe to exit the bootloader and I went back to an earlier rom found here, rom 2.09 & radio 1.30. That one actually installed. It seems to have worked. I'm back in windows now but I need to uninstall oil pro 1.2 and get nuSPL 2.47 on there before I move further (it looks like while it's still on the stock RUU won't work for me).
Do you guys know how I would go about uninstalling Oilpro 1.2? Will Titan_relocker do it for me? I'm not sure if installing nueSPL over oilpro will do it.
Use this ROm from Verizon to get the Stock 6.1 back up and running. It's the MR2 rom
http://www.pcdphones.com/phone_downloads.aspx?bid=89&cid=1&mid=287&carrier=Verizon Wireless
Beyond888 said:
AWESOME! I got it back up, thanks guys. For reference purposes I'm going to restate the problem and solution incase other noobs run in to the same issue.
PROBLEM:
I installed oilpro 1.2 during the process of installing a new radio then a rom. Along the way the rom install failed. I tried to reinstall a stock Verizon rom RUU 3.57 & 3.37 radio but it failed at 11%. I was then stuck at the splash screen with a message that said NO RADIO. I could still get in to the boot loader with the power and camera button. But the stock Verizon rom did not install anymore.
SOLUTION:
I used titan_exitbl.exe to exit the bootloader and I went back to an earlier rom found here, rom 2.09 & radio 1.30. That one actually installed. It seems to have worked. I'm back in windows now but I need to uninstall oil pro 1.2 and get nuSPL 2.47 on there before I move further (it looks like while it's still on the stock RUU won't work for me).
Do you guys know how I would go about uninstalling Oilpro 1.2? Will Titan_relocker do it for me? I'm not sure if installing nueSPL over oilpro will do it.
Use this ROm from Verizon to get the Stock 6.1 back up and running. It's the MR2 rom
http://www.pcdphones.com/phone_downloads.aspx?bid=89&cid=1&mid=287&carrier=Verizon Wireless
Click to expand...
Click to collapse
Glad to hear you got your phone back up
As far as I know you should be able to just install 2.47 and it will overwrite your old bootloader without problems. I could be mistaken but there isn't really a way to "uninstall" a bootloader, just overwrite it with a different one.
unL33T is correct...just run Nue 2.47 and let it overwrite the old one. 8p
Yeah that's what I thought too, but when I tried to over right it with 2.47 the 1.20 showed up again so I used the titan_relocker tool. Maybe I did something wrong. I'll go recheck, thanks for the replies guys.

[Q] htc hd2 stock rom 6.5.3

can somebody please help me, I have flashed 5 different ROM's to my vodafone HD2 and have encountered a varying degree of problems with each one. I would very much like somebody to tell me where I can get a Stock ROM not locked to any carrier so I can reflash my pretty usless fone or indeed to help direct me to a stable cooked ROM that would allow my fone to work again.
Thanks is advance.
P.s - my first post so please be gently, also the last 3 I have tried are Artemis ROM's with no sucessful outcomes.
peeko1979 said:
[Q] htc hd2 stock rom 6.5.3
Click to expand...
Click to collapse
there is no stock rom that is 6.5.x They are all 6.5
Not sure what you mean by stock rom not locked to a carrier, , do you mean a non branded rom (the ones marked HTC WWE, look HERE or in the various threads in the rom development section.) or do you mean you want to unlock your phone to use any network? in which case no amount of any kind of flashing will do that. Ask voda for a code, or buy one online.
Sounds to me like you need to return all the way to stock and start over. Get any of the voda roms from that link above (theyre marked vodaphone, you cant miss em, theres a 1,43 one, a 1.66 one ((if you're a brit)) or 1.72 if you have a european language voda.
Get that, and either
1 - remove hspl by running hspl.exe and choosing 1.66.0000
then
2 - run the downloaded rom.exe and flash over usb
or
1 - extract ruu_signed.nbh from the rom.exe you downloaded,(look it up if you dont know how) copy it to a formatted fat32 sd card smaller than 8gb, and rename it leoimg.nbh then start the phone into bootloader and it will ask you if you want to flash.
that way you are back to teh start, and you can apply hspl and start again.
(For people reading this thinking 'he didnt say do a task29',, its my understanding that using the official .exe to flash the rom does a task 29 anyway, and its been edited out of customruu.exe so it can be used to flash radios without wiping the rom,,,correct? yes no?)
I try 6 Rom but noone will work fine
Vodafone rom 1.72
I am not looking to unlock the fone, simply find a Rom that is 6.5.3 that is stable. I have just flashed back to voda 1.72 but that is 6.5, im fussy and don't like the start button at the top. I'm in scotland so need something that will work here ok on vodafone.
I was hoping to find a rom that had not been altered and as such an original (Stock) ROM.
your help is much appreciated.
There are no such stock roms for the HD2. If you want to flash a stable rom in the style you like (start button at the bottom) then you will need to HSPL (search the forum) your phone and I suggest you start with Dutty's rom. It's very stable and as close to stock as can be. You can always flash back to an original rom for warranty reasons if you need to.
tnx, trying one now. fingers crossed.
ok, just flashed one of duttys roms but now my phone will not boot, it turns on and stays at the htc splash screen. Wont turn off have to pull out the battery. If it will not boot how can I re-flash it? Any suggestions?
did you flash hspl? you will also need the newer radio 2.15.50_04
Quote from Dutty's first page:
Things to Know how about my ROMs:
* HSPL 1.66 Minimum required
* New Radio 2.15.50.04 can be flashed here:
http://forum.xda-developers.com/showthread.php?t=801252
* :Added XDA UC_NET_v0.94 for Auto install see here for instructions:
Thanks to ahirshfield for recommeding it and serfer222 for great work.
http://forum.xda-developers.com/showthread.php?t=709557
* :HSPL 1.66 Minimun recommended
* :Radio 2.10 / 2.11 / 2.12 / 2.14 / 2.15 NEEDED for ROM
* :No Radio version is included in these releases:
* :Correct radio needed to enabled 576 ram for NON-T-Mous HD2 users.
* HD2 Radios can be found here:
http://htcpedia.com/forum/showthread.php?t=2199
I hope you did some reading before you flashed!!
Put your phone into bootloader by holding the vol down side key and use a pen to push the little reset button when the back cover is removed. You should get a tri colour screen which shows you the hspl version you have. If you do this you can flash the correct radio which is probably why the phone will not boot.
all I have done previously is downloaded .nbh files and used SSPL_RUU.exe to flash and they have all flashed sucessfully, but with the after effects of either connection problems or freezing issues.
I have managed to re-flash to the vodafone 1.72 software so at least it is working again, this is not by any means where my talents lie. im a hardware guy, not software, so finding this all a bit confusing. I may just go with the artemis v33 rom which seemed to work the best apart from occassion signal dropouts.
Just out of curiosity - which hspl and radio are you using?
in the settings it says radio 2.07.51.22-2 and i believe the hspl was 1.42
just checked bootloader, spl 1.66
peeko1979 said:
just checked bootloader, spl 1.66
Click to expand...
Click to collapse
If you are sure it's SPL, than your problems are normal sir. To be able to flash custom ROM you need HSPL ex (1.66 HSPL)
is there another way to check other than in bootloader?
peeko1979 said:
is there another way to check other than in bootloader?
Click to expand...
Click to collapse
No sir only bootloader.
I have just re-flashed v33 artemis, so will stick with that, might look at updatin radio version tho. all help much appreciated but must away now as wokring in 5 hours.

HD2 Flashing via SD card and RUU -- replacing HSPL with SPL

Hey guys, let's see if you can help me.
My phone is dead, probably hardware failure. I last ran MAGLDR on it, and it was starting to tweak out. Random reboots, not booting up, etc. I flashed it back to stock about six months ago and it was still rebooting and dying but the rom did boot. Since then, for whatever reason and without actual use of the phone, the hardware problem has become MUCH worse. I can no longer boot into WinMo but can 1 in 20 tries boot into the HSPL screen/bootloader.
I need to send it back into HTC before the 28th of October and I don't want them to see Cotulla HSPL on screen. I've never overclocked or so much as used the phone for a long period of time, and I'm extremely gentle to electronics, so I don't know what the problem is.
I've been trying to flash back via this method.
http://www.youtube.com/watch?v=Wc89Gh0QpIY
I don't think the rom is right for my device, so I haven't used it. I own a TMOUS HD2 and the rom this guy has is a WWE rom. I don't know if this is safe to flash. Anyway, I went ahead and downloaded the latest TMOUS stock rom which unzips as an executable. I then ran the EXE, and it unzips the RUUXXXX.nbh file into C root--at least that's where I found it. I copied the file to root of the SD (FAT32) and renamed it LEOIMG.nbh. When I boot into the bootloader tri-color screen, it finds the image but only gives me an option for flashing the OS. In the youtube vid the guy flashes all sorts of things. When I flash the OS, it doesn't replace the HSPL. Does anyone have a LEOIMG that includes the SPL for a regular TMOUS? His RUU is 266 mb and mine is 5.
Any thoughts? I've scavenged the internet and I can't find a good nbh file that works.
metroidnemesis13 said:
His RUU is 266 mb and mine is 5.
Click to expand...
Click to collapse
thats wrong, you have a corrupt download or something, whats the filename before you extracted it? Go to t-mobile.com and download again. Instead of running the .exe and finding the file in c drive, you can just change the filename extension from .exe to .zip and it will open as a zip file.
I found an RUU that is 200 something MB. It has all that he had on his. It is also a TMOUS version. The problem I am having is the thing freezes after about a fifth of the installation completes, time and time again. I believe the image is good. I think the NAND on my HD2 is permanently messed up. When I access the tricolor screen now it tells me that the update failed and to please try again, and cotulla is still printed at the top. Any thoughts? Do you think HTC checks these? I sent in a Nexus One in and they sent me a new one back, no questions asked, even though the bootloader was unlocked.
I have to send this in very soon, since it expires the 28th of Oct.
all you can do is try all the tmous roms from the 't mobile test and stock roms'' thread, but not teh first three in eth list.
if all else fails you can try flashing a non tmous stock rom, which will brick teh phone, BUT will also brick bootloader, so they wont be able to see cotulla, which is the ionly thing they are interested in.
DISCLAIMER - flashign a non tmous stock rom WILL brick your tmous. The point being it will not boot at all, completely dead, so tey cant see the spl has been hacked.
Sounds like a plan.
That didn't work. The UK rom exe freezes at 1%. Returning to the bootloader I still see Cotulla's name. Ideas?
EDIT: After the third or fourth attempted flash it now says software update failed with an exclamation point and a triangle, and the only way to access the tricolor screen is to have a LEOIMG on an sd card and hit cancel. There it says cotulla. I'm going to try to brick it more with a .51 radio just to be safe.
Thanks for your help guys. The phone pretty much bricked itself. I couldn't flash the .51 radio because it stopped turning on after a while. I sent it into HTC and they repaired it, no questions asked. Now as long as it doesn't fail again... I may get an EU version because those seem to be a little bit more reliable...
Thanks again! Thread can be closed.

Categories

Resources