Related
I just bought a brand new T-Mobile G1 Black from Craigslist for someone in my family. While i was rooting the phone i decided to use Haykuro SPL. As soon i rebooted the phone it bricked on me and now i am pretty much freaking out.
Does Someone Knows How To Fix It ? And do you think HTC will take it back even tho i didnt bought from T-Mobile and dont even have the receipt ?!
Please guys help me.
did you bother checking which board the phone was using? pvt or dvt? did you know some people were having issues with the new spl? and how is it bricked? won't boot? stuck at g1 screen and can't enter recovery\bootloader?
try theses instuctions and tell me if they work make sure you pull the battery before holding power and home if it get you to the recovery screen you should be good. also try it with power camera
1. pulled sd card out put it in a sdcard reader and loaded the enginering bootloader
2. took battery out
3. put sd card back into g1
4. held power + home
5. while still holding power + home slid battery back in
6. when recovery showed up hit alt+w and alt+s
7. popped sdcard back out and and loaded my favorite rom version
8. put sd card back in
9. held power + home and flashed the rom and all came alive
First off, no, HTC will not take it back (maybe if you pack 200 dollars or so with it the will). What do you mean "bricked"? Can you still get into the bootloader or not? If you can't, then sorry, it is bricked for good (atleast as far as we at XDA know)
yeah unfortunately i cant make it to the bootloader...it stays on the T-Mobile G1 sign...
davil124 said:
yeah unfortunately i cant make it to the bootloader...it stays on the T-Mobile G1 sign...
Click to expand...
Click to collapse
??
The SPL loads before the G1 logo. Are you pressing back+power?
Why o people why do you not read the threads on this before you do anything. Geez. Do you not study and take precautions before you do anything?? Your most DEF screwed. If you cant get into any of the bootloader, then its bricked and no one has found a way to fix it "yet"( hopeing someone does). Please for the love of God. READ READ READ.
@futango, because people are dumb and get excited before reading, making their 2-300 dollar phone a 2-300 dollar brick. Its cool, if you saw how disastrous this forum was you would see how many topics there are on this issue, and you wouldn't have this problem. Hard lesson learned but oh well, have to deal with it until someone finds a fix, to which there isnt one now. Too bad. Next time you'll read hu? Reading is easier than spending that hard earned money....unbelieveable.
Reported.
Davil124, its seems like people are bickering again instead of trying to help you. lol.
Like what jashu said, after flashing the haykuro SPL, try holding BACK + POWER, to enter recovery mode. When in recovery mode, remove your memory card (place it in a card reader), and delete the update.zip that contains the haykuro SPL. Proceed to copy the update.zip that contains a hacked ROM (JF1.5, ADP1.5H, etc.) to your memory card. Then flash the ROM - update.zip by pressing ALT + S. This must be done after updating to the haykuro SPL (almost everyone forgets to do this, and end up looping.) Then just let it boot up (it may take a few minutes, so don't panic and pull the battery, just let it load.)
andonnguyen said:
Davil124, its seems like people are bickering again instead of trying to help you. lol.
Like what jashu said, after flashing the haykuro SPL, try holding BACK + POWER, to enter recovery mode. When in recovery mode, remove your memory card (place it in a card reader), and delete the update.zip that contains the haykuro SPL. Proceed to copy the update.zip that contains a hacked ROM (JF1.5, ADP1.5H, etc.) to your memory card. Then flash the ROM - update.zip by pressing ALT + S. This must be done after updating to the haykuro SPL (almost everyone forgets to do this, and end up looping.) Then just let it boot up (it may take a few minutes, so don't panic and pull the battery, just let it load.)
Click to expand...
Click to collapse
davil124 thats what ur sopposed to do.. i recall there's other threads on here that talks about bricked phones. im not gettin on u, people just need to understand.. if u have problems find the right thread to put ur post up.. someone will answer ur question
futango said:
Please for the love of God. READ READ READ.
Click to expand...
Click to collapse
Futango is right though. If you are going to jump into a hack without reading, you get what you deserve and you deserve what you get.
EVERYTHING ON THIS FORUM IS POTENTIALLY PHONE BRICKING.
Once you fully realize that, then you will think twice about flashing whatever update.zip someone casually posts on here.
p.s. can everyone stop treating Haykuro like some kind of god? He got a hold of some HTC pre-release builds and posted em on here. That's it.
jashsu said:
Futango is right though. If you are going to jump into a hack without reading, you get what you deserve and you deserve what you get.
EVERYTHING ON THIS FORUM IS POTENTIALLY PHONE BRICKING.
Once you fully realize that, then you will think twice about flashing whatever update.zip someone casually posts on here.
p.s. can everyone stop treating Haykuro like some kind of god? He got a hold of some HTC pre-release builds and posted em on here. That's it.
Click to expand...
Click to collapse
Jashsu you sound really jealous. lol jk. But I do agree with you. First jesusfreke was god, now haykuro. Isn't that blasphemy? lol.
But hopefully people will begin to realize the risks involved with flashing custom firmware. I've seriously looped at least 12 times (bad md5 checksums, faulty memory card, u name it lol), wiped over 100 times, but thankfully found solutions to every problem I've faced, but that was because I did my research before jumping the gun. I'm fully aware of all the risks involved, so all I can say to everyone is, proceed with caution.
andonnguyen said:
Jashsu you sound really jealous. lol jk. But I do agree with you. First jesusfreke was god, now haykuro. Isn't that blasphemy? lol.
Click to expand...
Click to collapse
I'm not jealous about having bricked about a dozen phones, i'll tell ya that
People should be approaching updaters with a serious heaping of caution, especially for something like the SPL. I won't blame Haykuro for not having fully tested the SPL before releasing it, but honestly he probably should have put up more than just a link and a wink (like I dunno some huge warnings and disclaimers). And for sure those links should have been pulled the moment that news of bricks came in. Just my two cents...
Well this sucks to hear man. Loosing a G1 is never fun...But the recent threads about the new SPL made it clear that it was only designed for the PVT. And from the looks of it, you probably have a DVT or some other derivative.
jashsu said:
I'm not jealous about having bricked about a dozen phones, i'll tell ya that
People should be approaching updaters with a serious heaping of caution, especially for something like the SPL. I won't blame Haykuro for not having fully tested the SPL before releasing it, but honestly he probably should have put up more than just a link and a wink (like I dunno some huge warnings and disclaimers). And for sure those links should have been pulled the moment that news of bricks came in. Just my two cents...
Click to expand...
Click to collapse
Haykuro is not to blame for anything. He also shouldn't have put up more info because....he can't. All of this is pretty much undocumented. It's all trial and error. If it wasn't for people like Haykuro, Dude, or JF...etc. We wouldn't have any of these new updates to our phones.
OP you should of read this first before attempting to use the new SPL.
READ THIS FIRST if you are flashing Haykuros new SPL
http://forum.xda-developers.com/showthread.php?t=516433&page=10
Bavilo said:
Haykuro is not to blame for anything. He also shouldn't have put up more info because....he can't. All of this is pretty much undocumented. It's all trial and error. If it wasn't for people like Haykuro, Dude, or JF...etc. We wouldn't have any of these new updates to our phones.
Click to expand...
Click to collapse
Let's imagine for a second that there was a room full of really thirsty kids. I walk in with an unmarked bottle of a strange looking liquid. I can't describe it because I myself don't know much about it. Would you say it would be irresponsible on my part to just leave it there with those kids who don't know any better? More to the point, would you blame me if one of those kids got sick after drinking it?
In a more perfect world, everyone would do a lot of prior research, understand the risks associated with experimental hacks, and fully accept the consequences of bricked devices. Unfortunately this is not a perfect world.
alright a appreciate some of you for been nice and try to help (that was the point for me writting this at first). And for the ones been rude and trying to act all smart ! F&@$ Off ! alright ? i need help and i learned from my mistakes. If you think i acted not rational or smart, you dont have to say anything. Just stay quite and move on and help others that need more help in the forum. Just dont come and start saying stuff that are not helping at all, and for the record i did not blame nobody for the mistake I made. I personally got a G1 running the SPL just fine, and i just didnt know that there were 2 different boards running on the G1's. So please stay away if you are not going to say anything positive, and try to help. thank you.
that sucks
Cant we all just get along
Two months agoi tried updating my phone. I did a reboot after loading a update.zip file from my sd card and my G1 didnt turn on at all. No g1 screen or any kind of response.
And now my G1 is bricked.
My question is do you think they will exchange it for me still? What should I say happened?
Alright this is enough. I think instead of treating users with bricked phones as noobs and lecturing them about being careful, we get to the point and try and help.
First off, we have a whole thread dedicated to the bricked phones now. One member is working on schematics to build an actual USB wire for a force install of a SPL to possibly repair the bricked phone issues. Right now, the plans are done, so we will see if he is able to construct the cable. However, the schematics are already uploaded, so maybe you should give a shot at it. look for the G1 brick technical think thank thread.
Hi,
my Device is a 32B Device.
i tried to change my vodafone Splash-Screen, so i followed this howto:
showpost.php?p=3843361&postcount=7
nk02 said:
with windows or linux (on wine + net framework 2):
1)download this
password "androidsocket"
2)with createG1splash create your splash (mysplash.rgb565) from a gif or png 332x498
3)put the splash file ( mysplash.rgb565 ) in sdk tools/ directory
4)boot the magic in fastboot mode (witch back+power)
5)on terminal (in sdk tools/ path):
Code:
fastboot flash splash1 mysplash.rgb565
fastboot reboot
(you need [here is a link, but as a new user i cannot post links, look at the original post] haykuro spl to flash splash screen!)
in this thread there are some splash jpg/gif !
Click to expand...
Click to collapse
This howto is linked in the newbie topic btw.
So i flashed the haykuro.spl using the recovery Menu(i booted it from fastboot), but now my phone doesnt work.
Power + Back at the start => no reaction.
Power + Volume Down => no reaction
Power + Home => no reaction
It doesn't boot anymore, the Vodafone Splash Screen freezes.
And if i plug it on my pc, the usb device cannot be recognized.
I think i bricked my Magic ...
I don't understand how this could happen!?
Any Suggestions?
Did you just say you flashed Haykuro's Death SPL?
brick. sorry, no response to "special" boots and no usb = brick
could you possibly list what you did, start to finish, just so we can better understand what's happened? i'm not entirely sure - did you successfully get a new splash screen and then change the spl and that's when it all went bad, or what?
personally, i can live with just about any splash screen, the risks involved with changing it are certainly not worth it imho...
it does nothing at all ? or you got the blue led? if its same advenced as a brick (it does absolutly nothin can be a specific hardware problem not big deal it happend to me because of that even the jtag didn't work )
FirstNoobToBrickHisPhone said:
Did you just say you flashed Haykuro's Death SPL?
Click to expand...
Click to collapse
I second that.... Did you honestly flash this, to an already rooted phone... just to change your spalsh screen?
I keep forgetting how hard it is to READ and COMPREHEND things now a days.
Sorry, but your phone is done for. No amount of questions you ask will change that.
It's people like this that make me afraid to ask questions around here.
kinstinct06 said:
Hi,
Power + Back at the start => no reaction.
Power + Volume Down => no reaction
Power + Home => no reaction
It doesn't boot anymore, the Vodafone Splash Screen freezes.
And if i plug it on my pc, the usb device cannot be recognized.
I think i bricked my Magic ...
I don't understand how this could happen!?
Any Suggestions?
Click to expand...
Click to collapse
Dude, I JUST started having this issue as well! I have a 32a and I was updating my Radio/SPL for 32a Devices and now I can do nothing... I just got the phone yesterday haha... so yea
And replaced at Tmobile a few hours ago
Good thing we have all these (to put it nicely) less than average intelligent human beings to keep hiking up costs for the rest of us with their fraudulent claims and pure stupidity of not knowing how to read.
G1ForFun said:
Good thing we have all these (to put it nicely) less than average intelligent human beings to keep hiking up costs for the rest of us with their fraudulent claims and pure stupidity of not knowing how to read.
Click to expand...
Click to collapse
No kidding. And some of them wonder why there are these releases of unrootable perfected spl's! lol, I think they gave up though (Nexus one, good idea on their part imo!), people probably still manage to brick it.
KAwAtA said:
No kidding. And some of them wonder why there are these releases of unrootable perfected spl's! lol, I think they gave up though (Nexus one, good idea on their part imo!), people probably still manage to brick it.
Click to expand...
Click to collapse
Wow... you have no idea the situation nor the circumstance that people brick their phone. It only takes a small mistake to do so. I just came from having a G1 which I modded and updated constantly just about every other day trying new things. I took apart the phone to replace the physical keyboard and ended up damaging a cable from the screen. I went to Tmobile store and purchased a Fender edition MyTouch which is special in a few ways. I had no problem rooting the phone with the Goldcard method, aside from finding a working 2gb sd... I decided to upgrade the 32a SPL and radio which bricked my phone. I see no reason why it would have bricked it but I wont be trying it again.
Everyone i repeat EVERYONE makes mistakes, all be it some make some pretty wild ones... but we are all Human and calling people idiots that do not know how to read and follow directions will not help anyone here.
These forums are designed to help and assist those who want to get the full potential out of their phones and customize to their own personal wants and needs. We should all be here to help those with questions (even dumb ones... sigh) for none of you would have the knowledge you have if you had not learned it. So please stop the bigotry and ignorance and be a little more helpful to those with issues. For those who have issues, dont go blaming the devs for messing up your phones, you know the risks so proceed cautiously and learn from your mistakes.
Fact is if you had followed directions exactly you wouldn't have bricked your phone. It's doubtful the tutorial was wrong.
heavensblade23 said:
Fact is if you had followed directions exactly you wouldn't have bricked your phone. It's doubtful the tutorial was wrong.
Click to expand...
Click to collapse
+1!
Gerr1985 said:
Wow... you have no idea the situation nor the circumstance that people brick their phone.
Click to expand...
Click to collapse
Um, yes I do. Way to come to that assumption.
Gerr1985 said:
Everyone i repeat EVERYONE makes mistakes, all be it some make some pretty wild ones... but we are all Human and calling people idiots that do not know how to read and follow directions will not help anyone here.
Click to expand...
Click to collapse
What? Another assumption already! I'm not calling anyone an idiot (in this thread LOL) haha, I simply agreed about the people bricking, not following wonderfully provided instructions and hiking up the costs. Sorry to be an ass, but if you stopped coming to those assumptions, perhaps your first phone wouldn't have been a nice brick!
KAwAtA said:
+1!
Um, yes I do. Way to come to that assumption.
What? Another assumption already! I'm not calling anyone an idiot (in this thread LOL) haha, I simply agreed about the people bricking, not following wonderfully provided instructions and hiking up the costs. Sorry to be an ass, but if you stopped coming to those assumptions, perhaps your first phone wouldn't have been a nice brick!
Click to expand...
Click to collapse
I never said the tutorial was wrong just that I made a mistake in picking the wrong one or messing up somewhere... obviously.
I'm not assuming anything... its fact you only have a general idea of how someone breaks their phone in that they made a mistake, but that you dont know how or the circumstances that caused it...
I wasnt assuming you were calling anyone an idiot and sorry I used your post to quote and not the others before generalizing "anyone" who breaks their phone as an idiot who cant follow directions. It could easily be that someone was not aware of specifics and hastily updated items that are not for their particular phone or missed a step.
In life it is far too easy to make mistakes, better to sympathize, say do better next time, and move on... simple as that.
I, for one, can't help but laugh when I make some mistakes. I was fully prepared to pay for another phone because I knew what "I" did broke it and no one was to blame but myself. Life goes on, pick yourself up and move forward. Sorry??? that I took a particular interest with a fellow mytouch user who mistakingly messed up and put the phone in the "break" status. I work as an IT Administrator for many large companies and mistakes can happen all of the time, I'm just glad they can happen to me and not a client
We all know the risks involved when we mess around with the phone. I also had no idea what a bricked phone did when bricked... until this morning
Gerr1985 said:
It could easily be that someone was not aware of specifics and hastily updated items that are not for their particular phone or missed a step.
Click to expand...
Click to collapse
Messing with your phone's baseband is not a time to be in a rush.
Hello everyone. I want to thank you all for this site, I have learned a great deal here and appreciate all your efforts. I have a question that many new comers have asked and they have been told to go read, so thats what I will do. I want you to know tho that its very hard when you have a baby, and very little time. I also want you to know that the only times I am really productive getting somewhere with my phone is staying up till like 4 am because everyone is asleep and I have the time needed to dedicate to all this reading, trying and learning.
I am not complaining, in fact I am grateful because I am getting somewhere thanks to your help, which has been more valuable than all the help Samsung and Rogers have given me washing their hands clean and leaving me with a defective phone. My problem has not been solved just yet, but I think a 2.2.1 rom will fix my problem. Ill keep reading and trying, ill get there.
I suggest you guys have a wikipage with a table with all the roms, what versions of android they are, what kernels, modems, etc they work with ( or not work with ), bugs, features, something all in 1 page for easy access. This would make it easier for people to access information. The easier it is the more people will use them and come here, the more ideas you will have, the more testers, its a win win situation!
I have been to the pages for all the roms, some of them tell you the bluetooh voice dialing is not working, most don't, id have to go looking for my answer. I have learned that for instance it seems people do not have an issue with it with froyo 2.2.1 but again, some roms tell you in the main page its 2.2.1, others don't.
I can't grasp all the information staying up at night till 4 am. Its the only time I have. I almost had a heat attack when I thought I bricked my phone, I can't afford another one. If all the important information is right there on 1 page, like links to the usb drivers, tools, roms, kernels, everything. Have the instructions to flash. Have a table with all the roms, their versions, what versions of kernels, modems, etc, they do ( or dont ) work with. maybe even some of the table cells are clickable, for instance bugs, click on it and a window pops up with a list of them.
I know all this information is in here somewhere. Thanks to everyone for it, but it needs to be on 1 page. Please make it easier for people who are new to this. You will benefit as well as them. Looking forward to being able to use voice dialing. I think it will be working by tomorrow or after tomorrow thanks to you guys. I could have done it in a day if all the information was right there .
Thanks for reading.
Try searching.
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SGH-I897
I have that bookmarked. It is also a sticky in this section.
But it doesn't say for instance which ones are 2.2.1, or which ones have the terrible voice dialing over bluetooth..
I do search and end up with over 15 tabs...
I am getting by, I am just saying it could be organized better for everyones benefit. It could be made so someone who has never done this before can get it done in a couple of hours if even, without keeping asking you the same questions here. I understand why people keep asking to recommend a ROM. It is not they they do not search, not all of them anyway. Things can be better organized.
I hear what you're saying, I think it's just that within the course of a month, about 20 ROM's have been released, if not more. And no one has had time to update the wiki.
vunuts said:
I hear what you're saying, I think it's just that within the course of a month, about 20 ROM's have been released, if not more. And no one has had time to update the wiki.
Click to expand...
Click to collapse
+1
The thing is that its not just the number of ROMs, but also the number of versions that are released. It would be a real pain and an added overhead for anyone maintaining it.
Also note that most devs are working too, and doing this in their free time. The little time they have to spare is taken up for making improvements. But they do release changelogs to look into.
If anyone has time, I would suggest they take it up to create a wiki and maintain it, rather than relying or asking the devs to do it.
Try capfaq.com it has a ROM table section, and I've used it alot.
Same issues with being 100% up to date, but it's the best Rom table format I've seen.
i897 running Cognition 3.02
Madtowndave said:
Try capfaq.com it has a ROM table section, and I've used it alot.
Same issues with being 100% up to date, but it's the best Rom table format I've seen.
i897 running Cognition 3.02
Click to expand...
Click to collapse
http://www.capfaq.com/w/ROM_Table
Looks like they have updated it!
Thanks guys, I will check that table out tomorrow.
It'd be nice if there was a modem chart as well. I know there are modems in the modem thread
forum.xda-developers.com/showthread.php?t=835272
...but near as I can tell it's not up to date, or at least the first page is not up to date (ie base Cognition runs on JL1 and Andromeda on JL2, but aren't on the first page).
If anyone knows a good and current modem reference guide, please let me know.
I can't complain too much because obviously things change all the time and it's a PITA to constantly update info...I'd volunteer but I got a 2 year old and baby 2.0 due in April.
Madtowndave said:
baby 2.0 due in April
Click to expand...
Click to collapse
made me lol at the versioning of baby
diablo009 said:
made me lol at the versioning of baby
Click to expand...
Click to collapse
Yeah it's like Richter Scale difference at least 0 to 1, and 1 to 2 kids...people that have more than 2 are either really bad at birth control, Catholic, or gluttons for punishment.
distortionist said:
I want you to know tho that its very hard when you have a baby, and very little time. I also want you to know that the only times I am really productive getting somewhere with my phone is staying up till like 4 am because everyone is asleep and I have the time needed to dedicate to all this reading, trying and learning.
Click to expand...
Click to collapse
And I thought I was the only one!
Thanks pal for making my day...
Sent from my SGH-I897 using XDA App
I bricked my phone
distortionist said:
I bricked my phone
Click to expand...
Click to collapse
How? What happened?
I have no Idea what I did wrong, my goal before I started was getting voice dial over bluetooth working for me, its essential to me. It started with trying to install paragon, as per http://www.capfaq.com/w/ROM_Table mentioned above.
I was stock rogers 2.2 so I wiped it clean, and tried the update thing, it didnt work. The only step I skipped was flash to stock and the master clear since it was 2.2 recently and I did the factory wipe. It did not work but I did not brick anything just yet. I figured most people tell you to flash with the one click odin which puts stock at&t on it. I did that and the phone stopped going into download and recovery, it did not stop completely i have gone into download and recovery a few times after that but it was a battle with my phone, since it was booting, I used adt instead which worked like a charm. at&t rom was not happy on my phone, it was going into at&t reboot loops where it would just reboot the bios over and over. after trying and trying it would boot android, i was trying to fix it but each time it restarted the reboot loop would kick off. I could not go to recovery or download mode till i finally got back into the OS and used adt to tell it to go to download mode where i reflashed my stock rogers.
My phone now had at&t logo on boot before rogers, which is not that bad but i had read you can get rid of it, i tried going into download mode with the buttons but didnt try too hard, adt was easier.
I was following these instructions :
http://www.mmacleod.ca/blog/2011/01/removing-the-att-boot-screen-from-a-samsung-captivate/
it wanted me to use odin to flash a file. I used my oden 1.3, i think he says oden 1.0, I didn't think it would make a difference.
Odin started to flash and said fail. I got the screen with "android ! computer", I have been there before when I first ever tried using odin and had to fight with my phone to get to download mode at the time ( this was before at&t ever came close to the phone, i never used odin before so i probably had trouble because of inexperience ).
anyway, this time no matter what I do I cannot go to download mode, I plan on making a jig today if i find someone who sells resistors in this little town.
any help would be appreciated. I dont want to put any more roms on my phone, i just want it to work. I am worried. Ill wait till samsung releases 2.2.1 I just want my phone back to the way it was when I bought it
As the person who write most of the documentation for Team Komin (the developers who make Andromeda), I would say this would be an immense pain. copying all of our information from the website, formatting it into wiki form and then posting it would be very time consuming.
nbs11 said:
As the person who write most of the documentation for Team Komin (the developers who make Andromeda), I would say this would be an immense pain. copying all of our information from the website, formatting it into wiki form and then posting it would be very time consuming.
Click to expand...
Click to collapse
True, but once done, it would be much easier to maintain and navigate. There is going to be a lot of crossposting and people asking for insight and advice.
I'm sure we all understand the search feature in the forum, but to be honest things change topic within a thread, and where someone asks a question that is somewhat unrelated and gets a very good answer, it is not always apparent by poking through page after page of posts to find that nugget of gold. I mean, searching for 'kernel' will give literally thousands of hits. A wiki would be much better in terms of 1. Where you are starting out from 2. what you need to do what you want 3. where to find these things, and 4. maintaining updates and version revisions.
I really appreciate all the work people do here, and I have had to find everything I wanted to know the 'hard' way, but as Android grows in popularity and market percentage, more and more people are going to come here looking for this information. Pobably better to do it sooner than later.
I just got the MT4GS after being a long time MT4G user and I'm wondering if it is worth it to root as there is currently no CM or stable Virtuous Rom which is what I used on the MT4G. Any helpful opinions are much appreciated.
micahman said:
I just got the MT4GS after being a long time MT4G user and I'm wondering if it is worth it to root as there is currently no CM or stable Virtuous Rom which is what I used on the MT4G. Any helpful opinions are much appreciated.
Click to expand...
Click to collapse
If Virtuous is what you like then I'd say yes, go for it and root. The Virtuous ROM might be in beta here in the MT4GS forums but it was smokin' fast and stable enough when I used it. I'm sure an official release is just around the corner anyway. good luck and welcome to the MT4GS family!!
siani_8 said:
If Virtuous is what you like then I'd say yes, go for it and root. The Virtuous ROM might be in beta here in the MT4GS forums but it was smokin' fast and stable enough when I used it. I'm sure an official release is just around the corner anyway. good luck and welcome to the MT4GS family!!
Click to expand...
Click to collapse
Thanks for the feedback and welcome, good enough reason for me. One thing I do like a lot on stock is the camera app, is that included in the beta or is there a flashable mod?
micahman said:
Thanks for the feedback and welcome, good enough reason for me. One thing I do like a lot on stock is the camera app, is that included in the beta or is there a flashable mod?
Click to expand...
Click to collapse
Yes sir, the Doubleshot camera app is included.
micahman said:
I just got the MT4GS after being a long time MT4G user and I'm wondering if it is worth it to root as there is currently no CM or stable Virtuous Rom which is what I used on the MT4G. Any helpful opinions are much appreciated.
Click to expand...
Click to collapse
Root it. Then you can:
Enhance your gps ability because of the generic gps file that's coded very poorly (in fact wrongly ... T-Mo doesn't maintain a good SUPL server, and if you're not on the T-Mo network your AGPS isn't working in stock configuration...well, maybe a little, but not anything worth mentioning. )
Flash a better security update to fix the big-brotheresque HTC spy mode (htcloggers.apk). HTC released an update to patch their security hole, but they are still monitoring everything you do with the device. Flash Undeadk9's security patch to just cut them off at the knees instead, or uninstall htcloggers.apk ( and other file I can't remember at the moment )
Change your hardware key files and re-map some buttons to be more useful.
Flash custom ROMs, as you're aware...
Play with the upcoming kernel files from myself and others...( give us time to make it stable )
...and so much more!
Generally do the things with the device that you've paid for that you should be able to do. Why spend all this money on something, and only use like 60% or less of what it can do?
If you're here and posting, then you should probably just go ahead and root it. It won't be long after you've been poking around in here reading through all the things we have been/are doing with the device before you'll go for it.
Check the sticky at the top of the general section to get a good handle on where to go first and what to read through. Take the time to read through the threads ( I know they are long ) - you'll see what all the problems were that people encountered, and how they were solved. Even if you don't run into the problems, at least you'll learn a whole lot and understand your device much, much more intimately.
...and if you get stuck, we're here to help. Many of us have been through this whole process countless times before, and are willing to lend a hand - just don't post random questions in the dev section and everything will be good.
Welcome to our little corner of the XDA universe - you'll love this device!
Blue6IX said:
Root it. Then you can:
Enhance your gps ability because of the generic gps file that's coded very poorly (in fact wrongly ... T-Mo doesn't maintain a good SUPL server, and if you're not on the T-Mo network your AGPS isn't working in stock configuration...well, maybe a little, but not anything worth mentioning. )
Flash a better security update to fix the big-brotheresque HTC spy mode (htcloggers.apk). HTC released an update to patch their security hole, but they are still monitoring everything you do with the device. Flash Undeadk9's security patch to just cut them off at the knees instead, or uninstall htcloggers.apk ( and other file I can't remember at the moment )
Change your hardware key files and re-map some buttons to be more useful.
Flash custom ROMs, as you're aware...
Play with the upcoming kernel files from myself and others...( give us time to make it stable )
...and so much more!
Generally do the things with the device that you've paid for that you should be able to do. Why spend all this money on something, and only use like 60% or less of what it can do?
If you're here and posting, then you should probably just go ahead and root it. It won't be long after you've been poking around in here reading through all the things we have been/are doing with the device before you'll go for it.
Check the sticky at the top of the general section to get a good handle on where to go first and what to read through. Take the time to read through the threads ( I know they are long ) - you'll see what all the problems were that people encountered, and how they were solved. Even if you don't run into the problems, at least you'll learn a whole lot and understand your device much, much more intimately.
...and if you get stuck, we're here to help. Many of us have been through this whole process countless times before, and are willing to lend a hand - just don't post random questions in the dev section and everything will be good.
Welcome to our little corner of the XDA universe - you'll love this device!
Click to expand...
Click to collapse
Wow, thank you for all the info, I am very grateful. I've noticed there are a few threads detailing how to root but can you tell me which one would be the best and most reliable? Thanks again for all the info, especially about that HTC spy stuff, I had no idea.
micahman said:
Wow, thank you for all the info, I am very grateful. I've noticed there are a few threads detailing how to root but can you tell me which one would be the best and most reliable? Thanks again for all the info, especially about that HTC spy stuff, I had no idea.
Click to expand...
Click to collapse
I used theunlockr.com to root it, worked like a charm and has a video walk throu.. which I'm a big fan of. Easier to follow. but the only difference is to flash modoco cwm not revolutionary.. so you can flash undeadK9's roms.. id suggest senseless.
Sent from my Senseless Doubleshot using xda premium
shady503403 said:
I used theunlockr.com to root it, worked like a charm and has a video walk throu.. which I'm a big fan of. Easier to follow. but the only difference is to flash modoco cwm not revolutionary.. so you can flash undeadK9's roms.. id suggest senseless.
Sent from my Senseless Doubleshot using xda premium
Click to expand...
Click to collapse
Thanks man! Got it rooted and running senseless! So far so good!
Not to contradict Shady's advice, especially since it seems like it worked for you, but i've previously and still do recommend against going to a third party web resource outside of XDA to root the device.
The reason being is that a lot of us did everything from the information available here, and we are familiar with the processes and common problems people run into following the guides posted here in the forums.
If you post questions about problems or an issue you run into, you run the risk of slow or no support because of the unfamiliarity the majority of us here have with outside methods and resources.
I know off the top of my head I could post a helpful response to someone having a problem with a method described here. For an outside resource...i'd probably have to go look it up, maybe download somehing, and probably try the method before being able to help.
Then i'd have to dig into the code of whatever offering was in question, to ensure it wasn't doing anything I didn't want it to do before installing anything.
Ultimately, this is a lot more time and trouble then just digging into my memory or looking up a specific thread to verify something, and also probably provide a link to the specific post that addresses the problem.
I'm hitting overtime consistently on my night job, and still picking up hours at my day job, and honestly would rather commit the level of time necessary to troubleshoot an outside resource on something more personally productive, like digging deeper into kernel source or something.
Just a thought to keep in mind as you (and others in the future) wander around here. I promise that everything you need to root your phone and install custom ROMs and such is right here in the MT4GS forums. (excepting the need to go to the revolutionary resource for S-OFF).
Cm7 just dropped like a bomb
sent from my real Gs move in silence like lasagna
mbernusg said:
Cm7 just dropped like a bomb
sent from my real Gs move in silence like lasagna
Click to expand...
Click to collapse
With a follow up by Official CWM Recovery. Today was a good day.
Coug76
Blue6IX said:
Not to contradict Shady's advice, especially since it seems like it worked for you, but i've previously and still do recommend against going to a third party web resource outside of XDA to root the device.
The reason being is that a lot of us did everything from the information available here, and we are familiar with the processes and common problems people run into following the guides posted here in the forums.
If you post questions about problems or an issue you run into, you run the risk of slow or no support because of the unfamiliarity the majority of us here have with outside methods and resources.
I know off the top of my head I could post a helpful response to someone having a problem with a method described here. For an outside resource...i'd probably have to go look it up, maybe download somehing, and probably try the method before being able to help.
Then i'd have to dig into the code of whatever offering was in question, to ensure it wasn't doing anything I didn't want it to do before installing anything.
Ultimately, this is a lot more time and trouble then just digging into my memory or looking up a specific thread to verify something, and also probably provide a link to the specific post that addresses the problem.
I'm hitting overtime consistently on my night job, and still picking up hours at my day job, and honestly would rather commit the level of time necessary to troubleshoot an outside resource on something more personally productive, like digging deeper into kernel source or something.
Just a thought to keep in mind as you (and others in the future) wander around here. I promise that everything you need to root your phone and install custom ROMs and such is right here in the MT4GS forums. (excepting the need to go to the revolutionary resource for S-OFF).
Click to expand...
Click to collapse
Very true. They use a lot of information found at xda to build their guides off of thou. And a video tutorial is always nice, for me anyways. but yeah.. don't expect support from theunlockr.com.
I always go their, sometimes their outdated or wrong. But still gave me a general idea and I was able to use multiple guides to give me the correct process..
Sent from my Senseless Doubleshot using xda premium
I'm glad I was able to find this thread, cause I've been wondering whether or not it would actually be worth it to root a MT4GS or not. And ya, I can agree that for the most part, rooting has more benefits than problems. And I always have gotten the same answer when asking that question about other devices, "Just root it; you'd have to be crazy not to; nothing compares to a rooted phone, etc...". So I gave in and rooted my MT3G 1.2 (w/ the headphone jack on top). After a while I noticed some definite problems: a few important features were gone, also it was impossible to update G. Maps (because of being rooted), and finally the worst scenario of all: not being possible to un-root the device. I must have tried 10 times, following the directions to the T and repeatedly getting the same failure error. I was finally able to find someone else with a similar problem who posted their solution. Tried, waited, failed. Fully bricked, I mean not even a flicker or a battery light would come on after that. Fortunately, I was able to lie to customer service and convince them to do a warranty exchange (Aeon-1, T-Mobile-0) so I got a replacement and haven't rooted since.
So I guess my point is, I'm actually scared to root my new MT4GS for the sake of potentially not being able to unroot it if need be. But, so far from what I've read it looks like it is reversable if I ever need to. I was likely considering using theunlockr.com's method due to clearly stated, and easily understood instructions. I wish I could say the same about the posts I've read @ XDA regarding rooting instructions.
-Which rooting methods are guaranteed to be un-rootable? That option is crucial, if I ever need to go back to stock or do a warranty exchange (for all those people who were gonna say "Why the hell would you ever consider unrooting?)
-So some people suggest ClockworkMod Recovery, others don't seem to care. I ask, is there any real difference between the two? And why?
-Also, which are the best/most stable roms you would suggest? Because I've done the trial and error thing before, comparing several different roms, and I never seemed to find anything worthwhile. (Also, I checked CyanogenMod's site and either I'm blind or they don't have a single rom for the MT4GS)
-I think you somewhat answer the question regarding features of the stock camera being available after rooting. But I need to know: After rooting, is the camera going to be the same as the stock one, including ALL available features (SweepShot, ClearShot HDR, Burst Shot, Macro, Night...)? And is that camera program featured within all rooted roms, or does it have to be installed seperately?
-And ditto that question in regards to G-Maps.
-And finally this may seem like a n00b question, but I've still never gotten a clear answer: How/When can a Nandroid Backup be performed? I know that it would be a safety precaution in case I ever f*cked up my device and needed to restore, but I've never been able to find clear, accurate, and relevant instructions on how to nandroid backup or even nandroid restore.
So I apologize for asking so many questions, especially since I imagine they seem redundant and novice. However, I have rooted phones before so I'm not a complete n00b; I'm just trying to be VERY thorough this time around, to avoid any potential for error. Thank you in advance for your time.
-Colton
@eon said:
I'm glad I was able to find this thread, cause I've been wondering whether or not it would actually be worth it to root a MT4GS or not. And ya, I can agree that for the most part, rooting has more benefits than problems. And I always have gotten the same answer when asking that question about other devices, "Just root it; you'd have to be crazy not to; nothing compares to a rooted phone, etc...". So I gave in and rooted my MT3G 1.2 (w/ the headphone jack on top). After a while I noticed some definite problems: a few important features were gone, also it was impossible to update G. Maps (because of being rooted), and finally the worst scenario of all: not being possible to un-root the device. I must have tried 10 times, following the directions to the T and repeatedly getting the same failure error. I was finally able to find someone else with a similar problem who posted their solution. Tried, waited, failed. Fully bricked, I mean not even a flicker or a battery light would come on after that. Fortunately, I was able to lie to customer service and convince them to do a warranty exchange (Aeon-1, T-Mobile-0) so I got a replacement and haven't rooted since.
Click to expand...
Click to collapse
Sorry to hear that didn't work out so well. I think you'll find that your MT4GS experience will be a lot better.
Check the link to my backup thread in my signature. Read through it, and feel free to ask any questions in that thread you may have. I or another will be happy to help you clear them up.
Link: Backups - After Rooting, before ROMing, take this step
@eon said:
So I guess my point is, I'm actually scared to root my new MT4GS for the sake of potentially not being able to unroot it if need be. But, so far from what I've read it looks like it is reversable if I ever need to. I was likely considering using theunlockr.com's method due to clearly stated, and easily understood instructions. I wish I could say the same about the posts I've read @ XDA regarding rooting instructions.
Click to expand...
Click to collapse
Yea, everything tends to happen first here, so trying to keep it all organized as things change and develop is difficult at times, much too convoluted at others.
Basically, you need to take your bootloader from S-ON to S-OFF. Do this with the Revolutionary exploit. It installs CWM 4.0.0.8 during the process.
Then you need to make a nandroid backup. (see my backup thread)
Then you should upgrade to the official Clockworkmod Recovery, replacing 4.0.0.8 that was installed with the S-OFF exploit. The version is 5.0.2.7
Dev section link for the official CWM:
http://forum.xda-developers.com/showthread.php?t=1329160
Once you do that, you should already have the superuser.apk you need for rooting that you found when you got the Revolutionary S-OFF tools. You can either have done it then, or now.
I'd wait until after getting the official CWM first, simply because that makes your first nandroid backup as fresh as it can be. It's up to you when you do it.
And that's basically it.
You now have a stock, rooted phone that you can start to play with. I'd say play with it for a little while on the stock ROM before switching to another, that way you'll get a feel for what you gain or lose, and if the various trade-offs are worth it.
Before doing any of that stuff, though, read through this thread:
Read this before posting. MT4G Slide Compendium
That will get you a little more familiar with the terminology, and provide helpful links to start exploring what you need to know.
Also read as much of this thread as you can stand:
S-OFF for Retail (S-ON) Devices, NOTE ADDED 8/17/11
This S-OFF for retail is the thread that officially announced the Revolutionary exploit for S-OFF here. The links in the OP will take you to where you need to go to get it.
If you get through that one, then this is a follow up:
PERMANENT-ROOT (NEW!) & Temp-Root (v2) for any MT4GS (Windows)
The temp-root thread is a bit confusing, because before we got S-OFF you could root the phone until you rebooted it. Once the Revolutionary S-OFF method was out, this thread also ran tandem with the official announcement thread. Because it was also dealing with temp root, it led to a lot of confusion.
There is some really good info in that thread, but I recommend reading the official release thread first. It'll make more sense that way, and you may not even have to check the temp-root thread.
(again, this lends to the evolving nature of what we're learning here - hard to keep it organized as it grows.)
Also, this thread: How To Turn S-Off, Install MoDaCo Clockworkmod Recovery, and Install a Rom For Dummie
Was written as a summary on how to get S-OFF and Root, because of how convoluted and looong the two previously mentioned threads got.
Once you hit this point, you're basically set.
My next move would be to install busybox, which you can find in the market, then immediately flash the Security patch to fix a glaring security flaw created by HTC.
At this point i'd make another nandroid backup.
@eon said:
-Which rooting methods are guaranteed to be un-rootable? That option is crucial, if I ever need to go back to stock or do a warranty exchange (for all those people who were gonna say "Why the hell would you ever consider unrooting?)
Click to expand...
Click to collapse
They are all un-rootable, but once you go from S-ON to S-OFF that's a one-way trip. Several people have reported exchanging their devices after returning to stock with an S-OFF bootloader without issue.
This is returning to T-Mobile, though, it's questionable if HTC will accept a return directly of a device with an S-OFF bootloader.
@eon said:
-So some people suggest ClockworkMod Recovery, others don't seem to care. I ask, is there any real difference between the two? And why?
Click to expand...
Click to collapse
As mentioned, upgrade to the official Clockworkmod recovery as soon as possible. From here on out it will be the only supported recovery.
@eon said:
-Also, which are the best/most stable roms you would suggest? Because I've done the trial and error thing before, comparing several different roms, and I never seemed to find anything worthwhile. (Also, I checked CyanogenMod's site and either I'm blind or they don't have a single rom for the MT4GS)
Click to expand...
Click to collapse
I'm working on releasing the updated version of Bulletproof right now, actually, and you'll like that one. Should be out in a day or so. The original developer is moving on and is handing it off to me.
I've just spent the last....dunno how long working at it, and needed to take 5 and clear my head. Cruised through the XDA MT4GS forums as i'm winding down for a break, and you caught me at a good time to give a response.
CM7 just got officially put on hold, but with your interest in the camera you probably wouldn't have gone for that right away. It's an alpha release, and we are very excited to have official CM support for the device, but since Ice Cream Sandwich ( Android 4.0 ) source code was just released, the CM team is focusing on that and it's likely to be a while before the CM7 for our phone sees an update.
Honestly, i'm more excited that they are focusing so exculsively on Ice Cream Sandwich, because that means a lot more for all the phones and devices beyond just our own version of CM7.
I'll leave other ROM recommendations to others who will surely come through here and tell you more about them.
@eon said:
-I think you somewhat answer the question regarding features of the stock camera being available after rooting. But I need to know: After rooting, is the camera going to be the same as the stock one, including ALL available features (SweepShot, ClearShot HDR, Burst Shot, Macro, Night...)? And is that camera program featured within all rooted roms, or does it have to be installed seperately?
-And ditto that question in regards to G-Maps.
Click to expand...
Click to collapse
Pretty much all of the ROMs will support both the Camera app (in its entirety, included in the ROM) and Google maps.
The alpha port of CM7 is the only one (pretty sure) that doesn't support the camera, because the camera is tied into the sense frameworks. CM7 has no Sense components to it, and it was stated very clearly in the thread that it never will. The CM team and their ROM is worth losing the camera app over to a lot of people, and they are the lone exception to the "no camera app" stigma.
Keeping the camera app is one of the things that has been driving development around here, and very few people were willing to use or invest time in making a ROM that would exclude it.
I should take this time to point out that the stock gps configurations are, well, flat out wrong. Misconfigured, and it doesn't work well.
Myself and another developer independently spent a lot of time working on fixing this issue, and when we realized what each other were doing we also realized that we had the piece of the puzzle the other needed to make it work.
We released a collaboration that solved the problem, which you can find here: GPS lock too long or not at all? Try this
If you want to know how my half of the puzzle works, that thread will explain it in almost excrutiating detail. I recommend my patch over the other developers, as he is no longer with us and I will only be continuing support in my thread.
@eon said:
-And finally this may seem like a n00b question, but I've still never gotten a clear answer: How/When can a Nandroid Backup be performed? I know that it would be a safety precaution in case I ever f*cked up my device and needed to restore, but I've never been able to find clear, accurate, and relevant instructions on how to nandroid backup or even nandroid restore.
Click to expand...
Click to collapse
Just cruise through my backup thread. Post 1 is an adb method, post 2 is the nandroid method. If you have any questions, post them in that thread and help us try to maintain some kind of order (hah!)
@eon said:
So I apologize for asking so many questions, especially since I imagine they seem redundant and novice. However, I have rooted phones before so I'm not a complete n00b; I'm just trying to be VERY thorough this time around, to avoid any potential for error. Thank you in advance for your time.
-Colton
Click to expand...
Click to collapse
Honestly, don't ever worry about asking too many or too long of a question, as long as you don't post the question itself as a new thread in the development section of the MT4GS forums.
I'm sorry to hear it took such a bad experience for you to become as cautious as you are, but now that you're long past it you are much better off.
I'd much rather see someone ask questions, read some stuff, ask more questions, and then act on knowledge then just go and do and then say "I broke it, what do I do".
I'm happy to help either way, but if the information is there already then reading it before you start is much better then retroactively. Save the "how do I fix it" for uncharted territory learning things that aren't already common knowledge.
Again, part of the problem is that information is so convoluted because we keep adding to it as we learn new things. You can't really structure it before you know what it's going to be.
Myself and a few others have been trying to put effort into organizing things, but it's really a monumental task and i'd like to develop new things more so then catalogue what we already know. It's a crappy balance, but I try to put equal time to developing and organizing/answering questions.
I hope this helped you out some, I know I didn't completely cover it all but it should give you some things to chew on and help you sift through the data by spending more time on the relevant parts. Even then it's still a lot that you should know.
Don't be afraid to ask questions, one of the reasons I go into such depth is because people can correct me precisely where i'm wrong if I am about something.
You learn more when you're willing to admit you don't know something, then to pretend you do for whatever reason. Asking the right questions depends on being honest about what you do and don't know with yourself, so fire away.
I've got to get outside for a few minutes, then get back into coding, but someone else will come along and add to this soon enough.
Take care!
Well I definitely very much appreciate your prompt, and very detailed response to my many questions. I've been reading over what you've written plus the links over the past day. The main issue I have is digging through each thread looking for relevant information, while trying not to get sucked into each and every tangent post/link/info. I lost track of how many hours I've wasted reading irrelevant info which I initially thought actually had something to do with what I was after. And now a day later, I have my desk covered in reference notes (which are no longer comprehensible) and I'm more confused than I was before.
There are plenty of issues I have with forums in general. First of which being, organization seldom exists. Its like going into a library with a single question about 'how to change a tire', and leaving with 15 random, heavy books on quantum theory and black-matter, because apparently someone implied they were somehow related (I'm referring to other people, not you). Discouraging to say the least. I thought this would be more black-and-white; more simple. When 'Android' was new, rooting was simple (less ways to re-invent the wheel).
I'm walking away from this for now. The headache isnt worth it (I literally feel like I got skull-f*cked by god himself). But thank you for your help and feedback.
micahman said:
I just got the MT4GS after being a long time MT4G user and I'm wondering if it is worth it to root as there is currently no CM or stable Virtuous Rom which is what I used on the MT4G. Any helpful opinions are much appreciated.
Click to expand...
Click to collapse
Yes it is DEFINITELY worth it... Root away my friend and welcome to the MT4GS family. This phones kicks ass and we are expanding every day like wildfire
Sent from my myTouch_4G_Slide using xda premium
@eon said:
...
I'm walking away from this for now. The headache isnt worth it (I literally feel like I got skull-f*cked by god himself). But thank you for your help and feedback.
Click to expand...
Click to collapse
Hah, yea, XDA is like that all over - just the nature of the beast.
This is not the quick-answer type of home, yet from a developers point of view there is no better place on the internet for android/phone development information and help.
It really does all start here, and the journey of discovery is much more prized and worthwhile then the actual end result. In that respect the way XDA is, is the way it should be.
Sometimes the best way to come to grips with something is to forget about it for a little while. Let your mind work it over running in the background, and when you bring it back into focus you'll have a better hold on what you need, and what you still have to learn.
Again, feel free to ask any questions you may have and we'll do the best we can to get you set in the right direction.
Ya, it was like mass overload the other day; it was like trying to make a PBJ sandwhich, then realizing I have to bake my own bread from scratch, grind up peanuts into butter, and somehow pick my own berries for jam, etc...
Anyways, I read over some of those topics again and some of it makes a little more sense. But still, some of those threads are so damn long, Im not gonna read each and every post from top to bottom of the thread, at least not yet. But the main issue I've realized is definitely going to be a problem is the fact that turning S-Off is irreversible. There is absolutely no method of turning S-On after its been turned off, which doesnt seem to make any sense; I figure, if you are able to flip a light-switch on, its only obvious you should be able to flip the switch off. So why is the 'S-Off' method a one-way path? And is this problem going to be fixed?
I read a bunch of articles and tutorials on 'unrooting' the MT4GS, and each one says that it will change the phone back to the stock factory condition it was in before rooting. Of course, once I scroll down and keep reading comments, everyone says that there isnt a way to turn "S-ON". SO, how the hell would someone be able to root their phone while still ever having the option to do a warranty exchange? Unrooting is great cause it gets you most the way there. But I've been reading that when T-Mobile recieves the phone, they send it to HTC for inspection/repair, and thats where they look at all the software/firmware/h-boot/recovery/S-ON Versions to make sure they are at factory specs. So once again, even though it is possible to "unroot" the MT4GS if need be, it still impossible to fully go back to factory standard (which is exactly what I was worried about).
Thats ****ty cause I was actually willing and ready to start rooting via theunlockr.com's method (cause its a hell of a lot easier than any tutorial in these forums, it does it the same way, its just easier to understand). BUT, that S-ON/S-OFF snafu is enough for me to reconsider. As I'm sure there are tons of benefits to rooting and therefore I may not ever want to unroot, I still may need to for the sake of the warranty exchange. And believe me when I say that I NEED to have the ability to exchange; I've had to exchange the MT4GS 5 times within 3 consecutive weeks because each one I recieved in the mail had some physical manufacturer defects. And since the most recent replacement is a refurb, I need to leave that Warranty-Door open in case I need to exchange.... again.
By the way, I forgot why S-Off was required in the first place. Is it possible to remain rooted without S-Off???
@eon said:
Ya, it was like mass overload the other day; it was like trying to make a PBJ sandwhich, then realizing I have to bake my own bread from scratch, grind up peanuts into butter, and somehow pick my own berries for jam, etc...
Anyways, I read over some of those topics again and some of it makes a little more sense. But still, some of those threads are so damn long, Im not gonna read each and every post from top to bottom of the thread, at least not yet. But the main issue I've realized is definitely going to be a problem is the fact that turning S-Off is irreversible. There is absolutely no method of turning S-On after its been turned off, which doesnt seem to make any sense; I figure, if you are able to flip a light-switch on, its only obvious you should be able to flip the switch off. So why is the 'S-Off' method a one-way path? And is this problem going to be fixed?
I read a bunch of articles and tutorials on 'unrooting' the MT4GS, and each one says that it will change the phone back to the stock factory condition it was in before rooting. Of course, once I scroll down and keep reading comments, everyone says that there isnt a way to turn "S-ON". SO, how the hell would someone be able to root their phone while still ever having the option to do a warranty exchange? Unrooting is great cause it gets you most the way there. But I've been reading that when T-Mobile recieves the phone, they send it to HTC for inspection/repair, and thats where they look at all the software/firmware/h-boot/recovery/S-ON Versions to make sure they are at factory specs. So once again, even though it is possible to "unroot" the MT4GS if need be, it still impossible to fully go back to factory standard (which is exactly what I was worried about).
Thats ****ty cause I was actually willing and ready to start rooting via theunlockr.com's method (cause its a hell of a lot easier than any tutorial in these forums, it does it the same way, its just easier to understand). BUT, that S-ON/S-OFF snafu is enough for me to reconsider. As I'm sure there are tons of benefits to rooting and therefore I may not ever want to unroot, I still may need to for the sake of the warranty exchange. And believe me when I say that I NEED to have the ability to exchange; I've had to exchange the MT4GS 5 times within 3 consecutive weeks because each one I recieved in the mail had some physical manufacturer defects. And since the most recent replacement is a refurb, I need to leave that Warranty-Door open in case I need to exchange.... again.
By the way, I forgot why S-Off was required in the first place. Is it possible to remain rooted without S-Off???
Click to expand...
Click to collapse
not permanently. you'd have to temp-root every time you reboot.
Revolutionary is about the easiest way to root a phone in existence so I'm not sure why you're so scared... assuming you have adb working, it's literally as easy as plugging your phone in and opening a single file in the Revolutionary zip archive. everything is done for you. as long as you don't download their faulty recovery (it will ask you if you want to... just say no), it's literally the easiest rooting method available that I've ever seen.
don't make it too complicated. I certainly believe in having all of your bases covered, especially when it comes to potentially screwing up a $500 bundle of plastic, metal and silicone, but rooting is not a big deal anymore.
many people will tell you that they have received warranty replacements after sending in S-OFF/rooted phones. my best guess would be that HTC/Tmo randomly pick phones to "thoroughly check" and the majority don't receive this type of treatment.. and even if they find a rooted device, there's no telling whether or not they will deny your replacement.
I received a warranty replacement (faulty hardware buttons, the leds never turned off) for my gal's rooted MT4GS simply by installing the stock rom and recovery, but still with Revolutionary's hboot installed. No issues whatsoever. I'm not saying it's "right" and I'm not guaranteeing you the same result, just offering my first-hand experience.
here's how you can obtain perma-root and s-off in ~10 minutes. no complicated guides:
www.revolutionary.io
download installer, enter serial # to get your code.
open archive and find the installer... let it run.
when it's done, you'll be rooted and s-off with a custom hboot. say "no" to the download recovery option and manually flash the official CWM recovery, or modaco's 4.0.0.9 recovery image. (either should be fine, although roms are going to start coming out that may have issues with the 4.0.0.9 modaco recovery so cwm is probably your best bet)
if not being able to flip the S-OFF switch back to S-ON at this point is something you can't get over, this isn't for you. personally, I spent $500 on this phone and I'm going to do whatever the hell I want to it, and if TMO and HTC have a problem with that, I will happily take my business elsewhere.
Its not rooting that I'm worried about, its the possibility of having to do (yet another) warranty exchange and being caught sending back a warranty-void device. And since I just found out that my premium phone insurance extends my warranty for an indefinite amount of time, I imagine that i will undoubtedly be exchanging this phone sometime in the future. I can only hope that by then either the S-Off thing has been fixed or T-Mobile announces they no longer care. I can see both happening, honestly.
Rooting is going to be the easy part, if/when I decide to do it. The last things I havent yet figured out are:
-Which Rom(s) I'm going to try. When I compare most roms side by side, they all seem vaguely identical. I remember Cyanogen having the option of fully customized visual aspects/themes, as well as tons of settings/features that werent offered through other roms. But the problem with CM is that, as you said before, the several camera options/modes in the stock rom are not being used by CM. I'm looking for a rom that is, above all, stable; lightweight/fast; includes all camera features of stock rom; and if apps like gmaps wont be included, I'd like to be able to find something that is comparable, or even better if possible. If not, I really hope the market allows gmaps to be installed on a rooted device (a while back on my rooted phone, the install of gmaps would always fail) Also, you had mentioned that you were nearing completion of a Rom of your own, so I might read up on that as well.
-I read up on that article on micro sd cards regarding speed comparisons, so I ended up running the benchmark app on my pc and found that my SanDisk 8bg Class 4 was (apparently) faster than my currently used Samsung 16gb Class 2, which sucks cause I like having more space than I use. But anyways it got me thinking, I realize that speed is important for file-transfers and also running apps that have been moved to the sd, but I could have sworn I remember someone talking about how they had rooted and then installed their OS/Rom onto their SD card instead of the phone itself. I dont know if I read that wrong or not. And if that was accurate, then I want to know if there is truly any benefit from doing that or not.
-Also, in regards to sd cards, I remember last year when I had a rooted MT3G with Amon Ra's recovery, there was an option to throw in partitions. Almost everyone I talked with on here told me to add a partition. Then after a few updates to the recovery, I noticed new options in the partition section: Ext.2, Ext.3, and Ext.4 as well as the options to select the partition size and "swap" size. I never did understand what exactly the difference (if any) between "Ext.2, Ext. 4.... etc" was.
And as far as the "swap" size, I remember there being a LOT of debate over what exactly this number should be. Some people started suggesting outrageously high numbers, while others explicitly explained to not do that, because apparently the lower the number the faster it becomes. Ok, so if thats the basic concept, great. But I still never did find any reliable information regarding "swap" size.
So ya, those are the final questions/issues that have been bugging me. Any advice/help is greatly appreciated.
Hi everyone,
I would like to clear out some points before posting my issue.
1-I have been reading hard brick threads on this device in this forum for 3 days, I am posting my question because I want to get clear answers on what my options are at this point. I have not seen not even 1 solution via Jig, which seems to be the easiest method.
2- The reason I bricked my phone is [most likely] I flashed a kernel that was intended for the N7000 model, although this might not make sense to some of you , for the sake of getting proper help, please hold back on comments that point out how much of a non skilled fan I am and how could I have got caught on such an obvious mistake. Comments like the ones I am describing just wont help so please you might as well keep them to yourselves.
3- Please do not take me as a pedantic person, I just happened to have read enough answers to know that there are highly skilled people who want to help others while some others just love to spend their free time spamming threads. I certainly do not have enough knowledge and skills to perform the jtag method since I cant even solder.
I was trying the JellyBeer rom and I flashed their kernel on TeamWin Recovery, what I do not understand is why did it brick, because I actually realized my mistake soon enough and I performed a restore to my previous rom/kernel, to my understanding, this brick should not have happened in the first place. But when I went ahead and rebooted the phone, it just turned off in the middle of rebooting never to turn on again. Its dead, it wouldnt even charge nor go into download mode or recovery, no vibration no nothing...
Returning the phone to the store is not an option for me as I brought this phone from the states to my country (Dominican Republic ) and is out of warranty.
To me it almost means that I dont have no choice but to keep using my sisters pink motorola that btw is like 10 yrs old until I can wait till some day to have that kind of money again and get a new one. I am leaving the final answer to the experts in this forum.
..If you actually read the whole thing I must thank you, because I know its waaay to long. Counting on you guys.
nicoalmontec said:
Hi everyone,
I would like to clear out some points before posting my issue.
1-I have been reading hard brick threads on this device in this forum for 3 days, I am posting my question because I want to get clear answers on what my options are at this point. I have not seen not even 1 solution via Jig, which seems to be the easiest method.
2- The reason I bricked my phone is [most likely] I flashed a kernel that was intended for the N7000 model, although this might not make sense to some of you , for the sake of getting proper help, please hold back on comments that point out how much of a non skilled fan I am and how could I have got caught on such an obvious mistake. Comments like the ones I am describing just wont help so please you might as well keep them to yourselves.
3- Please do not take me as a pedantic person, I just happened to have read enough answers to know that there are highly skilled people who want to help others while some others just love to spend their free time spamming threads. I certainly do not have enough knowledge and skills to perform the jtag method since I cant even solder.
I was trying the JellyBeer rom and I flashed their kernel on TeamWin Recovery, what I do not understand is why did it brick, because I actually realized my mistake soon enough and I performed a restore to my previous rom/kernel, to my understanding, this brick should not have happened in the first place. But when I went ahead and rebooted the phone, it just turned off in the middle of rebooting never to turn on again. Its dead, it wouldnt even charge nor go into download mode or recovery, no vibration no nothing...
Returning the phone to the store is not an option for me as I brought this phone from the states to my country (Dominican Republic ) and is out of warranty.
To me it almost means that I dont have no choice but to keep using my sisters pink motorola that btw is like 10 yrs old until I can wait till some day to have that kind of money again and get a new one. I am leaving the final answer to the experts in this forum.
..If you actually read the whole thing I must thank you, because I know its waaay to long. Counting on you guys.
Click to expand...
Click to collapse
Hello, a week ago I was trying to restore my phone back to the stock rom, it is a Samsung Galaxy i727, and now is dead or HardBrick, I´m from Dominican Republic, searching in the internet I found a local Mobile Repair Center offering the Jtag service in just 24 hour my phone is back, their name is ALUMUN, if you are in Dominican Republic they are the best, you can find them in google as ALUMUN
I agree with you, we need help not lip service. I too bricked my phone, the site I got my roms added the galaxy 2 rom to the site not thinking it would be a bad thing to add it since they added it to the group of roms I could download for my phone, well that was the wrong thing to do!! I don't live in the Dominican Republic so I need to fix this myself.....HELP PLEASE!! Thanks guys
trayluv73 said:
I agree with you, we need help not lip service. I too bricked my phone, the site I got my roms added the galaxy 2 rom to the site not thinking it would be a bad thing to add it since they added it to the group of roms I could download for my phone, well that was the wrong thing to do!! I don't live in the Dominican Republic so I need to fix this myself.....HELP PLEASE!! Thanks guys
Click to expand...
Click to collapse
Hopefully this will help http://forum.xda-developers.com/showthread.php?t=2083353