Apologies in advance for the newbie question.
I have a new SPV-M5000 locked to Orange. I think I have all of the files that I need to unlock it, and using all three hands I managed to get it into bootloader mode, but when I try to run MaUpgradeUt_noID.exe I get the following error: "MaUpgradeUt_noID.exe is not a valid Win32 application"
I hope that I am making some kind of really dumb (and therefore easily fixable) newbie mistake here. Any thoughts?
Thanks in advance.
Upgrade utility
Hi.
I have the same issue and posted the following on Buzz's site (buzzdev.net) over a week ago but have had no replies. Hopefully someone with an answer will reply to you here?
Quote:
Having read pretty much all the forums on Universal software optimisation starting with craigiecraigie4's excellent guide at http://forum.xda-developers.com/viewtopic.php?t=31697&postdays=0&postorder=asc&start=0 and extensive reading on the wiki site and of course Buzz's brilliant work throughout this and other sites, I finally feel ready to take the plunge with updating my new o2 xdaExec using o2's 1.30.107 WWE ROM, Dopod's 1.11.00 Radio and my own Extended ROM creation (yet to be made as I want to do 1 bit at a time). I thought I'd put Jasjar's extended ROM (164 I think) on until I have got use to modifying the Ext ROM image as I want.
However, I need to use Buzz'y MaUpgradeUt_noID.exe program as the standard installer is telling me there is a country error. Fine, so I have that downloaded BUT when I try to run it, my Windows XP system tells me that it is not a valid win32 application. Am I missing something here? Have I downloaded the wrong program or is there a problem with my XP? I don't appear to have this problem with other programs.
Hope I have included enough info for someone to tell me where I am going wrong.
HELP................
Unquote.
I have just downloaded a version from this forum (about half way down) - I haven't had a chance to test it yet but it IS different and if I run it without connecting my Universal, it does run the program but fails as no PPC device connected so it may be the better version. I will try it tomorrow but if you test it first, let me know
http://forum.xda-developers.com/viewtopic.php?t=54210&postdays=0&postorder=asc&start=25
O.K., that file seemed to do it.
I have now flashed my ROM with the latest non-Greek QTEK build, UNI_QTEK_13077_176_10900_WWE_Ship.exe, and then copied UNI_Unlock_v1.exe onto a SD card and ran it. I got a successful unlock message.
However, when I put my SIM into the phone, it booted up to a plain screen with a title bar of "Simlock" and the following message: "Network is locked, Please input unlock code".
Did I miss a step somewhere? Is it possible that the SIM itself could be locked (it's a brand new Cingular SIM) somehow?
Yes you did miss a step, in fact you missed lots of steps.
Go back and read the readme.txt file that came with the unlock program, everything is explained very clearly in there what you need to do!
This may be the wrong website to address my problem, but someone here can help, I'm sure. TIA!
I'm dual booting xp sp3/ubuntu 9.04 and can't install the CeCabMgr. Every time I double click it (in xp, of course) it says that another uninstall is pending and to restart the computer, to allow it to finish (which I've done 5 or 6 times) and when I go to install CeCabMgr again, I get the same message.
Does anyone know why or how to fix it?
And/or would someone who has CeCabMgr please just repack the IIWPO cab with my info in it for me? TIA!
OOps, double post.
Downloaded and used Cabintegr to be used on the ppc itself. A little more difficult beacuse of how ppc's are, but a pretty good program.
Anyone ever found a solution to this? I can use it under Windows 7 but under XP it states that a installation is pending. It must somehow find something from the Windows 7 Installation. Its annoying because Photoimpact stoped working under Windows 7. Now I need to keep switching back and forth. Used Filemon and Regmon without finding a way to circumvent the check and force the installation.
Help!
I was messing around with the Ubuntu on Rhodium stuff that's posted in the Android sub-forum and I think something got corrupted/overwritten on my phone...
I extracted all the files on to a freshly formatted card and ran haret and everything worked file and I eventually got to the Ubuntu desktop. Then I did a soft reset to get back to WM and then the problems started.
I cannot run any unsigned apps whether they are installed on the storage card or internal memory. Whenever I try and run an app I get an error saying "The file blah cannot be opened either it is not signed with a trusted certificate...".
I cannot get back into Android or Ubuntu coz haret is unsigned too.
I cannot even install new apps! When I run the cab file, I get the usual "This program is from an unknown publisher..." and when I select yes for continue it immediately comes up with "Installation of blah was unsuccessful."
Time for a hard reset? I'd really prefer not to if anyone can suggest a better way of getting my phone back to how it was.
R.
Tried installing this?
As I said in my original post, I cannot install any CABs that come from "Unknown Publishers" too and it seems that TP2-AppUnlock is one of those.
Thanks for trying,
R.
there is a setting somewhere for this. i saw it the other day while setting up a new rom.pretty sure
same problem
I have encountered the exact same issue...except that for me it occurred after booting back into WM after trying out the latest android build. Anyone have a solution?
dicko99 said:
Help!
I was messing around with the Ubuntu on Rhodium stuff that's posted in the Android sub-forum and I think something got corrupted/overwritten on my phone...
I extracted all the files on to a freshly formatted card and ran haret and everything worked file and I eventually got to the Ubuntu desktop. Then I did a soft reset to get back to WM and then the problems started.
I cannot run any unsigned apps whether they are installed on the storage card or internal memory. Whenever I try and run an app I get an error saying "The file blah cannot be opened either it is not signed with a trusted certificate...".
I cannot get back into Android or Ubuntu coz haret is unsigned too.
I cannot even install new apps! When I run the cab file, I get the usual "This program is from an unknown publisher..." and when I select yes for continue it immediately comes up with "Installation of blah was unsuccessful."
Time for a hard reset? I'd really prefer not to if anyone can suggest a better way of getting my phone back to how it was.
R.
Click to expand...
Click to collapse
Just found this thread that is supposed to fix the problem: http://forum.xda-developers.com/showthread.php?t=404170
I've already hard-reset my phone so I can't test it...
I too had the same problem but with the HTC hd2. I was trying out a 2.2 rom n the camera wasn't working so I turned off the phone, when I tried going to back android haret wouldn't run .if anybody has a fix to this please let me know.
Hi there,
Have you tried the "Security configuration Manager" mentioned in the thread linked to above?
I can't test it coz I haven't broken my phone again since the initial issue but for future reference I'd like to know if it cures the problem.
Hope this helps,
Richard
Yes i've tried security configuration manager but it still wouldn't work. Does doing the hard rest work? Thanks for the help
Yes, hard reset works.
I've used it on two occasions to fix this problem.
Regards,
Richard
after using config manager i cannot sync with outlook
i am still having the issue with certificates after runnig android and rebooting HD2
any help?
i am in mexico HTC HD2 unlocked if i make a hard reset i am going to loose unlocked feature right?
UPDATE 274/2012
Okay. So, Nokser's FFUPartTool extracts the IMGFS partition from the FFU.
Barin's OSBuilder (here) can be used to dump the contents of the IMGFS.
The registry files can then be edited in HVEdit (link), and the IMGFS can be recreated using OSBuilder.
FFUPartTool can then be used to replace the IMGFS partition in the FFU.
This FFU now needs a Mazaa to be flashed on.
If anyone out here is brave enough to flash their phone, please report the results!
UPDATE 17/4/2012
So, as we all know we have a stock mango FFU for the Mazaa (see here if you don't).
And due to recent developments, we also have this: FFUPart Tool v1.3.1
What this means is, we can create a custom FFU for the Mazaa. Now, personally, I have never created WP7 CFW before, but Nokser, the creator of the tool above assures me the creating CFW with this tool is quite possible.
So, what are you guys waiting for? Race to the finish line?
My list of things to be done starts and ends with this: get htc connection setup to run.
That's literally all we need to kickstart the Mazaa scene. Once we have that, we can do the whole shebang.
We need a ROM image for the Mazaa before anything at all can happen.
-------------------------------------------------------------
Here are the ROMs being used by people:
7.1.7649 - Test Rom. Has lots of interesting Microsoft applications (the zApps). But lacks quite a few features and stability.
7.1.7661.wp7_5_trial(mojobld).20110607-1657 - Similar Test Rom.
7.1.7720.68 - Locked bootloader. Phone is recognized as an HTC Device, but Connection Setup doesn't run.
7.1.7720.500 - Is basically the same as .68 but with an unlocked bootloader. Phone is not recognized as an HTC Device.
7.1.7740.16 - Updated via the official CAB [WP7 Cab sender tool]
7.1.8107.79 - via the official CAB [WP7 Cab Sender Tool]
7.10.8773.98 - via the official CAB [WP7 Cab Sender Tool] - 28/06/2012
Firmware revision number: 1600.1502.7720.68
Hardware revision number: 112.1410.2.0
Radio software version: 1.6.00.15.02
Radio hardware version: 8655/DDR2
Bootloader version: 7.27.00
Chip SOC version: 0.75.2.1
If anyone has different details, please post them.
-------------------------------------------------------------
The major problem with all ROMs is the lack of drivers.
1) LED lights don't function
2) SD Card slot
3) Connection Setup drivers
4) Internet Sharing doesn't work
Secondarily, because of the lack of connection setup drivers, there's no interop unlock. Which means no homebrew. Which means this device is pretty much what a technophobe buying a smartphone for the first time needs.
-------------------------------------------------------------
Does anyone know how to edit FFU (full flash update) files? They seem to be .cab files with a signed xml .blob in them.
Is there any way to edit these files?
Alternately, has anyone been successful at obtaining a stock ROM for the Mazaa? Because otherwise the device is extremely crippled.
Once we obtain a stock ROM, it's merely the point of identifying what drivers are missing, appealing to the DFT team to test the Mazaa to check whether HSPL/RSPL works, testing whether HTC Trophy drivers (and maybe other phones' drivers) work, cooking a rom, and flashing it. Once we get the ball rolling, it should all materialise.
-------------------------------------------------------------
Finally, what other problems are people having with their Mazaas?
Here's a list of problems I've noticed across the net:
Low battery life (4 - 6 hours at most).
Inability to connect to CDMA networks
Can't use HTC Connection Setup - hence no 3g/mms on certain networks
Inability to connect to certain GSM networks - lack of a valid IMEI
Frequent restarts/hangs [2 - 3 per day in some cases]
Each of these are frustrating faults.
Here' to hoping that the hundreds of DEVELOPERS with Mazaas can put in a concerted, collective effort and get this going. EVERY other phone has been unlocked/tweaked/improved upon, so why not a limited edition developer-exclusive device?
Thanks for summarizing the various versions. As developers, with a concerted effort, we should be able to resolve the issues and make it work for us.
I think most people sold the device, even if this wasn't allowed, at least for the first batch (not those won, but those requested for mango/gyro dev)
I had hopes battery problems where in a faulty battery...
even if they're sold, someone's still using them!
And the battery problems were too widespread (more than half a dozen cases) for me to discount.
the IMEI problem on the other hand was in a single case - mine.
abhilaksh said:
even if they're sold, someone's still using them!
And the battery problems were too widespread (more than half a dozen cases) for me to discount.
the IMEI problem on the other hand was in a single case - mine.
Click to expand...
Click to collapse
That's right, but they're probably not in dev hands anymore, so chances are not very helpful hands at this, especially since there's no more access to official updates.
All summed up, since not even the gyro works correctly on mine, it's a paper weight for which I'm still waiting for import taxes refunding
As far as issues, in addition to the above:
- I cannot send/receive MMS (SMS works, though)
- No 3G (DO or 2x only)
- 2-3 crashes per day
My build is 7.1.7720.68
Sent from my Mazaa using XDA Windows Phone 7 App
I have HTC Mazaa
I have the HTC Mazaa device that exactly matches all the details given in the original post in this thread.
For me, its working perfectly, no battery problems (works for 2-3 days), no crashes at all, I can't say about 3G support problems because we don't have that in our country. The phone works perfectly fine.
I have dev unlocked the device from App Hub but would love to remove the interop lock as well...in fact thats what I came here for.
Please guide me.
Thanks.
When I first got my cdma provisioned Mazaa, it had a 7.1.7600_Main build on it. This was like the test ROM - it had the zApps. Looked to be the internal Microsoft beta for employees. I think everything worked on that, just Mango was crippled.
Does anyone have this? I flashed the ffu and the backups can't restore. It would be an interesting starting point if the oem bits are all there.
Sent from my Mazaa using XDA Windows Phone 7 App
Please guide me on I can interop-UNlock the device.
How can I update my Mazaa to 7.1.7740.16 build?
Mike48236 said:
When I first got my cdma provisioned Mazaa, it had a 7.1.7600_Main build on it. This was like the test ROM - it had the zApps. Looked to be the internal Microsoft beta for employees. I think everything worked on that, just Mango was crippled.
Does anyone have this? I flashed the ffu and the backups can't restore. It would be an interesting starting point if the oem bits are all there.
Sent from my Mazaa using XDA Windows Phone 7 App
Click to expand...
Click to collapse
Hello there,
Currently I'm using a Mazaa sent from MS with the 7720.500 fw, It has all the zApps and the internal MS apps like FindSomeone, it has battery issues (but it's not worse than an Omnia 7 with Mango), and there are four annoying things experienced:
- volume is always a bit too loud and MP3 playback is sometimes faltering
- when you press the ON/OFF button, sometimes the screen comes back immediately after turning it off
- when you place a call, sometimes the screen turns off immediately, which can be brought back using the proximity sensor (hold close to head, then move it away)
- cannot receive MMS messages
Exact details:
OS: 7720.WM7_Main(mojobld).20110723-1640
FW: 1600.1502.7720.500
HW rev: 112.1410.2.0
Radio SW: 1.6.00.15.02
Radio HW: 8655/DDR2
Bootloader: 7.27.0.0
Chip SOC: 0.75.2.1
I'm no expert in messing with phones (only using homebrews once they become 99.999999999% safe) but if I can help in any ways I'm not breaking this phone, I can surely do my part provided I'm given step by step instructions.
To update to 7740/8701:
Use the WP7 update cab sender tool here
Okay. So, let's get this sorted: We need a ROM. MSFT has said ROM. We need MSFT to give us the ROM. So, I'm requesting everyone: Send a message to whoever your contact is in Microsoft and let them know of the many problems that everyone is facing. At the very least, ask them to provide new radios to get rid of the hardware glitches. Granted it's a test rom, all the more reason that they should actually be working on it. A phone that doesn't work as intended is more a burden than not.
abhilaksh said:
To update to 7740/8701:
Use the WP7 update cab sender tool here
Okay. So, let's get this sorted: We need a ROM. MSFT has said ROM. We need MSFT to give us the ROM. So, I'm requesting everyone: Send a message to whoever your contact is in Microsoft and let them know of the many problems that everyone is facing. At the very least, ask them to provide new radios to get rid of the hardware glitches. Granted it's a test rom, all the more reason that they should actually be working on it. A phone that doesn't work as intended is more a burden than not.
Click to expand...
Click to collapse
I'm sorry but I'm not going to be of any help in getting an updated ROM, since we are low on the supply chain. Also, the way we get each new build is by getting a new phone. (Send back old one, get one with newer software.)
I have an HTC Mazaa, running 7720. Everything is ok for a dev phone, I have no serious problems with it, except EDGE/GPRS not working and speaker emitting a loud tone when I'm calling a number outside my network. I'm thinking of installing the new updated build. How should I proceed exactly? Should I use the cab sender tool? I also want to mention that the phone is not dev unlocked, I'm still waiting for a student unlock. Thanks.
download the cab sender.
download the cab.
place the cab in the same folder as the cab sender.
run the cab sender.
send the cabs to the phone.
you're done.
I tried to update my HTC Mazaa and I got an error at the first restart. But, after that I typed *#06# on the Phone hub and I get this IMEI: 00A100000794C***.
I did it again, but this time, with my SIM card inside the phone. Unfortunately, I got the old IMEI message: Failed.
***
Even after all could not update my smartphone:
Verificando o status do telefone: Completed in 2,01 seconds
Verificando requisitos do sistema: Completed in 0,11 seconds
Fazendo o download de atualizações: Completed in 2,87 seconds
Verificando requisitos do sistema: Completed in 0,01 seconds
Transferindo atualizações: Completed in 24,65 seconds
Preparando para instalar: Completed in 46,16 seconds
Reiniciando o telefone: Completed in 231,04 seconds
Instalando atualizações: Completed in 70,15 seconds
Verificando o status do telefone: Completed in 0 seconds
Reiniciando o telefone: Completed in 34,28 seconds
Concluindo atualizações: Completed in 20,04 seconds
Error:
Update device 53d261df - cd29c761 - 4fe43c2f - 733020be Complete with error code
: 80180048, error message: Falha ao instalar IU (Image Update) devido a um erro.
■
╚══════» Done
Is there anyone on xda-devs to help us update our HTC Mazaa and also do the interop-unlock?
Mazaa ROM
Hmm...
Here.
http://hotfile.com/dl/135477621/ed2186c/FlashClean.zip.html
That's an FFU.
Which cab should I use? Or which is the recommended one? Thanks.
Thankyou for that FFU
@abhilaksh Thankyou for that FFU file it saved me from alot of messing around. So happy to get my Mazaa back in working order. It broke on me a few months ago and ive been though hell trying to get the bugger fixed. It just got stuck on the mobile operator screen.
imgur(dot)com/oBH9M
Even had it sent off to UK repair center for them to send it back in the same condition (Idiots). I was just about to send it off to a US repair center when i did some more searching. It worked a treat, really straightforward as well.
If anyone else is a noob in the same situation as i way id recommend these simple instructions:
1. Install Zune Beta Client (beta includes the UpdateWP tool)
2. Install the SetupUpdateWp.exe to get the tool
3. Follow these instructions to flash your phone
mobilitydigest(dot)com/ms-instructions-on-how-to-flash-a-windows-phone-7-device/
Thanks again, Rob
I've been looking into modding my Lumia 640 WP10, and it seems like most if not all of the apps involved require deploying with Windows Phone Power Tools. When I try to use it, it tells me the phone needs an update, and launches the Phone Tools Update Pack which always results in this message: "The update operation did not succeed. You can press Rescan to try reconnecting to the device. The exception code and error message is: 0x80004003 - Object reference not set to an instance of an object."
I have not been able to find any information about this particular error, and any assistance would be very helpful. I have already set the phone to developer mode and been able to deploy the root tool, but have been unable to do anything else without the power tools.
Same problem
I think the newest update is buggy. I was trying to do the same and keeps getting the same error. This might help you.
I'm not sure why the forum only emailed me for the first reply so I'm a bit late seeing yours, DaRealAce. I am not actually using an Insider build right now but thank you, that link did help. It's definitely not the same problem, but I was able to fix mine by using the Interop Tools app linked in that thread. Since that is an appx I was able to sideload it, making vcREG unnecessary. After going through the unlock settings in that app, I was able to deploy the AdBlocker app (my original goal) using the regular WP 8.1 Deployment Tool rather than WP Power Tools, which did not work previously.
Oddly though, somewhere in the process the phone no longer shows up on the PC as a mass storage device.
the same