Related
I used galaxy toolkit install touch screen CWM, then log into CWM install su.zip and reboot system, next time I log in CWM, i see a X mark on android robot stomach. then I tried to flash CWM again using galaxy toolkit, now i get error code on fastboot 'FASTBOOT STATUS- download 0058d000'.
what went wrong?
citrix80 said:
I used galaxy toolkit install touch screen CWM, then log into CWM install su.zip and reboot system, next time I log in CWM, i see a X mark on android robot stomach. then I tried to flash CWM again using galaxy toolkit, now i get error code on fastboot 'FASTBOOT STATUS- download 0058d000'.
what went wrong?
Click to expand...
Click to collapse
Not sure.
Here are some suggestions:
1) Lose the toolkit and flash things manually -- it is easier to see where things go wrong if you do things step-by-step yourself.
2) Don't use the touch version of CWM -- I've seen issue with it.
I'll gladly guide you though doing it manually if you cannot figure it out.
Use my sig bud.
As far as the error, I'm not sure what that means.
Doesn't seem like a fastboot error...but rather something the toolkit is displaying.
Possibly missing the .img? Try redownloading it.
Jubakuba said:
Use my sig bud.
As far as the error, I'm not sure what that means.
Doesn't seem like a fastboot error...but rather something the toolkit is displaying.
Possibly missing the .img? Try redownloading it.
Click to expand...
Click to collapse
no, it on the phone, right on bottom of bootloader screen, not in toolkit.
this is why people shouldn't use toolkits.
try to remove battery for a few mins, plug it back it, 3bc to bootloader.
is teamwork win recovery more reliable than clockwork?
i used galaxy toolket 7 to flash teamwork recovery, i can use it immediately but after reboot, it is gone, display a android robot with ! mark on the head. same with clockwork.
what is command for manually flash recovery? team win and clockwork.
citrix80 said:
is teamwork win recovery more reliable than clockwork?
i used galaxy toolket 7 to flash teamwork recovery, i can use it immediately but after reboot, it is gone, display a android robot with ! mark on the head. same with clockwork.
what is command for manually flash recovery? team win and clockwork.
Click to expand...
Click to collapse
It is disappearing because there are two files placed on your system by an OTA update. You need to delete the two files and re-flash your custom recovery. The two files are:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
efrant said:
It is disappearing because there are two files placed on your system by an OTA update. You need to delete the two files and re-flash your custom recovery. The two files are:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
Click to expand...
Click to collapse
Delete those will cause any problems? or not able to receive future OTA updates?
how to find thos files?
citrix80 said:
Delete those will cause any problems? or not able to receive future OTA updates?
how to find thos files?
Click to expand...
Click to collapse
Nope. No problems. Those files don't exist on a stock rom. Ota updates place them there.
Use a file explorer with root access, or via adb.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Nope. No problems. Those files don't exist on a stock rom. Ota updates place them there.
Use a file explorer with root access, or via adb.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
ok. it worked. Thanks.
I also found error code in fastboot is caused by PdaNet, I installed it from rooting guide. I closed the running pdanet then error code went away. don't know why.
citrix80 said:
ok. it worked. Thanks.
I also found error code in fastboot is caused by PdaNet, I installed it from rooting guide. I closed the running pdanet then error code went away. don't know why.
Click to expand...
Click to collapse
This is why I always recommend to uninstall all old drivers and use 1wayjonny's naked drivers. The are far better than anything else, and you don't have to install third-party software like pdanet just to get drivers.
Sent from my Galaxy Nexus using Tapatalk 2
Well, here's a suggestion;
Try to stay calm, and not to freak, when freaking, people temt to make things worse, by flashing unneccessary stuff, downloadig programs, etc. ...
Try to flash things manually, first bootloader, radio, boot, system then recovery.
If you still get the error code, try using Odin mode.
Worse-case scenario: You maybe need to JTAG it. But that is only in WORST-CASE!
You could also contact Google, see if they know what to do (Which they probably would, because they wrote the program/s)
efrant said:
This is why I always recommend to uninstall all old drivers and use 1wayjonny's naked drivers. The are far better than anything else, and you don't have to install third-party software like pdanet just to get drivers.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I downloaded 1wayjonny's naked drivers. how to install it?
citrix80 said:
I downloaded 1wayjonny's naked drivers. how to install it?
Click to expand...
Click to collapse
The driver has to install twice - once when your device is booted normally, and once when your device is booted in fastboot mode. But before you install, you have to remove the previous drivers, both in fastboot mode and in normal boot.
Uninstall all old drivers
1) Open Device Manager on you PC;
2) Plug your phone to your PC (when your device is booted normally);
3) Make sure that (on your phone), that you have USB Debugging enabled in Settings;
4) Uninstall anything you see in device manager related to Android, by right-clicking on whatever the item is and clicking uninstall;
5) Unplug your phone;
6) Reboot your phone in fastboot mode;
7) Plug your phone to your PC;
8) Uninstall anything you see in device manager related to Android, by right-clicking on whatever the item is and clicking uninstall;
9) Reboot your PC;
Install 1wayjonny's drivers
1) Open Device Manager on you PC;
2) Plug your phone to your PC (when your device is booted normally);
3) Make sure that (on your phone), that you have USB Debugging enabled in Settings;
4) You may see a prompt to install drivers. If you do, select manual install (or whatever the option is called) and navigate to the folder where you extracted 1wayjonny's drivers and select the file (can't remember the name off-hand);
5) Unplug your phone;
6) Reboot your phone in fastboot mode;
7) Plug your phone to your PC;
8) You may see a prompt to install drivers. If you do, select manual install (or whatever the option is called) and navigate to the folder where you extracted 1wayjonny's drivers and select the file (can't remember the name off-hand);
9) Reboot your PC.
i have tried way to many times to root this phone and have failed over and over. atleast once every 3 months i try with zero results. the phone is unlocked using the OneX v2.5 tool kit here. when i try to do perm root it says " User C not recognized as an external or internal command, operable program or batch file". ive tried putting the tool kit directly in C: and 86x. nothing works. what do i need to do to root this freaking phone. im fixing to get a bat to this phone!
Have you tried a different version, reinstall/redownload and running it as an admin?
Sent from my EndeavorU using XDA Premium 4 mobile app
Bl4ckX said:
Have you tried a different version, reinstall/redownload and running it as an admin?
Sent from my EndeavorU using XDA Premium 4 mobile app
Click to expand...
Click to collapse
no. i havent. do you have a recommendation for a different root system?
both programs ive used says "phone not connected". i dont get it. ive tried debugging and recovery. i have never had an android this hard to root. samsung galaxy s2 was very easy.
have you tried to flash a custom recovery and root package. that's how i did for mine and i was done within 10 minutes
You have a custom recovery ? Just install the SU.zip via recovery then. Tried that ?
mrbtree98 said:
have you tried to flash a custom recovery and root package. that's how i did for mine and i was done within 10 minutes
Click to expand...
Click to collapse
ive tried the all in one unlock and root kit. didnt work. could you post a link to what you used?
I never root stock rom. I'm always on a custom rom.
Just check for the superuser zip and install it in the custom recovery
Mr Hofs said:
I never root stock rom. I'm always on a custom rom.
Just check for the superuser zip and install it in the custom recovery
Click to expand...
Click to collapse
how do you use custom recovery? i tried everything on the all in tool kit(custom recovery to) and says phone not detected or what i posted up top. this is crazy. never have i seen and android phone so hard to root!!!
MPH33 said:
both programs ive used says "phone not connected". i dont get it. ive tried debugging and recovery. i have never had an android this hard to root. samsung galaxy s2 was very easy.
Click to expand...
Click to collapse
Do you get any output with "adb devices"? When you don't (and your phone has debugging enabled), it may as well be a driver problem.
(quick tip: add the antroid-tools folder to your PATH)
I personally can't find my phone on Windows anymore after the 4.2 update, so I just use an Ubuntu liveUSB for adb/fastboot purposes.
Sent from my HTC One X using Tapatalk
My opinion ? Don't use a toolkit. Straight commands from the prompt.
Download android sdk bundle, unpack it and go the the platform tools folder. Put there the recovery (recovery.img) open a command prompt there and type
Fastboot flash recovery recovery.img
Fastboot erase cache
Mr Hofs said:
My opinion ? Don't use a toolkit. Straight commands from the prompt.
Download android sdk bundle, unpack it and go the the platform tools folder. Put there the recovery (recovery.img) open a command prompt there and type
Fastboot flash recovery recovery.img
Fastboot erase cache
Click to expand...
Click to collapse
done as directed. went to cmd typed fastboot. still says internal or external not recognized. man this sux
Have you already followed the instructions on htcdev.com? You have to unlock your phone first before you can flash a recovery
Sent from my HTC One X using Tapatalk
svenvv said:
Have you already followed the instructions on htcdev.com? You have to unlock your phone first before you can flash a recovery
Sent from my HTC One X using Tapatalk
Click to expand...
Click to collapse
yes. the phone is unlocked. it's been unlocked for like 8 months. just cant seem to root it.
Are the drivers correctly installed, download the latest HTC sync. And also check if java and .net.frameworks are installed on the pc
Mr Hofs said:
Are the drivers correctly installed, download the latest HTC sync. And also check if java and .net.frameworks are installed on the pc
Click to expand...
Click to collapse
yes. sync manager is fully updated. maybe its my computer. i built it. running on windows 7 ultimate. hell, i dont know. this is weird. like i said before... my old samsung was so much easier. i just wanna root to get rid of all this bloat.
MPH33 said:
done as directed. went to cmd typed fastboot. still says internal or external not recognized. man this sux
Click to expand...
Click to collapse
That seems like you're not in the correct directory.
To get rid of that error forever just put the contents of platform-tools in your C:\windows\system32 and C:\windows\syswow64 folders
Then you can run the commands from anywhere.
Now:
Install HTC sync drivers.
Put your phone in fastboot mode.
Put a recovery image in the path that the cmd shows when you start it (eg. C/users/USER/) or "cd" to the recovery image.
Then:
fastboot flash recovery recoveryname.img
When that gives decent output we're getting somewhere.
In that case put the supersu zipfile on you phones storage and flash it from recovery.
Sent from my HTC One X using Tapatalk
Try updating or reinstalling drivers for the phone check if your cable is good and connects it to PC
[Knowledge from tegra 2 device you must have APT or NVflash driver and whne phone is off with custom key combination enters flash mode i guss is similar to this]
screw this. phone works great just wanted to root. mint condition, will sell cheap. pm me if interested.
it isn't due to the phone...it's because windows don't know for what this command is...so install again the latest java for your win7 ....you are definitely doing something wrong...you could also try to google that error which you get after typing fastboot bla bla
it works for all other ppl so should also work for you even with my non genuine win8.1 pro it's working fine
Hi there,
First I have installed CWM with the method I had to use the codes "adb reboot bootloader"... and so on and It worked perfectly.
I wanted to install the Envi ROM and on the tutorial there was said I first should install the Base ROM and then after restarting I should install the Envi ROM. After installing the Base ROM my CWM was gone. Now I can't install it anymore. I tried the following install methods:
-The one I've mentioned already <- Doesnt work because my PC says it does not know the command abd
-The install.bat method <- Does not work because my phone does not get recognized, despite I have all the drivers installed.
-The RecoverX method <- Does not work because my phone does not get recognized, despite I have all the drivers installed.
-The RecoverX app <- The says that installing CWM worked normally, but still I have no CWM
-The install.bat method directly on my phone <- SManager does not run the .bat even I ran it with the proper rights and adjustments
domiankrey said:
Hi there,
First I have installed CWM with the method I had to use the codes "adb reboot bootloader"... and so on and It worked perfectly.
.....
-The one I've mentioned already <- Doesnt work because my PC says it does not know the command abd
...
Click to expand...
Click to collapse
Did You try flashing a kernel with pre installed recovery? You can flash it using fastboot directly or flashtool.
Also, the command is adb, not "abd". Plus if windows doesn't recognize adb command, then the adb.exe is not in the folder from where You are running the command prompt from.
Mirhawk said:
Did You try flashing a kernel with pre installed recovery? You can flash it using fastboot directly or flashtool.
Also, the command is adb, not "abd". Plus if windows doesn't recognize adb command, then the adb.exe is not in the folder from where You are running the command prompt from.
Click to expand...
Click to collapse
How can I flash a Kernel with a pre Installed Recovery
Where do I get the adb.exe?
domiankrey said:
How can I flash a Kernel with a pre Installed Recovery
Where do I get the adb.exe?
Click to expand...
Click to collapse
You can install the DoomKernel, it has pre installed recovery. You can flash it via flashtool fastboot. But do note, You have to be on stock ROM.
adb.exe is usually in the flashing files.
Mirhawk said:
You can install the DoomKernel, it has pre installed recovery. You can flash it via flashtool fastboot. But do note, You have to be on stock ROM.
adb.exe is usually in the flashing files.
Click to expand...
Click to collapse
I have my phone connected in fastboot mode and the fastboot.exe and the kernel are in the same directory.
When I type: fastboot flash boot kernel.elf it only says "waiting for device"...
domiankrey said:
I have my phone connected in fastboot mode and the fastboot.exe and the kernel are in the same directory.
When I type: fastboot flash boot kernel.elf it only says "waiting for device"...
Click to expand...
Click to collapse
To connect Your phone in fastboot, You have to switch off Your phone. Then press & hold volume up and then connect the phone to Your PC.
Mirhawk said:
To connect Your phone in fastboot, You have to switch off Your phone. Then press & hold volume up and then connect the phone to Your PC.
Click to expand...
Click to collapse
I know that and I did that, but still my device cannot be detected.
I started Ubuntu (Live CD) installed adb und fastboot and tried it there... same result?
Is something wrong is my phone?
I don't think the drivers have been installed properly. Install fastboot and flash mode drivers from flashtool, it has drivers in it's folder. Else if even that doesn't work, install "Sony Update Service", and it will install required drivers.
Edit: I'm giving You instructions for Windows, are You using Ubuntu or was that just a trial?
Mirhawk said:
I don't think the drivers have been installed properly. Install fastboot and flash mode drivers from flashtool, it has drivers in it's folder. Else if even that doesn't work, install "Sony Update Service", and it will install required drivers.
Edit: I'm giving You instructions for Windows, are You using Ubuntu or was that just a trial?
Click to expand...
Click to collapse
I am using Windows. I installed from flashtool and I did not work, I am gonna try Sony Update Service now.
I tried Ubuntu because somebody said me that Ubuntu will detect all the drivers automaticly and there would be no detection problem...
Edit: After INSTALLING Update Service, I still get the same Message "Device not found" Should I run my phone through update Service too?
Why did it not work on my phone with smanager?
domiankrey said:
I am using Windows. I installed from flash tool and I did not work, I am gonna try Sony Update Service now.
I tried Ubuntu because somebody said me that Ubuntu will detect all the drivers automatically and there would be no detection problem...
Edit: After INSTALLING Update Service, I still get the same Message "Device not found" Should I run my phone through update Service too?
Why did it not work on my phone with s manager?
Click to expand...
Click to collapse
I suppose your phone is Xperia S.
If you have unlocked the boot loader , then Sony Official Softwares wont work. If your boot loader is still locked and this error is occurring then its mistake from your side.
I guess by Base ROM you meant official ROM. So if you were on official ROM, did you check for Root Privileges, Busy Box is installed etc ??
Im using Xperia Ion so the steps might be different but results all are same.
Try different methods, it will work.
Captain Droid said:
I suppose your phone is Xperia S.
If you have unlocked the boot loader , then Sony Official Softwares wont work. If your boot loader is still locked and this error is occurring then its mistake from your side.
I guess by Base ROM you meant official ROM. So if you were on official ROM, did you check for Root Privileges, Busy Box is installed etc ??
Im using Xperia Ion so the steps might be different but results all are same.
Try different methods, it will work.
Click to expand...
Click to collapse
By Base Rom I mean the following; I wanted to use the Envi Rom and for this Rom a Base Rom should be installed first.
I have unlocked Bootloader. Busybox is installed and Root Priviliges are given. Before installing the Base ROM I used the APP "Smanager" and I ran the install.sh with the app and then the CWM was there. But now that doesnt work anymore and DeliverX does also not work.
And all methods which require connection to PC won't work because those methods say my device is not detected or connected. I installed CWM on my phone and on other phones several times and never I had thode problems...
domiankrey said:
... After INSTALLING Update Service, I still get the same Message "Device not found" Should I run my phone through update Service too?...
Click to expand...
Click to collapse
Do one thing, check Your Device Manager. Disconnect Your phone, Open Device Manager, then connect Your phone again. See if the Device Manager gets refreshed. If it does, Your device is being connected to the PC. Then check for Xperia S or anything related to Sony under "Other Devices" or other similar areas. Then right click on it to install drivers.
Mirhawk said:
Do one thing, check Your Device Manager. Disconnect Your phone, Open Device Manager, then connect Your phone again. See if the Device Manager gets refreshed. If it does, Your device is being connected to the PC. Then check for Xperia S or anything related to Sony under "Other Devices" or other similar areas. Then right click on it to install drivers.
Click to expand...
Click to collapse
I just did that.
My phone is getting showed under "Tragbare Geräte" which means portable devices. When I right click on it says:
-Update drivers
-Deactivate
-Uninstall
-Looking for changed hardware
-Properties
If I click on Update drivers the message shows, that the best driver is already installed.
domiankrey said:
I just did that.
My phone is getting showed under "Tragbare Geräte" which means portable devices. When I right click on it says:
-Update drivers
-Deactivate
-Uninstall
-Looking for changed hardware
-Properties
If I click on Update drivers the message shows, that the best driver is already installed.
Click to expand...
Click to collapse
There should be a device like the highlighted one in attachment.
Mirhawk said:
There should be a device like the highlighted one in attachment.
Click to expand...
Click to collapse
This is how it looks on my PC.
Since (I was told in an other Android Forum it is like this) that on Ubuntu, Ubuntu recognizes my phone automaticly and still I installed the drivers there and it didnt not work and since neither RecoverX on my phone nor smanager on my phone dit install CWM I think the problem is my phone not the PC...
domiankrey said:
This is how it looks on my PC.
Since (I was told in an other Android Forum it is like this) that on Ubuntu, Ubuntu recognizes my phone automaticly and still I installed the drivers there and it didnt not work and since neither RecoverX on my phone nor smanager on my phone dit install CWM I think the problem is my phone not the PC...
Click to expand...
Click to collapse
Could You translate what the yellow mark text is? I think the device is recognized wrongly or wrong drivers were installed for it. Unfortunately, I don't know much about Ubuntu.
Mirhawk said:
Could You translate what the yellow mark text is? I think the device is recognized wrongly or wrong drivers were installed for it. Unfortunately, I don't know much about Ubuntu.
Click to expand...
Click to collapse
What do you mean with yellowk mark text? I see no yellow text...
If you mean the 3 devices which have a yellow sign:
- Ethernet Controller should be clear.
- Teredo Tunneling Pseudo-inferface - I do not know what that is.
- Basissystemgerät - means somehting like basic system device
With other ROMS I was able to install a CWM from my phone (with the deliverx app or a script manager app), but for this rom this doesnt work anymore.
So is there a way to install an other ROM without CWM (and when I have this ROM I would try if installing CWM directly with an app works again)?
domiankrey said:
With other ROMS I was able to install a CWM from my phone (with the deliverx app or a script manager app), but for this rom this doesnt work anymore.
So is there a way to install an other ROM without CWM (and when I have this ROM I would try if installing CWM directly with an app works again)?
Click to expand...
Click to collapse
Unfortunately Your device is not being detected as an adb device. The problem would be solved if somehow it is detected in adb or if You are able to install recovery from cell. I will try to check out more. Say, did You try the goo manager app, twrp manager or rom maanager to install recovery?
Mirhawk said:
Unfortunately Your device is not being detected as an adb device. The problem would be solved if somehow it is detected in adb or if You are able to install recovery from cell. I will try to check out more. Say, did You try the goo manager app, twrp manager or rom maanager to install recovery?
Click to expand...
Click to collapse
I will Try Goo and TWRPG Manager. Rom Manager does not work with Xperia S I already tried it.
EDIT:
1. Goo Manager does not work. I installed the Open Recovery.img and then I tried to install the ROM (eXistenZ V2 Black) but it only restarts my phone <- Does not work
2. TWRPG Manager does not even the TWRPG Recovery.
3. Previously I used this App to install CWM and it worked. Now I used the App and the App said installed CWM worked but There is no CWM on my phone (or it can't get started neither manually by pressing up nor automatically with an App which reboots me into CWM). <-Does no work.
4. On other time I used this App to run the cwm-install.ch on my phone. It worked and CWM was on my phone. Now the script does not run and therefore CWM also cannot be installed with this method. <- Does not work.
5. After all that, today I tried to install an official Rom with Sony PC Companion (and then starting from 0 with an other ROM, to try all the other stuff again) but It says I cannot install the official ROM Update. because, I do not have the official ROM installed, <- Does not work
I dont know what to do anymore.
My computers don't recognize my Asus Zenfone 2 Ze551ml. I've installed the intel drivers, the asus drivers, the google android drivers. I've restarted, tried different USB ports, tried different computers, and tried different USB wires but to no avail.
I originally wanted to unroot so that I could apply OTA updates but I couldn't get into recovery, all the phone does is restart into bootloader again. All the solutions I read require me to use ADB or get into recovery and since I can't get into recovery or get any computer to recognize the phone I seem to be stuck.
I haven't updated the OTA since 2.18.40.12 version. Can anyone help me figure out how to update my phone or get my computer to recognize it?
Thanks,
Please see the following for hardware reset/wipe cache partition procedure:
http://www.asus.com/us/support/FAQ/1011956/
Please see the following and scroll down for manual firmware update procedure:
http://www.asus.com/us/support/FAQ/1009748/
If you have any questions or concerns with Zenfone 2 please feel free to contact me direct at [email protected].
Sincerely,
ASUS_USA
Thanks for the reply Asus_USA,
Unfortunately, both the links you sent me don't work on my phone. For the first link (hardware reset/wipe cache partition) it asks me to go into fastboot mode, which I can do no problem, it then tells me to go into recovery mode. I can scroll down with my volume keys to the 'recovery mode' option but when I hit the power key to reboot the phone into recovery mode, it just reboots back into fastboot mode.
The second link (manual firmware update) asks me to download the update from the ASUS website, which I can do with no problem and then attach the phone to the computer and transfer the zip file to the root of my internal storage, I can't do this because the computer doesn't recognize my phone and therefore doesn't allow me to copy anything into it.
Let me know if you have any other ideas!
Thanks,
Kalkin19 said:
Thanks for the reply Asus_USA,
Unfortunately, both the links you sent me don't work on my phone. For the first link (hardware reset/wipe cache partition) it asks me to go into fastboot mode, which I can do no problem, it then tells me to go into recovery mode. I can scroll down with my volume keys to the 'recovery mode' option but when I hit the power key to reboot the phone into recovery mode, it just reboots back into fastboot mode.
The second link (manual firmware update) asks me to download the update from the ASUS website, which I can do with no problem and then attach the phone to the computer and transfer the zip file to the root of my internal storage, I can't do this because the computer doesn't recognize my phone and therefore doesn't allow me to copy anything into it.
Let me know if you have any other ideas!
Thanks,
Click to expand...
Click to collapse
You can download the file directly to your phone from chrome by going to the download site on your phone. Also try setting your phone to PTP mode when it is plugged in and see if anything changes in device manager.
Or take out the sd card and copy to that, once back in phone you can then copy or move...
ultramag69 said:
Or take out the sd card and copy to that, once back in phone you can then copy or move...
Click to expand...
Click to collapse
Tried it this way and then rebooted the phone. The phone recognized that there was an update file, and when I allowed it to install it rebooted into the Fastboot screen and then did nothing. I waited a half hour before touching the phone. When I rebooted the phone it didn't update and nothing had changed.
cmendonc2 said:
You can download the file directly to your phone from chrome by going to the download site on your phone. Also try setting your phone to PTP mode when it is plugged in and see if anything changes in device manager.
Click to expand...
Click to collapse
I tried downloading the file from online and the same thing happened as with the SD Card. When I restarted the phone it recognized that there was an update file and asked me if I wanted to install it. I clicked yes, it thought for about 30 seconds and then rebooted the phone into fastboot mode. Nothing happened after that and I had to choose the 'Reboot' option to start the phone back up; nothing had changed and the update did not work.
PTP mode doesn't seem to affect anything. My computer still doesn't recognize the phone.
I should also mention that the phone *does* charge when plugged into the computer.
Maybe u r having drivers issues
Try it with diff pc
Sent from my ASUS_Z008D using XDA Free mobile app
yakub234go said:
Maybe u r having drivers issues
Try it with diff pc
Sent from my ASUS_Z008D using XDA Free mobile app
Click to expand...
Click to collapse
I have. I tried it on 2 desktops and 3 different laptops, I installed the necessary drivers on all of them and tried using different USB cables. No luck.
Kalkin19 said:
I tried downloading the file from online and the same thing happened as with the SD Card. When I restarted the phone it recognized that there was an update file and asked me if I wanted to install it. I clicked yes, it thought for about 30 seconds and then rebooted the phone into fastboot mode. Nothing happened after that and I had to choose the 'Reboot' option to start the phone back up; nothing had changed and the update did not work.
PTP mode doesn't seem to affect anything. My computer still doesn't recognize the phone.
I should also mention that the phone *does* charge when plugged into the computer.
Click to expand...
Click to collapse
Your PC won't recognize it, even in fastboot mode?
If it does you can flash a new recovery in fast boot by using the adb tools. To test attach phone in fastboot mode to pc and type in "fastboot devices".
If it detects the phone you will see your serial number come up. Then reflash the pre-rooted image. it might replace the screwed up files in your recovery.
Instead of the ADB drivers only though, use the flashtools found here - http://forum.xda-developers.com/attachment.php?attachmentid=3301263&d=1431011927 Say thankyou to Shakalaka... I was having trouble using ADB, you might need to update to the latest drivers, but the flashboot tools worked with no problem...
You need to put the pre-root.img file in the folder and after connecting phone via usb hold shift, rightclick inside flashtools folder and select "open command window here" from drop down menu.
Then try the fastboot devices command.
Afterwards you can either flash the recovery again back to stock or flash the pre-rooted image and see if that fixes it.
You can find stock recovery,droidboot.img files and boot.img files here - http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
Again, BIG thanks to Shakalaka.
ultramag69 said:
Your PC won't recognize it, even in fastboot mode?
If it does you can flash a new recovery in fast boot by using the adb tools. To test attach phone in fastboot mode to pc and type in "fastboot devices".
If it detects the phone you will see your serial number come up. Then reflash the pre-rooted image. it might replace the screwed up files in your recovery.
Instead of the ADB drivers only though, use the flashtools found here - http://forum.xda-developers.com/attachment.php?attachmentid=3301263&d=1431011927 Say thankyou to Shakalaka... I was having trouble using ADB, you might need to update to the latest drivers, but the flashboot tools worked with no problem...
You need to put the pre-root.img file in the folder and after connecting phone via usb hold shift, rightclick inside flashtools folder and select "open command window here" from drop down menu.
Then try the fastboot devices command.
Afterwards you can either flash the recovery again back to stock or flash the pre-rooted image and see if that fixes it.
You can find stock recovery,droidboot.img files and boot.img files here - http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
Again, BIG thanks to Shakalaka.
Click to expand...
Click to collapse
My computers don't recognize my phone even when it's on fastboot mode so I can't follow any of the steps
Would the solution for flashing recovery detailed in this thread help you ?
http://forum.xda-developers.com/showthread.php?t=3166701
You would need to still have root.
Sent from my ASUS_Z00AD using Tapatalk
corrsea said:
Would the solution for flashing recovery detailed in this thread help you ?
http://forum.xda-developers.com/showthread.php?t=3166701
You would need to still have root.
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Thanks for directing me to that thread, it looks like, unfortunately, I have lost root access over the course of trying different solutions... Anyone know of a way to allow terminal to access root without superuser?
i have the same problem, computer sees my device in fastboot but i cant flash anything through recovery, everything is whiped i have no system on phone now i tried everything.
when i use adb drivers suggested in post above it says outdated server and still doesnt see my device in recovery mod.
i tried on 2 computers
i tried stock recovery matching my stock rom
i tried twrp
in general it says on my phone"you need sdb 1.0.32 or higher" but i use 1.3 version (15 secs install)
any suggestions?
thats the first phone ive ever bricked and i'm panicking right now...
Hi everyone.
And @Kalkin19 @ma.ruda,
Could you both try to follow my steps on other similar thread?
It's on http://forum.xda-developers.com/showthread.php?p=64093132
Let me know if your adb problem is solved or not.
Edit: Seems this thread is so old! Someone bumped it by posting the same issue. But, yeah, at least, give a reply. :silly:
Sent from my ASUS_Z00AD
krasCGQ said:
Hi everyone.
And @Kalkin19 @ma.ruda,
Could you both try to follow my steps on other similar thread?
It's on http://forum.xda-developers.com/showthread.php?p=64093132
Let me know if your adb problem is solved or not.
Edit: Seems this thread is so old! Someone bumped it by posting the same issue. But, yeah, at least, give a reply. :silly:
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
Sorry for such a delayed response, I haven't logged in and checked my messages in a while. This issue was fixed for me randomly. I kept plugging my phone into my computer and it eventually recognized it (after about 60 different tries). I quickly added adb, unlocked, rooted and have been having no issues since then. I appreciate your link! Hopefully it helps others in the future.
So I did the factory reset option in TWRP, rebooted the device before installing a new rom and now i'm stuck in a boot loop everytime I try to power on. I was running ViperM9 and was going to switch back rooted stock but now all my backups and roms are wiped from phone and SD card.
When I plug my phone into the computer it fails to install the proper drives every time. I've tried downloading the correct drives independently on the computer and it's still a no go. Then I tried connecting my microsd xc (64gb) to my computer via the SD adapter and the USB adapter it came with. Also doesn't work. The computer recognizes it as a "mass storage device" but won't let me move any files to it.
My brain is fried for the night and hoping I can find some help on here. I can still boot my phone into recovery mode so I'm hoping I can still salvage the situation. I'd like to get my phone working again without losing my root access because I don't want to have to send off to a java key angel again. Lol. I appreciate any and all insights on the matter.
paleost0ner said:
So I did the factory reset option in TWRP, rebooted the device before installing a new rom and now i'm stuck in a boot loop everytime I try to power on. I was running ViperM9 and was going to switch back rooted stock but now all my backups and roms are wiped from phone and SD card.
When I plug my phone into the computer it fails to install the proper drives every time. I've tried downloading the correct drives independently on the computer and it's still a no go. Then I tried connecting my microsd xc (64gb) to my computer via the SD adapter and the USB adapter it came with. Also doesn't work. The computer recognizes it as a "mass storage device" but won't let me move any files to it.
My brain is fried for the night and hoping I can find some help on here. I can still boot my phone into recovery mode so I'm hoping I can still salvage the situation. I'd like to get my phone working again without losing my root access because I don't want to have to send off to a java key angel again. Lol. I appreciate any and all insights on the matter.
Click to expand...
Click to collapse
Sounds like your sdcard failed. You said you can get into recovery, so try getting ahold of another sdcard with Viper ROM zip file on it and flash it.
Boot to the bootloader and flash an RUU using fastboot. An sdcard is not needed, only working adb/fastboot drivers. S-Off status will be unaffected. Root can be regained by installing superSU from recovery.
Get RUU from this thread by cmlusco and twrp from here
Reboot the phone into bootloader mode
Open a command prompt
Fastboot OEM rebootRUU (This assumes you have working drivers in windows. If you're having trouble, use the google drivers and just force windows to use it. In bootloader select the bootloader interface driver, for adb, select the adb interface driver. These are the only two drivers I use but they must be selected manually, windows will not automatically install them for the M9. You might have to do this a couple times.)
fastboot flash zip "path and name of RUU.zip" (This will take probably 10 - 20 minutes to complete but will give status updates.)
Get coffee
fastboot reboot-bootloader
Enter stock recovery
Factory reset
Reboot to bootloader
fastboot flash recovery "path and name of twrp image"
Boot to system
Download superSU
Reboot to recovery
Install superSU
Reboot to system
You should now have a stock rooted phone
l7777 said:
Boot to the bootloader and flash an RUU using fastboot. An sdcard is not needed, only working adb/fastboot drivers. S-Off status will be unaffected. Root can be regained by installing superSU from recovery.
Get RUU from this thread by cmlusco and twrp from here
Reboot the phone into bootloader mode
Open a command prompt
Fastboot OEM rebootRUU (This assumes you have working drivers in windows. If you're having trouble, use the google drivers and just force windows to use it. In bootloader select the bootloader interface driver, for adb, select the adb interface driver. These are the only two drivers I use but they must be selected manually, windows will not automatically install them for the M9. You might have to do this a couple times.)
fastboot flash zip "path and name of RUU.zip" (This will take probably 10 - 20 minutes to complete but will give status updates.)
Get coffee
fastboot reboot-bootloader
Enter stock recovery
Factory reset
Reboot to bootloader
fastboot flash recovery "path and name of twrp image"
Boot to system
Download superSU
Reboot to recovery
Install superSU
Reboot to system
You should now have a stock rooted phone
Click to expand...
Click to collapse
Is this basically the method to recover from a bootloop/ bricked phone? Gonna Sunshine my phone this evening and start flashing. I know I'll eventually brick the thing. Wanna know my recover options when the inevitable happens.
Sent from my HTC6535LVW using XDA-Developers mobile app
mikelikesbikes said:
Is this basically the method to recover from a bootloop/ bricked phone? Gonna Sunshine my phone this evening and start flashing. I know I'll eventually brick the thing. Wanna know my recover options when the inevitable happens.
Click to expand...
Click to collapse
There are many ways. This one uses a computer to send the updates. Having the proper file on the sdcard is another way and bypasses the need for working adb and fastboot drivers which seem to be a pain point for a lot of users.
l7777 said:
There are many ways. This one uses a computer to send the updates. Having the proper file on the sdcard is another way and bypasses the need for working adb and fastboot drivers which seem to be a pain point for a lot of users.
Click to expand...
Click to collapse
I do have working adb/HTC_fastboot on my computer, but having a signed RUU on my external SD card is all I need?
Sent from my HTC6535LVW using XDA-Developers mobile app
---------- Post added at 12:05 PM ---------- Previous post was at 11:48 AM ----------
mikelikesbikes said:
I do have working adb/HTC_fastboot on my computer, but having a signed RUU on my external SD card is all I need? Looking at the instructions I see the SD card must be formatted to fat32. I have no idea if mine is, but I have extras. I can format one of them to fat32, keep that file on it, and in case I ever need it I can pop it in the phone and flash it?
Sent from my HTC6535LVW using XDA-Developers mobile app
Click to expand...
Click to collapse
Sent from my HTC6535LVW using XDA-Developers mobile app
mikelikesbikes said:
I do have working adb/HTC_fastboot on my computer, but having a signed RUU on my external SD card is all I need?
Click to expand...
Click to collapse
Yes. It must have a special name and be in the root of the sdcard. I don't remember exactly what the name is for the M9 but it is posted in the RUU threads.