I Was attempting to install a new build.prop on my samsung admire metropcs phone. I obviously didn't follow instructions correctly and the new build.prop I installed has caused my phone to lock up after initial boot. It will only get to the Hello, Hello ,Hello, Metro Pcs splash screen with the audio but then the screen goes black and the phone starts vibrating and won't go any further. I've tried to see if the hold power, back and lower sound steps would help. They don't I get the screen with the options to reboot, wipe and reload stock start, etc. but none of the options helps. The phone is rooted and has the Admiral Beast theme installed. I was trying to boost speed when I screwed up. Can anyone offer any help? I cannot get the phone to open the drive when using the usb cable to the computer so I could fix the file in system.
Related
In December of last year, I had my friend root and install CyanogenMod onto my Mytouch 3G Slide. Everything was working fine until I wanted to update my ROM and tried to boot my phone into recovery mode to make a NANDroid backup. A screen with a picture of a phone and a red exclamation point inside a triangle would appear, and I'd have to pull the battery out to restart the phone.
Then, I tried to access the bootloader by holding the volume down and power buttons. After some loading, it asked me if I wanted to update. Not knowing what it was asking, I said no, and tried to access the actual recovery menu, but the same screen showed up.
I tried again, this time accepting the update. Now, when my phone boots, the stock mytouch splash screen appears and the phone does nothing from there.
At this point, what would be the best solution? Is my phone just bricked, or is there a way to restore it to the stock firmware/recover CyanogenMod?
EDIT: For clarification, I can still access the bootloader, where I have four options: Fastboot, Recovery (See problem above), Clear Storage, and Simlock.
EDIT 2: I left it on the splash screen and discovered that it seems to have just thrown my phone into a stock factory state, running 2.1-update 1. Not sure if it's still rooted.
Hi Guys,
I have tried to install a CM mod on my Motorola Defy as illustrated here. The problem is that despite the phone had been rooted, I had some problems with ClockWorkMod and rebooted my phone in recovery mode using the application that ships with the phone. I did remove the Cache and Factory settings and ran the zip file.
The problem is that upon restart, the phone kept rebooting itself, that is, I kept seeing the Motorola logo for a couple of minutes, and then, the phone reboots and the process is repeated.
Now, out of the blue, the phone is not even turning on. What I have is a small white light that turns on whenever I connect the phone to a laptop via usb. Any idea on how I can get the phone working? At the moment I do not really care about what OS version, as long as it runs.
Thanks in advance
Edit: There seems to have been an issue with the battery, I have managed to load up the phone to recovery mode. Can anyone show me how can I install a fresh Operating System? I seem to only have access to the phone's boot up screen. Also, the laptop does not seem to be able to connect to the phone via usb.
Hi,
I have a Galaxy S (I900) which I attempted to root yesterday. Stupidly, I used the wrong root kit and when I rebooted I was left hanging on the startup screen with the network logo (orange) flashing.
My boot menu was disabled for some reason but I could however access download mode - which I did. Whilst trying to rectify this I downloaded a couple of kernels that were recommended to fix the problem but to no avail.
Finally, running out of options I downloaded Odin3Execution v1.00 One-Click downloader, connected the phone and clicked start (which was also recommended to me). This completed successfully but when the phone tried to re-boot I was left with a flashing AT&T logo (which is not my carrier) and download mode no longer executes when pressing the buttons. Also, when I plug the charger in the screen just goes black.
I realise that this is my own stupid fault but i'd really appreciate some help on the matter.
(would a USB jig get me back into download mode?)
Hi guys,
New to flashing custom ROMS. Good news - flashed CM12, then LiquidSmooth and I'm learning a lot after having soft bricked my phone a few times. Bad news - After trying to get back to Stock I'm not able to get out of this LG Logo bootloop. The LG logo will flash, screen will go black and the whole process starts again. It doesn’t progress past that. I'm unable to get to TWRP recovery or download mode.
My idiotic move:
Iffy stability with camera and mobile data with CM and LiquidSmooth. Decided to go back to Stock.
I flashed my nandroid backup, which I believe led to a bootloop (can’t remember). Was able to boot to TWRP and get back to CM12. Then I had the genius idea of using AutoREC and selecting the “Go Back to Stock” option. Yes, it’s already sounding like a bad, and nonsensical idea as I say it now. Can't remember exactly what I did next - I either flashed my nandroid backup or did a factory reset through CM settings. Threw me into this bootloop.
The details:
Model - D800 - Am sure of this.
Stock software before flashing CM12 was Lollipop 5.0.2 via OTA.
TWRP Recovery 2.8x something or other. Used AutoRec to flash.
I can interrupt the bootloop and access Factory Hard Reset through Power + Volume Down
Had to go to JB Bootloader in order to Flash ROMs. Errors returned otherwise.
Roadblocks:
No download mode. Holding Volume Up & Inserting USB cable doesn't work. Although am able to get bootloop to include a blank screen with red flashing LED through this method from time to time.
Phone boots up, and goes directly into bootloop when plugging USB cable into phone. This happens both when plugging into a wall charger or into a computer. I think this is probably the biggest pain and is holding up things from progressing. Can turn off phone by holding down power for a few seconds, BUT if the phone is plugged in it will continue to boot on its own.
Phone not recognized by computer & ADB However, was at times able to get Device Manager to recognize the phone as an "Unknown Device" after going to the Factory Hard Reset screen. This is no longer working after trying different drivers. I’ve went through LG Mobile Universal Driver as well as the Koush driver.
Going through Factory Hard Reset via hardware buttons only throws phone back into BootLoop
Can’t boot into TWRP
Any insight or help guys? Thanks in advance. I think getting into Download Mode will be a quiet victory. I’d like to try to use Supersports guide once I get there to go back to stock.
Hey guys, I've got a Kyocera Brigadier and I decided to change the runtime from Dalvik to ART. Now the phone is stuck on loadscreen and I don't know how to fix it. The phone is rooted using the KingRoot app, but I don't know if that would help in any way.
Please help me guys!
Similar Issue
I am have a very similar issue, I also rooted my Brigadier with Kingroot and all went well. However, I attempted to flash the Xposed Framework onto it using Flashify. After doing such it got stuck in a bootloop, I was able to fix that problem by booting into fastboot mode and using fastboot to push stock firmware back onto my device. However now I have an even bigger problem where my phone boots up to the Powered by Android screen and then to the Kyocera screen, however instead of continuing to boot to the Verizon Wireless screen and then into the phone, it gets stuck at a black screen. I have tried waiting for hours and nothing at all happens, also I can no longer seem to boot into fastboot mode or in other words the Powered by Android screen with the little 1 in the top left corner of the screen. Fastboot nor ADB recognizes the device when plugged into my computer, as neither list anything when ran. Please help, I don't want to have to pay and end up sending my phone into Verizon to be unbricked.
Ornias Abezethibou said:
I am have a very similar issue, I also rooted my Brigadier with Kingroot and all went well. However, I attempted to flash the Xposed Framework onto it using Flashify. After doing such it got stuck in a bootloop, I was able to fix that problem by booting into fastboot mode and using fastboot to push stock firmware back onto my device. However now I have an even bigger problem where my phone boots up to the Powered by Android screen and then to the Kyocera screen, however instead of continuing to boot to the Verizon Wireless screen and then into the phone, it gets stuck at a black screen. I have tried waiting for hours and nothing at all happens, also I can no longer seem to boot into fastboot mode or in other words the Powered by Android screen with the little 1 in the top left corner of the screen. Fastboot nor ADB recognizes the device when plugged into my computer, as neither list anything when ran. Please help, I don't want to have to pay and end up sending my phone into Verizon to be unbricked.
Click to expand...
Click to collapse
I have the same problem. I bought a new a Brigadier that was on 4.4.2. I rooted with Kingroot ran update and now my phone will not boot past Kyocera screen. It goes black with the back light on. Did factory wipe and still nothing. I am shocked that KK has killed yet another phone of mine. I very much dislike KK ROM. What did you find out?