I was following the steps to update to Cyanogen's newest ROM and going through the steps on Cyanogenmod. I wiped, had both ROM's on my SD card and fell asleep while it was flashing the HTC recovery image. Well I must not have slept long and for some reason I thought it was done, but apparently I rebooted before the entire flash had finished. Right as I was rebooting I realized it said it was "formatting CACHE" but it was to late..I already started the reboot. So now my phone will get to the second loading screen that says "android" and then goes to a black screen. I have no recovery but can get into fastboot. I have the 1.6 SDK on my laptop, but have never used it, so the drivers aren't in place and plugging my phone in via USB does nothing.
I have read MANY posts about similar situations, but almost all of them involves using fastboot and ADB to push and install files, but how is that possible if I can't get ADB to work?? What else can be done via fastboot?? I know my phone isn't bricked, but not sure how to proceed from here.
I got a little further with my phone. I have ADB running on my laptop and I even got my computer to recognize the G1 as Android 1.0, but when I run ADB in a CD, it's not listing the phone. I am guessing because before this I wiped and never went and turned on USB de-bugging.
I ended up following the steps to downgrade, root, and ended up with a working phone.
Related
I was dumb enough to root my phone and try using some custom roms just to get a black notification bar and a couple other things. Thats literally all I wanted. Used Cyan, couldnt get notification bar to change color so went back to original. Anyways thought I'd try flashing the black desire bar or w/e, and failed.
Tries booting up and gets half stuck on the nexus 'X' animation loop. It gets really laggy and studders, never fully completing the loop. So I say eff it after fifteen or so minutes and reboot to recovery. Only it's the stock android recovery, not that clockwork one? So I'm lost, can't flash back to original, and decide i'll just try the factory reset. I have no time for this stuff at this point, and just want my phone so I can talk to people.
Did factory reset/wipe option, and still nothing, stuck on boot. Don't know what to do and I would greatly appreciate some help or advice. Honestly would be so sad if this $500 phone is a paperweight.
Dude relax,
1.First boot to superboot
2.Flash your clockwork (Or any other recovery). DONT REBOOT.
3.Go straight to recovery,
4.Restore your nandroid back up,
--- If you dont have back up then you have to download rom what you want (Stock froyo can be found some where in htc site)
--- Select mass storage option in the recovery and copy there the zip file, then flash it.
Tadaa everything is working again
Read my signature, "unroot / restore your Nexus", and execute. If you have ever updated to FRG83, you might be out of luck and no PASSIMG.ZIP will flash. In this case, you'll need to connect using ADB and run flash_image to flash recovery (most probably you'll get adb shell even if your phone isn't finishing boot - just make sure you run adb shell early enough in the boot). Once you've flashed the recovery, get into it and proceed with a custom ROM. If you flash stock again, your recovery will be lost again. If you didn't set up ADB (enable "USB Debugging" option on your phone) - then you're seriously out of luck. If you have it, but don't know how to use it - spend time reading and understanding "flashing Recovery" guide in the same place from my signature (Wiki), and if you have any further questions along the way - ask here.
You're not booting up because you've screwed up framework-res.apk and possibly some other system files - so you're stuck in boot loop. Need to read and understand what you're doing before you're doing it. It's really not that hard, and not willing to spend enough time understanding things "pays off" if mishaps happen - and they happen.
elkyur said:
Dude relax,
1.First boot to superboot
Tadaa everything is working again
Click to expand...
Click to collapse
He can't boot! Do you read what I read? He's stuck in a bootloop! What boot are you talking about?!
Take your time reading before you rush answering with wrong and incomplete instructions that won't get the OP anywhere. A good portion of mishaps happens because of instructions like these.
This is alot for me to take learn in such quick time to be honest.
I can't even get adb to recognize my phone and i've followed all the steps. My computer makes the noise that something has been plugged in through USB, but nothing else. Under that program to uninstall drivers, I try uninstalling them, but they just stay there, nothing changes.
As for the USB debugging and me being ****ed, I'm pretty sure I left that on.
Maybe it would help me if I told you more about what I know and what I've done.
Literally just followed the step by step instructions from this site theunlockr.com/ to root my phone and use a custom rom.
In the process it made me install PDANet (again probably means nothing, but I don't know).
If adb isn't recognizing my phone, I can't flash using it. Again thank you for the help, as I really am clueless about most stuff like this.
Most of the time when doing anything that could possibly do any harm to a device, I am very cautious. I have hacked several PSP's and didn't think this would be much different...
I read all about the rooting, and knew full well all i wanted to do was get a new notification bar, I didn't really read into the rest as I had no desire or use for that information. Then everything went well, and I learnt how easy it was to go back if I screwed up or didn't like what I had flashed. Not to mention people saying it's near impossible to brick your phone unless your really trying to. Maybe that was just me being ignorant, this could not have happened at a worse time. And I cannot thank you enough for your help thus far.
Thank you for the help. Your guides were very helpful. But unfortunately every step of the way I have run into some sort of problem.
When trying to install the sdk drivers, it won't let me install the amd64 or the i386, but only both of them together. As in it selecting usb_drivers installs (where both of the seperate drivers can be found). I don't know if this is right or not.
When typing in "fastboot devices", "HT036P901361 decives" shows up, but when viewed in USBDeview, 2 of the 3 HT036P901361 drivers show as not connected. The only one that shows as connected is the "vendor specific" one.
Also adb devices, shows nothing.
So again, I'm asking for advice or help.
Edit: So I can reboot fastboot through my computer, but cannot flash anything,
typing in "flashboot flash recovery recovery.img" I get a "cannot load recovery.img".
My recovery.img file is saved on the root of the SD card which is in the phone. Is this the correct way to do it? If so I assume it's still because of the issue stated at the beginning of this post (before edit).
Edit 2: Okay decided to try this
fastboot flash recovery C:\CWrecovery.img (where its located on my hdd), and it starts then says failed infoSignature.
volsey said:
Thank you for the help. Your guides were very helpful. But unfortunately every step of the way I have run into some sort of problem.
1. When trying to install the sdk drivers, it won't let me install the amd64 or the i386, but only both of them together. As in it selecting usb_drivers installs (where both of the seperate drivers can be found). I don't know if this is right or not.
2. When typing in "fastboot devices", "HT036P901361 decives" shows up, but when viewed in USBDeview, 2 of the 3 HT036P901361 drivers show as not connected. The only one that shows as connected is the "vendor specific" one.
3. Also adb devices, shows nothing.
So again, I'm asking for advice or help.
4. Edit: So I can reboot fastboot through my computer, but cannot flash anything,
typing in "flashboot flash recovery recovery.img" I get a "cannot load recovery.img".
My recovery.img file is saved on the root of the SD card which is in the phone. Is this the correct way to do it? If so I assume it's still because of the issue stated at the beginning of this post (before edit).
Edit 2: Okay decided to try this
fastboot flash recovery C:\CWrecovery.img (where its located on my hdd), and it starts then says failed infoSignature.
Click to expand...
Click to collapse
Let's get one thing straight. You need to read more, I guess, because you still don't know the basics - and with the lack of knowledge, it's going to be hard to help you.
Fastboot commands and driver only work when you're booted into bootloader - which is, 3 droids on skateboards on white screen and text menu, get there by booting with trackball or volumedown button pressed.
adb works only when you're booting the OS - which means, you don't touch anything and let the phone boot. Right when boot animation starts, adb should also start.
1. That's correct.
2. Are you booting into bootloader? There should be no other way to view fastboot driver. In that case, DON'T boot to bootloader, just reboot your phone and let it loop, and only then try "adb devices". If it works - use the "flash_image" method to flash recovery.
3. Read (2) above.
4. If your bootloader isn't unlocked (does it show a padlock below Nexus logo when you boot?), you won't be able to flash non-standard recovery through fastboot. You might be able to flash a complete system image through fastboot, though. Download a factory image, FRF91 for example, unzip it, then do "fastboot flash system system.img", "fastboot flash boot boot.img", and reboot.
When you flash something, you should open the Command prompt in the same directory as the file you're trying to flash! Or use full path for the image you're flashing. And it should be on the computer, not on SD card.
If everything fails - just unlock your bootloader and fastboot flash anything you want.
I am using bootloader.
C:\android-sdk-windows\tools>fastboot flash system system.img
sending 'system' (58570 KB)... OKAY [ 8.293s]
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 15.014s
That's the error I'm getting everytime.
I got the system.img from hXXp://developer.htc.com/adp.html, I tried looking for FRF91 but could only find megaupload links, and I had exceeded my limit somehow.
As for adb, still getting no devices when I leave it to boot by itself even though I've:
Uninstalled the 3 drivers, unplugged/rebooted, plugged back in/turned back on, and it automatically installs the wrong drivers again too quickly to do anything about it. I've gone into advanced system settings and checked it to never install system drivers automatically. Tried updating drivers, all say they're up to date.
1)So is bootloader not an option for me? Or is there something else I haven't tried? Why am I getting the signature errors?
2)Is it the drivers that are keeping adb from recognizing my phone? How do I fix this?
Any suggestions?
Ok, looks like USB debugging isn't on. In that case, there are exactly 2 options:
1) from here:
http://developer.htc.com/
Download FRG83 image for Nexus, rename to PASSIMG.ZIP, put on the root of your SD card (you can't use the phone for it, so use SD card reader), reboot into bootloader, it'll ask you to flash system image, answer "yes", wait for it to flash. Keep the phone powered. WAIT.
2) if it doesn't work - you're out of luck. "fastboot oem unlock" it is. Then you can flash whatever you want with fastboot.
Okay everything started when i wanted to go back to stock after having installed CyanogenMod 12 on my VS980. Everything went well with the install but when i finally wanted to go back, i couldnt enter download mode, instead i would get fastboot mode. I looked into that and people said i only had to replace files like Laf.img, boot.img, and aboot.img through command prompt. When i did this and rebooted the phone, the lg logo came out saying "Security Error" and then bootloops. I can enter Twrp Recovery with ease but i cant go into fastboot nor Download Mode. When i connect to the computer while in Twrp though, my computer picks it up as VS980 but says it was not installed correctly. I dont know what happened and im confused on whether is Soft- Bricked or Hard- Bricked. If anyone could help me with this problem please i have a Windows computer btw, not linux, im not sure if i need a linus for this fix though
Just putting out there, everywhere i look, people always send me here: http://forum.xda-developers.com/showthread.php?t=2432476
This just doesnt work for me since i cant enter download mode.
All help is appreciated and thank you in advance.
which TWRP version do you have?
the most simple solution if you have TWRP working is to flash a rom via OTG
I'm in the same boat man. I can get into TWRP 2.8.0.1 and download mode, but I can not get my drivers to install correctly. I have the drivers in a file. I've pointed my computer at that file, rebooted computer, changed usb cables, tried sideload feature in TWRP, tried the LG flash tool. Nothing helps. God I'm so dumb for erasing internal storage. I'm so used to having an sd card and was just thinking, don't erase sd card and you're good. I rushed through it and f'd up really good.
Errors
adb devices-doesn't list device just blank space
sideload or push just yields a list of all the commands, but nothing else
when I plug phone in to computer-drivers not installed correctly. 'MTP USB failed'
flashtool-'failed previous load'
sideload function of TWRP-It just tries to load forever
terminal in TWRP-I ran a command, but then it says you are not rooted install supersu. Not matter what I choose it reboots and sticks at 'LG' screen.
My drivers worked before I wiped internal storage, so I know it's my phone. Drivers just worked to transfer xdabbeb's 2.3 over 3 minutes before I shyt the bed with it.
I have a relatively new Nexus 6. The last phone that I rooted was the old HTC Hero, and things have changed! I had unlocked the bootloader and rooted the phone under 5.1.1 and when I flashed Marshmallow 6.0 yesterday I lost root.
So I decided that I would try to root the phone again. I had problems with the drivers... my PC would recognize the phone when it was powered up normally but as soon as I booted into fastboot I couldn't get ADB to find it.
Then I went to this link: http://www.theandroidsoul.com/marshmallow-root-for-nexus-5-6-7-9-and-player-by-chainfire-84862/
got my fastboot and adb set up and working, followed his instructions to get root, flashed the twrp image, and flashed the SuperSU file. Everything seemed to work properly. Made a complete backup using twerp and transferred it to my PC via USB.
After all this a tap on Reboot System was supposed to restart the phone. Didn't happen.
I'm stuck in a fastboot recovery loop. Whenever I power down and try to turn the phone on I come back to the fastboot screen. When I elect to go into "recovery" it opens the twrp screen on my phone which asks for my pin and then I have the twrp screen with the regular options.
This is new to me... I don't know if access to the twrp screen and its commands is a help or not, but I do realize that the adb and fastboot on my PC is necessary for about anything I need to do and it seems to be working. I believe that I've described my situation accurately...
Any help appreciated!
turnagerg said:
I have a relatively new Nexus 6. The last phone that I rooted was the old HTC Hero, and things have changed! I had unlocked the bootloader and rooted the phone under 5.1.1 and when I flashed Marshmallow 6.0 yesterday I lost root.
So I decided that I would try to root the phone again. I had problems with the drivers... my PC would recognize the phone when it was powered up normally but as soon as I booted into fastboot I couldn't get ADB to find it.
Then I went to this link: http://www.theandroidsoul.com/marshmallow-root-for-nexus-5-6-7-9-and-player-by-chainfire-84862/
got my fastboot and adb set up and working, followed his instructions to get root, flashed the twrp image, and flashed the SuperSU file. Everything seemed to work properly. Made a complete backup using twerp and transferred it to my PC via USB.
After all this a tap on Reboot System was supposed to restart the phone. Didn't happen.
I'm stuck in a fastboot recovery loop. Whenever I power down and try to turn the phone on I come back to the fastboot screen. When I elect to go into "recovery" it opens the twrp screen on my phone which asks for my pin and then I have the twrp screen with the regular options.
This is new to me... I don't know if access to the twrp screen and its commands is a help or not, but I do realize that the adb and fastboot on my PC is necessary for about anything I need to do and it seems to be working. I believe that I've described my situation accurately...
Any help appreciated!
Click to expand...
Click to collapse
how about this, adb NEVER EVER works in fastboot mode. that is reserved exclusively for fastboot. you have to use fastboot to flash a recovery, then the recovery to flash supersu.
---------- Post added at 04:49 PM ---------- Previous post was at 04:48 PM ----------
now it also seems as you have to fastboot flash a factory image as well.
turnagerg said:
I have a relatively new Nexus 6. The last phone that I rooted was the old HTC Hero, and things have changed! I had unlocked the bootloader and rooted the phone under 5.1.1 and when I flashed Marshmallow 6.0 yesterday I lost root.
So I decided that I would try to root the phone again. I had problems with the drivers... my PC would recognize the phone when it was powered up normally but as soon as I booted into fastboot I couldn't get ADB to find it.
Then I went to this link: link removed to satisfy forum policy...
got my fastboot and adb set up and working, followed his instructions to get root, flashed the twrp image, and flashed the SuperSU file. Everything seemed to work properly. Made a complete backup using twerp and transferred it to my PC via USB.
After all this a tap on Reboot System was supposed to restart the phone. Didn't happen.
I'm stuck in a fastboot recovery loop. Whenever I power down and try to turn the phone on I come back to the fastboot screen. When I elect to go into "recovery" it opens the twrp screen on my phone which asks for my pin and then I have the twrp screen with the regular options.
This is new to me... I don't know if access to the twrp screen and its commands is a help or not, but I do realize that the adb and fastboot on my PC is necessary for about anything I need to do and it seems to be working. I believe that I've described my situation accurately...
Any help appreciated!
Click to expand...
Click to collapse
I asked for help before searching thoroughly enough! I figured out that I needed to download another ROM, transfer it into the phone's storage, and install using TWRP. I really didn't understand the capabilities of this fabulous application and had simply flashed it because the thread instructed me to.
I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?
At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.
PiArc said:
At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.
Click to expand...
Click to collapse
I may not have a chance for a few days, but I will try this. I did try to download the software on the second link you provided and some of the links on that page were broken.
I'm not going to lie, navigating those threads is harsh.
Towards the end of the first linked thread you can see a post with what ended up getting me into fastboot. It might be a decent little roadmap to guide you in the right direction (plus, I think the files I indicate in that particular post are all still up).
Keep us updated!
ohioDroid said:
I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?
Click to expand...
Click to collapse
Try reflashing twrp via fastboot, install custom ROM -OR- download latest XML for your variant flash via rsd lite or manual flash.
Note: When using the XML you will lose everything, including data on internal storage.
Hopefully this helps ?
Also, if your phone stays black it's likely the battery is dead. Leave it hook up for awhile or keep trying to boot into fastboot(while plugged into outlet, not PC) and leave it for a couple of hours, should charge.
I'm speaking from personal experience, just without having Xposed framework, lol.
Sent from my Moto X using Tapatalk
I'm stuck at an issue that I've never seen before and need some assistance. I flashed invictrix 8.1.0 not to long ago and then installed an updated version of the rom through the rom's updater. It went through the automated flashing of the updated version and now I'm stuck in a recovery that seems to be stock, but it's not the stock version I am accustomed to seeing. I can not do anything in this recovery. I have used adb to do things before, but now adb and fastboot seem to get stuck at waiting for device errors or error:device not found even though adb devices and fastboot devices brings up the phone being connected. I now can no longer boot into the phone as I did a hard reset while my phone was operational.
Have you tried booting straight into fastboot mode by holding down Power+Vol Up until it reboots? And then see if you can use fastboot on your PC to flash TWRP again.
Also, all those error messages. Did you at some point reformat the cache partition as f2fs? It's supposed to be ext4..
I can boot into fastboot. The computer recognizes the phone through fastboot devices and adb devices. However, issuing a command through fastboot results in a waiting for device message. Maybe I need to find a more suitable adb. The one I’ve been using is the 15 second adb that only installs the google driver and the adb. I never formatted anything. I’m not sure what to do at this point.
I would use an unbrick guide and start from scratch.
Is there one you'd recommend ? I'm using this one :
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Yes, I also used it in the past and everything was ok.