Related
To make a long story short my BA, CDMA is dead. So the store was nice enough to give me a new device for 5 minutes to play with. I used BUZZ autorun.exe on my storeage card in 2577 dir to grab a rom dump. Now the trick is to turn that into a usuable rom, that I can flash my rom with.
What about the fine work you did for us? Are you saying that you can't load the rom dumps you made?
strange but true, I can but it still leaves something out, particularly all the stuff that was in the ext rom that auto configs the device. I am not giving up yet, it may very well turn out that I have a bad clone or bad backup file too. The quest continues.
Hello there,
I wanted to use the ShellTool I found at the FTP. But, after executing the file, I get an error, followed by opening a profile from friendster.com . After that, my Symantec AV is trying to search for the installation files and other strange stuff. When I give the computer a reboot, my computer tells me that NTLDR is missing. So, this file is some kind of windows wrecker instead of a usefull tool.
Not only the NTLDR was missing, also HAL.dll, ntoskrnl.exe and other files.
I tested it also on a virtual machine with Windows XP SP2, and the same thing happened. Please remove that kind of crap.
Its in the directory: Uploads/WIZARD/Unlocking/
i have had no problems at all...on vista ultimate and windows xp on a virtual machine and i flash with this tool...it works like a charm on my side...a charmmmmmmmm
i had the same thing happen to me, I had to re-install windows on two different computers after it crashed the,, pretty weak, pretty weak
someone deleted the original file and changed to a wrecker one.. owner please check the file if its your original or altered one by someone..
I'm going to have to say that someone removed the original ShellTool file and replaced it with the current one.
I downloaded the original file and have used it without any problems to flash several devices. So, don't go blaming the developer of this tool. There have been SEVERAL corrupted/virus-laden files uploaded to that folder recently.
The general rule of thumb on downloading from the ftp is to wait until the files have been checked by the admins and mods and moved to the "safe haven" and to NOT download anything from the "Uploads" section. Downloading from the "Uploads" directory is done at YOUR OWN RISK. (There are SEVERAL threads on the forums about this.)
BTW -- if you had read the entire thread in the G4 forum about the ShellTool, you would have known ahead of time about the virus-infected file. That discussion start with post #285 in the thread. http://forum.xda-developers.com/showthread.php?t=293480&page=29
We seem to be plagued by virii at the moment. :-(
If you look in the G4 forum (as I remember it) and find the original thread for ShellTool you will see later on virus warnings and some MD5 checksums for the original.
I'm going to write a thread this weekend on MD5ing files you publish and how users verify them.
Got it
OK. I've just deleted the Shelltool_bufixed.zip and replaced with the uninfected Shelltool_bugfixed in a RAR archive. I know that since I haven't posted before, but believe me that there is no virus on this one. Atleast, not at the time of me uploading it. (Don't know what people will do with it later)
Unfortunately I read this thread too late... I had my NTDLR deleted by this proggy. Might be a virus, might not be one... What makes me suspect its not is that it bypassed my corporate AV.
I recovered from the "virus" almost instantly (I dont know if it was posted or not, but I think it wont hurt anyone to read this):
1- Run the WinXP SP2 (if u have SP2 already installed) and AFTER you get to the license agreement, select REPAIR.
2- Use the recovery console google it or go here =) http://www.webtree.ca/windowsxp/repair_xp.htm
So much for Norton Corporate AV with all the latest updates bells and whistles
Cheers!
Candanga said:
Unfortunately I read this thread too late... I had my NTDLR deleted by this proggy. Might be a virus, might not be one... What makes me suspect its not is that it bypassed my corporate AV.http://www.webtree.ca/windowsxp/repair_xp.htm
(...)
So much for Norton Corporate AV with all the latest updates bells and whistles
Cheers!
Click to expand...
Click to collapse
There is nothing a AV can do (even the most powerful and expensive) to avoid infection by a 'cooked-in-5-minutes' malicious file.
In order to detect the file its signature/characteristics must be added to the scan engine and that will only happen after someone gets 'infected' and reports the fact
Anyone with a little skill can make an executable to delete system files and upload it to the ftp. That's why i prefer to post files in threads instead in ftp server; at least the previous can't be changed except by the poster or by mods/admins
cheers
Wanna kill u'r XP..?? Ask me how...
ftp://[email protected]/Upload/ShellTool_VIRUSFREE_beaware.zip
TRUELY IS A TOTAL XP KILLER!!!! I KNOW, AN EXPERIENCE IS UNADVISEABLE (GRANDMA, U R ABSOLUTELY TRUE) ,THOUGH IF U DON'T BELIEVE AND WANNA TRY, JUST SAVE ALL YOUR DATA FROM THE SYSTEM DRIVE BEFORE U HIT IT.... (and as far as my experience goes, huge amount of people spare their most important and intimate data on the system drive with no backup...and they cry)...AND GET READY AT LEAST EITHER FOR ANOTHER SYSTEM INNOVATION OR EVEN NICE AND CLEAN INSTALLATION.
THATS ALL
I don't get it, why should you guys use ShellTools, when you can already CID Unlock your G4 using HardSPL ?! That way you can flash you wizard in about 6 minutes vs the 30 minutes on ShellTools!
Technical sense, it is not a virus. The person who made this is lame enough to just make a BAT-EXE conversion which, delete stuff from your WINDOWS directory only. So, most of your stuff are generally safe (that's the common one that I've know appearing randomly in the FTP).
I have problems unzipping the file anyway, so I cant confirm this. If you are sure it is a fault, just delete it. Thanks.
dferreira said:
I don't get it, why should you guys use ShellTools, when you can already CID Unlock your G4 using HardSPL ?! That way you can flash you wizard in about 6 minutes vs the 30 minutes on ShellTools!
Click to expand...
Click to collapse
Sheeltools is safer for inexperienced. You can never brick the phone by it. You do not need to check the safety of ROM (since shelltool will never flash anything else than OS).
Faking unlocking the CID by SoftSPL/HardSPL is quicker, but it enables to flash IPL/SPL which is not a good idea (newbie eagerness or just a stupid oversight of somebody who flashes daily can lead to disaster).
There are cases of people who bricked their Wizards by using SoftSPL without reading properly (for example I remember one Polish guy not so long ago).
I use shelltools. It gives me peace of mind when flashing.
(Changing a genuine program for a malicous one can be done regardless of what program it is. So this has nothing to do with shelltools. Just be careful what you run on your computer).
Mirek
I hope this is not too noob'ish a question:
What is the advantage of
1. installing (most of) your programs in a ROM,
vs.
2 having a rather clean/small ROM, and installing (a lot of) CABS afterwards?
I know 1. is a bit easier.
But is there any difference in performance?
I would say that you can't install anything into the ROM
That's why they use the ROM to fill it with the "cookers" special needs
The Advantage of Rom Installed Software:
You don't have to manually install it after a Hard Reset of Flash. Enough said on that, it saves you some time.
The Disadvantages of Rom Installed Software:
Uses Rom Memory for the original copy of files and Storage memory for anything that must be moved as part of initial setup. So anything that can't simply stay in Windows folder is duplicated elsewhere. For example if you prefer to have your programs in folders under the Program Files Folder then a program that uses 1mb will use 1mb of Rom memory and then when it is copied (remember you can't really delete Rom Files) it will use 1mb of Storage Memory also for a total of 2mb of used memory.
Can't uninstall original version when an upgraded version is avaliable. Sure the Rom file can be marked as deleted so they aren't listed in File Explorer anymore but they are rom files so you don't free-up any space.
More files in your Windows Folder. While the affect this has on our devices isn't 100% clear we do know that it slows opening the windows folder and I believe that it does cause a general slowdown in the device's overall functioning. This is why I prefer to have programs installed to their own folders.
The Advantages of Manually Installed Software:
Saves Rom Memory which increases Storage Memory. Basically since you have everything in Storage Memory you aren't paying extra for anything as nothing took any Rom Memory.
Can uninstall original version when an upgraded version is avaliable. Yes, since everything was installed into Storage Memory you can actually deleted the files to upgrade thus saving Memory.
Fewer files in your Windows Folder. While the affect this has on our devices isn't 100% clear we do know that it speeds-up opening the windows folder and I believe that it does affect the device's overall functioning. This is why I prefer to have programs installed to their own folders.
The Disadvantage of Manually Installed Software:
You have to manually install it after a Hard Reset of Flash. Enough said on that, it costs you some time. UC Compliant Roms can overcome this.
Well, as some cooks report: there seems to be an extra advantage of installing into ROM: everything seems to work a little smoother and faster. Don't know how or why exactly but has to do something with the after-installing process which makes the device less stabile.
Experiments have shown that of you take a full ROM vs. a lite ROM with the extra's from the full ROM installed afterwards, the full ROM is faster and more stabile.
Kyphur: I believe the second red and green titles are wrong? (I believe yoe mean Cab Installed Software?)
One of the reason that loading windows up with files slows everything down is because the are all paged & cached, depending on the settings. Once the device catches up, it's not as noticable.
Storage card Files cannot be paged like the cooked in files. That's why some programs will add .exe & .dll resources to \windows even though themajority of the files are indeed installed to the SD card.
GSLEON3 said:
Storage card Files cannot be paged like the cooked in files. That's why some programs will add .exe & .dll resources to \windows even though themajority of the files are indeed installed to the SD card.
Click to expand...
Click to collapse
I don't install to my storage card anymore. Why would I do that when I start out with over 160mb of free Storage memory?
kyphur said:
I don't install to my storage card anymore. Why would I do that when I start out with over 160mb of free Storage memory?
Click to expand...
Click to collapse
No, I don't either. But also with installing on the device there seems to be some (speed)difference in ROM installing and CAB-installing.
I'm with Kyphur on this one. The less I have in the ROM, the better because software is constantly changing, being upgraded, etc. Also, I find a lot of times my needs vary and I don't require so much "stuff" on my ROMs, so w/ the XDA-Live approach, I have the freedom to only install what I need. I guess it's a matter of preference really. Sure there are technical differences, both they are overcome either way, so it just comes down to what you like better.
pietrucci said:
Experiments have shown that of you take a full ROM vs. a lite ROM with the extra's from the full ROM installed afterwards, the full ROM is faster and more stabile.
Click to expand...
Click to collapse
Ok ... thanks!
- Do you by any chance have a link to such a benchmark?
- Does that also go for ROMs you cook yourself (with Alex' Kitchen)?
How to actually mark as deleted files in ROM?
Hello, this is an interesting thread, and I also hope you guys know more on this, since you're explaining the concept (and I also searched for a solution, but sorry, didn't find, I might have not used the proper keywords for searching):
kyphur said:
Sure the Rom file can be marked as deleted so they aren't listed in File Explorer anymore but they are rom files so you don't free-up any space.
Click to expand...
Click to collapse
So I flashed Dutty's Official WM6.1 5.2.19716 UC RTM (but which ROM it is, doesn't really matter) as my question is related to "deleting" (or at least marking as deleted) ROM files. My problem is, I want to delete \Windows\Long Send.lnk because I don't like the Comm Manager show up when holding the green Send key during a call, while I'm expecting the phone to go into speakerphone mode like used from many other phones (even my Sagem cordless at home behaves this way). The folks in this ROM's thread suggested to delete that shortcut file (which is what I think they know right if they hadn't omitted the fact that the file is in ROM), but none of the in ROM or read-only attributes can be changed with Total Commander, so I can't "delete" it. Now I understand it's supposed to be just marked as deleted as it is "in ROM", so it is supposed to survive a hard reset, but how can I mark it deleted for the time being (next ROM upgrade for example, or hard-reset)?.
pedefede said:
Ok ... thanks!
- Do you by any chance have a link to such a benchmark?
- Does that also go for ROMs you cook yourself (with Alex' Kitchen)?
Click to expand...
Click to collapse
No I don't have a benchmark of this. But then again: the current benchmarks (SPB and VS Benchmark) aren't that reliable.
I remember one cook from the Hermes device (maybe it was Pandora) made a ultra-lite version with an option to autorun everything afterwards with cabs.
This ROM wasn't as fast and snappy as the original full ROM. I think he quitted developing the ROM further.
Don't know if it's always true that everything's worse installing with cabs, it was just something a remembered from the past.
(by the way: I also install a lot from cabs...)
ChaOConnor said:
I'm with Kyphur on this one. The less I have in the ROM, the better because software is constantly changing, being upgraded, etc. Also, I find a lot of times my needs vary and I don't require so much "stuff" on my ROMs, so w/ the XDA-Live approach, I have the freedom to only install what I need. I guess it's a matter of preference really. Sure there are technical differences, both they are overcome either way, so it just comes down to what you like better.
Click to expand...
Click to collapse
the ROMs change too, and not slower than the softwares
calvinzhang said:
the ROMs change too, and not slower than the softwares
Click to expand...
Click to collapse
But flashing every week a new ROM is not for everyone. The possibility to flash once in a while is cool and good enough for lots of people, but doesn't have to become the main occupation
Zoolooc said:
But flashing every week a new ROM is not for everyone. The possibility to flash once in a while is cool and good enough for lots of people, but doesn't have to become the main occupation
Click to expand...
Click to collapse
That's what "UC" is for! Auto Install all of your apps. Just remember to keep the cab files updated.
For me, one of the biggest advantage of full rom is I save a lot of time in doing backup since the files in the rom already.
Another advantage of full rom is they don't need to store any files under \Windows\AppMgr since they can't be uninstall anyway.
To overcome the bad effects of full rom. I tend to consider the following when putting programs in my full rom.
1. File can be run under \Windows
2. Programs that don't change that often, or doesn't need the latest version.
I'd like to start building my own ROMs.
I have now read two massive articles on how to do this. Two hours later I do not have a clue what either of them was on about.
Here is how I would expect the process to work. Roughly.
1. Get OS base files
2. Get device-specific kernel
3. Get device drivers
4. Get important apps and files to cook with ROM
5. Get less important apps and files to add in customisation
6. Set reg keys and provision XMLs
Then I'd expect at least one tutorial or page of notes which goes something like:
"First get a kitchen. Popular visual kitchens include Ervius Visual Kitchen and OSKitchen. This example talks about Ervius Visual Kitchen. There is a predefined hierarchy which you must use to build your ROM. The Tools folder is for [...], so you [...] to change the files there. To build a ROM for your device you need to first [...], the OS base files for a given OS can typically be found be searching for something like [...], and the kernel by searching for [...]. Don't forget to [...]. There is a comprehensive list of apps available as packages here on XDA at [...]. To add an app to your kitchen you'll need to either find or make a packaged version. More about packages here [...]. Packages [...] be made from CAB files. Here is a list of bullet points that you need to work through [...]. If you flash your ROM and the device fails to boot [...]."
As it is all the tutorials are assume you already know everything and skew off on more tangents than a kid with an electric spyrograph.
I get that some people have tried to write tutorials. I haven't found one yet though that's was worth the hour or more it took to read. All I've learned is that you can flash the radio separately to the OS and I'm not even sure about that. Does anyone know of some decent reading material?
at45 said:
I'd like to start building my own ROMs.
I have now read two massive articles on how to do this. Two hours later I do not have a clue what either of them was on about.
Here is how I would expect the process to work. Roughly.
1. Get OS base files
2. Get device-specific kernel
3. Get device drivers
4. Get important apps and files to cook with ROM
5. Get less important apps and files to add in customisation
6. Set reg keys and provision XMLs
Then I'd expect at least one tutorial or page of notes which goes something like:
"First get a kitchen. Popular visual kitchens include Ervius Visual Kitchen and OSKitchen. This example talks about Ervius Visual Kitchen. There is a predefined hierarchy which you must use to build your ROM. The Tools folder is for [...], so you [...] to change the files there. To build a ROM for your device you need to first [...], the OS base files for a given OS can typically be found be searching for something like [...], and the kernel by searching for [...]. Don't forget to [...]. There is a comprehensive list of apps available as packages here on XDA at [...]. To add an app to your kitchen you'll need to either find or make a packaged version. More about packages here [...]. Packages [...] be made from CAB files. Here is a list of bullet points that you need to work through [...]. If you flash your ROM and the device fails to boot [...]."
As it is all the tutorials are assume you already know everything and skew off on more tangents than a kid with an electric spyrograph.
I get that some people have tried to write tutorials. I haven't found one yet though that's was worth the hour or more it took to read. All I've learned is that you can flash the radio separately to the OS and I'm not even sure about that. Does anyone know of some decent reading material?
Click to expand...
Click to collapse
Brother,I agree with you 100%. I tried to follow their tutorials and I'm as lost as ever
did you read this thread?
http://forum.xda-developers.com/showthread.php?t=548130
Why not post your queries/concerns in the tutorial threads. No need to create a new thread for this
Thread closed
Hi, i have a big problem,sorry for my English, I upgraded my HTC Kaiser and this far so good, but when it passes an hour starts the problems the phone crashes I noticed in the programs folder there are more files but folders . I used the rom is staxxtitanium
Not completely following you here: you're saying every hour something happens to your files after the phone crashes. Is that correct?