[Tutorial] Revert completely to stock state including the flash counter - Galaxy Tab 2 10.1" Android Development

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

Related

[ODIN][UCLB3] UCLB3 Unbrick - Return to stock - Working PIT included

ABOUT
-------------------
This is a package to return your Infuse 4G to a complete stock state with the AT&T UCLB3 Gingerbread release. It includes a PIT file to repartition your phone. Also, this resets the Custom Binary Download counter. Consider this a way to put the phone back to stock or to recover from a soft-brick without going all the way back to Froyo.
There is both a complete stock version and a rooted version below.
PACKAGES
-------------------
Stock UCLB3
UCLB3_Unbrick_1.1.zip
Stock UCLB3 with root
UCLB3_Unbrick_root_1.1.zip
The version with root works exactly like the above version, but adds root. To add CWM recovery to the rooted version, download a custom Gingerbread kernel from HERE or HERE and flash the zImage using SGS Kernel Flasher (found in the Play Store) on the phone. If you go this route for root and CWM, your Custom Binary Download counter will not show any custom binary activity.
INSTALL
-------------------
1.) Download and extract the zip package.
2.) Place phone in download mode.
3.) If needed, install latest Samsung USB drivers by installing Samsung Kies from HERE.
4.) Open the included Odin exe.
5.) If phone is detected, the window under ID:COM will turn yellow.
6.) Click on "PIT" to browse to and select infuse_gb.pit. Make sure that Re-Partition is selected.
7.) Click on "PDA" to browse to and select PDA_UCLB3.tar.md5.
8.) Click on "PHONE" to browse to and select PHONE_UCLB3.tar.md5.
9.) Click on "Start", and allow Odin to flash the phone. Do not unplug or power off the phone until Odin is finished.
10.) When the Odin dialogue reads "PASS!", the phone should reboot into the stock UCLB3 Setup Wizard.
FAQ
-------------------
1.) Should I do a software Factory Reset in settings after flashing this?
In the case that the Setup Wizard does not appear on the first boot, apps from a previous installation are still present, or you have other issues, go to Settings / Privacy and choose "Factory data reset" and then "Reset phone". This will ensure that the phone is completely reset, and that there is nothing left-over from a previous install to cause issues.
2.) I have rainbow distortion in recovery or in the boot animation. How can I get Gingerbread bootloaders to fix this?:
If you have rainbow distortion, you still have Froyo bootloaders. You can download THIS .rar file, extract using 7zip, and flash the tar.md5 package in Odin (use the pda slot). Flashing Gingerbread bootloaders will correct rainbow distortion in recovery and in the boot animation. Only flash these if you are having issues with rainbow distortion, and only if you have had success flashing other, less dangerous items in Odin.
3.) Does this package remove anything from the internal or external sdcard partitions?
This package does not remove anything from your internal or external sdcard partitions, so all of your user files stay on the phone. If you are using this to reset your phone to stock before selling it, etc., you should format personal storage by using options found under Settings / SD card and phone storage.
THANKS
-------------------
gtg465x for earlier unbrick packages and posts on using dd
imnuts for posts on how to create Odin images
Przekret for the Samsung UCLB3 leak
Everyone in the Infuse 4g XDA forum - for everything else
CHANGELOG
-----------------
6/13/2012 - v. 1.1:
Fixed a bug in the initial version of the UCLB3 Unbrick that caused the phone to lose APN settings. After flashing the new version of the UCLB3 Unbrick, the phone now reboots into the Setup Wizard and does not have APN issues. Thank you to hvega11 for the heads up on the bug.
The new version is in a zip archive called UCLB3_Unbrick_1.1.zip and contains a README.txt file with this changelog information. If the zip archive README.txt does not contain this changelog, then you are using the older version. It is suggested that you delete that version and download version 1.1.
If you downloaded and used the initial version, you might have lost APN and carrier settings immediately after flashing. Go to Settings / Privacy and do a factory reset. This will set you back to normal. The new version should not normally require a factory reset after flashing, but a factory reset in settings is suggested if you have any issues.
Nice job, JScott.
You da Odin Man!
Wow, Scott you are "working it" these past weeks, Thank You Sir for your work.
Added to ISET page..thx again
qkster said:
Nice job, JScott.
You da Odin Man!
Click to expand...
Click to collapse
Just trying to add some more options to help folks out. If you like Heimdall one-click, qkster has you covered. Can't do Heimdall or prefer Odin, we've got that too.
bigjoe2675 said:
Added to ISET page..thx again
Click to expand...
Click to collapse
Thanks bigjoe, just tryin' to keep you busy.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
jscott30 said:
Thanks bigjoe, just tryin' to keep you busy. Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Always on the look out for the updates...
Just got off of work and i check xda to find a new port and a lb3 unbrick. I'm quiting work so i don't miss anything tomorrow. Excellent work on this. I'm tickled pink.
Sent from my SAMSUNG-SGH-I997 using xda premium
hey just a heads up I just flashed this and lost apn settings and network operators
hvega11 said:
hey just a heads up I just flashed this and lost apn settings and network operators
Click to expand...
Click to collapse
EDIT: This bug has been fixed, thanks hvega11 for the heads up!
Also, are you on AT&T or something else?
EDIT: Now that I'm on the PC, I can see that you are with AT&T. You can't see all of that in Tapatalk.
att theres just signal bars no att logo no h icon then in settings when you click apn its empty the click on network operators and its grayed out you cant add or change anything at this point
Alright, have you tried doing a factory reset in Settings / Privacy? I'm also going to test again here. Let me know what you get after factory reset, though.
EDIT: Just got finished with another test. I got the exact same behavior. After flashing the UCLB3 Unbrick, the phone had no APN settings or carrier information. After doing a factory reset in Settings / Privacy, all is back to normal. Do that if you haven't, and you'll be good to go.
Thanks for the heads up. I'm taking the file down until we get better results without having to do a factory reset in settings. I think that I know what is causing this.
jscott30 said:
Alright, have you tried doing a factory reset in Settings / Privacy? I'm also going to test again here. Let me know what you get after factory reset, though.
EDIT: Just got finished with another test. I got the exact same behavior. After flashing the UCLB3 Unbrick, the phone had no APN settings or carrier information. After doing a factory reset in Settings / Privacy, all is back to normal. Do that if you haven't, and you'll be good to go.
Thanks for the heads up. I'm taking the file down until we get better results without having to do a factory reset in settings. I think that I know what is causing this.
Click to expand...
Click to collapse
What do you think is causing this?
Occasionally, I also noted that a factory reset is also needed to clear out all other data. I did not noted the APN problem though.
qkster said:
What do you think is causing this?
Occasionally, I also noted that a factory reset is also needed to clear out all other data. I did not noted the APN problem though.
Click to expand...
Click to collapse
Since the PIT file repartitions the phone, the unbrick package has to have a dbdata.rfs file to rewrite that partition. Of course, neither this or the PIT file were included with the Przekret UCLB3 leak, so I dumped both from the phone, and edited the PIT file in a hex editor to remove several extra lines. The PIT file is good to go; I'm pretty sure that the issue lies in when I dumped the dbdata.rfs file from my phone. I live on the side of a mountain, and have very poor reception. I'm going to try to keep my personal settings and environment out of the mix when I dump the dbdata.rfs file. I'm trying a few things, but will let you know for sure after I test a theory.
Thanks jscott for the quick response sorry trying to do a factory reset didn't even cross my mind lol I had already odined back so I didn't get to try it.
Thanks again hvega11 for giving us a heads up about the APN issue / bug in the first version of the UCLB3 Unbrick.
The UCLB3 Unbrick is fixed and good to go. It was the dbdata.rfs file. I needed to dump it right after clearing cache and data (factory reset), and with the phone on the Setup Wizard screen. The tricky part was still having adb access at that point with USB debugging enabled. I remembered that you can wipe data and cache in CWM recovery and still keep USB debugging enabled, so I did that. At reboot, as soon as I saw the Setup Wizard, I got an adb shell and dumped the necessary files.
The phone starts at the Setup Wizard now after using the UCLB3 Unbrick, and doesn't have any APN issues.
EDIT: Version 1.1 has been uploaded. The APN bug has been fixed. This is working 100% for me. I've tested it over and over, and tried many different scenarios coming from ICS and Gingerbread roms. Every time I get a 100% working stock phone at the UCLB3 Setup Wizard.
EDIT 2: The only time that users might have to do a Factory Reset in settings is in the case that apps from a previous install are still present, or if any other issues arise - just to be sure that nothing is left-over from a previous installation. In most cases, the user won't have to do a Factory Reset in settings.
I need as many people as possible to test this and report back that it works. Thanks!
glad you got it fixed ill try it out tonight and report back
I've found that I personally prefer having an unbrick option that has root. So, I've updated the OP with a rooted UCLB3 Unbrick.
To get to CWM recovery from the rooted version: Flash any suitable custom Gingerbread kernel by using SGS Kernel Flasher. Then, it's back to flash, flash, flash, flash, flash, oops, unbrick, flash, flash, flash...
Neat thing is, that by not using download mode to install a custom kernel, the Custom Binary Download counter doesn't show any custom binary activity.
jscott30 said:
I've found that I personally prefer having an unbrick option that has root. So, I've updated the OP with a rooted UCLB3
Click to expand...
Click to collapse
Gotta have Root
{
"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"
}
A Unbrick with root. Very nice. Thank you a hundred times over. I feel like flashing something that i know i shouldn't just so i can use this.
Sent from my MB865 using xda premium

[Q] GS5 won't go back to stock

I have tried all of the below and am still stuck on the Galaxy S5 screen with "set warranty bit : kernel" in yellow at the top left. I've tried the stock firmware from the Samsung mobile site and cannot get it to go back to stock. Every time I go into download mode it still shows custom instead of original. When I've tried to flash the stock kernel I get a md5! binary error. I can get into download mode just fine, but can't get recovery to come up either. If anyone can help I would greatly appreciate it. I've tried everything I've seen in the forums and am very frustrated. My phone hasn't worked since Wednesday night. I'm fairly new at this, but have been doing things I've found in the forums but nothing has worked so far. Can anyone help?? Please....
Everything was fine with the phone until Wednesday when I pulled it out of my pocket and it was stuck on the screen with the kernel message. I think maybe an OTA update came up and somehow it was accepted when the phone was in my pocket. I'm not sure though because it had worked fine earlier that day.
Originally Posted by Joe0113 View Post
Some people seem to be having trouble, so I thought this might help you guys out.
1. DL Odin 3.09
2. DL this stock NCB tar. ----- Here is a faster/better DL mirror! Thanks to @ChaddyPaddy ----- And yet another mirror! Thanks to @roadrunnrr
3. Make a backup of your apps/data (TiBu/Helium/etc). MAKE SURE THE APP/DATA BACKUPS ARE TO YOUR EXT SD CARD!!!
4. Take out your EXT SD Card (if you have one).
5. Flash the stock NCB tar (put it in "AP/PDA" in Odin).
6. Do a factory reset in the stock recovery after you flash the tar (not necessary but deff won't kill ya!).
7. Reboot into Download Mode and make sure it says ROM type= OFFICIAL! If it says custom you will not be able to take the OTA.
8. Reboot, check for the OTA to "ND2" and wait for it to complete.
9. Your baseband and software should now end in ND2. If it does not, then you did something wrong, go back to step 1 and try a redownload, and reflash of stock NCB tar.
10. Re-root.
Also if someone that has SuperSU PRO version, can check if "Survival Mode" works for the GS5, that'd be awesome!
One person tried and said that it does not work.
There is now an Odin flashable tar of 100% stock ND2, no need to even go back to NCB to take it. Just flash the ND2 tar in Odin and you have the full ND2 update!
rleighska said:
I have tried all of the below and am still stuck on the Galaxy S5 screen with "set warranty bit : kernel" in yellow at the top left. I've tried the stock firmware from the Samsung mobile site and cannot get it to go back to stock. Every time I go into download mode it still shows custom instead of original. When I've tried to flash the stock kernel I get a md5! binary error. I can get into download mode just fine, but can't get recovery to come up either. If anyone can help I would greatly appreciate it. I've tried everything I've seen in the forums and am very frustrated. My phone hasn't worked since Wednesday night. I'm fairly new at this, but have been doing things I've found in the forums but nothing has worked so far. Can anyone help?? Please....
Everything was fine with the phone until Wednesday when I pulled it out of my pocket and it was stuck on the screen with the kernel message. I think maybe an OTA update came up and somehow it was accepted when the phone was in my pocket. I'm not sure though because it had worked fine earlier that day.
Originally Posted by Joe0113 View Post
Some people seem to be having trouble, so I thought this might help you guys out.
1. DL Odin 3.09
2. DL this stock NCB tar. ----- Here is a faster/better DL mirror! Thanks to @ChaddyPaddy ----- And yet another mirror! Thanks to @roadrunnrr
3. Make a backup of your apps/data (TiBu/Helium/etc). MAKE SURE THE APP/DATA BACKUPS ARE TO YOUR EXT SD CARD!!!
4. Take out your EXT SD Card (if you have one).
5. Flash the stock NCB tar (put it in "AP/PDA" in Odin).
6. Do a factory reset in the stock recovery after you flash the tar (not necessary but deff won't kill ya!).
7. Reboot into Download Mode and make sure it says ROM type= OFFICIAL! If it says custom you will not be able to take the OTA.
8. Reboot, check for the OTA to "ND2" and wait for it to complete.
9. Your baseband and software should now end in ND2. If it does not, then you did something wrong, go back to step 1 and try a redownload, and reflash of stock NCB tar.
10. Re-root.
Also if someone that has SuperSU PRO version, can check if "Survival Mode" works for the GS5, that'd be awesome!
One person tried and said that it does not work.
There is now an Odin flashable tar of 100% stock ND2, no need to even go back to NCB to take it. Just flash the ND2 tar in Odin and you have the full ND2 update!
Click to expand...
Click to collapse
Many different ways to tackle this 1.) flash recovery via odin, then restore nandroid, 2.) or go to sammobile get stock NCB firmware flash through odin, if you do this no worries it takes you back to complete stock but not rooted, your phone will be exactly the same as it was before restoring to stock...just not rooted lol mouth fullll. then reroot! By the way I don't think the phones can update unless you unroot, so jus flash stock NCB firmware take update then reroot if you want update, Its awesome its like dirty flashing! If you were trying ART instead of Dalvik before your phone took a poop, using ART causes the custom status everytime until you switch back to dalvik. Knox will always be 0x1 if you have rooted your S5 unless you haven't wait for an exploit, which is super not like gonna happen, cause S5 is locked up tighter then Fort Knox!
Iceburn1 said:
Many different ways to tackle this 1.) flash recovery via odin, then restore nandroid, 2.) or go to sammobile get stock NCB firmware flash through odin, if you do this no worries it takes you back to complete stock but not rooted, your phone will be exactly the same as it was before restoring to stock...just not rooted lol mouth fullll. then reroot! By the way I don't think the phones can update unless you unroot, so jus flash stock NCB firmware take update then reroot if you want update, Its awesome its like dirty flashing! If you were trying ART instead of Dalvik before your phone took a poop, using ART causes the custom status everytime until you switch back to dalvik. Knox will always be 0x1 if you have rooted your S5 unless you haven't wait for an exploit, which is super not like gonna happen, cause S5 is locked up tighter then Fort Knox!
Click to expand...
Click to collapse
I did go get the stock NCB firmware from sammobile, flashed through odin and the Samsung Galaxy S5 screen came up with "recovery booting" in blue and then "Set warranty bit: kernel" in yellow right under it. It won't go off of this screen. I can go back to download mode, but if I try recovery mode it goes right back to this screen. So then I flashed a recovery, I was using philz_touch_6.42.6-klte.tar. When this was flashed it want to the Samsung screen but had "set warranty bit: kernel" at the top in yellow. I haven't been able to get past this point as every kernel file I've tried in odin either had a binary error or froze and closed odin. I also tried openrecovery-twrp, and governaa, but had the same outcome with both of those. I haven't once had a problem getting into download mode, but can't get it to go into recovery to even try a backup. Oh, and I've been doing all of this with the sd card taken out of the phone, don't know if that makes a difference or not. I did try it with it in at first, but had no luck there either. The one post I read said it should be taken out, so I figured, what could it hurt? I am beyond frustrated. I'm new to this, this is the first phone that I rooted by myself, but it's my second rooted phone. Previously I had a GS3 and never had this kind of problem with that phone.
Also, how would I tell if I was using ART? Before the phone "died" I was playing a game on it. I closed out of the game, turned off the screen, and put it in my pocket. When I took it out of my pocket about an hour later it was on the Samsung Galaxy S5 screen with set warranty bit: kernel.
I just tried re-flashing the stock firmware and it's currently reading set warranty bit: recovery (in yellow) under the "recovery booting....." (in blue).
recovery
rleighska said:
I did go get the stock NCB firmware from sammobile, flashed through odin and the Samsung Galaxy S5 screen came up with "recovery booting" in blue and then "Set warranty bit: kernel" in yellow right under it. It won't go off of this screen. I can go back to download mode, but if I try recovery mode it goes right back to this screen. So then I flashed a recovery, I was using philz_touch_6.42.6-klte.tar. When this was flashed it want to the Samsung screen but had "set warranty bit: kernel" at the top in yellow. I haven't been able to get past this point as every kernel file I've tried in odin either had a binary error or froze and closed odin. I also tried openrecovery-twrp, and governaa, but had the same outcome with both of those. I haven't once had a problem getting into download mode, but can't get it to go into recovery to even try a backup. Oh, and I've been doing all of this with the sd card taken out of the phone, don't know if that makes a difference or not. I did try it with it in at first, but had no luck there either. The one post I read said it should be taken out, so I figured, what could it hurt? I am beyond frustrated. I'm new to this, this is the first phone that I rooted by myself, but it's my second rooted phone. Previously I had a GS3 and never had this kind of problem with that phone.
Also, how would I tell if I was using ART? Before the phone "died" I was playing a game on it. I closed out of the game, turned off the screen, and put it in my pocket. When I took it out of my pocket about an hour later it was on the Samsung Galaxy S5 screen with set warranty bit: kernel.
I just tried re-flashing the stock firmware and it's currently reading set warranty bit: recovery (in yellow) under the "recovery booting....." (in blue).
Click to expand...
Click to collapse
Did you try to flash recovery bro? Its on a separate partition, if you flash a recovery tar through odin maybe you can restore a nandroid. then go to developer settings in settings check to see if your using art or dalvik
damn need to stop skimming I see you tried, at a loss bro tryin!
Maybe your phone did update and you are using the wrong firmware, could b on nd2?
Did you try to use cf-auto root again just see what happens?
Iceburn1 said:
Many different ways to tackle this 1.) flash recovery via odin, then restore nandroid, 2.) or go to sammobile get stock NCB firmware flash through odin, if you do this no worries it takes you back to complete stock but not rooted, your phone will be exactly the same as it was before restoring to stock...just not rooted lol mouth fullll. then reroot! By the way I don't think the phones can update unless you unroot, so jus flash stock NCB firmware take update then reroot if you want update, Its awesome its like dirty flashing! If you were trying ART instead of Dalvik before your phone took a poop, using ART causes the custom status everytime until you switch back to dalvik. Knox will always be 0x1 if you have rooted your S5 unless you haven't wait for an exploit, which is super not like gonna happen, cause S5 is locked up tighter then Fort Knox!
Click to expand...
Click to collapse
Iceburn1 said:
Did you try to flash recovery bro? Its on a separate partition, if you flash a recovery tar through odin maybe you can restore a nandroid. then go to developer settings in settings check to see if your using art or dalvik
damn need to stop skimming I see you tried, at a loss bro tryin!
Click to expand...
Click to collapse
Any help is appreciated!!! I have no idea what to do next. I've done and re-done everything possible. For whatever reason it won't let me boot into recovery. It just goes straight to the Samsung screen with the warranty bit kernel at the top. I just reflashed the stock firmware and it booted up to the samsung screen showing "recovery booting" and "set warranty bit : recovery" at the top. If I flash a recovery (through odin, the same way I flashed the firmware) it will boot to the same screen, but will say "set warranty bit: kernel" instead, but will not go past that screen. I've tried several recoveries, all of them take me to the same screen when flashed. I feel like I'm in a boot loop myself with the things that I've been trying to get this thing to work.
A friend of mine said when I'm at the point that I'm on the samsung screen with the "set warranty bit: kernel" I should be able to boot to download and flash a stock kernel through odin. I haven't found one kernel file that worked. Every one I've tried either gives a md5 binary error or makes odin freeze and close.
I don't think I was using ART. When I got the phone all I did was root it, didn't even get a good ROM on it yet, but then again, I'm not exactly sure what "ART" is because I'm not 100% familiar with all of the terminology just yet, but I'm learning (or trying to).
At this point all I want to do is get it back to stock and re-root it.
Or, if there was a way to reinstate my warranty with Sprint, I'd take it back to them and get a new one.
s5 fix
Maybe your phone did update and you are using the wrong firmware, could b on nd2?
Did you try to use cf-auto root again just see what happens?
---------- Post added at 02:37 PM ---------- Previous post was at 02:13 PM ----------
Just flash custom recovery then use cf-auto root.
Iceburn1 said:
Maybe your phone did update and you are using the wrong firmware, could b on nd2?
Did you try to use cf-auto root again just see what happens?
---------- Post added at 02:37 PM ---------- Previous post was at 02:13 PM ----------
Just flash custom recovery then use cf-auto root.
Click to expand...
Click to collapse
I reflashed the stock firmware again, flashed philz recovery, and then did cf-auto root and got this...
recovery booting.... (in blue)
recovery is not seandroid enforcing (in red)
set warranty bit: recovery (in yellow)
When I got the phone all I did was root it. How am I able to tell if I'm using ND2 or something else? I can't boot to recovery. I wasn't even trying to update anything on it when it started giving the message set warranty bit: kernel. I was using it, turned the screen off, put it in my pocket for about an hour, and when I took it out it's been stuck on that screen ever since. That was Wednesday. Since then I've tried everything I could find and nothing has worked yet. I'm starting to think that this is un-fixable and now I have a very expensive paperweight. I have a variety of files I've downloaded, so if anyone has any idea, step-by-step what I can do to fix this, I'd be so grateful.
The stock files I got were from Sammobile's site, but I can't seem to get them to work correctly. I flash the stock firmware, then it gives me the set warranty bit recovery message, so I flash recovery (tried twrp, philz, cwm), and then it will boot as far as the Samsung screen, but changes to set warranty bit: kernel. I've tried flashing a new kernel, but can't find any that don't have md5 binary errors or freeze odin. Is there a certain "magic" order of flashing that I should do, like should the firmware be first, then recovery, then kernel (if it'd work), then root? Or firmware, then recovery, root, kernel? I think I've tried every combination imaginable.
xposed installed or gravity?
do you have xposed or gravity installed maybe that's whats causing bootloop, try safe mode. Turn phone off hold down volume down button and restart phone it will reboot into safe mode! uninstall mod.
---------- Post added at 06:21 PM ---------- Previous post was at 06:15 PM ----------
Are you 100% sure you were on ncb, I really want to know I mean as far as it goes now theres no coming back, might as well try to download the stock nd2 file and flash that it wont hurt that update can fix some bigs with phone like cameran stuff and you can still root!
Iceburn1 said:
do you have xposed or gravity installed maybe that's whats causing bootloop, try safe mode. Turn phone off hold down volume down button and restart phone it will reboot into safe mode! uninstall mod.
Click to expand...
Click to collapse
I think I did have xposed installed and gravity come to think of it. I tried holding volume down and power and it went to the samsung screen with:
recovery booting.....
recovery is not seandroid enforcing
set warranty bit : recovery
If I turn off, go back to download mode, flash recovery, let it reboot, it will then still be stuck on the samsung screen, but will have:
set warranty bit: kernel
I have not yet found a kernel that will flash successfully and I can't get it to go into recovery at all, just download. It keeps getting stuck on the samsung screen with either the set warranty bit : recovery, until I flash recovery, then it says set warranty bit : kernel.
Iceburn1 said:
do you have xposed or gravity installed maybe that's whats causing bootloop, try safe mode. Turn phone off hold down volume down button and restart phone it will reboot into safe mode! uninstall mod.
---------- Post added at 06:21 PM ---------- Previous post was at 06:15 PM ----------
Are you 100% sure you were on ncb, I really want to know I mean as far as it goes now theres no coming back, might as well try to download the stock nd2 file and flash that it wont hurt that update can fix some bigs with phone like cameran stuff and you can still root!
Click to expand...
Click to collapse
I'm not sure if I was on ncb or nd2. How do I tell? When I got it I rooted it with CF- auto root, but I didn't do anything else to it that I can recall. I was going to install a rom, but the file wouldn't transfer for me, so I gave up on that until there were other roms to try. The only other thing I did once rooted was download titanium backup, did a backup of everything, downloaded xposed, and was using some of the modules from there. I was using twrp recovery and now I can't get anything to come up that even says twrp.
rleighska said:
I reflashed the stock firmware again, flashed philz recovery, and then did cf-auto root and got this...
recovery booting.... (in blue)
recovery is not seandroid enforcing (in red)
set warranty bit: recovery (in yellow)
When I got the phone all I did was root it. How am I able to tell if I'm using ND2 or something else? I can't boot to recovery. I wasn't even trying to update anything on it when it started giving the message set warranty bit: kernel. I was using it, turned the screen off, put it in my pocket for about an hour, and when I took it out it's been stuck on that screen ever since. That was Wednesday. Since then I've tried everything I could find and nothing has worked yet. I'm starting to think that this is un-fixable and now I have a very expensive paperweight. I have a variety of files I've downloaded, so if anyone has any idea, step-by-step what I can do to fix this, I'd be so grateful.
The stock files I got were from Sammobile's site, but I can't seem to get them to work correctly. I flash the stock firmware, then it gives me the set warranty bit recovery message, so I flash recovery (tried twrp, philz, cwm), and then it will boot as far as the Samsung screen, but changes to set warranty bit: kernel. I've tried flashing a new kernel, but can't find any that don't have md5 binary errors or freeze odin. Is there a certain "magic" order of flashing that I should do, like should the firmware be first, then recovery, then kernel (if it'd work), then root? Or firmware, then recovery, root, kernel? I think I've tried every combination imaginable.
Click to expand...
Click to collapse
Try using another USB. For example if you are using the USB 3.0 then us the 2.0. Reason why is people from the T-mobile variant where having problem flashing files via odin with the USB 3.0. But damn this is one troubling problem
Try using this TAR filehttp://forum.xda-developers.com/showthread.php?t=2737112
Nyc1231 said:
Try using another USB. For example if you are using the USB 3.0 then us the 2.0. Reason why is people from the T-mobile variant where having problem flashing files via odin with the USB 3.0. But damn this is one troubling problem
Try using this TAR filehttp://forum.xda-developers.com/showthread.php?t=2737112
Click to expand...
Click to collapse
I have tried that TAR file, numerous times, same results as previously described. I didn't think to try a different USB cable, was using 3.0 as it came with the phone, but just now switched to the 2.0 and am also getting the same results.
safemode
I had seen you said u held volume down and power button to get into safe mode, you only hold down volume down and hit power button to turn on, let go power button continue hold volume down.
rleighska said:
I have tried that TAR file, numerous times, same results as previously described. I didn't think to try a different USB cable, was using 3.0 as it came with the phone, but just now switched to the 2.0 and am also getting the same results.
Click to expand...
Click to collapse
:crying: Let me give it a search on google and see what i can find.
Still nothing; all i can find is to restore to stock
Nyc1231 said:
:crying: Let me give it a search on google and see what i can find.
Still nothing; all i can find is to restore to stock
Click to expand...
Click to collapse
I'd be thrilled if I could restore to stock. At least then I could start fresh. I tried the method in my very first post on this thread and had no luck with that either.
xposed and gravity
Could b strong possibility that xposed and gravity causing bootloop, i would try n get to safe mode at all costs
Iceburn1 said:
Could b strong possibility that xposed and gravity causing bootloop, i would try n get to safe mode at all costs
Click to expand...
Click to collapse
I can't get it to boot to recovery. When it starts it shows the kernel message at the top in yellow, the samsung logo etc. and will not move from that screen. The only other thing I can do is put it in download mode.
safe mode
Safe mode is different from download and recovery it boots you into phone so u can disable xposed or gravity lossiboy the cause
rleighska said:
I'd be thrilled if I could restore to stock. At least then I could start fresh. I tried the method in my very first post on this thread and had no luck with that either.
Click to expand...
Click to collapse
Have you try using different version of odin when restoring to a stock firmware?
Sent from my SM-G900P using Tapatalk
Iceburn1 said:
I had seen you said u held volume down and power button to get into safe mode, you only hold down volume down and hit power button to turn on, let go power button continue hold volume down.
Click to expand...
Click to collapse
I tried that and it still goes right to the samsung screen with
recovery booting.... in blue
set warranty bit : recovery in yellow

[Q] need help using cwm

Thanks in advance to anyone who can help me. So I'm new to rooting and new to xda, I looked around the forums a bit but am unable to find exactly what I'm looking for. I have a Sprint note 3 smn900p. I successfully rooted it using towelroot and confirmed with root checker. I then downloaded Rom manager and used it to download cwm. Here is where I need help, I boot up my phone and this is what I get. (Volume down, home button, and power)
Odin mode
Smn900p
Samsung official
0x0
0x1 (towelroot did not trip this, it was either RM or CWM)
Qualcom secure boot enable (csb)
Rp swrev s1 t1 a1 a3 p1
Write protection enable
Udc start
At the bottom it says "downloading" and "do not turn off target"
That's where it stays and the only way to get rid of it is to do a battery pull.
Now if I hold volume up, home button, and power this is what it says.
Recovery booting
recovery is not seandroid enforcing
Set warranty bit enforcing.
Phone then starts up normally.
I am trying to do all of this without a computer because I don't always have access but any help at all is appreciated. The main reason I am rooting is to get free wifi tethering for my note 10.1 and after that possibly getting rid of the bloatware and overclocking the cpu.
Again thanks to all the developers and anyone else who makes this possible. You guys (and girls) rock!
nycemt said:
Thanks in advance to anyone who can help me. So I'm new to rooting and new to xda, I looked around the forums a bit but am unable to find exactly what I'm looking for. I have a Sprint note 3 smn900p. I successfully rooted it using towelroot and confirmed with root checker. I then downloaded Rom manager and used it to download cwm. Here is where I need help, I boot up my phone and this is what I get. (Volume down, home button, and power)
Odin mode
Smn900p
Samsung official
0x0
0x1 (towelroot did not trip this, it was either RM or CWM)
Qualcom secure boot enable (csb)
Rp swrev s1 t1 a1 a3 p1
Write protection enable
Udc start
At the bottom it says "downloading" and "do not turn off target"
That's where it stays and the only way to get rid of it is to do a battery pull.
Now if I hold volume up, home button, and power this is what it says.
Recovery booting
recovery is not seandroid enforcing
Set warranty bit enforcing.
Phone then starts up normally.
I am trying to do all of this without a computer because I don't always have access but any help at all is appreciated. The main reason I am rooting is to get free wifi tethering for my note 10.1 and after that possibly getting rid of the bloatware and overclocking the cpu.
Again thanks to all the developers and anyone else who makes this possible. You guys (and girls) rock!
Click to expand...
Click to collapse
You use Volume DOWN+Home+power button to flash firmware by USB using Odin program or restore original firmware using Samsung Kies.
The only way you can exit the Odin mode is remove the battery or after having successfully flash a firmware.
You use Volume UP+Home+power button to enter recovery mode. In recovery, you may be able to perform:
- backup of the entire OS and data of the phone.
- recover from a backup in case you encounter any problem flashing a custom rom, etc.
- perform a full wipe or factory reset
- install custom rom or firmware file saved on phone memory or external SD card.
You may use ROM toolbox to remove unwanted bloatware and overclock or underclock your device.
Please hit thanks if I helped.
But isn't it possible to flash roms/kernels using just your phone? Also when I do hit volume down home and power shouldn't I at least have options from my phone on what to do next, and shouldn't it say something about using cwm? Btw Thanks for the quick reply!
Did you install CWM?
nycemt said:
But isn't it possible to flash roms/kernels using just your phone? Also when I do hit volume down home and power shouldn't I at least have options from my phone on what to do next, and shouldn't it say something about using cwm? Btw Thanks for the quick reply!
Click to expand...
Click to collapse
It's not clear from your post whether your really installed CWM recovery. Use Odin (download mode) to flash tar.gz version of CWM (or TWRP). Search for the links yourself. Then you can enter CWM with vol up+home+power combo.
There on, you can flash any (other) recovery or ROM from phone itself via CWM (or TWRP or Philz).
nycemt said:
But isn't it possible to flash roms/kernels using just your phone? Also when I do hit volume down home and power shouldn't I at least have options from my phone on what to do next, and shouldn't it say something about using cwm? Btw Thanks for the quick reply!
Click to expand...
Click to collapse
Yeah, it is possible to flash ROM using your phone memory or external SD card thru Recovery mode (Vol UP+Home+Power).
I suggest you use [root] Mobile Odin Pro (this can be downloaded on play store) if you want to flash kernel/ROM without going to recovery mode. It is also safer to use than flashing in download mode.
For a more user friendly recovery, try using Team Win Recovery Project (TWRP).
It is touch-based recovery. Easier to use.
Please hit thanks if I helped.
Ok so I'm going to download twrp, if I did in fact download cwm will these interfere with each other. Also once I download twrp do I have to open it on my phone or just flash it through recovery mode or through mobile Odin pro. (Sorry for the basic, probably stupid questions)
nycemt said:
Ok so I'm going to download twrp, if I did in fact download cwm will these interfere with each other. Also once I download twrp do I have to open it on my phone or just flash it through recovery mode or through mobile Odin pro. (Sorry for the basic, probably stupid questions)
Click to expand...
Click to collapse
I flash mine using mobile odin. It will replace CWM.
Download the TAR file save it on your external SD.
Open odin.
Grant superuser request
Open file...
Select TAR file
Flash firmware
Your phone will reboot in recovery.
Ok so I bought Mobile odin pro from the play store now if I want to flash a Kernel to my device I would need to find it on here and then download it correct or I could find a rom with the kernel already on it and flash the whole thing and would I be able to find it on mobile odin or rom toolbox? Thanks again you guys are so helpful taking it baby steps with me.
What I meant on my previous post was I flash my recovery which is TWRP using mobile odin.
I suggest you flash TWRP recovery first using odin. Perform backup in TWRP before flashing any ROM in case anything goes wrong, you may be able to go back to the original state of your device.
nycemt said:
Ok so I bought Mobile odin pro from the play store now if I want to flash a Kernel to my device I would need to find it on here and then download it correct or I could find a rom with the kernel already on it and flash the whole thing and would I be able to find it on mobile odin or rom toolbox? Thanks again you guys are so helpful taking it baby steps with me.
Click to expand...
Click to collapse
defiantly follow the previous reply and backup first (very important).
i personally dont download roms etc from apps. i prefer to find it manually on the forum, so you know you have the correct, most up to date file for your device. also, you can read other users post to get an idea of how its working and the possible problems with it.
Ok sorry I took soo long to respond, work has been busy. So I Bought Wifi Tether Router for $2.50 which is still better than 10 extra dollars a month. It works, granted it takes a long time to start up and im not using the stock tether that is included with the phone which would have been great but it gets the job done and I have no complaints. This was one of the main reasons I wanted to root my phone. Anyway I guess when I have some more time to mess with it I will try flashing roms/kernels (I am just soo afraid of hard bricking my phone) but you guys gave some pretty clear instructions so I don't think I'll have a problem. As soon as I get a chance to do some messing around I will let you guys know how it went. Thanks again hopefully one day I will be able to return the favor.
Ok just double checked and now I need to ask another question. Mobile Odin states that my reactivation lock needs to be turned off but when I go to settings, general, security, there is no option to turn it off. It doesn't even show it in the list. Do I absolutely need to turn it off, would it be somewhere else?
nycemt said:
Ok sorry I took soo long to respond, work has been busy. So I Bought Wifi Tether Router for $2.50 which is still better than 10 extra dollars a month. It works, granted it takes a long time to start up and im not using the stock tether that is included with the phone which would have been great but it gets the job done and I have no complaints. This was one of the main reasons I wanted to root my phone. Anyway I guess when I have some more time to mess with it I will try flashing roms/kernels (I am just soo afraid of hard bricking my phone) but you guys gave some pretty clear instructions so I don't think I'll have a problem. As soon as I get a chance to do some messing around I will let you guys know how it went. Thanks again hopefully one day I will be able to return the favor.
Ok just double checked and now I need to ask another question. Mobile Odin states that my reactivation lock needs to be turned off but when I go to settings, general, security, there is no option to turn it off. It doesn't even show it in the list. Do I absolutely need to turn it off, would it be somewhere else?
Click to expand...
Click to collapse
i don't know. i looked into it and it appears it should be under security, but that was on a s5. maybe your device doesn't have that option.
Do you know what would happen if I backup or flash a rom and the reactivation lock is enabled?
nycemt said:
Do you know what would happen if I backup or flash a rom and the reactivation lock is enabled?
Click to expand...
Click to collapse
i dont know exactly, but through some research it looks like you could run into issues with a custom recovery. i can only assume a rom would be the same.
That really sucks, I'm gonna try and hopefully find a way around it but until then I guess I'm gonna have to wait. Would you happen to know how to check and see if it's activated? (Besides the normal spot in security that it should be)
nycemt said:
That really sucks, I'm gonna try and hopefully find a way around it but until then I guess I'm gonna have to wait. Would you happen to know how to check and see if it's activated? (Besides the normal spot in security that it should be)
Click to expand...
Click to collapse
sorry, i don't know. i had to google search to find the previous information.
What device do you use? Have you enabled this feature (reactivation lock) before? I've made a research that this is an anti-theft feature of galaxy s5 and note 3 which prevents fatory reset of the phone using your samsung acccount when stolen.
I think you don't need to worry about disabling this feature if you never enabled it. I'm using galaxy s3 international version (i9300). And I also don't have this feature. Mobile odin is only reminding you that you should disable reactivation lock (in case you have one) before flashing any rom.
I "guess" reactivation lock enabled will prevent you to format certain partition in your phone since it will be password protected.
I suggest that you use TWRP or CWM when flashing ROMs that are not touchwiz based (Cyanogenmod, AOKP, etc). I only use Mobile odin when flashing recovery and flashing stock firmware. Flashing custom ROMs other than stock, in my opinion, will be safer if you do it in recovery after a backup.
I hope I answered your question.

[GUIDE] How to Restore Stock Firmware Images in All Tab 4 Series: 7.0, 8.0 & 10.1

{
"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"
}
Hello guys, with this guide you can restore Stock Firmware Images for all Galaxy Tab 4 Series.
This is useful to restore firmware in case something goes wrong, if you flash a custom ROM and it fails, or, for example, if Samsung decides to update this devices to Lollipop. For this you also will need stock untouched firmware.​
Pre-requisites:
1) Make a backup of everything you consider important: Apps, photos, music, etc.
2) Download drivers for your specific device from HERE, install the drivers and reboot your PC to apply changes.
3) Download Odin 3.0.9, it is attached below in this post, and extract it.
4) Download the firmware image for your specific device from HERE and extraxt the file inside, it should be a huge 1GB+ size *.tar.md5 file.
5) Make sure your device's battery is at 60% or more.
6) Enable USB Debugging on Settings > General > Developer Options (If you can't find Developer Options menu, go to Settings > General > About Device and tap several times on Build Number, then it will tell you Dev Options is enabled).
Lets start:
1) Run Odin 3.09 as Administrator (in Windows right click on Odin icon and select "Run as Administrator")
2) Turn off your tablet and now turn it on in Download Mode (press Home + Volume Down + Power buttons at the same time until the tablet turns on, then when prompted, press Volume Up button to proceed)
3) Now connect your tablet to PC via USB cable. Odin should show a plugged device and an ADDED! message, like this:
If you can't get Odin to recognise your device, check which drivers you installed or try another USB cable.
4) Make sure that Auto Reboot and F. Reset Time options are selected, like this:
5) Now check the AP option and press the AP button to find and select the firmware image (the *.tar.md5 file you extracted earlier), when you select the image, Odin will check if it has errors. If everything is OK, it should say it succesfully checked it, like this:
6) You are ready to rock, so, hit the START button and wait...
7) Go, watch TV, chat with friends, make a sandwich or play Chess with your cat.
8) Once completed, you will see the Pass! message in ID:COM section, with a green background. Your tablet should auto reboot automatically.
9) Unplug your tablet.
10) Enjoy all the bloatware once again!
Thanks for reading and if you have doubts, let us know in the comments.
Cheers!!!​
Thank You!
Thanks Man! Custom ROMS are fun but it sucks when something is not working right that which was working perfectly in the Stock ROM. Will wait patiently. hope Lollipop comes to SM-T230NU soon
Joelsmarias said:
Thanks Man! Custom ROMS are fun but it sucks when something is not working right that which was working perfectly in the Stock ROM. Will wait patiently. hope Lollipop comes to SM-T230NU soon
Click to expand...
Click to collapse
it come in 6 months (might come tomorrow, after month any time), i promise
Any faster links?
sportscrazed2 said:
Any faster links?
Click to expand...
Click to collapse
Yes, here
Or here if you've got a 7.0
I cannot for the life of me get my tab to stay in download mode while flashing. It makes it as far as a quarter though the system partition then it just reboots back to the "firmware encountered an issue" screen. As far as I know the battery has more than enough if not a full charge!! HEEEEEEELP!!!!
thelous said:
it come in 6 months (might come tomorrow, after month any time), i promise
Click to expand...
Click to collapse
"You promise" and where did you get this information from?
Deejaydark said:
"You promise" and where did you get this information from?
Click to expand...
Click to collapse
Just wait and it will come lol, theres no hardware limitation on tab 4 7,0 so 5.1.1 will fall for us, just wait till samsung makes it or till CM12.1 is ready in xda
Will restore of stock firmware overwrite custom recovery
Hi... just finally got my Tab 4 8.0 rooted by using custom recovery and special kernel. I love having root, but in the event i have to send the tablet in for any kind of warranty repair, i just want to know if simply ODIN flashing the stock 5.1.1 firmware will restore the stock recovery and reset my knox counter and stuff... Any details greatly appreciated!
beatbreakee said:
Hi... just finally got my Tab 4 8.0 rooted by using custom recovery and special kernel. I love having root, but in the event i have to send the tablet in for any kind of warranty repair, i just want to know if simply ODIN flashing the stock 5.1.1 firmware will restore the stock recovery and reset my knox counter and stuff... Any details greatly appreciated!
Click to expand...
Click to collapse
It will definitely restore the stock recovery. Idk about resetting the flash counter, my instinct tells me no but that could be wrong. If worst comes to worst and you do have to send it in under warranty, tell them Kies broke it, that's worked for me and a few of my friends even with the knox counter tripped lmao. And if you want the quickest firmware file downloads, check out this thread. About a 5 minute download versus anywhere from 2-8 hours from any other host (seriously, it's awful).
How can I know when the flash is done?
Thank you for this helpful guide. I used this to upgrade my Samsung Tab 4 8.0 from 4.4.2 KitKat to Lollipop 5.1.1.
May I suggest, OP, adding a note on how to know when the flashing is over. I mistakenly thought that all the boxes on the top half (the row that begins with with a green "Pass" box) would all be colored. But the users should know that the flash is over when you see the green Pass box.
Please see my attached screenshot.
thanks for bringing my tablet back to life!
I played chess with my cat.... and lost. Thank you for this, my Tab has been shut away in shame for a while, and I decided to bring it back out again.
Does anyone know if this will activate knox if I revert to the original firmware? T530NU
Cyntil8ing said:
Does anyone know if this will activate knox if I revert to the original firmware? T530NU
Click to expand...
Click to collapse
From where ?
repey6 said:
From where ?
Click to expand...
Click to collapse
From 5.0.2. Non rooted T530NU. Southern Cellular version.
Cyntil8ing said:
From 5.0.2. Non rooted T530NU. Southern Cellular version.
Click to expand...
Click to collapse
nothing will be
repey6 said:
nothing will be
Click to expand...
Click to collapse
OK thanks. Reverted to stock ROM. It didn't trip knox.
thelous said:
Just wait and it will come lol, theres no hardware limitation on tab 4 7,0 so 5.1.1 will fall for us, just wait till samsung makes it or till CM12.1 is ready in xda
Click to expand...
Click to collapse
Yeah... Right. The t-230nu has less powerful hardware and its 2016 and lolipop hasnt even come.
Pix12 said:
Yeah... Right. The t-230nu has less powerful hardware and its 2016 and lolipop hasnt even come.
Click to expand...
Click to collapse
what ive seen so fsr with 4.4.2 i dont see any reason to change 5.1.1 so its not big deal

Samsung Tab 2 GT-P3100 bootloop and odin fail.

My TAB 2 7.0 was not rooted and was in the bootloop all of a sudden. The issue is when it reboots, it lets me enter lock screen password and when I try to use something - It reboots. I tried to do the Clear cache partition and Factory Reset from android boot menu (power + volume up button) which says that DATA WIPE COMPLETE but when I reboot the tab nothing changes, not even the WIFI connections and their passwords. The WiFi remains on and connected to my router.
I deleted those connection from Settings but again it reboots and all deleted wifi connections (which were successfully deleted) are back with their passwords.
I also tried RESET DEVICE from settings, it asked me for my password but when i entered it and tapped on reset my device option - BOOM! it reboots again without resetting.
I searched a lot on net and tried ODIN option with proper firmware but of no use. And most importantly, I did visit authorized service centre before doing any of these, they returned it after trying couple of time to flash it and asked me to change the motherboard(Which would cost me about the price of good android phone - $120).
Can anybody please suggest me any other option than changing the motherboard (which is way much higher than my budget). The option you suggest may be hardware repair or anything else, I may not be able to get it done myself if it is hardware thing but atleast it will help to search the repair option by precisely telling the guy (technician) - what to do?
I have posted this after i saw mentions online about this forum and experts here, I hope you guys help me out as this TABLET is of great use to me.
:crying:
notsogeeky said:
My TAB 2 7.0 was not rooted and was in the bootloop all of a sudden. The issue is when it reboots, it lets me enter lock screen password and when I try to use something - It reboots. I tried to do the Clear cache partition and Factory Reset from android boot menu (power + volume up button) which says that DATA WIPE COMPLETE but when I reboot the tab nothing changes, not even the WIFI connections and their passwords. The WiFi remains on and connected to my router.
I deleted those connection from Settings but again it reboots and all deleted wifi connections (which were successfully deleted) are back with their passwords.
I also tried RESET DEVICE from settings, it asked me for my password but when i entered it and tapped on reset my device option - BOOM! it reboots again without resetting.
I searched a lot on net and tried ODIN option with proper firmware but of no use. And most importantly, I did visit authorized service centre before doing any of these, they returned it after trying couple of time to flash it and asked me to change the motherboard(Which would cost me about the price of good android phone - $120).
Can anybody please suggest me any other option than changing the motherboard (which is way much higher than my budget). The option you suggest may be hardware repair or anything else, I may not be able to get it done myself if it is hardware thing but atleast it will help to search the repair option by precisely telling the guy (technician) - what to do?
I have posted this after i saw mentions online about this forum and experts here, I hope you guys help me out as this TABLET is of great use to me.
:crying:
Click to expand...
Click to collapse
I never encountered a problem like this before but 2 years screwing with my tab (well bootlooping it with myself) I would suggest rooting it via Odin and Flash TWRP (CWM works too but I prefer TWRP) through odin as well.
After that find a custom ROM, preferably a stable build since you'll be using it for daily use and flash it using TWRP. I would suggest downloading SlimKat or Cyanogen Mod 13 and GAPPS.
You can find a lot of guides (some are step by step) about rooting it through Odin, and flashing TWRP on your tab.
As well as custom ROMS and how to flash it.
Tell me how it goes dude. Goodluck
Edit:
Hmm before flashing custom ROMs, when you try to flash a firmware. Did you make sure that you're using a correct driver for your PC? Samsung Kies does the job but make sure to close Samsung Kies in order to avoid conflicts with Odin. Make sure also to switch your tab to Download Mode when you flash with Odin.
Factory reset but asif nothing happened? I'm sorry but your tab has the dreaded eMMc bug. Only an emmc replacement or a new motherboard can fix it. Sorry.
Sent from my espresso3g using XDA Labs
DeepBricked said:
I never encountered a problem like this before but 2 years screwing with my tab (well bootlooping it with myself) I would suggest rooting it via Odin and Flash TWRP (CWM works too but I prefer TWRP) through odin as well.
After that find a custom ROM, preferably a stable build since you'll be using it for daily use and flash it using TWRP. I would suggest downloading SlimKat or Cyanogen Mod 13 and GAPPS.
You can find a lot of guides (some are step by step) about rooting it through Odin, and flashing TWRP on your tab.
As well as custom ROMS and how to flash it.
Tell me how it goes dude. Goodluck
Edit:
Hmm before flashing custom ROMs, when you try to flash a firmware. Did you make sure that you're using a correct driver for your PC? Samsung Kies does the job but make sure to close Samsung Kies in order to avoid conflicts with Odin. Make sure also to switch your tab to Download Mode when you flash with Odin.
Click to expand...
Click to collapse
Dude, firmware flashing was already tried by the technician at the authorised service center, even he couldnt flash it. I tried flashing as you said. But when i went through all the step by step tutorials on flashing or rooting through odin, they all wanted me to turn on the developers options in settings which I can't. Even if i manage to do that, it will just reverse right away after reboot.
The TWRP thing and rooting through odin that you told me are the options left with me. But I am not familiar with all those things so It would be great if you can share any link about the step by step method.
Lightracer said:
Factory reset but asif nothing happened? I'm sorry but your tab has the dreaded eMMc bug. Only an emmc replacement or a new motherboard can fix it. Sorry.
Sent from my espresso3g using XDA Labs
Click to expand...
Click to collapse
New motherboard is way beyond my budget, so I am left with only one option i.e. eMMC replacement. Is eMMC readily available in the market, if yes then is there any trusted brand or something like that.
notsogeeky said:
New motherboard is way beyond my budget, so I am left with only one option i.e. eMMC replacement. Is eMMC readily available in the market, if yes then is there any trusted brand or something like that.
Click to expand...
Click to collapse
Unfortunately, I am not familiar with eMMc replacement although @Android-Andi does have a friend in Austria who can replace/upgrade it for you according to one of his posts.
Although if you ask me, you're better off buying another more recent tablet.
Sent from my espresso3g using XDA Labs
Lightracer said:
Unfortunately, I am not familiar with eMMc replacement although @Android-Andi does have a friend in Austria who can replace/upgrade it for you according to one of his posts.
Although if you ask me, you're better off buying another more recent tablet.
Sent from my espresso3g using XDA Labs
Click to expand...
Click to collapse
Thanks man. At least now I know what the issue is and what may be the best solution. I am from India so will have to search someone who replaces eMMC here.
It's only 11 screws & 25 bucks (USA) for a motherboard
http://www.ebay.com/itm/like/131488094589
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app

Categories

Resources