yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Q&A, Help & Troubleshooting] albundy2010:
All the info you could need. More than you need.

http://xdaforums.com/showthread.php?t=2010312
[Nexus 4 Q&A, Help & Troubleshooting] Berrydroidcafe:
Wait a minute, did I just read in that link that a computer is needed? That someone has to type commands in the command prompt box? I'll BET you that if you have a non-functional adb on that computer, you're have a heck of a time flashing ANYTHING via fastboot. :p:D:cool:

Good night!

Sent from my Nexus 7 (2013)
[Nexus 4 Q&A, Help & Troubleshooting] albundy2010:
Are you trolling or you're just clueless?

You don't need adb period. Get that through your head already.

This is why noobs get lost. People that don't know the difference between a command prompt / fastboot / adb or any other command line tool for that matter.

Adb and fastboot use different drivers and different modes on the phone!

You absolutely CANT use adb period with the phone in fastboot mode. Which is the mode used to flash factory images with fastboot.

---------- Post added at 09:08 AM ---------- Previous post was at 08:52 AM ----------

And that guide is more complicated than it needs to be too!

Get the device into fastboot mode and connected

If you downloaded the factory images, extracted them once ( not the zip inside of the original archive) and put all those contents in your directory where your fastboot executable lives. Launch the flash all. Bat included with the factory images and you're done.

You don't even need to type of a single command, or even open the prompt yourself.
[Nexus 4 Q&A, Help & Troubleshooting] Skywalker.00:
...It has already been stated, you've not hard bricked your device. Which means there is hope yet ;)

I'm not familiar with the Nexus line. I use Samsung, but from what I've gathered the best thing you could possibly do is go back to stock and start over from scratch. Google search "Nexus 4 back to stock". Find a guide that you CLEARLY understand and follow it step by step, by step. You'll be back up and running in no time.

Also to connect to PC you may need to enable USB debugging in developer options, and as someone else stated install/reinstall your drivers.

Toolkits are convenient, yes, but in this case I would recommend a manual fix. Good luck, my friend :)
[Nexus 4 Q&A, Help & Troubleshooting] Berrydroidcafe:
Wow, here comes the name calling. Hmm? So in other words, you could just do away with it on the computer? Period? If I'm wrong, fine, I'd be the first to admit that, however, maybe the problem is, you might not be willing to try and understand the way I'm looking at this. Never claimed to be Einstein, just trying to help, maybe learn something on the way, I just hate it when I feel someone is being condescending.

I read the article/post, and I'm pretty darn good with computers, and maybe I miss the class on fastbooting and the such, but yes, you can double click on a .bat file and not have to enter a command, I'll let you have that one, l am not as dense as you think I am. All I know is, from the first time I rooted a phone back in 2009, all the things I've read, (no, I haven't read it all) getting adb setup is one of the first things you need to get set up, after getting the sdk.

Maybe that has changed I don't know..... Apparently we're looking at the same thing differently.

Sent from my Nexus 7 (2013)

---------- Post added at 12:48 AM ---------- Previous post was at 12:47 AM ----------

He can only boot into the bootloader and recovery.

Sent from my Nexus 7 (2013)
[Nexus 4 Q&A, Help & Troubleshooting] albundy2010:
Its not name calling.

I was truly not sure if trolling or if you're clueless to what we are talking about.

Fastboot is a program that runs on your computer. It is a command line program only. Which means it runs in your terminal / command prompt.

Adb does the same. A command line program ran.

Just because both run through in your command line doesn't mean they are same or are interchangeable.

For what I think it's the 5th time. When you flash a factory Image it goes through fastboot and fastboot only. Adb is not needed period.

Abd is not needed period to root either. The only reason people put in the guides ( and it's a damp stupid reason and shouldn't be there as far I am concerned) is to issue the adb reboot command. Either back into the fastboot again or recovery. Or if it's a toolkit because you have to use the commands since a toolkit can't press the hardware buttons.

I'm not being condescending. But there is only so many ways and times I can say adb and fastboot are not the same thing without saying you just don't get it.
[Nexus 4 Q&A, Help & Troubleshooting] pincher65:
Sent from my Nexus 7 (2013)[/QUOTE]for fastboot not required drivers adb and usb debugging.LOL

---------- Post added at 09:26 AM ---------- Previous post was at 09:11 AM ----------

Cheers [/ QUOTE] flash full picture of fast loading, but the version that was founded your CyanogenMod. I came across three phone after CyanogenMod 10 may not lead to an outbreak of 4.3. * And 4.4. * Only 4.2.2. (Call is not found). and then update fails
[Nexus 4 Q&A, Help & Troubleshooting] xanthrax:
[MENTION=2986645]albundy2010[/MENTION] , please excuse [MENTION=4087094]Berrydroidcafe[/MENTION] , I was personally misleading him to his conclusion when he asked me about adb and fastboot relation, you're right, Android Debugging Bridge isn't required in the factory images process neither rooting, fastboot is enough

I will contact him and explain him how it is, thanks for understanding and I apologize both of you

sent from my Darkside of Nexus 4
[Nexus 4 Q&A, Help & Troubleshooting] Berrydroidcafe:
I'll try to reconcile all of this because I still believe that there's a relationship going on with fastboot and adb. Maybe not in the sense that's in my head, and that may as well be wrong. Just have to get it straight so I won't be caught off guard the next time.

I think that maybe it's because usually when one is mentioned, the other is as well, seeing that both are part of the Android SDK package. I'll figure it out.

Thanks!

Sent from my Nexus 7 (2013)
[Nexus 4 Q&A, Help & Troubleshooting] Sivi.N4:
Wow, big discussion to come back from work to.

I cannot enable Developer Tools as someone told me to do, drivers are fine.

I will read that guide.. I figured Toolkits would be the easiest way for a complete noob like me to root my phone but I understand that it is terrible that I do not understand what these tool kits are doing. I will be working on my phone tomorrow, thanks for the posts.
[Droid Ultra Q&A, Help & Troubleshooting] Einsteindks:
I'm rooted with rock my moto, stock recovery is reflashed, & I have write protection permanently off. Uninstalling safestrap is a no-brainer. I'm guessing the OTA will kill root and write protection? I presume slap my moto will work once I'm in Kit Kat, but is there anything I can do while on 4.2.2 to prepare for a rootable update into KitKat?

fat-fingered and Maxx-ed out.
[Droid Ultra Q&A, Help & Troubleshooting] aameghoo:
I second this, want to be fully prepared and make no mistakes
[Droid Ultra Q&A, Help & Troubleshooting] hawkswind1:
I fxz'd back to stock a few days ago. I was under the impression that our root method altered the system partition and would cause updates to fail
[Droid Ultra Q&A, Help & Troubleshooting] Einsteindks:
Root method only removes stock recovery (used for write protection off). Flash recovery back on in ADB, good as new. My stress is permanent write protection off causing a problem after pre-KK FXZ, or OTA in restoring root (if SuperSU Survival Mode can't maintain root).

Edit: WP will survive FXZ, but not likely OTA. Soooo...FXZ, OTA, Slap, WPoff (again) looks like.

fat-fingered and Maxx-ed out.
[Droid Ultra Q&A, Help & Troubleshooting] TheWhiteChallenger:
From what I can tell you need to fxz back to stock and run slapmymoto frist, since slapmymoto work like rockmymoto except installs a "backdoor" instead of root. Keep in mind by taking the 4.4 update you are risking preminate loss of root, because slapmymoto works on the idea that you can roll back to 4.2.2 after KitKat and moto has had a month since the moto x's update rolled to prevent this on the droids. Also I know that anyone has used the motowpnomo mod have has issues getting root back. There is a fix out but I haven't used it and am not sure how it will effect the moto slapping process
[Droid Ultra Q&A, Help & Troubleshooting] l337h4cker:
Please let us know if anyone gets a successful or unsuccessful method. Then we can verify what does/doesn't work. I have a backup running and the update downloading at the moment. I will post back if I get some time to give it a try.
[Droid Ultra Q&A, Help & Troubleshooting] TheWhiteChallenger:
Plz pull the update from /cashe with root explorer (or w/r you use) and post a link I'm happy to try but it hasn't been pushed to me yet.
[Droid Ultra Q&A, Help & Troubleshooting] Casen:
Can anyone pull the install-recovery.sh from system/img for the 4.2.2? I need it for my update.
[Droid Ultra Q&A, Help & Troubleshooting] rlmesq:
I just used House of Moto in "Keep Data" mode. Stock recovery is back, along with the annoying bootup sound. Still waiting for the update to push to my phone.

http://xdaforums.com/showthread.php?t=2450702&highlight=houseofmoto
[Droid Ultra Q&A, Help & Troubleshooting] Einsteindks:
Recommended you look over SlapMyMoto 1.0 before taking the OTA! If you still have root, you could run the MotoWPoff exploit now, if you want.

fat-fingered and Maxx-ed out.
[Droid Ultra Q&A, Help & Troubleshooting] rlmesq:
Will MotoWPoff survive the OTA? The thread says

http://xdaforums.com/showthread.php?t=2551113
[Droid Ultra Q&A, Help & Troubleshooting] Einsteindks:
Either it did, or KK allows WP toggle for rooted users. Not quite smart to know why. I can tell you what I did, but I can't tell you what happened or why it works. ;)

fat-fingered and Maxx-ed out.
[Droid Ultra Q&A, Help & Troubleshooting] bendrum30:
I have an unlocked bootloader. I haven't gotten update yet. Losing patience. I got the email last night saying it would push this morning. Still waiting
[Droid Ultra Q&A, Help & Troubleshooting] SDC_Bolts:
I am in the same situation, very curious on where to go from here to achieve root on 4.4. I have yet to get the update, but would like to be prepared.

Thank you.
[Galaxy S 4 General] entertainer99:
Hello XDA,

I would like to share my experience with you guys.

Ok first there was a notification saying that a software update was available for installation (I9505XXUEML1). After the software update was successfully installed, I went to Status and saw that the device status showed "Custom" instead. I don't know why, but after rebooting again, the device status reverted to "Official". Oh, and I was half-thinking that the change in device status was due to the sudden change is ROM version.

Anyone else has experienced this? If so, please reply below and share your experiences. Thanks.

From,

entertainer99
[Galaxy S III Q&A, Help & Troubleshooting] gmcmxci:
I have a Galaxy SIII (US Cellular), Windows 7, following this guide: http://wiki.cyanogenmod.org/w/Install_CM_for_d2usc

Under the section 2 (Installing CyanogenMod from recovery), I didn't push the .zip from ADB, I added CM rom to my external SD card. I chose the option "choose zip from external sd card". I select the mod.zip, and it says it's installing until:

E: Error in /external_sd/cm-11.zip

(Status 7)

Installation aborted.

A search for (Status 7) came up with this thread: http://xdaforums.com/showthread.php?t=2302599

I followed that tutorial to a T, no luck. I decided maybe the nightly build wasn't for me, so I went for the first stable version from this page: http://download.cyanogenmod.org/?device=d2usc

Still, (Status 7) error

Installation aborted
[Galaxy S III Q&A, Help & Troubleshooting] gmcmxci:
Keep in mind I've tried three different builds of CM: CM11 nightly, CM11 stable, and CM10 stable. No luck.
[Galaxy S III Q&A, Help & Troubleshooting] gmcmxci:
Bump
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
RULES please read them no bumping .

. Post a message only once.

As a large forum we don't need unnecessary clutter, You're free to edit your message as you like, so if you do not receive an answer revisit your message and see if you can describe your problem better. Not everyone is online at the same time, it might take a while before you receive an answer.
[Galaxy S III Q&A, Help & Troubleshooting] gmcmxci:
I'll be patient.
[Galaxy S III Q&A, Help & Troubleshooting] gmcmxci:
Having some luck....
[Galaxy S III Q&A, Help & Troubleshooting] Jumaqidi:
This guy shld be banned.

Sent from my SM-N9005.

Give a thank if I helped you :)
[Galaxy S III Q&A, Help & Troubleshooting] gmcmxci:
Thanks!
[Galaxy S III Q&A, Help & Troubleshooting] Jumaqidi:
Haha. XD Why u bricked ur fone. Karma is true O.O

Sent from my GT-I9300.

Give a thank if i helped you. :)
[Galaxy S III Q&A, Help & Troubleshooting] anil720:
Are you running the latest recovery? Installing CM 11 with an older version will give Status 7 errors
[Galaxy S III Q&A, Help & Troubleshooting] gmcmxci:
Thanks for the help.
[Galaxy S III Q&A, Help & Troubleshooting] Jumaqidi:


Give a thank if I helped you :)
[Sony Xperia P, U, Sola, Go] alarulrajan:
How to enable/add new display language for Xperia Sola. I have custom JB ROM based on Ultimate ROM v11 and Experimental Kernal v11*. I searched and got a app called Language Enabler. But it says it is only for Samsung Galaxy phones. But i tried it and it does not work. But i need it for Sony Xperia Sola

PS: Please delete this thread if it is a duplicate. Thanks in advance.
[Sony Xperia P, U, Sola, Go] alarulrajan:
Please delete this thread. Searched and got a app called "Locale & Languae" which helps to create custom one which is not in the phone settings. And i created and setup the locale which i need.

Thanks for the help.
[Sony Xperia P, U, Sola, Go] Wind07:
Report your own thread and ask for delete and that should do it ;)

Sent from Earth.
[Sony Xperia P, U, Sola, Go] ChikeD:
This by itself is a good reason not to delete this thread as it may help others with the same problem.
[Samsung Galaxy Mega] Traine:
Hey guys im just wondering if the Galaxy Note 3 battery compatible for the Galaxy Mega
[Samsung Galaxy Mega] shayneflashindaily:
Not sure ...I was researching this cause the note 3 has a zerolemon 9000something mah battery if you succeed met me know

2SHAYNEZ
[Samsung Galaxy Mega] Unreal988:
no, it isnt compatible

inviato dal 6.3
[Samsung Galaxy Mega] shayneflashindaily:
Have you tired

2SHAYNEZ
[Samsung Galaxy Mega] fixit35:
I can confirm its not the same my brother got a note 3.. the mega battery is more wide
[Samsung Galaxy Mega] shayneflashindaily:
Gotcha

2SHAYNEZ
[Samsung Galaxy Mega] captemo:
sorry to hijack guys, just wanted to touch base with Shayne.

just got my Mega 6.3 and its the biggest thing I ha a hold of in a long time.

:good::good::good:

wait, that didn't sound good :eek:
[Samsung Galaxy Mega] shayneflashindaily:
Hollly crap glad your around bro. Hey which one did you get ? I have the i9205

2SHAYNEZ
[Samsung Galaxy Mega] Traine:
Are you planning to put a custom ROM on the Mega?
[Samsung Galaxy Mega] captemo:
I got the i527, just like it says under here bro

---------- Post added at 07:21 PM ---------- Previous post was at 07:19 PM ----------

I would love to, dont think there are any for mine yet. I got a lot of reading to do first.
[Samsung Galaxy Mega] Traine:
If you go to the galaxy mega original android development, you can see that there is a custom rom for the galaxy mega. :) and if you want to know how to root it, just go to this site

http://androidxda.com/root-samsung-galaxy-mega-6-3:cyclops:
[Samsung Galaxy Mega] captemo:
Unless it states for i527 or I see others with same device.......but I still have some reading to do. I will look for you around my friend.

Thanx for the welcome.
[Samsung Galaxy Mega] Traine:
1 person has the galaxy mega i527m its the canadian version and he tried the custom rom for gt i9200 and it worked for him just fine...but i think you have to unlock your boot loader which i dont know how
[Samsung Galaxy Mega] str3tchb0y:
The canadian i527m and the AT&T i527 are different. The bootloader for the i527 has not been broken yet or there is no way yet to load a custom rom.
[Samsung Galaxy Mega] captemo:
that is the last I had heard. it has been rooted, but there is no recovery yet. there is a gentleman and I believe HASHCODE is his name, who is working on a safety strap. I believe that is a sort of dual recovery. enabling a portion of the system to remain stock, while using remainder as a free splinter to run alternative files.

I know my terminology blows, but I have a friend at work who says his Bionic worked the same way.

I think he is working on Note 3 right now and i527 is on a waiting list. that's fine for me cause I am not in a hurry, I need to feel confident in what I am doin cause I can reeeeaaaalllllyyy EFF things up if I want to. and I don't even have to try.
[Samsung Galaxy Mega] Traine:
OK :D
[Samsung Galaxy Mega] shayneflashindaily:
Lol best evva jk:rolleyes:

2SHAYNEZ
[Samsung Galaxy Mega] Traine:
Wait is that moderate use or heavy use? Mine lasted 14 hours and 13 minutes of heavy usage and i still have 27% of battery left and i didnt charged it
[Samsung Galaxy Mega] Traine:
Here's mine
[Samsung Galaxy Mega] shayneflashindaily:
Oh I was just joking around ..I had a lot if bump charges

2SHAYNEZ
[Samsung Galaxy Mega] Traine:
lol :laugh:
[Networking] davidkinsella:
I've searched the forum but I've been unable to find the CAB file which will install all this for me. Otherwise can anyone tell me the manual setup especially for MMS as it won't work with the settings I've input. This is just because I've put the Qtek ROM on the device.
[Networking] twojags:
It may be out of date but you could try

http://www.filesaveas.com/gprs.html
[Networking] MrPhilly:
I think this will work..

Try it.. This was originally found after a look using the Search function. I think I put "mms AND setting AND cab"..
[Networking] catalyst:
t-mobile gprs settings

APN - general.t-mobile.co.uk

number - *99#

username - user

password - pass
[Nexus 5 Q&A, Help & Troubleshooting] ac29593:
Is there an option you can check to have a screenshot stay open in edit mode similar to an option that you can check in Samsung phones display settings or default setting for the LG G2?

Grest feature I'm looking to figure out where to activate if possible...

Thanks
[Nexus 5 Q&A, Help & Troubleshooting] simms22:
no. but you can open it in the gallery and edit it.
[Nexus 5 Q&A, Help & Troubleshooting] ac29593:
Ok thanks.
[Moto X Q&A] DssTrainer:
So I had a rooted Sprint 4.2.2 (not unlocked, just rooted) and I got the OTA alert.

I accidentally installed it and it failed and now when it restarts, it gets to android for about 30 secs and then does the "powering off" bit and restarts... over and over.

In that 30 secs I can get to the settings and see that the version is still 4.2.2 so it didn't take. But it almost seems like it in stuck in that mode where it thinks it is doing the upgrade.

I tried killing memory resident stuff to prevent the restart to no avail.

I cannot get into any kind of stock recovery, it just reboots to normal mode

My only option is to go into Bootloader which does work.

But when I try to use RSD Lite and flash back to that last stock image, it shows

Failed flashing process 2/17 flash partition "gpt.bin"

I read that this may be due to the phone not allowing me to downgrade to a version lower than I currently have? Also read it could be the battery needs to be charged more.

Thoughts?
[Moto X Q&A] charlie-n:
Can you get to the factory reset in that thirty seconds?
[Moto X Q&A] gokart2:
If you can get to boot loader, will it go into recovery? If so, try restoring a backup. Likely you will have to do THIS, and I recommend doing this, the ota, then reroot.

Edit: if it boots to ROM for 30sec, try wiping cache and dalvik, then fix permissions, then reboot.
[Moto X Q&A] DssTrainer:
Ok so after reading around and doing some of my own playing around, I figured out how to fix it with some ideas from this thread

First off, the moto x rooting process actually REMOVES the recovery.img file from your phone, so what seems to be happening is that the upgrade downloads and starts to install... it attempts to load the recovery to flash the image, but since it doesn't exist, it just restarts the phone. When the phone restarts, the upgrade process still thinks it needs to run the upgrade, so it powers down.. this is where it gets stuck in the loop.

The solution is actually simple. Get into Bootloader mode (Power + Vol Down) which was slightly tricky since the phone always rebooted and never actually powered down. So I had to catch it at the end of the power off cycle, before it restarted. Once I was in bootloader mode I could use the following command:

fastboot erase cache

That seems to remove the downloaded update files as the phone stopped rebooting over and over.

But now I get Mobile IP Registration Error 67 (MIP) which basically means my registration data got wiped.. not sure I understand why that would happen.. but it basically means I need my MSL and have to enter the code to reset registration which will force a wipe of all data. At least I have the opportunity to back everything up over wifi now that I've stopped the looping.

The second part of this fix I haven't tried, but based on an educated guess, to actually GET the update correctly, I would need to flash the stock recovery image back using:

fastboot flash recovery recovery.img

where the recovery.img file comes from the zip file for the moto x stock image from the sbf repo:

http://sbf.droid-developers.org/phone.php?device=0

That of course needs to be done before I call Sprint to get my MSL and perform the reset.

All in all, a minor setback overall... better than a paperweight :) Perhaps instead of doing the erase cache step and just flashing recovery may have saved my MIP data

---- EDIT-----

Ah, gokart2, I see you had a similar process. Cheers
[Moto X Q&A] DssTrainer:
Turns out the Mobile 67 error was because my friend changed her service back to her old phone.... I should add that this wasn't my phone by my friend's phone.
[Verizon Samsung Galaxy S III] Maphack:
does the sim card gradually die, or is it more like one minute you're fine, the next you need a new one?

a couple times I have gotten "no sim card," but a reboot took care of the problem. i'm using the zerolemon battery so maybe that has deformed the sim slot?

it has only happened twice...and i'm wondering if this means it is only a matter of time before i'm screwed...or is it more likely i would be able to do something that would allow the sim card to be read properly because the slot is damaged? i read something about putting a piece of paper/cardboard in the slot, but i haven't looked much into it and hoping i don't have to...

thanks
[Glass General] animan:
I have 2 invites available. PM me if you are interested.
[Glass General] animan:
Thanks for the PMs. Two invites have been sent in. I have no more available.
[General Questions and Answers] bdh69691:
removed duplicate
[Android Q&A, Help & Troubleshooting] ummarrkhan:
How to root lava iris phones lile 458q?
[Android Q&A, Help & Troubleshooting] GuestD2709:
The easiest way is Framaroot

https://www.dropbox.com/s/akzk5i5cn91wto9/Framaroot-1.6.1.apk

Select SuperSU and Gandalf!
[Android Q&A, Help & Troubleshooting] shrikant716:
try this

http://xdaforums.com/showthread.php?t=2430676
[Android Q&A, Help & Troubleshooting] ummarrkhan:
not working it says device not compatible
[Android Q&A, Help & Troubleshooting] ummarrkhan:
see my post in that thread
[Android Q&A, Help & Troubleshooting] iamsrk:
try Kingo App root
[Android Q&A, Help & Troubleshooting] ummarrkhan:
where to find/downld this
[Android Q&A, Help & Troubleshooting] GuestD2709:
Try any of these then:

http://xdaforums.com/showthread.php?t=2511087

;)
[Android Q&A, Help & Troubleshooting] ummarrkhan:
i.e same

I will try again