Cracked Screen - Need to relock bootloader for RMA! - Nexus 7 Q&A, Help & Troubleshooting

Help!
My Nexus 7 screen randomly cracked (no touch input) and I have to send it back to Asus for RMA, I have managed to use Wug's Toolkit to flash stock and unroot, but when I try to re-lock the bootloader with the tool a message pops up on the Nexus 7 screen asking me to allow the connection, but I can't because if I take out the USB cable to put in my OTG mouse, the message goes away!
I've tried Airdroid but that doesn't work, please help otherwise Asus will say my warranty is voided :crying: :crying:
Thank you
Alan

Keydogg1 said:
Help!
My Nexus 7 screen randomly cracked (no touch input) and I have to send it back to Asus for RMA, I have managed to use Wug's Toolkit to flash stock and unroot, but when I try to re-lock the bootloader with the tool a message pops up on the Nexus 7 screen asking me to allow the connection, but I can't because if I take out the USB cable to put in my OTG mouse, the message goes away!
I've tried Airdroid but that doesn't work, please help otherwise Asus will say my warranty is voided :crying: :crying:
Thank you
Alan
Click to expand...
Click to collapse
Mine cracked for no reason too!!
did you have screen lifting problems maybe?
What does RMA stand for? Can you get a new one for this?
And looks like we have the same problem...maybe try with a usb extender? Or bluetooth mouse

RMA is just the returns procedure, but the guy on the phone said I have a chance of getting it repaired through warranty if it's a screen defect (which it is, i have never damaged it!).
I don't have a bluetooth mouse

What exactly is the difficulty with putting the tablet into bootloader mode and using a single fastboot command to relock the bootloader? You don't need a mouse or even a working screen to do that.
If you installed a toolkit on your PC, then you also have fastboot installed too - the toolkit is mostly just a wrapper around the fastboot (and adb) program(s).
Probably you can simply just repeat what you tried with the toolkit but starting with the tablet in bootloader mode. (But don't quote me on that, I don't use toolkits).
BTW, it is not the *current* condition of the bootloader lock state that determines the validity of your warranty - if you unlocked the boot loader at any time in the past, your warranty is voided.

bftb0 said:
BTW, it is not the *current* condition of the bootloader lock state that determines the validity of your warranty - if you unlocked the boot loader at any time in the past, your warranty is voided.
Click to expand...
Click to collapse
Im not too sure about that...
I talked to my local htc service and they say that they dont care what was done before it, they just want it in the condition in which they sold it to me.

mrsofa said:
Im not too sure about that...
I talked to my local htc service and they say that they dont care what was done before it, they just want it in the condition in which they sold it to me.
Click to expand...
Click to collapse
I get that. It makes no business sense for Asus to go all CSI on every tablet that comes in the door for repair, although I'm pretty sure they could tell quite easily whether a tablet has been previously unlocked if they actually wanted to. (No matter what state it is in when they receive it).
My point was about the T&C's (legal terms) that owners agree to in the click-through dialogs when they unlock their tablet. What folks "get away with" is a separate issue.
I'm pretty sure that XDA's policy is to encourage people to act in a stand-up fashion. Agreeing to terms and then later doubling back on them reflects poor character.

Unlocking or re-locking the bootloader doesn't involve the touch screen at all... everything is done with the buttons on the right hand side of the Nexus 7.
(Re-locking doesn't even require the buttons- just fastboot oem lock).
It's also debatable whether unlocking the bootloader actually violates warranty... see the screenshot attached (from my last N7 OEM unlock).
- note the use of the phrase...
may void warranty
'May' is a highly subjective word, that covers a whole multitude of sins.
Rgrds,
Ged.

Well, I suppose to avoid any shed tears I should have just pointed out that the information the OP sought - and now answered - can be posed in a way that completely avoids making XDA look like a place that encourages questionable behavior, or that people that offer technical assistance are complicit in those behaviors.
For instance:
"Hi! My Nexus 7 has a cracked screen so I am unable to use the touchscreen. I would like to lock the bootloader. (insert part about toolkit) How do I go about doing this?"
Note the complete lack of mention of warranty or RMA - it is completely irrelevant to the technical part of the discussion anyway & keeps XDA's nose clean.
cheers

Sorry buddy, I didn't mean any offence or to tarnish XDA's reputation - I love this place!
Ged - With regards to the command. I have always used toolkits (newb!) so didn't know how to execute a command whilst it was in fastboot mode, but I've just figured that our and it worked! Thank you very much mate

Keydogg1 said:
Sorry buddy, I didn't mean any offence or to tarnish XDA's reputation - I love this place!
Ged - With regards to the command. I have always used toolkits (newb!) so didn't know how to execute a command whilst it was in fastboot mode, but I've just figured that our and it worked! Thank you very much mate
Click to expand...
Click to collapse
You are most welcome...
Fastboot (and adb) is the easiest way of doing these sorts of things, rather than using a toolkit - although fastboot isn't currently an option for me, as I've relocked my bootloader and am running my device rooted (by exploit) and a custom ROM flashed via TWRP, which I flashed via the 'dd' command in Terminal Emulator. Thanks to bftb0 for info on how to do that... I was astonished when it worked. You can tell I'm still learning stuff here.
--------
Apologies from me as well, bftb0, regarding 'questionable behavior' and those 'complicit in those behaviors'... it's a fair point well made. XDA is too good and valuable a place to have it's reputation sullied by posts which encroach into areas of dubious legality, so I will confine my future posts to technical matters only... insofar as my current level of knowledge allows.
Rgrds,
Ged.

Did you get it repaired?
My service sent mine to the Czech republic, where they sent me a bill of 218€
Luckily it was just a sample, so the didn't do nothing.
I called the service, and they said that they will not repair the device with warranty and that I have to pay..
By the way im from Slovenia, and had some bad experiences with the htc service, so it's just probably here.
They sent the device back home... so now Im stuck -.-

So u no gonna tell i you got it repaired?

Related

Remove Root with Broken Screen (T-Mobile Warranty Replacement)

[ABANDONED] My worries have been aliviated by the people posting here that T-Mobile did not check for an unlocked bootloader. That's enough for me to close the issue. If someone does need to find the answer to this question, feel free to pursue it otherwise I consider this [CLOSED]
-----edit above-----
I've already searched for this EXTENSIVELY and need more help. I have a similar problem to this thread (which wasn't resolved), but didn't want to revive a dead thread from Dec '10 to ask this.
First and most important question is: WILL I NEED TO DO THIS?> Will T-Mobile check for the unlocked bootloader on a broken-screen phone and will they notice my MIUI rom? (I'm REALLY worried about this because rooting my phone does void the warranty, but honestly I didn't break it. The screen just stopped working. Really worried = the search for a solution).
Is HTC warranty a better option? (I'm actually the second owner and the original owner is going to try to do the replacement)
I've realized that I can use Android Screencast to see what the phone is showing, and touch input still works on my phone (though Android Screencast isn't letting me use my computer mouse/keyboard to use my phone). This is only available on a rom/backup with USB debugging enabled, and shows CWM Recovery (using the latest version).
Can someone please help me go through all the steps needed to restore everything to stock? I am cursed by this issue and realize that someone would need to take over an hour to figure all this out.
>>I know I'm asking for a lot, but this is a great community to be involved in and I've searched all over for help before posting.<<
__________________
P.S. I've also looked at [Guide] Remove permanent root, and I need to know what extra steps I will need to know with a broken screen. CWM 3.0+ presents a problem for stock rom, and I need one with USB debugging enabled already.
Also, fyi I used the Rage/Gfree latest version available as of Jan 24 (when I rooted). I did not flash the Engineering HBoot, which would probably help.
What i found was they dont care about the software. confirmed twice. Apparently it is a known defect in the phone that the screen stops working, they will admit it now. We have done 2 warranty replacements and the first one at the time of the post, they tried to charge me for breaking the screen (we did a better business bur Complaint) and got refunded. The second time they didnt even question it and we werent even charged.
So no they dont care, dont worry about it.
I just so happen to have the exact problem as you, i stepped on my phone leavng the screen internally broken put the touch screen still worked. I was running CM7 and i called them and just sent it in with no problems. there not there to look at the software and are not going to take the time to replace screens on all the phones they get in first to see if there rooted or not. If you cant tell its rooted by looking at the screen (i mean it is broken) then theres no way they will. Just send it in and you'll get it in about weeks time
I had this problem and submitted it to warrenty, anyway. They asked me three questions, is the screen cracked. Is there any external damage, and any water damage. All were no's, so they replaced the phone without ever checking for root.
Thanks for all the responses. All three of you have reassured me to the point that I'm not going to worry about it either. While I appreciate that T-Mobile is not going to charge me for rooting my device (which I should be able to do), I am annoyed that as a secondary owner I do not get warranty support and need to have the original owner take care of it.
daboma said:
Thanks for all the responses. All three of you have reassured me to the point that I'm not going to worry about it either. While I appreciate that T-Mobile is not going to charge me for rooting my device (which I should be able to do), I am annoyed that as a secondary owner I do not get warranty support and need to have the original owner take care of it.
Click to expand...
Click to collapse
Actually no, even if you are a second owner u can still get it replaced. I am also a second owner but I know a way to get it replaced. Pm me
Sent from my HTC Vision using Tapatalk

Acer Iconia bricked...Need help

Hello to all good guys in xda-developers forum.
This is my very first post and I really feel desperate and need your kind help.
New Acer iconia with stock firmware 3.2.1 was nicely running this morning until I tried to root the device.It was supposed to be very simple process and not to get into dirty complicated procedures but the gingerbreak.apk did not work as expected so I tried alternative methods.What I read in various forums was that the gingerbreak application is not able to root the new firmwares version so I tried to downgrade the firmware to 3.0.1.
Downloaded the Acer stock recovery firmware EUUs_SBK_Acer_A501_0.017.01_PA_ATT.exe and attempted to flash onto my tablet .I think I did all necessary pre-installation checks.The process started but it stopped on 10 percent for about 30 minutes without any progress.Only Acer logo was displayed and 'entering file downloading mode' at the top of the screen.
After long time no change I finally gave up and unplugged the device from the USB port and restarted but nothing works since then.
1. No vibration on Start
2. Black screen
3. No new USB device appear on my PC
4. No sign of any activity other then power button light
I guess the original firmware was wiped but the new firmware was not flashed...for whatever reason...perhaps the worst scenario.
I will really appreciate If anybody may give me advice how to fix it.
So it turns on but does not display anything? Have you tried to hold the power button and volume down button at the same to when you turn it on to try to get it into recovery. Also there is a little reset button on the side you can try to push.
Sent from my A500 using xda premium
tried all those thinks.All kind of tricks I could find on the net.The problem is that the device is not showing up in the device manager e.g not detected as USB device of an y kind....
acera500 said:
tried all those thinks.All kind of tricks I could find on the net.The problem is that the device is not showing up in the device manager e.g not detected as USB device of an y kind....
Click to expand...
Click to collapse
Try this thread. Look about halfway down, and you'll see almost the exact thing you did, and how this guy got it going.
http://forum.xda-developers.com/showthread.php?t=1291747
Basically you can run a search for APX in the main forum threads and find some other posts, but hopefully this will get you going.
I pulled this from the general forum (eventually), but you can also search the Q&A main forum page as well, and the dev forum.
Another link;
http://forum.xda-developers.com/showthread.php?t=1255519&highlight=apx&page=2
If its new just return it to the store for another one.
Sent from my A500 using xda premium
Acer or the store did not brick it
i THINK If you mess with the rom on your tablet and... BRICK your device .. you should tough it out and fix yourself... Acer or the store is not responsible for this .But then you could also argue that if they had not locked the bootloader this type of bricking would not happen..
So i say go above and beyond to try to fix it from the help on here.. if that fails.. THEN Maybe exchange it.. Its wrong to brake something then expect someone else to foot the bill. Yes im to honest for my own good at times... Acer has also been known to repair .
If you bought a extra warranty all of the above in my book is out the window.. Make them replace it ..
GIGGLES..
Good luck on getting it repaired ..and be more careful next time..
Piece of cake to fix if you kept you USB serial number (from the downgrade tool)???
===== If you have your USB serial number ====================
1. Lets assume you know your USB serial number. If not, then you might be able to get it from your registry.
2. Download my flashing tool at http://forum.xda-developers.com/showpost.php?p=20680452&postcount=137
a. Open up the readme.pdf for the instructions on how to flash
3. KEEP your acer unplugged and run the program
4. The program will install the APX flash drivers and will tell you to plug in the USB. Ignore this step. It will not work. In the instructions skip steps 3, 8, 9, 10.
5. Eventually the flashing tool will timeout because you do NOT have the tablet connected. It will then display a message box telling you how to use a paperclip and the power button to get you into APX mode. THIS IS THE secret to getting the tool to flash your ACER. However, once you get it into APX mode you will need your USB serial number (without it, you are fubar).
a. Plug in the tablet to your computer with the USB and paperclip yourself to fastboot.
6. Now in step 11, enter your USB serial number
7. Now just follow the rest of the instructions.
====== NO USB Serial number ==========
If you do not have your USB serial number than you are going to be out of luck, unless you have ever connected the device to your computer. If you did, then your registry will have a history containing your serial number.
Google usbdeview tool and download it. This will show the serial number of any USB device you've connected to your computer.
===== No Serial number, never connected it, what to do ==========
If you have no serial number and cannot get it, then hopefully you can get to recovery mode (power & volume) and flash using a signed update.zip from ACER. Download one of the update.zip's and put it on your external SDCard and then boot to recovery.
=== Bricked and No serial number, never connected, and you fubar'ed the recovery image ===
If you never connected your table to the USB and your computer to get the USB serial number then you are NOT going to be able to flash it to fix it.
If you fubar'ed the recovery image then you won't be able to get into recovery to run the ACER update zip.
At this point, you can still get your tablet into APX fastboot mode using a paperclip and the power button. But I know of NO way to flash it without the USB serial number and I know noway to get the USB serial number from the APX driver. I've tried and looked at getting the serial number from just APX mode, but I cannot determine how to get it. Someone out there might know.
Hope this helps,
TD
Your CPUID can also be found in the uid.txt file in your cwm backup folder - /mnt/external_sd/clockworkmod/backup/ - just remember to drop the 0x when you need to enter it
erica_renee said:
i THINK If you mess with the rom on your tablet and... BRICK your device .. you should tough it out and fix yourself... Acer or the store is not responsible for this .But then you could also argue that if they had not locked the bootloader this type of bricking would not happen..
So i say go above and beyond to try to fix it from the help on here.. if that fails.. THEN Maybe exchange it.. Its wrong to brake something then expect someone else to foot the bill. Yes im to honest for my own good at times... Acer has also been known to repair .
If you bought a extra warranty all of the above in my book is out the window.. Make them replace it ..
GIGGLES..
Good luck on getting it repaired ..and be more careful next time..
Click to expand...
Click to collapse
Honestly if more people returned bricked phones/tablets etc... they would quit locking them down... the you broke it you fix it because they want to keep people from doing things they should be able to do with THEIR system they bought... In other words I completely don't agree with this at all.. If everything was unlocked and such then I would support the you fix it, but then again we wouldn't be running into these issues now would we. But then again Most people need people to babysit them and tell them what they can and can't do with what they own..
wade7919 said:
Honestly if more people returned bricked phones/tablets etc... they would quit locking them down... the you broke it you fix it because they want to keep people from doing things they should be able to do with THEIR system they bought... In other words I completely don't agree with this at all.. If everything was unlocked and such then I would support the you fix it, but then again we wouldn't be running into these issues now would we. But then again Most people need people to babysit them and tell them what they can and can't do with what they own..
Click to expand...
Click to collapse
@wade7919. You clearly have never worked in IT support on a hardware level.
Or maybe, I am barking up the wrong panty-leg?
If you bought a high dollar corvette, GM will support it. If you add an aftermarket chip, and your engine blows, do you expect GM to fix it? No. I wouldn't expect it either. Not their problem. Just because you can add a chip, doesn't mean you should do it.
That's why they try to lock bootloaders. To prevent users from doing things they shouldn't. Unlock them, and it opens a whole world of issues based on "open source". God help us if they unlock bootloaders.....
Not sure what you are getting at. I am under the belief, if you broke it, you fix it. Take responsibility for one's own actions. Shouldn't take the panzy pussyass way (no offence Erica and werecaltf), and return it for replacement. Suck it up, and learn from experience. Otherwise, the next device, you'll do the same stupid thing again.
I like things the way they are. Difficult, but not impossible. That separates the people with balls (again Erica and wercatlf, no offense), from the sheep.
But if you fubar the device, own up to it, and fix it. Don't pawn it off to somebody else (return it). And if you don't have the brain cells to have a backup plan before you start... Well, don't shed tears over it. Own up, throw the testosterone in the garbage disposal, and fix it.
Somebody give me a zanex...
And people, stop using Gingerbreak!!!!!!
Why locking a bootloader will cost ACER billions
Moscow and wade7919, you both make good arguments.
But it is what point of view you're coming form. If I bought a car and changed the RIM's on all 4 wheels and the engine blew up, would GM refuse to honor the warranty?
However, if I put jet fuel and alcohol in for gasoline and blew the engine why would they honor the warranty?
So, the question here is does rooting a device cause actual damage to the device thereby preventing rooting saves them warranty issues? Or is the device also considered to include the software and is covered under warranty?
I'm not taking sides here, but you both are making very good points but with different examples at different points of view.
So, lets look at other items and see if we can draw a parallel. If I buy a brand new Dell computer and send it in for Warranty and there is nothing wrong with the hardware they charge me (correct?). So if I fubar the OS or load something that caused the damage I pay for it or fix it. If there is actually a hardware failure then they cover it under warranty.
So, why does an Android MFG take the warranty one step further and include the OS and take steps to lock it so you cannot change it? Well, this is because nobody owns the OS (it's open source) therefore they take ownership of the build. Because there's no Microsoft to blame, they lock the software and consider it to be part of the overall device (Apple claimed this in their lawsuit). So, in the MFG's mind, there is no difference from the screen, keyboard, or the firmware & software.
So the question is what do you think should be covered under warranty? Most people think it should be just the hardware like a PC. Others see the whole device which includes the OS.
My point of view:
What follows is my rant and my opinion (you are warned )
In my opinion, I had NO problem until they decided to lock the bootloader. I have no problem with them claiming warranty from A-Z and if I change anything they won't warranty it. No problem, I understand that and accept full responsibility. But by ACER locking the bootloader they went too far.
To me this would be like GM welding the hood shut on my car. Better yet, it would be like me waking up one morning and opening my garage to get in my car and discover that during the night GM welded the hood shut. This, in my opinion, is illegal. Matter of fact, in my opinion, it violates US Federal hacking laws because they enter a system and destroyed data. I eventually think OEM's will get a class action suit filed on them for this.
Secondly, Windows 8 is going to be the game changer. OEM's can now make a hardware device and sit behind only warranting the hardware. You have a problem with the OS, call MS. Also, there is a HUGE (I mean HUGE). Did I mention HUGE, demand for tablets in business. Businesses will NOT put a device that has all these consumer games and social networking loaded into the workforce. There are billions in business applications that can be made, but you cannot sell them if they only run on a tablet that cannot have games removed etc.
Example might help: Medical field <- Think of all the applications a tablet can be used to save costs in hospitals. Do your really want your doctor or nurse etc using this tablet on facebook? Insurance company's, law firms, retailers, traveling sales, etc etc (Government). The list goes on.
Developers will see this huge opportunity and will write applications because they can sell them to A-Z and the business buying them will buy them because they can remove facebook and gmail from their company owned tablets. Now, as more and more developers move to Windows they'll drop Android. Want another example, read about Netflix and the issues they have had supporting a fragmented Android OS. So, business applications will move to Windows, but you might say so what, the consumer market is still there. True, but all you need is one killer application that everyone will want and for that to only be on Windows 8. Want some examples, here's my list, NFL (or sports), Netflix, Skype (gee owned by MS now isn't it?), or something new.
Bottom-line is this, if ACER and the others want to lock their bootloaders then they have just taken themselves out of the game for any business sales. Can you imagine walking into a boardroom showing the Government how your new VA application will save the VA Hospitals millions next year alone and improve veterans healthcare. Your application runs on any HC Android tablet. Everything is smoking, going great, as you hand your tablets, ACER a500', around the room. They are loving it. You just hit 'pay-dirt', then someone says hey I see these ACER's have gmail, facebook, blah blah. We cannot have government employees using tablets with those applications loaded, your installer removes them doesn't it? Silence enters the room, all eyes are focused on you. Your mind see millions escaping which were just within your grasp, you pause, you think, and you say YES General as you grab your Motorola Xoom and say 'that's why we recommend you buy nothing but Motorola.'. ACER just kissed millions in sales goodbye (oh and this is a true story).
i do believe acer should lock the bootloader on there devices.
However thee are things I would be doing with my tab if it were not locked.
Acer should give us the ability to flash the bootloader and not use the proprietary software. Lock that software to there bootloader.for there protections.
Give us a wway to unlock it..AT OUR OWN RISK..
So it should be locked but have a way to unlock it with the end user understanding they are totally on there own ..
I would be OK with voiding my warranty.
@Dean,
"So if I fubar the OS or load something that caused the damage I pay for it or fix it. If there is actually a hardware failure then they cover it under warranty."
Yes, that is true. Bootloaders are locked, to prevent completely stupid idiots, from doing things they absolutely no idea what the sam hell they are doing.
The issue is, should we be able to return a device, after we fubarred it? Against warranty? To say, Hey, your weakness allowed me to do it.
Just because the ability to do it exists, and we can quote a thousand instances, It doesn't mean we should, and to shirk responsibility. And pass it off to the main individual.
The fact is, the policies and regulations are there, and we should abide. And if we don't, we have to own up and deal with it.
And if we don't, then we are no better than the low life of the world. The scum.
Moscow Desire said:
@Dean,
"So if I fubar the OS or load something that caused the damage I pay for it or fix it. If there is actually a hardware failure then they cover it under warranty."
Yes, that is true. Bootloaders are locked, to prevent completely stupid idiots, from doing things they absolutely no idea what the sam hell they are doing.
The issue is, should we be able to return a device, after we fubarred it? Against warranty? To say, Hey, your weakness allowed me to do it.
Just because the ability to do it exists, and we can quote a thousand instances, It doesn't mean we should, and to shirk responsibility. And pass it off to the main individual.
The fact is, the policies and regulations are there, and we should abide. And if we don't, we have to own up and deal with it.
And if we don't, then we are no better than the low life of the world. The scum.
Click to expand...
Click to collapse
Very well put.I do know of a few people who have sent there device to acer after messing it up installing rom and telling acer.acer still fixed it free.
Honesty is always best
The evils of rooting
I'm still missing something here, why locking a bootloader does anything. Go get a Mortorola Xoom (not the FE) and you run the unlock OEM. It tells you that you are unlocking it. It tells you that you unlock it at your own risk. You cannot relock it until it is 100% back to stock. It asks you three times are you sure.
Locking the bootloader and treating everyone as an idiot is the problem. Just do what Motorola does, and stop being everybody's keeper. If they want to 'Police' this then you should have to call ACER and they fax you a form. You give DNA to prove who you are and fax it back. Then you go to a mandatory rooting class, that lasts for 5 days, where ACER preaches to you the sins of rooting. Then you have to take and pass a test. Then and only then, after passing the test you get a certificate. Then you call back, give them your certificate ID. Now they give you the secret key to unlock only your tablet.
That's the ticket,
TD
Bottom-line, it's not that they locked the boatloader, it's that you cannot unlock it. Like I said, go out to your driveway some morning and find that GM welded the hood to your car shut because they think you are stupid and shouldn't be opening the hood. Mind you that YESTERDAY, and at the time your bought it, it was not welded shut. That ladies and gentlemen is what ACER did with their OTA.
Moscow Desire said:
@wade7919. You clearly have never worked in IT support on a hardware level.
Or maybe, I am barking up the wrong panty-leg?
If you bought a high dollar corvette, GM will support it. If you add an aftermarket chip, and your engine blows, do you expect GM to fix it? No. I wouldn't expect it either. Not their problem. Just because you can add a chip, doesn't mean you should do it.
That's why they try to lock bootloaders. To prevent users from doing things they shouldn't. Unlock them, and it opens a whole world of issues based on "open source". God help us if they unlock bootloaders.....
Not sure what you are getting at. I am under the belief, if you broke it, you fix it. Take responsibility for one's own actions. Shouldn't take the panzy pussyass way (no offence Erica and werecaltf), and return it for replacement. Suck it up, and learn from experience. Otherwise, the next device, you'll do the same stupid thing again.
I like things the way they are. Difficult, but not impossible. That separates the people with balls (again Erica and wercatlf, no offense), from the sheep.
But if you fubar the device, own up to it, and fix it. Don't pawn it off to somebody else (return it). And if you don't have the brain cells to have a backup plan before you start... Well, don't shed tears over it. Own up, throw the testosterone in the garbage disposal, and fix it.
Somebody give me a zanex...
And people, stop using Gingerbreak!!!!!!
Click to expand...
Click to collapse
Okay comparing A Tablet or PHone to a car is stupid... Compare it to a Desktop Computer or Laptop... Companies do not lock them down so you can not use different OS's now do they.. They offer Backups to restore the system back to how it was with recovery partitions dont they? or they offer the choice to buy whatever OS you want to install correct? they don't limit you to say just Windows or *NIX do they? But we don't see laptops or desktops locked down to where you can't upgrade your system yourself or anything else... and any dumdass can do that without an issue most of the time. and there is more issues with viruses and crap on computers than phones or tablets...
So before you start making statements like compare this to that learn what to compare to first. If you mess something up on a hardware level sure pay for it.. if you mess something up on a software level because they decided to Babysit people its their fault. and if you think its the persons fault because they decided to open up a PRODUCT that they bought and own then you are one of the people that need babysitting and like everyone telling you what to do and how to do it. Go to an apple product then.
---------- Post added at 07:07 PM ---------- Previous post was at 06:51 PM ----------
Also if you really brick your device you can always give
http://paranoidandroid.us an email to findout about getting it fixed
wade7919 said:
Okay comparing A Tablet or PHone to a car is stupid... Compare it to a Desktop Computer or Laptop... Companies do not lock them down so you can not use different OS's now do they.. They offer Backups to restore the system back to how it was with recovery partitions dont they? or they offer the choice to buy whatever OS you want to install correct? they don't limit you to say just Windows or *NIX do they? But we don't see laptops or desktops locked down to where you can't upgrade your system yourself or anything else... and any dumdass can do that without an issue most of the time. and there is more issues with viruses and crap on computers than phones or tablets...
So before you start making statements like compare this to that learn what to compare to first. If you mess something up on a hardware level sure pay for it.. if you mess something up on a software level because they decided to Babysit people its their fault. and if you think its the persons fault because they decided to open up a PRODUCT that they bought and own then you are one of the people that need babysitting and like everyone telling you what to do and how to do it. Go to an apple product then.
---------- Post added at 07:07 PM ---------- Previous post was at 06:51 PM ----------
Also if you really brick your device you can always give
http://paranoidandroid.us an email to findout about getting it fixed
Click to expand...
Click to collapse
I still like my car comparison
I make the car comparison to illustrate a point, because when I compare tablets to a PC everyone piles on *****ing about MS.
Bottom-line it doesn't matter if it's a blender or a PC. I own it, you own yours and I can do what I want with mine as you can with yours. Now, again I have a BIG(did i mention BIG issue with them changing it on me after I bought it.
To get back on topic, is the original poster still out there?? Has any of this helped? Are you still bricked?? Give us an update so we know if anything worked or you still need help.
The device was returned and accepted for replacement by the shop.Got new one and feel very nervous to start rooting procedure over.I was really lucky that they did not charge me anything but I really want to know what I did wrong so I don't brick my new device again.
I will provide further details soon about my computer OS and firewall settings and perhaps we may figure out what I did wrong.
To all good guys who send me them suggestions and solutions I wanna say big THANK YOU !!!
Your help is really priceless and thrilled me deeply. Will update topic soon
Happy New Yer to all Android fans!!!
So...Back on the subject.
My device was purchased in Japan and its current firmware version is
Acer_A500_7.009.03_AAP_CUS6JP
Q1. Can I flash US or World Wide firmware version on that device.
Q2. Does anybody know the Acer's ftp download server address for Japan
Q3. I think its a good idea to dump my original stock firmware but it seems there is no way doing that prior rooting.So..kinda stuck .any suggestions appreciated.
P.S. I'm thinking about flashing the latest Rooted rom 3.2.1 V3 by timmiDean (thanks for your hard work) I read the instructions very carefully and I think that everything will go smoothly but just in case (considering the specific Japanese firmware version)
would appreciate any further directions by the author.
Thanks

Collection of issues = RMA

Hi all,
Not so much of a Q (or A for that matter), but more for information / evidence purposes.
Had my Nexus 4 for about three days now. Unlocked the bootloader and rooted it.
The last couple of days have seen some peculiar behaviour though which is definitely not right:
- Very very rarely charges as AC. Always USB (always using official charger). This means it takes frickin ages to charge
- The whole thing gets really rather warm. Warmer than you'd expect given its usage. Not just the back but the front as well
- It will charge from USB but now is no longer recognised by any computer (device manager). Used a bunch of different cables.
- It literally hemorrhages battery. Screen on and it's losing 1% every minute (perhaps tied in with the heat)
I haven't dropped it.
Anyway, I phoned up Google support and they've issued a replacement straight away. Not being able to boot into fastboot mode (because of the USB issue) means the bootloader is unlocked. But I can't imagine they'll care really.
I've read that the temperature will affect the charging mode. And perhaps the battery is also affected by this. This definitely seems to be an iffy unit.
I'll report back when the replacement arrives.
Anyone else seen similar issues? I've read a few threads about individual problems but not the whole collection on one device.
RMA process is cool tho. I get to keep the fire brick until the new one arrives. Score.
andyvaughan said:
Not being able to boot into fastboot mode (because of the USB issue) means the bootloader is unlocked. But I can't imagine they'll care really.
Click to expand...
Click to collapse
Where did you get that information? My bootloader is unlocked but fastboot mode works fine; i don't think these are related.
Also, regarding google not caring - i would re-lock the bootloader before you return the device because the process of unlocking specifically states that unlocking the bootloader voids your warranty. Plus its pretty obvious that it is unlocked when it boots up because it shows a little unlock symbol.
Besides, i got the following email from a Google CSR in response to the RMA of my Nexus4:
Please be aware that devices that have been 'rooted', 'unlocked', or modified in a similar manner will have voided their warranty. I understand that you are experiencing device issues and defects, and I only forewarn you due to inconveniences that may arise if your device is found to be modified upon warranty inspection.
Click to expand...
Click to collapse
Still trying to RMA it - i will just unroot it and relock it before shipping.
andyvaughan said:
Hi all,
Had my Nexus 4 for about three days now. Unlocked the bootloader and rooted it.
The last couple of days have seen some peculiar behaviour though which is definitely not right:
- Very very rarely charges as AC. Always USB (always using official charger). This means it takes frickin ages to charge
- The whole thing gets really rather warm. Warmer than you'd expect given its usage. Not just the back but the front as well
- It will charge from USB but now is no longer recognised by any computer (device manager). Used a bunch of different cables.
- It literally hemorrhages battery. Screen on and it's losing 1% every minute (perhaps tied in with the heat)
Click to expand...
Click to collapse
klownkillah said:
Where did you get that information? My bootloader is unlocked but fastboot mode works fine; i don't think these are related.
Also, regarding google not caring - i would re-lock the bootloader before you return the device because the process of unlocking specifically states that unlocking the bootloader voids your warranty. Plus its pretty obvious that it is unlocked when it boots up because it shows a little unlock symbol.
Click to expand...
Click to collapse
Hi andyvaughan
Did you get anywhere with the RMA?
I have the exact same issue: charging only ever happens at USB speeds, never AC - I have tested MANY cables/chargers including original.
@klownkillah - if the OP has the same issue as me then no, it's not related to the bootloader being unlocked. It's simply that the computer DOES NOT recognise phone, neither as media device (MTP) or camera (PTP), nor via ADB while running Android or TWRP, nor via fastboot in the bootloader. Nothing comes up - I have enabled everything, and fastboot and adb worked before and still works correctly with other devices. Not a cable problem. It's only started being an issue at the same time as the charging problem began.
I therefore cannot relock bootloader or flash the stock recovery (as far as I know) before sending it back. I'll be gutted if the warranty doesn't cover this, as it's clearly not a software issue caused by rooting. Must be a hardware issue.
Does anyone have any experience with this, or know of a way to flash back to stock and relock without using a computer?
Thanks in advance.
You should still be able to lock the bootloader even without any USB at all.
Just use BootUnlocker from play store.
Sent from my Nexus 4 using xda app-developers app
Spec-Chum said:
You should still be able to lock the bootloader even without any USB at all.
Just use BootUnlocker from play store.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thanks. That's great.
Now does anyone know if it possible to reflash the stock recovery without computer/USB connection? The bootloader (presumably) won't lock if the stock recovery isn't installed?

[Q] Some doubts with Google RMA Nexus 4 - RED LED issue, Nexus 4 dead.

First than nothing, sorry for my bad english.​
My N4 got bricked, the problem seems to be the battery because when plug in to the AC charger the LED blinks red and nothing else happens, other members have the same problem.
There is few post about it
- http://forum.xda-developers.com/showthread.php?t=2050811
- http://forum.xda-developers.com/showthread.php?t=2011328
- http://forum.xda-developers.com/showthread.php?t=2048066
- http://forum.xda-developers.com/showthread.php?t=2077331
So after try everything my nexus 4 seems to be dead, I decide to RMA but I don't know some details, and maybe you can help me
First, what I think I have to do:
I live out of USA, so I shipped my N4 to my cousin, he was who bought the N4, when he get my N4 then he will do the steps that Google tell him.
My doubt is:
1 - My bootloader is unlocked when my N4 start with the issue, perhaps Google can not turn on the device and be aware of it because the phone is fried, so if they can not detect that the bootloader is unlocked my RMA is free? (Assuming you have the bootloader unlocked means forfeiting RMA)
2- If they detect that my bootloader is unlocked, they will ignore this? Google will send me a replacement device? Although i going to be charged again (Assuming that Google is left with the charge of money they make to your account which remain in hold)
3- The replacement device is now yours? Or is just four use while Google check the original device?
4- How long take the whole process ?
So, this is all my questions by the moment, thank you and sorry for bad english, I used a little bit of Google Traductor.
D3m0x said:
First than nothing, sorry for my bad english.​
My N4 got bricked, the problem seems to be the battery because when plug in to the AC charger the LED blinks red and nothing else happens, other members have the same problem.
There is few post about it
- http://forum.xda-developers.com/showthread.php?t=2050811
- http://forum.xda-developers.com/showthread.php?t=2011328
- http://forum.xda-developers.com/showthread.php?t=2048066
- http://forum.xda-developers.com/showthread.php?t=2077331
So after try everything my nexus 4 seems to be dead, I decide to RMA but I don't know some details, and maybe you can help me
First, what I think I have to do:
I live out of USA, so I shipped my N4 to my cousin, he was who bought the N4, when he get my N4 then he will do the steps that Google tell him.
My doubt is:
1 - My bootloader is unlocked when my N4 start with the issue, perhaps Google can not turn on the device and be aware of it because the phone is fried, so if they can not detect that the bootloader is unlocked my RMA is free? (Assuming you have the bootloader unlocked means forfeiting RMA)
2- If they detect that my bootloader is unlocked, they will ignore this? Google will send me a replacement device? Although i going to be charged again (Assuming that Google is left with the charge of money they make to your account which remain in hold)
3- The replacement device is now yours? Or is just four use while Google check the original device?
4- How long take the whole process ?
So, this is all my questions by the moment, thank you and sorry for bad english, I used a little bit of Google Traductor.
Click to expand...
Click to collapse
1.you have to call google for an rma
2.in my case, the send me a new one, including an envelope and the freightpapers for the old one
3. they authorize 349 euro on your credit card, but they just authorize it,they dont take it
4.if you receive the new device, you have to send the old device back to them within 21 days, otherwise they will take the 349 euros from your credit card
5. pray that they cant turn it on and you are good to go and you dont have to pay for it
6. in betwen 14 days you can keep the new device, dont know how they handle it over 14 days sorry
hope i could clearify some things lol
I live in Germany, had similar problems and doing the rma rightnow, too.
The replacement nexus 4 that you will get is yours. Until they checked your first nexus 4, they block the money for your replacement.
If your warranty isn't valid or the defect isn't covered by the warranty they will charge you for the replacement device.
Let's hope they cannot turn our devices on to check for an open bootloader
pa.pn2 said:
1.you have to call google for an rma
2.in my case, the send me a new one, including an envelope and the freightpapers for the old one
3. they authorize 349 euro on your credit card, but they just authorize it,they dont take it
4.if you receive the new device, you have to send the old device back to them within 21 days, otherwise they will take the 349 euros from your credit card
5. pray that they cant turn it on and you are good to go and you dont have to pay for it
6. in betwen 14 days you can keep the new device, dont know how they handle it over 14 days sorry
hope i could clearify some things lol
Click to expand...
Click to collapse
Qin-Root said:
I live in Germany, had similar problems and doing the rma rightnow, too.
The replacement nexus 4 that you will get is yours. Until they checked your first nexus 4, they block the money for your replacement.
If your warranty isn't valid or the defect isn't covered by the warranty they will charge you for the replacement device.
Let's hope they cannot turn our devices on to check for an open bootloader
Click to expand...
Click to collapse
Thank you guys! Really helped
Lesson learned: After root, ALWAYS block your bootloader
D3m0x said:
Thank you guys! Really helped
Lesson learned: After root, ALWAYS block your bootloader
Click to expand...
Click to collapse
Dont take a chance ! If you didn't send your device yet...
plug it into PC while holding ( VOL - )! JUST VOLUME DOWN ! no POWER KEY !
and when in fastboot mode, do :
Code:
fastboot oem lock
Dont take any chances ! ... They are super genuis ! I guess they can do anything to check the LOCK status !
miku3191 said:
Dont take a chance ! If you didn't send your device yet...
plug it into PC while holding ( VOL - )! JUST VOLUME DOWN ! no POWER KEY !
and when in fastboot mode, do :
Code:
fastboot oem lock
Dont take any chances ! ... They are super genuis ! I guess they can do anything to check the LOCK status !
Click to expand...
Click to collapse
Well bro, my phone its on the way to USA, but when my cousin get it, I'll tell that and lets see what happends...
I had no issues on 1836. I was on it all late last night. It was until I opened that benchmark app that went haywire.
Mentioned this in the other thread as well, but any idea what bin your CPU is?
Hey guys im in the same boat currently doing RMA. I have no red LED phone wont charge or turn on so hoping that Google cant either and Warranty holds.
No idea what bin I am im afraid. I have a hunch its fast or faster as I couldn't run matr1x v4.0 kernel and other people who also couldnt were fast bin (think it was due to the voltage tables).
RED LED fixed
hey guys, i've read a lot of threads about this red led issue and having the only solution was to RMA it.
just remebered the time when i had a RED LED after replacing my framework.apk that i have found in one the forums, after replacing the framework.apk, my phone cant respond to anything (screen touches and even power and volume button was not working) and after a minute my phone turned off. and i cant get it to turn on so i was panicking a bit knowing that i cant RMA my phone cause i only had my phone from my mother in UK and i'm in philippines so i plug my phone on the wall then the LED flashes RED ......
to make the long story short i tried everything to revive my phone and wugfresh's toolkit saved it, after a couple things the toolkit manages to flash the stock rom on my phone i was relieved.
that was just my experience, hope it help you guys
dannaoj said:
hey guys, i've read a lot of threads about this red led issue and having the only solution was to RMA it.
just remebered the time when i had a RED LED after replacing my framework.apk that i have found in one the forums, after replacing the framework.apk, my phone cant respond to anything (screen touches and even power and volume button was not working) and after a minute my phone turned off. and i cant get it to turn on so i was panicking a bit knowing that i cant RMA my phone cause i only had my phone from my mother in UK and i'm in philippines so i plug my phone on the wall then the LED flashes RED ......
to make the long story short i tried everything to revive my phone and wugfresh's toolkit saved it, after a couple things the toolkit manages to flash the stock rom on my phone i was relieved.
that was just my experience, hope it help you guys
Click to expand...
Click to collapse
Exactly what did you do in Wugfresh's toolkit to save it?
reaper000 said:
Exactly what did you do in Wugfresh's toolkit to save it?
Click to expand...
Click to collapse
i used the "flash stock +unroot"
shaded the soft-bricked/boot loop
Sent my device in for RMA over a week ago. Bootloader was unlocked and custom rom loaded. Same red light problem everyone else is having. Also ordered my replacement device which is still on back order.Charges have now cleared my credit card so no worries just in case anyone is worried they will not honor the warranty because you have unlocked and rooted the phone .Called google to find out where my replacement device is yesterday and they said that even the rma devices are on back order for 1 to 2 more weeks which really sucks!
So basically everyone here crashed their car ,it was their own fault, car not had an insurance and you expect to get a new one pretending it was manufacturing fault ?
Sent from my Nexus 4 using xda premium
You make too many assumptions, friend.
1. Not everyone browsing this topic has crashed their phone. I popped in while searching for Wug and toolkit, for instance.
2. It's their own fault: you know what "everyone here" did? Their phone use, their setup?
2a. It may not be manufacturing issue as much as a design flaw. Microsoft's Xbox "circle of death" comes to mind; this could be LG's version of that.
The Nexus line is known as the dev's phones, and devs push limits; that's inherent to development. Even experienced devs like Faux have had red LEDs.
The inability to yank the battery as a hard reset has always troubled me in this kind of environment. I hope Google's next phone corrects this
Sent from my Galaxy Nexus using Tapatalk 2
MattSkeet said:
So basically everyone here crashed their car ,it was their own fault, car not had an insurance and you expect to get a new one pretending it was manufacturing fault ?
Click to expand...
Click to collapse
Mine Nexus got the red led just now, never rooted, everything stock
[Update: after sometime connected to the computer the battery charging icon appeared and it booted]
Update on my RMA process. I noticed today that I have a new pending $299 authorization on my card and I am trying to find out why. The original $299 authorization that was placed on my card when I first started the RMA has now cleared because I had already sent the defective device back for repair and a few days later the pending charge went away. Now I am wondering why in the hell they placed a new $299 charge again even though my replacement device has not even shipped! Google has really dropped the ball on this whole nexus 4 situation!
If you take it apart and actually take the battery out, as a proper hardware reset, will that work? Anyone tried this?
Meleagru said:
If you take it apart and actually take the battery out, as a proper hardware reset, will that work? Anyone tried this?
Click to expand...
Click to collapse
Well, here's a thread that I started that addresses that question directly:
http://forum.xda-developers.com/showthread.php?t=2103451
Here's an update; it seems one brave soul did pull the Nexus 4 battery. Check out this thread : http://forum.xda-developers.com/showthread.php?t=2111947
Sent from my Nexus 4 using Tapatalk 2

[Q] How to ensure a returnable (for replacement) Nexus 7?

Hi guys,
I'm going to leave out the whole story leading up to this (you are welcome to read my past thread about it if you are curious) but basicly, I have a brick of a Nexus 7 that has no external defects at all (babied the hell out of the thing..), but has the 'unlocked' symbol at the google splashscreen, meaning my warrenty is void. Via the past thread, we have determined (and a friend who'se much more android-dev-inclined confirmed) that the flash memory is defective, as it is not not committing changes (no relock possible.) Therefore, my only option now is to open the thing up and see if I can rig it in such a way that the screen does not turn on (at the least), such that I can call in with that as my issue, instead of a brick with an unlocked bootloader as my problem (already did that.) What wires/ circuitry could I tamper with subtly to achieve this purpose?
I know this is a very devious thing to do, but frankly, due to the unlocked status, I have a brick of a tablet that was supposed to help me with reading textbooks in university, and having done everything right (except for unlocking it apparently,) I'm left out cold (and as a student I'm not exactly rich).
Thank you for any help with this.

Categories

Resources