Related
hi guys i sold my old galaxy s on Ebay, I factory reset it before sending tested it and it worked fine.
I never rooted or flashed this device, only one official Samsung update.
The guy has returned it saying the phone is laggy, slow to unlock, and slow running apps.
now I'm dubious that he may have done something to the device software/network unlock wise that went wrong and is just palming me off now he's damaged it.
Is there anything I can check such as software logs to see what the device has done in the last week?
Sent from my GT-N7000 using XDA App
okay, i received a n7 with a transfomer rom preinstalled on it 3 weeks ago, i called up customer service after a day trying and they said "do everything to make it work" and they will send me a email with instruction returning it.
headache: i managed to put a stock rom back on it, activated and everything, but i find out it's not as smooth as other devices (well, playing games for the first week is fine, than keep getting lagg after time), but luckily, i took a picture when i first start up the device (with transformer wallpaper,system info..)
currently the n7 is on stock rom with bootloader unlock and rooted, so if i return with this stock rom, are they will pass the examine of faulty and not "charge" me for another device? or i just go to the transformer section and flash their stock rom )
thanks for any advice
i dont think anyone have this case before -.-
That's weird.... was this straight from Google or did you buy elsewhere?
Sent from my Nexus 7 using xda app-developers app
There have been several instances where people have gotten ics (not TF, all asus products have the tree background) test roms on their devices, and experienced the same lag you are experiencing. It appears they got early pre-production devices, where the software (and perhaps hardware) has not been finalized yet, which may be what is causing the lag. I believe they will take it back if you change your complaint to "extreme lag", and explain what happened to it.
Good luck
kangxi said:
That's weird.... was this straight from Google or did you buy elsewhere?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, straight from play store.
hanthesolo said:
There have been several instances where people have gotten ics (not TF, all asus products have the tree background) test roms on their devices, and experienced the same lag you are experiencing. It appears they got early pre-production devices, where the software (and perhaps hardware) has not been finalized yet, which may be what is causing the lag. I believe they will take it back if you change your complaint to "extreme lag", and explain what happened to it.
Good luck
Click to expand...
Click to collapse
Yeah, i just afraid thr bootloader is unlocked, rooted, but this is all done before the device get to me, and because its up n working again, im just afraid they wont pass the examine
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
So my update is on Sept 1, and I plan on going anywhere I need to in order to find a MDL phone. I NEED my CM10.2! haha:angel:.
What are the chances I'll find one? I know they are getting slimmer by the minute, but I'm thinking maybe some rural Target or BB may have one? I've been trying to get my update anytime I'm near a store, but they all tell me I have to wait for the 1st of the Month. dumbbb.
Or do I wait for Note 3/LG G2/new Sony? (i know, i know, s4 forum...)
Or do I wait for the new iphone, sell it on fleabay/cl, and buy a Google Edition s4?
I dont NEED to update right away... But my skyrocket battery is KILLING me.
AHHH I hate this!
I'm on MF3 and I'm suffering with Touchwiz (I'm a huge fan of AOSP).
I'm pretty sure the Note 3 (from AT&T at least) will have a locked boot loader so it'll be the same situation us MF3 users are in right now.
Since MF3 has been out since July, I'd think that many/most S4's would have it. If you're willing to sell/buy unlocked, go ahead for the Google edition(I personally like black mist much more than white frost, which is what the Google edition comes with. ).
Sent from my Samsung Galaxy S4 (SGH-i337) via Tapatalk 4
teeg07 said:
... I'm thinking maybe some rural Target or BB may have one?
Click to expand...
Click to collapse
Actually, ask if the employee would be kind enough to let you see the stickers on their boxes. The side of the box shows the firmware revision (on brand new devices only). The employees, nor AT&T would have absolutely no reason to update something in-the-box like that, so this sticker should be accurate. It's the same sticker that includes all the serial numbers/etc.
It may or may not be beneficial to explain that you want a specific version of the firmware, otherwise the employee(s) may get a bit suspicious of a request like this. They may think you are trying to steal IMEI numbers or something stupid.
Aou said:
Actually, ask if the employee would be kind enough to let you see the stickers on their boxes. The side of the box shows the firmware revision (on brand new devices only). The employees, nor AT&T would have absolutely no reason to update something in-the-box like that, so this sticker should be accurate. It's the same sticker that includes all the serial numbers/etc.
Click to expand...
Click to collapse
Thats what my plan was to do. I'll say something about it performing better or something (even though we all know its not true. I love playing dumb )
teeg07 said:
Thats what my plan was to do. I'll say something about it performing better or something (even though we all know its not true. I love playing dumb )
Click to expand...
Click to collapse
Not exactly a lie. In the very end, MDL does perform better, because we can flash 'whatever' firmware we want... some of which can perform better.
whatever you do, DONT CONNECT TO THE INTERNET. install through apk's and then go to cm10.2. you can get terminal and the goomanager files, and install w/o internet....
Just ask to check it out before you buy. Most sales persons won't have an issue with it. Find one with MDL baseband and ask them to Leave it in box and that you prefer to set it up yourself
I'm running cm 10.2 on my s4 its so much better than touch wiz and the only feature I miss is the Samsung camera app.
Also I agree don't connect to the internet until after you have rooted and flashed a custom ROM as you can only delay the mf3 update 3 times before it auto installs
Good luck!
Sent from my Nexus 7 using xda app-developers app
vedantgp said:
whatever you do, DONT CONNECT TO THE INTERNET. install through apk's and then go to cm10.2. you can get terminal and the goomanager files, and install w/o internet....
Click to expand...
Click to collapse
txtech89 said:
Also I agree don't connect to the internet until after you have rooted and flashed a custom ROM as you can only delay the mf3 update 3 times before it auto installs
Click to expand...
Click to collapse
That was the plan guys- thanks! I've done my homework
I think thats what I'm gonna do. I'll see if I can find a MDL, and if not.... i'll cross that bridge when i get there.
Thanks for the help, friends!
Your welcome. I'm confident that you'll be able to find an MDL version laying around at one of the stores
Sent from my Nexus 7 using xda app-developers app
txtech89 said:
Your welcome. I'm confident that you'll be able to find an MDL version laying around at one of the stores
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I just picked up a 32GB version yesterday.
It has AMDL firmware. Turned on airplane mode as soon as I could and rooted then renamed the file to prevent an OTA.
billinaz said:
I just picked up a 32GB version yesterday.
It has AMDL firmware. Turned on airplane mode as soon as I could and rooted then renamed the file to prevent an OTA.
Click to expand...
Click to collapse
good news! Thanks! Is it september 1 yet?
Well, from here on out...ATT released a statement a few weeks ago stating they no longer will be supporting unlocked devices...which means all their smart phones will theoretically have a locked boot loader.
With that said...personally I wouldn't get another device and sell it for the Google edition. As far as I know (correct me if I'm wrong someone) the Google edition does not support touchwiz ROMs, only aosp. However you can get the T-Mobile variant which has an unlocked boot loader and allows you to flash anything from touch wiz to aosp based ROMs to the actual Google edition ROM...plus the T-Mobile supports all the bands that ATT uses so you won't have problems with service
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
mg2195 said:
Well, from here on out...ATT released a statement a few weeks ago stating they no longer will be supporting unlocked devices...which means all their smart phones will theoretically have a locked boot loader.
With that said...personally I wouldn't get another device and sell it for the Google edition. As far as I know (correct me if I'm wrong someone) the Google edition does not support touchwiz ROMs, only aosp. However you can get the T-Mobile variant which has an unlocked boot loader and allows you to flash anything from touch wiz to aosp based ROMs to the actual Google edition ROM...plus the T-Mobile supports all the bands that ATT uses so you won't have problems with service
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
the google edition (i9505G) is theoretically an i9505 running a nexus firmware... you should have no issues running a touchwiz rom made for i9505.
funny thing is when i got mine it was on MDL from at&t about a month and a half ago and it never onced tried to update. then i had to do a factory reset which put me on MDB and i want to go back to MDL. theres an over the air update now that im on MDB but i froze the apk because im scared its the MF3 firmware. i'd love to go back to MDL though is that even possible ?
I seen a little bit of bad information here that I feel I should clear up.
When you first get your device on MDL. Just don't insert the SIM card. You can power it on, and keep wifi completely open. No airplane mode needed. The OTA is pushed through on the AT&T network. If you don't have the SIM in on boot, it will not pull the update. The reason behind this is that the Phone verifies the network you are connected to. It can't verify AT&T without the SIM.
The only way you could possibly get the update without the SIM in is if you turn the phone on with the activated SIM, at this point it calls for the update. When on WiFi, it downloads it. So as soon as it calls for the update, you then need to remove required items to stop it. Even if you pull the SIM it will continue the download. So just don't turn it on with the SIM in it. I know this from personal experience and reading the Forums.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
I seen a little bit of bad information here that I feel I should clear up.
Click to expand...
Click to collapse
Thanks for the clear up! I was under the impression it would download as soon as i was connected to wifi.
Thanks again!:good:
Even if it downloads you don't have to install it. You can always disable the apps that prompt you to update.
I was in the same boat, being ready to upgrade after MF3 was released.
I spent the last two days checking 7 different ATT stores in the Los Angeles area for a 16GB S4 with the MDL firmware, unfortunately they had all been sold or replaced with the newer update. I was lucky to find one store that still had a 32GB version with MDL. I really dont need the extra 16GB, especially for an extra $50, but as long as i can Loki the damn thing Im happy. You might have to look for a 32GB version if you want a chance to find one as these do not sell anywhere near as frequently as the 16GB model.
Just do not put the SIM in until you block the OTA packages.
graydiggy said:
I seen a little bit of bad information here that I feel I should clear up.
When you first get your device on MDL. Just don't insert the SIM card. You can power it on, and keep wifi completely open. No airplane mode needed. The OTA is pushed through on the AT&T network. If you don't have the SIM in on boot, it will not pull the update.
Click to expand...
Click to collapse
The above quote is inaccurate. I purchased a used MDL S4 during the last week of August. For the first few days, I did not activate the SIM. However, whenever I turned on Wi-Fi, the update would start to download immediately.
Short story: I placed the su binary and su app on the root of the internal sd card via Samsung Kies, ran CASUAL to root the phone and install twrp, downloaded Quick Terminal via my desktop, placed Quick Terminal on the phone via Kies, installed it, then used Quick Terminal to disable the three apps causing the OTA update as well as delete the fragment of the update that downloaded via Wi-Fi. (I posted the commands in the loki, motochopper thread.)
After doing this, I activated the SIM and didn't have to rush to find a ROM since OTA was disabled.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Just got back from upgrading to the S4. I asked the clerk to look for a MDB or MDL and lo and behold he walked out from the back with a Black Mist 16GB MDL in his hand. Damn am I glad. :good:
There seems to be a dead spot on the touchscreen near the top. It's there on the stock ROM and on custom roms (both AOSP and ROMs based on LG's UI). Do you guys have the same issue?
http://i.imgur.com/4fKjQmG.jpg
Tried that on quick memo. I dont have it luckily.
Sent from my LG-D802 using xda premium
Tried it also. No problem for me too.
Sent from my LG-D802 using Tapatalk
My first one developed that after some time, same place too. Went to verizon, showed them that, and they replaced it with a "certified like-new" which thankfully seems to be new as far as i could tell.
UberMario said:
There seems to be a dead spot on the touchscreen near the top. It's there on the stock ROM and on custom roms (both AOSP and ROMs based on LG's UI). Do you guys have the same issue?
http://i.imgur.com/4fKjQmG.jpg
Click to expand...
Click to collapse
Saw it already reported here before. But I do not have it.
It's been reported several times here, in 99% of the time an update fixed that.
Which version do you have?
robogo1982 said:
It's been reported several times here, in 99% of the time an update fixed that.
Which version do you have?
Click to expand...
Click to collapse
I have the LG-D801 aka T-Mobile US version. The software version on it is D80110C_00. I used the LG flashing tool and flashed a .kdz file named "T-Mobile USA D80110C_00.kdz" since I bought it from craigslist and wanted it back to 100% stock (guy sold it for $80 since he rooted it and then did the OTA which caused him to go into that recovery boot loop issue and only way to fix it was to flash that .kdz file)
I'm not rooted and I am not using a custom recovery. I guess I'll do the OTA update the phone was bugging me to do.
EDIT; Installed the latest OTA. The issue is still there but it did decrease the dead zone. The biggest problem is that I can't press "install" for apps in the play store since the button is right in the dead zone.
Getting the same problem here on my device, suddenly. I updated to the new Kit Kat update (I'm on Sprint) but didn't seem to make a difference. How annoying this suddenly happened and my phone was not dropped or damaged or anything. My other friend with a G2 had the issue and it went away on its own over time somehow. i'm noticing the bar where I have trouble is aligned exactly with the power button on the back, so I wonder if that has something to do with it, in the hardware.
Hi I have the same problem too, affects where the install open button area on Play Store near the top right. I am running CloudyPro 2.1.
Did you manage to fix this problem?
randomvector said:
Hi I have the same problem too, affects where the install open button area on Play Store near the top right. I am running CloudyPro 2.1.
Did you manage to fix this problem?
Click to expand...
Click to collapse
This is very weird, same thing happened to me today around noon, phone was fine all morning, then dead zone in same area, wth is this, is At&t or LG doing something ota that we do not know about.
edit: just wanted to add, I am on the D800
I'm don't think so as I'm on a custom rom. I've heard from some on xda the update fixes it but I've used the stock KitKat Rom and no luck there. I'm now using cloudy flex 2.2 still the dead zone is there.
Sent from my Nexus 4 using Tapatalk
Same issue here too. Stock Verizon G2 on Kitkat. Can't click on install button when in play store. Turned on the 'show touch' in developer mode and it doesn't recognize the install button when on an individual app in the play store, it shows as touch above or below it. It also skips the button when i run my finger across the screen.
coreygator said:
Same issue here too. Stock Verizon G2 on Kitkat. Can't click on install button when in play store. Turned on the 'show touch' in developer mode and it doesn't recognize the install button when on an individual app in the play store, it shows as touch above or below it. It also skips the button when i run my finger across the screen.
Click to expand...
Click to collapse
Funny how this happened to me right after the ota as well...
Dead zone in the same spot ..
And well in order to fix it( the install button atleast) is to change the DPI to 330
I called lg and they gave me an authorization to send it in for repair.
Call and see what they tell u guys
This happened to me this week as well, unfortunately in Canada none of the carriers will replace my device for me, LG says its user damage and are gonna charge me 125 dollars to fix it. I'm gonna see what the local repair shop says and hopefully theyll just fix it for me. It seems like this is an increasingly common issue, it's a shame that LG don't recognize that we didn't damage our phones, they sold us defective units. I'm very unhappy with LG's customer service, we should raise awareness of this and hopefully LG will come up with a solution for us
Yep. VS980 Stock Kit kat rooted with TWRP 2.7.0.0
Same exact issue. Same exact spot. Can't hit install on the play store. Haven't tried taking it to Verizon yet. I bought my phone through Target though I hope Verizon will replace it if it is in fact a hardware issue. I'm not gonna try and take it in until after I try a couple different ROMS to make sure it is a hardware issue.
I am on D800 was on CloudyFlex when it happened so it has nothing to do with OTA exactly, I returned to fully stock At&t 4.2.2 and it was still there. I am getting a replacement under warranty. Something weird is definitely happening if so many have seen this issue. It is almost like a timer going off in phone coding and bam that part of screen is deactivated. Whatever it is, this will be my last LG phone. Never had an issue with my iphone or galaxy s2 skyrocket.
Same problem here, VS980. It started happening right after I tried the newest build of CloudyStock with knock on support. I've been browsing through multiple CloudyROM threads and I'm seeing identical problems, (including the exact area of the dead spot, around where the install button is on the Play Store). I can't post in any of them because a. I don't have enough posts, b. Cloudy in his FAQ states that the VS980 is only for testing. I've tried flashing different AOSP and Stock roms including the latest PA and XDABBEB builds and the problem crosses over after full wipes. Has anyone figured out a way to fix this yet other than returning the phone for another?
To be clear: This phone has no damage to it whatsoever. No scratches anywhere including the screen, etc. I'm worried about how Verizon will take a warranty seeing as there's an "UNROOTED" flag in the bootloader.
Has anyone tried to update touch firmware?
Sent from my LG-D803 using XDA Premium 4 mobile app
jester12345 said:
Has anyone tried to update touch firmware?
Click to expand...
Click to collapse
I've read some people do it to no avail, but I'd like some confirmation on that. The service menu still hasn't been discovered on the VS980 from what I've read. It's not the same code with a different model number at the end like the D802. For example, Every other model of the G2 is 3845#*XXX#, but the Sprint model is 5689#*980#. 3845#*980# for the VS980 doesn't work.
Dang. Now im worried to update.
Sent from my LG-D803 using XDA Premium 4 mobile app
I was updating some apps from the playstore and decided to check my voice mail by holding the 1 key in the dialer, but then my phone rebooted. Now, it won't boot past the TMO screen no matter what I do. I've tried wiping cache in recovery, and everything but a factory reset because I have a pin/fingerprint set up. I've heard that it will lock you out of your phone for 3 days if you factory reset from MM for security reasons, hence why I haven't done it. I can't find the firmware to sideload for the T-Mobile variant, can someone shed some light on this issue? It's rather annoying to have it softbrick for no reason, and not have the firmware to fix it. If someone has the firmware that would be great, or if they know how to fix it.
you can bypass FRP(the lock after reset). ive done this with about 5 s6 edges. I just bypassed one last night. i would assume it prolly works with the s7 edge also.
https://www.youtube.com/watch?v=ogMtWt7Znxw
t12icky0 said:
you can bypass FRP(the lock after reset). ive done this with about 5 s6 edges. I just bypassed one last night. i would assume it prolly works with the s7 edge also.
https://www.youtube.com/watch?v=ogMtWt7Znxw
Click to expand...
Click to collapse
I'm going to attempt a odin flash shortly since I found the firmware in the tmo subforum. Hopefully it works
Good luck
t12icky0 said:
Good luck
Click to expand...
Click to collapse
After a few "successful" flashes according to odin it finally booked correctly. It took it s long time to boot after the flash, so I'm glad it's working again. I would like to know what caused it to suddenly softbricked, I didn't do anything to cause an issue.
Not sure what happened today but everything been fine since I got my phone. Today after using bbc iplayer then going back to it from multi tasking menu everything froze up . .phone wen black and went off . .was scary to say least . .i held power and volume down for 7 seconds and it came back on. . . .nothing happen since . . .anyone know what that could have been?
PracticallyGeek said:
Not sure what happened today but everything been fine since I got my phone. Today after using bbc iplayer then going back to it from multi tasking menu everything froze up . .phone wen black and went off . .was scary to say least . .i held power and volume down for 7 seconds and it came back on. . . .nothing happen since . . .anyone know what that could have been?
Click to expand...
Click to collapse
Mine was similar except it got stuck on the tmo screen for over 10minutes before I called if softbricked.
Pilz said:
Mine was similar except it got stuck on the tmo screen for over 10minutes before I called if softbricked.
Click to expand...
Click to collapse
Did you do anything specific to flash? I'm trying to flash it but it fails
luisrcastillo said:
Did you do anything specific to flash? I'm trying to flash it but it fails
Click to expand...
Click to collapse
Are you using odin? I flashed all of the packages via Odin 3.10.7 I flashed the larger file (MD5 I think it was referred to as) and it succeeded every time according to Odin, but it took me 3 full flashes for it to boot fully.
Sent from my Nexus 6P using XDA Labs
Pilz said:
Are you using odin? I flashed all of the packages via Odin 3.10.7 I flashed the larger file (MD5 I think it was referred to as) and it succeeded every time according to Odin, but it took me 3 full flashes for it to boot fully.
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
I was using an older version of Odin so trying with the same version as you it is now flashing as we speak. Thanks!
luisrcastillo said:
I was using an older version of Odin so trying with the same version as you it is now flashing as we speak. Thanks!
Click to expand...
Click to collapse
Hopefully it works for you, I just downloaded the latest one I could find and flashed away. It seems to be working fine now despite the first boot taking a while
Sent from my Nexus 6P using XDA Labs
Pilz said:
Mine was similar except it got stuck on the tmo screen for over 10minutes before I called if softbricked.
Click to expand...
Click to collapse
So you tried the power on and volume key method but it stuck on starting up? Looks like I got off lightly . . Wonder if it's a software thing like the camera problem people are experiencing
This happened to a lot of s6edge+ users in the beginning.
Still no idea what was causing it. Updates seen to have cleared it, however, every s6edge+ reboots/freezes at launch one in a while.
Pilz said:
I'm going to attempt a odin flash shortly since I found the firmware in the tmo subforum. Hopefully it works
Click to expand...
Click to collapse
where is this firmware you speak off
PracticallyGeek said:
So you tried the power on and volume key method but it stuck on starting up? Looks like I got off lightly . . Wonder if it's a software thing like the camera problem people are experiencing
Click to expand...
Click to collapse
Yes no matter what I did it would not boot pas the T-Mobile screen.
kappatau808 said:
where is this firmware you speak off
Click to expand...
Click to collapse
In the T-Mobile S7E subforum
Sent from my Nexus 6P using XDA Labs
Pilz said:
After a few "successful" flashes according to odin it finally booked correctly. It took it s long time to boot after the flash, so I'm glad it's working again. I would like to know what caused it to suddenly softbricked, I didn't do anything to cause an issue.
Click to expand...
Click to collapse
Well, consider yourself lucky. I had (in fact have) a Moto 360 which was bricked by Motorola at the last update and now it's sitting on my desk as a paperweight for more than a month.
Cst79 said:
Well, consider yourself lucky. I had (in fact have) a Moto 360 which was bricked by Motorola at the last update and now it's sitting on my desk as a paperweight for more than a month.
Click to expand...
Click to collapse
That sucks is it the gen 1 or 2? Moto support went downhill after I bought my Nexus 6 from back in 2014. I haven't bought a Moto product since then for that reason. Can you boot into this bootloader at all? I've flashed my Huawei watch before without an issue.
Sent from my Nexus 6P using XDA Labs
Pilz said:
That sucks is it the gen 1 or 2? Moto support went downhill after I bought my Nexus 6 from back in 2014. I haven't bought a Moto product since then for that reason. Can you boot into this bootloader at all? I've flashed my Huawei watch before without an issue.
Sent from my Nexus 6P using XDA Labs
Click to expand...
Click to collapse
It is Gen1. It is fixable via ADB, with a proper connection rig but my improvised rig resulted in a fried USB port on one of my computers after a successful connection, so I just gave up. I may one day buy a Chinese connection rig (there are some nice ones for sale) but the investment is just not worth it, I will probably get a Gear S2 and be done with Motorola, forever.
Cst79 said:
It is Gen1. It is fixable via ADB, with a proper connection rig but my improvised rig resulted in a fried USB port on one of my computers after a successful connection, so I just gave up. I may one day buy a Chinese connection rig (there are some nice ones for sale) but the investment is just not worth it, I will probably get a Gear S2 and be done with Motorola, forever.
Click to expand...
Click to collapse
I know this is a little off topic:
Motorola didn't make it easy due to their lack of pogo pins (even though most people don't like them). I'm not sure how it would fry a USB port, but anything can happen. I plugged my 6P into my Surface Pro 4's dock via an A-C cable and it windows said it was trying to pull to much current and shut off the port until I rebooted. Things happen for better or worse, but I prefer AW over Tizen due to the long term support, despite liking Samsung's rotating bezel.
Pilz said:
I'm going to attempt a odin flash shortly since I found the firmware in the tmo subforum. Hopefully it works
Click to expand...
Click to collapse
can you send a link where you found that tmobile firmware? I'm having the same issue of not being able to go past the white t-mobile screen