Database Users

[Q] Unable to unlock bootloader. RMA my only option?

As title suggests, my bootloader is locked and my N7 will not boot past the Google logo. If i try Recovery, it says "booting failed" so I can only assume that it was lost/erased. Is an RMA through Asus my only choice at this point?

If you can boot into bootloader mode (which you can) you can use fastboot to flash a stock image. Here is a fine guide. It seems like something on your data and/or recovery partition got corrupted. If you still have a warranty, you should send it to RMA. But it's your choice.

Erovia said:
If you can boot into bootloader mode (which you can) you can use fastboot to flash a stock image. Here is a fine guide. It seems like something on your data and/or recovery partition got corrupted. If you still have a warranty, you should send it to RMA. But it's your choice.
Click to expand...
Click to collapse
I can get to bootloader but I am unable to unlock it. When I try to unlock it, it gives me the prompt, I click YES and then it just goes back to bootloader but still locked.

Well, that's interesting. I don't know what could it be. I guess, RMA is your best option.

engagedtosmile said:
I can get to bootloader but I am unable to unlock it. When I try to unlock it, it gives me the prompt, I click YES and then it just goes back to bootloader but still locked.
Click to expand...
Click to collapse
Hi, engagedtosmile...
This seems to be a common problem... inability to unlock the bootloader... I've come across it a few times, both here on XDA and on other forums.
As I suggested a while ago with this guy who had a similar problem... it could potentially be an eMMC chip gone bad, a corrupted partition structure (very unlikely though, since both his and your Nexus 7 boots and works fine otherwise) or a corrupted bootloader (extremely unlikely, as the Nexus 7 wouldn't boot at all).
As a bit of a last ditch 'clutching-at-straws' suggestion, I advised him to try a different USB port on his PC and/or a different USB cable... my experiences of using fastboot, is that it can be remarkably fussy about such things at times.
Anyway, it appears to have worked for him.
So, it might be worth a shot... change to a different USB port, and/or maybe try a different USB cable.
Good luck... and hope you have as much success as the guy whose post I referenced above.
Rgrds,
Ged.

Question regarding warranty

Hi guys, I recently had the misfortune of getting my Nexus 7 bricked.
Right. So if I claim warranty, how do I go about it? I don't mean the contacting htem and stuff. But what do I say to them to ensure maximum chance of getting the warranty?
I mean, I have voided the warranty by installing custom software on my Nexus. But is there any way I could actually logically persuade them to give me warranty? Or is it just luck? Hoping you get a not-so-smart technician to verify it is suitable for warranty?
Sent from my GT-S5570 using xda app-developers app

nobody_nowhere said:
Hi guys, I recently had the misfortune of getting my Nexus 7 bricked.
Right. So if I claim warranty, how do I go about it? I don't mean the contacting htem and stuff. But what do I say to them to ensure maximum chance of getting the warranty?
I mean, I have voided the warranty by installing custom software on my Nexus. But is there any way I could actually logically persuade them to give me warranty? Or is it just luck? Hoping you get a not-so-smart technician to verify it is suitable for warranty?
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Just call & request an RMA number. If it's truly bricked, they will not be able to ascertain that you installed a custom ROM.

Thank you for that answer but I thought RMAs were for when you returned the device within the first 15days?
And sadly, its obvious that there is a custom rom instAlled. Its hardbricked with an unstoppable bootloop, showing Clockworkmod recovery
Sent from my GT-S5570 using xda app-developers app

What if i do specify some hardware fault that my nexus did have? Like the ghost touch issue. could i get it replaced under that pretext?
Sent from my GT-S5570 using xda app-developers app

Sorry for bumping but I really do need some help. Please?
Sent from my GT-S5570 using xda app-developers app

nobody_nowhere said:
Thank you for that answer but I thought RMAs were for when you returned the device within the first 15days?
And sadly, its obvious that there is a custom rom instAlled. Its hardbricked with an unstoppable bootloop, showing Clockworkmod recovery
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Why do you say that it is hard bricked? It's near impossible to hard brick a Nexus device. If you see the Google logo when the device powers on, you should be able to go into fastboot mode. Then just use fastboot commands to flash TWRP or CWM recovery and then just flash a ROM from recovery.

veeman said:
Why do you say that it is hard bricked? It's near impossible to hard brick a Nexus device. If you see the Google logo when the device powers on, you should be able to go into fastboot mode. Then just use fastboot commands to flash TWRP or CWM recovery and then just flash a ROM from recovery.
Click to expand...
Click to collapse
Yea, it is hard-bricked. As it is stuck in a bootloop involving CWM-Fastboot-CWM------
It's a long story, which is actually in this thread. http://forum.xda-developers.com/showthread.php?t=2468392
The circumstances of my bootloop are eerily similar, right down to the name of rom I flashed. Or it's probably because of that.
I flashed a new ROM (Kaos Droid 7.0.0) and the fitting gapps some minutes ago from CWM Touch. Everything worked as supposed, no errors, no warnings, nothing. Then I rebooted the Nexus 7 and now it's stuck in the worst bootloop I have seen so far:
The Google Screen appears, stays for some seconds, then I see a screen with the CWM Logo and the text "ClockworkmodRecovery 6.0.38", after this the device seems to reboot and the sequence starts from the beginning again.
I can not get into recovery, I can connect to my PC via USB but connection and disconnection happens every few seconds (because of the bootloop).
Click to expand...
Click to collapse
But I'd rather you answered my questions about warranty since this problem seems totally unfixable. It doesn't respond to any keypress I make except for long-press power.

nobody_nowhere said:
Yea, it is hard-bricked. As it is stuck in a bootloop involving CWM-Fastboot-CWM------
It's a long story, which is actually in this thread. http://forum.xda-developers.com/showthread.php?t=2468392
The circumstances of my bootloop are eerily similar, right down to the name of rom I flashed. Or it's probably because of that.
But I'd rather you answered my questions about warranty since this problem seems totally unfixable. It doesn't respond to any keypress I make except for long-press power.
Click to expand...
Click to collapse
Weird. But if it's rather obvious that you voided the warranty, I don't think they'll send you a new one.

That's the problem. The Google logo does appear and technically I'm supposed to be able to use my fastboot commands to undo the issue. But it doesn't work. Since the nexus doesn't respond to a single button press. So I cannot enter fastboot mode proper.
Yea, I knew that. But what if I get it replaced on some other reason than that?
Sent from my GT-S5570 using xda app-developers app

BrianXP7 said:
Did you somehow interrupted a bootloader flash or wrote "fastboot erase bootloader"? If not and the "Google" logo still appears, you really don't need an RMA.
Click to expand...
Click to collapse
No. It's like when you type reboot recovery. It just goes directly into cwm. And then it reboots and again. And again.
https://dl.dropboxusercontent.com/u/12668781/Nexus7_bootloop.mkv

BrianXP7 said:
Since you can't access MTP, you can try ADB Sideload. (It's a feature in later versions of ClockworkMod Recovery and Team Win Recovery. Why are you still using CWM by the way?) It'll transfer the flashable ZIP to the root of /sdcard and it'll flash immediately after.
RMAs should be only used for last resort bootloader bricks if you don't have access to the proprietary blobs. Luckily, you're fine.
Click to expand...
Click to collapse
Mate, my nexus does not respond in any way to the keypresses I make. So I cannot access clockworkmod, or fastboot mode, or even try to force a regular boot. It just bootloops on and on, completely unimpressed by my presses

BrianXP7 said:
Oh, my mistake. I didn't see your video. Sorry about that. (Bootlooping might be incorrect terminology for recovery. I'm not sure.) Try reflashing another recovery image like TWRP instead? That's the best I can give you for now.
Click to expand...
Click to collapse
Okay, I love that you're atleast trying to help. But the point is I literally have no way of flashing anything on it. I cannot do anything to it, bro. Whatever I do it just keeps bootlooping on and on. If I could access fastboot, I could easily fix this problem but I can't so.
I'd love your feedback concerning what I should do with regards to warranty

BrianXP7 said:
Again, it's not a bootloader brick. You don't need an RMA. In the video, you simply left it booting normally (then falling back to recovery). Also, it's not recovery's issue. It's probably the internal ROM that's made unbootable by some kind of OTA update.
To enter Fastboot mode, turn off your device completely. After, hold Power + Volume Down. Release Power (keep holding Volume Down) when "Google" displays. If done successfully, it'll display an Android lying down. That's Fastboot mode.
Unless you somehow damaged your hardware keys, you might be completely screwed. In order for your RMA to be accepted, you need to remove any trace of modification and relocking the bootloader. If you did restore it to an RMA acceptable state, it's already usable. (Screwing with the bootloader completely, or APX mode, will be accepted as they can't detect if you unlocked the bootloader or not.)
Click to expand...
Click to collapse
hmmmm. Is there a way of completely disabling the bootloader or something?

BrianXP7 said:
Yes, but you need access to Fastboot. If you did have access Fastboot, might as well fix it yourself. Basically, you flashed an incorrect bootloader image or interrupt the writing process. (Just don't think about it unless you have a bootloader backup.)
Click to expand...
Click to collapse
Okay, Can you do something for me?
Type su and then reboot recovery on the terminal.
Now when the Google Image is shown in the beginning, can you try to put it in Fastboot mode instead? Power + Volume Down, like you said.
Tell me if it works

BrianXP7 said:
What? I think you're over-complicating things. You don't even seem to try.
Just turn your device off. (Forced, normally, however you want.) Hold Power + Volume Down until "Google" appears. (That's when you release the power button but keep holding Volume Down.) If you see an Android laying down with a few options such as "Reboot normally", you're in Fastboot mode.
After that, just flash the stock factory images. It's as simple as that.
Click to expand...
Click to collapse
Did you try to do that for me?
I need You to do that for me. And tell me if it works. My Nexus 7 simply cannot be saved. Whatever I do, It doesn't respond. I know all about Fastboot mode, and recovery mode, and flashing factory images. I'm not a n00b like you seem to think. I do have a problem, but it seems to have been caused by random hardware fault rather than a fault on my part. But the result is the same.

nobody_nowhere said:
Did you try to do that for me?
I need You to do that for me. And tell me if it works. My Nexus 7 simply cannot be saved. Whatever I do, It doesn't respond. I know all about Fastboot mode, and recovery mode, and flashing factory images. I'm not a n00b like you seem to think. I do have a problem, but it seems to have been caused by random hardware fault rather than a fault on my part. But the result is the same.
Click to expand...
Click to collapse
@GedBlake;, you're the only person who understood my problem and tried to help me before. Could you perhaps do the same again?

nobody_nowhere said:
@GedBlake;, you're the only person who understood my problem and tried to help me before. Could you perhaps do the same again?
Click to expand...
Click to collapse
Hi, nobody_nowhere..
I will try, but I'm not quite what it is you're asking of me...
If it's concerning RMA, then I don't think I'm going to be of much help, I'm afraid... as I don't know the procedure for claiming under warranty (ie., RMA), having never done it myself.
My own Nexus 7 is just a liitle over a year old now, and I've so far been fortunate in having only had minor, and easily recoverable softbrick/bootloop type situations.
In your second post on this thread, you suggest that RMAs were time limited to just 15 days. I'm not completely sure, but I think this is incorrect. In most countries/jurisdictions, warranties usually run for 12 months. This is certainly the case here in the UK.
The thread you mention, well, having read it yourself, you'll know that I attempted to resolve the problem experienced by the OP of that thread... and it all came to nothing in the end.
There seems to be two recognisable categories of 'brick'... hardbrick, typically caused by a damaged, corrupt or wholly erased bootloader... and softbrick, which can have any number of causes, but is usually always resolvable - principally by accessing fastboot mode. Fastboot mode, is a sort of a 'get-out-of-jail' free card... and I've used it many times in the past.
But if you can't access fastboot mode (apropos of your current predicament), but the bootloader still works (if it didn't, NOTHING AT ALL would happen), your technically not hardbricked.
You have an unrecoverable soft brick... semi-hardbrick maybe? - a third category of 'brick'??
With regard to claiming under warranty... as I've already said, I really have no idea how to go about doing this, but I assume some sort of 'phone conversation would initially start the ball rolling and some questions would be asked of the owner of the Nexus 7...
...but, if it is unambiguously clear (and it sounds like it is, with CWM boot looping), that you've installed custom software, then there's no point in being disingenuous. As soon as they receive the device, they'll know. It you're honest with them, you might have a fair chance of them fixing it. If you lie outrightly, your credibility suffers.
Your best bet, I think, is to emphasize that's it's a hardware issue - emphasize the buttons aren't working properly. Emphasize that you're a knowledgeable Android user, and you're familiar with fastboot, and flashing custom software. The idea, here, is to make it more of a hardware problem, than a software problem - because it then throws the ball back into their court. And personally, I happen to think it is a hardware problem. I have no idea if this will work or not - I'm really just guessing here.
Whether installing custom software itself is sufficient to void warranty is a discussion that could fill an entire thread many pages over, such is the ambiguity of the issue.
It's generally considered, though, that unlocking the bootloader alone, is enough to leave your warranty in tatters... but flashing a Google factory stock image requires the bootloader to be unlocked anyway. So, I'm not quite sure how that contradiction squares itself away!
Indeed the flash-all.* script, that ships with factory stock images, unlocks the bootloader as matter of course. Of course, Google recommend re-locking the bootloader afterwards.
And what of Nexus 7 Jellybean 4.2.2 users, several months ago, who could root without unlocking the bootloader at all, using the motochopper "exploit".
Does rooting with an exploit count as installing custom software... you're messing with /system after all?
Ultimately though, I think that you may have to face an unpalatable truth - that tinkering with your device, does sometimes go wrong... in ways that leave even the most experienced users baffled (and I'm not even close to that level of knowledge and expertise).
There are some posters, here on XDA, who have in their sig., a list of previously owned devices... crossed out... and the word BRICKED next to them. These are the guys with thousands of posts to their name... and their 'graveyard' of dead devices are their metaphorical battlescars.
As soon as you type fastboot oem unlock, you're tacitly accepting that this may happen to you some day... you've effectively 'removed the back' of of that expensive clock/watch/HiFi system or Nexus 7... in the belief you can make it 'go' faster or perform better. Most of the time, you will be successful, and you will make it perform better, with whatever Custom ROM or kernel you've chosen to install.
But sometimes, something will go so horribly wrong... that there is no way back.
And all that is then left is the capriciousness of the company you have warranty with (via RMA)... and you're own negotiating skills.
I really do wish there was some button sequence, or command line I could suggest... but when dealing with the warranty people... you're on your own, sorry to say. Ultimately, and essentially... they may choose to repair it, or not. And beyond that, there's not much else I can add.
Except... best of luck.
Rgrds,
Ged.

[Q] Flash Bootloader Failed， Why？

Still got this problem when flashing
nakasi-kot49h-factory-5e9db5e1
Click to expand...
Click to collapse
Last time I met this error was JWR66Y, after replace bootloader-grouper-4.23.img from JWR66V it fixed.
Now this error comes again, also, after times of flashing, I replaced bootloader again and avoided this error.
SO, Why this happen? what happened to the bootlaoder file with the same version number 4.2.3 ??
dose anyone know?

What is the error? Just failed? I assume youre using fastboot to flash the image, what's the output from terminal/cmd
Sent from my Nexus 7 using XDA Premium 4 mobile app

VolantBear said:
Still got this problem when flashing
Last time I met this error was JWR66Y, after replace bootloader-grouper-4.23.img from JWR66V it fixed.
Now this error comes again, also, after times of flashing, I replaced bootloader again and avoided this error.
SO, Why this happen? what happened to the bootlaoder file with the same version number 4.2.3 ??
dose anyone know?
Click to expand...
Click to collapse
Hi, VolantBear...
Take a look here...
http://forum.xda-developers.com/showthread.php?p=48416337#post48416337
It's getting to the point now where the factory images can no longer be trusted... particularly when it comes to flashing bootloaders, which is a risky procedure at the best of times.
If Google don't get their act together on this and sort out the mess soon, it's only a matter of time, I think, before somebody winds up permanently hard bricking their device.
Rgrds,
Ged.

look at the post up here by GedBlake and the post quoted there, you will know what happens.
wish this mistake would not coming in the future.
demkantor said:
What is the error? Just failed? I assume youre using fastboot to flash the image, what's the output from terminal/cmd
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse

Yes, that's the problem I wanna know. thx very much for informing this.
I wonder if I crashed my device when flashing a factory image by Google, will I get a new one for free?
GedBlake said:
Hi, VolantBear...
Take a look here...
http://forum.xda-developers.com/showthread.php?p=48416337#post48416337
It's getting to the point now where the factory images can no longer be trusted... particularly when it comes to flashing bootloaders, which is a risky procedure at the best of times.
If Google don't get their act together on this and sort out the mess soon, it's only a matter of time, I think, before somebody winds up permanently hard bricking their device.
Rgrds,
Ged.
Click to expand...
Click to collapse

Nexus 10 does not boot

Hi,
I'm having an issue with my nexus 10.
I unlocked the fastboot loader from it with fastboot oem unlock.
But I think I bricked it.
But I don't know what I did wrong.
Everything went according to the description.
But it does not start
Even with the other tip that I found about starting the recovery modes does not work as well.
Please help, don't want to have an brick
OS: Nexus 10 Android 4.4.4
It started bevor without any issues.

Can you start it to bootloader? If yes you could flash a custom recovery or the firmware

dracoVanDragon said:
Hi,
I'm having an issue with my nexus 10.
I unlocked the fastboot loader from it with fastboot oem unlock.
But I think I bricked it.
But I don't know what I did wrong.
Everything went according to the description.
But it does not start
Even with the other tip that I found about starting the recovery modes does not work as well.
Please help, don't want to have an brick
OS: Nexus 10 Android 4.4.4
It started bevor without any issues.
Click to expand...
Click to collapse
If nothing else works, there are JTAG services (I'm guessing here since I have only really heard of people doing this with their phones but I suspect that it can be done with the Nexus 10).

captican said:
If nothing else works, there are JTAG services (I'm guessing here since I have only really heard of people doing this with their phones but I suspect that it can be done with the Nexus 10).
Click to expand...
Click to collapse
Nah. That won't really do anything since that's really only for devices with radios (like cell phones). For example, if you wipe your EFS partition on a Nexus 5 by accident, and you don't have a backup, you're screwed. The only way would be to send it in or go to a shady place that would fix it for you.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 07:12 PM ---------- Previous post was at 07:11 PM ----------
dracoVanDragon said:
Hi,
I'm having an issue with my nexus 10.
I unlocked the fastboot loader from it with fastboot oem unlock.
But I think I bricked it.
But I don't know what I did wrong.
Everything went according to the description.
But it does not start
Even with the other tip that I found about starting the recovery modes does not work as well.
Please help, don't want to have an brick
OS: Nexus 10 Android 4.4.4
It started bevor without any issues.
Click to expand...
Click to collapse
What happens when you try to boot into recovery from the bootloader?
Sent from my Nexus 5 using Tapatalk

There is an adb command to wipe the device you need to do that when you unlock the boot loader for the first time iirc.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Bounty of $200 if someone can unbrick - hardbricked Nexus7

I have erased my bootloader - fastboot erase bootloader.
I am ready to give $200 if someone can give me procedure to bring it up again.
i can share CPUID as generated by NVFlash, thats all I have.
So if someone looking for quick $200, here is your chance..

Well I don't want your money, I would suggest wugfresh myself. Has the option for a bricked device. Has saved a lot of people. And I have no idea why you did that.

raviverma said:
I have erased my bootloader - fastboot erase bootloader.
I am ready to give $200 if someone can give me procedure to bring it up again.
i can share CPUID as generated by NVFlash, thats all I have.
So if someone looking for quick $200, here is your chance..
Click to expand...
Click to collapse
You can buy a Nexus 7 for less than $200 I own one myself paid £200 in 2012 and must admit they are ****e and Google must be held accountable for releasing a device which is always in beta

treefrog20012003 said:
Well I don't want your money, I would suggest wugfresh myself. Has the option for a bricked device. Has saved a lot of people. And I have no idea why you did that.
Click to expand...
Click to collapse
i updated lollipop on nexus 10 and then while doing on nexus 7, by mistake i did
fastboot erase bootloader
fastboot reboot bootloader
without
fastboot flash bootloader bootloader.img
i have done flashing several times, but this was my bad day. I have no blobs or other data saved as i never anticipated this will happen. I tried hard so far but could not bring up with NVFlash, so finally i thought if someone can do it definitely deserves the prise money of cost of the TAB.

raviverma said:
i updated lollipop on nexus 10 and then while doing on nexus 7, by mistake i did
fastboot erase bootloader
fastboot reboot bootloader
without
fastboot flash bootloader bootloader.img
i have done flashing several times, but this was my bad day. I have no blobs or other data saved as i never anticipated this will happen. I tried hard so far but could not bring up with NVFlash, so finally i thought if someone can do it definitely deserves the prise money of cost of the TAB.
Click to expand...
Click to collapse
ok have you tried the wugfresh nexus root toolkit it does the job

Tmzdroid said:
ok have you tried the wugfresh nexus root toolkit it does the job
Click to expand...
Click to collapse
I had tried that too.. it keeps looking for ADB, when there is no ADB.
I have the root tool kit installed. Please correct me if i am doing something wrong.
As i said, there is no bootloader so no fastboot either, only APX mode as of now.

Wugfresh has an option for bricked devices, I figured that would do it
Sent from my DROID3 using XDA Free mobile app

Do you mind uploading the screenshot with the button marked, if at all you can.
I cannt find any way for - unbriking on toolkit.

Its under a sub screen, advanced options I think. I would give you a screen shot but i'm not home and won't be for hours.
Sent from my DROID3 using XDA Free mobile app
---------- Post added at 11:29 AM ---------- Previous post was at 11:23 AM ----------
Go to YouTube and search for unbrick nexus 7, there are a lot of vids there, one should help.
Sent from my DROID3 using XDA Free mobile app

You know you can buy nexus 7 2012 model on ebay for around 100.00
you can buy a new Main board for around 35.00 ...And people on here will help you for free . Just ask.. If you did not do the pre boot-loader unbrick procedure you are totally lost .
NV-FLASH Is your only hope to revive without hardware Replacement. From the best of my knowledge anyway...
Sorry...

Thats right I dont have any per data saved.
NVFlash too wont work without blob.bin which is device specific.
I know people on xda help just for good of people but i wanted to reward since I have tried hard enough already with NVFlash.
If at all someone can bring it up deserves a good reasonable amount
Thank you and I am greatful.

After some extensive searching I'm going with your hosed. 2 options, buy a new main board or buy another one. Sorry about your situation, should you find a magical answer let us know.

New mb. There might be a way to reload the os through JTAG, which I think is how it is done at the factory, but it would cost more than just replacing it.

Yup looks like its time to say good bye to bricked Nexus7 and buy a replacement new Tab.
Thank you friends for all your help and time. Looks like its time to close the bounty as incomplete project.

I did a quick search on eBay and found a person offering JTAG services
http://www.ebay.com/usr/patrickwalls?_trksid=p2047675.l2559
Maybe you could talk to the guy.

Thank you ! I have contacted the guy you mentioned. Lets see what reply we get !

The nexus has a UART interface in the headphone jack. Not sure what UART can be but maybe can be used to comunicate at a low level with the board and flash a bootloader.

For less than $100 you can get another one on swappa.
http://swappa.com/buy/nexus-7-wifi/us

http://www.amazon.com/gp/product/B0...e=UTF8&camp=1789&creative=390957&linkCode=as2
USD$120 refurbished, fullfilled by amazon

Yes I have heard Nexus7 Serial interface through Audio Jack. I will try it. I think i have one audio serial interface cable.
All this exercise is becoming a collective hacking of Nexu7.
I did HEX Diff of two Blob.bin generated by flatline.img and found there is
- a common header and footer
- in between there is around 2MB of AES encrypted data.