Hi, guys, maybe i am stupid, but i cant find a link where i can download Death SPL
Please help, thanks.
sssats said:
Hi, guys, maybe i am stupid, but i cant find a link where i can download Death SPL
Please help, thanks.
Click to expand...
Click to collapse
DON'T.
We call it the "deathspl" for a reason.
And there is NO BENEFIT to it.
If you want to use a ROM that wants to use more than about 65MB in the /system partition, just move some files into /cache and symlink to them!!!! There is no reason to risk your hardware for something this pointless.
Where i must wach, if i have enough space?
Could you please rephrase that? I can't understand the question.
Here you go, download links and instructions http://forum.xda-developers.com/showthread.php?t=625886
lbcoder said:
DON'T.
We call it the "deathspl" for a reason.
And there is NO BENEFIT to it.
If you want to use a ROM that wants to use more than about 65MB in the /system partition, just move some files into /cache and symlink to them!!!! There is no reason to risk your hardware for something this pointless.
Click to expand...
Click to collapse
I see using SuperD a huge benefit
Joe333x said:
I see using SuperD a huge benefit
Click to expand...
Click to collapse
And risking a brick doesn't help you run it.
As I said, just move the overflow files into /cache. Fits just fine unless you're a retard.
lbcoder said:
And risking a brick doesn't help you run it.
As I said, just move the overflow files into /cache. Fits just fine unless you're a retard.
Click to expand...
Click to collapse
Or instead of moving anything you can just read this http://forum.xda-developers.com/showthread.php?t=625886 and not have to move files every time you want to flash a ROM. Trust me if you follow the guide you will not brick your phone.
Joe333x said:
Or instead of moving anything you can just read this http://forum.xda-developers.com/showthread.php?t=625886 and not have to move files every time you want to flash a ROM. Trust me if you follow the guide you will not brick your phone.
Click to expand...
Click to collapse
Trust me, sometimes even if you DO follow the guide, you'll STILL brick your phone.
The SPL you are recommending is simply NOT COMPATIBLE.
And no, it does not cause you to need to move files every time you write a different ***SYSTEM IMAGE***.
(Hint: The word "rom" does NOT APPLY)
I curse that stupid kid "haykuro" every time someone recommends this "deathspl". It has had TWO effects, neither of them positive;
1) Creates BRICKS,
2) Creates INCOMPATIBILITY.
*** if the various cookers weren't lazy douches, they would arrange files to be suitable for REGULAR SPL, and therefore there would be no issue of "this system requires XXXX SPL"....
It has been a TERRIBLE DISSERVICE.
Note: It is TRIVIAL to write a script to automatically REPAIR your various ill-conceived "update.zip" archives.
i.e.: (this won't work exactly like this, requires minor debugging, but to give you the idea...)
Code:
#!/bin/bash
unzip update.zip
mkdir -p update/cache/app
mv update/system/app/(a bunch of .apk's) update/cache/app
echo "(a few trivial lines to write /cache and create symlinks" >> update/META-INF/com/google/android/update-script
zip fixedupdate.zip update/*
java /path/to/testsign.jar fixedupdate.zip
Just run that on every update.zip that you feel like installing!!!
Well...
Hey!
Concerning deathspl...
1) Creates BRICKS,
2) Creates INCOMPATIBILITY.
*** if the various cookers weren't lazy douches, they would arrange files to be suitable for REGULAR SPL, and therefore there would be no issue of "this system requires XXXX SPL"....
Click to expand...
Click to collapse
Well said.... and agreed 1000%
So called deathSPl for HTC Dream is nothing more than engineering bootloader 1.33.2005 from HTC Sapphire.
Of course these devices are similar but not the same...
I know that this works out well for some, but it's also obvious that some like to mix it all up
Personnally i would appreciate to use some clever hacks for the original evironment to run modified ROMs.
Regards,
scholbert
lbcoder said:
Trust me, sometimes even if you DO follow the guide, you'll STILL brick your phone.
The SPL you are recommending is simply NOT COMPATIBLE.
And no, it does not cause you to need to move files every time you write a different ***SYSTEM IMAGE***.
(Hint: The word "rom" does NOT APPLY)
I curse that stupid kid "haykuro" every time someone recommends this "deathspl". It has had TWO effects, neither of them positive;
1) Creates BRICKS,
2) Creates INCOMPATIBILITY.
*** if the various cookers weren't lazy douches, they would arrange files to be suitable for REGULAR SPL, and therefore there would be no issue of "this system requires XXXX SPL"....
It has been a TERRIBLE DISSERVICE.
Note: It is TRIVIAL to write a script to automatically REPAIR your various ill-conceived "update.zip" archives.
i.e.: (this won't work exactly like this, requires minor debugging, but to give you the idea...)
Code:
#!/bin/bash
unzip update.zip
mkdir -p update/cache/app
mv update/system/app/(a bunch of .apk's) update/cache/app
echo "(a few trivial lines to write /cache and create symlinks" >> update/META-INF/com/google/android/update-script
zip fixedupdate.zip update/*
java /path/to/testsign.jar fixedupdate.zip
Just run that on every update.zip that you feel like installing!!!
Click to expand...
Click to collapse
Actually not one person that has followed that guide has bricked, I have read every post in the thread seeing as I am the one who made the guide and the brick percentage is at zero. Why call people who make ROMs for others to use lazy? They create ROMs on their own time for free so that others can enjoy them. I really dont see the need to do extra work every time you flash something when you can simply flash the Danger SPL correctly one time and then you will be fine. As far as incompatibility goes I dont really see why that matters its no one right to be able to flash a certain ROM. If they want to use a ROM that requires a different SPL then flash the SPL if you dont want to flash the SPL no one is forcing you to just use a different ROM its as simple as that. The devs on here work for free and they are free to make requirements for their ROMs if people dont like that then they wont use that devs ROM but as you may know many people have been willing to switch SPLs to use a certain ROM.
You are definitely dense.
IT IS NO EXTRA WORK!!! I just PROVED it to you!
And I call them LAZY because they ARE.
lbcoder said:
Just run that on every update.zip that you feel like installing!!!
Click to expand...
Click to collapse
lbcoder said:
You are definitely dense.
IT IS NO EXTRA WORK!!! I just PROVED it to you!
And I call them LAZY because they ARE.
Click to expand...
Click to collapse
I could be wrong but running a script every time you update seems like extra work to me even though it maybe trivial and easy to do so is flashing an SPL one time. If they were lazy they wouldnt be cooking ROMs for anyone. I could say that anyone who doesnt want to simply flash an SPL is also lazy, but its just their choice not to just like its the devs choice to not do extra work to make their ROM not require a certain SPL. Its very simple you dont want want to flash the SPL then dont and dont use any ROMs that require it. If you do want to flash the SPL then just follow the How-To and you will be fine. There is no sense in arguing about it there hasnt been a Haykuro brick from anything besides flashing an old radio, so simply dont flash an old radio and you wont brick, very simple.
Related
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'm no longer keeping up with NAND on the vogue. So if anyone would like to keep me informed and email me or post me on any changes with NAND, ill be happy to add the news on the first post. The lock up issue with NAND has been fixed!
This is simply for any noobs or others who are having issues with Android and NAND.
IMPORTANT!!!
FOR VOGUE USERS ONLY
I am not responsible for any bricked or messed up devices. By continuing you are agreeing to my simple rule.
MY SIMPLE RULE: I owe you nothing.
I will help you through the way though if you bricked or need any sort of help.
How-to Video up NOW!!!
http://www.youtube.com/watch?v=3gTkJkOc7m4
​
First off, What is NAND?
To keep it simple...its your phones internal memory. Up untill recently we (Vogue Users) had to run Android off our SD cards using HARET. But thats another story.
What are the benefits of running from NAND? (based on what I have seen)
-Runs faster
-Longer Battery life
-faster boot up
-can be faster to put together.
-Easier to connect your vogue with android to your pc and sync
-Much more convenient.
So how do I start?
STEP1:
The Build
First you need to find a Build that is usable with NAND. Most Hero builds at this moment are not. Here are some links:
Donut 1.6
http://forum.xda-developers.com/showthread.php?t=591104
Hero
http://forum.xda-developers.com/showthread.php?t=603028
Cupcake 1.5
Method 1 from http://forum.xda-developers.com/showthread.php?t=593786
DO NOT DOWNLOAD ANYTHING JUST YET! I WILL TELL YOU WHEN A GOOD TIME WOULD BE
You may want to consider reading the rest...
STEP2:
Base Files (Most builds will supply these)
For all builds (Except the Link in Cupcake "instructions are givin in the download.) you will need a basic set of base files. The link below contains the 3 basic empty files for all builds and Systems.
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/Androidstuff.rar
IF
You are using Hero make sure you download hero.user.conf too:
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/hero.user.conf
-create a new folder called conf
-and place hero.user.conf in your new folder.
STEP3:
Rootfs
After you have the Base files you will need a rootfs. Depending on your Build, you may need a different type then the one I am going to supply you. Most builds will supply you with one. This one is DZO's rootfs.
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/rootfs.img
STEP4:
Prepare
-You need to clean out your storage on your SD. Make sure you delete everything.
-Create a file called android on your desktop.
-Download the base files, unzip, open folder, and place all 3 in your android folder
-Download the rootfs and place them in your android folder. Make sure you either download DZO's or the one your Build provides.
-Download a System.img. When you download a System most likely it will have a different name such as system-hero-123.img. You need to rename it system. So it should look like system.img . Then place it in your android folder.
-If you are using Hero place your conf folder in your android folder.
-Depending on your Build (mostly Hero) you may also need a Data file. The build you select should supply one. Download it and place it in your Android Folder
STEP5
Placing
Open up your android folder of all your collected files and select all, copy, and paste into your empty SD card.
STEP6
Unlocking
If you have never flashed a ROM before than you don't have HardSPL installed. So unlock your phone with...
http://forum.ppcgeeks.com/showthread.php?t=20370
Make sure you follow the forums directions.
STEP7
Method
Method1: The way I do it.
Download ROMUpdateUtility.rar
http://cid-e5302e6abd554cb9.skydrive.live.com/self.aspx/XDA/ROMUpdateUtility.rar
Extract to a newfolder
Download a kernel with your screen size
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
Don't know your screen size...check this out
http://forum.xda-developers.com/showthread.php?t=544906
After you have have gotten the kernel:
rename it to RUU_signed and place it in the ROMUpdateUtility folder you created.
NOW you need to plug your phone into your computer. Establish active sync. And run ROMUpdateUtility.
-Follow the Instructions on the screen.
Method 2 and 3 can be found here:
http://forum.xda-developers.com/showthread.php?t=593786
This also shows my method...but a little less detail. You can also find many other helpful things there.
If you fail OR think your bricked your phone.
You will need to download one of these depending on your carrier...Make sure you download the shipped gps rom. (If you are Verizon skip down)
http://forum.ppcgeeks.com/showthread.php?p=191607
Than you will put your phone in boot mode. Hold the Camera and Power button. While holding both of them...get a pen or something small and hit the little restart button on the bottom of your phone. You may have to hold it for like a second.
-you will see three color bars on your phone
-plug your phone into your computer
-run the backup
After your phone is all back to normal. Make sure you run internet explore on your phone. It will enable you to get data.
For Verizon follow the instructions here.
http://wiki.ppchaven.com/index.php?title=Pocket_PC_WIki:FIX_VERIZON_GPS
That is about it. I'm sure I forgot some stuff and will add on to this. Make sure you donate to the Devs for all their hard work.
DZO
http://forum.xda-developers.com/showthread.php?t=593786
jamezelle
http://forum.xda-developers.com/showthread.php?t=603028
plemen
http://forum.xda-developers.com/showthread.php?t=591104
vilord
http://forum.xda-developers.com/showthread.php?t=523692
They deserve it.
thank you this was very helpful
inphin1ty said:
thank you this was very helpful
Click to expand...
Click to collapse
No problem...
yea here is the md5sum: 9b08971e7f23619b6a9a4db9d52d857a
jamezelle said:
yea here is the md5sum: 9b08971e7f23619b6a9a4db9d52d857a
Click to expand...
Click to collapse
Whats that?
staud8469 said:
What are the benefits of running from NAND? (based on what I have seen)
1 Runs faster
2 Longer Battery life
3 faster boot up
4 can be faster to put together.
5 Easier to connect your vogue with android to your pc and sync
6 Much more convenient.
Click to expand...
Click to collapse
great thread. I've run both from nand and sdcard. i have not messed with ext2 on the sdcard.
I agree with 3 for sure. I would also add that there is a deep gratification in wiping win mo off the sdcard
6 is debatable, depends on which conveniences you want. changing lcd.density, changing resolution are all much faster running from the sdcard - no flashing or messing with build.prop, just edit default.txt and reboot (aside - if you have a non-sdhc card you can flash on the fly from the sdcard, but changing lcd.density still requires pulling and pushing files from the system, which is not as easy as changing the default.txt). also more convenient to back-up or revert to a data.img when running from sdcard. definitely booting straight into android is convenient, as is the new mass storage on boot method, as well as having a re-writable system (which you also have using ext2).
1 and 2, I honestly have not noted a significant difference in battery life. With a fast sdcard, I don't think there is a significant difference in speed either - dzo has said this in one of the non-vogue forums as well. i have not tried any sense builds from the sdcard though, and that's where you would notice the greatest difference in speed if there is any.
4 I agree with in general.
I think running from the nand is a huge advance, and great for everyone to try. but, running from the sdcard is still a decent way to use android. choosing between the two comes down to choosing which conveniences suit your usage style the most.
One last thing - please add vilord to your donate links (his google ion on vogue thread), he has been instrumental in developing the ril and advancing android on the vogue. srwalter also deserves mention for his reverse engineering of the libgps.so to bring gps first to cupcake and now to donut as well. jamezelle, plemen, mssmison, zenulator, enatefox, f00bar (no specific order) have all worked hard porting roms and working on things like compcache, swap, modem, etc, which has all been invaluable (zenulator and mssmison deserve special credit for spearheading the porting business). however the gruntwork of porting to the vogue has been done mainly by dzo who brought us the kernel and initial ril and now nand (he's just frickin amazing, he singlehandedly got the first functioning port to the vogue and others helped from there), then vilord who took the ril and really refined it. I guess suffice to say, there have been a lot of people involved along the way, thanks to all of them.
when i try to run android from both nand and haret i always get an error about not being able to mount sd card. does this mean i need to reformat the card? if so how do i do this?
Barogi44 said:
when i try to run android from both nand and haret i always get an error about not being able to mount sd card. does this mean i need to reformat the card? if so how do i do this?
Click to expand...
Click to collapse
When do you get this error? During linux kernel bootup?
Verizon users.
I just update a fix for Verizon users. Shows you how to get GPS too!
Also...there will be a video up soon. It seems that there are so many people having issues. So I will create a video from start to finish. Will be posted up late tonight/ tomorrow morning.
staud8469 said:
When do you get this error? During linux kernel bootup?
Click to expand...
Click to collapse
Yea.. i think i may need a new sd card. Can android boot from a 4gb card or is 2 the max?
Barogi44 said:
Yea.. i think i may need a new sd card. Can android boot from a 4gb card or is 2 the max?
Click to expand...
Click to collapse
i running with a 8gig PNY sdcard
it could theoretically run off of a 512, but you would be a little cramped on space
i guess android doesnt like some of them
so really it doesn't matter how big the card is? do they all have to be formatted to fat32?
Barogi44 said:
so really it doesn't matter how big the card is? do they all have to be formatted to fat32?
Click to expand...
Click to collapse
short answer, yes.
Hey guys...I will try my best to get that video up today. I am about to start recording it.
Am I correct in assuming that step 4-b is create a FOLDER name android on the desktop?
Can I delete those files from the SD when flashing is done?
THANK YOU for the N00B instruction, works great.
stopthebus said:
Am I correct in assuming that step 4-b is create a FOLDER name android on the desktop?
Can I delete those files from the SD when flashing is done?
THANK YOU for the N00B instruction, works great.
Click to expand...
Click to collapse
Yes that is correct, as for deleting the files...I would assume you could. But im not sure. Maybe they are still needed on boot. Never hurts to try though.
im not getting access to the internet after i flashed, am i suppose to edit anything?
im running the donut flash on my sprint vogue.
gigermunit said:
im not getting access to the internet after i flashed, am i suppose to edit anything?
im running the donut flash on my sprint vogue.
Click to expand...
Click to collapse
Wait...NVM you want data to work right?
If you are using donut...try to restart your phone one time. After it boots back up you should see a 3g symbol appear on the notification bar.
If that does not work...go to your apps and open modem. Click once on disconnect and then once more. Then click connect.
Tell me if that works...
n00b, but not an idiot here. been playing with handhelds for many years, new to android though.
I've been watching this forum (CDMA Hero sect.) since I got my Hero, been learning quite a bit. Held off on rooting until there was a official 2.1 release for the device that a ROM could be built around (I wanted full function of the phone and software), did the stupid thing of running the RUU (leaked official), and had to wait until Regaw (thanx!) gave us root...
It would seem the tone of this forum has changed fundamentally since the release of the EVO and an official 2.1 for our Heros. I can understand that perhaps the "thrill" is gone, and since we can all get 2.1 now without rooting, I guess it's "why bother"? (see questions below)
Aaaaanyway...
just did my first root, my first nandroid BU, my first rom flash (hated the rom), and then my first nandroid recover ;-) (what an amazing function, what a relief!) About to try out a 2nd ROM, see if I like it better...
(as an aside to the point of this post, the ROM i tried was DamageR, found it too "messy" for my tastes, and while I can appreciate the work put into it, the options it offers... not my style. was thinking on Damageless, waiting for a "rerelease" of his final. Or perhaps the Aloysius...)
Now that I have my caveats and excuses out of the way, I had a few n00b questions?
1) while I think I have figured out what JIT is, why is it "enabled" in many new ROMs? Is it not an included part of Sense 2.1 from HTC on the Hero?
2) When I was wiping before flash, I was unable to wipe davlik (sp?), insisted I had to do through adb. Is this "normal"?
3) could someone explain what "push" an APK is? Since I have rooted, will I be unable to use the application installer in the HTCsync? (haven't actually tried yet...) And how to "flash" a file? (Example: Dammageless' LWP fix...) I am sure it's something very simple that I am just not getting dues to being unfamiliar with the jargon here.
4) I would really like to use the A2SD feature, and in the recovery screen (where one does the nandroid BUs) it gives me the option to create partitions. I was of course clever enough to BU all data on the card before doing Anything re: root/flashing/etc, but I would like to know if this was needed? Will it just use empty space already present on the card? And in general, I would love to know what I am doing re: A2SD in general, I know "search is my friend", but would someone point me to a quick and succinct link to the "instructions" of doing this? And the different kinds of partitions (ext2? ext3?ext4? huh? why?) I need to know about?
5) And, so why bother rooting now? I know this sounds like a dense question, but really since I don't know enough about it, I guess I am looking for a list of "the obvious reasons" that would not occur to me, or other Android nooblets. LWP will be nice i guess, other launchers, A2SD, bootscreens, OCing... what else?
5) Personally, I am hoping people will rise to the Froyo challenge. While being ignorant of most things involving "programing", or compiling (cooking?), my understanding is that 2.2 runs several times faster due to (a new?) JIT (admitted ignorance again), so does this mean "more efficient"? Would something like a Hero be able to take advantage of that? I realize that we (due to CPU) will never have the highend features (OpenGL, gaming, LWPs being sluggish), so please correct me if I am grossly missing something, besides it not being written for this HW, I see that many other versions written for other devices have been ported to this device.... is this being actively worked on, seen a worthy challenge? Or even a possible one? One that has any benefits?
7) And the n00best question of them all: ROM suggestions? I happen to like Sense, or thought I did because of the 7 screens and other neato features in the UI, but it seems from further reading I can get most features and function out of just about any of them... As an example, what will I gain from flashing Damageless as opposed to the stock RUU? (While Damageless' ROM seems to be the most popular, it is also the least described in his post re: features added/removed, and it's benifits. It would seem like his ROM was "da bomb" when we didnt have 2.1 officially, but since we do now... do I bother with his? Or move to something "more exciting"?
Thank you for your patience.
/n00b-rant
1) JIT just speeds up the phone a bit, although, it's incompatible with Sense :\
2) Don't worry about the dalvik cache unless you're getting problems with booting up a new ROM
3) Push = copying a file to the device (usually when you're putting an .apk in the /system/app/ directory) And about HTCsync? I've never used it before, but it probably wouldn't hurt to try.
4) A2SD? I suggest you back up the files on your sd card before trying anything with it, also, make sure it's a fast card.
5) Rooting? To get rid of annoying sprint bloatware, overclocking, Wi-Fi Tether, etc.
5b) It'll be a little while before we get a stable FroYo (when they release the source, the work will begin)
7) I was about to suggest DarchDroid, but seeing as you like sense.....
(although, 7 homescreens? That's available in just about every homescreen app on the market, my favorite being LauncherPro Beta)
1. The JIT leak we have is buggy at best, and Force close city at worst, but is supposed to be fully featured in 2.2
2. What version of recovery are you running?
3. You can still use the HTCSync installer, but to push system files, you need to use ADB (Google "Android SDK"). You flash a file the same way you flash a ROM, always nandroid backup.
4. A2SD is only really helpful if you have a Class 6 SDcard, and can be hurtful otherwise. A2SD requires a portion of the SDCard to be formated as EXT, so say you have a 1GB SDcard.
256MB EXT (Space for apps)
0MB Swap (basically, "RAM" on your SDCard)
The rest as FAT. In a file manager and you phone, your SDcard will only appear to be ~760MB, as 256 is taken up by EXT.
5. Being able to completly customize everything, getting day by day support to fix bugs instead of waiting on Sprint/HTC, Basically, rooting is what makes your phone YOUR phone.
6. 2.2 is currently available in a very basic install, and will be developed further when the source code is released. Yes, the new JIT is supposedly 450% faster, by being more efficient with how it handles everything, and theorhetically with it, we can expect to see performance increases in everything.
7. I'm a personal fan of DarchDroid, it lacks Sense but he's incorporating ADWLauncher into his next release (Google it, it's amazing.) Damageless is also no longer developing his ROM as the Evo is out. Same thing with Flipz.
Anything else?
Hi guys.
I know that the z4mod can successfully patch a Tab kernel, without any problems (I did it myself, flashed it, and ran it just fine for a few days).
But when I tried to run one of the zip files to switch the file system, everything went nuts and I had to reflash my Tab from scratch.
So I did a little investigating, and as far as I can tell, all that needs to be done to make the whole thing successful is to modify the script in the zip file to correct the mount point names (as they are different from the SGS).
So if anyone around here knows anything about this sort of business, please take a look at it and let me/us all know, cuz it would be GREAT to get z4mod working on the Tab.
Here's the web site if anyone's interested;
http://www.sgscompilebox.dreamhosters.com/
Hi, did you tell ryanZA what results you got? I'm sure he'll be interested to help.
However, thank you for trying, I was about to do the same.
Noob question. What's the benefit of running ext2/3 for the internal partitions versus rfs?
knightnz said:
Noob question. What's the benefit of running ext2/3 for the internal partitions versus rfs?
Click to expand...
Click to collapse
RFS is Samsung's partition format (FAT + journal) that is supposed to be better for flash devices. Apparently it is not so good, and very laggy. Therefore people are switching partitions to ext2/3 or moving and linking stuff to SD card with ext2/3 or jffs2 partition.
jeebspawnshop said:
So I did a little investigating, and as far as I can tell, all that needs to be done to make the whole thing successful is to modify the script in the zip file to correct the mount point names (as they are different from the SGS).
Click to expand...
Click to collapse
Could you explain how you came to that conclusion ?
I was not able to locate my mount points to compare with what you did observe, but i guess we should start with that, then ask ryanZA his thought about what you've found.
Fyi: http://forum.xda-developers.com/showthread.php?p=9629477#post9629477
doloop said:
Could you explain how you came to that conclusion ?
I was not able to locate my mount points to compare with what you did observe, but i guess we should start with that, then ask ryanZA his thought about what you've found.
Click to expand...
Click to collapse
It has been tested by many Galaxy S users. Go to their forum and you will know
evermick said:
It has been tested by many Galaxy S users. Go to their forum and you will know
Click to expand...
Click to collapse
I'm really newb on linux, but i've read a little since last post.
What if we:
1 - dump mount list from a working SGT (terminal or adb shell -> mount ?)
2 - apply Z4mod then SGT won't boot (i assume it creates /etc/.fstab)
3 - edit /etc/fstab to match the dump in step 1
But, how do we read/write /etc/fstab once the sgt is locked ? using some kind of update.zip, or is there some shell service we could connect to, even if some mounts aren't in the right place ?
Unfortunately, everything I could contribute to this idea was in my first post. I know absolutely nothing about Android development, sadly...
But after reading what Deodexed said about volumes not mounting properly during recovery (he's the guy trying to get CWM to work for our Tabs) it seems that maybe that's the reason that z4mod may not work... If the volumes aren't mounted correctly, it can't convert the filesystems.
Maybe what doloop said might work? I hope so. An SGT running on ext2 would rock the socks off anything else out there. God I want it
I like to tweak my ROMs before a flash. i.e. make changes to /system apps; framwork tweaks... etc.
However, whenever I try to replace a kernel zImage or modem binary(using 7z, so as not open archive), I get stuck at a bootloop.
I can replace .apks and .pngs no problem using this method.
Can zImage and .bin be replaced as well? Does redbend also need to be copied? Since .bin and zImage reside in same folder in ROM... which redbend to use if needed?
Thank you?
Whenever I use a new kernel in Loki, or test one personally, I use the version of redbend that the dev included with their kernel initially. Modem does not seem to matter. Are you using a kernel that is meant for the version of Android that matches your rom? If you want to, specifically, what are you using?
This is interesting to me as well, as I did not know you could flash a zip that had been added to, so can you briefly explain how this is done? I would much rather inject my apps than do the titanium backup dance.
I also noticed that SGS Kernel flasher flashes the zImage by simply copying it, and rebooting.
If you are about to tell me I can manipulate my FS to add anything i want, in an update.zip, then sir, I love you.
BTW, if its a simple explanation, whats the redbend file do?
Br1cK'd said:
Whenever I use a new kernel in Loki, or test one personally, I use the version of redbend that the dev included with their kernel initially. Modem does not seem to matter. Are you using a kernel that is meant for the version of Android that matches your rom? If you want to, specifically, what are you using?
Click to expand...
Click to collapse
Exactly what Br1cK'd said. Use the redband that's with the kernel. If pulling the kernel from a rom and a modem from a different one same deal. Also be careful which kernels you use ie: right kernel for phone and version of Android.
d33dvb said:
This is interesting to me as well, as I did not know you could flash a zip that had been added to, so can you briefly explain how this is done? I would much rather inject my apps than do the titanium backup dance.
I also noticed that SGS Kernel flasher flashes the zImage by simply copying it, and rebooting.
If you are about to tell me I can manipulate my FS to add anything i want, in an update.zip, then sir, I love you.
BTW, if its a simple explanation, whats the redbend file do?
Click to expand...
Click to collapse
No sir it is not quite that simple. Proper settings have to be in the update script for everything to install properly. Replacing one file for another of the same name usually works and some files can be added but system apps and additional folders need to be in the update script.
Br1cK'd said:
Whenever I use a new kernel in Loki, or test one personally, I use the version of redbend that the dev included with their kernel initially. Modem does not seem to matter. Are you using a kernel that is meant for the version of Android that matches your rom? If you want to, specifically, what are you using?
Click to expand...
Click to collapse
Br!ck'd, fan of your work and EDT as a whole... great dev team! It happens on any kernel/ROM combo I have tried, which is interesting. Update.zips just carry signed certs and simple copy bash scripts, essentially pushing new files to correct directories, correct? I definitely check for kernel compatability before, I am noobish, not noobtacular
d33dvb said:
This is interesting to me as well, as I did not know you could flash a zip that had been added to, so can you briefly explain how this is done? I would much rather inject my apps than do the titanium backup dance.
I also noticed that SGS Kernel flasher flashes the zImage by simply copying it, and rebooting.
If you are about to tell me I can manipulate my FS to add anything i want, in an update.zip, then sir, I love you.
BTW, if its a simple explanation, whats the redbend file do?
Click to expand...
Click to collapse
1. I believe redbend is samsung tool for flashing volatile memory (NAND).
2. You can use 7zip to explore archives/apks without extracting them and breaking signings. Thus you can simple copy paste .apks/.pngs to appropriate directories without extracting
Most update zips are the actually apk and simple scripts in a flashable container. Roman form EDT has an excellent tool for creating flashable zips if interested... but yes you can manipulate file system of phone and archives. I use adb from recovery. Or android commander is a useful tool as well
EDIT: Explodingboy gives better explanation above
I use untermench's modified redbend. It's the same thing except it removes that ugly blue splash screen every time it is run. That said, I've simply copied over OS and CW into the trigger zips to override the stock kernel. And I never received any reports if it not working from anyone (and I've had releases with both).
Point being, in my experience it doesn't really matter (so long as everything matches). I've done the same for previous modems.
And as you said, all it's doing is copying them to the proper partitions.
Sent from my SGH-T959 using Tapatalk
birgertime said:
I use untermench's modified redbend. It's the same thing except it removes that ugly blue splash screen every time it is run. That said, I've simply copied over OS and CW into the trigger zips to override the stock kernel. And I never received any reports if it not working from anyone (and I've had releases with both).
Point being, in my experience it doesn't really matter (so long as everything matches). I've done the same for previous modems.
And as you said, all it's doing is copying them to the proper partitions.
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
Very cool... thanks.
Also, you are going to think I am crazy... but that ugly blue splash screen can tell me if it is a bad flash or not. When it happens on the top of screen= good flash, on bottom = gonna need to flash again, cause behavior goes wonky. Maybe just bizarre coincidence???
Poser said:
Br!ck'd, fan of your work and EDT as a whole... great dev team! It happens on any kernel/ROM combo I have tried, which is interesting. Update.zips just carry signed certs and simple copy bash scripts, essentially pushing new files to correct directories, correct? I definitely check for kernel compatability before, I am noobish, not noobtacular
Click to expand...
Click to collapse
I've seen you around, you're not noobtacular, but hell I'm still way noobish about a lot of things. Dig the avatar btw. I don't know if I can give an intelligent enough answer to your question, would probably have nobody running Loki by tomorrow, lol. Have you grabbed any logs, or tried to, while its looping?
I have no issues doing this with winrar.
Sent from my Amazing Captivate using the XDA Premium App Infused with Tiger Blood
Br1cK'd said:
I've seen you around, you're not noobtacular, but hell I'm still way noobish about a lot of things. Dig the avatar btw. I don't know if I can give an intelligent enough answer to your question, would probably have nobody running Loki by tomorrow, lol. Have you grabbed any logs, or tried to, while its looping?
Click to expand...
Click to collapse
<Palm to forehead> Probably should logcat... duh.
Just flashed with with custom kernel/modem combo... seems to be booting fine, will report any anomalies.
Only thing I did different was copy zImage and redbend from Kernel.zip
Thanks peoples!