Database Info

[Q] New Member of the Club, now Rooting but not flashing

Hi guys since today im a proud owner of a Galaxy Note 10.1 N8000 stock 4.1.2, but now comes the question, is it possible to Root it without flashing anything?
I only need root access to install a few apps, FolderMount, Titanium, Root explorer, etc.
I own too a Galaxy S2 that I rooted by the method of "rooting without flashing unsecure kernel" is it possible to apply the same method to the Note 10.1?
THANKS for any help given.

pedrohell said:
Hi guys since today im a proud owner of a Galaxy Note 10.1 N8000 stock 4.1.2, but now comes the question, is it possible to Root it without flashing anything?
I only need root access to install a few apps, FolderMount, Titanium, Root explorer, etc.
I own too a Galaxy S2 that I rooted by the method of "rooting without flashing unsecure kernel" is it possible to apply the same method to the Note 10.1?
THANKS for any help given.
Click to expand...
Click to collapse
Welcome to the club. Take a look at all the sections for the tablet and make sure you read the stickies too.
Method #2 and youl be good to go.
http://forum.xda-developers.com/showthread.php?t=1831152

I had already read that stickie and if I have correctly read, Method 2 (and the others) involves Odin and flashing something and that is what I dont want.
Isnt there a way to root without flashing?

pedrohell said:
I had already read that stickie and if I have correctly read, Method 2 (and the others) involves Odin and flashing something and that is what I dont want.
Isnt there a way to root without flashing?
Click to expand...
Click to collapse
Let me ask you this, why no flashing? As far as I know it's either Odin or flash. You need to get a custom recovery on it in order to root.
---------- Post added at 05:31 PM ---------- Previous post was at 05:30 PM ----------
Also with the s2 the recovery and kernel are in one. This is not.

Thanks for your help and time spent helping me, but I think I will pass the root on the Note, I thought there was a more easier/safe method like that on the S2.
Thanks

pedrohell said:
Thanks for your help and time spent helping me, but I think I will pass the root on the Note, I thought there was a more easier/safe method like that on the S2.
Thanks
Click to expand...
Click to collapse
No problem, but it don't get any easier than odin or recovery.

pedrohell said:
Thanks for your help and time spent helping me, but I think I will pass the root on the Note, I thought there was a more easier/safe method like that on the S2.
Thanks
Click to expand...
Click to collapse
There was an Exynos exploit method but Samsung patched the security hole a few updates ago.
The method in the link that was posted does alter your flash count and that can be correct but you are the owner of the device and if you are not comfortable flashing you tablet I wouldn't.
I have flashed mine and tried a few rom's but I always ended up resetting my flash counter and going back to stock.
Folder mount works great and that was the reason I rooted in the first place but you can store your files on the ext drive and transfer them back and forth manually but I found with my fast wifi I'm better off re-downloading the data along with "Helium - App Sync and Backup" to backup and restore my data and you do not need root, only draw back is that you have to have a computer connection for backup and restore to work.
.

Yes, its just a matter of not feeling confortable, and there is also the risk of blocking the camera. (had a similar issue with 4.1.2 on S2 needed to downgrade to 4.0.4).
But it seeems to me a bit odd that to grant root access we need to flash the rom.

I don't think you read that right. You're not flashing a ROM, just a custom recovery through ODIN, then a root app. It's actually very simple. (Any simpler and I would be concerned about rogue app exploits)
Fyi: I'm also new to Samsung devices and bought my tablet this week. Rooted it this morning by following the stickies, but sticking with the stock ROM for now. I'm more than happy with the tablet so far.
Sent from my GT-N8013 using xda app-developers app

pedrohell said:
Yes, its just a matter of not feeling confortable, and there is also the risk of blocking the camera. (had a similar issue with 4.1.2 on S2 needed to downgrade to 4.0.4).
But it seeems to me a bit odd that to grant root access we need to flash the rom.
Click to expand...
Click to collapse
There is no flashing a rom with method 2. You Odin the custom recovery then you have to flash the superuser into the system. You need superuser to get root and Odin is the easiest way.
Trust me we have all been in your shoes about being nervous, I've been doing this a long time and this method is really easy.

You can also use this method - http://forum.xda-developers.com/showthread.php?t=1957002
It does require ODIN but as has been stated this is the norm. You are not replacing any kernels or flashing another rom, you are just adding the root components. Using this method also leaves stock recovery intact...
If you woory about flash counter then run triangleaway after to reset the flash counter and recoveries....
I found doing this, doing a factory reset from settings then reflashing the Stock rom using Mobile ODIN pro gave me a stock standard, but rooted, rom with all statuses "Official" and 0 flash count....
A lot of work I know but then worthwhile things generally require it...

Ok, I followed the Method 2 made everything like on video, after pressing Power+Volume Up, I entered on STOCK Recovery, not the CWM,even so, I apply the .zip and I get:
MANUAL MODE
--Appling Multi-CSC....
Applied the CSC-code:LUX
Successfully applied multi-CSC.
--Install /sdcard....
Finding update package....
Opening update package....
Verifying update package.....
E:FAILED TO VERIFY WHOLE-FILE SIGNATURE
E:FAILED TO VERIFY WHOLE-FILE SIGNATURE
E:signature verification failed
I also retryed and turned off auto-reboot in Odin before starting the process but I get the same thing, now what should I do?
Its not rootable?

Ok, Its finally rooted, What I had to do,
On Odin unthick auto-reboot, When Odin finished doing its thing, dont shutdown the Tablet but press Power+Volume Up and go directly to CWM recovery and there follow the rest of instructions.
Thanks to everybody that took time to help me, thats why I love this forum.
A BIG THANK YOU.

pedrohell said:
I had already read that stickie and if I have correctly read, Method 2 (and the others) involves Odin and flashing something and that is what I dont want.
Isnt there a way to root without flashing?
Click to expand...
Click to collapse
I see that I'm probably too late now to answer the OP.
But maybe others can be interested.
I find that the easiest way to root (without odin and without installing a custom recovery) is Framaroot.
It uses some Exynos exploits, and has been also recently updated by the developer to counteract Samsung's patches.
It may work or it may not work on some devices and with some of the more recent firmware.
In any case giving it a try doesn't cost anything. It's just an app.
If it works the app can also be used to temporarily remove the root.
For me it worked with Firmware N8000XXCLL3 and I know that it works with some more recent fw too.
Furthermore it doesn't change the counter and even the Devices Status remains "Official". Well, actually the devices status may change to "Custom" after few days with the tablet on, but it returns Official after a simple reboot.

pedrohell said:
Ok, Its finally rooted, What I had to do,
On Odin unthick auto-reboot, When Odin finished doing its thing, dont shutdown the Tablet but press Power+Volume Up and go directly to CWM recovery and there follow the rest of instructions.
Thanks to everybody that took time to help me, thats why I love this forum.
A BIG THANK YOU.
Click to expand...
Click to collapse
Awesome to hear! I ran into the same thing you did, forgot to go straight to recovery from odin.
Enjoy!

Stuck
Please help..
I get this error when i try to install: View attachment 2066244
What did i do wrong ?

brix696 said:
Please help..
I get this error when i try to install: View attachment 2066244
What did i do wrong ?
Click to expand...
Click to collapse
I don't use CWM, but see if there is a signature seeing to turn it off. Also make sure your md5 of the zip is correct.

brix696 said:
Please help..
I get this error when i try to install: View attachment 2066244
What did i do wrong ?
Click to expand...
Click to collapse
What were your options on the page right before that? What option did you select to initiate that?
Maybe try using the files from here instead:
http://droidviews.com/2013/root-and...ung-galaxy-note-10-1-n8000-n8010-n8013-n8020/

bigtoysrock said:
I don't use CWM, but see if there is a signature seeing to turn it off. Also make sure your md5 of the zip is correct.
Click to expand...
Click to collapse
Where should i look for a signature ? I have downloaded the file 3 times, just to manke sure that i wasen't bad.
Before that, it was the page where i choose "apply update from external storage"
I have tryed the CF, still the same

brix696 said:
Where should i look for a signature ? I have downloaded the file 3 times, just to manke sure that i wasen't bad.
Before that, it was the page where i choose "apply update from external storage"
I have tryed the CF, still the same
Click to expand...
Click to collapse
I would use the touch cwm, and what rom are you trying to install?

The first case reset Warranty Bit in Galaxy Note 3 Exynos N900 successfully!!!

Hello forum,
I come from Vietnam, I have participated in this forum for a long time. The devs helped guys like me so much to be able to use our phone in the best ways.
Today I have one thing to share with you, may be it will help the devs to find a way to solve the problem of reseting warranty bit in Samsung Galaxy Note 3 into 0.
I bought my Note 3 N900 five months ago. At that time, I rooted my phone and then update my note 3 via OTA. But from the fist update which showed Warranty Bit: 1 (MJ7). I didn't update it via OTA any more.
Then I download a stock rom named "STOCK-DEODEX-ROOT-N900XXUCMJ7_N900OLBCMJ3_N900DXUCMJ3_HOME" of developer @nguyenxuanhoa then rooted it again and used it untill yesterday.
Yesterday, I found that my device wasn't rooted and CWM disappear. I couldn't understand. Then I installed CWM and rooted it again. After that. I uploaded rom cook version 9.0 then 8.1 (android 4.4.2) of developer @nguyenxuanhoa but it did't work well (couldn't use apps restored from titanium backup and couldn't logged in evernote)
Then I used the stock Mj7 4 files but just uploaded 1 file AP in order to restore my phone to android 4.3 but it was suspended at samsung logo. Then I went to stock recovey to wipe data and reboot, but it was fault: force close samsung keyboard.
In the last time, I flashed 4 files in stock MJ7 to restore again and OMG! The warranty bit was restored to 0. I can't understand but very happy. I can use Knox, of course. Everything in my phone was restored as when i bought it from the seller.
I hope that information will help you to guess how could we resset warranty bit of Galaxy Note 3 N900 into 0.
Stock Rom Mj7 4 files: Link/
STOCK-DEODEX-ROOT-N900XXUCMJ7_N900OLBCMJ3_N900DXUCMJ3_HOME: Part 1 Part 2
Rom cook by @nguyenxuanhoa: Link
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
View attachment 2628353
View attachment 2628354

Maaaaaaaaaaaaaaaaan
if what you did is true and we can all do it.
then thank you very much my freind and hope that this will help the devs defeat this knox app.

We need someone to try this I hope that is true
Sent from my SM-N900

DON AMIGO said:
Maaaaaaaaaaaaaaaaan
if what you did is true and we can all do it.
then thank you very much my freind and hope that this will help the devs defeat this knox app.
Click to expand...
Click to collapse
dannycanrock said:
We need someone to try this I hope that is true
Sent from my SM-N900
Click to expand...
Click to collapse
I'm not sure, because there are not many people keep their N3 in firmware Mj7 like me, so I don't know if this case is right with the other. I just post my case there and hope that someone can follow this and reset warranty bit successfully, too.

ii have a note 2, i have full wipe and flashed 4 tar in bl, csc, ap and nothing happens, i still have knox bit 1, i am curious how did you do that, is it because you download bl then upload it agian? hummm

If you look a little the menu is a little different for n900 not like n9005.Maybe different bootloaders diferent knox and maybe for n900 work.

luckyboy_103 said:
I'm not sure, because there are not many people keep their N3 in firmware Mj7 like me, so I don't know if this case is right with the other. I just post my case there and hope that someone can follow this and reset warranty bit successfully, too.
Click to expand...
Click to collapse
Yeaahh, thanks for your report. We are working on testing progress. I think maybe the reason that you flash many time and get luck. I don't know how and why but good work.
Send from my SM-N900 using Tapatalk 4 Pre

newxdabie said:
ii have a note 2, i have full wipe and flashed 4 tar in bl, csc, ap and nothing happens, i still have knox bit 1, i am curious how did you do that, is it because you download bl then upload it agian? hummm
Click to expand...
Click to collapse
No, I just flashed AP file for the first time, then flashed all 4 files in stock mj7 for the second time and.. it worked :d
Sent from my SM-N900 using Tapatalk

will somebody test this method.

luckyboy_103 said:
No, I just flashed AP file for the first time, then flashed all 4 files in stock mj7 for the second time and.. it worked :d
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
Make a guide for amateur like us...
Sent from my SM-N900 using XDA Premium 4 mobile app

ghalib87 said:
Make a guide for amateur like us...
Sent from my SM-N900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Maybe he got luck. Let's see how to do. Hope that's guide for developers to fix it perfect.
Send from my SM-N900 using Tapatalk 4 Pre

luckyboy_103 said:
No, I just flashed AP file for the first time, then flashed all 4 files in stock mj7 for the second time and.. it worked :d
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
I cant understand it... flashing ap before flash 4 files dont make any sense about it...because i realized that their flash bl first if you have knox bit the bl will load thia information and do not replace it...i guess there something is missing in your steps or because you flashed deox knox rom or rom with bl lower before...not sure

I can confirm this, However im not sure of the method. But I do remember It involved the MJ7 Firmware. At a point of flashing where my Phone got Soft Bricked, I noticed that the Warranty Bit was Reset and 0x0. At that Point the phone was not useable, and it was soft-bricked with a "Stuck on Boot Logo" Situation. However, After I installed CWM and SuperSu again, It was gone. In order to find out the exact method and to create a guide (And of course to take the bounty! ) I tried to recreate this over and over again, But It never worked out. Then I just ditched the idea thinking it might be a fault in the Recovery. Now that you have posted this in OP, I believe there is a trigger within the phone itself. The Phone which I tested too was a N900 and I was playing with the MJ7 Firmware.

newxdabie said:
I cant understand it... flashing ap before flash 4 files dont make any sense about it...because i realized that their flash bl first if you have knox bit the bl will load thia information and do not replace it...i guess there something is missing in your steps or because you flashed deox knox rom or rom with bl lower before...not sure
Click to expand...
Click to collapse
I can't understand, too. I flashed 4 files after flashing ap just because it was fault. There was nothing in my steps missed. I absolutely sure about that.
Sent from my SM-N900 using Tapatalk

JazonX said:
I can confirm this, However im not sure of the method. But I do remember It involved the MJ7 Firmware. At a point of flashing where my Phone got Soft Bricked, I noticed that the Warranty Bit was Reset and 0x0. At that Point the phone was not useable, and it was soft-bricked with a "Stuck on Boot Logo" Situation. However, After I installed CWM and SuperSu again, It was gone. In order to find out the exact method and to create a guide (And of course to take the bounty! ) I tried to recreate this over and over again, But It never worked out. Then I just ditched the idea thinking it might be a fault in the Recovery. Now that you have posted this in OP, I believe there is a trigger within the phone itself. The Phone which I tested too was a N900 and I was playing with the MJ7 Firmware.
Click to expand...
Click to collapse
Thank you for your confirmation. I am luckier than you while my phone was reset to 0x0 within any fault. I'm not sure it could happen again :d
Sent from my SM-N900 using Tapatalk

i'm sure that someone in this great forum will help us in this matter
and give us the method and hopefully help the devs here to defeat this knox app.

DON AMIGO said:
i'm sure that someone in this great forum will help us in this matter
and give us the method and hopefully help the devs here to defeat this knox app.
Click to expand...
Click to collapse
matbe downgrade between knox enable bootload can reset knox counter, i am in note 2 we have only 4.3 mk9, i ve doing this process lot of times and still knox bit =1 and i realized there are note 3 that have odin mode diffrent from yours, we have knox warrenty bit and ap swaev : A2, and your phone only has warenty bit, and tell me more one thing, when you flash the second time, you need turn indo odin mode(download mode) you already seeing knox bit = 0 this step or just after flashing 4 files? and what is your configuretion with odin? what version are you using? thx

newxdabie said:
matbe downgrade between knox enable bootload can reset knox counter, i am in note 2 we have only 4.3 mk9, i ve doing this process lot of times and still knox bit =1 and i realized there are note 3 that have odin mode diffrent from yours, we have knox warrenty bit and ap swaev : A2, and your phone only has warenty bit, and tell me more one thing, when you flash the second time, you need turn indo odin mode(download mode) you already seeing knox bit = 0 this step or just after flashing 4 files? and what is your configuretion with odin? what version are you using? thx
Click to expand...
Click to collapse
Regret that I didn't see warranty line when I flashed 4 files and even after that. I only saw it after flashing CWM failed as I mentioned in #1.
I just flashed files by odin normally. Version of odin is 3.04!

luckyboy_103 said:
Regret that I didn't see warranty line when I flashed 4 files and even after that. I only saw it after flashing CWM failed as I mentioned in #1.
I just flashed files by odin normally. Version of odin is 3.04!
Click to expand...
Click to collapse
so you flashed it dont in odin mode?, if you in odin mode you should see it

It mean that:
- flash 4.4.2 rom - > flash ap -> let's it boot in 20-30s -> wipe -> flash all 4 file (bootloader MJ7 again?) -> wipe
So, simply it can tell: Maybe a software bug in MJ7 bootloader that will check system integrity of system and set KNOX flag again to 0 (it was 1) in bootloader.
Why it's a bootloader bug? It didn't check check warranty bit was writen. It will check and rewrite everytime you flash it. (Maybe bootloader will check a flag/file in data/system/hidden partition that was set by kernel/OS that tell integrity state of system and set know flag)
So now i need a volunteer that have equal or below MJ7 (MJ1/MJ7)... And flash AP (MJ7) - when flash with odin please don't check reboot. when it flashed. Go to Recovery and wipe. Then flash 4 files include bootloader again.

How to restore warranty at sammy custom roms 4.3, 4.4.2, updated added ZSUFNJ2

First a big thanks to anyone who is cooking roms writing apps scripts etc here and to user faria for the param.bin file.
Now the point, i found a solution to restore warranty at custom roms and i like to share with you.
This checked and working at any 4.3, 4.4 sammy rom.
Now what u need
1) mj5 bootloader
2) a rom compatible with mobile odin
3) mobile odin (i am using pro but i think is not necessary such as everoot is not necessary, don't forget if u don't use pro u have to download with app and the proper mobile odin kernel from chainfire's post)
4) triangle away
5) the files attached at end
6) stock kernel and recovery ( u can extract them from same version original rom, attention don't use other rom with other version stock kernel because u will have not wifi)
Ok now the procedure install and open mobile odin
Put at the place is saying param the param.bin file
Put at the place is saying kernel the stock kernel
check to wipe the dalvik cache (is not necessary but do it)
Flash and reboot
Check root, is ok 99% but if is not ok flash with your custom recovery supersuupdate
and after reboot check again root
If ok open again mobile odin and
put at the place is saying recovery stock recovery and flash it
After reboot install triangle away follow dev instuctions and reset the counter.
Thats all after reboot shut down your phone enter download mode and check your warranty.
Now i am attaching the param.bin file (u have to extract with winrar)
and some ready packets (kernel, recovery, param.bin) for some 4.4.2 versions, u can use them or use your own with param.bin file).
The srvr is paid but u can download as free user too (is not necessary to pay)
Thanks for reading.
Files:
4.4.2 XXUFND3.rar - 15.1 MB
4.4.2 XXUFNE1.rar - 15.1 MB
4.4.2 XXUFNE2.rar - 15.2 MB
param.rar - 877 KB
4.4.2 XXUFNG4.rar - 27.4 MB
4.4.2 XXUFNG3.rar - 15.0 MB
4.4.2 XXUFNH2.rar - 15.0 MB
4.4.2 XXUFNI1.rar - 15.0 MB
4.4.2 XXUFNI4.rar - 15.0 MB
4.4.2 ZSUFNJ2.rar - 15.6 MB
And some new important info.
I tried to a rom not compatible with mobile odin (the mobile odin didn't restart to flash the kernel etc)
I rebooted at once manual with 4way reboot to recovery without closing the app and mobile odin worked made the flash.
After reboot i tried to see if my custom recovery was ok and was everything ok.
After i flashed stock recovery and made the same didn't restart,i restarted again with 4way reboot at recovery and made the flash safe.
And know the good one, it did the same with triangle away, i checked reset counter and didn't restart, i restarted at recovery at once with 4way reboot and worked.
Custom Binary Download No, official, official, warranty bit 0 with any custom rom (sammy base)
This is a personal experience which i am sharing with u, i am not a developer or something other and i am not responsible if something goes bad.
Use it with your own responsibility.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/URL][/IMG]

Great stuff
vagsvag said:
First a big thanks to anyone who is cooking roms here and to user faria for the param.bin file.
Now the point, i found a solution to restore warranty at custom roms and i like to share with you.
This checked and working at any 4.3, 4.4 sammy rom (only at latest 4.4.2 XXUFNG4 i haven't test it)
Now what u need
1) mj5 bootloader
2) a rom compatible with mobile odin
3) mobile odin (i am using pro but i think is not necessary such us everoot is not necessary, don't forget if u don't use pro u have to download with app and the proper mobile odin kernel from chainfire's post)
4) triangle away
5) the files attached at end
6) stock kernel and recovery ( u can extract them from same version original rom, attention don't use other rom with other version stock kernel because u will have not wifi)
Ok now the procedure install and open mobile odin
Put at the place is saying param the param.bin file
Put at the place is saying kernel the stock kernel
check to wipe the dalvik cache (is not necessary but do it)
Flash and reboot
Check root, is ok 99% but if is not ok flash with your custom recovery supersuupdate
and after reboot check again root
If ok open again mobile odin and
put at the place is saying recovery stock recovery and flash it
After reboot install triangle away follow dev instuctions and reset the counter.
Thats all after reboot shut down your phone enter download mode and check your warranty.
Now i am attaching the param.bin file (u have to extract with winrar)
and some ready packets (kernel, recovery, param.bin) for some 4.4.2 versions, u can use it or use your own with param.bin file).
The srvr is paid but u can download as free user too (is not necessary to pay)
Thanks for reading and again to user faria for the param.bin file.
Files:
4.4.2 XXUFND3.rar - 15.1 MB
4.4.2 XXUFNE1.rar - 15.1 MB
4.4.2 XXUFNE2.rar - 15.2 MB
param.rar - 877 KB
Click to expand...
Click to collapse
Great stuff. :good:
Waiting for 4.4.2 XXUFNG4 version.

xbean said:
Great stuff. :good:
Waiting for 4.4.2 XXUFNG4 version.
Click to expand...
Click to collapse
Thank you, u can try it with XXUFNG4 too 99,99% will work extract kernel and recovery from original rom and use and the param.bin file with the posted procedure.
It is the same param.bin file everywhere. You can use this procedure at 4.3 too.

1rst post updated
Ok guys i checked at 4.4.2 XXUFNG4 and working
I am attaching kernel recovery and param.bin (by mistake i uploaded and the modem ignore it)
Link:
4.4.2 XXUFNG4.rar - 27.4 MB
And some new important info.
I tried to a rom not compatible with mobile odin (the mobile odin didn't restart to flash the kernel etc)
I rebooted at once manual with 4way reboot to recovery without closing the app and mobile odin worked made the flash.
After reboot i tried to see if my custom recovery was ok and was everything ok.
After i flashed stock recovery and made the same didn't restart,i restarted again with 4way reboot at recovery and made the flash safe.
And know the good one, it did the same with triangle away, i checked reset counter and didn't restart, i restarted at recovery at once with 4way reboot and worked.
Custom Binary Download No, official, official, warranty bit 0 with DEEP IMPACT ROM v2.3
This is a personal experience which i am sharing with u, i am not a developer or something other and i am not responsible if something goes bad.
Use it with your own responsibility.

hi dev,
my note2 has xxufng4 bootloader,
i am noob for this work pls give with screenshots for safe side
thank u

Is this a method to reset the warranty bit from 1x1 to 0x1?
My warranty bit is 1x1 since I flashed the mk9 bootloader and then a custom recovery. I've since updated the bootloader to ND3.

JGKUMAR1976 said:
hi dev,
my note2 has xxufng4 bootloader,
i am noob for this work pls give with screenshots for safe side
thank u
Click to expand...
Click to collapse
tonylee000 said:
Is this a method to reset the warranty bit from 1x1 to 0x1?
My warranty bit is 1x1 since I flashed the mk9 bootloader and then a custom recovery. I've since updated the bootloader to ND3.
Click to expand...
Click to collapse
@JGKUMAR1976 Sorry this is working only with mj5 bootloader
@tonylee000 Sorry i don't know a way to change warranty bit, this guide is resetting Custom Binary Download from any number to no

vagsvag said:
@JGKUMAR1976 Sorry this is working only with mj5 bootloader
@tonylee000 Sorry i don't know a way to change warranty bit, this guide is resetting Custom Binary Download from any number to no
Click to expand...
Click to collapse
Ok cool. That's what I suspected. I don't see the point in the risk involved? If you've not flashed a bootloader newer than mj5 then its a simple case of flashing a stock rom from sammobile, root, triangle away, unroot. Job done. Then your phone is in a condition where it can be returned for repairs under warranty. If you return it with a custom rom installed then it's gonna be obvious the warranty been violated or is there something I'm missing here?
Ifyour not returning the phone to use warranty then you don't need to bother?

tonylee000 said:
Ok cool. That's what I suspected. I don't see the point in the risk involved? If you've not flashed a bootloader newer than mj5 then its a simple case of flashing a stock rom from sammobile, root, triangle away, unroot. Job done. Then your phone is in a condition where it can be returned for repairs under warranty. If you return it with a custom rom installed then it's gonna be obvious the warranty been violated or is there something I'm missing here?
Ifyour not returning the phone to use warranty then you don't need to bother?
Click to expand...
Click to collapse
You missed a point, the point is that most of us have phones with faulty emmc chip etc and many of our phone die suddenly, how do you flash your 9 months phone when is totally dead and goes only in download mode? Impossible, the next thing is to sent it 4 repair to change motherboard. The first thing they look at service is your binary count, if is ok your repair is free if is not 180 euro from your pocket goes away. I hope you understand the meaning of all this now.
Sent from my GT-N7100 using Tapatalk 2

vagsvag said:
You missed a point, the point is that most of us have phones with faulty emmc chip etc and many of our phone die suddenly, how do you flash your 9 months phone when is totally dead and goes only in download mode? Impossible, the next thing is to sent it 4 repair to change motherboard. The first thing they look at service is your binary count, if is ok your repair is free if is not 180 euro from your pocket goes away. I hope you understand the meaning of all this now.
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
I wasn't being funny with you was wondering what the end game was. I wouldn't worry too much about the Emmc problem. If your phone is only 9 months old you should be fine. Early note 2s had the dodgy chip or 'insane' chip. My note 2 is one of those. There are apps you can get off the play store to tell you if you have an insane chip or a safe one. If the service centre can see download mode and see the binary counter is 0 then wouldnt they be able to see the warranty bit too? Unfortunately my warranty bit is now set to 1 so my warranty is probably not valid. I've had mine for 22 months now so I only have 2 months left on the warranty anyway so its not really a big problems for me now. As i recall the 'insane' emmc problems occurred because of a kernel issue in android 4.1.1 that burnt the chip out which was fixed in the 412 uodate

tonylee000 said:
I wasn't being funny with you was wondering what the end game was. I wouldn't worry too much about the Emmc problem. If your phone is only 9 months old you should be fine. Early note 2s had the dodgy chip or 'insane' chip. My note 2 is one of those. There are apps you can get off the play store to tell you if you have an insane chip or a safe one. If the service centre can see download mode and see the binary counter is 0 then wouldnt they be able to see the warranty bit too? Unfortunately my warranty bit is now set to 1 so my warranty is probably not valid. I've had mine for 22 months now so I only have 2 months left on the warranty anyway so its not really a big problems for me now. As i recall the 'insane' emmc problems occurred because of a kernel issue in android 4.1.1 that burnt the chip out which was fixed in the 412 uodate
Click to expand...
Click to collapse
The warranty bit at mj5 bootloader is cosmetic 1000 flashes to do 0 will stay. Mine is 18 months old.
The fix they made is dirty fix and not really fix also the kernel hadn't any problem at 4.1.1 the problem was the chip and the fix they made was to setup the newer kernels to don't write at certain blocks which had the problem..If you search little about this you will see and "safe" emmc chips 1301 etc have also sds symptom.
The secret with these faulty chips is i believe to don't fill all the internal memory, and also if you have warranty to be active.

First post updated added support for XXUFNG3
4.4.2 XXUFNG3.rar - 15.0 MB

First post updated added XXUFNH2, XXUFNI1
4.4.2 XXUFNH2.rar - 15.0 MB
4.4.2 XXUFNI1.rar - 15.0 MB

Does this still work??
Very Curious!! :crying:

Bunny2rock said:
Does this still work??
Very Curious!! :crying:
Click to expand...
Click to collapse
Working like a charm.
Sent from my GT-N7100 using Tapatalk 2

Do I understand it right that with this method you can reset knox_warranty_void to 0?
Everyone is saying that it is not possible! That would be very nice

teddyteddy92 said:
Do I understand it right that with this method you can reset knox_warranty_void to 0?
Everyone is saying that it is not possible! That would be very nice
Click to expand...
Click to collapse
I too wanted to know same...

teddyteddy92 said:
Do I understand it right that with this method you can reset knox_warranty_void to 0?
Everyone is saying that it is not possible! That would be very nice
Click to expand...
Click to collapse
mietens said:
I too wanted to know same...
Click to expand...
Click to collapse
No guys this method reseting the flash counter (custom binary download from any number to no even if you have custom sammy based rom installed) not the knox warranty void and working with mj5 bootloader and older. At mj5 bootloader the knox warranty is cosmetic, 300 flashes to do 0 will stay. If you have installed newer than mj5 bootloader don't try it you'll loose your time.
Sent from my GT-N7100 using Tapatalk 2

First post updated added support for XXUFNI4
4.4.2 XXUFNI4.rar - 15.0 MB

First post updated added support for ZSUFNJ2
4.4.2 ZSUFNJ2.rar - 15.6 MB

6.0.1 OTA for stock rooted system

Hi, sorry if this is a stupid question, but I just noticed Sprint pushed an OTA for 6.0.1 to my stock rooted device (S-on) and I'm just trying to figure out what the best way to get this OTA is going to be. I'm assuming I shouldn't download and install the OTA as-is due to the TWRP recovery and root.
After looking around a bit, it seems like the only option available is to use a stock 6.0.0 RUU file in the bootloader and basically reset the entire device back to factory settings (losing all apps and data in the process presumably), installing the OTA, then re-flashing TWRP and re-rooting.
I guess what I'm asking is - 1. is this the correct way to go about doing this? and 2. is there any better alternative perhaps that doesn't involve losing my data?
Thanks in advance guys.

Been googling around for the last few days and scouring this board for just as long and still haven't come to a definitive conclusion. From what little I've seen the documentation on this seems kind of spotty and I'm just wondering which direction to head in. Any help on this would be much appreciated.

Safest way.. ruu back to stock everything take ota and re root/download apps etc...

Thanks for the reply, man.. Thats kind of what I had gathered pouring over all these articles and board posts. I went ahead and RUU'd back to 1.10.651.1 for sprint.. Literally just moments ago though I downloaded the OTA and hit install and got presented with an error screen during the update. Phone rebooted back into the system normally, and I went to check the version # only to see it unchanged, along with a prompt to install the OTA for 1.57.651.1 again.
Any idea why this might've happened or how to remedy it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wonders_Never_Cease said:
Safest way.. ruu back to stock everything take ota and re root/download apps etc...
Click to expand...
Click to collapse

What was the error? You may have to relock bootloader to accept the ota...unsure of how they are with their device,GSM device I have doesnt need relocked...(S-Off as well so)
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
Also the 1.57.651.1 RUU is available... Why not use it?
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.57.651.1_R2.exe

Thats the weird part, it didnt give an error message, just that icon in the image I added to my last post. forelock the bootloader would be kind of surprising... Might give that a try in the morning after I find out if it can be re-unlocked.
EDIT: Ohhh I just saw your last edit, i didnt see that before, i'll use that then. Thank you!!!
Wonders_Never_Cease said:
What was the error? You may have to relock bootloader to accept the ota...unsure of how they are with their device,GSM device I have doesnt need relocked...(S-Off as well so)
---------- Post added at 12:50 AM ---------- Previous post was at 12:47 AM ----------
Also the 1.57.651.1 RUU is available... Why not use it?
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.57.651.1_R2.exe
Click to expand...
Click to collapse

Download the .651 ruu,reboot phone into download mode and run it... Should be up to date after that for a bit id think
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
How did you unlock it to begin with? HTC Dev site? If so then should be able to use the same unlocktoken.bin from before... Or can resubmit and get another one...
txag2011 said:
Thats the weird part, it didnt give an error message, just that icon in the image I added to my last post. forelock the bootloader would be kind of surprising... Might give that a try in the morning after I find out if it can be re-unlocked.
EDIT: Ohhh I just saw your last edit, i didnt see that before, i'll use that then. Thank you!!!
Click to expand...
Click to collapse

Thats precisely what I did. Unlocked it with the HTC Dev Token. I gotta admit, I was pretty surprised that I had an OTA so soon after getting the phone and unlocking / rooting it. Just when I had everything set up how I liked it
I just finished flashing the 651 RUU and its just optimizing the apps now, but looks like it should do it!
Wonders_Never_Cease said:
Download the .651 ruu,reboot phone into download mode and run it... Should be up to date after that for a bit id think
---------- Post added at 12:58 AM ---------- Previous post was at 12:53 AM ----------
How did you unlock it to begin with? HTC Dev site? If so then should be able to use the same unlocktoken.bin from before... Or can resubmit and get another one...
Click to expand...
Click to collapse

Cool glad got it sorted...
txag2011 said:
Thats precisely what I did. Unlocked it with the HTC Dev Token. I gotta admit, I was pretty surprised that I had an OTA so soon after getting the phone and unlocking / rooting it. Just when I had everything set up how I liked it
I just finished flashing the 651 RUU and its just optimizing the apps now, but looks like it should do it!
Click to expand...
Click to collapse

Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Wonders_Never_Cease said:
Cool glad got it sorted...
Click to expand...
Click to collapse

First thing ya need to do is read how to install adb and fastboot and get away from toolkits... Download 2.67 from this thread...copy to device flash through twrp...
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
txag2011 said:
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Click to expand...
Click to collapse

And didnt mean that in a snotty,sarcastic way... Those tools sometimes cause issues that could be avoided is all I was getting at...

I want to join this conversation.
The A9 of my mom got is a Vodaphone UK version (cid: vodap001) and got the update message to version 1.62.161.2
I've rooted the device and installed TWRP.
So now i relocked the bootloader, installed the firmware.zip that was inside the OTA Download which i've copied from Update-App Path.
If i now want to manualy update the OTA-zip with fastboot in download-mode, i got Error 7.
If i want to update with original OTA updater Up, it stops at 25% with the red cross.
So what should i do now?
There is noch previous RUU-file for this firmware-version thats why i've already updated to the recovery from this OTA-update.
I hope someone can help with it.
Thanks,
Bond

txag2011 said:
Actually.. I've hit another wall now tryign to achieve root with this. I've got TWRP back on the device, and I'm using WinDroid Toolkit to flash SuperSU to it. It'll show that it's pushing it, then drop into recovery and naturally ask for me to wipe the /data partition since it's encrypted, before proceeding to install the supersu.zip package.
The only problem is, there doesn't appear to be any supersu.zip anywhere on the device once it gets into recovery, either before or after the data wipe. Any idea where it's going?
Click to expand...
Click to collapse
I have to agree with Wonders_never_cease about the toolkits. I have used many different ones and they are great from a few things but not all things go right using them unlike adb/fastboot. You should have better results from using adb/fastboot here.
That being said.....it would be easier to achieve root by simply going to full stock using RUU or system/boot.img in fastboot, flashing TWRP, format data, reboot into TWRP, flash supersu 2.74 from your SD card either by itself to obtain normal root or follow steps here http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 for systemless root. it's that simple...or at least was for me. I never could get pushing supersu through adb right or to work really.
---------- Post added at 10:12 AM ---------- Previous post was at 09:59 AM ----------
Bond246 said:
I want to join this conversation.
The A9 of my mom got is a Vodaphone UK version (cid: vodap001) and got the update message to version 1.62.161.2
I've rooted the device and installed TWRP.
So now i relocked the bootloader, installed the firmware.zip that was inside the OTA Download which i've copied from Update-App Path.
If i now want to manualy update the OTA-zip with fastboot in download-mode, i got Error 7.
If i want to update with original OTA updater Up, it stops at 25% with the red cross.
So what should i do now?
There is noch previous RUU-file for this firmware-version thats why i've already updated to the recovery from this OTA-update.
I hope someone can help with it.
Thanks,
Bond
Click to expand...
Click to collapse
You will not be able to apply the OTA update if you are not completely stock including being with stock recovery. Having your bootloader unlocked will not be an issue so no need to relock it like you did. Use a system/boot/recovery.img to restore stock completely, or whatever RUU need. Then accept the OTA or flash it manually, then reroot. Thats really the only way you will be able to get that to work.....

mcbright80 said:
You will not be able to apply the OTA update if you are not completely stock including being with stock recovery. Having your bootloader unlocked will not be an issue so no need to relock it like you did. Use a system/boot/recovery.img to restore stock completely, or whatever RUU need. Then accept the OTA or flash it manually, then reroot. Thats really the only way you will be able to get that to work.....
Click to expand...
Click to collapse
Thanks for your answer.
But how to get complete stock without nandroid or RUU?
The Firmware.zip of the 1.62.161.2 OTA Update was installed without Errors. But as i already mentioned i Need stock System/boot-files of my last Version (1.62.161.1) to get this partitions to stock. And they are not available anywhere.

Bond246 said:
Thanks for your answer.
But how to get complete stock without nandroid or RUU?
The Firmware.zip of the 1.62.161.2 OTA Update was installed without Errors. But as i already mentioned i Need stock System/boot-files of my last Version (1.62.161.1) to get this partitions to stock. And they are not available anywhere.
Click to expand...
Click to collapse
Ah so sorry, it was 4 am when i was replying so i missed that part on it installing correct, or confused it with the other question i was replying to at that same time haha......anyhoo....i looked for you as well and nothing was found on my end as well so I think you may be in the exact situation i was in when i bought the sprint variant of the A9. HTC has faults like all companies but the one that really pisses me off is their lack of proper support on ALL variants especially concerning firmware. The phone was released and i found NO RUU on their site or anywhere online and of course not many people had my specific variant which meant no one on here or anywhere had the means to get me the stock firmware i too needed to restore my phone.
The ONLY reason anyone here, who has SPRINT US VERSION, is able to then and NOW get the RUU on the HTC website is directly due to my incessant badgering and yelling at HTC damn near daily about having a handset on the market for sale but no firmware for it in case of tech service needs. You may have to do the same thing sadly.
I assume you have checked htc UK site for the rom downloads......contact their tech support and see whats up. Till then, like i had to when the sprint version came out....you'll have to just keep checking back on here and anywhere online for someone else who may post what you need or some other kind of solution.

Thanks mcbright80,
as you already said, HTC resists and says RUUs are only available in the US. I'm excited on their reaction that there are still lower RUU-versions of my UK-edition.
It is an annoying mess with all these different versions for tons of carriers, countrys and so on.

I give up.

I've got a Galaxy S5 that I purchased from someone earlier today and it worked well until I did some type of software update, it went well but then restarted and it's been messed up since. Now, whenever I boot up the phone it boots fine all the way too the Sprint Spark screen and it just hangs, and hangs and then restarts again, and goes through the same process. I've tried reflashing the device using Odin but I keep getting an error "SW REV CHECK FAIL" with some other stuff. I've tired to do so much, I tried resetting the device and the cache using the options. Please, can someone offer me some help. It's a 900P and it's a Sprint device. I just got back from a funeral a little bit ago so I'd love to get this thing working finally, I've been working on it all night.

Can you check the model number under the battery?
I think Sm-g900m is the South America version, and Sm-g900p should be the North America sprint version.

tys0n said:
Can you check the model number under the battery?
I think Sm-g900m is the South America version, and Sm-g900p should be the North America sprint version.
Click to expand...
Click to collapse
Yes, that's correct my bad. It's the 900P. I'll correct the thread.

nulledbyme said:
Yes, that's correct my bad. It's the 900P. I'll correct the thread.
Click to expand...
Click to collapse
Ok, good The "SW REV CHECK FAIL" is probably caused by secure bootloader which won't allow downgrade.
Have you tried to flash the latest firmware?

tys0n said:
Ok, good The "SW REV CHECK FAIL" is probably caused by secure bootloader which won't allow downgrade.
Have you tried to flash the latest firmware?
Click to expand...
Click to collapse
Could you link me a GOOD site that doesn't require me to pay to get fast downloads? Haha I'll try it in the morning if you send me a link.

nulledbyme said:
Could you link me a GOOD site that doesn't require me to pay to get fast downloads? Haha I'll try it in the morning if you send me a link.
Click to expand...
Click to collapse
Sure! This should be the latest firmware available. http://updato.com/firmware-archive-select-model?record=281516900A1911E7963AFA163EE8F90B
Hope it will work to get you up and running.

tys0n said:
Ok, good The "SW REV CHECK FAIL" is probably caused by secure bootloader which won't allow downgrade.
Have you tried to flash the latest firmware?
Click to expand...
Click to collapse
tys0n said:
Sure! This should be the latest firmware available. http://updato.com/firmware-archive-select-model?record=281516900A1911E7963AFA163EE8F90B
Hope it will work to get you up and running.
Click to expand...
Click to collapse
It goes fine all the way till the system.img.ext4 part and it just sits there. I tried letting it sit last night for 4+ hours on a different firmware and it just sat there. Any thoughts?
EDIT: So, I reflashed it, it was successful but my device still hangs at the Sprint screen..

nulledbyme said:
It goes fine all the way till the system.img.ext4 part and it just sits there. I tried letting it sit last night for 4+ hours on a different firmware and it just sat there. Any thoughts?
EDIT: So, I reflashed it, it was successful but my device still hangs at the Sprint screen..
Click to expand...
Click to collapse
Hmm, I have no idea why it won't boot properly. This "stuck on bootlogo" seems to be a common problem on todays samsung models.
Have you tried factory reset in recovery after flash?
Only other thing I can think of is if some other partition got messed up during the software update.
Maybe can be fixed with a 4-file "repair firmware" with BL/AP/CP/CSC-parts. I'll see if I can find one.

tys0n said:
Hmm, I have no idea why it won't boot properly. This "stuck on bootlogo" seems to be a common problem on todays samsung models.
Have you tried factory reset in recovery after flash?
Only other thing I can think of is if some other partition got messed up during the software update.
Maybe can be fixed with a 4-file "repair firmware" with BL/AP/CP/CSC-parts. I'll see if I can find one.
Click to expand...
Click to collapse
I've heard of that before but I've never really looked into it much. Do you by any chance have a Skype or a Discord link I could join so I could talk to you more direct?

nulledbyme said:
I've heard of that before but I've never really looked into it much. Do you by any chance have a Skype or a Discord link I could join so I could talk to you more direct?
Click to expand...
Click to collapse
Sorry, I don't. Maybe it's better if you ask for more help in S5 forum on how to go on with this, as I don't own this device myself. I will probably find that thread if you do, and be able to help futher if needed
Otherwise there's plenty of tutorials on how to flash 4-files with odin.
I did find one and uploaded it to mega in case you want to grab it. G900PVPS3CQB3_CSC_SPT_CL10090296_QB12576102_REV00_user_low_ship_MULTI_CERT.tar.zip
I've used those kind of firmwares on various devices for all kind of problems where official firmware wasn't enough to fix it, and it always worked without problems.

tys0n said:
Sorry, I don't. Maybe it's better if you ask for more help in S5 forum on how to go on with this, as I don't own this device myself. I will probably find that thread if you do, and be able to help futher if needed
Otherwise there's plenty of tutorials on how to flash 4-files with odin.
I did find one and uploaded it to mega in case you want to grab it. G900PVPS3CQB3_CSC_SPT_CL10090296_QB12576102_REV00_user_low_ship_MULTI_CERT.tar.zip
I've used those kind of firmwares on various devices for all kind of problems where official firmware wasn't enough to fix it, and it always worked without problems.
Click to expand...
Click to collapse
I'll try that so, with those files I just put them all into Odin?

nulledbyme said:
I'll try that so, with those files I just put them all into Odin?
Click to expand...
Click to collapse
Yes exactly. This is what you'll find once it's unzipped.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
First make sure your battery is well charged (we don't want it to die during flash)
Just put the files in their boxes in odin, connect your phone in download mode and flash.
Hopefully it will now boot past that bootlogo. If not...there must be some hardware problem.

tys0n said:
Yes exactly. This is what you'll find once it's unzipped.
View attachment 4098803
First make sure your battery is well charged (we don't want it to die during flash)
Just put the files in their boxes in odin, connect your phone in download mode and flash.
Hopefully it will now boot past that bootlogo. If not...there must be some hardware problem.
Click to expand...
Click to collapse
Well, it looks like Odin is just sitting at the "aboot.mbn" part of the flashing process :L thoughts?

nulledbyme said:
Well, it looks like Odin is just sitting at the "aboot.mbn" part of the flashing process :L thoughts?
Click to expand...
Click to collapse
It just sits there? No errors? Maybe you should try a different version of odin, like Odin 3.09
You could also try another usb port and/or different cable. Those are the most common problems when flash won't start.

tys0n said:
It just sits there? No errors? Maybe you should try a different version of odin, like Odin 3.09
You could also try another usb port and/or different cable. Those are the most common problems when flash won't start.
Click to expand...
Click to collapse
I'll give those tips a try I'm also trying Samsung Smart Switch to see if it'll do something.

nulledbyme said:
I'll give those tips a try I'm also trying Samsung Smart Switch to see if it'll do something.
Click to expand...
Click to collapse
Yeah you can do that too. Another thing you've reminded me of now when talking about smart switch...Go to your task manager on pc and make sure that no smart switch or kies is running in background before open odin. It may interfere with odin connection.
I remember it was a common problem with kies/odin.

tys0n said:
Yeah you can do that too. Another thing you've reminded me of now when talking about smart switch...Go to your task manager on pc and make sure that no smart switch or kies is running in background before open odin. It may interfere with odin connection.
I remember it was a common problem with kies/odin.
Click to expand...
Click to collapse
I'll try that, I'm still so confused by this. I flash it, and then ODIN says "RESET" in blue, it resets the device and it hangs at the Sprint logo..

nulledbyme said:
I'll try that, I'm still so confused by this. I flash it, and then ODIN says "RESET" in blue, it resets the device and it hangs at the Sprint logo..
Click to expand...
Click to collapse
Yeah, it's a mystery. If it flash and pass without errors it should work. Can't figure out why it doesn't

tys0n said:
Yeah, it's a mystery. If it flash and pass without errors it should work. Can't figure out why it doesn't
Click to expand...
Click to collapse
Well guess what, I ****in fixed it haha. I just reset after the flash and it's working now! Thanks for all your help man!

nulledbyme said:
Well guess what, I ****in fixed it haha. I just reset after the flash and it's working now! Thanks for all your help man!
Click to expand...
Click to collapse
That's awesome! Glad I could help.