Related
Hey everyone. I figured id make an official thread,although a thread a few down is very similar but still quite different.
I attempted to re-lock my XOOM wifi and I got the error.
-only able to get into RSD mode 2 or Fastboot protocol
-pc will not recognize through adb or RSD 5.0
-tried various command and no luck
-Screen wont turn off unless battery dies.
- reinstalled sdk, drivers etc.
I might of missed a few details, but ive been all around the forums and have yet to see a solution for this other than send it to Motorola. Ha just curious to whether anyone could shed a little more light on this situation. Not being able to RSD or adb seems like a bad situation, even if we did have that darn sbf id still be stuck! Thanks guys!
Sent from my DROIDX using Tapatalk
Try to get the xoom back into fastboot by rebooting (vol up + power) and then immediately holding vol down + power until the fastboot screen comes up. From there try pushing system and boot .img's through fastboot. Then you should be able to reunlock from the fastboot command on your pc. There is no way that I know of to re-lock a wifi only xoom as of yet.
Yeah, my bootloader screen says that im "Starting Fastboot protocol service" but I get no response from my PC. I've never had problems with adb recognizing my xoom before this. Its like the drivers arent even compatible with the device anymore?? For craps i attempted to send some commands through adb even though it didnt recognize the device, and had no luck. ADB simply replies "waiting for device" for all of them.
try reloading your moto drivers
Make sure you aren't using a front panel port. I had thus problem for ages, XOOM is a power hog. As for the LNX failure its the result of relocking with an invalid image, don't do it.
Sent from my HTC Desire using Tapatalk
Yeah, i spent days trying to figure that one out with the front ports vs. the back ports with my droid. I could never get it to remount in RSD when flashing a .sbf.
Thanks for the heads up though. Im not sure what made me think that it would be ok. My failure to do some research always lands me in pretty much the same spot! Here.
I reloaded all the drivers ect and have been unable to get anything. My droid works great, but no xoom.
Had this exact thing happen to me today. What fixed it for me was
- boot into fastboot (Power+Vol Up then immediately hold Vol Down until you see it display the fastboot message) and push the stock boot/system images found all over this forum for your model (Wifi/3G)
Now obviously your ADB isn't seeing your device... neither was mine
- Go under Device Manager on your PC and uninstall your Motorola drivers from whatever devices are listed
- Do a fresh install of the Moto Drivers and restart your PC
- Run, 'fastboot oem lock' to allow RSD to do it's work
That's what it took for me. If that fails, unplug your Xoom from the PC and set to debug mode, then plug back in and let Windows find your drivers. Windows could take some time, and actually took me unplugging/replugging twice until it decided it found them.
RSD is a load of junk, but when it works it's like the miracle worker =P Good luck and keep your head up! These things are harder than people think to completely wreck =)
Xezuka said:
Had this exact thing happen to me today. What fixed it for me was
- boot into fastboot (Power+Vol Up then immediately hold Vol Down until you see it display the fastboot message) and push the stock boot/system images found all over this forum for your model (Wifi/3G)
Now obviously your ADB isn't seeing your device... neither was mine
- Go under Device Manager on your PC and uninstall your Motorola drivers from whatever devices are listed
- Do a fresh install of the Moto Drivers and restart your PC
- Run, 'fastboot oem lock' to allow RSD to do it's work
That's what it took for me. If that fails, unplug your Xoom from the PC and set to debug mode, then plug back in and let Windows find your drivers. Windows could take some time, and actually took me unplugging/replugging twice until it decided it found them.
RSD is a load of junk, but when it works it's like the miracle worker =P Good luck and keep your head up! These things are harder than people think to completely wreck =)
Click to expand...
Click to collapse
Just curiousity, if we can't boot our xoom, how can we enable USB debug mode?
This is the same of my problem:
http://forum.xda-developers.com/showthread.php?t=1052762
tritran18518 said:
Just curiousity, if we can't boot our xoom, how can we enable USB debug mode?
Click to expand...
Click to collapse
Sorry I guess I didn't mean to set it to Debug from the Xoom, but as in to remove it and boot into Fastboot. Then plug it back in and allow Windows to install the drivers.
I had a hard time getting it to work, but after uninstalling and reinstalling the drivers, it recognized it and allowed me to flash the SBF.
Correct me if I'm wrong here! It's what worked for me. My Xoom went down like this and I resurrected it this way. Been working flawlessly on Tiamat 1.3.1 ever since.
Sorry guys, but the condition I'm in is becoming popular lately. I'm able to get the XOOM wi/fi to show "starting fastboot protocol" but absolutley no recognition on the pc. RSD or ADB. Therefore all commands sent from the ADB simply respond with "waiting for device" and unable to flash any images onto the device. Its in a real brick mode. At least for the time being with the lack of software communication on the pc and no .sbf yet. I sent the device into motorola for repair. They said the repair would be under the warranty and free of cost. I was honest as well, telling the repp I had unlocked the device and attempted to re-lock. Thanks for all the suggestions and input guys.
follow up?
hello i am curious what happened with your returned brick? did moto replace it?
I ask because i have the exact same issue and have gone through all the suggestions.
same error, cannot get into fastboot, no adb, no RSD, nothing. tried the various vol power button combos etc. no recognition on PC at all. yes i re-installed drivers etc etc etc... i have been reading...
it seems only option is to wait on SBF or return?
Yeah the only solution would be an sbf flash. But even with that i do not know how because the RSD lite does not recognize the device either.I simply placed an order online, they sent a box the next day, sent it and got it back in two days. Extremely fast. I told the tech rep over the phone that i had unlocked the device and and then downloaded an app that starting causing for restarts and so i attempted to re-lock the device and from there it was officially a true brick. I was honest and they seem to be very understanding. Im sure they understand that the lack of support for the device is evident and we are all beta testers. SO let em know whats going on. I also let him know i was a developer, whether it mattered or not i dont know, but i was just being honest. Its all covered under warranty he said. I didnt pay a penny
OK well its good to know I am totally screwed!!! thanks for the reply...
I told the rep on the phone what I did but I don't think he had any clue what I was talking about... he asked to me to reboot with vol up, then try to boot into fastboot, but didn't once say fastboot, just said vol down, then said he would send me a shipping box.
Get it today!!
I am in this situation after trying to re-lock in order to install the 3.1 update. I tried re-installing and updating the Moto drivers, rebooting etc but I can't get my PC to recognise the device in fastboot or RSD. I am on a stock Canadian ROM (but unlocked obviously).
I have sent an email to Motorola and been honest with them. Will see what they say.
That's the thing - moto provides all the tools to relock for US ONLY! There is no official way for canadians, which makes no sense. So us canadians can unlock no problem, but cannot relock, yet US units can? Strange to me...
chaz03 said:
Yeah the only solution would be an sbf flash. But even with that i do not know how because the RSD lite does not recognize the device either.I simply placed an order online, they sent a box the next day, sent it and got it back in two days. Extremely fast. I told the tech rep over the phone that i had unlocked the device and and then downloaded an app that starting causing for restarts and so i attempted to re-lock the device and from there it was officially a true brick. I was honest and they seem to be very understanding. Im sure they understand that the lack of support for the device is evident and we are all beta testers. SO let em know whats going on. I also let him know i was a developer, whether it mattered or not i dont know, but i was just being honest. Its all covered under warranty he said. I didnt pay a penny
Click to expand...
Click to collapse
Try rsdlite 4.9 or earlier it should see it then.
I tried RSD 4.9 and no luck. I think it just doesn't work with Wi-Fi only zooms.
Sent from my Nexus S using XDA App
footboydog said:
I tried RSD 4.9 and no luck. I think it just doesn't work with Wi-Fi only zooms.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Anyone who locked the zoom back and now can't boot, try my instructions from another thread...
1) Turn the xoom on and leave it plugged into USB. 2) When it says Starting RSD Mode 2, type the following in your command prompt in windows "fastboot oem unlock"
*Make sure you are typing these commands within the directory where your fastboot and .img's are located. ( I dropped mine in C:\Android-sdk\platform-tools\*The Xoom will not respond initially and your command prompt will say "waiting for device".
3) Hold the power button and volume up to reset the xoom. The fastboot command should intercept the xoom booting and take you to the unlock prompt again. Follow the on screen instruction.
*This will wipe the device again, which I'm assuming you did when you locked it with a custom kernel (boot.img)
After it is completed, type "fastboot reboot" in windows command prompt or just reboot however you can.
crushsuitandtie said:
Anyone who locked the zoom back and now can't boot, try my instructions from another thread...
1) Turn the xoom on and leave it plugged into USB. 2) When it says Starting RSD Mode 2, type the following in your command prompt in windows "fastboot oem unlock"
*Make sure you are typing these commands within the directory where your fastboot and .img's are located. ( I dropped mine in C:\Android-sdk\platform-tools\*The Xoom will not respond initially and your command prompt will say "waiting for device".
3) Hold the power button and volume up to reset the xoom. The fastboot command should intercept the xoom booting and take you to the unlock prompt again. Follow the on screen instruction.
*This will wipe the device again, which I'm assuming you did when you locked it with a custom kernel (boot.img)
After it is completed, type "fastboot reboot" in windows command prompt or just reboot however you can.
Click to expand...
Click to collapse
I have just tried this and still no luck. Fastboot just sits there with the "waiting for device" message and the Xoom just boots with the "Starting RSD mode 2" message. I also tried your suggestion with rebooting into fastboot mode by holding the vol down button and that doesn't work either.
BTW I don't have a custom boot.img. I am on a stock ROM but I just had the bootloader unlocked.
Incidentally I have tried RSD lite 4.8, 4.9 and 5.0 now and none work.
Hey guys, how are you?
Well, I wished to root my Moto G, so I (tryed?) to unlock the bootloader. Alright, done it, but then I ran into some trouble...
After the booting up, everything started forceclosing and since then, when I try to boot it, I get a black screen after the Motorola logo.
Now, I am really really worried about my phone. I got it a month ago. I'm so afraid I really f****d up my phone right now that my hands are shaking.
I'm new to Android, so sorry if the solution is pretty obvious. And if it's not, could explain it very carefully to me? I don't know what to do.
My best wishes to you, guys.
I'm assuming you used superboot if so that would happen.
The logo sort of blured out right just press volume down and power and it would work
Or did this happen when you were just trying to unlock bootloader?
TomGlass1 said:
I'm assuming you used superboot if so that would happen.
The logo sort of blured out right just press volume down and power and it would work
Or did this happen when you were just trying to unlock bootloader?
Click to expand...
Click to collapse
Yeah, that happenned when I was trying to unlcok bootloader.
And well, my computer now doesn't even recognizes my phone.
EDIT: It appears as "Fastboot falcon S" in the Device Manager. Tried installing some drivers I found in the Internet, but it didn't work.
Explain exactly what happened please. Was the unlock successful and did you just bootup normally after or did u do anything else in fastboot mode? Why are you trying to install fastboot drivers again, as you already wouldve had them to unlock the bootloader. Did you try installing recovery or some root img from fastboot? You said its forceclosing, but it isnt starting at all now?
Some things you can do right now (if your bootloader is unlocked) is to flash a recovery (twrp,cwm) through fastboot and if you think most system files (or settings) are beyond repair, flash your firmware version though fastboot. Will point you to the guides for them, but post more info if you want help.
hemanthmahesh said:
Explain exactly what happened please. Was the unlock successful and did you just bootup normally after or did u do anything else in fastboot mode? Why are you trying to install fastboot drivers again, as you already wouldve had them to unlock the bootloader. Did you try installing recovery or some root img from fastboot? You said its forceclosing, but it isnt starting at all now?
Some things you can do right now (if your bootloader is unlocked) is to flash a recovery (twrp,cwm) through fastboot and if you think most system files (or settings) are beyond repair, flash your firmware version though fastboot. Will point you to the guides for them, but post more info if you want help.
Click to expand...
Click to collapse
Alright, just after I unlocked, when I was booting, I got a message saying that "xxxx has stopped working/failed to initialize/something like that". And then, when I rebooted, I got the usual message of the "bootlocker has been unlocked". After that, the Motorola logo started animating, but then I just got a black screen. I can't turn it off and the battery just got depleted (I'm charging right now).
When I try to connect it in my computer, the PC recognizes it as "MTP Device" or "Fastboot falcon S" when fastbooted. I can't install any drivers and the Motorola Device Manager doesn't recognizes it either.
Well, if there is some missing information, just ask me. I tried to describe my problem the best I could. Anyway, sorry for my bad English and thanks in advance for any effort trying to discover what's wrong.
Motorola Device Manager isn't helpful in this state as it doesn't handle things in fastboot. You already have all the required drivers (fastboot falcon S is the right driver afaik, falcon being motog codename) for flashing your stock firmware.
1. First, you can try the "Factory" option in bootloader (the third one, use volume down to move selector, volume up to select), though this might not really work for major issues.
2. When in fastboot mode, use "fastboot getvar all" to get the firmware details if you already didn't know about it.
3. Otherwise if yours is a standard gsm (non dualsim/non cdma), just download Blur_Version.174.44.9.falcon_umts.Retail.en.GB (UK stock for gsm, 4.4.2)
Download the mfastboot files to use rather than fastboot for flashing. You might need to modify your commands a bit for various firmwares.
http://forum.xda-developers.com/showthread.php?p=47820707 (refer this thread for flashing your stock firmware)
All the firmwares are in either of the links below (all around 400mb):
http://sbf.droid-developers.org/phone.php?device=14
(or)
http://www.filefactory.com/folder/c6cdedc45a775d27
I still don't get why many ppl are getting these errors after unlocking, very bad unlock method of moto if so ( I didnt get any such issues though).
When I use the "fastboot getvar all" command, it says "waiting for device". The phone is already connected, but the Moto G doesn't recognizes it's connected either.
I'm getting more and more afraid I really hardbricked it.
http://www.mymotocast.com/download/MDM?platform=windows
Tried installing these drivers? Your fastboot doesn't seem to be setup properly. How did you unlock without a working fastboot driver? You are trying that command in bootloader mode right?
Already installed it from the start. The message I got is always this:
"There aren't any updates for your device at the moment
Current Version: N/A"
My fastboot: Doesn't matter the operation I do, I always get this <waiting for device> and the phone is already connected into the computer. And the phone doesn't recognizes it is connected too.
And greeeeat news: my phone now doesn't charges either. I get stuck on a screen with a battery logo and 0%, when connected to the charger. Still, I still can access the fastboot mode. Well, am I lucky or not?
I'm pretty confused with this. How exactly did you unlock without a working fastboot (no waiting for device issue)? Did you change your pc drivers after unlock or trying this from a different pc? When you say "phone doesn't recognizes it is connected" you mean it says "Connect USB data cable" below "Device is UNLOCKED"? If so, maybe try another usb port cause it should normally say "Transfer Mode: USB Connected" regardless of proper drivers.
Your phone will chrarge no matter what though, no worry about that. It needs to say "Battery OK (Charging)" when connected to PC
No, as long as you have working your device isn't technically bricked in any sense. Don't worry, get that fastboot working again and anything can be fixed.
Also you didnt say whether or not you tried that "Factory" option in bootloader!
hemanthmahesh said:
I'm pretty confused with this. How exactly did you unlock without a working fastboot (no waiting for device issue)? Did you change your pc drivers after unlock or trying this from a different pc? When you say "phone doesn't recognizes it is connected" you mean it says "Connect USB data cable" below "Device is UNLOCKED"? If so, maybe try another usb port cause it should normally say "Transfer Mode: USB Connected" regardless of proper drivers.
Your phone will chrarge no matter what though, no worry about that. It needs to say "Battery OK (Charging)" when connected to PC
No, as long as you have working your device isn't technically bricked in any sense. Don't worry, get that fastboot working again and anything can be fixed.
Also you didnt say whether or not you tried that "Factory" option in bootloader!
Click to expand...
Click to collapse
OMG. I tried that "Factory" option before but it didn't work. Now I tried a second time and it worked. Thanks a lot! Really :laugh:
Anyway, now my phone is back again and rooted. Thanks for the help, guys!
Thaiane said:
Already installed it from the start. The message I got is always this:
"There aren't any updates for your device at the moment
Current Version: N/A"
My fastboot: Doesn't matter the operation I do, I always get this <waiting for device> and the phone is already connected into the computer. And the phone doesn't recognizes it is connected too.
And greeeeat news: my phone now doesn't charges either. I get stuck on a screen with a battery logo and 0%, when connected to the charger. Still, I still can access the fastboot mode. Well, am I lucky or not?
Click to expand...
Click to collapse
Guys the problem occurs due to corruption of /data folder. Even I had the same issue.
What you can do is
1. Connect your phone to PC in fastboot mode.
2. In fastboot, enter the command "adb erase userdata" and "adb erase cache" without quotes and reboot you phone. It will work for most of the devices, if it doesn't I have some other workaround too.
help
forgotter said:
Guys the problem occurs due to corruption of /data folder. Even I had the same issue.
What you can do is
1. Connect your phone to PC in fastboot mode.
2. In fastboot, enter the command "adb erase userdata" and "adb erase cache" without quotes and reboot you phone. It will work for most of the devices, if it doesn't I have some other workaround too.
Click to expand...
Click to collapse
I have the same problem. my phone stuck in blank screen after Unlock Bootloader. and then I try to do "adb erase userdata" and "adb erase cache". but my phone has no chenge, still stuck in.
I attach log when enter command adb above.
I'm sorry before. I can't spech English well
jidurrr said:
I have the same problem. my phone stuck in blank screen after Unlock Bootloader. and then I try to do "adb erase userdata" and "adb erase cache". but my phone has no chenge, still stuck in.
I attach log when enter command adb above.
I'm sorry before. I can't spech English well
Click to expand...
Click to collapse
The log you have posted contains only the help commands of adb and not the actual commands you gave.
Give a try to factory reset from fastboot mode on your phone. And do you a custom recovery installed in your phone?
forgotter said:
The log you have posted contains only the help commands of adb and not the actual commands you gave.
Give a try to factory reset from fastboot mode on your phone. And do you a custom recovery installed in your phone?
Click to expand...
Click to collapse
I've tried factory reset for several times, but no change as well.
yes, I get a CWM in my phone. and then, what have I do?
jidurrr said:
I've tried factory reset for several times, but no change as well.
yes, I get a CWM in my phone. and then, what have I do?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2704207
Go to the above forum.
Sorry for late reply was busy with studies.
I had flash stock firmware
through PC
I was attempting to flash a factory image, and now am stuck in bootloader. I've attempted to flash the image via fastboot, but the terminal command gets stuck at waiting for device. I suspect something else is going on that is keeping me from communicating properly with the phone from the terminal commands but cant figure it out. I uninstalled and reinstalled adb/fastboot on my computer. When in terminal I am unable to find my device listed with adb devices command. This I think is the issue. How to do I get that to work?
Secure Boot is enabled Lock state is unlocked.
working with a mac
Also tried my wife's mac but nothing.
geekrd1 said:
I was attempting to flash a factory image, and now am stuck in bootloader. I've attempted to flash the image via fastboot, but the terminal command gets stuck at waiting for device. I suspect something else is going on that is keeping me from communicating properly with the phone from the terminal commands but cant figure it out. I uninstalled and reinstalled adb/fastboot on my computer. When in terminal I am unable to find my device listed with adb devices command. This I think is the issue. How to do I get that to work?
Secure Boot is enabled Lock state is unlocked.
working with a mac
Also tried my wife's mac but nothing.
Click to expand...
Click to collapse
ADB works in recovery. Fastboot works in bootloader. Macs shouldn't need any drivers as far as I remember.
Enter bootloader and type:
fastboot devices
With an s on the end
fastboot devices
rootSU said:
With an s on the end
fastboot devices
Click to expand...
Click to collapse
Yep that. Thanks man I haven't had my coffee yet.
no luck.
I get an error "could not get pipe properties"
I am at a loss since I can't get the phone to even be recognized by the computer. I just tried to reboot to recovery, and it shows me the twrp splash screen but then goes right to the opening google text with the unlocked padlock screen. Same as if I just try to boot the phone. I did have twrp flashed, but wanted a fresh start so I tried flashing in bootloader and got stuck.
geekrd1 said:
no luck.
I get an error "could not get pipe properties"
I am at a loss since I can't get the phone to even be recognized by the computer. I just tried to reboot to recovery, and it shows me the twrp splash screen but then goes right to the opening google text with the unlocked padlock screen. Same as if I just try to boot the phone. I did have twrp flashed, but wanted a fresh start so I tried flashing in bootloader and got stuck.
Click to expand...
Click to collapse
I'm gonna assume your on TWRP 2.8.2.0 It's a known issue that some are having with it. Try plugging your phone into your comp before you boot to recovery and see if it stays in revovery. Also try a different usb cable and a different port on the comp to try and solve the pipe error.
theesotericone said:
I'm gonna assume your on TWRP 2.8.2.0 It's a known issue that some are having with it. Try plugging your phone into your comp before you boot to recovery and see if it stays in revovery. Also try a different usb cable and a different port on the comp to try and solve the pipe error.
Click to expand...
Click to collapse
I've done all of those attempts. booting without being plugged in, booting while being plugged in, Trying 3 different cables.... still nothing.
geekrd1 said:
I've done all of those attempts. booting without being plugged in, booting while being plugged in, Trying 3 different cables.... still nothing.
Click to expand...
Click to collapse
Well I'm not a Mac guy but I found this that may or may not help:
http://forum.xda-developers.com/showthread.php?t=1129942
theesotericone said:
Well I'm not a Mac guy but I found this that may or may not help:
http://forum.xda-developers.com/showthread.php?t=1129942
Click to expand...
Click to collapse
Thanks, I think that helped. At least I've got the phone working now
theesotericone said:
Yep that. Thanks man I haven't had my coffee yet.
Click to expand...
Click to collapse
Hope you've had a chance to have your coffee by now. I've been sucking mine down all day while trying to fix the problem :good:
So I unlocked the bootloader no problem. TWRP no problem, then something happened with the magisk flash. Phone tried to boot, as normal, then it went to recovery, then to a boot loop. I can get it to the fastboot screen, but ADB won't recognize the phone, I have chased around different USB drivers for two hours, thrown every command at it that I can think of, but nothing is working. Any suggestions? I literally picked the phone up (bought off of swappa locally), drove home and bricked it lol.
edit: The phone is recognized by my computer, just not ADB.
jerseymk2 said:
So I unlocked the bootloader no problem. TWRP no problem, then something happened with the magisk flash. Phone tried to boot, as normal, then it went to recovery, then to a boot loop. I can get it to the fastboot screen, but ADB won't recognize the phone, I have chased around different USB drivers for two hours, thrown every command at it that I can think of, but nothing is working. Any suggestions? I literally picked the phone up (bought off of swappa locally), drove home and bricked it lol.
edit: The phone is recognized by my computer, just not ADB.
Click to expand...
Click to collapse
So you put the phone in fastboot mode and ADB won't recognize the phone? That is normal, ADB works when the phone is booted normally. In fastboot mode you only use fastboot commands.
Fastboot devices
Just need to "fastboot flash boot boot.img" with the stock boot.img.
jsauder2 said:
Just need to "fastboot flash boot boot.img" with the stock boot.img.
Click to expand...
Click to collapse
Sorry I work for the railroad and was away for the last few day. I am aware of that, the issue I was facing was that the phone was not communicating with the laptop when I booted fastboot. I was able to get it this morning after about what felt like 900 attempts. I knew what needed to be done, I was having severe connectivity issues, I played the game of switching cables, switching usb ports etc... finally it had connectivity. Thank you again for your help though.
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.