Right now I am devastated and beyond frustrated. Really hoping someone can help me. Last night I decided to reboot my Redmi Note 7 Pro however now for some reason instead of booting back into system like usual it got stuck on the "Redmi Note 7 Pro by Xiaomi" logo, after about 5 minutes it finally boots into recovery mode. No matter what I try or how many times I try rebooting the same exact thing keeps happening and I have no idea why! Only other option I have is booting into fastboot mode however my PC won't even detect the Note 7 when plugged in, Note 7 wont get power at all including when plugging into charger.
I had unlocked my bootloader and rooted, following the tutorial on here, running MIUI 10.3.5 Chinese rom. Apparently there's a newer version but I hadn't bother to update yet. Everything was working perfectly. All I was doing was a simple reboot so I have no idea why this is happening? My only explanation is that maybe Xiaomi tried updating MIUI when I rebooted my phone and it got corrupted somehow?
Would really appreciate advice on how this can be fixed if so? I guess if this can be fixed I'm going to be losing all my data? Right now I'm holding onto a glorified brick, it really sucks, talk about a bad day!
If it boots to twrp recovery any how than maybe you can take the data from there without losing it and if it not booting to recovery then you reflashed the twrp recovery and mount it there and the data to your pc
Thanks for replying. It boots into stock 3.0 recovery only options I have is reboot, wipe clean and mi assistant. It keeps looping into recovery until battery drains flat. I don't know why it started doing this all of a sudden? I didn't even do anything to cause this!
I have accepted the fact I will lose my data, I just want my phone fixed. Can anyone give me instructions on how to do this please?
toyspeed said:
Thanks for replying. It boots into stock 3.0 recovery only options I have is reboot, wipe clean and mi assistant. It keeps looping into recovery until battery drains flat. I don't know why it started doing this all of a sudden? I didn't even do anything to cause this!
I have accepted the fact I will lose my data, I just want my phone fixed. Can anyone give me instructions on how to do this please?
Click to expand...
Click to collapse
Now u r not able to rebooting to twrp? Right? So u should install twrp using fastboot again beacuse ur bootloader is unloacked. Then download any cus rom in your pc and push that rom in your phone when you are on twrp using following command-
adb push "whatistheromyouhavedownloaded.zip" /sdcard/
Then select the zip and install wia twrp. Once your rn7p get back into life you can again flash fastboot miui rom and root it.
Alternate you can try flashing wia mi flash tool since bl is unlocked so u can flash the fastboot rom for rn7p.
Byt the way which twrp u were using? Official one or peter?
Sent from my Redmi Note 7 Pro using XDA Labs
toyspeed said:
Right now I am devastated and beyond frustrated. Really hoping someone can help me. Last night I decided to reboot my Redmi Note 7 Pro however now for some reason instead of booting back into system like usual it got stuck on the "Redmi Note 7 Pro by Xiaomi" logo, after about 5 minutes it finally boots into recovery mode. No matter what I try or how many times I try rebooting the same exact thing keeps happening and I have no idea why! Only other option I have is booting into fastboot mode however my PC won't even detect the Note 7 when plugged in, Note 7 wont get power at all including when plugging into charger.
I had unlocked my bootloader and rooted, following the tutorial on here, running MIUI 10.3.5 Chinese rom. Apparently there's a newer version but I hadn't bother to update yet. Everything was working perfectly. All I was doing was a simple reboot so I have no idea why this is happening? My only explanation is that maybe Xiaomi tried updating MIUI when I rebooted my phone and it got corrupted somehow?
Would really appreciate advice on how this can be fixed if so? I guess if this can be fixed I'm going to be losing all my data? Right now I'm holding onto a glorified brick, it really sucks, talk about a bad day!
Click to expand...
Click to collapse
Try using the MiFlash Tool, it might not appear in your PC as a device but might get detected in MiFlash
hackermssharma said:
Now u r not able to rebooting to twrp? Right? So u should install twrp using fastboot again beacuse ur bootloader is unloacked. Then download any cus rom in your pc and push that rom in your phone when you are on twrp using following command-
adb push "whatistheromyouhavedownloaded.zip" /sdcard/
Then select the zip and install wia twrp. Once your rn7p get back into life you can again flash fastboot miui rom and root it.
Alternate you can try flashing wia mi flash tool since bl is unlocked so u can flash the fastboot rom for rn7p.
Byt the way which twrp u were using? Official one or peter?
Sent from my Redmi Note 7 Pro using XDA Labs
Click to expand...
Click to collapse
I used twrp found here when I root my phone, I never needed to use again after that everything was perfect until now:
https://forum.xda-developers.com/re...overy-unofficial-twrp-touch-recovery-t3921637
I try using your advice, I put into fastboot and plug into PC, which recognize it being plugged by sound, otherwise shown no other sign of being connected to RN7P. I use powershell and all I get is this following message when trying to make connection with phone:
"
adb : The term 'adb' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ adb devices
+ ~~~
+ CategoryInfo : ObjectNotFound: (adb:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Suggestion [3,General]: The command adb was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\adb". See "get-help about_Command_Precedence" for more details.
PS C:\platform-tools>
"
I don't know what to do?
toyspeed said:
Right now I am devastated and beyond frustrated. Really hoping someone can help me. Last night I decided to reboot my Redmi Note 7 Pro however now for some reason instead of booting back into system like usual it got stuck on the "Redmi Note 7 Pro by Xiaomi" logo, after about 5 minutes it finally boots into recovery mode. No matter what I try or how many times I try rebooting the same exact thing keeps happening and I have no idea why! Only other option I have is booting into fastboot mode however my PC won't even detect the Note 7 when plugged in, Note 7 wont get power at all including when plugging into charger.
I had unlocked my bootloader and rooted, following the tutorial on here, running MIUI 10.3.5 Chinese rom. Apparently there's a newer version but I hadn't bother to update yet. Everything was working perfectly. All I was doing was a simple reboot so I have no idea why this is happening? My only explanation is that maybe Xiaomi tried updating MIUI when I rebooted my phone and it got corrupted somehow?
Would really appreciate advice on how this can be fixed if so? I guess if this can be fixed I'm going to be losing all my data? Right now I'm holding onto a glorified brick, it really sucks, talk about a bad day!
Click to expand...
Click to collapse
Flash orange twrrp . then offcourse you lose all of your data
toyspeed said:
I used twrp found here when I root my phone, I never needed to use again after that everything was perfect until now:
https://forum.xda-developers.com/re...overy-unofficial-twrp-touch-recovery-t3921637
I try using your advice, I put into fastboot and plug into PC, which recognize it being plugged by sound, otherwise shown no other sign of being connected to RN7P. I use powershell and all I get is this following message when trying to make connection with phone:
"
adb : The term 'adb' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ adb devices
+ ~~~
+ CategoryInfo : ObjectNotFound: (adb:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Suggestion [3,General]: The command adb was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\adb". See "get-help about_Command_Precedence" for more details.
PS C:\platform-tools>
"
I don't know what to do?
Click to expand...
Click to collapse
Which platform and adb tools u r using update them to latest
Bro u flashed wrong twrp u flashed twrp of rn7 not of rn7 pro thats why u get in this situation. The link u share of twrp is of rn7 thread not of our rn7 pro
Sent from my Redmi Note 7 Pro using XDA Labs
Thank you guys for help, I finally fix today.
toyspeed said:
Thank you guys for help, I finally fix today.
Click to expand...
Click to collapse
Glad to know your issue is addressed.
Would it be asking for too much to know what steps you followed in order to fix the issue?
I hope that way rest of the community folks would gain some insight should they revisit this issue.
fusionboyz said:
Glad to know your issue is addressed.
Would it be asking for too much to know what steps you followed in order to fix the issue?
I hope that way rest of the community folks would gain some insight should they revisit this issue.
Click to expand...
Click to collapse
He had flashed the wrong recovery for his device so not much of a learning for the rest of the community.
Boot to fastboot & flash stock rom....its because your phone downloaded the rom & when you restart it tried installing rom but failed
Stuck on the logo
I Have a RN7P, in morning my device got restarting again and again and now it got stuck on the "Redmi Note 7 Pro by Xiaomi" logo. I haven’t done anything like unlock bootloader or flash any rom. But scared why this thing happening again and again.
Appreciate if someone can advise how to fix this issue without losing any data.
I got same problem in my own device Redmi note 7 it hanged in TWRP Recovery logo and iF you got any solution for this, give me solution.
I have redmi note7 pro this phone suddenly switch off then not working and not working charging what will do???????
Shavith said:
I have redmi note7 pro this phone suddenly switch off then not working and not working charging what will do???????
Click to expand...
Click to collapse
What u did ? Elaborate did u try to unlock BL or try to install recovery or a rom or any ohter zip? Explain
Sent from my Redmi Note 7 Pro using XDA Labs
hi i am facing an issue with my redmi note7s phone its showing reboot, wipe all data n phone name and i pressed lots of time but its not coming in normal mode plzz help me to get outof this issue
toyspeed said:
Right now I am devastated and beyond frustrated. Really hoping someone can help me. Last night I decided to reboot my Redmi Note 7 Pro however now for some reason instead of booting back into system like usual it got stuck on the "Redmi Note 7 Pro by Xiaomi" logo, after about 5 minutes it finally boots into recovery mode. No matter what I try or how many times I try rebooting the same exact thing keeps happening and I have no idea why! Only other option I have is booting into fastboot mode however my PC won't even detect the Note 7 when plugged in, Note 7 wont get power at all including when plugging into charger.
I had unlocked my bootloader and rooted, following the tutorial on here, running MIUI 10.3.5 Chinese rom. Apparently there's a newer version but I hadn't bother to update yet. Everything was working perfectly. All I was doing was a simple reboot so I have no idea why this is happening? My only explanation is that maybe Xiaomi tried updating MIUI when I rebooted my phone and it got corrupted somehow?
Would really appreciate advice on how this can be fixed if so? I guess if this can be fixed I'm going to be losing all my data? Right now I'm holding onto a glorified brick, it really sucks, talk about a bad day!
Click to expand...
Click to collapse
Same thing happened to me. Stuck in TWRP bootloop. I had already installed the custom rom I wanted. This solved my problem -
Input these command in TWRP recovery then reboot to system
"dd if=/dev/zero of=/dev/block/bootdevice/by-name/fota
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc"
I've precious pictures of my buddies baby data. I tried to flash my redmi note 7 pro without flashing the userdata using the Miracle Xiaomi Tool v1.58 but it didn't work its the same, Stuck on redmi logo can anybody help me to get my friends data off my phone. Thank You
I've encountered the same problem today....
Can anyone help me
I don't know about twrp or anything that has been mentioned above
Plz some one help me
Related
Restored my Honor back to stock rom from CM11 and now can't boot the phone into fastboot/rescue mode, anyone got any ideas?
BUMP
Solved my issue by myself.
Switch phone off and hold the volume down button as you plug the phone into the PC.
As you solved yourself you could let us know how you did.
theoneofgod said:
Switch phone off and hold the volume down button as you plug the phone into the PC.
As you solved yourself you could let us know how you did.
Click to expand...
Click to collapse
I'm aware of the correct way of doing but it wouldn't work. As there was zero replies in x number of views I took it that nobody knew the answer or was at least interested in the issue.
In the end I used the adb command to reboot the phone into fastboot and so forth.
And till then it's working fine again ?
You can get into fastboot as you want in the classic way ?
CSeb95 said:
And till then it's working fine again ?
You can get into fastboot as you want in the classic way ?
Click to expand...
Click to collapse
Now I'm getting replies .... I haven't tested it since I used adb.
Hey,
is there somebody else with the above problem? Because i have the same since i got my phone. I didnt tought this will be a big probem. But since i updated my honor 6 and something went wrong my phone is completely bricked, because it is in a bootloop and i can not enter bootloader nor fastboot mode or recovery. I am afraid that huawei says its my fault and denies warranty, so i am really intrested if there are more then two people out there with the same problem.
Thanks a lot
sideshowbob
sideshowbob84 said:
Hey,
is there somebody else with the above problem? Because i have the same since i got my phone. I didnt tought this will be a big probem. But since i updated my honor 6 and something went wrong my phone is completely bricked, because it is in a bootloop and i can not enter bootloader nor fastboot mode or recovery. I am afraid that huawei says its my fault and denies warranty, so i am really intrested if there are more then two people out there with the same problem.
Thanks a lot
sideshowbob
Click to expand...
Click to collapse
dude evem i am also facing the same problem , phone reboots continuously till honor logo ....what to do.how to flash it.
iitsanup said:
dude evem i am also facing the same problem , phone reboots continuously till honor logo ....what to do.how to flash it.
Click to expand...
Click to collapse
Same Problem man pls .....hlp......
Download Honor 6 Multi-tool and do the "Unbrick" trick through the fastboot menu. To enter fastboot first install Huawei USB drivers on PC and hold volume down when your phone is bootlooping with the USB cable connected to PC. Or use adb.exe from android sdk and type "adb reboot fastboot" when the screen shows "Honor" logo. Repeat the action by "copying\pasting" the command very fast until adb sends your commmand to the phone.
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.
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 :-\
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.
UPDATE: I've unbricked my phone! I used MSM Tool for OnePlus 7 Pro.
Here is a link to the video that saved my phone:
=====================================
Today i installed Android 10 Public Beta on my OnePlus 7 pro. It was great, i liked it. But i noticed i didn't have root. So i tried rooting it by flashing twrp.
Now this is where i fqed up. I flashed a TWRP image to boot. So i tried to boot into TWRP, but it just loaded back into fastboot. So i got myself stuck. But there is more.
I then wanted to give up and go back, but i couldn't find a OnePlus 7 pro stock boot image for Android 10. So i tried installing the latest version, and i thought it worked.
Now when i boot up my phone, it does the boot animation, but crashes in the process and turns off (Or i think so, the screen goes black). I for some reason can't access fastboot anymore. And i can't access the phone through adb. Windows makes a device connected sound, but doesn't show up anywhere.
Someone please help, what to do?
-HLVM
Use the MSM tool. That should sort you out.
HLVM said:
Today i installed Android 10 Public Beta on my OnePlus 7 pro. It was great, i liked it. But i noticed i didn't have root. So i tried rooting it by flashing twrp.
Now this is where i fqed up. I flashed a TWRP image to boot. So i tried to boot into TWRP, but it just loaded back into fastboot. So i got myself stuck. But there is more.
I then wanted to give up and go back, but i couldn't find a OnePlus 7 pro stock boot image for Android 10. So i tried installing the latest version, and i thought it worked.
Now when i boot up my phone, it does the boot animation, but crashes in the process and turns off (Or i think so, the screen goes black). I for some reason can't access fastboot anymore. And i can't access the phone through adb. Windows makes a device connected sound, but doesn't show up anywhere.
Someone please help, what to do? ((
-HLVM
Click to expand...
Click to collapse
You probably still have fastboot just not hitting the right buttons. Hold volume up and down and power untill you see fastboot mode. When you get there run fastboot -w (it will wipe your device) and see if it will boot then.
joemossjr said:
You probably still have fastboot just not hitting the right buttons. Hold volume up and down and power untill you see fastboot mode. When you get there run fastboot -w (it will wipe your device) and see if it will boot then.
Click to expand...
Click to collapse
Thanks for replying!
I did what you told me to, but fastboot never shows up. The screen is just black. But i can hear the phone disconnecting and connecting to my Windows pc
hallo dare said:
Use the MSM tool. That should sort you out.
Click to expand...
Click to collapse
Thanks for the suggestion, i will check it out
HLVM said:
Thanks for replying!
I did what you told me to, but fastboot never shows up. The screen is just black. But i can hear the phone disconnecting and connecting to my Windows pc
Click to expand...
Click to collapse
if its booting and windows is connecting something does it show up under adb devices?
dat_Noko said:
if its booting and windows is connecting something does it show up under adb devices?
Click to expand...
Click to collapse
Nope, the device doesn't show up when i run the command "adb devices". But i can see the device as "QUSB_BULK_CID:0404_SN:B8F829A6" in Device Manager
have you tried edl mode heres thread hope this helps you man if not dont give up on edl the screen dont come on but the exe will show connection heres fix ive done that to lg g5 hope this does it edl mode works forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595