Related
So I've apparently, effectively bricked my phone. Under bootloader it is listed as S-OFF. Is there any way I can return my evo in and stay under warranty?
Note: I can not reach recovery.
What happens when you rename a recovery to PC36IMG.zip and try to update via bootloader?
I go into a boot loop no matter what i do, no matter what I flash. I have flashed 10+ PC36IMGs with everything from bootloaders to recoveries, to every img that can be on the phone... there is a thread still on the first page if you want to look at that.
Anyways, it doesn't look like I'm going to be able to fix it, so this is more about what options are available to me in getting a new phone, if you having any suggestions though on what I can do to fix mine, please be my guest and comment on my thread below, I'm still trying to fix it!
Just report the phone lost or stolen and pay $100 deductible.
Sent from my PC36100 using XDA App
I would try one last time to flash Amon's recovery.
Download this: http://forum.xda-developers.com/attachment.php?attachmentid=483320&d=1294435056
Rename it to "PC36IMG.zip"
put it on the root of your sd card via a card reader if you have one or someone elses phone.
then update via bootloader.
Other than that I'm out of ideas. The good news is I'm not as savvy as 95% people on here, which means someone much smarter than me might know the answer. Good luck.
Hmm, yeah I may just have to pay the 100 then... but is that an insurance thing or a warranty thing? I don't have insurance
Do you think Sprint will even check for the S-ON?
thanamesjames said:
Hmm, yeah I may just have to pay the 100 then... but is that an insurance thing or a warranty thing? I don't have insurance
Do you think Sprint will even check for the S-ON?
Click to expand...
Click to collapse
i dont think its a warranty thing its insurance and i think your screwed
What happens when you put a pc36img.zip file on the root of your SD card and start up in bootloader?
I appreciate the people trying to help me... but honestly i've flashed a ridiculous amount of PC36IMGs. Both boot.img and recovery.img and then much more. This is more about, is there anyway I can return it to sprint and get another under warranty. Sounds like i'm out of luck.
So you cleared all the caches?
thanamesjames said:
I appreciate the people trying to help me... but honestly i've flashed a ridiculous amount of PC36IMGs. Both boot.img and recovery.img and then much more. This is more about, is there anyway I can return it to sprint and get another under warranty. Sounds like i'm out of luck.
Click to expand...
Click to collapse
What did you do that caused this issue? Or what were you trying to do? Also what hboot version do you have?
I've done "clear storage" I don't see a place to clear anything other than that in hboot.
thanamesjames said:
I appreciate the people trying to help me... but honestly i've flashed a ridiculous amount of PC36IMGs. Both boot.img and recovery.img and then much more. This is more about, is there anyway I can return it to sprint and get another under warranty. Sounds like i'm out of luck.
Click to expand...
Click to collapse
Pretty much. If you haven't tried yet, try re-rooting via toast's method.
http://forum.xda-developers.com/showthread.php?t=690762
Try going through the whole process. If successful make sure you have a nice stock ROM like the current Sprint Lovers ROM to flash.
Unfortunately my phone isn't getting listed as a device under adb, and thats part of the toast tutorial I have tried his eng-PC36IMG.zip, and it didn't work
woah woah woah....
take your phone to wal-mart and slide it over the demagnetizer at the register a couple times.
THAN take it in.
_MetalHead_ said:
What did you do that caused this issue? Or what were you trying to do? Also what hboot version do you have?
Click to expand...
Click to collapse
I had nightlies of CM7 they would reboot fairly often, but I just figured they were unstable. Out of nowhere it rebooted, and lost all my texts, and desynced my google account. I decided to switch to CM6. When i switched to CM6, soon after it rebooted out of nowhere, and then staid in an endless loop and never came out. I currently have hboot .76, for more fastboot commands.
Try this PC36IMG.zip. If it doesn't work the first time then try it again. If it doesn't work the second time, then I would say you're SOL. I know you said you've tried a bunch but they aren't all the same. It's the sprintlover's full update ROM.
_MetalHead_ said:
Try this PC36IMG.zip. If it doesn't work the first time then try it again. If it doesn't work the second time, then I would say you're SOL. I know you said you've tried a bunch but they aren't all the same. It's the sprintlover's full update ROM.
Click to expand...
Click to collapse
Is it from here? http://forum.xda-developers.com/showthread.php?t=830153
If so I've tried it
thanamesjames said:
Is it from here? http://forum.xda-developers.com/showthread.php?t=830153
If so I've tried it
Click to expand...
Click to collapse
Yep :/ I don't know what to tell you then man, sorry.
I guess I'm going to Sprint and playing stupid!
Has anyone done this successfully?
It sucks because as soon as I started having these problems, all the experts would be frustrated and say "*sigh* you're not bricked, you can get into bootloader" and so I was so sure it was fixable... but apparently not. Every time I mention it I have a thousand people yell at me "FLASH PC36IMG!!" Anyways thanks for the help!
Hello,
So I bought my Xoom over the weekend when I never heard back from a Craigslister about a Xoom they have that is bootlooping.
Finally got back to me today and I am looking to fix it, and make a little profit.
Guy explained he knows it can get into Fastboot and mentioned RSD lite so I know he has done some research but ultimately he said he is not good at computers and cannot fix it.
My question is what do I need to consider? If I can access hboot ( from power off wait til see M and hit Vol - right?) I should be good to go is my understanding. Is there any way to run a diagnostic and see if there is hardware issues going on?
What would you do I guess lol
He said I could tinker with it first. I am familiar with ADB and rooting / custom roms on Android but have only had my Xoom for about 3 days.
Thanks
If you can definitely get into fastboot, you can recover it; simple as that. Whether there are hardware issues is another matter.
MoreGone said:
Hello,
So I bought my Xoom over the weekend when I never heard back from a Craigslister about a Xoom they have that is bootlooping.
Finally got back to me today and I am looking to fix it, and make a little profit.
Guy explained he knows it can get into Fastboot and mentioned RSD lite so I know he has done some research but ultimately he said he is not good at computers and cannot fix it.
My question is what do I need to consider? If I can access hboot ( from power off wait til see M and hit Vol - right?) I should be good to go is my understanding. Is there any way to run a diagnostic and see if there is hardware issues going on?
What would you do I guess lol
He said I could tinker with it first. I am familiar with ADB and rooting / custom roms on Android but have only had my Xoom for about 3 days.
Thanks
Click to expand...
Click to collapse
The question is, how much are you willing to pay if you can't fix it, then if you can you will be happy, if not you should stay happy.
Bootloop can be software but they can easily be hardware too so better be safe than sorry
take a laptop with you and do "fastboot devices' on the spot.
If the computer can see it then it can be wiped clean and fixed
It's $300 and it wouldn't kill me, obviously wouldn't be ideal but not the end of the world either.
ydaraishy said:
If you can definitely get into fastboot, you can recover it; simple as that. Whether there are hardware issues is another matter.
Click to expand...
Click to collapse
That's what everyone told me when mine went into a boot loop. I was able to flash the new images in fastboot, but it never came out of the boot loop.
P00r said:
The question is, how much are you willing to pay if you can't fix it, then if you can you will be happy, if not you should stay happy.
Bootloop can be software but they can easily be hardware too so better be safe than sorry
Click to expand...
Click to collapse
At what point would I be able to run that command? When powering up, at the M etc?
Zargon335 said:
That's what everyone told me when mine went into a boot loop. I was able to flash the new images in fastboot, but it never came out of the boot loop.
Click to expand...
Click to collapse
Stock images?
Zargon335 said:
That's what everyone told me when mine went into a boot loop. I was able to flash the new images in fastboot, but it never came out of the boot loop.
Click to expand...
Click to collapse
That's certainly a concern
ydaraishy said:
Stock images?
Click to expand...
Click to collapse
Yes.
10chars
@OP
If seller knows about Fastboot & RSD Lite, he's probably on this forum. Might even be in this thread.
HEY SELLER just let me figure this out and I'll buy it right off ya, OK?
If you CAN get out of it that certainly a very good price. Most cases I think I have seen have been recoverable. Maybe ask the seller how he got into this situation in the first place, might give you a better understanding of how to fix it.
Hi everybody, I enjoyed my stock N4 for almost a year and today several apps started to crash suddenly, after that the device rebooted itself and never got out of the bootloop. I immediatly booted into recovery and tried to wipe the cache memory and perform a factory reset but I cannot do either of the two, the error I get is something like "can't mount cache partition".
What should I do? How did this happen?!? I really need my phone back asap.
Thanks everybody!
Flash the stock images.
Chromium_ said:
Flash the stock images.
Click to expand...
Click to collapse
Ok I will but...How can this happen? A fully stock phone who never had a problem suddenly corrupts it's partitions?! (This is my understanding of the situation, correct me if I am wrong)
Thanks again for the link
Update: unlocking the bootloader works but when I reboot it appears to be locked again.
flashing the bootloader img file fails.
chikosneff said:
Update: unlocking the bootloader works but when I reboot it appears to be locked again.
flashing the bootloader img file fails.
Click to expand...
Click to collapse
sounds like your storage itself fails. thats the same issue that happens when the storage goes bad.
simms22 said:
sounds like your storage itself fails. thats the same issue that happens when the storage goes bad.
Click to expand...
Click to collapse
Thanks for helping, yes it looks like..so I can throw away my phone or there's something more I can try?
It feels so weird because it's one of the few phones I always kept stock, never fell, never had a single problem. Damn.
chikosneff said:
Thanks for helping, yes it looks like..so I can throw away my phone or there's something more I can try?
It feels so weird because it's one of the few phones I always kept stock, never fell, never had a single problem. Damn.
Click to expand...
Click to collapse
You could give this a try, but I really doubt it'll do much. I guess its worth a shot though.
chikosneff said:
Ok I will but...How can this happen? A fully stock phone who never had a problem suddenly corrupts it's partitions?! (This is my understanding of the situation, correct me if I am wrong)
Thanks again for the link
Click to expand...
Click to collapse
chikosneff said:
Update: unlocking the bootloader works but when I reboot it appears to be locked again.
flashing the bootloader img file fails.
Click to expand...
Click to collapse
Tried to Toolkit yet ? http://forum.xda-developers.com/showthread.php?t=1766475
Why did it happen? A phone is basically a mini computer, same as when you have to reload a computer OS sometimes,(failing hardware, bad app???)
Timboe73 said:
Tried to Toolkit yet ? http://forum.xda-developers.com/showthread.php?t=1766475
Why did it happen? A phone is basically a mini computer, same as when you have to reload a computer OS sometimes,(failing hardware, bad app???)
Click to expand...
Click to collapse
I'll give it a shot thanks, but I am afraid that the fastboot flash error is pretty clear :crying:
I get the phone being a computer, and I am totally ready to reload an OS...but I am not so ready to see the storage fails so suddenly leaving me with no phone, especially because this phone has received more care than any other phone I ever had..
Timboe73 said:
Tried to Toolkit yet ? http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
If its failing when he does it manually via fastboot commands, its very unlikely that using a toolkit will change anything. A toolkit simply runs the same fastboot commands behind a GUI.
Switched to windows to give the toolkit a try, then I will follow the unbrick procedure...I still cannot believe that this phone is lost without even having experienced the fun to mess it up with my own hands
chikosneff said:
Switched to windows to give the toolkit a try, then I will follow the unbrick procedure...I still cannot believe that this phone is lost without even having experienced the fun to mess it up with my own hands
Click to expand...
Click to collapse
As expected: toolkit not working. Since the bootloader " relocks" itself after rebooting the toolkit is unable to flash it afterwards.
Will try to contact google support but I am currently living in Europe I don't think it will be easy to get help.
Any other help is greatly appreciated. Thanks everybody.
1. if its within the warrenty period, this is something that would be covered.
2. its fixable. it can be professionally repaired, or you can try to do it yourself with the right parts.
but you will lose whatever you had in your storage, if you havent already.
another case reported :/
i think some batches of nexus 4 contains emmc brick bugs
just see this thread, more then 5 or 6 have been reported here.
http://forum.xda-developers.com/showthread.php?t=2259334
so after reading that thread i **** my self, because if this occured to my nexus i will have no warranty no google claims no nothing because i live in Pakistan.
So i ran emmc check app on my phone to check what it shows.
my emmc check shows i have "NO, Sane chip"
this means i am safe? if it give me "Yes, Insane chip" then i,m not safe according the my theory.
EMMC check app also shows the chip type, my chip type is "016g92"
googling this chip type i came across no specific results, one from S3 sudden death thread discussion. one person reports he have the 016g92 type and it is a safe chip according to other folks.
and one person having a galaxy s3 bricked his emmcs chip and claim the warranty. after the phone returns his chip type change to 016g92
http://smartphone.usofttech.com/t85915.html
so they change the emmc chip to 016g92.
can i surely assume that my nexus is safe from this serious hardware defect?
also any one here run the emmc chip and do give there chips type here, as i want to confirm if i,m safe or not. if not i,m going to sale my phone here. because the lose will be unbearable for me if the brick did occured
---------- Post added at 11:48 AM ---------- Previous post was at 11:37 AM ----------
simms22 said:
1. if its within the warrenty period, this is something that would be covered.
2. its fixable. it can be professionally repaired, or you can try to do it yourself with the right parts.
but you will lose whatever you had in your storage, if you havent already.
Click to expand...
Click to collapse
Dear Sir do advice me
simms22 said:
1. if its within the warrenty period, this is something that would be covered.
2. its fixable. it can be professionally repaired, or you can try to do it yourself with the right parts.
but you will lose whatever you had in your storage, if you havent already.
Click to expand...
Click to collapse
I still have 2 weeks of warranty left but I'll be in Europe till next year..I will try to ask the warranty service if I can send it in at my own expense.
Damn a worldwide warranty service doesn't look so useless now as it looked when I bought it :laugh:
PHONE BACK FROM THE DEAD!!!
So I got in touch with google's customer care to arrange the RMA and just to show them that my phone was impossible to recover I jumped ahead and told 'em: ok let's do a factory reset together so that I can show you what's the problem....
Fastboot>recovery>>data wipe....COMPLETED!
I cannot understand why did it work, I tried to wipe it at least ten times yesterday.
So now I have my N4 back working. What's your opinion on what happened? Do you feel like the problem is going to show up again soon? Is there anything I should do now that it's working? I just did a factory reset, not the cache wipe.
Just FYI: RMA from oversea is a pain in the ass, you have to ship the phone back to somebody in the U.S. and THEN ask for the RMA.
I wish I had your luck, mine did the same thing about 2 weeks ago. Couldn't get it to factory reset either. Mounting issue. My RMA came in yesterday. I'm enjoying the new phone though. It's even got the little nubs on the back. Mine original was a creaky 1st or 2nd batch one, I think. I will miss all the memories, pics, and data on my old one though.
SefEXE said:
I wish I had your luck, mine did the same thing about 2 weeks ago. Couldn't get it to factory reset either. Mounting issue. My RMA came in yesterday. I'm enjoying the new phone though. It's even got the little nubs on the back. Mine original was a creaky 1st or 2nd batch one, I think. I will miss all the memories, pics, and data on my old one though.
Click to expand...
Click to collapse
Since I feel this problem is hardware related I do not feel completely safe and I believe you were the lucky one getting the RMA
I had no choice, I should have sent the phone back to the US and then ask for the RMA...big pain in the ass
:fingers-crossed: let's hope this thing holds
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.
*EDIT 05-24
I had a problem where I would get stuck even after using MSMDOWNLOADTOOL completely. With the help of great minds,
#fullofhell #Dark Nightmare #Scott and frankly a god #Eliminater74 I could fix the phone completely. I am heading for modem work, which put me into this situation.
As of this point, I cannot find any misbehavior but I am quite new to this, so I can be deadly wrong. (Well but then, sensors are fine, calls , texts, data, wifi is working just fine. I don't know what else to check!)
I know as a fact that what happened to me is not really that rare (although it is quite rare, it happened before as well.)
So I was about to share how I fixed it but decided not because what I did was so out of experimental and I frankly have no idea if the same would work for others.
Tbh, if you are in the same position as I am, go ahead and contact the Oneplus service team. I did what I did only because I had to, I am Korean, and couldn't get it fixed.
If anyone, comes to this point and has absolutely no way to get it fixed, I will be glad to help,
(only if that person agrees that there is more chance to totally destroy it then fixing it XD.)
Again, Thank you so much Scott, dark nightmare. What you guys shared with me saved a bunch of time and you guys are what the forum truely needs!
P.S, Still couldn't find the moded MSMdownload tool. What can you recall what functions it had? Maybe enabled engineer mode?
I can't assist with your dump file, I'm just curious though how exactly did you brick your device?
Pain-N-Panic said:
I can't assist with your dump file, I'm just curious though how exactly did you brick your device?
Click to expand...
Click to collapse
Although it's pure stupidity, I guess it's worth sharing. I was messing around with the modem and somehow somewhere I broke proximity sensor.
So, I used fastboot flash tools including critical partitions. Which is the same process shared by amt911 "https://forum.xda-developers.com/oneplus-6t/help/bricked-oneplus-6t-msmdownloadtool-t3900145". Once I was done with flashing, I could not reboot. Here, I could have just side load or try to find other way out but I decided to use msm tool, which locked my oem.
basically, I think it's critical partition that causes un-recoverable boot-loop to some of us. That is not fixed by msmdownloadtool for now.
Which, I am curious, do you think msm-download tool will wipe and flash every partitions? From what I searched so far, everyone seems to agree that msm tool will flash every partitions including the critical parts (which is not exactly true because I know for a fact it doesn't wipe out efs partition). If not, do you think there is a way to force it?
Thank you for your interest though! I am going quite sad and mad alone here!
Somehowko said:
Although it's pure stupidity, I guess it's worth sharing. I was messing around with the modem and somehow somewhere I broke proximity sensor.
So, I used fastboot flash tools including critical partitions. Which is the same process shared by amt911 "https://forum.xda-developers.com/oneplus-6t/help/bricked-oneplus-6t-msmdownloadtool-t3900145". Once I was done with flashing, I could not reboot. Here, I could have just side load or try to find other way out but I decided to use msm tool, which locked my oem.
basically, I think it's critical partition that causes un-recoverable boot-loop to some of us. That is not fixed by msmdownloadtool for now.
Which, I am curious, do you think msm-download tool will wipe and flash every partitions? From what I searched so far, everyone seems to agree that msm tool will flash every partitions including the critical parts (which is not exactly true because I know for a fact it doesn't wipe out efs partition). If not, do you think there is a way to force it?
Thank you for your interest though! I am going quite sad and mad alone here!
Click to expand...
Click to collapse
Damn man, sorry to hear that. I've never had to mess with msm tool, thankfully. The fact that it locks the bootloader kind of scares me. From what I've read about the tool it does sound like it wipes/flashes all partitions including critical.
Are you able to unlock the BL in fastboot mode using the command?
Pain-N-Panic said:
Damn man, sorry to hear that. I've never had to mess with msm tool, thankfully. The fact that it locks the bootloader kind of scares me. From what I've read about the tool it does sound like it wipes/flashes all partitions including critical.
Are you able to unlock the BL in fastboot mode using the command?
Click to expand...
Click to collapse
As the bootloader is locked and I cannot boot, I am can't put enable oem-unlock on the data. Which means, yes I cannot unlock the bootloader as long as oneplus 6t doesn't have a loophole like oneplus 3T. I am pretty sure that was fixed though.
Well, I don't know if it's msm tool really. If I just started with that I would have been fine (at least I believe so). Yes I didn't wanted to lock the boot loader, which is why I used fastboot flash tool. But then, that's why I ended up here. So, if you end up in a situation where you might, might need msm tool or flash tool, always go with the msm tool !
For msm, I am quite certain it doesn't flash all partitions. I think there is some partition checkup somewhere. Here is why I think so
1) Completely formatted OS cannot be on a boot loop unless it's caused by hardware issue.
2) All partitions except vendor, system goes way too fast. It ends within 200 seconds for me. I would assume that kinda makes sense as it really is the problem of usb-pc hardware power but installing the image should take longer I think (but then I truly have no idea)
My conclusion is that the tool checks partition size before flashing, and does not touch / replace every file. I am probably wrong since it is
EDI tool after all, but I simply cannot believe msm tool cannot fix something that has nothing to do with the hardware.
I mean, imagine we can brake our newly formatted PC OS without any single components corrupted! (Is it even possible?)
I don't know man....with the bootloader locked you're not able to fastboot flash ANYTHING?
Somehowko said:
For msm, I am quite certain it doesn't flash all partitions.
Click to expand...
Click to collapse
Im sure this is correct. This is about the 3rd or so thread that I have read whereas the MSM tool could not completely recover the phone.
So far no one has found a solution. One person ended up sending theres back to OnePlus so we are waiting to find out how it turned out. Here is the thread I am referencing: https://forum.xda-developers.com/oneplus-6t/help/bricked-oneplus-6t-msmdownloadtool-t3900145
Scott said:
Im sure this is correct. This is about the 3rd or so thread that I have read whereas the MSM tool could not completely recover the phone.
So far no one has found a solution. One person ended up sending theres back to OnePlus so we are waiting to find out how it turned out. Here is the thread I am referencing: https://forum.xda-developers.com/oneplus-6t/help/bricked-oneplus-6t-msmdownloadtool-t3900145
Click to expand...
Click to collapse
Well, tbh, we know as a matter of fact it is not a complete flashing. I mean it clearly says flashing to partition _a only unlike previous versions of msm tools (ah, good days.) What I am curious of is if there is anything we can do about skipping partitions. I am suspecting using qfil would, through unpacking ops files. Although it seems like a long shot.
Btw, thank you for your interest!
Scott said:
Im sure this is correct. This is about the 3rd or so thread that I have read whereas the MSM tool could not completely recover the phone.
So far no one has found a solution. One person ended up sending theres back to OnePlus so we are waiting to find out how it turned out. Here is the thread I am referencing: https://forum.xda-developers.com/oneplus-6t/help/bricked-oneplus-6t-msmdownloadtool-t3900145
Click to expand...
Click to collapse
Msm tool has hidden functions, it's a pain but not impossible.
Search Google and gsm forums for readback mode, smt wipe, and imei/esn restore...
Siren siren... Watch out the xda police gunna blow down and remove my comment.. oh nooooo aghastt....
Btw u cannot use berklers script without an AES recovery key. There aren't any around as far as I know for fajita.
Easiest thing is if OnePlus bought device, get an exchange.. play dumb.. oops I dunno, your Android Q crap broke it..
Or if tmo bought, add insurance if u don't have it, play dumb. Get a new one. I did for a scratched screen..but made it about the modem not working, bc I erased it...
These corporations owe us nothing.
Get a new phone man
fullofhell said:
Msm tool has hidden functions, it's a pain but not impossible.
Search Google and gsm forums for readback mode, smt wipe, and imei/esn restore...
Get a new phone man
Click to expand...
Click to collapse
Thank you so much! I don't have to hassle with python anymore!!! That thing was making my brain fart!
Sadly, That's the only option that I got. As I am living in Korea and I cannot send a phone outside of a country (funny isn't it? they say battery hazard, I say licking Samsung's ass) I can't even get it fixed.
Frankly, I love my phone and I would go an extra mile even for a hint of getting it back to work again.
I will try to look for back up and smt wipe. Hopefully, I wouldn't totally destroy my phone. (again, hopefully.)
If you have any other information, please share with me!
Somehowko said:
Thank you so much! I don't have to hassle with python anymore!!! That thing was making my brain fart!
Sadly, That's the only option that I got. As I am living in Korea and I cannot send a phone outside of a country (funny isn't it? they say battery hazard, I say licking Samsung's ass) I can't even get it fixed.
Frankly, I love my phone and I would go an extra mile even for a hint of getting it back to work again.
I will try to look for back up and smt wipe. Hopefully, I wouldn't totally destroy my phone. (again, hopefully.)
If you have any other information, please share with me!
Click to expand...
Click to collapse
You're saying an msm reload didn't fix the device? Btw you can use the unlocked device msm tool as well as of version 9.0.11 I believe, just look for the modded tool that skips the model check, did you do a full system backup before tinkering? If so you can dd files back into place if msm doesn't overwrite them the way its supposed to, I've done some crazy things to the 6t, a bit surprised recovery didn't fix it for you...
And yeah FoH already pointed out that decrypt tool is useless to us.
Dark Nightmare said:
You're saying an msm reload didn't fix the device? Btw you can use the unlocked device msm tool as well as of version 9.0.11 I .
Click to expand...
Click to collapse
Are you talking about what
PHP:
Eliminater74
shared with us? if so, I tried to use back up before smt download but it fails. firehorse read data error 995.
And I didn't do the back up; I only flashed every partition with the fastboot-flash tool. I am quite surprised to see msm letting me down as well );
Can you share more if you know more?
Somehowko said:
Are you talking about what
PHP:
Eliminater74
shared with us? if so, I tried to use back up before smt download but it fails. firehorse read data error 995.
And I didn't do the back up; I only flashed every partition with the fastboot-flash tool. I am quite surprised to see msm letting me down as well );
Can you share more if you know more?
Click to expand...
Click to collapse
Na, there was another someone else had modded, it should be in the general forum, I believe it was linked in the new international conversion method, the one after my thread. If you simply flashed using the fastboot-flash-tool, then you should definitely be recoverable, attempt a msm reload, I believe you may have a usb port issue if you're having firehose failures, try using an onboard port and not the front ports.
Dark Nightmare said:
Na, there was another someone else had modded, it should be in the general forum, I believe it was linked in the new international conversion method, the one after my thread. If you simply flashed using the fastboot-flash-tool, then you should definitely be recoverable, attempt a msm reload, I believe you may have a usb port issue if you're having firehose failures, try using an onboard port and not the front ports.
Click to expand...
Click to collapse
That's weird. If I had a usb port issue it would say it during the msmdownloading wouldn't it? Msmdownload goes fine but I just can't use the readback function.
And thank you I will go and look for it!
Somehowko said:
That's weird. If I had a usb port issue it would say it during the msmdownloading wouldn't it? Msmdownload goes fine but I just can't use the readback function.
And thank you I will go and look for it!
Click to expand...
Click to collapse
qusb is weird, it would let me backup but not flash once, tried a different port and it worked fine for both, so I figured I'd suggest such, doesn't hurt to try after all?
Dark Nightmare said:
qusb is weird, it would let me backup but not flash once, tried a different port and it worked fine for both, so I figured I'd suggest such, doesn't hurt to try after all?
Click to expand...
Click to collapse
Weird, different port different errors. Error code changed. I will try with other desktops this afternoon.
For another msmdownload tool, are you referring to the thread "T-Mobile 6T to International Conversion (WITHOUT unlocked bootloader/SIM unlock!)"?
Thank you so much for your help!
Somehowko said:
Weird, different port different errors. Error code changed. I will try with other desktops this afternoon.
For another msmdownload tool, are you referring to the thread "T-Mobile 6T to International Conversion (WITHOUT unlocked bootloader/SIM unlock!)"?
Thank you so much for your help!
Click to expand...
Click to collapse
That's correct and if you're on windows 10 it may be a system update messing with the drivers, its dumb, but it actually affects the simplest of things.
Somehowko said:
Weird, different port different errors. Error code changed. I will try with other desktops this afternoon.
For another msmdownload tool, are you referring to the thread "T-Mobile 6T to International Conversion (WITHOUT unlocked bootloader/SIM unlock!)"?
Thank you so much for your help!
Click to expand...
Click to collapse
As crazy as it sounds three reboots and four different ports did the trcik!
And sincerely thank you! Although I couldn't find the modded msmtool you told me I was able to boot into the os finally.