Hi there,
I recently purchased a zenfone 2 from ebay (I believe it to be the Z00A, 4GB model).
It had some issues, such as the touchscreen not working, but the phone is in generally flawless condition.
I was able to get it to boot up (seller said it wouldn't boot), used USB OTG keyboard and mouse to do initial "Welcome" setup.
Connected it to my wifi, and it asks me to login to the previously used google account. I obviously can't do that.
Am I boned? I want to send it in to ASUS for repair, but I don't know what would happen in this scenario.
I'm thinking I should just file a paypal chargeback on the device.
Boot into fastboot, unlock the bootloader, and then re flash the original bootloader. Or see if you can factory reset via the recovery options.
NissanskylineN1 said:
Boot into fastboot, unlock the bootloader, and then re flash the original bootloader. Or see if you can factory reset via the recovery options.
Click to expand...
Click to collapse
Touchscreen doesn't work. Can't enable USB debugging.
Try entering the word "null" for user and password. (No quotes of course)
Sent from M919V Galaxy S4 via XDA Premium HD app.
madman604 said:
Try entering the word "null" for user and password. (No quotes of course)
Click to expand...
Click to collapse
Didn't work, it requires a google account. says unknown account for "null"
I was able to get in. Now, any ideas why the touchscreen won't work? The screen is not cracked or damaged in any way.
You can try to get it repaired by asus. If you need to try and reflash the firmware, I think it should take an OTG mouse.
arusiasotto said:
You can try to get it repaired by asus. If you need to try and reflash the firmware, I think it should take an OTG mouse.
Click to expand...
Click to collapse
I am going to try their advanced repair service. Hopefully this will work out, because I was really excited to get this phone working myself, I was even going to consider trying to replace the LCD/Touchpanel myself, but if asus will fix it, then that would be even better.
My Zenfone was recently stolen, it's a chance in a million but if you did find it please report the guy who sold it to you to the police. You know it's mine if you take the back cover off and all the screws but the void one are missing. I did that intentionally in case something like this happened. Reply here if those screws are missing. If not, guess it wasn't mine.
millybricks said:
My Zenfone was recently stolen, it's a chance in a million but if you did find it please report the guy who sold it to you to the police. You know it's mine if you take the back cover off and all the screws but the void one are missing. I did that intentionally in case something like this happened. Reply here if those screws are missing. If not, guess it wasn't mine.
Click to expand...
Click to collapse
Mine had all the screws in it, I don't think it's yours
Coolty said:
I was able to get in. Now, any ideas why the touchscreen won't work? The screen is not cracked or damaged in any way.
Click to expand...
Click to collapse
How were you able to get in? I bought the exact phone and its stuck at the google verification screen after wifi set up.
I have no clue what the previous owners info was.
Related
(NOTE THAT I AM ONLY EXPLAINING IN *DETAIL SO THAT SOMEONE MAY BE ABLE TO CORRECTLY ANALYZE THE PROBLEM)
Okay, so I got my new AT&T Samsung Galaxy S III less than a month ago.
My friend helped me in the past few days to root and install cyanogenmod 10. Everything was still fine, until I did something in some kind of pixel density changing app. When rebooting, it only showed the Samsung and Samsung Galaxy S III screens when booting up, but went no further. I wiped everything and restored the last backup I made (advanced restore). Everything ran fine again, with all the original factory stuff. I decided to try and see if I could reinstall cm10 (wiped everything, installed zip, rebooted), and it was successful. Then I decided I wanted to wipe that and try out Energy HD 2.0. Once trying to install the zip, it returned an error message and aborted. I then decided to scrap that idea and just go back to the original factory rom and everything. So I once again wiped and restored my last backup. Upon hitting Reboot, it just went black and didn't turn on again. Now I am completely unable to turn it on, charge it, go into cwm recovery, or download mode. Plugging into the computer just pops a driver install message for QHSUSB_LOAD. Never has anything, even the LED, so much as blinked.
Can somebody please help me? I just would like to know if there is a way to get it working. I'd be very grateful, thanks!
*detail, meaning just what I was doing, as I do not remember exact error codes and such.
Try reflashing. What stock image are you using?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
kinghorsey said:
Try reflashing. What stock image are you using?
Click to expand...
Click to collapse
Is it even possible to re-flash a recovery image (from Odin3) when the device cannot enter download mode?
I think it may have been CWM Recovery v5.0.4.2 or something that I originally installed/flashed (can't check right now though, because I was kicked off my computer). Then it had upgraded to v6.something later on my phone.
((Sent from my stupid old iPhone 3Gs))
Look into jtag service
sent from outside ur window
twanskys204 said:
Look into jtag service
sent from outside ur window
Click to expand...
Click to collapse
Haha, okay. I just don't want to spend $60 at this very moment.
Sent from omygoshwhatthehellareyoudoingoutthere
stupid iPhone
Ascyndaeon said:
Haha, okay. I just don't want to spend $60 at this very moment.
Click to expand...
Click to collapse
Yeah I would say your bootloader is messed up and the only way to breath life back into your phone is jtag repairs. I had a problem identicle to yours and I searched the net for a week solid trying to figure out how to fix it without having to fork over the money.. but alas had to send it. Luckily the guy who provides the repairs is amazing at what he does. Phone will be back in your hands within a few days if you're from the states.
fallenkirmit said:
Yeah I would say your bootloader is messed up and the only way to breath life back into your phone is jtag repairs. I had a problem identicle to yours and I searched the net for a week solid trying to figure out how to fix it without having to fork over the money.. but alas had to send it. Luckily the guy who provides the repairs is amazing at what he does. Phone will be back in your hands within a few days if you're from the states.
Click to expand...
Click to collapse
Hmm, okay. I wonder then why only JTAG Repairs knows how to fix this stuff, and the information isn't widely available.
And so if I do send it to jtag, then I guess I'll be getting it back within a few days, 'cause I live in the US.
Thanks for your input.
Ascyndaeon said:
Hmm, okay. I wonder then why only JTAG Repairs knows how to fix this stuff, and the information isn't widely available.
And so if I do send it to jtag, then I guess I'll be getting it back within a few days, 'cause I live in the US.
Thanks for your input.
Click to expand...
Click to collapse
Well there is a way for you to do the jtag repairs yourself... but i wouldn't touch the process with a 10 foot pole lol... I would rather let a pro do things like that... just youtube jtag repair and take a look at some of the process.... way beyond my comprehension atleast..
fallenkirmit said:
Well there is a way for you to do the jtag repairs yourself... but i wouldn't touch the process with a 10 foot pole lol... I would rather let a pro do things like that... just youtube jtag repair and take a look at some of the process.... way beyond my comprehension atleast..
Click to expand...
Click to collapse
Ah, I suppose you're right. Not to mention expensive. That equipment probably costs more than having them fix it. Though it would probably be worth it of you bricked it on a regular basis.
Unfortunately I managed to drop my phone over the weekend. Not particularly far, but as a result the screen is cracked. The display actually seems to work fine, but touch recognician is gone so I can't use my unlock code or access any of my data.
It isn't a total loss as I have equipment protection. My new phone will be here today. I need to do two things. First get all my pictures off the device and second wipe everything off it before I send the broken one back. The phone is on V9 and is rooted. The boot loader is locked. USB debugging is turned on. As I mentioned I have an unlock pattern. Please help!
Thanks all,
Jager
yikes
Jaegerrr said:
Unfortunately I managed to drop my phone over the weekend. Not particularly far, but as a result the screen is cracked. The display actually seems to work fine, but touch recognician is gone so I can't use my unlock code or access any of my data.
It isn't a total loss as I have equipment protection. My new phone will be here today. I need to do two things. First get all my pictures off the device and second wipe everything off it before I send the broken one back. The phone is on V9 and is rooted. The boot loader is locked. USB debugging is turned on. As I mentioned I have an unlock pattern. Please help!
Thanks all,
Jager
Click to expand...
Click to collapse
Probably not very helpful tip but here goes.
Obviously you cant take it to Sprint while its rooted, since that voids your warranty. The ONLY options I can think of is either to try to open your phones files onto your PC with the USB cord and troubleshooting trying to get it back to anything stock. 2.) Try using your phones screen sideways? ( Had an HTC with busted digitizer, this worked for me.) 3.) Last but not least, there is a way to get the phone apart via two very small T bits. not sure what size. But if your tech savvy, you can always try replacing the screen and or digitizer yourself with parts from overseas. They may take several weeks to arrive, but there cheap.
If I find anything else, Ill let you know. Hope I helped? And sorry man, thats a frustrating predicament.
Jaegerrr said:
Unfortunately I managed to drop my phone over the weekend. Not particularly far, but as a result the screen is cracked. The display actually seems to work fine, but touch recognician is gone so I can't use my unlock code or access any of my data.
It isn't a total loss as I have equipment protection. My new phone will be here today. I need to do two things. First get all my pictures off the device and second wipe everything off it before I send the broken one back. The phone is on V9 and is rooted. The boot loader is locked. USB debugging is turned on. As I mentioned I have an unlock pattern. Please help!
Thanks all,
Jager
Click to expand...
Click to collapse
what i suggest doing is lgnpst it back to stock, this will unroot you BUT will not erase any of your personal files. then when you get your new phone go to sprint and ask them to transfer everything over. if you wanna do this just pm me and ill give you the files. they are copyrighted so i cant post them on here.
Tried USB... What about ADB?
I tried plugging in with USB and I can't see my files. I guess that is probably because I have the phone locked with a pattern. As I mentioned, I got a replacement via equipment protections so I'm not going to fix it... It's a work phone anyway. I got a replacement today and have to send the old one back.
I was hoping someone savy with ADB could tell me how to get the pictures from my phone that way. In addition, I would think there would be a way to force a factory reset at the leass so I won't sending the broken phone back with all my personal information on it.
Thanks again,
Jaeger
Figured it out....
I found my way and wanted to post what I did incase anyone else is ever searching for this.
I guess I was lucky that USB debugging was turned on. I simply connected and used the adb shell to look at my files and adb pull commands to download all my pictures.
The next part was wiping my data. This was luckily a work phone connected to my companies exchange server. I simply went into outlook via the web interface and went to options and then phone. You could easily wipe the phone from there.
I guess what I really learned from this is to have phone cloud back-ups in place. Even if you are careful with your stuff (as I am), the unforseen always occurs.
-Jaeger
Bricked my Nexus 4 flashing a wrong ROM. Since i'm in EU and the phone USA probably will not get warrantly either
Now it won't even go to recovery, is there anything i can try?
Razer(x) said:
Bricked my Nexus 4 flashing a wrong ROM. Since i'm in EU and the phone USA probably will not get warrantly either
Now it won't even go to recovery, is there anything i can try?
Click to expand...
Click to collapse
Is it going into fastboot?
(with phone off, press power and volume down)
EDIT: This is in wrong section. Should be in Q&A / Troubleshooting
Tought i was in Q/A, yes should be moved/closed
Unfortunately no fastboot
OK is anything happenning when you plug into computer?
Is USB recognising anything? What did you try to flash?
N10AP said:
OK is anything happenning when you plug into computer?
Is USB recognising anything? What did you try to flash?
Click to expand...
Click to collapse
When i connect it to the pc it tries to install drivers, but then nothing happens
try getting into fastboot..
or try connecting it to the pc n install the toolkit n then use the option 16
OK you can try to install the qualcomm drivers as the phone must be in download mode. That`s why its recognising it.
Then I think you need to flash a hex image or something.
Take a look:
http://forum.xda-developers.com/showthread.php?t=2108247
Maybe one of the kind members here (a regular) may let you send it to them in the states and you could RMA it from there?
N10AP said:
OK you can try to install the qualcomm drivers as the phone must be in download mode. That`s why its recognising it.
Then I think you need to flash a hex image or something.
Take a look:
http://forum.xda-developers.com/showthread.php?t=2108247
Maybe one of the kind members here (a regular) may let you send it to them in the states and you could RMA it from there?
Click to expand...
Click to collapse
Not sure what should i do
What rom did you flash?
Seroiusly mate. IMHO if you don`t have the qualcomm hex images (or whatever they are) or a means of JTAGing your phone, then only option is to send it to someone in the US who can RMA it. For the cost of postage and maybe a beer for the kind person, they could do it for you.
Assuming you ordered it from your Google account when you was in the US...
1) Find someone trustworthy in US
2) Ask if you can send your Nexus 4 to them
3) They RMA it using your account details
4) They send the new device to you in Europe when google drop it off.
Everyones happy.
sandy-achar said:
What rom did you flash?
Click to expand...
Click to collapse
An AOSP rom for Note
N10AP said:
Seroiusly mate. IMHO if you don`t have the qualcomm hex images (or whatever they are) or a means of JTAGing your phone, then only option is to send it to someone in the US who can RMA it. For the cost of postage and maybe a beer for the kind person, they could do it for you.
Assuming you ordered it from your Google account when you was in the US...
1) Find someone trustworthy in US
2) Ask if you can send your Nexus 4 to them
3) They RMA it using your account details
4) They send the new device to you in Europe when google drop it off.
Everyones happy.
Click to expand...
Click to collapse
Yeah, but shipping to US takes weeks, RMA takes weeks too
Might ask in Italy before
Razer(x) said:
An AOSP rom for Note
Yeah, but shipping to US takes weeks, RMA takes weeks too
Might ask in Italy before
Click to expand...
Click to collapse
as i seem to recall, even an unlocked bootloader wont give u access to boatloader partition and other important partitions..
which makes it still recoverable..
if u ask me, get a different pc with windows vista/7 *not windows 8*, download the nexus drivers from xda and install and then try flashing via fastboot..
and if i seem to recall, the installation scripts in the rom.zip dont format partitions numbers but use tags such as system or data which is predefined so you cant flash system in bootloader by mistake..
ofcourse, i can be wrong
Can't go in fastboot mode, that's the problem
I think the only option is to send it to a JTAG service, if sending to google aint possible. I remember reading it was around 60 USD to revive a nexus 4.
maybe its the charge?
leave it for charging for 30 min-ish
then try fastboot
or try holding power for 20 second-ish to make sure the phone's restarted
as in, maybe its semi-booted
Charging doesn't work, will need a JTAG service or ask LG support
Just noticed this on W8
Razer(x) said:
An AOSP rom for Note
Yeah, but shipping to US takes weeks, RMA takes weeks too
Might ask in Italy before
Click to expand...
Click to collapse
I know it may take a while, but it`s a means to an end. A bricked Nexus 4 is no good to anyone, unless you want to sell it for a pittance for parts...
Personally I wouldn`t care if it took weeks. You would be getting a brand new phone eventually.
http://mobiletechvideos.mybigcommerce.com/lg-nexus-4-jtag-brick-repair/
DOOOO ITTTTTTTTT !!!!
On a serious note, i bricked my nexus somehow a while back and these guys were able to fix my phone , they are very trustworthy.
BTW they do have international shipping too
EDIT: just checked , its 105 dollars in total for a repair, you have a couple choices: you can sell your phone for pieces (there is high demand for screens since everyone is cracking theirs, and as you know it doesnt work after being cracked), you can find someone local to repair, and your last choice is to just take the bullet and pay 105 dollars (+ shipping from your area to them) to send and repair your phone.
I'm sure there's another way to fix it bro.. It can't be that hard. Just search around
SneakyGuyDavid said:
there is high demand for screens since everyone is cracking theirs, and as you know it doesnt work after being cracked
Click to expand...
Click to collapse
Yeah, don't remind me.... (been there, done that)
But on a related note, sounds like a JTAG is definitely in order. If you're comfortable learning how to use a JTAG yourself, I believe they're about $150-200. You can fix your phone, and keep the JTAG to start fixing other phones in your spare time. After a few repairs, it would pay for itself! I've often considered going this route. Something I've thought of doing is buying bricked phones for cheap, fix them with a JTAG, and resell them for profit. Could be a fun little business and you'd learn a lot about several different devices. Look up the RIFF Box or Medusa Box - definitely do some research first, if you decide to go through with this. Just a suggestion at the very least...
I was excited to see that one of my Nexus 7 tablets was getting the 4.4.3 update today. I started the update and let it go. When I came back I was at the lock screen. I only have the simple swipe to unlock. I couldn't unlock it at all. Held in the power button for several seconds until it shut off. Thought maybe something didn't load right. When I booted it back up, same thing. No touch screen.
Here is a little background. This is a Nexus 7 v2. Unlocked it and rooted it using the Nexus Root Toolkit version 1.8.2. During the process I did install the recommended recovery option. Everything worked great until the update today. Seems like I can't do anything. I can't use this toolkit to restore from the backup I made because I can't get into the tablet to turn on USB debugging or whatever it is asking me to do. I tried booting into recovery by holding the volume down and power button. The result was a picture of the android with a red triangle and an exclamation point. Not sure what else to do so I am posting this for all of you guys with more experience than me. Can anyone give me any suggestions?
opreda said:
I was excited to see that one of my Nexus 7 tablets was getting the 4.4.3 update today. I started the update and let it go. When I came back I was at the lock screen. I only have the simple swipe to unlock. I couldn't unlock it at all. Held in the power button for several seconds until it shut off. Thought maybe something didn't load right. When I booted it back up, same thing. No touch screen.
Here is a little background. This is a Nexus 7 v2. Unlocked it and rooted it using the Nexus Root Toolkit version 1.8.2. During the process I did install the recommended recovery option. Everything worked great until the update today. Seems like I can't do anything. I can't use this toolkit to restore from the backup I made because I can't get into the tablet to turn on USB debugging or whatever it is asking me to do. I tried booting into recovery by holding the volume down and power button. The result was a picture of the android with a red triangle and an exclamation point. Not sure what else to do so I am posting this for all of you guys with more experience than me. Can anyone give me any suggestions?
Click to expand...
Click to collapse
Once you are back at the android lying on its back, hold down power and tap the volume up key, this will get you a recovery menu, from there you can try to wipe cache and dalvik, and if need be, factory reset.
Touch screen is still dead.
Thanks for the quick update. I did all of the above and was able to reset the tablet. Not I am at the Welcome screen and tapping the screen does nothing I find it hard to believe that the touchscreen died during the update. I guess I will need to look on EBay for some parts. Can anyone suggest what parts to look for? Touch screen digitizer assembly is listing for around $65.
opreda said:
Thanks for the quick update. I did all of the above and was able to reset the tablet. Not I am at the Welcome screen and tapping the screen does nothing I find it hard to believe that the touchscreen died during the update. I guess I will need to look on EBay for some parts. Can anyone suggest what parts to look for? Touch screen digitizer assembly is listing for around $65.
Click to expand...
Click to collapse
I might suggest you open it up now (you're going to have to anyways to replace it), and make sure the cable is securely inserted.
opreda said:
Thanks for the quick update. I did all of the above and was able to reset the tablet. Not I am at the Welcome screen and tapping the screen does nothing I find it hard to believe that the touchscreen died during the update. I guess I will need to look on EBay for some parts. Can anyone suggest what parts to look for? Touch screen digitizer assembly is listing for around $65.
Click to expand...
Click to collapse
If touch works in TWRP then its not hardware related
Sent from my Nexus 4 using XDA Free mobile app
Tried the cables...
I found a tear down video on YouTube and was able to disconnect and then reconnect the long cable that goes across the battery connecting the 2 circuit boards. I believe this cable is connected to the digitizer. I was hoping that maybe this would fix my problem. No such luck.
Here is my question. This tablet was purchased on EBay and was sold as a refurbushed tablet with a 90 day warranty from Asus. I purchased it about a month ago so I should be in the warranty period. Since I unlocked the bootloader and rooted it, should I even try to send it to Asus for repair or should I just spend the $65 and buy the replacement parts on EBay? Instead of just buying the digitizer, I was thinking I would get the combo digitizer and lcd screen since it would save me having to use a heat gun to unglue the screen from the digitizer.
What do you think would be my best bet?
Thanks to everyone for all your suggestions.
opreda said:
I found a tear down video on YouTube and was able to disconnect and then reconnect the long cable that goes across the battery connecting the 2 circuit boards. I believe this cable is connected to the digitizer. I was hoping that maybe this would fix my problem. No such luck.
Here is my question. This tablet was purchased on EBay and was sold as a refurbushed tablet with a 90 day warranty from Asus. I purchased it about a month ago so I should be in the warranty period. Since I unlocked the bootloader and rooted it, should I even try to send it to Asus for repair or should I just spend the $65 and buy the replacement parts on EBay? Instead of just buying the digitizer, I was thinking I would get the combo digitizer and lcd screen since it would save me having to use a heat gun to unglue the screen from the digitizer.
What do you think would be my best bet?
Thanks to everyone for all your suggestions.
Click to expand...
Click to collapse
You can always unroot and relock the bootloader (you can use this to get it back to factory), if it's under warranty I'd go that route.
USB debugging...
Wouldn't this require me to have USB debugging enabled on the tablet? Since I went into recovery and restored it back to factory defaults, I can't get past the "Welcome" screen because I can't touch the screen. I am going to try and chat with the Asus support team and see if I can get an RMA. I'd rather go that route than take the whole thing apart myself. I like messing with computers but I don't like messing with phones and tablets. They are just too small and fragile for my unskilled hands. Thanks for your help. I will post an update if I am able to send the tablet out for repair.
opreda said:
Wouldn't this require me to have USB debugging enabled on the tablet? Since I went into recovery and restored it back to factory defaults, I can't get past the "Welcome" screen because I can't touch the screen. I am going to try and chat with the Asus support team and see if I can get an RMA. I'd rather go that route than take the whole thing apart myself. I like messing with computers but I don't like messing with phones and tablets. They are just too small and fragile for my unskilled hands. Thanks for your help. I will post an update if I am able to send the tablet out for repair.
Click to expand...
Click to collapse
It uses fastboot, I don't think it needs it (in spite of what the OP says). And if I'm wrong, the worst that will happen is it won't work. You will need the fastboot drivers correctly installed in your windows or linux environment though.
worked
Thanks for the link. I ran the dead_nexus7.bat file since I couldn't turn on the USB debugging. It wiped out everything. I then ran the command to relock the bootloader. All set. Talked with Asus (web chat) and got an RMA number. They even sent me a FedEx label to use. Now I am more comfortable sending this unit back since it has been restored to stock and the bootloader is locked again. Thank you for all of your help.
opreda said:
Thanks for the link. I ran the dead_nexus7.bat file since I couldn't turn on the USB debugging. It wiped out everything. I then ran the command to relock the bootloader. All set. Talked with Asus (web chat) and got an RMA number. They even sent me a FedEx label to use. Now I am more comfortable sending this unit back since it has been restored to stock and the bootloader is locked again. Thank you for all of your help.
Click to expand...
Click to collapse
No problem, please let me know how it worked out. Good luck!
Update to my issue...
I contacted Asus using their web chat. Told the CSR about my issue and confirmed my Nexus 7 serial number. They emailed me paperwork to take to my local FedEx shipping location. It happened to be our local Office Max store. They scanned in the bar-code and processed it. I got a confirmation email with the tracking number. This was around June 6th. They received it in Texas 4-5 days later (because of the weekend). I checked the status almost every day. About 10 days after they received it I saw a status update. They included a FedEx tracking number but every time I entered it into the FedEx website, it showed up as invalid. I gave it a couple of days and then called FedEx. They were able to track the package and it was delivered to my house in late June. All in all it took about 3 weeks but they did repair it. I thought they would have just sent me a refurbished tablet. They actually fixed my tablet because it still had my screen protector on it. Just wanted to update you with the good news. My son was so excited to finally get his tablet back. I wasn't expecting it to take so long but I guess I can't complain. It didn't cost me anything out of pocket even to ship it to them. Thank you for your help with getting everything back to stock and the boot-loader locked.
Tablet was originally purchased as a refurbished tablet from a seller on EBay. It was supposed to have a 90-day warranty from Asus. Glad they held up their end. It all worked out in the end.
opreda said:
I contacted Asus using their web chat. Told the CSR about my issue and confirmed my Nexus 7 serial number. They emailed me paperwork to take to my local FedEx shipping location. It happened to be our local Office Max store. They scanned in the bar-code and processed it. I got a confirmation email with the tracking number. This was around June 6th. They received it in Texas 4-5 days later (because of the weekend). I checked the status almost every day. About 10 days after they received it I saw a status update. They included a FedEx tracking number but every time I entered it into the FedEx website, it showed up as invalid. I gave it a couple of days and then called FedEx. They were able to track the package and it was delivered to my house in late June. All in all it took about 3 weeks but they did repair it. I thought they would have just sent me a refurbished tablet. They actually fixed my tablet because it still had my screen protector on it. Just wanted to update you with the good news. My son was so excited to finally get his tablet back. I wasn't expecting it to take so long but I guess I can't complain. It didn't cost me anything out of pocket even to ship it to them. Thank you for your help with getting everything back to stock and the boot-loader locked.
Tablet was originally purchased as a refurbished tablet from a seller on EBay. It was supposed to have a 90-day warranty from Asus. Glad they held up their end. It all worked out in the end.
Click to expand...
Click to collapse
Good to hear, thanks for the update.
I finally was forced to update to android 5.0.1. I updated at work but it failed halfway through and is now in a boot loop. I've tried every solution the internet can provide me. What do I do now? The device IMEI has a limited warranty until 2017. I purchased through swappa. I have original box but no documentation besides the barcode sticker on the side. Will AT&T replace this? It was their update that caused this anyway. Any experiences with this sort of thing please? I dropped a large chunk of change on this paperweight. Thanks
Wildstar34 said:
I finally was forced to update to android 5.0.1. I updated at work but it failed halfway through and is now in a boot loop. I've tried every solution the internet can provide me. What do I do now? The device IMEI has a limited warranty until 2017. I purchased through swappa. I have original box but no documentation besides the barcode sticker on the side. Will AT&T replace this? It was their update that caused this anyway. Any experiences with this sort of thing please? I dropped a large chunk of change on this paperweight. Thanks
Click to expand...
Click to collapse
The first thing to do is find a local Best Buy with a Samsung Experience shop. They can reflash the firmware or send the phone in for repairs. This would be the best and easiest option. Most likely, you'll be able to get everything fixed in around an hour max.
BTW, it doesn't matter if the device was purchased from somewhere other than Best Buy!
I'm not sure if ATT will replace the phone if you didn't buy it from ATT. You can contact them to see though. Call them and tell them that you bought the device from Swappa. Though, most likely, they'll turn you away unless they have some sort of business alliance with Swappa.
Do this as a Plan B.
The third option is to get in contact with Swappa. I don't know anything about that service though. Usually in order to claim warranty, you need the device and proof of purchase. If Swappa has an online receipt, or even just an online purchase history, that should work. They most likely would just need some sort of proof that you actually bought the device from or through them. Like I said, I don't know anything about Swappa, so you'll have to contact them to get specifics of what you'd need.
When all else fails, go directly to Samsung. Again, tell them that you got the device from Swappa. Though, this would basically be like the first option, except that it would take longer.
All options except the first one may result in you getting a refurbished replacement. Just an FYI. The only way that Best Buy will give you a refurbished replacement is if they were to send the phone back to Samsung and it was replaced.
PM me if needed!
Sent from my SM-P600 using Tapatalk
spexwood said:
The first thing to do is find a local Best Buy with a Samsung Experience shop. They can reflash the firmware or send the phone in for repairs. This would be the best and easiest option. Most likely, you'll be able to get everything fixed in around an hour max.
BTW, it doesn't matter if the device was purchased from somewhere other than Best Buy!
I'm not sure if ATT will replace the phone if you didn't buy it from ATT. You can contact them to see though. Call them and tell them that you bought the device from Swappa. Though, most likely, they'll turn you away unless they have some sort of business alliance with Swappa.
Do this as a Plan B.
The third option is to get in contact with Swappa. I don't know anything about that service though. Usually in order to claim warranty, you need the device and proof of purchase. If Swappa has an online receipt, or even just an online purchase history, that should work. They most likely would just need some sort of proof that you actually bought the device from or through them. Like I said, I don't know anything about Swappa, so you'll have to contact them to get specifics of what you'd need.
When all else fails, go directly to Samsung. Again, tell them that you got the device from Swappa. Though, this would basically be like the first option, except that it would take longer.
All options except the first one may result in you getting a refurbished replacement. Just an FYI. The only way that Best Buy will give you a refurbished replacement is if they were to send the phone back to Samsung and it was replaced.
PM me if needed!
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Hey, thanks a lot. This may be the single most helpful forum post I've ever read. I will drive up to BestBuy tomorrow and give it a shot. I wasn't able to flash a AT&T stock rom through Odin, but I guess it's worth a shot. I believe the flash failure was due to the AT&T bootloader being locked?
Wildstar34 said:
Hey, thanks a lot. This may be the single most helpful forum post I've ever read. I will drive up to BestBuy tomorrow and give it a shot. I wasn't able to flash a AT&T stock rom through Odin, but I guess it's worth a shot. I believe the flash failure was due to the AT&T bootloader being locked?
Click to expand...
Click to collapse
Welcome!
Most likely something just went wrong during the installation. The bootloader is not a factor in this matter since all ATT Note 4s have it locked and the firmware is meant for this phone.
Now, if you had the phone rooted (permanently), installed a custom kernel and recovery, etc, then the update failure would be 100% explainable. But since you can't do any of that with this phone, then the most likely cause is just "sh1t happened" or the installation was interrupted (like battery died).
Sent from my SAMSUNG-SM-N910A using Tapatalk
Have you tried kies to reflash your phone?
floatingtrees said:
Have you tried kies to reflash your phone?
Click to expand...
Click to collapse
I used Kies, Kies3 and Swap Sync or whatever to do an emergency restore. All of them failed. Kies 3 recognized the phone and was 98% done downloading the firmware and then failed.
Also i am not rooted and never attempted a root (on this phone anyway).
Good news. Just got off the phone with AT&T and they have a replacement on the way. Thanks for your help everybody. We have achieved the best case senario for me as i was having problems with the volume buttons anyway
I would consider this case solved.
Wildstar34 said:
Good news. Just got off the phone with AT&T and they have a replacement on the way. Thanks for your help everybody. We have achieved the best case senario for me as i was having problems with the volume buttons anyway
I would consider this case solved.
Click to expand...
Click to collapse
Awesome! Win-win for you (I guess?)
If the volume keys were messed up, then I wonder if there was some other problems with the phone too. Ones you couldn't see... ones that prevented proper firmware installation.
Sent from my SM-P600 using Tapatalk