So, I have CyanogenMod 7.0.3 Stable flashed in my Legend, and it's been working just fine. Until couple days ago when I made some theme changes through Theme Chooser and flashed some theme add-ons. Now the phone is acting just stupidly. It's in a bootloop (sometimes loops in HTC bootscreen, sometimes in the CyanogenMod bootscreen), usb connectivity doesn't work (fastboot usb works, adb/mass storage etc. doesn't). I have tried to wipe the phone and flash that rom/recovery again through fastboot, but fastboot says "remote: not allowed" or something like that. Bootloader works, fastboot works, even recovery works but it's no use 'cause adb driver doesn't recognize the phone.
Please guys, help me. What should I do to get my phone running again? (working CyanogenMod or even a stock without root, I don't care, I just want this thing up and running again)
EDIT: And the weird thing is, that couple times I was able to boot the phone normally using recovery by just sticking the usb cable into the phone. And also, couple times I was able to boot it normally by just using fastboot reboot (I was able to get to the HTC Setup screen and then it would crash and show just black screen with notification bar)
It's possible the you're USB bricked. A quick search of "USB unbrick" should bring the required thread to light (search in development)
TheGrammarFreak said:
It's possible the you're USB bricked. A quick search of "USB unbrick" should bring the required thread to light (search in development)
Click to expand...
Click to collapse
Yeah, I have thought of that! Only problem is that how am I supposed to get the required files (flash_image and .img) to SD card without a way to manage SD card? Can I flash the image using fastboot?
I can't do it inside the phone 'cause I'm in a bootloop and can't boot the phone.
EDIT: Is there a chance to do a wipe and flash a new rom using only fastboot or something?
In theory you can flash without recovery, but only if you're S-OFF. You'll need the ROM in .img format too.
I used a microSD to SDCard reader to transfer the files., they're fairly cheap in high street stores. Or borrow a friends Android phone
TheGrammarFreak said:
In theory you can flash without recovery, but only if you're S-OFF. You'll need the ROM in .img format too.
I used a microSD to SDCard reader to transfer the files., they're fairly cheap in high street stores. Or borrow a friends Android phone
Click to expand...
Click to collapse
Well, am I able to flash those files once they are in the SD card? I mean with S-ON cause I don't have S-OFF?
Or is my phone a complete brick? =( Cause I'm pretty much all out of ideas..
Once you've got the files needed for a USB unbrick on your SD card you'll be fine
if you have recovery access did you try to make apply update from SD card in order to pass in cwm recovery.
if you got a USB brick you can use a multifonction printer to mount your SD on your computer.
So in a nutshell, my problems are:
- My Legend is in a bootloop
- Apparently my phone is USB bricked cause only fastboot works
- I don't have a recovery, when I go manually into recovery (recovery -> POWER + VOL UP) it goes into stock recovery
- And also my phone is S-ON
Could you guys point me into the right direction with this, I really want my phone back working. What should I do?
When you get to the stock recovery, navigate to ans select "flash update.zip from SDcard" That should get you to ClockworkMOD. Once there you'll need to use ADB to push the files required for the USB unbrick procedure to the SDcard (adb push [files-on-pc] /sdcard/) You should no be able to perform the the USB unbrick.
You may need your phone plugged into a PC for it to boot
TheGrammarFreak said:
When you get to the stock recovery, navigate to ans select "flash update.zip from SDcard" That should get you to ClockworkMOD. Once there you'll need to use ADB to push the files required for the USB unbrick procedure to the SDcard (adb push [files-on-pc] /sdcard/) You should no be able to perform the the USB unbrick.
You may need your phone plugged into a PC for it to boot
Click to expand...
Click to collapse
But I'm getting this blue recovery screen with only four options instead of the original green one including option to flash zip. So wtf has happened?
EDIT: In the blue recovery screen it says Can't open cache/recovery/command. And when I choose "apply sdcard:update.zip" it says "signature verification failed" and it aborts the installation.
Fakeflash.
TheGrammarFreak said:
Fakeflash.
Click to expand...
Click to collapse
So I am able to flash roms only using this menu? Am I correct? Just do a wipe and apply update.zip?
Why does it say "verification failed" then?
EDIT: Oh I see, I have to download fake-flash update.zip and apply update.zip takes me to the clockwork recovery? When I put the update.zip to the SD card and apply it, then it should go on with out any "verification failed" errors?
TheGrammarFreak said:
Fakeflash.
Click to expand...
Click to collapse
My main priority is just to get the phone to run normally again, I can worry about the USB Unbrick later. So I just want to do a full wipe and flash Cyanogenmod again. Am I able to do all that is required to run the phone again normally with fakeflash?
Thanks in advance TheGrammarFreak, I really appreciate your help!
The phone won't run normally until you do a USB unbrick.
One of the things that happens with this USB brick is that a flag for advanced debugging gets set. It's a very deep setting, and the setting is read ad the HBOOT level. If this flag is set to on (like it is in a USB brick) the phone will not boot unless it's plugged into a computer. Remember that
In order to get your phone back I believe you will need to plug your phone into the PC and turn it on. It should boot, if not you will need to get to recovery and wipe/reflash (you'll need to do this while plugged into a PC too). Once you have a running system/you're in recovery you can use ADB to push the files needed for a USB unbrick to your SD card.
Assuming you got that far, you should be in a prime position to follow the USB unbrick procedure.
I'm going away tomorrow for a week, and I will not be online at all. If you need more help you will need to get someone else in. That said, I believe that with the information in this thread, the USB unbrick thread, the fakeflash thread and Google you have enough information and help top fix your phone
TheGrammarFreak said:
The phone won't run normally until you do a USB unbrick.
One of the things that happens with this USB brick is that a flag for advanced debugging gets set. It's a very deep setting, and the setting is read ad the HBOOT level. If this flag is set to on (like it is in a USB brick) the phone will not boot unless it's plugged into a computer. Remember that
In order to get your phone back I believe you will need to plug your phone into the PC and turn it on. It should boot, if not you will need to get to recovery and wipe/reflash (you'll need to do this while plugged into a PC too). Once you have a running system/you're in recovery you can use ADB to push the files needed for a USB unbrick to your SD card.
Assuming you got that far, you should be in a prime position to follow the USB unbrick procedure.
I'm going away tomorrow for a week, and I will not be online at all. If you need more help you will need to get someone else in. That said, I believe that with the information in this thread, the USB unbrick thread, the fakeflash thread and Google you have enough information and help top fix your phone
Click to expand...
Click to collapse
Legend is up and running again! Thank you so much TheGrammarFreak!
Same problem here, but slightly different. He doesn't recognize my SD card (tried different ones) anymore ... out of the blue ... so how can I unbrick ??
http://forum.xda-developers.com/showthread.php?t=751265
follow this guide, helped me a lot.
you'll need root access.
Hi all,
So, I done effed up. I've been running Elegancia with no problems for a while now, and decided off the cuff to try something new. Long story short, I didn't read properly and ended up flashing an International ROM to my phone by accident. No problem, I think, I'll just ADB sideload Elegancia again.
I boot into TWRP recovery and then find that my computer no longer recognizes my phone. So, I hit restore on TWRP, and restore a backup that I'd made beforehand. After everything finishes restoring, I discover to my dismay that the backup did not include my OS.
Now, when I power up my phone, I can boot only into bootloader. When I try to boot into recovery, the phone is stuck on the TeamWin logo and doesn't move. If I turn on the phone without booting into bootloader, I'm stuck on HTC's logo. My primary goal right now is just
In conclusion, I have no idea what to do with the following problems:
1. When booting into bootloader, my computer no longer recognizes my device, so I have trouble flashing TWRP. Basically, my computer searches for an HTC MTP driver, and then fails to find one/install one. When I try to update the driver manually by downloading a MTP driver and then installing via Device Manager, Windows tells me I'm already using the most up-to-date version.
2. When booting into bootloader and then going to Recovery, my phone will boot into teamwin's logo ... and then not move from there.
I'm aware that I've screwed up pretty bad-- I've done my best to read stuff that's relevant, though. I'd love more help, please! Thanks in advance. Lots of invisible cookies coming your way.
[EDIT: It turns out TWRP was just taking a really, really, really long time to load. That said, my problem now is this:
- When going to Advanced -> ADB Sideload, my computer does not recognize my device when using adb devices.
How can I make sure that this actually works? Thanks again!]
[EDIT #2: Okay, um, I don't know why, but for some reason my computer now lists my device after going into sideload from TWRP. Maybe something to do with a reboot of my computer. If that's true, I feel really stupid. Will update if sideload doesn't work ... I think the cosmic gods are laughing at me. I guess all I had to do was post in xda-developers so that I could publicly embarrass myself before I fix my phone.]
[EDIT #3: Everything works and I'm dumb.]
I have done a lot of Googling over the past couple weeks trying to solve this issue.
I have two Alcatel OneTouch Elevate phones (5017B). One is working and the other is bricked. I tried to turn off the softkeys using a root app (something I had done successfully before) and it never booted past the Alcatel boot logo screen after that (screen goes black). I can boot into (stock) recovery, and wiping cache and data don't fix the issue. I am pretty sure I have corrupted something.
I have managed to extract all of the partitions from my good phone (system.img, boot.img, recovery.img, etc.), and I can boot into recovery on the bricked phone. However, it is stock recovery, and I have yet to find a twrp or cwm for the phone (I am currently looking into making my own or using one for a different phone with the same chipset).
Does anyone know how I can unbrick this phone or how I can create a bootable sd card so I can start up the phone and try to fix what's broken?
Thanks!
Are you rooted? Does adb detect the device? If so, I can probably help you fix it easily.
Sent from my XT1609 using Tapatalk
RealWelder said:
Are you rooted? Does adb detect the device? If so, I can probably help you fix it easily.
Sent from my XT1609 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. Yes I am rooted. I have not been able to get the bricked phone recognized by adb yet. I have tried to connect while in recovery with no success. When regularly booting (such that it goes to black screen as stated), my computer (Windows) makes the "usb device plugged in" beep sound, but nothing comes up in explorer and adb does not recognize anything when I use 'adb devices'. I am not sure if my device has a download mode; that (I feel like) is my last hope if I can't reinstall my partitions with an SD card or something.
Hey,
I'm quite new with all this stuff and I just got into some problem. I wiped everything in recovery mode using twrp, cache and internal memory etc (dont ask me why). Anyway, my phone seem to be stuck on a booting loop since I can't enter recovery because twrp fail to load up correctly. You can see where it gets stuck in the image I attached.
Someone know what's wrong and if it's possible to fix somehow?
Thanks :fingers-crossed:
Okay, it seems like I managed to fix it myself. I used adb and fastboot to install everything as stock.
https://developers.google.com/android/images
However I'm not sure about the USB debugging part, how do I enable that if there is no os installed? Do I even need it enabled when I use fastboot?
Hi there! I'm hoping someone on XDA Developers can help me sort out a root gone-wrong.
I did my best to follow the guide on XDA. I have an Umidigi A9 Pro with 6gb ram. I was successfully able to get the android tools on PC and was able to unlock the bootloader. I went to the Umidigi website to get the ROM. I think I *might* have grabbed the wrong one. Once I got this zip from the Umidigi website, I unzipped the folder and copied the boot.img that was in that root folder to the device. I then went into Magisk and patched the img. I then copied the patched img to my PC then use the commands on the XDA guide to flash the image to the device, the flash was successful (I think). However the device is now stuck in a boot loop. The device displays the Umidigi OEM logo and the android logo; underneath it says in small text:
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
after 5 seconds the screen goes black and then comes back with the same screen. This happens continuously. I have tried holding the volume down, the power button, and several combinations of volume up, down, and power. Holding all buttons down makes the screen stay black, however while plugged into the PC the PC still makes the device connected and disconnected sounds off and on. Whenever I release the buttons, it goes right back to the loop. Windows PC plays the device connected and disconnected sound on and off. The command prompt is not able to affect the device. When I run "adb devices" it doesn't display the phone so it doesn't seem that windows is detecting the device.
ROM: https://community.umidigi.com/forum.php?mod=viewthread&tid=22236&extra=page=1
https://www.umidigi.com/page-Download.html
I'm hoping for some help on this one
Thank you!
It should be obvious that when being in a bootloop ADB cannot function: On Android side the ADB daemon gets started and after seconds closed, and this over and over again.
In the simplest explanation, a bootloop describes when your phone is stuck in a loop of rebooting. The term "bootloop" is just a more common way of saying "reboot loop."
Curious if you ever managed to get this figured out? I'm in essentially the same situation, though I was not attempting to flash a ROM. I successfully managed to get TWRP 3.5.2 installed and then I was trying to get Magisk installed.
My phone data was wiped, which honestly I didn't care about, however I must have done something wrong with the Magisk installation as now I have the rebooting issue.
I'm able to use ADB and have been trying to push a ROM to the sdcard folder of the internal storage. ADB says the file has successfully completed, but nothing is on the phone. I fixed the issue of the storage showing up as 0MB by changing from EX4 to EX2 and then changed it back to 4.
Really unsure of how to flash a ROM if I can't get the file to pushed to the phones internal memory though.
Zeidwinder said:
Curious if you ever managed to get this figured out? I'm in essentially the same situation, though I was not attempting to flash a ROM. I successfully managed to get TWRP 3.5.2 installed and then I was trying to get Magisk installed.
My phone data was wiped, which honestly I didn't care about, however I must have done something wrong with the Magisk installation as now I have the rebooting issue.
I'm able to use ADB and have been trying to push a ROM to the sdcard folder of the internal storage. ADB says the file has successfully completed, but nothing is on the phone. I fixed the issue of the storage showing up as 0MB by changing from EX4 to EX2 and then changed it back to 4.
Really unsure of how to flash a ROM if I can't get the file to pushed to the phones internal memory though.
Click to expand...
Click to collapse
I honestly haven't messed with it since. It was a very cheap extra android phone I had laying around. Once it got messed up I pretty much just put it in a drawer and said "maybe another day"