Hi all. So here's the skinny:
I've got a Verizon nexus 6, unlocked boot loader and rooted running 5.1.
No other mod except for the net tethering provision.
I did a factory reset this morning because my device wasn't showing up on ADM. It shows up in Google play via the website, and I'm able to install apps to it from there.
I have gone through all the basic troubleshooting steps Googling could afford me. After the factory reset, it showed up in ADM. But when I checked again just now, it's gone again. That was one of the primary reasons I did the reset (which was a pain in the butt by the way because I had a pin-at-boot and even after telling the phone to do a factory reset twice, it didn't go away until telling it to in the boot loader menu).
I'm pretty frustrated now, because I went through a lot of hassle to fix it... And with no SD card, titanium backup is out the window too.
Does anybody have a solution or has someone else experienced this?
Related
Weirdest thing happens, I'll boot my DS7 and it's like if I just did a factory reset...every time. I'll customize my homescreens/gmail and what not, and do a normal reboot and it does a factory reset every time. I've read a few threads about similar topics and no one seems to know what's going on.
I've wiped data/cache/dalvik and fixed permissions, doesn't help. Re-install ROM, doesn't help.
I tried reflashing superuser.zip says installation aborted (bad). Same when I try to flash HC (yes, I'm still on Froyo).
Any clues ladies and genitals? Any help would be appreciated.
Sounds like you are experiencing the READ-ONLY bug that plagues this device. Hopefully it is still under warranty so that you can send it to Dell. Last summer I sent my Streak 7 to Dell. They repaired the read-only bug and had it back to my house in about 2 weeks.
Basically, what happens when your tablet goes into read-only mode... any updates, installs, customizing you do will be lost upon a reset... even though it appears like things are updating, they simply are not saved to the internal flash drive. Also, when it gets really bad some of the apps (along with the web browser) will start to get fatal errors.
That sounds about right, especially since even when I try to move a file from my netbook to the device (such as a new ROM to try to flash in CWM) it wont show up after I reboot either.
Don't think its under warranty anymore, dang.
Yes this is what happened to the one I got off Craigslist too the person I bought it from also changed his phone number instantly, so I got screwed but I'm in the process of getting a replacement or getting an extended warranty on it.
Sent from my Galaxy Nexus using XDA App
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
I'm trying to factory reset my HTC Desire C has it was feely slow, but I'm having trouble un-rooting the phone, Does anyone know of any way I could do this with my model please?
I've tried Quick Root but that just seems to get stuck removing the perm-root.
Thanks in advance.
I've attached the info of my phone, thank you.
mkkid28 said:
I'm trying to factory reset my HTC Desire C has it was feely slow, but I'm having trouble un-rooting the phone, Does anyone know of any way I could do this with my model please?
I've tried Quick Root but that just seems to get stuck removing the perm-root.
Thanks in advance.
Click to expand...
Click to collapse
You can do this: - lock bootloader
- power on device
- enable adb debugging on device
- make sure you have adb and fasboot working corectly
- connect device via usb to PC
- run RUU with administrator rights
- and from there on just follow the instructions given by software
- http://www.androidruu.com/?developer=Golf
you really need the 2-4 lines i mentioned up for this to work
Well I managed to lock my bootloader and that, but when i tried to install the RUU it gave me a error. I think it might be an older version.
I think I'm going to need the 2.00.771.3 version :S
I think my phone is useless now. A bit of info, I tried factory resetting my phone (I have rooted my phone prior to this and stupidly thought that factory reset would get rid of the root) but when I reset my phone after the inital setup had gone through all menus it said setup has stopped working. Then my phone wouldn't work no apps or home screen, I could recieve calls and then go onto my settings at the top but nothing more then that, I'm not sure how I can get my phone working again now lol
mkkid28 said:
Well I managed to lock my bootloader and that, but when i tried to install the RUU it gave me a error. I think it might be an older version.
I think I'm going to need the 2.00.771.3 version :S
I think my phone is useless now. A bit of info, I tried factory resetting my phone (I have rooted my phone prior to this and stupidly thought that factory reset would get rid of the root) but when I reset my phone after the inital setup had gone through all menus it said setup has stopped working. Then my phone wouldn't work no apps or home screen, I could recieve calls and then go onto my settings at the top but nothing more then that, I'm not sure how I can get my phone working again now lol
Click to expand...
Click to collapse
once it booted it not useless
try what i said with and without locked bootloader
if you need further help add me on fb
https://www.facebook.com/makerr00
I absolutely hate creating yet another thread, but I've tried everything I can and I'm stuck. I was up until 4am (no lie) last night and been at it again for hours tonight. So... here are the symptoms.
Multiple bootloops/reboots at any of the following points:
1) "Preparing device" with the "Please wait" animation.
2) Force close: Unfortunately, Setup has stopped.
3) Force close: process.com.android.systemui has stopped.
4) Force close: Google search has stopped.
5) Bootloop at the bootloader warning message
Usually, the boot animation doesn't even start. Often, I'll see the "Bootloader Unlocked" warning message, then the Moto logo, then it cycles back through any of the above fail points. Sometimes, it'll stay on the bootloader warning message the whole time and then jump directly to the lock screen.
All of this started after unlocking my brand new Moto X Pure Edition and then attempting to use the "Multi-tool" to root. Or...maybe it was after trying to root using one of the Chainfire images. I can't recall. After doing so, wifi stopped working (wouldn't turn on). So, I tried (using the tool again) to flash back to stock. At that point things strange things started happening (force closes). I then tried flashing to stock and immediately flashing the OTA (all via fastboot). When I booted up, Lollipop setup wouldn't load, it'd bootloop, come back and maybe I could get to the next screen, but wifi would be dead. Or I'd get wifi to work, but it'd crash after accepting Google privacy terms.
So, after all of that, I decided I would just revert back to stock. At that point I tried a number of options including what I think is the likely best bet, @SolarTrans guide here. Oh, and somewhere along the line I flashed TWRP 2.8.3 and flashed one of the custom ROMs (LiquidSmooth). It booted, but was very unstable and also threw the same/similar systemui force close messages, occasionally would lose wifi or begin force closing like crazy. Makes me think I have a bigger issue since it happens regardless of ROM/firmware. I also tried graffixnyc's images. So... yeah... just want to get back to stock.
I've been doing this stuff with Android for many years. Not a newbie by any means. Completely comfortable using fastboot or adb command line. I'm just at a loss and feel that it's likely I'll have to send it back to Motorola. I can get into the bootloader no problem. Everything else is a toss up. The last time I flashed files via the SolarTrans guide, it eventually loaded up the home screen (after many bootloops), but wifi wasn't working and I got a strange Moto message about reverting the sensors firmware or update. I rebooted and it never booted again, so I erased cache and userdata via fastboot. That didn't help. I just flashed the original firmware again and it spent a good 20/30 minutes bootlooping before getting to the setup screens. I skipped everything. Then it bootlooped at the home screen.
Open to suggestions!
Edit 1:
Pretty much anything causes the phone to bootloop, but I was able to get a screenshot of the baseband, kernel, build, etc. It bootlooped, but worked the second time around. I think I just made things way worse by trying to turn on bluetooth. It's just bootlooping over and over. Gonna try and get some sleep!
So, before bed, I flashed the OTA from the SolarTrans thread. It booted up, threw some errors and then once I connected to wifi it bootlooped. It did this for at least 10 minutes before I plugged the phone in and went to bed. When I woke up this morning, it was sitting on the setup screen. No errors. I signed in to my Google account and it restored all my apps. I rebooted. Still no problems. Just before leaving for work, I noticed that Dropbox wasn't installed. I installed it, signed in and then it bootlooped. After that...no luck. Kept rebooting. So, I brought the phone to work and left it on my desk for a few hours. It bootlooped or hung on the bootloader unlocked warning screen for at least 3 hours. I wiped cache. Same thing. Just now, I wiped userdata and rebooted. It went through the setup process without errors. Began restoring my apps and then froze. I manually restarted and now... no dice. Bizarre.
mercado79 said:
So, before bed, I flashed the OTA from the SolarTrans thread. It booted up, threw some errors and then once I connected to wifi it bootlooped. It did this for at least 10 minutes before I plugged the phone in and went to bed. When I woke up this morning, it was sitting on the setup screen. No errors. I signed in to my Google account and it restored all my apps. I rebooted. Still no problems. Just before leaving for work, I noticed that Dropbox wasn't installed. I installed it, signed in and then it bootlooped. After that...no luck. Kept rebooting. So, I brought the phone to work and left it on my desk for a few hours. It bootlooped or hung on the bootloader unlocked warning screen for at least 3 hours. I wiped cache. Same thing. Just now, I wiped userdata and rebooted. It went through the setup process without errors. Began restoring my apps and then froze. I manually restarted and now... no dice. Bizarre.
Click to expand...
Click to collapse
So, what was the problem then? The Dropbox app? Why is that?
No. Don't think so. It was just the trigger. I'm convinced any app would have eventually caused the bootloop.
I tried one more clean install of the official image straight from Motorola last night. Same results. So, I've initiated a return/repair.
Sent from my Moto X
Have they accepted repairing your device even with unlocked bootloader and root?
Sent from my XT1097 using XDA Free mobile app
They acknowledged that I'd unlocked the phone (it was logged in the record when they looked up my phone by IMEI), though I said I did so while trying to fix it (in order to wipe partitions and flash images which I also requested via their developer resources page).
They're sending a replacement phone without any push back at all. Honestly, I expected to send it in for repair. The rep said the standard protocol was to issue me a pin to order a new phone (mine is a customized Moto Maker model with a bamboo back).
Just so you're aware, unlocking the bootloader on Pure Edition phones does not void the warranty.
So, a replacement should be in my hands in about a week, I'm told. The phone was still within the initial month and so they're sending a brand new phone.
Sent from my Moto X
I have a stock AT&T G6, got it when the phone first came out, and I haven't touched the firmware. Update after update, no problems.
Finally this morning my phone had enough - I performed a system update. However during the reboot, the phone froze for 30 minutes on the AT&T logo. Nothing changed.
Reset phone, nothing changed, 15 minutes no change. Reset phone to recovery mode - wipe cache - reset phone. Same thing - stuck at AT&T logo.
Finally I had enough - I did a full Factory reset. AT LAST! After 8 painful minutes stuck at the AT&T logo, my phone came to life and welcomed me to my new phone (FML).
So here I am with a freshly loaded copy of my new Nougat 7.0 software on my AT&T Build ( NRD90M.G920AUCS6EQF1 ) and I am desperately trying to run every possible data recovery option possible.
I WANT to recover my photos and SMS messages before I start using my phone. But I can't - every app I've run shows no results. Everything I'm seeing shows I need to root this phone to make it work.
Unfortunately I have no clue htf to do that. Every instruction I find online does not include my build version. My phone is turned off and not used until I recover this data. I would appreciate any help I can get in recovering this data!
Cassetti said:
I have a stock AT&T G6, got it when the phone first came out, and I haven't touched the firmware. Update after update, no problems.
Finally this morning my phone had enough - I performed a system update. However during the reboot, the phone froze for 30 minutes on the AT&T logo. Nothing changed.
Reset phone, nothing changed, 15 minutes no change. Reset phone to recovery mode - wipe cache - reset phone. Same thing - stuck at AT&T logo.
Finally I had enough - I did a full Factory reset. AT LAST! After 8 painful minutes stuck at the AT&T logo, my phone came to life and welcomed me to my new phone (FML).
So here I am with a freshly loaded copy of my new Nougat 7.0 software on my AT&T Build ( NRD90M.G920AUCS6EQF1 ) and I am desperately trying to run every possible data recovery option possible.
I WANT to recover my photos and SMS messages before I start using my phone. But I can't - every app I've run shows no results. Everything I'm seeing shows I need to root this phone to make it work.
Unfortunately I have no clue htf to do that. Every instruction I find online does not include my build version. My phone is turned off and not used until I recover this data. I would appreciate any help I can get in recovering this data!
Click to expand...
Click to collapse
No known root for current builds to my knowledge. Don't know if anyone is still picking away at it, but I wouldn't hold my breath. Development on this device has been almost silent for many months.
dandrumheller said:
No known root for current builds to my knowledge. Don't know if anyone is still picking away at it, but I wouldn't hold my breath. Development on this device has been almost silent for many months.
Click to expand...
Click to collapse
Pretty much what I've figured. Sounds like I'll just have accept they're lost and move on. Thx