[Q] Help! I'm about ready to give up on this tablet - Nexus 10 Q&A, Help & Troubleshooting

I posted about this previously and didn't receive much help. Since the issue has only worsened, i figure i'll try again.
My nexus started experiencing random reboot and pretty soon, it wouldn't stay on if i wasn't charging it. I downgraded from kit kat 4.4.4 to 4.4.3 and then to 4.4.2. Didn't help. Then i installed a twrp recovery and the SlimKat rom. Still nothing. So i bought a new battery. Still the same issue. At this point i'm at the end of my rope, not sure if there is anything else i can do. Of course i'm out of warranty so google plus is either unable or unwilling to help, i'm not sure which. They usually sound so hapless when i call. Any ideas what might be the issue or what else i can do? Thanks for your help!

Have you pulled logcat or kmsg when this happens? Did you try complete wipes/formats and full install of all stock firmware/software?

demkantor said:
Have you pulled logcat or kmsg when this happens? Did you try complete wipes/formats and full install of all stock firmware/software?
Click to expand...
Click to collapse
Thanks for your response.
I hadn't ever heard of a logcat until you asked me. I ran a quick scan using catlog and found a boatload of errors and failures. But i'm not really sure how to read them or what to do with it. I was going to post the result of my search filtered to show only the errors and failures, but it wouldn't let me post any outside links.
As to your second question. I performed a factory reset earlier on and then i found your Manta help thread and used it install other stock versions of kit kat. I'm pretty sure i wiped the device completely clean a few times while following those instructions. Correct me if i'm wrong. Thanks for your help. I know its a trial to deal with noobs like me!

Its all good, everyone starts somewhere
Factory resets can often help but the full format you just did via fastboot may have done the trick. As to the logcat you will often see many errors that aren't too important, in your situation you are looking for what may be causing a kernel panic / unwanted reboot
Here is a good place to go to learn how to read them
http://forum.xda-developers.com/showthread.php?t=2274119

demkantor said:
Its all good, everyone starts somewhere
Factory resets can often help but the full format you just did via fastboot may have done the trick. As to the logcat you will often see many errors that aren't too important, in your situation you are looking for what may be causing a kernel panic / unwanted reboot
Here is a good place to go to learn how to read them
http://forum.xda-developers.com/showthread.php?t=2274119
Click to expand...
Click to collapse
Thanks for your help. I've spent the last day and a half reading up on this and even individually googling each error to see what might come up. I haven't come to any satisfactory conclusions. If its not to much work, can you, or anyone else help me read the logcat to see what might be the issue? I have it posted on paintbin. I filtered it to show just the errors and failures to make it short. http://pastebin.com/MyNgt476. Thanks.

I don't see anything terrible in there that would cause it to shut down. Can you grab a last_kmsg after random reboot or get the log while the reboot happens?

demkantor said:
I don't see anything terrible in there that would cause it to shut down. Can you grab a last_kmsg after random reboot or get the log while the reboot happens?
Click to expand...
Click to collapse
I did Last_kmsg after a reboot as you sugested and the result can be found at: http://pastebin.com/z0UquBmq
I also did another logcat this time using adb and pasted it here : http:// pastebin.com/vtGD1qjG. I hope this is able to shed some light on my issues. Thanks so much for your help!

Well good news and bad news, I don't see anything specifically bad.
In the kernel log it looks like reboot was triggered by a keypress which may mean that your power button is faulty or could be something more software where removing it from charger triggers the key press even without actually touching the power button. The problem is that the trigger would be in /system/bin and if an error was there (as in some kind of bad file present) it should be removed in a complete wipe/format. So in truth I can't tell what the cause is.
So to reiterate, your tablet works perfectly fine so long as it is on the charger, once removed it powers off? Or gets stuck in a bootloop? And this wont matter if on stock or custom ROM/kernel? And will it not power on if not on charger or just bootloop?

demkantor said:
Well good news and bad news, I don't see anything specifically bad.
In the kernel log it looks like reboot was triggered by a keypress which may mean that your power button is faulty or could be something more software where removing it from charger triggers the key press even without actually touching the power button. The problem is that the trigger would be in /system/bin and if an error was there (as in some kind of bad file present) it should be removed in a complete wipe/format. So in truth I can't tell what the cause is.
So to reiterate, your tablet works perfectly fine so long as it is on the charger, once removed it powers off? Or gets stuck in a bootloop? And this wont matter if on stock or custom ROM/kernel? And will it not power on if not on charger or just bootloop?
Click to expand...
Click to collapse
Yup, it powers off if unplugged. Nothing i've done so far had changed it. It never bootloops, just off and on. If its unplugged and i try to boot it, it starts for a second and then just fizzles out. Should i maybe try a complete wipe again? Maybe i should sign on to google plus? Am i grasping at straws?

hillsfr said:
Yup, it powers off if unplugged. Nothing i've done so far had changed it. It never bootloops, just off and on. If its unplugged and i try to boot it, it starts for a second and then just fizzles out. Should i maybe try a complete wipe again? Maybe i should sign on to google plus? Am i grasping at straws?
Click to expand...
Click to collapse
I meant, maybe i shouldn't sync to google after a complete wipe so as to avoid all apps?

hillsfr said:
I meant, maybe i shouldn't sync to google after a complete wipe so as to avoid all apps?
Click to expand...
Click to collapse
Yes exactly, do a full format with fastboot
Flash latest stock firmware/software (including bootloader) and reboot but don't sign in
Then test, if it works then sign in and wait and test, if still working then restore apps and data and test.
But if after complete format and install of stock everything your issue still persists then it may be safe to chalk it up to hardware... Which may prove trickier to troubleshoot
Best of luck!

Related

Display is Reversed!

After several unsuccessful attempts to mount 3.1 on my Xoom, something seems to have caused the display to reverse. That is, the display is a mirror image of what it should be! This starts with the boot-up image of the Motorola Icon and carries all the way through till it's up. Several restarts have failed to resolve it, and it has me in a bit of a panic.
Have I just bricked my Xoom? Has this happened to others? Ideas? Suggestions? There's nothing on it that I have to save, so I could re-flash it, but I am not sure if/how to do this.
Many thanks in advance for any suggestions/fixes!
Phillip
Its not bricked if it boots...
That is strange though. May have to reflash stock images.
Try bringing everything back to stock?
Thanks, I would be happy to do that, but it's kind of hard to do it with everything backwards!
I had to hold my cell phone up to the screen to (barely) read the mirror image text in the System Recovery. But, when I selected (what I thought was) the 'Restore Defaults' option in the blue recovery area, I got another screen with a list of selections that I also couldn't read! Rather than choose the wrong thing, I opted to reboot, but no luck, alas.
Gr3yghost said:
Thanks, I would be happy to do that, but it's kind of hard to do it with everything backwards!
I had to hold my cell phone up to the screen to (barely) read the mirror image text in the System Recovery. But, when I selected (what I thought was) the 'Restore Defaults' option in the blue recovery area, I got another screen with a list of selections that I also couldn't read! Rather than choose the wrong thing, I opted to reboot, but no luck, alas.
Click to expand...
Click to collapse
No push the images using adb
I figured it could be done. Could you please point me to a thread explaining how to push images using adb?
Not sure if you have 3g or wifi but here are the 3g instructions
http://forum.xda-developers.com/showthread.php?t=988942
djsaad1 said:
Not sure if you have 3g or wifi but here are the 3g instructions
http://forum.xda-developers.com/showthread.php?t=988942
Click to expand...
Click to collapse
That's great, thanks for the info. I'll have to do this later today when I am at a PC (now at a Mac).
Any ideas about why this would happen in the first place? I've looked through the forums but haven't seen any other threads about this issue. It may be fixable with a reflash, but it sure was 'easy' to 'break' today without even knowing why...:^(
djsaad1 said:
Not sure if you have 3g or wifi but here are the 3g instructions
http://forum.xda-developers.com/showthread.php?t=988942
Click to expand...
Click to collapse
I have the 3G model. Looking at the instructions in that post, I have to admit I am not sure about a few (like most!) of the steps. It may become more apparent when I am doing it, but right now I am not clear as to where these steps take place.
[edit] Ok, I have just done some more reading and it appears I have quite a bit of work ahead of me, and that's just to get back to square one. Dang this was too easy to mess up!
I am confused now, I figured you would have adb installed since you already tried upgrading to 3.1 a few times.
All you need to do is flash the stock system, recovery, and boot image files.
djsaad1 said:
I am confused now, I figured you would have adb installed since you already tried upgrading to 3.1 a few times.
All you need to do is flash the stock system, recovery, and boot image files.
Click to expand...
Click to collapse
Sorry for the confusion, but I haven't been using adb. I was trying to install the update manually with a usb data stick and the microsd cord that came with my Xoom. That's how I got myself into this pickle...way too easy it was!
Sent it back
Thanks to all who helped here. I ended up taking it back to Verizon and asking for a replacement. This they did, and even shipped it overnight at no charge (though I had to ask them to do that--they were going to charge me). The fellow at the counter was as perplexed as me. Apparently this is not a common problem.

Stuck in read only?

To keep it relatively short, for whatever reason, my recovery is corrupted or broken. I had flashed clockwork, did a full backup, and have my UID and all of that stuff. Today, sometime after I started downloading files from Google Music, my tablet restarted, and now programs and applications constantly crash, presumibly since the tablet seems to be locked in Read Only mode. Chmod seems to work, but then nothing actually changes. Ive been able to seemingly uninstall root, and reinstall it, but its a hassle, and I dont think that works correctly.
Obviously, without recovery, I cannot flash anything, and without being able to write correctly, I cant get it to update. Acer Recovery says that it is successful, but it is not, and simply reboots the tablet.
One user described it as "GroundHog Day" as the tablet returns to the state it was in previously.
So yeah, I need help getting recovery back and working again, so I can either wipe this rom or do something entirely different. Thanks!
Edit: I should say, the stock Acer recovery seems like it wants to load, then it errors with:
Secure Boot: image SOS checksum fail
But none of the fixes work, nor does hitting volume up and the toggle to clear user data.
Borman18 said:
To keep it relatively short, for whatever reason, my recovery is corrupted or broken. I had flashed clockwork, did a full nandroid backup, and have my UID and all of that stuff. Today, sometime after I started downloading files from Google Music, my tablet restarted, and now programs and applications constantly crash, presumibly since the tablet seems to be locked in Read Only mode. Chmod seems to work, but then nothing actually changes. Ive been able to seemingly uninstall root, and reinstall it, but its a hassle, and I dont think that works correctly.
Obviously, without recovery, I cannot flash anything, and without being able to write correctly, I cant get it to update. Acer Recovery says that it is successful, but it is not, and simply reboots the tablet.
One user described it as "GroundHog Day" as the tablet returns to the state it was in previously.
So yeah, I need help getting recovery back and working again, so I can either wipe this rom or do something entirely different. Thanks!
Edit: I should say, the stock Acer recovery seems like it wants to load, then it errors with:
Secure Boot: image SOS checksum fail
But none of the fixes work, nor does hitting volume up and the toggle to clear user data.
Click to expand...
Click to collapse
Are you using Iconia Root to root and unroot? Let's start there?
Off to bed, I'm sure one of the other "late nighters" will be able to help you.
My only question is that you stated you installed CWM, if so, why didn't you create a full backup with it instead of nandroid?
Yes, I used Iconia Root to do the deed, which has worked since I got the unit a week ago until today.
And thats what I mean in terms of backing up, my apologies (im just use to calling it Nandroid for whatever reason).
I have no idea how the recovery got wiped though.
Borman18 said:
Edit: I should say, the stock Acer recovery seems like it wants to load, then it errors with:
Secure Boot: image SOS checksum fail
But none of the fixes work, nor does hitting volume up and the toggle to clear user data.
Click to expand...
Click to collapse
I STRONGLY recommend you read the following thread.
http://forum.xda-developers.com/showthread.php?t=1129873
Looks like you flashed something and didn't run "itsmagic".
Ive tried that, and no go. As far as I can remember, I havent flashed anything in days, since updating to the latest update a few days ago. And its been fine since then, until today. I started downloading google music stuff, went to the bathroom, came back and my tablet was off. I can give it another go though.
If it wasn't clear, I can definitely boot, its just with all those errors
But you get a checksum error, right? Have you gone through the steps in that thread that detail how to fix the checksum error?
If so, I suggest you contact sc2k.
Correct, if I hold the volume - and power, it gives that error. Just ran through the steps for the "<CASE 1> SOS checksum error" again to be safe, and its the same. I PM'ed him earlier (maybe twice..), but I can only assume he's sleeping, so I was just trying to see if anyone has any ideas.
Edit: from my ADB Shell session, just to show that it seems to want to work anyway? But of course, the same old..
# /data/local/itsmagic
Some magic trick by @sc2k on xda
it tricks the bootloader to run any kernel you want.
Thx @Acer for making this so easy.. why did you say the BL is locked if it isn't?
USE AT YOUR OWN RISK!
Done. Have fun!
# exit
Your best option is to wait until sc2k gets back to you, then. Don't worry. He's a fairly nice guy and has helped plenty of folks sort out similar issues on their tabs. Just remember to beer him afterwards!
Of course Thanks for your help regardless, I figured it was worth a shot. Of course, it does this right before I am to go camping for a few days (I had some maps and stuff on here to use as backup).
Borman18 said:
Of course Thanks for your help regardless, I figured it was worth a shot. Of course, it does this right before I am to go camping for a few days (I had some maps and stuff on here to use as backup).
Click to expand...
Click to collapse
AH, y'see, now you know what caused it in the first place! You tempted the fates! Never tempt the fates, for they are mean and sadistic beings that just LOVE to screw with folks right before they go camping.
I hope sc2k is able to help you out.

Black screen after SU Binary update

Hi everyone, I've searched and tried some solutions for this but the problem is the display is permanently black, not even samsung logo is displayed on bootup.
My GT-i9505 has a CWM recovery installed and a custom ROM, and today it notified me that SU Binary needs to be updated, so I updated it and it said Success, recommend to reboot, which I did.
It seemed to boot up but the display was constantly black. Manually turned it off by holding down power button, then restarted but still nothing.
I have Odin and samsung drivers etc, just not sure if I should try and flash a stock/new Custom ROM from Odin or if theres an easier way to do it (maybe someone can guide me thru the CWM recovery and be my eyes since my screen is Black?)
Please and thank you.
First of all, you better switch to TWRP.
Second, maybe try flashing a SuperSU zip through the recovery.
If that doesn't work, then try dirty flashing your current rom again.
GDReaper said:
First of all, you better switch to TWRP.
Second, maybe try flashing a SuperSU zip through the recovery.
If that doesn't work, then try dirty flashing your current rom again.
Click to expand...
Click to collapse
Thanks for the goble-de-goop, I have no idea what you are saying (this is n00b friendly forum topic!) and how can I even try that when there's nothing but blackness on my screen?
It is booting and running, touch is working etc but I'm completely blind. Can someone please try to help with n00b friendly suggestions, will flashing a new Custom ROM work? And I'd like to know what has happened after the SU binary update that caused screen/backlight to become non-functional...
Just to point out, I'm not being rude I am being up-front, the first reply I get from here is exactly what I expected, not n00b friendly but more of a suggestion from a nerd who wants to show the other readers that he really 'knows his stuff', however un-useful it is.
I know a little but not enough to solve this on my own, I'm hoping someone out there see's this and unselfishly suggests something without turning it into debate about n00bs not asking the right questions in the right place at the right time!
My phone doesn't work, I need it to work, stupid SU binary update has screwed it, please help!
Pandemic_ said:
Thanks for the goble-de-goop, I have no idea what you are saying (this is n00b friendly forum topic!) and how can I even try that when there's nothing but blackness on my screen?
It is booting and running, touch is working etc but I'm completely blind. Can someone please try to help with n00b friendly suggestions, will flashing a new Custom ROM work? And I'd like to know what has happened after the SU binary update that caused screen/backlight to become non-functional...
Just to point out, I'm not being rude I am being up-front, the first reply I get from here is exactly what I expected, not n00b friendly but more of a suggestion from a nerd who wants to show the other readers that he really 'knows his stuff', however un-useful it is.
I know a little but not enough to solve this on my own, I'm hoping someone out there see's this and unselfishly suggests something without turning it into debate about n00bs not asking the right questions in the right place at the right time!
My phone doesn't work, I need it to work, stupid SU binary update has screwed it, please help!
Click to expand...
Click to collapse
...err...wow...
do you have a HDMI adaptor cable aka MHL adaptor or a chromecast type device at home ? it maybe that your screen has just died and that it's nothing to do with the binary (if it's booting normally albeit with a blank screen).
_neutron_ said:
...err...wow...
Click to expand...
Click to collapse
Starting to think XDA is not the right place to ask for help...
3mel said:
do you have a HDMI adaptor cable aka MHL adaptor or a chromecast type device at home ? it maybe that your screen has just died and that it's nothing to do with the binary (if it's booting normally albeit with a blank screen).
Click to expand...
Click to collapse
Good idea, I do have chromecast but will need mini HDMI cable/adaptor to check. Although it would be massive odds against random screen death, since it was immediately after reboot from SU binary.
Thanks for the intelligent reply, glad to see there are still some helpful people here.
if you can borrow a lead and your screen is being mirrored you can download an image file of TWRP and flash it with flashify from the store. I doubt screen mirroring works from the recovery
http://play.google.com/store/apps/details?id=com.cgollner.flashify
unzip the attached file and copy it to your SDcard then find it within the flashify app...
Awesome OK that gives me a starting point TY. When I connect the MHL adapter will it mirror automatically or will I have to try to blindly press the mirror symbol? I haven't used an MHL adapter/cable before. If it works then I'll use Flashify and hope it restores the phone screen.
if it's going to work it will work without any selecting of options, it's automatic...
If the you run out of solutions, you could flash a stock ROM back to your phone as this will bring the phone back to the factory settings; however, you will lose your data and installed apps.
If you decide to flash back to stock using Odin, I suggest launching Odin, uncheck everything except f.reset time, connect the phone in download mode, flash the rom, when you see the word "reset" in the status window, remove the USB cable from the phone, remove the battery, wait 5 seconds and replace the battery, boot into recovery, perform a factory reset, and reboot. Be sure to use the stock firmware from sammobile.com for your phone.
Pandemic_ said:
Thanks for the goble-de-goop, I have no idea what you are saying (this is n00b friendly forum topic!) and how can I even try that when there's nothing but blackness on my screen?
It is booting and running, touch is working etc but I'm completely blind. Can someone please try to help with n00b friendly suggestions, will flashing a new Custom ROM work? And I'd like to know what has happened after the SU binary update that caused screen/backlight to become non-functional...
Just to point out, I'm not being rude I am being up-front, the first reply I get from here is exactly what I expected, not n00b friendly but more of a suggestion from a nerd who wants to show the other readers that he really 'knows his stuff', however un-useful it is.
I know a little but not enough to solve this on my own, I'm hoping someone out there see's this and unselfishly suggests something without turning it into debate about n00bs not asking the right questions in the right place at the right time!
My phone doesn't work, I need it to work, stupid SU binary update has screwed it, please help!
Click to expand...
Click to collapse
Since you said you have CWM recovery and a rom installed I assumed you would knew how to flash stuff. Unless they were flashed by somebody else?
Anyway, flashing SuperSU.zip is as easy as googling for the zip then boot into recovery and flash the zip file.
Unless the recovery is dark too. Then that's a problem.
And flashing the rom again is done the same way. No need for TVs and chromecasts.
Theoretically, flashing the SuperSU.zip should work, as it replaces the binaries.
Flashing the rom should work too. Unless you have a dead screen. Then no software can fix it.
When you're using apps that modify system files things like this can happen. Something may have went wrong during the update.
@GDReaper he's already said "how can I even try that when there's nothing but blackness on my screen?" to your suggestion of flashing via recovery so MHL will help him
1) to see if the phone is running normal minus the screen
2) to replace CWM as you suggested without using recovery (which he won't be able to do even with MHL).
3mel said:
@GDReaper he's already said "how can I even try that when there's nothing but blackness on my screen?" to your suggestion of flashing via recovery so MHL will help him
Click to expand...
Click to collapse
So I probably misunderstood him. He said it is booting and so I thought that, during the booting, the screen works, and only when you are about to go into the OS the screen is black (As it happened to me before). My bad.
If the screen is black during the whole process it means the screen is busted. And it was probably just a coincidence, as I don't really see how updating the su binaries can damage the screen.
GDReaper said:
So I probably misunderstood him. He said it is booting and so I thought that, during the booting, the screen works, and only when you are about to go into the OS the screen is black (As it happened to me before). My bad.
If the screen is black during the whole process it means the screen is busted. And it was probably just a coincidence, as I don't really see how updating the su binaries can damage the screen.
Click to expand...
Click to collapse
Ok thanks man, it's dark in recovery too unfortunately. Will update again after trying the MHL cable. :good:
Pandemic_ said:
Ok thanks man, it's dark in recovery too unfortunately. Will update again after trying the MHL cable. :good:
Click to expand...
Click to collapse
Ok. Then it is definitely a screen problem. Changing software won't fix it.
You have to get a new screen.
I've tried the cable, no output to HDMI though. Phone is operating but in complete black screen from power on. Have tried to tap the screen mirroring button blindly (by touching all the top system buttons one by one) but no change. This leads me to think it is a software/firmware issue, somehow the SU binary has affected graphics output???
So my only chance now is try to flash using Odin? I have downloaded a new Custom ROM, ResurrectionRemix-M-v5.6.4-20160223-jfltexx but I think I can only flash that one using recovery which will be difficult blind, unless someone can give me precise button sequence. Unfortunately I can't remember exactly what recovery I have on there, but I think it may be the touch version...
I flashed TWRP using Odin no probs, but still no use as screen is still blank from power on.
I was going to revert to stock first but sammobile.com downloads at only 15kb/s so I'm not waiting 2 days for that 1.5gb download.
Can someone please give me a link to a good download for my GT-i9505, that I can flash with Odin. I want a light Custom ROM but if not possible to flash from PC then I'll try stock first.
Thanks,
Hi guys, I have a similar problem. I had a notification saying I need to "Update the #SU Binary". There was issues with the update, it gave me the option of restarting or trying the update again. I selected to try the update again. It failed again and now the screen is black with constant error messages, saying "Unfortunately, Galaxy Apps has stopped", "Unfortunately, S Health has stopped". Pretty much the same error message recurring with every app that would normally run on start up, then the phone just reboots itself every 5 minutes after the error messages have all done a round. I am desperate to recover the data on the phone.
Pandemic_ said:
I flashed TWRP using Odin no probs, but still no use as screen is still blank from power on.
I was going to revert to stock first but sammobile.com downloads at only 15kb/s so I'm not waiting 2 days for that 1.5gb download.
Can someone please give me a link to a good download for my GT-i9505, that I can flash with Odin. I want a light Custom ROM but if not possible to flash from PC then I'll try stock first.
Thanks,
Click to expand...
Click to collapse
SamFirm should speed things up.
---------- Post added at 07:37 AM ---------- Previous post was at 07:34 AM ----------
leNoobe said:
Hi guys, I have a similar problem. I had a notification saying I need to "Update the #SU Binary". There was issues with the update, it gave me the option of restarting or trying the update again. I selected to try the update again. It failed again and now the screen is black with constant error messages, saying "Unfortunately, Galaxy Apps has stopped", "Unfortunately, S Health has stopped". Pretty much the same error message recurring with every app that would normally run on start up, then the phone just reboots itself every 5 minutes after the error messages have all done a round. I am desperate to recover the data on the phone.
Click to expand...
Click to collapse
There isn't much you can do. Backup user data and factory reset.

Help!! my Angler is dead (bootloop)

I need help, my phone went into a Bootloop. I have tried to flash the factory image (7.0 and 6.0.1) using NRT and manually and still does not pass the Google logo. It does not let me enter the recovery, it only restarts continuously. When flashing the factory image did not give me any error, even the computer detects it in fastboot mode.
All this happened when I was about to open an application and suddenly I shut down and began to restart continuously. I had using android 7.0 stock.
Exact thing happened to me and I flashed both 7 and 6.0.1 and wiped data and caches multiple times.. nothing seems to work.. any ideas?
Tried everything but still bootloops.
Same thing here, although I was on a 7.1 build. There must be a flaw that can cause this to happen in recent build(s), I was trying to share a picture and it froze and bricked like this suddenly. I tried every combination of formatting and flashing stock images and whatnot but no luck.
Seanmiz said:
Same thing here, although I was on a 7.1 build. There must be a flaw that can cause this to happen in recent build(s), I was trying to share a picture and it froze and bricked like this suddenly. I tried every combination of formatting and flashing stock images and whatnot but no luck.
Click to expand...
Click to collapse
Your Nexus 6P uses Samsung eMMC doesn't?
I've seen countless threads here and on reddit about this.
My phone hard bricked last week and I suspect the Samsung emmc is to blame, too many people are having the exact same issue without a solution in sight. I am absolutely unable to access the recovery or anything on the emmc for that matter.
See if you're still covered under warranty (mine was 5 days past its warranty, and Google refused to help), otherwise you're SOL. I think we need to make some noise about it and have AP or another site pick up on this.
darksmartz said:
Your Nexus 6P uses Samsung eMMC doesn't?
Click to expand...
Click to collapse
I believe it was Samsung, yes. I RMA'd it right away after exhausting all flashing efforts.
darksmartz said:
Your Nexus 6P uses Samsung eMMC doesn't?
Click to expand...
Click to collapse
How do I know if my 6p uses Samsung eMMC? What is this, btw?
Edit
Nevermind. I just figured out. Mine is Toshiba, btw.
Rafsxd said:
How do I know if my 6p uses Samsung eMMC? What is this, btw?
Edit
Nevermind. I just figured out. Mine is Toshiba, btw.
Click to expand...
Click to collapse
how did you find this out ? would be nice to tell people so they can check to find out if they will be at risk
brichardson1991 said:
how did you find this out ? would be nice to tell people so they can check to find out if they will be at risk
Click to expand...
Click to collapse
You can find this information on the Bootloader screen listed under eMMC about halfway down the list.
Same problem, samsung memory here
Same for me too,i send my phone back to amazon
Envoyé de mon HUAWEI VNS-L31 en utilisant Tapatalk
Mine uses a Toshiba eMMC and bootloops nevertheless. Not sure if this is actually what's causing it. At this point my only thought is that there was a bad batch of devices as so far no one could find a pattern on what exactly causes the bootloops.
seco2004 said:
Mine uses a Toshiba eMMC and bootloops nevertheless. Not sure if this is actually what's causing it. At this point my only thought is that there was a bad batch of devices as so far no one could find a pattern on what exactly causes the bootloops.
Click to expand...
Click to collapse
Yeah, it doesn't actually seem to be related to eMMC brand. It was very strange, because after it happened, I was able to flash 7.0 stock and regain OS use on a very touchy level. I couldn't access USB connectivity, the home button didn't work most of the time, and if I tried to do too much with it, it would go right back into infinite bootloops. After accomplishing this 2 or 3 times, I could never again get back into the OS.
I could wipe and flash all of the partitions with no errors, I could always get into stock recovery, but TWRP never worked.
Was anyone *not* on the November patch level of v7.0+?
Seanmiz said:
Yeah, it doesn't actually seem to be related to eMMC brand. It was very strange, because after it happened, I was able to flash 7.0 stock and regain OS use on a very touchy level. I couldn't access USB connectivity, the home button didn't work most of the time, and if I tried to do too much with it, it would go right back into infinite bootloops. After accomplishing this 2 or 3 times, I could never again get back into the OS.
I could wipe and flash all of the partitions with no errors, I could always get into stock recovery, but TWRP never worked.
Was anyone *not* on the November patch level of v7.0+?
Click to expand...
Click to collapse
When this first started for me I was on the latest beta build, October security patch.
Same issue here - 64MB Samsung memory.
Google support are aware of the issue, they sent out a replacement no questions asked. For some reason, the guy suggested (but he said unofficially) tapping on the power button. Anybody have any clue why this would be relevant?
Regardless, I'm in a position where I can access fastboot, but nothing else. Can anyone think of any data recovery options at this point?
---------- Post added at 12:26 PM ---------- Previous post was at 12:20 PM ----------
To follow up on my previous post - just before I hit a reboot that threw me into the bootloop, I encountered a hard freeze. I received a bug report after the hard freeze and this is now sitting in my gmail drafts. Would this bug report have any pertinent information here?
thisisgil said:
For some reason, the guy suggested (but he said unofficially) tapping on the power button. Anybody have any clue why this would be relevant?
Click to expand...
Click to collapse
I know exactly why it's relevant!
He's trying to make sure it's not a shoddy power button. My Galaxy SII back in the day had a common power button failure where it would think that you are just constantly hitting/holding the power button if you even breathed on it. My phone would bootloop or suddenly reboot constantly because it was getting power button commands from the poor quality button. Better quality buttons along with other methods of locking/unlocking the phone to reduce power presses have mostly prevented this sort of thing these days.

[RE-OPENED] Possibly Bricked My Phone. AGAIN.

Edit: My phone is miraculously recovered, see last post for details. Big thanks to everyone throwing in suggestions! :highfive::good:
Edit 2: Here we go again... Had my phone set up for a day and after installing the "App Systemizer" Magisk module, the restart upon booting is back. Please help, is magisk causing this??
So, I'm reaching out because I'm now at a loss. I have no other ideas as to how I could fix my phone.
Background:
A few days ago, I was setting my alarm for work in the morning and I noticed the UI was extremely sluggish. I then locked my phone with the lock button and a notification saying "Powering down..." came up and proceeded to shut off. At this point, I knew I should re-flash my ROM/boot.img first. Didn't help, every boot up ended in the same "Powering down..." message and shutting down within 15 seconds of unlocking the device. At this point, I think to fully wipe and revert to stock. Now, I try to install the latest stock OOS via fastboot. Same result as before when I booted after the fastboot install. And this is where it ended... I tried to use the MSM tool and the device went BLACK with no response after that.
What I've tried:
- fastboot
-MSM Tool
- randomly pressing/holding all physical buttons in every order
- leaving the device plugged in to charge overnight
Conclusion:
Any suggestions other than what I've tried would greatly be appreciated. If, by some chance, my phone is truly bricked... would anyone know about whether T-Mobile would replace the device for me if I act clueless as to what happened to my device? lol, I'm on the Jump! plan, so this phone isn't even paid off yet.
Thanks!
Only time I saw this "powering down" issue was when I updated my phone without disabling my Magisk modules. That time I just removed the module using TWRP and the phone booted.
When you used the MSM tool did it complete successfully? It should take around 5 minutes to restore. Mine took 302 seconds on the dot. That should clear out any and all software issues. If the problem still persists after a successful MSM restore then my thoughts would be hardware damage.
I assume your battery is still working (?), and you can't reach TWRP either?
Have you tried this https://www.getdroidtips.com/oneplus-6t-black-screen-death-issue/ ?
When my 6T didn't respond at all. It would stay black no matter what but I knew it was charged. All I did was hold volume up and the power button for a good 15 to 30 seconds. Then it booted up
Sent from my [device_name] using XDA-Developers Legacy app
Car Transport in mumbai
Car Transport In Mumbai[/URL]
Hey u...I also had the same issue...SHUTTING DOWN...in every boot....and I had fixed it....anyways if u have fixed it ...m glad....if not whatsapp or telegram me on +918898340211
Jager said:
Only time I saw this "powering down" issue was when I updated my phone without disabling my Magisk modules. That time I just removed the module using TWRP and the phone booted.
When you used the MSM tool did it complete successfully? It should take around 5 minutes to restore. Mine took 302 seconds on the dot. That should clear out any and all software issues. If the problem still persists after a successful MSM restore then my thoughts would be hardware damage.
Click to expand...
Click to collapse
MSM didn't even pick up my device... it said something along the lines of "No communication"
F5:ed said:
I assume your battery is still working (?), and you can't reach TWRP either?
Have you tried this https://www.getdroidtips.com/oneplus-6t-black-screen-death-issue/ ?
Click to expand...
Click to collapse
Thanks for the suggestion! Unfortunately, all steps were tried before seeing this post and didn't help.
i7vSa7vi7y said:
When my 6T didn't respond at all. It would stay black no matter what but I knew it was charged. All I did was hold volume up and the power button for a good 15 to 30 seconds. Then it booted up
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
This is important... but did not help me... initially.
sanjeev7 said:
Hey u...I also had the same issue...SHUTTING DOWN...in every boot....and I had fixed it....anyways if u have fixed it ...m glad....if not whatsapp or telegram me on +918898340211
Click to expand...
Click to collapse
Well boys, she's up and running again!
Here's what happened:
- I left my phone on the stock charger (wall-block and cord) to make sure the battery wasn't just dead. This resulted in nothing, still no response from the device.
- Early in the morning, while getting ready for work, I continued to press all physical buttons in any and every order as well as holding different combinations of the buttons. Nothing.
- Gave up, took it off the charger, and tossed the damned thing to the side. I took my iPhone X to work and hated every minute of it lmao.
- I then get off work and decide to mash the physical buttons in a half fit-of-rage and half last-ditch-effort.. and BOOM! The screen flashes with a screen saying the battery is dead in a few different languages.
(I never plugged a device in to charge so fast... lol)
At this point, I decided to fastboot the latest stock OOS (.13) to both A/B partitions and she's like brand new!!!! I spent the day rooting and reinstalling everything today and I'm honestly relieved. :victory: All of my data is lost... pics of my baby sister after just being born and of my fiance But order has been restored.
tl;dr - My phone is fixed, don't ever underestimate the power of button mashing! :good:
..Cory.. said:
MSM didn't even pick up my device... it said something along the lines of "No communication"
Click to expand...
Click to collapse
I suggest you re-read the thread on the MSM tool. It will always work unless there is physical damage to your device. The reason you got the "No communication" error is because you were not in the Qualcom bootloader mode or whatever, not fastboot and not TWRP, there is a third mode accessible by holding certain buttons while plugging in your phone to the computer, in this mode the screen does not light up or anything. Read the thread, the steps are in there. I guarantee that if you can get the MSM tool to restore your phone everything will be working on it.
I even tested the MSM tool once. I wiped all partitions on the phone including the boot partition. The MSM tool can always fix a Software issue.
Edit: Didn't see that you said it was fixed already. My message here is still valid though. Some day you will have to use the MSM tool so it's a good idea to get familiar with it.
Jager said:
I suggest you re-read the thread on the MSM tool. It will always work unless there is physical damage to your device. The reason you got the "No communication" error is because you were not in the Qualcom bootloader mode or whatever, not fastboot and not TWRP, there is a third mode accessible by holding certain buttons while plugging in your phone to the computer, in this mode the screen does not light up or anything. Read the thread, the steps are in there. I guarantee that if you can get the MSM tool to restore your phone everything will be working on it.
I even tested the MSM tool once. I wiped all partitions on the phone including the boot partition. The MSM tool can always fix a Software issue.
Edit: Didn't see that you said it was fixed already. My message here is still valid though. Some day you will have to use the MSM tool so it's a good idea to get familiar with it.
Click to expand...
Click to collapse
Well, like I said... I couldn't just change modes at will... I was legit stuck with the screen completely off and no response to any physical button being pressed. So as long as switching modes was impossible... so was the MSM tool. I read a F*CK-TON of threads before I posted this, I haven't seen anyone else post about being in my situation of not being able to boot into ANY kind of a mode... at all lol.
Bumping to ask for help again...
I had my phone all set up, stable OOS (.13) on both partitions. I installed the "App Systemizer" Magisk module in order to move an app to the system. When I rebooted after the module installation, the "Phone is rebooting..." message comes up after a few seconds post-boot and go straight to recovery every time.
I'm lost at this point. :/
You'd probably be better off seeking support in the mod thread.
..Cory.. said:
Bumping to ask for help again...
I had my phone all set up, stable OOS (.13) on both partitions. I installed the "App Systemizer" Magisk module in order to move an app to the system. When I rebooted after the module installation, the "Phone is rebooting..." message comes up after a few seconds post-boot and go straight to recovery every time.
I'm lost at this point. :/
Click to expand...
Click to collapse
Go to TWRP
go to file manager
Delete /data/adb/ *all files related to Magisk*
This will work
..Cory.. said:
Bumping to ask for help again...
I had my phone all set up, stable OOS (.13) on both partitions. I installed the "App Systemizer" Magisk module in order to move an app to the system. When I rebooted after the module installation, the "Phone is rebooting..." message comes up after a few seconds post-boot and go straight to recovery every time.
I'm lost at this point. :/
Click to expand...
Click to collapse
I have never read about a really bricked OP6T, there is always a solution (and use MsmDownloadTool if nothing else work....).
Now, when you already have "bricked" your phone once and fixed it, you are asking the community for help again... It's obvious to me that you are fiddling around with your device without any clue, and creates a mess for yourself. Why?
Stay outside what you do not understand, and stick to stock version only in the future.
To try to help you, I suggest you use MsmDownloadTool.
WOOOOOOOW.
So this whole time it was Magisk. I never knew about Magisk Manager for recovery. That thing is a MUST HAVE.
So what happened was the new Magisk update broke a few modules I use daily. After using MM to disable every module one-by-one, I found the culprit.
The thing that always gets me is the A/B partition BS. But I guess Magisk was really the pain in my ass!
Closing thread for good, thanks to everyone giving suggestions!!! :good:
Cablespider said:
You'd probably be better off seeking support in the mod thread.
Click to expand...
Click to collapse
Right, thank you! I just feel as if this section is less intrusive for noob questions haha
sanjeev7 said:
Go to TWRP
go to file manager
Delete /data/adb/ *all files related to Magisk*
This will work
Click to expand...
Click to collapse
Thank you! Used this to clean some of the files up when reinstalling the new stable update.
F5:ed said:
I have never read about a really bricked OP6T, there is always a solution (and use MsmDownloadTool if nothing else work....).
Now, when you already have "bricked" your phone once and fixed it, you are asking the community for help again... It's obvious to me that you are fiddling around with your device without any clue, and creates a mess for yourself. Why?
Stay outside what you do not understand, and stick to stock version only in the future.
To try to help you, I suggest you use MsmDownloadTool.
Click to expand...
Click to collapse
If you don't think I deserve help, move on to another thread! :good: No problems here though; I took advice I found helpful and I fixed my phone :victory:
I'm far from a noob though, this is just my first A/B parition device. I had an iPhone for years and was last active on XDA before Magisk was even released.We all need to brush up on the basics every once in a while, though!
..Cory.. said:
Right, thank you! I just feel as if this section is less intrusive for noob questions haha
Thank you! Used this to clean some of the files up when reinstalling the new stable update.
If you don't think I deserve help, move on to another thread! :good: No problems here though; I took advice I found helpful and I fixed my phone :victory:
I'm far from a noob though, this is just my first A/B parition device. I had an iPhone for years and was last active on XDA before Magisk was even released.We all need to brush up on the basics every once in a while, though!
Click to expand...
Click to collapse
Thank you for the arrogance.
I have already tried to help you (twice, in this your own thread). Your arrogant answer tells me that the iPhone-comfort zone suite you best.
In short: you act as an imbecile (since I have experience of you, and have "discussed" with you, before outside this thread).
So, sell your OP6t and buy an iPhone - problem solved.
F5:ed said:
Thank you for the arrogance.
I have already tried to help you (twice, in this your own thread). Your arrogant answer tells me that the iPhone-comfort zone suite you best.
In short: you act as an imbecile (since I have experience of you, and have "discussed" with you, before outside this thread).
So, sell your OP6t and buy an iPhone - problem solved.
Click to expand...
Click to collapse
That systemize tool is not very stable in my experience. There is two location's of system apps in my experience which is most always only about at least half correct a little less than half the time. Is that if you use something like MiXplorer and move the apk into either system apps or priv apps then reboot it is much easier to do than rely on scripts that may not be setup for the device you are using. It shouldn't take any longer than 25.89 seconds to manually move an app.
..Cory.. said:
WOOOOOOOW.
So this whole time it was Magisk. I never knew about Magisk Manager for recovery. That thing is a MUST HAVE.
So what happened was the new Magisk update broke a few modules I use daily. After using MM to disable every module one-by-one, I found the culprit.
The thing that always gets me is the A/B partition BS. But I guess Magisk was really the pain in my ass!
Closing thread for good, thanks to everyone giving suggestions!!! :good:
Click to expand...
Click to collapse
Download the magisk uninstaller zip , put it on your internal storage
So when magisk modules messing up with your boot
Go to twrp, flash the uninstaller zip , reboot to twrp, reflash magisk and then you're be able to boot again to your rom ..
F5:ed said:
Thank you for the arrogance.
I have already tried to help you (twice, in this your own thread). Your arrogant answer tells me that the iPhone-comfort zone suite you best.
In short: you act as an imbecile (since I have experience of you, and have "discussed" with you, before outside this thread).
So, sell your OP6t and buy an iPhone - problem solved.
Click to expand...
Click to collapse
Sorry, I forgot ur the internet law enforcement. Yes, sir! Please dont shoot! :HandsUp: :ShakingInFear: :Terrified: :NotReally: :WatchOut_InternetBadAss:
Jager said:
I suggest you re-read the thread on the MSM tool. It will always work unless there is physical damage to your device. The reason you got the "No communication" error is because you were not in the Qualcom bootloader mode or whatever, not fastboot and not TWRP, there is a third mode accessible by holding certain buttons while plugging in your phone to the computer, in this mode the screen does not light up or anything. Read the thread, the steps are in there. I guarantee that if you can get the MSM tool to restore your phone everything will be working on it.
I even tested the MSM tool once. I wiped all partitions on the phone including the boot partition. The MSM tool can always fix a Software issue.
Edit: Didn't see that you said it was fixed already. My message here is still valid though. Some day you will have to use the MSM tool so it's a good idea to get familiar with it.
Click to expand...
Click to collapse
The MSM Tool does not fix everything. The 6T I have is brand new was working fine until I installed LOS on A & B and deleted the persist partition. I have flashed the original stock rom as well as 3 other OOS roms. MSM Tool completes the flash no problem with no errors, but on every rom it only makes it to the boot screen and hangs. If the MSM Tool is supposed to fix this, then why isn't it getting fixed? I don't know what else to try to fix? Usually it fixes most problems for me, but on this occasion it is not.

Categories

Resources