Related
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
This ISN'T Resolved. I get errors when attempting to fastboot the stock image
~/Desktop/adb-fastboot/adb reboot bootloader
brings about the following error
"error: device not found"
I was already in bootloader and tried:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
I get:
error: cannot load '/Users/grnmons/Desktop/adb-fastboot/boot.img'
If anybody has any ideas please let me know, I really don't know what to do at this point.
grnmons said:
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
If anybody has any ideas please let me know, I really don't know what to do at this point. Plan B is to use a PC which I can only access later in the week. If you know someone, or have a link I would really appreciate it. Also ask me anything if it can help make this clearer.
Thanks
Click to expand...
Click to collapse
Okay your bootloader is unlocked which is good, but your MAC doesn't see your phone in bootloader mode?
grnmons said:
Plan B is to use a PC which I can only access later in the week.
Click to expand...
Click to collapse
Can you bootcamp or use a virtual machine?
grnmons said:
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
If anybody has any ideas please let me know, I really don't know what to do at this point. Plan B is to use a PC which I can only access later in the week. If you know someone, or have a link I would really appreciate it. Also ask me anything if it can help make this clearer.
Thanks
Click to expand...
Click to collapse
Wrong section..but
I would def use a PC and use Odin ! Make your life easier...it takes like 3-5 Mins..takes it to stock!
Sent from my Galaxy Nexus using xda premium
All you have to do is fastboot flash those stock images of 4.0.2 google gave us. There's not even any need for Odin. You can do this right on your Mac.
Sent from my Galaxy Nexus using Tapatalk
Please uninstall and reinstall your phones drivers. Your just soft bricked is all. Once your computer sees the device you should be good.
sent from the Almighty One himself....
borgey said:
All you have to do is fastboot flash those stock images of 4.0.2 google gave us. There's not even any need for Odin. You can do this right on your Mac.
Click to expand...
Click to collapse
I can't seem to figure out how to do that. Seems like that's what got me here in the first place, the mac version might be missing files I'm missing the steps to actually do that.
Can't find any forum/site/guide that tells me how to do that. Does anybody have this?
grnmons said:
I can't seem to figure out how to do that. Seems like that's what got me here in the first place, the mac version might be missing files I'm missing the steps to actually do that.
Can't find any forum/site/guide that tells me how to do that. Does anybody have this?
Click to expand...
Click to collapse
fastboot flash (google on how to use these)
you do them when you're in bootloader mode. you need to have a ADB/Fastboot environment set up (look at root guides and do step one of it..... verifying the part of getting the environment, ignore drivers)
stock images are here: http://code.google.com/android/nexus/images.html
zephiK said:
fastboot flash (google on how to use these)
you do them when you're in bootloader mode. you need to have a ADB/Fastboot environment set up (look at root guides and do step one of it..... verifying the part of getting the environment, ignore drivers)
stock images are here: http://code.google.com/android/nexus/images.html
Click to expand...
Click to collapse
Thanks. Can you confirm that these are the steps?
1) Download the latest stock image( i will leave finding that image to you since this post can become outdated)
2) Unzip the files, and place the images into the adb-fastboot folder you created on your desktop above.
3) Open a terminal and use the following commands:
Code:
~/Desktop/adb-fastboot/adb reboot bootloader
4) Wait for bootloader to reboot on phone.
5) Then, in terminal use the following commands:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
~/Desktop/adb-fastboot/fastboot flash system ~/Desktop/adb-fastboot/system.img
~/Desktop/adb-fastboot/fastboot flash recovery ~/Desktop/adb-fastboot/recovery.img
~/Desktop/adb-fastboot/fastboot flash userdata ~/Desktop/adb-fastboot/userdata.img
~/Desktop/adb-fastboot/fastboot erase cache
~/Desktop/adb-fastboot/fastboot oem lock
6) Reboot to System, and you should be returned to Stock and Unrooted
~/Desktop/adb-fastboot/adb reboot bootloader
brings about the following error
"error: device not found"
I was already in bootloader and tried:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
I get:
error: cannot load '/Users/grnmons/Desktop/adb-fastboot/boot.img'
anybody have any other suggestions to this? or a follow up?
It should be easy to fix. You do not seem to have the correct driver installed.
Sent from my Galaxy Nexus using xda premium
Understood, I think I definitely did a few things wrong here. But my problem requires some kind of steps to solve. I don't mean to sound lazy but I've been running around the forums for awhile and I'm in way over my head, I was hoping someone could just list a few steps, links, SOMETHING. I'm looking for solvency here.
grnmons said:
Understood, I think I definitely did a few things wrong here. But my problem requires some kind of steps to solve. I don't mean to sound lazy but I've been running around the forums for awhile and I'm in way over my head, I was hoping someone could just list a few steps, links, SOMETHING. I'm looking for solvency here.
Click to expand...
Click to collapse
reinstall the android sdk from here that will get your drivers in order so your computer can see your phone
then fastboot flash recovery
then manually flash su (attached)
ogdobber said:
reinstall the android sdk from here that will get your drivers in order so your computer can see your phone
then fastboot flash recovery
then manually flash su (attached)
Click to expand...
Click to collapse
Thanks muchly, I feel like I'm getting closer but could you elaborate on the manual flash su step? My **** is all over the place now, my desktop is littered with files, should I be in recovery for this or still fastboot? and what is the command if you have?
grnmons said:
Thanks muchly, I feel like I'm getting closer but could you elaborate on the manual flash su step? My **** is all over the place now, my desktop is littered with files, should I be in recovery for this or still fastboot? and what is the command if you have?
Click to expand...
Click to collapse
download the gnex-su.zip and put in in the root of your sd card. then in recovery select "-install zip from sdcard" then "-choose zip from sdcard" then select the gnex-su.zip. this will give you root and install the superuser app
not to get ahead (previous post), but after your computer recognizes the phone you need to flash clockwork recovery
you need to open a terminal in the platform-tools folder of the sdk (also put the recovery.img there) and then
Code:
fastboot flash recovery name-of-recovery.img
Thanks for your help ogdobber, I'm incredibly frustrated and you must be too trying to help me, but I must have done something wrong as after I flash recovery, i still cannot access it - it continues to hang out in the Google screen.
Let me go through my steps with you and you tell me what I might have done wrong. So with my bricked phone, 1. I clicked your link and updated my SDK.
There's no indication that I did anything right here, it just shows that everything is installed and that's all I think I need here.
2. Opened up terminal fastboot flash boot (in this case) bootloader-toro-primekk15.img DONE!
3. Fastboot flash recovery (in this case) recovery-clockwork-5.0.2.0-crespo.img
DONE!
Then... nothing. Recovery doesn't load for me. Just get a boot loop. Anything I might have done wrong prior or inbetween these steps? Also, besides flashing and running commands off terminal - i assume this is considered computer recognizes my phone. Could the problem be there?
Just got your last post, I'm unfamiliar with SDK but I've since put the recovery file in there, not sure how to flash recovery. I have tried flashing recovery through terminal and surprisingly it says "-bash: fastboot: command not found"
grnmons said:
Thanks for your help ogdobber, I'm incredibly frustrated and you must be too trying to help me, but I must have done something wrong as after I flash recovery, i still cannot access it - it continues to hang out in the Google screen.
Let me go through my steps with you and you tell me what I might have done wrong. So with my bricked phone, 1. I clicked your link and updated my SDK.
There's no indication that I did anything right here, it just shows that everything is installed and that's all I think I need here.
2. Opened up terminal fastboot flash boot (in this case) bootloader-toro-primekk15.img DONE!
3. Fastboot flash recovery (in this case) recovery-clockwork-5.0.2.0-crespo.img
DONE!
Then... nothing. Recovery doesn't load for me. Just get a boot loop. Anything I might have done wrong prior or inbetween these steps? Also, besides flashing and running commands off terminal - i assume this is considered computer recognizes my phone. Could the problem be there?
Click to expand...
Click to collapse
that is for the nexus s
check your pm
ogdobber said:
that is for the nexus s
check your pm
Click to expand...
Click to collapse
If you are still having problems ...like I said before ...use Odin......since the simple process of fastboot is not working properly for you.Odin makes things so Much easier
Sent from my Galaxy Nexus using xda premium
I didn't to a NANDROID backup before trying to flash a new ROM (fail I know). I had factory reset my phone before flashing the new ROM, but the ROM that was flashed hasn't installed correctly and the phone no longer powers completely on. I would like to just throw a different ROM/gapps on the SD card, but I can no longer access it on my computer since the phone will not completely boot up.
Someone suggested somewhere that I mount the USB Storage from recovery, but in the mount + storage recovery section all I see is mount /data, mount /system, and mount /cache, none of which make the GNEX storage available on my computer.
Any suggestions for fixing this problem, or for simply accessing the SD card on my computer without the phone turning completely on?
Thank you.
You can adb push a ROM while booted in a custom recovery. You should check out the stickies in this forum & the general forum.
Download the factory image from google for your phone. Extract it and get system.img from it (you have to extract it a few times). Get adb/fastboot setup by installing the correct drivers and the android sdk (there may be files posted here at xda with just the files needed for adb/fastboot). Then put system.img in the same folder as fastboot.exe (assuming you use windows).
Connect your phone while in bootloader (both volume keys + power) and from a command prompt in that directory, type:
1) fastboot flash system system.img
2) fastboot reboot
It won't wipe anything other than /system.
I'm getting < waiting for device > when executing the first command (fastboot flash system system.img)
I tried a few solutions for this error based on information I could find, such as reinstalling the drivers from Samsung, but nothing seems to have worked. Any help here? I really just need to get any form of a working ROM installed so I can boot the phone.
Paybacks1 said:
I'm getting < waiting for device > when executing the first command (fastboot flash system system.img)
I tried a few solutions for this error based on information I could find, such as reinstalling the drivers from Samsung, but nothing seems to have worked. Any help here? I really just need to get any form of a working ROM installed so I can boot the phone.
Click to expand...
Click to collapse
You need to get your phone to be recognized by your pc. It is a driver problem. Try following some of the steps in this thread.
mwalt2 said:
You need to get your phone to be recognized by your pc. It is a driver problem. Try following some of the steps in this thread.
Click to expand...
Click to collapse
Paybacks1 said:
I'm getting < waiting for device > when executing the first command (fastboot flash system system.img)
I tried a few solutions for this error based on information I could find, such as reinstalling the drivers from Samsung, but nothing seems to have worked. Any help here? I really just need to get any form of a working ROM installed so I can boot the phone.
Click to expand...
Click to collapse
I have the same problem. Going to take a look at what mwalt suggested tomorrow. Paybacks, if you find a solution, can you please post it here? Thanks.
mwalt2 said:
You need to get your phone to be recognized by your pc. It is a driver problem. Try following some of the steps in this thread.
Click to expand...
Click to collapse
I was finally able to flash the system.img from Google, but see no change. What is expected to happen once this .img has been pushed?
EDIT: Ended up flashing the entire .zip installation instead of just the system.img file and I have a stock install atm. Thank you for the help!
To Man_Utd, I ended up just re-executing the superboot r5 while in bootloader and it seemed to help recognize the phone..-shrug-.
hey guys i need some serious help here. so i accidentaly erased my sd card with my custom roms on it. im sitting at the "google" screen right now and my computer (windows 8 64) recognizes the phone in adb, if i go into CWM i cannot install drivers windows 8 will not let me no matter how i try. but this is my huge dilemma im trying to push the rom to my sdcard with adb and i keep getting either permission denied, or failed to copy..... is a directory. what command am i missing? i have done this plenty of times before and it worked. currently i have tried the directories on the device: /data/media/sdcard, /sdcard/, /sideload, /mnt/sdcard/ and all come back with a similar error. please help i cant figure out what is wrong.
Chyrio said:
hey guys i need some serious help here. so i accidentaly erased my sd card with my custom roms on it. im sitting at the "google" screen right now and my computer (windows 8 64) recognizes the phone in adb, if i go into CWM i cannot install drivers windows 8 will not let me no matter how i try. but this is my huge dilemma im trying to push the rom to my sdcard with adb and i keep getting either permission denied, or failed to copy..... is a directory. what command am i missing? i have done this plenty of times before and it worked. currently i have tried the directories on the device: /data/media/sdcard, /sdcard/, /sideload, /mnt/sdcard/ and all come back with a similar error. please help i cant figure out what is wrong.
Click to expand...
Click to collapse
Try /storage/sdcard0
But if that doesnt work, reboot to bootloader and flash stock userdata.img through fastboot; reboot to recovery right after that, push rom.
Sent from my i9250
I ran into the same problem, I erased my internal memory and i'm now stuck with the google screen
i have TWRP recovery but there is nothing on the sd card to flash from, how do i push files to the sd card from the computer?
I tried use the nexus root toolkit but i get "fastboot device not found" even though the bootloader says that it is in fastboot mode.
please help
nope that didnt work either but i found a work around. i had never played with CWM's sideload feature. FOR FUTURE GOOGLE GOERS
NOTE: you need CWM 6.0.1.5 and above i think
reboot into recovery
select install from sideload
make sure drivers are installed (i used the universal android drivers here: http://forum.xda-developers.com/showthread.php?t=1514942)
open up adb in cmd (hopefully you have adb in your com)
and type "adb sideload <filename.zip>" without quotes or the little arrows
and you should see it start copying
I would like CWM and TWRP for using this in their recovery!!!!!
Chyrio said:
nope that didnt work either but i found a work around. i had never played with CWM's sideload feature. FOR FUTURE GOOGLE GOERS
NOTE: you need CWM 6.0.1.5 and above i think
reboot into recovery
select install from sideload
make sure drivers are installed (i used the universal android drivers here: http://forum.xda-developers.com/showthread.php?t=1514942)
open up adb in cmd (hopefully you have adb in your com)
and type "adb sideload <filename.zip>" without quotes or the little arrows
and you should see it start copying
I would like CWM and TWRP for using this in their recovery!!!!!
Click to expand...
Click to collapse
I tried to use your sideload command but it didn't work. It said "ERROR: CLOSED"
i'm really anxious and worried if i can get the phone to work at all:crying:. any help will be greatly appreciated!
Download Wugfresh Galaxy Nexus Tool. You can't possibly have a bricked phone after using that tool
italbomber said:
Download Wugfresh Galaxy Nexus Tool. You can't possibly have a bricked phone after using that tool
Click to expand...
Click to collapse
Thank you. I tried doing that but it wasn't any help. however, i figured how to sideload using the TWRP setting. It took a little trial and error but finally got it to work.
i don't see how can you guys not get it to work through normal adb, other than you're using Windows, but glad you got it to work.
Glad to hear you are up and running again. Sorry i just always had great luck with his toolkit. Adb was always failsafe too.
Sent from my Galaxy Nexus using Tapatalk 2
Just a note you were probably getting an error because you didn't Mount the sdcard in recovery before trying to push to it.
Sent from my Galaxy Nexus using xda premium
I did a full wipe of the phone and SD card and was unable to see my phone in adb while in CWM recovery.
I run the push command any way and it did push to the file to the phone.
I push the file to /data/media/ no need to mount SDcard as it doesn't have a real one, in the past (while using ics) I have had to mount data to push files to /sdcard/
Hi everyone,
I have a Nexus 4 and I just managed to get it in a boot loop after trying to install Paranoid Android 4.0 beta (pa_mako-4.0-BETA-20131223.zip).
I saw an update come up in goomanager so I downloaded and tried to install it, but after rebooting and starting the update from recovery mode it failed with the following message:
Code:
...
set_metadata_recursive: some changes failed
E:Error in /sdcard/paranoidota/pa_mako-4.0-BETA-20131223.zip
(Status 7)
Error flashing zip '/sdcard/paranoidota/pa_mako-4.0-BETA-20131223.zip'
Updating partition details...
After this the phone doesn't boot, it stays with the Google logo for a while, and then automatically reboots and goes to recovery.
I'm not sure what that happened. After researching a bit I found out that I may have had to update the recovery first (I'm using TWRP 2.4.4.0).
Therefore I downloaded the last version and tried to install it, but I've found another problem. When I connect the phone to the computer with a microusb cable, the phone is not recognized at all by the computer. I tried both fastboot (booting the bootloader in the phone) and ADB Sideload from the recovery. I use Ubuntu, and the phone should be listed with the command lsusb, but it's not. It's something similar to the device not coming up in the device manager on Windows. It's not listed when running either adb devices nor fastboot devices. I thought it may be a problem of having disabled USB debugging in the phone, but I read somewhere that fastboot should work nevertheless.
I tried 3 different microusb cables, 3 USB ports, 2 kernel versions in my computer and 2 different computers.
Can anybody give me some hope? :crying: Also ideas on how I may solve the problem would be really helpful.
Thanks a lot.
sepha said:
Hi everyone,
I have a Nexus 4 and I just managed to get it in a boot loop after trying to install Paranoid Android 4.0 beta (pa_mako-4.0-BETA-20131223.zip).
I saw an update come up in goomanager so I downloaded and tried to install it, but after rebooting and starting the update from recovery mode it failed with the following message:
Code:
...
set_metadata_recursive: some changes failed
E:Error in /sdcard/paranoidota/pa_mako-4.0-BETA-20131223.zip
(Status 7)
Error flashing zip '/sdcard/paranoidota/pa_mako-4.0-BETA-20131223.zip'
Updating partition details...
After this the phone doesn't boot, it stays with the Google logo for a while, and then automatically reboots and goes to recovery.
I'm not sure what that happened. After researching a bit I found out that I may have had to update the recovery first (I'm using TWRP 2.4.4.0).
Therefore I downloaded the last version and tried to install it, but I've found another problem. When I connect the phone to the computer with a microusb cable, the phone is not recognized at all by the computer. I tried both fastboot (booting the bootloader in the phone) and ADB Sideload from the recovery. I use Ubuntu, and the phone should be listed with the command lsusb, but it's not. It's something similar to the device not coming up in the device manager on Windows. It's not listed when running either adb devices nor fastboot devices. I thought it may be a problem of having disabled USB debugging in the phone, but I read somewhere that fastboot should work nevertheless.
I tried 3 different microusb cables, 3 USB ports, 2 kernel versions in my computer and 2 different computers.
Can anybody give me some hope? :crying: Also ideas on how I may solve the problem would be really helpful.
Thanks a lot.
Click to expand...
Click to collapse
From what I gather you can get into recovery mode without issue.
Simply restore a backup or try reflashing the previous version of the ROM
Anu6is said:
From what I gather you can get into recovery mode without issue.
Simply restore a backup or try reflashing the previous version of the ROM
Click to expand...
Click to collapse
Thanks Anu6is for the reply. Yes, recovery mode works, but no backups appear in the "restore" option and I can't find any either if I manually browse the file system at /sdcard. I thought I made one when first installing PA but nothing is there.
Also, no previous versions of the ROM are currently in the file system. I never thought I would need them again so I removed them to free space.
Is there a reason why ADB and fastboot would be inaccessible through USB besides a hardware failure?
Your problem is the antiquated recovery. Update your recovery
Sent from my Nexus 5
sepha said:
Thanks Anu6is for the reply. Yes, recovery mode works, but no backups appear in the "restore" option and I can't find any either if I manually browse the file system at /sdcard. I thought I made one when first installing PA but nothing is there.
Also, no previous versions of the ROM are currently in the file system. I never thought I would need them again so I removed them to free space.
Is there a reason why ADB and fastboot would be inaccessible through USB besides a hardware failure?
Click to expand...
Click to collapse
Boot into fastboot instead of recovery and update your recovery via fastboot
Pirateghost said:
Your problem is the antiquated recovery. Update your recovery
Click to expand...
Click to collapse
Thanks Pirateghost and Anu6is for confirming that the problem is an old recovery. Updating the recovery is what I'm trying to do, but as I commented in my first post I can't use fastboot, since even when I'm in the bootloader the phone is not detected by the computer when plugged.
Any idea how to fix that?
Thanks
sepha said:
Thanks Pirateghost and Anu6is for confirming that the problem is an old recovery. Updating the recovery is what I'm trying to do, but as I commented in my first post I can't use fastboot, since even when I'm in the bootloader the phone is not detected by the computer when plugged.
Any idea how to fix that?
Thanks
Click to expand...
Click to collapse
When in fastboot mode, try the command
fastboot devices
see if you computer returns anything
Anu6is said:
When in fastboot mode, try the command
fastboot devices
see if you computer returns anything
Click to expand...
Click to collapse
As I commented in my first post, adb devices and fastboot devices don't return anything. My phone doesn't even appear in the device manager. I tried different cables, different USB ports and different computers.
sepha said:
As I commented in my first post, adb devices and fastboot devices don't return anything. My phone doesn't even appear in the device manager. I tried different cables, different USB ports and different computers.
Click to expand...
Click to collapse
Yeah, sorry...that was too much to read, just scanned it.
I don't know...That's always my fallback, not sure why it wouldn't show
Sent from my Nexus 4 using Tapatalk
So I'm guessing wiping the phone is a no-no for you. Going through basics here.
So you've made sure that the daemon service is running.. .well friend i hope you get throug
Sent from my ONE TOUCH 4033A using xda app-developers app
D_Dio said:
So I'm guessing wiping the phone is a no-no for you. Going through basics here.
Click to expand...
Click to collapse
I've tried wiping caches and doing a factory reset after doing a backup (of the system already in the boot loop condition) but it didn't change anything.
If you've already got root. Can try recovery tools app to install the new recovery
ⓐⓝⓓⓡⓞⓒⓛⓓⓔ ⓘⓢ ⓝⓞⓣ ⓐ ⓢⓘⓝ
plegdroid said:
If you've already got root. Can try recovery tools app to install the new recovery
Click to expand...
Click to collapse
the problem is that I cannot copy a new recovery to the phone's memory, since Android won't boot, and ADB and fastboot won't work, and it doesn't have a microsd slot
sepha said:
the problem is that I cannot copy a new recovery to the phone's memory, since Android won't boot, and ADB and fastboot won't work, and it doesn't have a microsd slot
Click to expand...
Click to collapse
My much bad. Hope you get it sorted
While iam here thou, have you updated your computers drivers for the n4? Incase that's the reason its not finding your phone.
ⓐⓝⓓⓡⓞⓒⓛⓓⓔ ⓘⓢ ⓝⓞⓣ ⓐ ⓢⓘⓝ
sepha said:
the problem is that I cannot copy a new recovery to the phone's memory, since Android won't boot, and ADB and fastboot won't work, and it doesn't have a microsd slot
Click to expand...
Click to collapse
Try cleaning your USB port on the phone with some alcohol
Sent from my Nexus 5
Pirateghost said:
Try cleaning your USB port on the phone with some alcohol
Click to expand...
Click to collapse
Thanks Pirateghost. I tried but it didn't work. I'm more and more convinced there's something wrong with the hardware. Maybe I dropped it one too many times. It was just a strange coincidence and really bad luck that I realized it didn't work just after the problem installing a new ROM.
Anyways, I ordered a replacement for the PCB that holds the microusb connector. Let's hope that works.
I solved the problem.
I managed to make the phone appear on the computer. There must be something broken in the microusb port in the phone because sometimes when I connect the phone nothing will appear on dmesg (I use Linux), sometimes I get USB errors and after trying a few times I managed to make it work.
I updated the recovery through fastboot and then I was able to successfully install the new ROM from recovery and now everything works alright.
Once the replacement board I ordered arrives I'll try replacing that and see if that fixes the USB connection problems.
Thanks to everybody who helped.
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.