yashsingh1/xdaforums huggingface dataset:
[Barnes & Noble Nook Tablet] johninsf:
I looked around and searched first for similar threads before posting this one.

On my rooted NT, I have noticed that charging only works when it is powered off. (I rooted immediately so have no point of reference to non-rooted behavior.)

1. When powered on and plugged in to charge(A/C), I look under Settings/Battery and it shows discharging.

2. Also, the light on the micro USB is green, not orange, if the NT is on.

3. I turn off, the light turns orange until fully charged then turns green.

Could someone confirm that this is the correct NT behavior? I was thinking that it should charge if plugged in whether powered on or off.
[Barnes & Noble Nook Tablet] lenardo:
it charges on or off if you have the nook tablet cable plugged in, the only time you need the nook off is if you are using a micro usb normal cable via computer to charge, so in answer

no not normal behavior
[Barnes & Noble Nook Tablet] johninsf:
Thanks. That is what I feared. Unsure what might be causing so hope someone with broader insight might be able to give direction.
[Barnes & Noble Nook Tablet] Berryblue:
Interesting. My NT was charging but after rooting it, it doesn't charge either. I did a search and came across your post. I blocked it from receiving further updates but that shouldn't be the cause.
[Barnes & Noble Nook Tablet] johninsf:
Mine charges fine when off and have not heard from anyone on a solution or potential cause. As such, I just plug in each night with power off.

I did a nook hardware test and it detects the USB just fine but no charging from what I can tell when power is on.
[Barnes & Noble Nook Tablet] lostwhat83:
Nook not charging while turned on

I have the same issue. It started this morning. I rooted my nook yesterday using this method http://xdaforums.com/showthread.php?t=1354487. Before rooting my nook it charged fine while being plugged in to the wall socket. After rooting last night I could charge the nook (Plugged into the wall) while it was turned on. This morning I can not charge the nook while the device is turned on. Rooting and blocking OTA's using the link above is the only thing i have changed. Thank you guys in advance.
[Barnes & Noble Nook Tablet] DipDog3:
Also, don't have a problem, but I am scared to break the connector since I have heard it is really fragile, so I don't use it plugged up.
[Barnes & Noble Nook Tablet] cgdash:
Interesting,,,, I used Indirect's rooting method and I am charging right now as I write this on my NT. The only differences I can think of is I used one of his earliest root versions (in mid November) so I don't have some of the later script additions. Also to block the OTA update, I just uninstalled the update service instead of the steps to get mine to show as version 9.9.9
[Barnes & Noble Nook Tablet] cfoesch:
To make sure I understand what people have done. You follow Indirect's rooting method, and then use TiBu to restore the DeviceManager app, in order to block OTAs, correct?

Nothing else? You haven't touched the /system directory otherwise?
[Barnes & Noble Nook Tablet] cgdash:
Well like I said, I used an early version of Indirect's script to root. Then I backed up the DeviceManager app in Titanium backup (just in case I caused problems) and then deleted it completely. That's why I said my software version doesn't show 9.9.9 like others who have used the db version workaround.
[Barnes & Noble Nook Tablet] cfoesch:
Ok, so you deleted your DeviceManager.apk? I'll see if I can replicate your bug by deleting that apk. That might be what caused the problem.

----

Nope, still charging while powered on...
[Barnes & Noble Nook Tablet] cgdash:
Oh - I don't have the charging bug. I was saying that maybe I

can

charge because I rooted with an older version of the script and just deleted the DeviceManager APK to avoid firmware upgrade. Whereas others used a newer version of Indirect's script plus the work around to make the version 9.9.9

Not sure why some can't charge while on cause it works fine for me on my rooted NT.
[Barnes & Noble Nook Tablet] cfoesch:
Basically, where I am at as well. I've rooted numerous times, ever since the 24th, and I've never had this no charging problem.

Figuring out what is different about what they did, and what others who don't have the problem is difficult. There is nothing in the rooting process that should make a difference. Except perhaps if they all reverted from 1.4.1 to 1.4.0 ... Indirect, and I both can charge, but never had 1.4.1 on our tablets.

There could be something left over from 1.4.1 that is screwing things up? (Unlikely, but possible?)
[Barnes & Noble Nook Tablet] cgdash:
Yeah I never have had 1.4.1 on mine either and no charging problems.
[Barnes & Noble Nook Tablet] Berryblue:
That is exactly what I did...nothing else.

---------- Post added at 11:49 PM ---------- Previous post was at 11:47 PM ----------

That could be a possibility as I finally rooted after getting the 1.4.1 OTA. Everything else is fine, just the charging issue.
[Barnes & Noble Nook Tablet] lostwhat83:
I had to downgrade to 1.4.0 using the zip to SD card method, before rooting, to mod the apk to version 9.9.9.9 to block OTA'S.
[Barnes & Noble Nook Tablet] Berryblue:
I used the Factory Reset option since my NT came originally with 1.4.0 so I didn't have to do the SD card. I'm thinking about (banging my head on desk) going back to factory setting and re-installing Indirect's files. Maybe after the New Year.
[Barnes & Noble Nook Tablet] kevalin:
I started with 1.4.0; never had to downgrade to root. But since I rooted and blocked the OTAs using Indirect's methods, my nook will not charge unless it's off.

I'm not sure I'm all that thrilled with the Nook anyway, but this could be a deal-breaker. I'd hate top be in the middle of something and suddenly have to turn off my Nook for three hours before I could finish with it.
[Barnes & Noble Nook Tablet] ckevinwelch:
Just to be clear, you are plugging it into the wall, and it will only charge with the screen off, or completely powered off? If you are plugged into a computer and it is only charging with the screen off, that is normal.
[Barnes & Noble Nook Tablet] kevalin:
This is plugging into the wall and using the charger that came with the Nook (when I initially charged it up, I used the cord, etc., from my Samsung Captivate. It charged up completely in about three hours).

The cord indicator shows orange, as if it's charging, but in Settings, it says, "Not charging," as opposed to "Discharging," which is what it says when there's no charger connected--and the battery continues to drain. I have the screen set to go dark after two minutes, so it spent most of the time "Not charging" with the screen dark. Also, it took around five hours for it to charge back to 100% from a low of 15%.

I'd really rather not, but I'm about ready to give a go to sending it back to stock and seeing if one of the other rooting methods will give me back my "on charge." That is, unless someone has some ideas for how to make Indirect's root and OTA block allow for charging regardless of whether it's on or off.
[Barnes & Noble Nook Tablet] Berryblue:
I just did a factory reset on my NT (daughter wants to swap out my NT for her Streak 7).

The first thing I just did after going thru the registration screens & deactivating the wifi was to plug in the device into an outlet...it's charging fine with it being on.

I'm going to be placing Indirect's image onto the NT again...I wasn't able to add shortcuts or anything outside of widgets to the screens...quite annoying. I'm sure I didn't miss a step but something went wrong and second time around is a charm. :)
[Barnes & Noble Nook Tablet] ckevinwelch:
That's odd. I used Indirect's methods too, and don't have any charging issues. Perhaps you should restore from the magic SD card and try again.
[Barnes & Noble Nook Tablet] kevalin:
I believe I will, as the tablet revealed a few other unfortunate quirks, though they may not be related: eg., I had to re-install my various widgets every time I restarted the tablet; things like that. Very annoying.

I will report back, of course.
[Barnes & Noble Nook Tablet] ckevinwelch:
Good luck! Was that Go widgets, by any chance? There is a thread in Apps discussing that behavior. I have Beautiful Widgets, and a couple of Google widgets installed with ADW and don't have any issues.
[Barnes & Noble Nook Tablet] kevalin:
Well, that worked!

It took a bit to find a file app that would let me install the unroot apk, but it let me back to stock and worked like a charm. It also took a bit of work to get my computer to recognize my Nook before I unrooted--and there's definitely some question as to whether or not it will ever let me do so again. I had to install my apps from Titanium Backup, etc., straight to my external sd card, then reinstall it into the Nook, because once I unrooted again, my computer simply would NOT recognize the Nook as a Nook, no matter what I did.

Now that I've re-installed Indirect's unroot and OTA block, though, I can charge the Nook without having to turn it off. Here's hoping it keeps.

The widgets in question aren't Go Widgets, but I am using the Go Launcher. Guess I'll have to look for another one. I didn't really care for ADW asthetically speaking, but having to reinstall my widgets every time I restart the damned tab is just not acceptable. And Honeycomb just looks way too... incomplete.

Anyway, I'm glad it worked. And hope I don't have to do it again for awhile.
[Barnes & Noble Nook Tablet] Berryblue:
It works

Well I unrooted and rooted again and the charging is now working while the device is on. I can now had it off to my daughter who wants to swap...why it beyond me but I'm willing to please. :)

Happy New Years everyone!
[Barnes & Noble Nook Tablet] lavero.burgos:
Thats great so now we know what caused this issue.
[T-Mobile myTouch 4G Slide] Emmanuel U:
Sometime before, me and a couple people were having problems with Wifi when it was connected with a strong signal but no internet access could be obtained. I found out how to fix it.

settings/privacy/ uncheck backup my data

reboot into recovery

Full Wipe (data, cache, dalvik, system)

reboot

skip filling out Gmail

wait 5-10 mins

reboot

fill out Gmail and all other neccesary items

DONT restore any backups as it has the corrupted wifi data in it,

START FRESH!!!

...eat a donut ;-)
[Wildfire Q&A, Help & Troubleshooting] Slymobi:
Since xda went down earlier today!! No matter what I try I can't upload screenshots from the app yet I see other members are able to. All i get is....Unknown error code (2) when moving file to system file please try again later.

Driving me mad!!!! Anybody help?
[Wildfire Q&A, Help & Troubleshooting] Scratch0805:
Have you tried clearing data on the app?

I don't use it now its always been buggy to me, I use a photobucket app I found somewhere other than the market and just upload to there and copy across.
[Wildfire Q&A, Help & Troubleshooting] Slymobi:
I've tried everything mate.cheers.

Quote " its healthy to have enemies, it means you've stood up for something you believe in "
[Wildfire Q&A, Help & Troubleshooting] heavy_metal_man:
xda app

ive been having issues with the xda app also, for some reason it always force closes when i try to start a new thread :(
[Galaxy Note GT-N7000 General] danieldeanhodge:
Hi guys,

Since I've had the Note I've had this really irritating issue.

Every now and then, the browser will just stop being hardware accelerated and will become incredibly laggy. I have to end the task and restart it to get it to work. This happened on stock ROM, stock ROM with FM kernel, and Rocket ROM V8 with AbyssNote Kernel 2.2. I have no idea what's going on and it's really frustrating.

The browsing experience is wonderful when hardware acceleration is actually working. It's just a guess that I'm losing H/W Accel. but I figure it from the lack of checkerboard patterns when scrolling and the lagginess in general.

I have only used the stock browser but find that the stock browser is the most responsive.

I've searched and cannot find anybody else with this problem so I hope I'm not the only one. Has anybody else experienced this?#

EDIT: Nevermind, I'm a retard, another thread discusses this here: http://xdaforums.com/showthread.php?t=1390417

Looks like I'm not the only one.
[Samsung Galaxy Nexus] le3ky:
Thought you guys might be interested in my review of the CaseMate Barely There case for the Nexus.

http://droid-den.com/accessory-reviews/samsung-galaxy-nexus-casemate-barely-there-case-review/

Feel free to ask any questions, it's not a bad case :P
[Samsung Galaxy Nexus] allen2oo3:
thanks. the pictures were really helpful
[Xoom Q&A, Help & Troubleshooting] urwifeismyslave:
For the xoom family edition can u use the same root method and from as regular zoom?
[Xoom Q&A, Help & Troubleshooting] Muffycheeks:
This question has been asked many times and the answer is no. I do not believe the "Family" has be rooted reliably yet.
[Xoom Q&A, Help & Troubleshooting] danegrclose:
There is a way to reliably root the Xoom FE, you just have to know how to read, follow instructions, and not be running pirated software. Check out the Developers Think Tank for more: Developers Think Tank
[G2 and Desire Z Q&A, Help & Troubleshooting] sayedamir02:
Ok, after using my phone for a while i decided to root it. Since I have the stock Gingerbread rom i followed the guide to downgrade to the stock froyo rom. http://xdaforums.com/showthread.php?t=1178912

I reached the part

Temp-Rooting to Backup

However, when i run titanium backup it says Error: Sorry, I could not acquire root privileges. This application will *not* work.

What am I supposed to do? I followed the guide to the letter and everything up till that point was exactly as the guide said.

My phone's details are

Android version 2.3.3

Baseband version 12.56.60.25U_26.10.04.03_M

Kernel version 2.6.35.10-g7b95729

Software number 2.42.415.17

Here is what i did in adb

http://pastebin.com/jkxE55Yh

For some reason, new users are not allowed to post links in their replies. Nipqer, i redid all my steps and did what you told me.

here is the link of all what i did:

http://pastebin.com/Fze9uB33
[G2 and Desire Z Q&A, Help & Troubleshooting] Nipqer:
First, thank you so much for linking a pastebin of what you've done, makes it so much easier to try help.

However I'd really like to see if there was any output after running 'adb shell /data/local/

tmp/fixsu.sh' so if you can get that ouput and post it, would be much appreciated.

You might have to run it from inside shell:

adb shell

cd /data/local/tmp

./fixsu.sh

-Nipqer
[G2 and Desire Z Q&A, Help & Troubleshooting] sayedamir02:
Thanks Nipqer and sorry for the late reply.

I did what you told me and this is what i got

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell

adb server is out of date. killing...

* daemon started successfully *

# cd /data/local/tmp

cd /data/local/tmp

# ./fixsu.sh

./fixsu.sh

#

though i don't know if it helps with anything.

I just got confused because in the guide it says to install Titanium backup and backup my data. I have already done a manual backup myself but i figured doing a backup using Titanium backup will not hurt. I have used other programs like Root Checker Basic and it tells me that i don't have proper root access.

Can I just ignore this issue and go ahead with the downgrade? Or will there be some problems?

Thanks again in advance!
[G2 and Desire Z Q&A, Help & Troubleshooting] Nipqer:
Hmm, it should give you root permissions after running fixsu.sh.

The lack of output shows it should've worked.

That part of the guide is entirely optional anyway, so If you already have what you want backed up, go ahead and downgrade.

-Nipqer
[G2 and Desire Z Q&A, Help & Troubleshooting] utx:
Well. fixsu.sh returned no error for me, too. But Titanium backup did not get root and trying to call "su", I got I/O error. And looking to dmesg, I seen corrupted file system.

After a bit of research I got the reason: rw remount succeeds, Linux thinks, that data are written to flash, but no data are written for real. Once data leave cache, they are lost and system "returns" to intact state.

I wrote a different fixsu.sh, which does not have this problem, but I am still failing to get root privileges, even with the latest Superuser+su. I got only a pop-up about refused root access. (But "su number_of_any_existing_uid" and then "su" in adb shell says says about permitted access.)

Here is my preliminary fixsu.sh:

#!/system/bin/sh

chmod 755 /data/local/tmp/busybox
chmod 4755 /data/local/tmp/su

/data/local/tmp/busybox cp -a /system/xbin /data/local/tmp/
mount -o bind /data/local/tmp/xbin /system/xbin

/data/local/tmp/busybox --install -s /system/xbin/

/system/bin/rm /system/xbin/su 2>/dev/null
/data/local/tmp/busybox cp -a /data/local/tmp/su /system/xbin/

/data/local/tmp/busybox cp -a /system/bin /data/local/tmp/
mount -o bind /data/local/tmp/bin /system/bin
/data/local/tmp/busybox cp -a /data/local/tmp/su /system/bin/

# /etc/* changes are needed only for some busybox utils, not for Superuser's su
/data/local/tmp/busybox cp -a /system/etc /data/local/tmp/
mount -o bind /data/local/tmp/etc /system/etc

/data/local/tmp/busybox echo "root::0:0:root:/data/local:/system/bin/sh" > /system/etc/passwd
chmod 0666 /system/etc/passwd

/data/local/tmp/busybox echo "root::0:0:root:/data/local:/system/bin/sh" > /system/etc/passwd

/data/local/tmp/busybox echo "root::0:" > /system/etc/group
chmod 0666 /system/etc/group

# Optional:
ln /data/local/tmp/busybox /data/local/tmp/xbin/busybox

And here is the code to recover "writable" state after reboot:

#!/system/bin/sh
mount -o bind /data/local/tmp/xbin /system/xbin
mount -o bind /data/local/tmp/bin /system/bin
mount -o bind /data/local/tmp/etc /system/etc
[G2 and Desire Z Q&A, Help & Troubleshooting] Nipqer:
Unfortunately I can't tell you why it won't work. Might just be your partitions are too corrupted or something.

Have you tried a full power cycle (turn phone off, pull battery), it's helped other phones work in the past.

Otherwise I'd say just use adb to pull your entire /data dir, so you have everything saved and can mess round with trying to put it back in later.

-Nipqer
[G2 and Desire Z Q&A, Help & Troubleshooting] utx:
I tried to reboot without battery removal. Partition was "corrupted" before reboot and intact after reboot. I tried to write again. I again got corruption. And ffter reboot it was again byte-equal to the original system.img. It means, that not write actually happens. Linux kernel just assumes that data are written, but they are lost after leaving kernel cache.

Hopefully, Android mount command supports -o bind, so one can bind mount directories from /data and /system is seemingly writable then.

I saved all mmcblk0p* before starting my experiments. It should be the most complete way to backup, but it does not easily allow partial restore.
[G2 and Desire Z Q&A, Help & Troubleshooting] Setherio:
If you saved the data from the partitions, restoring would just be placing the apk in /data/app/ and then placing the data files back into /data/data/ - if you do it this way, you must run fix_permissions whether you saved it with or without preserving the permissions (owner, read/write/execute, et cetera). The app, when you put it on the different rom, will have a different UID (more than likely) than it did before and the data files permissions would be incorrectly set. Running fix_permissions should resolve that issue.

*EDIT*

I may of misunderstood what you meant by saving mmcblk0p*. How did you do this? At first I was thinking you just meant you did a tar backup of each partition, but after re-reading sounds more like you something like

# dd if=/dev/block/mmcblk0p# of=/sdcard/mmcblk0p#.img

Is that what you did? If so, are you trying to restore it by the same method?

# dd if=/sdcard/mmcblk0p#.img of=/dev/block/mmcblk0p#

If so, I'm not sure that would work properly… You might have to extract the data from it then copy it over to the partition...
[G2 and Desire Z Q&A, Help & Troubleshooting] ari3z:
I've had that problem after geting temp root. Titanium would say no root premissions. So I redid the steps after reboot...but I found the problem was that if you open titanium back up be for u root it will throw yu that msg so if yu have did that that's why so go back after you root in to applications and force close titanium and then reopen app then it shuld give you root premssions at least it worked for me but I still wasn't able to down grade and another thing are u using the gfree method kus that didn't work for me to get root... I had to use the freevo method to get temp root as gfree kept giving me errors after doing the adb coommands

sent from my Tmobile G2 Rush Vision
[G2 and Desire Z Q&A, Help & Troubleshooting] ari3z:
And if that dosnt work yu can use sdcard maid to back up your system apps n such or delete them ....

sent from my Tmobile G2 Rush Vision
[G2 and Desire Z Q&A, Help & Troubleshooting] utx:
I am aware of this problem. But if one returns exactly equal /system as it was there before, the /data will need no change.

It was just an abbreviation:

cd /dev/block
for PARTITION in mmcblk0p* ; do
dd if=/dev/block/$PARTITION of=/sdcard/$PARTITION.img
done

I guess, that the most straightforward way to restore that /data would be: First run

fsck mmcblk0p26.img

(on Linux machine) on that /data image (when you don't have root and custom recovery yet, you cannot backup /data in read-only mode, so the image is corrupted a bit for sure; if the fsck puts something to /lost+found, you can delete it after finishing of the rooting process). Then rename mmcblk0p26.img to userdata.img and add it to the PC10IMG.zip that restores stock system. Otherwise you will again fight with "partition in use" problem when trying to restore.

I did not test this method, as I did not understand the partition layout that deeply before I root. But there is no reason why it would not work.
[G2 and Desire Z Q&A, Help & Troubleshooting] Vince683:
Hello everybody,

for quite a while i am reading several guide for rooting my desire z (android 2.3.3, not branded, USB debugging activated, Fast boot deactivated). In Germany most of the guides refer to Setherio's guide. So working with the source is as usual the best.

Unfortunately - even after 3 tries, with factory resets, rebooting, removing the battery, etc. - I cannot gain a temporary root. neither titanium backup nor MyBackUp Root gain access for making a backup. So I ended up here. I am not sure, if Sayedamir had the same problem. Nevertheless, I appreciate every help.

This is what I have done so far:

http://pastebin.com/NKD6D7Av

Furthermore, referring to Nipquer's 1st post, I executed fixsu as described with following results:

http://pastebin.com/0EQS0UnF

I am not sure, if I should proceed with the downgrading without having a backup and I guess, when the backup isn't working (lack of temporary root), the downgrading would not work anyway?!
[G2 and Desire Z Q&A, Help & Troubleshooting] sayedamir02:
Hi Vince683,

Yes I had exactly the same problem. I too followed Setherio's guide and after 2 attempts I still couldnt get temp root. I ended up not being able to back up any of my apps.

However i suggest you back up your messages and contact as that was the only stuff I could back up. there are alot of apps in the market that do that and i guess they dont need root.

If backing up your app data is that not important you can proceed with the downgrade. It worked in my case. I guess the only nuisance would be that you have to manually install and configure all yours apps again.

Tell us how it goes.
[G2 and Desire Z Q&A, Help & Troubleshooting] Vince683:
Perfect, it worked. Thank you for encouraging me ;)

And Cyanogenmod 7.2 works fine.
[G2 and Desire Z Q&A, Help & Troubleshooting] sayedamir02:
You're welcome :)