yashsingh1/xdaforums huggingface dataset:
[Xperia Z1 Q&A, Help & Troubleshooting] xasbo:
Well, it really depends on what exactly you formatted. If it was just sdcard0, most of the "brains" are still there. If you nuked everything that's physical on the internal SD, you're in worse trouble. But I don't know what you did.

You didn't include the recovery keypresses, but I'm guessing if you try to boot the phone normally (just pressing power button), you never get the vibration pulse when it turns on? If not, make sure to use the force-off button by the sim card (hold it for 10-15 seconds) to make sure the phone is off and not stuck on. If that still doesn't work, I think your best bet is to reach out to a service center.
[Xperia Z1 Q&A, Help & Troubleshooting] Sari95:
Hmmm... that I am not sure of.

Exactly! no vibration nor LED light when I push the powerbutton. Imagine yourself pushing the button, yet it is as if you did not push it at all. I have tried the force-off button too, so my last and final solution seems to be the service center.

Thanks for your replies! HIghly appreciated :)
[Xperia Z1 Q&A, Help & Troubleshooting] Sari95:
WOOOPPP! I have some kind of development actually. Now, when I plug the device to the wall or computer, a red

LED lights up for about 3 seconds before disappearing. However, from here nothing happens and it is dead as usual.

Any idea how to go further from here o.O?
[Xperia Z1 Q&A, Help & Troubleshooting] lil-diabo:
From what I've read. That means the battery is completely dead.

I believe you need to leave your phone charging for a few hours/overnight and sometimes it will get recognised by flashtool
[Xperia Z1 Q&A, Help & Troubleshooting] xasbo:
This is a good point, I didn't consider a dead battery scenario (though it makes a lot of sense versus the phone just doing nothing). I haven't actually read about cases where USB charging will bring back a super dead phone, but it's theoretically possible if the battery were removed and charged manually. That process, however, is definitely only for people who know what they're doing with potentially explosive battery chemistry. If nothing else, leave it plugged in for a while and see what happens.

I remember posting in another thread where someone killed their battery. The best preventative measure is to make sure you never get below 10% or so. The generally dispersed "knowledge" that taking the battery to 0% is good for calibration is NOT TRUE. These are Li-ion batteries, and deep discharges permanently reduce the battery capacity.
[Xperia Z1 Q&A, Help & Troubleshooting] Sari95:
Great point, you two.. This reason seems quite probable too. However at the same time, it is WEIRD if the battery suddenly dies as a result of formatting the internal SDcard :l

Maaan, I had a slight hope, but I'll try charging it overnight.

Worst case scenario, the service center finds out I had rooted it and I have to pay for the service.... :(
[Xperia Z1 Q&A, Help & Troubleshooting] lil-diabo:
http://xdaforums.com/showthread.php?t=2574764

There's an entire thread dedicated to how people bricked their phones. Have a look there for some info

It all relates to flashing phones, but maybe what you done had some kinda of a similar effect

Do you remember how much charge you had left?

Supposedly the system loses calibration with the battery and and and and (Most of this relates to flashing though, so hopefully you just have a completely dead battery and an overnight charge will fix it back up.

I also don't think you lose warranty from having your phone rooted?

Think voiding warranty only applies if you unlocked your boot loader... - I could be wrong though.

Good Luck!
[Xperia Z1 Q&A, Help & Troubleshooting] eclyptos:
Actually I saw this behavior on deads Z1 thread, sorry to say, this actually is not a good sign.

Yes, I will suggest this too and when your phone apparently will be charged try just to push volume down and connect via usb to pc and see if it will be recognized. If he dose flash a stock FTF immediately.
[Xperia Z1 Q&A, Help & Troubleshooting] Sari95:
Yea, I read through a few pages of that thread, but didn't feel it covered my case. I had a minimum of 89% of battery and it was charging. Hmm.. about the battery calibration, the day before this happened, I charged my phone to 100% and used Battery calibrator, which is an app in Play Store to calibrate it, so this shouldn't be a problem.. However, I suppose something has happened during the formatting.

I am quite certain one loses warranty when rooted or has unlocked BL.

Indeed, this seems to be my last way out of this. Either it comes back to life in the morning, or I am doomed! haha :P I have even prepared FLASHTOOL and the firmware, if the phone actually comes back to life and is recognized by the computer.

I will update you on this! :) You are a very helpful group of people. I am grateful for your help so far :D :good:
[Xperia Z1 Q&A, Help & Troubleshooting] Sari95:
Woke up today and tested it. No sign of life at all :( so it is now sent to the service center..

Thank you for your help! :D You have helped me a lot :)
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] EknCn:
I don't understand how to change tee folder. Just want how to CM11 install my I9070P telephone. Thanks for help.
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] EknCn:
Now what im doing? I tried this way but it's not work. But i think i'm not change tee folder how?
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] shut_down:
I have I9070 phone, so I can't tell you what you are doing wrong. Did you follow every step in that guide?
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] EknCn:
Yes i do. I'm trying flash and say "Installation Aborted"...
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] shut_down:
For that part take a look here: http://xdaforums.com/showthread.php?t=2302599
[T-Mobile LG G2] rebar71:
My phone is rooted - no recovery. I have received the OTA "g" update twice and supposedly processed it twice. But my phone still reports "c" version.

Does anyone know what's different/changed with the OTA?

Is it worth the trouble to back up and revert to stock so I can properly process the update?
[T-Mobile LG G2] mannequin:
http://xdaforums.com/showthread.php?t=2574911

but to sum it up:

wifi/data connection seems more reliable, they fixed the fonts, brightness slider stays put once auto brightness is enabled (the annoying lower brightness screen auto adjustment seems to be gone too!), touch screen issues (which i had very rarely to begin with) are not there anymore but surely this needs more testing.
[T-Mobile LG G2] rebar71:
Thank you. I just processed the update via the LG Support Tool.
[T-Mobile LG G2] mantici:
Use the support Tool

I had the same exact issue, rooted with not recovery. Received the update several times, phone rebooted, got about 40% through the update process, rebooted again and didn't actually install anything.

Checking the version number was still on D80110c.

My wife's g2 unrooted upadated fine.

I used the LG support tool, took about 1/2 hour and all is well.

download it here:

http://csmgdl.lgmobile.com/client/app/B2CAppSetup.exe

or you can pull it from my copy account:

https://copy.com/zRBNXz7xPY8bhzq0

oh and if you're not familiar with copy. . .like dropbox, but 20 GB free, 5GB for each referral

here's my referral:

https://copy.com?r=6b3vjR

i did lose root, but that was easy to get back:

http://www.andromods.com/root-unlock/how-to-rooted-tmo-lg-g2-d80110g-ioroot.html
[Moto G Q&A, Help & Troubleshooting] oldblue910:
Hi everyone,

So it would appear that the current builds of CWM and TWRP for the retail XT1032 Moto G won't boot on the Google Play Edition, at least not while booting from memory.

I've tried using fastboot boot recovery.img and it simply reboots and boots into the stock ROM normally.

Since factory images aren't available, I won't attempt to do a perm flash (fastboot flash recovery recovery.img) because I don't want to overwrite stock recovery without dumping it first (for archival purposes).

So, I guess my question here is twofold.

1. Has anyone else with a Moto G GPE had luck booting CWM or TWRP?

2. If not, is someone willing to try to get a version of one or both that WILL boot?

Any insight and help would be appreciated!
[Moto G Q&A, Help & Troubleshooting] :
Have you tried the Supervboot method? That may allow you to root without modifying the recovery.
[Moto G Q&A, Help & Troubleshooting] joel_sinbad:
Maybe it sounds dumb, but did you unlocked the bootloader first? maybe you just can flash the recovery safely since the GPE its Android 4.4.2, you can flash the same stock recovery from the US Retail 4.4.2... I don't see why the recovery must be updated on the GPE since it has the same Android version as the other 4.4.2 firmwares...
[Moto G Q&A, Help & Troubleshooting] oldblue910:
I'll check into that.

EDIT: Not going to work. It would involve changes to the boot image, which I also don't want to do. I want raw, untouched dumps of system, boot, and recovery. I get the feeling that the only way to get that right now is going to be booting CWM or TWRP from memory using "fastboot boot," but that method doesn't currently work with the currently available Moto G builds of TWRP or CWM.

The recovery is different between each and every Android ROM. The stock recovery from the retail ROM would probably boot but you wouldn't be able to flash GPE OTAs with it. And yeah, I unlocked the bootloader before I booted it for the first time.
[Moto G Q&A, Help & Troubleshooting] joel_sinbad:
I saw this from a post from XDA but maybe you can try it:

conect via adb shell or in terminal emulator type: cat/proc/mtd and press enter

you will see which is recovery partition and then type: dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img (note that mtd1 you must replace with number which is recovery partition)

after that you will have recovery.img on your sd card
[Moto G Q&A, Help & Troubleshooting] oldblue910:
OK so I downloaded the stock XT1032 US falcon_umts images for Android 4.4.2. I did fastboot boot recovery.img on the stock recovery from those images. It worked, so the bootloader is definitely capable of booting a recovery from memory. I think this is more an issue with the actual custom recoveries available. With that said, anyone up for trying to get this working? I'll happily be the guinea pig for any test builds.
[Moto G Q&A, Help & Troubleshooting] oldblue910:
Unfortunately, that only works if you're rooted. That's why I'm looking to boot a custom recovery from memory. I'll have root access via adb shell and be able to dump to my heart's content without overwriting the stock recovery or the stock boot image. Thanks for the suggestion, though.
[Moto G Q&A, Help & Troubleshooting] scott_doyland:
[MENTION=3423169]oldblue910[/MENTION] I don't think this method changes boot.img. it just boots a custom boot.img from your PC and roots phone. On next boot it boots boot.img from the phone as normal.

BTW I'm on non-GPE 4.3 stock recovery and can issue

fastboot boot recovery.img

to boot into a custom recovery.

However I believe on nexus devices the option to boot a recovery from PC was removed but you can still do it using some weird parameters on the command - maybe the same type of thing on moto g GPE when booting just a custom recovery??

See following link for the parameters on nexus 7 (which is most likely just for nexus 7 but you get the idea)

http://xdaforums.com/showthread.php?t=2380675
[Moto G Q&A, Help & Troubleshooting] oldblue910:
Thanks for clarifying about the boot.img. I'll look into it some more.

As for "fastboot boot", every Nexus and GPE can do it as long as the bootloader is unlocked. I've never had any issue booting recoveries from memory except on the GS4 GPE. Not to get off topic, but touch recoveries are useless if booted from memory on the GS4 GPE. That's not so much of a problem for CWM since you can navigate with the volume and power keys, but TWRP, forget it. If you perm flash, everything is fine.

EDIT: That's interesting about the Nexus 4. Apparently that was a bootloader change beginning with Android 4.3. I can confirm that more modern Nexus devices do not have this issue. Weird.

Anyway, I'm going to look into that root method some more. I'll report with success or failure.
[Moto G Q&A, Help & Troubleshooting] oldblue910:
OK, just an update. Superboot doesn't work with the Play Edition ROM. If you fastboot boot it (I tried using normal Android fastboot and the Moto fastboot that comes in the zip file), it just boots to a blank screen and hangs. No boot animation, no nothing.

Obviously there's something different somewhere between the GPE and the retail US XT1032. Not sure what it is...but yeah, right now none of the custom recovery kangs work and superboot doesn't work. The only thing I've managed to boot successfully using fastboot boot was the 4.4.2 stock recovery for the retail US XT1032.
[Moto G Q&A, Help & Troubleshooting] oldblue910:
At this point I'm going to loop [MENTION=709835]a1Pha[/MENTION] into this thread and ask if he has any thoughts, since he created the working kangs of CWM and TWRP that people seem to be using.
[Moto G Q&A, Help & Troubleshooting] joel_sinbad:
I just rooted my XT1032 US Retail 4.4.2 with Superboot, it booted a weird purple screen and then went black screen, but after Hard Rebooting, the phone was rooted, did you checked that?
[Moto G Q&A, Help & Troubleshooting] oldblue910:
Just checked. There is no su binary in /system/xbin or /system/bin/.ext and there is no Superuser.apk file either.
[Moto G Q&A, Help & Troubleshooting] a1Pha:
Interesting. So did I understand this correctly, that flashing a stock recovery from non-GPE Moto G does work?

Which version does your bootloader show? Which kernel version shows up in phone settings?
[Moto G Q&A, Help & Troubleshooting] oldblue910:
You understand correctly, yes. The bootloader version is 41.05 and the kernel version in settings is 3.4.0.
[Moto G Q&A, Help & Troubleshooting] a1Pha:
Looks like we have to wait for GPE sources to be released to adapt the kernel to the new bootloader. They should release the sources quite soon, so said a source of [MENTION=4112553]dhacker29[/MENTION] ;)
[Moto G Q&A, Help & Troubleshooting] oldblue910:
Sounds good. Thank you very much for your help! Let's keep this thread open for continuing discussion once the sources are released. Once we have kernel source, I'll be happy to test any recovery builds on my GPE device if you need testers.
[Moto G Q&A, Help & Troubleshooting] dhacker29:
The GPE Moto G uses ext4 data partition vs f2fs data partition for the Retail version so it's just a matter of having the right fstab in the recovery.
[Moto G Q&A, Help & Troubleshooting] vocoderism:
Try with this build

https://mega.co.nz/#!P8BQGYKK!StnnD0z91KLFxAgxQvSMUVWGC-A-4tcqiv9sgh1yXcw

alternate link

https://drive.google.com/file/d/0BxD_8WtIEc3SZnY2al9ZM0VTOFE/edit?usp=sharing

install with flashify app from phone booted in normal mode and then go to recovery
[Moto G Q&A, Help & Troubleshooting] Entropy512:
If you go through a1pha's thread, you'll find a TWRP repack from me that was based on a stock 4.4 kernel. Can you try that with "fastboot boot"? (In fact, that particular release from me is ONLY compatible with fastboot boot as it's too big to fit into the recovery partition...) That particular build has a lot of flaws, but should at least let you flash SuperSU on your device so you can back up the stock recovery and kernel partitions.

My observations on Monday are that a lot of recoveries that work properly when flashed to the device fail when attempting to boot them using "fastboot boot" - even on the non-GPe variants! None of the recoveries in dhacker's CM11 thread work with "fastboot boot" and neither does any one I build from Omni sources.

Many non-Nexus devices often have weird issues where "fastboot boot" doesn't work properly. I know Omni lost at least two weeks on the Oppo N1 due to the fact that "fastboot boot" is broken on that device.
[Moto G Q&A, Help & Troubleshooting] insanespain:
I havent been on xda for a week or so, but I've been dying to get root on my GPE Moto G. I just ran across this thread and I'm so happy people are working on this thing. But am I reading correctly? Sorry if i'm not understanding, I'm still a novice, but can I currently flash a stock version of either CWM or TWRP onto the device itself and it will boot? Then I can root from there? I understand we cant boot a recovery from a pc, but if I can go ahead and flash one to the device and get root, that would be amazing.
[Moto G Q&A, Help & Troubleshooting] erikivy:
My GPE is rooted with Paul o'brian's superboot. It should work for you too.
[Moto G Q&A, Help & Troubleshooting] insanespain:
Which superboot zip did you use? I'm trying it and can't get it to do anything. Phone just hangs at a blank screen when I run the superboot bat file. And yes my bootloader is unlocked.
[Moto G Q&A, Help & Troubleshooting] theoneofgod:
Recovery and root here:

http://xdaforums.com/showthread.php?t=2635706
[Moto G Q&A, Help & Troubleshooting] insanespain:
Thanks for nothing. None of that applies to a GPE Moto G. So far I've been unable to use any regular Moto G root methods on my GPE successfully.
[Moto G Q&A, Help & Troubleshooting] theoneofgod:
Because you lack the ability to read the thread, you missed that the purpose of it is to make a standard Moto G a Moto G GPE, recovery and root included.
[Moto G Q&A, Help & Troubleshooting] insanespain:
Exactly. And because you lack the ability to read THIS thread, we are talking about ACTUAL GOOGLE PLAY EDITION Moto G's, and how to get root and custom recovery on a REAL GPE. So pointing me to a thread that tells me how to convert a standard Moto G, does me absolutely no good. But thanks anyways.
[Moto G Q&A, Help & Troubleshooting] theoneofgod:
Why don't you use the tool in the thread I gave you to flash CWM for GPE. After you do that, follow the instructions to root it using CWM.
[Moto G Q&A, Help & Troubleshooting] insanespain:
Because as of now, the way i understand it is that we can't use a version of CWM built for the standard moto g on our GPE devices. Everything in that thread you linked to, pertains to a STANDARD moto g. And even though they are the same hardware, there are some small differences that are causing issues with recoveries. Hence the entire point of this thread.
[Moto G Q&A, Help & Troubleshooting] theoneofgod:
Look, the thread gives instructions on how to turn a standard Moto G into GPE. Then after doing that process, you flash the CWM made for GPE, and then you root it. GPE is GPE, there isn't a special GPE (apart from maybe being signed) for the standard Moto G, they are all the same.
[Moto G Q&A, Help & Troubleshooting] insanespain:
Jesus, this is clear as mud. I wish someone would confirm this would work on a REAL GPE phone.
[Moto G Q&A, Help & Troubleshooting] theoneofgod:
Why don't you do us all a favour and try it yourself.
[Moto G Q&A, Help & Troubleshooting] erikivy:
Mine did the same. I then went to the play store and installed SuperSU, allowed it to update itself and all my apps requiring root then worked perfectly.

Also, if you are still looking for a functional recovery for your GPE, the attached one works fine for me. The dates are borked, but that's no big deal.
[Moto G Q&A, Help & Troubleshooting] Entropy512:
Any CWM releases that fail to boot on the GPE are broken and will also fail on any non-GPE G with 4.4.2 bootloaders.

Common problems, whether non-GPE with 4.4.2 bootloaders or GPE are:

1) Most 4.4 source-built recoveries fail to boot with "fastboot boot", but will work fine if flashed to the recovery partition

2) Repacks that are compatible with "fastboot boot" are too big to flash into the recovery partition - an example being the repack I posted in a1pha's thread. That particular repack is, for the most part, pretty terribad, but it's enough to allow you to flash SuperSU to root your device.

3) People new to Moto (including myself) forget that volup selects an entry in thebootloader menu and power just forces a normal boot no matter what is selected, leading to them thinking that their recovery is busted (this happened to both myself and Dees_Troy)

I have confirmed that Dees_Troy was able to "fastboot boot" the TWRP image I posted in a1pha's thread, and was also able to flash and run a source-built TWRP that I sent to him (built from integrating dhacker's device trees and kernel into an omni configuration). e.g. his GPE is not behaving any differently, at all, from my non-GPE with 4.4.2 bootloaders.

Main delay has been that until someone was able to gain root, they couldn't gain a backup of the stock recovery for the GPe, and those people were nervous about flashing an unknown recovery to their recovery partition without a backup. The issues with "fastboot boot" resulted in a big delay.
[Moto G Q&A, Help & Troubleshooting] insanespain:
I said screw it and used that tool to install CWM and it did work and I was able to flash superuser.zip and get root working on my stock GPE. FINALLY. Someone really needs to make a specific thread for rooting and recovery on a stock GPE device to avoid all of this confusion and thread hunting.
[Galaxy Tab 3 Q&A, Help & Troubleshooting] kevinocouk:
has anyone got a solution to this problem please?

when my tab 3 is in recovery mode when i press the volume button to it skips a selection.

say im on the top selection "reboot system now" i press volume down once nothing happens, press again and it jumps to "apply update from external storage" press down again nothing press again and it misses "wipe data/factory reset" and jumps to "wipe cache partition".

same happens on the way back up to?

thanks in advance
[Galaxy Tab 3 Q&A, Help & Troubleshooting] gr8nole:
http://xdaforums.com/showthread.php?p=49486913

Sent from my SCH-I605
[Galaxy Tab 3 Q&A, Help & Troubleshooting] kevinocouk:
thanks very much :)
[Galaxy Tab 3 Q&A, Help & Troubleshooting] gkvidhu1979:
Use the latest philz touch recovery (unofficial build). You may find the link to this build in kumajaya's thread on CM 11.
[Verizon Samsung Galaxy S III] crmass:
I am running a 4.1.2. stock root and have not taken the 4.3 OTA update. I would like to update to 4.3 via Cyanogenmod 10.2, but the problem I have is how do I transfer app data from one to the other? When I flashed CM 10.2 and tried to restore with Titanium Backup, it could restore the apps, but not the data. Any ideas? Am I missing something?

Thank you.
[Verizon Samsung Galaxy S III] buhohitr:
make sure your phone is rooted! download SuperSu from the market and install it. Once it rooted you should able to restore data with Titanium BU.
[Verizon Samsung Galaxy S III] crmass:
All that was done, but for some reason I can't restore the data. I vaguely remember reading something about not being able to transfer data from a 4.1.2 ROM to one that is on 4.3.
[8125, K-JAM, P4300, MDA Vario General] bugone:
Hi, I havent had my O2 XDA Mini long.

I've got a 2gb memory card in it, and I want to set it so that when I receive a file (beam or bluetooth), it goes to the memory card instead of to the onboard memory.

I'm sure this can be done, but I can't find any mention of it.
[Samsung Galaxy Nexus] driodmaster92:
#include
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*/

Our Gerrit http://illugerrit.bricked.de/#/q/status:open,n,z

FEATURES

KNOWN ISSUES

DOWNLOAD

FLASHING INSTRUCTION

Changelog

Initial Build

19.01.2014

HALO From PA

Non Intrusive Call UI

Harware Key Remapping

Network Speed Indicator

MMS Package Updated

White Background for Settings [WIP]

Many More...Visit Here

​

Credits:

Ronald Ramsay II

AndrolinRoot

PA for GAPPS

Download :

http://illusionroms.com/

XDA:DevDB Information

Illusion 4.4, a ROM for the Samsung Galaxy Nexus

Contributors

driodmaster92

ROM OS Version: 4.4.x KitKat

Based On: AOSP

Version Information

Status: Alpha

Created 2014-01-19

Last Updated 2014-01-19