Related
Guys, my phone is dead and I need a little help please.
I have a T-Mobile MDA Compact II and have mistakenly (why it worked I don't know) 'updated' it with a Prophet firmware release. This progressed as I expected but was I since discovered completely wrong. My phone now shows a black screen with Dopod logo on boot and then hangs.
I have since found this site (looks good btw!) and subsequently the ftp area. I've downloaded the correct firmware for my phone, reset into the three colour screen and kicked off the Romupdater for the proper version I believe to be for my phone. With the 2 releases from ftp (one in that directory appears to be only half a zip file) they appear to be uploading but there is no change with the black screen problem.
I'm now stuck and am hunting for options. I'm more than happy to help myself but can someone explain what I need to do and start me on my way to fixing this.
All because it hangs from time to time when I run up too many apps on it.
Thanks in advance
Andy
Tell us what ROM you are using and which software you are using to perform your ROM update.
Anyway, it is weird that the Prophet ROM doesn't work on your phone. Keep this low tone, but I've done a Prophet ROM flash on my Charmer before. Everthing works well except the camera, that's why I flashed it back to the original ROM. I won't advise others to do so, there seems to be a few 'fatal' cases. I'm not sure, probably because it is compatible with the earlier Prophet version.
UPDATE: Nevermind, you seems to have the information. Good if you can stick to the same threat to avoid confusion. To others, please refer to
http://forum.xda-developers.com/showthread.php?t=275337&highlight=
At work and I've left the phone at home but I believe it was something like 2.3.15 (i.e. upgrade from v1 to v2)
Correction, it's SPL 2.15, IPL 1.12.
I have seen a post on Hermes bootloader access over USB using Mtty and now have access to the cmd> Can someone help me perform a bootloader based ROM downgrade to known working or deleting the image that is there?
Have now found the awizard utility, which file type does awizard need to be fed via the ROM directory?
Yes I'm a newbie at this and shouldn't have messed with the ROM update but I'm an I.T. guys by trade so if you can feed me the info I need I should be able to follow instructions
Phone is still 'dead' though.
It needs
XXX-OS.nba
XXX-Radio.nba
XXX-ExtROM (directory wit Ext Rom stuff)
You ought to get these from the FTP. I've myself uploaded a Charmer original UK ROM T-mobile, it should be still there is no one messed with it.
Hmm, I've missed something then. I put the .nba files into the ROM directory and then run awizard and hit w. Where I would expect to see a list of files with numbers there isn't any.
What I miss?
the dir structure of the aWizard looks like the attached, where you have the ROMs under the "ROM" dir and Ext ROM. Where the aWizard directory has the aWizard.cmd file.
Can someone provide a split up (i.e. seperated nbf files) for the Charmer or the correct memory addresses to punch into nb2nbf to create my own?
The images seem to have been removed from the FTP site and I'm in position to de-brick my phone!
Hello!
I recently bricked my MyPal A626. In the last weeks I tried several things but until now I weren't able to figure out how to fix this thing.
I know that you can flash the ROM via the USBLoader.exe over USB. But I need a .nb0 file for this.
Perhaps there is someone in this board who can help me out with this file?
You should be able to dump the rom with the itsutils over RAPI.
http://wiki.xda-developers.com/index.php?pagename=XdaUtils
It should be something like this:
1) pdocread -t
2) pdocread -l
3) pdocread 0x0 xxxxxx nk.nb0
One of the first commands gives you the length of the ROM.
I can't test it by myself because my device is bricked.
Perhaps it would be enough if somebody with an A626 can execute the first and second commands and post the output here.
It would be very great if somebody can help me!
BTW:
I have got a Backup... But the bootloader doesn't want this. It reads everything from USB but it isn't flashed. And I have absolutely no idea why.
I can upload this file to rapidshare if somebody wants to look at it.
I really hate to ressurect an old thread, but I am having the exact same problem. ASUS tech support has been rather less than helpful. They won't provide a NB0 file to end users, nor any fix tools that would work with the encrypted image or anything like that either. They told me I have to RMA the thing after passing me back and forth and giving me the runaround for about an hour or more even. Only, I STILL haven't gotten a response from the RMA department even... The person I tried to do this update for REALLY needs her PDA back already and I find this whole situation to be quite unacceptable. I only had to attempt to use the update in the first place because they made a screweup that makes the SD card inaccessable without reinserting after pressing the power button... A pretty big screwup IMO considering that good PDA practices really requires one to run as much as possible from the SD card for the sake of wasting less resources in a device that already has all too few resources to begin with... (Then again, MS still hasn't caught on to the fact that minimizing rather than closing programs on a device that has so little memory is rather less than ideal, so I guess there's nothing new in that area.) The funniest thing of all is that I wasn't trying to modify it or anything like that, I just did the update right by the manual needing only to get the SD card fix and it STILL went wrong (especially I find it annoying that the update process did a checksum on the update.img file and reported that the file was actually correct, then it fails AFTER completely flashing and doesn't bother to make any kind of recovery.
If anyone could help me out with a NB0 for this thing, I'd REALLY appreciate it. I just want to get it up and running again so she can use her PDA for getting organized as she has been desperately needing for so long.
BTW, should the OP ever read this, I have noticed that if you send the right things, it WILL try to flash. I once sent the update.dat file in the hopes that it might include information needed to make the flash work (it was my hope that the process was a little smart and that it would, therefore, use the DAT file for information on the flash and then include the needed image.) The device actually did make a flash with this file. Of course, the flash obviously didn't work, but the point is that it can do a flash through this method if you send what it's looking for.
GOOGLE this A696_dump_wm5_eng.rar
No good. All two links Google finds are dead (I see two different posts in two different forums, but actually each link to the same links and these are both dead.) I did see a reference to a "A696_dump_wm6_2_eng.rar" but it too is dead. (One of those two forums was this one, I see, surprisingly enough considering that the first thing I did was run a search as is evidenced by finding an old thread -- but then I must admit that I was searching for A626, not A696...) The next closest I can find through this search is a Russian dump for an A636N. I don't have an A636N and I can't read a word of Russian. That link is still alive, but I'm not even going to try it since even if it were actually compatible with the A626 (and I'm betting it's not) it still would be as good as a brick to me still.
But anyway, is the A696 ROM actually directly compatible with an A626 system?
EDIT: I stand corrected! The link for the 6.2 update on the A696 isn't dead after all. When I tried last night it would just spend a REALLY long time trying to load and eventually either time out or produce a database error. When I tried today though, it did sucessfully download. Looks like it does work. Thank goodness because the PDA's owner really needs a working PDA, and ASUS seems rather less than helpful...
Nazo said:
But anyway, is the A696 ROM actually directly compatible with an A626 system?
EDIT: I stand corrected! The link for the 6.2 update on the A696 isn't dead after all. When I tried last night it would just spend a REALLY long time trying to load and eventually either time out or produce a database error. When I tried today though, it did sucessfully download. Looks like it does work. Thank goodness because the PDA's owner really needs a working PDA, and ASUS seems rather less than helpful...
Click to expand...
Click to collapse
626,686,696 are same series.. aka. asus 6x6 or the cannes. if you go to asus website. there is a single rom for these 3 models.
what's the 6.2 update you are talking about ? anyway.. let me know if you still want the 6x6 wm5 dump file. I can upload it to somewhere..
Well, I went ahead and flashed despite worrying about model compatibility. I figured they were the same basic hardware, but I figured that it was always possible that there could be important differences such as memory latencies or such that could make it incompatible perhaps even to the point of danger. But, it's just the software end of things more than anything else, so I figured that it couldn't brick the PDA any worse than it was already bricked and went ahead. As you say though, I have noticed that you are correct that they do use the same ROM for all three models on the official site anyway, so it works 100%.
As for the 6.2, it's in the link I provided to a topic here on this forum. The only other result you'll find on google is just a site in Russian or whatever where they repeat the exact same links for each of the files so you might just as well use this one. It's hosted on MediaFire which was really screwed up when I posted that it was a dead link, but it seems to have recovered and I was able to download that updated ROM from there. I think that you may have to look on the previous page from the link I gave though.
I must say though, I'm glad to have found that one. I HAD to do the update. You see, it was more than just an update to WM6.2. It also included a lot of bugfixes. The most notable being that the system would no longer recognize the SD card after a suspend for a while (or several suspends -- I never was sure just which was the culprit.) Resetting or ejecting and reinserting fixes it, but she was having troubles with this because she isn't exactly the most technosavvy person I have ever known. The SD card dissapearing bug was a fatal flaw because she must load up things such as books and such via SD card and all of it together adds up to well over what can fit safely in internal memory and the file storage combined (but which easily fit an a 2GB SD card) and I needed that update, so if I had to get the WM5 ROM again I'd have to just update again and again as many times as it took to get past the bricking. This way I needed only load up the ROM once and that was it. ASUS really needs to create a tool that can load the encrypted ROM from a PC like HP has done (I've bricked my h1945 PDA while attempting to update it once before and was able to fix it quite easily just as soon as I figured out how to get into the so called "parrot mode.") and such so we don't have to resort to such means to fix them...
Anyway, now I need to get started on loading up all of the stuff she needs.
I just bricked my A363N - WM5.0->6.0 upgrade failed (SD card read error).
Now I'm trying to make it work again.
Russian WM5.0 doesn't work - stops on the calendar screen.
I wonder if I can try to upload update.dat file from the Asus wwe.rar
with SD card inserted and containing Update.img.
Is the update.dat file in .nb0 format ?
Is the A636 actually the same series? If not that post belongs in an appropriate thread instead. If it is, why are you trying to use the Russian update? Just use the plain English one. Here, it's in this post on this site: http://forum.xda-developers.com/showpost.php?p=1495484&postcount=126 I checked and the link is still alive right now.
Yeah, very cool.
I remembered this post 10 minutes ago.
I will try the 696 firmware... Lets see if we can get this ****ing machine running the moon
Meanwhile i tried several things with the update.img file. The "Encryption" is a simple xoring with 0xd0 ^^
But even if you xor the whole file with this value you still don't have a valid nb0. I tried it many times to cut out the firmware with an hex editor on the obvious places in the file (go and see yourself if interested) but all this didn't work.
edit:
It doesn't seem to work for me... The file gets flashed and the device reboots.
After that it still gets stuck at the blue asus screen but it is recognized by the computer as a RNDIS device.
another edit:
WOAH... I tried it again and now it works.
It seems that the battery was empty because of all the previous tries.
Unsuccesfull rom flash
Hello,
I bricked my 696 asus, trying to do un update from the asus site.
Can you tell me some methods to repair it, using the sd card, because the method with usbloader.exe and nk.nb0 is not working ("USB pipe opening error", I tried on several computer and many usb ports).
Also, how can I transform the nk.nb0 flashing image into a *.dio image (I understand the last one can be used to boot and repair automatically from the SD card, it is real???).
10x a lot
Still not working
any new idea to reflash rom foa a696 ?
Hello to you
any news about how to make rom upgrade foa asus a696 ?
Hi. I am relatively new with the PDA scene and as much as I would have loved to read an answer to my question from some other thread instead of starting a new one, I could not do it cos there are none. At least in "idiot's guide" style.
To the question that is stated in the title. As much as I have understood, there are (at least) three storage areas on a device (mine being Vodafone v1520) - the ROM, the EXT ROM and the files that we see on under "My Device" in Explorer. Some of the files have been marked as "ROM" if to look at the properties and those cannot be deleted (at least I haven't found any way) but they can be overwritten (with Resco or smth). The point of my question is that when I overwrite the WELCOME.GIF file (marked as ROM file, it's VF splash screen) it does overwrite it nicely (confirmed) but when I hard reset, it's back. Although I don't understand also why after overwriting I still see the VF logo instead of my own file, that is a separate issue.
The reason I am asking this is that nobody in this forum has been able to answer me how to unlock the EXTROM part on that ASUS P550 that I have. So I thought maybe if I change the STARTER.EXE or GENERALINSTALLER.EXE to something pointless, the EXTROM part won't be installed.
Although I suspect the VF logo is displayed from EXTROM part while booting, cos there is nowhere else that same file in normal storage.
Summary:
1) Does changing files marked as "ROM" really change ROM files or is it until the next hard reset and why?
2) Does anyone know how to unlock and unhide the EXTROM part on ASUS P550?
3) Does anyone know where the VF splash screen comes from while booting?
If anyone has ANY information on these issues, PLEASE enlighten me. It seems that there are a lot of senior members who have the knowledge but are quite unwilling to share it. I don't know why but it seriously sucks that they don't reply to threads or PM. I thought this forum was for helping each other, not giggling behind the screen: "I know something You don't". At least that is the impression that I have recently gained when trying to contact people that have the knowledge.
Thanks.
aiiro
The answer to your "stupid" question - "are ROM files REALLY ROM files" - is NO.
The question is not stupid and the files are really not the files.
Actually you have only the information about the files in ROM - the name, the size and other attributes. That's it.
You are not really overwritting anything when you copy the different file with the same name to ROM.
If you somehow dump the ROM from your device - you'll get real files.
Welcome Gif can permanently be changed only in dump.
Unlocking EXTROM .... I am not sure that I got what you mean. And why do you want to do that. But do the following: with Resco Registry go to
HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC2\FATFS
Change MountHidden value from 1 to 0
You will be able to see the EXTROM content.
VF splash screen definitely comes from Windows folder of your device while booting - it's a part of the ROM.
OK, thanks for a quite thorough reply, but I still don't get it then - why does Resco (or similar prog) ask to overwrite the file? OR, if it doesn't overwrite it, how do I see the new file in Windows folder and the prog looking for splash screen file does not?
The EXTROM fascinates me because after hard reset the device is installing some "Auto Installation packages" and as far as I have found out those come from the EXTROM. I suspected that the WELCOME.GIF came from there too but now I am not sure. Might have to dump the ROM somehow and look into it but there are not many people with P550 and like I said those who have, don't have the willingness to help with that.
BTW, thanks also for the tip about the registry, but I have tried all the registry tweaks that I have found (including the abovementioned) but none of the works...
Thanks again and looking forward to Your (or anyone else's) comments.
aiiro said:
OK, thanks for a quite thorough reply, but I still don't get it then - why does Resco (or similar prog) ask to overwrite the file? OR, if it doesn't overwrite it, how do I see the new file in Windows folder and the prog looking for splash screen file does not?
Click to expand...
Click to collapse
Resco has been done like you have!
Try to do the following: copy your own Welcome.gif to Windows folder. You will be prompted to overwrite. Say yes. Then simply delete that file. It will not disappear - the old version of file will become visible again. ROM is not a number of files - it is one file which contains a copy of the data that later will be written (flashing process) straight to a read-only memory chip.
(Pay attention on my words "read-only")
Imagine yourself a wall painted with a hell of 100 dollar bills. You can see them. But you cannot take one of them. You can even glue you own bill upon the drawn one. It will work. But when you wash the wall (hard-reset) - your real paper bill will be washed down and the old painted one will appear (sorry for metaphor)
BTW, thanks also for the tip about the registry, but I have tried all the registry tweaks that I have found (including the abovementioned) but none of the works...
Thanks again and looking forward to Your (or anyone else's) comments.
Click to expand...
Click to collapse
Nothing works probably cause the registry is write-protected. Unlock your registry by changing the following:
HKLM\Security\Policies\Policies\00001001 = 1
HKLM\Security\Policies\Policies\00001005 = 40
But! You would do it with the digitally signed regedit. For example - one is attached. Unzip it to your device, run it, change the security policy settings, reboot. Then try to tweak your Asus again.
The attached regedit has OEM Sign 2005 - hopefully it will work for you.
Thank You for a thorough explanation and especially for the metaphore - it was very helpful.
But about the registry - wow... I mean I haven't even heard of unlocking registry...
As usually, answers are generating new questions. The ones I have now are:
1) How come some of the registry tweaks made with Resco still work even now - like showing the clock instead of battery (changing the TBOpt key) etc and the values are still there after soft reset?
2) Resco is also digitally signed, isn't it?
3) If I use this app, will hard reset still create a clean registry? (The answer to this probably is "yes" but I still ask just to be sure).
4) Can I seriously f**k up something with this method?
Thanks in advance.
But
aiiro said:
... answers are generating new questions. The ones I have now are:
1) How come some of the registry tweaks made with Resco still work even now - like showing the clock instead of battery (changing the TBOpt key) etc and the values are still there after soft reset?
2) Resco is also digitally signed, isn't it?
3) If I use this app, will hard reset still create a clean registry? (The answer to this probably is "yes" but I still ask just to be sure).
4) Can I seriously f**k up something with this method?
Click to expand...
Click to collapse
Read your PM - sure I don't have any subscriptions, but it's OK (I mean PM) - it works.
So:
1. The point is that not the whole registry is write protected - only several "important" parts mostly in HKLM. Normally - if you change someting in HKCU - it will work even with the protected registry. The vendor only protects the keys and values that can cause some "critical" system changes.
2. If to tell the truth - I know that Resco has digital signature - but anyway the permission level of it does not allow you to modify the protected keys. So that's why I offered you to use Regedit, signed with the customizers.
3. For sure - after HardReset you will return to factory defaults completely - it means you registry will again become clean and write-protected.
4. It depends upon what you mean writing "seriously". The worst thing - to damage the bootloader, but you will never do that modifying the registry. So - feel free to do whatever you want - you will always be able to return to factory defaults.
OK, thank You very much for the explanation! I have bookmarked like 200 pages related to PDAs, which means that if even only every 10th page gets bookmarked, I have gone through thousands of pages in 4 months and I haven't stumbled on this information before. So everything You have enlightened me about here is most useful, thanks again!
I hope I will not push it but since You have been so helpful and seem to know stuff, I am risking asking some more questions. First of all, would You happen to know a good "idiot's guide to flashing ROM"? I have read those on the wiki but as they are for HTC devices and asus mobile club russia does not have any basic explanation in English, it's pretty hard to catch the idea. I know that much that there is a PC involved with some kind of programs etc, but that's about it. I don't even know what the hell is a bootloader. There also isn't any good PDA architecture drawings lying around in the net
The second question is also related to hardware. I have the Vodafone v1520 as mentioned above and it has a small annoyance - the earpiece volume adjustment during call does not work. The slider moves and I hear the clicks getting louder or quieter but the volume level of the caller voice does not change. I took it to a repair shop and they told me that it's a faulty hardware but I know that there are people with exactly the same problem in this forum and I find it hard to believe that they installed some kind of faulty earpiece on all these devices. Or is that possible? What do You think?
Thanks.
aiiro
Sorry dude but both your last questions are about the specific device - your Vodafone. To answer - I should buy Asus P550 and get an experience first. It's only 700 bucks in my country but I am not sure that I really wanna have it. My current device (pretty old now) is P525 and the next one will probably be Diamond or something better and more expensive.
Second thing - I am not IT professional - I am just a user. OK, I always use my own (cooked) ROMs but it does not mean that I can give the answers to all your questions!
OK, I knew I was pushing it a little bit and in no way did I mean that You should make some kind of spendings. I just thought maybe You had any ideas and maybe ASUS devices are similar enough that they are compatible ROM-wise with each other or something like that.
Anyway, thanks for those thorough replies - You have been most helpful! As soon as I will have some time I will try the registry things out.
Thanks again and good luck!
try to install this cab file ,I make it .you can QQ me by my QQ:421264988 my E-mail:[email protected]
i'm sorry ,I chinese ,and my English is very poor
安装这个CAB文件试试,我的手机也是P320,安装完解锁成功,但在删除程序里看不到之后安装的程序,欢迎和我交流,我的QQ:421264988 E-mail:[email protected]
对不起,我是中国人,我的英语很差
Modified registry values don't survive reboot?
Try switching the device off before reboot.
The registry is not flushed to disk at every write.
And search the net for
flushing registry pocketpc
Click to expand...
Click to collapse
newxda-new said:
Try switching the device off before reboot.
The registry is not flushed to disk at every write.
And search the net for
Click to expand...
Click to collapse
So if you reset the handheld without putting it into suspend mode before, you risk losing configuration data (registry settings)?
Alright,
I notice this phone gets very little attention by the community, however, I like the phone, form factor, etc..
I am looking to "cook" my own HardSPL for this phone. Other providers now support GPS, EVDO RevA, Win Mobile 6.1, and I'm still stuck in what I feel is the ice age..
Please note that any instructions with a prompt are to be done in dos..
So far, I have done the following to extract the SPL:
1) Download HTC update for phone and extract using appropriate zip program
2) c:\>NBHextract RUU_***.nbh
This should leave you with a slew of .nb files - one will be named XX_SPL.nb
Now, to disasm this SPL, you can either go straight to IDA PRO or take an intermediate step using dumprom - dumprom creates a pe.exe and handles the offsets for you, so it puts you a step ahead, imo.
1) c:\>mkdir SPLDISASM
2) c:\>dumprom -5 -d SPLDISASM XX_SPL.nb
Now, in the SPLDISASM folder, you should have an exe file that you can now open in IDA PRO.
Now, here's where it is starting to get foggy for me. I followed the same process to dump the stock SPL and the HardSPL from a Hermes phone and I am in the process of hand tracing and hand comparing it to see how SuperCID/Write protection/Protected FF writes is implemented in the HardSPL - hoping that I can port the differences to my phone.
So, I pose the following to the experts:
1) In order to test my HardSPL once it is complete, can I run it as a SSPL and load a new ruu as a test - or will that mean certain death to my device?
2) Now that I'm this far into the code, i've come to realize that reassembling the code will be a lot of pain. Do you guys disasm/asm, or do you just hand edit in a hex editor?
3) Any suggestions to look out for, any ideas, etc?
Let me finish with a few disclaimers
1) To the experts: I have no intention of reverse engineering the HardSPL codebase - if I do use any of the code I have found, I will be sure to give props to the people involved and ask for permission before distributing. I am not looking to profit or scam or steal ideas, i am simply looking at how to make my phone better.
2) To the beggers: I have nothing to release at this time, this is all vaporware, I don't know when it will be done, I don't even know if it's do-able. I'm just trying ATM.
3) To the beginners: any or all of the advice above can probably wreck your device. This is by no way a means to unlock your phone, it's just my thought stream as I take what I believe are the preliminary steps to make my Libra the phone it's meant to be.
desquirr decompiler
I am now using the desquirr decompiler plugin for IDA PRO - it's dumping the subroutines into rudimentry c code.
I am now far closer to understanding what it is my device does; as well as understanding some of the hardspl code.
I recommend this tool if you are also SPL "cooking"
More Progress!
No Replies yet? Man, this is starting to feel like a blog..
Okay, I have managed to dump my Libra SPL, and I have disassembled it, and I have also decompiled it - Well, partially.
All the subfunctions are now represented in C - it's not particularily the most efficient c code I've ever seen, but it's readable. You'll get a hang for it and start to notice the FOR loops, IF/ELSE, WHILE structures.. Multiple return values.. etc.. etc.
I have decided to attach the Stock Libra SPL - I am hoping that I can eventually turn this into a tutorial to build your own custom SPLS for devices that aren't supported by the general community (note, this is high risk stuff..)
Hopefully this will serve as a reference to the community as I progress.
I do hope I get a little feedback too. If I'm going down the wrong path in terms of my approach, or for sharing this project with the community, it would be good to know.
Once again, small disclaimer - this file will not do anything for your phone as of yet.. Just a development step.. (I hope...)
MegaHambone said:
1) In order to test my HardSPL once it is complete, can I run it as a SSPL and load a new ruu as a test - or will that mean certain death to my device?
Click to expand...
Click to collapse
The hard part is to make a patched SPL run as Soft SPL from within OS.
You can try pof's JumpSPL and/or Haret to start your SPL, however I'm not sure these will run on smartphone platform at all. If not, JumpSPL source code should be available, so you can try to figure it out.
Be sure you don't overwrite your stock SPL or radio when flashing a custom ROM with RUU, this is the best way to brick it!
Unless you really can't go without flashing a HardSPL, IMO it's safer to keep the stock SPL flashed for recovery purposes.
HardSpl to add new commands
I'm happy to hear that somebody is working on a hard SPL for HTC S720. Here's the deal, I really want to change esn in this phone but I realized that for now it's not possible.
It's a MSM7500.
**I've tryied QPST but the version 2.7 only support MSN6500.
**I've tried QXDM 3.9.19 and still can't write the new esn. It says read only.
_________________________
How to put it not in read only?
Could I use a anykind of ready/writer to change info directly on the chip?
-----------------------------
**CDMA Workshop 2.7 all kind os ESN write doesn't work.
-----So, two options left:
1- either I desolder the esn chip and change it for a new one (to be honest, I haven't discovered yet if the esn is inside the MSM or on a different chip. If it's the case (on a diff. chip) it's a bit a pain in the but to do but it's still an option.
2 - I want to try shadowmite's method for writing the ESN into a PPC6800. Again it need to be done in high level via MTTY.
Concerning MTTY I cannot run commands because I can't put the phone on the boot loader screen.
I will try to run RUU wich will put the phone in bootloader screen. And then try mtty.
If this fail, I guess my only hope will be a hard spl.
I guess I've said a ton of thing that gonna make me look like a newbie (wich I am in prgramming).
Any suggestion...? Or any help I could bring to create this hard spl?
I am using HTC S720 in India. Currently I am using windows 6. Is it possible to make it work for windows 6.1. Telus ROM for HTC S720 is already available.
HardSPL for HTC5800/S720/LIBRA
I am currently trying to create a HardSPL for this phone and am having a hard time. I really need a solution for this and if anyone can create a HardSPL the company I work for is willing to pay a reward.
Why not try get a goldcard for it.Try ask at http://psas.revskills.de/ or if you know anyone with a axebox i think they do goldcards
Hi, Need some help here....tired of the same whole mix-mash from htc (recycled phones) so going back to basics - htc s620 (wm6) + my just acquired used 4700. Intend to upgrade it to WM6.1, I've been using htc phones so I am used to rom flashing... or so i thought. I downloaded some of the wm6 and 6.1 roms only to find that dont come with an ruu built in. Not a problem I thought,just get a carrier and replace the nbf file. Unfortunately despite an extensive search on brighthand and here and yahoo searches galore i havent been able to find a suitable guide with the necessary utilities to carry out the flash. The "universal bootLoader" no longer seems to be around (404 errors) samething with other Ruu's (from ru websites etc) yet I can still see thru the long 220 - 251 pg threads that people are flashing with something. In the interest of new 4700 owners would it be possible to have a particular "How-to-flash" thread possibly as a sticky? If not at least can someone help me with a how-to guide and any link to the relevant ruu or bootLoader utility for the rom flash.
Thanx all appreciate it.
You can find all the neccessary information on this page; different ROM's, a bootloader, and instructions in PDF format..
Thanks a lot ridolfo. that has helped a great deal. Slight problem that you hopefully know a way around. After downloading the BootLoader.exe rar file, I tried to open it to proceed but it kept on coming up with an error... "windows cannot open the selected path file...you may not have the appropriate permissions to open them" I just cant get past that altough it has apparently opened and expanded showing a whole lot of other files but i cannot basically get past that stage to run the rom nbf file... Any ideas please?
Right sorted!
Very simple but unexpected solution especially since i hadn't seen the issue mentioned elsewhere.
Simply disconnected all connections to the internet especially wifi (for safety/protection etc) and then disabled zone alarm!
Everything went thru as normal,updated and now just waiting for boot-up.
thanx a lot Ridolfo!!!