OK. I have the ATT htc one x. I was attempting to install Cyanogenmod 9. I unlocked the bootloader. Rooted the phone. I loaded twrp. This is where things get fuzzy. For some reason I was not able to load the .zip file of cyanogen. Then when I restarted the device it went into a kind of loop. Twrp was gone and I could and can go into the boot loader but the os is gone and it just shuts down if I attempt to go into recovery or reboot. Also, to make things worse, the phone is no longer being recognized by my computer with adb. Is my phone bricked or is there something I can do to set things right?!?!?!?!
did you install the twrp with working usb mount?
No. I installed it using goomanager. I wasn't able to install twrp or CWM using usb mount.
Is fastboot usb working in the bootloader (It will say fastboot usb in the bootloader screen while your device is plugged in)? You may have to ruu if both recovery and the os is not loading, but you'll have to relock your oem bootloader first using fastboot if possible. Otherwise I wouldn't know of any other fix without recovery working, unless someone on here knows of another way. This has happened to me once and I had to just ruu and start everything over again.
No fastboot usb is not working is there any way I can restore the ability to access it?
I have nothing left on it anymore so restoring is no problem if I can get access to my device.
[solved]
just downloaded drivers and moved them to htc driver folder in program files for anyone who was wondering.
glad to hear. was actually just about to ask whether you had the drivers installed correctly. Hope everything works out from there.
I have unlocked bootloader, rooted phone and installed TWRP recovery without any problems. I made one huge mistake - I wiped system and data, so Im left with no OS and no image to flash from memory. I can access TWRP wihout any problems, but i cannot use OTG mode (i cannot check box to mount it and in explorer usb is empty). When i connect my phone to PC i cannot flash using ADB, it cannot find the device. Fastboot can see it though. What do I do now, how to revive my phone?
fillion_f said:
I have unlocked bootloader, rooted phone and installed TWRP recovery without any problems. I made one huge mistake - I wiped system and data, so Im left with no OS and no image to flash from memory. I can access TWRP wihout any problems, but i cannot use OTG mode (i cannot check box to mount it and in explorer usb is empty). When i connect my phone to PC i cannot flash using ADB, it cannot find the device. Fastboot can see it though. What do I do now, how to revive my phone?
Click to expand...
Click to collapse
You need to use the mfastboot method. Check this tutorial: http://forum.xda-developers.com/showpost.php?p=47820707. Download the firmware (ideally 4.4.2 or 4.4.3) in *.xml.zip format, and do all the steps at the tutorial. Skip 3a) and go to 3b) - the one with mfastboot commands.
That's what helped me when I accidentally deleted my system - I also made a thread: http://forum.xda-developers.com/moto-g/help/bricked-moto-g-xt1032-converted-to-gpe-t3054655.
fillion_f said:
I have unlocked bootloader, rooted phone and installed TWRP recovery without any problems. I made one huge mistake - I wiped system and data, so Im left with no OS and no image to flash from memory. I can access TWRP wihout any problems, but i cannot use OTG mode (i cannot check box to mount it and in explorer usb is empty). When i connect my phone to PC i cannot flash using ADB, it cannot find the device. Fastboot can see it though. What do I do now, how to revive my phone?
Click to expand...
Click to collapse
Ya.. Using mfastboot and typing out those commands as given in tuitorial you can install stock firmware to your phone using the Adb.. Its not hard bricked. Don't worry. Had faced the same issue last month.
Sent from my Moto G using Tapatalk
I cannot flash sparsechunk 1,2 and 3 files, but it can be ROM's fault. I'll download another one to check if its working
EDIT: using another ROM worked for me, thanks for help
Debanka said:
Ya.. Using mfastboot and typing out those commands as given in tuitorial you can install stock firmware to your phone using the Adb.. Its not hard bricked. Don't worry. Had faced the same issue last month.
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
Sorry for pushing this old thread.
My phone is also stucked, adb cannot find my device. How do I do it then? If my device is not listed, is it possible using fastboot to get back to the old stock Firmware?
Hi everyone,
I'm hoping you can help me. I've had a OnePlus One since August 2014, completely stock. Never modded it, never 'flashed' anything, never installed anything outside of the Google Play Store. Always installed the official OTA updates as they pop up on the phone itself. Basically a reeeeealllly boring android user!
So Thursday morning (09/06/2016) I got a notification that a system update was downloaded and ready to install. Clicked install, the process began, phone rebooted as per usual. However, on the install progress screen (the green android with the spinning cogs), about one third of the way through the phone freezes. About 20 seconds later the phone reboots itself and then tries to install the update again. Freezes. Reboots. Tries to install. Freezes. Reboots. Tries to install.... I think you get the idea. It was doing this for a couple of hours before I checked it.
I'm moderately tech-savvy but never really got involved with android modding, rooting or flashing. So I'm a bit confused as to why my completely stock phone is stuck in a bootloop after installing an official CyanogenMod OTA update. The current status of my phone is that I can only boot into Fastboot mode via VolUp + Power. I can get my computer to detect my phone in Fastboot mode, however it informs me that my bootloader is locked. Attempting to boot into recovery mode via VolDown + Power just starts the update install and enters the bootloop.
I've done some research in to flashing a recovery image or manually applying the OTA update. One problem I've noticed is that I have absolutely NO idea what version of Android / CM my device was at before the update, and I have NO idea what version it was trying to update to. I do know that it was some version of Marshmallow before it broke. I've had no issues with the phone before this, aside the occasional self-reboot.
I REALLY want to keep all my data (pictures, contacts etc.) and am very nervous about actually doing anything because I have very little idea as to what I'm really doing.
Can anyone offer any advice on how to get my phone to boot/update/recover through Fastboot with a locked bootloader and without losing any data?
Thanks,
Stormin'
AKA the "HOW DO I PLAY BOOM BEACH NOW?!" guy
Edit: I solved my issue. It might work for you too, permalink to my post (#9) below: http://forum.xda-developers.com/showpost.php?p=67278091&postcount=9
Are you able to get into recovery mode? If so, you should be able to just flash a new ROM. Sideload one using the adb push command, wipe your data (this will clear settings, apps, etc. DO NOT SELECT SD CARD - that will wipe your personal files including your photos). Then install. Hopefully it should all work fine.
If you can't access the recovery can you access the bootloader sceen (the one with the big green bugdroid)? Then I'd suggest using Fastboot to install a new recovery. Then try the above.
If you can't even get to that stage you're screwed, just like me (unless anyone has any ideas). I've had soft bricks many times before but today I can't even get to the bootloader screen. ADB says the phone is offline. The screen is back and flickers on for a split second every now and then. Bloody CM Updater.
As IBM9001 has said, if you can get into recovery - even being stock - you can still clear your cache - don't do a full factory reset, just the cache, this may help, but even if it doesn't it still rules out one option.
I can't access recovery mode, using the key combo it just boots straight into the installer.
I've got a support ticket open with OnePlus and a scheduled remote assistance tomorrow. However from the preparational email it looks like they are going to factory reset the phone and then clean install CM. They've instructed me to make sure that all my files are backed up... I assume this means I will lose them.
Is there ANY way just to access or pull the photos off my phone? That's the most important bit. Dropbox hit its storage limit at the beginning of 2015 and I refused to pay, so now I have 18 months worth of pictures that I have no other copies of on death row
The only thing I can access is Fastboot...
Edit:
ibm9001 said:
If you can't access the recovery can you access the bootloader sceen (the one with the big green bugdroid)? Then I'd suggest using Fastboot to install a new recovery.
Click to expand...
Click to collapse
I can boot into Fastboot mode, and plugging my phone into my PC works i.e. it is recognised. I have the fastboot .exe and USB drivers, and can issue commands to my phone through cmd such as
Code:
fastboot reboot-bootloader
which works.
How do I use a recovery .img through Fastboot? or can I pull the contents of the sd card through Fastboot?
Hey mate i had same problem with my friends phone. But in that case i was able to open recovery mode.. So if you can do that just download any full zip of opo.. Like cm12.1 or cm13. Then flash it without clearing data.. So will not loose amything not even a single application..
I did that by using adb sideload just google it how to use it. And for that download full android sdk toollit and then download only fastboot and adb domt download whole studio. Because somete old version of adb and minifastboot will not work on adb sideload... So good luck with that..
Hi guys,
I have the same issue!
If I flash a new recovery from fast boot will I lose my data on sdcard?
Thanks.
Sent from my iPad using Tapatalk
masterjigar said:
Hey mate i had same problem with my friends phone. But in that case i was able to open recovery mode.. So if you can do that just download any full zip of opo.. Like cm12.1 or cm13. Then flash it without clearing data.. So will not loose amything not even a single application..
I did that by using adb sideload just google it how to use it. And for that download full android sdk toollit and then download only fastboot and adb domt download whole studio. Because somete old version of adb and minifastboot will not work on adb sideload... So good luck with that..
Click to expand...
Click to collapse
I cannot boot into recovery mode, unfortunately
masterjigar said:
Hey mate i had same problem with my friends phone. But in that case i was able to open recovery mode.. So if you can do that just download any full zip of opo.. Like cm12.1 or cm13. Then flash it without clearing data.. So will not loose amything not even a single application..
I did that by using adb sideload just google it how to use it. And for that download full android sdk toollit and then download only fastboot and adb domt download whole studio. Because somete old version of adb and minifastboot will not work on adb sideload... So good luck with that..
Click to expand...
Click to collapse
I'm currently having a very similar issue, but my phone completed the update. It's just stuck in a reboot/"optimizing apps" loop. I can boot into recovery and I tried to clear cache, but It's still just optimizing apps then rebooting and optimizing again over and over. Do you think your suggestion would help me too?
Wooooo, I've fixed it! I don't know why what I did fixed the issue (probably bypassed something) but my phone is up and running again! First thing I'm doing is making a freakin' backup!
So I was just trying everything in desperation. So that others can attempt to fix the same problem, here's what I did:
1. State of phone was either boots normally and crashes when installing update, or boots into fastboot. Would NOT boot into recovery!
2. Booted into fastboot using key combo (hold Volume Up, then Power Button)
3. Attached phone to computer via data usb lead
4. Started up cmd console, used command "fastboot devices" to check that device was recognised (note you need the fastboot files and USB drivers etc., Google it if you're not sure)
5. Used command "fastboot continue" to continue with 'autoboot'. This rebooted my phone but skipped the installer and went to the 'optimising apps' stage. Left phone alone for a couple of hours but it got stuck in another bootloop optimising apps, rebooting, optimising apps and so on.
6. Turned phone off, then booted normally with just the power button. This started the update install again except it didn't crash, and completed the update install. Then it optimised the apps again (albeit with a different total app count) and once finished, phone starts up normally.
Thanks for all the suggestions everyone! Happy to have my phone back. Now to go through the half-dozen or so voicemails I've collected over these last few days... great.
Hi guys,
@stormin, congrats!
@masterjigar, so you didn't lose the data like photos etc. doing so?
I can boot to recovery, but can't connect by PC to it.
In fast boot mode my PC sees it as well as in dab sideload mode.
I haven't the boot loader unlocked then I have to do it first, right?
But cyanogen site says that unlocking the boot loader will wipe all the device data.
Is there any way get the photos and other files back?
Thanks.
From the FAQ:
Q4a: Can I flash ROMs or SuperSU or anything else with the stock recovery?
No, the stock recovery can only flash zips that are signed by CM, this means official updates only. You need a custom recovery to flash anything else.
Click to expand...
Click to collapse
Does it mean I can flash an official CM firmware without unlocking the boot loader?
Thanks.
hibernick said:
Hi guys,
@stormin, congrats!
@masterjigar, so you didn't lose the data like photos etc. doing so?
I can boot to recovery, but can't connect by PC to it.
In fast boot mode my PC sees it as well as in dab sideload mode.
I haven't the boot loader unlocked then I have to do it first, right?
But cyanogen site says that unlocking the boot loader will wipe all the device data.
Is there any way get the photos and other files back?
Thanks.
Click to expand...
Click to collapse
That's what adb sideload is all about. It will give you temporary adb access (which is always after unlocking bootloader and root). So you can also flash xip via sideload. Without losing data and media..
Same problem, Also PC not detecting my phone
Hey Guys, I am Stuck at the same thing at Bootloop. But to do anything further I need to connect my phone to the PC. I haven't been able to connect my phone to PC since the time I have got the phone. I tried all available drivers and even tried different cables. I dont know what has been left out to try.
If any one has a working driver pls share the link. Its been three days now that my phone is dead.
Pls help!!
Thanks in advance.
masterjigar said:
That's what adb sideload is all about. It will give you temporary adb access (which is always after unlocking bootloader and root). So you can also flash xip via sideload. Without losing data and media..
Click to expand...
Click to collapse
can I flash this cm-13.1-ZNH2KAS1KN-bacon-boot-debuggable-b19ebe021f.img with the sideload and get adb working over usb?
Thanks
hibernick said:
can I flash this cm-13.1-ZNH2KAS1KN-bacon-boot-debuggable-b19ebe021f.img with the sideload and get adb working over usb?
Thanks
Click to expand...
Click to collapse
You can't adb sideload .img or a partition.
You have to use fastboot.
Code:
fastboot flash boot boot_img_name.img
or
Code:
fastboot boot boot_img_name.img
saurav007 said:
You can't adb sideload .img or a partition. You have to use fastboot.
Click to expand...
Click to collapse
Yes but then I have to unlock my bootloader first. And unlocking bootloader erase all the user files....
Is there other way to to run cm-13.1-ZNH2KAS1KN-bacon-boot-debuggable-b19ebe021f.img on the devise?
Hello all,
I have a stupid question for you all.
I have updated yesterday to Android Pie - and all is good.
Today I wanted to root.
I checked USB debugging is enabled, then booted in fastboot.
When I do fastboot devices on my PC, the phone does not show.
This worked 100% before (I have rooted this and previous phones many times)
What is going wrong here?
Thank you for any suggestions
I figured it out - the USB cable does not work. The second cable I tried worked - now I need to find a working TWRP as the previous TWRP (which I use as fastboot boot twrp.img ) crashes...
Bluspark latest worked fine for me.
Thank you! Would you have by any chance a link to download the latest bluspark? I found version 3.0.3 for OP 3 - is that the latest?
Same thing happened to me aswell. My PC didn't detect my phone when it was updated to Pie but i could still execute the commands. Flashed with bluespark twrp and all is good.
So I have a generic android rugged phone (F150 B2021) that I bought off eBay for £10. Nothing special but a decent backup. So anyway, this phone came with no OS installed but could get to the bootloader, fastboot and flash via ADB with what is one of the more feature-rich stock recoveries I've seen. I've tried everything- and I mean EVERYTHING to get this phone to work- flash TWRP, reboot into EDL mode, clear cache/ data both on the phone and via fastboot (neither worked)- nothing.
I can't get into the phone to enable OEM unlocking so the only method I found was flashing via fastboot- with all of the individual files. My only problem there is that I don't really understand how to do that- apparently you need to look at the contents of an .xml file (there are none of those visible in the stock OS files) and flash each one individually which I could do if I knew how to actually get to that stage. I was thinking perhaps to install a GSI of something just so I can get in to enable OEM unlocking and then flash it normally via ADB because I presume something like the Lineage 17.1 GSI would have even the "flash_all.bat" file which would make it much easier.
I guess my question is, from that stock ROM (attached) what do I actually need to flash? And how do I do it? It's so much different from, say, Nexus OS files I'm slightly more used to.
As long as a phone's bootloader isn't successfully unlocked FASTBOOT tool won't work at all.
You can try to flash phone's Stock ROM via ADB Sideload method.
xXx yYy said:
As long as a phone's bootloader isn't successfully unlocked FASTBOOT tool won't work at all.
You can try to flash phone's Stock ROM via ADB Sideload method.
Click to expand...
Click to collapse
Hi, that didn't work either. I was wondering if maybe I could enter EDL mode and connect the contact points to force it? Thanks
My f150 has mtk chipset I used mtk client tool to unlock and root