Ive searched and havent been able to find a solution to this, although Ive seen it asked before.
Galaxy Tab P100 bought from a pawn shop. It still has the prior owners (unknown) gmail info minus p/w. I cannot remove the account, or access market because of this. Everytime I tried to data reset (both via Privacy settings and also CWM), add a new rom, or add apps - after I reboot it goes back to the prior owner settings and apks.
I have Odin'd/Heimdall with different roms but they dont stick. Different kernels install though. Ive added two different CWMs. Superuser breaks after every reset - I gain, then lose, root. Ive rooted/added root explorer and deleted accounts.db and user.db - they go back after. Ive spoken with Sprint and we tried everything they had, as well as a ##786# and MSL number (resetting phone activation I think?). Their response was take it in to send back. I want to fix it myself.
It seems to me that this prior info is overriding and reinstalling every reboot, preventing any new flashing/etc from taking place.
Here is my question. I took it apart this morning and disconnected the battery (thinking maybe it will wipe any memory). But does it have a CMOS-type battery? I noticed there is a small round battery-looking connection soldered into the mainboard (see here - step 7/8 http://www.ifixit.com/Teardown/Samsung-Galaxy-Tab-Teardown/4103/1)
Does anyone know what this is? I dont really have anything to lose, but Im not great with a soldering iron, but will try. Im thinking this might be for the memory, and disconnecting/reconnecting this would erase any permanent user information, freeing it up for me to add mine.
Or if anyone has any new ideas I would appreciate it.
Thanks for the time. Ed
Sent from my rooted/rom'd PG86100 using XDA Premium App
It is not a battery backed memory, it is a NAND chip.
Sounds like the chip gone bad.
Sent from my GT-P1000 using XDA
Just an update.
I did not do anything with the round battery thing, as priyana stated the memory is stored on a nand chip. I put the tab back together.
I rooted again, and found the ea24 firmware and loaded it via odin. It took, but the prior user info was still there, and everything (I mean a crapload of apps) began force closing. I did confirm that ea24 was on it. I then flashed back to ef17.
I contacted Sprint repair store again, and they told me that they probably cant fix it, and its something they have to send back. They said that I have done all that they would do in-store.
I dont understand what could be wrong, as I found the prior owner and spoke with her. She had no issues with it. It worked fine prior to her getting rid of it. And it works fine, I just cant get rid of any prior info. I googled it and it seems like there are people out there who have the same problem, but no one has an answer, including sprint or samsung.
So much for my venting. Ill keep trying to find an answer.
roninep said:
I have Odin'd/Heimdall with different roms but they dont stick. Different kernels install though. Ive added two different CWMs. Superuser breaks after every reset - I gain, then lose, root.
Click to expand...
Click to collapse
First of all, I'd like to apologize for posting something that won't really help, but I recognize this from somewhere else. On some devices, there's some kind of file (that you can delete via the adb prompt when you're root) that on every bootup checks to see if the installed ROM matches stock, and if not, restores to stock. This sounds exactly what you're experiencing when you mention that no ROMs "stick".
I think you should try to look into if there's some files that need to be erased in order for a ROM to be cleanly installed that you haven't gotten rid of. It might also be some kind of feature that the previous user enabled, so maybe it's somewhere around in the settings that you can disable it, who knows.
It definitely does not sound like a memory issue because I don't see how a memory issue could make the stock ROM suddenly appear again after you've installed a custom ROM through CWM (assuming CWM gives no errors or anything and the custom ROM has actually been wiped).
Maybe you can do a more thorough wipe of the device memory manually with some guidance from someone who knows more about how these tablets work :fingers-crossed:
I agree with you about some type of file and bootup. Thats why I went with maybe it being a cmos/nand issue. I couldnt understand that I wiped everything, and information was still coming back. It makes me think that somewhere, something is being stored separate from the main drive.
Ive used the factory restore, CWM (2 different versions - 3 and 5 I believe), and wiped data (factory reset), cache and Davlik three times each before I flashed the CM ROMs. And I have not had any errors or problems installing any of the CWMs.
I spoke with the previous user, and she did nothing above turning it on/off, and using it. I am not on the Sprint network with it, and the wi-fi doesnt turn on until I set it up, so I cant see it being something that contacts Sprint and OTAs from them.
Can anyone tell me if, using ADB, there is a more thorough wipe I can perform ? More than the normal one done through CWM or Android factory restore?
Something similar to the reformatting of a hard drive?
Thanks
Ed
I have the same problem. Did you find any solution?
I believe the previous owner info is stored on sprint servers. When you reboot, it downloads all the crap.
The long time required to reboot explains the slow transfer of data - wireless.
These wireless service providers are pretty sneaky.
Thanks
Hi,
Have you tried formatting both internal and external Sd via Windows? (connecting via USB)
You can also try CM10, it has a different memory map which will write your device completely.
Regards
Sent from my GT-P1000 using Tapatalk 2
I have this same problem with a tab. Its not connected to sprint,has not been on the internet at all. Was there ever a fix for this?? Please let me know its a christmas present and i need to fix this issue. Thank you
Hey everyone,
I've been eyeing this forum ever since I got my XZ, two months ago. I decided to root a few days ago (that Kingo one click program) and tried to improve my phone a bit everyday.
Today, I tried to hide the navbar by adding that line at the bottom of build.prop. I edited the file with QuikOffice but when I wanted to save, I couldn't simply replace the one there so I saved it somewhere else and copy/pasted it in place of the old one. I shut down the phone and when I tried to turn it on again : bootloop. I don't know how an extra line could mess the phone this much but I'm wondering if I haven't modified some other line without knowing it.
I read that using flashtool was an option so I downloaded an installed SEUS and then Flashtool (EMMA). I connected the phone following the instructions (volume down button) but I got a "Locked phone error". I haven't done much after rooting, especially not setting up a recovery or unlocking the bootloader.
Can anyone guide me through this ? I read things about using an update.zip file but have no idea how that works. I also don't have access to the original build.prop. I've also read people who espaced a bootloop without losing data. But the "locked phone" part doesn't seem to be common. As for the Sony Update Service, it just tells me that the phone already has the last "software version" and that's it.
Thanks.
hm, can you download sony pc companion and try? I used it yesterday and there is a service tab where you can fix and download updates etc. Maybe there is a reinstall firmware or some such
pixellegolas said:
hm, can you download sony pc companion and try? I used it yesterday and there is a service tab where you can fix and download updates etc. Maybe there is a reinstall firmware or some such
Click to expand...
Click to collapse
Thank but PC Companion offered to repair the device but at the cost of all data.
I was able to solve the issue and keep my data by flashing a stock ROM using the actual Flashtool and not Emma. I'm not running CM10.2 and everything is looking great .
So I have done a ton of research on the subject since last night when I made the mistake of editing my build.prop file in the system directory to try and get Milk Music installed and working on my N6.
steps I took pre soft brick
made a copy of build.prop and placed it in my nexus 6 home directory
then went in to edit the file in the system folder
Changed the following
ro.product.model=Galaxy S4 (from Nexus 6)
ro.product.brand=Samsung (from Motorola)
ro.product.manufacturer=Samsung (from Motorola)
Saved the changes using ES file explorer with root access of course and went on to DL the milk music app from http://forum.xda-developers.com/showthread.php?t=2676662 which is the tutorial page to get this all working.
dl'ed the app got it open and got an error saying milk music is only supported on samsung devices so I didnt think much of it and went to copy the backup build.prop over to replace the faulty edited one currently in the system folder. did this, or so I thought and rebooted.
now I am welcomed with just the Google while letters and the unlock symbol at the bottom of the screen and it will not move on.
I can boot into stock recovery but I only have the stock.
I do have adb installed and it worked to unlock N6 bootloader but haven't used it since and I am currently out of the house till prob a little later in the day.
steps I have taken to attempt the (known fixes) have all been shot down by the fact that I can't get ADB working from my friends computer and I am not sure if it is the phone or lack of drivers (which does not seem to be the case) or me just being very noob when it comes to adk and android sdk anything. I have only used it once and that was about a week ago to unlock bootloader.
I wont be able to check this forum till I get home a little later but will update on the situation when I get there and can try to connect phone to my PC where everything has already worked before.
thank you all in advance for all the help
I got home to test some things and I have ADB access and have tested fastboot.
I tried a fresh flash with the guide located here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
had to do the long way like everyone else in comments was describing. everything went smooth no hiccups but still stuck on black screen with Google in white letters with the white unlock at bottom.
any input would be highly appreciated.
Just did the exact same thing I did in second post and went for yet another fresh flash and IT WORKED. got the spinning dots and after a bit ANDROID popped up and the initial welcome screen popped up.
Thank you guys so much for all your help. not sarcastic at all i promise. the guys who lead me to this fix are in so many different forums and threads and have no idea i was piecing it all together to get to this outcome, so to all of them and all of you who participate here on XDA thank you so very much.
I flashed one of the first ver of Android N. It was OK but I could not updated it go back or do anything. It also took root away and unlike M there were no setting to turn it on and I could not get it back. I tried every cmd and attempted to flash forward and back and root again. I finally got pissed and software bricked it. Again I tried everything I could find but when I ran NRT_v2.1.5.sfx.exe to my surprise on the first try it fixed it and I am at 6.01. <
Hi,
First thread on here so forgive me for being a noob.
Two weeks ago I set my HTC One M7 to updated to lollipop before I went to bed. When I woke up it was still stuck on updating. I rebooted my phone and it was then bricked.
Took it to a phone repair shop and was told it failed because I didn't have enough free memory on the phone for the software to extract and install so it failed. They tried resetting to factory settings etc but no joy, there was no boot file.
After TWO WEEKS with the phone they have now managed to install lollipop on the device and everything seems to be in working order, except.... I have all my contacts backup up Dropbox using HTC Backup app. So now that I have my phone back I want to restore from Dropbox.
The only problem is that 'HTC Backup' is not on Google Play store. When I searched for HTC Backup on Chrome it gave me the option to open in the Play Store but with the error "Your device is not compatible with this version".
Firstly, is there a reason why HTC Backup is now not compatible since I upgraded to Lollipop?
Is there any other way of restoring my backup from Dropbox without using HTC Backup app?
Please let me know if you need any more info that I may have let out.
Thanks.
Hi all,
I completed a root for my z3c following Strmy's guide from here:
https://forum.xda-developers.com/z3-compact/general/guide-newbshow-to-291-mm-z3clocked-t3536395
one change I had to make to that process was to not flash the ''superuser_238_291.zip'' because every time I did, the phone kept getting stuck in a boot loop.
The process was completed successfully, and the phone worked like a charm for a day.
This morning, I found it strangely incapacitated - missing were many of the new apps I installed, along w gmail, chrome, and google play. I can't access the settings on the phone, and when connected to a computer, I can't allow file transfer.
Does anybody have an idea what may be happening and how to approach this situation?
Many thanks!
Update: I have since flashed the D5803_Customized US_23.5.A.0.570 R5D w/o any change to functionality of the phone. It also appears that I have lost access to TWRP recovery. This is all really confusing. Any advice would help.