Cannot flash radio - JASJAR, XDA Exec, MDA Pro Software Upgrading

Hi,
I'm on radio 1.14 T-Mobile MDA Pro.
I've flashed my radio from 1.10 to 1.13 then 1.14 over the last 6 months without any problems. 1.14 is not the best radio I've ever used and seems to be pretty poor with WM6. I'm trying to reflash with 1.13 but it's not having it. I've tried directly from the bootloader (1.01) screen but it still won't have it.
Could anyone help?
Thanks

what kind of error message appears in ma_noupgrade when u try to flash radio in bootloader mode?

Error message
Wow that was quick!
Thanks,
It's 114 Radio Rom Update Error (i've attached a screen grab). I'm using parallels to do the flashing - works on a rom as long as there is no radio.nbf to be flashed.
Thanks

sometimes it could happen. but you should be able to continue.
retry again two or more times.
if it stuck during flashing, retry again.
if it didn't work, try to uninstall activesync 4.5 and temporarily try to flash radio with 4.2 version.

activesync 4.5 in only necessary for WM6 synchronization.
you can use 4.2 while u are in bootloader mode, and try to flash radio.

Still no luck
I've tried everything without it working. Think it might be due to Parallels. I've reflashed the rom to 2.02.00 and it seems to have stopped the problems with the radio dropping out anyway.
Thanks for your help

Related

unable to downgrade/upgrade rom

I have dopod d810, i recently flashed my device to LVSW 2.0.0.7, radio 1.41, and also HARDSPL.
Now i want to upgrade to LVSW 2.0.1.1 latest rom. But after so many times i have done the upgrade procedure, after reset, it keeps going back to the previous rom.
The upgrade seemed to be working. but when it finished, i still got the old rom...
I have tried SUPERCID unlock my device. but no luck.
even worse I tried to revert back to original dopod rom, still no luck.
There is no error when flashing, it wen from 0% to 100% without problem, just it keeps reverting to old rom.
anyone??
klikman,
Check this link: http://forum.xda-developers.com/showthread.php?t=293632

Radio Problem (I Guess...)

hi guys....
When I received or made a phone call....it ended suddenly......no voice & I lost the '3G' or 'G' sign on the title bar.....
after the call ended....the sign back again.....
Do I have problem with my radio (1.46.00.11)??
Should I upgrade my Radio?
FYI...I am running karmba latest version (touch flo)
widigol said:
hi guys....
When I received or made a phone call....it ended suddenly......no voice & I lost the '3G' or 'G' sign on the title bar.....
after the call ended....the sign back again.....
Do I have problem with my radio (1.46.00.11)??
Should I upgrade my Radio?
FYI...I am running karmba latest version (touch flo)
Click to expand...
Click to collapse
Well, I have used that radio for a long time with several ROMs and did not encounter any problems at all. You might try reflashing the radio (as it does not involve any data loss) and if problem still persists try switching to another radio version or ROM.
My two cents ....
tnyynt said:
Well, I have used that radio for a long time with several ROMs and did not encounter any problems at all. You might try reflashing the radio (as it does not involve any data loss) and if problem still persists try switching to another radio version or ROM.
Click to expand...
Click to collapse
Based on my experience, the 1.46 radio ROM is extremely stable.
I did have problems with the karmba_a 6.2 ROM freezing on me, which has never happened with any other ROM before.
The freezing may be due to either the ROM itself or by a conflict with third-party applications, I wasn't able to identify which ....
I'd be inclined to try another ROM as my primary solution. If the problem persists, I'd reflash the 1.46 or look at another radio ROM, as tnyynt suggested.
Cheers!
hoja67

HELP Error [246] Device not responding (Not the typical version of error)

Hi Guys
I have read all the threads and support messages re: Error [246] Device not responding. And mine is different.
I first experienced this problem after I flashed Pays 1.45 Lite after previously installing Pays 1.45 Full. When i try to flash any ROM (not just Pays) I get an "Error [246] Device not responding" message.
Unlike other Error [246] Device not responding problems my bootloader tricolor screen does not come up on my Hermes. I have tried, reinstalling Active Synce, Hard and Soft Resetting, Restarting the bootloader SSPL and still no resolution of the problem.
Sorry bring this problem to bear but it is different to your typical "Error [246] Device not responding " problem and it is driving me batty. the ROM i currently have installed works (Pays 1.45 Lite) and my USB syncs with active sync fine.
Any ideas what the problems could be? I am tempted to drown the hermes in holy water atm to make sure it isn't demonic possession ;(
Any help would be appreciated ;p
Quick update:
I used Force using Safe SSPL for installing ROMS in the past with no problems. It is using this method that I get the 246 Error.
Other methods used gain different errors:
SPL1.04/1.10 - SPL1.09 Bootloader = Error 260 Update Error (check phone attached to usb cable and computer - which it is)
SPL1.11/1.13/1.20/1.35/1.40 Bootloader = 1% complete progress the error 270 Update Error (file image is corrupted) NO MATTER WHAT ROM I USE.
SPL2.02/2.10/2.30 New Bootloader = error 270 as above
Bootloader Screen Reads:
HERM100
IPL-1.01
HERM100
SPL-2.03
I have successfully flashed about 4-5 roms before without experiencing this problem. I have made no changes to my device or my PC. I don't know what could have caused this to happen all of a sudden and out of the blue.
Could a moderator please move this to Hermes Upgrading etc section please?
Have you tried installing the latest Olipro Hardspl v7.... it will read as v2.10 which is a later release than the v2.03 that you have... it will also fix any bad blocks on your device and you should be fine after that...
Debonairone
You. sir.... ROCK!
Works great. Tragedy averted. Thoughts about buying an iphone extingusihed.
;p
Hi gurus,
Im having the similar problem encountered the Error [246] Device not responding.
I have try installing the latest Olipro Hardspl v7 but unable to work. I am still encountered the same problem.
Im currently on Dopod 838 Pro (Hermes 100) with PAYS ROM, Rome Date : 08/09/07, Radio Version : 1.47.00.20, Protocol Version 32:80.7020.20H
Any advises and ideas ?
debonairone said:
Have you tried installing the latest Olipro Hardspl v7.... it will read as v2.10 which is a later release than the v2.03 that you have... it will also fix any bad blocks on your device and you should be fine after that...
Click to expand...
Click to collapse
can i use this olipro v7 for the herald/wing? i am unable to flash anything. i am hard spld and i have a working rom, i just dont like it. thanks
NO!!!! Using the Hard SPL for ANY Version of HTC device it wasn't intended is the fastest way to brick your phone...
ultramag69 said:
NO!!!! Using the Hard SPL for ANY Version of HTC device it wasn't intended is the fastest way to brick your phone...
Click to expand...
Click to collapse
cool, i didn't use it. but i can't flash anything. this stinks. i'm stuck with a rom i dont want.

Only get bootloader after WM6 re-image.

On my Universal (02 Exec) which I had Ranju's v7.6 image on for quite a while I got a problem. pmnotify.exe stopped working and it stopped recieving calls, so I decided to re-flash it with a different image.
After trying to flash it with BL's latest image it failed on all three parts, Radio, CE and Extended, and the recovery part of the program crashed as well.
I then tried to install Ranju's image again but that also failed with a 112 error. Whats going on? Is there any way I can fix this so I can flash it again? I haven't bricked it have I?
EDIT: Oh yeah the bootloader says "Serial v2.01" just to let you know
Fixed using this:
http://wiki.xda-developers.com/index.php?pagename=Uni_Stuck_Bootloader

Issues Flashing New Radio

I know that I have already posted on someone else's thread, so I figured rather than hijacking someone else, I would start my own.
Here is my issue. I have tried every posted method out there for flashing Radios into my Sprint Vogue (flashed to MetroPCS). I am currently on NFSFAN's 1.00.6.5 Rom (21864), with radio 3.37.10.
I have tried...
*Flashing from SD card with a fat32 formatted 2 GB card, renamed radio to VOGUIMG.NBH (upper and lower case),
*Flashing via USB with ActiveSync on,
*Flashing via USB with ActiveSync off,
*Flashing via USB with bootloader preset,
*Flashed back to the Alltel rom used for SuperCID and tried to flash radio while in that rom,
*I have tried with radios 3.42.30, .40, and .50.
The only thing I have not tried has been mtty, but somehow I have my doubts that it will work.
Every time the RUU runs, it starts and the progress quits at 8%, with my phone being rebooted. Also, the RUU displays error message 328....
I have searched all over and tried a few things but most of them are related to the Titan and not to the Vogue. If anyone has encountered this issue and knows how to solve it, I am open for suggestions. Thanks...
I suggest your flash your phone with the stock rom of bell if your want the 3.42.5 radio. Just reset as soon as your see the 3 second customization screen.
Then unlock phone, and then flash your fav custom rom.....
SL said:
I suggest your flash your phone with the stock rom of bell if your want the 3.42.5 radio. Just reset as soon as your see the 3 second customization screen.
Then unlock phone, and then flash your fav custom rom.....
Click to expand...
Click to collapse
I'll give that a shot. Thanks for the suggestion...
@SL
I followed your advice to a certain extent. I went with the latest Sprint official rom, which carried 3.42.30 in it. This seemed to work ok. I still cannot go to .40 but I guess if I flash from the original carrier that had this rom, I will be in good shape (Bell with .50, etc). Do you know which carrier has .40? Thanks for the help!!!
@ SL
I finally went over to the Bell rom that can be found in HTC's official website. I am finally up and running with 3.42.50!!!
I will probably try to make a sticky or a post describing the problem and the solution for people with the same issue, which I have seen quite a bit looking for an answer...
Once again, thanks for all your help!

Categories

Resources