Database Users

How to be sure Nook Color is back a t stock?

Got a Nook Color, decided it wasn't for me even after hacking and custom romming it up and decided to restore to stock and sell. Here's a brief run down:
Followed a guide to flash stock image with custom recovery. When I was rooting I had a micro sd with CR and I had also installed a version to the NC's internal memory. From the guide I read it looked like flashing the stock image would restore it back to stock for everything. Did this and I got the standard boot screens and the setup screen with the girl and the video. Powered it off, cleaned it up, reboxed and put it up for sale. After I sold it I got a call back from the buyer saying it was hanging on the startup screen for nearly ten minutes. That later devevolved into boot loops. I would have originally held by "all sales final" mentality with craigslist buyers but then he mentioned it would flash a screen for a moment that would say "android" before boot looping again. Figured at this point I should be a guy and take it back, mainly because I HAD told him I did not root it. I got it back and it was boot looping, going through the "touch the future of reading" page and the N logo. Forced 8 failed starts and got an error message saying install could not complete. I fiddled some more (this is all while with friends at a Best buy mind you) and managed to get it to boot to screen, register my b&n account, and do a factory reset. After this it operated and ran perfectly fine, and after multiple factory resets, resetup runs, and trouble testing to force issues, it yielded perfect functionality. I even tested to make sure it would accept a credit card and that worked fine.
I'm gearing up to sell it to another buyer but I want to make sure I have my ducks in a row. I haven't fiddled with it beyond what I did the night I took it back but all testing I've done today has been fine. With B&N rolling out a froyo update though I want to be sure the unit is fine and won't give the other guy any trouble. There is no super user login or anything else that would suggest it's rooted or running anything other than stock firmware. I'm thinking that not letting it factory reset after flashing a stock rom may have contributed to my first bout of issues. Is there anything else I can check or look at to make sure the NC is good to go though?
EDIT:
Just performed a successful factory reset with deliberate 8 failed boots. Worked like a charm. Think I'm golden less otherwise advised.

Sent you a PM.

Rooted and SuperSU'd to fix the 4.3 memory card issue. Can I relock?

Hi. Been playing with smartphones for a long time, but I'm no developer, and definately not an expert. So I look to those more experienced than I for an answer to this question.
Dropped my Note II and shattered the screen. Hadn't done this since a Windows Phone back the 3.0 or so OS days (when if you pulled the battery, you lost all the data stored on the phone). Knew full well I wasn't going to be able to get one under contract, having got the Note II only months prior, so I went to Engadget and saw the "best available" was the Galaxy S 4. And word was the Google Play edition was a little faster without the bloatware or carrier stuff, so that's exactly what I ordered and have now.
Got the phone and read about the 4.3 update, and how that messed up 3rd party app ability to access the memory card. Having a 64GB card, I wanted full functionality. And as I didn't see anything about an Official Google update or patch (4.31 perhaps?), I followed instructions to root the phone, installing the recovery partition as part of the process, and using SuperSU to allow me to edit the file for memory card permissions to work correctly. ONLY AFTER I had done the fix, did I install my memory card from the Note II and it's seem to work perfect.
So I'm using my phone Thursday, and I remember how Flixster won't work with SuperSU installed. And looking for an app that will hide my SuperSU unlocked from from Flixster, everything says the S 4 is different and this won't work atm. Thinking to myself, "Well... I don't really need my phone unlocked... as I'm not updating the OS nightly or anything, maybe I can just remove SuperSU and I'll be fine. This actually DID work, thought not EXACTLY how I'd have preferred. I CAN use Flixster with SU gone from the device, but when I reboot the phone it STILL shows the unlocked symbol at the bottom of the front page. Would love to fix this, but the articles I've read seem to indicate using SU rights to change it.
So my phone is unlocked, and probably still rooted, but I do NOT have Super User permissions atm. If I wanna get the first screen at reboot to NOT show my phone unlocked (because I'm OCD and it's BUGGING me), do I have to go through reinstalling SU somehow? Or is there some way to make the boot logo go back to the old way?

[Q] XCOM:EU will not launch past initial loading screen

Hi, I'm Nyshan and I've been having a bit of a problem with XCOM:EU. I recently purchased it from the Google play store after looking through several forums and seeing that my device (Nexus 4) was compatible. I then proceeded to download it to my (at the time) rooted, 4.3 OS on Franco Kernel. To my dismay the game refused to launch. So I did the only rational thing and unrooted my device while also backing up XCOM. I then reinstalled XCOM after the unrooted and to my absolute disgust found the game still would not load up. I then proceeded to update my phone to the latest OS (4.4.2, still unrooted with a locked boot loader, mind you) in the waning hope that it might fix my problem. Obviously, it didn't. So now, I come here as an absolute last resort.
For ease of access:
Nexus 4
Currently Stock (4.4.2)
Unrooted, Boot loader locked
Any help would be appreciated.
Thanks,
Nyshan
P.S. I made this on my phone, so I apologize for the block of text. Also the search bar refuses to function without disappearing every time I try to use it, so sorry if this was an already resolved issue.
Has anyone else had this problem?
I've got 90+ views and 0 replies, someone say something, please!

[Q] Galaxy S4 won't boot past recovery (urgent)

This is somewhat urgent because I am leaving the country for two weeks on Friday, and need a working phone. I am not sure what happened today, but my Sprint Galaxy S4 (SPHL720TBK) wouldn't connect to WIFI at my house. My tablet would, so I know it was a phone issue. I rebooted then was going through settings, and just checking things. The phone rebooted itself, and when it came back up, it went through a couple of screens, one of which asked about activation. It seemed like it was installing an update from Sprint, which it had been trying to do for a week or so. But it kept failing, saying it didn't have enough space for the download, despite there being several GB free internally and on the SD card. (I figured it must be because it was rooted). After a couple of additional screens on which I could only answer OK, the phone rebooted again, and that was it. It would not boot again. I decided to power off the phone and deal with it tonight. I can boot into recovery, and connect with Odin. I can boot to recovery and connect with ADB (in sideload mode). I know I could just do a factory reset, but unfortunately, I do not have a full backup since the end of January, and I would rather not lose everything. The phone was running v 4.4.2. I had rooted the phone several months ago with CF Auto Root using CF-Auto-Root-jfltespr-jfltespr-sphl720.tar.md5, so it was essentially stock, but rooted. Is there anything I can do to get the phone back on its feet that will not lose everything? Or anyway to copy data from the phone with it in this state? Any assistance will be VERY much appreciated! Thanks!

Fixed it myself
andrewt2323 said:
This is somewhat urgent because I am leaving the country for two weeks on Friday, and need a working phone. I am not sure what happened today, but my Sprint Galaxy S4 (SPHL720TBK) wouldn't connect to WIFI at my house. My tablet would, so I know it was a phone issue. I rebooted then was going through settings, and just checking things. The phone rebooted itself, and when it came back up, it went through a couple of screens, one of which asked about activation. It seemed like it was installing an update from Sprint, which it had been trying to do for a week or so. But it kept failing, saying it didn't have enough space for the download, despite there being several GB free internally and on the SD card. (I figured it must be because it was rooted). After a couple of additional screens on which I could only answer OK, the phone rebooted again, and that was it. It would not boot again. I decided to power off the phone and deal with it tonight. I can boot into recovery, and connect with Odin. I can boot to recovery and connect with ADB (in sideload mode). I know I could just do a factory reset, but unfortunately, I do not have a full backup since the end of January, and I would rather not lose everything. The phone was running v 4.4.2. I had rooted the phone several months ago with CF Auto Root using CF-Auto-Root-jfltespr-jfltespr-sphl720.tar.md5, so it was essentially stock, but rooted. Is there anything I can do to get the phone back on its feet that will not lose everything? Or anyway to copy data from the phone with it in this state? Any assistance will be VERY much appreciated! Thanks!
Click to expand...
Click to collapse
Since I didn't spark enough interest for anyone to offer advice, had to spend most of the afternoon/evening fixing these problems myself. Everything seems to be working, so I thought I would pass along key parts of this hard-learned lesson in case anyone else finds himself in such a situation.
First I booted into adb sideload mode, which is all I could do anyway. I installed philz_touch_6.23.9-jflte.zip and the aromafm.zip. I was then able to boot into a "normal" recovery mode. Aromafm was troublesome, and I eventually had to manually put the zip into place for it to work consistently. These are both WONDERFUL , and I highly recommend them both. Thanks very much to the creators! I used the file manager to find the files that I didn't want to lose, and used ADB to pull the files over to my PC. (ADB pull <source> <target>) Then I did a full wipe and factory reset. That did little other than delete all my data, which I had already copied anyway. The phone still would not boot past recovery.
I tried to use ADB to install a new ROM, but got a variety of errors. My phone being an L720T, there are not many ROM's available, at least not for which I could find functioning links. I finally found a TAR, L720TVPUBNG5_L720TSPTBNG5_L720TVPUBNG5_HOME.tar.md5, and used ODIN v3.09 to install that.
I still need to go back and re-root the phone, and install lots of APPS and restore data, but at least I have a functioning phone, and I can do the rest on my plane ride tomorrow.
I found the information I needed in a variety of posts here on xda developers, and would not have been able to get through this without all the helpful advice posted to other threads. So thanks to all of you for the wealth of information available here!

LG G2 D802 Bootloop Problem?

Hi,
I have an old G2 which had lineageOS on it, and I wanted to go completely google free and uninstall google play services and stuff, but it seemed my device wasn't rooted (by checking for # in a terminal). I'm completely new to rooting and flashing and everything. Basically I decided I was going to ignore the fact that my brother had already changed things on the phone and I was just going to try and follow a guide to root it and then put whatever ROM I wanted on. Apparently my phone was encrypted, and this needed to be changed before I could do anything so I tried to do a factory reset. When I did this, I ended up in TWRP, which is apparently installed and tried to do a factory reset in that. It prompted me to install Super User or something which seemed like an easy way to root so I said yes. The problem is, the phone never loads. I left it for a good 2 hours to do the factory reset, then it seemed it was not doing anything so I restarted and messed around more. The result is, it is just stuck looking like it's loading up (I assume that's called a bootloop).
So my question is how can I get this phone back into usable condition, I'm not fussed about finishing what I started necessarily, I just need a usable phone. There seems to be good news in that I can access TWRP (v2.8.6.1), which I guess would be useful if I knew how to use it.
Thanks for any help
EDIT/SOLVED: I managed to get it working by going into TWRP, wiping cache and dalvik, installing a new build of lineageos i had already downloaded, not installing superuser, wiping the cache and dalvik again, and rebooting system, and a fresh start of lineage finally loaded. Doubt that's relevant to many people but thought I'd share anyway.

brokemyG2 said:
Hi,
I have an old G2 which had lineageOS on it, and I wanted to go completely google free and uninstall google play services and stuff, but it seemed my device wasn't rooted (by checking for # in a terminal). I'm completely new to rooting and flashing and everything. Basically I decided I was going to ignore the fact that my brother had already changed things on the phone and I was just going to try and follow a guide to root it and then put whatever ROM I wanted on. Apparently my phone was encrypted, and this needed to be changed before I could do anything so I tried to do a factory reset. When I did this, I ended up in TWRP, which is apparently installed and tried to do a factory reset in that. It prompted me to install Super User or something which seemed like an easy way to root so I said yes. The problem is, the phone never loads. I left it for a good 2 hours to do the factory reset, then it seemed it was not doing anything so I restarted and messed around more. The result is, it is just stuck looking like it's loading up (I assume that's called a bootloop).
So my question is how can I get this phone back into usable condition, I'm not fussed about finishing what I started necessarily, I just need a usable phone. There seems to be good news in that I can access TWRP (v2.8.6.1), which I guess would be useful if I knew how to use it.
Thanks for any help
Click to expand...
Click to collapse
you can access the twrp with the power off button and volume less when the lg logo looses the power on and you press again:fingers-crossed:
---------- Post added at 10:04 AM ---------- Previous post was at 10:02 AM ----------
brokemyG2 said:
Hi,
I have an old G2 which had lineageOS on it, and I wanted to go completely google free and uninstall google play services and stuff, but it seemed my device wasn't rooted (by checking for # in a terminal). I'm completely new to rooting and flashing and everything. Basically I decided I was going to ignore the fact that my brother had already changed things on the phone and I was just going to try and follow a guide to root it and then put whatever ROM I wanted on. Apparently my phone was encrypted, and this needed to be changed before I could do anything so I tried to do a factory reset. When I did this, I ended up in TWRP, which is apparently installed and tried to do a factory reset in that. It prompted me to install Super User or something which seemed like an easy way to root so I said yes. The problem is, the phone never loads. I left it for a good 2 hours to do the factory reset, then it seemed it was not doing anything so I restarted and messed around more. The result is, it is just stuck looking like it's loading up (I assume that's called a bootloop).
So my question is how can I get this phone back into usable condition, I'm not fussed about finishing what I started necessarily, I just need a usable phone. There seems to be good news in that I can access TWRP (v2.8.6.1), which I guess would be useful if I knew how to use it.
Thanks for any help
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=HL1wOPe5pLc