After I updated my G1 to the newest Radio. Radio: 2.22.19.26I
My G1's voice quality has improved. But it would random reboot or not responed after an incoming calling (Ringing) or after the call (when I press the Back KEY).
IF it doesn't reponse, it could be powered on as well. I have to take off the battery and put on the battery again to power the phone.
Drea110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
Sep 2 2008
Serial0
ROM 1.5
baseband 62.50S.20.17H_2.22.19.26I
Kernel 2.6.27-00392-g8312baf
Internal version kila-user 1.5 CRB21 147201 ota-rel-keys,release-keys
I have bought a new battery, but it doesn't help.
Before I updated the Radio, Only voice quality problem. Do I have to update the SPL or ROM ?
Any suggestion? Thanks very much!
I have been having the same issues with mine and no matter what ROM I try I keep having the same issues with random resets.. sometimes on incoming calls etc.. I was starting the think that perhaps it is my phone.
You have a crap SPL installed. Search the DEV forum for the hugely long SPL thread and find yourself the 0.95.3000 SPL -- that is the good one that you want -- includes unlimited fastboot.
The radio image itself isn't known for causing that kind of weirdness unless there is something in the system image that doesn't like it, I suggest upgrading to Android 1.6.
myfriendsh said:
After I updated my G1 to the newest Radio. Radio: 2.22.19.26I
My G1's voice quality has improved. But it would random reboot or not responed after an incoming calling (Ringing) or after the call (when I press the Back KEY).
IF it doesn't reponse, it could be powered on as well. I have to take off the battery and put on the battery again to power the phone.
Drea110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
Sep 2 2008
Serial0
ROM 1.5
baseband 62.50S.20.17H_2.22.19.26I
Kernel 2.6.27-00392-g8312baf
Internal version kila-user 1.5 CRB21 147201 ota-rel-keys,release-keys
I have bought a new battery, but it doesn't help.
Before I updated the Radio, Only voice quality problem. Do I have to update the SPL or ROM ?
Any suggestion? Thanks very much!
Click to expand...
Click to collapse
Thanks very much lbcoder !
I would try to upgrade my SPL and ROM.
Is this one for my G1?
hxxp://android-roms.googlecode.com/files/EngBootloader_v2_NoSigCheck.zip (SPL)
and Another ROM based on Official Donut 1.6
SPL flash first ? then ROM?
Thanks again for your help!
Best regards!
David
Yes, I believe that that is the correct SPL, however, I am not familiar with that source.
I would suggest getting it from HERE: http://forum.xda-developers.com/showthread.php?t=455860 -- I know for fact that it is good from this link.
Note: the so-called "hardspl" doesn't actually offer any benefits. Unlocked fastboot is a free for all. You can literally write anything you like in the world with the proper engineering spl, so it really doesn't make sense to use a HACKED UP SPL.
Thanks lbcoder.
After upgrade to the 0.95.3000 SPL and 1.6ROM
The G1 still would reboot randomly.
Strange! Any suggestion? Before the upgrade of radio, it won't reboot or FReeze.
No idea for me now.
Anyway, thanks very much!
myfriendsh said:
Thanks lbcoder.
After upgrade to the 0.95.3000 SPL and 1.6ROM
The G1 still would reboot randomly.
Strange! Any suggestion? Before the upgrade of radio, it won't reboot or FReeze.
No idea for me now.
Anyway, thanks very much!
Click to expand...
Click to collapse
What 1.6 ROM are you using?
Since we're trying to deal with stability issues at this moment, try installing the official ADP1 system image from http://developer.htc.com/adp.html
And don't forget to perform a user-data wipe.
See if it'll work stable as a fully-stock ADP1. If it does, then start playing with modified firmwares and see where it gets you.
If it doesn't work stable with all official ADP1 software on it, then I would guess that there is some kind of hardware fault.
There is a newer radio out now..
http://forum.xda-developers.com/showthread.php?t=640535
Might be worth a try if all else fails.
goldenarmZ said:
There is a newer radio out now..
http://forum.xda-developers.com/showthread.php?t=640535
Might be worth a try if all else fails.
Click to expand...
Click to collapse
Not related.
Risky.
2.22.19.26 radio is known to be stable. I suggest sticking with that rather than trying out random things from questionable sources.
goldenarmZ said:
There is a newer radio out now..
http://forum.xda-developers.com/showthread.php?t=640535
Might be worth a try if all else fails.
Click to expand...
Click to collapse
been confirmed to work over and over.... also works for me. a lot of people say they also get faster gps lock and better reception... dunno about that for me. it's definitely stable, though.
I had to send out my g1 to HTC, back in july for the same issue. If i pressed down the lower portion of the phone, it would reboot. Like a short/mobo issue. They replaced the board. You may have a hardware fault.
r3s-rt said:
been confirmed to work over and over.... also works for me. a lot of people say they also get faster gps lock and better reception... dunno about that for me. it's definitely stable, though.
Click to expand...
Click to collapse
Go back to 3rd grade.
You do NOT introduce unknown variables into an equation until AFTER you have isolated the problem. If you do, and the problem persists, you will NEVER know the source of the problem.
bigo1087 said:
I had to send out my g1 to HTC, back in july for the same issue. If i pressed down the lower portion of the phone, it would reboot. Like a short/mobo issue. They replaced the board. You may have a hardware fault.
Click to expand...
Click to collapse
Way to read between the lines, Poindexter.
Where do you think I've been leading him?
If he follows exactly what I have suggested and there are STILL problems, then it MUST be hardware defect.
lbcoder said:
Go back to 3rd grade.
You do NOT introduce unknown variables into an equation until AFTER you have isolated the problem. If you do, and the problem persists, you will NEVER know the source of the problem.
Click to expand...
Click to collapse
Actually, since the variable that triggered the problem in the first place was a change of radio, It seems perfectly logical to try another version.
I do agree though, chances of a radio rom alone causing this kind of instability seem remote. I'd look elswhere first.
goldenarmZ said:
Actually, since the variable that triggered the problem in the first place was a change of radio, It seems perfectly logical to try another version.
I do agree though, chances of a radio rom alone causing this kind of instability seem remote. I'd look elswhere first.
Click to expand...
Click to collapse
It is actually a well known side effect of mismatched radio/system combinations.... which is why it is NOT a good idea to try yet another radio, but instead to try a KNOWN VALID combination with KNOWN GOOD radio and KNOWN GOOD system.
That "new" radio that people seem to be jumping into... where did it come from? Some guy named "phreke"? What is in it? You REALLY trust that source? It could be ANYTHING -- it COULD just be hacked to change the version number. There is no telling what it is!!!
Until it comes from a KNOWN SAVE SOURCE (i.e. developer.htc.com/adp.html), I would STRONGLY recommend keeping clear of it!
lbcoder said:
Go back to 3rd grade.
You do NOT introduce unknown variables into an equation until AFTER you have isolated the problem. If you do, and the problem persists, you will NEVER know the source of the problem.
Click to expand...
Click to collapse
Here's what you said in a nice little metaphor (if it was grammatically correct):
You're cars engine blows up. You put a new steering column in your car. Since you changed the steering column, you will never know why your car broke down.
Um... wa? I seriously rofled when I read that. Thanks, bro.
Now, blah blah blah, he said it was the newest radio that caused the problem: so try the newest newest one and see if it works. If that doesn't make sense to you, then damn. There are some good psychiatrists these days. They can probably help you with such abnormal thinking.
Oh: I'm in college. Calculus for that matter.
Reason I state this - this isn't an equation. The correct definition for equation is a mathematical problem. Not a general problem. Argue back "yes it is," then please grab a dictionary. Or use google. Or wikipedia. Or just get brain. <3
Ahhh a pissing match! What fun! LOL.
Probably a good idea for you to evaluate your opponent before just assuming that you can piss further, otherwise you will tend to make a fool out of yourself. Which you have.
You: College student.
You have NOT graduated... otherwise you wouldn't call yourself a student any more. That leaves on the table the possibility that you will FLUNK OUT.
Similarly with your "calculus" course. The fact that you are in the course does NOT imply that you know calculus since you could still FAIL.
On top of that, calculus has no relevance to this discussion at all! Are we trying to come to the integral of .... radio? LOL. How about the partial derivative of engine with respect to steering column?
I would suggest that you enroll yourself in some LOGIC courses -- that seems to be the area where you are suffering. Might help you to learn the meaning of "correlation".
Reason I state this - this isn't an equation. The correct definition for equation is a mathematical problem. Not a general problem. Argue back "yes it is," then please grab a dictionary. Or use google. Or wikipedia. Or just get brain. <3
Click to expand...
Click to collapse
Yes and no.
The nice thing about a "general" problem is that it can be expressed mathematically -- otherwise what is the point of math? In fact, this problem is very simple, we can express it numerically in base-2 (binary) and just use straight BOOLEAN LOGIC to solve it.
Here's our boolean definitions: Works = 1 "true". Doesn't work = 0 "false".
Here's our equation expressed logically:
radio AND spl AND system_image AND hardware = false.
radio = works/true,
spl = works/true,
true AND X = X, applied twice, (this is called the "property of boundedness")
system_image AND hardware = false
TWO VARIABLES -- "system_image", and "hardware".
Either could be bad.
BOTH could be bad.
How do you tell?
(you don't want to add in another variable here, do you?)
By substituting one for a known good.
So we introduce the STOCK ADP1 system image.
system_image AND hardware = ?
You will note the "?" introduced since we no longer know the answer.
system_image = works/true
property of boundedness one more time...
hardware = ? --> if it works with known good system image, radio image, and SPL, then the previous system image was defective, otherwise the hardware is defective.
Note: if we find that the hardware STILL doesn't work, this does NOT prove that the previously tried system image is good, since FALSE AND FALSE = FALSE, and TRUE AND FALSE = FALSE.
Proven logically.
Mathematically.
Using equations.
Imagine that!
And to put the pissing match to rest... I have two university degrees in computer engineering, one of which is a graduate degree. I have taken all of the advanced calculus courses offered, as well as all of the logic courses.
Congratulations kid, you lost the pissing match.
I hope you can learn something from this.
lbcoder said:
Ahhh a pissing match! What fun! LOL.
Probably a good idea for you to evaluate your opponent before just assuming that you can piss further, otherwise you will tend to make a fool out of yourself. Which you have.
You: College student.
You have NOT graduated... otherwise you wouldn't call yourself a student any more. That leaves on the table the possibility that you will FLUNK OUT.
Similarly with your "calculus" course. The fact that you are in the course does NOT imply that you know calculus since you could still FAIL.
On top of that, calculus has no relevance to this discussion at all! Are we trying to come to the integral of .... radio? LOL. How about the partial derivative of engine with respect to steering column?
I would suggest that you enroll yourself in some LOGIC courses -- that seems to be the area where you are suffering. Might help you to learn the meaning of "correlation".
Yes and no.
The nice thing about a "general" problem is that it can be expressed mathematically -- otherwise what is the point of math? In fact, this problem is very simple, we can express it numerically in base-2 (binary) and just use straight BOOLEAN LOGIC to solve it.
Here's our boolean definitions: Works = 1 "true". Doesn't work = 0 "false".
Here's our equation expressed logically:
radio AND spl AND system_image AND hardware = false.
radio = works/true,
spl = works/true,
true AND X = X, applied twice, (this is called the "property of boundedness")
system_image AND hardware = false
TWO VARIABLES -- "system_image", and "hardware".
Either could be bad.
BOTH could be bad.
How do you tell?
(you don't want to add in another variable here, do you?)
By substituting one for a known good.
So we introduce the STOCK ADP1 system image.
system_image AND hardware = ?
You will note the "?" introduced since we no longer know the answer.
system_image = works/true
property of boundedness one more time...
hardware = ? --> if it works with known good system image, radio image, and SPL, then the previous system image was defective, otherwise the hardware is defective.
Note: if we find that the hardware STILL doesn't work, this does NOT prove that the previously tried system image is good, since FALSE AND FALSE = FALSE, and TRUE AND FALSE = FALSE.
Proven logically.
Mathematically.
Using equations.
Imagine that!
And to put the pissing match to rest... I have two university degrees in computer engineering, one of which is a graduate degree. I have taken all of the advanced calculus courses offered, as well as all of the logic courses.
Congratulations kid, you lost the pissing match.
I hope you can learn something from this.
Click to expand...
Click to collapse
Lol.
Quick, I have to run. Wanted to get my laugh in from you.
1. Still not mathematical.
2. It doesn't just have to be the system image, spl, or hardware. Could be an application doing it. Could be a lot of things.
3. Your University Degree doesn't really mean anything.
4. Starting college fresh out of high school with already 2 years under my belt, suggests I probably won't fail. School is too damn easy. I've never once had to study for any test I've ever came across. That's how damn easy school really is.
5. You didn't prove anything except that if one doesn't work it could affect the other one. Who the HELL ever said it couldn't? I just suggested trying a new radio if he thought the radio was the problem. If it still causes random reboots, the it wasn't. Next step is disable applications. This is more likely the cause rather than a hardware failure or a "bad" SPL.
6. Chill out, bro. Take 4 blue footballs and report to me in the morning. 8)
7. I SAID IF THE ENGINE BLOWS UP. I promise you, if your engine blows up putting another steering column won't help you at all. I PROMISE you that. Don't believe me, please feel free to toss a match in your oil, replace your steering column (if you can find it), and start your car. It won't work.
8. You said go back to third grade. I just knew you were going to attack with something like "blah, blah, it is mathematical (because it's really not) what are you in 5th grade math." You're quite predictable, and fun.
Lbcoder, while I do agree with your logic of isolating variables to figure out what is causing the phone issues, your attitude towards others opinions/thoughts could use some improvement. How about you guys put an end to this "pissing match" and help the OP figure out his phone issues.
OP, I would suggest following lb's suggestions of using what has been proven to work together first. If your issues are still there, signs lead to a possible haredware issue. If your problem is gone, start replacing SINGLE components first in hopes to replicate your issues. If single components don't cause the issue, then its quite possibility a combination.
Lbcoder, I'm not against you in anyway, I just think your attitude towards others could be better, IMO.
I've already provided you with all you need in order to understand.
If you insist on STILL failing to understand (I assume to be some moronic childish ego thing...), then that is YOUR LOSS.
I could go through and refute your statements with proof, but that would not be worth the effort, you clearly lack the necessary understanding of logic and mathematics in order for this to work for you.
I suggest you stick to your drama courses. There is some chance that you will pass that.
r3s-rt said:
Lol.
Quick, I have to run. Wanted to get my laugh in from you.
1. Still not mathematical.
2. It doesn't just have to be the system image, spl, or hardware. Could be an application doing it. Could be a lot of things.
3. Your University Degree doesn't really mean anything.
4. Starting college fresh out of high school with already 2 years under my belt, suggests I probably won't fail. School is too damn easy. I've never once had to study for any test I've ever came across. That's how damn easy school really is.
5. You didn't prove anything except that if one doesn't work it could affect the other one. Who the HELL ever said it couldn't? I just suggested trying a new radio if he thought the radio was the problem. If it still causes random reboots, the it wasn't. Next step is disable applications. This is more likely the cause rather than a hardware failure or a "bad" SPL.
6. Chill out, bro. Take 4 blue footballs and report to me in the morning. 8)
7. I SAID IF THE ENGINE BLOWS UP. I promise you, if your engine blows up putting another steering column won't help you at all. I PROMISE you that. Don't believe me, please feel free to toss a match in your oil, replace your steering column (if you can find it), and start your car. It won't work.
8. You said go back to third grade. I just knew you were going to attack with something like "blah, blah, it is mathematical (because it's really not) what are you in 5th grade math." You're quite predictable, and fun.
Click to expand...
Click to collapse
Related
I was attempting to flash 2.x using behnaam and lox's rom.
Rom: http://forum.xda-developers.com/showthread.php?t=592596
Here is the HBoot info previous to my tinkering:
HERC XC
HBOOT-1.41.0000 (HERO20000)
MICROP-0110
TOUCH PANEL-SYN0104
RADIO-1.04.01.09.21
SEP 1 2009,19:18:45
Phone is rooted using adb.
I used unlockr's guide to flash a custom recovery image onto my CDMA hero and that worked fine, here is the guide I followed:
http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
I first moved the radio recommended for the rom by the dev to root on the sd and renamed it update.zip. After, I used the recovery image to wipe, then apply update.zip from sdcard. It seemed to flash fine, as it said please select reboot to complete, which I did, and it completed and rebooted the phone.
Once rebooted it gave me the android installing software image without anything else for a while, then turned off. I cannot seem to awaken my phone with any combo of keys or by plugging it into its use cable. The charging led doesn't even light up anymore.
Well I seem at the moment to be SOL, unless someone can come by and throw me a bone. I really am at a loss as to what I did wrong, as I have always read to do radio first. Not to mention as I watched it install radio it said it was installing radio.
Thanks for the help everyone.
You attempted to flash a GSM ROM to your CDMA phone, this is why your phone is bricked. I'm not sure if its possible to recover, people with more experience than I have can help you there. The problem was flashing a GSM ROM to CDMA. You are not the first to have done it, we all mess up from time to time.
Uuuh Umm...that software was for the GSM hero's NOT THE CDMA Hero.............bless your heart.
Ah **** I thought it was CDMA, guess it was a bad idea jumping into roms while still a noob.
Yea I only got the radio installed, not the rom, although that probably doesn't make a difference.
I don't think the phone can be recovered once you attempt to flash the Radio, but I could be wrong.
Hmm well if worst comes to worst I'm going with what I read on another thread and saying that I was installing the update that it found when I went to phone details and halfway through the update the phone just turned off and won't turn on anymore.
According to the other thread once it is bricked beyond belief and you play stupid they can't prove you wrong.
Best case scenario they replace it, and I won't feel bad seeing as it was a defective phone that is allowing dust to enter under the screen. But that who ordeal is an entirely different rant...lol
Sigh
ftp://xda:[email protected]_Hero_C_Sprint_1.29.651.1_signed_release.exe
Go......Now......Move with haste...
gu1dry said:
I don't think the phone can be recovered once you attempt to flash the Radio, but I could be wrong.
Click to expand...
Click to collapse
Yea, you're right. Flashing a GSM rom on the CDMA won't really break much. It's flashing the radio that bricked it.
flipzmode said:
Yea, you're right. Flashing a GSM rom on the CDMA won't really break much. It's flashing the radio that bricked it.
Click to expand...
Click to collapse
All is lost!!!!
Yep RUU brought back Error 170 cannot connect to phone.
Maybe the sprint repair stores will not be so asshole-esque this time around.
I'm hopeful though, as I have read a few posts about them exchanging it for a new one. Which after a bunch of calls I had hoped to have happen due to the dust thing, but oh well.
Maybe I will get lucky and my brick will actually turn out to be a phoenix in disguise.
unfortunately, flashing the GSM radio on pretty much destroys the phone.
i think its got something to do with the voltage and electricity used by the GSM radios. probably higher than what the CDMA radios use, so you didn't really brick your phone, you 'fried' it in a sense.
sorry bout that... but if you have the equipment protection plan you can probably get it replaced real easily, since the sprint people probably won't really understand what's wrong.
again I am reminded why I dont screw with radios
willowmp said:
Yep RUU brought back Error 170 cannot connect to phone.
Maybe the sprint repair stores will not be so asshole-esque this time around.
I'm hopeful though, as I have read a few posts about them exchanging it for a new one. Which after a bunch of calls I had hoped to have happen due to the dust thing, but oh well.
Maybe I will get lucky and my brick will actually turn out to be a phoenix in disguise.
Click to expand...
Click to collapse
Once you do get it replaced and you want to put a custom ROM on it, look at the first page of this forum and you'll find sticky threads regarding four different ROMs you can put on your phone (two production release and two experimental betas).
I would suggest either MoDaCo's rom or Fresh rom. I use Fresh in mine and had no problems (although I have used MoDaCo's before and also had no issues).
Also, if you want to root the phone, there are also sticky threads that will tell you how to root your phone from Windows, Mac and Ubuntu.
Good luck.
Yep thanks everyone.
Yea I figured once no buttons would do anything and the leds wouldn't even light up for charging that it was pretty much fried. Definitely got that sinking feeling in the pit of my stomach.
I definitely should have come into this section specific to my phone and read this info instead of just doing tons of searches and getting mixed up.
Although I'm hesitant on flashing to a replacement phone if I get one, I think I will but this time make a post just to verify without a doubt. I'm sure many wouldn't mind a simple post asking if this will blow up my phone or not, lol.
Once again thought, thanks for the help. Especially to a noob that made a real noob mistake lol.
Edit: All is well, I contacted sprint chat and they confirmed I will be receiving a brand new phone when I arrive at a sprint store, and with the chat log sent to my email and printed out the repair stores cannot pull any of their gimmicks on me, they are getting a command from sprint HQ after all. This is nice, I kill my phone and I get a brand new one without dust, and this time the invisible shield goes on asap.
willowmp said:
Although I'm hesitant on flashing to a replacement phone if I get one, I think I will but this time make a post just to verify without a doubt. I'm sure many wouldn't mind a simple post asking if this will blow up my phone or not, lol.
Click to expand...
Click to collapse
Well once you are retry the flashing on your new phone, just msg me & I'll give you my contact info & I'll walk you thru it.
willowmp said:
Edit: All is well, I contacted sprint chat and they confirmed I will be receiving a brand new phone when I arrive at a sprint store, and with the chat log sent to my email and printed out the repair stores cannot pull any of their gimmicks on me, they are getting a command from sprint HQ after all. This is nice, I kill my phone and I get a brand new one without dust, and this time the invisible shield goes on asap.
Click to expand...
Click to collapse
while the attempted flash was boneheaded , this (what I quoted) was very smart. I've had them try to reverse the decision and noted on my account in the past. All ended well, but a hard copy of the convo between me and Corporate would have been nice to have.
props for a good idea.
if you don't want trouble with rooting and flashing new ROMs to your phone, try flipz's pre-kitchen. just to try it, i RUU'd my phone and re-rooted it through that app, and its simply amazing. you just sit back and watch, don't even have to do anything.
Ok so its pretty funny but whoever it was who says that once you flash for the first time its addictive, I do have to agree. I will be getting my phone tomorrow because they had to replace it and I will be flashing, although this time I will play it safe and triple check before I get click happy...lol
So what are the danger zones in flashing, like what can brick or kill your phone? I know playing with radios can kill it if the wrong one is flashed, and I know powering off or interrupting a flash will kill/brick, but what else.
I know people said firmware alone usually will not brick you.
willowmp said:
So what are the danger zones in flashing, like what can brick or kill your phone?
Click to expand...
Click to collapse
Well obviously it can brick your phone if you flash the Radio I kid, I kid
willowmp said:
I know playing with radios can kill it if the wrong one is flashed
Click to expand...
Click to collapse
With the CDMA Hero, you do not have to flash the Radio. So if your attempting to flash the Radio, you're doing it wrong.
willowmp said:
I know powering off or interrupting a flash will kill/brick, but what else.
Click to expand...
Click to collapse
Well if the custom recovery is installed (RA-heroc), if the phone looses power while flashing the firmware, you are usually still safe, because you (usually) still boot into the recovery without issues.
Like I already said, if you want I can walk you thru the entire process thru an IM client, Steam, or Skype.
Oh ok thanks, I'm actually headed up to PA for a little trip but definitely will hit you up on that offer when I get back.
Hi,
I'm a new Android user and I'm getting the Galaxy S I9000 tomorrow.
I would like to know the tasks to perform to have a "nice" phone aka:
- which firmware to upload (where to get it if its not on the official samsung site)
- which fixes to run (lagfix app isnt needed if proper firmware is applied right?)
- which apps to install if necessary (not gadgets but the ones that are mostly imperative to get a good experience)
- which other steps to take (eg format the phone to another file system?)
- gps fixes (?)
thanks a lot
Depends if you want to void your warranty on the first day or not.
First thing would be to update to the latest official firmware with KIES (if you can get the damn thing to recognise your phone, mine doesn't anymore...) and see if you have any problems with lag or whatever. My phone didn't have any lag once I used a 3rd party task manager. Now I have installed loads of widgets and clocks and crap like that, my phone does lag quite often, but I don't let it bother me as much as with other people.
For me, rooting isn't something I would want to do with such a new phone, I would rather wait for the official FROYO 2.2 update, if that doesn't fix the niggles I have, then I will consider it.
i dont mind the warranty but as far as i could ready going froyo isn't especially a good idea right now if i want it to be sort of stable
I mean JH2(?) or whatever the latest official one you get from KIES, not the leaked FROYO builds from samsungfirmwares. You might want to wait a month before rooting or whatever anyway just in case there's any hardware problems that might not be apparent. Things like screen issues, bluetooth, etc. You don't want to discover a dodgy bluetooth module or something like that just after you have rooted/flashed it and can't claim on the warranty.
Tachikoma_kun said:
I mean JH2(?) or whatever the latest official one you get from KIES, not the leaked FROYO builds from samsungfirmwares. You might want to wait a month before rooting or whatever anyway just in case there's any hardware problems that might not be apparent. Things like screen issues, bluetooth, etc. You don't want to discover a dodgy bluetooth module or something like that just after you have rooted/flashed it and can't claim on the warranty.
Click to expand...
Click to collapse
Yea but even if he roots.. unrooting it (especially with the one click app) is extremely easy/safe.
Well as far as I could gather, hackeclair seems to be a nice rom with most things fixed inside.
I wonder still how i switch the whole phone from vfat to ext4 (if that's possible) and how to backup the original firmware (yeah forum + search = sucks, results are never what you want lol)
bilboa1 said:
Well as far as I could gather, hackeclair seems to be a nice rom with most things fixed inside.
I wonder still how i switch the whole phone from vfat to ext4 (if that's possible) and how to backup the original firmware (yeah forum + search = sucks, results are never what you want lol)
Click to expand...
Click to collapse
the latest factory ROM JH2 has everything working properly, unlike what you read on the rest of the forum.
AllGamer said:
the latest factory ROM JH2 has everything working properly, unlike what you read on the rest of the forum.
Click to expand...
Click to collapse
thanks
the phone still use vfat tho right?
I'm a linux user, and i'm wondering why it's not on ext ,i'd fear data corruption and poorer performance
i know.. not much of android, learning every minute lol. Suppose will be easier when i get the actual phone tomorrow
bilboa1 said:
thanks
the phone still use vfat tho right?
I'm a linux user, and i'm wondering why it's not on ext ,i'd fear data corruption and poorer performance
i know.. not much of android, learning every minute lol. Suppose will be easier when i get the actual phone tomorrow
Click to expand...
Click to collapse
no exactly, it uses linux format, well at least if you are using the Performance hack dubbed as "one click lag fix"
but for people without lag to begin with, it's just a performance boost
As far as I understood the lag fix, its putting critical files into a ext3 ("linux format") image and leaves the rest on vFat, which fixes the lag, but it's hackish, and slower than if the whole phone was ext3 or ext4. also more corruption prone
I don't know how difficult it is to build a "own" rom, since switching to full ext3/4 would mean wiping the phone
I have never experienced this so called "lag" on my phone, and I have been using it for over a month. Makes me wonder just what exactly are they trying to do on their phones...
Tachikoma_kun said:
Depends if you want to void your warranty on the first day or not..
Click to expand...
Click to collapse
With all due respect, this is actually questionable. I haven't seen Samsung ever officially say that rooting or installing custom firmware voids the warranty, so any chance of showing where they say that?
For rooting, they are unlikely to care, because the change is quite basic. Generally, you can simply flash an official firmware before sending to a service centre anyway. Be aware that often companies charge if problems are caused by corrupt (or beta) firmware though, or there are signs of abuse. But this is generally the same with any media player company.. If you do hand them a phone which uses I9000M firmware, not I9000 though, they probably wont be impressed
Also, if the CPU is burnt out and there is evidence of overclocking, they may possibly be reluctant to accept it under warranty.
If Samsung were TRULY concerned though, they wouldn't have allowed access to USB debugging (which is a feature used only by people messing around, and developers). It is a grey area, and obviously, it makes sense to assume they will void your warranty. HOWEVER, the phones have no way of letting anyone know if they have been rooted before and tech support has better things to do than slow down their queue to aggrevate customers for something which rarely causes an issue.
Do keep in mind though, you can't trust every rom (some may be compromised), and if you don't need root, there probably isn't much sense rooting your phone.
Well i don't mind rooting it anyways
I'll probably need it at some point to toy with it too
bilboa1 said:
Well i don't mind rooting it anyways
I'll probably need it at some point to toy with it too
Click to expand...
Click to collapse
yup, you will find a lot of cool software will not work if not rooted, for even something as simple as a backup program.
andrewluecke said:
With all due respect, this is actually questionable. I haven't seen Samsung ever officially say that rooting or installing custom firmware voids the warranty, so any chance of showing where they say that?
Click to expand...
Click to collapse
From the email I sent them regarding removing the stock apps:
Please note that this e-mail has come from an outbound response system.
Any direct response to this e-mail will not reach the customer care
inbox. If you do need to contact us again please click on the 'contact
us' link located at the bottom of the email or copy the following into
your Browser:
http://erms.samsungelectronics.com/customer/form/contact/contact_uk.html
Dear XXXX XXXX
Customer Reference: XXXXXXXX
Thank you for contacting Samsung Electronics regarding your mobile phone.
Please accept our sincere apologies for the delay in responding to your enquiry.
With regard to your e-mail, you can remove the Samsung Apps from the screen; however you will not be able to remove them fromthe phone without voiding your warranty. To remove them from the front screen, please press the application and drag it to the bottom of the screen.
I hope this has been of some assistance to you. If you do have any
further queries, please do not hesitate to contact us quoting your 210-
reference number.
Kind Regards
Ana
Samsung Electronics UK
Customer Communication Centre
Tel.: 0845 726 7864 (All calls charged at Local Rate)
Homepage: www.samsung.com/uk
[Product] GT-I9000
I mentioned the apps can be removed by rooting the device, and asked if there was a way to remove them without rooting the phone.
Interesting, but in Apple resellers, they seem to officially say the same thing (but from what I've seen, it was never enforced).
well ive got the phone now (woohoo)
i flashed it to JH2 and it's better indeed but it's the wrong model (no big deal it just works)
i got some issues with flashing, have to use a short usb cable without an possible interference else it just fail in the middle.. the phone doesnt get bricked tho, even with bad flash u can still go in download mode and flash with odin.
then i flashed with the newest froyo, and i didn't find any bug, im not sure which bugs are being talked about with it.
moreover I tested the GPS before upgrading and it sucked. I tested it after upgrade and it was perfect accuracy and much faster lock, so it looks like this firmware also fixes gps somehow
That's it for now ;p
All links pulled due to XDA Request after an XDA member complained I was only out for profits to a moderator on a few products I have. Due to the fact I link to a product or two and a few other things in many videos, I was asked to pull any content relating to this.
I will still be offering all this great material at my website. Just go to google and search for MobileTechVideos.
Great work!
I'm sure a lot of users will appreciate the time you put into this. I thank you for them ;-)
Good idea, but allow some constructive criticism. Too long of a video, people don't really need to know how the file structuring works, too long of a demonstration is just going to cause them to get impatient and step ahead of you, possibly bricking or causing their device to malfunction. That's all fine and good, but you forgot to emphasize that new Captivate's don't have 3-button.
It's important, because if they end up bricking it, the only way to recover is to make a usb jig to force the phone into download mode. I would say that to protect yourself, give people the proper precautions to flash. If i were to buy a captivate right now, and try to flash Cog or something with Odin and botched it up, I wouldn't be able to boot it into Download or Recovery, and would most likely have to do a warranty claim.
Long post short, I think you should definitely edit video one and make a notion of the importance of the 3-button fix. Good video over-all, and I always thought it would be a great idea to have a visible tutorial video as some people learn better from videos than they do from text or audibles, but way too much information, being well informed is best case scenario for any scene, as it would lessen the clutter of idiotic searchless support we suffer on here, but 3 parts is too much. Another thing I'd like to mention is if people need to be instructed on how to manage their screen real estate, they probably won't understand any of the video.
geokhentix said:
Good idea, but allow some constructive criticism. Too long of a video, people don't really need to know how the file structuring works, too long of a demonstration is just going to cause them to get impatient and step ahead of you, possibly bricking or causing their device to malfunction. That's all fine and good, but you forgot to emphasize that new Captivate's don't have 3-button.
It's important, because if they end up bricking it, the only way to recover is to make a usb jig to force the phone into download mode. I would say that to protect yourself, give people the proper precautions to flash. If i were to buy a captivate right now, and try to flash Cog or something with Odin and botched it up, I wouldn't be able to boot it into Download or Recovery, and would most likely have to do a warranty claim.
Long post short, I think you should definitely edit video one and make a notion of the importance of the 3-button fix. Good video over-all, and I always thought it would be a great idea to have a visible tutorial video as some people learn better from videos than they do from text or audibles, but way too much information, being well informed is best case scenario for any scene, as it would lessen the clutter of idiotic searchless support we suffer on here, but 3 parts is too much. Another thing I'd like to mention is if people need to be instructed on how to manage their screen real estate, they probably won't understand any of the video.
Click to expand...
Click to collapse
Thanks a lot for the comment. I know it is LONG, but the intent was to give users a Real-Time analysis and be with them step by step. I mentioned the importance of watching the video BEFORE flashing as well a few times. I included a large disclaimer as well in the beginning. This was really a shot to all the "I have no clue how to ROM" folks so I made it as newbie-proof as possible. Try to keep a, I have no clue how to do this and I'm not an IT pro type of mentality when watching as that is the TARGET audience. I'll definitely consider making a shorter version however with time-lapsed instances.
Well, great job, it's something that should definitely be worked on and stickied. If at all possible I would still recommend at most a pause and a text overlay alerting the noobs in question of the 3 button. I work at AT&T, and I deal with captivates every day, and I get a lot of people who come back in with bricked phones that don't have the 3-button fix. I would say, before they try flashing anything, make sure 3-button is present, and if it's not, stress how important it is, and stress how important it is that they follow your directions to the T if it is indeed absent, as it's the only user-friendly way to recover from a brick. I only say this because the fickle community known as the internet might take it out on you if they follow your video and end up with a doorstop.
Nice job dude, should definitely be a stickied topic, you've done a service to all of the XDA members; we won't have to answer as many questions now!
geokhentix said:
Well, great job, it's something that should definitely be worked on and stickied. If at all possible I would still recommend at most a pause and a text overlay alerting the noobs in question of the 3 button. I work at AT&T, and I deal with captivates every day, and I get a lot of people who come back in with bricked phones that don't have the 3-button fix. I would say, before they try flashing anything, make sure 3-button is present, and if it's not, stress how important it is, and stress how important it is that they follow your directions to the T if it is indeed absent, as it's the only user-friendly way to recover from a brick. I only say this because the fickle community known as the internet might take it out on you if they follow your video and end up with a doorstop.
Nice job dude, should definitely be a stickied topic, you've done a service to all of the XDA members; we won't have to answer as many questions now!
Click to expand...
Click to collapse
To truly make sure I'm on the same page as you, are you referring to the 3 button download mode sequence? I teach the step using the 2 button plus USB cable sequence instead. Just making sure.
connexion2005 said:
To truly make sure I'm on the same page as you, are you referring to the 3 button download mode sequence? I teach the step using the 2 button plus USB cable sequence instead. Just making sure.
Click to expand...
Click to collapse
Lots of phones don't have any button combination that works, even if you are just holding the vol buttons and inserting the USB. I think he is just talking in general for people to know if their phones are cable of entering download mode via any way possible before flashing, as it is always a topic of "I bricked my phone help me" status.
flashman2002 said:
Lots of phones don't have any button combination that works, even if you are just holding the vol buttons and inserting the USB. I think he is just talking in general for people to know if their phones are cable of entering download mode via any way possible before flashing, as it is always a topic of "I bricked my phone help me" status.
Click to expand...
Click to collapse
I see. Nothing leading up to entering download mode will brick the phone. So basically if you are unable to enter download mode during this video, literally all you have done is backed up your applications. At this time I assume a post or comment would be made and other methods may be mentioned. See what I mean? Basically if you can't complete the step at the point of the download mode step, you won't risk getting stuck.
these are very nice videos, gret for begginers!
realy sorts things up!
one thing i am missing here...
the id restore, in all my installes i always backup the 2.1 original device id, and i had to implement it int the cog roms or any other using android id changer.
i tried it on 3 different captivates, with different rom versions of cog, all with the same results. maybe you shuld mention it in a comment or something.
my 2 cents.
Yossi
Death_Keeper said:
these are very nice videos, gret for begginers!
realy sorts things up!
one thing i am missing here...
the id restore, in all my installes i always backup the 2.1 original device id, and i had to implement it int the cog roms or any other using android id changer.
i tried it on 3 different captivates, with different rom versions of cog, all with the same results. maybe you shuld mention it in a comment or something.
my 2 cents.
Yossi
Click to expand...
Click to collapse
Excellent point. I did forget about the ID Changer app and that the COG roms and many others were momentarily not reflashing SSID info. I'll try and cook that into the first video.
nice video bro BTW, do you necessarily have to flash back to stock rom using odin or can you just use clockwork and rom manager to do a direct flash?
geokhentix said:
but you forgot to emphasize that new Captivate's don't have 3-button.
Click to expand...
Click to collapse
I have build 1009 (newer than the problematic 1008), and my 3 button works just dandy.
xterminater07 said:
nice video bro BTW, do you necessarily have to flash back to stock rom using odin or can you just use clockwork and rom manager to do a direct flash?
Click to expand...
Click to collapse
You can but nobody really recommends it. Flashing back to stock is just the easiest way to ensure Vodoo or other lagfix options don't get in the way of the way the ROM was natively intended to install. I wanted to do a full wiping flash. The master clear really is going above and beyond but hey I was being an over achiever...
I think this is really nice, but it seems like there is a gap between the end of video one and the beginning of video two. You explain how to boot into download mode, but then you never actually show the flashing back to stock process, and instead skip right to re-rooting the newly flashed phone.
plus_M said:
I think this is really nice, but it seems like there is a gap between the end of video one and the beginning of video two. You explain how to boot into download mode, but then you never actually show the flashing back to stock process, and instead skip right to re-rooting the newly flashed phone.
Click to expand...
Click to collapse
I can't believe I missed that. I recorded all of that footage and have it in the single bulk file but apparently missed it when cropping the file for multi-part uploading. I'll fix it tonight and thank you for pointing that out.
EDIT: I actually didn't miss that. My video project shows I cropped correctly but after producing the software unexplainably cropped incorrectly. I'm patching with the latest update and then hoping I can correctly produce that clip. I'll reupload soon. I just didn't have 30 mins available at the end to full watch the clips.
OK CLIP 2 SYNC ISSUES RESOLVED. ALL CLIPS ARE NOW INLINE...
I'm new to Android but I have some decent enough tech skills from a career in IT and tinkering. However I was absolutely terrified to do this just because of the harsh reality that bricking my phone is possible. This guide was immensely helpful and I'll probably attempt to flash to 2.2 soon. Thanks for all your work!
Should be sticky! v
I've just found your videos and while I haven't watched them yet (it's too late, tomorrow.....) I have one comment - please don't edit out info about file structure, etc. I need that kind of info! I'm hoping to learn enough to get brave and take the plunge
MikeyMike01 said:
I have build 1009 (newer than the problematic 1008), and my 3 button works just dandy.
Click to expand...
Click to collapse
Me too - purchased at the beginning of October
My phone has been through a lot and seems un-brickable or at least I can always get back into download mode
Sent from Cyanogen... or something similar
Un-root And update download the file from here: http://forum.xda-developers.com/showthread.php?t=975888 and apply. This will give you stock and S-on.
That simple!
Thanks for the info, but the fun is just beginning. This is always good to have just in case you have to return it.
You should be able to load any stock RUU. As long as the hboot and the recovery exist in the RUU, it should return you to a stock condition.
Jaywan, how about a simple root and s-off?
It's simple to make a app run the commands needed to make a one click rooter. And easier to edit a already working rooter to work for this phone. Idk why he don't want the one click released. Took me 30 minutes to root.. maybe he only want people to root using his method. I not gonna step on his toes by posting one tho...
Sent from my ADR6400L using XDA Premium App
ok ok, I hear yah. I will just bite the bullet and type in all 90 of the commands tomorrow when I get off work.
BTW, I left the MT4G and came over to verizon also. I went to the SGS4G before I left tmobile. Lack of dev support for that phone made me give it up. Thanks for coming over to the Thunderbolt.
also, take a look at this thread I started. Somethings up with this one click unroot deal.
http://forum.xda-developers.com/showthread.php?t=1004567
Jaywan said:
It's simple to make a app run the commands needed to make a one click rooter. And easier to edit a already working rooter to work for this phone. Idk why he don't want the one click released. Took me 30 minutes to root.. maybe he only want people to root using his method. I not gonna step on his toes by posting one tho...
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I heard him meantion he wants people to learn adb so if something happens further down the line they can use it
Seriously I'm with him, the hardest part about adb for me was getting it installed. The root was easy and took 30 min
sent from my Thunderbolt
For what its worth, he said feel free to post the one clicks, just give credit. I dont honestly care however, copy, paste, seemed simple enough. Was no where near as hard as the original root method for the DInc.
Sent from my ADR6400L using XDA App
The only legitimate reason I could buy about not wanting a one click released, is if SOMEHOW it would make our phones vulnerable to some sort if attack.
As background, I've ben using custom roms since my old g1 was new and JesusFreke was just getting started and I dont ever recall ANY dev with holding something that would make the users lives easier. In recent history I've done a ton of flashing roms with both mine and my wifes old vibrants and the only time I used adb was if I wanted to push a file to the phone without mounting it on my computer.
PERSONALLY, this whole mess sounds of ego and elitism. I am incredibly greatful to the devs who have paved the way, but fearful of what they are trying to do. No one should have the right to prevent another from releasing something, it's in gross violation of the gpl. If a dev wants to code something under a different license, fine. However it needs to be clearly annotated as such, and devoid of any gpl work itself. In other words, it basically can't contain anything related to android unless it was developed 100% blind through an emulator.
Sent from my ADR6400L using Tapatalk
Can't step on my toes, I got stealtoe boots...
I want a chance to review any one clicks before release. I REALLY want new users to understand what they are doing BEFORE they try one clicking.
I want proper md5sum verifications, I want proper warnings, etc.
I already stopped the release (until fixed) of one 1click root that would of been REALLY bad for the community and anyone using it.
Ppl need to stop blaming me for this crud.
ShanDestromp said:
The only legitimate reason I could buy about not wanting a one click released, is if SOMEHOW it would make our phones vulnerable to some sort if attack.
As background, I've ben using custom roms since my old g1 was new and JesusFreke was just getting started and I dont ever recall ANY dev with holding something that would make the users lives easier. In recent history I've done a ton of flashing roms with both mine and my wifes old vibrants and the only time I used adb was if I wanted to push a file to the phone without mounting it on my computer.
PERSONALLY, this whole mess sounds of ego and elitism. I am incredibly greatful to the devs who have paved the way, but fearful of what they are trying to do. No one should have the right to prevent another from releasing something, it's in gross violation of the gpl. If a dev wants to code something under a different license, fine. However it needs to be clearly annotated as such, and devoid of any gpl work itself. In other words, it basically can't contain anything related to android unless it was developed 100% blind through an emulator.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
Are you a troll or do you really believe all that crock you just posted?
The issue with one clicks was an increased risk of bricking with this method. And where does the GPL even come in here at, any GPL code we used as released before the root was even up.?
I stopped a one click from being released today that not only left your phone vulnerable to an attack, but also left you with an outdated, faulty radio and other faulty firmware.
Either you are a troll, have a personal issue with me, or have a seriously problem.
jcase said:
Can't step on my toes, I got stealtoe boots...
I want a chance to review any one clicks before release. I REALLY want new users to understand what they are doing BEFORE they try one clicking.
I want proper md5sum verifications, I want proper warnings, etc.
I already stopped the release (until fixed) of one 1click root that would of been REALLY bad for the community and anyone using it.
Ppl need to stop blaming me for this crud.
Click to expand...
Click to collapse
omfg most of us been rooting since g1 came out THE FIRST DAY come on if modaco was working on this aka paul. like his app visionary he would have it out.... who cares most of us know adb... but i dont want to turn s off i just want root access to remove **** and do a couple mods. why is this such a big fuc88ing deal just release the app and we will all be grateful of who release one click root
jesemalave1 said:
omfg most of us been rooting since g1 came out THE FIRST DAY come on if modaco was working on this aka paul. like his app visionary he would have it out.... who cares most of us know adb... but i dont want to turn s off i just want root access to remove **** and do a couple mods. why is this such a big fuc88ing deal just release the app and we will all be grateful of who release one click root
Click to expand...
Click to collapse
o.m.g.
Dude it doesn't work that way on this phone. It is not the G1, z4/visionary/anyonphoneroot does not work, root REQUIRES adb (even with one click).
Fact is, you can't root this phone, temp or perm, one click or not, without ad.
If you can find a way, please do. We are awaiting your one click, root that does not use adb, and is not dangerous.
fyi one click has been released, hours before your post.
Code:
while (true) {
facepalm();
}
I'm going to cut out all your attacks, because you've clearly missed my point in its entirety and decided to get defensive.
jcase said:
The issue with one clicks was an increased risk of bricking with this method. And where does the GPL even come in here at, any GPL code we used as released before the root was even up.?
Click to expand...
Click to collapse
I brought the GPL in because like it or not, you don't have the right to say who can and cannot release anything regarding "one click" roots UNLESS you yourself made an essential piece of the current rooting method, that is in its entirety your own. To make an analogy, you can't patent (and thus control the distribution) to a Toyota Carolla, simply because you assembled the whole thing from spare parts. If you were to completely design and fabricate a motor vehicle without using off-the-shelf parts you WOULD have that right.
There is nothing personal in my view of this against you, I don't hold any grudges against anyone; but its the mentality here that irritates me, and it just happens that you're the one that posted it:
jcase said:
I want a chance to review any one clicks before release. I REALLY want new users to understand what they are doing BEFORE they try one clicking.
Click to expand...
Click to collapse
I understand you want people to learn; I really do. I've done enough work with computers that I too get really irritated at people who demand answers to questions answered much faster by doing a quick search. I also understand why you want to avoid screw ups because of a poorly made one click. HOWEVER, just because you WANT people to get them cleared through you first; does not mean they HAVE to or that you have a right to demand that they do.
jcase said:
I stopped a one click from being released today that not only left your phone vulnerable to an attack, but also left you with an outdated, faulty radio and other faulty firmware.
Click to expand...
Click to collapse
And thus you've found the wonder of open source software. Sometimes crap gets released. But guess what? Every one of us here are supposed to be adults, or at the very least the authorized users of our phones; which means that if we screw something up, or use something that screws up; its our own damn fault.
The whole purpose of OSS is to allow freedom of ideas and development. I don't know how old you are, or what your experience with OSS outside of Android phones are; but I personally have seen PLENTY of OSS software that started out as utter crap, turn into wonderful software packages. Maybe you're old enough to remember KDE2 vs KDE4, or how about pre v1 Mozilla vs modern versions of Firefox.
I'm not some OSS nutter; I've got no problem with closed source or proprietary software; just a problem with others trying to control things they have no right to.
All that having been said, maybe you DO hold software rights related to some piece of the current rooting method. If so I've seen nothing indicating so, nor anything indicating that any part of the rooting method is not OSS; however if you DO, then you have my apologies, as you would indeed have control over distribution of that specific piece. You still would not be able to prevent distribution of any one click that were released provided they simply had users download your piece separately.
You are missing the point, and obviously did not read anything. This will be my last time wasting time with you until then.
I never said THEY CANT release, I asked them not to, until we had a safer way and time to check it out. Big difference. I stopped one from going out today that would of more or less ruined phones until someone fixed them.
Fact is, MOST of the one clicks I have seen lately, violate the GPL, why don't you go after them, or hell even better we could really use you to go after HTC (in all seriousness).
ShanDestromp said:
I'm going to cut out all your attacks, because you've clearly missed my point in its entirety and decided to get defensive.
I brought the GPL in because like it or not, you don't have the right to say who can and cannot release anything regarding "one click" roots UNLESS you yourself made an essential piece of the current rooting method, that is in its entirety your own. To make an analogy, you can't patent (and thus control the distribution) to a Toyota Carolla, simply because you assembled the whole thing from spare parts. If you were to completely design and fabricate a motor vehicle without using off-the-shelf parts you WOULD have that right.
There is nothing personal in my view of this against you, I don't hold any grudges against anyone; but its the mentality here that irritates me, and it just happens that you're the one that posted it:
I understand you want people to learn; I really do. I've done enough work with computers that I too get really irritated at people who demand answers to questions answered much faster by doing a quick search. I also understand why you want to avoid screw ups because of a poorly made one click. HOWEVER, just because you WANT people to get them cleared through you first; does not mean they HAVE to or that you have a right to demand that they do.
And thus you've found the wonder of open source software. Sometimes crap gets released. But guess what? Every one of us here are supposed to be adults, or at the very least the authorized users of our phones; which means that if we screw something up, or use something that screws up; its our own damn fault.
The whole purpose of OSS is to allow freedom of ideas and development. I don't know how old you are, or what your experience with OSS outside of Android phones are; but I personally have seen PLENTY of OSS software that started out as utter crap, turn into wonderful software packages. Maybe you're old enough to remember KDE2 vs KDE4, or how about pre v1 Mozilla vs modern versions of Firefox.
I'm not some OSS nutter; I've got no problem with closed source or proprietary software; just a problem with others trying to control things they have no right to.
All that having been said, maybe you DO hold software rights related to some piece of the current rooting method. If so I've seen nothing indicating so, nor anything indicating that any part of the rooting method is not OSS; however if you DO, then you have my apologies, as you would indeed have control over distribution of that specific piece. You still would not be able to prevent distribution of any one click that were released provided they simply had users download your piece separately.
Click to expand...
Click to collapse
I agree!! If anyone is in violation of GPL license it is HTC.
And once we have that kernel source in the hands of the community amazing things will happen!!
Once the custom kernels start flying you will see the TB doing crazy things. I can only imagine 2GHz speeds or insanely efficient battery life (to name a few)!
ShanDestromp says "And thus you've found the wonder of open source software. Sometimes crap gets released. But guess what? Every one of us here are supposed to be adults, or at the very least the authorized users of our phones; which means that if we screw something up, or use something that screws up; its our own damn fault. "
This has got to be the stupidest statement I have read in a long time, I can guarantee, If you used a 1-click method and it bricked your phone you would be screaming " where's the oversight in this forum, I cant' believe that that mods would allow faulty programming to be posted."
Jcase I for one am glad you are stepping up and doing what needs to be done to prevent a potential $750 brick, thank you sir.
jcase said:
I never said THEY CANT release, I asked them not to, until we had a safer way and time to check it out. Big difference. I stopped one from going out today that would of more or less ruined phones until someone fixed them.
Click to expand...
Click to collapse
I'm not privy to any private conversations, nor do I read every thread here on XDA, so my general impression, which I'm sure is shared based upon what others have said, was of a more explicit "No you cannot," not a "do you mind if I take a peek first". Furthermore, I did not name any one individual "responsible" for any blockade; I only began to interact with you once you brought yourself into the thread. Beyond that, if you go back to my original post, I explicitly thank the people who made root possible at all.
jcase said:
Fact is, MOST of the one clicks I have seen lately, violate the GPL, why don't you go after them
Click to expand...
Click to collapse
For starters I don't know much, if anything about them other than they exist. Unless I personally see something that I think is in violation, I assume good faith. I certainly don't seeking violations.
jcase said:
or hell even better we could really use you to go after HTC (in all seriousness).
Click to expand...
Click to collapse
I'm guessing you're referring to the fact that they didn't release the kernel source as expected this week? I'd mentioned it in another thread, though I don't recall which anymore; but from what I recall of GPLv2 developers have 60 days from the "official" binary release to provide source. To expand on that, HTC has 60 days from when the phone officially went on sale, to provide upon request the source code to any GPL licensed software, however it is version specific. That is to say 60 days from March 17th to make available the source to the firmware that was on the phone when released (since to the best of my knowledge there have been no other OFFICIAL firmware versions released).
Of course any such source will inherently exclude any third party proprietary software, for example if HTC used a closed-source bluetooth stack (not saying they did, just a hypothetical example). Additionally, there isn't any specific method to release stipulated. If HTC wishes they could mail out copies of the source on 3.5" floppies and still be within the rules; and all this assumes GPLv2 is how Android is licensed. If its v3 then I honestly have no clue if any time provisions exist.
I just want to reiterate, I have no ill-will to you nor anyone else. It appears as though the whole issue stems from miscommunication.
I work in a large company. We have 40 Wildfires (long story).
I want to build up what we want to have on one phone.. then image it and push to the rest..
Any ideas????
insanemal said:
I work in a large company. We have 40 Wildfires (long story).
I want to build up what we want to have on one phone.. then image it and push to the rest..
Any ideas????
Click to expand...
Click to collapse
Default or cm7
Sent from my HTC Desire using Tapatalk
Not sure yet. Both if possible. I would like to run CM7 but im not sure the warrenty will cover it.. at least if it was a modded stock rom they would have less case to clam we did something horrible to it. But if I have to have a custom rom I would want to keep the stock boot animations.
Your warranty will be lost in case you flash CM or any custom modded stock ROM.
Yeah probably,
But this is not the point.. I need to customise 40 of them...
If I can't use a modded stock rom, I don't care.. I just have no idea of the easyest way to get this done.
Build the ROM to your liking on on one phone, take a Nandroid backup of that, and provide that to the 40 other phones, and restore from it. It should work. I can't think of any method to 'Push' it yet.
Warranty should not be an issue. RUUs are always there if you mess something up. My screen got messed up, and with an RUU I made it completely factory (including the HBOOT - it replaces it) and gave it to HTC service, and they are replacing it under warranty now.
nhnt11 said:
Warranty should not be an issue. RUUs are always there if you mess something up. My screen got messed up, and with an RUU I made it completely factory (including the HBOOT - it replaces it) and gave it to HTC service, and they are replacing it under warranty now.
Click to expand...
Click to collapse
I hope they don't give it back to you with factory updated 2.2.1. This sort of thing happened to many around here.
Anyhow, I was only suggesting that because the OP seems to want his phones for business purposes, and, I thought, for such situations, warranty and productivity is the most important factor, and, terms like modding and customization take a back seat.
3xeno said:
I hope they don't give it back to you with factory updated 2.2.1. This sort of thing happened to many around here.
Anyhow, I was only suggesting that because the OP seems to want his phones for business purposes, and, I thought, for such situations, warranty and productivity is the most important factor, and, terms like modding and customization take a back seat.
Click to expand...
Click to collapse
I told the guy 3 times not to touch the software, and he assured me he won't lol.
Me: Will you update the software or anything?
Him: No problem. We'll do it for you if you want.
Me: I DON'T WANT IT OMG.
Him: Sure we won't update then.
They seem to know about root and stuff
I agree though, if it's for business then CM7 doesn't really seem appropriate, although it would make my respect for the business ++
nhnt11 said:
I told the guy 3 times not to touch the software, and he assured me he won't lol.
Me: Will you update the software or anything?
Him: No problem. We'll do it for you if you want.
Me: I DON'T WANT IT OMG.
Him: Sure we won't update then.
They seem to know about root and stuff
I agree though, if it's for business then CM7 doesn't really seem appropriate, although it would make my respect for the business ++
Click to expand...
Click to collapse
But they are giving you a new device ? Than it will have the updated Hboot lol ! Yeah offcourse they know, that's why they updated hboot!
h4oxer said:
But they are giving you a new device ? Than it will have the updated Hboot lol ! Yeah offcourse they know, that's why they updated hboot!
Click to expand...
Click to collapse
no only replace screen.
i meant the service center guys know about it. not HTC lol.
3xeno said:
Build the ROM to your liking on on one phone, take a Nandroid backup of that, and provide that to the 40 other phones, and restore from it. It should work. I can't think of any method to 'Push' it yet.
Click to expand...
Click to collapse
Cool, I didn't realise a Nandroid could be restored to other phones.
Also we got lucky, they are running HBOOT 0.80.0008
Seems the OTA updates didn't apply. So the hard part will be rooting them all... wow.. so slow.. I will prolly use CM7 as a base.. But I'm not sure.. I need a way to Have GMAIL but not Market. Can I add the GAPP's pack and then remove the market.apk? Also we want NONE of the stock 'bigpuddle' crap on the phones as the users only have small data allowances. Hmmm Also the GAPPS' pack is it gmail maps and Market? Because we are only 50/50 on having email on the phones.. if it is.. I might just leave it out all together.