Develop Bugs

Another Bricked Nexus 7 after Lollipop

Seems a few are having the same problem as me after trying to flash 5.0
My Nexus will no longer boot past the Google Logo (White one). I can only access the Bootloader. When I try to go to recovery I see the TWRP logo but stays stuck there. I tried flashing a new image a few times but always had the same problem.
I then tried to relock the bootloader and unlock again again to prepare a fresh install. This is where it gets worse. I managed to lock the bootloader but I can no longer unlock. I get to the screen warning that data will be wiped if I choose "YES", but when I do proceed, I stay stuck on "Erasing userdata...". I left it for 5 hours and was still stuck with the same message.
I cant see what else I can do now.
Ive read a few threads saying its a motherboard issue. Seems weird that it appeared when I tried to install Lollipop. Also seems Im not the only one.

this worked for me
I'm sure someone wiser will respond to you later but ..... I've been in a similar situation.
I use Windows 7 64bit and always connect device with usb 2 port (i.e. not usb3).
I was getting stuck on the google logo with an open lock symbol low on the screen - indicating unlocked bootloader. Like you could get into recovery but unable to get any further once there.
Try using Wugfresh's Nexus Root Tool. Look in the development thread. I'd suggest reading his faq's.
Download and install the latest version 1.9.6 (as I recall) - I had problems when using the earlier versions.
Get an stock image downloaded.
Then you should be able to flash the image using the force flash method he mentions in his faq. You set it in the options menu.
Set USB debugging on the device and usb options for storage to ptp rather than mtp - that's what worked for me.
You'll probably see repeated "installing driver" messages and new "open location" popups as you go through it.
(if your bootloader is locked you'll need to unlock it first. - just re-read your original post and I'm hoping that the latest NRT version will get you unlocked OK.)
If you have problems with this at first try going through the driver installation section of the tools.
After that you can use the same tool to root it. That didn't work completely but did allow me to use an OTG flash drive. If you need full root there's a patch you need to flash - Key Pie patch - took me a while to find it but it's somewhere on these forums.
After the problems I had everything went smoothly in the end. Just be prepared to watch it go through various rebootings while the magic is being done.
Apologies if this is a bit haphazard - I tend to try and rush through things and then forget what it was exactly I did!

I have tried NRT but cant do anything as I cant unlock the bootloader. I have tried both Fastboot and NRT, they both block at "erasing userdata".

Just a thought
Sorry to hear that.
Have you tried "Flash Stock + unroot" with the "Soft-bricked/Bootloop" option in NRT? I now recall that's something that helped me get mine recovered. Just a thought.
I recall reading forum posts that suggested I might have motherboard issues - but I didn't believe it was likely to be the case so I kept trying.

Tried all NRT options including force flash.
Problem is none work with the locked bootloader.

Nexus Root Toolkit v1.9.7 out now
Change log:
What’s new in Nexus Root Toolkit 1.9.7: November 16th, 2014
· Included the latest Masterlists to prevent users who never utilized the “Update” in the kit from getting the AutoIt error (for KTU84P Nexus 7 2013). This error was due to the modified boot.img for that build being accidentally removed from the server. Its was then reuploaded and the masterlists were updated, but those users who never updated would still get the error.
· No longer will the “Force Flash” recommendation be made to N4 users, because it seems to cause a bootloop – however factory resting will fix that either way.

IDEM
I spent exactly the same as you, I also lock the bootloader and now I can not do anything, always get "write failure" and when I try to unlock stays forever "erase ..."
There will be some way to revive it?
Cursed Android 5.0!
If the problem is confirmed to be Android 5.0, Google can help solve these problems?

Use the instructions to reflash your bootloader.
http://blog.laptopmag.com/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
Note replace the instructions to download 4.1.1. with the correct version of the ROM you want to flash. Make sure you grab the correct version for your device. Flashing the wrong bootloader can hard brick your NEXUS with no chance of recovery. Also don't relock your bootloader unless you are certain that you will never want to flash again. Unlocking wipes all of your data and you also can't be rooted if you lock it again.

Doesnt work. Cant get passed the first step. After 1 hour its still "erasing boot..."

I flashed 5.0 successfully... You can't send it to Google with warranty? Try on other computer, do it manually using fastboot and don't give up!

As long as you can still boot into Fast Boot..
Your device can be restored..
I suggest using Wugfresh's Nexus toolkit
http://www.wugfresh.com/nrt/
The issues coming from the latest upgrade are common problems when ever we upgrade..
Its always better if you know how, just use the Nexus Toolkit and install the factory image..
Then it will sit at bootup for about 5-7 mins, then restore your apps... Profit
OTAs will always cause issues with some devices..

Zaphodspeaks said:
As long as you can still boot into Fast Boot..
Your device can be restored..
I suggest using Wugfresh's Nexus toolkit
http://www.wugfresh.com/nrt/
The issues coming from the latest upgrade are common problems when ever we upgrade..
Its always better if you know how, just use the Nexus Toolkit and install the factory image..
Then it will sit at bootup for about 5-7 mins, then restore your apps... Profit
OTAs will always cause issues with some devices..
Click to expand...
Click to collapse
Again.. I cant unlock the bootloader whether manually trying with fastboot or running NRT. Flashing a stock image is not possible.

tigerdim said:
Again.. I cant unlock the bootloader whether manually trying with fastboot or running NRT. Flashing a stock image is not possible.
Click to expand...
Click to collapse
If you have not tried the latest version of NRT, you may of fried your locked bootloader..
Regardless, don't give up... Someone will come to the rescue.. Nexus devices are pretty robust..
Try using another cable, make sure you have the correct driver, double check in Device Manager...
Then try again with the lastest NRT.. Mine just updated.. As a rule of thumb its better not to use a USB hub if thats the case.. Try swapping out your cable, make sure you have the Nexus drivers... I had to re install mine..

tigerdim said:
Doesnt work. Cant get passed the first step. After 1 hour its still "erasing boot..."
Click to expand...
Click to collapse
I'm in the exact same spot. Also, I know that I don't have USB debugging enabled, so not sure if I'm blocked out because of that. Very frustrating.
The computer sees the tablet though. If I click on List Devices in NRT Advanced Utilities, it shows my serial # fastboot.
update: I tried the Unlock command and it goes to the Unlock Bootloader screen. I click Yes, but then the device just hangs on that screen (I let it sit for 30-40 minutes). Ideas?

dayz3r0 said:
I'm in the exact same spot. Also, I know that I don't have USB debugging enabled, so not sure if I'm blocked out because of that. Very frustrating.
The computer sees the tablet though. If I click on List Devices in NRT Advanced Utilities, it shows my serial # fastboot.
update: I tried the Unlock command and it goes to the Unlock Bootloader screen. I click Yes, but then the device just hangs on that screen (I let it sit for 30-40 minutes). Ideas?
Click to expand...
Click to collapse
It hangs because its probably stuck at "erasing userdata". If you do it manuall with fastboot oem unlock you will see this in the cmd window.

tigerdim said:
It hangs because its probably stuck at "erasing userdata". If you do it manuall with fastboot oem unlock you will see this in the cmd window.
Click to expand...
Click to collapse
yep, it does

I ve given up . Bought a Nexus 9. Wasted too much time on this.

Having the same problem
My Nexus 7 (2013 32gb wifi) was working just fine on Monday. Had an unusual freeze up when I was reading something on Adobe Acro., but a quick reboot had it running again. I remember a notification about a system update but didn't pay it much mind. Later that evening I went to pick the N7 up and it was stuck on the Google loading screen. Freezes at Google loading screen when I attempt Recovery mode from Fastboot. Fastboot OEM unlock gives me the same stall at 'erasing user data' as mentioned above (left it on for this for 12+ hours yesterday and nothing). I haven't tried a different cable other than stock yet but I have tried multiple ports and two different machines to unlock the bootloader so I can flash the OS. No other functions with NRT (1.9.9) work including forced flash+unroot. I can't even flash the bootloader or erase or format any partitions. Feeling a little SOL here and I think it has something to do with Lollipop update.
N7 was unrooted and used for reading for the past couple weeks, so pretty vanilla use over the recent past.
4 months out of warranty with Asus and they want an est. $100 for RMA. Google tossed me to them after dragging me through the basic stuff I've been doing the past few days. Going to keep messing with it I suppose once exams are over but feel like I'm running out of things to try. If anyone has any suggestions, questions or a solution, posting them here would be much appreciated.

My upgrade from 4.4.4 to 5.0.1 took ages. It was like bouncing the four small balls for perhaps 5 minutes. Just have patience.
I would recommend not to use xposed or titanium backup as I expect those programs mess with /system files and that can break the android upgrade script. Just disable any unwanted bloatware in regular application control. At least all my updates have been successful so far. Yes, I am rooted.
Good luck.
---------- Post added at 12:51 AM ---------- Previous post was at 12:45 AM ----------
For Wugfresh excellent "Nexus Root Toolkit" to work you need to enable usb debugging in developer menu. You enable the developer menu by tapping a lot on your version information.
The usb debugging gets reset on every upgrade.

Mordecai253 said:
My Nexus 7 (2013 32gb wifi) was working just fine on Monday. Had an unusual freeze up when I was reading something on Adobe Acro., but a quick reboot had it running again. I remember a notification about a system update but didn't pay it much mind. Later that evening I went to pick the N7 up and it was stuck on the Google loading screen. Freezes at Google loading screen when I attempt Recovery mode from Fastboot. Fastboot OEM unlock gives me the same stall at 'erasing user data' as mentioned above (left it on for this for 12+ hours yesterday and nothing). I haven't tried a different cable other than stock yet but I have tried multiple ports and two different machines to unlock the bootloader so I can flash the OS. No other functions with NRT (1.9.9) work including forced flash+unroot. I can't even flash the bootloader or erase or format any partitions. Feeling a little SOL here and I think it has something to do with Lollipop update.
N7 was unrooted and used for reading for the past couple weeks, so pretty vanilla use over the recent past.
4 months out of warranty with Asus and they want an est. $100 for RMA. Google tossed me to them after dragging me through the basic stuff I've been doing the past few days. Going to keep messing with it I suppose once exams are over but feel like I'm running out of things to try. If anyone has any suggestions, questions or a solution, posting them here would be much appreciated.
Click to expand...
Click to collapse
They quote you $100 RMA, but once you send it in they will send you an invoice for $200. $165 for the motherboard, $25 labor and $10 return shipping. I fought it and they eventually dropped $10 for the return shipping. Last time I ever deal with Asus.
Sent from my Nexus 9 using Tapatalk

BOOTLOADER is LOCKED and Usb debugging is not enabled

My phone is gone into LOOPMODE only showing GOOGLE , and no OEM enabled , no USB debugging Enabled also DEVICE state is LOCKED...
please help me to restore my set.
how to Unlock the bootloader or how to enable USB debugging ?

From the reading that I have done, if the device state is locked you are in a bad way.
I have almost had success freezing my phone down to -18C, it will then complete the boot process but reboots before I can get into turn on OEM unlocking in the settings.
I am going to try and boot the phone whilst it is disassembled and use some freeze spray to keep it cool, in a couple of days when I have some free time.

First off , thankyou for replying
sconno said:
From the reading that I have done, if the device state is locked you are in a bad way.
I have almost had success freezing my phone down to -18C, it will then complete the boot process but reboots before I can get into turn on OEM unlocking in the settings.
I am going to try and boot the phone whilst it is disassembled and use some freeze spray to keep it cool, in a couple of days when I have some free time.
Click to expand...
Click to collapse
yeah sure, i m on HOLD , i have tried all things such as adb, nexus toolkit and all adb commands .
Reply soon bro !

Freezing you phone is nonsense and won't do anything for a software problem!
What you need to do is unlock the bootloader again. (do a search for howto do this)
And then give the adb command to format userdata! ("fastboot format userdata") This will wipe any encryption on the phone that's blocking further acces.
The next step is to download the lastest OTA and sideload it through adb. This will unconditionally write a clean stock ROM on your phone and you should be good to go.
MIND THAT THIS WILL WIPE EVERYTING ON YOUR PHONE!!!

r3act said:
Freezing you phone is nonsense and won't do anything for a software problem!
What you need to do is unlock the bootloader again. (do a search for howto do this)
And then give the adb command to format userdata! ("fastboot format userdata") This will wipe any encryption on the phone that's blocking further acces.
The next step is to download the lastest OTA and sideload it through adb. This will unconditionally write a clean stock ROM on your phone and you should be good to go.
MIND THAT THIS WILL WIPE EVERYTING ON YOUR PHONE!!!
Click to expand...
Click to collapse
but how to unlock bootloader , thats the problem bro ! i have done evrytthing to do so !

OK, so after trying to get my phone to boot for the past 3 days, I have finally done it and enabled the OEM unlock option.
I am running bullhead 7.1.2
1. Put phone in freezer at -18C for about 30 minutes.
2. Plugged phone into USB, pressed the power button and it then finally booted all the way.
3. Went into settings
4. Enabled developer options
5. Went into developer options and enabled OEM unlock. (I had to enter my pin number to make this happen)
I can now access the device using adb and device in no longer locked.

sconno said:
OK, so after trying to get my phone to boot for the past 3 days, I have finally done it and enabled the OEM unlock option.
I am running bullhead 7.1.2
1. Put phone in freezer at -18C for about 30 minutes.
2. Plugged phone into USB, pressed the power button and it then finally booted all the way.
3. Went into settings
4. Enabled developer options
5. Went into developer options and enabled OEM unlock. (I had to enter my pin number to make this happen)
I can now access the device using adb and device in no longer locked.
Click to expand...
Click to collapse
but i think my Android is corrupt , it showing only google when i press and hold the power button.
give me another solution bro !
And anyone from MUMBAI (BORIVALI WEST)

Try this. It worked for me on 2 devices.
https://hackaday.com/2017/02/11/nexus-5x-phone-resurrected-by-the-oven/

harihacker said:
Try this. It worked for me on 2 devices.]
Thanks for this, I am going to give this a go with a heat gun later on today.
Click to expand...
Click to collapse

harihacker said:
Try this. It worked for me on 2 devices.
https://hackaday.com/2017/02/11/nexus-5x-phone-resurrected-by-the-oven/
Click to expand...
Click to collapse
lol , I think my Phone is dead RIP .

Softbricked, locked bootloader ... HELP!!

I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:

Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
If it still boots into the boot loader you're fine and fixable.

Phalanx7621 said:
If it still boots into the boot loader you're fine and fixable.
Click to expand...
Click to collapse
Well that's good news at least!
What can I do?

Prosis said:
Well that's good news at least!
What can I do?
Click to expand...
Click to collapse
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools

Phalanx7621 said:
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.

Prosis said:
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.
Click to expand...
Click to collapse
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.

Phalanx7621 said:
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.
Click to expand...
Click to collapse
Yeah I tried that but the dead android never appears. It reacts the same way it does when I try to boot into the system, which is just a white flicker that appears and disappears on the top of the screen. It's like it's trying to load the white screen with the Google logo but it can't.

Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.

Phalanx7621 said:
Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.
Click to expand...
Click to collapse
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks

Prosis said:
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks
Click to expand...
Click to collapse
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.

Phalanx7621 said:
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.
Click to expand...
Click to collapse
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.

Prosis said:
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.
Click to expand...
Click to collapse
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?

Phalanx7621 said:
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?
Click to expand...
Click to collapse
Yeah I did. I even tried several tools that are supposed to be able to help but without having Allow OEM Unlock enabled nothing works :/

After maybe 2 hours left alone charging now it's not even booting into the booloader anymore...

Are you going to be able to RMA it? Is it still under warranty?

Phalanx7621 said:
Are you going to be able to RMA it? Is it still under warranty?
Click to expand...
Click to collapse
I'm waiting for my seller to give me the original order number (which seems like forever right now given the situation). Then Google will be able to tell me if it's still under warranty. If not then, according to the authorized repair center, it's either the battery, the port or the motherboard which means it's probably the end for this phone as prices range from less than $100 to nearly $400. :crying:

Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha

Homeboy76 said:
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha
Click to expand...
Click to collapse
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.

Prosis said:
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.
Click to expand...
Click to collapse

Good news! I got an RMA!!
Thanks for your help everyone!

Question Hard Bricked Pixel 6 Pro Android 13

Hello! I think I've bricked my Pixel 6 Pro using Android 13, I rooted with Magisk successfuly but when I flashed kirisakura kernel using EXKM and rebooted it gave me a bootloop, after bootloop tried flashing patched boot.img from factory in Pixel Flasher but didn't work, also tried using adb and nothing. I think I have flashed the wrong file or something after kirisakura because it would show on Pixel Flasher with a ? at the beginning of the ADB connected devices.
It only would boot to Google logo and then restart, did it a few times but then the screen became black and unresponisive, I've tried vol down power and vol down power and vol down only and vol up power any combination for more than 30 seconds and nothing works, doesn't show on adb devices or wants to boot into any mode.
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Sad thing, my Pixel arrived yesterday and I hard bricked it in the same day.
willing to pay anyone here if someone helps me to boot my pixel again.
Thanks in advance.

PunkOz said:
Hello! I think I've bricked my Pixel 6 Pro using Android 13, I rooted with Magisk successfuly but when I flashed kirisakura kernel using EXKM and rebooted it gave me a bootloop, after bootloop tried flashing patched boot.img from factory in Pixel Flasher but didn't work, also tried using adb and nothing. I think I have flashed the wrong file or something after kirisakura because it would show on Pixel Flasher with a ? at the beginning of the ADB connected devices.
It only would boot to Google logo and then restart, did it a few times but then the screen became black and unresponisive, I've tried vol down power and vol down power and vol down only and vol up power any combination for more than 30 seconds and nothing works, doesn't show on adb devices or wants to boot into any mode.
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Thanks in advance.
Click to expand...
Click to collapse
Reflash the entire android 13 image

DespairFactor said:
Reflash the entire android 13 image
Click to expand...
Click to collapse
How if it doesn't boot into fastboot or anything, PC won't recognize anything since my Pixel's screen is completely black, won't do a single thing, just a sandwich glass, won't even show if it's charging, nothing.

Read this thread if you haven't...

blackhawk said:
Read this thread if you haven't...
Click to expand...
Click to collapse
Everything downloaded to my PC belongs to Android 13, factory image, kernel, everything, didn't rollback, I was in a bootloop where my device went into fastboot mode everytime but then it went to google logo and stopped working at all. Nothing shows on my screen, I've read somewhere on reddit that a guy had the same problem and had to return his device.

PunkOz said:
Everything downloaded to my PC belongs to Android 13, factory image, kernel, everything, didn't rollback, I was in a bootloop where my device went into fastboot mode everytime but then it went to google logo and stopped working at all. Nothing shows on my screen, I've read somewhere on reddit that a guy had the same problem and had to return his device.
Click to expand...
Click to collapse
Yeah I've been watching this out of curiosity as I run Samsung's on 9 and 10. That thread has a lot of good information and links. Someone there may be able to help.
I thought 13 be fubar, it hasn't disappointed

I know you said you tried all combinations of buttons, but when pressing power+volume down, have you tried "fastboot devices" in terminal to see if the device ID shows?
If you can get into fastboot even with no display, you should be able to reflash the factory images.
Edit:
Also, if you're going to try flash custom kernels and want an easy app to use, I'd recommend installing Kernel Flasher as it'll backup all of the modified images and allows you to check the partitions.

lottarake said:
I know you said you tried all combinations of buttons, but when pressing power+volume down, have you tried "fastboot devices" in terminal to see if the device ID shows?
If you can get into fastboot even with no display, you should be able to reflash the factory images.
Click to expand...
Click to collapse
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices

@PunkOz can you describe exactly how you updated? Did you attempt to flash the custom kernel immediately after the update, or did you let Android 13 boot normally on the stock kernel?

PunkOz said:
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
Click to expand...
Click to collapse
ADB and fastboot display different device IDs. You'll want fastboot vs adb when in fastboot mode.
If you can't get it to display and want to get a new pixel, hopefully you're within the return window and can exchange it easily.
Edit:
Reread your OP and the reason you bootlooped from what I gather is that you manually flashed the stock boot.img and kernels now modify more than just the boot.img, so you're in conflict with dtbo, vendor_boot, and vendor_dlkm images. When returning to stock with a custom kernel, you'll need to be sure reflash all of these from the factory zip.

PunkOz said:
Yes, went to platform tools and used cmd adb devices and nothing shows. It's like stuck booting maybe (?) but with a black screen and won't let me do anything, I'm not even sure if it's charging, I think the only way to reset is remove battery and put it back but it may void my warranty, waiting for it to discharge is impossible as it was 95% charge.
Edit: Will try kernel flasher if I ever get it to boot again. I think my last option is to return it and hope to get a new one, it's my first time hard bricking a device and I've done countless kernels and custom roms since Galaxy S2 and Nexus devices
Click to expand...
Click to collapse
it seems like you may have booted a kernel that didn't work, failed boot a few times and threw you onto the A12 bootloader. Would need to verify how you installed android 13

Following....
I have the same problem...blackscreen. All I did was use the command " fastboot flash boot patched_magisk.img”.

Easy solution: using chrome on your pc or mac go to pixel factory firmware and find the the newest update. Plug in your phone and click "flash", select your device, wipe everything and flash all partitions.

rajchelu said:
Following....
I have the same problem...blackscreen. All I did was use the command " fastboot flash boot patched_magisk.img”.
Click to expand...
Click to collapse
If you manage to fix it, I recommend booting the magisk image, instead of flashing it with the 'fastboot boot /patched_boot.img' command
Then direct install in magisk app
If it fails when booting the image, device will just reboot into normal mode.

PunkOz said:
Did I completely brick my device flashing a wrong boot file after my bootloop? Is there any way to recover my Pixel 6 or should I try to return and ask for a new one and see if they accept it?
Sad thing, my Pixel arrived yesterday and I hard bricked it in the same day.
willing to pay anyone here if someone helps me to boot my pixel again.
Click to expand...
Click to collapse
The good news is that your phone is still under warranty!
The bad news is that you now have to USE the warranty.
A13 includes anti-rollback code for the bootloader. Unfortunately, the anti-rollback code BRICKS the device instead of putting you into a recoverable state.
The sequence that killed you is this; you installed A13 and the updated bootloader to one slot, but not the other. You successfully booted A13 at least one time, which advanced the anti-rollback version. You then installed a kernel/boot that was incompatible with A13, which failed to boot a few times, causing it to switch to the other slot (with the old bootloader). Because it tried to run the old bootloader with the updated anti-rollback version, it immediately went into BRICK mode.

DespairFactor said:
it seems like you may have booted a kernel that didn't work, failed boot a few times and threw you onto the A12 bootloader. Would need to verify how you installed android 13
Click to expand...
Click to collapse
I think that's what happened, I installed Android 13 via OTA, had to apply for beta in order to receive the update faster because it wasn't available in my country yet.
Than installed patched boot - magisk - custom kernel via EXKM app and then bootloop and then flashed a few times boot stock and patched and nothing worked. @V0latyle
96carboard said:
The good news is that your phone is still under warranty!
The bad news is that you now have to USE the warranty.
A13 includes anti-rollback code for the bootloader. Unfortunately, the anti-rollback code BRICKS the device instead of putting you into a recoverable state.
The sequence that killed you is this; you installed A13 and the updated bootloader to one slot, but not the other. You successfully booted A13 at least one time, which advanced the anti-rollback version. You then installed a kernel/boot that was incompatible with A13, which failed to boot a few times, causing it to switch to the other slot (with the old bootloader). Because it tried to run the old bootloader with the updated anti-rollback version, it immediately went into BRICK mode.
Click to expand...
Click to collapse
Yeah, I haven't been around XDA community as much as before, it was 100% my fault, didn't read that much before starting to flash custom kernel and boot. Didn't know there were 2 slots. My phone is 100% dead now, I bought it through amazon from a third party store, do you think I voided my warranty? Screen won't turn on at all with any combination of keys (Pwr+Vol) and won't even display when it's charging, completely bricked

If anyone out there has an answer to fixing this problem. Please let us know! I'm also on the same boat. Didn't flash to both slots so now I have a paperweight. Really don't wanna spend money on a new phone so I'll try to be patient and hope someone can be my saviour

So does anyone have an update about this problem? I'v eread somewhere that it could be in EDL mode when the screen doesn't turn on. Could that be the case and could we do something with that?

Markelijk said:
So does anyone have an update about this problem? I'v eread somewhere that it could be in EDL mode when the screen doesn't turn on. Could that be the case and could we do something with that?
Click to expand...
Click to collapse
We don't have tools to deal with this processor's EDL mode, so unfortunately it's likely the only fix is to reach out to Google to have it repaired under warranty.

Shot in the dark here...but this reminds me of people only flashing to one slot and the phone rebooting into the other "okd OS" slot and the phone bricking. So this is a little different...the phone MIGHT be on, just on a big black screen that just shows nothing. So yes it IS "bricked".
But UNPLUG the phone, give it about 10 seconds, then press and hold power, volume up and volume down, preferably OUT of the case, and just hold it for like a minute. After thirty seconds or so it might forcefully reboot, if it does, then we need to get into fastboot and reflash A13, but then ALSO flash it to the other slit. This is why it is SO IMPORTANT to flash BOTH SLOTS.
I had THIS problem on my Oneplus 6T, yes...a different phone...but it my phone was DEAD for a week before I discovered that I could force boot it.
But if you have the phone connected to the pc, the bootloader or whatever is trying to talk will not allow the phone to do anything.
Also, plug the phone into the charger. If it is in a hard soft brick and the phone DIES it can be a NIGHTMARE to get it back to life, usually involving you JUMPING the battery manually....like I said. A shot in the dark. But worth a shot.

OEM Unlock Doesn't Exist | Galaxy Note 10+

Hey guys I have finally admitted defeat, Im not really sure what else to do at this point, as I have tried a lot;
- Flashed the base android pie (12.0) OS
- Hard reset
- Changed Date and Time back 7 days to prevent jail
- Disabled automatic system updates
- Disabled things such as updates, timezone change, etc.
Enable Developer options: and OEM doesn't appear at all, simply doesnt exist, not even grayed out or anything
The only thing I could find online explaining this issue is that the reason this happens is because my device is SIM-locked. Which it isn't. It's fully unlocked (XAG/XAG/XAA)
Model: SM-N975U1 Region: XAA
Any help would be great thanks

and yes it is connected to the wifi, and tried updating also (im on the latest), still nothing has changed

jacobjake7 said:
Hey guys I have finally admitted defeat, Im not really sure what else to do at this point, as I have tried a lot;
- Flashed the base android pie (12.0) OS
- Hard reset
- Changed Date and Time back 7 days to prevent jail
- Disabled automatic system updates
- Disabled things such as updates, timezone change, etc.
Enable Developer options: and OEM doesn't appear at all, simply doesnt exist, not even grayed out or anything
The only thing I could find online explaining this issue is that the reason this happens is because my device is SIM-locked. Which it isn't. It's fully unlocked (XAG/XAG/XAA)
Model: SM-N975U1 Region: XAA
Any help would be great thanks
Click to expand...
Click to collapse
Your device is probably RMM locked. Please take a look at this thread.

nxmryada said:
Your device is probably RMM locked. Please take a look at this thread.
Click to expand...
Click to collapse
Thanks,
I don't quite understand this part;
"
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Power" + "Vol. Down" + "Vol. Up" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Vol. Up" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
***Don't boot into rom because it will lock your device again!!!!
Once the custom recovery booted, swipe to "Allow modification" and flash RMM-State_Bypass.zip as normal zip"
I flashed then did as it said but it just sends back to the original recovery screen

jacobjake7 said:
Thanks,
I don't quite understand this part;
"
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Power" + "Vol. Down" + "Vol. Up" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Vol. Up" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
***Don't boot into rom because it will lock your device again!!!!
Once the custom recovery booted, swipe to "Allow modification" and flash RMM-State_Bypass.zip as normal zip"
I flashed then did as it said but it just sends back to the original recovery screen
Click to expand...
Click to collapse
RMM locking prevents flashing AFAIK. Please check for "RMM state" in download mode, if it's "Prenormal" then you're locked out.

nxmryada said:
RMM locking prevents flashing AFAIK. Please check for "RMM state" in download mode, if it's "Prenormal" then you're locked out.
Click to expand...
Click to collapse
I am unable to find any display info on this device, like such as in downloader. Where can I find my RMM state?

nxmryada said:
RMM locking prevents flashing AFAIK. Please check for "RMM state" in download mode, if it's "Prenormal" then you're locked out.
Click to expand...
Click to collapse
Wait isn't RMM state just that 7 day jailing? I tried doing this before I flashed/hard reset my phone was on months before I reset it and was still unable to get that OEM option

nxmryada said:
RMM locking prevents flashing AFAIK. Please check for "RMM state" in download mode, if it's "Prenormal" then you're locked out.
Click to expand...
Click to collapse
I understand the lingo a bit more now after reading up, but that article is a flat circle. It wants me to Install twrp to flash a RMM bypass zip (which you need to disable bootloader to even do in the first place), and you need root access to use twrp.
Yet the information provided below of how to root tells me I need to install twrp and boot into it's recovery, but you need to be root to do that?!?
Make it make sense!

Probably by flashing a combination without etoken or something of that sort?
Locked bootloader prevents booting unsigned boot stages.
What about disable Knox through ADB with the SamFwTool ?
I think you may need to remove google account and screenlocks first, not sure.

Network_Pro said:
Probably by flashing a combination without etoken or something of that sort?
Locked bootloader prevents booting unsigned boot stages.
What about disable Knox through ADB with the SamFwTool ?
I think you may need to remove google account and screenlocks first, not sure.
Click to expand...
Click to collapse
Disabling Knox within SamFw works, however I am still KG/RMM locked

Hit a brick road here not really sure where else to go...
I have a Galaxy Note 10+ (SM-N975U1 XAG) that is RMM locked an unable to get the OEM option in dev settings,
Since Knox is one responsible for the valutmanager line that releases the RMM check, I tried disabling Knox completely through SamFW tool, disabling works, however I am still locked.
Any help would be apricated...

jacobjake7 said:
Hit a brick road here not really sure where else to go...
I have a Galaxy Note 10+ (SM-N975U1 XAG) that is RMM locked an unable to get the OEM option in dev settings,
Since Knox is one responsible for the valutmanager line that releases the RMM check, I tried disabling Knox completely through SamFW tool, disabling works, however I am still locked.
Any help would be apricated...
Click to expand...
Click to collapse
This video may help...
youtu.be/6RTbx2jTkpQ
as the person said only Exynos versions can be unlocked and not Snapdragon ones.
and also this video below shows how to unhide the hidden oem unlock button
youtu.be/mF2Nxck4FtM

aiSanaul said:
This video may help...
youtu.be/6RTbx2jTkpQ
as the person said only Exynos versions can be unlocked and not Snapdragon ones.
and also this video below shows how to unhide the hidden oem unlock button
youtu.be/mF2Nxck4FtM
Click to expand...
Click to collapse
I have a Exynos, OEM doesn't exist in Dev options, since im RMM locked....

jacobjake7 said:
I have a Exynos, OEM doesn't exist in Dev options, since im RMM locked....
Click to expand...
Click to collapse
check out methods here
www (dot) 99mediasector.com/how-to-disable-rmm-state-lock-in-samsung-galaxy-devices/

aiSanaul said:
check out methods here
www (dot) 99mediasector.com/how-to-disable-rmm-state-lock-in-samsung-galaxy-devices/
Click to expand...
Click to collapse
Thanks,
First option I can't do TWRP since I need root and unlocked bootloader, so next step;
Miracle Box Thunder ive been messing around with before, is interesting, can only get it to work for the first half second it connects to my phone and then the stop button grays out :/
Though I got it do to this for the "Reset Reactivation/EE Locks":
Start Detect device.
Device detected OK.
Downloading..
Get phone data..
Reactivation Lock Reset Launched...
Searching For Reactivation Data 1...
Loading Data Please wait..
Rc Block Update ok...
Processing Data...
Done..
EE Lock Reset Launched...
Searching For EE Data 1...
Loading Data Please wait..
Error Data Not Found...
>>All Done..
I am unable to view my download mode info in the top left. Would you know how to "enable" it or how I can go about viewing it another way?

aiSanaul said:
check out methods here
www (dot) 99mediasector.com/how-to-disable-rmm-state-lock-in-samsung-galaxy-devices/
Click to expand...
Click to collapse
Actually while doing the "Reset Reactivation/EE Locks" it gave me a text top left of the download mode, saying "ODIN: TOKEN Size is too large [-13]"

Update...I was able to bypass the RMM/KG lock by first doing a fresh install;
skip through all intro and setup (or just FRP skip)
DONT SET A SCREEN LOCK, must be unlocked or swipe otherwise you will be softbricked in a infinite "starting device..."
next you use Minimal ADB and Fastboot terminal and type "adb shell pm disable-user --user 0 com.android.systemui"
your phone is gonna freak out now dont worry about it and open up FRP Samsung by NKTEAM and click "Kill update" (this is important)
then after kill update is complete you can run "Disabled KG Locked MTK ADB" which will lock your phone saying you uninstalled a samsung service etc....just reboot your device and your good!
Though, I don't understand how to unlock OEM still? I still don't have the option?
Should I flash oreo or something? Though flashing causes it all to relock again

Not to give up and never admit defeat, here is what I would do since I am not sure what that RMM is, I am not actively reversing this technology just collecting information from the web.
I would ask the tools creators through their support chats if they can extend the tools to deal with the faulting security mechanisms. At the same time I will check where is a cheap replacement board, just in case help it brick itself (yes the security mechanism design is self-destructing, I do not admit I break it it breaks itself).
I will flash with Odin with pit file with format to try to truly revert to factory. If I am not happy with the result I start becoming creative with the tools at hand LOL:
Then I will start flashing Bin-compatible official files with patched Odin, until the device resets itself to factory at least two times. The idea being due to crypto differences in the versions, the entire partitions gets rewritten during flashing. I would try this by removing all locks and protections (accounts), resetting to defaults, and flashing the first and the last bin-compatible firmware from samfw site.
Someone mentioned they achieved not-keeping previous things by mixing their firmware files AP BL CSC etc this is something I would try to try and get the device to confuse the crypto and overwrite things.
The idea is that the second stage bootloader BL will always be able to get you to download mode to flash with Odin so messing and even triggering with the later boot and protection stages should not erase the XBL. If it does then I will need the emergency_download_debug whatever package for the Bin version.
What Bin version is the device anyway ?

SM-N975U1 is Snapdragon. Why did you think it was Exynos?

Ask @afaneh92 he is unlocking specific versions of bootloaders for US/Canada devices since the SamPWN team are missing from the forums. https://forum.xda-developers.com/t/...unlock-for-samsung-us-canada-devices.4215101/