My phone froze during the soff procedure. Following the direction I excited bearcontrol and restarted it in hopes that it would try to continue from where it left off. Not the case.
I'm trying to adb amon ra now but my phone isn't showing up with ADB. It automatically boots to fastboot everytime I turn it on. I remember there was a way that I could flash amon without using fastboot flash recovery.... but I can't seem to find it.
My memory card needed to be formatted when I tried to add ph98img through a card reader. I followed the directions but for some reason it only reformatted at 128kb. This isn't big enough to hold anything.
phone won't boot passed fastboot at this point.
Suggestions?
flash the SD card in a pc untill it gets formated... also did u get s-off in your Hboot?
no fastboot
Try to replace your boot image with a PH98IMG file you can find here on xda.
That will allow you to boot your phone back to the rom you had before.
I'm having this exact problem, but further cannot access ANYTHING or charge
my phone with USB cable. Am desperate to flash something to get access to USB
again.
I tried reformatting the card in another phone but it's still formats to 128kb. I picked up a new sd card and will try that when I get home tonight.
No I did not get s-off...yet
memory card error
Your sdCard was partitioned to a small readable portion and the rest unavailable when trying the S-0ff.
You can put it into a computer and use a partitioning program to get
it all back. I just used a freeware program called Mini Tool Partition Wizard Home Edition, saw many others while searching.
I am still S-0n and HTC unlocked but can't run any PH98IMG's other than the
boot install that allowed the phone to start again. Also can't get into recovery or install another recovery. It just ignores the PH98IMG in hboot.
New memory card did the trick. I'm back up and running.
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 just downgraded my phone from hboot 1.58 to 1.40. I put the PG86IMG_1.40hboot on my sd card and rebooted into the bootloader and it started applying the PG86IMG update (downgrade?) It worked, my hboot is now 1.40 but, when the phone reboots it is now in a bootloop. So here is where I'm stuck, every time I go into the bootloader it automatically starts applying the PG86IMG that I used before I can access my recovery to delete the file. Is there a way I can get into recovery so I can delete this or any other work around for me to use?
Thanks
If you have adb setup on your pc it is easy.
With phone powered off connect usb cable to pc. Charge light will come one for a moment then go out and come back on. Now use this command on your pc. Adb reboot recovery. You will boot directly into recovery.
Without adb you will need to use a card reader on a pc to remove the file.
Sent from my PC36100 using xda app-developers app
Thank you so much.
I was running CM12 and everything was fine. I received a notification to update to CM 13 and I selected yes. It installed OK, but no GAPPS. I tried everything I could think of to install GAPPS, and kept getting errors. IN my frustrated efforts, something happened to my TWRP and now I only have CM Recovery. I'm trying to reinstall TWRP but my phone is being recognized as a "Marshall London Bootloader Interface" ONLY when in the Fastboot and Recovery mode. I have Huawei Hisuite installed and it recognizes the phone fine when powered on, but as soon as I boot into Fastboot and Rescue mode, it reverts to the MLB interface. I am at my wits end as to how to get my PC to recognize my phone properly when in Fastboot and recovery. I did try removing and reinstalling drivers when in Fastboot, but the Marshall Interface keeps on getting inserted. Any suggestions?????? (I also seem to have erased the SD card that has my original system backup files on it. I tried to flash several downloaded stock ROMs using CM recovery, but they all error out. )
I was finally able to re load TWRP using the Huawei Hi Suite. I flashed Carbon ROM and GAPPS and everything seems to be OK but I still cannot use ADB because the phone is recognized by Windows as a Marshall device ONLY when in bootloader mode and ADB does not find the device. When I connect normally it is recognized as a Mate 2 and it connects normally to Hi Suite. I have no idea what could be wrong, but I have read of other people who have this mysterious "Marshall" device show only up when in bootloader mode. Anyone have any ideas????? Can I go back to stock from here if I don't have a saved recovery image to see if I can fix this???
I have no idea what Marshall device means. Is it possible to place the stock 5.1 ROM on a blank micro SD card and follow the flashing instructions? (boot to download mode or whatever it's called)
ScoobSTi said:
I have no idea what Marshall device means. Is it possible to place the stock 5.1 ROM on a blank micro SD card and follow the flashing instructions? (boot to download mode or whatever it's called)
Click to expand...
Click to collapse
I explained what "Marshall Device" is in the first post. I ended up going back to stock (322) and loosing root. I then updated to 5.1 using the SD card. Everything seems to be working OK. Maybe I'll root again and start over when I have more time.
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.
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"