yashsingh1/xdaforums huggingface dataset:
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] marknderm:
After I rooted my AT&T Note 3 (N900A)and then loaded in the newest version of safestrap, (everything went fine no problems getting any of that working)

After all that, I rebooted and did another backup of my rom, (3rd backup) reset the phone and went back into recovery again. I made the 1st slot active (in safestrap) then I tryed to do a recovery of one of the backups that I made. It went the whole way through, and then said: failed. So I then tried every other back up. And they all did Tha same thing, (load in &fail). So I thought it may be the backups that I made. Then I went and got the rom called omni. I tried that and the same thing. (Load in & fail). I will try to put some pics of what it looks like if I can. So had anyone else run into this yet?
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] Virus.Shell:
What version of SS are you running? Also, as far as I know, Omni can't run since it's AOSP based. With SS it's TouchWiz only due to the locked bootlader. Try putting it in the Stock Rom slot after doing a backup of it. That's where I usually flash over so I don't have to bother with smaller sized partitions.
[Xoom Q&A, Help & Troubleshooting] Kabish:
I just recently purchased a used Motorola XOOM Verizion 4G tablet. The device has been working flawlessly until I noticed that the battery usage over night went from 98% to 34% without anyone touching the tablet. I installed Walklock Detector on it and charged it to 100% again and let it sit. 13hrs latter the battery was down to 44% without any usage. According to Walklock this is what is keeping the tablet awake:

motoril-recovery-wklock

MMRIL_INIT_WAKE_LOCK

Both those processes are showing a "wake" time of the total time that the unit was unplugged.

Anyone have any ideas on what could be causing this? This is the first time google has failed me on troubleshooting something, it had no results.

Below is my unit details:

Model Number: Xoom

Android Version: 4.1.2

Equipment ID: IHDP56LU2

Baseband version: CDMA_N_03.1A.71PS

Kernal version:

2.6.39.4-g4e32b94

android-build@vpbs1)

#1 SMP PREEMPT Mon Sep 10 14:01:08 PDT 2012

Build Number: JZ054M

Any suggestions or help is much appreciated. I bought this unit for my daughter to use on an upcoming flight.
[Xoom Q&A, Help & Troubleshooting] Kabish:
I'd also like to note that this is factory (not rooted) and I have done a factory reset via the RECOVERY option of the device. This is a Verizon 4G tablet, however I don't utilize the 4G service, I just use the device for WiFi (no SIM card)
[Xoom Q&A, Help & Troubleshooting] runandhide05:
The lack of a SIM may be why it's draining. My simple suggestion would be turn airplain mode on. Then only turn on WiFi which will keep the radio from being turned on and see if that solves the wake lock

sent from(:::§:::)
[Xoom Q&A, Help & Troubleshooting] Kabish:
I installed JuiceDefender Ultimate and basically had it kill everything when the screen was off. I did however just try to put it into airplane mode and it's still keeping the kernel awake with the same process names.

Maybe I'll just root it and put a ROM on it and hope for the best. I do have an inactive Verizon Sim card, so maybe I'll throw that in and see what happens? We leave for our trip next week, wife will kill me if I brick it lol

Its now showing deleted_wake_locks waking the kernel over 2,000 times in the past 20 minutes.
[Xoom Q&A, Help & Troubleshooting] Kabish:
So I think having the Airplane mode turned on did help out some but still lost quite a bit of the battery.

11h 42min off the battery, 99% Awake time.

deleted_wake_locks 80,176 times

motoril-recovery-wklock 491 times

MMRIL_INIT_WAKE_LOCK 491 times

This is after a Recovery factory reset and the only software I installed was Wakelock detector.
[Xperia SP Q&A, Help & Troubleshooting] UltraWelfare:
Hello everyone..

I don't know what I did but when I try to charge my phone while it's off it boots up...

Search doesn't seem to help for me :/...

All I found is to install an app called "nomoarpowah" but not compatible with Xperia SP...

How can I fix that?
[Xperia SP Q&A, Help & Troubleshooting] Nanostray:
Offline charging bug. Did you install a mod, rom or something or did you flash a firmware?
[Xperia SP Q&A, Help & Troubleshooting] UltraWelfare:
Before this I changed rom lots of times...I used SEUS to go back to stock then I rooted using "TowelRoot" and after I installed a recovery to flash SuperSU...
[Xperia SP Q&A, Help & Troubleshooting] KiranP23:
i too have same issue after using towerroot , - I too went back to stock after 205 update came, fresh flash stock rom after restoring TA partition

and after updating to 205 update i did TowerRoot , now when i charge phone turn on's when i connect to power
[Xperia SP Q&A, Help & Troubleshooting] smogf:
Just flash fix via recovery

http://xdaforums.com/showthread.php?t=2606107
[LG Optimus G (International)] tabrizz:
So here is my problem i tried to flash the firmaware V20A GER and everything was working fine but i didnt have network signal, so i decided to go back to the stock rom but now phone keeps rebooting it self and i have no signal, phone doesnt recognize my network operator, i tried to flash diferent modems none of them work, i really dont know what to do, i hope you guys can help me :)
[LG Optimus G (International)] Brontok:
flash stock jelly bean e97510h ( 43 NEU/EUROPE OPEN	V10H	LGE975	1002.58 Mi	7193 - http://lg-phone-firmware.com/firmware-Lg+Optimus+G-Tutti-20.html ) using these instructions http://xdaforums.com/showthread.php?t=2010624.. works every time.. if u still have problems then you`re doing something wrong.. as I said it works every single time..
[LG Optimus G (International)] tabrizz:
Thx for your answer i was wondering if it will work with my model LG-E976 from Peru?, and yes i tried with that tutorial but the kdz updater can extract the file i always error extracting file
[LG Optimus G (International)] Brontok:
sorry, in that case download your countrie`s firmware, one of these http://prntscr.com/3zrsk1... you can find them on the same page... the method should work on your device ..
[LG Optimus G (International)] tabrizz:
Ty and what about the error i get extracting the kdz file
[LG Optimus G (International)] Brontok:
it might be a corrupted kdz file, download it again, turn off your antivirus program and make sure you have correct drivers installed on your pc.
[LG Optimus G (International)] Creative9170:
Check in setting that do you have IMEI number or its lost? Also you can dial *#06# to check.
[LG Optimus G (International)] tabrizz:
when i try to check the imei without sim, it shows me the correct imei, but when i i put the sim in and try to check the imei it shows me "null" and the phone keeps rebooting it self every 5-10 minutes
[Kindle Fire Q&A, Help & Troubleshooting] lob455:
Background: Kindle Fire 1st generation. Stuck on "kindle fire" logo screen. This is a stock KF -- never any previous attempts to root it.

KFU is unable to connect to the device -- or get it into fastboot. I purchased a factory cable, and that also was not successful. (BTW, I have a different KF 1st gen that works fine, and KFU recognizes it and can fastboot perfectly fine with that one).

I also attempted using the Firekit utility on a Debian Linux system. The tool seems to have the same issue -- gives me a "error: device not found" message when trying to set bootmode.

The "Post #1" HOW-TO by kinfauns talks about the bad bootloader scenario, and it mentions opening the case to short a circuit in order to enable USB boot. Can someone please point me to a link regarding this shorting technique? I think that is my next step.

Thanks,

lob455
[Kindle Fire Q&A, Help & Troubleshooting] sd_shadow:
Does it show up in Device manager? as kindle, android phone, or something else...?
[Kindle Fire Q&A, Help & Troubleshooting] lob455:
No. When connected to the Windows7 machine, the bootloop-stuck KF is not recognized at all (regardless of whether using the standard USB cable or the factory cable).

On the working KF which was purchased from Amazon at the same time, Device Manager shows this working KF as "Android phone".
[Kindle Fire Q&A, Help & Troubleshooting] Thepooch:
Fairly certain your battery is dead http://xdaforums.com/showthread.php?t=1623244 . If so you can shock it`s inards and hook up fastboot cable all day long and it wont make a bit of difference till you get a new battery.
[Kindle Fire Q&A, Help & Troubleshooting] lob455:
Thanks to Thepooch. Progress has been made. I was admittedly very skeptical about the dead battery theory. This Kindle Fire had been connected to a charger for literally days if not weeks. But I grabbed my wife's 2A charger and connected it.

Okay. Here is where the weird part starts.....

After several hours on the 2A charger, I hit the power button and got a TWRP Recovery screen! I was astounded. When using KFU, I have always gotten "ADB Status: Offline" and "Boot Status: Unknown" with this unit. I still do. But I have certainly tried the KFU selections of "Install Latest TWRP Recovery" and "Install Latest FireFireFire". Even though the utility returns messages that imply it was not successful (typically "< waiting for device >"), the only thing I can figure is that it was successful at least once. Even today when I run KFU, it still behaves as though it does not recognize the unit. Also, Device Manager still does not see the Kindle Fire.

So, now I have a Kindle Fire that seems to have good TWRP Recovery and FFF (I get the white & blue Kindle Fire logo now when booting). And this is a good thing, and a major step past the infinine white and orange Kindle Fire logo boot screen.

However, since I can't apparently connect to the unit via USB, I can't put a ROM on it to install. This is where I am stuck now.

Please let me know if you have any recommendations.

Thanks again.
[Kindle Fire Q&A, Help & Troubleshooting] Thepooch:
First you must fix your driver. Unless it shows up in device manager as android composite adb interface. I still have question of it's proper installation since mounting sdcard is connected to a proper install.

adb push rom.zip/sdcard/

shift plus right click on kfu's tool folder select open command window here. Type

adb devices

you should get a number string code 1234××××××××× device if it says offline then driver is not proper. If it says 1234×××××××××× device then your good.

Type adb push <---leave one space here drag and drop the file you wish to push into terminal , then one more space , /sdcard/ it takes some time depending on file size. When it's done it will show records in and records out along with the time that the push took. If successful make a backup and then wipe cache, dalvik, and system. Flash rom.zip/gapps.zip reboot system. There is a catch 22 is the recovery packaged with KFU new enough to flash newer ROMs with full s-Linux support follow the steps in my guide highlighted in my signature to at least flash rooted stock before proceeding. [MENTION=4267571]sd_shadow[/MENTION] 's Rom would be perfect for first flash.

Edit: Side note modifications need to be made to driver to keep adb working on custom ROMs as some have been added prior this helps but the device ID changes with each new build ics, kit kat and so forth.
[Kindle Fire Q&A, Help & Troubleshooting] lob455:
Thanks [MENTION=4571227]Thepooch[/MENTION] for the detailed reply.

I spent several hours playing with this Kindle Fire, a different Kindle Fire (stock unit that works), regular USB and factory cables, kfu, and adb. Here are my observations that may or may not be significant:

1) With the working stock Kindle Fire: this shows up in Device Manager as Android Phone > Android Composite ADB Interface. In KFU, this working Kindle Fire shows ADB Status: Online and Boot Status: Unknown. If I run the "adb devices" comand, it happily gives me a 17BExxxxxxxxxxxx response.

2) With the non-working Kindle Fire that I am working with: This does not show up in Device Manager UNLESS I am in the FFF (white & blue logo screen) with the 3 boot choices listed at the bottom of the screen (Normal Boot, Recovery, Reset Boot Mode). If those 3 choices are shown, then Device Manager recognizes this as Android Phone > Android ADB Interface (it does not say "Composite" -- no matter how hard I try to delete that Android ADB Interface driver). This non-working Kindle Fire then disappears from Device Manager completely if in any TWRP screen or any FFF screen other than the one with the 3 boot choices at the bottom. When I run the "adb devices" command, I get a message "List of devices attached" with nothing below (no numbers or anything).

I suspect that you are correct -- that I am fighting a driver issue -- but I don't know how to get the Windows 7 computer to recognize the non-working Kindle Fire as a Android Composite ADB Interface. It happily recognizes the working Kindle Fire as Composite, so I know the driver is on the PC.

Any ideas of how to go forward are appreciated. I think that I have tried everything that I know to try on that Windows 7 PC, so at this point, my next plan is to play with this Kindle Fire using the FireKit tools and a Debian Linux PC. Maybe that will help -- or at least I will learn something.
[Kindle Fire Q&A, Help & Troubleshooting] Thepooch:
Android adb interface alone is a detection of fastboot composite is normal boot. This could be due to a partially broken shell try while the device is in recovery not at the bootloader your bootmode is iffy.
[Kindle Fire Q&A, Help & Troubleshooting] sd_shadow:
What is current Twrp versiom? 2.7.1.0?

If the problem is Kindle software, a could try a couple of things

adb commands should not work in bootloader mode

fastboot commands should work in bootloader mode

try

fastboot devices

if that works could try flashing twrp, I would Flash a different version so you know it worked, like 2.6.x.x http://techerrata.com/browse/twrp2/blaze
[Kindle Fire Q&A, Help & Troubleshooting] lob455:
Thanks [MENTION=4267571]sd_shadow[/MENTION] for the reply.

In recovery mode, TWRP reports that it is version 2.6.3.1

I did try the "fastboot devices" command. When I am in the initial FFF screen (blue & white kindle fire logo with "Press power button for boot menu") or I am in the FFF menu with the 3 boot choices at the bottom (Normal Boot, Recovery, Reset Boot Mode), the "fastboot devices" command returns "0123456789ABCDEF fastboot". I didn't make up that number. It reports the hexadecimal digits in order from 0 through F, followed by the word "fastboot". It is pretty apparent that this is not a valid device ID number, but it is reporting something. I just don't know what it means.

If I am in any screen other than those, the "fastboot devices" command returns nothing, and it goes back at the command prompt.
[Kindle Fire Q&A, Help & Troubleshooting] sd_shadow:
I press the power button, to show boot menu (Normal Boot, Recovery, Reset Boot Mode) so it will pause the boot process for 2 mins or so.

the "0123456789ABCDEF fastboot" could be good, I believe that is what i usually get, and would go ahead and flash twrp.

fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img (or whatever version you are trying)

or try the reboot command

fastboot reboot
[Kindle Fire Q&A, Help & Troubleshooting] Thepooch:
When in recovery if there is no adb my first thought is driver. Two other things are possible missing or broken shell or broken recovery. I myself lean to the side of it being a driver issue. Attach your working Kindle to pc while in recovery. Type adb devices it should say 12345678 blah blah recovery. If it does not then it's your driver.
[Kindle Fire Q&A, Help & Troubleshooting] lob455:
[MENTION=4267571]sd_shadow[/MENTION] -- the "fastboot flash recovery openrecovery-twrp-...." command worked, and TWRP now reports that it is running version 2.7.1.0 (it was 2.6.3.1). It was immensely satisfying to find a command that this Kindle seems to like. Seriously. Thank you.

My next stupid question is, can I use another fastboot command to program the ROM, or can I use some fastboot command to load the ROM on sdcard via USB and then install it with TWRP? If I can do either of those things, then I think this problem is licked.
[Kindle Fire Q&A, Help & Troubleshooting] Thepooch:
Just place a Rom on your Sdcard and flash it.
[Kindle Fire Q&A, Help & Troubleshooting] sd_shadow:
Try the mount option in twrp again
[Kindle Fire Q&A, Help & Troubleshooting] lob455:
[MENTION=4267571]sd_shadow[/MENTION] [MENTION=4571227]Thepooch[/MENTION]

Thanks both of you for your help. But not all stories have a happy ending.

Over the past couple of days, I have been fighting a battle with the battery. The battery charge level indicated in the main TWRP menu would decrease even when connected to the 2A charger. I found that I could temporarily add a few percent charge by disconnecting the USB cable, reconnecting to the 2A charger. However, that trick would only last for a few minutes and a few percent charge, and then the power button light would go out and discharge would start again.

I think that the battery is now pretty dead. Power button light stays off event with the charger connected. If I disconnect the USB cable and reconnect, then I can *occasionally* get the power light to go green then orange, and it will fire up into a FFF blue&white logo screen, but then it shuts off again.

At this point, I think I have to decide if I want to spend the $ for a replacement battery and then try to fight the rooting battle again. I was never able to get the PC to recognize the device in normal mode so no adb -- only fastboot would work.
[Kindle Fire Q&A, Help & Troubleshooting] Thepooch:
The battery will always charge in recovery. When it goes flat you end in a 5 second boot loop. Try 2 things since your bootloader is equipped to hand such things as a failsafe attach to pc via USB right when it powers on long press power button till it powers off and let sit for 24 hours. The low level charge might even kick in and indicate charging on the screen if so let it sit and it will eventually boot properly on its own. Good luck
[Kindle Fire Q&A, Help & Troubleshooting] sd_shadow:
I suspect it's the usb port that is bad, not the battery. The Kindle's usb port is weak and has a high failure rate, it can be repaired but likely not worth it, unless you know how to solder connections.
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] marknderm:
AT&T Note 3 N900A/rooted with towelroot n safestrap.

After I rooted my AT&T Note 3 (N900A)and then loaded in the newest version of safestrap, (everything went fine no problems getting any of that working)

After all that, I rebooted and did another backup of my rom, (3rd backup) reset the phone and went back into recovery again. I made the 1st slot active (in safestrap) then I tryed to do a recovery of one of the backups that I made. It went the whole way through, and then said: failed. So I then tried every other back up. And they all did Tha same thing, (load in &fail). So I thought it may be the backups that I made. Then I went and got the rom called omni. I tried that and the same thing. (Load in & fail). I will try to put some pics of what it looks like if I can. So had anyone else run into this yet?
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] Cod3L1ne:
I think your issue is your backup... you should do it from ?(SS)?

Sent from N900A ThunderKat HeadQuarterZ
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] marknderm:
I should have said something in the last post. The backups I made were u in SS. and when I try to load a sock backup in slot 1234 it fails. I haven't tried to load it back in to the stock slot, because that is the only one I have working, I don't want to mess it up.
[AT&T Galaxy Note 3 Q&A, Help & Troubleshooting] marknderm:
Well I found that log file. I'll try to put it up here. Still nothing I try works when I make a backpack in safestrap and then try to restore it. It still comes up saying failed. I wish there was a way to take a screen shot while I'm in safestrap.
[General Questions and Answers] Kobro:
I had a pattern lock on my phone. I forgot the combination, so I selected the get pattern via gmail option. I got an email saying: "your pattern is 31556" what does that mean? Its a pattern, not a pin or password, so what do the numbers corespond to?
[General Questions and Answers] TimSimonds:
Try look at it like this...

1 2 3

4 5 6

7 8 9

You would start at top right and finish on the one bellow that..

(Not sure why it has 5 twice tho)

Sent from my GT-I9300
[General Questions and Answers] Paget96:
go to android device manager on pc, and log in on same account as on phone, your phone must connect to the internet, then on pc appear ring, lock and i think reset.. click on lock,and enter a password which you want, and unlock device ;)

dont forget to press thanks if this work to you ;)
[General Questions and Answers] Kobro:
i tried that, i reversed the numbers, everything. i cant make heads or tails out of it.
[General Questions and Answers] Kobro:
thats what i did in the end, but i still want to know what the numbers mean.
[Galaxy Note 3 Q&A, Help & Troubleshooting] Android525:
I bought a note 3 from someone on kijiji. I did not do my due diligence in checking that there was nothing wrong with the phone before I bought it. I have some experience rooting androids as well as using customs wrong but not for several years when I had an LG G2X which didn't work properly (which is why I got into it).

Anyway I am really stuck with this phone. The model number SM-N9006. It is unlocked. It is running Android 4.4.2.

This is where the weirdness starts: It appears to be running an HTC bootloader?(the little android logo is the same one as HTC). I cannot boot into anysort of recovery mode and doing a factory reset doesn't really work. It puts the phone back the way I got it but it is definately not stock factory. I cannot sync my google contacts, and I randomly get weird push notifications in a language I don't understand but appears asian (characters).

I really just want to figure out how to completly wipe it and install a new rom from scratch, it doesn't really matter if its a stock rom or a custom rom.

A friend of mine has to wipe phones sometimes for his job and he got this information from his work software:

Model : SM-N9006

OS : 4.4.2

Firmware: N9006ZCBMIT3

Kernel Version : 3.4.0-1590669

se.infra@RO304-14#1

Wed Sep 11 23:59:42 KST 2013

Build #: JSSI5J-N9006ZCUBML5

Odin Version: Odin3 V3.09.3

What happens when I boot into recovery is that a menu will show up but you cannot select any of the options. I also cannot boot into odin mode.

What my friends work software does is secure wipe the phone and restore it to the stock image stored on the phone. However it did not work properly because the rom stored on the phone is not the stock rom.

I would really appreciate any help, advice, what to try next. I don't have alot of experience with this stuff and I really can't afford to just buy a new phone.
[Galaxy Note 3 Q&A, Help & Troubleshooting] BoZo.+_+.POISON:
not gonna lie u got the chinese note 3 clone probly running MTK chipset
[Galaxy Note 3 Q&A, Help & Troubleshooting] Bibz0r:
Yep, N9006 is the Chinese clone version.

Have you tried flashing the stock firmware on SamMobile via Odin? Can you at least get to download mode?

EDIT : Check this link, it should help you : http://www.androidjinni.com/update-galaxy-note-3-chinawcdma-n9006zcubmj3-android-4-3-2417/
[Galaxy Note 3 Q&A, Help & Troubleshooting] AO7:
There is no way he could even get it to connect into Odin. Forget about flashing stock.
[Galaxy Note 3 Q&A, Help & Troubleshooting] Bibz0r:
Have you turned on USB debugging mode?

http://www.androidjinni.com/2-best-ways-to-enable-usb-debugging-mode-android-511/

Then, follow this procedure :

http://www.androidjinni.com/how-to-update-your-android-device-firmware-539/

Let me know if any of this doesn't work and I'll try to help you the best I can.
[Galaxy Note 3 Q&A, Help & Troubleshooting] AO7:
His phone is a clone. How could a stock factory image run on a system which is completely different? It would be like attempting to flash a stock Nexus 7 image onto a Galaxy s4