Previously, I had this phone rooted, and running CM12 with an open source gapps setup, with no problems. I also had TWRP installed, and an SD card with a copy of my ROM as I liked it, and my data.
Everything worked, and I was able to update my Android version and expand functionality quite a bit, which was useful while traveling abroad.
The other day however, when seconds before I had been using it as my hotspot, I tripped over the charging cord and dropped the phone quite hard on tile.
It broke into pieces, with the back coming off and the battery coming out.. The display is fine. I thought I killed it entirely, but I took the battery out and left it alone for half a day, and when I came home, I realized that it would:
1. Charge
2. Boot to recovery
3. Boot to download
This gave me some hope.
However, doing anything else would result in a bootloop.
I booted into recovery in preparation to re-flash my rom, and TWRP was not able to mount my SD card, and would not recognize my data there.
Additionally, when I tried to wipe everything but my SD card, TWRP failed to mount all partitions, as if something got corrupted.
When I tried to repair or change the file system type, this too failed. I cannot seem to get TWRP to recognize any storage. It says the phone is empty, with no internal, no external, and no OS.
Just a bunch of red "failed" lines every time I try to do something through the recovery.
I checked my SD card externally using an adapter on my mac, to make sure it was not corrupted. All my data is still there, including the backup of my ROM. However, since the phone will not recognize it, it's useless, and I can't find an Odin flashable .tar version of the CM12 ROM for this phone, plus when I tried to convert a copy to the correct file type, it failed to flash.
I tried to flash a copy of the stock rom (metroPCS version) to begin with, that I had saved on my computer.... which worked before when I messed up my initial flash. This time, It will flash successfully per Odin, but cause a bootloop.
Odin will still recognize my device... but adb from my mac terminal will not recognize it when I have the device connected or I would try to rebuild the file system that way.
I feel like I am going in circles and running out of options, or missing something..(possibly several things) but... I don't want to give up on this phone just yet, even if I had to demote it from daily driver use in the end ... any advice would be appreciated.... Thank you sooooo much!
Edited to add: I got ADB to recognize the device and ran a restore command, based on a file I had locally. This is what happened:
localhost:~ user$ adb restore ~/Downloads/cm-12-20150319-UNOFFICIAL-gardalte.zip
Now unlock your device and confirm the restore operation.
/sbin/sh: /sbin/bu: not found
Also adb remount resulted in a failed output.
Lastly, it appears abd only works in terms of recognizing my device when I am in recovery.
Related
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.
"""I recently updated my TF300T to JellyBean 4.2.1. That worked fine. I then wanted to see if I could root this version. I tried 4-5 different custom recoveries, including multiple TWRP and CWM versions. Although they were able to boot to the custom recovery, they could never mount any of the data on the tablet, so I wasn't able to flash any custom roms or root my device. Anyway, I finally installed the latest CWM for the TF300 on JellyBean (6.0.3.1 or something). I still could not mound any tablet data from the recovery. Although installing any of this on a brand new 4.2.1 was incredibly stupid, it gets worse...
I thought that maybe if I did a "wipe data" on the device I would be able to mount it. I then got stuck in a situation in which the tablet would only boot to CWM recovery. I didn't even press the volume key- it would simply go directly to the recovery. This was useless, to say the least, as I could not flash anything or do anything from this.
I then found a way to actually boot into my transformer- I used my PC and typed "adb reboot-bootloader". This gave me the option to cold boot and get into the tablet like normal. However, any subsequent reboots or power-offs would require PC intervention and a cold boot in order to boot into the tablet. This wasn't convenient, although I admin it is much better than where I am now.
I tried multiple times to flash a new recovery, and the same CWM stays on the system. I cannot for the life of me get this stinkin CWM recovery off my device! I ended up trying to wipe my system again, and now I'm absolutely stuck. I can only boot into recovery if I don't do anything on the PC. I can get into fastboot by using a PC, but that's about it. I can't boot into the system after fastboot, and recovery has no rights to change any files.
I can run commands to write new recovery, system, etc using adb, and it sends the file, "writes" it unrealistically fast, and then just says OK as if it was complete. The screen on the tablet doesn't change at all during this, other than the fact that the blinking box for the Fastboot options becomes solid. I have let it sit there for 10-15 minutes and it simply does nothing. (The last attempt was "fastboot -i 0x0B05 flash system blob" where the blob file was the one from the most recent stock firmware download from ASUS.com.) I then have to manually reboot the tablet using the power button, and the whole cycle starts over again.""" I didn't feel like writing all this out so I'm plagiarizing; kill me if you like. I did exactly what he did and got things working the way he did.
Recently though I wiped my hard drive to start a clean windows 7 from scratch and I can't figure out how to get the drivers installed on my computer. As Asus hasn't published them from what I can find and I haven't gotten the android sdk manager to do anything past flashing cmd prompt for a millionth of a second. I basically just need help with the drivers, so any help would be very appreciated. I haven't found anything so far looking through the forums that has helped by the way. I haven't been able to find any threads with solutions yet...
I used the asus pc sync package for the tf300t from asus's website since the tf300tg did not want to download, in any case that with the new google sdk works for me.
Also I noticed issues using anything but twrp openrecovery-twrp-2.5.0.0-tf300t-4.2.blob when it comes to mounting and backups this is the only one that i tried that worked so far.
Hello, I'm a little bit new to all this, so any help and detailed instructions are very very helpfull.
So I have Gigabyte GSmart Aku A1 device (MediaTek 6589), I don't know if it's bricked or what but apparently is not working quite well.
When I turn on my phone, it just loads and loads and loads and nothing happens (waited for about 4-5 hours), that was starting to happen after I somehow installed CWM on my device with some tutorial, CWM worked for the first time and after next reboot, it disappeared and stock recovery came back (and the problem with infinite loading screen - only showing logo).
I have ADB drivers installed, SDK aswell, tried to put stock firmware (got it from official site) and in like 1/4 of installation it says:
Code:
symlink: some symlinks failed
After that, I tried to install few versions that I downloaded from that official site, but same error again and again. (I tried to install with SD card and with ADB too. ADB is only working when I go to "apply update from ADB" in recovery. I have also used 2 different types of SD cards.)
That didn't worked either, so I got to some russian forum, and using google translator I downloaded 5-6 types of custom ROM's / Firmwares. That didn't worked either, one time when installing one of those ROM's - it said something about signature..
After that I was trying to install those ROM's with ADB and with SD Cards aswell, but turns out that every single time I get error saying: "Installation aborted.".
I have ofcourse tried to wipe data/factory and to wipe cache too, but nothing helps..
Also, when I'm in ADB console, when I type any command besides adb sideload or adb devices, I get error saying: "error: closed". I cant get into fastboot with adb console.
I really don't know what to do anymore, so any help would be very very appreciated. Thank you for your help in advance, if you need any videos, pictures or something, just tell me.
Edit: When I go to "wipe data/factory reset" in recovery, it says: "Mount /data error.".
BUMP!
BUMP^2!
luuksa said:
BUMP^2!
Click to expand...
Click to collapse
i would look for stock rom in form of full mtkdroidtools backup and preloader drivers for your mtk chipset
and flash it using flashtool (it uses preloader[you can determine if it's available/undamaged by turning phone off and opening device manager on pc and plugging phone to pc if there will be a flash in device manager before the charging starts it will flash ])
So, this is my problem: I was using for months now CM13 and TWRP3.0 by EdwinMoq, but the phone suddenly started to drain battery abnormally, I read CM13 was the cause so I installed TWRP 2.7.1.1 to flash Paranoid Android 4.6 BETA. When I wiped partitions to install PA (using TWRP 2.7.1.1), somehow SD Card files were deleted (I didn't select wipe SD Card at any point so I don't know what happened). Then powered off to copy the flashable *.zip again on the SD Card and when I tried to boot recovery, LG Logo appeared but after few seconds phone shutted down (and this happens everytime).
It is a p768 with unlocked bootloader. I can use fastboot just fine, delete partitions, flash them, but I obviously can't flash a system.img via fastboot (it's too big). And I tried flashing different recovery files (TWRP, CWM) and it's exactly the same. I can boot into "S/W Upgrade Mode" too, but when I try to flash any kdz it gets stuck at 15% saying phone is not connected. I tried using another USB port and making Windows install drivers for the device again with no luck.
Drivers are installed correctly (4.0.4 version) and I see phone in the Modems, Ports and USB controllers sections of Device Manager everytime so I don't know what to do. Fastboot is the only thing that's working and I know /system is missing but I can't flash anything.
My issue is kind of like this one BUT, I can boot into S/W Upgrade.
Nevermind, after some quiet crying over the phone I found that my buttons are screwed. I wasn't pressing VolUp right, tricky button. I feel like a retard.
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"