I have been trying to flash Clockwork Mod Recovery through fastboot, but it's not working. I boot into the bootloader (Power + Vol Dwn), and then into the second bootloader menu (Vol Dwn instead of Vol Up when prompted to go into recovery). When I get the 3 icons (Android Cold Boot, Fastboot USB Protocol, Wipe), I select Fastboot, and the tab displays "Starting Fastboot USB Download Protocol" but nothing happens from here. Is there a problem with the bootloader? Is there a way to replace the bootloader or the fastboot protocol?
gaxiolafm said:
I have been trying to flash Clockwork Mod Recovery through fastboot, but it's not working. I boot into the bootloader (Power + Vol Dwn), and then into the second bootloader menu (Vol Dwn instead of Vol Up when prompted to go into recovery). When I get the 3 icons (Android Cold Boot, Fastboot USB Protocol, Wipe), I select Fastboot, and the tab displays "Starting Fastboot USB Download Protocol" but nothing happens from here. Is there a problem with the bootloader? Is there a way to replace the bootloader or the fastboot protocol?
Click to expand...
Click to collapse
It was saying the same for me too,but just go ahead and flash...it will work just fine.
Pretoriano80 said:
It was saying the same for me too,but just go ahead and flash...it will work just fine.
Click to expand...
Click to collapse
I've tried like 10 times, twice I left it plugged in for about 4 hours, and nothing flashed. When I put "fastboot -i...." in the command prompt, I get "<waiting for device>" and nothing happens, and I can't type anything else.
gaxiolafm said:
I've tried like 10 times, twice I left it plugged in for about 4 hours, and nothing flashed. When I put "fastboot -i...." in the command prompt, I get "<waiting for device>" and nothing happens, and I can't type anything else.
Click to expand...
Click to collapse
Oh,check if the drivers are installed corectly.Some users reported the same issue like yours in the CWM recovery thread and some of them managed to fix it,have a look in that thread.
Pretoriano80 said:
Oh,check if the drivers are installed corectly.Some users reported the same issue like yours in the CWM recovery thread and some of them managed to fix it,have a look in that thread.
Click to expand...
Click to collapse
I've tried everything in that thread. The command window still hangs at <waiting for device>
I downloaded drivers from 4 different places, still nothing. I just flashed the .30 update downloaded directly from Asus, and ran the Debugfs root method again, still nothing. At least now I don't have TWRP! I will just wait until there is another method for flashing CWM, since I'm not seeing any official ROMs I want to flash at the time, anyway.
Thanks for taking the time to reply.
I have also been trying to flash CWM as a custom recovery on my TF700t. I have never done this before so please bear with me. I unlocked my device, turned on usb debugging, plugged it into the computer, on the computer I have fastboot installed and I have 6.0.4.7-NonTouch.img in the fastboot folder. I held down power and volume down until I saw RCK, Android, Wipe Data, and in the top left in tiny print it says starting fastboot USB download protocol. I then opened my command prompt and typed in "cd C:/Fastboot" and it brought up fastboot but when I type "Fastboot devices" to check if I am connected it does not give my serial number but it also does not say device not found. when I check my computers devices it says that I have an unspecified device named fastboot connected with all the drivers up to date. And so I typed in "fastboot -i 0x0B05 flash recovery 6.0.4.7-NonTouch.img" and it says it is sending "Recovery" eleven thousand ish KB but it never actually finishes. Am I doing something wrong that it is not recognizing my device properly? Please Help. Thanks in advance.
Titanium318 said:
I have also been trying to flash CWM as a custom recovery on my TF700t. I have never done this before so please bear with me. I unlocked my device, turned on usb debugging, plugged it into the computer, on the computer I have fastboot installed and I have 6.0.4.7-NonTouch.img in the fastboot folder. I held down power and volume down until I saw RCK, Android, Wipe Data, and in the top left in tiny print it says starting fastboot USB download protocol. I then opened my command prompt and typed in "cd C:/Fastboot" and it brought up fastboot but when I type "Fastboot devices" to check if I am connected it does not give my serial number but it also does not say device not found. when I check my computers devices it says that I have an unspecified device named fastboot connected with all the drivers up to date. And so I typed in "fastboot -i 0x0B05 flash recovery 6.0.4.7-NonTouch.img" and it says it is sending "Recovery" eleven thousand ish KB but it never actually finishes. Am I doing something wrong that it is not recognizing my device properly? Please Help. Thanks in advance.
Click to expand...
Click to collapse
Sounds like you don't have the right drivers installed on your PC. With it connected to the PC in fastboot open your device manager - what does it say - any transformer or adb devices with yellow question marks?
sbdags said:
Sounds like you don't have the right drivers installed on your PC. With it connected to the PC in fastboot open your device manager - what does it say - any transformer or adb devices with yellow question marks?
Click to expand...
Click to collapse
I re installed fastboot and it recognized my device. I then typed"fastboot -i 0x0b05 flash recovery 6.0.4.7-NonTouch.img" it said "sending 'recovery' (11796 KB)..." then "OKAY [3.523s]" then "writing 'recovery'..." then "OKAY [2.493s]" then "finished. Total time: 6.016s" I then typed "fastboot -i 0x0b05 reboot" and it said "rebooting..." then "finished. total time: 0.548s" When it said this my tablet did not reboot it froze (instead of a green flashing square around RCK it just showed a solid green square) so eventually I just held down the power button till it restarted and booted into fastboot then selected RCK. it showed a little android with his front open and a spinning triangle and said updating then it showed the android flat on his back said error and a triangle with an exclamation point inside. Should I retry sending the recovery?
---------- Post added at 09:25 PM ---------- Previous post was at 09:12 PM ----------
Titanium318 said:
I re installed fastboot and it recognized my device. I then typed"fastboot -i 0x0b05 flash recovery 6.0.4.7-NonTouch.img" it said "sending 'recovery' (11796 KB)..." then "OKAY [3.523s]" then "writing 'recovery'..." then "OKAY [2.493s]" then "finished. Total time: 6.016s" I then typed "fastboot -i 0x0b05 reboot" and it said "rebooting..." then "finished. total time: 0.548s" When it said this my tablet did not reboot it froze (instead of a green flashing square around RCK it just showed a solid green square) so eventually I just held down the power button till it restarted and booted into fastboot then selected RCK. it showed a little android with his front open and a spinning triangle and said updating then it showed the android flat on his back said error and a triangle with an exclamation point inside. Should I retry sending the recovery?
Click to expand...
Click to collapse
I believe its the original cable but I bought my tablet used. I double checked all my connections. And I used a different port. After trying again I realized that the tablet is actually freezing when I send the recovery before I even try to reboot. Do I need to root my device or is it possible to have a custom recovery unrooted?
Titanium318 said:
I re installed fastboot and it recognized my device. I then typed"fastboot -i 0x0b05 flash recovery 6.0.4.7-NonTouch.img" it said "sending 'recovery' (11796 KB)..." then "OKAY [3.523s]" then "writing 'recovery'..." then "OKAY [2.493s]" then "finished. Total time: 6.016s" I then typed "fastboot -i 0x0b05 reboot" and it said "rebooting..." then "finished. total time: 0.548s" When it said this my tablet did not reboot it froze (instead of a green flashing square around RCK it just showed a solid green square) so eventually I just held down the power button till it restarted and booted into fastboot then selected RCK. it showed a little android with his front open and a spinning triangle and said updating then it showed the android flat on his back said error and a triangle with an exclamation point inside. Should I retry sending the recovery?
---------- Post added at 09:25 PM ---------- Previous post was at 09:12 PM ----------
I believe its the original cable but I bought my tablet used. I double checked all my connections. And I used a different port. After trying again I realized that the tablet is actually freezing when I send the recovery before I even try to reboot. Do I need to root my device or is it possible to have a custom recovery unrooted?
Click to expand...
Click to collapse
Rooting won't help here. You have unlocked it first right?
sbdags said:
Rooting won't help here. You have unlocked it first right?
Click to expand...
Click to collapse
Yes I unlocked it using the asus unlocker tool
Titanium318 said:
Yes I unlocked it using the asus unlocker tool
Click to expand...
Click to collapse
I tried a touch version and also a flashable zip both locked up my tablet the same as before. While my tablet is frozen after attempting to send the recovery I re-entered fastboot devices and it replied "????????????? fastboot" What does this mean?
Titanium318 said:
I re installed fastboot and it recognized my device. I then typed"fastboot -i 0x0b05 flash recovery 6.0.4.7-NonTouch.img" it said "sending 'recovery' (11796 KB)..."
Click to expand...
Click to collapse
11.7 MB? Where did you get this recovery?
_that said:
11.7 MB? Where did you get this recovery?
Click to expand...
Click to collapse
This is where I downloaded CWM: http://d-h.st/YLd. So I switched and tried TWRP and it sent to my device and it did not freeze this time. It showed a blue loading bar at the bottom. I rebooted and opened RCK and TWRP opened successfully. I then Told my system to backup to my removable SD card. After it finished I tapped the reboot system button that came up. I opted not to root my device by installing superSU. I then downloaded Cromi-x to my tablet from here: http://forum.xda-developers.com/showthread.php?t=2425383 choosing the deodex option. Ithen followed the rest of the instructions and everything works great Thank you so much for your help!
Titanium318 said:
This is where I downloaded CWM: http://d-h.st/YLd.
Click to expand...
Click to collapse
Did you really expect a recovery for the Nexus 5 to run on the TF700?
Flashing stuff for different devices can just not work, as in your case, or it can turn your tablet into an expensive paperweight. Consider yourself lucky.
Motorola xoom wifi So the other day I woke up to my tablet being dead, it was time for work so I plugged it in figuring the battery had ran down.
Get home that night and it wont turn on. Needless to say im still at that point. If I press and hold the power button and up vlm button I get the motorola symbol. Hitting the down vlm button gives me three options of android recovery, fastboot, and rsd
Selecting Android recovery says - Cold-booting linux. Reading ODM fuse:1
Selecting Fastboot says - Starting fastboot protocol support.
Selecting RSD says - Starting RSD protocol support 0. Onewire: Charger is not connected or battery is not being charged.... Battery charge level:99%
Not exactly sure whats happened. I havent installed any new software in a while and have been using it as normal for a long time.
Can anyone please help me? Is there any way for me to get it booted up? If I can get it booted up I can try to run a restore to factory on it.
Thanks in advance for any help. It is greatly appreciated.
Try fastboot a boot.img
How do I do this? Can you provide instruction?
Hooked the tablet up and tried to ADB into it however the device isnt recognized. Is there any way to turn on usb debugging? Or im I at this point SOL?
You should be able to fastboot without adb or usb debugging enabled while in fastboot mode. Make sure you have the drivers installed for the xoom on your pc. if not download them and install them.
Download the stock images for the wifi xoom hereand unzip it to a folder.
download fastboot.exe to the same folder you unzip the system images.
open a command prompt in windows and navigate to the folder you have all the files.
type fastboot and a list of commands display's
then type each line and wait till it is done before typing the next. When it is done reboot your phone by pressing power button vol up and down all at the same toime until you see the moto screen.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
i have the same problem , my xoom doesnt boot up!
Please help!!!
when i connect my xoom , the pc makes a sound , that makes it clear that its not bricked , but how can i fix the boot thing?
Its not booting up..Please help
I have 2 Xoom tablets, in Germany, and I took the SD Card from one of them to put it on a new phone, the Tablet kept working fine until last week that I forgot to plug it and the battery ran out. When I charged it and started it, it didn´t work again, I got the Encryption message, nothing happens when I click the Reset Tablet either, I tried putting the SD card from my other Xoom but still nothing. I enter the Recovery mode and did a Factory Reset and the tablet was OK.
Battery run out again yesterday and got the same problem once again, but now factory reset is not working, tablet stays stuck at the "M" logo after doing it, I have repeat the operation a zillion times and nothing, it stays on the M. Plus I can´t turn it off either.
The model is the MZ604 and Android Version 4.0.4
I connected the xoom to the computer after installing the drives but it won´t recognize it. I got to do the fastboot and flashed motorolas images but nothing. I can´t do the adb reboot bootloader command because ADB won´t work, because I don´t have USB Debbuging checked, but I can´t check it now because I can´t get to settings (
What can I do to recover the tablet?
Anyone, is driving me crazy, no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either
I tried RDS too and after the reboot stays the same in the M logo, nothing changes. What can I do?
No ideas? :crying:
I want to save the tablet if possible.
Hi, could you explain exactly what you've tried?
In particular what you mean by "I got to do the fastboot and flashed motorolas images but nothing." and "no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either"
By flashed Motorola's images do you mean you flashed the stock images?
And when you say you flash new images but it always stays on the original, I assume you mean the recovery stays as Xoom default?
Let me know and I'll see if I can help.
alecbond said:
Hi, could you explain exactly what you've tried?
In particular what you mean by "I got to do the fastboot and flashed motorolas images but nothing." and "no matter how many time I flash new images it always stays on the original, so I can´t flash any special recoveries either"
By flashed Motorola's images do you mean you flashed the stock images?
And when you say you flash new images but it always stays on the original, I assume you mean the recovery stays as Xoom default?
Let me know and I'll see if I can help.
Click to expand...
Click to collapse
Yes I mean stock images, and yes, it always stays on Xoom default, it never changes no matter which Recovery image I flash.
The recovery is likely reverting to default because the Xoom does this automatically each boot.
We might be able to give you a recovery that stays put but the booting issue may or may not be something worse.
Being able to fix the recovery in place is reliant on adb working from recovery itself, which I'm unsure is possible.
Whilst you seem to have reasonable knowledge of flashing and using adb/fastbbot, I'll give full instructions.
I assume you have the necessary files for fastboot so I'll skip that.
Place your chosen recovery image in your fastboot folder. (I recommend ClockworkMod Touch recovery from here)
Hold shift and right click the folder containing your recovery image and fastboot files, then select 'open command prompt here'
Your PC is now setup for the fastboot process.
Connect your Xoom to your PC.
Power on your Xoom and once you see the Motorola logo, wait about 3 seconds, and press volume down.
The screen should show the Motorola logo in the center and '--> Android Recovery' in the top left.
Press volume down twice more until the top left says fastboot then press volume up.
The screen will say 'Starting Fastboot protocol support'
Now on your PC, in command prompt run the following:
fastboot flash recovery xxxx.img
Rename xxxx.img to whatever your recovery .img file is namedOnce verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Again, when you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery, you should now see your flashed recovery.
This is where I'm unsure. Try running the following:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.oldIf you are able to run this, this will rename the files that are reverting the recovery to default and prevent it happening again. If not, we can go ahead with attempting to flash stock images anyway.
To flash stock images download Build H.6.2-24 for Retail Europe (found here.)
Extract the files to your fastboot folder.
Again, reboot your Xoom, either by holding volume up and power, or from recovery.
And again, after about 3 seconds press volume down 3 times until the top left says '--> Fastboot' then press volume up.
Now run the following from command prompt:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lockThis will wipe all data on the Xoom, and hopefully reset it to stock.
Finally, run:
fastboot rebootand you should boot into Android 3.2(?), fingers crossed.
If you require further clarification or help let me know.
alecbond said:
The recovery is likely reverting to default because the Xoom does this automatically each boot.
We might be able to give you a recovery that stays put but the booting issue may or may not be something worse.
Being able to fix the recovery in place is reliant on adb working from recovery itself, which I'm unsure is possible.
Whilst you seem to have reasonable knowledge of flashing and using adb/fastbbot, I'll give full instructions.
I assume you have the necessary files for fastboot so I'll skip that.
Place your chosen recovery image in your fastboot folder. (I recommend ClockworkMod Touch recovery from here)
Hold shift and right click the folder containing your recovery image and fastboot files, then select 'open command prompt here'
Your PC is now setup for the fastboot process.
Connect your Xoom to your PC.
Power on your Xoom and once you see the Motorola logo, wait about 3 seconds, and press volume down.
The screen should show the Motorola logo in the center and '--> Android Recovery' in the top left.
Press volume down twice more until the top left says fastboot then press volume up.
The screen will say 'Starting Fastboot protocol support'
Now on your PC, in command prompt run the following:
fastboot flash recovery xxxx.img
Rename xxxx.img to whatever your recovery .img file is namedOnce verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Again, when you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery, you should now see your flashed recovery.
This is where I'm unsure. Try running the following:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.oldIf you are able to run this, this will rename the files that are reverting the recovery to default and prevent it happening again. If not, we can go ahead with attempting to flash stock images anyway.
To flash stock images download Build H.6.2-24 for Retail Europe (found here.)
Extract the files to your fastboot folder.
Again, reboot your Xoom, either by holding volume up and power, or from recovery.
And again, after about 3 seconds press volume down 3 times until the top left says '--> Fastboot' then press volume up.
Now run the following from command prompt:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lockThis will wipe all data on the Xoom, and hopefully reset it to stock.
Finally, run:
fastboot rebootand you should boot into Android 3.2(?), fingers crossed.
If you require further clarification or help let me know.
Click to expand...
Click to collapse
Thanks for the info, sadly I have done almost all that, I can´t use adb commands because I never allowed the tablet to do USB Debbuging, since I wasn´t doing anything that needed that and never thought I would need it. I think I didn´t kept the tablet connected to the PC, so I will try again and let you know if it works.
Like I said before, I'm unsure whether it'll work as I'm not an expert.
However, you may find this helps:
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
I believe ClockworkMod Recovery enables USB debugging anyway, through modifying default.prop
I'd recommend trying the above, and/or if that fails for any reason download Motorola USB Drivers here.
Thanks again but nothing works, I tried rebooting being connected to the PC and the same thing happens, the default recovery from the Xoom stays there, fastboot shows on the command Prompt and in the tablet that everything went ok and the new image was flashed but the rebooting kills it, and I can´t use any ADB commands because of the stupid USB Debugging, if something like this can happen, Motorola should have left it open from default or at least have a fail safe in case something like this could happen. RDS also flashes an image but when it rebbots the whole thing goes to hell, it stays on the damn logo with the same images. I think I can throw the tablet to the trash :crying:
Unless its a serious hardware issue, I wouldn't trash it! It clearly has life as you're able to successfully flash and such.
I'd recommend having a look at the FAQ.
alecbond said:
Unless its a serious hardware issue, I wouldn't trash it! It clearly has life as you're able to successfully flash and such.
I'd recommend having a look at the FAQ.
Click to expand...
Click to collapse
Thanks, but I have done everything, what is the good thing of a successful flash when the tablet returns to it´s previous state as soon as it reboots?
Plus I can´t use one of the most important things, adb, because of the usb debugging, I can´t get into the tablet to activated it, and even if there are recoveries which bypass this thing, I can´t flash them into the tablet, well I can, they just aren´t there after the reboot. And all this because the tablet run out of battery :crying:
ClockworkMod recovery itself allows the use of adb regardless of USB debugging setting.
I believe the command adb remount should allow it.
If adb is denied you can try what I said earlier
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
Click to expand...
Click to collapse
alecbond said:
ClockworkMod recovery itself allows the use of adb regardless of USB debugging setting.
I believe the command adb remount should allow it.
If adb is denied you can try what I said earlier
Click to expand...
Click to collapse
The problem lies with the recovery, I only have the default recovery from the xoom, it doesn´t matter how many times I flash it and everything seems to work correctly, when I restart the tablet I get the default recovery. I don´t understand why this happens, command prompt and the tablet in fastboot mode tell me the recovery has been flashed, but to use it I have to reboot and when I do I always find the same good for nothing recovery.
recovery
Hello,
I don't really understand your problem with the recovery ?
When you flash a custom recovery with fast boot, you restart the tab and after 2 or 3 second you see the Motorola Logo you push the volume down
and volume up button to enter in the new recovery.
If you flash custom recovery but restart completely the TAB without manually enter in the custom recovery, each time you retrieve the original recovery.
pots22 said:
Hello,
I don't really understand your problem with the recovery ?
When you flash a custom recovery with fast boot, you restart the tab and after 2 or 3 second you see the Motorola Logo you push the volume down
and volume up button to enter in the new recovery.
If you flash custom recovery but restart completely the TAB without manually enter in the custom recovery, each time you retrieve the original recovery.
Click to expand...
Click to collapse
Here is what happens, I flash new recovery, I restart the xoom with power and volume up, when the logo appears, after 3 seconds, I push volume down, recovery option shows, I press volume up and the default recovery is still there, not the new one I just flashed.
Is really no one out there that can help? :crying:
There's nowhere stated that, however I believe you already have unlocked your bootloader, didn't you? Because it's REALLY weird that it can't flash the recovery, I mean, you left the battery run out, then after charging you wasn't able to boot normally again.
I'll think a little, but give a check if your bootloader is really unlocked, the device should have installed the recovery, and as you didn't restart it entirely (let it go after the dual core logo), the recovery should be there...
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
I have done the fastboot oem unlock command, should I do it everytime? I can´t use adb, because like I said, I never check the USB Debugging, which I have done in my other tablet now, don´t want the same thing to happen twice.
is it dead?
hgokuh said:
is it dead?
Click to expand...
Click to collapse
I unfortunately believe that yes, however I'm still thinking about it! So don't give up! As soon as I have another answer I shall post something
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
Hi Guys, newbie here.
After installing a custom rom on my desire s a while back I have been edging towards doing the same on my Huawei ascend mate.
I have read the excelent posts in the developer forum but was not allowed to post there.
I have tried to flash twrp from joe.stones thread but maybe using a recovery installer from within android was not too smart.
My mate is now in a boot loop.
I have tried to get access using fastboot on linux but whatever I try, it keeps "waiting for device".
I've tried using power+volume up, power+volume up and volume down, tried the same buttons with usb attached and with an UPDATE.APP(both 221 and the 907 version) in dload on the sdcard
I have googled so much my head starts to spin...
Is there anything I can try?
partial succes, there is some communication!
I missed this thread:
http://forum.xda-developers.com/showthread.php?t=2682979
When passing a command like "fastboot flash recovery recovery.img" as root in terminal I get <waiting for device>
- Then connect via usb
- I/you then have to hold volume DOWN+ power to get a responce and I did!
Still not booting up but very nice to have the phone talking again!
Now trying some other fastboot stuff, but very gently....!
Done!
SvenHee said:
I missed this thread:
http://forum.xda-developers.com/showthread.php?t=2682979
When passing a command like "fastboot flash recovery recovery.img" as root in terminal I get <waiting for device>
- Then connect via usb
- I/you then have to hold volume DOWN+ power to get a responce and I did!
Still not booting up but very nice to have the phone talking again!
Now trying some other fastboot stuff, but very gently....!
Click to expand...
Click to collapse
In above thread is mentioned that you can extract files, boot.img and recovery.img, from the original UPDATE.APP that was used on your phone, in my case 907.
After flashing as mentioned the phone booted up again without any change!
Note
I used xubuntu linux 14.04, adb and fastboot utilities can be installed from the software center. Phone drivers are either not needed or were included in the install.
I used the extractor tool mentioned in the thread above in a virtual machine to extract the files from the UPDATE.APP
Hi, I have a OnePlus 6 that was running Pie Beta 3. Yesterday it rebooted on it's own and kept going to qualcomm crash dump mode. At that time, I was able to get into FastBoot but not recovery. I then used the MSMDownload Tool which completed successfully but now it only vibrates with a black/blank screen when I try to turn it on. If I keep holding the power button down, it vibrates every 3 seconds or so. Now I can't get into recovery or fastboot. The only thing I can do is see my phone in device manager by holding down vol+ when connecting it to my laptop.
Any ideas would be appreciated.
Thanks!
Update, now it keeps taking me to fastboot mode every time I turn it on (even while only pressing the power button). I still can't get in Recovery mode.
If you're in fastboot, you already won.
Get TWRP on the start (preferably from eng.stk) > plug in to your PC > fastboot boot twrp.img
You can also find the Stock boot image and run it, see if that helps. fastboot boot <whicheverfile>.img
matteosaeed said:
You can also find the Stock boot image and run it, see if that helps. fastboot boot <whicheverfile>.img
Click to expand...
Click to collapse
I found the stock image but I'm not sure how to put it on the phone with fastboot. Is there a tutorial some where?
I knew to all this stuff.
Thanks in advance!
Patrick
preilly44 said:
I found the stock image but I'm not sure how to put it on the phone with fastboot. Is there a tutorial some where?
I knew to all this stuff.
Thanks in advance!
Patrick
Click to expand...
Click to collapse
It is easy, you do not need to put it on the phone
You'll use this in cmd
fastboot boot (filename).img
Have you used fastboot before ?
matteosaeed said:
It is easy, you do not need to put it on the phone
You'll use this in cmd
fastboot boot (filename).img
Have you used fastboot before ?
Click to expand...
Click to collapse
Unfortunately, I have not used Fastboot before. I did install it with ADB but that's it.
I just connected the phone (device manager shows it's connected) and typed fastboot devices and it doesn't show any. I also tried fastboot boot filename.img and it just sits there "waiting for device" (even though DM shows it connected).
Any help would be appreciated. OnePlus remoted in and used the MSM tool which was successful but it still wouldn't boot so they told me to RMA it which will take about 10 days. I'm hoping to avoid that.
preilly44 said:
Unfortunately, I have not used Fastboot before. I did install it with ADB but that's it.
I just connected the phone (device manager shows it's connected) and typed fastboot devices and it doesn't show any. I also tried fastboot boot filename.img and it just sits there "waiting for device" (even though DM shows it connected).
Any help would be appreciated. OnePlus remoted in and used the MSM tool which was successful but it still wouldn't boot so they told me to RMA it which will take about 10 days. I'm hoping to avoid that.
Click to expand...
Click to collapse
Send me a message. I'll see what I can do.