As long as you can get into fastboot mode, you haven't bricked your device
Click to expand...
Click to collapse
Is this statement true?
I know it isn't impossible to brick your device to the point of no return. I've actually done it myself (huray!) with my Nexus S. It was declared dead even by AdamOutler himself, the maker of the Unbrickable Resurrector. After trying to unbrick it myself, I sent it to him. Apparently I screwed up the radio, a mistake which is impossible to recover from. Don't ask me how I did it... I did flash something before, but my phone worked fine for a while. Only then the battery drained really quickly. When it was dead and I plugged in the charger, it booted up fine, but the moment I started the browser my Nexus S died. Forever. RIP.
I guess it's no different with the N4. If you screw up the radio, you have a problem. Can somebody confirm this? And are there other ways to brick your phone to the point of no return?
I think it's kind of stupid that you are able to brick your phone. You can't brick a PC, can you? That's just impossible. You can ALWAYS completely reset everything. Well, not with Android apparently. I think it's weird that even with Nexus devices, there's still a way to brick it. I guess you need to be stupid like me to brick a Nexus device, but still... it shouldn't be possible.
Yes as long as bootloader mode is able to be started! You cannot brick. Just flash google stock factory images.
Sent from my Nexus 4 using xda premium
Its because Android phones are dependant on the Bootloader, whereas a PC is dependant on the BIOS and CMOS. If you fail at flashing a BIOS then you brick the motherboard. So you technically can brick a PC.
Hah, I've bricked PC's with BIOS flash fails.
But as for the phone, as long as you can enter fastboot, you are able to recover.
Harry GT-S5830 said:
Its because Android phones are dependant on the Bootloader, whereas a PC is dependant on the BIOS and CMOS. If you fail at flashing a BIOS then you brick the motherboard. So you technically can brick a PC.
Click to expand...
Click to collapse
You can? Ah, then I rest my case.
I did screw up the radio though, and not the bootloader. I was able to get into download mode using the resurrector tool, only the screen stayed black.\
by the way, I don't think the Bootloader is the same as the BIOS. If it was, then you would technically be able to flash anything on your phone, even Windows. It isn't split up like the BIOS and Windows. Correct me if I'm talking nonesense by the way ;p.
You could think of it as the bootloader = the BIOS and Android = Windows
Androyed said:
[snip]
by the way, I don't think the Bootloader is the same as the BIOS. If it was, then you would technically be able to flash anything on your phone, even Windows. It isn't split up like the BIOS and Windows. Correct me if I'm talking nonesense by the way ;p.
Click to expand...
Click to collapse
You technically could flash anything on your phone, assuming you had the right bootloader and partition table and the right drivers. The issue is that the bootloader on an Android device is designed to boot (i.e., load into RAM ) a Linux kernel. It isn't designed to (and hence, won't) boot a Windows, or any other, kernel.
You could always delete your bootloader, thall brick your device pretty fast
efrant said:
You technically could flash anything on your phone, assuming you had the right bootloader and partition table and the right drivers. The issue is that the bootloader on an Android device is designed to boot (i.e., load into RAM ) a Linux kernel. It isn't designed to (and hence, won't) boot a Windows, or any other, kernel.
Click to expand...
Click to collapse
Very true. For an example, Check out the HD2 phone and the various bootloaders available for it. I have booted Windows Mobile 6 and 7, Ubuntu, oh.. and Android on it. It was originally a WM6 phone. It also has the ability to change partition sizes, and has an sBoot partition so it can do a true dual boot. One from Nand memory and one from SD card with just a reboot.
I waiting to see if we get a way to flash unsigned bootloaders on Nexus 4 (or get a key).
I seem to recall a few devices being bricked in the few days after release. There was a problem with the faux kernel that caused the device to totally and irreparably brick if one overclocked (to 1.8Ghz I think) and then ran an antutu benchmark.
The few could not recover from the brick despite a lot of suggestions thrown around and some even from the dev of the kernel. Ultimately, they RMA'd.
Have a look at this thread: http://forum.xda-developers.com/showthread.php?t=2011328
Many users seen to have bricked their devices by overclocking their CPUs and running benchmarks.
Heck, I even see people talking about the red LED problem daily. Something's clearly not right...
Sent from my Nexus 4 using Tapatalk 2
The red led problem clearly appears too frequently... it really has to be cleared up what the heck is causing it.
Lownita said:
The red led problem clearly appears too frequently... it really has to be cleared up what the heck is causing it.
Click to expand...
Click to collapse
The red led bug is most likely hardware related.
Just think about it. Overclocking draws significantly more power. The nexus 4 isn't even able to supply the power for USB host, so it might be some kind of power failure.
Or simply a shorted circuit.
Nuu~ said:
The red led bug is most likely hardware related.
Just think about it. Overclocking draws significantly more power. The nexus 4 isn't even able to supply the power for USB host, so it might be some kind of power failure.
Or simply a shorted circuit.
Click to expand...
Click to collapse
There is the point.
Bricking by software alone will be almost impossible. I have seen a few flashing bricks recovered already.
Bricking by damaging the hardware, well, that is probably unrecoverable. Over Clocking or O/C + Over-Heat is causing what seems to be permanent damage in some phones.
fastboot mode on nexus 4 says "secure boot: on" --- anyone knows what that means? afair i havent seen that on my old gnex and nex7.
and is it possible to use download mode to flash a new bootloader in case the old one is corrupted?
I don't think anyone has the QCOM_USB_DLD mode figure out yet and I don't think anyone knows what secure boot does either, I know originally people blamed it for custom recoveries being reverted, but that's just a script that's called on bootup.
molesarecoming said:
fastboot mode on nexus 4 says "secure boot: on" --- anyone knows what that means? afair i havent seen that on my old gnex and nex7.
and is it possible to use download mode to flash a new bootloader in case the old one is corrupted?
Click to expand...
Click to collapse
I've seen that on my Nexus S... after I had bricked it completely ;p. I don't think it had anything to do with the brick though. It's something from HTC devices: http://www.addictivetips.com/mobile...on-htc-android-phones-with-unrevoked-forever/. At least I think so.
When I tried to repair my bricked Nexus S, I asked if it had something to do with secure: on. They didn't know what it was exactly, so maybe it isn't the same as s-on on HTC devices.
molesarecoming said:
fastboot mode on nexus 4 says "secure boot: on" --- anyone knows what that means? afair i havent seen that on my old gnex and nex7.
Click to expand...
Click to collapse
Pure speculation on my part: I think that the "secure boot: on" relates to the boot chain of the Snapdragon SoC. When it's on, I think that it will not boot an unsigned bootloader, and hence you cannot boot the device. Similar to, but not quite the same as, S-ON for HTC devices as was mentioned above.
molesarecoming said:
and is it possible to use download mode to flash a new bootloader in case the old one is corrupted?
Click to expand...
Click to collapse
More speculation: I haven't had much time to look into it yet, but I'm guessing that you should be able to flash a .tot file (an LG "factory image" I think like the ones found here) while you are in download mode. I think it requires something like the LGNPST tool with the right .dll. This is my first LG device (and my first Snapdragon SoC), so I'm still in the reading/learning stages.
Related
hi guys ...i hav some big problem n i really need ur help pls.
i hav tried to root my xoom but it failed n now im afraid i hav bricked my xoom
- unlock ok
- fastboot flash boot boot.img ok
- fastboot reboot fail ( dual core technology frozen)
the only thing that it shows is the dual core technology screen nothing more and when i reset it it starts alone by itself again and stock
i hav a motorola xoom 3g titan i guess before i try to root it was 3.0.1 or may be 3.1
but i never try to use a sd card so i dont know if it works
while trying to fix it i wipe the factory, cache but still bricked
best regards
daddymaths said:
hi guys ...i hav some big problem n i really need ur help pls.
i hav tried to root my xoom but it failed n now im afraid i hav bricked my xoom
- unlock ok
- fastboot flash boot boot.img ok
- fastboot reboot fail ( dual core technology frozen)
the only thing that it shows is the dual core technology screen nothing more and when i reset it it starts alone by itself again and stock
i hav a motorola xoom 3g titan i guess before i try to root it was 3.0.1 or may be 3.1
but i never try to use a sd card so i dont know if it works
while trying to fix it i wipe the factory, cache but still bricked
best regards
Click to expand...
Click to collapse
The sd card should not be an issue since you use your computer connected to the Xoom with adb/fastboot when rooting.
Which rooting guide are you using? It does matter, especially for 3G non-US models.
I'm sure you are not bricked. You will need to start again but make sure you have all of the correct files in you platform tools folder (or whatever folder you are using for adb).
If you have successfully unlocked you can skip that step.
You are frozen at the dual core screen because you have flashed an incorrect boot.img for your specific model of xoom, and the android version you have on your xoom a.k.a 3.0-3.2. Since you are on the 3g version make sure you get a 3g boot.img and might as well get both the 3.1 and 3.0.1 boot.Hold the power button and the volume up button at the same time to reboot, wait 3 seconds,and then press only the the volume up button. you should now have a message at the top that says starting fastboot protocol support. begin flashing the images.
rootfan said:
You are frozen at the dual core screen because you have flashed an incorrect boot.img for your specific model of xoom, and the android version you have on your xoom a.k.a 3.0-3.2. Since you are on the 3g version make sure you get a 3g boot.img and might as well get both the 3.1 and 3.0.1 boot.Hold the power button and the volume up button at the same time to reboot, wait 3 seconds,and then press only the the volume up button. you should now have a message at the top that says starting fastboot protocol support. begin flashing the images.
Click to expand...
Click to collapse
Ditto, you will know for sure whenu brick when your screen is black only. You have a little work to do as notedbut stay calm.. You will get things fixed.
rockhumper said:
Ditto, you will know for sure whenu brick when your screen is black only. You have a little work to do as notedbut stay calm.. You will get things fixed.
Click to expand...
Click to collapse
+1 dont jump the gun and read everything over 5x before moving forward... Its a lil work like said but you will probably be more knowledgeable after its all said and done and be able to help others that may be stuck like you one day..
Good luck
Hey guys... I have bricked my xoom too. It's a wifi only xoom. I missed the last step in the guide I was using "fastboot oen lock" and rebooted... so now it stays on the dual core screen. I tried vol up and power buttons to get fastboot and it stays on the starting fastboot protocol... the computer doesn't recognize it. Just don't know what to do next...
Please help...!
Sent from my T959 using XDA App
rickyx said:
Hey guys... I have bricked my xoom too. It's a wifi only xoom. I missed the last step in the guide I was using "fastboot oen lock" and rebooted... so now it stays on the dual core screen. I tried vol up and power buttons to get fastboot and it stays on the starting fastboot protocol... the computer doesn't recognize it. Just don't know what to do next...
Please help...!
Sent from my T959 using XDA App
Click to expand...
Click to collapse
Read the sticky on page one... That says a guide to all your rooting needs... Proceed
This is what scares people
Don't freak out if your xoom won't boot. Your xooms are certainly not nowhere near bricked. >.>
Kippui said:
This is what scares people
Don't freak out if your xoom won't boot. Your xooms are certainly not nowhere near bricked. >.>
Click to expand...
Click to collapse
The word "bricked" gets way too much use... 95% of folks saying they bricked are no where near it...
rockhumper said:
The word "bricked" gets way too much use... 95% of folks saying they bricked are no where near it...
Click to expand...
Click to collapse
I have only seen one bricked xoom so far.
Sent from my PG86100 using Tapatalk
bwcorvus said:
I have only seen one bricked xoom so far.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Dont you know that 50 percent of all statistics are made up? And thats 99 percent of the time
thx guys
i was unfortunately little bit busy with work and exams ....i m relieve ..i will try to follow ur advices and keep u in touch.
thx a lot.
best regards
daddymaths
Is your Xoom still "bricked?" If so, shoot me a PM and I'll help you out. I HIGHLY doubt it is truly bricked.
rooting guide?
okantomi said:
The sd card should not be an issue since you use your computer connected to the Xoom with adb/fastboot when rooting.
Which rooting guide are you using? It does matter, especially for 3G non-US models.
I'm sure you are not bricked. You will need to start again but make sure you have all of the correct files in you platform tools folder (or whatever folder you are using for adb).
If you have successfully unlocked you can skip that step.
Click to expand...
Click to collapse
i have as i say a 3G motorola titan ....could anyone provides me the right routing files ? thx
I have a completely and 100% bricked Xoom. Was in the rooting process, and did something wrong, but the device is totally dead.
No response when plugging in via USB, although white LED illuminates when the power is plugged in.
cdinoz said:
I have a completely and 100% bricked Xoom. Was in the rooting process, and did something wrong, but the device is totally dead.
No response when plugging in via USB, although white LED illuminates when the power is plugged in.
Click to expand...
Click to collapse
Hit power and volume up to reboot...there is nothing the root process can do to brick it. Stop by the irc channel.
Sent from my PG86100 using Tapatalk
Have tried that.... Is still dead, and get no response from the device. Apparently I may have totally wiped the NAND storage....?
cdinoz said:
Have tried that.... Is still dead, and get no response from the device. Apparently I may have totally wiped the NAND storage....?
Click to expand...
Click to collapse
What exactly did you do (or try to do)?
okantomi said:
What exactly did you do (or try to do)?
Click to expand...
Click to collapse
I tried to root the device and install the Tiamat kernel. I was enabling the micro SD slot (or so I thought) and when I dropped in my SD card, there was a warning that the device needed to be re-partitioned. So I did. Didnt format the microSD, seems to have formatted the entire device.
Related to this issue:
http://forum.xda-developers.com/showthread.php?p=14462676#post14462676
cdinoz said:
I tried to root the device and install the Tiamat kernel. I was enabling the micro SD slot (or so I thought) and when I dropped in my SD card, there was a warning that the device needed to be re-partitioned. So I did. Didnt format the microSD, seems to have formatted the entire device.
Related to this issue:
http://forum.xda-developers.com/showthread.php?p=14462676#post14462676
Click to expand...
Click to collapse
That's one of the only two ways to brick it. I would stop by the irc channel, but I think you may have actually bricked it.
Sent from my PG86100 using Tapatalk
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.
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.
So I apologize in advance, I am a n00b to rooting android devices.
Long story short, I think I hard bricked my TF300T.
I had followed some rooting guides (from other sites ) and yup, I'm stuck at the Asus logo with the "unlock" message in the corner.
I can't get into fastboot or anything else by holding Volume Down + Power, all I can get is my computer to recognize it as an APX device.
At one point previously, it almost bricked and froze at the same spot, but I somehow played with different reset combinations and it came alive again. Is there any reset combinations that worked for anyone?
Also, I remember doing a system backup within the device. Is there any way to access that, or is it gone?
In other words, do I need to buy a new motherboard? Or is there a remote possibility I can fix it?
One last layman question: why is it I can't just read and write to the device's internal memory, regardless of its status?
-Cannon Fodder
Cannon Fodder said:
So I apologize in advance, I am a n00b to rooting android devices.
Long story short, I think I hard bricked my TF300T.
I had followed some rooting guides (from other sites ) and yup, I'm stuck at the Asus logo with the "unlock" message in the corner.
I can't get into fastboot or anything else by holding Volume Down + Power, all I can get is my computer to recognize it as an APX device.
At one point previously, it almost bricked and froze at the same spot, but I somehow played with different reset combinations and it came alive again. Is there any reset combinations that worked for anyone?
Also, I remember doing a system backup within the device. Is there any way to access that, or is it gone?
In other words, do I need to buy a new motherboard? Or is there a remote possibility I can fix it?
One last layman question: why is it I can't just read and write to the device's internal memory, regardless of its status?
-Cannon Fodder
Click to expand...
Click to collapse
Looks like you will need to replace the mb, if you have not already generated nvflash binaries. You can't read/ write to internal memory because when connected to a pc this is done using the mtp protocol which os loaded by android, and hasn't in your case.
JoinTheRealms said:
Looks like you will need to replace the mb, if you have not already generated nvflash binaries. You can't read/ write to internal memory because when connected to a pc this is done using the mtp protocol which os loaded by android, and hasn't in your case.
Click to expand...
Click to collapse
Ok another n00b question...
Why can't I download someone else's binaries from the same type of product?
Forgive me, I'm used to working with Windows and I'm thinking in terms of an install disc...
Cannon Fodder said:
Ok another n00b question...
Why can't I download someone else's binaries from the same type of product?
Forgive me, I'm used to working with Windows and I'm thinking in terms of an install disc...
Click to expand...
Click to collapse
NvFlash blobs are specific to each device they are generated on.
Its like trying to infuse with a different blood type, where each tf300 has a different blood type. Wheelie will reject it and your tablet will reject it.
Cannon Fodder said:
So I apologize in advance, I am a n00b to rooting android devices.
Long story short, I think I hard bricked my TF300T.
I had followed some rooting guides (from other sites ) and yup, I'm stuck at the Asus logo with the "unlock" message in the corner.
I can't get into fastboot or anything else by holding Volume Down + Power, all I can get is my computer to recognize it as an APX device.
At one point previously, it almost bricked and froze at the same spot, but I somehow played with different reset combinations and it came alive again. Is there any reset combinations that worked for anyone?
Also, I remember doing a system backup within the device. Is there any way to access that, or is it gone?
In other words, do I need to buy a new motherboard? Or is there a remote possibility I can fix it?
One last layman question: why is it I can't just read and write to the device's internal memory, regardless of its status?
-Cannon Fodder
Click to expand...
Click to collapse
Here is a link to my guide to enter the bootloader.* Try these each several times as this tablet morphs as you progress.
Provide us a little more info.
What happened to create this problem? *Details please.
Did you have a custom recovery, rom, etc? *If so which ones?
Can you fix it; maybe. *We'll have a better idea once we know your details.
cmendonc2 said:
NvFlash blobs are specific to each device they are generated on.
Its like trying to infuse with a different blood type, where each tf300 has a different blood type. Wheelie will reject it and your tablet will reject it.
Click to expand...
Click to collapse
Thank you for that illustration. It did help me understand.
One last thought of desperation: Is the internal storage an actual SD Card? Or is it just called that on the device menu for some odd reason?
tobdaryl said:
Here is a link to my guide to enter the bootloader.* Try these each several times as this tablet morphs as you progress.
Provide us a little more info.
What happened to create this problem? *Details please.
Did you have a custom recovery, rom, etc? *If so which ones?
Can you fix it; maybe. *We'll have a better idea once we know your details.
Click to expand...
Click to collapse
I was installing a custom ROM, when I went to "RCK"(?), it hung up when it said it was booting kernal. It didn't do anything for quite a while, so I held down the power buttong and reset it. And now it is stuck in the boot loop.
cmendonc2 said:
NvFlash blobs are specific to each device they are generated on.
Its like trying to infuse with a different blood type, where each tf300 has a different blood type. Wheelie will reject it and your tablet will reject it.
Click to expand...
Click to collapse
off topic but that is a pretty good analogy :highfive:
One question tearing me long enought: did someone tryed to hack nvflash binaries? As far as I know there is only one unique file and may be not all of it's content is specific for certain device. Did someone dig in that direction?
Graiden05 said:
One question tearing me long enought: did someone tryed to hack nvflash binaries? As far as I know there is only one unique file and may be not all of it's content is specific for certain device. Did someone dig in that direction?
Click to expand...
Click to collapse
that would be really useful.
And although I understood the analogy, I still don't get the technical aspects of why you can have 1,000 devices that are all the same but they each need a different file. I'm used to building Windows computers, and you can use the same image repeatedly for multiple copies of the same type of computer.
I'm also wondering: why can't anything be installed straight from the SD card or even USB when a device is bricked? How does Asus do it when they fix people's motherboards?
Cannon Fodder said:
that would be really useful.
And although I understood the analogy, I still don't get the technical aspects of why you can have 1,000 devices that are all the same but they each need a different file. I'm used to building Windows computers, and you can use the same image repeatedly for multiple copies of the same type of computer.
I'm also wondering: why can't anything be installed straight from the SD card or even USB when a device is bricked? How does Asus do it when they fix people's motherboards?
Click to expand...
Click to collapse
Think of it like a cryptographic key. Each tablet's NVFlash blobs has a certain signature. To compare it to the Windows situation, assume that you have a legal, non-volume licence key for Windows, only that when you installed it the first time, the key was permanently bound to the motherboard.
Assume that it is a string of lower-case letters (good chance that it has numbers, capital letters, and all sorts of fun stuff). A two-character signature has a space of 26*26, which is already over 625 keys. That number scales hella fast when you add more characters.
Asus will fix your tablet by either replacing your motherboard completely (more likely), or they may have the NVFlash keys for your device by its serial number. However, since your bootloader is unlocked, and they will have your serial number on file as "unlocked", they may just refuse to repair it outright. Surely, they will refuse it for a warranty repair, though I don't know if they will even repair your device for money.
So.. I totally forgot to change the naming convention in the flashable bootloader/modem files. And I bet most of you can surmise the colossal mess I am in right now... Do I get insurance and "wait" then claim? Or is this fixable? All in all... I was on 10p and accidently flashed the 10k bootloader and modem as the only difference between the two is the last tiny, yet uber important, version letter... And being overly tired, I farked...
What is the result of this?
Nothing.... Literally... No power, no backlight, no vibration... Nada.... The only thing of refrence to something like this is a Kindle Fire whos bootloader got mis-flashed and they has to jumper the device and use usbboot.. But I am unsure as to the translation over to LG droid....
Any help or suggestions beyond the painfully obvious "Sounds like you ****ed up" would be of the utmost appreciated.
TIA
j5
Also.. I have been noticing a performance degradation on the device. Even with fresh installs of the "Fast as Balls" 10p rom, and excess heat. I tried to flash Weta and it was stuck in a boot loop, up to the LG screen then reboot and up to the LG screen again. I would expect to see some sort of life, even if it can't get past the bootloader... Or is that how these operate? if bootloader is cooked(I am guessing that is my issue) then NO power gets transferred? Shouldn't the battery charge at least?
Also... The battery is full.....
****SIDE NOTE TO MAKER OF FLASHABLE BOOT PACKAGES*******
Can you implement a version check before it goes on and flashes the BL? Which would have saved me in this case... And could save future me's from doing this..??
ARB was triggered, and it blew the qfuse. Even if we had a way to boot from the SD card or USB (which we don't), your CPU is physically damaged. Thank Qualcomm, LG, and T-Mobile, for being super *****.
anonymoustl said:
So.. I totally forgot to change the naming convention in the flashable bootloader/modem files. And I bet most of you can surmise the colossal mess I am in right now... Do I get insurance and "wait" then claim? Or is this fixable? All in all... I was on 10p and accidently flashed the 10k bootloader and modem as the only difference between the two is the last tiny, yet uber important, version letter... And being overly tired, I farked...
What is the result of this?
Nothing.... Literally... No power, no backlight, no vibration... Nada.... The only thing of refrence to something like this is a Kindle Fire whos bootloader got mis-flashed and they has to jumper the device and use usbboot.. But I am unsure as to the translation over to LG droid....
Any help or suggestions beyond the painfully obvious "Sounds like you ****ed up" would be of the utmost appreciated.
TIA
j5
Click to expand...
Click to collapse
Anything happen when you connect it to usb? Try various methods you can find, i believe some involve removing the battery and holding a volume key. Can you get to download mode? You can try a lg warrenty claim and play dumb, 50% chance they will fix it if its still under warrenty. And if they want money to fix it, you have the option to have it returned to you at no cost, but you will Be without the device for a few weeks.
The usb would recognize it only under the PORTS in win10 as Qualcomm something.... But nothing would get it to fastboot/dl or recovery. I just told them that I had been experiencing slowness and that my network was attacked by sophisticated malware and that during an OTA from 10k to 10p, my device somehow got interrupted, and thus presented me with the symptoms described in this thread, and on the RMA.. That way, an unlocked bootloader splash could be explained away by the malware, and the 10k to 10p update being disrupted will cover anything else wrong with it as far as what I reported. The RMA was approved and it is on its way.... Bases Covered...
Just an FYI, you didn't have to lie to them. I have sent one of my v20s back to them 3 times. In my trying to find ways to root the H910 v10m, and just understand protected boot in general, risks had to be taken. I was up front with them everytime that I flashed something I shouldn't have.
Also, your phone was recognized as Quallcomm 9008 QD Loader. The CPU goes into that mode when the boot loader is damaged, or if the qfuse has been popped.
runningnak3d said:
ARB was triggered, and it blew the qfuse. Even if we had a way to boot from the SD card or USB (which we don't), your CPU is physically damaged. Thank Qualcomm, LG, and T-Mobile, for being super *****.
Click to expand...
Click to collapse
Well as you know runningnak3d, I'm not sure I agree on that point.
What I mean is that with the proper tools, you could put a 10p bootloader on there and it would work again. That's my theory.
But right now there is no known working solution for H918. So the point becomes kind of moot.
There is for the other V20 variants though. Octoplus can.
This is the way that it works. This is no longer a guess:
There isn't just one qfuse, there are several. One determines if trusted boot is enabled -- this one is blown on all production Qualcomm phones. One contains the ARB version, and one contains the SHA1 signature of the XBL. There may be more, but those are the ones that were are interested in.
When you boot your phone, the PBL checks the TRUSTED_BOOT fuse, and if it is blown, it checks the SHA1 hash of XBL. If the hash is good, XBL loads, and it checks to see what the ARB version is. The ARB is a bitmask of qfuses. When you get a fresh CPU, and no firmware has been BOOTED with a greater ARB, then no fuse gets blown and ARB stays zero. If you boot an XBL with a greater ARB version, it pops bit one of the qfuse and you are at ARB 1.
Now, here is the problem. If you flash an older ARB version XBL, then it will not boot (9008). You are correct. If we had the tools to get the proper XBL back onto the NAND, the phone would come back to life.
EDIT: just to be clear, that is the abbreviated version of the boot process. The PBL and XBL actually do a lot more checking before booting, but for the sake of this thread -- that is the important part.
-- Brian