Develop Bugs

Black Screen with LED Notification Shining White

please help my oneplus 3 can't boot to system or recovery after unbricking with mega unbrick method 1 and 2
the phone boot to black screen and led notification shining white
i try unbricking method again and flash recovery from fastboot dosn't work
sorry my english

Did you solved? I have the same issue ... No ideea what to do... How did you solved?

bibiii79 said:
Did you solved? I have the same issue ... No ideea what to do... How did you solved?
Click to expand...
Click to collapse
If you follow the instructions for method 2, and repeatedly do it a few times, you can succeed. The important thing is to follow the instructions strictly, however silly they may look like.

I did several times, double checking all steps, still boot loop. After apply the method 2 , is doing a boot loop. Than I tried to apply again method 2 I have the successful download with green ...than I go in recovery and flash over adb sideload oos 3.2.8 ...than I start , no more boot loop, but after Oneplus logo goes into black screen with a withe stable notification led turned on ....I left over night ... But it keep staying like that until I force to power off by pressing and holding power button( after I want to turn off i cannot only going into bootloader and from there I choose power of, because is automatically turning on if I press and hold only the power button in order to turn off the device).
Pfiu difficult... I am thinking, some files are missing, this , and where I go in bootloader in missing the values on. Bootloader version- , and baseband version- ....

bibiii79 said:
I did several times, double checking all steps, still boot loop. After apply the method 2 , is doing a boot loop. Than I tried to apply again method 2 I have the successful download with green ...than I go in recovery and flash over adb sideload oos 3.2.8 ...than I start , no more boot loop, but after Oneplus logo goes into black screen with a withe stable notification led turned on ....I left over night ... But it keep staying like that until I force to power off by pressing and holding power button( after I want to turn off i cannot only going into bootloader and from there I choose power of, because is automatically turning on if I press and hold only the power button in order to turn off the device).
Pfiu difficult... I am thinking, some files are missing, this , and where I go in bootloader in missing the values on. Bootloader version- , and baseband version- ....
Click to expand...
Click to collapse
The bootloader and baseband versions were missing when i bought the phone new and are still blank today after flashing a few ROMs and Recoveries/Firmware and modems. So that is not an issue.
Are you downloading the correct files?

tnsmani said:
The bootloader and baseband versions were missing when i bought the phone new and are still blank today after flashing a few ROMs and Recoveries/Firmware and modems. So that is not an issue.
Are you downloading the correct files?
Click to expand...
Click to collapse
Yes, I am using the unbrick method with msm download tool, using the Method 2, after apply, installing all's the Qualcomm drivers 9008 , drivers signature off in windows.... The unbrick tool is passed with the green message .... Reversing back to oos 3.1.2 Android 6.0.1 ..stock, I have recovery working and bootloader also working, bootloader is locked ....so I cannot do too mutch. I start the device right away after unbrick tool and still boot to op logo that is going to vibrate as restart .... And stays in boot loop. Next step I go into recovery , and do over sideload an update with a full ROM, oos 4.0.1 , also tried with full ROM 3.2.8 ...I can sideload the whole ROM , than i start the device and after op logo goes in black screen and white motivation led lighted .... I leave it for 30 min, and still in the same, now I force turn off by going into bootloader and power off. Notice that after this sideload flash I cannot access the recovery. So I need to apply back the unbrick msm download tool for op3.
I tried also to flash over sideload a signed script from Ahmed , unified toolkit , to activate the USB debugging, but gives an error.
I run out of ideas .....any help is welcome ....
Thanks

bibiii79 said:
Yes, I am using the unbrick method with msm download tool, using the Method 2, after apply, installing all's the Qualcomm drivers 9008 , drivers signature off in windows.... The unbrick tool is passed with the green message .... Reversing back to oos 3.1.2 Android 6.0.1 ..stock, I have recovery working and bootloader also working, bootloader is locked ....so I cannot do too mutch. I start the device right away after unbrick tool and still boot to op logo that is going to vibrate as restart .... And stays in boot loop. Next step I go into recovery , and do over sideload an update with a full ROM, oos 4.0.1 , also tried with full ROM 3.2.8 ...I can sideload the whole ROM , than i start the device and after op logo goes in black screen and white motivation led lighted .... I leave it for 30 min, and still in the same, now I force turn off by going into bootloader and power off. Notice that after this sideload flash I cannot access the recovery. So I need to apply back the unbrick msm download tool for op3.
I tried also to flash over sideload a signed script from Ahmed , unified toolkit , to activate the USB debugging, but gives an error.
I run out of ideas .....any help is welcome ....
Thanks
Click to expand...
Click to collapse
Hi bro, did you solved it? Im facing the same problem here

bluuquthug said:
Hi bro, did you solved it? Im facing the same problem here
Click to expand...
Click to collapse
Unfortunately not yet ... Yes I solve it, I bought a Moto Z with dual SIM and snapdragon 820 and 64 GB and SD card with 280 euro .... I am disappointed at the moment about Oneplus 3 , I was a Nexus fan and switched to oneplus ... I thought will be opensource ... But way to expensive repair this done in service , Easter to buy another one ... You save time .. you cannot save money on it ..

bibiii79 said:
Unfortunately not yet ... Yes I solve it, I bought a Moto Z with dual SIM and snapdragon 820 and 64 GB and SD card with 280 euro .... I am disappointed at the moment about Oneplus 3 , I was a Nexus fan and switched to oneplus ... I thought will be opensource ... But way to expensive repair this done in service , Easter to buy another one ... You save time .. you cannot save money on it ..
Click to expand...
Click to collapse
Had the same problem with my oneplus x.

P
oneszero said:
Had the same problem with my oneplus x.
Click to expand...
Click to collapse
And what was the end of your story with Oneplus x?

bibiii79 said:
P
And what was the end of your story with Oneplus x?
Click to expand...
Click to collapse
RMA'd it to a service center for repair, after two tech support calls. They actually told me that they couldn't repair it due to "water damage." Funny thing is, that phone was never dropped in or on anything, let alone in WATER. Then to add insult to injury they refused to send it back to me stating that I had to pay for return shipping. My wife got on the phone with them and by the end of the phone call they said that they would send it back for free. HAHA. So I bought a Oneplus 3 after that whole ordeal. All the while the Oneplus X sat in the box on my desk for about 5 months. Last week I decided to pick it up and tinker with it some more. I scoured the net trying to find any other programs or solutions that I hadn't tried prior to sending it off. I came across somethings that I hadn't seen before. https://forum.xda-developers.com/oneplus-x/help/fastboot-mode-available-stuck-kindly-t3387918. http://rootmygalaxy.net/oneplus-x-s...w.pickmod.com/rom/4187/coloros-for-oneplus-x/. Ended up flashing Color OS via msm tool. Wouldn't load OS, but i didn't end up with a black screen and white LED, it just sat there. So right after I flashed Color OS, i Flashed the mini unbrick tool by Naman, and BOOM it booted into OS. Hope this helps.

Is it acceptable to you that a $800 phone dead in 21 months?

My pixel xl(1st gen) purchased from Google store in Jan 2017, and in bootloop a week ago.
I contact google support, they told me my device out of the 1-yr warranty, and redirect me to UbreakIfix for repair, cost on myself.
I contacted UbreakIfix, get a quote for 300+ to change motherboard.
As of today, the Pixel XL only worth $130 trade-in value, and the condition need to be perfect.
So clearly I won't spend $300 to save a device only worth $130.
About the issue, I had some level of experience with fastboot/adb command:
* tried re-image all latest Google Stock Image of Android 7/8/9 individually with boot-loader unlocked, no luck;
* tried adb sideload ota image of Android 7/8/9 individually, with boot-loader locked/unlocked, no luck;
* tried change active slot to a and b with combination of above two items, no luck;
* checked the recovery logs, the boot-loader did take whatever Android stock image I feed to to it, and I do almost every time can get in to both boot-loader or recovery-mode successfully, and has no limit to run any fastboot/adb commands, but these are all I can do, and still not to get the phone boot into Android OS.
* in a very few times, the static "Google" in the white screen did spinning into a big rainbow "G", but it was frozen right after, and eventually reboot again.
I don't know if it worth spend more time on it, and feel very frustrated about spending my time on this doomed device and dealing with the Giant company as a individual customer.
I am not a picky guy, I accept the device running slow, or buggy sometime, but doesn't accept it dead in 2 years as a premium phone.
What do you think, guys?
By the way, many thanks to XDA forum, I learnt a lot from many brilliant and kind people here.

It's not acceptable, but it's the norm. Look at buying a new tv - Some mfg warranties are like 90 days labor and 6 months to a year on parts...It's a shame you pay all that money for something that could be a paperweight in a year.

Acceptable for a phone, or any gadget worth $800 to die in 21 months? LMAO. If this acceptable to some group of people, please redirect them to the best psychic facility available on this planet.

Like you said, you can just grab another one for $130. Phones are put through a lot and used every day so it's hard to say. Lots of people have no issues for several years.
Sent from my Pixel XL using Tapatalk

lafester said:
Like you said, you can just grab another one for $130. Phones are put through a lot and used every day so it's hard to say. Lots of people have no issues for several years.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I used my Pixel as a regular way, never root it, never even boot into bootloader before the bootloop issue, always use ota in os to get update. No water spilt, never get drop or hit. In another word, I never "abuse" the phone, and the phone has no accident.
Yeah, whatever, for the phone issue, I'm just having bad luck, like you said, many people have no issues. What I upset about is a $800 phone became a brick within 2 years with a normal usage, and Google not even give this case as an exception to cover it out of warranty.
You may say, or like Google said, then what the warranty stands for, right? I say, if only a few people got this issue, then as a Giant company, should cover since no fault on customer, and it would be a small cost to Google; if a lot of people got this issue, then still Google need to cover, since it becomes a general issue to this phone, which indicates this is a failed model at all.
Please don't think I'm a cheap guy, and trying to take advantage from Google, just trying to think the logical here. BTW, I'm not just complaining Google without putting in effort to solve the issue by myself, I did a little bit research and pickup learning, regard this issue, I'm not alone, many other users have the same issue as well, some of them get it "resolved" by reimage, but the other just has no luck like me.
You don't have to agree with me, I'm a kind of guy would love to discuss with people no matter they have same point view as mine or not.

What is the actual problem with the phone? You can get into the boot loader screen then correct? When you try to install the latest stock factory image from Google with fastboot what happens?

Phalanx7621 said:
What is the actual problem with the phone? You can get into the boot loader screen then correct? When you try to install the latest stock factory image from Google with fastboot what happens?
Click to expand...
Click to collapse
Both the boot-loader and recovery-mode functions are normal. after flash in the stock factory image, all the progress logs shows flawless, and phone will reboot itself upon the progress is successfully complete. Instead of going into Android OS, the phone is stuck on a white screen with colorful "GOOGLE" in screen center, after like about 30 seconds, it reboots again, and if you leave the phone there, you will see it sometime just keep rebooting, showing the logo screen, or it goes into recovery-mode, showing "no command" black screen.

Lei.SHI said:
Both the boot-loader and recovery-mode functions are normal. after flash in the stock factory image, all the progress logs shows flawless, and phone will reboot itself upon the progress is successfully complete. Instead of going into Android OS, the phone is stuck on a white screen with colorful "GOOGLE" in screen center, after like about 30 seconds, it reboots again, and if you leave the phone there, you will see it sometime just keep rebooting, showing the logo screen, or it goes into recovery-mode, showing "no command" black screen.
Click to expand...
Click to collapse
I'm having the exact same issue and Phalanx7621 tried helping me out but unfortunately it looks like there's no solution for it.. Just like your issue, everything successfully flashes, but I got a little past the Google logo a couple of times, but no more. My phone wasn't dropped, never wet, nothing at all. Yesterday morning I woke up and the screen was just black and it started boot looping.
Funnily enough, 2 weeks after I paid the phone off. 1 week after Verizon called to let me know they had open enrollment on their insurance plans and I turned it down since, yanno, I don't mistreat my phone.. "Coincidence" I guess..
My post btw https://forum.xda-developers.com/pixel-xl/help/possibly-bricked-t3861057#post78033420 if any of that helps you hopefully.

That is the weirdest thing. So everything flashes and it reboots like it's going into the operating system and then just reboots in a boot loop? unless someone else times in its possible is a hardware failure.

Lei.SHI said:
Both the boot-loader and recovery-mode functions are normal. after flash in the stock factory image, all the progress logs shows flawless, and phone will reboot itself upon the progress is successfully complete. Instead of going into Android OS, the phone is stuck on a white screen with colorful "GOOGLE" in screen center, after like about 30 seconds, it reboots again, and if you leave the phone there, you will see it sometime just keep rebooting, showing the logo screen, or it goes into recovery-mode, showing "no command" black screen.
Click to expand...
Click to collapse
Phalanx7621 said:
That is the weirdest thing. So everything flashes and it reboots like it's going into the operating system and then just reboots in a boot loop? unless someone else times in its possible is a hardware failure.
Click to expand...
Click to collapse
I've made it far enough in to setup my device, receive and send a text message and then it will completely freeze up for a few seconds and restart. Then it may or may not make it past the Google logo, usually it'll stick on the Google logo or the G before freezing and restarting. But one out of every dozen or two restarts it'll load all the way into the OS before freezing and restarting after a few minutes.

premedicated said:
I've made it far enough in to setup my device, receive and send a text message and then it will completely freeze up for a few seconds and restart. Then it may or may not make it past the Google logo, usually it'll stick on the Google logo or the G before freezing and restarting. But one out of every dozen or two restarts it'll load all the way into the OS before freezing and restarting after a few minutes.
Click to expand...
Click to collapse
Ok so how about downloading TWRP on your PC and flash kernel on your phone, (https://forum.xda-developers.com/pixel-xl/development/marlin-flash-kernel-1-00-t3788300) put TWRP in the same folder as fastboot on your PC and reboot into boot loader and fastboot boot TWRP.img ( or whatever you named TWRP) . From TWRP, flash Flash kernel, then reboot and see if it boots into Android.

Phalanx7621 said:
Ok so how about downloading TWRP on your PC and flash kernel on your phone, (https://forum.xda-developers.com/pixel-xl/development/marlin-flash-kernel-1-00-t3788300) put TWRP in the same folder as fastboot on your PC and reboot into boot loader and fastboot boot TWRP.img ( or whatever you named TWRP) . From TWRP, flash Flash kernel, then reboot and see if it boots into Android.
Click to expand...
Click to collapse
Sure. Gimme a couple minutes and I'll report back
---------- Post added at 08:15 PM ---------- Previous post was at 07:40 PM ----------
Phalanx7621 said:
Ok so how about downloading TWRP on your PC and flash kernel on your phone, (https://forum.xda-developers.com/pixel-xl/development/marlin-flash-kernel-1-00-t3788300) put TWRP in the same folder as fastboot on your PC and reboot into boot loader and fastboot boot TWRP.img ( or whatever you named TWRP) . From TWRP, flash Flash kernel, then reboot and see if it boots into Android.
Click to expand...
Click to collapse
So it loaded up TWRP, then I remembered that I didn't set a pin after the latest reflash. So I went into software and setup a pin and moved the TWRP files over onto the phone as well as the kernal before it restarted. But now I can't get 'fastboot boot twrp.img' to actually load TWRP on the phone.. Command prompt says "downloading boot.img, booting, finished. And then on the phone it loads up the google logo and then just freezes and restarts.. I'll dink with it some more and see if i can make it work

Yeah you don't want a pin or password in TWRP. Any pin or password would've been erased with the wiping we did via fastboot earlier before we installed the newest factory image.

Phalanx7621 said:
Yeah you don't want a pin or password in TWRP. Any pin or password would've been erased with the wiping we did via fastboot earlier before we installed the newest factory image.
Click to expand...
Click to collapse
Alright so I guess I'll wipe everything again, then get far enough into the software to pull TWRP and the Kernel over? Or is there a way I can do all that from fastboot?

premedicated said:
Alright so I guess I'll wipe everything again, then get far enough into the software to pull TWRP and the Kernel over? Or is there a way I can do all that from fastboot?
Click to expand...
Click to collapse
If I were you I would wipe everything with fast boot and flash-all.bat again. See if you can get it to boot up once into Android, then reboot to the bootloader, fastboot boot TWRP.img and from TWRP because it's connected to your PC it will allow you to transfer files. download The flash kernel on your PC and just transfer it over to your phone and flash it, then reboot into Android to see if it works. But be careful whenever you reboot for the first time from TWRP because it will ask you to install TWRP as a system file or something. make sure to always hit do not install because if you swipe it will install it. That can definitely mess things up.

Phalanx7621 said:
If I were you I would wipe everything with fast boot and flash-all.bat again. See if you can get it to boot up once into Android, then reboot to the bootloader, fastboot boot TWRP.img and from TWRP because it's connected to your PC it will allow you to transfer files. download The flash kernel on your PC and just transfer it over to your phone and flash it, then reboot into Android to see if it works. But be careful whenever you reboot for the first time from TWRP because it will ask you to install TWRP as a system file or something. make sure to always hit do not install because if you swipe it will install it. That can definitely mess things up.
Click to expand...
Click to collapse
Well, knock on wood, I'm about 10 minutes into it and it seems to still be working.. But earlier it was on for a good bit of time before restarting as well. I'll report back!

premedicated said:
Well, knock on wood, I'm about 10 minutes into it and it seems to still be working.. But earlier it was on for a good bit of time before restarting as well. I'll report back!
Click to expand...
Click to collapse
Excellent ! Ok, so let's install magisk via TWRP. You'll need to boot back into TWRP via fastboot using fastboot boot TWRP.img and then transfer Magisk (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) onto your phone. After flashing , reboot and install kernel auditor here https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor so we can see what's going on with the kernel
Edit:also, you could flash TWRP with this file as well https://dl.twrp.me/marlin/twrp-pixel-installer-marlin-3.2.3-1.zip.html (you flash the zip while in TWRP) to not have to use fastboot to boot into it )

Phalanx7621 said:
Excellent ! Ok, so let's install magisk via TWRP. You'll need to boot back into TWRP via fastboot using fastboot boot TWRP.img and then transfer Magisk (https://github.com/topjohnwu/Magisk/releases/download/v17.1/Magisk-v17.1.zip) onto your phone. After flashing , reboot and install kernel auditor here https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor so we can see what's going on with the kernel
Edit:also, you could flash TWRP with this file as well https://dl.twrp.me/marlin/twrp-pixel-installer-marlin-3.2.3-1.zip.html (you flash the zip while in TWRP) to not have to use fastboot to boot into it )
Click to expand...
Click to collapse
Done, done and done.
I flashed TWRP through the zip, so it's a more permanent fixture. Magisk is installed as well as the kernel adiutor. What type of data/info am i looking for through the kernel program?
---------- Post added at 11:19 PM ---------- Previous post was at 10:47 PM ----------
Phalanx7621 said:
Excellent ! Ok, so let's install magisk via TWRP. You'll need to boot back into TWRP via fastboot using fastboot boot TWRP.img and then transfer Magisk (https://github.com/topjohnwu/Magisk/releases/download/v17.1/Magisk-v17.1.zip) onto your phone. After flashing , reboot and install kernel auditor here https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor so we can see what's going on with the kernel
Edit:also, you could flash TWRP with this file as well https://dl.twrp.me/marlin/twrp-pixel-installer-marlin-3.2.3-1.zip.html (you flash the zip while in TWRP) to not have to use fastboot to boot into it )
Click to expand...
Click to collapse
Apparently i didn't knock on wood hard enough. Was working for a solid 45 minutes to an hour, but then as I was reading through some stuff it froze up and went back into boot looping..

premedicated said:
Done, done and done.
I flashed TWRP through the zip, so it's a more permanent fixture. Magisk is installed as well as the kernel adiutor. What type of data/info am i looking for through the kernel program?
---------- Post added at 11:19 PM ---------- Previous post was at 10:47 PM ----------
Apparently i didn't knock on wood hard enough. Was working for a solid 45 minutes to an hour, but then as I was reading through some stuff it froze up and went back into boot looping..
Click to expand...
Click to collapse
No! OMG I'm sorry man. I thought we had this problem on its way to being solved. So it's now boot looping again ? Same exact thing as before ?

Phalanx7621 said:
No! OMG I'm sorry man. I thought we had this problem on its way to being solved. So it's now boot looping again ? Same exact thing as before ?
Click to expand...
Click to collapse
Well here's the deal.. Right after I posted that it started bootlooping again. It went through about 6 bootloops before I said 'eff it' and then just plugged it into the charger and walked away. I came back to it a little bit ago and according to the Kernel manager, it has an uptime of an hour and 32 minutes. So I grabbed it and was dinking around for a minute with it. Downloaded hulu, no problems. Downloaded netflix, no problems and then I was writing out a text and all of a sudden it froze and rebooted. Bootlooped once, then on the second try it started up. It's been up for about half an hour now.
Are there some sort of .log files with Android that could possibly show exactly what it is that's causing it to restart? Maybe something in the Kernel manager could help?

Question Unbrick tool for the 6/6 Pro yet?

So here's the story, TL;DR at bottom.
So I have been checking out gaming phones for a little bit and saw the RedMagic 6 Pro and was captivated by its glowing RGB, 16GB of RAM, high refresh screen, a delicate and strange but mighty internal fan and A BATTERY THAT WOULD LAST ME ALL DAY.
So naturally I ordered the phone as soon as it launched in NA and waited about a week and before I got it. Once I did, it was like Willy Wonka and I was Charlie with a golden ticket.
At first I didn't notice anything wrong, maybe these glitches were there all along and I just never noticed it. After some steady usage, I started noticing little things here and there that were annoying, like the app switcher not opening sometimes, not closing apps, notifications not showing, misspelled words in the Settings app. You know, annoying stuff like that.
Obviously I tried to do factory resets a couple times to see if it would help but nothing fixed it so my conclusion was that something was wrong with the software itself.
My next idea was to download and try to I guess manually update the phone in hopes that that would also reload part of the system...¯\_(ツ)_/¯
Went to the global rom page on redmagic.gg>downloaded the rom to my computer that matched my phone model>factory reset the phone>copied update over>manual install through settings>phone says installing... whatever>then reboots to the RedMagic boot logo and never goes from there.
So now I'm sitting here, clearly devastated by the loss of my little pocket heater, my side table light show, my phone I use to cheat on Apple and iPhone with (shh don't tell Siri).
Things I've already tried>
1) More factory resets through the recovery
2) Letting the battery die and then charging it.... ¯\_(ツ)_/¯
3) extracting .img from payload update file and flashing through fastboot (always fails due to locked bootloader)
4) Reaching out to Nubia support, I don't think they like me because they haven't answered back yet.
TL;DR -- Is there a way to unbrick/reflash the 6 or 6 Pro with a locked bootloader yet?​

waiting for same thing.... quite sad that i can't use my phone just from an update

Yeah, there is a number of us in the same position. We could start a club. The really expensive paperweight club or something. I've also reached out to support. They asked a couple of questions, I promptly answered, and thin it's been crickets since.

Are you unable to unlock the bootloader?

chocolote4444 said:
Are you unable to unlock the bootloader?
Click to expand...
Click to collapse
yes my phone open bootlooder

chocolote4444 said:
Are you unable to unlock the bootloader?
Click to expand...
Click to collapse
No I never really got a chance to do it and now since I can't boot, I can't unlock it.

my redmagic 6 pro stuck on fastboot mode since from 4 days. i have tried 2/3 process from some website which are for redmagic 5g, still same situation. I can't use my phone.waiting to get unbrick tools for remagic 6 pro and twrp file

shakhawat1993 said:
my redmagic 6 pro stuck on fastboot mode since from 4 days. i have tried 2/3 process from some website which are for redmagic 5g, still same situation. I can't use my phone.waiting to get unbrick tools for remagic 6 pro and twrp file
Click to expand...
Click to collapse
Are you unlocked? Did you flash anything?

CyberWolf92 said:
So here's the story, TL;DR at bottom.
So I have been checking out gaming phones for a little bit and saw the RedMagic 6 Pro and was captivated by its glowing RGB, 16GB of RAM, high refresh screen, a delicate and strange but mighty internal fan and A BATTERY THAT WOULD LAST ME ALL DAY.
So naturally I ordered the phone as soon as it launched in NA and waited about a week and before I got it. Once I did, it was like Willy Wonka and I was Charlie with a golden ticket.
At first I didn't notice anything wrong, maybe these glitches were there all along and I just never noticed it. After some steady usage, I started noticing little things here and there that were annoying, like the app switcher not opening sometimes, not closing apps, notifications not showing, misspelled words in the Settings app. You know, annoying stuff like that.
Obviously I tried to do factory resets a couple times to see if it would help but nothing fixed it so my conclusion was that something was wrong with the software itself.
My next idea was to download and try to I guess manually update the phone in hopes that that would also reload part of the system...¯\_(ツ)_/¯
Went to the global rom page on redmagic.gg>downloaded the rom to my computer that matched my phone model>factory reset the phone>copied update over>manual install through settings>phone says installing... whatever>then reboots to the RedMagic boot logo and never goes from there.
So now I'm sitting here, clearly devastated by the loss of my little pocket heater, my side table light show, my phone I use to cheat on Apple and iPhone with (shh don't tell Siri).
Things I've already tried>
1) More factory resets through the recovery
2) Letting the battery die and then charging it.... ¯\_(ツ)_/¯
3) extracting .img from payload update file and flashing through fastboot (always fails due to locked bootloader)
4) Reaching out to Nubia support, I don't think they like me because they haven't answered back yet.
TL;DR -- Is there a way to unbrick/reflash the 6 or 6 Pro with a locked bootloader yet?​
Click to expand...
Click to collapse
could you please tell me your process, how did you try to flash ? my bootloader is unlocked even though I could not flash with .img file, everytime it's showing - FAILED (no such partition)

numbawon said:
Are you unlocked? Did you flash anything?
Click to expand...
Click to collapse
yes ,phone is unlocked, when i go for flashing with miflash, no .img file showing, or /and to install twrp,its showing no such partition

numbawon said:
Are you unlocked? Did you flash anything?i
Click to expand...
Click to collapse
i unlocked bootloader. i flash twrp after that it stuck on fastboot mode

shakhawat1993 said:
i unlocked bootloader. i flash twrp after that it stuck on fastboot mode
Click to expand...
Click to collapse
Where is everybody getting TWRP? I don't think there is one yet for the 6 yet. Not till there is kernel source available.
I have the rom extracted here for both the EU and NA/Asia releases. In each is an output folder. You need to flash the boot.img.
in Treble based roms the boot and recovery are in the boot.img. So you flashed over the whole boot image with TWRP that isn't working for the 6 yet, so it defaults to fastboot.

numbawon said:
Where is everybody getting TWRP? I don't think there is one yet for the 6 yet. Not till there is kernel source available.
I have the rom extracted here for both the EU and NA/Asia releases. In each is an output folder. You need to flash the boot.img.
in Treble based roms the boot and recovery are in the boot.img. So you flashed over the whole boot image with TWRP that isn't working for the 6 yet, so it defaults to fastboot.
Click to expand...
Click to collapse
i flashed with redmagic 5g twrp on my redmagic 6 pro. my bad

shakhawat1993 said:
i flashed with redmagic 5g twrp on my redmagic 6 pro. my bad
Click to expand...
Click to collapse
You have been very bad. You will be punished. *invites in the scary nurse with the big paddle*

@shakhawat1993 see this other post as it explains some more in it just in case it's helpful.

shakhawat1993 said:
my redmagic 6 pro stuck on fastboot mode since from 4 days. i have tried 2/3 process from some website which are for redmagic 5g, still same situation. I can't use my phone.waiting to get unbrick tools for remagic 6 pro and twrp file
Click to expand...
Click to collapse
i was in same situation like you,,start RM6 only on fastboot but thie works ,download you rom from this page https://drive.google.com/drive/mobile/folders/1BE4FSGDcfXavYoJ3Kw3toGMiPHgCGakC?usp=sharing
extract boot.img to your folder with fastboot
start mobile in fastboot
and open cmd.
fastboot device
if you see your device try next command
fastboot flash boot boot.img
restart your phone and you have stock recovery,,wipe data and you have unbricked device
i download latest twrp but not working and after install twrp i was stucked in fast boot like you

I pulled apart the RM5 unbrick tool to see if I can learn anything that might help us that are stuck at the logo screen. So obviously this contains the RM5 rom right now.
It contains all the firehose files and script and such and obviously the image to the RM5. I was looking into if it could be used to recover the RM6. I've been slammed at work and not been able to dig into it as I'd like, but i have it located here if anybody wants to dig into it too.

numbawon said:
I pulled apart the RM5 unbrick tool to see if I can learn anything that might help us that are stuck at the logo screen. So obviously this contains the RM5 rom right now.
It contains all the firehose files and script and such and obviously the image to the RM5. I was looking into if it could be used to recover the RM6. I've been slammed at work and not been able to dig into it as I'd like, but i have it located here if anybody wants to dig into it too.
Click to expand...
Click to collapse
It would great if can just replace those system, recovery, boot etc in folder, then boom it works lol...

Nocturne Seigneur said:
It would great if can just replace those system, recovery, boot etc in folder, then boom it works lol...
Click to expand...
Click to collapse
That's what I was hoping for but worried it's going to take more than just that, like the GPT layout and some other things.

For sure you will need the partition table, rawprogram, & a firehose for the SD888; I'd be surprised if the one for the RM5 would work on the RM6.

Bootloop (?) dm-verity corruption

So my phone is stuck on this issue. I haven't done anything wrong. My phone was just peacefully charging then the phone switches off by itself then the bootloop happened.
This showed on the screen:
dm-verity corruption
your device is corrupt.
it can't be trusted and my not work properly.
press enter button to continue.
Or, device will power off in 5s.
(written in white)
Although it does turn off by itself if I ignore it, after I turn it on again and press enter or power button it boot until lockscreen and if I try to do something like unlocking, scrolling down notifs bar, and sliding through different page on home screen it will turn off again. It seem like it's crashing. The thing is I am not trying to root or flash something. I haven't done anything on my phone. I only have one phone and I badly need your help. I hope wiping or reformatting the phone is my last resort. My phone is updated to Android 11 and lateset MIUI (provided by the system itself and not downloaded somewhere). Thank you.

Well seems like something is corrupt.
It reboots when you touches the screen(or do anything)?

LR7875 said:
It reboots when you touches the screen(or do anything)?
Click to expand...
Click to collapse
It's more like it turns itself off again and if I try to press again power button if the problem show again, same thing happen. Sometimes MIUI logo appears and shuts down again it can't even go to lock screen.

Is there any chance you can unlock it?
It seems like your internal storage is corrupted.

LR7875 said:
Is there any chance you can unlock it?
It seems like your internal storage is corrupted.
Click to expand...
Click to collapse
At some point I did manage to unlock it but it happened only once and when I tried to open the notifs by scrolling down or tried to different part of homescreen it just shuts down. After that, it can't even go to the lockscreen after reboot. It's a never ending cycle. I can go to fastboot mode but I don't know if I can do miracle with that.

Well immediately plug into a computer and pull photos amd videos from it if you get it unlocked.

LR7875 said:
Well immediately plug into a computer and pull photos amd videos from it if you get it unlocked.
Click to expand...
Click to collapse
I reformatted it hoping that it will fix the problem. I was wrong. *sigh*

hyung_z said:
I reformatted it hoping that it will fix the problem. I was wrong. *sigh*
Click to expand...
Click to collapse
Well most likely your EMMC internal storage chip went bad R.I.P. (well maybe you sending those emojis will be more appropriate, but, oh well)
Maybe search more on google, I can't help you more

LR7875 said:
Well most likely your EMMC internal storage chip went bad R.I.P. (well maybe you sending those emojis will be more appropriate, but, oh well)
Maybe search more on google, I can't help you more
Click to expand...
Click to collapse
Do you think service center can help me with this or they'll probably just say to replace the phone if a bad chip is the case?

Maybe they will replace the motherboard with some fee. Or they will try to convince you to buy a new fancy phone just purely because xiaomi could earn more.
Thats all about luck (and problem is on xiaomi side, not your fault)

what's the smartphone model?

Redmi note 8 pro is the OP's phone.
Wait Wait just found some interesting lead.
Xiaomi needs a better way to unbrick its devices instead of Authorized Mi Accounts
Xiaomi has locked down the EDL mode on all of its devices, making it nigh impossible to unbrick a device without an Authorized Mi Account. Read on for more!
www.xda-developers.com
Patched SP flash tool!

heh, i have the same phone. reflash yours with the firmware that was on it before everything that happened. but don't flash userdata if you want your data on it
flashing it is simple process

LR7875 said:
Redmi note 8 pro is the OP's phone.
Wait Wait just found some interesting lead.
Xiaomi needs a better way to unbrick its devices instead of Authorized Mi Accounts
Xiaomi has locked down the EDL mode on all of its devices, making it nigh impossible to unbrick a device without an Authorized Mi Account. Read on for more!
www.xda-developers.com
Patched SP flash tool!
Click to expand...
Click to collapse
there is already a way to flash it with SPFT without authorization
also he must try to flash it in fastboot because it's not bricked

AsyJAIZ said:
there is already a way to flash it with SPFT without authorization
also he must try to flash it in fastboot because it's not bricked
Click to expand...
Click to collapse
He probably doesn't have his bootloader unlocked.
Fastboot OEM unlock wont work as oem unlock is probably not enabled in settings dev options.

LR7875 said:
He probably doesn't have his bootloader unlocked.
Fastboot OEM unlock wont work as oem unlock is probably not enabled in settings dev options.
Click to expand...
Click to collapse
ok i got it, then he should somehow put it in download mode...

Do you guys think I need to go to the service center because I don't know what to do. I really don't want to brick my phone. But a while ago my phone booted. I set it up just like buying a new phone but after I finished setting up, I just wait for the phone to catch up because I was afraid the phone will just shut down suddenly. And then, it happened again the phone shut downs without me doing anything. Now I tried to boot it up again but it is currently stuck at Redmi logo (plus "powered by android" at the bottom").

hyung_z said:
Do you guys think I need to go to the service center because I don't know what to do. I really don't want to brick my phone. But a while ago my phone booted. I set it up just like buying a new phone but after I finished setting up, I just wait for the phone to catch up because I was afraid the phone will just shut down suddenly. And then, it happened again the phone shut downs without me doing anything. Now I tried to boot it up again but it is currently stuck at Redmi logo (plus "powered by android" at the bottom").
Click to expand...
Click to collapse
SPFT enables when phone is a brick, so there's no need in service center.
they will flash it like we are going to do

Help, does anyone know how to fix dm-verity corruption? I was using my tab normally, then it suddenly shuts down and this error keeps popping up whenever my device boots. It goes on a loop unless I press the power button again.

deleted

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.