Related
well just something I came to think about while writing an other thread.
we buy our expensive HTC phones and the first thing I do is hardspl then on goes my first custom ROM. Now I have an expensive phone with no warranty thats good new for HTC because now they don't have to give me a new phone or repair it for free.. if something should go wrong with it. (I have had 10 HTC devices and none have had any problem)
this is just thoughts but funny when I think of it
U are right. That's funny true. I think by the same way just like you
yeah its nice to think of it that way
but you must admit that very few of the HTC phones give HARDWARE problems (i never had any bad experience)
I returned 3 or 4 flashed phones and never had a problem. Rogers clerks...
Yeah,
Thanks to XDA HTC and WM are now and after reflashing a cooked ROM the best option!
I have flashed more than 50 times and will continue doing it
Thanks XDA!!
Yeh, Flashing is way cool But I lost count how many times
In the Tom Codon's forum "HTCpedia" is a girl making some publish job interviews... and some thinks like that... hope she asks to any that guys that works in HTC or MS, if this kind of forums gives them some support... or troubles to them... as far as we play more with this things as advanced users than a smartphone with Symbian or OSX phones users... cause i have saw many people that has HTC windows mobile phones without a single hack runing stock roms... wn5 or 6... sad but true, but the most loyal CELLPHONE user i guess.
htc loves us for flashing but google doesnt like us for flashing since they include closed source apps
example "HERE"
AndroidFiend said:
htc loves us for flashing but google doesnt like us for flashing since they include closed source apps
example "HERE"
Click to expand...
Click to collapse
But I heard we can flash other Android ROM to other Android device right? Cause I've seen ppl who flashed Hero ROM to Magic device.
techinically we can always flash the stock radio/rom/spl back and so claim back on the warranty if things do go wrong so its not that much of a risk.
without xda, i will be lost.. however sometimes i hope that we have a more systematic way of finding the different roms... i get lost sometimes in the many many wonderful roms out there
flashing stock can be problem if you're usb breaks..
riotburn said:
flashing stock can be problem if you're usb breaks..
Click to expand...
Click to collapse
Most devices can be flashed via microSD card by renaming the .nbh ROM file to the 4 letter device name (KAIS for the Kaiser, RHOD for the Rhodium, etc.) then adding IMG to the name. So RUU_Signed.nbh would be KAISIMG.nbh for a Kaiser and RHODIMG.nbh for a Rhodium. Even SPL versions can be updated with a microSD card.
As for the original topic of the thread, I would have to disagree. HTC probably does not like us flashing. It breathes a lot of new life into older devices, thus extending their lifespan and discouraging people from buying newer and more expensive HTC phones. Also, as has been mentioned before, most people revert to stock ROM and SPL before repairing, thus causing HTC to perform repairs at their expense, even though the original owner was at fault, and not HTC. I would say that flashing keeps a loyal customer base, which they want, but it comes with a price of unnecessary repairs.
DaveTheTytnIIGuy said:
Most devices can be flashed via microSD card by renaming the .nbh ROM file to the 4 letter device name (KAIS for the Kaiser, RHOD for the Rhodium, etc.) then adding IMG to the name. So RUU_Signed.nbh would be KAISIMG.nbh for a Kaiser and RHODIMG.nbh for a Rhodium. Even SPL versions can be updated with a microSD card.
As for the original topic of the thread, I would have to disagree. HTC probably does not like us flashing. It breathes a lot of new life into older devices, thus extending their lifespan and discouraging people from buying newer and more expensive HTC phones. Also, as has been mentioned before, most people revert to stock ROM and SPL before repairing, thus causing HTC to perform repairs at their expense, even though the original owner was at fault, and not HTC. I would say that flashing keeps a loyal customer base, which they want, but it comes with a price of unnecessary repairs.
Click to expand...
Click to collapse
they seem to think it's worth it though, because when the g1 had the hero ports HTC never stopped them, and got many good reviews and tests for it, and optimized the UI and stuff thanks to XDA, but it's definitely a trade-off.
prince.siraj said:
they seem to think it's worth it though, because when the g1 had the hero ports HTC never stopped them, and got many good reviews and tests for it, and optimized the UI and stuff thanks to XDA, but it's definitely a trade-off.
Click to expand...
Click to collapse
Well of course HTC wouldn't stop them, since XDA is one of their biggest selling points. Angering their entire enthusiast community would be a PR nightmare, and an incredibly stupid move from a business standpoint. That's why I can't understand why Google is sending Cease and Desist leters concerning their Android applications.
DaveTheTytnIIGuy said:
Most devices can be flashed via microSD card by renaming the .nbh ROM file to the 4 letter device name (KAIS for the Kaiser, RHOD for the Rhodium, etc.) then adding IMG to the name. So RUU_Signed.nbh would be KAISIMG.nbh for a Kaiser and RHODIMG.nbh for a Rhodium. Even SPL versions can be updated with a microSD card.
As for the original topic of the thread, I would have to disagree. HTC probably does not like us flashing. It breathes a lot of new life into older devices, thus extending their lifespan and discouraging people from buying newer and more expensive HTC phones. Also, as has been mentioned before, most people revert to stock ROM and SPL before repairing, thus causing HTC to perform repairs at their expense, even though the original owner was at fault, and not HTC. I would say that flashing keeps a loyal customer base, which they want, but it comes with a price of unnecessary repairs.
Click to expand...
Click to collapse
And how does flashing custom ROM's increase the number of times that HTC phones have to be repaired??
TravisBean said:
And how does flashing custom ROM's increase the number of times that HTC phones have to be repaired??
Click to expand...
Click to collapse
I'm not saying that it necessarily makes more phones that need to be repaired, but rather, HTC is repairing a lot of devices that they shouldn't be repairing because they actually have voided warranties due to flashing (I probably should have made that more clear in my other post).
And if you don't frequent the Kaiser sections, you might not know about the Radio from Hell incident. What happened was a signed, yet somewhat broken radio was uploaded onto the forum, and once flashed, this radio could not be changed or removed through normal or conventional means. And many people did not get good reception from this radio. Since they couldn't change it, yet they needed their phones, many people intentionally bricked their Kaisers in order to get working models with no Radio from Hell.
And in a completely unrelated incident, the many people who used MTTY on their Kaisers and typed "Task 2a", expecting to fix bad blocks on the NAND, were unpleasantly surprised when their SPL and all internal memory were completely erased. All contents of their device, such as User Data, the ULDR partition, the OS partition, and the SPL were all completely erased, thus rendering their devices completely useless, many of which were sent to HTC while their owners played dumb about why their phones stopped working.
So what I'm trying to say is: while flashing in itself doesn't necessarily cause more repairs, user actions may very well, and in the end HTC may end up paying for your mistake when they think it's their fault your phone doesn't work.
DaveTheTytnIIGuy said:
I'm not saying that it necessarily makes more phones that need to be repaired, but rather, HTC is repairing a lot of devices that they shouldn't be repairing because they actually have voided warranties due to flashing (I probably should have made that more clear in my other post).
And if you don't frequent the Kaiser sections, you might not know about the Radio from Hell incident. What happened was a signed, yet somewhat broken radio was uploaded onto the forum, and once flashed, this radio could not be changed or removed through normal or conventional means.
And in a completely unrelated incident, the many people who used MTTY on their Kaisers and typed "Task 2a", expecting to fix bad blocks on the NAND, were unpleasantly surprised when their SPL and all internal memory were completely erased.
Click to expand...
Click to collapse
And a factory reset of the device did not fix the problems? ( just asking)
That warranty-void analysis is invalid.
Legally, if you make a modification and something completely unrelated fails, then the warranty is still valid on the failed component. The reason for this is simple; things like auto makers would be denying warranty claims on transmissions for ladies fingernail scratches around the door handle.
lbcoder said:
The reason for this is simple; things like auto makers would be denying warranty claims on transmissions for ladies fingernail scratches around the door handle.
Click to expand...
Click to collapse
Ah Ha!! So that's why my tranny is slip'n between 2nd and 3rd!
Hi,
This is a stab in the dark, but my attempt to contribute to the good work been done by many others in rooting and flashing the tattoo, but I'm going to need some pointers.
I foolishly told the wife to buy a HTC Tattoo that was locked to Orange UK thinking, hey it'll be a piece of p!ss to unlock. That definitely isn't the case. Now I've rooted the device using the various things on the forum, the contributors are vast, so not enough space to mention them all here.
I plan tonight to flash using the AzusaRom, but as it's been pointed out on a number of occassions this doesn't unlock the phone from the CID check. I've also tried one of those turbosims without joy, so I thought I'd start taking a very tenative look around the tattoo to see if I'm able to understand what's going on a bit more.
I was hoping for a little guidance that's all. I'm assuming at some level there's a process spawned which at boot says check this SIM card? One approach I guess will be to understand what that process is and disable it? Although from what I gather the issue is to do with the version of the radio rom and the thing we really need to do is hack and flash the radio rom?
I'm probably putting myself out there for some ridicule, but this problem seems to be a recurring theme and perhaps a consolidated thread might be useful for everyone in the same boat.
So anyone wishing to join the party please do.
http://www.dealextreme.com/details.dx/sku.12167
Works perfectly in my Orange Tattoo and I running my O2 SIM no problems whatsoever. We would all love a hacked radio rom but me thinks it not that simple.
I would have thought that on a rooted phone if we flashed the HTC rom 1.67.405.6 then this would write the generic radio rom to the phone but I guess it doesn't, there must be some other protection somewhere.
Heyo N1 community!
So, after much deliberation, I dropped some cash on newegg for the first nexus experience...I also just needed a good backup phone.
That said, I'm probably going to be spending a lot more time here than in the Atrix forums as I'm REALLY liking the N1...and MIUI (...I'm kind of in love).
All this said, I had a couple questions about things I should be wary of...and just am not familiar with.
1. Blackrose
-From what I understand, due to the small ROM capacity, this is used to repartition the N1 to accommodate larger ROMs. I also see something about a custom HBOOT being involved. I don't really know what that is, though. Do most ROMs need this now? I was lucky enough to flash MIUI which apparently doesn't require blackrose. Granted, I don't know any of the implications of Blackrose. Is it reversible? Does it limit you in any way if you're on it?
2. Kernels
-Back on the Captivate, I feel like it was the roaring '50s with kernels. You could flash whichever kernel you wanted on whatever ROM you wanted...it was all about preference. With the Atrix, it's the opposite...doesn't help that there's basically only 1 stable kernel either. That said, I flashed the latest (non-ICS) MIUI and it looks like it comes with a slightly dated CM7 kernel- is this a big deal? Should I look to update it to something more recent/stable/etc? Or are kernels pretty specific as to ROM compatibility?
3. Radios
-Pretty much same situation with the kernels. I want to be careful because I know the N1 shipped for a couple different carriers, T-Mo and AT&T at the forefront. Now, I'm on AT&T, but the box my N1 came in is marked for Vodafone UK. As I understand it, Vodafone's freq's are the same as T-Mo's, right? Is there any difference between my "vodafone" N1 and one designed to work with T-Mo, AT&T, or any others?
4. Hardware issues/life expectancy/replacement options
-First and foremost, I'm still confused as to whether Nexus 1's are even still being manufactured. I heard somewhere that some UK carriers still sell them (obviously Google stopped doing it direct awhile ago). To me, it's the kinda thing where, in all honesty, I'd love to use the N1 as my EDC forever- the screen size is perfect for me, the Dev community is MASSIVE and very experienced, and the phone is simply iconic. That said, though, I'm wondering how long it'll be until things start to bite it and I have to look for a replacement...and if I'll even be able to find one. Alternatively, I've seen a lot of people say that HTC has been pretty forgiving about replacing busted power buttons and the like. Besides the power button, though, is there anything else I should be keeping an eye on?
Lastly, I want to thank all the Devs who've contributed. Poking around through the dev section gave me an overwhelming sense sense of options, and the conversation here seems a bit more mature than over in the Atrix forums ("WHEN WILL WE HAVE CM7/CM9?!" was almost every other thread...and the poor devs got TORN UP trying to contribute what they could).
Sorry if I blinded anybody with all the writing, but I appreciate any advice or input you can give me.
1. You don't need Blackrose for MIUI. Use A2SD and partition your SD card. How? Search. Help - Wiki link is in my signature.
2. You don't need to switch from default MIUI kernel, unless you want to overclock.
3. Doesn't matter, as long as you're on one of the Gingerbread radios. Any of the latest will be good enough. No difference in baseband builds between different N1 models.
4. You're going to eat a lot of pain with screen touch craziness, which is the most painful part of this phone. The second most painful part is sub-par GPU, but unless you game a lot, you won't notice it - MIUI is smooth. So I'm really in doubt you'll want to keep this phone for a long time. In any case, press the power button gently and closer to the inside of the phone, and avoid pressing it as much as you can (use ROMs with trackball wake and screen lock widget).
Jack_R1 said:
1. You don't need Blackrose for MIUI. Use A2SD and partition your SD card. How? Search. Help - Wiki link is in my signature.
Click to expand...
Click to collapse
Thanks for the tip. It occurs to me that I jumped the gun and flashed a ROM before I should have- not that anything bad has happened. Just thinking I'll probably go round two here shortly once I learn all the ins and outs (like Apps2SD...and popping in an SD that bigger than the included 4GB one to make it worthwhile). Thanks for the tips bro.
Jack_R1 said:
2. You don't need to switch from default MIUI kernel, unless you want to overclock.
Click to expand...
Click to collapse
Not worried about OCing. UVing might be nice...but I'm thinking unnecessary for battery life- First discharge gave me 1 day 12 hours after WHALE-HEAVY use...and even then I still had 20% left.
This is something I'm actually in awe regarding.
Jack_R1 said:
3. Doesn't matter, as long as you're on one of the Gingerbread radios. Any of the latest will be good enough. No difference in baseband builds between different N1 models.
Click to expand...
Click to collapse
Awesome. Now, real quick- did MIUI include a GB radio upon flashing it? I haven't flashed one specifically yet...should I head over to the Kernel/Radio thread and pick one out? Also, just to clarify/double-check, you're saying that a T-Mo N1 = Vodafone UK N1 etc etc? Same hardware and everything? (Obviously excluding N1's designed for AT&T's freq's?)
Jack_R1 said:
4. You're going to eat a lot of pain with screen touch craziness, which is the most painful part of this phone. The second most painful part is sub-par GPU, but unless you game a lot, you won't notice it - MIUI is smooth. So I'm really in doubt you'll want to keep this phone for a long time. In any case, press the power button gently and closer to the inside of the phone, and avoid pressing it as much as you can (use ROMs with trackball wake and screen lock widget).
Click to expand...
Click to collapse
Ha! Yep, I've definitely gotten some odd touches from the screen even after my little time with it. I've found I am ALWAYS hitting the home button...or the area that REGISTERS as the home button...whenever I go to press the space bar when typing. Quite possible it's due to having only used Android phones w/ larger, 4" screens...so I'm used to "reaching down farther" for the space bar, so to speak. And about trackball/volume wake & screenlock widget- already on it, ha! Not only is it a lot more convenient, but I figured it's something I should get used to in light of the power button's frailty.
It occurs to me- how wiggly is the trackball supposed to be? When I got my phone and started playing with it, I noticed a slight amount of give before it'd click (to select). Is this normal? While it always returns to it's normal amount of...portruding (sp?)/portrusion, should there be NO give before it clicks? Thanks for the input.
Also...about the screen...are there any mods/hacks to make it more accurate/less glitchy? Fix multitouch snapping? Etc?
Lastly, I'd always rock the V6 supercharger script on my Atrix. Now that I'm on MIUI, do they have it baked in? If not, is it compatible? Does it make a difference?
Thanks for the info/input so far bro I really appreciate it.
xyrovice said:
Awesome. Now, real quick- did MIUI include a GB radio upon flashing it? I haven't flashed one specifically yet...should I head over to the Kernel/Radio thread and pick one out? Also, just to clarify/double-check, you're saying that a T-Mo N1 = Vodafone UK N1 etc etc? Same hardware and everything? (Obviously excluding N1's designed for AT&T's freq's?)
Click to expand...
Click to collapse
No rom should include a radio, and as a general rule you should always flash radios from fastboot to avoid any problems.
xyrovice said:
Also...about the screen...are there any mods/hacks to make it more accurate/less glitchy? Fix multitouch snapping? Etc?
Click to expand...
Click to collapse
What can be done has already been done as far as tweaks.
evilkorn said:
No rom should include a radio, and as a general rule you should always flash radios from fastboot to avoid any problems.
Click to expand...
Click to collapse
Hmm...gotcha. Just wondering (as I didn't mess w/ fastboot until the Atrix- all Captivate radios were just flashed in recovery), what problems could arise from non-fastboot flashes? And how likely is this? Thanks for the info btw.
Update:
Well so I quickly checked the Radio thread, specifically the newest one (from a Korean update?).
Read and read and read and read before doing anything...then went and checked my phone only to find out the baseband version in my setting>about phone matches that of the newest one: 5.12.00.08. Don't know what difference it makes, but I have a "U" halfway through instead of an "H." So, two possibilities: Either my phone shipped with it (Odd as it's a Korea update?), or it was included in the ROM. Either way, I haven't noticed any issues, and I figure I'll leave it be.
Thanks again for the info though fellas.
I know your questions probably have been answered but I'll give it a shot:
1 - Blackrose will repartition the N1's partitions regarding cache, data, and such. If you want MIUI or pretty much any Gingerbread ROM you most likely 99.9% don't need Blackrose or a custom partition layout. Only certain ICS ROMs require Blackrose. The custom HBOOT you are referring to is Blackrose and the custom partition sizes. There are no limits if you are on Blackrose, and you can always get rid of it just as easy as installing it. Getting rid of Blackrose HBOOT will also refer you back to the stock partition layouts, if you made any changes while on Blackrose.
2 - There are a rather great deal of kernels for the N1 out there. I can think of at least 5 main ones, such as Wilmonds, IR's, and many more. Most will work with any ROM, such as CM or MIUI. But as always, backup before you flash. As for need, you don't really need to flash a custom kernel yet it can help. Some kernels boast improving animations and performance while others try to boast battery saving. Just check out the comments of each kernel's thread for a true evaluation.
3 - As for radios, flashing is not really that important. Most N1's are on 5.08 version which is the latest release for the US; all be it that is is a year or so old. There is a newer 5.12 radio released in Korea but there is no need to flash/install it. Some say connection is better but there is no difference if you are in the US. No ROM requires a certain radio.
4 - I had my N1 for almost 2 years with absolutely no issue with any buttons. I do hear that some have issues with the power button however. I guess it depends how well you take care of your device. I have dropped my phone very rarely and I take pretty good care of it. No complaints here.
Hope this helped you. And welcome to the N1 community! Any other questions feel free to ask!
Androidity3000 said:
I know your questions probably have been answered but I'll give it a shot:
...
Hope this helped you. And welcome to the N1 community! Any other questions feel free to ask!
Click to expand...
Click to collapse
Awesome info bro! Your explanation of Blackrose was especially concise, simple, and informative. Thanks for the kernel advice too! I appreciate it man!
Hey fellas, I hate to double post in the interest of bumping, but there are still a couple questions I'm still wondering about, and I'd rather bumprez than make another/2/3 different threads about each question.
The info you've given me so far has been AWESOME, and I'd appreciate any more input you might have.
Thanks in advance fellas.
What are the remaining questions?
Can't go wrong with Nexus One. Any weakness in memory can be dealt with through blackrose and a2sd. Hardware issues are minimal and even potential power switch problem is easily repaired.
Sent from my Nexus One using xda premium
Jack_R1 said:
What are the remaining questions?
Click to expand...
Click to collapse
So sorry- let me lay them out:
(And my bad for getting back to this so late- been really quite swamped with life!)
xyrovice said:
It occurs to me- how wiggly is the trackball supposed to be? When I got my phone and started playing with it, I noticed a slight amount of give before it'd click (to select). Is this normal? While it always returns to it's normal amount of...portruding (sp?)/portrusion, should there be NO give before it clicks? Thanks for the input.
...
Lastly, I'd always rock the V6 supercharger script on my Atrix. Now that I'm on MIUI, do they have it baked in? If not, is it compatible? Does it make a difference?
Click to expand...
Click to collapse
Also, I'm wondering about the AMOLED vs SLCD differences- something I don't think I've asked about yet.
Basically, regarding any and all facets of a screen- what are the differences between the AMOLED and the SLCD hardware?
And to reiterate- I'm talking about any kind of difference regarding anything, whether it's vibrancy, clarity, powerdraw, touch-sensitivity/accuracy...anything at all.
Lastly, regarding Blackrose:
So, Androidity3000 gave me a great cliff's notes on Blackrose, but I want to make sure- If I flash Blackrose (which is a custom HBOOT that reconfigures the partition sizes so as to avoid space-constraint issues?) can I just keep that all the time? Can certain ROMs NOT be flashed if I'm running Blackrose? Also, does Blackrose automatically decide the sizes of the new partitions, or do I have to configure the sizes myself? If so, are different configurations better, and why?
Thanks for all the good info and patience so far, breauxs. I appreciate it.
Trackball has some free movement, what you describe seems normal.
I've expressed my opinion on all kinds of "magical" scripts at some other point in time. Look at the free memory you have (which is probably >100MB at any given point in time), and think - do you need anything?
SLCD and AMOLED look a bit different. If you search the forum and Google, I bet you find enough examples and explanations. The question seems way too lazy.
Read the Blackrose thread to understand more, what it is and what it does. Also too lazy of a question.
I just picked up a N1 off ebay. It is in almost new condition got it for $155.00. I moving over from a mytouch 3g fender so the n1 is much better, i love it. This post helped me out alot. I've always wanted the n1 I've had my mytouch since it came out
Jeffrey.Dahmer said:
I just picked up a N1 off ebay. It is in almost new condition got it for $155.00. I moving over from a mytouch 3g fender so the n1 is much better, i love it. This post helped me out alot. I've always wanted the n1 I've had my mytouch since it came out
Click to expand...
Click to collapse
Glad to hear it bro! I like thinking that there have gotta be others with the same questions/concerns as me, and I'm glad this thread was of some use!
...AND that, as it hopefully filled you in sufficiently, you didn't feel the need to make another thread!
Enjoy the phone man!
I purchased the HTC one from a sprint store. It is the M7_wls hboot 1.44.00. I promptly rooted it by unlocking the bootloader with fastboot and installed TWRP and cyanogenmod 10, since I used and loved cyanogenmod7 for 3 years on my EVO before physical damage and processing inferiority finally made me throw in the towel. It was perfect. beautiful. best device and ROM combo I ever saw. The HTC one and cyanogen 10: a match made in heaven. But then, quite unexpectedly, after allowing the phone to die on a job site one day, it would not take a charge. The good news is that sprint will not attempt to open the phone and so no unrooting was necessary to replace it. In fact they did it there in the store since I was within fourteen days of the original purchase date. No removable battery! It was their contention, and I tend to agree, that it simply became unseated within the case, although I hadn't dropped it. fine. new phone. I once again unlocked the bootloader and installed TWRP and cyanogenmod 10. used it for a day (which was quite cold and humid, but I was inside primarily) and the audio stopped working. No music, no in-call audio. While frantically texting customers, I managed to download the nightly cyanogen update and flash it. My in-call audio came back, but ringtones, notifications, music, games and all other possible audio remained null.
I unrooted it by running the RUU in a virtual machine (I use a mac) and, even returned to stock, no sound. In-call audio remained (thank god). I took it in again and after the obligatory sea of clerical errors, sprint ordered me a new one. I really don't want to go through this again. I love the phone, but business is suffering. Is it possible that either of these issues were my fault? I've heard the inside of the M7 is quite convoluted and littered with coaxial cables like older HTCs and I did drop the second one twice. It had a nice case and simply slid out of the angled, inside breast pocket of my coat maybe three feet onto the floor each time. No such occurrence on the first. It makes sense what some are saying that the sound card simply became disconnected inside the case, but now I'm wondering if I'm mussing the root up somehow. My new phone will be here in a few days and I'm simply never going to use Sense 5. I'd rather eat discarded blowpops out of a sandbox. How can I make sure this doesn't happen again? Is it possible that these are both hardware defects and I'm the most unlucky customer ever? I see minimal cases of the latter issue occurring on the stock ROM, but it does happen. Usually it is fixable however. Mine was definitely not. Are these phones as unreliable as they have been for me? They seem to really impress even the picky crowd, so I'm thinking no. Help! Were these really both hardware issues, or did I mess them up?
Longest post I've ever seen. LOL
Sent from my HTCONE using Tapatalk
I would unlock, root, and S-off your new device as soon as you get it, and try something different. CM10 is pretty outdated as it is, and even if you are hesitant to go to a newer version for fear of having a less stable experience, there are plenty of 10.2 ROMs that should be stable. Not only that, but there are numerous stock-based ROMs that will offer a great user experience with the ability to disable sense or remove it completely. RENOVATE is a great choice for that sort of experience. If you are looking to try something new, my latest build of Beanstalk is 4.4.2, CM based, and offers a lot of custom features not found in most other ROMs here at M7SPR. It does have some small bugs here and there, but nothing that impedes your ability to use it as a daily driver. Not pimping my own build, mind you, just offering options. So, give something new a try and hope for the best is my advice. Oh, and try harder not to drop the damn thing.
Happy Holidays!
derp
elvisypi said:
Longest post I've ever seen. LOL
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Yeah, sorry for the verbosity. I think I may have a problem 19th century British dramas.
hey thanks!
BMP7777 said:
I would unlock, root, and S-off your new device as soon as you get it, and try something different. CM10 is pretty outdated as it is, and even if you are hesitant to go to a newer version for fear of having a less stable experience, there are plenty of 10.2 ROMs that should be stable. Not only that, but there are numerous stock-based ROMs that will offer a great user experience with the ability to disable sense or remove it completely. RENOVATE is a great choice for that sort of experience. If you are looking to try something new, my latest build of Beanstalk is 4.4.2, CM based, and offers a lot of custom features not found in most other ROMs here at M7SPR. It does have some small bugs here and there, but nothing that impedes your ability to use it as a daily driver. Not pimping my own build, mind you, just offering options. So, give something new a try and hope for the best is my advice. Oh, and try harder not to drop the damn thing.
Happy Holidays!
Click to expand...
Click to collapse
Thanks for the advice!:highfive: Out of curiosity, why do you say to get s-off instead of just HTCdev unlock? Also, I find alot of files that I assume are for the m7wls with m7spr in the title. I don't really not follow most of what people have posted about the different modes and titles, but I gather that as long as the ROM says m7 and is a CDMA version I'm good? I'm going to superglue this new one to my hand. not really. I need to be more careful though. never had a nice phone before. I would like one that has kitkat... I never had that phase of, "I hope I don't mess my phone up," with the EVO, but I like the one so much that I find I'm apprehensive about ROMs now. For the sake of calming my paranoia, what do you think the likelihood is that either of those issues had to do with CM10? It feels low to me since I unrooted and the problem persisted on the second one. Do you use your kitkat mod? I kinda do want kitkat and I'm such a fan of CM. admittedly partially because I like the color, but still. I like it. Where can I download?
Eligible, not elagible...
I will be purchasing a brand new, in box, LG G2 from Verizon even though I could get the G3. Why? Because the G2 is more developed and from everything I have read, is better in a few ways (Same mAh battery, but charge held better and build quality is greater, etc). If you disagree, let me know why please. I can still reconsider after all...
I just have a few questions. I did search the forum before hand, but found an overwheling amount of information. Processing it all will take a while so I figured I would ask here and see what the already informed have to say.
What is the best way to root currently?
For warrenty purposes, what is the best way to unroot?
I've seen some things about a flag in "Download Mode" that flips when rooting. Does the unroot method above address said flag in "Download Mode"?
In your opinion, what is the best AOSP or AOKP rom to flash?
What recovery should I use, if any?
Any tips I should hear?
Thanks for your time. I'm still quite new with all of this stuff, and just want to make sure I get it right. Better to ask questions than to guess, right?
Animalthewolf said:
Eligible, not elagible...
I will be purchasing a brand new, in box, LG G2 from Verizon even though I could get the G3. Why? Because the G2 is more developed and from everything I have read, is better in a few ways (Same mAh battery, but charge held better and build quality is greater, etc). If you disagree, let me know why please. I can still reconsider after all...
I just have a few questions. I did search the forum before hand, but found an overwheling amount of information. Processing it all will take a while so I figured I would ask here and see what the already informed have to say.
What is the best way to root currently? - ioroot25
For warrenty purposes, what is the best way to unroot? - The return to stock guide in the General section
I've seen some things about a flag in "Download Mode" that flips when rooting. Does the unroot method above address said flag in "Download Mode"? Yes
In your opinion, what is the best AOSP or AOKP rom to flash? Carbon or Gummy
What recovery should I use, if any? TWRP, use Autorec to install it, there's some hoops you gotta jump through to get receovery on 4.4.2, it does it all for you.
Any tips I should hear? Be warned people are getting damaged displays from time to time flashing roms, your phone will be covered under warranty the first year so return to stock and exchange it if it happens.
Thanks for your time. I'm still quite new with all of this stuff, and just want to make sure I get it right. Better to ask questions than to guess, right?
Click to expand...
Click to collapse
See my comments above.
Thank you very much good sir!
Animalthewolf said:
Thank you very much good sir!
Click to expand...
Click to collapse
Stick to the G2. G3 is still new and to me its not really worth the upgrade in my opinion. I actually traded an s5 for my current g2. Best trade I done.