Things were good for a while but now it all has gone to ****s.
My BA is having issues and not only with BT. I have managed to enable big store using exttools.exe and repart_doc.exe. The only issue is that I guess that has wiped the hidden rom where all the preinstall apps were.
To make a long story short, I had reinstalled the original rom, from a rom dump I did right when I got the device, however, the device, even after hard reset does not run the usual set up utilities that it did and install the junk my telco has included. While for the most part this was not a big deal now I realize that some of the fixes were needed.
For example I used to have BT xxx.3500 now I have xxx.3900 all find and dandy but with both versions my BT will not stay up for more than 2 minutes before it drops the connection.
On soft reset I get the following error message.
Cannot find "storage" ( or one of its components) Make sure the path and filename are correct and all the required libraries are available. Bugger
So now the question is - IS there a way of making these apps run and if so, how or is there another fix that can be done. MY BA is bleeding and it is dying and it is pissing me off.
After all the restores I can see the Extended_ROM on the PPC once again and all the apps in it, just can't run any of the darn things.
BTW, as my signature says this is BA from Telus and it is running on CDMA. which btw is missing from the WWE version on http://wiki.xda-developers.com/index.php?pagename=BA_Versions
Any insight would be appreciated.
If I understand everything correctly, you've effectively wiped the Extended ROM and are using it, along with your Storage as one big "persistent storage" folder on your BA, which is what those programs were designed to do. Everything you did, functioned as it was supposed to.
If this is not what you want, then you might try reflashing your device with the last ROM you got from your carrier and see if that restores everything.
I did just that, and I did flash the device with the "virgin" rom which I have uploaded to wiki. But somwhere along the line something just does not jive. While preforming a hard reset the device would normally auto config itself with all the junk that the telco has put on the device including a number of patches and what not. That function does not run anymore, which is what causing me grief. If I unhide the ROM I can see the files that are supposed to run, including the autoexec.exe all there. I try to unlock to copy these files and run them manually but I am not allowed to copy them anywhere. and while I try to use EXTTOOLS.exe to unlock the ROM thing just go south. It says that the ROM is unlocked but I am still not able to copy any of the files from the ROM.
szamot,
there is nothing availble yet for our phones to update them or make them any better...
I can't believe you tried messing with your harrier... just wait a while until sprint releases their update to the ppc6600. (fingers crossed) we should be able to do something then...
all of the roms you see here (so far as far as I know) are for gsm units, and their roms will NOT work with our cdma's. WAIT!!!!!
Hopefully you can get things back to normal.. otherwise your gonna have an expensive pile of nothingness to work with.
good luck.
as i side note wiki has 4 cdma roms.
Actually I uploaded the rom because it seemed to be the newest one at the time.2.04.00 WWE, I also upgraded the BT to xxx.3900 which all worked fine. However somwhere along the line the Ext Rom got screwed, even though I can see it I can't get at it. Not all is lost however I just procured the contents of the rom from a new device, and even though I run all the fixes and updates and patches the PPC still runs like crap. Even hard reset does not get the unit back to its original state.
Related
Does anyone know if doing this will make the phone a brick? I am daring to do it, but hesitant because I cannot find a launch rom from Verizon to go back to.
Mike
I would not recommend doing this, there are some major differences in how they work there networks, and you will probably brickafy your phone. It's best not to try.
but what if you use the unbranding trick (hard reset after you flash, soft reset before carrier customization begins)?
anyone treied this? anyone WILLING to try this? i will supply the sprint rom if needed!
With all the ROM swapping we did on the 6700 it seems like it should be possible. As long as just the CE ROM is updated and not the Radio ROM you shouldnt run into any problems. The Extended ROM may need some select customizations (removals from the Verizon, additions from the Sprint) but that is cake once the CE ROM is updated. My guess is all that would be needed is an MaUt_NoID ROM updater for the 6700 like we had for the 6600. I don't have a 6700 as of yet so I can't help you but I'm upgrading from my 6600 soon and am definitely interested in getting this new ROM working for other carriers
I'm pretty new to the whole PDA world, so I am still gathering some basic info. I have a Sprint PPC 6700 I would like to convert to the Verizon network, and it is already a brick. When turned on it shows 'Serial' at the top of the screen until it is plugged into the USB, and then it says 'USB'. At the bottom it reads 'v1.00'. I assume this is the bootloader screen, but what I need to know is how do I get a rom to install. I would settle for getting this thing back to factory.
put it in the cradle with power and run the Rom Upgrade Utility
That won't work because in its current state, Active Sync does not see it. Windows sees it and recongizes it as a CE device, but that's it.
try using WinRAR to open up the installer and run the EXEs it contains one by one (I think the one you'll need is MaUpgradeUt.exe or something like that
I'll give that a try this evening. Thanks.
I tried that, and it tells me that the ROM image is corrupted, and I need to download the proper image for my device. I have tried both updates with this with no luck.
hi
I tried to upgrade my pda2k to 2005, but I get hang
then when I tried again it show this message
http://www.600kb.com/uploads/20aac64ad6.jpg
can i get help please
sarab
Strategies for dealing with radio ROM update 114 errors
I had this problem last week and recovered from it. At first it looked pretty bad, nothing seemed to work. I looked the Internet up and down and in most forums, including this one, people agreed that nothing could be done about error 114, the mainboard of the BA needed replacement, etc.
When I finally did fully recover from this situation, it was from a combination of measures that I took and as I don't really know which one actually did the trick, I'll try to describe all of them even though not all will probably apply to others. Another problem is that I probably won't be able to remember them all, but anyway, here goes:
1) I downloaded the latest full official ROM update from site of the carrier this phone was branded for, in this case T-Mobile. It included a radio ROM, albeit version 1.13.0, not 1.15.0 which is the one I had been trying to flash. I decided it would be best to go back to that official version first.
2) I had been trying to do the radio ROM upgrade from a Macintosh (OSX) under Virtual PC. I have since done several ROM installations (without the radio part) from the Mac/VPC which worked fine, but since people had observed that radio ROM updates seem to be more sensitive than fiddling with the normal ROM, I decided to fire up my "real" PC, which runs WIndows XP, SP2, with Active Sync 4.5.
3) As others had suggested, I made sure that I had my cradle connected directly to a USB port on the computer; before I had been trying to go trough a hub. I also made sure the cradle was connected to the power adapter.
4) I had unlocked my device before to work with a non-T-mobile SIM card, but since I wasn't sure wether or not SIM/Net lock problems might still interfere with radio upgrades, I took my SIM card out of the unit, as well as the SD card -- trying to eliminate as many potential sources of screw-up as possible.
5) I think I tried to set my BA into as much of a defined state as I could by hard-resetting it and THEN invoking boot loader mode. I don't remember whether or not this was possible as the device was not reacting much to anything at the time.
6) On the Windows PC, I opened Active Sync, then went to Connection Settings and explicitly disabled the USB connection. I then quit Active Sync and invoked the Windows task manager (Ctrl-Alt-Del) to check that no other processes were running. Trying to cut out interference as much as poosible ...
7) I then proceeded to flash the official ROM version, which went flawlessly including the Radio ROM, took less than fifteen minutes in all. To be honest, I don't remember which ROM upgrade utility (BaUpgradeUt/MaUpgradeUt_noID) I used ... sorry. I know I tried whatever was included with the T-Mobile download first.
After that, I verified that everything was working again, then immediately flashed Radio ROM 1.15.0 as I had originally intended. This time it went uneventfully.
Hope some of this helps, I know how frustrated you must be at this point.
Good luck!
thanks a lot
i'm going to follow your instruction today.
regards to all
[email protected] said:
thanks a lot i'm going to follow your instruction today.
Click to expand...
Click to collapse
So did you have any luck?
Aloha everyone,
I have tried to not post for about 3 weeks but I just can't move forward. I have read and tried to follow everything on the site but I am just confused. I know this is a developers site and I am very intimiated to be castigated by you guys but...it's the internet so what the hell.
I have found numberous instruction threads pertaining to updating ROMS on the Wizard. It seems that up until recently there was only one way to do things but now there are many. As I try to answer questions I come into conflict over which way I shoudl be heading.
I currently have a working WIZ100 that boots with IPL 2.21.0001 SPL 2.21.0lip with GSM 2.25.11 and OS 2.25.11.1. I somehow got to this point, I think by following the instructions to get hardSPL on my device and booting on startup. I did not know if I next needed to find a ROM and if so then how to get that ROM activated on my device or what programs to do this with. I know that the threads spell it out but the threads pertain only to direct assumptions; the assumption that my head is not in my ass.
I wanted to attempt to put a new rom on here, for fun and to play around with something new. Perhaps increase reliability or to get WM6 going. I am stuck now though. Part of me wants to turn back and load the original ROM from the HTC site and the other part of me wants to try a new ROM as I already have this thing booting to the 0lip SPL.
Is anyone out there willing to help me either via this thread, personal message or IM?
Since you have already installed Hard SPL you should be safe to go ahead and pick virtually any ROM you choose on there. I don't have a lot of experience with Hard SPL yet, except for installing it on my kaiser, but the one thing I would guess that you should make sure that the ROM you want to flash doesn't have would be an IPL/SPL update included. As far as I know, I don't think any of the public ones that you find on here have them but make sure you read the chef of the ROM's entire post to make sure. And, if you magically happen to find my ROM somewhere, which you shouldn't since I only gave it to 2 people to try, don't flash it because mine does include an IPL/SPL update.
From my best understanding you have already loaded HardSPL and now are CID unlocked. If this is the case then I would recommend going forward and flashing a new rom to your device. Just go to the Wizard Mobile 6 thread and find one you like, and flash it.
Simple as that.
I appreciate your replies.
1) I am clarified like butter! What program do I download and use to flash the ROM to the Wiz, this has been a source of confusion for me.
2) If I download and install the HTC Cingular ROM from HTC, will that overwrite the HardSPL and return my phone to Factory Default, including the radio areas? In other words do I rid myself of 2.21.0lip?
Thanks for not beating my head in...very polite you devs are...
I like beating people's heads in, and you are far too polite, that I am actually having a very slight guilty twinge! Damn you. I have a G3 myself so I cannot help much, however, I found this sticky which may help.
http://forum.xda-developers.com/showthread.php?t=332320
I do know that once you choose your rom, you open the folder and run the item marked as ruu.
Now if you only had a G3, then I could fry you like the noob you are.
I suppose at some point, I should make a point of reading/learning about G4's. I know they are a far different animal from my G3.
That's the reason I said not to flash a ROM that contained an IPL/SPL upgrade since there is the possibility that it may overwrite Hard SPL, although I'm not positive of that, but better safe than sorry especially if it it's not an official ROM that carries the correct IPL/SPL format for a G4. If it doesn't contain the correct format for a G4 it could ruin your phone. If you flash an official ROM though and it overwrites it you can always just reinstall Hard SPL again and keep flashing. I hope this makes sense.
As for the files you need to flash a new ROM, they're usually included with the ROM. If they're not then just let me know and I'll upload them for you.
Good that you asked before damaging your (expensive) device...
Every Flash version comes with a RUU (Rom Update Utility) you just run that proggy and it does the rest.
To make it easier, look for a rom that states it's G4 safe (no IPL/SPL included), so you don't have to mess around with the inner files. If you want to, begin your tests with the TNT series, the latest build, stated in my sig is G4 safe, after that you'll be able to know the initial procedure.
Good Luck.
Thanks for the info.
Do I execute the ruu from Windows XP or from the SD card ont he device?
Why am I have a hard time searching for and finding TNT 5.2.1921 TouchFlo ROM?
The rom update utlity gives me an error when I try to update. Should I try to do all this from the sd card?
Well, I am plugging along. I rebooted after an error 300 came up on the rom utility. Any suggestions for me?
I found this thread, back in business, thanks for your help guys.
I guess my only unanswered question is...if I use the HTC ATT exe from htc.com will it kill the hardSPL and restore the computer back to normal?
If you have ROM on your desktop, Connect your phone to your computer via USB, open up Activesync, uncheck the check box in settings that allows USB connections. Make sure you have at least 50% battery, then put your phone into bootloader mode. (soft reset while holding down the camera button- keep holding the button for 5 sec.) a tri-color RGB screen should come up. This is boot loader mode. Then run the rom update utility program, and everything is automatic from there on. once it is done flashing the phone will restart itself.
Thresher said:
I found this thread, back in business, thanks for your help guys.
I guess my only unanswered question is...if I use the HTC ATT exe from htc.com will it kill the hardSPL and restore the computer back to normal?
Click to expand...
Click to collapse
Try it and find out. I'd kind of like to know the answer to that one too, although my phones a G3 and already CID unlocked anyway. You can always reinstall Hard SPL over again if it does.
So this worked out well for me overall. Installing HardSPL to my G4, and then using a correct bootloader with the right ROM (to review).
I am having one issue.
I have the OEM ROM, however the RUU gives me an error. Is there a documented way to restore the phone to an original status? Is it even necessary?
I ask due to problems since my upgrade to the TNT rom. I am noticing a lot of missed calls and people have complained. Is this an issue with the 8125 and the particular ROM?
I don't know what to ask, or how to search for this. Thanks for any input you can offer.
Otherwise the TNT rom is awesome. I do miss the voice dialing though. Thats another search.
Actually, that's usually an issue with your radio version. Try using either version 2.19 or farias 2.69 and see if that fixes your problem. You should be able to find both of them in the wiki and you may want to try both of them and see which one gives you the better reception because sometime one will work much better than the other for you depending on your location.
By the way, you don't have to be CID unlocked or have hardspl installed to update your radio so you shouldn't have an issue with the RUU giving you an error. If you do, let me know and I'll upload a different RUU for you to try.
xeno1 said:
Actually, that's usually an issue with your radio version. Try using either version 2.19 or farias 2.69 and see if that fixes your problem. You should be able to find both of them in the wiki and you may want to try both of them and see which one gives you the better reception because sometime one will work much better than the other for you depending on your location.
By the way, you don't have to be CID unlocked or have hardspl installed to update your radio so you shouldn't have an issue with the RUU giving you an error. If you do, let me know and I'll upload a different RUU for you to try.
Click to expand...
Click to collapse
So the Rom is broken up into major parts. Those parts must ineract with one another, so that would be why my radio version may be at cause?
Yep. The ROM can contain the IPL, SPL, OS, Splash Screens, GSM (the radio), and extended ROM, any of which can be changed or upgraded individually without affecting the other parts of the ROM (for all intents and purposes anyway). That means you can change your radio version without it deleting all of your settings or your installed apps in your OS, etc etc.
Since you still upgrade each individual part using a RUU that is able to update any of the parts you still get a warning when you run it that it will delete all of your files, but as long as the update that you're running doesn't include a new OS you can ignore those warnings.
I decided to back out of the entire upgrade and move back to WM5 Official Cingular HTC ROM. I am stoked that I now know the full process of taking a G4 through hardSPL, ROM updates and restoral.
I was too scared to try any radio updates or fixes. Maybe when I upgrade phones I will come back to playing with the 8125 but for now, I just need a good functioning phone for work.
Do these Cingular radio fix cabs apply to a standard phone or only to upgraded ones?
Here is the deal: I was running the leaked WM6 ROM for ATT, I tried to downgrade to WM5 again, but my device got bricked, it was always failing to finish the update.
so, i ran the recovery tool from PALM, and it came back up but...when I go into the settings, there is no software version listed, basically just some little squares characters. But I still tried to run the WM6 updater but it keeps saying "device unsupported". After reading many threads on this forum, I went ahead and changed the payloads.xml version from 1.13 to 2.25, and still no result.
Any other ideas? I have also tried the SD recovery or updater and nothing, the bootloader screen doesn't give me the option to start the upgrade and when I go back into the SD card, i see a PALM.o and .h file, meaning that the system tried to compile it.
Of course, the card was formated several times into FAT32. Bad card maybe??
So, what should I do?
thank you
Sounds like you've tried about everything known to the Treo. There are some other things that may work in the other HTC threads, but no guarantees and may make things worse. Since you got it back to WM5, can you warranty it? Not sure how long you've had it (what carrier/country you're in), but always worth a shot to go to your provider's store and see what magic you can work.
Good luck mate!
Some days ago, i've flashed my phone to get an "up-to-date" ROM. I chose "PDACornerIllusion 21139" of 2009.03.06. All went fine excepting the keyboard of my GPS wont work anymore (dunno why of course), so i re-flashed with another ROM.
I was surprised that my phone kept the CornerIllusion BootScreen, but i didnt care.
All of a sudden, after having soft reset the ROM i chose (the 2nd one), for an installation of some proggie. The ROM restart as brand new asking me to reset the screen, the clock, date etc... losing all my content and customizations. Then i couldnt sync with Outlook after the first sync i've done minutes ago (error code 800004005). I've decided to soft-reset the phone, and now, TF3D wont even start, (it selft tries to start several times, then gives up), AND the programs lists is all broken, no shortcuts left and the games folder is named *h1/4Eg+ç^, nothing works anymore.
I flashed with about 4 roms (including Aztor one), resulting in the same mess.
Does it have something to do with the first one "PDACornerIllusion 21139" and its still remaining BootScreen?
Can i flash my phone from its roots, to get rid of this ?
As it's maybe not the "fault" of PDACornerIllusion, i write this in this section of the Diamond general thread and made a double post at PDACornerIllusion development thread
I suggest you perform a hard reset before flashing any new rom and that you use the traditional "flash-from-PC-using-ActiveSync-connection" method to flash.
And above all I wish you luck!
What was the other ROM you flashed? I am curious.
rondol1 suggests you hard reset prior to flashing a new rom. I suggest you hard reset after flashing a new rom. Net result is probaby much the same. You could even just do a hard reset now with whatever is loaded and things will probably improve. Main thing is...whenever you flash a rom do a hard reset straight after loading it. I always do this religiously and with the exception of one recent rom I tried I have never had a problem.
First of all, thank you both for trying to suggest hints, i really appreciate it.
I've never hard reset the ROM before or after having installed a new one. I never have a problem before.
For the last 2 months, i was on NEON 1.28, then i've decided it was time to update seeing the new features of the more up-to-date ROMs
I've just reflashed it (an hour ago) with PDACornerIllusion 21139, i've hard reseted before and after. let's see how it turns out ....
I've tried NATALY, CLOUDY, MORNA & AZTOR, no luck with any of them, all died after a soft reset or after the 1st sync (reconnecting for a 2nd sync).
Maybe the problem comes from the very root of the phone (like BIOS in a PC, dunno), maybe something in there got corrupted. How to repair it if my guess exists and is it repairable?
dunnno said:
I've never hard reset the ROM before or after having installed a new one.
Click to expand...
Click to collapse
There in lies the problem.
I bet you will be fine from now on. Don't ask why you need to do the hard reset - as no one has been able to give a definitive answer - But it is a well known step that many chefs recommend post flash - just do it from now on and you wont regret it.
logger said:
There in lies the problem.
I bet you will be fine from now on. Don't ask why you need to do the hard reset - as no one has been able to give a definitive answer - But it is a well known step that many chefs recommend post flash - just do it from now on and you wont regret it.
Click to expand...
Click to collapse
completely agree with logger - hard reset after you flash any ROM. I haven't used PDACorner - so can't say for sure... but do the flash via CustomRUU once... when the new ROM is flashed... do a hard reset as soon as it's complete..
good luck!
let's see then, >>>>crossing fingers<<<<
I've had this happen a lot lately as well. Might have something to do with the newer SYS? Anyway, hard reseting hasn't always fixed it for me. However, flashing back to the Sprint stock ROM (or HTC stock for you GSM guys) then flashing a new custom ROM has always done the trick. Maybe because the stock ROMs are bigger and "clean" out the memory somehow? At any rate, flash stock and then you're good to go. No permanent damage.
no luck, after a 2nd soft-reset, the phone is asking "touch the screen to configure for the 1sy use blablabla", all data's lost again & again...
what do you mean by stock Rom ? the rom that came with my phone when i've bought it ?
I've got the same problem with the Diamond rebooting like a hard-reset. But I always did a hard-reset after a fresh install. I blamed it on the rom and tried several others, including donsalari's "Clean Basic Rom", the Gen.Y Sense 2.1 and 2.5 versions and an older Aztor rom. Same problem every time, the first reboot after changing the device locale works fine, then I set the whole phone up properly and on the next reboot it will come up as if had performed a hard reset.
Additionally, the file system on my internal storage got corrupted somehow, had to reformat. At some point, I also had the impression that data on the phone memory got lost gradually. First the Contact's numbers got replaced by some nonsense characters, then there were numbers and contacts missing, and finally I had no contacts at all. ActiveSync stopped working so I was in the middle of a trip without my phonebook...
I've got two hypotheses:
1) The Gen.Y bootloader messed with the phone (Had tried the Sense 2.5 Gen.Y rom before donsalari's)
2) Flash controller or Flash itself is broken
@dunnno: I suggest you rename the thread to something like "diamond hard-resets on 2nd reboot after rom install"
edit: oops, just realised I resurrected a very old thread... Maybe there's a fix already?
My diamond still suffers from this problem. I tried it again and again with different roms but everytime, at some point all my configuration is lost and the diamond reboots like after a fresh install. Can anyone please help?
I'm having this problem as well :|
Grr, I have to rely on my phone for so much, but it just doesn't want to work correctly.
Help is immensely appreciated.
Well, I got mine to work, I just flashed the stock HTC ROM and everything has gone back to normal. H3PO, I suggest you give that a shot if you are still having problems.
I had these problems when I first started flashing my Diamond with custom roms.
Now I always flash my carrier stock rom first, then hard reset, then flash custom rom, then hard reset and I never have any problems. I have no idea why flashing the stock rom first stops the problems but I haven't had any problems with the dozens of roms I've flashed using this method.
Also I always flash from internal storage, but others prefer using MTTY
I still have some problems with the Contact Database, but flashing some stock O2 Rom solved the "reboot as new" problem.