Develop Bugs

A big problem (Recovery no volume buttons without software ?)

I have a DHD I stick it in recovery mode but I do not go volume buttons. I tried to install a custom room and formatted system after that I gave reboot. How do I put the phone in recovery mode without volume buttons and software installed? ADB does not recognize device. Please, help me!

Grady22 said:
I have a DHD I stick it in recovery mode but I do not go volume buttons. I tried to install a custom room and formatted system after that I gave reboot. How do I put the phone in recovery mode without volume buttons and software installed? ADB does not recognize device. Please, help me!
Click to expand...
Click to collapse
if you can access fastboot flash a ruu
Sent from my GT-N7000 using xda app-developers app

Without volume or usb recognition you can't. You've really got to get adb working.
Sent from my Margarita blender.

There are any chance to back my DHD life
Hello Dev
I fall in the same problems here. Only my OS ubuntu 12.10 detected my HTC Desire HD..Here is lsusb :
(Bus 002 Device 003: ID 0bb4:0ff9 HTC (High Tech Computer Corp.) Desire / Desire HD / Hero (Charge Mode)
No adb no fast boot, Not working volume Down. Even last night i was make a gold card .. and put shipped rom there but no luck.
Last OS was CYANOGEN 7.0 then update to 7.2.. After that i did the mistake.. I was run aahk package for root and downgrade .. actually i wanted to go back stock rom.. but i can not :crying: :crying: :crying:
is there any chances to back my DHD life.. oh i visit aahk irc channel ... and they kicked me ..

I solved the problem, I downloaded the drivers for adb from here, and run adb, I gave command adb fastboot recovery and flash new rooom . Thx XDA

What about me BRO??
Grady22 said:
I solved the problem, I downloaded the drivers for adb from here, and run adb, I gave command adb fastboot recovery and flash new rooom . Thx XDA
Click to expand...
Click to collapse
Then u may just fall in or stuck in some kind of driver probs. its not bricked. My HDD is actual bricked. There is no hope i think... I tried from ubuntu 12.10 /OS and also win 7...
CAN ANYONE GIVE ME A CLUE..:crying::crying::crying::crying::crying::crying::crying::crying::crying:

soft bricked need help please :(

hey guys my phone is bootlooping again i know i can fix it i just need to get into recovery the problem is my vol buttons are both broken before i used a program that booted my phone into recovery but i cant remember the name for it ive tried looking for it again but cannot find it can anyone help? its not omap
EDIT: i think its soft bricked my comp is recognizing it tho as galaxy nexus

Do you mean ADB?

you have adb on your computer ? adb reboot recovery ?

acras13 said:
you have adb on your computer ? adb reboot recovery ?
Click to expand...
Click to collapse
no im actually not sure whats wrong now its recognized as omap 440 omap flasher works without any errors but still bootloops adb doesnt work it recognizes it but says its offline

so the current situation is im bootlooping cant get into fastboot or recovery the computer recognizes my device and its called samsung adb interface under device manager and samsung mtp device. adb wont work because it says my device is offline any help would be highly appreciated odin doesnt recognize my device either (

[Q] Bricked my Ouya

Hello,
I have tried to install cm11 on my ouya with the result that I got only a black screen now.
ADB says that the ouya is offline!
Is there any trick to get in fastboot?

Did you have any type of recovery installed? Might be too late, but remember you need to have Bootmenu installed first, if you did, then it should be fixable. If it doesn't work...pretty sure Target sells OUYA in-store for like $35. Their website says $89, but the last few times I've been there they were $35-40.

brandogg said:
Did you have any type of recovery installed? Might be too late, but remember you need to have Bootmenu installed first, if you did, then it should be fixable. If it doesn't work...pretty sure Target sells OUYA in-store for like $35. Their website says $89, but the last few times I've been there they were $35-40.
Click to expand...
Click to collapse
Hey,
thank you for your answer!
I had cwm installed and was in cwm before! then i did something wrong
Your tip with a new ouye is no help for me, because I am from germany.
Here costs the ouya 99€ that are nearly 135$.

You need to have CWM installed, then OUYA BootMenu, then CM11. When you say ADB tells you the OUYA is offline, I assume you were doing the ADB TCP connection before. Does Windows detect anything when you have your OUYA plugged in to your computer? Does Device Manager show "OUYA (or OUYA 1.1)" with a yellow exclamation point? If not, then you're probably hosed - but, I believe their rooting policy is pretty laxed, you may want to see if it would be worth sending it in for a repair/replacement if you can't get it started.
Anyway, if it does show up in Device Manager, then you need to modify the USB driver (there are several guides, including on this forum), disable driver signing if necessary, and you should be able to get fastboot to work (assuming you're in this situation).

Hi! Never used adb over tcp! Cwm was installed... i was in cwm and tried to install cm11 over adb... since this its bricked! I have bought my ouya on ebay and have no invoice... so there is no warranty!
The ouya is shown up as adp device... tried the other ones in the driver package i have got... it worked before this crash!
Gesendet von meinem XT894 mit Tapatalk

Does it show up as actually connected though? If it does, then the recovery partition should still be there (I can't imagine CM11 includes a recovery partition, otherwise we wouldn't need BootMenu it seems to me). If it does then adb reboot recovery should work, if you can get to recovery then you're golden.

What did you mean with connected though? if it is shown up in device manager? Yes it is!
I only see a blank screen on tv!

So if you type adb devices does it show up as connected? If it does, try adb reboot recovery.

brandogg said:
So if you type adb devices does it show up as connected? If it does, try adb reboot recovery.
Click to expand...
Click to collapse
Hi,
the device is shown up with its device ID as offline!
adb reboot brings: error device offline!

This may help
ibaxx said:
Hello,
I have tried to install cm11 on my ouya with the result that I got only a black screen now.
ADB says that the ouya is offline!
Is there any trick to get in fastboot?
Click to expand...
Click to collapse
Found an unbrick method it works as long as adb is on and clockworkmod is accessible,i saw your post and i uploaded my guide just so take a luck if you have had no joy,it has a tool to get if adb is not working for xp so you could try that if your on xp and only get OUYA? showing in device manager,this was my problem and this is something i figured out alone,i couldn't edit anything in ini files to make it work as adb device,but this tool saved my @ss.It took 48hrs of painstaking scouring the net to fix the device, i had put boot menu on but the console had been destroyed playing after showing red on normal boot,nobody gives the details anywhere i find in laymans to apply the cynogenmod firmware, someone should put one up on xda that has simple laymans step by step points to follow on setting it up,i got it on just would not boot past the logo for cynogenmod firmware?And online nobody has written a laymans tutorial infact only guide i found is the most uninformative and convoluted tutorial i have ever seen before.

[Q] ADB Error device not found

Hey guys thanks for reading and hopefully we can get this problem solved. The problem is that my pc won't reconize my phone when I boot into hboot. I've been trying to return to stock since I'm returning the phone for a replacement but I cant because it doesn't show up.
I've tried
Different cables
restarting phone and pc
uninstalling and reinstalling
Different platform tools
Another this is that when the phone is on and connected it shows up when I type adb devices if you guys can help that would be great, Thanks

Solved - Device Shows up
This same no show in hboot sent me in circles until I realized that in order for my device to show that I had to not be in the the bootloader. When I am in bootloader it shows List of Devices attached as empty, however when I use the adb devices while device is at the boot-screen it will show the device and can receive fastboot commands. Hope that helps.:good:
LoneWolf said:
Hey guys thanks for reading and hopefully we can get this problem solved. The problem is that my pc won't reconize my phone when I boot into hboot. I've been trying to return to stock since I'm returning the phone for a replacement but I cant because it doesn't show up.
I've tried
Different cables
restarting phone and pc
uninstalling and reinstalling
Different platform tools
Another this is that when the phone is on and connected it shows up when I type adb devices if you guys can help that would be great, Thanks
Click to expand...
Click to collapse

Problem with fastboot (ZE550ML)

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.