How to reset flash counter after unrooting - AT&T Samsung Galaxy Note II

If I want to unroot, I'm thinking of just flashing the newly released firmware on Sammobile for Rogers. This will take away root, BUT flash counter will still remain at 1 or 2. One way to reset flash counter is with TriangleAway, which I've done many times before, but in order to do that, one needs to be rooted which is what I'm trying to get rid of. If I remember reading correctly somewhere, the USB jig which I got for my S2 will not work on the Note 2 (unless I'm wrong). So in conclusion, after I remove root, how can I reset the counter? I'm doing this so I can regain my ability to receive OTA and gain some knowledge
Also, I notice that when the phone boots up, the "Samsung Galaxy Note II" logo is not present. It just goes from "Samsung" to the animation and to OS. Is this normal on Rogers or does this have anything to do with the root?
Many thanks for your help guys!

http://forum.xda-developers.com/showthread.php?t=1992303
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

Related

Rooting from stock MC3 firmware

I am planning on rooting my friend's stock i317 running the MC3 stock firmware. He recently got a carrier replacement i317 due to a hardware issue but I had also previously rooted his other i317 and installed a CM10.2 nightly ROM. Upon using the same method of rooting his first phone on the new one, I ended up soft bricking his second phone. I basically used ODIN to flash a few different recoveries but when I would boot to recovery each time then the Galaxy Note II logo would start flickering for a few seconds and then the screen would go blank. I tried using ODIN to restore to JL2 and upon successfully restoring, I couldn't get past the boot animation. I told my friend to replace the phone again as I couldn't even get the phone to boot up successfully no matter what I tried doing to fix it. Maybe I had to find and ODIN the MC3 firmware to successfully boot the device so please let me know what I did wrong which prevented the device from booting successfully.
I don't know whether there was recently a major AT&T firmware update that changed the security on the device which prevented previous methods of root from working so please update me on any changes. My friend just got a new i317 today and I would like to root it successfully as the AT&T warranty center was nice enough to replace his phone but had to void his warranty due to looking at the flash counter. I just found an app called Framaroot which looks much simpler to use
http://forum.xda-developers.com/showthread.php?t=2130276
I have been rooting and flashing ROMs on various Android devices for a long time now so I am up for using any root methods no matter how advanced they may be including using ADB. I did not have enough time to research about the i317 so it was my fault that I could not successfully root his device. Any help would be much appreciated.
Thank you
For rooting purposes start HERE:
http://forum.xda-developers.com/showthread.php?p=33854391
For recovery look HERE:
http://forum.xda-developers.com/showthread.php?p=33867032
Add I prefer TWRP recovery over CWM!!
From everything you said you did it sounded right. Cuz you even tried going back too the original firmware that was shipped with the device!! But I didn't seed that after you flash the Rom,, did you try to do a factory data reset. Sometimes that's all it takes to fix that bootloop problem.
One other thing if you can get into download mode then the phone is fixable. Think it was just over your head on the process on how to get it back to fully functioning... lol
We've all been there. Think it's because we panic when something isn't working the way we want it TO..
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4

[Q] Samsung Note 2 Stuck On boot Screen

So I am having a problem with my Samsung Galaxy note 2. It was originally with AT&T until the contract had ended so I decided to use T-Mobile instead. I had to downgrade my firmware from 4.3 to unlock because ATT refused to unlock it. Anywho, it was working fine until it started getting this Samsung (ATT) update kept popping up repeatedly and accidentally I pressed for it to apparently download and I didn't realize it until the last minute. My phone began to restart and it got stuck on the "Samsung Galaxy Note 2" boot screen.
To make a long story shorter than what it already is, I tried everything to fix this I could possibly think of. From trying to go back to stock firmware, enter recovery mode (which it will not let me enter) and nothing will work. I am scared I am not going to be able to find a solution, as I've did research and attempts for over 8 hours today, so I'm somewhat on the edge. If anyone could help, it'd be much appreciated! I am also sorry if this type of thread has been posted, it's just I have tried everything on other threads and websites an can't seem to find a solution. Maybe I am doing something wrong, or just can't find the right stuff
Flash (in Odin) the tz-param file linked in post #2 here....
http://forum.xda-developers.com/showthread.php?t=2618447
That should allow the ota update to complete and allow phone to boot or at least get you recovery mode and allow you to wipe cache - assuming there are artifacts from the ota.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Thankyou!
Thankyou so much! It worked wonderfully!

[Q] Attempted Factory Reset now locked out!

So this may be a stupid question (but it's my first post so go figure) but I've read a few forum posts and I still can't seem to find a resolution.
I'm using a Rogers SGH i3170 with Android 4.3. I used the cf auto root file to root my phone with ODIN and otherwise did not modify the original software I manually installed the SuperSu apk to get around KNOX.
I was going to sell the phone so I went into the backup & reset option to clear out all my information. the phone seemed to clear itself just fine but now it won't go back the 'samsung' boot screen.
It'll show the device name, do the boot animation and otherwise just sits there.
The battery is at 80-90%
My main issue is that I would flash the stock ROM but it also won't go into recovery mode. It just reboots without actually going there.
Did I just brick my phone?
**I'm fairly new to rooting, I've rooted my S4 and Nexus 5 and was able to reset them without issue through the menus without using CWM or TWRP. I'm familiar enough with the processes just need some direction I guess!
Try this: Vol down& power& home. That'll put you into download mode so you can use Odin to return to stock...
You can also try THIS
If that doesn't help then goHERE for more INFO:thumbup:
Sent from my SAMSUNG-SGH-I317 using Tapatalk
LENT0N said:
So this may be a stupid question (but it's my first post so go figure) but I've read a few forum posts and I still can't seem to find a resolution.
I'm using a Rogers SGH i3170 with Android 4.3. I used the cf auto root file to root my phone with ODIN and otherwise did not modify the original software I manually installed the SuperSu apk to get around KNOX.
I was going to sell the phone so I went into the backup & reset option to clear out all my information. the phone seemed to clear itself just fine but now it won't go back the 'samsung' boot screen.
It'll show the device name, do the boot animation and otherwise just sits there.
The battery is at 80-90%
My main issue is that I would flash the stock ROM but it also won't go into recovery mode. It just reboots without actually going there.
Did I just brick my phone?
**I'm fairly new to rooting, I've rooted my S4 and Nexus 5 and was able to reset them without issue through the menus without using CWM or TWRP. I'm familiar enough with the processes just need some direction I guess!
Click to expand...
Click to collapse
My guess would be depending on what options you chose for wiping your data you probably wiped the root folder.
in which case there is nothing to boot to.
I have done that before in error and its a pain.
If you still have a recovery great you just need to flash a ROM.
Otherwise you might have to ODIN a recovery back on and then flash. Which is what I had to do.

[Q] softbrick throwing me for a loop

I normally work stuff like this out, but i'm having difficulties.
Note II i317, Was running rooted 4.4.2, knox tripped. (rooted it before we had facilities not to trip knox) I was prepping it for trade in, so I ran the back to stock zip instructions from the main forum. UCALJ2 went in fine, it booted and worked, and then OTA happened and now I'm frozen at the Galaxy Note 2 logo in the bootloader.
I have sdk, odin and can access download mode/flash, but can't get in to recovery (it never gets that far) .
I've tried re-flashing stock kies, i've tried a number of roms. I suspect that don't quite understand enough about knox or the bootloaders. I would think if download still works it's still fixable, but reflashing the stock includes a fresh boot loader and it still hates me. It's like it got something in the OTA that the flashes aren't touching.
Any ideas would be greatly appreciated, I've decided to keep it instead of trade but my note 4 is still a couple of days out.
Noting like posting a question to figure out wtf
http://forum.xda-developers.com/showthread.php?t=2596256 seems to have me going in the right direction

downgrading sgh-m919 from 4.4.4 to 4.4.2 for towel root guide

i just recently got a replacement galaxy s4 from tmobile because of a manufacturer defect. when this phone was shipped and i received it the stock firmware was the dreaded 4.4.4 firmware which breaks functionality with towelroot. i was somewhat dismayed because i really wanted to root my replacement without tripping the knox counter on my phone like before in case i have another problem (3rd galaxy s4 in about 1 year exact, first 2 both had same manufacturer defect. it was the "sim card has been removed error" which i can confirm after speaking to advanced technical support from tmobile that a defective batch of samsung galaxy s4's was sent to tmobile and they were extremely helpful and understanding.) Since rooting 4.4.4 is impossible to do without tripping knox (to my knowledge) i was looking for a way to downgrade to 4.4.2 without voiding the warranty. i can also confirm that according to samsung and tmobile downgrading to an official firmware will not void any kind of warranty as long as there is no custom recovery or anything of sort. i had read over other forums that people were having trouble with knox and the counter and a few other things and downgrading and even read some that: some people tripped the counter, was completely impossible to do, or would still be unable to root. all of this dashed my hopes of rooting and maintaining my warranty. i still wanted to try and after talking to tmobile and samsung gave it a try.
These are the steps i used and i hope they can help others who want to maintain their warranty while rooting after updating to 4.4.4 and finding out they might be in a hopeless situation.
~Things you will need: odin3, stock firmware 4.4.2 for sgh-m919 (can be downloaded from several places, good place to start is sammobile), windows computer, charging and sync/charging cable, your sgh-m919
Step 1: open odin on your computer and connect phone in odin mode (volume down+ power+ home)
Step 2: in pda option select the official stock firmware you downloaded before and click start
Step 3: it should start pretty quickly but if you notice no progress for a few minutes then check and see if you have text in the bottom left corner saying "get pit for mapping". if that is the case i had the same issue and all i had to to do was switch what usb port my phone was connected to on my computer and click start again.
Step 4: this where i had some more issues. after the phone reboots after odin is done i got stuck in a weird boot loop i believe and somehow fixed it pretty easily. so after getting stuck in the boot loop i removed my battery and then put it back and and tried booting in to recovery mode to perform a factory reset. i unfortunately was able to get to download mode. every time i tried it would it was recovery booting and then completely reboot. i tried several times with no luck. so i tried to see if odin mode would work and it did. so i held the power button and did a regular boot and removed the battery and put it back in and then tried to boot into recovery mode and it worked just fine this time.
Step 5: after reaching recovery mode again you will want to perform a factory reset. after it is done select the reboot phone option.
And that's all i had to do to downgrade. you should be on stock 4.4.2 firmware
i can confirm that after using this method i was able to root with towelroot and have not tripped knox
i have no idea if this will work on other samsung galaxy s4 models and do advise caution when flashing any kind of firmware without confirmation that it will work on your phone model
i have no idea if this has been covered but was unable to find anything myself after countless hours of searching the internet and hope that by creating this it will pop up in a search with key words pertaining to this issue in order to help people who just cant find this exactly while searching.
i would love to know if this works for any other galaxy s4 models so we can spread sneaking behind knox security to root without tripping the knox counter ( keep in mind that any form of custom recovery will trip knox)
hope this helps someone

Categories

Resources