Related
Hi guys, something strange happened, got my nexus 3 weeks ago and i right away unlocked bootloader, flashed custom recovery and rooted it, installed a few apps and everything was fine, day before yesterday while sending an email my phone got stuck and rebooted, took awhile and when it did i noticed the cell network being empty, i would press anything on the screen and it would do the same. So i downloaded the stock images and flashed everything according to section D of the topic http://forum.xda-developers.com/show....php?t=2010312 and boot took awhile finally it started and i got the welcome screen, clicked on English USA and again the cell network is empty and phone frooze in the first screen only, it rebooted and it boots up with a black screen and i get the message "process system isn't responding, OK or wait" and press ok or wait whichever and phone reboot or even if i try to press any of the options, its stuck. But bootloader works since i can do fastboot devices or fastboot reboot-bootloader, i can also boot into recovery which is CMW. This is getting frustrating and im confused, can anyone help me out here? Thanks
RMA time. Relock the bootloader and ship her off. If reloading the stock images doesn't fix it, it's likely hardware.
estallings15 said:
RMA time. Relock the bootloader and ship her off. If reloading the stock images doesn't fix it, it's likely hardware.
Click to expand...
Click to collapse
Isn't there anything else i can try before shipping it back or give up?
EDIT:
I pushed CM zip file via adb and it got pushed successfully and i even flashed it via CMW recovery and it even said complete and when i reboot the device its stuck on the Google screen and nothing else happens..
masantula said:
Isn't there anything else i can try before shipping it back or give up?
Click to expand...
Click to collapse
Gong back to all stock software with fresh flashes is the most extreme attempt at a fix, software wise. What else would you do?
Hmmm, true...this sucks, no other option...thanks
ok so i have 2 issues and i dont know how to fix them
i know how to fix the second one but the first one is when i reboot or start up the phone after doign all the root and all it still boots into ur phone is currupted on eatch boot, is there a fix that the phone goes to the LG screen and just boots normaly
te second issue is the static screen, i know the temp way is to have the second screen off or cover that sencer then turn off the screen but i think plashing boot2.img can fix that as i thnk i did it before and just stick with the first issue
LASERWOLF452 said:
ok so i have 2 issues and i dont know how to fix them
i know how to fix the second one but the first one is when i reboot or start up the phone after doign all the root and all it still boots into ur phone is currupted on eatch boot, is there a fix that the phone goes to the LG screen and just boots normaly
te second issue is the static screen, i know the temp way is to have the second screen off or cover that sencer then turn off the screen but i think plashing boot2.img can fix that as i thnk i did it before and just stick with the first issue
Click to expand...
Click to collapse
first one no known fix for the second flash this https://forum.xda-developers.com/v20/development/kernel-restock-stock-based-kernel-v20-t3556263
Ever find a fix for the first? I read that flashing the VS995 TWRP instead of the US996 on the VS995 during the rooting / bootloader unlock process would do away with the screen static. I tried this however my handset wont boot into recovery by hard keys the first attempt so im not sure if it worked. I ended up getting the first error with the corrupt FS and had to enter in passes 16 some times before it finally formatted and then let me back into the OS.
LASERWOLF452 said:
i know how to fix the second one but the first one is when i reboot or start up the phone after doign all the root and all it still boots into ur phone is currupted on eatch boot, is there a fix that the phone goes to the LG screen and just boots normaly
Click to expand...
Click to collapse
noidodroid said:
Ever find a fix for the first?
Click to expand...
Click to collapse
While there is no real fix for that warning delay, some have managed to replace the warning logo with the LG logo to make it look nicer:
https://forum.xda-developers.com/v20/how-to/guide-hide-unlocked-bootloader-warning-t3879658
C D said:
While there is no real fix for that warning delay, some have managed to replace the warning logo with the LG logo to make it look nicer:
https://forum.xda-developers.com/v20/how-to/guide-hide-unlocked-bootloader-warning-t3879658
Click to expand...
Click to collapse
Awesome. You are reading my mind! heh. I was going to give that a try. Thanks kindly for the link.
As for the second issue i have found a way to fix this but trying to remember the complete process I did and single out what more than likely was the actual fix so nobody has to replicate everything i did. No static at all whatsoever and boots clean. Only there will be issues with booting into stock OS so you will need to flash a custom ROM. Ill create a thread when i get a minute.
Was just using it today morning and it froze up on me... I held the power button and forced shut it down. Then I tried booting it up. It goes to the warning screen (Cause I have unlocked my phone.) Then it takes me to the google white logo screen thing and yeah, just turns off, back to the warning screen then back to the google screen. I was rooted with twrp recovery. Phone wont even boot into recovery, just keeps repeating those steps. I tried using the nexus toolkit as well, to boot into a temporary recovery, no luck. I even used the bricked/wont turn setting. Which just flashed all the stock images into the phone. But same thing, over and over again.
Seems like i have the bootloop death and nothing seems to bring it up. My question is how do I go about contacting google and trying to get a different device? Or something they can help me with? I brought it from amazon (my dad did.) So no idea what to do... Is there a email or a contact no?
bump
xringo said:
Was just using it today morning and it froze up on me... I held the power button and forced shut it down. Then I tried booting it up. It goes to the warning screen (Cause I have unlocked my phone.) Then it takes me to the google white logo screen thing and yeah, just turns off, back to the warning screen then back to the google screen. I was rooted with twrp recovery. Phone wont even boot into recovery, just keeps repeating those steps. I tried using the nexus toolkit as well, to boot into a temporary recovery, no luck. I even used the bricked/wont turn setting. Which just flashed all the stock images into the phone. But same thing, over and over again.
Seems like i have the bootloop death and nothing seems to bring it up. My question is how do I go about contacting google and trying to get a different device? Or something they can help me with? I brought it from amazon (my dad did.) So no idea what to do... Is there a email or a contact no?
Click to expand...
Click to collapse
I have exactly the same problem. I was on O dev preview 3 and today it bootlooped randomly. Now it wont go beyond google screen. Ive tried flashing factory images of N and O preview 3, with and without wiping. Ive also tried relocking the bootloader, relfashing stock recovery and twrp....
NoobInToto said:
I have exactly the same problem. I was on O dev preview 3 and today it bootlooped randomly. Now it wont go beyond google screen. Ive tried flashing factory images of N and O preview 3, with and without wiping. Ive also tried relocking the bootloader, relfashing stock recovery and twrp....
Click to expand...
Click to collapse
Do you get any errors when you fastboot FORMAT sytem, userdata and cache?
NoobInToto said:
I have exactly the same problem. I was on O dev preview 3 and today it bootlooped randomly. Now it wont go beyond google screen. Ive tried flashing factory images of N and O preview 3, with and without wiping. Ive also tried relocking the bootloader, relfashing stock recovery and twrp....
Click to expand...
Click to collapse
Yeah same issue with me. Download a bunch of images and tried flashing it, no luck. Can't even go to any other screen other than the google white logo and bootloader. This sucks, wish I never brought this piece of ****. So much issues with this phone.
v12xke said:
Do you get any errors when you fastboot FORMAT sytem, userdata and cache?
Click to expand...
Click to collapse
No, I did not attempt that. Somehow miraculously, when I was chatting with customer support, the phone booted in after about 2 hours of bootlooping. However, I had wiped it by then. I read somewhere about allowing the bootlooping phone to bootloop for sometime. Then it would get in and we would have to change some kernel settings related to the big CPU cores.
I did no such thing , however, I do not know when the problem will reoccur.
Also had the bootloop when flashing N2G48B. Flashed N2G47W and now boots again.
hi guys,
so the nexus 6p i had got the oreo ota update and after a couple of day it restarted and since then stuck on google logo(bootloop).
it only goes to fastboot mode,
download mode is disabled,
recovery is not there of any kind, meaning i cant boot to recovery mode.
every things gone on it can i do something to get it back, oem unlocking was not turned on in it. developer option was never turned on. bootloader is also locked.
i am in a big trouble guys please help me if there is a way.
alijaved154 said:
hi guys,
so the nexus 6p i had got the oreo ota update and after a couple of day it restarted and since then stuck on google logo(bootloop).
it only goes to fastboot mode,
download mode is disabled,
recovery is not there of any kind, meaning i cant boot to recovery mode.
every things gone on it can i do something to get it back, oem unlocking was not turned on in it. developer option was never turned on. bootloader is also locked.
i am in a big trouble guys please help me if there is a way.
Click to expand...
Click to collapse
Tried factory reset and reboot?
tropical cactus said:
Tried factory reset and reboot?
Click to expand...
Click to collapse
as i mentioned there is no recovery mode on it. its red and i cant boot to it. it returns back to fast boot mode dude
alijaved154 said:
as i mentioned there is no recovery mode on it. its red and i cant boot to it. it returns back to fast boot mode dude
Click to expand...
Click to collapse
You can select factory reset by pressing the volume button . Factory reset will come up. Select by pressing power button and press again to wipe.
tropical cactus said:
You can select factory reset by pressing the volume button . Factory reset will come up. Select and wipe.
Click to expand...
Click to collapse
in fastboot only the options are:
start
barcodes
recovery
bootloader
alijaved154 said:
in fastboot only the options are:
start
barcodes
recovery
bootloader
Click to expand...
Click to collapse
I have factory reset as an option. Not sure why you don't.
tropical cactus said:
I have factory reset as an option. Not sure why you don't.
Click to expand...
Click to collapse
in fastboot? i dont have it i dont know what hapoened to it
alijaved154 said:
in fastboot? i dont have it i dont know what hapoened to it
Click to expand...
Click to collapse
Try reboot bootloader and scroll through options again.
tropical cactus said:
Try reboot bootloader and scroll through options again.
Click to expand...
Click to collapse
comes back to the same screen but will still try today
alijaved154 said:
comes back to the same screen but will still try today
Click to expand...
Click to collapse
Very strange, unless it only shows up if you enable developer options before.
Same problem after update
Exactly same problem after update, no way to factory reset phone, developer option was unlocked
Erroras said:
Exactly same problem after update, no way to factory reset phone, developer option was unlocked
Click to expand...
Click to collapse
you are not alone...?
Same issue on one I have my hands on. This could get interesting.
From fastboot can anything be pushed/flashed like a previous actually functional firmware? Is there other specific software to do so? Only got my hands on the defective non functional device today but I'm planning and scheming a fix if possible.
One thing is really interesting. Why only after this update???? Why not after update from 6 to 7 then 7 to 7.1 and after 7.1 to 8.0. I think Google or Huawei is cheating us and forcing us to buy Google pixel.
I also have this issue (I'm using a nexus 5x, but this thread is the closest to my issue I've found), but it came incrementally. First, I started getting reboots every 20m or so, while doing normal phone things (reading, mostly). Then it started getting into bootloops that were 2-3 boots long, and would then work normally for the 20m mentioned above. I tried a factory reset, but it just got worse, and now either reboots on the Google logo or during the Android animation. My fastboot menu only has the regular "Start" as green. The only other options are Restart Bootloader, in red, and Recovery mode, also in red. Power off is there, obviously, but that's it. It started happening yesterday, and worsened to its current point within only a few hours.
Well. I have just joined the club. What is going on with that?
Happened to me today and I was using the latest build of SuperXE 6P.
Guys! lol
1. Dev options in ROM is same old. Settings/about and tap build 10 times to see count down to developer. Back to settings. In there for OEM unlock
2. Factory reset can be done any number of ways.
a. In ROM. Settings/backup and reset/factory reset.
b. From anywhere, hold power+volume down until you see the bootloader. There are 2 possible screens in there. One of them has factory reset. Beware! From here it will likely wipe your sdcard!
c. From recovery. You can get there from bootloader. You can also flash an up to date recovery image from bootloader.
The rest of your recovery process should be provided by the ROM thread by which you will get your choice of ROM.
Make sure you have access to a PC with adb. You will likely need to flash a vendor image
My device is only recognized in fastboot mode. No ADB, no recovery. Tried to uninstall and manually install latest USB drivers, it didn't work. My Nexus is now just stucked in a bootloop. I even tried to flash factory images to no avail. Really don't know what to do...
FYI I have no screen in bootloader allowing me to factory reset: only Start/Reboot/Reboot bootloader/Barcodes, as others stated above.
Alright, so I had just installed TWRP and Magisk, made backups of my ROM and EFS, everything is going well. I go to install LuisROM.
I go into TWRP, click install, and click on the LuisROM package. Says it doesn't find a digest file, but installation is continuing, so I figure it's no big deal. Reboot, and I get the Unlocked Bootloader warning that I've just recently began to familiarize myself with, but at the bottom of the screen, say the bottom half inch or so, is crazy static. Completely jumbled nonsense. It's not animated or anything, just randomly colored static pixels. Odd.
Next screen? Black. Nothing. Plugged into the computer and the she makes the familiar beeps that a device has been plugged in. For a time I find myself stuck in a boot loop trying to get back into recovery via power + vol down, but nothing. Seems to instant reboot back into the warning then black screen.
Now: I can't even seem to turn the phone off! If I plug into the laptop, I hear the familiar sounds, but can't do anything about it that I know of. If I hold the power button for 30-60 seconds: nothing.
I saw a few posts on here saying something about a complete power drain and recharge, so that's my next best guess, but I'm hoping someone else has a better idea.
lynxon said:
Alright, so I had just installed TWRP and Magisk, made backups of my ROM and EFS, everything is going well. I go to install LuisROM.
I go into TWRP, click install, and click on the LuisROM package. Says it doesn't find a digest file, but installation is continuing, so I figure it's no big deal. Reboot, and I get the Unlocked Bootloader warning that I've just recently began to familiarize myself with, but at the bottom of the screen, say the bottom half inch or so, is crazy static. Completely jumbled nonsense. It's not animated or anything, just randomly colored static pixels. Odd.
Next screen? Black. Nothing. Plugged into the computer and the she makes the familiar beeps that a device has been plugged in. For a time I find myself stuck in a boot loop trying to get back into recovery via power + vol down, but nothing. Seems to instant reboot back into the warning then black screen.
Now: I can't even seem to turn the phone off! If I plug into the laptop, I hear the familiar sounds, but can't do anything about it that I know of. If I hold the power button for 30-60 seconds: nothing.
I saw a few posts on here saying something about a complete power drain and recharge, so that's my next best guess, but I'm hoping someone else has a better idea.
Click to expand...
Click to collapse
Can you reboot to EDL Mode? Plug in your phone. And hold the power and Volume Up button till it turns off. As soon as the Screen Goes black, let go of Power and Hold both the Volume Buttons. You will hear the Windows Connection Sound from your PC but phone screen will be back. After that, follow the instructions from the MSM Download Tool thread. It's in the Guides Section or you can Google 'MSM Download Tool OP6T"
DarthVader said:
Can you reboot to EDL Mode? Plug in your phone. And hold the power and Volume Up button till it turns off. As soon as the Screen Goes black, let go of Power and Hold both the Volume Buttons. You will hear the Windows Connection Sound from your PC but phone screen will be back. After that, follow the instructions from the MSM Download Tool thread. It's in the Guides Section or you can Google 'MSM Download Tool OP6T"
Click to expand...
Click to collapse
The phone is currently stuck in a state where the screen is black, but is stuck powered on. I cannot seem to power down manually.
That being said, after going to the thread you've directed me to, it does appear in the device manager under the name indicated by the thread! I will report back once I've tried all I can with this lead, thank you very much.
lynxon said:
The phone is currently stuck in a state where the screen is black, but is stuck powered on. I cannot seem to power down manually.
That being said, after going to the thread you've directed me to, it does appear in the device manager under the name indicated by the thread! I will report back once I've tried all I can with this lead, thank you very much.
Click to expand...
Click to collapse
Good Luck.
Alright, so right now I'm getting "Sahara Communication Failed, please try again after power off phone."
So, I guess I'm back to waiting for the phone to run out of battery on its own. I'll try the MSM Download Tool again once that time comes :good:
lynxon said:
Alright, so right now I'm getting "Sahara Communication Failed, please try again after power off phone."
So, I guess I'm back to waiting for the phone to run out of battery on its own. I'll try the MSM Download Tool again once that time comes :good:
Click to expand...
Click to collapse
I think you're forgetting the 3-button-magic of your device. Press power + vol-up + vol-down simultaneously for 10 seconds to make it power down.
Wrapped with delicious Fajita [emoji896]
Timmmmaaahh said:
I think you're forgetting the 3-button-magic of your device. Press power + vol-up + vol-down simultaneously for 10 seconds to make it power down.
Click to expand...
Click to collapse
I did actually try that as well, to no avail.
DarthVader said:
Can you reboot to EDL Mode? Plug in your phone. And hold the power and Volume Up button till it turns off. As soon as the Screen Goes black, let go of Power and Hold both the Volume Buttons. You will hear the Windows Connection Sound from your PC but phone screen will be back. After that, follow the instructions from the MSM Download Tool thread. It's in the Guides Section or you can Google 'MSM Download Tool OP6T"
Click to expand...
Click to collapse
Good news is that this time the MSM Download Tool could recognize the phone, however I received "Images do not match with the phone." I had to download 9.0.12. as it seems that 9.0.13. actually got removed from that server as I was in the middle of downloading it. I found another source for 9.0.13. and am downloading that now. Hopefully that's the correct version...
lynxon said:
I did actually try that as well, to no avail.
Good news is that this time the MSM Download Tool could recognize the phone, however I received "Images do not match with the phone." I had to download 9.0.12. as it seems that 9.0.13. actually got removed from that server as I was in the middle of downloading it. I found another source for 9.0.13. and am downloading that now. Hopefully that's the correct version...
Click to expand...
Click to collapse
Is your phone a T-Mobile Converted
DarthVader said:
Good Luck.
Click to expand...
Click to collapse
And the phone is alive again! Hallelujah! I had to use the T-Mobile version of the MSM Download Tool, which is funny because I had bought the phone used and there was no T-Mobile screen at boot before, but there is now, but she is alive!!!
Thank you again for your help. You're doing great work since returning to the light side, Vader
lynxon said:
And the phone is alive again! Hallelujah! I had to use the T-Mobile version of the MSM Download Tool, which is funny because I had bought the phone used and there was no T-Mobile screen at boot before, but there is now, but she is alive!!!
Thank you again for your help. You're doing great work since returning to the light side, Vader
Click to expand...
Click to collapse
Glad to know you're back up. You bought it off eBay I assume? That would explain the no TMo Splash Screen earlier. Now if you'd like to revert to International again, there is a Guide you can use to convert your TMo into International and then update to latest 10.3 or Flash a Custom ROM as you please. It's in the Guides Section.
May the Force be with You.
DarthVader said:
Glad to know you're back up. You bought it off eBay I assume? That would explain the no TMo Splash Screen earlier. Now if you'd like to revert to International again, there is a Guide you can use to convert your TMo into International and then update to latest 10.3 or Flash a Custom ROM as you please. It's in the Guides Section.
May the Force be with You.
Click to expand...
Click to collapse
Yes! Back up and then immediately down... So, I followed the procedure to remove the T-Mobile info and that worked well, back to stock OxygenOS 9.0.13. Followed the directions here for unlocking the bootloader, running TWRP and Magisk. All good.
Last time I flashed with RR and crashed. This time I flashed with LineageOS 17 and... Exact same crash. Static on the bottom of the screen, bootloop and all. So, now I'm stuck waiting again for the battery to die down before I can reflash to T-Mobile, then to international, then unlock the bootloader.
Any idea what I can do differently this time so I can have a custom ROM?
Not eBay, but I was using OfferUp and found a local shop selling it so I was able to sidestep the middleman.
lynxon said:
Yes! Back up and then immediately down... So, I followed the procedure to remove the T-Mobile info and that worked well, back to stock OxygenOS 9.0.13. Followed the directions here for unlocking the bootloader, running TWRP and Magisk. All good.
Last time I flashed with RR and crashed. This time I flashed with LineageOS 17 and... Exact same crash. Static on the bottom of the screen, bootloop and all. So, now I'm stuck waiting again for the battery to die down before I can reflash to T-Mobile, then to international, then unlock the bootloader.
Any idea what I can do differently this time so I can have a custom ROM?
Not eBay, but I was using OfferUp and found a local shop selling it so I was able to sidestep the middleman.
Click to expand...
Click to collapse
Could you perhaps provide an image of Said Crash? And a couple more things. Which ROM were you trying to Flash. What was your OOS version before trying to Flash the ROM. And what TWRP did you use? Because this sounds like a Crash Dump which is common if you use the wrong Vendor Firmware.
DarthVader said:
Could you perhaps provide an image of Said Crash? And a couple more things. Which ROM were you trying to Flash. What was your OOS version before trying to Flash the ROM. And what TWRP did you use? Because this sounds like a Crash Dump which is common if you use the wrong Vendor Firmware.
Click to expand...
Click to collapse
Well, hopefully I won't crash again as I have to wait a day for the battery to train to fix the crash haha. It happened so far with RR and LineageOS. OxygenOS 9.0.13. And...
Woah. Just now seeing that my TWRP Zip file is 3.2.3-2 and Img file is 3.3.1-1. Perhaps that is the culprit?
EDIT: Nope! Just tried with TWRP 33.1-1, LineageOS 16 official build as of 1/11/2020. Included is a photo of the boot warning page, and apparently I can fastboot right now as well, but there's no particular information on either page that I can imagine is useful.
Boot warning
Fast boot
This time I also tried wiping the Dalvik. I also notice that on the bootloader unlocking directions it says to not update with partial OTAs (under 1GB) as this can cause a soft-brick. All of the ROMs I've been trying to flash are about 500mb. Is this the problem?
lynxon said:
Well, hopefully I won't crash again as I have to wait a day for the battery to train to fix the crash haha. It happened so far with RR and LineageOS. OxygenOS 9.0.13. And...
Woah. Just now seeing that my TWRP Zip file is 3.2.3-2 and Img file is 3.3.1-1. Perhaps that is the culprit?
Click to expand...
Click to collapse
It is. Always use the latest version of TWRP, OOS, Magisk, etc UNLESS said otherwise.
DarthVader said:
It is. Always use the latest version of TWRP, OOS, Magisk, etc UNLESS said otherwise.
Click to expand...
Click to collapse
I seem to have edited my last post without noticing your reply. Updated both copies of TWRP, img and zip, to the latest and still crashed. Though if you look at my last post there is one other potential, though I'm not sure what to do about it, I also uploaded pics.
This magic right here!!
After following the directions in this video, I have achieved a custom rom. RR is loading right now. It would seem the major difference is that I wasn't decrypting my data, which is included in this video.
Thanks again for sticking with me and being so patient. ?
lynxon said:
This magic right here!!
After following the directions in this video, I have achieved a custom rom. RR is loading right now. It would seem the major difference is that I wasn't decrypting my data, which is included in this video.
Thanks again for sticking with me and being so patient. ?
Click to expand...
Click to collapse
Hmm. Glad to know that you're up and running. If you don't mind, could you tell me what you did different when flashing this time? And how were you flashing before that lead to the bricks.
DarthVader said:
Hmm. Glad to know that you're up and running. If you don't mind, could you tell me what you did different when flashing this time? And how were you flashing before that lead to the bricks.
Click to expand...
Click to collapse
Basically it comes down to the directions here, which I used as a base, and the directions in this video.
The unlocking bootloader directions didn't have anything about installing a custom ROM, so I figured that once I had everything else set up: unlocked bootloader, TWRP, root, then all I had to do was go to "install" in TWRP and flash the new ROM, which had led to the crash with static at the bottom of my screen.
But then, when using the video tutorial, this guy did things in a particular way. The very first thing was decrypting the data, which I didn't know was necessary, but probably made the difference. This was done under "wipe" and then "format data" in TWRP. He also instructed on flashing the newest version of OxygenOS and TWRP twice, apparently this installed it under both A/B partitions. After installing the custom ROM he also wiped the "data" and "cache." Lots of steps in the video, I felt as if they didn't need to be done exactly the way he directed, but in this case I trusted his method and I'm glad I did.