yashsingh1/xdaforums huggingface dataset:
[G2 Q&A, Help & Troubleshooting] cptnsmelly:
So long story short I screwed my phone up and had to use LG Flash Tool to make it work again. The weird thing is, when I tried to flash a D803 .TOT file the LG Flash Tool said "wrong phone model" or something along those lines. It then said "D801" was my phone model. I searched and searched and SEARCHED for Bell D801 and could only find people saying it's D803. Well, I said screw it and downloaded TMobile's D801 .TOT and flashed it. The phone works now but it has a TMobile boot animation. It still connects to Bell fine, but here's the main issue;

Part of my touchscreen doesn't work anymore and I'm still under warranty if I can just get the phone back to stock to have it sent in. How can I do this? Any help? Also, does flashing with the LG Flash Tool make it so LG can't see I ever rooted the phone?

Thanks!
[G2 Q&A, Help & Troubleshooting] danial.aw:
Maybe its a wind phone? I believe those are d801s because I have a bell one and that is D803
[G2 Q&A, Help & Troubleshooting] cptnsmelly:
Thanks for the quick reply, but i purchased the phone at a bell store 9 months ago... This makes no sense. I really need Bell stock back...
[G2 Q&A, Help & Troubleshooting] Funjet:
Stock rom is KDZ, not TOT

http://lg-phone-firmware.com/firmware-Lg+G2-Tutti-36.html

bell V20G
[G2 Q&A, Help & Troubleshooting] cptnsmelly:
So are you saying there is no TOT? I cant get the kdz method to work... so i need a tot.
[G2 Q&A, Help & Troubleshooting] cptnsmelly:
Ok so I typed my IMEI into some site and it said my phone is indeed a D803! However, because I flashed a TMobile .TOT to the phone, my phone thinks it's a D801. Oh god... How do I fix this now?
[G2 Q&A, Help & Troubleshooting] cptnsmelly:
BUMP!
[G2 Q&A, Help & Troubleshooting] danial.aw:
Hmm I'm not sure how you can go back but if you are within warranty you can try wrecking the system (so it doesn't work) and send it in for repair... They will reinstall a new version
[G2 Q&A, Help & Troubleshooting] wulsic:
Maybe your bootloader or whut was d801?? Idk but can you try to flash this kdz http://storagecow.eu/index.php?dir=Xda/LG+G2/Stock/Canada+D803/

Then the one from bell? I hope its gonna be alright if you can flash it. Note that if you screw up with flashing then try not to wreck your system but try to repair it you itself since a system wreckage doesn't come fromself and lg doesnt need to pay the price to fix it. Even under warranty. I know lg screws up stuff but flashing is at own risk.

Edit: I sawmyour other thread so nvm.
[G2 Q&A, Help & Troubleshooting] cptnsmelly:
Alright so I redownloaded LG Flash Tool and everything and I put my phone in download mode. It starts updating my firmware, it gets to 49% and then fails and says "TYPE_WPARAM_UPGRADE_ERROR" in the log. What does this mean and how do I fix it? I think when I flashed the TMobile .TOT it made my Bell phone think it is TMobile and maybe that's why I'm getting this error. How do I fix my phone and make it realize it's D803?
[G2 Q&A, Help & Troubleshooting] wulsic:
Change your windows language and locals like unicode to english if it wasn't

Turn off or allow the app through your antivirus.

Reinstall LG USB Driver, LG Flash Tool etc

Change the LG device in Device manager to COM port 41 or COM port 4 before connecting to PC.

See or your KDz weights around 2gb and not less then it cause that would be maybe a sign of an corrupted KDZ.

The last thing what i also think is that the Lg flash tool maybe reads the D801 in the build.prop or what and as safety measure it cuts off the flashing progress so you might change the D801 to D803 or however it was called in Bell.

Hope that one of these things could solve your problem.
[G2 Q&A, Help & Troubleshooting] cptnsmelly:
Thanks for the info, but how do I change the build prop? I tried the adb usb thing and I get "device closed"
[G2 Q&A, Help & Troubleshooting] cptnsmelly:
Woohoo! I fixed the bi*ch! Sorry, I'm a little excited here... Anyway, I followed the instructions above and it worked. I think the above is well written and easy to understand except for one thing: How to change build number (if you're like me and flashed the wrong TOT).

It's simple. Make sure you have a rooted phone and download root explorer (black icon with a little android face). Next, follow this: http://xdaforums.com/showthread.php?t=1948558

Make sure you change the model number before you try flashing the kdz only if you messed up with tot flashing like me. Otherwise, as mentioned above, make sure you're on COM41. This worked great. Now I can take my bell phone back to the store and have it seen to (I have a hardware issue with the screen no sensing touch in certain areas).
[G2 Q&A, Help & Troubleshooting] wulsic:
Great to hear that it worked :) yes about that build.prop editing i wasn't clear sorry for that but good that it worked now.
[Verizon LG G2] betatest3:
How can I fix it I am running stock KitKat, with TWRP 2.7.1.0.

EDIT: I fixed it, I think it was a bad ip address for proxy.
[Verizon LG G2] njstein:
Have you tried a new SIM card?
[Verizon LG G2] betatest3:
I cant get a new sim card, and the one I am using is fine(it works in a test phone).

This is my apn setting:

Name: T-Mobile US

APN: epc.tmobile.com

Proxy: 216.155.165.050

Port: 8080

MMSC: http://mms.msg.english.t-mobile.com/mms/wapenc

MMS Proxy: 261.155.165.050

MMS Port: 8080

MCC: 310

MNC: 260

APN Protocol IPv4

APN Roaming Protocol: IPv4

Is anything wrong?

Signal checker says im connected but when I disable WiFi, there is no 3G,4G,2G, or anything.
[Verizon LG G2] betatest3:
OK, I fixed it(hopefully)

Ok I fixed the data issue, I now get HSPA, with 7.82mbps download, not 4G, but close enough for me.

I don't want to break anything so I won't even try to get 4G
[Samsung Galaxy Xcover 2 Questions & Answers] es0tericcha0s:
http://xdaforums.com/showpost.php?p=54324275&postcount=283

There are many users with network issues with that rom, but seems because there are a lot of different firmware versions for different areas which is why every other users that mentioned it were having issues while the others said all was well.
[Samsung Galaxy Xcover 2 Questions & Answers] JonHue:
Thanks for the Link.

I´m also thinking that it´s a Problem with the Permissions.

After setting all to chmod 777 in /efs and /modemfs Folders I´m now able to connect to the mobile service...

But not really good.

Sometimes it´s two hours without service, sometimes it works then for 5min but it never works for more than 10 minutes.

When I try to connect to the mobile Internet i can only use very very slow G connection.

Normally i should get H here...

Help me :crying:
[Android Q&A, Help & Troubleshooting] shanu736:
i have recently unbrick my phone by jtag repair when i tried to put in emergency mode it enter octopus mode .... I want to change the rom it is on . SO help me any suggestions
[JAM, MDA Compact, S100 Software Upgrading] gerdi99:
Hello

Is there a possibility to completely shutdown the qtek s100 (Magician) so that it does not consume any more power? If i press the power button, the screen goes black, but it can receive calls, the led blinks and if a press the button again, it is back on instantly.

This is very nice, but there are times where I would like to shut it down completely. Pressing the power button long only turns off the backlight.

Thanks.

Edit: Sorry, posted in the wrong section, can somebody move it?
[JAM, MDA Compact, S100 Software Upgrading] vijay555:
Try my app VJEschton, with the command line -sleep

V
[JAM, MDA Compact, S100 Software Upgrading] lanuk79:
turn the flight mode on. it turns off the phone but u can still use the PDA function. the battery lasts much longer this way
[JAM, MDA Compact, S100 Software Upgrading] shoonari:
take off a battery cover and back. thats all
[Android Apps and Games] alensaqe:
A Crazy 2D Racer Build bringing back some of the classical-retro feeling!

Features 2 Game Modes and 4 cars!

A lot lot more to come!!!

STAY TUNED AND RACE!

Download

Waiting for some feedback and recommadations :D !
[Android Apps and Games] alensaqe:
Updates Area!

What's New

*New Icon

*Improved performance on older android devices

*Improved graphics and tweaked the gameplay
[Android Apps and Games] alensaqe:
Update

The all new classic american muscle is here!

*New Icon

*Fixed a bug on car selection scene

*Changed the Main menu screen

*Added a "Garage" screen where you can choose the car

*Changed the "Game Over" Layout to fit the design style

***AND A LOT MORE TO COME***

Sorry guys we had to reset your high scores as they will be game mode dependent. Each game mode will have its own high score!
[Android Apps and Games] alensaqe:
Im checking your game out!

Meanwhile we published a new update.

We added two new cars for you to enjoy! One "German Pride" and one "Japanese Perfection"!

*New Icon

*Added cars specs on the garage

*Added acceleration on the start of each game

*Changed the explosion to look better

*Improved game play in older devices

*Tweaked the game and the speed of the cars

***AND A LOT MORE TO COME***
[Android Apps and Games] dweebster:
Nice game but the input was a bit too sensitive for my liking.
[Moto G Q&A, Help & Troubleshooting] barky02:
Hi,

I have messed around with my rooted Moto G and edited build.props. I turned on my phone and a message came up saying "error system.ui has stopped"' this message kept repeating every time I pressed OK.

After failing to fix it, I went onto my recovery and wiped the storage, cache and dalvik. Obviously now when I turn on the phone it just stays on the boot image and nothing happens.I put the phone into fast boot by holding power and vol down, then tried to flash 4.4.2 Stock ROM to my phone but all CMD says is "waiting for device". I'm not sure what to do from here.

Can anyone help me at all? I've already posted before but no one seems to help me.

If you need any screenshots etc I will add them

Thanks,

Matt
[Moto G Q&A, Help & Troubleshooting] hhp_211:
[MENTION=5824075]barky02[/MENTION]

what are you using to try and install your stock rom? are you just in command prompt terminal or using a program?

anyway,,, your phone needs to be in fastboot mode to be able to run adb commands
[Moto G Q&A, Help & Troubleshooting] barky02:
[MENTION=983303]hhp_211[/MENTION]

[MENTION=5989261]Martin3lli[/MENTION]

I'm using CMD, and I was following this guide: http://xdaforums.com/showthread.php?t=2542219

I am unsure how to put my phone into fastboot mode, can you show me how? I put the phone into fast boot by holding power and vol down, and thats how I tried to flash the ROM. all command prompt was saying was <waiting for device>

Thanks,

Matt
[Moto G Q&A, Help & Troubleshooting] Martin3lli:
When your phone is off, push volume down and power button simultaneously for a few seconds, then it should start fastboot. Plug in your USB cable and proceed with other steps as guide says.
[Moto G Q&A, Help & Troubleshooting] barky02:
[MENTION=5989261]Martin3lli[/MENTION]

Sorry I misunderstood, I did put my phone into fastboot but it still didn't work, I updated my previous reply with the details
[Moto G Q&A, Help & Troubleshooting] Saphire007:
try this

I don't know if this will work, this is my threat. Hope it helps

http://xdaforums.com/moto...t1032-t2814093
[Moto G Q&A, Help & Troubleshooting] barky02:
Thank youu :3

404 error? is it the right link?
[Moto G Q&A, Help & Troubleshooting] hhp_211:
I assume you are trying to run "flashall.bat"?

in the command prompt try this

adb kill-server

then type

adb start-server

then try running the commands...

I believe you are a full xt1028 Verizon phone?

I know what I do for 4.4.2 is using the file

CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip

un-zip [extract] that file,,,

then make sure you copy and paste from the "/windows" folder in the zip

fastboot.exe

AdbWinApi.dll

cAdbWinUsbApi.dll

into the main folder [where your .bat file is]

with phone connected to pc...

then open it up and double click on the .bat file

CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.bat

and it will do all the necessary work

.
[Moto G Q&A, Help & Troubleshooting] barky02:
I have an english phone, none of the things you have said were in the tutorial, and the xml I am using doesn't come with any of those, only mfastboot.exe

I don't think my PC is recognising my Moto G properly. On the fastboot screen it says USB connected, but in my devices my phone is called "Fastboot Falcon S"
[Moto G Q&A, Help & Troubleshooting] hhp_211:
Yes you have a Verizon Moto G Right [XT1028]? not a converted Boost Mobile [XT1031]?

what is the name of the zip file you have?
[Moto G Q&A, Help & Troubleshooting] barky02:
I have a T-Mobile Moto G XT1032

The Zip file name is: EE-GB-SL_FALCON_KLB20.9-1.10-1.24-1.1_cid7_CFC_1FF.xml
[Moto G Q&A, Help & Troubleshooting] hhp_211:
Ahhh... I keep forgetting there are so freakin may versions...

can you show a screenshot of what files you have in there

also did you try the

in the command prompt try this

adb kill-server

then type

adb start-server

this will restart the adb session
[Moto G Q&A, Help & Troubleshooting] Ysharief:
Here is a another thread to restore stock

http://xdaforums.com/showthread.php?t=2794271
[Moto G Q&A, Help & Troubleshooting] barky02:
These are the files in the xml folder - mflashboot was the thing I added

Im not too brainy with cmd, at what time do I put adb kill-server in?
[Moto G Q&A, Help & Troubleshooting] Saphire007:
sorry

Sorry bro, my bad xs hope this works.

http://xdaforums.com/moto-g/help/fix-bricked-xt1032-t2814093
[Moto G Q&A, Help & Troubleshooting] hhp_211:
thanks

after reading some more up on mfastboot I don't believe you have to use the adb commands...

you should be able to use this file mfastboot.bat.txt as long as you have the mfastboot.exe on your pc

download it and move it into your "EE-GB-SL_FALCON_KLB20.9-1.10-1.24-1.1_cid7_CFC_1FF.xml" folder

then rename it to just mfastboot.bat

and doubleclick that

and follow along

don't worry if you see errors on your device screen, it's normal

this is the contents and the

correct flashing order

of the bat file

and are for that xml.zip that you have

edit:: edited to remove file and update below code to hopefully work

SET mfastboot=mfastboot.exe
%mfastboot% flash aboot emmc_appsboot.mbn
%mfastboot% flash partition gpt.bin
%mfastboot% flash motoboot motoboot.img
%mfastboot% flash logo logo.bin
%mfastboot% flash boot boot.img
%mfastboot% flash recovery recovery.img
%mfastboot% flash system system.img_sparsechunk.0
%mfastboot% flash system system.img_sparsechunk.1
%mfastboot% flash system system.img_sparsechunk.2
%mfastboot% flash modem NON-HLOS.bin
%mfastboot% erase modemst1
%mfastboot% erase modemst2
%mfastboot% flash fsg fsg.mbn
%mfastboot% erase cache
%mfastboot% erase userdata
[Moto G Q&A, Help & Troubleshooting] barky02:
[MENTION=983303]hhp_211[/MENTION]

I think this will work but I just need the pc to recognise the device, I have attached screenshots of what the device is coming up as. I have installed Motorola Device Manager, SDK tools and Google USB but it still won't be recognise.

I ran the .bat file but command prompt is still saying <waiting for device>

Thank you so much for your help, I think its nearly fixed

Matt
[Moto G Q&A, Help & Troubleshooting] hhp_211:
@ barky02

have you also installed the

Moto G USB Drivers (WinXP/7 32Bit-64Bit)

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

what os are you running on your pc?

.
[Moto G Q&A, Help & Troubleshooting] barky02:
[MENTION=983303]hhp_211[/MENTION]

Windows 7 (just with 98 theme)

I already have that installed, and it still doesn't work. A lot of threads are saying to enable usb debugging, but I can't do that in the phones current state right?

I attached the screenshot of what cmd stays on
[Moto G Q&A, Help & Troubleshooting] hhp_211:
Ok I thought Win 7, but then other shots were looking different...

well I'll ask anyway...

have you downloaded and installed

the Minimal ADB and Fastboot -- Version 1.1.3

https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit?usp=sharing

the mfastboot-v2.zip

http://xdaforums.com/attachment.php?attachmentid=2427667&d=1385958280

[[[and extract the zip then copy mfastboot.exe into the same folder as the stock firmware files (the same folder as the .bin and .img files).]]]

then put the .bat file inside the firmware folder,,, then doubleclick the .bat file while phone is in fastboot mode and attached to pc
[Moto G Q&A, Help & Troubleshooting] barky02:
Yes I have, and when I go on the bat file I have attached what happens, it stays on <waiting for device> and the phone doesnt appear to be doing anything
[Moto G Q&A, Help & Troubleshooting] hhp_211:
let's see what you phone is saying while in fastboot mode and does it change any after the .bat is ran?
[Moto G Q&A, Help & Troubleshooting] barky02:
So when I plug in the phone, the log says

"

Fastboot Reason: Volume down key pressed

USB Connected

"

Then when I run the bat, nothing changes at all. I tried plugging it in different USB ports but still nothing
[Moto G Q&A, Help & Troubleshooting] hhp_211:
Like this
[Moto G Q&A, Help & Troubleshooting] barky02:
Exactly, and if you connect the USB it will come up with a message.
[Moto G Q&A, Help & Troubleshooting] hhp_211:
may have found the whole issue...

open up the .bat file [edit]

and remove the 3rd line it says

%mfastboot% reboot-bootloader

also remove the last line that says

%mfastboot% reboot-bootloader

then save the file and retry...

that should flash everything now...
[Moto G Q&A, Help & Troubleshooting] hhp_211:
[MENTION=5824075]barky02[/MENTION]

if for some reason that one does not work try this version of the .bat file

.
[Moto G Q&A, Help & Troubleshooting] barky02:
I ran the .bat file and the exact same thing happens. <waiting for device>

device does nothing
[Moto G Q&A, Help & Troubleshooting] hhp_211:
man, if you have verified that the .bat you are running does not have the lines in there

%mfastboot% reboot-bootloader

then I am not too sure what else it could be...

the 1st one

that was messing it up for me and not letting it flash, the second time I decided to remove only because it was clearing the phone screen

try this,,,

connect device to pc and put into fastboot mode

open a cmd terminal and cd [change directory] to your .xml folder

cd "c:\Users\Matthew\Desktop\EE-GB-SL_FALCON_KLB20.9-1.10-1.24-1.1_cid7_CFC_1FF.xml"

and type mfastboot devices

what does it show

after that also type this

mfastboot getvar all

and post the output

.
[Moto G Q&A, Help & Troubleshooting] barky02:
[MENTION=983303]hhp_211[/MENTION]

Typing mfastboot devices didn't show anything at all, just a new blank line

typing mfastboot getvar all just brought up the <waiting for device> messages again
[Moto G Q&A, Help & Troubleshooting] hhp_211:
[MENTION=5824075]barky02[/MENTION]

Ok then you need to try and reinstall the the Minimal ADB and Fastboot -- Version 1.1.3 and Moto G USB Drivers (WinXP/7 32Bit-64Bit)

that seems to be where the issue is
[Moto G Q&A, Help & Troubleshooting] barky02:
[MENTION=983303]hhp_211[/MENTION]

Reinstalled both applications. problems still persists

<waiting for device> (See attachments)
[Moto G Q&A, Help & Troubleshooting] hhp_211:
man I'm really at a loss try installing the official Motorola Device Manager

http://www.mymotocast.com/download/MDM?platform=windows
[Moto G Q&A, Help & Troubleshooting] barky02:
[MENTION=983303]hhp_211[/MENTION]

The problem has not gone :/

I am not familiar with adb, but I did adb devices and no devices were "attached", I had a look into that but the driver for the phone is coming up as motorola adb interface

I have no clue why this isn't working? It's only a soft-brick

Do you have any idea what else I can do now? is there anything else I can try, or anyone else I should contact?
[Moto G Q&A, Help & Troubleshooting] hhp_211:
start a new cmd window and cd to the xml again...

try manually entering each line and see if it hangs

try like the 1st 5 lines and see if they will work

I doubt it because it does not seem to be seeing your moto g

mfastboot flash partition gpt.bin

mfastboot flash motoboot motoboot.img

mfastboot flash logo logo.bin

mfastboot flash boot boot.img

mfastboot flash recovery recovery.img

mfastboot flash system system.img_sparsechunk.0

mfastboot flash system system.img_sparsechunk.1

mfastboot flash system system.img_sparsechunk.2

mfastboot flash modem NON-HLOS.bin

mfastboot erase modemst1

mfastboot erase modemst2

mfastboot flash fsg fsg.mbn

mfastboot erase cache

mfastboot erase userdata

mfastboot reboot-bootloader
[Moto G Q&A, Help & Troubleshooting] barky02:
[MENTION=983303]hhp_211[/MENTION]

Nope, tried 6 lines and they all hang, this is so annoying :(
[Moto G Q&A, Help & Troubleshooting] hhp_211:
yup, I dont know what else to try... it seems as though it sees the device

"motorola adb interface" is correct for it to see when in fastboot mode and "Fastboot falcon S" is how mine shows too

but as to why it will not follow through with the mfastboot command is beyond me...

--------------------------------------------------------------

drastic measures---

you may also try uninstalling hidden or old devices/drivers that may be causing issues...

download this program USBDeview v2.35 from here

http://www.nirsoft.net/utils/usbdeview.zip

then seriously nuke

All

your old phone devices and adb interface, etc

,,, just make sure not to delete a 'USB Root Hub',,, 'usb mouse' or 'usb keyboard' or 'harddrive'...

it is an easier method of

this

http://www.sevenforums.com/tutorials/77614-device-manager-hidden-devices.html

and this

http://masterandcmdr.itgroove.net/removing-uninstalled-missing-devices-in-device-manager/

when that is finished reboot pc, and re-install all the adb, fastboot, mfastboot, motorola drivers again and see if it works.

-------------------

happy reading materials

http://www.droidrzr.com/index.php/t...et-up-adb-and-fastboot-for-your-windows-7-pc/

http://mark.cdmaforums.com/ADB.htm

http://mark.cdmaforums.com/MotoX-mFastboot.htm

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

-------------------------------------------------------------------------------------------------

.
[Moto G Q&A, Help & Troubleshooting] Ysharief:
If your PC cant detect phone then try other PC which has no android phone connected, take working android phone switch off connect to the PC and boot.

Install adb drivers manually if system cannot install the drivers do it manually by device manager.

If you don't have any other PC, just search and download a tool called USBdeview open the tool and uninstall or delete all phone drivers except mouse and keyboard.

Then connect phone in fastboot mode, hope you PC will install correct adb drivers
[Moto G Q&A, Help & Troubleshooting] barky02:
I followed everything you said down to a tee, and it WORKED!

Thank you so much for sticking with me! The device is showing up as attached and I can flash the first line, checking out the other lines now

THANK YOU SO MUCH :D

Much Love,

Matt
[Moto G Q&A, Help & Troubleshooting] hhp_211:
yeah !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

my persistence paid off !!!!!!!!!!!!!!!!!!!!!!!!

thank you for hanging in there too !!!!!!!!!!!!!!
[Android Q&A, Help & Troubleshooting] john.somedude.doe:
Hi all,

I've just joined the xda forum, i'm a software developer ( mainly DSP, Linux and uCos2 ) and have an interest in android.

I recently purchased a cheap tablet ( Azpen A1320 ) and can confirm that the Kingo rooting application

does root the tablet.

thanks.
[Android Q&A, Help & Troubleshooting] NewbieNga:
I also purchased the 1320, from TigerDirect outlet a while back. I've been trying find anything I could on good apps and rooting tools for it but haven't had much luck. As I understand, it comes pre-rooted but doesn't have an pre-installed root tool/customizing tools. I tried ROM Manager with no suck luck. Thanks for confirming that Kingo works.

I'm a newbie. So forgive me if this sounds like a dumb question but, should I install SuperSU or BusyBox? Also, does Titanium Backup work, and if so, how well?

Also, which version did you download? I didn't see Azpen listed in the device list.