Database Info

Need help. Phone has bad rom, can't access recovery

i may be up a creek now. i've tried everything i can.
here's the whole situation, maybe someone can offer some guidance on how i can get my phone back.
i installed this rom, http://forum.xda-developers.com/showthread.php?t=1835478, but did not see that there was a problem with people getting stuck at the initial google boot logo. i wouldn't have tried it if i did.
but it's too late now. so i too have that problem. in addition, i also have that problem with the nexus s in that the power button is busted, works only to boot the phone.
so i boot the phone normally, i get to that boot logo indefinitely.
i press up and power button i get to fastboot screen. for some reason the volume buttons don't work on that screen so i can't pick recovery there. only thing that works is hitting the power button and reboots the bootloader.
i plug the phone into my pc and i can't access it through adb, fastboot... does not recognize a device is connected.
so in summary, all i can do is access the fastboot screen or the boot logo screen.
if someone can help me figure out how to do one of the following: boot into recovery instead of fastboot, figure out how to use the volume buttons in fastboot, or get the phone recognized by my pc so i can use adb, that would be awesome.
i feel like i just bricked it for good....
thanks

Install the SDK. Launch it. Find the drivers to download in the SDK. Install them. Boot the phone into fastboot and connect it to pc. Open up a command prompt IN the directory that has fastboot in it. Type in the command prompt fastboot devices.
If your serial number shoes your good to go. Get the .img of your custom recovery and type fastboot flash recovery nameofile.img. with that being the exact file name ( hint type the first letter of the recovery and hit tab)

Yep, you gotta get fastboot working again. It's pretty important.
Sent from my Nexus S 4G using xda premium

i've had the sdk/driver installed already.
like i said, the phone when it boots is not being recognized by the laptop at all, as if it's not even plugged in. so when i do fastboot devices, nothing shows up.

Was it recognized prior?
Sent from my Nexus 7 using Tapatalk 2

in the prior rom it was recognized by the laptop, before i tried to flash the rom i linked above that created this mess...

albundy2010 said:
Install the SDK. Launch it. Find the drivers to download in the SDK. Install them. Boot the phone into fastboot and connect it to pc. Open up a command prompt IN the directory that has fastboot in it. Type in the command prompt fastboot devices.
If your serial number shoes your good to go. Get the .img of your custom recovery and type fastboot flash recovery nameofile.img. with that being the exact file name ( hint type the first letter of the recovery and hit tab)
Click to expand...
Click to collapse
AlphaEchoViktorSierra said:
Yep, you gotta get fastboot working again. It's pretty important.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Yep fastboot is a great tool, if you have a nexus s then you MUST get it working!
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
wookietv said:
i've had the sdk/driver installed already.
like i said, the phone when it boots is not being recognized by the laptop at all, as if it's not even plugged in. so when i do fastboot devices, nothing shows up.
Click to expand...
Click to collapse
Seems like your nexus s drivers are not installed in your laptop
google the nexus s usb drivers download them and put in the respective folder
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
albundy2010 said:
Was it recognized prior?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
was gonna ask the same question

like i said, i already had the sdk and drivers installed.
they worked fine before i installed that rom.
this definitely seems like it's on the fault of the phone, not the laptop.

looks like you got busted like a SIR!!
Just kidding man dont take it seriously...
I might sound silly but i hope you have tried this but if you have not then do try
Go here and try changing the usb plugs
http://forum.xda-developers.com/showthread.php?t=1785672
IT shows flashboot steps, you need to connect phone in bootloader mode which you are achieving atm, and see if it works
and if it doesnt then let me know i will try to help out more if i could
P.S I am also new in android so pardon my noobnes

i went another route...
i figured i had nothing to lose at this point... so i ripped the phone apart and attempted to fix the power button, which i believed in turn would fix not being able to use the volume keys in the fastboot screen.
i was correct. i jiggled with the power button inside and it seemed to work. the volume keys now reacted in the fastboot screen.
i was able to then get into recovery, wipe the phone, connect the phone to the laptop and put a new rom on it.
i'm not sure if its fixed the button completely, but at least i can get into the new rom :laugh:

well thats a relief and i am glad that you problem is solved
a little advice, get repaired that power button for good so that you have no hassle in near future

converse5 said:
well thats a relief and i am glad that you problem is solved
a little advice, get repaired that power button for good so that you have no hassle in near future
Click to expand...
Click to collapse
+1, I agree with you. It does not cost much as well. I had this problem and was managing with apps. But finally got it replaced for good.

[Q] My One is not booting at all, and does not react when i try to charge it

If i just use my charger, there is no response from the phone. When i try with the laptop, my laptop makes a sound to show that the phone has been plugged in, but the phone does not respond at all. I had a cm12 nightly flashed, and tried to flash Francos kernel on it, which made the phone get stuck on that blue alien logo when booting. After trying various fixes with no results, i just wiped everything ( i had no backups because i am a stupid ****) and then it got stuck on the Oneplus One logo. Now i am trying this http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541[1] and while i used the flash all.bat file, i noticed that cmd just kept showing waiting for device response (or something like that) which was weird, since it had completed some of the previous actions. Then i looked at my phone, with nothing at the screen. And it is now that it does not boot at all (not into the recovery, fast boot, normally, nothing) and does not show anything while i try to charge. What can i do?
Before the cmd process, the phone was showing up as a unit under Computer, but it is not anymore.
Just before, when i plugged it in, windows showed that something had been connected, but it did not know what, so i assume that there are some driver issues or something, though i have installed the qpst driver.
I also made a reddit post about it, where i got some response, but i could not go through with those either https://www.reddit.com/r/oneplus/comments/3bzwel/my_one_is_not_booting_at_all_and_does_not_react/
Do you know what i am doing wrong? Got any other fixes? Thanks in advance.

One get a otg cable then flash any custom rom using ur pen drive or go to adb and connect ur phone and check in device manager if it shows ur phone there or install any adb driver the try that flashall.bat it will surely work!! But I would say get a otg cable
Transmitted via Bacon

alan2500 said:
If i just use my charger, there is no response from the phone. When i try with the laptop, my laptop makes a sound to show that the phone has been plugged in, but the phone does not respond at all. I had a cm12 nightly flashed, and tried to flash Francos kernel on it, which made the phone get stuck on that blue alien logo when booting. After trying various fixes with no results, i just wiped everything ( i had no backups because i am a stupid ****) and then it got stuck on the Oneplus One logo. Now i am trying this http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541[1] and while i used the flash all.bat file, i noticed that cmd just kept showing waiting for device response (or something like that) which was weird, since it had completed some of the previous actions. Then i looked at my phone, with nothing at the screen. And it is now that it does not boot at all (not into the recovery, fast boot, normally, nothing) and does not show anything while i try to charge. What can i do?
Before the cmd process, the phone was showing up as a unit under Computer, but it is not anymore.
Just before, when i plugged it in, windows showed that something had been connected, but it did not know what, so i assume that there are some driver issues or something, though i have installed the qpst driver.
I also made a reddit post about it, where i got some response, but i could not go through with those either https://www.reddit.com/r/oneplus/comments/3bzwel/my_one_is_not_booting_at_all_and_does_not_react/
Do you know what i am doing wrong? Got any other fixes? Thanks in advance.
Click to expand...
Click to collapse
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
yashshan said:
One get a otg cable then flash any custom rom using ur pen drive or go to adb and connect ur phone and check in device manager if it shows ur phone there or install any adb driver the try that flashall.bat it will surely work!! But I would say get a otg cable
Transmitted via Bacon
Click to expand...
Click to collapse
That won't work, the phone isn't turning on.

Heisenberg said:
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
That won't work, the phone isn't turning on.
Click to expand...
Click to collapse
Thanks a lot, i dont know how i did not come upon that link while trying various fixes, now i can boot the phone again

Heisenberg said:
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
That won't work, the phone isn't turning on.
Click to expand...
Click to collapse
Uh, new problem, i used the toolkit to unlock the bootloader, and i had to use the Ultimate Tool kit to get TWRP on it. When i connect the phone to the pc (windows 7) i keep getting a message saying i have to format the phone before i can use it. When i click that, it says its writing protected. When i boot up the phone, it turns on, and i can go to the home screen (some times) but after a few seconds, it just turns off it self. Sorry for asking for your help again, but do you know of this problem? Google just came up with results for people with battery problems.

Heisenberg said:
Go here:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
That won't work, the phone isn't turning on.
Click to expand...
Click to collapse
I am just going to message you again before i mess up my phone even more, after a lot of hassle, i messed something up and redid the guide in the link you sended to me. According to the Oneplus one toolkit, my bootloader is unlocked. I can not enter fastboot, so i can not get a custom recovery or root. I can not turn on the phone normally either. I can Volume up+power button though, which takes me to the ColorOS RECOVERY screen. I would appreciate your help.

alan2500 said:
I am just going to message you again before i mess up my phone even more, after a lot of hassle, i messed something up and redid the guide in the link you sended to me. According to the Oneplus one toolkit, my bootloader is unlocked. I can not enter fastboot, so i can not get a custom recovery or root. I can not turn on the phone normally either. I can Volume up+power button though, which takes me to the ColorOS RECOVERY screen. I would appreciate your help.
Click to expand...
Click to collapse
Get rid of the toolkit,they're nothing but trouble. Plus, you don't need it. Plus, they allow you to bypass some very crucial learning experience. Power + volume up should take you to fastboot, not recovery, the button combo for recovery is power + volume down. Are you sure you can't get into fastboot? Is adb working in ColorOS recovery?

Heisenberg said:
Get rid of the toolkit,they're nothing but trouble. Plus, you don't need it. Plus, they allow you to bypass some very crucial learning experience. Power + volume up should take you to fastboot, not recovery, the button combo for recovery is power + volume down. Are you sure you can't get into fastboot? Is adb working in ColorOS recovery?
Click to expand...
Click to collapse
Oh brainfart, yup, its volume down+power that goes to the recovery. I just tried volume up+power, and now it goes into fastboot. I did try before, and the vibration was there, but no text on the screen. Not sure what to say about adb, when i launch adb.exe the CMD window just opens up, types a bunch in so fast that i cant read it, and then it closes down. It does the same thing when my phone is not plugged in, so i assume it does not work.

alan2500 said:
Oh brainfart, yup, its volume down+power that goes to the recovery. I just tried volume up+power, and now it goes into fastboot. I did try before, and the vibration was there, but no text on the screen. Not sure what to say about adb, when i launch adb.exe the CMD window just opens up, types a bunch in so fast that i cant read it, and then it closes down. It does the same thing when my phone is not plugged in, so i assume it does not work.
Click to expand...
Click to collapse
Ok, you're not meant to launch adb.exe like that though. You go to the folder where adb.exe is located, then hold shift and right click the mouse, and select "open command prompt here" from the menu, then you can issue adb commands. The same process goes for using fastboot. Anyway, now that you have access to fastboot all you should need to do is flash the stock images, go to section 8 of my guide thread for instructions:
http://forum.xda-developers.com/showthread.php?t=2839471

Heisenberg said:
Ok, you're not meant to launch adb.exe like that though. You go to the folder where adb.exe is located, then hold shift and right click the mouse, and select "open command prompt here" from the menu, then you can issue adb commands. The same process goes for using fastboot. Anyway, now that you have access to fastboot all you should need to do is flash the stock images, go to section 8 of my guide thread for instructions:
http://forum.xda-developers.com/showthread.php?t=2839471
Click to expand...
Click to collapse
Thanks a bunch, i got through it this time lol. So just to be sure that i do not end up bricking my phone again, can i just install TWRP, root, then dirty flash the latest CM nightly? I have no idea whats best to go with, and other than long battery life and good performance, i do not really have any needs, so i am thinking the latest cm will be fine. It was a nightly i was running before i bricked the phone actually.

alan2500 said:
Thanks a bunch, i got through it this time lol. So just to be sure that i do not end up bricking my phone again, can i just install TWRP, root, then dirty flash the latest CM nightly? I have no idea whats best to go with, and other than long battery life and good performance, i do not really have any needs, so i am thinking the latest cm will be fine. It was a nightly i was running before i bricked the phone actually.
Click to expand...
Click to collapse
Don't dirty flash, clean flash. Try out the Exodus ROM, great battery life and great features too.

Help me fix a bricked OPO :(

Phone memory was almost totally full and my sister was still shooting videos on it.
During one shoot the phone turned off and I can't turn it back on again.
Here is my problem, the phone just doesn't boot.
Shows only first screen with 1+ logo and then reboots. Not even the system boot animation.
When I try to enter recovery mode it shows TWRP screen and then reboots again. So I can't even access recovery.
And when I try to enter Fastboot Mode it turns on but the PC won't see it in adb.
What are my options here?

try charging the phone for a few hours

se7enlyn said:
try charging the phone for a few hours
Click to expand...
Click to collapse
yeah, forgot to mention that. can't even charge it. when I plug it in it does the same. tries to turn on. shows the first splash screen and reboots doing the same again and again. doesnt even show the charging screen with chinese text and battery animation.

sounds like u need a new battery

ireaper4592 said:
sounds like u need a new battery
Click to expand...
Click to collapse
already tried that too. had a replacement battery laying around. changed it and still no luck.

@bmark240
help please

se7enlyn said:
@bmark240
help please
Click to expand...
Click to collapse
hi you need to follow this guide :https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732

Hi.
Firstly, you have recovery installed, so that is good.
Some things for you to try:
Can you hold down the power button for longer than 10 seconds. This will clear temporary memory and hard reboot.Press power button & volume 'down' button until you enter TWRP.
Try this firstly.
Can you access ADB at all?
15 second ADB drivers should work.
What Operating system is on your Computer?
TWRP should pop up & be accessible
If you have Windows 10 on. If it doesn't recognize your phone you will have to run an update for Media Center for Windows 10 (64 bit...I'm assuming its not 32bit).
TWRP should be read by your computer if you can access it as it contains the drivers inbuilt.
If it still is inaccessible you might have to flash TWRP again through fastboot mode using ADB.

bmark240 said:
Hi.
Firstly, you have recovery installed, so that is good.
Some things for you to try:
Can you hold down the power button for longer than 10 seconds. This will clear temporary memory and hard reboot.Press power button & volume 'down' button until you enter TWRP.
Try this firstly.
Can you access ADB at all?
15 second ADB drivers should work.
What Operating system is on your Computer?
TWRP should pop up & be accessible
If you have Windows 10 on. If it doesn't recognize your phone you will have to run an update for Media Center for Windows 10 (64 bit...I'm assuming its not 32bit).
TWRP should be read by your computer if you can access it as it contains the drivers inbuilt.
If it still is inaccessible you might have to flash TWRP again through fastboot mode using ADB.
Click to expand...
Click to collapse
Yes, I have TWRP installed, but cant access it. Shows the TWRP splash screen and then reboots after like 10 seconds or so.
ADB does not see device. Only shows the device during that 10 second TWRP splash screen time, but even then no commands are effective and it just reboots.
Already tried holding down power button for few seconds. No luck.
I already installed all the possible drivers and media feature packs on my Windows 10. Still no luck.
And yes, I am running latest Windows 10 Pro x64.
And no, since I cant access Fastboot, I can not re-flash TWRP either.

kallum7 said:
hi you need to follow this guide :https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
Gonna try that right now. Hopefully that will fix it.

Daaaamn I really frankensteined the sh*t out of this one
I tried that Color OS unbrick method but it did not work. I mean the process itself worked, but the phone would not boot past the logo.
So I grabbed the system.img from old CM13 image, grabbed 2016 modem.img, then placed twrp.img instead of CM recovery and pressed START.
AAAAAND IT WORKED!!! The phone is alive!!!
Now I am in TWRP and I'm going to flash a new ROM. Hopefully everything will go perfectly.
Thanks a lot for your help @kallum7
EDIT: Flashed new ROM. Everything went just fine.

THEVAN3D said:
Daaaamn I really frankensteined the sh*t out of this one
I tried that Color OS unbrick method but it did not work. I mean the process itself worked, but the phone would not boot past the logo.
So I grabbed the system.img from old CM13 image, grabbed 2016 modem.img, then placed twrp.img instead of CM recovery and pressed START.
AAAAAND IT WORKED!!! The phone is alive!!!
Now I am in TWRP and I'm going to flash a new ROM. Hopefully everything will go perfectly.
Thanks a lot for your help @kallum7
EDIT: Flashed new ROM. Everything went just fine.
Click to expand...
Click to collapse
because i had bricked my phone a few months ago and that is how i got my phone back using the colour os

THEVAN3D said:
Phone memory was almost totally full and my sister was still shooting videos on it.
During one shoot the phone turned off and I can't turn it back on again.
Here is my problem, the phone just doesn't boot.
Shows only first screen with 1+ logo and then reboots. Not even the system boot animation.
When I try to enter recovery mode it shows TWRP screen and then reboots again. So I can't even access recovery.
And when I try to enter Fastboot Mode it turns on but the PC won't see it in adb.
What are my options here?
Click to expand...
Click to collapse
This is Bacon Root Toolkit (BRT) by WugFresh's
install file
https://drive.google.com/file/d/1DdFXrHPhVDlSzPqAk1PVfjK_Q0J_UzxO/view?usp=sharing
If you need stock rom
https://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
If you have any question find me on discord FiveO#8241 I will try help you out

FairuzOnn said:
This is Bacon Root Toolkit (BRT) by WugFresh's
install file
https://drive.google.com/file/d/1DdFXrHPhVDlSzPqAk1PVfjK_Q0J_UzxO/view?usp=sharing
If you need stock rom
https://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
If you have any question find me on discord FiveO#8241 I will try help you out
Click to expand...
Click to collapse
Thanks, but I already fixed it.

i had it in the past for some reason too. Managed to fix it using the color os method. Carefully followed the steps until i could flash again. That was a year ago tohugh. There should be some thread around wit some all-in-one solution against bricks.

Phone won't turn on, no system

I have a xiaomi redmi note 7 pro from china and I was planning on rooting it and changing the rom. Anyways I unlocked boot loader and installed twrp but couldn't install the rom using twrp recovery mode. Then I followed a video which rebooted the phone into recovery mode again after clearing some things. However, before rebooting it says no OS but the video did it anyways. In the video the phone rebooted back into recovery mode fine, but my phone does not boot. It constantly boots up to the redmi logo, flashes and boots again into redmi logo. This continues forever. I can, however, at this point enter fast boot. I thought the problem must be I have no rom so I just need to flash a rom. Using mi flash tool didn't work there was always some error and I turned the phone off. After turning the phone off, I cannot turn it back on again!!! Nothing, not holding power, not holding power + volume, just pure blank can't boot at all. I really don't know wtf I can do know it just doesn't turn on at all no matter what. Please help guys.

zhou111 said:
I have a xiaomi redmi note 7 pro from china and I was planning on rooting it and changing the rom. Anyways I unlocked boot loader and installed twrp but couldn't install the rom using twrp recovery mode. Then I followed a video which rebooted the phone into recovery mode again after clearing some things. However, before rebooting it says no OS but the video did it anyways. In the video the phone rebooted back into recovery mode fine, but my phone does not boot. It constantly boots up to the redmi logo, flashes and boots again into redmi logo. This continues forever. I can, however, at this point enter fast boot. I thought the problem must be I have no rom so I just need to flash a rom. Using mi flash tool didn't work there was always some error and I turned the phone off. After turning the phone off, I cannot turn it back on again!!! Nothing, not holding power, not holding power + volume, just pure blank can't boot at all. I really don't know wtf I can do know it just doesn't turn on at all no matter what. Please help guys.
Click to expand...
Click to collapse
1. Never boot into the system when there is a 'no OS' warning.
2. Use this TWRP next time (https://forum.xda-developers.com/redmi-note-7-pro/development/unofficial-twrp-3-3-1-proper-t3933531)
Does the phone charge or get detected by the computer when connected via USB?
If MiFlash doesn't seem to work try using ADB to Fastboot the ROM
If all hope is lost, the service centres can fix it.

Naveenthemi said:
1. Never boot into the system when there is a 'no OS' warning.
2. Use this TWRP next time (https://forum.xda-developers.com/redmi-note-7-pro/development/unofficial-twrp-3-3-1-proper-t3933531)
Does the phone charge or get detected by the computer when connected via USB?
If MiFlash doesn't seem to work try using ADB to Fastboot the ROM
If all hope is lost, the service centres can fix it.
Click to expand...
Click to collapse
when connected it is detected as qualcom 9008. I searched I think the phone is hardbricked, so can't enter fastboot. I think it can turn on and off. After holding power for 15 seconds, the usb is no longer detected. I could do the same to turn it back on. Do you know a service centre in Toronto?

Fcyrp Zip Need to Flash After Flash any Custom Rom
And Come in Telegram Official Group For Any Support of Redmi Note 7 Pro https://t.me/Rn7proGlobal

zhou111 said:
when connected it is detected as qualcom 9008. I searched I think the phone is hardbricked, so can't enter fastboot. I think it can turn on and off. After holding power for 15 seconds, the usb is no longer detected. I could do the same to turn it back on. Do you know a service centre in Toronto?
Click to expand...
Click to collapse
Yes it's hardbricked for sure! But are you sure MiFlash doesn't detect it?
If so any good service centre around you should be able to fix it, it's something to do with the software so they won't need Mi authorised parts...

Naveenthemi said:
Yes it's hardbricked for sure! But are you sure MiFlash doens't detect it?
If so any good service centre around you should be able to fix it, it's something to do with the software so they won't need Mi authorised parts...
Click to expand...
Click to collapse
Mi flash detects it as COM10 or COM20 depending on which USB. But when I flash I get error like no hello packet. Also I am not sure if I am suppose to put prog emmc sdm660 in the images folder or not.

zhou111 said:
Mi flash detects it as COM10 or COM20 depending on which USB. But when I flash I get error like no hello packet. Also I am not sure if I am suppose to put prog emmc sdm660 in the images folder or not.
Click to expand...
Click to collapse
Ok so Hello Packet errors are caused due to corrupted files or also if your flashing is interrupted in the middle
Try:
1. Making sure your PC isn't 32 bit
2. Draining out the phone battery and try again
3. Disabling driver signature enforcement(https://www.androidfoot.com/2016/08/how-to-disable-driver-signature.html)
4. An older version of MiFlash
5. If all of the above don't work ,try using another PC
6. Also make sure the USB ports are in working condition ( I think yours is working tho)

Naveenthemi said:
Ok so Hello Packet errors are caused due to corrupted files or also if your flashing is interrupted in the middle
Try:
1. Making sure your PC isn't 32 bit
2. Draining out the phone battery and try again
3. Disabling driver signature enforcement(https://www.androidfoot.com/2016/08/how-to-disable-driver-signature.html)
4. An older version of MiFlash
5. If all of the above don't work ,try using another PC
6. Also make sure the USB ports are in working condition ( I think yours is working tho)
Click to expand...
Click to collapse
My pc is 65 bit. I can't try #2 yet since it takes a while for battery to drain. I disabled driver signature enforce and using old mi flash and tried new pc still doesn't work. My boot loader is unlocked but maybe I accidently locked it? I don't know how to check.

zhou111 said:
My pc is 65 bit. I can't try #2 yet since it takes a while for battery to drain. I disabled driver signature enforce and using old mi flash and tried new pc still doesn't work. My boot loader is unlocked but maybe I accidently locked it? I don't know how to check.
Click to expand...
Click to collapse
Try this in ADB
(fastboot getvar all)
Without the brackets, now check for the unlocked line in the output and see if it shows yes or no
1. 64 eh, ok then no probs there
2. Oh ok take your time draining it
3. Try fastbooting the ROM via ADB see if that's works too

Naveenthemi said:
Try this in ADB
(fastboot getvar all)
Without the brackets, now check for the unlocked line in the output and see if it shows yes or no
1. 64 eh, ok then no probs there
2. Oh ok take your time draining it
3. Try fastbooting the ROM via ADB see if that's works too
Click to expand...
Click to collapse
I entered the command says waiting for device. how do you flash with adb?

zhou111 said:
I entered the command says waiting for device. how do you flash with adb?
Click to expand...
Click to collapse
Oh that means ADB isn't recognizing it.
There isn't much we can do if ADB doens't recognize it!
Did you look up for Service Centres?

zhou111 said:
I have a xiaomi redmi note 7 pro from china and I was planning on rooting it and changing the rom. Anyways I unlocked boot loader and installed twrp but couldn't install the rom using twrp recovery mode. Then I followed a video which rebooted the phone into recovery mode again after clearing some things. However, before rebooting it says no OS but the video did it anyways. In the video the phone rebooted back into recovery mode fine, but my phone does not boot. It constantly boots up to the redmi logo, flashes and boots again into redmi logo. This continues forever. I can, however, at this point enter fast boot. I thought the problem must be I have no rom so I just need to flash a rom. Using mi flash tool didn't work there was always some error and I turned the phone off. After turning the phone off, I cannot turn it back on again!!! Nothing, not holding power, not holding power + volume, just pure blank can't boot at all. I really don't know wtf I can do know it just doesn't turn on at all no matter what. Please help guys.
Click to expand...
Click to collapse
I had the same issue, but my phone went to fastboot from there I flashed it, the process was simple :
1. Download the fastboot rom and extract it (I guess two times, the first extraction extracts a file, open that with some extraction tool and uzip again, there you will see the fw with certain folders and images etc ).
2. Download the adb/fastboot zip file I"ll attach that here, extract it to the same folder where your fw files are. (fw = firmware).
3. You will find 3 bat files, flash all, flash all and lock, flash except storage, choose flash all (execute it).
4. Once done, reboot to recovery (stock), do a data wipe again.
This worked for me, hope it does for you too.
4.

hackeroid said:
I had the same issue, but my phone went to fastboot from there I flashed it, the process was simple :
1. Download the fastboot rom and extract it (I guess two times, the first extraction extracts a file, open that with some extraction tool and uzip again, there you will see the fw with certain folders and images etc ).
2. Download the adb/fastboot zip file I"ll attach that here, extract it to the same folder where your fw files are. (fw = firmware).
3. You will find 3 bat files, flash all, flash all and lock, flash except storage, choose flash all (execute it).
4. Once done, reboot to recovery (stock), do a data wipe again.
This worked for me, hope it does for you too.
4.
Click to expand...
Click to collapse
He/She said the phone doesn't boot into Fastboot either so that's very unlikely to work :-\

Bricked OnePlus 7 Pro - CrashDump Mode

So, i`m pretty sure my phone is hard bricked.
I was running with it for several months with no issues, so today i decided to flash EK 1.15 and then rebooted my phone, but instead of booting it went to CrashDump Mode and i can`t get it to boot or enter fastboot.
I`ve tried to use MSMtool but to software does not recognize my phone and on the device manager it shows as `Qualcomm HS-USB Diagnostics 900E`, on the CrashDump it shows `Could Not Decompress Initial ramdisk image.rd_load_disk`.
I`m opening a ticket with OnePlus, but as i live in Brazil and this phone was imported i think i`m fu****
Does anybody had this problem or knows if it is indeed a hardbrick?

So looks like i was trying to enter fastboot the wrong way...
I was able to boot into fastboot and then booted from there the TWRP image and then flash the stock image and TWRP and Magisk, after that i was able to boot normally.
Thank you guys anyway, as all the info was already on the forum, all i did was do a deep search.

bmonteiro said:
So looks like i was trying to enter fastboot the wrong way...
I was able to boot into fastboot and then booted from there the TWRP image and then flash the stock image and TWRP and Magisk, after that i was able to boot normally.
Thank you guys anyway, as all the info was already on the forum, all i did was do a deep search.
Click to expand...
Click to collapse
I'm so glad you got it up and running again! There's nothing worse than thinking there's no way out!

bmonteiro said:
So looks like i was trying to enter fastboot the wrong way...
I was able to boot into fastboot and then booted from there the TWRP image and then flash the stock image and TWRP and Magisk, after that i was able to boot normally.
Thank you guys anyway, as all the info was already on the forum, all i did was do a deep search.
Click to expand...
Click to collapse
Glad to see you got it. I had the same issue few days ago and, indeed, it was quite hard to run fastboot mode.
Sent from my GM1913 using XDA Labs

Good recovery! Cheers

I had a OnePlus 6t around the time they first came out and I ended up in crash dump mode probably 12-15 times, sometimes just randomly without doing anything to my phone..I would look at it and it was in crash dump. I recall the devs saying something about a fix for it back then... I have a OnePlus 7 pro 1917 global model now and I bought it used and only had it about one week now. Same exact cinereous. I looked down at my device on day one of me having it and there it was, crash dump mode. Since then on my Guac I've seen crash dumb four times. I've only flashed dotOS and DerpFest but the first crash dump I experienced on this phone was before I flashed anything. I was stock with TWRP installed.. I'm back at my home base now so if and when it happens again ill grab logs and share them. I have always been lucky enough to be able to get control of my device back by holding down power+ volume until I boot to bootloader and then tap power at the "start" screen and ive always booted back up. Have you all experienced crash dump mode often on 7 pro? Hopefully this will be fixed we some point.