DO's AND DONT's FOR FLASHING GALAXY NOTE - Galaxy Note GT-N7000 General

DO:
1) Hate Gingerbread and pester Samsung about official ICS update to Note
2) Google around for best ways to root your device. Specifically check out rootgalaxynote.com for noob-friendly advice and videos
3) Check out in your phone's about settings and note down the kernel version and the ROM version on your device. Also note the manufacturer's official designation of your device (i717, N7000 or i9220 in this case)
4) Realize that what you do to your device is your own responsibility. Samsung and/or XDA and/or your mom won't be there when you are staring at a fancy black brick as a result of the RISKY procedures here. Well, maybe your mom will be there, so be good to her
5) Check which features are and are NOT working in a given ROM before flashing it
6) Be in it for the long haul and be prepared to tinker, adjust, flash, reflash, backup and restore to mold your device to your liking. There is NO ONE SIZE FITS ALL solution to anything
7) Purchase MyBackup Pro and make complete backups of your apps every now and then
8) Develop sufficient proficiency with ClockWork Mod to be able to Nandroid backup before EVERY flashing
9) Go to your local market and check for fallback options in case you lose your phone. Either shortlist the same device (Note) or get some cheaper options (such as dirt-cheap and excellent Galaxy Nexus) shortlisted. Make sure your bank account has the requisite sum before you even think about hitting download mode on your device
10) Keep in mind that for some strange reason, flashing a Note is more complicated and risky than flashing a GS2 which confirms that earlier assumption regarding both devices being largely the same is not that true
11) Keep in mind that NO TWO GADGETS, NO TWO SETUPS and NO TWO CONNECTIONS are the same, even though they might be the SAME model from the same manufacturer. Some might have different memory, or a different radio, or your PC/Laptop might have a few kilobytes missing from the downloaded drivers, or there might be a power surge. Bottom line: following the same steps as another user might NOT give you the same results.
12) Hit search for 'ICS Repack' in any Note ROM forum. That, and the unstable leaked kernels (LP5/LP6) seem to be causing the most cases of bricking of Note while flashing. Avoid ICS repack if you can - I did with good results.
DON'T
1) Think that the ROM creator, or Samsung, or your mom, is in any way responsible for anything bad that happens to your device
2) Flash without ensuring that your kernel is up for it (see (3) above)
3) Skip steps or downloads in a lengthy procedure in hopes that things will work out in the end
4) Backup or restore system apps via MyBackup or Titanium
5) Conclude on the performance of your battery before going thru several charge/recharge cycles
6) Adopt an accusatory tone in your comments

Thanks captain obvious.

someone actually thanked the OP for this list?

panyan said:
someone actually thanked the OP for this list?
Click to expand...
Click to collapse
That's a bad thing why? If the majority of new Note users would actually read lists like these we'd have a lot less 'oh noes' and 'why doesn't this work' threads and posts.
Taking the time to make a list like this shouldnt be rewarded with ****ty remarks like yours or irish-sid's. At least he's trying to contribute something to this community.

DO:
11) Flame OP
Sent from my GT-N7000 using XDA

irish-sid said:
Thanks captain obvious.
Click to expand...
Click to collapse
panyan said:
someone actually thanked the OP for this list?
Click to expand...
Click to collapse
Beretta93 said:
DO:
11) Flame OP
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
you guys are what's wrong with this community and the world in general. zero tolerance for anything. The OP is just trying to be helpful, no need for snide comments, and useless posts unless its helping answer someone's question or making an informative post/thread. If something is misleading, then yes make a post that's letting someone know its misleading, THAT's informative. This may all be obvious, but its all the right information given, and it may help someone that's new here, and even to regular members.

It's a joke come on...
Sent from my GT-N7000 using XDA

fail0verflow - Long-ass dos and don'ts list with not a mention of ICS repack kernel issues, which is THE most important issue for this device right now.

Entropy512 FTW!
Sent from my GT-N7000

Nice list. Problem is: People who really need such info usually don't read or google They prefer to ask the same questions over and over again.
Sent from my rooted Galaxy Note using XDA Premium App

Thanks op.
Why would anyone need to search rootgalaxynote.com to know the best method when everything is here at xda (most of the time those guides are copied from XDA). Don't take me wrong I appreciate your efforts.
It should mention ICS kernel repack issues.
My friend bricked his phone while flashing with Odin.
He had custom power saving plan on his laptop that put it to sleep mode in the middle of flashing process.
You should never leave flashing with PC Odin unattended if you have kids or a nasty dog at home.

Boy124 said:
You should never leave flashing with PC Odin unattended if you have kids or a nasty dog at home.
Click to expand...
Click to collapse
*nods sagely*
Sound advice!

panyan said:
someone actually thanked the OP for this list?
Click to expand...
Click to collapse
Listen, if you go even in a cursory manner around the Galaxy Note ROM forums (esp Stunner) you will plainly see that this guide is badly needed.
And thanks for taking out the time and the effort for that constructive comment.

Boy124 said:
Thanks op.
Why would anyone need to search rootgalaxynote.com to know the best method when everything is here at xda (most of the time those guides are copied from XDA). Don't take me wrong I appreciate your efforts.
It should mention ICS kernel repack issues.
My friend bricked his phone while flashing with Odin.
He had custom power saving plan on his laptop that put it to sleep mode in the middle of flashing process.
You should never leave flashing with PC Odin unattended if you have kids or a nasty dog at home.
Click to expand...
Click to collapse
Many thanks for your support. I intended it to be a general guide leading up to the relevant information in the forums, rather than reproducing the information here. That's why I stressed on people reading all the posts on an entire forum. Reading this would easily lead people to ICS repack related issues, but still I am editing the OP to include a mention.
I plugged rootgalaxynote.com simply because it contains some helpful videos, otherwise I agree that XDA has everything needed.

Oh boy.. look's like I've managed to transgress with several of the items listed.

Is there any advisable way to restore apps + app data (not system data) after a fresh flash? I'm really not crazy about starting from scratch every time. Seems very un-Androidy.

Xephrey said:
Is there any advisable way to restore apps + app data (not system data) after a fresh flash? I'm really not crazy about starting from scratch every time. Seems very un-Androidy.
Click to expand...
Click to collapse
Titanium backup. I advise you to buy the pro version. It's really worth it. You cant have a rooted phone and not have this (that's if you are even rooted).
Sent from my GT-N7000 using xda premium

Oh! He said not to backup or restore -system- apps. I'm retarded. Dunno why I missed that.

Related

Recommended Development Topic Outline

Ladies and gentle men,
Here's the example topic outline I've been promising for about a week now. I have wanted to create this for a while now, as many of the [ROM] and [Patch] topics are--how shall I phrase this?--messy. I'm putting this up as a reference guide, and it will be a work in progress. Please feel free to borrow the parts you like (including the whole thing!), criticize the parts you don't like, suggest and request improvements, and flame the trolls who will inevitably come, should this see much conversation.
I don't mean this as an insult to any of you developers, chefs, or script kiddies, I just think some of you could use some help in the UX/UI department, and I've got some time on my hands. I think your users and fans will thank both of us for it, as my intention is to improve the volume of information provided, and also make it much more readable.
Key Facets of Improvement
Breadth of information
Clarity
Conciseness
Standardization
Searchability
Index
Introduction, How-To Guide, and recommended Style Guide (This post.)
Example [ROM] Topic (not limited to ROMs!) (Second post.)
Example posted in
PHP:
* format for easy Copy & Paste (Third post.)
[/LIST]
* [CODE] parses the BB Code tags, therefore defeats its own purpose for existing. Weird, huh?
Example Outline Model
Introduction
This is where I tell you how awesome my new ROM is: AmericanJedi's SuPeR-MEGA-sweet-ICS-Candy totally rocks! It has all the features you want, and none of the crap you don't. It's built on a foundation of win, with a bit of profit and unicorns thrown in to guarantee you'll like it! I know you've never downloaded a ROM from me before (because I didn't make one before!!!), but this paragraph here is where I'm doing my damnedest to convince you to try it.
Features
Awesome Sauce
Unicorn blood
Baby tears (but only the happy ones)
Automagicalness
mkasick's Keyboard Tweak -- (Oh **** son, now you know it's good!)
Existing Issues
Umm, did you not read the Features list?
Oh yeah, it's only built on ICS. I'm still hacking Google's servers to get Jellybean.
Fixed Issues
Now with ICS added!
"Auto" added to Magicalness
Baby tears sync'd with CyanogenMod repository
E911 works better than EpicMTD CM7 -- Dials straight to the State Police, no messing around with local yokels!
Removed CIQ from GPS firmware
FAQs
Test Question 1?
Test Answer 1.
Test Question 2?
Test Answer 2.
DISCLAIMER
Some of my methods are... questionable. If you think I can be held responsible for any adverse effects this ROM may have on your phone, you are sadly mistaken! Please be intelligent enough to learn the ins and outs of the techniques described below and use some critical thinking skills before blindly jumping in head first. You have been warned!
Installation
-- Full Wipe Method (Nothing is saved from current ROM or user data!)
Do a Nandroid backup from Recovery and/or back up your apps and settings!
Do a full memory wipe (Cache, Dalvik, and /data partition) in Recovery
Smash your screen with a hammer (WARNING: it's made of Gorilla Glass, so you'll need to hit it hard! Wear safety glasses.)
Be sure you have a full charge before flashing! Use a modded charging cable (simple way: cut the end off) and connect directly to a 220v outlet
USB is waaay too slow, solder a SATA connector directly to the motherboard
-- Upgrade Method (Your data and settings should remain intact.)
Do a Nandroid backup and/or back up your apps and settings!
Do a partial memory wipe (Cache and Dalvik) in Recovery
Drop your phone repeatedly, increasing the height by two feet on each successive drop until your screen has the desired number of cracks
I can't think of anything funny for this step
Breakdance.
-- Caveats (Stuff I think you should know, but doesn't fit elsewhere.)
Nothing comes to mind!
I'm that damn good.
Bullet point #3!
Downloads
-- ROM
Current Build
Previous Build 1
Previous Build 2
Previous Build 3
Previous Build 4
-- Add-Ons
Google Apps ("GApps")
-- Source Code and Resources
http://github.com/SuPeR-MEGA-sweet-ICS-Candy
Screenshots and Videos
Homescreen
Settings Menu
About Phone
Recommended Add-Ons
Fairy Dust Kernel
Bronie Hack
AmericanJedi001's Rotation Lag Eliminator
Thanks and Acknowledgements
Thanks to pawitp for creating the topic that was the inspiration for this example outline, and for allowing me to copy from him: [ROM][ICS][ITL41D] teamhacksung's ICS Port for Galaxy S (BUILD 9). His well-written ROM post is what mine is based on.
Thanks to codest3r for his suggestions.
P.S. I may have gotten carried away with the whole "be funny so they'll like me!" routine. If you don't like fun and would prefer this whole thing be as serious as Stephen Hawking at a track meet (good analogy, right?) then post below and let everyone know how boring your life is. Wait, that whole postscript came out wrong. Let me start over...
[Code] Copy/Pasteable
Sorry for the PHP formatting tags, but CODE tags didn't preserve the code structure at all--they were parsing the BB code! It kind of makes sense, and kind of blows my mind. I thought CODE tags were supposed to A) use a fixed-width font, and B) display the code written as unicode, not parse the formatting! Eh, I found a workaround. And it's in pretty Christmas colors! But Holy Hell, was it a pain to restructure to look like my original code for the second post! Just try writing something that uses BB code (specifically lists), then try to post that and have it look the way you typed it for the sake of readability. I dare ya!
ExampleTopicOutline.txt straight from my Dropbox. (FYI: This will be updated more frequently than the PHP-formatted code below because it's a simple copy/paste, whereas wrangling the code to appear as you see it below makes me want to martyr myself.)
PHP:
[SIZE="4"][B]Introduction[/B][/SIZE]
This is where I tell you how awesome my new ROM is: AmericanJedi's SuPeR-MEGA-sweet-ICS-Candy totally rocks! It has all the features you want, and none of the crap you don't. It's built on a foundation of win, with a bit of profit and unicorns thrown in to guarantee you'll like it! I know you've never downloaded a ROM from me before (because I didn't make one before!!!), but this paragraph here is where I'm doing my damnedest to convince you to try it.
[SIZE="4"][B]Features[/B][/SIZE][LIST]
[*]Awesome Sauce
[*]Unicorn blood
[*]Baby tears (but only the happy ones)
[*]Automagicalness
[*]mkasick's Keyboard Tweak -- (Oh [I]****[/I] son, now you know it's good!
[/LIST]
[SIZE="4"][B]Existing Issues[/B][/SIZE][LIST]
[*]Umm, did you not read the Features list?
[*]Oh yeah, it's only built on ICS. I'm still hacking Google's servers to get Jellybean.
[/LIST]
[SIZE="4"][B]Fixed Issues[/B][/SIZE][LIST]
[*]Now with ICS added!
[*]"Auto" added to Magicalness
[*]Baby tears sync'd with CyanogenMod repository
[*]E911 works better than EpicMTD CM7 -- Dials straight to the State Police, no messing around with local yokels!
[*]Removed CIQ from GPS firmware
[/LIST]
[SIZE="4"][B]FAQs[/B][/SIZE]
[SIZE="4"][B]Installation[/B][/SIZE]
[SIZE="4"][B]Downloads[/B][/SIZE]
[SIZE="4"][B]Thanks and Acknowledgements[/B][/SIZE
]
thanks
first, we really need this it ll help alot
Almost 1st lol...sweet ics wit the baby tears mod (hope no babies were hurt while making this rom)...tried to download but link is broken. Great work tho bro!
Sent from my SPH-D700 using XDA App
Interesting. So aside from the good humor, as I understand it, you're trying to fork pawtip's CM9 code and also fork work from Deca's CM7 build? (such as 911 working)?
This thread seems fresh from the ice cream sandwich factory.
Almost fell for it.
Sent from my SPH-D700 using XDA App
Lol I love this thread I do think it would help, I myself have a hard time writing and organizing an OP.
Sent from my SPH-D700 using XDA Premium App
if done right, this could cut thread sizes in half! Thanks for bringing this to us!
Sent from my SPH-D700 using xda premium
adamdelozier said:
if done right, this could cut thread sizes in half! Thanks for bringing this to us!
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
BS LMAO most people on here are illiterate
Sent from my SPH-D700 using xda premium
jbadboy2007 said:
BS LMAO most people on here are illiterate
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Lol! That's why I said "could" and not will!
Sent from my SPH-D700 using xda premium
adamdelozier said:
if done right, this could cut thread sizes in half! Thanks for bringing this to us!
Click to expand...
Click to collapse
That's part of the reason for doing this, cut down on questions that should already be answered in the OP.
Thanks for the props guys, I'll continue to work on it. Any suggestions? I'm thinking of adding more color, but color can be distracting and therefore detract from the informative nature of an OP. Did I miss any important sections?
Lastly, let me know if I should add more seriousness. I promise I won't make fun of you for being a boring person! ...Much.
If only every OP was this clean and well organized.
I like it. Install steps and videos from QB both go under Installation? How about a caveats or modem compatibility section? Just thinking out loud.
Sent via Decadent Epic 4G CM7
codest3r said:
If only every OP was this clean and well organized.
Click to expand...
Click to collapse
Thanks, that's the idea!
codest3r said:
I like it. Install steps and videos from QB both go under Installation? How about a caveats or modem compatibility section? Just thinking out loud.
Click to expand...
Click to collapse
I'm afraid I don't follow you. I don't understand what you're saying about "install steps," and "QB," but I'll add a Caveats section or sub-section. As to modem compatibility, I believe that's a non-issue, but let me know why you think it's important and I'll seriously consider it. Thanks for the feedback!
AmericanJedi001 said:
I'm afraid I don't follow you. I don't understand what you're saying about "install steps," and "QB," but I'll add a Caveats section or sub-section. As to modem compatibility, I believe that's a non-issue, but let me know why you think it's important and I'll seriously consider it. Thanks for the feedback!
Click to expand...
Click to collapse
I see a lot of posts about what modem to use and where to get it and how to get it on. Maybe my perception. Maybe the modem deltas make it more challenging than usual. In the past I thought certain ROM bases were meant for specific modem.bin's. Maybe not so much anymore?
Install Steps... cause its not always as easy as flashing a ZIP, and even when it is best confirm it in OP cause some require a wipe, some don't, some have other dependencies before determining if a wipe is required. Used to the obligatory "nandroid first" was always there too. Just sayin'... ;-)
QB as in qbking77 and all his howto videos. Doesn't he have a video demo'ing or showing install steps for every ROM ever made on the Epic?
Sent via Decadent Epic 4G CM7
codest3r said:
I see a lot of posts about what modem to use and where to get it and how to get it on. Maybe my perception. Maybe the modem deltas make it more challenging than usual. In the past I thought certain ROM bases were meant for specific modem.bin's. Maybe not so much anymore?
Install Steps... cause its not always as easy as flashing a ZIP, and even when it is best confirm it in OP cause some require a wipe, some don't, some have other dependencies before determining if a wipe is required. Used to the obligatory "nandroid first" was always there too. Just sayin'... ;-)
QB as in qbking77 and all his howto videos. Doesn't he have a video demo'ing or showing install steps for every ROM ever made on the Epic?
Click to expand...
Click to collapse
Okay, now I follow you! I'll add the Modem sub-section, though I've never seen a ROM that has any particular modem requirements. In my experience, while the ROM and modem work hand-in-hand, they are separate issues that should be addressed independently. But to each, his own! If anyone doesn't like or need that section they can remove it.
Concerning Installation, I'll add more generic methods.
As to QBking77's how-to videos, that's a good suggestion for the Videos or Installation section.
Good ideas, keep 'em coming!
Would a Mod please sticky this? Surely a clean, well-formatted structure for posting new development projects would be a boon to these forums! If the Mod(s) would like, I will clean up the example to be more professional-looking and remove profanities. I can understand that being a requirement for stickies.
C'mon, surely other people agree this would be useful! If you think any part of it, from the Title to the footnotes, needs changing for this to be taken seriously, please let me know. I'd rather it be less funny and get used, than to be hilarious and fall into obscurity!
AmericanJedi001 said:
Okay, now I follow you! I'll add the Modem sub-section, though I've never seen a ROM that has any particular modem requirements. In my experience, while the ROM and modem work hand-in-hand, they are separate issues that should be addressed independently. But to each, his own! If anyone doesn't like or need that section they can remove it.
Click to expand...
Click to collapse
Right on bro! I think its handy for folks that run into an issue like this.
Good luck getting this stuck on the forum. I gotta say - the OP's look really good and clean in a web browser (I was using Tapatalk before).
codest3r said:
Right on bro! I think its handy for folks that run into an issue like this.
Good luck getting this stuck on the forum. I gotta say - the OP's look really good and clean in a web browser (I was using Tapatalk before).
Click to expand...
Click to collapse
Hmm, your link appears broken when I click it in the XDA app, but when I quoted you for this post it looks fine. Weird...
You saying the OPs look good in a web browser made me realize I hadn't checked them out with the XDA app--holy crap, what a train wreck! Apparently the app doesn't process lists properly (or at all!). I really don't want to change that formatting, but I know a lot of people use the app regularly, so maybe I should.
Or maybe the XDA app should be updated! <hint, hint> (I'm looking at you, XDA admins!)

[REF/SOLUTION] Samsung Custom Flash Counter (UPDATED)

*Disclaimer -- I just wanted to post this as an information source as people are just now starting to get their North American SGS III's and are eagerly awaiting ROOT and custom ROM access.
UPDATE as of 7/18/2012 -- Chainfire just posted a new version of Triangle Away that appears to work for the US/Canadian SGSIII variants.
Thanks to The Root for calling attention to it and directing folks to Chainfire's Twitter for quick testing (he's leaving for a month holiday) - http://forum.xda-developers.com/showthread.php?t=1781104
And pop over to Chainfire's thread to grab version 1.70 (or get the donation version on Play if you want to show him some love) - http://forum.xda-developers.com/showthread.php?t=1494114
With that said, if you are new to the latest line of Samsung Android devices, you should be aware that the latest devices have a Custom Binary Flash Counter built in.
What does that mean?
Well, for reasons still yet unknown, Samsung has built in code that will essentially track every time a user flashes certain unsigned pieces of code to their phone, including but not limited to recovery and kernels.
The general thinking is that Samsung and/or the carrier could take one look at this counter and refuse warranty service since modifying the phone is technically against the TOS. This is the risk.
Why is this important?
Many times the first (and most easily found) ROOT and CWM recovery solutions (if you don't know what CWM is, I highly suggest doing some reading up on this, as it's one of the basics of Sammy SGS ROM flashing) will trigger this counter. And once it's tripped -- it's not exactly easy on some devices to reset this counter.
How do I tell if the counter has been tripped?
It can manifest itself in many ways. For example on the SGS II, there would be a yellow caution sign with a triangle that would show up every time the phone would boot (hence the origin of the name Triangle Away which I mention below). On other devices, you see a counter when going into Download Mode. For example on the Galaxy Tab 2, in download mode there is a screen that mentions if a Custom Binary is loaded and a numbered counter of how many times a non-standard code has been flashed.
But what about Chainfire's Triangle Away and USB Jigs?
First, the USB Jig is an important tool to have since it allows folks to get into Download Mode without using a PC. Early on, users discovered on early versions of the SGS II, the USB Jig also reset the binary counter. However, in newer released bootloaders on the SGS II, as well as newer devices like the Galaxy Note, Tab 2, and SGS III -- Jigs don't reset the counter.
As for Triangle Away -- EDIT (7.18.2012) -- Version 1.70 is now compatible with the US & Canadian versions of the SGS III. Go show Chainfire (the dev) some love!
So what's the solution?
Now there are 2 choices (as of 7/18):
(A) EDIT -- thanks to MrRobinson there is now an way of rooting and adding CWM to the i747 w/o tripping the counter - http://forum.xda-developers.com/showthread.php?t=1739426
(if devs from the other carriers ask MrRobinson nicely, I'm sure he'd be happy to share what he did to get the root injected since it took a bit of tweaking. The CWM part should be universal);
(B) Or if you have already tripped the counter, as mentioned above, grab version 1.70 of Chainfire's Triangle Away - it now works on the US & Canadian versions.
EDIT: 6/22 - Changed the title to better reflect the post contents.
EDIT: 6/26 - Added appropriate [tag] due to forum combination.
EDIT: 6/28 - New Root w/o tripping counter for i747 linked
EDIT: 7/18 - Chainfire upped Triangle Away v1.70 that resets the counter.
OH NO!!!
Just kidding, most people on this forum really don't care, I'm sure it will be okay, the flash counter isn't the end of the world or even worthy of a long disclaimer from anyone but Samsung themselves.... What's a warranty, anyways? I have SquareTrade on all my previous devices and will try ZAGGshield on the SIII, they're both going to fix anything that happens to it if we're stupid enough not to follow directions by more than qualified devs!
KryptosXLayer2 said:
OH NO!!!
Just kidding, most people on this forum really don't care, I'm sure it will be okay, the flash counter isn't the end of the world or even worthy of a long disclaimer from anyone but Samsung themselves.... What's a warranty, anyways? I have SquareTrade on all my previous devices and will try ZAGGshield on the SIII, they're both going to fix anything that happens to it if we're stupid enough not to follow directions by more than qualified devs!
Click to expand...
Click to collapse
Hahah, my last phone (SGS II) was the first phone that I haven't had to warranty through AT&T (switched out my Cappy 3x, WinMo phones before at least once or twice each) and I'm actually very careful with my phones.
Just like the options -- but you're right, a lot of people will just dive in and go crazy and say hell with it.
I'm on my 3rd Captivate as well, all covered under warranty. I'll be somewhat worried about keeping my SGS3 warranty-able when I get it here in a week or 2.
Definitely useful information, until the dev's get things sorted out and proper hacks in place.
pinoymutt said:
Hahah, my last phone (SGS II) was the first phone that I haven't had to warranty through AT&T (switched out my Cappy 3x, WinMo phones before at least once or twice each) and I'm actually very careful with my phones.
Just like the options -- but you're right, a lot of people will just dive in and go crazy and say hell with it.
Click to expand...
Click to collapse
I added your warning to the first post of the odin thread in big red letters... hope that helps
Fallon said:
I'm on my 3rd Captivate as well, all covered under warranty. I'll be somewhat worried about keeping my SGS3 warranty-able when I get it here in a week or 2.
Definitely useful information, until the dev's get things sorted out and proper hacks in place.
Click to expand...
Click to collapse
This is going to be a very popular device, so I'm sure it won't be long before we get some talented devs over and this whole issue will become obsolete. They'll figure it out, it'll just take a little time! :good:
Or if you need to replace for warranty, kill the phone completely... like lamp cord to USB port adapter.
Sent from my SGH-T959 using XDA
junglizste said:
Or if you need to replace for warranty, kill the phone completely... like lamp cord to USB port adapter.
Sent from my SGH-T959 using XDA
Click to expand...
Click to collapse
That would be the 'shady way' to get around this problem as well, but was trying to stay away from that one in case someone electrocuted themselves!
pinoymutt said:
That would be the 'shady way' to get around this problem as well, but was trying to stay away from that one in case someone electrocuted themselves!
Click to expand...
Click to collapse
Microwave for 5-10 seconds will also kill it, and prolly safer than the lamp cord method.
Sent from my MB865 using xda premium
jimbridgman said:
Microwave for 5-10 seconds will also kill it, and prolly safer than the lamp cord method.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Reminds me of the old "lighting storm" trick if you have ever put an old CD in a microwave!
I'm sure 1-2 seconds is more than enough. Most microwaves are 900 Watts + so don't need very much time.Also don't include the battery when you microwave it.
Sent from my GT-I9100 using xda premium
Look man I know you are trying to warn people by posting this everywhere... But a couple of things...
1. This is not close to being development so wrong section
2. Posting once is enough no need to spoonfeed noobs and post it in every thread
3. If they are concerned with warranty they should not be on xda.
Please just calm your horse and post this once in the correct section... Because it seems like u just want people to praise u as a zomg u saved my warranty I love you... Or ur just fishing for thanks or both.
Sent from my HTC Desire HD using xda premium
howtomen said:
Look man I know you are trying to warn people by posting this everywhere... But a couple of things...
1. This is not close to being development so wrong section
2. Posting once is enough no need to spoonfeed noobs and post it in every thread
3. If they are concerned with warranty they should not be on xda.
Please just calm your horse and post this once in the correct section... Because it seems like u just want people to praise u as a zomg u saved my warranty I love you... Or ur just fishing for thanks or both.
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
Come'on man - I thought I've already settled this in the other thread. This is the last place I'm going to leave it - the thread is here as an FYI and I'm not going to mention it in other threads.
Please don't keep fueling the fire...
pinoymutt said:
Come'on man - I thought I've already settled this in the other thread. This is the last place I'm going to leave it - the thread is here as an FYI and I'm not going to mention it in other threads.
Please don't keep fueling the fire...
Click to expand...
Click to collapse
ok thank you but my point was that this isnt a dev topic... not fueling any fire just saying so that in the future if you are going to put out something similar u post in the correct forum.... which is General.
pinoymutt said:
Come'on man - I thought I've already settled this in the other thread. This is the last place I'm going to leave it - the thread is here as an FYI and I'm not going to mention it in other threads.
Please don't keep fueling the fire...
Click to expand...
Click to collapse
Wrong section or not, thank you for posting this. I am not an android noob but I am a Samsung noob.
Thanks have been given.
Sent from my Axiom MAXX!!
Thanks for the post! I don't know if this is the wrong section or not, but I do appreciate the brief explanation before deciding when to proceed with root. I am not new to Android, but this will be my first Samsung device. Rooting the HTC Desire and Incredible S didn't have considerations such as a flash counter to consider. Hopefully, I'll catch on to the lingo with Samsung rooting when the time comes to give it a try.
I think it fits just fine where it is as I don't usually go to the Q&A or General Discussions (thats what the search function is for). I am not noob to samsung, or galaxy, or android. The dev section is one of the first places I look when checking on any device new or old. I don't even have my phone yet, don't plan on rom'ing for a while but its good to know that a simple root may become an issue. I appreciate the time you took to get this info out there. That's just my ways though.
No worries guys. That was my original intention putting this thread in this particular area.
If one of the forum mods thinks it's better placed in another area they will let me know or move it accordingly. As long as it helps someone it's all good.
With root accomplished on the US variants things are going to get interesting but folks just gotta make sure they research before doing anything. There's already a kernel thread in the Sprint development side that was shut down because unfortunately the kernel hard bricked some phones (I think including the Op's) so one can't be too careful!
Sent from my GT-P3113 using Tapatalk 2
Thanks for the nice explanation, this is my first Samsung phone so I had no clue. Looks like I may hold off on rooting until a fix for this gets found, never know when you may need to make a warranty claim.
Well this has no links to a Rom, mod or kernel. Which means it's going to general.

[UPDATE:16.10.12]ATRI Atrix ThatRom Installer v2

hello, i've made an Automated Atrix ThatRom Installer.
This script will help noobs to do everything without any troubles.
The file is a rar archive with all firmware files + installer.
here is a link http://www.mobile-inform.com/content/view/1148/1/
this is early alpha. you take all responsibility on yourself. I do not recommend you to use this rom, but if you still want to use it - here it is
UPD Updated To ThatRom v2 (AtrICS)
all thanks to the author of ThatRomv2 (AtrICS), i made only the Installer!
With best regards
the_fly
I don't think that it's a good idea to make an automatic installer of something that it's no stable for someone who doesn't even know how to use fastboot nor flash a zip. Maybe when this finally reaches the stable "level", then you should do the Installer.
BravoMotorola said:
Maybe, until you're not annoying, you should stfu. Seriously stop trying to tell people what to do.
Click to expand...
Click to collapse
Wow dude, that was really uncalled for. He is actually right because now the op has put himself in a position to be harassed by anyone who tries this and messes up their phone even though they should and do know the risks. He was just trying to be helpful, he wasn't attacking the op for making it.
I agree making an unstable, untested, developer test build easily available to newbies is a very bad idea. If they can't at the VERY least learn how to use fastboot and adb, they should come nowhere near this ROM. Unless of course you really want to be held responsible for dozens of bricked and/or unusable phones, and be expected to provide extensive support at all times.
if they are noobs - it is their problem. Everything is written befoure me.
Everyone takes responsibility for their actions.
There were several noobs who were crying about ICS even if they do not know what to do. and they are happy now, despite the bugs.
I am not, but i made for those who are. I am not going to tell anyone to install it, i did only help, but i suggest nobody to install it.
It doesn't work and you know it. It's as if there was some paid software that people want, and you made a crack/patch for it, and then you say you don't advise using it. Do you really think people will stay away just because you advised so? No, they won't. In fact in that case your disclaimers make no difference whatsoever, you are equally at fault for making it available as they are for using it. Why do you think all anti-piracy companies always go after crack makers and distributors and not so much after users? I mean many crack makers also advise against using their cracks. But people are stupid and never listen, and in in the eyes of many crack makers are the original offenders.
Or if you want a different analogy - go find a mentally unstable person who can't really think straight (may seem offensive but noobs who want test builds on their phones clearly do not know what they're doing), then place a bottle of some drugs and a fresh needle within easy reach, and then tell them you advise not using it. Observe what happens.
IMO this kind of things are best dealt with preemptively, by not even making the potentially controversial stuff easily available.
you see, i've made first script of unlocking the boot a year ago. a lot of peole thanked me. they were happy - they unlocked once and than used other ways to change the firmware. They were noobs, but happy noobs. 18 000 downloads (i think some of them were same persons, for example me - while i was testing, or when i was unlocking for my friends), but only 4!!! broken phones. 2 of them caused by bad motherboard and 2 of them by ignoring the manual and all the warnings.
This one is more easy one. less questins. less work. just use it.
and if person already have unlocked boot there will be no problem with this FW
and i want to mention it again some users are happy enought with this fw. Some do not have reboots, some have but for them it is ok.
You should tell everyone that this is a very alpha rom. It does run without multiple reboots for most people per the forums. I personally have tried all methods and cannot get it to run.
I appreciate your efforts but this is not something that noobs will get any value from. You should be very clear upfront.
Sent from my MB860 using xda app-developers app
agurzhiy said:
hello, i've made an Automated Atrix ThatRom Installer.
This script will help noobs to do everything without any troubles.
The file is a rar archive with all firmware files + installer.
With best regards
the_fly
Click to expand...
Click to collapse
Thanks agurzhiy!
I am a proud noob who used your unlock script and will use this one.
For all the pros which have a problem with this- you have the same approach as Motorola - "It's complicated you can't understand this". It's my choice what to do with my phone and agurzhiy providing us noobs with a possibility to participate in the effort to make it better.
The bottom line is instead of criticize why don't you spend this time and energy on creating and helping the community. Remember you were ones noobs too.
Sent from my MB860 using xda app-developers app
e07015 said:
You should tell everyone that this is a very alpha rom. It does run without multiple reboots for most people per the forums. I personally have tried all methods and cannot get it to run.
I appreciate your efforts but this is not something that noobs will get any value from. You should be very clear upfront.
Click to expand...
Click to collapse
i think everyone knows that it is alpha rom. nobody is going to install a script if if nobody knows what's inside. But i will add that it is alpha
ComX said:
For all the pros which have a problem with this- you have the same approach as Motorola - "It's complicated you can't understand this".
Click to expand...
Click to collapse
You're missing my point entirely here. But that's okay. I don't want to argue anymore.
Is this just a fastboot script or an bootloader unlocker and ram fix etc etc
ravilov said:
You're missing my point entirely here. But that's okay. I don't want to argue anymore.
Click to expand...
Click to collapse
I do not think that this is an argument. It is more like sharing different views on a subject.
I know what you mean, you want to prevent (or at least warn) noobs from taking the risk of bricking their phone and you are right 100%. But let me ask you how many of XDA readers are dumb enough to download some thing like this without reading at least a bit about it(*). Give ppl a little credit, most of us will stop on red light although it is possible to continue. Take me for example: I wanted to use nebtop but had a difficulty to understand how to root. Than mramirezusa came out with Automatic bootloader for noobs like me and boom - now I'm using the atrix as a streamer and without this tool I couldn't do this on my own. My point is that having a possibility to do stuff is highly appreciated.
* Ryan Dunn: If You Gonna be Dumb - You Gotta Be Tough.
this is a fastboot script to make it faster and easyer for a noob
UPDATE:
added the 32 bit version for x86 Windows
agurzhiy said:
UPDATE:
added the 32 bit version for x86 Windows
Click to expand...
Click to collapse
Dude, you've only been thanked here 7 times... Stop thinking so highly of yourself.
Unless you are going to stick around the forums helping these guys out when they have issues with your release, because they won't have anywhere else to go, and because other devs are busy with their own stuff, than you should probably refrain from posting anything that makes it easier to flash dangerous software.
Unless you're willing to help "guy xyz" (since quotes seem to be in) on "page 74" when he asks again, "why am i having video issues after flash", because your main post lacks important details and explanation and your web link is not multi-lingual, please refrain from posting content which could be perceived as harmful to use.
Any good software community recommends first releasing to a smaller test group in order to work out major bugs and minimize any potential impact the software may have on the device... And, any good service community would recommend first releasing to a smaller test group in order to create a base to compare full deployment scenarios against... In no cases would they make it easy to install buggy software on devices of users who can not adequately report issues during alpha stages of software.
Why is it so hard to understand how that applies here?
Zeljko1234 said:
IMO, you should stop spending so much time here on the forum arguing with people. Don't get me wrong but your posts are usually quite offensive (example what I saw today). You post almost in every thread, smartassing noobs, playing to be moderator... If you know something, share it, if post or thread is against the rules, report it.
Now you're arguing with guy who made first script of unlocking the bootloader and in the same time insinuate that many of xda members are just dump.
Forum, especially xda, is about sharing knowledge not giving useless advise/comment or to google it.
P.S.
Sorry everyone for off topic.
Click to expand...
Click to collapse
We try not to feed him, Zeljko1234... Just let him be.
Your point is well deserved; but don't feed the trolls.
knigitz said:
Dude, you've only been thanked here 7 times... Stop thinking so highly of yourself.
Unless you are going to stick around the forums helping these guys out when they have issues with your release, because they won't have anywhere else to go, and because other devs are busy with their own stuff, than you should probably refrain from posting anything that makes it easier to flash dangerous software.
Unless you're willing to help "guy xyz" (since quotes seem to be in) on "page 74" when he asks again, "why am i having video issues after flash", because your main post lacks important details and explanation and your web link is not multi-lingual, please refrain from posting content which could be perceived as harmful to use.
Any good software community recommends first releasing to a smaller test group in order to work out major bugs and minimize any potential impact the software may have on the device... And, any good service community would recommend first releasing to a smaller test group in order to create a base to compare full deployment scenarios against... In no cases would they make it easy to install buggy software on devices of users who can not adequately report issues during alpha stages of software.
Why is it so hard to understand how that applies here?
Click to expand...
Click to collapse
Why don't you argue with epinter or any other person who put ThatRom?
Why are you arguing with me?
i made the thing easier, but i am not responsible for the uncomplete software. some people are lazy to use fastboot, but they know how to use it (i have flashed my phone 3 times while testing some of options to find out how it works)
other do not have enough knowledge to flash, but it's thair dream to have it, they are ready for the bugs and they alwas can ask me to help them to flash any other FW. And if they have unlocked boot - they can use CWM.
And the last group - the people who are just afraid to install after a lot of information about locking bootloaders. In russian community forums i've read 10 such questions from people who i know, from people who know how to use fastboot.
And if person do not want to install it - he may not install it!
I'm thankful to everyone who share knowledge. Even if I don't use everything, I usually download or read just to learn how. Without such guys, Internet itself will be mostly useless.
Do not blame anyone (especially epinter) for your mistake. He and many others guys spend a lot of their private time to figure how to do something, developing, supporting... and then sahre for free! As I can see, very rare they get donation. Almost never for the most loudest complainers which just wait that someone else will do something for them.
As I explained, as long as you are willing to stick around and help people with issues they encounter after flashing this, and provide more detailed instructions that people can read in your first post, it's not an issue.
Low thank count makes the more seasoned members cringe, as people release stuff that brick phones then disappear (it happens), leaving the community in a state of unrest trying to figure out the full impact of an unmaintained release, how many users were affected by the release, and a common way to fix the issues, and it leaves it up to other developers to explain to every xyz person to read this thread, read that thread, or flash this to fix.
Sent from my MB860 using Tapatalk 2

Let OUYA know we want custom ROMs supported

I'm keeping a track of how many requests we get relating custom firmware, and from what I'm seeing the user base is not as interested in custom firmware as you might think, which is echoed by this thread (we've shipped 60,000+ units, and less than 10 people have commented in the last month in this thread about getting access to recovery mode).
That doesn't mean that we're shooting the idea down, you need to keep in mind that in terms of priorities this is way down the list as you'd expect from any feature where it's being requested by less than one tenth of one percent of the user-base.
I'm sure @Wajeemba is familiar with CM requests that a very small minority of the user-base are very passionate about, so hopefully you can understand why we're not rushing to work on this.
Click to expand...
Click to collapse
Go to this thread and let them know we want support:
http://forums.ouya.tv/discussion/1380/recovery-mode
Done! The mobile site won't connect to the create account page for me, so I logged in with Google. Didn't want to do that, but I wanted to be sure I made the request. I hope it's cool with you that I copied this post to another forum.
Sent from my SCH-I535 using Tapatalk 2
TadeoNYC said:
Done! The mobile site won't connect to the create account page for me, so I logged in with Google. Didn't want to do that, but I wanted to be sure I made the request. I hope it's cool with you that I copied this post to another forum.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, the more the better!
I posted as well... I hope the admin/mod replies to my post though
Sent from my Nexus 10 using Tapatalk HD
Vinny75 said:
Thanks, the more the better!
Click to expand...
Click to collapse
I figured as much. Could this be moved to the general section? If there is a big groundswell of support it should make a better impact than posts trickling in over a few days.
Sent from my SCH-I535 using Tapatalk 2
Update: this what OUYA thinks of its customer's requests...
Posted by alsutton on http://ouyaforum.com/showthread.php?3193-Let-OUYA-know-we-NEED-to-be-able-to-boot-to-recovery
and a I monitor this forum as well, so thanks for the heads up you're trying to artificially raise the numbers beyond the level of people who'd normally ask for it.
My *personal* view (that's mine, not OUYAs) is that you don't NEED to be able to boot to recovery, you LIKE access to it. The system works fine without being able to boot to recovery, many people use it without even knowing what recovery is, so it's not needed to use your OUYA. A number of people have managed to make their device unbootable with just root access by experimenting with things like compiling new kernels, then expect OUYA to fix them. Personally I think this is a bit unreasonable (if you started changing parts of the engine in a car and it broke down would you go back to the dealership?), and I'm sure most of the user-base would like support focusing on things other than user created problems (yes, shipping, we know).
So just a "lets all post bomb -->this<-- thread" isn't going to get it raised up the priority list. All I have to do now is factor in the number of "me too posts" from people who may not actually know what they're asking for.
Click to expand...
Click to collapse
This is ridiculous and insulting.
Copied from Ouya's Google+ page.......
OUYA
Shared publicly *-* Jul 23, 2012
*
Hey +OUYA* devs! Don't worry about rooting your device (or purchasing the pre-rooted device). We will provide builds and instructions that can be used to restore the device to 'unrooted' factory state!
Official response to my support ticket:
The OUYA is based on Android which makes it far more open than other consoles, and an OUYA gives your root access which gives you access to far more access than most Android devices. We currently do not provide instructions on how to access recovery mode, and I can not comment on whether or not that may change in the future.
OUYA
Click to expand...
Click to collapse
Post-Bombing isn't helping anyone.
If someone's really interested in that matter, he'll find answers for his questions in this forum!
4rz0 said:
Post-Bombing isn't helping anyone.
If someone's really interested in that matter, he'll find answers for his questions in this forum!
Click to expand...
Click to collapse
These posts are not located in this forum and are relevant to the topic. thanks, though.
Post bombing either forum isn't helpful...
Sent from my SAMSUNG-SGH-I317 using xda premium
Voice your opinions here. I think it more clearly explains the situation we are working with.
s/with/against
http://www.reddit.com/r/ouya/comments/1gk0km/ouya_advertised_as_a_hackers_welcome_device_quite/
I was all set to buy an Ouya, but after reading this forum I'm not so sure. Ouya doesn't sound like a company I want to support. What do you guys think about the Mad Catz console coming out. I want Ouya's hardware not their restrictions. It seems like it will be more open. And to the guys at Ouya, don't hinder the peeps at xda, they are the ones that are going to make you successful.
I posted, thank you for the link. Was wondering where I should voice my concerns.
I posted[/URL as well. I based it mainly as a fail safe for things just happen. The other comments, were more based on others assumptions.
http://www.madcatz.com/m-o-j-o-android-micro-console/
What do you guys think about this. It seems like more what I want. I think if Ouya is going to be restrictive, all dev support should go to a better company. Lets face it, people are looking at the Ouya for what it could be not what it is. It has the hardware to easily replace all the Google Tvs, Apple TVs and Rokus. I actually want it to dual boot into Google TV. Anyway, the Ouya will be releasing soon and there will be many tech articles about it. If we can go onto those articles and leave comment about how the Ouya isn't the good solution we can make a good company popular. I think most people buying the Ouya are just assuming that they will be able to hack it any way they want.
Confused
So do we or dont we have access to a custom recovery? Based on the dev forum I see we have a customer recovery available..what issues are there with it? Also i see WIP for multiple custom roms and even a kernel. I can't imagine one would waste time and making these if there is no viable way to flash them.....
Any information would be much appreciated.
The custom recovery works, many confirmed it on that thread including myself, as for the rest there stillb WIP's
Sent from my Amazon Kindle Fire using xda app-developers app
ej_424 said:
So do we or dont we have access to a custom recovery? Based on the dev forum I see we have a customer recovery available..what issues are there with it? Also i see WIP for multiple custom roms and even a kernel. I can't imagine one would waste time and making these if there is no viable way to flash them.....
Any information would be much appreciated.
Click to expand...
Click to collapse
Ozz465 said:
The custom recovery works, many confirmed it on that thread including myself, as for the rest there stillb WIP's
Click to expand...
Click to collapse
Yes, we can do those things - the heart of the issue is that if any of those things mess up you have the potential to brick your device with no way to recover short of sending it back to OUYA, Inc. Most android device provide a method to enable a usb recovery mode in the event of such a drastic failure, the OUYA console does not. How many people are willing to test/use software that could potentially brick their $100 device that they have been waiting months to get?
ej_424 said:
So do we or dont we have access to a custom recovery? Based on the dev forum I see we have a customer recovery available..what issues are there with it? Also i see WIP for multiple custom roms and even a kernel. I can't imagine one would waste time and making these if there is no viable way to flash them.....
Any information would be much appreciated.
Click to expand...
Click to collapse
The thread title is a bit misleading/confusing, recovery is accessible by rebooting to recovery. The problem is that you there is no way to boot to recovery via hardware except crashing the device during boot up using a keyboard.
They have gone about it all wrong, by allowing users the tools to brick OUYA but not the tools to fix it. Forgive me if I am wrong, but booting in to recovery does not allow us to do anything we can't already do by rebooting in to recovery. I have to wonder if behind closed doors they are moving towards removing root access.
Sent from my SCH-I535 using Tapatalk 2

Rooted Lollipop, want to try Marshmallow.

Hey all, I've spent a couple hours sifting through these pages to find an answer I cannot see. Or, I'm not reading correctly.
I am currently running Jasmine Rom on my rooted/unlocked OF1 Note 3. After several months of everything working fine but slow here and there, I would like to try one of two things. If anyone has some insight (Google certainly doesn't ) that may or may not help me, I'd very much appreciate you...
1- Is unrooting as lollipo to update to marshmallow a good or bad idea? Why?
2- If good, could you point me to a page that I don't have to read 700 posts to find clear instructions to do so?
3- If bad, I will stick with what I have...BUT, I'd really like to get rid of the bloatware (permanently, if possible). Is this possible? NOTE: I've sifted through countless pages of safe to remove bloat, so I'm asking if there's a way to do this upon fresh rom installation?
4- I love this place. I've rooted many a phone with all of your help. I must say that this note 3 vzw section is a WRECK. How can non-devs possibly sort through all this to find working answers? I'm legit asking, not being a smartass...there's active threads from 1983, and how's a regular Joe who wants to play with his toys too supposed to make sense of the endless this-one-works no-it-doesn't mess?
I'm sincerely seeking some final, working answers to the above questions, any help would be appreciated. Thank you in advance.
There is no "update to marshmallow" AFAIK.
OF1 is Lolipop.
XDA has zero threshold to entry, so the postings here are from both geniuses and idiots. You get to sort through them.
Postings are made while the phones are in play - which is to say while stock firmware is changing constantly, and devs and hackers are making changes, revising their stuff and learning new tricks.
So in addition to info which is correct - and stays correct, there is also information that becomes incorrect with new software... or never was correct in the first place.
So yeah, XDA is a mess. But you are missing the point - that it's a hot mess.
Your expectation of perfectly curated data, 100% correct and up-to-date instructions that minimize your time (at the expense of others, naturally) is unreasonable for this simple reason: it doesn't exist anywhere else.
So... step up or step out.
All this stuff is optional behavior. If you don't have time for it, well... then you don't have time for it.
If you want to try marshmallow on your device flash this rom using TWRP : [ROM][CM13][6.0.1_r43][VZW][OTA-Updates] Temasek's UNOFFICIAL.
I'm using version V10.8 on my unlocked OF1 Note 3 and everything works, here is the thread: http://forum.xda-developers.com/ver...opment/rom-temaseks-unofficial-build-t3364382
bftb0 said:
There is no "update to marshmallow" AFAIK.
OF1 is Lolipop.
XDA has zero threshold to entry, so the postings here are from both geniuses and idiots. You get to sort through them.
Postings are made while the phones are in play - which is to say while stock firmware is changing constantly, and devs and hackers are making changes, revising their stuff and learning new tricks.
So in addition to info which is correct - and stays correct, there is also information that becomes incorrect with new software... or never was correct in the first place.
So yeah, XDA is a mess. But you are missing the point - that it's a hot mess.
Your expectation of perfectly curated data, 100% correct and up-to-date instructions that minimize your time (at the expense of others, naturally) is unreasonable for this simple reason: it doesn't exist anywhere else.
So... step up or step out.
All this stuff is optional behavior. If you don't have time for it, well... then you don't have time for it.
Click to expand...
Click to collapse
Thank you for the reply. I must say, though, there's a clear difference between everything being perfectly organized to my taste and organized for the everyman who doesn't have all day to sort through everything in the forum on a particular phone. Im not demanding anything, nor am I accusing anyone of laziness or ignorance. There's wasn't anything implying anyone should do anything. Rather, a question was posed to understand the processes. I get the point of this forum, and more to the point, I APPRECIATE this forum. But I will say that at some point clean up might be a good idea. That's an opinion, not a demand. It is silly to me how unkempt this PARTICULAR part of XDA is.
That said, I will continue to use it happily, messy, hot, or otherwise, and I appreciate everyone's work on these devices for the everyman to experience the full range of possibilities with our devices.
Thanks for the answers.
aaroon200 said:
If you want to try marshmallow on your device flash this rom using TWRP : [ROM][CM13][6.0.1_r43][VZW][OTA-Updates] Temasek's UNOFFICIAL.
I'm using version V10.8 on my unlocked OF1 Note 3 and everything works, here is the thread: http://forum.xda-developers.com/ver...opment/rom-temaseks-unofficial-build-t3364382
Click to expand...
Click to collapse
Awesome, I will check out it.
Forgive my tone on my original post, XDA. I believe I came across as *****y, and I didn't mean any offense.

Categories

Resources