I have an AT&T HTC One I bought off swappa. It was fully converted to the Google Play Edition. About a week ago I clicked install update when it popped up (dumb probably). It rebooted and showed a "no command" screen with a keeled over android guy with his stomach open and a caution sign there.
I took it to Seattle Android Guy who tried to get it all stock by locking the bootloader and turning s-on, but it wouldn't take it because the bootloader was still the dark bootloader. I took it back home and managed to get TWRP Recovery on it, but it won't take any of the roms I try to flash over to it or install via TWRP. I am pretty new to everything so if you have a solution, the more detailed the better. I've read that it's possible it is bricked, but I really want to keep looking for a solution. I paid almost $400 for this device and only got a couple weeks use out of it. Any suggestions, ideas, or help would be greatly appreciated.
Thanks.
Related
Some of you might have seen my earlier thread, my ReZound is rooted. HTC sent out the ICS update my phone attempted to install it and afterwards it would not advance past the white HTC screen. After many hours of playing around with it (being semi-noobish to all things rooting, but decently knowledable with technology) I realized that on the H-boot screen it was telling me that the Image was missing. I assumed that the HTC update deleted it? After thinking about it, I thought that maybe installing a custom ROM would fix this, so I grabbed Scotts Clean ROM. Sure enough I did and I was finally able to advance past the white HTC screen. It looks as if everything is working fine with the phone now EXCEPT I have no data and no calling connection. Im assuming that my phone is just that messed up from the attempted upgrade this morning that im missing files needed for the connection.
My next thought was to just say heck with it and do a factory reset hoping to get back to a bone stock phone that at least functioned, but when I try the factory reset it doesnt work....
Any ideas of what I should do next? Ive spent 5-6 hrs trying to fix this phone today, I really hope to get something figured out. Thank you everyone for your help!
EDIT: I feel like an idiot... Because of putting the battery in and out for resets I left the back off the phone. I now have service. Main issue now is that when I try to call out, as soon as I type a number on the dialer it freezes up and restarts itself....
The phone still tries to look for the old image on the restart and gives me issues every time on startup still also. Id like to be able to get this back to not needing a ROM....
If it were me, I would download the official RUU for ICS found here: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/ IIRC, mirror #3 was the fastest. Then follow the directions from that site:
After downloading the file, rename it to "PH98IMG.zip" (no quotes)
Place the renamed file onto the root of the SD Card
Power down your device
Reboot into the bootloader by holding VOL DOWN + Power
The flashing process should begin automatically
Let the device reboot, and you should be done.
That will get you up and running. Then you can go about rooting it again if you like.
So long story short I have this thunderbolt that is not working any longer. All of this happened over a year ago so I am vague on what I did to get the phone in its currently ruined state. It was rooted with the stock image and after trying to put a CM rom on it that didn't work I mistakenly booted into the phones recovery instead of clock work.
I now get a security warning and it is now s-on. If i do a recovery or factory reset it just boots back into the bootloader. Attached is an image of what is current on the screen when I power it on. I can't get ADB working on this pc but my spare rig has it working in OSX. ADB does not display the device. I have a way to get files onto the sd card but I am still kinda new to all of this stuff and just looking for some help. So where do I proceed from here?
I am going out of my mind.
So the phone just literally booted into my rooted rom. So now the question is, how do I get rid of the security warning and get s-off permanently?
At my end.
After a long day of trying to fix this thing and crawling all over the internet reading different posts I officially don't have a damn clue as to how to fix this. I am pretty sure the bootloader is corrupted and seeing as the phone is so old now it's really hard to find working links to downloads for this device.
So I've seen this question covered a few times but not sure if my situation is the same as the ones that have been answered prior.
I have a 1-1/2 year old S4 that I rooted when I received it, using whatever flavor of the day rooting method was out there. I have never used any kind of custom firmware with this device, just rooted and disabled some of the built in features like jedi hand wave mode, follow my eyes, etc. (yeah I know those aren't the real names)
Over the past few days I've been noticing apps not being able to open, the screen would go black for a second like the app was launching and then it would return to the home screen. Also a few times the notification bar would flicker while trying to open an app. So I decided to reboot today and now it is stuck at the verizon boot screen.
I've tried all of these options:
Pull battery for 30 sec, remove and replace sim card, replace battery boot.
go into recovery mode and wipe cache
go into recovery and do factory reset
Of course none of these options worked, which is why this thread exists.
now the next option I'm seeing when I'm looking for an answer is either
replace/update the firmware
return to verizon
I guess I'm wondering if the first option is even available to me since I never flashed anything custom before? If it is, I'm sure there's a wonderful thread here that would walk me through the process, if anyone would be so kind as to point me there. I'm just a little confused over what's available in my particular flavor of firmware.
Or, is there a verizon flavor that I could update to and be able to root as well? I remember when I originally rooted it was suggested to keep the older version so you wouldn't get locked in to not being able to do any custom stuff, but not sure if that's been overcome since. I don't need anything fancy, just a rooted phone works for me.
If updating is not an available option for me, is a verizon return my next step? And if so, can/should I remove signs of rooting before sending it in?
Hey lovely ladies and gents,
So here is the situation: I have an LG Optimus l70 MS323, which until yesterday was with a stock ROM. I banged my head against the wall, trying desperately to follow a guide and root it, along with trying to unlock the bootloader until I watched a video (in Spanish. Thank you high school spanish!) which used flashify to flash a CWM and boot to the custom recovery. I loved it, since that meant that I would be able to finally flash an official Cyanogenmod OS. The first ROM that I flashed was cm-13.0-20160121-NIGHTLY-w5.zip, which worked and made me feel SO HAPPY (I almost yelled Eurika for the sake of historical comedy). I then went ahead and installed an Superuser-SU binary update through the CWM recovery because I wanted to keep on having root. Then I installed a nano gapps package for ARM, Android 6.0 with some minor complications (mostly the "Setup Wizard" crashing every 2 seconds). I rewiped and reinstalled Cyanogenmod through CWM, flashed gapps on the same go, and made a little backup through the recovery menu. I booted up successfully to be met with that buttery-smooth GUI of Marshmallow (ugh, so good.) I decided to go ahead and fetch some apps from the Play Store, such as Messenger and ROM manager. I saw that the Cyanogenmod Update Center had pushed out a notification that the newest nightly snapshot is already downloaded and decided "Meh. What new features have been added? Let's reboot and reinstall." At that point it was 4:40am (keep in mind that I've been trying to get the goddamn phone to cooperate since ~10pm) and I noticed that the boot sequence takes up a lot longer and told myself "It's probably taking a bit longer than usual, it's normal." I put the phone next to my head, hoping that it's going to be ready to use in the morning.
Fast forward to 8:07 am. Bootloader is still going, phone is so hot it can cook an egg.
GNAAAAAAAAAAAAAAAAAAAHHHH. WHY YOU GOTTA DO DIS TO ME PHONE?!??! WHY!?!
SO, the CURRENT situation:
1. Whenever I press the power button, it starts off normally. According to my definition of bootloop, it's stuck in a bootloop.
After hours of staring that goddamn cyanogenmod mascot do you realize that it's going to boot itself into the booting oblivion.
2. I don't have access to CWM. I have tried holding down the power buttons with godknowswhat combinations (I like to call them the Naruto Jutsu of pure despair). Maybe I should hold the buttons for 2 milliseconds longer and it might work. *Sigh*
3. I don't think that I can use fastbood or adb. My computer doesn't see the phone. (GNAAHHAHASDJFLSKDHFSLJHLKJ.)
4. I am totally clueless about what I should do or try. I've basically softbricked my phone and don't know how to unbrick it.
So, now that you see that saying that I'm frustrated is truly an understatement, what do you suggest I do?
In advance, I'd like to thank you SO MUCH for even giving a sh!t about my problem.
Other misc info: I have a 32GB SD card on which I have all the different tools I have used throughout this journey.
I am willing to have it back on stock ROM. My biggest goal is to somehow boot into CWM recovery. From there on, I will be able to deal with it. Until I come back to this forum, begging for mercy.
Have u tried using LG suite or LGUP u need to go to LG 's firmware page I'm not sure about this phone but it worked w my k7 about 100 times also helped unlock it. Check out the LG k7 forum lots of guys on there that use the lgup program and can help
So I admit I am an idiot and did this to myself. I installed the latest FireOS OTA through TWRP then thought to keep TWRP I would install it before I rebooted. I know I probably should have read threads about keeping root and the horribleness of 5.6.0.1 but I did not. So I can boot into the OS and I can boot to bootloader but I have no recovery at all. Any one know how to recover from this? Found out the unbrick method I have used before does not work. Fastboot give me an error about locked hw.
Been working on this anyone know or have a fastboot zip or image. I am getting a errors trying to flash the amazon bin with fastboot.
I know I am the only one posting here. I read through a bunch of threads that seem to be people in the same issue. I have now managed to get it stuck in demo mode. I also cannot seem to accomplish much from fastboot because I get a locked hw error. Bought a couple for parts HD6s off ebay. So hopefully I can make something work and get at least one working tablet. This has really put a damper on trying to create a device tree to try and build cm12.
Closer to being a brick. Some how I managed to have root in adb and managed to wipe all. Which I guess really meant all. Now all I get is the amazon logo. No desktop. No adb. No way to get to fastboot.
So ebay tablets came in, bout a lot that had 2. The one was listed as a demo model, so a simple ;demo in the search and resell the device and viola fully working tablet. It still had 4.1.1 on it so a simple update to 4.5.3, Kingroot, and TWRP install and back on CM11. The second was "black screen" so I assumed bricked as it did not seem to turn on when plugged in, initially. Tried running through unbrick but nothing from ./reader.sh so assumed on newer FireOS that blocked that function. After setting the first up I was rearranging my stack on now 2, what I thought where, badly bricked devices. Hit the power button and booted to lock screen with 7% battery. So I now have an extra HD6 to mess with. Best part is I got both of them for $20 total.