Related
Hello!
I've been researching a lot the last few days about flashing ROMs, Unbranding and Root etc..
i currently have SGS2 which is also my first Smartphone / Andriod Phone.
So even tho I've read FAQ's Wikis guides. etc i still have some things to get cleared up. which i hope some here could help me with ^_^.
1. I live in Scandinavia, more specific Denmark. Do i have to use Certain "CSC" and "PHONE" Number/Codes, for the phone to work, where i live. afaik. the CSC and Phone is the things that controls WIFI BT GPS, and the 2g/3g networks.
2. Sometimes i see people mention "Kernel" and that its important to use a rom based on the same "kernel" is kernel just another word for firmware? the thing is i think its entirely different. some clarification is needed here.
3. If i flash a modified Stock rom To my phone. with ROOT CWM for example this one (http://forum.xda-developers.com/showthread.php?t=1103399). is it possible to undo Root and CWM. i'm in doubt because further down in the thread, he states by flashing a stock rom onto the phone, you can remove the triangle but not the root and cwm.
This is the things that is still unclear for me. and since it's my first time to try and do all this, i must be 100% sure, i understand it all correctly.
Thanks!
Edited the first post.
If the questions is hard to understand, i can try and Re-formulate them.
//Tolana
1. I live in Scandinavia, more specific Denmark. Do i have to use Certain "CSC" and "PHONE" Number/Codes, for the phone to work, where i live. afaik. the CSC and Phone is the things that controls WIFI BT GPS, and the 2g/3g networks.
on your dialler enter *#1234# and look at the last 3 letters of the description under PDA.
- You will also find this info if you go in to settings\about phone\Baseband Version
2. Sometimes i see people mention "Kernel" and that its important to use a rom based on the same "kernel" is kernel just another word for firmware? the thing is i think its entirely different. some clarification is needed here.
Similar to what I mentioned above, use one of the ROMs that has the same 'extension' as your phone now as it is most likely using the same modem etc..
3. If i flash a modified Stock rom To my phone. with ROOT CWM for example this one (http://forum.xda-developers.com/showthread.php?t=1103399). is it possible to undo Root and CWM. i'm in doubt because further down in the thread, he states by flashing a stock rom onto the phone, you can remove the triangle but not the root and cwm.
If you flash a stock, unmodified ROM, it will remove root. It's like getting an update from Samsung directly.
Tolana said:
Hello!
I've been researching a lot the last few days about flashing ROMs, Unbranding and Root etc..
i currently have SGS2 which is also my first Smartphone / Andriod Phone.
So even tho I've read FAQ's Wikis guides. etc i still have some things to get cleared up. which i hope some here could help me with ^_^.
2. Sometimes i see people mention "Kernel" and that its important to use a rom based on the same "kernel" is kernel just another word for firmware? the thing is i think its entirely different. some clarification is needed here.
Kernel is not firmware its the base below OS level that communicates with the CPU . Firmware is a full package CSC Modem OS Kernel APPS .
Kernels can be mixed but thats a user choice and user accepts it may not work well .
3. If i flash a modified Stock rom To my phone. with ROOT CWM for example this one (http://forum.xda-developers.com/sho...ecovery jig .
Makes it much easier .
jje
Click to expand...
Click to collapse
Thanks for the answers.
I'm still a bit unclear on my first subject.
The Modem/PHONE number, does it have to be a specific "Scandinavia Compatible" Number/Code for my phone to function with calls etc.
the same goes for the CSC code.
Thanks again.
//Tolana
Some users report that particular radios/modems work better in certain countries than others, but you sohuld be able to use ANY of the modem/radios found on these forums on your SGS2.
For example, my phone came with KE1 radio. I flashed KE7 to match the cf kernel installed when rooting. It works fine
Right. Thank You!
This Guide has been written to aid users both old and new as a generalization of how the entire process of phone customization works. It is useful and relevant knowledge that will aid in the process of unlock, root, flash, and recovery. This is not a tutorial on unlocking your HBOOT, nor is it a tutorial of how to root your phone. It is a list of things you should know before, during, and after you complete the process. Below is everything I could think of to help guide you as you attempt to obliterate unlock your phone. There are risks involved and you may end up with an unusable device, this is not to be taken lightly. However I have included a basic troubleshooting guide as well. Should you run into trouble, it lists some of the most common issues. If all goes well then congratulations on unlocking your device.
ROOT This is a term used for everything here. Basically there are areas of your phone that are locked out. Root gives you admin or superuser privledges that can be used to modify things like build.prop or app data that you could not normally access. Typically during to root process an app is installed on your phone that governs which apps are given exclusive superuser privileges to modify your system. Superuser by CHAINSDD and SuperSu by CHAINFIRE are the only two apps I'm aware of.
S-OFF Security off, Basically the Holy Grail of Android customization. This disables the security allowing you to directly modify the NAND memory of your device. This in turn allows you to apply patches, device drivers and other niceties not normally available. This is why developers work tirelessly to enable S-OFF (Be sure to thank them for their amazing work).
HBOOT - This is your boot loader and is very similar to the BIOS on a PC, it basically performs POST (power on self test). It is responsible for flashing official software releases, enabling FASTBOOT and is basically the bouncer outside a club. This is what initially stops you from flashing unsigned code to your phone. OEMs have begun offering tools to unlock your boot loader and enabling the use of fast boot. Examples include HTC DEV Unlock, Samsung Odin, and Motorola's Unlock My Device.
Note: Depending on the security of your HBOOT you may or may not have access to the boot partition. Best example would HTC's HBOOT software. Unlocked it only offers access to FASTBOOT which in turn allows for recovery and flashing of ROMs. It does block flashing radios and other firmware
What does upgrading your HBOOT do? It adds support for new hardware (future phones) or fix bugs (break any chance you have of S-OFF, it may also bed your significant other but I have yet to confirm)
Should I upgrade my HBOOT? If a new firmware is released they may contain bug fixes, new radios, or newer versions of Android. If you want S-OFF and have yet to obtain it, no. Developers may find an exploit that can be used to obtain S-OFF. If you are stuck with S-ON and are waiting for S-OFF, again the answer is no. Developers may find an exploit to obtain S-OFF. If you don't care about obtaining S-OFF and you want to update your firmware, flash new radios, or simply want the bug fixes then this is the only option you have while S-ON if you are running stock. The only real benefit comes from what you can not flash with S-ON, basically radios or update for various drivers.
What does downgrading my HBOOT do? It falls back to the previous version of HBOOT, in some cases developers have released tools to downgrade to a previous HBOOT allowing users to then exploit the older boot loader and achieve S-OFF. Some people with S-OFF will upgrade but there is no real benefit, it often causes more problems with ROMs. They then attempt to return to previous HBOOT (very real potential for bricking your phone)
How do I upgrade my HBOOT? By installing an OTA or by using official ROM Upgrade Utility (RUU) To my knowledge there is no other method for upgrading HBOOT
Why do I need to downgrade HBOOT? As of right now, you don't. Do not trifle in what you do not understand.
Does rooting my phone require a certain HBOOT? Root is not dependent on HBOOT
Help, I upgraded my HBOOT and lost root! HBOOT has nothing to do with removing root, the RUU replaced your ROM with one that doesn't have superuser privileges.
RUU ROM Upgrade Utility, this is used to update your phone or revert it to a OEM factory state. The most common use of RUU in the community is to restore the original recovery and or re-enable S-ON
RECOVERY A very small type of operating system that resides on a part of your phone that is separate from Android. It is used by OEMs to install official OTA updates. Developers have created custom recoveries such as CWM, Amon Ra, and TWRP that allow a user to flash unsigned ROMs to the phone allowing for a greater degree of customization not offered by the stock operating system.
Nandroid Also referred to as a system back up. This is a copy if your phone's current system state. It creates duplicate images of your kernel and system including system settings, apps and app data, userdata, and or any mods. First and foremost, this is the most important thing to do after you flash recovery and before you flash a ROM. Should anything go wrong during the course of flashing a new ROM package (ROM/Kernel) and or should you wish to return to a stock state, restoring a Nandroid is the easiest and most effective way. Always be sure to back up your current system state prior to flashing a new ROM and or Kernel.
Note: Using Flash Image GUI will replace kernel from within OS. Be sure to create Nandroid before using this app to flash a new kernel.
ROM A package consisting of a boot image (kernel) and a system image (AOS or Android Operating System, I will now refrain from calling it AOS in fear that Apple may ruthlessly try to sue me for infringing on such a broad generalization to an operating system). ROM broadly refers to all of the phone's software. A custom ROM is any ROM that is modified from stock OEM or AOSP (for good measure, Android Open Source Project)
AOSP vs STOCK
AOSP Pure untainted Android OS maintained by users who want a clean open source mobile OS that is available for everyone. This is the base for ROMs like CM10 or Kanged. This is also the starting point for all OEMs
STOCK A build of Android that has been customized by an OEM. At first manufacturers used the opportunity to build custom skinned versions of Android. They supplied custom apps which they packaged into the ROM separate from the apps available in the market as a means to include exclusive features. This started a fierce competition between manufacturers who began making radical changes to the lowest levels of Android, including the kernel and framework. This led to slow, unreliable devices (frustrating for many developers who only have one real world device) that may have great hardware but poor software. In order to satisfy carriers OEMs may remove features or add many unwanted features. The most prominent issue stemming from this practice has been the Carrier IQ debacle. Roms like Venom and Mean use stock as their base.
Note: The most recent changes done by HTC and other OEMs are so extensive that they now offer their own SDK (Software Development Kit) for app developers to be able to write applications that are compatible with their framework
Kernel It is the layer between software and hardware. It allows the hardware and software to communicate with each other. The kernels must match the ROM Base and Version. Sense with Sense, AOSP with AOSP, ICS with ICS, Jelly Bean with Jelly Bean
CPU Governors A CPU Governor controls the frequency of the processor in response to the workload placed on it. If your phone supports multiple forms of governing, You will have the option to choose how it affects the performance and battery power consumed.
On Demand Pretty much the standard governor. The way it work is by ramping up the frequency to max in order to ensure responsiveness and then sampling the work load and scaling down the frequency to match. This is done by setting maximum frequency when the CPU is busy and gradually scales down as CPU reaches idle.
Interactive Governor Similar to On Demand, Interactive will dynamically scale the clock frequency as the workload demands. This is where the similarities end however. Rather then ramping clock speed to max when CPU is busy, interactive determines how to scale the CPU as it comes out of the idle state. When the CPU leaves idle, the governor sets a timer (pre-set by the developer). If the CPU use is intensive between leaving idle and timer expiring, governor will assume the system is under clocked and ramp to max frequency. It is better suited to handling intermediate clock speeds. Think of this as a faster, smarter On Demand
Performance I got a fever, and the only prescription is more cowbell! This sets the min frequency to the max. Your phone will burn, your battery will spring a leak, and you will see insane benchmark scores. This is obviously not a day to day solution.
Power Save Is anyone home? This will set you max frequency to your min. What a bore.
User Space This allows the user to set the frequencies. Better suited to the more advanced users
Input/Output Schedulers Determines "who goes first" by assigning which operations go to the storage volumes.
NOOP Scheduler This scheduler works on a sort of "first come, first serve" basis and will implement request merging. Its best for solid state drives and good on DB systems. It uses the least amount of CPU cycles per request. The one flaw I can see straight away is "less cycles = less performance"
Deadline Scheduler Used to minimize latency, it reserves five queues and schedules all I/O operations accordingly. This is an aggressive scheduler that runs at near real time speed. It is great for reducing latency and like NOOP, works best on solid state drives, db systems, and reduces latency in any I/O request. When system becomes taxed, this scheduler becomes very unpredictable.
Completely Fair Queue Scheduler This scheduler is scalable per I/O Queue, it distributes I/O bandwidth to all I/O requests fairly and equally. It helps maintain balanced performance through out and is great for multiple processors. The problem is when too many requests are competing for bandwidth, performance degrades.
Simple Input Output Scheduler This is as plain as it gets. No priority queues, no reordering or sorting requests, and the most basic merging. Minimum latency and low overhead, this is a simple and reliable scheduler.
BFQ Scheduler I would rather not risk getting into trouble with this acronym, lets just say the B is for brain and the F is a no-no word. I have not really used this scheduler but it's supposed to be good for USB data transfer, high definition video recording, video streaming, and is a fairly reliable scheduler. In my personal use I didn't get very good results.
MD5 It is basically a finger print for files, the developers use this to help regular users verify the integrity of the file. Most recoveries already support MD5SUM to prevent users from flashing corrupt files. Always verify the MD5 of any Kernel or ROM before flashing it to your phone
How to verify MD5 Hash
In Windows Like most useful utilities in Windows this is not supported, you can download a small utility that will load the file and display the Checksum Hash needed to verify.
In OSX Open a terminal and navigate to the folder your ROM is in and type md5 filename.ext
In Linux Again open terminal, navigate to folder and type md5sum filename.ext
In Android Open a terminal emulator, navigate to folder and use the same command used in Linux. Not surprising as Android is Linux but really neat! There are also apps for checking MD5 Hash Sum
Crossplatform Download managers and manager extensions for browsers like Firefox and Chrome may come with Checksum built in
Recovery As stated, most if not all recoveries will verify checksum hash. It is still good practice to verify by other means to avoid a bad flash
ROM Downloaders I don't really trust these or any large download on Android, sue me. Downloader apps should have a means to verify hash
NAND or N(OT) + AND Named after its basic operating principle, it is a form of non-volatile flash memory. Devices such as USB drives, cameras, mp3 players, and cellphones use NAND to store necessary firmware/software needed to operate. On Android phones the NAND memory is what holds all the information that powers your device. It is divided into separate partitions that are used to store firmware, the kernel and the system along with any other information such as contacts and cached data.
The Partitions are as follows
BOOT This Partition holds the HBOOT and Kernel and as the name suggests, is responsible for the allowing the phone to start. This is the most important Partition in your NAND memory.
SYSTEM This Partition is what holds our beloved Operating System. It contains the entire Android Operating System and the apps that come preinstalled on our phones.
RECOVERY Recovery can be thought of as our alternative boot partition. It holds the advanced recovery console that we need for flashing our phones.
DATA Also refered to as user data. This partition holds our contacts, messages, apps, and settings.
CACHE This is for the temporary storage of frequently used app components and frequently used data.
MISC This contains various bits of information like CID (Carrier or region identification), hardware configurations and various hardware/system settings.
SD_EXT Not to be confused with the Ext-SD shortcut on some phones (a way to access the external SD) This is not a standard Partition, it is an additional partition stored or your SD card that acts as another data partition. This allows you to install apps on your SD card and store data relative to the apps installed.
ADB Android Debug Bridge, it is used for development purposes but it has its usefulness
adb push This allows you to copy a file or directory to a phone
adb pull This allows the opposite, copy a file or directory from the phone
adb sync Copy host - phone if there are any changes present
adb logcat View phone log
adb install [ -l ] [ -r ] < file name > Push package file to phone and install it (-l means forward lock the app, -r means reinstall the app keeping its data)
adb uninstall [ -k ] Removes app package from phone (-k means keep data and cache directories)
adb reboot [bootloader] Reboots phone into the bootloader
adb reboot [recovery] Reboots the phone into the recovery
FASTBOOT A command line interface that can be used to directly flash the file system in Android, it is quite possibly the most reliable method to use if you know what you are doing. HBOOT must be unlocked (OEM or S-OFF) to have access to FASTBOOT
fastboot devices List all connected devices/phones
fastboot update Flash/re-flash a phone from update.zip
fastboot flashall Flash boot, recovery, and system
fastboot flash Flash a specific partition (partitions are boot, recovery, system, cache, and userdata)
fastboot erase Erase specified partition
fastboot reboot Reboot phone normally
fastboot reboot-bootloader Reboot into bootloader
fastboot -w Erase cache and userdata
fastboot oem lock Relock the boot loader
Flash Image GUI Created by member joeykrim, it is an Android app used for flashing recoveries and kernels from with in Android ROM. This is an easy to use tool for OEM Unlocked (S-ON) users to replace/update the kernel and or recovery before rebooting into recovery to switch ROMs. I have not used this myself so I can not determine how safe it is. Always verify MD5SUM
HTC Dumlock Created by TeamWin as a means to flash phones with OEM Unlock (S-ON) on HTC devices with HBOOT that do not allow for boot partition to be flashed. It is built in to TWRP, TeamWin also offer a Universal Dumlock solution compatible with other recoveries. It is probably the safest method for new users despite its seemingly complex nature. It is installed from recovery and run from within Android similar to Flash Image GUI but does not flash kernels. It makes a back up of your boot and recovery and then it takes the back up recovery and writes it to boot from within OS, your phone will then reboot (some phones must reboot manually, do not boot to recovery). From here on the recovery is running from within boot, you must then restore boot and then you will be allowed to flash a ROM like you would if the phone was S-OFF. Be aware that this is not the most ideal method as it writes to your boot partition 3 times (recovery, then restore boot, then kernel). Still this is the most flexible method for new users.
Uniflash Created by member MihailPro, this utility is a veritable swiss army knife of Android customization. It is basically several tools rolled into one. It supports and automates adb, fastboot, image editing/creation, manipulation of file system, back up and restoration of NAND partitions.
Features:
Flash
flash core (My guess is this is the flashall command; boot, system, recovery)
flash recovery
flash splash
flash radio
flash official and custom firmware (updates, patches and zip files)
Modify
edit Build.Prop
remove bloat
install or remove custom applications
copy to and from the device (internal, external memory) with the option to delete files
wipe user data, cache and perform factory reset
Image Creation
Basically back up and recovery
Note: This application is not compatible with HTC Sync, in order to use it please uninstall sync. Those of us with HBOOT 1.15+ still can not modify certain aspects of the memory but this application should at least make it easier to fastboot flash kernels, recovery and or ROM
PRI Product Release Instruction, the protocol used for the transmission of voice and data across Sprint's cellular networks. It may be updated from time to time to improve battery life and/or performance. It will also be updated when any drastic changes are made to the network. This directly affects the performance of your phone's voice and data
PRL Priority/Preferred Roaming List, It is a database used primarily by CDMA networks. It provides a list of network identifiers(service providers), wireless bands, and sub bands used to select the best service for roaming (example of bands/sub bands: PCS wireless band is 1850mhz to 1990mhz, divided into 6 blocks I believe. Sprint uses 1900, Block G if I'm not mistaken). Rather then giving you the best and most reliable option, the carriers choose which service providers to use (they have roaming agreements which help keep company costs down).
NV Non volatile memory, it contains info for MEID/ESN/EVDO and other credentials.
Radios These are basically drivers for the radios on your phone (basically firmware) They pertain to CDMA/EVDO, WIMAX, LTE, BLUETOOTH, WIFI and even NFC. They may be updated with patches or bug fixes to improve battery life and or performance.
Note: The only means of flashing new firmware on S-On unlocked devices is by using official HTC software
Basic Troubleshooting
**Please take the time to read all the relevant info I have posted prior to reading the troubleshooting section. I promise it will help you to better understand your phone and that is the entire purpose of this guide**
Note: To those of you with CWM Recovery, it is recommended that you use TeamWin Recovery as it is better suited for our phones.
Brick This is a very serious problem, your device is catatonic and will not respond to the usual methods of power on/off or sim-pull. In some cases the phone comes back when the battery dies and is recharged, this isn't very often. There are un-bricking tools written by OEMs when they screw up (Samsung / Motorola) and there are tools written by developers working on S-OFF. They notice a very real danger and will supply the tool just in case (this is not possible in all cases). Bricking can and will be permanent in many situations
Boot loop There a different kinds of boot loop situations (also referred to as soft brick, please do not cry brick in the forums if it is a boot loop) the most common are a mismatch of kernel and ROM.
Help, my phone is stuck in a boot loop or my phone is stuck on HTC! Not a problem at all. Hold down the power button and continue to hold it, the capacitive buttons will begin flashing and phone will reboot. After the screen turns off let go of power for one second and the press and hold power and volume down to boot into the boot loader. This is known as a simulated battery pull. HTC built this in as a fail safe to reboot your phone, and it gives us a chance to jump into the boot loader should anything go wrong. Once you have successfully made it to the boot loader read through these forms of boot loop to understand what went wrong.
Known forms of boot loop
Generic Boot loop You have a working recovery and now you have installed your first ROM. There's just one problem every ROM you try boot loops but if you restore your back up and it runs fine. This is common when you haven't taken the time to wipe your phone before you flash. You can use a wipe script to clean your phone or you can systematically wipe Dalvik, Cache, Factory Restore, and then wipe System. Now you can flash your custom ROM (HBOOT 1.15+ requires you to flash the kernel separately)
Help my phone won't boot past the splash screen similar to a generic boot loop, the most common fix is to wipe the phone before flashing your ROM. Wipe your dalvik and cache, the factory reset and wipe system. You can now flash your new ROM
Kernel Issue You have flashed a kernel that may be corrupt, originate from a different base, or is just not supported by the ROM (not really the case these days, most developers are willing to share tweaks and custom code) The result is a phone that boots to a black screen and will hang or reboot.
Note: HBOOT 1.15+ requires you to flash the kernel separately, all relevant info to do so is in this guide.
ROM Issue The kernel boots and luckily the ROM takes to the kernel but something in the kernel does not agree with your ROM. The result is a phone that will boot to android and promptly reboot.
Missing ROM Due to a misunderstanding, you have already wiped all ROM data from phone (cache, dalvik, and system) and fastboot flashed the kernel. Now phone hangs on HTC boot screen and will not load Android. Only the kernel has been flashed, the screen hangs because there is no OS to load. Fear not, return to recovery and flash the ROM package that your boot.image originated from. Now select reboot to system and wait for your phone to restart. The kernel will boot, your OS will load, and all will be right with the world.
Update.zip or update pmg.zip This is a doozy, the rewrite didn't take and you no longer have a working kernel or system image, phone will keep booting to boot loader. If you updated using fastboot this will be less frustrating then if it was placed on the root of your phone/SD card. If fastboot method was used just jump into recovery and flash a working ROM package or restore a back up. If updating from boot loader, remove the SD card and delete update. The boot loader will continue to automatically read update and flash it until you do so.
Bad kernel and or system image and recovery Phone will boot to boot loader, will not boot to OS and selecting recovery will boot to boot loader. All is not lost, simply fastboot recovery and or boot image (for those on HBOOT 1.15 and higher) and then flash ROM from recovery. This happens but it is very unlikely it will happen to you.
MISC
Help I just flashed the latest *insert ROM here* and my apps wont open (force close) This isn't the end all solution, but in many cases you just boot into recovery and select fix permissions. If you still have apps force closing and you know its not from the market, you may have to boot recovery and wipe the system and data, you will then need to re-flash the ROM
Help I flashed a new ROM/update/script and now I can't access my internal/external SD card Its OK, the SD card has been corrupted but you can reformat it with recovery itself or by using recovery to mount the card and formatting it by PC
Help the internal card isn't recognized by recovery or PC! (This is rare so make sure before attempting this fix) You're card is beyond a simple reformat, the physical address linking the card and or entire card is corrupt. Don't panic, you have to start clean. Back up the info on you external or remove it, make sure you have a ROM available on your PC. Go into recovery and repartition your phone, this will wipe all memory. You then load up a working ROM (a bad back up may be responsible or just reintroduce the problem), after you have flashed the ROM (HBOOT 1.15+ must fastboot kernel, unless S-OFF) go ahead and boot into android and restore your apps.
Help I repartitioned my phone and now I'm having trouble with my apps Not a problem, go into recovery and fix permissions.
My power button is broken! While I really don't recommend continued flashing of your phone without a power button, you can use built in menu options to reboot to recovery or adb reboot to recovery and or adb boot to fastboot.
Note: In the event that recovery is somehow damaged, phone may boot to boot loader depending on the state of your system. To the best of my knowledge, there is no way out if power button is damaged
Help my power button is broken and I'm stuck in the bootloader without Rom or Recovery Without the power button you can not choose recovery from the menu, so even if you flash TWRP you are stuck in bootloader. Flash recovery normally so that you have it after the problem is fixed. (Type fastboot flash recovery twrp.img) Now flash recovery again, only this time you will flash to boot. (fastboot flash boot twrp.img) This is a workaround to get into TWRP. Now we reboot the phone and flash the rom. (Type fastboot reboot) Wipe the phone as you normally would. (Dalvik, Cache, Factory reset, System) Install a Rom that has a kernel installer and reboot.
I can't seem to get my GPS to lock onto my location You can try using an app called GPS Tools, it will clear any data and reset GPS
How do I check to make sure my ROM/Kernel isn't damaged? Open zip file prior to flash or verify MD5 Checksum Hash
How do I check MD5? Read my section on MD5 verification
How do I flash ROMs? You can use Regawmod but I recommend you use HTC DEV Unlock. The basic process for this is simple. Register to HTC Developer website, go to unlock device and select other. Follow the simple instructions to enable adb and request token(Its a unique identifier for each phone). The website will then ask for token and send an email with further instructions. Once you have unlocked the boot loader you will now have access to fastboot. You have 2 methods of flashing recovery, you may fastboot flash the recovery image or use the update zip provided by TeamWin (Make sure the zip or image is compatible with your phone and verify MD5 sum to ensure no corrupt files are flashed). Once recovery has been flashed, its best to boot into recovery and make a back up of your phone's current state. Now before attempting to flash any ROMs, boot back into stock Android and download Goo manager from the market. Once installed, open app and from the menu select install open recovery script. This will ensure you have the latest recovery incase the one you just flashed is out of date. It will also enable you to use yet another alternative method to reliably flash your phone. As always, please read all relevant information before you attempt to unlock or flash your device. There are guides to help you posted on the forums. Good Luck!
Note: HTC Device Drivers must be installed prior to using HTC Dev Unlock, it should be covered in the HTC's unlock instructions.
Help the RUU failed and my phone is stuck in boot loader Try running it again or failing that, flash twrp in fastboot, then flash a kernel from which ever rom package you wish to flash and flash rom in twrp. If you really want to update it would probably be better for you to flash a stock rom with a stock recovery and perform an OTA update. If you relocked your boot loader, just flash the unlock_code.bin which you can get by unlocking through HTC DEV
Help my Android has super ceded Isaac Asimov's Three Laws of Robotics You gave it root, what did you expect to happen. It's the ghost in the machine man, Sky Net has to happen eventually.
So a brooding teenager with a hatred for machines really is our only hope for survival? God no, an emo teenager is never the solution
I think this is it for the most part, everything here should help most users troubleshoot their phones by themselves.
Thank you thank you thank you
Oh yea FIRST lol
Sent from the depths of hell
---------- Post added at 01:13 AM ---------- Previous post was at 01:07 AM ----------
Btw nice write up suggestion if i may would be add link to my flashung thread that also has rx's link to his thread about everything just a suggestion
Sent from the depths of hell
didnt I shoot you, damn those incredible recoveries they save just about anything if you know how to use them. Also, I believe that post has inevitably given me some form of carpal-tunnel. That or I'm just tired of typing typing typing. ALSO, I thought about linking the guides but that would make it more of a tutorial style and I clearly state it is not a tutorial, all the relevant information is on XDA or linked by other members
om4 said:
didnt I shoot you, damn those incredible recoveries they save just about anything if you know how to use them. Also, I believe that post has inevitably given me some form of carpal-tunnel. That or I'm just tired of typing typing typing. ALSO, I thought about linking the guides but that would make it more of a tutorial style and I clearly state it is not a tutorial, all the relevant information is on XDA or linked by other members
Click to expand...
Click to collapse
Very true well sorry bout carpel tunnel and all that lol very informative tho if used that is
Sent from the depths of hell
These people better use it lol, I some what ignored the gf to write this and I suspect she will be forgoing all extra-curricular activities in retaliation
I've been a bit confused on this: If I have S-OFF already, flashing a new RUU isn't going to be a problem; right? All I would have to do is re-install a rooted ROM to be back to where I am now (using CMX)?
if you want the new radios you can flash a zip that has the new radios without changing your hboot
om4 said:
And for the love of God clear your Wallet settings before you do anything. Menu > Settings > Reset Google Wallet. This can not be done anywhere else, you have been warned
Click to expand...
Click to collapse
Actually, I think it has been proven that you don't have to clear Wallet settings. I can't remember where I read it, but the problems when the phone first came out were problems with the app itself. I have flashed around 5-6 times with a full wipe without clearing the settings and Wallet works fine. I use it every day.
sofla2 said:
Actually, I think it has been proven that you don't have to clear Wallet settings. I can't remember where I read it, but the problems when the phone first came out were problems with the app itself. I have flashed around 5-6 times with a full wipe without clearing the settings and Wallet works fine. I use it every day.
Click to expand...
Click to collapse
well 1.22.651.3 did reset some of the phones that had bricked the secure element but not all of them, there are users who havent taken the new updates either so better safe then sorry. I added it as an after thought just to be safe but if its no longer a concern I can remove it
om4 said:
well 1.22.651.3 did reset some of the phones that had bricked the secure element but not all of them, there are users who havent taken the new updates either so better safe then sorry. I added it as an after thought just to be safe but if its no longer a concern I can remove it
Click to expand...
Click to collapse
No, probably best to leave it to let people know there was a problem, especially if for some reason they are still on the original software.
sofla2 said:
No, probably best to leave it to let people know there was a problem, especially if for some reason they are still on the original software.
Click to expand...
Click to collapse
Out of curiosity I looked at the change log for Wallet, all data is stored in the cloud now. So if I'm understanding this correctly, the secure element problem appears to have been bypassed
om4 said:
Out of curiosity I looked at the change log for Wallet, all data is stored in the cloud now. So if I'm understanding this correctly, the secure element problem appears to have been bypassed
Click to expand...
Click to collapse
That is a possibility
Arrghh!!?!?!! A developer called MihailPro just released a tool aptly named Uniflash that now makes a good chunk of this irrelevant. Oh well, it makes things easier for everyone here. I guess I could always add troubleshooting scenarios, unless a dev thinks of a way to automate that as well lol
om4 said:
Arrghh!!?!?!! A developer called MihailPro just released a tool aptly named Uniflash that now makes a good chunk of this irrelevant. Oh well, it makes things easier for everyone here. I guess I could always add troubleshooting scenarios, unless a dev thinks of a way to automate that as well lol
Click to expand...
Click to collapse
I will have to search for that. Also, Joeykrim's Flash Image GUI works great! I have used it on a few of my compatible devices. It takes 5-10 seconds to flash an img
Sent from my EVO using Xparent SkyBlue Tapatalk 2
om4 said:
Arrghh!!?!?!! A developer called MihailPro just released a tool aptly named Uniflash that now makes a good chunk of this irrelevant.
Click to expand...
Click to collapse
This still deserves a sticky.
Here is the link for more info on Uniflash, for those interested: http://forum.xda-developers.com/showthread.php?t=1859261
Added basic information on Uniflash, i was trying to add it earlier but my internet hates me
side note: those who took the time to read and learn about the info I posted will most likely be able to name the adb/fastboot commands this program automates...not very useful but it shows how easy these tools become when you understand the underlying process
Pretty good write up, but the key is whether people actually read it
Rxpert said:
Pretty good write up, but the key is whether people actually read it
Click to expand...
Click to collapse
thats always the case and a major problem with american education lol
Wileout suggested I post links to the tools and guides on how to root. I sincerely thought about it but theres a major issue with that, if I post links for tutorials or links for the tools I listed the reader is more likely to skip reading and go straight to the tool. Then we end up with more people asking for help
Posting links to other threads also puts the burdon on you for keeping the information up to date. I'd suggest leaving out anything that changes rapidly
Rxpert said:
Posting links to other threads also puts the burdon on you for keeping the information up to date. I'd suggest leaving out anything that changes rapidly
Click to expand...
Click to collapse
pfft...thats half the guide now and I wrote that thing at 2am this morning
Hello!
I'm relatively new to the whole android scene (but pretty versed in PC knowledge). Picked up an HTC EVO 3D from Sprint 2 years ago, and up until now I've just been a "dumb user". Now that I qualify for an upgrade, I was looking into rooting my ever aging EVO 3D, just to get a feel for things.
Thing is, this seems like a completely different process than reformatting a PC, with much more risk involved. I would almost say the process is tantamount to flashing ones BIOS? Was wondering if anyone could offer some pointers or tips on where to start for a first timer? Is there one particular mainstream ROM that most have had luck with on this device? This one caught my eye, specifically because of the unlocked wifi tethering: http://forum.xda-developers.com/showthread.php?t=1327237 can anyone else vouch for this one?
With the tethering unlocked (assuming I dont go data crazy and download the entire internet) would a carrier ever be able to find out or cancel my account because of doing so? Is this illegal?
As far as the tools needed to do it, I understand I need this ROM (which is like an operating system?), as well as a Radio (is that pretty much a "phone app"?). There are other things I found on this page here like kernels and various tools. Do I need a kernel? If so which one, or is it preference? Do I download and install these tools onto my phone or onto a PC and root the phone via computer? What do these terms "S-off" and Hboot" mean that I keep seeing and hearing people throw around?
Just looking for a little clarification and guidance from this wonderful community, so thanks in advance for any you can offer
Alright to start with you are right this is nothing like reformatting a hdd and putting a new os on it is closer in similarity to flashing a bios on a pc. I would suggest you read over this http://forum.xda-developers.com/showthread.php?t=1889438 and the links within many many times before you start. If you are unsure about anything please ask before you start since there is always a chance that if done wrong you wont have a usable device. The chances are slim but they are there. Now to fill you in on the definitions that you have asked about.
ROM = OS . There are two main types in the HTC world. Sense, which is htc's OS (this uses a sense kernel more info later) and Aosp which is basically the foundation of all Android roms (these can not use a sense kernel)
S-off = This means that your phone is completely unlocked (most manufactures lock down the phone so users can not change things and mess up the phone) this allows you to flash roms, kernel, recoveries, hboots, radios, splash screens, etc. S-off is the best way to go.
Htc unlock = This will allow you to flash roms and recoveries, but not much else. Kernels can be flashed but you have to do a few tricks to get that to work. Again S-off is best
Recovery = This is a tiny OS that allows you to change roms, make and restore backups, and few other things
Hboot = This would be the same as a bootloader (bootstrap) on your PC. There are several versions for the 3D
Radio = Software that is used to communicate with cell towers (not a phone app or even similar)
Kernel = A software layer between the hardware and OS (kind of like a BIOS)
Now there are 3 main OS's for the 3d GB-gingerbread 2.3.x (oldest software), ICS- ice cream sandwich (newest officially supported by HTC), and JB- Jelly Bean (newest version from Google and not supported officially by HTC) you can think of this like xp, vista, and 7
Now any rom you install will come with a kernel. Some users like to change kernels for various reasons. If you decided to change kernels you need to follow a simple guide line. Kernel needs to be the same os version gb os- gb kernel ics os - ics kernel also need to match sense kernel to sense os and aosp kernel to aosp os. Now this can get confusing here with the 3D since some kernels have the aroma installer they can cover multiple os's and sense or aosp.
Now this is not a complete guide but just something to help you out. Always search for answers and then ask your questions before you do anything you are unsure of. No one minds helping you out as long as you do a little research of your own first.
unproventheorem, I would check out this thread if I was you
http://forum.xda-developers.com/showthread.php?t=1466228
That thread should get you along and explain things in detail with the proper definition of what they are and what they do
Here's Some info on hboots on 3D only so no confusion
http://forum.xda-developers.com/showthread.php?p=29844067
And how to root and S-off
http://forum.xda-developers.com/showthread.php?p=31617712
Sent from my One S using Tapatalk 2
My stats: Fairly comfortable with computer and other forms of tech, but have only recently began diving into the Android system. I have limited development/programming experience, however, I'm not a novice or noob to it but definitely not advanced. Importantly for those willing to help I understand most terminology and can follow instructions. Thanks in advance.
Phone Stats: AT&T Samsung Galaxy Note SGH-i717
Android Version: 2.3.6 (Gingerbread)
Baseband Version: i717UCLF6
Kernel Version: 2.6.35.11
Build number: GINGERBREAD.UCLA1
Root Access: Yes
Stock Rom: Unsure, bought online.
Carrier/Service Provider: Straight Talk (U.S.) Phone was previously used on the AT&T network exclusively, and done so with an AT&T provided SIM card. After I purchased it, I ordered a new SIM card from Straight Talk (U.S.) and reprogrammed the APN settings under their instruction in order for my phone service to work correctly, and have had no problems with that.
I can't stand being on Gingerbread any longer. I guess, since my phone is an AT&T phone but I'm using it through Straight Talk I can't get any of the OTA updates. I've tried downloading the OTA's several times, both, prior to and post Root access without success in either case.
So here are my questions:
1. Am I doing something incorrectly which might be keeping me from getting OTA updates? Please remember, I've tried downloading the OTA's several times both with and without Root Access and the conclusion is the same each time: "No Updates Available At This Time. Your Phone Appears To Be Up To Date. Try Again In 24hrs."
2. Is my only option at this point to manually update to a newer firmware? If so, should I update to a newer STOCK version or a custom ROM version?
3. If a manual update is the option, after reading my above outline of my own experience with the Android system, what would be way to go? Simple, not overly complex yet doesn't assume the user is either a complete moron or can write code in his sleep. I've checked into a couple of options. Rom Manager seems like it would be a nice route to go, but in the Recovery Setup portion I basically get told I can't use that application because my specific device isn't supported.
I checked out GooManager and, unless it's just me, it seems like it's an app that likes to do all the work without telling you what it's doing exactly, but when it does ask me or tell me information, I'm not always sure how to answer or react to it's warnings.
Plus, I've noticed that sometimes when downloading a ROM, sometimes I have to "flash" the gapps myself and other times I don't.
4. Is it easier to download everything separately and apply them one by one, for example the ROM then gapps then Kernal...etc? Or look for something that has it all in one package?
I have a laptop in which I can download/transfer programs and apps between it and my Note so download space and internet access isn't a problem.
Also, it most likely isn't information that is going to help in anyway, but I live in Oklahoma, United States of America.
Thanks for all the feedback...UnluckyOnion
I'm not answering these in any specific order,
As I kinda just sped read thru most of it...
Since you're rooted, or know how to, goomanager is superior to Rom manager.
It supports this device and has a current version of twrp to install, instead of an outdated cwm.
Just use it to install recovery, then boot your device into recovery and use that. Not the app. You'll be provided with much more information and this is the preferred way of flashing.
Official Updates are always "manual" either with a less than user friendly program called kies, or with a less annoying way (which you may be familiar with seeing as you've rooted) ODIN. Both pc programs used with the phone in download mode connected with usb cable.
Gapps are only needed to flash separately with an aosp based Rom as it's against Google's T.o.S. to include them in am entirely aftermarket compiled firmware, however if it's a Modified version of a stock based Rom (in this case TouchWiz) they can be, and thusly are, included within.
Official or custom is up to you really.
If official..just grab the .tar and flash it with Odin.
If custom, obtain a custom recovery either the way i mentioned above or downloading a .tar of twrp and use Odin to flash that.
Once you have a custom recovery, you'll simply be able to flash a Rom from there.
Roms include a kernel, if you want to use a different one than what is included, that would be flashed after the Rom.
After flashing you'll have to input your carriers apn settings in again.
studacris said:
I'm not answering these in any specific order,
As I kinda just sped read thru most of it...
Since you're rooted, or know how to, goomanager is superior to Rom manager.
It supports this device and has a current version of twrp to install, instead of an outdated cwm.
Just use it to install recovery, then boot your device into recovery and use that. Not the app. You'll be provided with much more information and this is the preferred way of flashing.
Official Updates are always "manual" either with a less than user friendly program called kies, or with a less annoying way (which you may be familiar with seeing as you've rooted) ODIN. Both pc programs used with the phone in download mode connected with usb cable.
Gapps are only needed to flash separately with an aosp based Rom as it's against Google's T.o.S. to include them in am entirely aftermarket compiled firmware, however if it's a Modified version of a stock based Rom (in this case TouchWiz) they can be, and thusly are, included within.
Official or custom is up to you really.
If official..just grab the .tar and flash it with Odin.
If custom, obtain a custom recovery either the way i mentioned above or downloading a .tar of twrp and use Odin to flash that.
Once you have a custom recovery, you'll simply be able to flash a Rom from there.
Roms include a kernel, if you want to use a different one than what is included, that would be flashed after the Rom.
After flashing you'll have to input your carriers apn settings in again.
Click to expand...
Click to collapse
Thanks for all the information and help...more importantly, thanks for taking the time. I have ODIN on my laptop and have always used it when needed but I saw a highly rated and positively commented Mobile version of ODIN in the Play Store that claims you can do everything from the convenience of your phone which sounds appealing, however it's kinda pricey, especially if it doesn't work. Would you recommend the mobile version or PC version? Also, I have been doing a lot of ROM and Root research as of late, and wondered something...Why so many different Galaxy Note's? It seems as though I have the least popular version with the most popular being from the Galaxy Note "N" series, specifically the N7000. If I download and use an application that says it's meant for the Galaxy Note N7000 and I use it on my Galaxy Note SGH-i717, what will happen? Nothing, something, brick, work perfectly, etc...?
The N series is not carrier branded and sold internationally, so naturally it's more popular compared to a north American variant.
DO NOT FLASH ANYTHING FOR THE N7000
IT WILL BRICK YOUR PHONE.
The international version has a different cpu, gpu and antenna, for north American LTE bands to work those key components needed to be different.
So I say again just to stress:
DO NOT FLASH ANYTHING FOR THE N7000
IT WILL BRICK YOUR PHONE.
As for Odin, you're either going to flashing a stock firmware, or if you choose a custom Rom, you'll only need Odin once to flash TWRP. Then all the rest will be done in recovery on the phone itself. No need for it after you've either manually updated to the latest stock rom, or flashed a recovery for use of custom roms
So... imo mobile Odin, though being nifty, is a bit pricey for how little you'll need it, whereas it's free on pc.
I don't think mobile Odin is even available for the i717. It's not listed in supported devices.
I tried installing mobile odin and it's not supported
Thanks for the reply. And an even bigger Thanks for downloading the app and checking. I admire sacrificing your own work just to help me out. So what about yourself? Would you suggest, advise or heed caution to anymore of my questions?
By the way, what are you two running?
As long as you read the op of threads and all other important posts that follow BEFORE ever touching your phone, I'd say try a custom Rom...if you decide you don't like any of them, you can Odin flash the stock jellybean firmware at any point.
I myself am running unofficial aokp compiled and posted by a fellow team member BlownFuze.
Oh yeah, how's it running? Nice and stable or crawling with bugs? Any key selling points?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
I'm on the stock 4.1.2 release and rooted.
Everything works, no bugs, but battery sucks. Even after removing and freezing useless processes a stock rom will never be as light and battery friendly as a custom rom.
I just upgraded to the same version. Planned on rooting over weekend. Any success since your last post? Do you nave preferred Root method?
Thanks
Unlucky Orion
Use Odin to flash twrp
Newest version of twrp "should" Sr that you're not rooted and ask if you would like to do so within recovery before booting back into the os.
If not, there's links to an su.zip to flash in twrp for root.
studacris said:
Use Odin to flash twrp
Newest version of twrp "should" Sr that you're not rooted and ask if you would like to do so within recovery before booting back into the os.
If not, there's links to an su.zip to flash in twrp for root.
Click to expand...
Click to collapse
Hey man, thanks, it worked like a charm. I appreciate the help from both you.
Here is a guide I put together for the VZW Galaxy Note III
I TAKE NO CREDIT FOR THE LINKS POSTED IN THIS GUIDE!!!
------------------
Section 1: How to return to Stock Android 4.X or recover from a Soft Brick
Section 2A: How to flash a Custom Recovery, Root, and More for the (Dev. Edition N3 ONLY)
2B: How to Root and flash a Custom Recovery for the Retail Locked N3
Section 3: Android Directory
Section 4: Android Glossary
-------------------
Section 1: How to return to Stock Android and recover from a Soft Brick.
Take Note If your Retail Locked N3 took the OTA update, you can not revert back to older firmware. Verizon now has Samsung blacklist the older firmwares bootloader after each update. If you try and flash older firmware the device will softbrick or fail at Aboot in Odin.
Step 1: Download and install Odin 3.09 to a Windows based PC - http://www.mediafire.com/download/c4jk4e4i553jscs/Odin3_v3.09.exe
Step 2: Download a stock Odin image and Pit file to the PC. If Odin does not recognize the file then extract it with a program such as 7zip.
RETAIL Locked N3 Restore Files
Official VRUEOB6 5.0- http://www.sammobile.com/firmwares/download/45906/N900VVRUEOB6_N900VVZWEOB6_VZW/
Official VRUDNK1 4.4.4-http://www.sammobile.com/firmwares/download/41501/N900VVRUDNK1_N900VVZWDNK1_VZW/
Official VRUCNC4 4.4.2- http://www.sammobile.com/firmwares/3/?download=29319
-Mirror- http://www.androidfilehost.com/?fid=23501681358549642
Official VRUBMJE 4.3- http://www.androidfilehost.com/?fid=23269279319196106
Developer Edition N3 Restore Files
DE_VRUBMJE 4.3-http://www.androidfilehost.com/?fid=23269279319196402
-------------
HLTE_32gb.PitFile- https://www.mediafire.com/?i3vfwql159a4bfo(works for both DE and Retail devices)
Step 3: Power device off, hold the volume down/home/power keys until you see a yellow triangle, then press the volume up key to access "odin or download mode".
Step 4: Open Odin and connect the oem usb cable from pc to device. The driver should automatically install( it did for me on windows 7 64bit). There should also be a "comport number" in upper left hand corner of Odin indicating communication between the pc & device.
*If the drivers do not automatically install, then manually install the drivers in link and proceed to the next step. http://forum.xda-developers.com/showthread.php?t=2038555
Step 5: Click on the Pit function of Odin and select Pit file you downloaded in Step:2.
Step 6: Click on the AP/PDA(depends on Odin version) function of Odin. Select the stock 4.3 image you downloaded in step 2, then select start. This operation should take less than 8 minutes before Odin will say pass/reset.
Step 7: Your device should boot back up into factory stock Android! However, these stock Odin files do not wipe data and as a result the device may bootloop or stick at the samsung sash screen depending on the devices state before flashing the above files.
To get the device to boot: power the device off, press and hold the volume up/home/power buttons until the samsung logo appears. The device will boot into recovery and from there you will need to wipe data/factory reset, then reboot.
----------------------------------------------------------------------------------------------------------------------
Section 2A: How to Flash a Custom Recovery, Root, and More For The (Dev. Edition N3 ONLY)
Do not worry about Knox, the DE device has no warranty anyway
Step 1: Download and Install Odin 3.09 and drivers from section 1 if you have not already.
Step 2: Download the Official CWM recovery.tar to the desktop of your PC
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltevzw/philz_touch_6.08.9-hltevzw.tar.md5
Step 3: Download the SuperSU.zip to the root of your Internal SD.
http://download.chainfire.eu/351/SuperSU/
Step 4: Power your device off, connect the OE usb cable from device to PC, Press and hold the volume down/home/ power buttons until you see a yellow triangle, then press volume up to access "odin/download mode". Take note there should be a Com port number in the upper left hand corner of Odin indicating communication with device.
Step 5: Click on the AP slot in Odin and find the recovery.image.tar you downloaded in step 2. Also make sure to Uncheck Auto Reboot!!
Step 6: Hit Start, Odin should take less then 15 seconds before indicating completion.
Step 7: Unplug device, Pull and Re-insert battery, Press and Hold the Volume UP/Home/Power buttons until you see the Samsung logo or indication that the device is Recovery Booting.
Step 8: Congrats you should now be booted into TWRP recovery!! Continue following directions below for ROOT!
Step 9: Create a Nandroid back up by tapping back up, chose partitions to back up(system, data, boot are standard), then swipe to back up. Return to the main menu by pressing the return arrow 2 times.
Step 10: Select Wipe, Advanced Wipe, Check both Cache and Dalvik cache, then swipe to perform action. Tap the return arrow 2 times to return to the main TWRP page.
Step 11: Select Install and find the root.zip you downloaded in step 3, then select it. Swipe to Confirm Flash.
Step 12: Navigate back to the home page and reboot. Once the device is booted up, open app drawer and confirm the SuperSU app is installed.
For Installing Kernels, Mods, Roms, or any .zip from Recovery
-Boot into Recovery via three finger method(hold vol. up/home/power)and follow steps 8-11, just replace the file in step 11 with the one you are trying to flash.
-The only extra step for flashing a Rom is to Wipe DATA in step 10.
-If something goes south and your device will not boot after flashing in recovery, this is where creating that Nandroid back up will save you. Simply power the device off, Three finger into Recovery, Select Restore, Then Select the back up you created and swipe to restore.
-----------------
Section 2B: How to Root and Flash Safe Strap Recovery for the Retail Locked N3
Step:1 First you need Root. https://towelroot.com/
- Click the Red symbol and download Towel Root.apk.
-Navigate to system setting/security/unknown sources and check the box.
-Install and run the TR.apk
Step 2: Once you have verified you have Root and updated SuperSU, head over to this thread and Download the SafeStrap.apk to the root of the devices internal sd(mount/sd).http://forum.xda-developers.com/showthread.php?t=2517610
Step 3: Open the app drawer and find the File Manager app(If you do not have this app download it from the playstore), use the app to find the SafeStrap.apk you downloaded in step 2.
Step 4: Click on the SafeStrap.apk and click Install.
Step 5: Navigate to the app drawer and open the SafeStrap app, agree to the disclaimer, then select install recovery.
Step 6: Reboot and you should see a new Splash screen upon boot.
Step 7: Congrats you now have Safestrap recovery and are ready to flash mods & roms.
Be Sure to Thank and/or donate to HashCode for his efforts!!
----------------------------------------------------------------------------------------------------------------------
Section 3: Android Directory
-----------------
[Firmware][Collection]Modems,Kernels,Stock Tars-http://forum.xda-developers.com/showthread.php?t=2524572
-----------------
[How To][Disable Stock Apps Safely]- http://forum.xda-developers.com/showthread.php?t=2478589
[How To][Add Toggles to Notification Panel]- http://forum.xda-developers.com/showthread.php?t=2482867
[How To][Tethering Without Root]- http://forum.xda-developers.com/showthread.php?t=2480705
[How To][Videos]Root-Unlock-More- http://forum.xda-developers.com/showthread.php?t=2484201
------------------
[MOD][ROOT][All Root Methods]- http://www.note2forum.com/forum/galaxy-note-3-development/4355-root-methods-all-one-place.html
[MOD]Native Multiwindow-http://forum.xda-developers.com/showthread.php?t=2507975
------------------
Section 4: Android Glossary
Download Mode- This is a setting in which you will put your phone when using Odin. There are other ways, but most noobs will reach download mode by powering down, removing the battery, and holding volume down while plugging the factory usb cord into the computer and phone. Odin can only communicate properly with your phone if the phone is in download mode.
F. Reset Time- This is a check box in Odin. It's not clear that anyone knows the exact details of what it actually does, nor is it clear what will happen if you leave it unchecked vs checked. It seems to reset some arbitrary counter in your phone. As a general rule, you can either follow the instructions of whatever guide you're using or just leave the checkbox how you found it.
Fast Charge- This is a feature on some ICS ROMs that can be turned on or off. When enabled, it allows your phone to draw as much charge as possible regardless of the charging source. Without fast charge, your phone will place artificial speed limits on charging when plugged, for example, into the USB slot on your computer. Fast charge bypasses these limits, letting your phone believe it is always plugged into a wall charger. It is worth noting that your phone will not be recognized by your computer as a USB device when fast charge is enabled. It will only charge.
FC - Force Close- This is when an app stops working unexpectedly. This can happen to both rooted and unrooted phones. It doesn't cause any damage to the phone. In most cases, the app can just be opened right back up. It seems to depend on a lot of factors, including the quality of the app itself. ROMs and kernels that experience very few FCs are said to be "stable."
Flash- This is a term used to describe the installation of software onto your phone. It refers to fundamental changes in your phone's operating system. It is different from just installing an app from the Marketplace (Google Play). Commonly, people will flash ROMs, kernels, patches, and radios. There are basically two ways to flash new software onto your phone:1. Odin2. CWM Recovery (or a comparable recovery program)
Freeze -There are two meanings in general use. One might use this term to refer to his or her phone becoming unresponsive. More commonly, though, it refers to a special ability of a program called Titanium Backup. This program can be downloaded from the Android Marketplace (Google Play), but it requires a rooted phone to work. When Titanium Backup is used to freeze an app or process, that app or process is essentially gone from the phone. It won't show up in the app drawer, and it won't be running in the background. The difference between freezing and uninstalling, though, is that anything frozen can be quickly "thawed," also with Titanium Backup. With the touch of a button, the missing app or process is right back where it used to be. This is a convenient way for newly rooted users to test the waters of debloating.
Gapps - Google Apps- When flashing custom ROMs, the apps on the phone are usually deleted. As an alternative to going to the Marketplace (Google Play) and re-installing all the favorites (Google Maps, Google Talk, Google Voice, etc.), many devs have packaged these into a tidy zip file that can be flashed via CWM. Why don't they just put the Google Apps in the ROM, you ask? Custom ROMs and Google Apps get software updates at different rates, so keeping the two separate allows users to always have the most up-to-date version of each. On MTD ROMs such as CM7 or anything ICS, you generally must flash the gapps package to get the Android Marketplace (Google Play).
Governor- This refers to the type of logic your phone uses to control how fast its processor ramps up when needed or slows down when not. The choice of governor can influence overall performance and battery life. The governor can be selected using an OC/UV program such as Voltage Control or NS Tools. No one governor is right for everyone. The fun is in experimenting. Here are some examples and brief descriptions:
performance:Keeps the processor always ramped up to to maximum; useful for benchmarking.
ondemand:*Rapidly ramps up the processor when needed; gradually slows it down when not neededconservative:*Similar to ondemand, but ramps up more slowlyuserspace:*The user can define the parameters (for advanced users only).
lazy:*This was developed specifically for Android by xda dev Ezekeel. He states it is an enhanced version of ondemand, tuned to our phones' capabilities. Don't be fooled by the name. He tested it with numerous processor-intensive applications.
interactive:Uses a logic to try to predict how quickly it needs to ramp up processor speed, attempting to balance battery life and performance
interactiveX: A tweak on interactive (by dev imoseyon), which locks the processor at the minimum speed when the screen is off
smartass & smartassV2:Modified interactive governors by dev erasmux, they use logic to determine how quickly to ramp up or slow down; designed to optimize battery life without sacrificing performance.
powersave:This keeps the processor always set at the minimum frequency. The name may be a bit misleading, as certain processes will just take longer, using up more battery.
Heimdall- This program is similar to Odin. It was created by an Australian software company called Glass Echidna. It can be used to flash files onto your phone. Some users prefer this program over Odin. Heimdall can be used with Mac computers, whereas Odin can not. Many high level users regularly use both Heimdall and Odin.
init.d- This is a type of script used by developers when they modify Android code. You hear the term a lot because modifications using this type of script have far-reaching effects in the overall performance of the phone. High level users (who aren't quite devs) can even insert bits and pieces of init.d scripts to make minor tweaks to their phones.
Inverted- By default, most Google apps consist of a white screen with dark lettering. Inverting changes this to a dark screen with light letters. There are several advantages to this. Beyond the aesthetic advantages, it tends to be easier on the eyes in low light situations and reduce battery consumption. Inversion is done by talented individuals called themers.
I/O Scheduler- This refers to the type of logic your phone uses to order and process read and write requests to your phone's hard drive. There are several types, which are listed below, but there is no magic bullet. The joy is in finding the one that works for you in terms of performance and battery life. It is worth noting, though, that certain schedulers were designed to be used with mechanical rotating hard drives, taking the drive's rotational position into account. This does not apply to our phones, which use solid state drive technology. A scheduler can be selected by using an OC/UV control program such as Voltage Control or NS Tools. Specific descriptions are beyond the scope of this glossary, but simple Internet searches can expand on any of schedulers listed.*Examples: noop, deadline, cfq, bfq, sio, vr, bfs* In the absence of a dev's recommendation, if you don't feel like reading up on the subject, you can leave the scheduler at the default or choose noop or sio.
JB - Jelly Bean- Android 4.xGoogle likes to name its Android releases after sweet foods. This is the latest version of Android to hit the streets, and devs are flocking to it , making all JB development new and exciting.
Jig- This is a tiny Frankensteinian device made of a small chip, a transistor, and the tip of the little micro-USB connector that you plug into your phone to charge it or attach it to your computer. When your phone will not go into download mode through normal means, putting a jig into the phone when the battery is in will make your phone go into download mode. You can make one yourself or buy one online for less than $10.
Kang- Generally used as a verb, this means to take bits and pieces of someone else's coding and to then integrate it into your own. Granted, noobs won't be doing this, but devs do it all the time. For the most part, this is considered a welcome practice among friendly devs, provided it is done correctly and politely. Kanging often serves to better the community as a whole. The key for devs is to give credit to the other devs from whom they have kanged.
Kernel- This is one of the two main components (ROM being the other) of the software running on an Android phone. It is the piece of software that connects the hardware (screen, softkeys, vibration, speakers, etc.) to the other software components. An unrooted phone comes with a stock kernel. It is stable but somewhat slow. Practically speaking, installing (flashing) a custom kernel will make your phone feel much faster and smoother as it moves through screens and opens apps. Generally speaking, installing a new kernel will not change the basic appearance of your phone or erase any of your phone's information. Custom kernels can also unlock several abilities of rooted phones. Examples include:-wireless tethering (ignoring that pesky $30/month charge from Verizon)-control over how and when the softkeys at the bottom of the screen light up-overclocking/undervolting-voodoo lagfix (This only applies to phones with BML-based ROMs. MTD ROMs don't need lagfix.)-custom boot animationsLean Kernel*- Created by imoseyon, He intentionally leaves out a lot of the "bells and whistles" to keep the experience simple, smooth, and fast. Imoseyon works with several phones, so it is imperative that you have the correct version of Lean Kernel, the one appropriate for your phone.
Linaro- This is a team of software engineers developing open source software for numerous platforms, particularly as it relates to getting maximum bang for the buck from systems with memory and hardware limitations. For our purposes, many Linaro modifications are making their way into our custom ROMs, promising increased speed and responsiveness.*Logcat*- This is a log of all of the processing activity your phone did over a certain period of time. This is useful for bug reporting, as devs can examine logcats and attempt to determine the source of the error(s). Many threads in the development forum request logcats to go alongside any bug reports. A logcat can be generated through adb, and there are also some apps that will do it for you. Random complaints aren't terribly useful for devs, but logcats generally are. This classic cartoon illustrates how many devs feel about disorderly complaints about their work, even though most are far too polite to say anything.
Milestone- Devs are always trying to incorporate the latest and greatest features into their ROMs. The add-ons are incorporated as parts of new releases, or "builds." This is what makes development exciting, but it also leads to bugs. Milestone builds occur when the devs sit back, roll up their sleeves, and work the bugs out of all the awesome features they've crammed into their work. The milestones are considered the relatively safe and stable builds. When installed correctly, they rarely experience major bugs.
MIUI- This term is a transliteration of a Chinese name for a special customization of Android actually developed in China. MIUI ROMs can be installed on the Fascinate. They change the look and feel of the Android system, moving it closer to something resembling iOS, the iPhone's operating system. A lot of custom development has been done with the software code from the MIUI system. Many devs will integrate bits and pieces of MIUI into their own ROMs.
Nandroid- This is a backup of your entire phone as it stands at that moment in time (ROM, kernel, text messages, your Angry Birds progress, etc.). It is stored on your sd card, which is somewhat immune to your tinkering. A Nandroid backup is a good failsafe for the times when you might want to try out that new experimental kernel your favorite dev has been working on. The files can also be saved on a home computer/flash drive/etc. for safe keeping. Nandroid backups are created using a recovery program like Clockworkmod Recovery. CWM can also use old Nandroids to restore a phone to its previous condition.
Nightly - Nightlies- Some rooted users like the idea of having the most stable, tested, and reliable ROMs available. Others prefer the excitement of being on the cutting edge. Nightlies are the untested regular releases of whatever a certain dev happens to be working on at the time. They package them up, post them online, and let the discussions ensue. These are not for the faint of heart. They are for people who are comfortable addressing freezes, boot loops, and force closes.
Noob- If you have to ask what this means, this is what you are. It's a derivation of "newbie" or "newb," someone who's new to the activity at hand. In many ways, the noob is defined by his actions rather than by the amount of time he's spent rooting phones or posting on xda. Here are a few standard behaviors that will immediately brand someone as a noobosting new threads to ask questions that have been answered dozens of times. (Hint: It's best to search before posting)-Posting ROM complaints (without logcat), beginner questions, and other non-development topics in the development forums (It has been theorized that this will ultimately be the end of xda)-Diving in and flashing away without reading and then posting about your problems (Everyone needs to read the Guide.)
NSTools- This is an app that requires superuser permissions. It can be used to control a variety of the phone's features that are unlocked when running a custom kernel. It can enable fast charge, BLN, overclocking, and undervolting. It often comes pre-installed with ICS ROMs.*OC - Overclocking*- Computer processors operate at a variety of speeds. When a manufacturer sells a product (like a phone) to the general public, they strictly limit the speed at which the built in processor can operate, even though the processor may be capable of more. This is to promote stability and reliability. Rooted users can overclock their phone's processor, raising the maximum speed at which it can operate. This can be done through various apps, including Voltage Control and NS Tools. Some ROMs even have the controls built into their settings. There are limits, though. Running a processor at too high a speed can cause overheating and/or glitches.
Odin- This is a program of seemingly mysterious origins that allows your home computer to communicate with your phone. You download it to your home computer. Good communication with your phone requires the installation of Samsung drivers on your computer as well as the use of the USB cable that came with your phone. Among other things, Odin can be used to root your phone, install CWM Recovery, install custom ROMs and kernels, and return your phone to stock after you've screwed it up.**NEVER touch the "Phone" button on Odin. It should be labeled "Destroy your Phone"
OP - Original Post- This refers to the first post in any given thread, the one that started the thread in a discussion forum. A common noob mistake is to hop into a thread on page 27, read for 30 seconds, and then chime in with a question. He is often directed to the OP, which contains the answer to his question.*
OTA - Over the Air- These are the official firmware upgrades that Verizon has released over the life of this phone. They were either pushed out to our phones in the middle of the night or offered up for us to download at our convenience. Generally speaking, rooted users do not receive OTA updates. Also generally speaking, this doesn't really matter. The updates can be found on xda, and it is unlikely that the Fascinate will ever receive another OTA update.
Patch- This generally refers to a zip file that can be flashed using CWM. The file usually contains updates or small modifications to an existing ROM or kernel. A great example is the patch that reprograms the phone dialer's voicemail button to open Google Voice instead of the standard voicemail or Visual Voice Mail.
PDA Button- This is the button you will want to use when using the Odin program. You should always avoid the "Phone" button.
Pit file- This is a type of file used with Odin when returning your phone to stock. There is a "Pit" button on Odin you can push to enter the pit file you wish to use. An example of a pit file that you will probably use is Atlas_v2.2.pit. To return to stock, you would use a pit file along with a stock ROM, putting both into Odin at the same time. Droidstyle's guide provides detailed instructions.
Project Butter- This is a Google initiative, launched with Jelly Bean, aimed at reducing phone lag, both real and perceived. It involves research into human visual perception, the pairing of GPU and CPU, graphics buffering, and so on. It's purpose is to make your Android phone run "like buttah."
Radio - a.k.a. Modem- This generally refers to the software that manages the phone's connection to the outside world, not the physical device itself. Verizon would release new versions of this software from time to time in their OTA updates.
Recovery- Your phone comes with a recovery program. You have to choose to boot it up as an alternative to booting up your phone's normal touchscreen interface. An ordinary phone user would probably never even see this program. It's not pretty. It's just functional. It is basically a list of commands and technical terms that you can navigate using the phone's softkeys, volume up & down buttons, and the power button (to select). Essential to rooting are the special recovery programs such as CWM Recovery. A special recovery program, will replace the stock recovery program for a rooted user.
Re-Partition- This is one of the check boxes in Odin. This box should be checked only when returning your phone to stock. Of Odin's various check boxes, this is the only one for which widespread agreement of its use exists.
ROM- This is one of the two main components (kernel being the other) of the software running on an android phone. It generally determines the overall appearance of your phone, including which apps are installed by default. The ROM that comes installed on your phone right out of the box is known as the stock ROM. Created by devs, there are numerous custom ROMs available. The process of flashing a custom ROM to your phone will, generally speaking, erase everything on your phone. When you buy your phone from Verizon, Verizon still controls it. You are simply a user who is allowed to perform various Verizon-approved activities on it.
Root- Gaining root access to your phone grants you the control that Verizon had previously held. Rooting quite literally makes you the "Superuser," opening numerous possibilities for improvement, customization, and ruin. Root access is essential to having a fast, fully customized phone.
Root Explorer- This is an app downloadable from the Android Marketplace (Google Play). As it requires Superuser permissions, it is only functional for rooted users. Its abilities far exceed those of standard file management apps. For example, Root Explorer can copy .apk files directly into the system/apps folder in Android. It's a great way to get that obscure Samsung widget reinstalled on your phone after your favorite developer's ROM washed it away and called it bloat.
Samsung Drivers- This is a small piece of downloadable software that will need to be installed on your home computer before it will be able to communicate with your phone (via Odin or adb).
Skin- This is a program that a phone manufacturer creates with the goal of making its phones more user friendly. It is basically an interface that sits on top of the pure Android guts underneath, hence the term "skin." The skin that comes with Samsung phones is called TouchWiz. This is why our phones don't look quite the same as our friends' HTC or Motorola phones, even though they are all using Android. Some people love TouchWiz. Some people hate it. Some custom ROMs are designed to be used with TouchWiz. Others are designed to be rid of it.
SOD - Sleep of Death- This is when your phone goes into standby mode but then goes into a catatonic state somewhere between being asleep and completely powered down. Users report various degrees of SOD. Some ROMs and kernels have been associated with it, as have certain apps, certain radios, and certain SD cards. Experimenting with fringe OC/UV and didle settings are often responsible these days. Generally, a battery pull (or better, Volume Up + Power) will revive the phone. Once a phone experiences a SOD, it seems likely that it will happen again, so a fix will need to be instituted. A modification of OC/UV settings or a return to stock and clean installation of your ROM, kernel, and apps are recommended.
Superuser- A rooted phone will have a new icon in the list of apps called Superuser. This is what distinguishes a rooted phone from a non-rooted phone. There are numerous apps available on the web and Android Marketplace (Google Play) that require "Superuser permission" to do what they do. Common examples of these apps include NS Tools, Titanium Backup, Root Explorer, Voodoo Sound, NS Tools, and Voltage Control. When a rooted user first runs one of these special apps, the app will ask for Superuser permission. Since you are now the Superuser, you get to press the button that says allow or one that says deny.
S Voice- Korean Siri, courtesy of Samsung.
Swype Beta- One of the early perks of rooting, the latest version of Swype is not available to unrooted users because the Fascinate comes with a special pre-installed (and perhaps outdated) version of Swype. Upgrading gives a slicker version of Swype with a more advanced word selection logic. You must follow a few steps to do it correctly:1. Change the input method to the Android keyboard (settings->language & keyboard).2. Uninstall Swype using Titanium Backup.3. Go to the Swype website, give them your email address, and then follow their lead.
.tar- This is the file extension for the files that get flashed via Odin. The file to install CWM, for example, is a .tar file. Another example is the file that returns your phone back to stock.
Titanium Backup- This is an app available on the Android Marketplace (Google Play). It is for rooted users only, and it requires Superuser permissions to operate normally. Its two main functions are:1. Creating backups of your phone (or parts of it) in case you screw it up2. Freezing or uninstalling apps and other stuff you don't want (i.e. debloating)
Thanks button- Once you have created an established account at xda and made a post or two, you will begin to see a button with a little thumbs up sign next to the word "Thanks." This can be found on the lower right corner of someone's post. Pushing this button lets the person who posted know that their work is appreciated. It is considered polite to thank anyone who has helped you, whether or not it was in direct response to your own question. It is always polite to thank the devs whose software you are using. Xda tallies these thanks and gives experienced users a quantifiable measure of their contributions to the community. You will see a thanks meter under other users' names. Helpful people and prolific devs can have hundreds or thousands of thanks.
Troll- This describes a person who attempts to transform a civil forum discussion into a battle of harsh words. They generally lure people into a massive argument by posting inflammatory remarks that are just slightly off topic. They then sit back and laugh to themselves as the argument develops into the nerd equivalent of a bar fight. To feed a troll and make him stronger, just respond to him. To weaken him, report his posts to moderators.
TW - TouchWiz- see "Skin"*
TWRP - TeamWin Recovery Project- This is an alternative to the traditional recovery program. Rather than using the volume rocker, softkeys, and power button to interact with it, a touchscreen interface is used. While it offers some interesting potential, it is still under development in terms of compatibility with the Fascinate and our popular ROM/kernel setups.
UV - Undervolting- This is a means of attempting to reduce battery consumption when using custom kernels. Rooted users can accomplish this through one of several apps, with Voltage Control and NS Tools being common examples. The point of whether UV reduces battery consumption is highly contentious, but there does seem to be a theoretical basis for its validity, as well as a preponderance of anecdotal evidence.
Voltage Control- This is an app available on the Android Marketplace (Google Play). It requires root access (i.e. Superuser permissions). When used with compatible kernels, it allows you to overclock and undervolt your phone.
Voodoo- Project Voodoo is a collaborative software development effort started by dev supercurio back when Galaxy S phones first hit the market. Its goal was to optimize the Galaxy S, bringing it up to its full potential. Voodoo innovations have been used by countless rooted users. Voodoo features can only be used on compatible custom kernels. The project consists of three main branches:1.
Voodoo Color - optimizes screen images/video *Not really available in most modern Fascinate setups, but people still talk about how they miss it.2.
Voodoo Sound - optimizes sound quality for audiophiles *The Voodoo Sound app is available from the Marketplace (Google Play) to control settings.
Wipe x3- This term refers to the act of wiping the slate clean on your phone. It removes all apps you have installed and any data associated with those apps. It will not erase Android, your ROM, your kernel, or anything on your sd card (your photos and videos are on your sd card by default). The Wipe x3 is often done before making major changes to your phone's system. The process is accomplished through a recovery program such as CWM. Here are the 3 commands (hence the "x3"):1. wipe data/factory reset2. wipe cache partition3. wipe dalvik cache*Note, performing a wipe data/factory reset will reportedly wipe the cache partition and the dalvik cache, so steps 2 & 3 may be redundant.
zip- For our purposes, this refers to the file type for files that can be flashed with CWM or other recovery programs.
------------------------------------------------------------------------------------------------
Thanks droidstyle. ?
Sent from my SM-N900V using Tapatalk now Free
The button is now AP on odin, but ya it does work as I have went from root to stock and back a couple times so far
Sent from my SM-N900V
Thank you droidstyle. Coming from the Bionic that used RSD Lite and never owning a Samsung before, I was unsure of the process using Odin. You made it very simple for a newb like me to understand.
thunderbread said:
Thanks droidstyle. ?
Sent from my SM-N900V using Tapatalk now Free
Click to expand...
Click to collapse
Your welcome
sfld said:
The button is now AP on odin, but ya it does work as I have went from root to stock and back a couple times so far
Sent from my SM-N900V
Click to expand...
Click to collapse
The older versions of Odin should still work which is why I put AP/PDA in the instructions.
R-1 Rider said:
Thank you droidstyle. Coming from the Bionic that used RSD Lite and never owning a Samsung before, I was unsure of the process using Odin. You made it very simple for a newb like me to understand.
Click to expand...
Click to collapse
This exactly why I posted these instructions, glad it helped you. Take note more will be added to this guide as things get rolling for the N3. It most likely will be a All in One guide with Root, Rom, Recovery,and Return to Stock instructions at some point.
droidstyle said:
Please note I do not have the N3 yet, but returning to stock has been very similar on all three of my previous samsung devices. So if you notice something slightly different just let me know and I will change it.
For instance: when you three finger combo to access download mode does a yellow triangle appear?
These are the type of little differences you might notice from the instructions.
Click to expand...
Click to collapse
Are you getting the developer edition?
droidrev71 said:
Are you getting the developer edition?
Click to expand...
Click to collapse
Yep.
Thanks droidstyle it worked
Mods, please sticky this or move it to Original Section,
:good::good:
Knox?
Does this trip the Knox flag? Might want to update the OP either way.:good:6
Thank you for this!
Sent from my SM-N900V using xda app-developers app
RainingPanic said:
Does this trip the Knox flag? Might want to update the OP either way.:good:6
Click to expand...
Click to collapse
Not trying to be rude, but how would flashing back to stock trip the Knox flag?
bajasur said:
Thank you for this!
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
you are welcome good sir!! I appreciate your contributions as well!!
droidstyle said:
How would flashing back to stock trip the Knox flag?
Click to expand...
Click to collapse
would flashing back to stock reset tripped KNOX flags?
tgamer said:
would flashing back to stock reset tripped KNOX flags?
Click to expand...
Click to collapse
I wish I knew, but I have a feeling No. It would be the same principal as using Chainfire's Triangle away to erase the flash counter on prior devices. Flashing back to stock does not erase it on its own, so I wouldn't expect it to in this case either. This is why I am buying a Dev Edition, Tired of worrying about that stuff.
droidstyle said:
Not trying to be rude, but how would flashing back to stock trip the Knox flag?
Click to expand...
Click to collapse
Not sure... that's why I asked the question. Why does Chain fire's Autoroot trip the Knox flag but Designgear's method does not? I haven't flashed back to stock using these files, but surely someone has and could answer the question. It probably doesn't, but I was just thinking it might be useful if it was stated in the OP to help reassure inexperienced members like me. :good:
RainingPanic said:
Not sure... that's why I asked the question. Why does Chain fire's Autoroot trip the Knox flag but Designgear's method does not? I haven't flashed back to stock using these files, but surely someone has and could answer the question. It probably doesn't, but I was just thinking it might be useful if it was stated in the OP to help reassure inexperienced members like me. :good:
Click to expand...
Click to collapse
When you get a chance read the entire OP of the Root La Vega thread...its all explained there. In short no flashing back to stock does not trip the knox flag.
If I recall correctly, resetting Knox flag after you've already tripped it is useless. I read somewhere that Knox actually communicates with a Samsung/Verizon server that takes your Knox status. Aka once you've tripped it, they already have your void status. (That is, once you've booted and gave it a chance to communicate with servers)
But we don't care about warranties since we gave that up rooting our phones now do we.....
And I'm with droidstyle, flashing completely stock images should never trip anything bad. Unless you did something severely wrong.
Sent from my Galaxy Note 3 using Tapatalk 4
@droidstyle Thanks for this!
sfld said:
The button is now AP on odin, but ya it does work as I have went from root to stock and back a couple times so far
Sent from my SM-N900V
Click to expand...
Click to collapse
It doesn't trip the 0x1?