Related
Hi Guys,
So I have successfully S-OFF'd my device using rumrunner, and I was then using the instructions in this thread http://forum.xda-developers.com/showthread.php?t=2358781 in order to flash my device to a Google Play Edition device.
It worked fine for the commands:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip RUU-HTC_One_GE-3.06.1700.10-rooted.zip
and then I got the expected error message. I then entered the same command again as instructed, but this time I got the message "waiting for device" which didn't go away.
I've tried rebooting my phone a few times, and I can no longer get any fastboot.exe commands to work, I just continuously get the "waiting for device"message. adb.exe still works correctly, so after rebooting my phone I can use adb to boot into fastboot (I know that's not the only way, I'm just saying it to demonstrate that adb appears to be fine) but after that no fastboot.exe commands work anymore.
My phone is running Software version 3.62.401.1. My Hboot I was very sure used to be 1.55 but now after that failed "fastboot flash zip RUU-HTC_One_GE-3.06.1700.10-rooted.zip" it now shows as HBOOT 1.54.
Thanks guys, any help would be immensely appreciated.
Try another computer? Also perhaps a different fast boot package?
Does the device show up in device manager when it boots in fastboot?
SaHiLzZ said:
Try another computer? Also perhaps a different fast boot package?
Does the device show up in device manager when it boots in fastboot?
Click to expand...
Click to collapse
Trying another fast boot package didn't work, but a different computer did. Now I'm all set and ready to go thanks!
Just for the record, on the first computer my phone no longer showed up when I put in fastboot devices. I guess for some strange reason there's now a problem with the drivers on the first computer? I thought perhaps reinstalling HTC Sync would help that apparently not.
Anyways, that problem is solved until I want to do this again and want to use the first computer again.
After flashing successfully viper rom after a full data wipe my phone is now stuck in the Bootloader screen. I can't get to recovery, I can't reboot, and factory resetting does nothing. Help?
cknuth said:
After flashing successfully viper rom after a full data wipe my phone is now stuck in the Bootloader screen. I can't get to recovery, I can't reboot, and factory resetting does nothing. Help?
Click to expand...
Click to collapse
What happens when u choose reboot in fastboot mode in the bootloader??
cknuth said:
After flashing successfully viper rom after a full data wipe my phone is now stuck in the Bootloader screen. I can't get to recovery, I can't reboot, and factory resetting does nothing. Help?
Click to expand...
Click to collapse
Can you reboot into recovery again and enter to fastboot mode?
Can go between fast boot and the Bootloader menu but if I hit reboot, it just comes back to Bootloader. If I pick recovery it just flashes for a second and comes back to Bootloader. I am S-off btw.
cknuth said:
If I pick recovery it just flashes for a second and comes back to Bootloader. I am S-off btw.
Click to expand...
Click to collapse
fastboot erase cache
nkk71 said:
fastboot erase cache
Click to expand...
Click to collapse
Computer wont recognize device. While I can enter fastboot mode it does not go to fastboot usb mode when I plug it in and fastboot only will "waiting for device"
cknuth said:
Computer wont recognize device. While I can enter fastboot mode it does not go to fastboot usb mode when I plug it in and fastboot only will "waiting for device"
Click to expand...
Click to collapse
OS, and hboot versions? (and if you're on Windows what does Device Manager show?)
nkk71 said:
OS, and hboot versions? (and if you're on Windows what does Device Manager show?)
Click to expand...
Click to collapse
unfortunately my HBOOT is 1.44 (I just now read that it needs to be 1.55) My OS is Win 8.1. My work computer is Vista though.
device manager shows nothing connected via USB
cknuth said:
unfortunately my HBOOT is 1.44 (I just now read that it needs to be 1.55) My OS is Win 8.1. My work computer is Vista though.
device manager shows nothing connected via USB
Click to expand...
Click to collapse
if you have a USB stick, just make an Ubuntu Live USB (no need to install, you just make it, then boot the laptop/pc from the USB), check my guide under FAQ #5 (i think) it's very easy and ubuntu doesn't have issues with hboots, drivers, etc...
nkk71 said:
if you have a USB stick, just make an Ubuntu Live USB (no need to install, you just make it, then boot the laptop/pc from the USB), check my guide under FAQ #5 (i think) it's very easy and ubuntu doesn't have issues with hboots, drivers, etc...
Click to expand...
Click to collapse
ok so the guide walks me up to the point of installing fastboot for unbuntu using a couple cmd lines but for my specific situation will I need any files saved in specific locations? I have never used Ubuntu or Linux before so youll have to bear with me.
Ok so im in Ubuntu, I think I have the guide pretty much figured out, but It still doesnt want to detect my device. I installed ADB according to the guide, but "sudo fastboot devices" comes up blank and the phone only says "fastboot" not "fastboot usb"
entering the command to flash CWM gives me the same waiting for device message. I have tried multiple USB cables as well.
cknuth said:
Ok so im in Ubuntu, I think I have the guide pretty much figured out, but It still doesnt want to detect my device. I installed ADB according to the guide, but "sudo fastboot devices" comes up blank and the phone only says "fastboot" not "fastboot usb"
entering the command to flash CWM gives me the same waiting for device message. I have tried multiple USB cables as well.
Click to expand...
Click to collapse
the phone has to say FASTBOOT USB, otherwise it's a problem with the port (phone/PC/cable).
ubuntu doesn't have driver issues, but when you connect your phone to the PC, it has to change from FASTBOOT to FASTBOOT USB.
nkk71 said:
the phone has to say FASTBOOT USB, otherwise it's a problem with the port (phone/PC/cable).
ubuntu doesn't have driver issues, but when you connect your phone to the PC, it has to change from FASTBOOT to FASTBOOT USB.
Click to expand...
Click to collapse
It doesnt change, so then its likely something with the system partition as it relates to the USB port? Because the port was working fine until the failed flash. But what it sounds like is this is a brick?
cknuth said:
It doesnt change, so then its likely something with the system partition as it relates to the USB port? Because the port was working fine until the failed flash. But what it sounds like is this is a brick?
Click to expand...
Click to collapse
doesn't sound like a brick at all, as long a hboot (ie bootloader is fine) no brick should be involved.
but i have to call it a night, hopefully someone will be along shortly, and take over... (timezones ) take it ease, DO NOT PANIC, DO NOT RUSH things!!
Cool, all your help is greatly appreciated. So I should hold off on the trip to the phone store?
Any other ideas to get communication to the phone?
Different Computer, USB Port, and USB Cable. Without saying FASTBOOT USB on the phone, can't do anything.
I'm trying too root my Asus memo pad 7 (170C), I've tried EVERY method, using KingoRoot, SuperOneClick, Frameroot, motochopper. None of them worked.
So I decided to do the rooting stuff myself, first I tried on Windows 8, the fastboot driver was not recognized, I installed the PdaNet, It recognizes the device now, the problem is when I run "fastboot oem unlock" or "fastboot oem unlock0x0b05" (ASUS VendorID), it returns : "FAILED (remote: unknown OEM command)"
I enter bootloader with "adb reboot bootloader" or by pressing Volume Up and Power.
I have also tried in Ubuntu 14.04, It doesn't even recognize the device in fastboot, and yes I run fastboot as root, still no chance "fastboot devices" returns nothing, and "fastboot oem unlock" returns "Waiting for device"
I did run "usbls" command, and it was clear that the OS has recognized the tablet, but why the fastboot does not?
Here is some information of my specs: ASUS MemoPad 7 (170C) Windows 8.1 64bit AND/OR Ubuntu 14.04
Bootloader: DroidBoot Provision Os, DroidBoot Ver: WW_MeMO_Pad-11.2.3.28-20141230 IFWI Version: 64.25
PLEASE somebody save my life as I'm stuck with it for a very long time!
arman92 said:
I'm trying too root my Asus memo pad 7 (170C), I've tried EVERY method, using KingoRoot, SuperOneClick, Frameroot, motochopper. None of them worked.
So I decided to do the rooting stuff myself, first I tried on Windows 8, the fastboot driver was not recognized, I installed the PdaNet, It recognizes the device now, the problem is when I run "fastboot oem unlock" or "fastboot oem unlock0x0b05" (ASUS VendorID), it returns : "FAILED (remote: unknown OEM command)"
I enter bootloader with "adb reboot bootloader" or by pressing Volume Up and Power.
I have also tried in Ubuntu 14.04, It doesn't even recognize the device in fastboot, and yes I run fastboot as root, still no chance "fastboot devices" returns nothing, and "fastboot oem unlock" returns "Waiting for device"
I did run "usbls" command, and it was clear that the OS has recognized the tablet, but why the fastboot does not?
Here is some information of my specs: ASUS MemoPad 7 (170C) Windows 8.1 64bit AND/OR Ubuntu 14.04
Bootloader: DroidBoot Provision Os, DroidBoot Ver: WW_MeMO_Pad-11.2.3.28-20141230 IFWI Version: 64.25
PLEASE somebody save my life as I'm stuck with it for a very long time!
Click to expand...
Click to collapse
Because these Asus tablets use Intel processors, I do not believe that fastboot works. You did not indicate that you had tried the RootZenFone tool in your post above. See this thread:
http://forum.xda-developers.com/memo-pad-7/help/me170cx-k01a-root-t2985421
I have rooted two of these tablets using this method, and it worked perfectly on both of them.
CYoung234 said:
Because these Asus tablets use Intel processors, I do not believe that fastboot works. You did not indicate that you had tried the RootZenFone tool in your post above. See this thread:
http://forum.xda-developers.com/memo-pad-7/help/me170cx-k01a-root-t2985421
I have rooted two of these tablets using this method, and it worked perfectly on both of them.
Click to expand...
Click to collapse
Yes I did try the RootZenFone tool, but it didn't work either.
Unfortunately I forgot to "Forget the wireless networks" (I just disabled the WiFi), and the RootZenFone failed rooting my device...
Is there any way to get it work again?
HELP ME!!
Anybody got an idea?
Would it be helpful if I Re-Flash the Asus official ROM to my tablet and start over? If it is, how can I do that?
PLEASE somebody help me!
arman92 said:
Anybody got an idea?
Would it be helpful if I Re-Flash the Asus official ROM to my tablet and start over? If it is, how can I do that?
PLEASE somebody help me!
Click to expand...
Click to collapse
Yes, you can go into bootloader mode and restore the factory rom, which will likely downgrade you to 4.3 again. Then you can do the OTA update and use the RootZenFone again. This time, remember to follow the instructions EXACTLY, and you should do fine.
Edit: I do not have the two I set up right now, but they both were visible to my desktop in fast boot mode. They responded to fast boot device. Beyond that, I never tried fastboot oem unlock. Did you try just typing fastboot to see the comand set? You might try that.
Done! I'm Root
CYoung234 said:
Yes, you can go into bootloader mode and restore the factory rom, which will likely downgrade you to 4.3 again. Then you can do the OTA update and use the RootZenFone again. This time, remember to follow the instructions EXACTLY, and you should do fine.
Edit: I do not have the two I set up right now, but they both were visible to my desktop in fast boot mode. They responded to fast boot device. Beyond that, I never tried fastboot oem unlock. Did you try just typing fastboot to see the comand set? You might try that.
Click to expand...
Click to collapse
I've followed the instructions in this page : http://forum.xda-developers.com/android/help/instructions-reviving-me170c-me170cx-t3017466
I successfully made it flash the Asus official ROM, but every time the freaking "Unfortunately Asus Demo has stopped" showed up.
I tried 4 different ROMs, still I got the error. I tried the RootZenFone-1.4.6r.apk everytime, no chance. The rooting process was interrupted by the "Unfortunately Asus Demo has stopped"
Then I figured out that when the tablet is connected to a power source (e.g. USB charge or PC), the error come up more frequent, so I disconnected the USB cable and tried the RootZenFone again, after a fresh ROM recovery, this time it successfully finished the rooting process. Huurrraaaay!!
So for every one else that has the same issue: just disconnect the USB cable and you are good to go!
Thanks for everyone that helped.
I am not new to flashing phones, but I cannot figure this out. I can run Mofo and Mofoverify, but I cannot run a fastboot commands like "fastboot flash logo logo.bin". All I get is waiting for device. " Adb devices" and "fastboot devices" both return an empty list in there respective modes. Now I have tried several similar but not the same fixes from many Google and XDA searches. I have tried all sort of driver solutions, USB cables, toggleing of settings in my phone and such. I have used Mofo without issue and still can, but fastboot won't let me flash the setup files for Lollipop and I want me some sweetness! I have a newer Windows 8.1 machine and the XT1254. Lastly, this is my first Q&A thread post, so please be gentle. Thank you ahead of time, because this is XDA, and it can solve anything!
DragonRyderX said:
I am not new to flashing phones, but I cannot figure this out. I can run Mofo and Mofoverify, but I cannot run a fastboot commands like "fastboot flash logo logo.bin". All I get is waiting for device. " Adb devices" and "fastboot devices" both return an empty list in there respective modes. Now I have tried several similar but not the same fixes from many Google and XDA searches. I have tried all sort of driver solutions, USB cables, toggleing of settings in my phone and such. I have used Mofo without issue and still can, but fastboot won't let me flash the setup files for Lollipop and I want me some sweetness! I have a newer Windows 8.1 machine and the XT1254. Lastly, this is my first Q&A thread post, so please be gentle. Thank you ahead of time, because this is XDA, and it can solve anything!
Click to expand...
Click to collapse
Any way you could try it on a Windows 7 machine?
Where did you get your fastboot files? If mofo detects it then your fastboot files are jacked up
Go here: http://dl.google.com/android/android-sdk_r24.3.3-windows.zip
Once you extract it, run SDK Manager, Select to install Android SDK Tools, Platform-Tools.
Once that's done, go to \android-sdk-windows\platform-tools. Hold shift, right click and Open Command Prompt. Then fastboot will work
O
Here's an easy way to install Fastboot/ADB.
Once that is installed you'll have to change your commands to fit the file path of the fastboot files.
For example:
Code:
fastboot flash logo C:\Users\OP\Desktop\logo.bin
[/COLOR]
savagebunny said:
Where did you get your fastboot files? If mofo detects it then your fastboot files are jacked up
Go here: http://dl.google.com/android/android-sdk_r24.3.3-windows.zip
Once you extract it, run SDK Manager, Select to install Android SDK Tools, Platform-Tools.
Once that's done, go to \android-sdk-windows\platform-tools. Hold shift, right click and Open Command Prompt. Then fastboot will work
O
Click to expand...
Click to collapse
DragonRyderX said:
I am not new to flashing phones, but I cannot figure this out. I can run Mofo and Mofoverify, but I cannot run a fastboot commands like "fastboot flash logo logo.bin". All I get is waiting for device. " Adb devices" and "fastboot devices" both return an empty list in there respective modes. Now I have tried several similar but not the same fixes from many Google and XDA searches. I have tried all sort of driver solutions, USB cables, toggleing of settings in my phone and such. I have used Mofo without issue and still can, but fastboot won't let me flash the setup files for Lollipop and I want me some sweetness! I have a newer Windows 8.1 machine and the XT1254. Lastly, this is my first Q&A thread post, so please be gentle. Thank you ahead of time, because this is XDA, and it can solve anything!
Click to expand...
Click to collapse
This minimal version of fastboot is a lot smaller and worked for me.
I have used minimal Adb/fastboot. I don't know if it helps, but when in Android, even after revoking USB debugging authorizations, I never get asked on my phone to re-authorize my pc. As for a Windows 7 machine, I could downgrade my laptop, but I wanted that to be a last resort.
@savage- sorry for posting this on ComputerFreaks thread, but it was his image I am trying to install and figured someone doing the same as me may have had same issue, but I'm sorry.
DragonRyderX said:
I have used minimal Adb/fastboot. I don't know if it helps, but when in Android, even after revoking USB debugging authorizations, I never get asked on my phone to re-authorize my pc. As for a Windows 7 machine, I could downgrade my laptop, but I wanted that to be a last resort.
@savage- sorry for posting this on ComputerFreaks thread, but it was his image I am trying to install and figured someone doing the same as me may have had same issue, but I'm sorry.
Click to expand...
Click to collapse
A windows 7 machine is unnecessary. I used windows 8.1 pro x64 to perform the whole upgrade process without a hitch. If mofo functions correctly, that means the fastboot drivers are installed correctly. If you start up minimal adb/fastboot, plug in your phone while it's in fastboot mode and type "fastboot devices," what do you get?
EDIT: Duh. You already said that it says returns nothing. Well in that case there has to be some sort of problem with the USB connection or the minimal adb/fastboot installation. Maybe try running the minimal adb/fastboot shortcut as administrator. I don't remember having to do that on mine, but who knows?
St33ve- see OP, nothing listed for adb or fastboot devices commands in their respective modes.
Have you tried a different USB cable?
Yonnor said:
Have you tried a different USB cable?
Click to expand...
Click to collapse
Yes, about 7 different ones. 4 that I am sure have worked before, and no physical damage to them.
You said Mofo is able to see your device though, so that's kind of throwing me through a loop. You could try a fresh install of the Minimal ADB, and double check your drivers?
That's a sign of drivers not being installed!
Try opening up device manager n see if the driver is not installed.... If u see a device with an exclamatory mark n "quark" somewhere in it... The drivers aren't installed...
When the phone is in fastboot mode, the phone is listed as quark fastboot, but no exclamation mark. I reflashed computerfreaks image (KK) without an issue, but still isn't recognized in fastboot or Adb. I really want to flash me some Lollipop! I have crack flashed with every phone I own. I'm going thru withdrawals here LOL.
i am having the exact same issues. I've reinstalled drivers, switched usb cords and have had no success.
I'm not certain what actual fixed mine because I tried so many things but I got mine to recognize my phone. I think what did it was revoking the USB debugging authorizations and deleting the adb files on my computer under username/.Android. Then reauthorizing my phone. That and I believe I may have had duplicate drivers interfering with each other. Hope this helps
Hallelujah, I have lollipop!!!
I do not know exactly what the issue was but after factory resetting windows 8.1, and manually loading each driver for adb and fastboot, it works (again). I wish there was a Thank All Button. THANKS ALL!!!
Hi all,
I'm encountering a very annoying issue with my brand new Zenfone 8.
I wanted to install the last LineageOS image, but now my phone seems stuck.
Here are what I did:
- Unlocked the bootloader: success with the ASUS APK after a few tries (error 11000 and 11006 ans eventually worked).
- Rebooted to bootloader
- Entered into recovery
- Used fastboot to flash the vendor partition.
At this point, everything looked OK. But then.... :
- Powered off the phone and restarted to bootloader.
- Tried to enter into recovery to flash the Lineage Recovery
But at this point, I had a ASUS logo stucked on the screen.
I can't do anything with adb or fastboot commands.
I tried the method explained here (https://www.asus.com/Content/Android-13-Beta/) to rollback to stock Android 12, but nothing happened too: I looked at the shell script (I'm on Linux) and I reckon that it stucks on fastboot command (the phone is in the bootloader).
Any idea about what failed? The last command used (vendor partition flash) said "OKAY".
And especially, what can I do now? Any way to reinstall the ASUS recovery?
Thanks in advance guys.
Not quite sure what your status is if you say "can't do anything with adb or fastboot commands". I've flashed Zenfones a couple of times (my household has 3 Zenfone 8's on LineageOS) and I had one that went into ramdump. I recovered from that using fastboot to manually reflash all 19 firmware partitions, in both slots. That got the phone out of ramdump, and I got to continue the upgrade to the new LineageOS. So: if you can boot to the fastboot environment, then that would be a road that might leaed you out. But if you can't even get a response to the command "fastboot devices" then I don't know of a course of action for you.
To use fastboot commands I had to run the phone into bootloader mode, then to "recovery" and eventually "fastboot" (I'm note 100% sure but it's what I remembered).
Without that, I was unable to use any fastboot commands like device or flash.
And now the issue is that I'm not able to go to recovery/fastboot again, because I have just the ASUS logo and nothing else.
It looks like that the stock recovery was dead, but I don't know why - and I don't know how to fix/reset it.
From the bootloader you should be able to flash the raw image again, it should flash everything
Adaoh said:
From the bootloader you should be able to flash the raw image again, it should flash everything
Click to expand...
Click to collapse
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.
semurel said:
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.
Click to expand...
Click to collapse
On Linux and maybe macs too you need to run fastboot commands as Root (sudo fastboot devices) for example. The raw image script should ask you for your Root password for this reason
Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).
semurel said:
Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).
Click to expand...
Click to collapse
Yes, they work from the bootloader, I always run the script from the BL too. Ironically, I had issues running fastboot commands from fastbootd for installing Omnirom, so I did it all in the bootloader and all worked fine.
I am not sure I can help you more at this point, it looks like it maybe got interrupted mid flashing and now something is wrong somewhere. Maybe if you look inside the bash script file you can find the command that it got stuck on and run that manually if you manage to get fastboot command access.
Strange - they have never worked from the bootloader. I tried that before according to the LineageOS wiki. I thought it was a mistake and use the recovery > fastboot to do that. I dont like that - I hope it's not a local version of the Zenfone or something like that.
I'm not at home tonight but yes I'll try to find commands not requiering the fastboot command.
Unfortunately all commands from the script are using fastboot. And as "fastboot devices" sees nothing, I can't do anything.
I've tried from the bootloader screen (with start, recovery, poweroff option) - from the start screen showing unlocked bootloader warning and from the ASUS logo when I try to start the recovery. I've tried the commands/scripts with Linux and Windows: same result.
So :
- I can't use any fastboot commands.
- I don't have the ASUS recovery.
Speaking of the ASUS recovery, I've found screenshots on internet and they don't have a "fastboot" submenu (I'm not sure it's a Zenfone 8). May had I a different version?
I don't like that. If I don't have others option, I guess that the warranty doesn't work because the phone is unlocked?
I eventually found a solution! I've tried with my old OnePlus cable and fastboot commands start working from the bootloader screen.
I have no idea why my other cable was faulty (it can charge the phone and executes commands from the Recovery > Fastboot menu - but not on the BL screen).
Anyway my problem is now fixed.
Thanks all for help and support.