i've been trying to use a fastboot method to get out of a softbrick.
I'm not sure what im doing wrong, i cant get into recovery mode but my phone just boot loops.
When i try to use the guide with the software they provide my computer tells me "This application has failed to start because AdbWinApi.dll was not found." when i try to run a command prompt.
Does anyone know what i can do to fix this?
Download dhacker's one-click and follow the instructions.
Sent from my DROID BIONIC using xda premium
Related
Apparently when it comes to rooting, flashing, etc I know enough to wreak havoc. This is my first attempt at rooting and flashing a new rom. I decided to experiment with my old g1 before doing it with my vibrant. What I have managed to do is make it not work. I was following the guide to flash cm 6. I updated the radio, then put danger spl on, that was the easy part. Through this entire process when I power+home I'd get the triangle ! and would need to press alt+L to see my options. When I would try to update the rom I would get "can't find update script" and the installation would fail. Now my G1 just hangs at the t-mobile G1 screen. I can get into my fastboot and recovery screen so I know I'm not completely toast. I have installed android sdk on my computer and updated the drivers, in device manager it recognizes my "android phone" but when I go into adb or fastboot my device is not recognized. I'm lost and not sure what to do. Any help would be greatly appreciated.
You need a custom recovery image.
See this post and follow instructions for fastboot.
http://forum.xda-developers.com/showthread.php?t=566669
I tried to follow that, but fastboot doesn't recognize my device.
Just to clarify the "fastboot devices (to make sure that fastboot "sees" your device)" this would be from the cmd prompt correct?
Any ideas? Anyone?
Sent from my SGH-T959 using XDA App
Yes but u have to make sure u are in the right directory in the prompt before u type the command.
Sent from my HTC Magic/Dream using XDA Premium App
Or try this
http://forum.xda-developers.com/showthread.php?t=532719
Hey so I currently have an unlocked bootloader and I try to flash a custom recovery via fastboot yet it hangs on < waiting for device > every time.
I have followed the cyanogen mod wiki step by step. It hangs on clockwork and amon RA. USB debugging is enabled. When I boot into recovery it says fastboot I then connect it to my computer it says fastboot USB.
I'm sure it will be some little setting that's wrong. I am currently running 2.3.4 stock, no root so rom manager is a no go.
I guess what I'm asking is does anyone know what I can do to flash a custom recovery?
Have you tried "fastboot devices" to make sure you have a connection?
What kind of computer are you using (Win/Mac/Linux)?
Fastboot devices gives an empty line the a new terminal line.
Also I'm running win 7.
My initial suggestion would be to update your drivers for fastboot. I have had this happen a couple times and a driver update resolved it for me.
Sent from my Nexus One using XDA Premium App
CapStone said:
Fastboot devices gives an empty line the a new terminal line.
Also I'm running win 7.
Click to expand...
Click to collapse
That means your phone is not connected. Update the drivers, as suggested above...
Much appreciated I will try this when I get home tonight.
Good evening all. I am hoping for some help before I try and exchange my Nexus 7.
The Nexus 7 was running Rasbeanjelly fine on a trinity kernel.
I flashed a new kernel motlry kernel.
I am now stuck with access to fastboot, no access to recovery, the 7 wont boot up.
So I cant get to recovery (which was TWRP). I cant flash a new rom because the computer (windows 7) doesnt see the device. I have downloaded the Nexus 7 tool kit but it doesnt see the device even if I refresh the drivers (before the issue I had no problems with the 7 being seen on the computer). I dont see how I can use adb as the device cant be seen by the computer.
Any last thoughts before I return?.
Many thanks one and all.
Matt.
This may help you blog.laptopmag.com/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
Yeah but adb uses command line? Just because it is not showing up doesn't mean you are without a fix. Don't give up. Did you try using a toolkit? I had a similar problem but got it to work. I am trying to remember how I got it to flash. Thinking......
Sent from my Nexus 7 using xda app-developers app
fastboot you say that you have? try fastboot booting your recovery. also, when you get this sorted, your gonna want to flash the newest bootloader, it fixes the issue of not being able to get into recovery from your bootloader.
put the recovery file into the same folder as fastboot on your computer. open fastboot/open the command window. type..
fastboot devices(press enter)(this should give you your devices id number if fastboot sees your device)
fastboot boot recovery yourrecoveryname.img(press enter)(this should boot the recovery)
Thanks guys for the advice. I will give it another go this weekend and come back for a bit of help or let you know resolved. Last day at work!.
Thanks again.
Matt
I had mine stuck with no bootloader and managed to get it flashed. I do not see the point in spending hours with command line unless you would want to learn. Why spend hours on something when you don't have the time? Some say not to use toolkits but I guess they always want to make things harder for themselves. Granted, we need to understand exactly it is what we are doing, many of tutorials are like one of big riddle. I recommend using this toolkit.... http://forum.xda-developers.com/showthread.php?t=1809195 Make sure you are at page 1.
Sent from my Nexus 7 using xda app-developers app
Thanks all got it fixed with Nexus Root Tool kit. I have now update the bootloader to 3.41.
Matt
Hello,
ok so the problem is I tired to update to Jelly beam, i read about it here and i follow the steps. I make it to recovery and when i wanted to install files from zip it gave me error - Installation Aborted. I read somewhere that i have to update my Clockwork recovery so i tried and since then i can't do anything. When i press the power button i go to bootloader, from there if i chose Recovery the phone reboots and stucks on the colored X. When i type "adb devices" in cmd so i can try to apply some method list of devices is empty. I think it can be fixed if i make it to recovery but i can't. I looked a lot and maybe its because im mad or something but i can't find a solution, so if anyone can help me i will be very happy. I don't bother if im back to stock.
Use fastboot in bootloader, adb is only available in os and recovery
fastboot flash recovery recovery.img
Sent from my Nexus One using xda app-developers app
demkantor said:
Use fastboot in bootloader, adb is only available in os and recovery
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Tried that, stuck on : <waiting for device>
EDIT: I tried on my brother laptop and it worked but when i exucute the command, it says FAILED(remote: image update error)
EDIT2: Thanks i fixed it its working now. WOOHO!
when in bootloader have phone in fastboot mode, connect to pc via usb, make sure you have the proper drivers
HERE, THIS SHOULD HELP this is for a different phone so dont use the files but the concept is the same
Hey all, so I was installing HD revolution which is compatible with the T mobile version. I installed it before and had no problems. Went to install the updated version today and did and at the end it says root may be lost and asked to fix it. I said yes. Now the phone is in a boot loop. It goes to the HTC "quietly brillant" screen and has the this build is for developmental purposes at the bottom and what not and then reboots to the same screen but says entering recovery at the top then the screen turns black and it flashes a glimpse of CWM then restarts the process over and over. I tried to boot into recovery and what not through the toolkit but USB debugging isn't available. Please help I have no idea what to do.
EDIT- I can get into the boot loader but I've never done anything with adb or fastboot or anything like that so hopefully there is a way to fix it with this?
Also in the bootloader above "unlocked" It says "tampered", not sure if that means anything.
http://forum.xda-developers.com/showthread.php?p=41076144
Download the mini sdk file from that post. Use the instructions there to access fastboot. Then use the command "fastboot erase cache"
Should fix your recovery issue and then reflash the Android Revolution ROM.
Sent from my HTC One using xda app-developers app
ilal2ielli said:
http://forum.xda-developers.com/showthread.php?p=41076144
Download the mini sdk file from that post. Use the instructions there to access fastboot. Then use the command "fastboot erase cache"
Should fix your recovery issue and then reflash the Android Revolution ROM.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks man you're awesome. It worked.