Database Info

Factory Reset after Upgrade?

I own a GT-P6200L and upgraded to the Samsung GT-P6200 Austrian ICS via Odin. Everything including wi-fi works well except for the occasional random reboot.
I've connected to Kies to see what would happen and it says that my unit "cannot be upgraded via Kies", so it doesn't like my upgrade via Odin.
What happens if I need to "factory reset" for any reason? How about if an "official" upgrade comes for my 6200L? Can I factory reset and then upgrade? Or should I just leave well enough alone?

If you would like to make a "factory reset"there are no problems..... Finally, in order to be able to update without problems with the tool journal Samsung there is a requirement that many neglect themselves and to which do not lend themselves never attention.
Kies allows you to install updates only if the firmware currently installed on the device coincides with the one provided for your Product Code...Another fundamental element in order to complete the procedure for updating the Galaxy is to have a firmware entirely original.
If you have on your phone a test version, root permissions enabled or a modified kernel installed (e.s. , CF-Root) will be unable to update.
Kies in fact, in these cases will not be able to recognize the correct version of the software installed on the Galaxy.

devid801 said:
If you would like to make a "factory reset"there are no problems..... Finally, in order to be able to update without problems with the tool journal Samsung there is a requirement that many neglect themselves and to which do not lend themselves never attention.
Kies allows you to install updates only if the firmware currently installed on the device coincides with the one provided for your Product Code...Another fundamental element in order to complete the procedure for updating the Galaxy is to have a firmware entirely original.
If you have on your phone a test version, root permissions enabled or a modified kernel installed (e.s. , CF-Root) will be unable to update.
Kies in fact, in these cases will not be able to recognize the correct version of the software installed on the Galaxy.
Click to expand...
Click to collapse
Thanks for your response. Why do I hear about folks bricking their units on a factory reset? Is it just rooted machines only? Because I have not rooted, simply upgraded to the "incorrect" version of ICS...

I performed a factory reset and I have not bricking my tablet......ICS 4.0.4

I wonder if samsung really detects if we have control of root permissions or if it marks our firmware as "dirty“ after manual flashing any kind of zip package using recovery(as our method for rooting).
Sent from my MB525 using Tapatalk 2

devid801 said:
I performed a factory reset and I have not bricking my tablet......ICS 4.0.4
Click to expand...
Click to collapse
So, you had Honeycomb as standard on the tab, then you upgraded to ICS via Odin, then you did a factory reset to Honeycomb? And everything went well going back to your original Honeycomb?
Is that correct?

scottb4u said:
So, you had Honeycomb as standard on the tab, then you upgraded to ICS via Odin, then you did a factory reset to Honeycomb? And everything went well going back to your original Honeycomb?
Is that correct?
Click to expand...
Click to collapse
It will not reset the device back to Honeycomb. It just resets the device with ICS still installed.

k_t_b said:
It will not reset the device back to Honeycomb. It just resets the device with ICS still installed.
Click to expand...
Click to collapse
what does it reset to? when upgrading to ICS via Odin, it kept my apps, etc. So what does it reset to?

[Completed] Problems when updating a previously rooted Nvidia Shield Tablet

As many of you may know, Nvidia has recalled their Shield Tablets. I'll be getting a replacement soon. I'll be rooting it as soon as possible when I get it, but first I have a few questions.
First of all, I rooted my tablet using a guide at IBTimes (that used info from XDA forums) installing CWM recovery.
After rooting I installed Link2SD, pretty much the reason I rooted, to save up some space on my internal memory. Everything was going fine, until I received the recall notice. I moved all my app files back to the internal memory, deleted Link2SD, ran a full unroot on SuperSU, (after a while of hanging on the "Please Wait" screen the app just crashed, it wouldn't load up and Root Checker said I had no root access after rebooting.
I don't know whether this was supposed to happen or whether it should have gone more smoothly, please give me an answer to this and tell me if it affected my system in any way) and fastboot flashed the stock recovery.img.
However when I tried to install the update, I got a red triangle error. After checking the log I got an error saying "Package expects build fingerprint of ... or ..., this device has ...."
I can't remember what the fingerprints were, but the first one was something that began with "nvidia/", had a bunch of numbers in the middle followed by an underscore, then it ended with "/release-keys".
However the device's current build fingerprint was exactly the same as the first, except that it cut off halfway through, right after the numbers and the underscore.
I tried resetting my cache, I tried a wipe of the user data. The only way to fix this for me was to re-install a bunch of stock images - recovery.img, boot.img, system.img, etc.
I don't want to wipe my data next time. So I ask for this in my answer:
- An explanation of what the error means
- How this error is caused
- A way to fix this error without wiping my device
- How to prevent this error
- If what happened to SuperSU in my case is normal and if it affected my device in some way
- And, if possible, a way to install the update successfully without getting this error and without having to unroot or remove CWM, and details on how to do this method and any risks.
Thanks in advance. An answer soon would be appreciated.

Hi there,
You'd be best served asking for help from the experts who own your device here:
Shield Tablet Q&A, Help & Troubleshooting
Good luck

F***ed up badly, now downloading factory rom, need help to continue

Hi guys, I just registered @ xda because it looks like it's the only serious and feedback active community available. In 10 minutes I found most of the info I was looking for, but I still want to make sure what Im planning to do is fine before I mess up again. Here's the issue:
I was fooling around with the tablet and had just rooted it so I could get rid of some bloatware, and decided to go further and install cyanogen, just for the looks. So I got this thing cm-10.1-20130411-EXPERIMENTAL-p3110-M3 from the official site, which was I put on a folder inside the tablets storage (not on the 16gb SDcard it had in it). I downloaded Rom Manager and skipped through the "search and download rom" and went for the option of looking for it inside the SD card. I had the Backup options and the wipe cache and data ON.
So I proceeded and it booted, started to do the backup and at some final point it had an error, something like "could not backup Data!". I had the options of rebooting, some other stuff and the option of installing a rom from the SD Card. I went for it and searched for the .zip inside the storage, and installed it. It did it withouth trouble, and when it finishd it prompted me to install an update, which I didn't (don't know why).
Then, I went for the reeboot option and when it started I get the normal samsung's black screen with the device's name on it, but then I get a fast glitching image that sweeps through the screen and the cyanogen startup logo which gets stuck for ever.
Click to expand...
Click to collapse
Now Im past it, I can get to download or recovery mode, so I moved onto getting the original firmware so I can clean-install again. I got it from sammobile, chose the one belonging to Chile (that's where I got the tablet), and it's 729mb of data. The tablet is a Samsung Galaxy Tab 2 7.0 P3110
If I flash it with Odin will everything be fine? All I have to do is that thing in downloadmode when I rooted it, but with that 729mb file? Should I put it in the external SD or is it more convenient to place it in the internal storage?
I appreciate your help in advance, I know this is as basic as it gets but messing up again would cost me dearly, since I have to do other stuff.

forum.xda-developers.com/showthread.php?t=1900055 read here, all the information you will need.
It's fine to flash through odin, you will back at stock provided you don't overlook small details and do exactly like the way it is shown. Don't worry, Don't panic. Just be careful to use the files meant for your device only. Second be extra careful when you are dealing with kernel file, pit file or reparation in odin in future.
Third, get root and custom recovery,twrp.
Fourth, after your device start running take backup from twrp recovery. That will save you from most of the trouble.
Most of the details and instructions are already here

billysam said:
forum.xda-developers.com/showthread.php?t=1900055 read here, all the information you will need.
It's fine to flash through odin, you will back at stock provided you don't overlook small details and do exactly like the way it is shown. Don't worry, Don't panic. Just be careful to use the files meant for your device only. Second be extra careful when you are dealing with kernel file, pit file or reparation in odin in future.
Third, get root and custom recovery,twrp.
Fourth, after your device start running take backup from twrp recovery. That will save you from most of the trouble.
Most of the details and instructions are already here
Click to expand...
Click to collapse
hey thanks a lot, im feeling better ow. There's just one issue left: I cant download the original firmware (it's 699mb, and the download keeps stopping midway through it). What happens if I go into clockwork recovery mode and do a factory reset? would that bring me to the original OS? Im kinda scared of downloading an erroneous file again.
EDIT: im doing a factory reset and then flashing this rom called AOSP Project Android 5.1.1 Lollipop on Samsung Galaxy Tab 2 7.0 P3110 which is a 161mb file. Will that work?

aguscanzani said:
hey thanks a lot, im feeling better ow. There's just one issue left: I cant download the original firmware (it's 699mb, and the download keeps stopping midway through it). What happens if I go into clockwork recovery mode and do a factory reset? would that bring me to the original OS? Im kinda scared of downloading an erroneous file again.
EDIT: im doing a factory reset and then flashing this rom called AOSP Project Android 5.1.1 Lollipop on Samsung Galaxy Tab 2 7.0 P3110 which is a 161mb file. Will that work?
Click to expand...
Click to collapse
Factory reset is just clearing data and cache, if you have made changes in kernel or system, factory reset won't reset them, in your case, system has been altered so you will have to format system, then flash the new rom. If you were on jelly bean stock, you are good to flash it.

billysam said:
Factory reset is just clearing data and cache, if you have made changes in kernel or system, factory reset won't reset them, in your case, system has been altered so you will have to format system, then flash the new rom. If you were on jelly bean stock, you are good to flash it.
Click to expand...
Click to collapse
You guys have helped me a lot. I've worked everything out and now i've got to reinstalling android on it, AOSP's 5.1.1 Lollipop. It's beautiful. There's just one problem: Since it came with no apps at all, I wanted to install everything on it again. Problem is, when I go to google play, it shows that i've already got my apps installed, so it wont let me download them, and it doesn't matter if I place the APK's inside the tablet as there's no manager to open them. Even if I download apk's through the tablet's own web browser, it says it can't open the file. Any ideas on this?

[HELP] Phone keeps rebooting, factory reset and odin flash fail

Hi,
My sister has a GT-P3100, since last week the phone keeps rebooting randomly after 3 - 5 minutes most often there are also an error message about Google Play Services or other services has stopped. The phone has Samsung stock Android 4.1.2 XSE and this is the latest firmware as per Samsung website. No root nor custom firmware.
I noticed something weird also, any change made to the settings or apps are reverted back upon reboot. For example, if I set up a WiFi setting, the setting will be gone after reboot. The phone has a number of unread SMS messages too, if I read these messages all of them will become unread again after reboot.
I tried to do factory reset from within the Android setting, it did not work . Everything still intact after reboot.
I tried to do factory reset from Recovery mode, it did not work too. Nothing gets wiped out.
I tried to flash the same firmware using Odin, the NAND write was going on till about 50-55% then it failed. When I rebooted the phone after this failed flash, the phone still has everything intact. No change at all as far as I can see.
Could somebody please help to fix this issue?

dvn2008 said:
Hi,
My sister has a GT-P3100, since last week the phone keeps rebooting randomly after 3 - 5 minutes most often there are also an error message about Google Play Services or other services has stopped. The phone has Samsung stock Android 4.1.2 XSE and this is the latest firmware as per Samsung website. No root nor custom firmware.
I noticed something weird also, any change made to the settings or apps are reverted back upon reboot. For example, if I set up a WiFi setting, the setting will be gone after reboot. The phone has a number of unread SMS messages too, if I read these messages all of them will become unread again after reboot.
I tried to do factory reset from within the Android setting, it did not work . Everything still intact after reboot.
I tried to do factory reset from Recovery mode, it did not work too. Nothing gets wiped out.
I tried to flash the same firmware using Odin, the NAND write was going on till about 50-55% then it failed. When I rebooted the phone after this failed flash, the phone still has everything intact. No change at all as far as I can see.
Could somebody please help to fix this issue?
Click to expand...
Click to collapse
Symptoms are of the emmc card bug. Will need hardware intervention. No flashing files will solve this. Get it to the repair shop, they will either replace the motherboard or will get a replacement of the emmc chip.
This is the reason no samsung tab 2 series is safe if they are on a stock rom.
I feel they have better chance on custom rom as with newer roms, this bug doesn't create a problem.

billysam said:
Symptoms are of the emmc card bug. Will need hardware intervention. No flashing files will solve this. Get it to the repair shop, they will either replace the motherboard or will get a replacement of the emmc chip.
This is the reason no samsung tab 2 series is safe if they are on a stock rom.
I feel they have better chance on custom rom as with newer roms, this bug doesn't create a problem.
Click to expand...
Click to collapse
tough luck, the warranty is no more
I had Samsung Galaxy Note 2 that bricked due to emmc bug too.. I did not know this bug affected other Samsung phones/tablets
If I managed to get the emmc chip replaced, will the bug reoccurs?
Thanks for the info

A Standard Update Put my Phone into a Reboot Loop? Why? But it does Unlock.

Galaxy s8 on Verizon, a standard update notice kept appearing past few days, finally installed it. The minute it finished, it is now in an endless restarting loop. The phone does unlock and show my homescreen. I can get into it, but I only get about 10 seconds to do stuff then it freezes/restarts. Tried Clear Partition Cache in the recovery mode. Tried Safe Mode. No luck.
When I rush over to Settings>Software Update, and click it, it says "Software update in progress"....so it makes me think it is the remnants of the new software update completing itself, and that causes the rebooting. The final stages perhaps? Is there a way to CEASE that the second I unlock my phone? To stop all the background stuff.
Or maybe wouldnt make a difference. Any ideas besides factory reset? Way to revert back?
Wanted to backup a few recent pictures first.

A factory reset is the last resort to fix this.
Maybe it's theme related. Try toggling the button layout (settings -> display -> navigation bar) a couple of times.
If you have substratum installed, try disabling it.
If you want to back up your pictures;
Have you tried accessing the phone using a computer? Either just through a file explorer or by using ADB? To use ADB, you may need to get into settings -developer mode

I tried plugging into a computer, but I only have about 10 seconds, so I dont get enough time to access the files. I get into the phone drive on windows Samsung Galaxy>DCIM> CAMERA> ...then it reboots.
Developer mode is already enabled. Can ADB be used while on the recovery mode screen? I can access that command line looking screen as long as needed.
But accessing the phone normally like turning it on and unlocking the screen would not work, I would keep losing the connection when it reboots.

halfhumble said:
Galaxy s8 on Verizon, a standard update notice kept appearing past few days, finally installed it. The minute it finished, it is now in an endless restarting loop. The phone does unlock and show my homescreen. I can get into it, but I only get about 10 seconds to do stuff then it freezes/restarts. Tried Clear Partition Cache in the recovery mode. Tried Safe Mode. No luck.
When I rush over to Settings>Software Update, and click it, it says "Software update in progress"....so it makes me think it is the remnants of the new software update completing itself, and that causes the rebooting. The final stages perhaps? Is there a way to CEASE that the second I unlock my phone? To stop all the background stuff.
Or maybe wouldnt make a difference. Any ideas besides factory reset? Way to revert back?
Wanted to backup a few recent pictures first.
Click to expand...
Click to collapse
Try downloading that same version of Odin flashable stock firmware from the internet, the same version as the update that you received, then flash that via Odin. As long as the update does not upgrade your bootloader or your binary, it will not wipe your user data(pics).
But first....
If you can get to the homescreen and unlock the device, don't touch anything else once the device opens, just connect it to PC and retrieve your photos from the internal storage, then factory reset the device.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Try downloading that same version of Odin flashable stock firmware from the internet, the same version as the update that you received, then flash that via Odin. As long as the update does not upgrade your bootloader or your binary, it will not wipe your user data(pics).
Click to expand...
Click to collapse
I dont know what version the update was that caused it or how I would find out. But I ended up getting it fixed.
I just downloaded the most recent version firmware from SamFW.com, and used that one. The First flash, the phone was worse! It was now stuck at the samsung logo looping. I flashed it a second time, then it worked! Phone back to normal and backed up my pictures. I had used the home CSC file too, and none of my user data was wiped. I thought it was supposed to wipe that, got lucky
I assume once that OTA update comes back and tries to install, I may have this problem all over again. I can't go forever without the security updates.
Droidriven said:
If you can get to the homescreen and unlock the device, don't touch anything else once the device opens, just connect it to PC and retrieve your photos from the internal storage, then factory reset the device.
Click to expand...
Click to collapse
^
I had tried that a couple times, it lasts about 15 seconds then restarts. Not enough time, I would get to the DCIM folder but before pics loaded, it froze and restarted.

halfhumble said:
I dont know what version the update was that caused it or how I would find out. But I ended up getting it fixed.
I just downloaded the most recent version firmware from SamFW.com, and used that one. The First flash, the phone was worse! It was now stuck at the samsung logo looping. I flashed it a second time, then it worked! Phone back to normal and backed up my pictures. I had used the home CSC file too, and none of my user data was wiped. I thought it was supposed to wipe that, got lucky
I assume once that OTA update comes back and tries to install, I may have this problem all over again. I can't go forever without the security updates.
^
I had tried that a couple times, it lasts about 15 seconds then restarts. Not enough time, I would get to the DCIM folder but before pics loaded, it froze and restarted.
Click to expand...
Click to collapse
The most recent version that you downloaded might be the same update. The OTA updates and the Odin flashable updates are the same thing, the OTA update is just more automated. Flashing the same version as the OTA update via Odin, yields the same results. I think the Home CSC is the one that doesn't wipe user data. I think the Home CSC is intended for users that intend on keeping the device and using it in the same region/network and the other CSC is intended for users that want to sell the device or use the device in a different region or if you have a custom ROM and custom recovery on the device and you want to restore to stock. I could be wrong though.
If you do get a prompt for an OTA update, backup your data then factory reset the device then allow the device to update. That should prevent any further issues with updating via OTA.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
The most recent version that you downloaded might be the same update. The OTA updates and the Odin flashable updates are the same thing, the OTA update is just more automated. Flashing the same version as the OTA update via Odin, yields the same results. I think the Home CSC is the one that doesn't wipe user data. I think the Home CSC is intended for users that intend on keeping the device and using it in the same region/network and the other CSC is intended for users that want to sell the device or use the device in a different region. I could be wrong though.
If you do get a prompt for an OTA update, backup your data then factory reset the device then allow the device to update. That should prevent any further issues with updating via OTA.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Okay, I see.
Well when the phone did boot back up normally after the 2nd flash, there was a pop up that said software update unsuccessful. So I'm not sure if the same OTA update actually updated per se. But yeah, next time Im ready, I've got everything backed up!
Thanks so much!

halfhumble said:
Okay, I see.
Well when the phone did boot back up normally after the 2nd flash, there was a pop up that said software update unsuccessful. So I'm not sure if the same OTA update actually updated per se. But yeah, next time Im ready, I've got everything backed up!
Thanks so much!
Click to expand...
Click to collapse
I always prefer updating via Odin instead of OTA, it is much better and less chance of issues such as bootloop or random reboot. These are the issues you were having. I actually suggest using Odin or Smart Switch on PC the next time an update is available. Or, on older devices, use Odin or Samsung Kies to update. OTA is frequently unreliable, it commonly causes bugs, especially if the update is a newer android version than what is already on the device, it usually causes conflicts due to user data from your previous system apps and user settings conflicting with the new system because of differences between the older system apps and the newer system apps or differences in settings in the older system conflicting with changes in how the newer system settings are handled. Systems don't like using system data that was created by another system when there are differences between the two systems.
Another method that can be used is if your manufacturer/carrier releases a stock update.zip that can be flashed via stock recovery, they are made specifically for flashing via stock recovery ONLY, they are not the same as the stock firmware file that is flashed via Odin. These can be downloaded to the phone's internal/external memory then you boot into stock recovery then factory reset/wipe cache in recovery(backup data before wiping) then you can flash the update.zip. Alternatively, you can flash the update.zip without resetting/wiping(this is called a "dirty" flash), in theory, a dirty flash is useful when you don't want to wipe data or lose data. But that comes with a chance of causing bugs, as you have discovered for yourself during your update process.
Sent from my SM-S767VL using Tapatalk