Related
All,
I have a big problem. When I try to start my phone I get the black screen with google and the unlocked padloack, after which the screen goes dark and nothing happens anymore.
What I did before this are two things. I had been mukking around with the screen resolution (I had it set at 240 and 280, as some apps did not show up in the market) also downloaded LCD density to solve the market issue.
I then rebooted the device and entered CWM to do a backup which as far as I knew succeeded. unfortunately after rebooting, see the above.
I have tried a couple of reboots, tried restoring the nandroid (the above was the only one I had). that didn't work, so tried to connect to the PC to load a new ICS rom (original 4.0.4 by google), unfortunately my device can not go into USB mode in CMW (it comes up with UMS lunfile missing....)
so I am woring in circles. can't start the device to download a rom, can't open USM to load a ROM to start the device again.....
any help would be appriciated
thanks
Patrick
hey
flash a new ROM via fastboot then, there are enough guides
-Syn
Edit: Alternatively, flash the stock Google ROM via GNex toolkit and go from scratch.
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
sorry, you mentioned fastboot.... not USB.
so connect it to usb cable. I then entered fastboot devices, no number came up, as was also the case with ADB. thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
pwvandeursen said:
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
Click to expand...
Click to collapse
To flash stock images the files are on your PC, not the phone.
If you can get the phone to boot into fastboot (via vol up + vol dn + power) and get your PC to recognize it you're good to go.
thats the issue. pc cannot recognize the phone, so cannot get any files from the PC to the phone (ie. cannot get a rom file to the phone...)
pwvandeursen said:
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
sorry, you mentioned fastboot.... not USB.
so connect it to usb cable. I then entered fastboot devices, no number came up, as was also the case with ADB. thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
Click to expand...
Click to collapse
Either directly from Samsung or download the GNex Toolkit (You might want to use it anyways to flash the stock image), the drivers come with it.
After you installed the drivers and have you phone plugged in, go to the device manager to check if it is connected properly.
pwvandeursen said:
[snip]
thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
Click to expand...
Click to collapse
For the drivers, I would recommend you remove all old drivers and install these. If you don't know how to install them, or are having issues, look here.
pwvandeursen said:
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
sorry, you mentioned fastboot.... not USB.
so connect it to usb cable. I then entered fastboot devices, no number came up, as was also the case with ADB. thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
Click to expand...
Click to collapse
I had a similar issue with regard to my PC recognizing the drivers. I googled around and found that people were having success with installing the PdaNet drivers, so maybe you can try that too. I had installed the Android SDK as well as the PdaNet drivers, and I eventually got mine to work.
I would probably follow Efrant's links first though - if that doesn't work for you, then maybe you can try PdaNet drivers and/or installing the SDK.
Good luck.
Why not just do a factory reset from within recovery?
¢ £®0π π€XU$ |||
the factory reset didn't help, the phone just wouldn't go past the black lockscreen. So in the end I used the galaxy nexus toolkit. installed the drivers for the PC, was able to go through fastboot and push files and flash a new rom.
Al is now solved, just need to do a lot of work to bring the phone back to where it was and make a backup asap.
thansk all for the help!
case closed.
pwvandeursen said:
the factory reset didn't help, the phone just wouldn't go past the black lockscreen. So in the end I used the galaxy nexus toolkit. installed the drivers for the PC, was able to go through fastboot and push files and flash a new rom.
Al is now solved, just need to do a lot of work to bring the phone back to where it was and make a backup asap.
thansk all for the help!
case closed.
Click to expand...
Click to collapse
Good to hear you got it.
Hello, I'm having some problems with my HTC One X.
When trying to send commands to the phone while it is in fastboot, cmd says "waiting for device" and doesn't change.
My bootloader is unlocked and CWM Recovery is installed although when I try and install one of the 4 ROM's I have on my phones internal storage the installer looks like it's working until it gets to around 20% and then says it is complete. When the device restarts it gets stuck on the "HTC quietly brilliant" screen. I am however still able to mount the phone and put files onto it through CWM. I have tried to use RUU and this just gives an error about USB not connected.
If you think you can help, thank you and if you need to know anything else I will try and give you as much information as I can.
Thanks,
Andy
Here's a checklist for you:
Phone in fastboot mode
Correct drivers installed
ADB/fasboot up to date
What does 'fastboot devices' return?
Yeah, it was all working earlier today but it just seemed to stop. fastboot devices returns
"c:\Fastboot>fastboot devices
c\:Fastboot>"
TToivanen said:
Here's a checklist for you:
Phone in fastboot mode
Correct drivers installed
ADB/fasboot up to date
What does 'fastboot devices' return?
Click to expand...
Click to collapse
What OS is your computer running? Does it say FASTBOOT USB on phone display?
I have a macbook pro as my main computer but all things to do with rooting I do on a windows desktop.
This display says fastboot usb but all fastboot commands do nothing and it still doesn't show up in fastboot devices.
TToivanen said:
What OS is your computer running? Does it say FASTBOOT USB on phone display?
Click to expand...
Click to collapse
Reboot pc and phone if you haven't already.
You could try it with your mac, there's plenty of guides out there on how to setup.
Make sure to use sudo!!
Tried it on mac like you suggested, still no devices listed. And installations still only get to around 20%.
Do you think it's bricked?
TToivanen said:
Reboot pc and phone if you haven't already.
You could try it with your mac, there's plenty of guides out there on how to setup.
Make sure to use sudo!!
Click to expand...
Click to collapse
Are you using the original delivered HTC usb cable ?
Mr Hofs said:
Are you using the original delivered HTC usb cable ?
Click to expand...
Click to collapse
No, I lost it ages ago. I have tried several cbales now though and they were all working fine yesterday.
Alwsys use the original. Try again then
Mr Hofs said:
Alwsys use the original. Try again then
Click to expand...
Click to collapse
Tried a friends original cable for the same phone, still nothing. Anything else that you think might work?
after updating my phone and rebooting it am stuck on the boot animation, the weird thing is that I cant access the recovery menu, because my volume buttons are broken and cant be repaired. :crying::crying:
I tried sitting up the sdk and try ADB. but its giving an unauthorized devices message after I type in the adb devices command I have been looking and trying to solve this problem for 4 days now and I was wondering if someone could help me here???
little info might help :
Galaxy nexus GT-I9250
I attached a pic
Thank you in advance
SVT5533 said:
after updating my phone and rebooting it am stuck on the boot animation, the weird thing is that I cant access the recovery menu, because my volume buttons are broken and cant be repaired. :crying::crying:
I tried sitting up the sdk and try ADB. but its giving an unauthorized devices message after I type in the adb devices command I have been looking and trying to solve this problem for 4 days now and I was wondering if someone could help me here???
little info might help :
Galaxy nexus GT-I9250
I attached a pic
Thank you in advance
Click to expand...
Click to collapse
install latest adb file version 1.0.31
samersh72 said:
install latest adb file version 1.0.31
Click to expand...
Click to collapse
This helped me out a ton when I couldn't recover from trying to flash back to the CM 10.2 8/18 nightly.
Can you explain with a little bit more details?
ok updated my adb, and platform tools and also installed google usb drivers, but now am getting the the device is offline after typing in adb devices
any help ?????
Hardware buttons which can't be repaired? That's a first.
Ya the guy who took a look at it said the motherboard is damaged where the buttons should be welded and needs a new mother board
Hey guys,
So, I tried to turn my T-Mobile into a GPE. Everything went OK, pushed the RUU - and it hanged for a long time, so I quit out. Tried pushing it again, ADB not detecting the phone anymore - reinstalled drivers, rebooted everything - phone detected on pc as "My HTC", still no device detected in ADB. Rebooting the phone leads to the white HTC screen, booting into bootloader works but it's black for some reason, and I'm unable to boot into recovery - The OS text is red and reads "OS-3.32.531.2 (2.12.1700.1)". I've been trying to look for a solution for the past couple of hours but all the solutions require ADB to work, and all the solutions to get ADB to work are not solving it, so at this point I'm kinda stuck.
Any and all help would be appreciated greatly.
Thanks in advance!
I don't know if there's a t-mobile ruu available but if so, you can try and run that. I would simulate the battery pull first and then see if it recognizes it. From what you described for your os, mine would show that during the process of upgrading firmware
There is a T-mobile ruu in T-mobile one m8 general
Is it possible to run an RUU when the PC doesn't recognize the device properly?
Salabrin said:
Is it possible to run an RUU when the PC doesn't recognize the device properly?
Click to expand...
Click to collapse
Nope. It uses adb/fastboot.
Try uninstalling all HTC Sync and HTC drivers. Then plug the phone, go to Device Manager, find the device and select the option to manually select a driver, then pick Generic MTP Android Device (or something like that).
Also, bootloader screen on GPE is supposed to be black.
So I ran an RUU, it gives me an image error - I changed the CID earlier to install GPE, is that what might be causing the issue? If so, is there a way to change the CID without adb(Still can't get it to detect the phone)?
Wondering if any of you guys can advise me - having strange problems with fastboot (windows 8.1 and Zenfone 2 ze550ml). Wanted to flash the pre-rooted image to my device so downloaded it and extracted to the flashtools folder and renamed system.img then hooked up my phone. Checked adb drivers were installed and adb devices command returns a code string, so assumed all was good to go with flashing. However, on entering any fastboot command it just sits at "waiting for device". Tried manually starting the phone in fastboot and then connecting it, and this did enable me to execute fastboot commands (reboot or reboot-bootloader work). However, fastboot flash system system.img just results in a message about file size and then "failed to load system.img"
kanagawaben said:
Wondering if any of you guys can advise me - having strange problems with fastboot (windows 8.1 and Zenfone 2 ze550ml). Wanted to flash the pre-rooted image to my device so downloaded it and extracted to the flashtools folder and renamed system.img then hooked up my phone. Checked adb drivers were installed and adb devices command returns a code string, so assumed all was good to go with flashing. However, on entering any fastboot command it just sits at "waiting for device". Tried manually starting the phone in fastboot and then connecting it, and this did enable me to execute fastboot commands (reboot or reboot-bootloader work). However, fastboot flash system system.img just results in a message about file size and then "failed to load system.img"
Click to expand...
Click to collapse
You need to rename the system image to system.img and put it where the fastboot file is. It's looking for it but can't find it.
No, don't think that is my problem - as I said I extracted it to the flashtools folder, so it is already where the fastboot file is. And anyway, though I'd like to solve the problem of flashing the system.img, I am kind of more interested in why I can't get past "waiting for device" without first manually entering the fastboot mode.
Cause Windows sucks. I'm on Linux and no issues. Maybe someone on Windows can chip in?
I can easily do a quick ubuntu install and try it that way if you think it might work better. At the weekend maybe. Could you give me some pointers on how to do it in linux if I do? Would be much appreciated!
kanagawaben said:
No, don't think that is my problem - as I said I extracted it to the flashtools folder, so it is already where the fastboot file is. And anyway, though I'd like to solve the problem of flashing the system.img, I am kind of more interested in why I can't get past "waiting for device" without first manually entering the fastboot mode.
Click to expand...
Click to collapse
I have encountered that problem with the "waiting for device" while I was flashing pre root rom.
Try the cmd adb devices
Then it will list the device connected to the computer...if it says not authorized, then you need to check the phone which is turned on and a pop up window with the RSA key and tap on trust this computer or something..
Then repeat adb devices and it should say allow or something..then it will allow you to flash.
(double check the commands online, I might missed something)
Nah, don't blame Windows... I flashed mine with Windows 10 and worked wonders.
Also... could it be that PC isn't USB 3.0? Perhaps system.img transfer is stopped somewhere during the copying phase?
Thanks, but actually the first time I tried it I did the adb devices command and authorised my pc on the phone. When I connect and do adb devices now it shows the string of numbers code for the device. However, still can't get past "waiting for device"
My pc has both usb 3 and usb 2 ports. Tried on all of them and with various different cables including the asus issued ones, all to no avail.
Can u post a pic of your flashtool folder?
Sent from my Nexus 7
Here is a snap of my platform-tools folder and cmd window
Did you manage to find a solution to this?
I updated the zenfone 2 via OTA to the latest system update.
Ive read and downloaded all relevant files to install the pre root img from the correct sources.
Now when I hold power + vol up. I can see the droid on its back. I choose the RECOVERY option and press power button to select.
When phone reboots it goes to droid icon and says installing system upgrade.................then error appears! No recovery mode!
All the correct drivers are installed into Windows 7, the phone asks me to allow RSA key connection to laptop.
Ive tried the flash tool installer 1.0.7 with phone connected and system img (renamed) and still nothing.
Anyone got any ideas?
Ive factory reset twice in a row and allowed debugging.
Ive placed the (renamed) system.img into the fastboot folder and tried the open command with line ' fastboot flash system system.img' and the reply is usually unable to read system.img or device waiting.
Ive installed the latest android sdk develppment kit and still unable to root using this pre root image.
Im familiar with android and how to follow instructions on rooting, but this zenfone 2 is mind boggling.
Thanks for reading. I know its someone else post. I didnt want to start a fresh post with the same dilemma.
Any advice on whats going wrong would be appreciated.
tsam19 said:
When phone reboots it goes to droid icon and says installing system upgrade.................then error appears! No recovery mode!
Click to expand...
Click to collapse
Hit power and vol up again, just really quickly. Don't hold it, just press and let go. Sometimes it takes several attempts.
hkdmjack, yes your right managed to do it at last.
Cheers
Hi guys, I am facing quite a difficult problem at the moment.
My friend has "accidentally" attempted to use an Asus Zenfone 5 rooting method to root his zenfone 2 550ML.
When I received it to take a look at it, I instantly noticed that I could not get into fast boot (or droidboot). I expected to see usual droid with text on the left side and also expected to be able to select from a number of options using the volume keys (i have some past experience), but instead am met with this solid usb logo. One like this: h ttp://zenfo ne-blog-forum.2 8820.n7.nabble.c om/file/n4 5/P_20140728_051139 .jpg (remove spaces)
I did some research, and found that there were many "bricked" zenfone 5's which were stuck on this usb logo, however this zenfone 2 can start up normally and be used throughout the day normally. Only when I try to enter fast boot, by either ADB commands or by power + volume up, I cannot get past the usb logo.
I have linked up the ZenFone to my computer, and confirmed that ADB devices correctly lists the device (I have usb debugging enabled), however, when I try to go to fast boot and am met with the usb logo, my computer does register and detect the phone, however, under device manager it has a yellow triangle with the device named "" MOOREFIELD". When the ZenFone 2 is in this usb logo state, I cannot access any fast boot commands. I am quite stumped at the moment.
Any help please? By the way, I use a windows 8.1 computer with usb 3 ports. However, I have tested using different cables, and on a windows 7 laptop with usb 2 ports, still to no avail. Should I try and update the firmware using Asus' software? Or is there a better solution?
Thanks
Edit: My friend claims that he did not see at any point in time, the flashing on the zenfone 2 start. He was faced with a "<waiting for devices>" or something similar message, telling me that the phone was not fully in fast boot yet. If I can get it into fast boot, I am sure I can reflash the custom stock onto the phone, and most issues will be resolved.
same error
i have the same error by my zenfone2 after update
please help
amohammadiazar said:
i have the same error by my zenfone2 after update
please help
Click to expand...
Click to collapse
Could you specify which update you did? From your computer? Or via Asus update on ur phone?
pkvk9122 said:
Could you specify which update you did? From your computer? Or via Asus update on ur phone?
Click to expand...
Click to collapse
my orginal firmware is CN and i wanted to change to WW mode i tried by pc .... now when i conect phone t pc it want moorefeild driver for conection and i dont have those ,,
Whenever I try to flash system.img it gets stuck on "writing 'system'..." and just hangs there. I have left it for over half an hour and it still didn't work. Does anyone know a solution to this problem?
Hey guys,
So after a while without any responses, I headed over to Asus customer service to receive a very unhelpful reply.
I gave up hope of finding an answer online and so I decided to take a leap of faith by updating the firmware via the Asus Update app on the phone.
I upgraded from 2.14 to 2.15 and miraculously fastboot seemed to have restored itself. I am not sure whether or not every single update restores fastboot, or whether the update to 2.15 does, but I'm glad that it has been fixed.
My previous problems of being unable to detect fast boot devices has been resolved. Hopefully others who have experienced the same issue can find this post helpful.