Develop Bugs

My phone sometimes crashes, how can I rule out a software issue?

Hello everyone,
First of all my problem. Since about 2 weeks I started getting random crashes. The phone is unresponsive and the screen goes from really bright to a greenish/grey color (hard to explain). I googled but I didn't find an answer. If anyone here knows the problem that'd be great but I doubt it since there are so many this that could cause this. So now my question is, how can I be certain it's not an software issue? Further info: My phone is rooted, and I didn't change the ROM. However, I don't actually have root permissions and when I open SuperSU it asks me to update the binary which always fails. I tried to Root it again with the Galaxy Toolkit and it says it's already rooted. Also, Under the google logo is a unlocked lock sign.
Thanks

I would recommend you to try some custom stable ROM, based on 4.1.2. CM, AOKP are among top ones.
better make a backup using recovery, and flash a new ROM. It will give you a fresh start with SU too.
If you dont like using a custom ROM, restore an earlier backup if you already have..
marcusabu said:
Hello everyone,
First of all my problem. Since about 2 weeks I started getting random crashes. The phone is unresponsive and the screen goes from really bright to a greenish/grey color (hard to explain). I googled but I didn't find an answer. If anyone here knows the problem that'd be great but I doubt it since there are so many this that could cause this. So now my question is, how can I be certain it's not an software issue? Further info: My phone is rooted, and I didn't change the ROM. However, I don't actually have root permissions and when I open SuperSU it asks me to update the binary which always fails. I tried to Root it again with the Galaxy Toolkit and it says it's already rooted. Also, Under the google logo is a unlocked lock sign.
Thanks
Click to expand...
Click to collapse

ahsanali.pk said:
I would recommend you to try some custom stable ROM, based on 4.1.2. CM, AOKP are among top ones.
better make a backup using recovery, and flash a new ROM. It will give you a fresh start with SU too.
If you dont like using a custom ROM, restore an earlier backup if you already have..
Click to expand...
Click to collapse
My only expercience with custom roms got me into a boot loop, so I don't prefere that. I actually want a "out-of-the-box" phone without any modifications. Therefore I tried a factory reset but that keeps the root and unlock.

marcusabu said:
My only expercience with custom roms got me into a boot loop, so I don't prefere that. I actually want a "out-of-the-box" phone without any modifications. Therefore I tried a factory reset but that keeps the root and unlock.
Click to expand...
Click to collapse
ok, if you want to get the total old look, relock the bootloader, and install official GNex image that comes straight from Google. Hope this sorts the issue out.
Yes, Custom ROMs are a bit time taking to setup in the start, but thats the whole point - a lot of options. I flashed alot of ROMs and luckily, I have had no boot issue still. I think following the proper instructions(which are simply wiping and formatting data, cache, and dalvik) are easily gonna keep the boot loops away.

You can rule out a sw issue by starting fresh.
http://forum.xda-developers.com/showthread.php?t=1626895
Sent from my i9250

[Q] CyanogenMod Installer Update Issues

Hey all,
I apologize if there is a thread for this already. I have the Sprint GS3 that I made the terrible, terrible mistake of upgrading to the stock 4.3 to give it a try and see if I like it.
After some scary moments trying to go back to the beloved CyanogenMod and bricking the device, I found I could install Cyanogenmod using their self-installer after restoring the phone to stock in Kies.
I'm running Cyanogenmod now, but there is an update available and when I try to let it update, it reboots into recovery, gives the sad broken android graphic, and reboots. I've not been able to install anything ROM related since.
Is Knox preventing the update, and is there a workaround to get the update to install without wiping the device back to stock?

emike09 said:
Hey all,
I apologize if there is a thread for this already. I have the Sprint GS3 that I made the terrible, terrible mistake of upgrading to the stock 4.3 to give it a try and see if I like it.
After some scary moments trying to go back to the beloved CyanogenMod and bricking the device, I found I could install Cyanogenmod using their self-installer after restoring the phone to stock in Kies.
I'm running Cyanogenmod now, but there is an update available and when I try to let it update, it reboots into recovery, gives the sad broken android graphic, and reboots. I've not been able to install anything ROM related since.
Is Knox preventing the update, and is there a workaround to get the update to install without wiping the device back to stock?
Click to expand...
Click to collapse
I will give you my two cents. First, rooting and installing custom ROM's should not be done using magical wonderful "one click" processes or apps that will do it for you. The Cyanogen Installer was a huge disservice to the rooted community in my opinion. Users need to get their hands dirty when rooting, so that they know how to work through problems forwards and backwards. That being said, I would highly recommend following this procedure to make sure your phone is rooted properly and running the correct recovery (Philz Touch, which is unbelievably awesome); my friend @goku2778 did a very nice job putting this tutorial together:
http://forum.xda-developers.com/showthread.php?t=2596697
After that, just download the ROM (or ROM's, I like to run various ones at any given time) from the proper sources, and flash them yourself.

I'm against one-click stuff myself. I've been rooting and running custom roms since my original Evo 4g.
If bricking my device after trying to roll back to a custom rom after Knox did it's business, and then recovering back isn't getting my hands dirty, then I don't know what is. I've spent plenty of time in adb. This issue though has me boggled. Why can the installer put a custom rom on when attempts to flash a custom rom (usually run nightlies) brick the device?
Thanks for the link, I'm taking a look into it now.

emike09 said:
I'm against one-click stuff myself. I've been rooting and running custom roms since my original Evo 4g.
If bricking my device after trying to roll back to a custom rom after Knox did it's business, and then recovering back isn't getting my hands dirty, then I don't know what is. I've spent plenty of time in adb. This issue though has me boggled. Why can the installer put a custom rom on when attempts to flash a custom rom (usually run nightlies) brick the device?
Thanks for the link, I'm taking a look into it now.
Click to expand...
Click to collapse
Didn't mean to imply that you weren't getting your hands dirty in general, just the way I word that rant every time I give it! My understanding is that there are compatibility issues between the CM installer and Knox, so yes, that is probably the basis of your problem. The combination of Philz Touch recovery and SuperSU that @goku2778 uses in his tutorial should solve your problems, it is the combination I have been recommending to VM and Boost users on Android Forums for a while now, with great success.

Mr. Struck said:
Didn't mean to imply that you weren't getting your hands dirty in general, just the way I word that rant every time I give it! My understanding is that there are compatibility issues between the CM installer and Knox, so yes, that is probably the basis of your problem. The combination of Philz Touch recovery and SuperSU that @goku2778 uses in his tutorial should solve your problems, it is the combination I have been recommending to VM and Boost users on Android Forums for a while now, with great success.
Click to expand...
Click to collapse
If memory serves there is a zip out there somewhere that flashes Knox apps away. Furthermore if it's a Boost or VM device you have to edit the updater script to make a Sprint ROM flash successfully.

Deucalion29710 said:
If memory serves there is a zip out there somewhere that flashes Knox apps away. Furthermore if it's a Boost or VM device you have to edit the updater script to make a Sprint ROM flash successfully.
Click to expand...
Click to collapse
The DeSamsungnizer zip is part of the tutorial by @goku2778, but keep in mind that this just takes care of the Knox apps, the actual bootloader is never ever going away unfortunately. And yes, for any users of VM or Boost who are reading this, there is extra work involved once the custom recovery has been installed and root has been successfully achieved.

Galaxy s3 on Virgin Mobile running cm11
I recently upgraded my s2 which was running cyanogenmod 11. I rooted and flashed everything myself with no difficulty. But after I switched that phone to an s3 I have had a ton of issues. My s3 was for Virgin Mobile (sgh-I747M) and nothing supported it. I was able to root and install clockworkmod with a little bit of difficulty. It wasn't until I tried installing cyanogenmod that it got really tough. Flashing would fail and at that point I didn't have an os so I thought I downloaded stock but was wrong when I hard bricked my phone. Anyways to the point. I ended up using the cyanogenmod installer which worked perfectly fine but now I can't update or download any nightlys. I'm not sure if it is because cyanogen had to install a custom kernel or not. When I go into system updates it says "your system is up to date. There is only one button that just checks for updates. Does anyone know how to fix this and allow me to install nightlys?
- Eric

Will CM installer work on S3-i9300(Int) version with 4.3 already installed?
Hi,
I am using the International version of SGS3- GT i9300. I dont know any of the process of rooting or installing a new version of android. But recently i have come across the cyangonmod installer app which i heard does all the work for us. I want to ask this doubt is that will the installation cause any problem if my S3 is already updated to 4.3 version? I am hearing people saying the KNOX might cause error. Should i wait for the CM 11 stable version or just give it a try ?
Thanks.

ericandbailey said:
I recently upgraded my s2 which was running cyanogenmod 11. I rooted and flashed everything myself with no difficulty. But after I switched that phone to an s3 I have had a ton of issues. My s3 was for Virgin Mobile (sgh-I747M) and nothing supported it. I was able to root and install clockworkmod with a little bit of difficulty. It wasn't until I tried installing cyanogenmod that it got really tough. Flashing would fail and at that point I didn't have an os so I thought I downloaded stock but was wrong when I hard bricked my phone. Anyways to the point. I ended up using the cyanogenmod installer which worked perfectly fine but now I can't update or download any nightlys. I'm not sure if it is because cyanogen had to install a custom kernel or not. When I go into system updates it says "your system is up to date. There is only one button that just checks for updates. Does anyone know how to fix this and allow me to install nightlys?
- Eric
Click to expand...
Click to collapse
did you figure out how to get nightly updates, from cyanogenmod installer ? I want to try the cyanogen installer to get cm 11 on my gs2 and gs3 (my specific devices are not on the cyanogenmod devices list, so i'm hesitant ) .. please respond .. anyone who can help ..

[Q] N5110 no rom or backup

So I have rooted and installed roms on several devices in the past but typically using how-to guides and such rather than just knowing how to do it. I got a little too confident with my note and decided to go ahead with a rom (Carbon) that didn't install (error 7). I, of course, deleted my cache and data and did a very dumb thing by not backing up before doing so. Yes, I know.
I am able to use Odin to switch from the stock boot screen (is it a bootloader just out of curiosity?) and cwm. I believe that if I could get a stock version of the N5110 Android rom I could switch from CWM to stock boot, and then sideload the stock rom.
As a sidenote, I am able to sideload with the stock boot however when using CWM, adb doesn't detect the device. Odin functions with both.
Just based on my past experience this seems salvagable to me. I have searched extensively for information but cannot find my specific situation with my specific hardware (gt-n5110) and, as always, the devil is in the details. I am also unable to find the stock N5110 firmware online except through Terafile which will not allow access without giving them $.
Can I utilize the fact that Odin functions in both settings (CWM and stock)?
I don't need to be chastised for how dumb not backing up is...lesson learned believe me.
Hope I haven't exposed my ignorance. Any constructive input would be appreciated.
Edit: I tried http://forum.xda-developers.com/showthread.php?t=2450005 and it said the signature was incorrect

Rom for note 8.0

Rom for note 8.0
jallenusn said:
So I have rooted and installed roms on several devices in the past but typically using how-to guides and such rather than just knowing how to do it. I got a little too confident with my note and decided to go ahead with a rom (Carbon) that didn't install (error 7). I, of course, deleted my cache and data and did a very dumb thing by not backing up before doing so. Yes, I know.
I am able to use Odin to switch from the stock boot screen (is it a bootloader just out of curiosity?) and cwm. I believe that if I could get a stock version of the N5110 Android rom I could switch from CWM to stock boot, and then sideload the stock rom.
As a sidenote, I am able to sideload with the stock boot however when using CWM, adb doesn't detect the device. Odin functions with both.
Just based on my past experience this seems salvagable to me. I have searched extensively for information but cannot find my specific situation with my specific hardware (gt-n5110) and, as always, the devil is in the details. I am also unable to find the stock N5110 firmware online except through Terafile which will not allow access without giving them $.
Can I utilize the fact that Odin functions in both settings (CWM and stock)?
I don't need to be chastised for how dumb not backing up is...lesson learned believe me.
Hope I haven't exposed my ignorance. Any constructive input would be appreciated.
Edit: I tried http://forum.xda-developers.com/showthread.php?t=2450005 and it said the signature was incorrect
Click to expand...
Click to collapse
Well friend, do never install a custom rom without making a backup
Here you can find the stock 4.2.2 for your Note 8:https://drive.google.com/file/d/0B9QvmNs9dpD-M21DaF95NWdNUW8/edit?usp=sharing
And also, I use to install custom roms and I always use this recovery:http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n5110/philz_touch_6.12.8-n5110.tar.md5

I really appreciate the upload. Whenever I sideload I am getting this error:
E: Signature Verification Failed
Any additional information I can provide?
Edit: Disregard. I installed phils touch wiz and now i'm attempting to sideload again. Keep getting a protocol fault (no status). Just a total shot in the dark but is this due to the pc-tablet connection dropping?
Edit 2: Dude. You are the man. Installed the touch wiz which, imo, far superior to CWM considering it allowed me sideload access and cwm didn't. Then turned off signature verification. Piece of cake.
Thanks so much.

jallenusn said:
I really appreciate the upload. Whenever I sideload I am getting this error:
E: Signature Verification Failed
Any additional information I can provide?
Edit: Disregard. I installed phils touch wiz and now i'm attempting to sideload again. Keep getting a protocol fault (no status). Just a total shot in the dark but is this due to the pc-tablet connection dropping?
Edit 2: Dude. You are the man. Installed the touch wiz which, imo, far superior to CWM considering it allowed me sideload access and cwm didn't. Then turned off signature verification. Piece of cake.
Thanks so much.
Click to expand...
Click to collapse
You're Welcome friend :laugh:
and by the way, next time you install a custom rom, make a backup first, you wont regret it

[Q] CyanogenMod not getiing installed. SuperSU Crashing.

Hello All,
I am a beginner to all this stuff. I wanted to root my phone after seeing OnePlus One running on CyanogenMod. So, first I tried to directly install the Mod using the softwares downloaded from Cyanogen's website. But the software gave the error "Unsupported Firmware". Then I researched a bit on manually installing the mod. I followed the instructions.
- First I rooted my phone with Odin 3.09v
- Installed ROM Manger on my phone (Meanwhile the SuperSU app kept on crashing)
- Somehow I managed to install ClockworkMod (What I did was downloaded SuperSU apk, installed it again. It started working and then, not losing the chance I installed ClockworkMod).
- Then I tried to install CyanogenMod through ROM Manager
- My phone re-booted and then gave a error "Can't install package on incompatible data".
- I'm having the latest snapshot version on CyanogenMod.
- Then I left the things as it is. No rooting, unrooting, etc.
- So, now I tried to take backup of my current ROM, in case something happens at least I'll be having something with me to recover
- I used ROM Manager to take backup. But it gave the error "Can't create the image"
So, now I'm stuck between middle of nowhere. Please help me out to reach to some point.

svikramajit said:
Hello All,
I am a beginner to all this stuff. I wanted to root my phone after seeing OnePlus One running on CyanogenMod. So, first I tried to directly install the Mod using the softwares downloaded from Cyanogen's website. But the software gave the error "Unsupported Firmware". Then I researched a bit on manually installing the mod. I followed the instructions.
- First I rooted my phone with Odin 3.09v
- Installed ROM Manger on my phone (Meanwhile the SuperSU app kept on crashing)
- Somehow I managed to install ClockworkMod (What I did was downloaded SuperSU apk, installed it again. It started working and then, not losing the chance I installed ClockworkMod).
- Then I tried to install CyanogenMod through ROM Manager
- My phone re-booted and then gave a error "Can't install package on incompatible data".
- I'm having the latest snapshot version on CyanogenMod.
- Then I left the things as it is. No rooting, unrooting, etc.
- So, now I tried to take backup of my current ROM, in case something happens at least I'll be having something with me to recover
- I used ROM Manager to take backup. But it gave the error "Can't create the image"
So, now I'm stuck between middle of nowhere. Please help me out to reach to some point.
Click to expand...
Click to collapse
Ok, first I think your SuperSu is not working properly. Open the Supersu app to see if it needs to update binaries. If it continues to crash, go into recovery manually (not using rom manager) and flash the latest SuperSu. Wipe Cache, go to advanced and Wipe Dalvik. Reboot. Your phone will say "android is upgrading" for a bit. Once it's booted up, go back into the supersu app and see if it needs to update binaries, if so- let it update, if not- move on. Here's a link to download SuperSu 2.02
Go back into recovery manually and select backup and restore-> backup to sdcard (or sdcard1, external sd, is my preference) This will start the backup process.
Once that is done, you need to find the CyanogenMod file specific to your phone, then you can enter recovery and flash it.
If you have trouble entering recovery, you can flash a new one via recovery or with odin.

Hello absinthesummer,
I followed every instruction you told. Now I'm done till creating backup. The problem now I'm facing is this 'Status 7' error. It says "Can't install package on incompatible data.....". Now what to do?

Status 7 is a very specific error. It means your recovery is out of date. Get the absolute newest you can find and try again. This is good news though, you've got progress!
---------- Post added at 11:48 AM ---------- Previous post was at 11:46 AM ----------
Edit: flash the latest recovery you can find via Odin. You probably won't be able to do it in recovery while you're getting the status 7 error.

absinthesummer said:
Status 7 is a very specific error. It means your recovery is out of date. Get the absolute newest you can find and try again. This is good news though, you've got progress!
---------- Post added at 11:48 AM ---------- Previous post was at 11:46 AM ----------
Edit: flash the latest recovery you can find via Odin. You probably won't be able to do it in recovery while you're getting the status 7 error.
Click to expand...
Click to collapse
No, I've got the latest recovery. But I figured out the problem. It was with the package I downloaded. The CM 11 M9 version was giving errors. I researched and tried few fixes, but still it didn't work.
The fixes I tried :-
1. Deleting some coding lines from the updater-script file. But this fix gave the status 6 error.
2. Changing the updater-script file format to UNIX format. Then again it gave the status 7 error.
So, what I did, when I had no more brain to fix it, I downloaded the CM 11 M6 version and tried installing it. And VOILA! It worked. Then I updated it to M9 version through phone. Now it's working. Though it has some bugs. And some features are missing too that I wanted badly.

svikramajit said:
No, I've got the latest recovery. But I figured out the problem. It was with the package I downloaded. The CM 11 M9 version was giving errors. I researched and tried few fixes, but still it didn't work.
The fixes I tried :-
1. Deleting some coding lines from the updater-script file. But this fix gave the status 6 error.
2. Changing the updater-script file format to UNIX format. Then again it gave the status 7 error.
So, what I did, when I had no more brain to fix it, I downloaded the CM 11 M6 version and tried installing it. And VOILA! It worked. Then I updated it to M9 version through phone. Now it's working. Though it has some bugs. And some features are missing too that I wanted badly.
Click to expand...
Click to collapse
Awesome! I'm glad you got it working. You can also try comparing the two files to see what's different, or maybe swap the updater script. Maybe you'll be able to get the one you wanted working with a little modification

absinthesummer said:
Awesome! I'm glad you got it working. You can also try comparing the two files to see what's different, or maybe swap the updater script. Maybe you'll be able to get the one you wanted working with a little modification
Click to expand...
Click to collapse
Thanks to you. You too helped me in working it out!
But, I have some more questions
Question 1 : If I flash stock ROM on my rooted phone, will I receive the new updates? If yes, will I be able to install them via Kies on my phone without getting into any trouble?
Question 2 : If I install stock ROM of any other phone, say Galaxy S5, will it work on my phone properly without any problems? If yes, will I receive the updates for that too and able to install them via Kies? If no, is there any way to install it? Cause I have seen people using S5 ROM on Note 2.

First question the answer is yes. As long as you have the stock recovery and stock kernel (along with the stock rom) you will receive ota updates. You can use ota root keeper (an app) to keep root during an ota update. There are many people who choose to stay fully stock but root to get rid of bloatware & stuff. However, if you want to get ota, I recommend freezing the bloatware instead of uninstalling, because an ota usually replaces old bloatware with new bloatware and can sometimes abort the ota if those apps are missing... but keep on mind this is not always the case, only certain devices.
Second question, no you cannot. Roms from other devices have to be ported to be compatible. But if you look in the development forums, you can find many roms that are basically stock but have specific features from other roms, along with the system ui (ie S5, note 3, & so forth). These rom devs have ported either parts/features or full on roms to be compatible on our device. They are excellent! I recommend reading up them and if you see some you like, try them out!

absinthesummer said:
First question the answer is yes. As long as you have the stock recovery and stock kernel (along with the stock rom) you will receive ota updates. You can use ota root keeper (an app) to keep root during an ota update. There are many people who choose to stay fully stock but root to get rid of bloatware & stuff. However, if you want to get ota, I recommend freezing the bloatware instead of uninstalling, because an ota usually replaces old bloatware with new bloatware and can sometimes abort the ota if those apps are missing... but keep on mind this is not always the case, only certain devices.
Second question, no you cannot. Roms from other devices have to be ported to be compatible. But if you look in the development forums, you can find many roms that are basically stock but have specific features from other roms, along with the system ui (ie S5, note 3, & so forth). These rom devs have ported either parts/features or full on roms to be compatible on our device. They are excellent! I recommend reading up them and if you see some you like, try them out!
Click to expand...
Click to collapse
- Stock Recovery
- Stock Kernel
- OTA Root Keeper
- Bloatware
Well, to be honest, just right now I learned these new terms but know nothing about them. Can you please give me a brief description for these four terms so that when I do advanced search on them, I'd have a idea in my mind about what these are. It will make it easy for me to understand the advance things.
And I'm looking for S5 ROM for my phone. Let's see what I get.

One more question. I made a backup of my rooted stock ROM via latest ClockwordMod, manually. Now, if I reset the binary counter using Triangle Away and then wipe Cache and Dalvik and then flash my stock ROM which is located on my memory card and then after flashing I use SuperSU to unroot and then a factory reset (I don't know the method of factory reseting cause I'm confused. Whether to do it manually, like going into recovery mode or just from the phone settings. So please tell me this also.), will my phone be unrooted totally?
And sorry for bugging you so much. I hate to do that, but I don't want to take risk with my phone. So I am just collecting information. I hope so many queries are not a problem for you.

Ok...
You already know what a rom is. A kernel is a lower-level base. It controls the hardware. So when you do something on the interface, in the rom, it tells the hardware how to react. (Ie if you're playing music it tells which speakers to play and how loudly). The kernel controls almost everything you can't see, it relates to performance. Most stock kernels can be limiting as they underclock the cpu by a certain percentage. Because of this, people seek out custom kernels to max out their device's potential. Louder speakers, faster cpu, better graphics, etc. This is all stuff the kernel can optimize... but because you can change so many factors there is a risk of instability if you push your device too hard (max performance) or limit it too much (max battery saving).
Recovery is exactly what it sounds like. When you boot your device the very first screen that pops up is the bootloader. It's giving you time to boot in 3 different modes. The first mode, by doing nothing, is a normal boot into the rom/OS. The second mode, which you get to by one button combination, takes you to recovery. The stock recovery is very limited. It gives you the option to factory restore, wipe cache, update, or boot normally. Stock recovery only exists for emergencies, if your phone fails to boot normally. We have custom recoveries so we can do more stuff, flash custom roms and tinker with things. The third mode is download mode/Odin mode. This is the bootloader interface itself. It's the last resort for recovery if your recovery has been damaged or corrupted. It allows you to connect to Odin or kies and perform an emergency recovery of the device. If you damage your bootloader, your device is completely bricked.
So the order of operation is this:
Lowest level- bootloader
Second level- recovery
Third level- kernel
Fourth level- rom
Bloatware is all the pre-installed apps that your carrier adds to your phone. Most people don't use it, don't like it, and don't want it. That why we root. Without root we basically are just guest users of the device. With root we become the administrators of the device. Until you root, your carrier has admin rights over your phone (to use windows terms).
When you receive an ota update, your carrier can make it to where the update won't proceed if their pre-installed apps have been removed (although this isn't always the case). Additionally, the update package itself checks the integrity of the device. It checks recovery, kernel, and rom. If any have been altered, it will not proceed because it could cause conflict and potentially brick your device. That's why those things have to be stock.
Ota root keeper is simply an app that backs up your superuser rights before an update and restores them after its done.
You should be able to find plenty of roms with S5 features. I'm using one that makes my device fully like an S5 (my device even thinks it is an S5 and every app identifies it as such) I can think of at least 2 others as well. There's plenty to choose from, and if you see a rom you like but it's mudding a particular feature, you can probably find that feature as a stand-alone installation in the forum's themes & apps section. Just about every feature of S5, S4, and note 3 has been ported to this device, so look around!
Also, for future reference, if someone helps you on the forum, hit the thanks button instead of saying it. I don't mind either way, but some people get annoyed and will stop helping them if they don't hit that button lol. It's silly, but it's part of "forum decorum"
---------- Post added at 12:54 AM ---------- Previous post was at 12:44 AM ----------
svikramajit said:
One more question. I made a backup of my rooted stock ROM via latest ClockwordMod, manually. Now, if I reset the binary counter using Triangle Away and then wipe Cache and Dalvik and then flash my stock ROM which is located on my memory card and then after flashing I use SuperSU to unroot and then a factory reset (I don't know the method of factory reseting cause I'm confused. Whether to do it manually, like going into recovery mode or just from the phone settings. So please tell me this also.), will my phone be unrooted totally?
And sorry for bugging you so much. I hate to do that, but I don't want to take risk with my phone. So I am just collecting information. I hope so many queries are not a problem for you.
Click to expand...
Click to collapse
You're fine, I don't mind answering your questions. Yes, you can unroot fully in the way you just mentioned but you don't even have to go through all the trouble of factory reset. Just unroot in the app. The app can be uninstalled afterwards via the play store.
You can factory reset either way, the same commands are given no matter which way you go about it. But it can be more efficient to do it from recovery because when you do it from the rom it has to create a wipe script for when it reboots, and it has to shut down the rom first. If you do it from recovery it doesn't have to anything, the rom isn't running and it can execute the wipe command immediately. (The wipe command is wipe /data /cache etc)

Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?

svikramajit said:
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
Click to expand...
Click to collapse
If you damage the bootloader it's a hard brick and you would have to send it in for jtag services (this is a low level emmc chip flash service) The bootloader won't get damaged unless you do something to corrupt it. If you ever feel the need to flash a new bootloader, do it via Odin, never recovery! If you remember that you should be fine.

svikramajit said:
Thanks again for all that great info!
Questions : Is there no way to fix the Bootloader if it gets damaged by chance? And which S5 ROM are you using?
Click to expand...
Click to collapse
I meant to tell you I'm using DN3 rom. It has an aroma installer that lets you choose whether you want an S5 ui, a note 3 ui or a mixed ui. Choosing S5 ui & S5 build prop allows your device to work with S5 apps & it looks just like an S5. It's not the only rom out there, but it's beautiful, fast, and stable & the team works hard on it.

absinthesummer said:
I meant to tell you I'm using DN3 rom. It has an aroma installer that lets you choose whether you want an S5 ui, a note 3 ui or a mixed ui. Choosing S5 ui & S5 build prop allows your device to work with S5 apps & it looks just like an S5. It's not the only rom out there, but it's beautiful, fast, and stable & the team works hard on it.
Click to expand...
Click to collapse
Hey absinthesummer!
I tried to unroot my phone with the method I told you. But in the restore option, I am stuck at 'Checking MD5 Sums..'. What to do now?

MD5 checking takes forever! You have to wait it out. Most recoveries offer a way to turn it off. You shouldn't have to factory reset though, just click unroot in the super su app and then uninstall the app from the play store.

absinthesummer said:
MD5 checking takes forever! You have to wait it out. Most recoveries offer a way to turn it off. You shouldn't have to factory reset though, just click unroot in the super su app and then uninstall the app from the play store.
Click to expand...
Click to collapse
I waited and the system was restored. But I got an error on 'Restoring Data'. I rebooted the phone and now it's showing glowing Samsung logo from like 3-4 minutes.

I've seen that before. Can you get back into recovery? You may have to flash stock in Odin, flash recovery and then do the Restore again. Data got messed up.

absinthesummer said:
I've seen that before. Can you get back into recovery? You may have to flash stock in Odin, flash recovery and then do the Restore again. Data got messed up.
Click to expand...
Click to collapse
I'll try removing the battery now. Let's see what happens.

Ok if you can get into recovery, do a fresh flash and then try to restore again. And see if it offers a way to turn off MD5 checking. That's why I use philz or twrp, they offer that and move much faster through MD5 check by default.
---------- Post added at 11:13 AM ---------- Previous post was at 11:12 AM ----------
If you still fail on data, flash stock in Odin, flash custom recovery, then you should be able to enter recovery and have a successful restore.

No longer able to boot my Note 2 into recovery mode

1. I started with fully working Samsung Galaxy Note 2 GT-N7100 (Rooted)
2. I'm a newbie to flashing ROM, and read numerous articles to build awareness (and have never used a forum before - so please be gentle!)
3. Installed ClockworkMod Recovery using "ROM Manager"
4. Flashed Slim6 (Slim-6.0.1.alpha.0.1-UNOFFICIAL-20160522-1030) ROM, then Gapps, then re-booted and all OK (Note2 seemed to work fine)
5. Kernel is now3.0.101-Haxynox
6. Spotted (and surprised) that Note 2 no longer rooted (and in particular, want to use Titanium Backup)
7. So, flashed CWM6-root-note2.tar using ODIN, resulting in "Pass"
8. Note2 still not Rooted, and suspect that I should have flashed SuperSu after Slim6 ROM and before Gapps
9. So, tried to reboot to ClockworkMod reccovery using "ROM Manager" but hangs. Tried using VOL+ and HOME and POWER (many times, and for different intervals) but see Samsung logo followed by some "stripes" on the screen (rather like the horizontal hold needs to be adjusted for those that are old enough to remember such things!), but it will not boot into recovery mode.
10. In addition, Odin no longer appears to see the Note2
11. Note2 will boot conventionally, but I'm extremely keen not to have to live without rooting and flashing capability
12. I've searched hard for hints for this particular issue, but would really appreciate some advice, at least so that I don't make my beautiful Note2 any worse (and hope I've not missed any posts that I should have spotted!).
13. Please let me know if I've missed any key information.
Thanks in advance.

Flash the tar version of TWRP for your phone using Odin. You can root by flashing supersu from TWRP.
CWM is very outdated and cannot be used to flash current custom ROMSs.

Many thanks, I've moved over to TWRP and it seems much better.
I also tried to find a more "suitable" (reliable) ROM and chose Resolution Remix, especially as services kept stopping on Slim6.
So now I can get to recovery mode, but still I have issues. Mainly...
a) I've so far failed to flash a compatible Gapps file
b) I've flashed supersu and busybox (Root_SuperSU.0.98-Busybox.1.20.2-signed.zip) but root is still not available. Sometimes I see a "Grant" prompt but it hangs for ages when I grant. The SuperSU app can be seen, but is not responsive. Titanium Backup responds eventually to confirm that Root is not available.
c) Downloading from the Playstore is problematic (sometime very slow to download, usually extremely slow to install - go for a walk type of slow!)
d) Typically the pre-installed applications "stop" shortly/immediately after trying to start them (for example, "Browser", "Clock",...), but then appear after "OK"ing the Close infor box
e) Is my choice of ROM reasonable? And/or is there a ROM which has ROOT "baked in"? (Or, should I go back to JellyBean as being more suitable for a Note2?)
f) Is there some "fine tuning" to the flash process that I need to learn about?
Any hints/tips would be welcome, and many thanks for your initial suggestion to move to TWRP

Is the ROM pre-rooted? If yes, don't flash supersu.
You performed a full wipe, including data, before flashing the ROM?
Phone is running these latest bootloader and modem?
Various versions of gapps are here and flash there version that matches your ROM and processor: http://opengapps.org

Many thanks for your further questions/prompts...
a) Yes, I believe I had done a full wipe before flashing, but haven't touched bootloader and modem so they may well be "old"
b) More reading suggests that Cyanogenmod 13 is a very popular ROM, so flashed this with TWRP
c) Found that with this ROM there were no issues when flahsing openGapps
d) Eventually discovered/realised that CM13 is pre-rooted (but has to be enabled in Settings) and that flashing supersu was causing problems
So, with the benefit of hindsight, if I'd used TWRP/CM13/OpenGapps without flashing supersu, it would have been straightforward! I've certainly learned a lot and you supporting questions have led me to what seems to be a nice, stable implementation of Marshmallow - thanks again.
I'm still looking for a quick/easy way to take a screenshot (just used a palm-swipe before), and a free "real" FM radio, but pretty much everything else works.
Great!!!

Glad you got the phone working on CM. We're all here to help and learn from each other.
Last time I looked, which was a while ago, there was no custom AOSP or CM rom that supported radio functions. If you want the FM radio, look into custom ROMs based on a stock Samsung kernel.