Hello,
I own a US Xoom wifi only which is on Android 3.1 (HMJ37), and I received the OTA to update it to Android 3.2, but when the Xoom reboot in recovery, there is a problem when flashing (and the droid gets a "!").
I push power + volume up to see what's wrong and it seems there is a problem with /cache (see the screenshot atached).
I've searched on several forums, I even contacted Motorola support, but their only answer was to do a factory reset, which didn't solve my problem.
Hope someone can help
PS : My xoom is not rooted, and not unlocked.
I had similar issues and ended up using this posted method...
It worked well and I did not have to reinstall or reload any apps or data.
http://forum.xda-developers.com/showthread.php?t=1165998
Hope this helps
Thanks for the answer, but I wan't to keep my xoom 100% stock, and your solution need to have CWM :/
I'm having the same problem! Not rooted, and she doesn't want to update. I get the yellow exclamation point. Any help would be appreciated!
Not sure what the issue is but this is what I would do. I don't think you will though.
Unlock the bootloader.
Flash all the official system images from motorola. Wipe etc.
Relock the bootloader. Make sure you flashed the official imgs for your device( us 3g /wifi are the only avaible ones) before/if you relock it.
You are now back to factory shipping stock.
If you still have the issue your device likely has a hw issue or a defect of some kind.
Or just send it in for warrenty repair if you don't want to try that method. Which is what I think you should do since you're one of those I want 100 percent stock folks.
Sent from my Xoom using Tapatalk
Make sure NO µSDcard is insered during the update
on my xoom, I had this issue and it solved without µSDcard.
Here's the problem, I have an evo4g, rooted, cwm recovey. Touchscreen stopped working, but all else is ok. I can boot into recovery and flash from cwm etc. Now, I have TEP and would like to get it repaired. I see that I can switch between son/soff via cwm and unrevoked utils, but would like to go back to 100% stock so that I don't have issues with sprint. Can this be do e with cwm? If so, can someone point me to the steps and files that I need?
Thanks!
Use the PC36IMG.zip on this page: http://forum.xda-developers.com/showthread.php?t=780141
Leaving S-Off will be fine, if someone gets that phone again I'm sure that if they try to root they will appreciate it. Download the PC36IMG.zip, put on root of SD Card, go to bootloader, hit down button and the bootloader will search for the PC36IMG.zip, choose to update.
It's been pretty well documented that Sprint doesn't care that it's been rooted if it's a hardware problem. I have taken a rooted phone running CM7 into get a screen replaced and the techs just asked me how I liked that ROM. It "potentially" voids your HTC warranty, but doesn't affect your service from Sprint.
Thanks guys, maybe I'll just leave it as is and see if they'll just fix it!
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.
Hi All,
I've found myself in quite a bind. Today, my Spring Galaxy S4's screen spontaneously decided to stop working (the battery charging icon and the boot animations both do not show). I've contacted Samsung and they've agreed to bring it in for repairs, however, I am running cyanogenmod 11 and thus both the rom and the flash counter are obstacles to the repair. Flashing to stock wouldn't normally be a problem, however, I am having trouble getting into download mode reliably without seeing the screen (I know the command, but sometimes it will unreliably boot up). Additionally, the only method of resetting the flash counter i have found is triangle away, which would also require the screen turning on. Does anyone have any suggestions or links to threads that I may have missed regarding a similar problem? I didn't find anything in my searching the forums.
Michael
Atrius010 said:
Hi All,
I've found myself in quite a bind. Today, my Spring Galaxy S4's screen spontaneously decided to stop working (the battery charging icon and the boot animations both do not show). I've contacted Samsung and they've agreed to bring it in for repairs, however, I am running cyanogenmod 11 and thus both the rom and the flash counter are obstacles to the repair. Flashing to stock wouldn't normally be a problem, however, I am having trouble getting into download mode reliably without seeing the screen (I know the command, but sometimes it will unreliably boot up). Additionally, the only method of resetting the flash counter i have found is triangle away, which would also require the screen turning on. Does anyone have any suggestions or links to threads that I may have missed regarding a similar problem? I didn't find anything in my searching the forums.
Michael
Click to expand...
Click to collapse
So you have ZERO display on the screen at any time? If that's the case they can't tell it's not stock?? If it boots and you have usb access just grab whatever you need off of it. Do you ever get it into download mode at all? Can you get Odin to recognize it (com block is green)?? If it's boned for sure what do you have to loose if the Odin fails? It'll be fubar and they have even less of a chance of knowing it's not kosher.
Please anyone with a better idea correct me, but this is what I would do.
That's right, zero display on the screen at any time. Althought the capacitive buttons do appear to work. I can boot it into download mode and have used the info in the first post of this thread to remove cyanogenmod, but since I can't use my screen I can't see triangle away to reset the counter. Odin recognizes it at this point and I can flash whatever. I'm more concerned that Samsung has some way of reading the flashcount with a non-functional screen.
CyberpodS2 said:
So you have ZERO display on the screen at any time? If that's the case they can't tell it's not stock?? If it boots and you have usb access just grab whatever you need off of it. Do you ever get it into download mode at all? Can you get Odin to recognize it (com block is green)?? If it's boned for sure what do you have to loose if the Odin fails? It'll be fubar and they have even less of a chance of knowing it's not kosher.
Please anyone with a better idea correct me, but this is what I would do.
Click to expand...
Click to collapse
Atrius010 said:
That's right, zero display on the screen at any time. Althought the capacitive buttons do appear to work. I can boot it into download mode and have used the info in the first post of this thread to remove cyanogenmod, but since I can't use my screen I can't see triangle away to reset the counter. Odin recognizes it at this point and I can flash whatever. I'm more concerned that Samsung has some way of reading the flashcount with a non-functional screen.
Click to expand...
Click to collapse
Well, you have a non functional phone with a voided warranty so you have no choice but to send it in as is. Samsung will either fix it under warranty, fix it and charge you for the repair, or refuse to fix it and send it back to you. That is the chance we all take when we root and install custom roms. If you can get the stock rom flashed through odin then maybe you can connect it to a tv and access triangle away that way. The touch screen may still be responsive even though the screen is dead.
Well, issue resolved. Sprint was able to replace the backlight in my phone, and now my screen works. Thanks for all of your help anyways! As an added bonus, they reflashed my phone and the binary counter is now back to official status.
cruise350 said:
Well, you have a non functional phone with a voided warranty so you have no choice but to send it in as is. Samsung will either fix it under warranty, fix it and charge you for the repair, or refuse to fix it and send it back to you. That is the chance we all take when we root and install custom roms. If you can get the stock rom flashed through odin then maybe you can connect it to a tv and access triangle away that way. The touch screen may still be responsive even though the screen is dead.
Click to expand...
Click to collapse
Atrius010 said:
Well, issue resolved. Sprint was able to replace the backlight in my phone, and now my screen works. Thanks for all of your help anyways! As an added bonus, they reflashed my phone and the binary counter is now back to official status.
Click to expand...
Click to collapse
Just the binary count right? Not the Knox counter. That would be news.
Sent from my SGH-L720 using XDA Premium 4 mobile app
Sorry, I never had Knox given that I was always on MF9. Unfortunately now I'm missing stock recovery, but they flashed me back to 4.2.2 with MDC firmware.
CyberpodS2 said:
Just the binary count right? Not the Knox counter. That would be news.
Sent from my SGH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Since I got my Nexus 6P sometimes it could just hang and then restart, I thought this was nothing major so I did nothing about it. Today however, I got a couple of these restarts in one day and after the last one I can't boot. The unlocked bootloader message appears, then the Google logo and after that it keeps looping. I can get into bootloader, however when I try anything there (boot into recovery, BP tools or "factory") it just starts looping again. I have tried restoring nexus 6p system images with Google's "flash-all" bat file, and with Heisenberg's method on 2 different android versions and it goes through without problem, however I'm still stuck in a bootloop.
Any help would be appreciated.
Thanks.
Try flashing all of the factory image files manually. If it still fails to boot, contact Google / Huawei for an RMA.
RoyJ said:
Try flashing all of the factory image files manually. If it still fails to boot, contact Google / Huawei for an RMA.
Click to expand...
Click to collapse
I've been through 5 so far. I'll give them a call tomorrow morning and see how it goes. Hopefully the warranty still covers me. I've done some digging around, and what is happening to me is the exact same thing as what is happening to some people through the OTA nougat update, with the only solution being exactly what you said.
I just really hope I can actually get a replacement as I have done nothing wrong on my side, it seems to be purely Huawei's fault. Thanks anyway.
Called them this morning. The person on the phone said that because the phone was rooted, it would need out of warranty repairs (which is ridiculous as this exact issue happens to people that were never rooted and didn't even unlock the bootloader, who can get a replacement for free). I'll see how it goes.
domdomrys said:
Called them this morning. The person on the phone said that because the phone was rooted, it would need out of warranty repairs (which is ridiculous as this exact issue happens to people that were never rooted and didn't even unlock the bootloader, who can get a replacement for free). I'll see how it goes.
Click to expand...
Click to collapse
How did they saw if your phone was rooted? Did you told them?
GKti22 said:
How did they saw if your phone was rooted? Did you told them?
Click to expand...
Click to collapse
The guy at Huawei didn't really know what the warranty covers. I mentioned trying to restore from Google's factory images (implying that I unlocked the bootloader) and he said that this might have voided the warranty (which I'm pretty sure it hasn't) as it is a software modification in a sense, but he's not entirely sure. They're going to send me a box to send the phone to them, and through that they'll be able to tell that no modifications have happened I hope (it's technically all stock and unrooted now, it just doesn't boot up). If they do try and charge me, I'll call the actual repairs team (as they're not available today) and explain the situation. No way am I paying for something like this as it hasn't happened through my own fault.
Under Europe regulations THEY have to formally prove the software modifications lead to the hardware fault (if that's a hardware fault) and that would be really bad publicity for Huawei. Not sure how UK applies that to its local right.
Root may very well void the warranty based on an old thread on XDA here that's buried in the general section somewhere, but an unlocked bootloader absolutely will not void the warranty.
Hi, can someone please upload the build.prop for nexus 6p 7.1 dev preview, I did some changes and now stuck in boot loop, also the backed up copy that I have has previous version names and all according to 7.0 , I am stuck in twrp and don't have computer then how is it possible to make changes directly from twrp terminal, I tried "vi build.prop" and was able to see build.prop but couldn't edit, Thanks
Here you go https://paste.debian.net/897221
For anyone wondering, I got the phone the other day and they fixed it under warranty. No extra costs or anything (I enclosed a letter giving proof as to why I believe it should still be under warranty, and it worked fine). The serial number and IMEI has changed, so it leads me to think that it was indeed a motherboard failure. Thanks for the help!