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
Related
Hi everyone, I post this tutorial in order to help people (like me) want to revert to stock state, including the "famous" flash counter, and Stock Recovery, in order to install update by official methods.
WARNING
I'm not responsible malfunctions, bricks and other by make these actions.
All actions described were tested by me in the same order in a Galaxy Tab 2 Wifi-only P5110
However, it should work on any Galaxy Tab 2 model.
Requeriments:
You have permission of superuser
Recomendations:
Use Titanium Backup in order to backup your apps & apps data
Step 1:
Install Mobile Odin Pro (by Chainfire. XDA thread: http://forum.xda-developers.com/showthread.php?t=1347899)
and Triangule Away (if your counter's valor isn't zero.) (by Chainfire. XDA thread: http://forum.xda-developers.com/showthread.php?p=22463153
Step 2:
Download a stock firmware from your device:
http://forum.xda-developers.com/showthread.php?t=1704668
UPDATE. Android 4.0.4 avaible now for P5110: http://forum.xda-developers.com/showthread.php?t=1877286
Step 3 (here start the hard work )
Use Triangule Away in order to reset your counter. You will can observe that counter is zero after the process.
Step 4
Copy your stock firmware (unzipped) into your Internal or External Memory.
Open Mobile Odin. When says "Open File..." select memory where you copied and then select the tar.md5 file (I don't support (I don't know) other files)
After that, you can observe a section called Everroot. You have 2 options:
-Check all options if you want preserve root (recommended, although that isn't a "truly" stock state)
-Uncheck all options. You lose root, but you return a truly stock state. However, if you want return the root state, you probably will have to use Odin PC again, returning to a "non-stock" state. In addition, you probably won't have access to your backup from Titanium Backup when the process finish.
For that reason, I recommend check those options, and, if you must send the device to Samsung service, you can reflash a tar.md5 file via MobileOdin and uncheck those options.
Step 5
Check all wipe options
(for any reason, when I did this, I DIDN'T lose any data, but that is not guaranteed. Backup your apps with Titanium Backup)
Step 6
Tap "Flash firmware" and wait until the process finish. Device will reboot automatically.
Remember, Mobile Odin NOT increase your flash counter!!!
And enjoy your device with stock state!!
Don't forget press the :good:"Thanks button" !!!
It should work on every gtab 2 , nice work.
Yes, it should work or any Galaxy Tab 2.
I really hope someone can help. I have a GT-P5113 and have rooted and put CM10 on it. The touch screen is broken now and I need to send it in for warranty (broken as in not working not shattered or cracked) and need help! I can still use the power and volume buttons so getting the new firmware on it isn't the issue, its resetting the flash counter. PLEASE HELP!!!
I think you need usb otg cable (so cheap) ,then connect usb mouse (better) or keyboard ,then download triangle away 1.90 app from market (paid) or xda forums (free) ,then use to reset counter ,then boot to download mode by long press power then reboot/download (better) or power off then volume down+power ,then connect to computer ,then flash stock firmware from www.samfirmwsre.com or so via odin
Sent from Galaxy S2 or Galaxy Tab2
smileygui said:
I really hope someone can help. I have a GT-P5113 and have rooted and put CM10 on it. The touch screen is broken now and I need to send it in for warranty (broken as in not working not shattered or cracked) and need help! I can still use the power and volume buttons so getting the new firmware on it isn't the issue, its resetting the flash counter. PLEASE HELP!!!
Click to expand...
Click to collapse
You can prove this tutorial using a mouse with a USB OTG cable for Galaxy Tab 2. You can buy it on eBay or other online shops.
ok, so I am waiting for my OTG adapter to get here to try that out and hopefully that works for getting back to stock. Here is my next big question. I am going to try to send this back to samsung for warranty because the touch screen doesn't work and the lcd is very dark along the left side from top to bottom. I was removing dust that somehow got caught between the front glass and the lcd and in doing so i cut the ribbon cable for the digitizer. (lcd was already really dark before hand, that is a factory defect) being that one would have to cut the seal to see that, is that something that samsung would be able to know? I've reassembled the tablet and you would never even know it was apart, i didn't see any void stickers or even watermark stickers. any thoughts?
Anybody? Please?
smileygui said:
Anybody? Please?
Click to expand...
Click to collapse
Even if they find it they probably won't care. This is from experience with Samsung phones and them not really giving a crap. They'll probably send you a refurb with no questions asked. Can't hurt to try, anyways.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Just did this successfully on a P5113 with CM10, using Mobile Odin Lite.
It was "stuck" on the boot logo, so I went into recovery and wiped data, and now it seems fine.
smileygui said:
ok, so I am waiting for my OTG adapter to get here to try that out and hopefully that works for getting back to stock. Here is my next big question. I am going to try to send this back to samsung for warranty because the touch screen doesn't work and the lcd is very dark along the left side from top to bottom. I was removing dust that somehow got caught between the front glass and the lcd and in doing so i cut the ribbon cable for the digitizer. (lcd was already really dark before hand, that is a factory defect) being that one would have to cut the seal to see that, is that something that samsung would be able to know? I've reassembled the tablet and you would never even know it was apart, i didn't see any void stickers or even watermark stickers. any thoughts?
Click to expand...
Click to collapse
The only thing you can do is try sending it in for warranty. Bte, you can just flash the stock rom via Odin using a laptop or desktop. Flashing stock does not increase your counter.
frankdrey said:
Just did this successfully on a P5113 with CM10, using Mobile Odin Lite.
It was "stuck" on the boot logo, so I went into recovery and wiped data, and now it seems fine.
Click to expand...
Click to collapse
mine too. P5100 with CM10.1. also using Mobile Odin lite. Also stuck on boot logo. Wipe data n factory reset done. back to stock...
:laugh::laugh::good::good:
If I only wanted to reset my flash counter but I am running CM10.1 on my GT-P5113, triangle away will work correct? Or would I expect problems after resetting counter? Tab is running perfect, just want to fix counter
Edit: so I got a response for this in the thread for the CM10.1 nightly build and TA is safe for my device/rom combination.. So I ran TA, and after I run, it went from 10 to 0. Perfect, rebooted into DL mode, and it says 1.. Relaunched TA, sure enough, it said 1 again, so I reran, it says 0, but when I reboot, I should expect to see 1 again? (I thought I remembered reading that it would do this, but didn't remember where, I reread this OP)
This is after using TA to reset the flash counter from 10 to 0, notice it says "0" and "Official binary":
{
"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"
}
This is after only rebooting, nothing else was done, its like a kernel gets flashed on reboot:
I have a jig too, and I just got some converters to "adjust" the USB port configuration.. I'm thinking about plugging in the usb that came with my tab, converting the reg USB (male) to micro USB (female) and then plugging in the jig. The only thing I would need to know though is if the jigs are device dependant and os version dependant.. (After thinking about it, in order to actually use the jig on an E4GT, I have to restore it to EL26 or 29..) So I guess it prolly won't work on a GT-P5113.. :/
sj
Sent from my pimped out E4GT on WftN_CM10.1 - 1/25 with [email protected] Pro 2.4.10
sjsharksfan420 said:
If I only wanted to reset my flash counter but I am running CM10.1 on my GT-P5113, triangle away will work correct? Or would I expect problems after resetting counter? Tab is running perfect, just want to fix counter
Edit: so I got a response for this in the thread for the CM10.1 nightly build and TA is safe for my device/rom combination.. So I ran TA, and after I run, it went from 10 to 0. Perfect, rebooted into DL mode, and it says 1.. Relaunched TA, sure enough, it said 1 again, so I reran, it says 0, but when I reboot, I should expect to see 1 again? (I thought I remembered reading that it would do this, but didn't remember where, I reread this OP)
This is after using TA to reset the flash counter from 10 to 0, notice it says "0" and "Official binary":
This is after only rebooting, nothing else was done, its like a kernel gets flashed on reboot:
I have a jig too, and I just got some converters to "adjust" the USB port configuration.. I'm thinking about plugging in the usb that came with my tab, converting the reg USB (male) to micro USB (female) and then plugging in the jig. The only thing I would need to know though is if the jigs are device dependant and os version dependant.. (After thinking about it, in order to actually use the jig on an E4GT, I have to restore it to EL26 or 29..) So I guess it prolly won't work on a GT-P5113.. :/
sj
Sent from my pimped out E4GT on WftN_CM10.1 - 1/25 with [email protected] Pro 2.4.10
Click to expand...
Click to collapse
It's because you have a custom rom and recovery
It detects that and bumps up the counter to 1
Sent from my GT-P5110 using Tapatalk HD
frankdrey said:
It's because you have a custom rom and recovery
It detects that and bumps up the counter to 1
Sent from my GT-P5110 using Tapatalk HD
Click to expand...
Click to collapse
Thanks for the post.. I just wanted to be sure I wasent missing something.. if that's expected as the outcome due to my rom/recovery configuration, then I totally understand
sj
Sent from my PimpedOut GT-P5113 on CM10.1 - 1/28 Nightly using [email protected] Pro 2.4.10
chapitron said:
Hi everyone, I post this tutorial in order to help people (like me) want to revert to stock state, including the "famous" flash counter, and Stock Recovery, in order to install update by official methods.
WARNING
I'm not responsible malfunctions, bricks and other by make these actions.
All actions described were tested by me in the same order in a Galaxy Tab 2 Wifi-only P5110
However, it should work on any Galaxy Tab 2 model.
Requeriments:
You have permission of superuser
Recomendations:
Use Titanium Backup in order to backup your apps & apps data
Step 1:
Install Mobile Odin Pro (by Chainfire. XDA thread: http://forum.xda-developers.com/showthread.php?t=1347899)
and Triangule Away (if your counter's valor isn't zero.) (by Chainfire. XDA thread: http://forum.xda-developers.com/showthread.php?p=22463153
Step 2:
Download a stock firmware from your device:
http://forum.xda-developers.com/showthread.php?t=1704668
UPDATE. Android 4.0.4 avaible now for P5110: http://forum.xda-developers.com/showthread.php?t=1877286
Step 3 (here start the hard work )
Use Triangule Away in order to reset your counter. You will can observe that counter is zero after the process.
Step 4
Copy your stock firmware (unzipped) into your Internal or External Memory.
Open Mobile Odin. When says "Open File..." select memory where you copied and then select the tar.md5 file (I don't support (I don't know) other files)
After that, you can observe a section called Everroot. You have 2 options:
-Check all options if you want preserve root (recommended, although that isn't a "truly" stock state)
-Uncheck all options. You lose root, but you return a truly stock state. However, if you want return the root state, you probably will have to use Odin PC again, returning to a "non-stock" state. In addition, you probably won't have access to your backup from Titanium Backup when the process finish.
For that reason, I recommend check those options, and, if you must send the device to Samsung service, you can reflash a tar.md5 file via MobileOdin and uncheck those options.
Step 5
Check all wipe options
(for any reason, when I did this, I DIDN'T lose any data, but that is not guaranteed. Backup your apps with Titanium Backup)
Step 6
Tap "Flash firmware" and wait until the process finish. Device will reboot automatically.
Remember, Mobile Odin NOT increase your flash counter!!!
And enjoy your device with stock state!!
Don't forget press the :good:"Thanks button" !!!
Click to expand...
Click to collapse
That's great to restore stock state for P5110.
chapitron said:
Step 1:
Install Mobile Odin Pro (by Chainfire. XDA thread: http://forum.xda-developers.com/showthread.php?t=1347899)
and Triangule Away (if your counter's valor isn't zero.) (by Chainfire. XDA thread: http://forum.xda-developers.com/showthread.php?p=22463153
Step 2:
Download a stock firmware from your device:
http://forum.xda-developers.com/showthread.php?t=1704668
UPDATE. Android 4.0.4 avaible now for P5110: http://forum.xda-developers.com/showthread.php?t=1877286
Step 3 (here start the hard work )
Use Triangule Away in order to reset your counter. You will can observe that counter is zero after the process.
Step 4
Copy your stock firmware (unzipped) into your Internal or External Memory.
Open Mobile Odin. When says "Open File..." select memory where you copied and then select the tar.md5 file (I don't support (I don't know) other files)
After that, you can observe a section called Everroot. You have 2 options:
-Check all options if you want preserve root (recommended, although that isn't a "truly" stock state)
-Uncheck all options. You lose root, but you return a truly stock state. However, if you want return the root state, you probably will have to use Odin PC again, returning to a "non-stock" state. In addition, you probably won't have access to your backup from Titanium Backup when the process finish.
For that reason, I recommend check those options, and, if you must send the device to Samsung service, you can reflash a tar.md5 file via MobileOdin and uncheck those options.
Step 5
Check all wipe options
(for any reason, when I did this, I DIDN'T lose any data, but that is not guaranteed. Backup your apps with Titanium Backup)
Step 6
Tap "Flash firmware" and wait until the process finish. Device will reboot automatically.
Click to expand...
Click to collapse
Hi, i tried to return to stock with your Tutorial (thanks btw) but it didnt work for me. I configured MobileOdin and taped "flash firmware", everything went very fast and the GalaxyTab2 Bootlogo appeared. A few seconds later there is the blue Mobile Odin Logo and on the left side of the screen it says "Wipe.....done flash.....done, kernel....done its too fast to read any word exactly and then: BOP - Samsung Bootlogo again and again mobile odin and again Bootlogo and so on. CWM doesnt work anymore but Odin-Mode (Download-Mode?) still works.
Is it possible to flash the stock rom with Odin PC in Odin-Mode on my tablet? And is it possible that i downlaoded the wrong Stock-Rom? Im from Germany, using a P5110 and downloaded this one: P5110XWALD2 (4.0.3) - Netherlands April 2012 (Official).
pls help if somebody can help
thanks in advance
edit: ok first i'll try the 4.0.4 Stockrom from the first post via Odin on PC, see if it works...
edit2: WORKS! Even if no one helped (no reproach!): thank you guys, i appreciate your work and time you all are spending for ous!! This is the greatest community
Flash count question
frankdrey said:
Just did this successfully on a P5113 with CM10, using Mobile Odin Lite.
It was "stuck" on the boot logo, so I went into recovery and wiped data, and now it seems fine.
Click to expand...
Click to collapse
I was wondering, and probably a noob question. Does the flash count increase when installing official Samsungs update OTA? Such as from 4.0.4 to 4.1.1?
BrooklynSpartan said:
I was wondering, and probably a noob question. Does the flash count increase when installing official Samsungs update OTA? Such as from 4.0.4 to 4.1.1?
Click to expand...
Click to collapse
No...OTA is official...flash official ROM using Odin also will not increase your binary....as long its official..its good to go...cheers...
Done!
I followed the steps, and was able to go from CWM recovery + CM10.1 to full stock.
Only issue was after it flashed, the boot sequence continued (samsung logo) in infinite loop without responding to any key press, off switch etc. Finally I removed the micro-sd card and tried, it rebooted, now it works fine! Had some tense moments..was that step required? when it is on infinite reboot loop, what is the correct way to reset?
Everything works fine or seems to..thanks very much. The counter too showed zero after I reset it. Now when I go to download mode, dont see any counter stat.
BTW, if the Device status message shows NORMAL that means the counter is zero?
Tks
DDLF2 Full (PIT,BOOTLOADER,PDA,PHONE,CSC) Orignal Firmware.
Imported From Samsung Service Center Directly, Ultra Compressed 200 MB Only Uploaded By Me "Sgatechwork". :good: :laugh: :victory: Enjoy ... Don't forget PRESS "THANKS BUTTON" :good: :good:
You Can Directly Flash This On your i9003 no need to flash any thing before this. Because its a full pack firmware.
For cm 10 10.1 or any other based on these if you are from india or if you want your baseband Version to I9003DDLE1 Than just download modem.zip (ultra Compressed) from attachment Extract zip take modem.bin and push it in /radio 0664 which is rw-rw-r--
Like this
{
"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"
}
Download Only Modem.bin View attachment modem.zip
Resumable Links
Download Now
Mirror
Mirror Download
Edit:
Confirmation
Installation instructions:
1:Turn Off Your Phone
2ress Vol Down+Home + Power Until Downloading Screen Comes...
3:Than Start Loading Files in
Code:
PIT =latona_20110114.pit
Bootloader =APBOOT_I9003DDLF2_CL1153545_REV08_user_low_ship.tar.md5
PDA=CODE_I9003DDLF2_CL1153545_REV08_user_low_ship.tar.md5
Phone=MODEM_I9003DDLE1_REV_00_CL1149304.tar.md5
CSC=GT-I9003-MULTI-CSC-ODDLF2_RST.tar.md5
For CF Root Open Odin 1.85 Load Only PDA=DDLF2-CFROOT-30-06-2012.tar
For Root And ClockWorkMode Recovery
CF Root LF2 (PDA only with Odin) Download Download CF Root Link
Download Odin 1.85 Download Now
Than Check Box Re-Partition Auto Reboot F.Reset Time Phone Bootloader Update Than Press Start When it says PASS In a green Box wait Till reboot is done than remove the cable enjoy...
Does this mean that we can flash DDLF2 directly instead of starting from xxkpe as this new uploaded firmware contain all necessary files??
probably. but still a confirmation would be great.
Sent from my GT-I9003 using xda app-developers app
Yeeh does that mean full clean begin from it .. We need confirm about these thing ..
Thanks very much ..
Sent from my GT-I9003 using xda premium
Tested.Works like a charm.And yes it makes a full wipe.
I suggest you add a guide on how to flash this if its proven that this does not need xxkpe to start with. This is really great. Flashaholic members will no longer have a hard time doing a clean flash.
---------- Post added at 07:47 AM ---------- Previous post was at 07:46 AM ----------
devilhell007 said:
Tested.Works like a charm.And yes it makes a full wipe.
Click to expand...
Click to collapse
You flashed directly? Wow. Have you included the bootloader? your from what base rom?
marshygeek said:
I suggest you add a guide on how to flash this if its proven that this does not need xxkpe to start with. This is really great. Flashaholic members will no longer have a hard time doing a clean flash.
---------- Post added at 07:47 AM ---------- Previous post was at 07:46 AM ----------
You flashed directly? Wow. Have you included the bootloader? your from what base rom?
Click to expand...
Click to collapse
Yeah I flashed it directly.I did not include the bootloader.Iwas on CM 10.1 Alpha 4.Just wanted to make a clean install so tested it.
devilhell007 said:
Yeah I flashed it directly.I did not include the bootloader.Iwas on CM 10.1 Alpha 4.Just wanted to make a clean install so tested it.
Click to expand...
Click to collapse
Great news! :thumbup:
Thanks a lot for the confirmation!
Sent from my GT-I9003.
Good news bro
easy clean now !!!
Tested just now I will review all the installation instructions thank you for this easy clean
With Odin 1.85
- Full LF2 reset odin then remove cable and battery after bootanimation
PIT =latona_20110114.pit
Bootloader =APBOOT_I9003DDLF2_CL1153545_REV08_user_low_ship.tar.md5
PDA=CODE_I9003DDLF2_CL1153545_REV08_user_low_ship.tar.md5
Phone=MODEM_I9003DDLE1_REV_00_CL1149304.tar.md5
CSC=GT-I9003-MULTI-CSC-ODDLF2_RST.tar.md5
Click to expand...
Click to collapse
- CF LF2 (PDA only with Odin) reset odin then remove cable and battery after bootanimation
- jellymystery A4 reboot automatic recovery works fine now !!!
- jellymystery A4 again with new recovery
- Wip cache and dalvik cache
time of need to put this topic in post-it
can you add link CFroot LF2 also
- CF Root LF2 (PDA only with Odin)
enjoy...
thanks bro :good:
thanks.
using xwlf2 as a base (eastern europe), but I guess that will do
I never checked "Phone Bootloader Update" in Odin. Is it necessary for this full DDLF2 ?
Currently I'm using same old DDLF2 over XXKPE method without using "Phone Bootloader Update" option
Please confirm.
yes bootloader no need after froyo
just for froyo upgrade (to GB HONEY ISC JB uses the same bootloader) no need updating this !!!
it is even not recommended to put bootloader because it is often responsible for Brick
Bootloader is the first step in flash, if you have a conflict on your computer
avoid process, samsung kies, adb, antivirus internet security software and others scan stuff before flash !!!
@LoLaTiOn!
That what i thought so and read everywhere but was bit confused about checking that option. Thanks! for confirming
I would like to go back to GB from Jb only because of the battery.
Im currently in Qwerty
can someone post every single step in a noob (me) friendly way,please?
From what i've read:
1) you need odin 1.85 installed on your pc
2)Start the phone while pressing Vol down+home+power to start in download mode (these has to be with the phone connected to the pc via usb cable or you can plug it in later?)
3)Fill every file category with the corresponding file in odin.
4)Check Box Re-Partition Auto Reboot F.Reset Time Phone Bootloader Update
5)Press Start
7)When it says PASS In a green Box wait Till reboot is done ....
8)thee remove usb cable from phone
Am i missing something? devilhell007 says that you dont need the bootloader file? Is this file necessary only with certains roms? which roms would that be?
and finally, i've read that some roms, change the file system of the phone, and returning to stock bricks it, does this method prevents and reverts that?
sorry for the noobish questions, big thanks in advance!
Load all the files as i mentioned... and flash it... than after paas ur done...
Sent from my GT-I9003 using xda premium
felaipes said:
I would like to go back to GB from Jb only because of the battery.
Im currently in Qwerty
can someone post every single step in a noob (me) friendly way,please?
From what i've read:
1) you need odin 1.85 installed on your pc
2)Start the phone while pressing Vol down+home+power to start in download mode (these has to be with the phone connected to the pc via usb cable or you can plug it in later?)
3)Fill every file category with the corresponding file in odin.
4)Check Box Re-Partition Auto Reboot F.Reset Time Phone Bootloader Update
5)Press Start
7)When it says PASS In a green Box wait Till reboot is done ....
8)thee remove usb cable from phone
Am i missing something? devilhell007 says that you dont need the bootloader file? Is this file necessary only with certains roms? which roms would that be?
and finally, i've read that some roms, change the file system of the phone, and returning to stock bricks it, does this method prevents and reverts that?
sorry for the noobish questions, big thanks in advance!
Click to expand...
Click to collapse
LoLaTiOn said:
yes bootloader no need after froyo
just for froyo upgrade (to GB HONEY ISC JB uses the same bootloader) no need updating this !!!
it is even not recommended to put bootloader because it is often responsible for Brick
Bootloader is the first step in flash, if you have a conflict on your computer
avoid process, samsung kies, adb, antivirus internet security software and others scan stuff before flash !!!
Click to expand...
Click to collapse
As you can see LoLaTiOn said the same thing.
And bootloader might even brick your phone.So please refrain from doing so.
I hav no idea about it in samsung service center offically.. they use all the files to flash including bootloader even me my self always flashed my phone with all files never bricked... infact with my previous phone i always used bootloader and all files... els u c
Sent from my GT-I9003 using xda premium
the first galaxysl and comes with froyo
That is why we must put the bootloader for an upgrade to gingerbread
after the upgrading not a time of need for clean
understand all ?
if a person is on froyo and does not put the bootloader it will encounter a bootloop only ^^
i totally understand and agreed with you
LoLaTiOn said:
the first galaxysl and comes with froyo
That is why we must put the bootloader for an upgrade to gingerbread
after the upgrading not a time of need for clean
understand all ?
if a person is on froyo and does not put the bootloader it will encounter a bootloop only ^^
Click to expand...
Click to collapse
i totally understand and agreed with you but i am just saying what Samsung engineers thought to there service center technicians and instructed to do as per proper procedure, load all the files and flash it they do this for all the device any Samsung phone down grade up grade or same reflash they do the same sorry if am wrong but am just saying in the official way rest all on us...
This is reserved for W8 only! If you have any other model, this will not work
Whats different from the other other upgrade threads? This one doesn't block you from going back to 4.3, it allows you to retain knox 0x0 and it's safe.
Just tried this, worked perfectly. I came from X-Note 7.0 and did this on my friends Note 3 and he was on stock. I already had knox 0x1 but i was alble to keep his at 0x0.
As of now, this has only been tested on W8 model as it takes the files from the Telcel firmware (mexico). You can use this method on any W8 model, the only thing you will have to change is substitute my modem (CP) by the modem from the latest 4.3 firmware of your carrier. It seems as the MD5 from all modems for all canadian carriers match exactly, so the model for rogers also applies to Bell and Telus
If you are coming from a non-canadian W8, you can extract your modem directly from stock firmware. Here is how:
This is just an example on how to extract a modem from a stock firmware:
Use winrar to:
1- extract firmware downloaded on sammobile.com or other (please use latest firmware), should output an MD5 file.
2- Rename that file from xxxxxxxxxxxxxxx.tar.md5 to xxxxxxxxxxxxxxxxx.tar
3- extract .tar firmware and locate modem.bin file
4- compress the modem.bin, it should give you a modem.zip
5- rename that modem.zip to modem.tar
6- You not have your flashable odin modem
Click to expand...
Click to collapse
Upgrading to Kit Kat and downgrading back to 4.3 does not trip knox, and rooting using my instructions either. Be sure to turn off reactivation lock before flashing this. This method gives you an easy way to official 4.4.2, once you're there, you can flash any 4.4 rom.
Also, and this is an important factor for a lot of people, this doesn't block you from going back to 4.3. If ever you want to go back to Jelly Bean 4.3, just flash back to it via ODIN
Download all the files, PIT, BL, AP. CP and CSC, the flash via ODIN 3.09. Then flash CF-Root and CWM if you wish. I did not check re-partition in ODIN, it worked for both of my Notes, most users didn't check it either, but a small few said the flash failed until they checked re-partition, either way, it should not brick your device.
Here are the links to the files:
PIT: http://pc.cd/K7H (MD5: e2dba603c963443660b369e04b07d574)
BL: http://pc.cd/gXH (MD5: 1bce2f5a137901e2fb206379d3e7ae11)
AP: http://pc.cd/7kH (MD5: 08443eb20702a975fc0be85f7e9c439d)
CSC (this one is for Canada only, if you have any other carrier please download yours): http://www.mediafire.com/download/xn11kh614eag7ir/Canadian+Multi+CSC.tar
(MD5: beae61ca1628b303657c40e14cac3fb6)
CP: http://www.mediafire.com/download/1oias85eoz8ykuh/Rogers+Modem+(CP).tar (MD5: 45522799eb027108fa1c493cbd83abf5)
ODIN: http://uploaded.net/file/hwtdrpll
CF-Root: http://download.chainfire.eu/352/CF-Root1/CF-Auto-Root-hlte-hltexx-smn9005.zip?retrieve_file=1 Don't use included ODIN in CF-Root, use 3.09 and flash via AP
CWM: http://d-h.st/gb3 (MD5: 31e4a86b58837ba87bfa1bf2073371db)
{
"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"
}
Enjoy!
Thanks to Oogar for a more complete version of this process. This method does break WiFi and NFC so head over to his thread for the patch and a proper thanks
I can confirm after testing this a few times on the N9005 that it is only working on the N900w8.
radicalisto said:
I can confirm after testing this a few times on the N9005 that it is only working on the N900w8.
Click to expand...
Click to collapse
That's too bad, but at least there are other ways for you guys!
There will be a way around it I think, especially as the w8 can do it. Shows it's possible somehow
radicalisto said:
There will be a way around it I think, especially as the w8 can do it. Shows it's possible somehow
Click to expand...
Click to collapse
is there any official 9005 firmware? I saw today that besides poland, russia also got the firmware which is exynos based, also deployment in eastern europe is under way, can't we apply this method to the 9005?
Only the .pl firmware currently, status on sammobile shows AFG (Afghanistan) region is pending apparently, so I expect a wide roll out any time soon.
radicalisto said:
Only the .pl firmware currently, status on sammobile shows AFG (Afghanistan) region is pending apparently, so I expect a wide roll out any time soon.
Click to expand...
Click to collapse
in that case, can we apply this method and substitute the mexican files for the polish ones? It seems technically possible
polish_pat said:
Whats different from the other other upgrade threads? This one doesn't block you from going back to 4.3 and it's safe.
Just tried this, worked perfectly. I came from X-Note 7.0 and did this on my friends Note 3 and he was on stock.
As of now, this has only been tested on W8 model as it takes the files from the Telcel firmware (mexico). You can use this method on any W8 model, the only thing you will have to change is substitute my modem (CP) by the modem from the latest 4.3 firmware of your carrier. You can take the official tar file and extract the modem.bin and re-zip it back to a tar file and use that.
This does not trip knox, be sure to turn off reactivation lock before flashing this. This method gives you an easy way to official 4.4.2, once you're there, you can flash any 4.4 rom.
Also, and this is an important factor for a lot of people, this doesn't block you from going back to 4.3. If ever you want to go back to Jelly Bean 4.3, just flash back to it via ODIN
Enjoy!
Click to expand...
Click to collapse
Rogers user here. Stock. To clarify.
Can I flash these files and well be in 4.4.2? Without tripping Knox? And can go back to 4.3?
Will this reset my phone?or will my data and apps still be intact?
Sent from my SM-N900W8 using Tapatalk
Canadoc said:
Rogers user here. Stock. To clarify.
Can I flash these files and well be in 4.4.2? Without tripping Knox? And can go back to 4.3?
Will this reset my phone?or will my data and apps still be intact?
Sent from my SM-N900W8 using Tapatalk
Click to expand...
Click to collapse
I hope you,re kidding for this "Can I flash these files and well be in 4.4.2? Without tripping Knox? And can go back to 4.3?" If you were not able to confirm this information while reading the OP, i'm not sure anything else but a drawing will help you. No offence
And as for your last question, yes, your phone will be wiped clean
Well I was under impression that flagging would upgrade the bootloader from which you couldn't go back.
Also wanted to be sure the included files were good for Rogers without me needing to separately including my own modem
Sent from my SM-N900W8 using Tapatalk
Canadoc said:
Well I was under impression that flagging would upgrade the bootloader from which you couldn't go back.
Also wanted to be sure the included files were good for Rogers without me needing to separately including my own modem
Sent from my SM-N900W8 using Tapatalk
Click to expand...
Click to collapse
Yes, you're good to go! Enjoy
EDIT: also for anybody wondering, i was able to revert back to 4.3, i actually screwed up the rooting process, i used the ODIN included in zip from chainfires site instead of ODIN 3.09 and it gave me bootloop, so i tried to revert back to 4.3 using ODIN 3.09 and it worked. I'm going back to kitkat now
Do you cause a wipe? Cause I am not ripped so have no backup. Unless you know how to root and preserve knox
Sent from my LG-V500 using Tapatalk
Canadoc said:
Do you cause a wipe? Cause I am not ripped so have no backup. Unless you know how to root and preserve knox
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
I'm not sure i understand what you want, i dont know what causing wipe or being ripped means unless you're talking about muscular mass, but i can tell you there is no way of doing this process, or any other and not wiping the device.
polish_pat said:
in that case, can we apply this method and substitute the mexican files for the polish ones? It seems technically possible
Click to expand...
Click to collapse
I tried, but it just bootlooped for me. Was slightly afraid to force the BL incase I hard bricked it. However I may try again today at some point.
Normally flashing am update leaves your data intact. All I am asking is whether fleshing this will effectively factory reset my phone.
If so,,if I root before and don't trip knox, will I be able to flash this with mobile Odin and preserve root with tripping knox.
Sent from my LG-V500 using Tapatalk
Canadoc said:
Normally flashing am update leaves your data intact. All I am asking is whether fleshing this will effectively factory reset my phone.
If so,,if I root before and don't trip knox, will I be able to flash this with mobile Odin and preserve root with tripping knox.
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
This wipes your phone, call ir how you want, factory reset, format, restore, your data, root and everything else is GONE
polish_pat said:
in that case, can we apply this method and substitute the mexican files for the polish ones? It seems technically possible
Click to expand...
Click to collapse
OK so... I just done this again and whatever I done this time around must have differed from last time Because I just Hard Bricked big style :silly: - My advice is no one try this on N9005 -- Now for the fun of restoring life to my device or playing the dopey card with my retailer! :good:
And fixed. no defeating me!!
Sent from my SM-N9005 using XDA Premium 4 mobile app
radicalisto said:
OK so... I just done this again and whatever I done this time around must have differed from last time Because I just Hard Bricked big style :silly: - My advice is no one try this on N9005 -- Now for the fun of restoring life to my device or playing the dopey card with my retailer! :good:
Click to expand...
Click to collapse
radicalisto said:
And fixed. no defeating me!!
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
How did you unbrick a hard brick?
The SDcard image method?
I was under the impression that that one doesn't work on the N9005
radicalisto said:
And fixed. no defeating me!!
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I doubt you were hard bricked if you got out of it that easily. There are two experiences devs that hard bricked their phone, by hard brick, i mean no power or screen whatsoever, no download mode or recovery, NOTHING. They tried a few methods (micro SD and motherboard shortcut method) and both ended up servicing their phone by samsung.
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.
Hey everyone,
Please bare with me, I haven't rooted a phone (using Chainfire's work with a custom stock rom) in over 3 years and I'm once again new at this.
Yesterday I flashed a stock rom (using Odin) to my S7 SM-G930W8 to downgrade from nougat back to Marshmallow 6.0.1 (G930W8VLU2APK3 , (carrier: Koodo), Canada). Now I want to root it (I know, I'll have to redo the whole process but while I have a fresh backup copy, why not) especially because of the software updates nagging. I haven't found any G930W8 root files, only G930F, and while some people say "Oh, just go ahead, doesn't matter", I just want further advice on if I should really use G930F even if my current model is G930W8. I don'T wanna mess anything with my carrier (like unable to place calls, or my IMEI numbers not showing up or anything uncool (yes, I know that my warranty will most probably be void but if it's "just" that, I can live with that)).
So, any advice ?
isnull said:
Hey everyone,
Please bare with me, I haven't rooted a phone (using Chainfire's work with a custom stock rom) in over 3 years and I'm once again new at this.
Yesterday I flashed a stock rom (using Odin) to my S7 SM-G930W8 to downgrade from nougat back to lollipop 6.0.1 (G930W8VLU2APK3 , (carrier: Koodo), Canada). Now I want to root it (I know, I'll have to redo the whole process but while I have a fresh backup copy, why not) especially because of the software updates nagging. I haven't found any G930W8 root files, only G930F, and while some people say "Oh, just go ahead, doesn't matter", I just want further advice on if I should really use G930F even if my current model is G930W8. I don'T wanna mess anything with my carrier (like unable to place calls, or my IMEI numbers not showing up or anything uncool (yes, I know that my warranty will most probably be void but if it's "just" that, I can live with that)).
So, any advice ?
Click to expand...
Click to collapse
Hi mate
Yes it does work in all Exynos variants
Check this confirmation from an user in Chainfire thread
https://forum.xda-developers.com/showpost.php?p=65982420&postcount=83
Just follow the steps as it was a G930F
MAX 404 said:
Hi mate
Yes it does work in all Exynos variants
Check this confirmation from an user in Chainfire thread
https://forum.xda-developers.com/showpost.php?p=65982420&postcount=83
Just follow the steps as it was a G930F
Click to expand...
Click to collapse
Hi, thanks for your quick reply !
But how do I know mine is not snapdragon and is exynos? Does W8 at the end imply it'S a exynos cpu ?
isnull said:
Hi, thanks for your quick reply !
But how do I know mine is not snapdragon and is exynos? Does W8 at the end imply it'S a exynos cpu ?
Click to expand...
Click to collapse
Hi
yes W8 model comes with a Exynos chipset......but you can always double check with an app like PhoneInfo
MAX 404 said:
Hi
yes W8 model comes with a Exynos chipset......but you can always double check with an app like PhoneInfo
Click to expand...
Click to collapse
Oh, thanks, neat little app. And yeah, exynos indeed:
screenshot
isnull said:
Oh, thanks, neat little app. And yeah, exynos indeed:
Click to expand...
Click to collapse
Great..now read.....and go for it
CF autoroot only works on MM in N you need to flash TWRP and then SuperSU-v2.79-SR3
MAX 404 said:
Great..now read.....and go for it
CF autoroot only works on MM in N you need to flash TWRP and then SuperSU-v2.79-SR3
Click to expand...
Click to collapse
1 - Did you mean only works on Marshmallow but that in Nougat you need TWRP ? (sorry to ask)
2 - Doing MM (and reinstalling MM) anyway (I just realized I had mistakenly typed "lollipop" in my opening question, I meant MM)
3 - Just downloaded "CF-Auto-Root-herolte-heroltexx-smg930f.zip", is it normal it's just 35 MB ? I was expecting something like ~2 GB, which would contain the modded (rooted) stock firmware
And yeah, I think I'll have more reading to do than I thought
isnull said:
1 - Did you mean only works on Marshmallow but that in Nougat you need TWRP ? (sorry to ask)
2 - Doing MM (and reinstalling MM) anyway (I just realized I had mistakenly typed "lollipop" in my opening question, I meant MM)
3 - Just downloaded "CF-Auto-Root-herolte-heroltexx-smg930f.zip", is it normal it's just 35 MB ? I was expecting something like ~2 GB, which would contain the modded (rooted) stock firmware
And yeah, I think I'll have more reading to do than I thought
Click to expand...
Click to collapse
Hi
1 That is right
2 I thought so...
3 Yes 35MB is about right ....is not the whole rom is only patching some modifying
MAX 404 said:
Yes 35MB is about right ....is not the whole rom is only patching some modifying
Click to expand...
Click to collapse
Oh cool, thanks! Is there any comprehensible guide here (or anywhere) for this? Like is it's just a patch if I load it in Odin's AP or BP or whatever... (not specified in Chainfire's post) ? I'm willing to read a 24 hour long paper if I need to
isnull said:
Oh cool, thanks! Is there any comprehensible guide here (or anywhere) for this? Like is it's just a patch if I load it in Odin's AP or BP or whatever... (not specified in Chainfire's post) ? I'm willing to read a 24 hour long paper if I need to
Click to expand...
Click to collapse
Ok , get your reading glasses out....
This is the official post....
https://forum.xda-developers.com/galaxy-s7/development/sm-g930-exynos-cf-auto-root-t3337353
And here the instructions for CF Autoroot
ODIN flashable devices
BASIC INSTRUCTIONS
All downloads contain .tar.md5 files flashable in ODIN as PDA.
Make sure your device is in ODIN download mode (usually you can get there by holding VolDown+Home+Power when the device is turned off), then start the included Odin3-v1.85.exe file, press the PDA button, select the .tar.md5 file, and click Start. You can find more detailed instructions and assistance at XDA.
A modified recovery and cache partition will be flashed, which will install (only) SuperSU, then clean-up the cache partition and re-flash the stock recovery.
For the root to work, the device must reboot into recovery. Most devices will do this automatically after flashing these files, but in case that does not happen, please boot into recovery manually.
UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !
Extract from here
https://autoroot.chainfire.eu/
MAX 404 said:
Ok , get your reading glasses out....
This is the official post....
https://forum.xda-developers.com/galaxy-s7/development/sm-g930-exynos-cf-auto-root-t3337353
And here the instructions for CF Autoroot
ODIN flashable devices
BASIC INSTRUCTIONS
All downloads contain .tar.md5 files flashable in ODIN as PDA.
Make sure your device is in ODIN download mode (usually you can get there by holding VolDown+Home+Power when the device is turned off), then start the included Odin3-v1.85.exe file, press the PDA button, select the .tar.md5 file, and click Start. You can find more detailed instructions and assistance at XDA.
A modified recovery and cache partition will be flashed, which will install (only) SuperSU, then clean-up the cache partition and re-flash the stock recovery.
For the root to work, the device must reboot into recovery. Most devices will do this automatically after flashing these files, but in case that does not happen, please boot into recovery manually.
UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !
Extract from here
https://autoroot.chainfire.eu/
Click to expand...
Click to collapse
Wow, thanks so much!
Quick question: once I'm flashed & rooted (when everything's been successful), can I turn off "OEM Lock" or do I leave it on?
isnull said:
Wow, thanks so much!
Quick question: once I'm flashed & rooted (when everything's been successful), can I turn off "OEM Lock" or do I leave it on?
Click to expand...
Click to collapse
Up to you mate......mine is in unlock position
MAX 404 said:
Up to you mate......mine is in unlock position
Click to expand...
Click to collapse
Oh cool, thanks. Think I'm ready now, will post a screenshot when I'm done, after re-reading a couple of things (Samsung Pay (which I don't use anyway), etc). You've been a huge help!
MAX 404 said:
Up to you mate......mine is in unlock position
Click to expand...
Click to collapse
It worked! Hell yeah. Thanks again! I'm def' gonna donate to Chainfire, this was rather easy
{
"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"
}
isnull said:
It worked! Hell yeah. Thanks again! I'm def' gonna donate to Chainfire, this was rather easy
Click to expand...
Click to collapse
Yeah he deserve it !!!
Cool mate glad for you.
@MAX 404
Is it normal when I wipe cache partition now I get a red text saying "dm-verity verification failed" ? I just Googled it and some say it's because I might have flashed an incompatible ROM before rooting but I for sure flashed a compatible one. Otherwise, does it even matter whether it says that or not?
Also, unrelated, I tried a trick to quit having software updates (firmware by Samsung) by clicking on the FotaAgent and "installing" it (doesn't actually install it, in /system/priv-apps/ (going by memory here, might be mistaken) but then I had the nagging "Unfortunately, Software Update has stopped" message a couple of times in a row on each boot or every time I turn on Wi-fi. I then tried fixing THAT by disabling DiagMonAgent through BK Disabler, but that now gives me a message (on boot up) saying "All apps associated with this action have been blocked, disabled or uninstalled". Not the end of the world but still, is there a way to end all this? I was thinking re-flashing the ROM (stock) but I'm hoping there's another solution.
Just in case someone was going to reply to this here, I moved the "Software update" question here since it's a whole other story.
isnull said:
@MAX 404
Is it normal when I wipe cache partition now I get a red text saying "dm-verity verification failed" ? I just Googled it and some say it's because I might have flashed an incompatible ROM before rooting but I for sure flashed a compatible one. Otherwise, does it even matter whether it says that or not?
Also, unrelated, I tried a trick to quit having software updates (firmware by Samsung) by clicking on the FotaAgent and "installing" it (doesn't actually install it, in /system/priv-apps/ (going by memory here, might be mistaken) but then I had the nagging "Unfortunately, Software Update has stopped" message a couple of times in a row on each boot or every time I turn on Wi-fi. I then tried fixing THAT by disabling DiagMonAgent through BK Disabler, but that now gives me a message (on boot up) saying "All apps associated with this action have been blocked, disabled or uninstalled". Not the end of the world but still, is there a way to end all this? I was thinking re-flashing the ROM (stock) but I'm hoping there's another solution.
Click to expand...
Click to collapse
Hi
Regarding Dm-Verity ,, is a message that detects that the sytem is not 100% original , is easy to solve if you have a custom recovery installed then you can flash a dm-verity and force encryption disabler zip. without a custom recovery is a little harder... but if it is not giving you any trouble let it be....
Regarding the software update issue ..no idea how to solve it , never had that problem..sorry only thing i can think of is to re flash rom...BTW once you are rooted ther will not be updates for your device....OTA check your binary status if is not original...there is no OTA
MAX 404 said:
Hi
Regarding Dm-Verity ,, is a message that detects that the sytem is not 100% original , is easy to solve if you have a custom recovery installed then you can flash a dm-verity and force encryption disabler zip. without a custom recovery is a little harder... but if it is not giving you any trouble let it be....
Regarding the software update issue ..no idea how to solve it , never had that problem..sorry only thing i can think of is to re flash rom...BTW once you are rooted ther will not be updates for your device....OTA check your binary status if is not original...there is no OTA
Click to expand...
Click to collapse
Thanks for taking the time. Oh, I see, so from what I understand the dm-verity is not really an issue. Thanks for the tip on the custom recovery. But from what you know (doesn't have to be exact), even if I have the capability (say with twrp) do I really need to flash the dm-verity & force encryption disabler? Or is it for those who are just nagged by the small text when they're in recovery mode?
It's REALLY GOOD to know about the OTA not pushing through or by push-notifications if rooted, next time I flash it (still didn't have time to get around it) I'll just root it directly after and nevermind all the steps to deactivate the firmware updates, thanks!
isnull said:
Thanks for taking the time. Oh, I see, so from what I understand the dm-verity is not really an issue. Thanks for the tip on the custom recovery. But from what you know (doesn't have to be exact), even if I have the capability (say with twrp) do I really need to flash the dm-verity & force encryption disabler? Or is it for those who are just nagged by the small text when they're in recovery mode?
It's REALLY GOOD to know about the OTA not pushing through or by push-notifications if rooted, next time I flash it (still didn't have time to get around it) I'll just root it directly after and nevermind all the steps to deactivate the firmware updates, thanks!
Click to expand...
Click to collapse
Hi mate
If your only modification to the system is just root and you do not notice any thing strange let it be do not flash dm verity zip , that error is caused by a "flag" set by the kernel as far as i know it should not be a problem , actually latest SuperSu should take care of it also