Database Info

I need urgent help :(

Hey there... I was trying to get my OnePlus 7 -That I just bought - to a rooted Android 10, updating was the easy part but while trying to "fastboot flash boot twrp.img" I think I somehow got myself stuck making the bootloader (aka fastboot mode ) as my main thing the phone load into and now when I turn on the phone it goes straight to fastboot mode I go and try to "fastboot flash boot twrp.img" it says OKAY twice but I can't load into recovery it takws me back to the fast boot again.... Idk what to do... Help

More into:
I got to the twrp before once during the process and idk why dumb me rebooted when I couldn't access my phone files from pc I wanted to put the image of OOS on a flash drive and via OTG but once I restarted by mistake after that whatever choice I make on the fastboot screen will quickly restart and get back to the same screen, so I can do "fastboot flash boot twrp.img" successfully but I can't load to it I hit reboot to recover or Start or Reboot Bootloader nothing takes me to twrp,
Also when I try "fastboot flash recovery twrp.img"
It says sending recovery okay, writing recovery failed, (remote: (recovery_b) no such partition)
I hope to get any help and I'm sorry if it's an obvious thing I couldn't notice, I'm not the sharpest between my brothers. Momma says. ? with me. I'll appreciate it I promise.

Have you tried this Fastboot ROMS?

Use this:
https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
After that just put offical Rom zip for your region on internal memory and after that install update. voila

Unbrick tool also available for OxygenOS pie https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325 :good:

Help
same issue with me...whenever i try to recover using fastboot method,it gives an error like product name is sdm845 and required is msmnile
and when i use the msm tool , it gives an error of sahara server....
any help is highly appreciated.

sourabhone said:
same issue with me...whenever i try to recover using fastboot method,it gives an error like product name is sdm845 and required is msmnile
and when i use the msm tool , it gives an error of sahara server....
any help is highly appreciated.
Click to expand...
Click to collapse
"sahara server" problem : disable driver signature / update drivers
https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Qualcomm dr: https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/
you must to press power button at the same time you plug in usb cable.....keep trying and your computer will start installing drivers for Port 9008
(you can use Google Search for more Info about "sahara" problem)

First of all twrp.img is a recovery image. You would normally use fastboot flash recovery twrp.img.
Secondly, you aren't supposed to flash twrp.img but use fastboot boot twrp.img and then boot to twrp and flash the twrp installer. If you can boot into fastboot, type fastboot boot twrp.img(twrp.70 for android q) and then flash twrp installer and oos. And if you can't boot into recovery you will have to use the msm tool.

daitalos said:
"sahara server" problem : disable driver signature / update drivers
Qualcomm dr:
you must to press power button at the same time you plug in usb cable.....keep trying and your computer will start installing drivers for Port 9008
(you can use Google Search for more Info about "sahara" problem)
Click to expand...
Click to collapse
Thanks daitalos for the reply..
the drivers for 9008 are installed as visible in device manager...
the msm tool shows the phone as connected, when i start the process, it waits for loading firehose binary and waits there for 10 sec.....after that throws error of sahara communication failed (FH:258)
i again tried the volume up + power button combo but to no avail...
also there is no red led light on the phone while charging

sourabhone said:
Thanks daitalos for the reply..
the drivers for 9008 are installed as visible in device manager...
the msm tool shows the phone as connected, when i start the process, it waits for loading firehose binary and waits there for 10 sec.....after that throws error of sahara communication failed (FH:258)
i again tried the volume up + power button combo but to no avail...
also there is no red led light on the phone while charging
Click to expand...
Click to collapse
In device manager you can see "Qualcomm HS -USB QDLoader 9008 (com3 for example) ?
You tried another usb port (?)
in windows 10 it is better for the computer to have the "developer mode" enabled
Close any antivirus temporarily..
Run msm tool as Administrator ofcourse..
(I don't know but If you try with msm tool from here : https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
you should see the models it supports (GM1900, GM1901, GM1903, GM1905)
_I think the problem is on the computer and the communication with the device...
sry for english

Thanks
daitalos said:
In device manager you can see "Qualcomm HS -USB QDLoader 9008 (com3 for example) ?
You tried another usb port (?)
in windows 10 it is better for the computer to have the "developer mode" enabled
Close any antivirus temporarily..
Run msm tool as Administrator ofcourse..
(I don't know but If you try with msm tool from here : h t tp s: // forum . xda-developers . com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
you should see the models it supports (GM1900, GM1901, GM1903, GM1905)
_I think the problem is on the computer and the communication with the device...
sry for english
Click to expand...
Click to collapse
Thank you so much daitalos.
At last i was able to recover my phone from being a paperweight.Used my other laptop and it worked perfectly first time.Maybe my 1st laptop was having some issues.

Help needed in edl flashing!!!

I made a custom EDL cable of Type B and made my bricked note 7 pro go to EDL. I used a Data converter to do that. When I connected to Pc the device shows as a Unrecognized USB. Also not showing in MI FLash Tool. What to do?

Panda-Guy said:
I made a custom EDL cable of Type B and made my bricked note 7 pro go to EDL. I used a Data converter to do that. When I connected to Pc the device shows as a Unrecognized USB. Also not showing in MI FLash Tool. What to do?
Click to expand...
Click to collapse
What do you mean by Type B? Redmi note 7 pro never goes edl using deep flash cabels. U have to use test point method.

Unlock your phone if your phone booting into fastboot

Grajatyadav said:
Unlock your phone if your phone booting into fastboot
Click to expand...
Click to collapse
I did that

Panda-Guy said:
I did that
Click to expand...
Click to collapse
what you want to do?
if your phone goes to fastboot then flash custom recovery or flash stock rom.
Drivers installed??
---------- Post added at 10:15 PM ---------- Previous post was at 10:13 PM ----------
Panda-Guy said:
I made a custom EDL cable of Type B and made my bricked note 7 pro go to EDL. I used a Data converter to do that. When I connected to Pc the device shows as a Unrecognized USB. Also not showing in MI FLash Tool. What to do?
Click to expand...
Click to collapse
if its bricked it will already show itself in edl mode .just directly plug your original type c cable
check what it shows in pc.
you need drivers

[Hard Brick] My realme Q have hard brick after format data in TWRP

Help me. pls . i cant boot to fastboot

Lingg said:
Help me. pls . i cant boot to fastboot
Click to expand...
Click to collapse
If you have TWRP then you are saved otherwise you need to visit service centre.

Lingg said:
Help me. pls . i cant boot to fastboot
Click to expand...
Click to collapse
Search internet how to enter edl mode to flash ROM with Qfil

People are willing to help, but no response from the post creator. Many others might be in the same situation waiting for a solution. Come on.

I've bricked my device countless times but it only disabled booting to system and recovery for me. Fastboot always kept usable for me no matter how badly I messed up anything. Then I could flash twrp and vbmeta through fastboot.bat solution on PC and finally a working ROM from TWRP. What did you do? Please write about your situation in detail so I might try to come up with a solution. I'm also a realme Q user.

jijojamie said:
People are willing to help, but no response from the post creator. Many others might be in the same situation waiting for a solution. Come on.
Click to expand...
Click to collapse
You need to open your phone and "short" the board using a paperclip or tweezers
Install Qualcomm Snapdragon drivers on pc
When you connect your phone it will appear as Qualcomm 9008 in device manager of windows
Download Qfil flashing program from Qualcomm..install it. ..run it ..it will detect your phone
Flash stock fastboot rom to device using QFIL
nobody can do all the work for you
Google :
-Testpoint realme
-Qfil Qualcomm
-Qualcomm 9008 drivers
- fastboot stock ROM realme
-emmc firehose programmers files realme

KevMetal said:
You need to open your phone and "short" the board using a paperclip or tweezers
Install Qualcomm Snapdragon drivers on pc
When you connect your phone it will appear as Qualcomm 9008 in device manager of windows
Download Qfil flashing program from Qualcomm..install it. ..run it ..it will detect your phone
Flash stock fastboot rom to device using QFIL
nobody can do all the work for you
Google :
-Testpoint realme
-Qfil Qualcomm
-Qualcomm 9008 drivers
- fastboot stock ROM realme
-emmc firehose programmers files realme
Click to expand...
Click to collapse
Ohhh god, that's so advanced stuff.
Msg misunderstood...
I just said there maybe others in the same situation, not me. I won't dare to open my phone and do those stuff because i have messed many in the past. I am on stock rom and very happy..
I was just concerned about the person who posted this thread. Sorry if you misunderstood my msg.

I upgraded to realme ui 1.0, and then formatted data. The result is the same as you. Finally, I can only change the motherboard

gigdn said:
I upgraded to realme ui 1.0, and then formatted data. The result is the same as you. Finally, I can only change the motherboard
Click to expand...
Click to collapse
If you are on RUI 1.0, you will have fastboot and stock recovery access. You can download latest UI and install it via stock recovery. Why change MB?

KevMetal said:
You need to open your phone and "short" the board using a paperclip or tweezers
Install Qualcomm Snapdragon drivers on pc
When you connect your phone it will appear as Qualcomm 9008 in device manager of windows
Download Qfil flashing program from Qualcomm..install it. ..run it ..it will detect your phone
Flash stock fastboot rom to device using QFIL
nobody can do all the work for you
Google :
-Testpoint realme
-Qfil Qualcomm
-Qualcomm 9008 drivers
- fastboot stock ROM realme
-emmc firehose programmers files realme
Click to expand...
Click to collapse
I am not able to get emmc firehose file for realme x2 pro.. still searching for that. can you suggest me where to get?

phone not vibrate to power on after flash vbmeta for android 11 gsi

please any help , my phone "redmi 6a " , I tried to install android 11 gsi from google from this tutorial
Install Android 11 on GSI Supported Project Treble Devices
In this guide, we will show you how to install Android 11 GSI on Project Treble devices using two methods: TWRP and Fastboot Commands.
www.droidwin.com
, and flashing vbmeta.img by twrp was not clear for me as I must "select partition to flash image " as twrp says , so i flashed vbmeta.img one time as boot and another time as bootloader and then flash system.img as system and then install permissiver_v5.zip and then reboot , my phone now not powered on at all , even any logo not appear , i put it in charger and hold power button a lot but no vibration at all and also can't open twrp or fastboot as my hold on power button all it did is flash the above light led when it is in the charger , no any thing else , I think the problem is related to my mistake when flash vbmeta as i didn't know any option i must choose or what is the problem and how can i fix it please ?

You messed up your boot system.....

1. You need a PC
2. Redmi Drivers
3. USB CABLE
4. MiFlash tool and the stock ROM

Do you have MiFlash installed on your PC?

yes , it is installed , i connected the phone as you say but it is not read by the flash tool till now

Wait so has it been discovered or not

Tried different usb ports?

Keno_I said:
Wait so has it been discovered or not
Click to expand...
Click to collapse
not discovered as in this image , although in past days , it was discovered

Keno_I said:
Tried different usb ports?
Click to expand...
Click to collapse
yes

You cannot get into bootloader?

If you cant did you check if adb connects?

Keno_I said:
You cannot get into bootloader?
Click to expand...
Click to collapse
yes , i can't but i hope i use wrong program , did you see my attachment above , if this the program you say , then yes it can't read my device although i click driver and install the drivers from the program it self

Keno_I said:
If you cant did you check if adb connects?
Click to expand...
Click to collapse
adb devices not showing any device although my phone has the above tiny light circle that indicates that it is charging by the cable connected to my pc

Try fastboot devices
Or adb devices command

Keno_I said:
Try fastboot devices
Or adb devices command
Click to expand...
Click to collapse
tried them both

i want to know is the problem already is flash vbmeta as boot ?
and now what can i do ?

1. Windows PC with MiFlash Beta (!) tool
2. Download a Xiaomi Fastboot Rom
3. extract Rom to your PC
4. start MiFlash Beta tool and point to the extracted folder
5. press Vol+ & Vol- & Power on your Mi for 10 seconds and connect it to your PC while holding the buttons another second after plugging it in
6. press refresh button on MiFlash tool
7. if your drivers are installed correct, your phone should be visible on COM-Port XXX
8. press flash and hopefully it will be flashed
9. if not: try several times
10. wait until it boots to the welcome screen (around 5 mins)
now your phone should be useable again.

i will try those steps now and tell you , i thank you very much

Did it work?

Keno_I said:
Did it work?
Click to expand...
Click to collapse
no , mi flash tool can't read it but there are good and bad news , good is that from here
i could solve my problem using sp flash tool and all instructions in the above video , but bad is after that i tried to root my device using magisk patched boot image and then got infinite boot loop and also want now to solve it the same way by sp flash tool but phone restarts every 6 or 7 seconds so sp flash tool not working with me and also tried a lot of combinations of buttons to go in fast boot mode but invain so what you think i am supposed to do now

[Sovled] Unknown USB Device problem

Hi , yesterday I was flashing the MIUI official rom via the Spflash Tool and I unplugged it accidentally , after that I tried to reconnect it and it appear "Unknown USB Device (Descriptor Request Failed)" in the device manager. Is this fixable with software such as hydra , spflash tool or reinstalling the drivers? (Sorry for my bad English.)

phone is booting to OS or did you brick it?

yaro666 said:
phone is booting to OS or did you brick it?
Click to expand...
Click to collapse
I guess its bricked , I was flashing the miui 12 via the spflash tool but I unplugged the cable accidentally so now it became Unknown USB Device in the device management.

does it boot to fastboot?

yaro666 said:
does it boot to fastboot?
Click to expand...
Click to collapse
no , it even can't boot to the MediaTek mode (the mode which uses spflash tool).

then you bricked it. try edl or seqrch for someone with box

Okay so now the unknown usb device problem is fixed but theres a new problem. When I use the MediaTek EDL mode to flash the MIUI , it appeared a error "ext ram expectioned". It stucked at the "Download DA" process and after 60s the device disconnected from my pc and appeared that error.