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.

HTC One X Not Power On

Hello All,
Mine one friend is trying to flash custom rom in his AT&T One X and he hard bricked it, the phone is not responding on any key combination and also not booting directly in recovery. He was using TWRP Recovery and trying to flash this rom
http://onexroot.com/one-x-roms/icecoldjelly-aokp-rom-for-rooted-one-x-android-4-1-2/
Can anyone body help me in this regard or tell me any method which will work ?
Any help in this regard would highly appreciated.
Thanks in Advance.
Imk

imk79 said:
Hello All,
Mine one friend is trying to flash custom rom in his AT&T One X and he hard bricked it, the phone is not responding on any key combination and also not booting directly in recovery. He was using TWRP Recovery and trying to flash this rom
http://onexroot.com/one-x-roms/icecoldjelly-aokp-rom-for-rooted-one-x-android-4-1-2/
Can anyone body help me in this regard or tell me any method which will work ?
Any help in this regard would highly appreciated.
Thanks in Advance.
Imk
Click to expand...
Click to collapse
When you plug it into your USB cable do you have the charging light?
Also that rom is for the Tegra One X not the Dual Core Adreno One X, i've done this before and if im still right you can get into download mode you can go back to stock.

MrKickstand said:
When you plug it into your USB cable do you have the charging light?
Click to expand...
Click to collapse
No nothing is happen. Phone is giving no response

imk79 said:
No nothing is happen. Phone is giving no response
Click to expand...
Click to collapse
Hmm... Ok, on your computer go into Device Manager and plug in your phone to the PC and tell me what kind of sound it makes when it connects and if the device shows a triangle with a "!" in it on the device manager.

MrKickstand said:
Hmm... Ok, on your computer go into Device Manager and plug in your phone to the PC and tell me what kind of sound it makes when it connects and if the device shows a triangle with a "!" in it on the device manager.
Click to expand...
Click to collapse
When I connect the device nothing happened and device showed like in the attached screenshot.

imk79 said:
When I connect the device nothing happened and device showed like in the attached screenshot.
Click to expand...
Click to collapse
Ok, im pretty sure you can recover from that, especially since when i bricked mine it made an abnormal sound when i connected the usb and not the normal boobooop. Try ADB rebooting into bootloader mode or plug it into the USB Cable and Hold the Power + UP + DOWN at the same time and it should still push you into recovery mode. Also download the stock RUU, some of them have a bat you can run and itll do most of the work all you need to do is get into bootloader mode.

MrKickstand said:
Ok, im pretty sure you can recover from that, especially since when i bricked mine it made an abnormal sound when i connected the usb and not the normal boobooop. Try ADB rebooting into download mode or plug it into the USB Cable and Hold the Power + UP + DOWN at the same time and it should still push you into recovery mode. Also download the stock RUU, some of them have a bat you can run and itll do most of the work all you need to do is get into download mode.
Click to expand...
Click to collapse
Can you pls guide me about ADB Rebooting how can I perform it also I did Volume Down+ Power and Volume Down + Up + power button but nothing happen

imk79 said:
Can you pls guide me about ADB Rebooting how can I perform it also I did Volume Down+ Power and Volume Down + Up + power button but nothing happen
Click to expand...
Click to collapse
I didnt mean download mode since im still thinking about the S3, but i mean bootloader. But first off i assume you already have ADB and the Android SDK. So go into your android folder -> platform tools -> hold shift and right click in while your in platform tools and click Open Command Window here and once the window is open type in ADB Reboot Bootloader and see what it does. (i assume that while flashing a rom you had debugging enabled." BUT, also go here and download a RUU http://forum.xda-developers.com/showthread.php?t=2119610 , (id use AT&T USA and the 1.85.502.3 RUU, just click right under OTA and to the right you'll see "DOWNLOAD" and run that EXE to see if it works)

MrKickstand said:
I didnt mean download mode since im still thinking about the S3, but i mean bootloader. But first off i assume you already have ADB and the Android SDK. So go into your android folder -> platform tools -> hold shift and right click in while your in platform tools and click Open Command Window here and once the window is open type in ADB Reboot Bootloader and see what it does. (i assume that while flashing a rom you had debugging enabled." BUT, also go here and download a RUU http://forum.xda-developers.com/showthread.php?t=2119610 , (id use AT&T USA and the 1.85.502.3 RUU, just click right under OTA and to the right you'll see "DOWNLOAD" and run that EXE to see if it works)
Click to expand...
Click to collapse
Can you pls give me a link how to install ADB I remember once I have installed for my LG G2x but not sure is still exsist or not ? Can you pls tell me where is this Android Folder in my system ?

imk79 said:
Can you pls give me a link how to install ADB I remember once I have installed for my LG G2x but not sure is still exsist or not ? Can you pls tell me where is this Android Folder in my system ?
Click to expand...
Click to collapse
Here ya go.
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/

MrKickstand said:
Ok, im pretty sure you can recover from that,
Click to expand...
Click to collapse
You would be incorrect. QHSUSB_DLOAD mode after flashing IceColdJelly meant fo the ENDEAVORU is a death sentence. The device is in fact hard bricked, meaning the only fix is sending the phone for JTAG. The exception, is if the phone was originally on hboot 1.09 (somewhat unlikely at this point, unless the phone was pretty old).
http://forum.xda-developers.com/showthread.php?t=1974101
Couple mistakes were made here that led to this fatal condition:
1) Can't say this enough: DO NOT install mods from random websites. As clearly demonstrated here, these other random websites don't clearly delineate between the EVITA and ENDEAVORU, and this can brick your phone. Stick to the proper device forum on XDA.
2) Why did the person try to install a version of ICJ from 8 months ago? Unless you are doing it for a specific reason, installing obsolete firmware is kinda asking for problems, as well.

redpoint73 said:
You would be incorrect. QHSUSB_DLOAD mode after flashing IceColdJelly meant fo the ENDEAVORU is a death sentence. The device is in fact hard bricked, meaning the only fix is sending the phone for JTAG. The exception, is if the phone was originally on hboot 1.09 (somewhat unlikely at this point, unless the phone was pretty old).
http://forum.xda-developers.com/showthread.php?t=1974101
Couple mistakes were made here that led to this fatal condition:
1) Can't say this enough: DO NOT install mods from random websites. As clearly demonstrated here, these other random websites don't clearly delineate between the EVITA and ENDEAVORU, and this can brick your phone. Stick to the proper device forum on XDA.
2) Why did the person try to install a version of ICJ from 8 months ago? Unless you are doing it for a specific reason, installing obsolete firmware is kinda asking for problems, as well.
Click to expand...
Click to collapse
Thanks for the info
Any other solution rather then Jtag ?

imk79 said:
Any other solution rather then Jtag ?
Click to expand...
Click to collapse
If you originally rooted (or later RUUed) to 2.20 firmware or later, than no. If you were on 1.85 or 1.73 firmware, you can try the unbricking thread and/or JET tool. Unbricking thread is linked in the ICJ "warning" thread I posted above. JET tool can be found in the Development forum.

[Q] I need to return a broken rooted phone, and have a question before I do so...

I need to return a broken rooted phone, and have a question before I do so...
the phone has been rooted, and has the HellFire ROM installed. The phone currently won't boot up completely. It gets to the boot animation, and just loops forever. I first thought this was a battery issue, as I'm unable to even do a factory reset or get into download mode. After ordering a new battery, I found this wasn't the issue, and now need to send it back to tmobile.
now my question...
if I send it back, will they be able to tell if it's rooted, since it won't boot up, or is there a way I can make it impossible for them to find out? I've heard I can cook it in the microwave for a few seconds, but I'm not trying to blow anything up. LOL
any assistance would be greatly appreciated.

SevnSins said:
I need to return a broken rooted phone, and have a question before I do so...
the phone has been rooted, and has the HellFire ROM installed. The phone currently won't boot up completely. It gets to the boot animation, and just loops forever. I first thought this was a battery issue, as I'm unable to even do a factory reset or get into download mode. After ordering a new battery, I found this wasn't the issue, and now need to send it back to tmobile.
now my question...
if I send it back, will they be able to tell if it's rooted, since it won't boot up, or is there a way I can make it impossible for them to find out? I've heard I can cook it in the microwave for a few seconds, but I'm not trying to blow anything up. LOL
any assistance would be greatly appreciated.
Click to expand...
Click to collapse
Are you sure that you can't key combo into recovery?
If you have the time, make a jig to force your phone into download mode. Then you can use odin to flash stock.
If you are wanting to send it in for warranty because you can't accomplish the tasks above.
Then you have adb access on then run the tool in my signature and use the unroot command.
(It will take a while for adb to start up at the bootscreen but it does startup.)
Just make sure that you have drivers properly installed.
They shouldn't be able to tell the difference.

Lgrootnoob said:
Are you sure that you can't key combo into recovery?
If you have the time, make a jig to force your phone into download mode. Then you can use odin to flash stock.
If you are wanting to send it in for warranty because you can't accomplish the tasks above.
Then you have adb access on then run the tool in my signature and use the unroot command.
(It will take a while for adb to start up at the bootscreen but it does startup.)
Just make sure that you have drivers properly installed.
They shouldn't be able to tell the difference.
Click to expand...
Click to collapse
No, I've tried booting into recovery & download mode both several times, and they both are unsuccessful. When trying recovery, it displays the blue recovery starting text, but never goes into recovery. It just skips to the boot animation, and loops. When trying download mode, as soon as it asks to press volume up or down, the device powers off. it doesn't even give me the time to click anything.
Not sure what you mean by "make a jig to force download mode", but I'll give your second suggestion a try.
thanks

SevnSins said:
No, I've tried booting into recovery & download mode both several times, and they both are unsuccessful. When trying recovery, it displays the blue recovery starting text, but never goes into recovery. It just skips to the boot animation, and loops. When trying download mode, as soon as it asks to press volume up or down, the device powers off. it doesn't even give me the time to click anything.
Not sure what you mean by "make a jig to force download mode", but I'll give your second suggestion a try.
thanks
Click to expand...
Click to collapse
i downloaded your script, placed on a flash drive, and I'm getting the attached errors.

SevnSins said:
i downloaded your script, placed on a flash drive, and I'm getting the attached errors.
Click to expand...
Click to collapse
Which version of windows?
I have tested this script on four different machines,
It seems that your path variable is most likely messed up.(Unless you manage to find issues with my code which is appreciated too )
If you like then you can post the output of the path command while running adbClient and I can help you fix that problem.
Otherwise use the instadb command to fix this if you don't want to fix your potential path variable problem.
(instadb will install adb to the system)
Back to the topic at hand, Jig
There is a link to making a usb jig. (It is a VERY helpful link, as long as you take the time to read everything [The Xda way ] )
That can get you into download mode.
You can either go find a usb jig online and buy it, or you can make your own.
I also found this at the bottom of the page:
darkamikaze - "I got this from sparkfun. While it's not necessarily buying a complete jig, it saves the hassle of cutting a perfectly working usb cord
https://www.sparkfun.com/products/10031 "
I'm interested in the path thing though, so please do post the output of the path command being used inside the tool.

Lgrootnoob said:
Which version of windows?
I have tested this script on four different machines,
It seems that your path variable is most likely messed up.(Unless you manage to find issues with my code which is appreciated too )
If you like then you can post the output of the path command while running adbClient and I can help you fix that problem.
Otherwise use the instadb command to fix this if you don't want to fix your potential path variable problem.
(instadb will install adb to the system)
Back to the topic at hand, Jig
There is a link to making a usb jig. (It is a VERY helpful link, as long as you take the time to read everything [The Xda way ] )
That can get you into download mode.
You can either go find a usb jig online and buy it, or you can make your own.
I also found this at the bottom of the page:
darkamikaze - "I got this from sparkfun. While it's not necessarily buying a complete jig, it saves the hassle of cutting a perfectly working usb cord
https://www.sparkfun.com/products/10031 "
I'm interested in the path thing though, so please do post the output of the path command being used inside the tool.
Click to expand...
Click to collapse
I'm using Win7
I'm not as familiar with adb as I should be, as I haven't had to use it much through my experiences, so I don't really know my way around it that well.
instadb is asking for username & password info, and I don't know what goes in there.
I don't have a soldering iron, so I'll likely need to buy one it looks like.
I've attached the path output you requested.
thanks for your help

SevnSins said:
I'm using Win7
I'm not as familiar with adb as I should be, as I haven't had to use it much through my experiences, so I don't really know my way around it that well.
instadb is asking for username & password info, and I don't know what goes in there.
I don't have a soldering iron, so I'll likely need to buy one it looks like.
I've attached the path output you requested.
thanks for your help
Click to expand...
Click to collapse
Thanks for the path info.
If you want to build it then you can buy a soldering iron, but if you manage to buy an already built jig it might be cheaper and require less time. ey
instadb requires the username of an admin account on your machine and the password for that account. (It elevates user permissions then copies binaries to the system32 folder)
You can do this manually by copying the dlls for adb from the bin folder and the adb and fastboot executables from the bin folder into system32.
After that you shouldn't receive anymore errors.
Thanks for the info, apparently nothing is wrong with the path variable. (Whats weird is the "F:\-" in the photo you attached it should normally be drive letter:\path to adb , F:\bin in a variable)
Try my tool on a local drive. (Its finnicky sometimes )

Lgrootnoob said:
Thanks for the path info.
If you want to build it then you can buy a soldering iron, but if you manage to buy an already built jig it might be cheaper and require less time. ey
instadb requires the username of an admin account on your machine and the password for that account. (It elevates user permissions then copies binaries to the system32 folder)
You can do this manually by copying the dlls for adb from the bin folder and the adb and fastboot executables from the bin folder into system32.
After that you shouldn't receive anymore errors.
Thanks for the info, apparently nothing is wrong with the path variable. (Whats weird is the "F:\-" in the photo you attached it should normally be drive letter:\path to adb , F:\bin in a variable)
Try my tool on a local drive. (Its finnicky sometimes )
Click to expand...
Click to collapse
ok, looks like the script is working now, but I'm getting a "device unauthorized" error. The device is connected, and has the boot animation looping.
i also tried to reboot into recovery from your script, and get the same "device unauthorized" error.
screenshot attached.

SevnSins said:
ok, looks like the script is working now, but I'm getting a "device unauthorized" error. The device is connected, and has the boot animation looping.
i also tried to reboot into recovery from your script, and get the same "device unauthorized" error.
screenshot attached.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2401452
Its impossible to use adb at this point. (Never say never: Has adb worked before?)
You have a samsung phone right?
Your phone would have to be working to accept a key on screen for adb access.
The only thing now is the usb jig.

Lgrootnoob said:
http://forum.xda-developers.com/showthread.php?t=2401452
Its impossible to use adb at this point. (Never say never: Has adb worked before?)
You have a samsung phone right?
Your phone would have to be working to accept a key on screen for adb access.
The only thing now is the usb jig.
Click to expand...
Click to collapse
I do have a samsung phone (Galaxy S3), but I don't recall if I ever used adb with this phone. I know I've used it a few times in the past, but that could have been on my G1 & G2.
think I'm just going to put it in the microwave like I used to do my playstations. LOL! I need to get a working phone, and waiting for a jig to ship is going to take a few days I'm sure.
thanks again for all your help

SevnSins said:
I do have a samsung phone (Galaxy S3), but I don't recall if I ever used adb with this phone. I know I've used it a few times in the past, but that could have been on my G1 & G2.
think I'm just going to put it in the microwave like I used to do my playstations. LOL! I need to get a working phone, and waiting for a jig to ship is going to take a few days I'm sure.
thanks again for all your help
Click to expand...
Click to collapse
Well seems like a repair would leave you with the jig as the only option.
If your house burns down then I got your back there too.
You could just come chill with me.
Just make sure to post pics of your microwaved phone. (Or a video :laugh

Lgrootnoob said:
Well seems like a repair would leave you with the jig as the only option.
If your house burns down then I got your back there too.
You could just come chill with me.
Just make sure to post pics of your microwaved phone. (Or a video :laugh
Click to expand...
Click to collapse
well... where wasn't a fire, but I got a pretty cool spark. although; it still didn't "kill it" all the way. it's still try to boot up. I just decided to send it in, if they charge me for it, I'll just pay it. my job is taking over my phone bill anyways, so I shouldn't need to worry about it.
thank again for your help :good:

Phone won't boot up

I was trying wipe everything on the phone but for some reason it saids no OS. So when it boots up, I only see the google word on the screen.
Trying to flash the stock rom, followed instruction to install adb drivers...etc then boot the phone into fastboot mode,. This is the one screen I can get so far. Looks like my pc can't detect my phone. it saids failed when running those commands...Can someone give me a hint what to do next?
All I want is to put the stock rom back in.
thx

you didnt wipe data, you wiped your system partition, wiped the rom off your phone. and that screenshot is the stock recovery. you need to boot into the bootloader to flash the factory img(stock). the bootloader is the same as fastboot mode.

I did wipe data. I remember I checked that box
I also got this error in the command line.
simms22 said:
you didnt wipe data, you wiped your system partition, wiped the rom off your phone. and that screenshot is the stock recovery. you need to boot into the bootloader to flash the factory img(stock). the bootloader is the same as fastboot mode.
Click to expand...
Click to collapse

benzso63 said:
I did wipe data. I remember I checked that box
I also got this error in the command line.
Click to expand...
Click to collapse
before you tried any code.. did you do "fastboot devices" first, to make sure fastboot sees your phone?
also, sounds like you used twrp recovery. if you just swipe on the wipe screen, it wipes your partitions. if you chose advanced, then it gives you a list of things to wipe, then all you'd do is choose data and wipe.

I power down the phone, hit vol down + power. And I see the Fastboot mode
I connected the usb cable to my pc, but when I ran the code, it saids device not found. My pc can't see it
Now I am not using twrp at all just want to at least have the fastboot mode see my pc. but it is not.
Any other step i can make the phone communicate to my pc ?
simms22 said:
before you tried any code.. did you do "fastboot devices" first, to make sure fastboot sees your phone?
also, sounds like you used twrp recovery. if you just swipe on the wipe screen, it wipes your partitions. if you chose advanced, then it gives you a list of things to wipe, then all you'd do is choose data and wipe.
Click to expand...
Click to collapse

benzso63 said:
I power down the phone, hit vol down + power. And I see the Fastboot mode
I connected the usb cable to my pc, but when I ran the code, it saids device not found. My pc can't see it
Now I am not using twrp at all just want to at least have the fastboot mode see my pc. but it is not.
Any other step i can make the phone communicate to my pc ?
Click to expand...
Click to collapse
you're going to have to install that driver first, before it'll see your phone. you are using windows? try koushes universal adb driver for windows http://www.koushikdutta.com/post/universal-adb-driver

I did. I installed it. I have tried different drivers.
If I goto device manager, Android Device and under that it saids "Android Bootloader Interface".
I don't see anything saying Nexus or so.
simms22 said:
you're going to have to install that driver first, before it'll see your phone. you are using windows? try koushes universal adb driver for windows http://www.koushikdutta.com/post/universal-adb-driver
Click to expand...
Click to collapse

benzso63 said:
I did. I installed it. I have tried different drivers.
If I goto device manager, Android Device and under that it saids "Android Bootloader Interface".
I don't see anything saying Nexus or so.
Click to expand...
Click to collapse
If everything else fails try lg flashtool as a plan B. Link in my signagure.

Will try everything you say. Also this is a screen capture.
When I put the phone in fastboot mode, I notice this pops up under device manager (screen shot)
So does it mean it detects the phone right? But for some reason when I run the command code, it saids device not found.
bitdomo said:
If everything else fails try lg flashtool as a plan B. Link in my signagure.
Click to expand...
Click to collapse

benzso63 said:
Will try everything you say. Also this is a screen capture.
When I put the phone in fastboot mode, I notice this pops up under device manager (screen shot)
So does it mean it detects the phone right? But for some reason when I run the command code, it saids device not found.
Click to expand...
Click to collapse
It means you installed the drivers right.
Reboot your PC, try other USB port, close any unecessary apps in the background, avoid USB3.0 ports or run the flash-all.bat in administrator mode. These are the ideas that have come into my mind in this moment.

Oh by the way I was following your link.
RIght now my phone has the screen firmware update. do not unplug.. the usb connection until the process is complete....
Then follow the rest of your instructions.
Now how do I Enter your phone to Download Mode. ? Right now still with this screen "Firmware update".
bitdomo said:
It means you installed the drivers right.
Reboot your PC, try other USB port, close any unecessary apps in the background, avoid USB3.0 ports or run the flash-all.bat in administrator mode. These are the ideas that have come into my mind in this moment.
Click to expand...
Click to collapse

benzso63 said:
Oh by the way I was following your link.
RIght now my phone has the screen firmware update. do not unplug.. the usb connection until the process is complete....
Then follow the rest of your instructions.
Now how do I Enter your phone to Download Mode. ? Right now still with this screen "Firmware update".
Click to expand...
Click to collapse
When you see "Firmware update" that is the download mode. Watch the video I made. Maybe it explains everything more.

I got that part. Now I am using the LG Flash Tool, port 1 com41. I clicked the yellow arrow and screen showing it is ready. But on the phone I don't need any progress at all, it is till 0%. would it automatically run it itself ?
bitdomo said:
When you see "Firmware update" that is the download mode. Watch the video I made. Maybe it explains everything more.
Click to expand...
Click to collapse

benzso63 said:
I got that part. Now I am using the LG Flash Tool, port 1 com41. I clicked the yellow arrow and screen showing it is ready. But on the phone I don't need any progress at all, it is till 0%. would it automatically run it itself ?
Click to expand...
Click to collapse
What is shown on the PC?

Bro, now its running. I moved to usb 3.0 port. will keep you posted
Confirmed. Working Flawlessly ! OMG, you are my life saver. Really appreciate your hard work.
Man, you are the BEST !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
bitdomo said:
What is shown on the PC?
Click to expand...
Click to collapse

benzso63 said:
Bro, now its running. I moved to usb 3.0 port. will keep you posted
Confirmed. Working Flawlessly ! OMG, you are my life saver. Really appreciate your hard work.
Man, you are the BEST !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Your welcome.

You need to open a Master Class LOL. Seriously, you have no idea how frustrated when you can't get the phone to work.
bitdomo said:
Your welcome.
Click to expand...
Click to collapse

benzso63 said:
I was trying wipe everything on the phone but for some reason it saids no OS. So when it boots up, I only see the google word on the screen.
Trying to flash the stock rom, followed instruction to install adb drivers...etc then boot the phone into fastboot mode,. This is the one screen I can get so far. Looks like my pc can't detect my phone. it saids failed when running those commands...Can someone give me a hint what to do next?
All I want is to put the stock rom back in.
thx
Click to expand...
Click to collapse
if your pc cannot detect your phone , it seems you havn't install driver.

OP7 Pro Fastboot Bootloop! [HELP]

This may be a simple solution, but I am completely puzzled on how to fix this.
SO i recently rooted my phone & used the twrp "twrp-3.3.1-4-guacamole". Installed magisk via that twrp and continued with my day.
I accidentally got a virus by trying to get a full free vpn, me being a terrible pirate, i accidentally got a virus! Silly me.
It was annoying me and I decided to factory reset my phone... not via twrp. I remembered after I clicked "Reset all" on oxygenos that it's not the way how to do it with a root device, and well.. it didn't exactly work.
Every time I power/reboot the phone it just brings me to the fastboot menu of "START", "POWER OFF", "RECOVERY MODE", & "RESTART BOOT LOADER". I thought since TWP is recovery mode I try to access that... no luck, it just brings me back to that fastboot menu. I tried going on CMD via adb by saying "fastboot flash boot twrp-3.3.1-4-guacamole.img". It will say it's finished and successful, but when i reboot and try to access recovery mode it just does not work.
TL;DR: Think I bricked my phone, there is no OS installed and I can only access the fastboot.
Any help? Much appreciated

https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691

trapcoder666 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Click to expand...
Click to collapse
Thank you for the guap recovery as i didn't know it existed. However, what are the steps? when i go on the MSM download tool it doesn't detect my phone.
that being said, i can't access any of my files through my pc using fast boot. on MSM it's just saying "waiting for device" even when plugged in so thats annoying.

trapcoder666 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Click to expand...
Click to collapse
I downloaded the one you sent, and after a while as my internet is bad. It still does not work.
Whenever I try to install the qualcomm drivers it never shows up, and when i try and boot it up so the gual recover detects my phone it never works. It's still saying "waiting for device".
Does anyone know how to fix this? it's doing my head in that it's not as easy as it should be.

MOweenSalah said:
I downloaded the one you sent, and after a while as my internet is bad. It still does not work.
Whenever I try to install the qualcomm drivers it never shows up, and when i try and boot it up so the gual recover detects my phone it never works. It's still saying "waiting for device".
Does anyone know how to fix this? it's doing my head in that it's not as easy as it should be.
Click to expand...
Click to collapse
Pretty sure that your phone will not be accessible via adb/fastboot during the msm process. Did you follow the directions in the link above to a T?
A few things to note:
- Works perfectly fine for unbricking GM1917 modeled OnePlus 7 Pros.
- Use the original cable and try to plug it into a USB 2.0 port. I've found that this is the most ideal condition.
- Make sure your device is charged up. If you can't see how much charge it has, leave it charged via the 30W warp charger for 40 minutes and that should be good enough.
- In the L2 drivers folder found in the archive, navigate to the 32 or 64 folder depending on your system's architecture, and click on the file that ends in the extension ".cat". Then, click "view signature", then "View certificate", then "Install." This is IMPORTANT.
- Then, make sure your device is powered OFF, then, plug in the USB-A side of the cable (big head) into your computer and do NOT connect the USB-C (small head) into your phone yet.
- Hold down Volume up AND volume down for five seconds, and while you're continuing to hold, plug the USB-C side into your phone. The drivers should automatically download, and you should see a "Qualcomm QD loader" device in Device Manager. If you see an exclamation mark or you don't see this, you are doing it wrong and you need to repeat the above steps.
- Open up MSMTool.exe as an administrator and click 'start' only. Should take a few minutes, but you will have a good-as-new OnePlus 7 Pro.
Click to expand...
Click to collapse

Krsmqn said:
Pretty sure that your phone will not be accessible via adb/fastboot during the msm process. Did you follow the directions in the link above to a T?
Click to expand...
Click to collapse
I did yes, i pressed all buttons and the power button for 5 seconds and plugged my charger in. Then after that went on the MSM tool and it went straight to the fastboot. I really don't know but it loves this fastboot tool haha

Krsmqn said:
Pretty sure that your phone will not be accessible via adb/fastboot during the msm process. Did you follow the directions in the link above to a T?
Click to expand...
Click to collapse
Add: I made a video showing what I mean with the fastboot. Basically if i do anything with the phone fastboot it will just go back to the menu (sorry for bad quality)
https://www.youtube.com/watch?v=jU8a6kDXNNs&feature=youtu.be

MOweenSalah said:
Add: I made a video showing what I mean with the fastboot. Basically if i do anything with the phone fastboot it will just go back to the menu (sorry for bad quality)
&feature=youtu.be
Click to expand...
Click to collapse
It's one of those things where if someone was there with you, it'd likely get figured out. I've seen this kind of situation hundreds of times on XDA, and with all due respect, the problem is most always at the hands of the user. These phones are cookie cutter made, so there's nothing different (besides individual variants) that would make thee tools not function correctly, unless it's operator error. But that's not set in stone. Just don't give up. Try setting up your camera for an overhead view. I couldn't tell if you were plugging in your cord. And it seemed to reboot, instead of power off. Repeat the steps carefully, and see if you can achieve better results.
Don't give up! We're here for you ?

Make sure phone is powered off before plugging it in. Launch msm tool, Press the vol up and down key for a few seconds then plug in.
Edit : make sure your drivers are up to date too.

I don't know about msm tools never tried it but I know your situation.
Don't do fastboot flash boot twrp-3.3.1-4-guacamole.img
Remove the word flash. You are supposed to boot into twrp then flash the zip file to the phone.
look at this

Command in Fastboot mode is:
Fastboot boot "name of the recovery".img. Phone should boot to twrp. Then flash twrp.zip
or try Fastboot roms:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Choose the one for youre phone (region)
MSM tool it's the last option.

Can't you just switch slots from fastboot or did you mess up both?

trapcoder666 said:
Make sure phone is powered off before plugging it in. Launch msm tool, Press the vol up and down key for a few seconds then plug in.
Edit : make sure your drivers are up to date too.
Click to expand...
Click to collapse
Firstly I'm terribly sorry for no response (same goes to everyone else looking into this matter for me. THANK YOU!)
However, I have done this multiple times in the past and it instantly goes back to boot menu. it sucks :/

IronSingh said:
I don't know about msm tools never tried it but I know your situation.
Don't do fastboot flash boot twrp-3.3.1-4-guacamole.img
Remove the word flash. You are supposed to boot into twrp then flash the zip file to the phone.
look at this
Click to expand...
Click to collapse
Okay. I shall go and look into this situation when I receive my phone back (going to explain that in a later quote)

larsdennert said:
Can't you just switch slots from fastboot or did you mess up both?
Click to expand...
Click to collapse
If i'm honest with you.. i'm not sure in the slightest. My only assumption is no because the only thing I can access is only the fastboot. if i attempt to go into recovery mode it will go back to fastboot. when I flash twrp it will flash but it won't boot into it. It's confusing as hell.
Just to add to this whole situation:
Since I have no idea and just wanted it fixed in the day; i was willingly to give money for this phone to be fixed, but thanks to the person, he just made it a slower process by doing things i've already done.. going to pick the phone back up in an hour of this message.
I haven't used the fastboot boot twrp cmd yet, but from how everything else has been so far i feel like that won't work, but i will update everyone on that situation.
Just to add additional things that I may have not mentioned in the past will be below:
- Whenever i type in "ADB Devices" in cmd, it will not show up with anything. However, when I type in "fastboot devices" it shows it's serial and in "fastboot". It will only show as fastboot and i can't access the phone via file explorer in windows.
When i say "ADB Devices" it says *devices attached* and will show none of my phones details, but when i say fastboot devices it will then show the devices.
^ what i said above means I can't use the guap recover, or anything which means the phone has to be detected in windows, because other than fastboot, it won't work at all.
- So far I can't access twrp as a whole, so if anyone knows how to give me a guide on how to install it from where I am at, that would be amazing (if not, i'll try and reiterate what to do with the one given from a previous comment, so thank you )
- There was one time I was allowed in TWRP but i completely forgot how i entered it (so i can't explain), So i feel like there is hope in that aspect. I feel like i entered something via cmd so maybe there's a way?
In terms of hardware my phone is completely fine, there's not a single problem other than the software being a pain in the ***!!
if anyone can just spew out a bunch of help in different explanations it means the world because so far all I can see is that I wasted about £600 on an amazing phone because of dumb *** haha.
Thank you to everyone who has helped, and is helping

From your comments, you are not familiar with how Android functions. Not knowing the difference between adb and fastboot is an indicator that you should just endeavour to have a stock phone until you understand whats going one. It's also hard for people to help as no one has hands on and can see what is broken. Everyone here will be working blind like trying to fix your car for you from across the country.
Start the phone into fastboot and connect it to a pc. From a pc command prompt in your fastboot directory enter the command:
fastboot getvar current-slot
If the current slot is A then:
fastboot --set_active=b
or vice versa
fastboot --set_active=a
then fastboot reboot and see if you boot into the other slot.
Not knowing what phone you have makes it even tougher but I suspect you will have to reflash a clean complete rom via fastboot.
https://forum.xda-developers.com/on...fastboot-roms-oneplus-7-pro-t3931424#poststop

larsdennert said:
From your comments, you are not familiar with how Android functions. Not knowing the difference between adb and fastboot is an indicator that you should just endeavour to have a stock phone until you understand whats going one. It's also hard for people to help as no one has hands on and can see what is broken. Everyone here will be working blind like trying to fix your car for you from across the country.
Start the phone into fastboot and connect it to a pc. From a pc command prompt in your fastboot directory enter the command:
fastboot getvar current-slot
If the current slot is A then:
fastboot --set_active=b
or vice versa
fastboot --set_active=a
then fastboot reboot and see if you boot into the other slot.
Not knowing what phone you have makes it even tougher but I suspect you will have to reflash a clean complete rom via fastboot.
https://forum.xda-developers.com/on...fastboot-roms-oneplus-7-pro-t3931424#poststop
Click to expand...
Click to collapse
I do appreciate the help. If i'm honest with you the only reason I did this is to increase my data speeds (which from look of things is outdated now), and a longer battery life. I don't know much about rooting/jailbreaking but believe me that I have been in the scene for years, but not even knowing everything haha!
that being said.. i'm in twrp! thank you so much mate, i'll try and go and install the rom now. thank you!

Now install the zip twrp

Thankfully.. IT'S FIXED!
I didn't have to install twrp again or any of that. I simply changed the slot from A to B and pressed all buttons when it was showing the "! Your decide is unlocked" orange/black screen.
I had msm tools up and it detected and instantly installed the OS to the latest one and boom. It works again!
I got to thank everyone for helping me because without you people I wouldn't of been able to fix it. I looked everywhere and no help anywhere as I feel like it's pretty dumb to do what I did haha!
Thank you again people!

Oh you gave up on root?
You are supposed to read the instructions and follow them to the letter. When I read your post I realized you tried to install twrp like you would pre Oreo but it changed you have to boot into twrp then install it via zip file.
Anyways just remember that for next time.