yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] AspiringDeveloper:
2 months ago I was installing a CM nightly and something went wrong (I think it was incompatible versions of CM & gapps) and the main result was I had no keyboard access. No amount of attempts to correct this were successful at the time. Things just seemed to be going from bad to worse quickly. Failing all else I picked some option for system restore (I can't recollect what at this point) and got a screen that it was downloading the OS (I presumed the default Samsung OS for the phone but I have no way of knowing) It just stayed on that screen for hours. (possibly because I was off my data plan at the time. I've heard (too late) that some upgrades require it). Since it was getting nowhere I powered down the only way I could... taking out the battery. Then nothing. No boot screen, no recovery, nothing. For over 2 months. Last night I charged it figuring I'd give it one more shot before tossing it in the recycler. Then it boots up! WTH? I'm so happy!!!

But my problem remains what it was prior to going dead... no keyboard and erratic behavior (in particular the back button rarely activates. It will vibrate when pressed but not DO anything)

Baseband= N7000UUBKK2

kernel ver. 3.064-CM-gb07657a

CM ver. 10.2-20130824-nightly-n7000

build number cm_n7000-userdebug 4.3 JSS15Q

gapps-jb-201308-signed.zip

So I've been given a second chance to do it right. What can I do to fix this? Any suggestions would be much appreciated even if it involves moving back to unrooted stock OS and firmware.

Thanks in advance,

A.D.

P.S. I will be getting my data plan back if I can get this working right. Wish me luck.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] XxPixX:
First an foremost then update - and do a full wipe before. If you still want CM 10.2 then just go for it, but you can also try out KitKat (OmniROM - original development)
[Galaxy Note II Q&A, Help & Troubleshooting] Stempanssi:
What recovery does the CM installer install onto the device, if running stock before installing?

If it installs eg. CWM, will "the rom" also update the recovery automatically when possible?
[Galaxy Note II Q&A, Help & Troubleshooting] alinux777:
No

i think the installer will update the recovery based on the version of CM your installing
[Galaxy Note II Q&A, Help & Troubleshooting] Stempanssi:
Nonono I mean if there is no other than stock recovery installed eg. Running completely stock.

I myself know how to flash and have done it multiple times, but I am just curious.
[Galaxy Note II Q&A, Help & Troubleshooting] alinux777:
yeah

sorry i got mixed up with the answer but i think it will install the latest cwm recovery on the version of CM your installing.
[Galaxy Note II Q&A, Help & Troubleshooting] Stempanssi:
Okay thanks! No problem!
[Nexus 5 Q&A, Help & Troubleshooting] tariq199:
[Q] Nexus 5 Screen back light flickers slightly & Touch pointer ghosts. Please Help

Hello there,

I bought my Nexus 5 (D821) 16 GB from the grey market in UAE. Now after a week of excellent performance my phone screen back light seems to flicker like blink all the time, its mostly visible when the screen is at HOME or when the screen is grey in color. I tried switching off the Auto Brightening system , making brightness to lowest or highest none of then seem to help the flickering.

the second issue is my touch screen goes Mad/Ghost touch/Phantom touch while i touch the screen but not move my finger. i just cant type anything.

FYI : I rooted the phone the day i bought it. And yah no Warranty!

Please Help!:(:(:(:(:(
[General Questions and Answers] faheemakbar18:
Hello guys

Got samsung galaxy note shv-e160k (korean)

I flashed stock official rom jellybean 4.1.2 (mc3) through odin

Now its stucked on samsung logo for 15 min (common with samsung on flashing via odin, you have to wipe data from recovery to pass that but here comes the bad part)

It cant enter recovery tried all methods

Vol up+ power( after loading start giving vibration with black screen)

Vol up+ vol down+ power( same as above)

Vol up+ home + power(same)

All key(same)

tried with adb reboot recovery command no use in download mode as well stuck logo

Now how to wipe data / factory reset or other method to enter recovey

Ps in prev rom i used rom manager to enter recovery but cant boot to rom here lol
[General Questions and Answers] z0rin:
Maybe you will find something useful here http://xdaforums.com/showthread.php?t=1710869&page=66
[General Questions and Answers] faheemakbar18:
no luck there, asked before

and i guess its general query if samsung device fails to enter recovery by button combo, there should be some method
[General Questions and Answers] xsenman:
korean phones, recovery combo may be volumedown+home+power or you can try flashing a tegrak kernel, look here for link

Check this out! Links to useful Guides and " Banned " Documentaries ​
[General Questions and Answers] faheemakbar18:
goes to download mode

tegrek didnt helped as well, recovery installs fine and can be accessed from rom using rom manager reboot to recovery
[General Questions and Answers] xsenman:
in tegrak kernel, you can do full wipes, factory reset, as well as backups before phone boots, just read the menu as it starts.

Check this out! Links to useful Guides and " Banned " Documentaries ​
[General Questions and Answers] faheemakbar18:
I cant find tegrek kernel for my build its jmb1
[General Questions and Answers] faheemakbar18:
plz suggest me other method to enter recovery or wipe data
[General Questions and Answers] xsenman:
Basically if you only want to do the wipes, you can use other tegrak kernel build for your device ( shv e160K) as long as they are the same Android version . After wipe you do not reboot phone but remove battery and enter download mode to flash your working ROM.

you must remember to to enter recovery menu before phone boots when trying this method. ( you will only have 5 seconds)

or

you can try the recovery tools for MY Android Collections ( link below)

Check this out! Links to useful Guides and " Banned " Documentaries ​
[General Questions and Answers] faheemakbar18:
Ok finally i can enter recovery

you have to press vol up and vol down and then power, on first vibrate pull power button but keep pushing vol buttons

you will get into recovery after a black screen (4 5 second)
[General Questions and Answers] gandrigoes:
I have the same problem too.

still, i cannot enter to recovery, even with your suggestion.

It end with text "samsung", any idea?

thx for the answer.
[Moto G Android Development] a1Pha:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

What is CWM?

Everything should work.

Installation:

fastboot flash recovery recovery.img

Download:

CWM

CWM Touch
[Moto G Android Development] Doublepranks:
Thanks I will try it later!
[Moto G Android Development] matmutant:
Linked to FAQ :)
[Moto G Android Development] ferreinf:
will try asap :)

edit: booted fine, backing up as we speak..............

Looks promising, i still prefer TWRP but now we need some new builds to flash, and i don´t care witch one works best ;)

thanks
[Moto G Android Development] nupi:
fastboot boot recovery.img does work, flashing it through fastboot does not do anything for me.

Edit: when booted with fastboot boot, flashing supersu was no issue whatsoever, my device is happily rooted now.
[Moto G Android Development] a1Pha:
What happens when you flash it? Any messages on screen? What happens, when you select recovery in bootloader? Are you sure you are selecting with VolUp? Power is not the "enter" key!
[Moto G Android Development] ferreinf:
Yeah Vol. UP e select when on bootloader, learn it the "hard" way, lol
[Moto G Android Development] ferreinf:
I guess I'm gonna stick with twrp, look at the dif in sizes

Sent from my Moto G
[Moto G Android Development] t-bon3:
I'd be more worried about the difference in dates, what is going on with the CWM backup?
[Moto G Android Development] ferreinf:
didn´t noticed the date 2023 lol
[Moto G Android Development] a1Pha:
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!

Thanks for the hint, has to be fixed. Shows creation date as January 1970. But shouldn't be an issue for functionality.
[Moto G Android Development] a1Pha:
I can confirm that restoring from backup works like a charm.
[Moto G Android Development] nupi:
That might be the issue - power has been the enter key on any other android device I have used :). I will report back.

Lo and behold, boot to recovery from QuickReboot does work with CWM, so it was the power key thing (probably simply turned the damn thing off).
[Moto G Android Development] Doublepranks:
Great job buddy ! Now lemme ask... rather beg you something, it's about CWM font size, please make it bigger, please!

I got this birth eyesight disease which usually isn't that much of a big deal but in this particular case the words are so small that i can barely read them! Please make it bigger or teach me how to do it myself!
[Moto G Android Development] a1Pha:
I will have a look at how CWM manages fonts and increase font size when I find it :)
[Moto G Android Development] Benowit:
Wipe cache partition don't work, the recovery frozen
[Moto G Android Development] a1Pha:
Works without any problem here. Which model do you have?
[Moto G Android Development] Benowit:
RETAIL-FR_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF
[Moto G Android Development] lost101:
'Wipe cache partition' working fine on RETAIL-GB_4.3_14.10.0Q3.X-76-LGG-8_cid7_CFC_1FF.
[Moto G Android Development] a1Pha:
This is strange, there are no partition layout differences between the different countries, as far as I know.
[Moto G Android Development] WiCiO_MeDi:
@up +1
[Moto G Android Development] Andiii:
could anybody help me out please because its not possible for me to boot CWM V2 or V3 (Moto G shows green Motorola Logo - after that Bootloader warning and Motorola logos and system starts). Its impossible to boot to custom recovery with the command fastboot boot file_name.img.

Same happens with TWPR builds (v3) from here

BUT

this Build does boot with the same fastboot command !

But i get an error if i try to create a backup:

/data/media/0/twrp/backups/ta8

E: Unable to create folder: /data/media/0/TWRP (

E: Failed to make backup folder

i had 4.3 Stock en.DE Rom with stock recovery copied the en.DE OTA file to SD Card.

After reboot the "system update" was recognized and i could follow the steps to install it.

So i have version 174.44.9.falcon_umts.Retail.en.DE on my phone.

My device was never rooted and the custom recovery was always booted temporarily via fastboot command. (to have a backup of Stock Rom in the pocket)

for ADB i use Minimal ADB tool and tried different Moto G drivers:

the official one and also Koush patched to Motorola

but since i have 4.4.2 its always the same problem....my Moto G won't boot into the recovery (only the one named "twrp_falcon_44.img" which sadly did not backup)

Would like to flash latest CWM or TWPR build to do a backup and test faux custom kernel....

Would anybody please help me?
[Moto G Android Development] r4v3rr:
CWM not booting :(

-Error message: no command

-XT1032 (Tesco)

-Updated via sideload (to Tesco 4.4)

Couldnt update OTA because of mods so I flashed stock 4.3 to be sure I was rid of all mods. The OTA then just didn't come through (typical).

So I sideloaded the update and here we are.

Anyone know why this is happening? Is using the 4.3 bootloader and the previous version of CWM the only work around?

Open to suggestions

Thanks
[Moto G Android Development] michalurban:
Im not sure but I believe you need ...

- CWM 6.0.4.5 on bootloader 4.3

- CWM 6.0.4.6 on bootloader 4.4
[Moto G Android Development] Andiii:
i tried to boot v2 (for 4.3 BL) and also v3 (for 4.4 BL) none of them started :(

is there a way to check which bootloader i have after OTA to 174.44.9.falcon_umts.Retail.en.DE?

This APP did not work - shows bootloader version: unknown
[Moto G Android Development] r4v3rr:
Yer I know m8....No joy.
[Moto G Android Development] Newmak:
I've the same issue. My stock rom is 172.44.falcon_umts.Retail.en.US (Kit Kat - Global GSM). Please help to fix it.
[Moto G Android Development] wolframio74:
anyone is having problems with backups? mine does the backup but when i browse to the backup folder theres nothing :S
[Moto G Android Development] lukas033:
When you get to the Android guy with the exclamation mark NO COMMAND, just press and hold the Vol Up button for about 10 seconds, then tap the Power button.
[Moto G Android Development] mr.death7:
Have you looked here : /data/media/clockworkmod/backups/ ?
[Moto G Android Development] michalurban:
Just to make sure - in bootloader, are you using Volume Down to highlight RECOVERY and Volume Up to select it?

I personally dont have any problems with this. I flashed the US Kitkat ROM (after many previous flashings) and then I flashed the CWM 6046 - and it worked without a glitch ever since.
[Moto G Android Development] Newmak:
The second download link worked fine for me. I've flashed again with that recovery, and now I've CWM. :)
[Moto G Android Development] I900-Nutzer:
Hmm - CWM 6.0.4.6 is backward compatible - for me it also works with bootloader 4.3
[Moto G Android Development] michalurban:
Good to know about backward compatibility. Not that I would be going back to 4.3, but still ... :)
[Moto G Android Development] r4v3rr:
Problem solved.

If anyone else is getting the "no command" error when trying to install CWM, Use the second download link.

[MENTION=709835]a1Pha[/MENTION] You may want to check the files or re-upload m8. I'm not the only person who had this issue.

Thanks
[Moto G Android Development] ShOrTyNaToR:
German Version , 4.4.2 OTA and CWM 6.0.6.4 (first download link) = No problems here.

Gesendet von meinem Moto G...
[Moto G Android Development] kieranc88:
help

So if I flash this through fastboot on stock UK kitkat ota ROM,I will have cwm ? I flashed the mirror 1 link and get a picture of a dead android when I boot recovery.
[Moto G Android Development] yeiyei0891:
For my 4.3 which file I need to flash for? I want to do a full backup of my phone (include firmware), and how a I can back later to stock recovery?
[Moto G Android Development] justjr:
I'm also getting a dead droid with 4.4... trying to flash v3.
[Moto G Android Development] eddvys:
So what are the changes in this version? Only that it supports 4.4 bootloader ? Don't know but previous version works like a charm.
[Moto G Android Development] zoological:
same here, and same with v3.

Damn
[Moto G Android Development] michalurban:
Any chance to be able to use "USB mount"?
[Moto G Android Development] AceDuff93:
As far as I know, KitKat doesn't come with this feature. Dev said it some pages ago.

Got it me too the first time...Rebooted, did reset and then flashed again. This second time phone booted into CWM correctly...Maybe you could try again! ;)

EDIT: Booted into bootloader cause I wanted to flash SuperSU via recovery and...CWM has disappeared! I'm going to investigate this, maybe I'll flash CWM again. Lol, this Moto G is a though gay, never had such problems with Sony devices...:-\

EDIT 2: Nevermind, looks like CWM was gone by my fault. Everything is fine! ;)
[Moto G Android Development] a1Pha:
Strange, the first download link is the "original" one, provided by [MENTION=4112553]dhacker29[/MENTION]. The second download link is just the first download link downloaded and uploaded again to another hoster. I'll try to reproduce the error...
[Moto G Android Development] zoological:
I'm still getting the "no command" and stock recovery.

i tried both files, same result.
[Moto G Android Development] tstivers1990:
Does this work with the Verizon Moto G (XT1028). Motorola doesn't allow you to unlock the bootloader with this device.

fastboot getvar all:

(bootloader) version: 0.5
(bootloader) version-bootloader: 4022
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x3
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8626 CS
(bootloader) serialno:
(bootloader) cid: 0x0002
(bootloader) uid:
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 12-06-2013
(bootloader) sku: XT1028
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Jan 20 8:14:26 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_verizon/falcon_cdm
(bootloader) ro.build.fingerprint[1]: a:4.3/14.10.0Q3.X-84-14/16:user/re
(bootloader) ro.build.fingerprint[2]: lease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.14.14.14.falcon_cdma
(bootloader) ro.build.version.full[1]: .Verizon.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_JB_3.2.3.04.03.0
(bootloader) ro.build.version.qcom[1]: 0.166.006
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.0-g741c020-00002-g4bec
(bootloader) kernel.version[1]: dcd (hudsoncm@ilclbld26) (gcc version 4.
(bootloader) kernel.version[2]: 7 (GCC) ) #1 SMP PREEMPT Thu Nov 21 21:5
(bootloader) kernel.version[3]: 5:40 CST 2013
(bootloader) sdi.git: git=MBM-NG-V40.22-0-gac19e15
(bootloader) sbl1.git: git=MBM-NG-V40.22-0-g114f094
(bootloader) rpm.git: git=MBM-NG-V40.22-0-g4018bbe
(bootloader) tz.git: git=MBM-NG-V40.22-0-g9043ffe
(bootloader) aboot.git: git=MBM-NG-V40.22-0-gbf98691
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 2/1
all: listed above
finished. total time: 0.059s
[Moto G Android Development] Kodaro:
Hello, 4.0.4.46 works fine here on 442.

If I want to reboot my device it says something like "root could be lost do you want to overwrite system/xbin?" Is Yes or No the better choice here?
[Moto G Android Development] t-bon3:
Unlikely unless someone adds MTP functionality to a custom recovery.
[Moto G Android Development] rapunzel11:
Have you tried to push volume up and power button together if you seen the dead droid with no command
[Moto G Android Development] dhacker29:
If you have SuperSu you'll get this prompt. Select no. If you're using koush superuser or are not rooted select yes
[Moto G Android Development] 98tiburonfx:
Can't mount sd card

I have a google play moto g and loaded cwm. I can boot into recovery but when I try to flash anything, cwm states that can't mount sd card. I went into mounts and it shows that the sd card is not mounted. I tried to mount and I get an error. Any help would be appreciated.
[Moto G Android Development] will8578:
I don't seem to be having any luck with any of the recoveries, i started off on 4.3 then updated to 4.4, does that mean im on 4.4 bootloader? Cwm backs up but just get bootloop when i install a rom, and twrp doesn't back up.
[Moto G Android Development] zoological:
Yep, it boot the stock recovery instead of cwm
[Moto G Android Development] dhacker29:
You MUST boot directly into recovery after flashing it and when you exit it will ask you if you want to disable stock recovery flash. Say yes. Otherwise android is designed to run install_recovery.sh every boot which patches a copy of the boot.img and flashes it to recovery. Overwriting your custom recovery.
[Moto G Android Development] rapunzel11:
If i have understood her/him correctly, it isn't possible to boot directly into CWM. So I think CWM is not or not correctly flashed.
[Moto G Android Development] frojnd:
Does CWM work on encrypted 4.4 (OTA) rooted version? Who managed to make it work and how. It would be most pleasant if users who made it work with 4.4 OTA and encrypted phone would share their experience. Thanx.
[Moto G Android Development] k-kuchen:
How do I boot directly into recovery in bootloader? Selecting Recovery just boots to Android. I can't get CWM and TWRP to boot

Edit:

Stupid me :( Vol Up is select, not the power button how I was used to
[Moto G Android Development] zoological:
u got the point
[Moto G Android Development] alonsoch:
ok i flashed the recovery and SU, but the recovery don't ask if i want disable the stock recoery...so, i think i have the stock recovery,,, again..i will try...

**EDIT**

all is working great, i have installed CWM thanks... one question, if in the future i want TWRP just i need reflash the recovery?

fastboot flash recovery twrp.img for example?
[Moto G Android Development] da900:
Yes.
[Moto G Android Development] alonsoch:
mount usb don't work, is a know issue?

---------- Post added at 01:31 AM ---------- Previous post was at 01:28 AM ----------

and one more thing, when i reboot to the system(in recovery)... when in boots the sd is not detected, i need reboot again the device to make the sd work..
[Moto G Android Development] BachuArg:
Im on kitkat with 4.3 bootloader and Cwm v2. I have the backup location issue and also the date starts with 2024.

Are these bugs fixed in v3 for 4.4 bootloader?

Are these bugs present in last TWRP?

Thanks

Enviado desde mi GT-P5110 mediante Tapatalk
[Moto G Android Development] BigBlue007:
Quick question:

I need the stock recovery from 4.4.2 in order to install a new OTA update (just a very small one, 1.9MB) that is available since yesterday here. With CWM installed, the installation of the OTA update ends up in a bootloop, because the OTA needs to be installed in the stock recovery. Actually, CWM comes up automatically and asks to install the OTA update, but this then fails with an error. You can exit CWM and reboot, but once the device has bootet, it sees that the OTA is not yet installed and reboots right away. You can get out of this loop by booting into the bootloader (pressing Vol-Down when the reboot occurs), start CWM manually, and then wipe the cache partition from within CWM.

Now, as said, I would need the stock recovery for 4.4.2. My model is XT1032. My idea was the following: There is this install_recovery.sh mechainsm on the device which normally is a pita when you install CWM because it automatically flashes back the stock recovery if you forget to launch CWM right after you have flashed it. That means that the stock recovery.bin must be somewhere on the device. The question is: Where?

In another thread here on XDA I found a stock recovery.img which should be for XT1032, but probably this was from a 4.3 ROM. I could flash it without any problems, and the device works, but when I tried to install the OTA update again, it failed again. This time it just reboots with no recovery coming up at all, probably because that stock recovery doesn't match for 4.4.2 and is simply not executed. The bootloop happens again of course, but I was easily able to recover from this again by flashing back CWM and formatting the cache partition again.

Any idea where to get the 4.4.2 stock recovery?
[Moto G Android Development] readonly24:
Try this one.
[Moto G Android Development] alonsoch:
can you post the zip OTA?
[Moto G Android Development] asheehanjr:
I'm getting a md5 mismatch error on 6.0.4.5 on my moto g us gsm on 4.4 bootloader after when I tried to restore from a backup. I turned of the toggle verification and still did the same thing. It said it created the backup successful but, I don't see anything in the cwm folder? Any Ideas? Thanks!
[Moto G Android Development] dexterdre:
someone could create a zip to flash for TWRP

Enviado desde mi XT1032 mediante Tapatalk
[Moto G Android Development] MobRookie:
Booting to recovery?

Hey,

hope I haven't overlooked the answer in the thread but didn't find anything similar....

I can't boot to recovery from bootloader. It just switches the phone off when I choose "Recovery" in bootloader. The only way I can get to recovery now is through ROM Manager... Did anyone encounter a similar problem? Or can you guys think of any solution to it?

Regards,

Lukas