Hello. I decided to start a new thread. I have a Moonshine s-off phone. Recently I reset the phone put stock recovery on it and ran the newest RUU. It worked I got the new software[emoji3] . Then I unlocked the phone using the HTCDev method and my old unlock key, everything worked, when I went into BOOTLOADER phone said TAMPERED UNLOCKED S-OFF.
The only thing missing is my camera. Sometimes it turns on, but very rarely ( maybe 1/200 tries ). It tells me Unable To Start The Camera.
I think it's a software glitch, as with previous version of Android I had no issues. Also with the new OS the flash is BUSY sometimes. When I want to use a flashlight phone tells me PHONE SCREEN WILL BE USED FOR ILLUMINATION SINCE THE FLASH IS IN USE BY OTHER APP. There is no other app running...
I tried flashing TWRP but fastboot just hangs, I left it on for 3 hours and it never finished. I tried using the SD IMG method. It goes thru, tells me to reboot. When I do I'm on the same stock recovery...
I have backups of my phone. But they are all done with TWRP and I can't install it. I tried CWM as well, same result, timeout.
I might try running a lower version RUU and see if that fixes all...
[emoji27] [emoji23] [emoji24]
I have found a temp solution. If I disable my Phone Data and Location for a few minutes, then enable just the Phone Data camera will start. I don't know the time you need to wait... 2-5 minutes. I tried just putting the phone in Airplane mode but that did not make my camera. App start...
My Flash started working again. I have updated all my Apps, maybe that helped...
Related
Hello everyone!
I'm having some trouble right now, My phone was updated with the AT&T update because my phone prompted me about the update. I updated my phone and successfully updated the phone. I installed all of my backup apps from Titanium back, but when I restarted my phone after the apps were installed my phone booted up but said that NFC stopped working dailer stopped working,basically everything was not working - i couldnt even do anything with the phone. What I did was I tried doing a factory reset via TWRP but it didn't work. I also cleared the Dalvik and Cache but didnt work either.
I locked my bootloader and thought I would flash the RUU for my device. everything went fine untill the RUU displayed an "unknown bootloader version". I tried downloading the RUU again but it didnt seem to work.
I installed Elegancia through ADB install went through perfectly untill I reboot into the phone the HTC screen with the white background does not go anywhere. I occasionally get a pop up that says "stopped responding would you like to stop the program". I downloaded the Mongoose custom rom for my phone, again install went fine no problems. but once again when I boot into the phone I still get stuck on the HTC white background. This time the phone has a black screen with the status bar with the icons of the battery time and an x on the signal icon then the phone restarts.
What is going on with my phone? How can I reinstall an OS and get my phone working again?
any help would be greatly appreciated!
Since you have done the update, you will have to flash the ROM of this thread, everything you need to know is in this post.
Lucky Thirteen said:
Since you have done the update, you will have to flash the ROM of this thread, everything you need to know is in this post.
Click to expand...
Click to collapse
Thank you so much it worked perfectly!!
Any reason why the other ROMS didn't work?
Glad it work!
Please edit your OP title and write : [Solved] Any way to bypass HTC setup screen? Stuck on HTC logo all white.
First let me talk about how I got into this mess. I had used the thunderbolt as my phone previously and had rooted it, installing custom roms often. After getting a new phone, I decided to unroot my thunderbolt and give it to a family member. At first, everything was working fine; I had no problems unrooting the phone. However, a month or so later it started having problems.
Upon booting, the phone goes straight to hboot where it displays a security warning. But this only happens occasionally. Sometimes it will actually boot but take about 20+ minutes to start up where it come to the homescreen with a solid black background, soon to freeze and turn off.
I have tried fixing the phone based off methods others used to fix similar issues, but to no avail. For example, I have tried flashing the 2.11.605.19 firmware through hboot only to have the same problems occur. Perhaps I did not use the right version. Do you guys have any idea on how I can fix this? Could flashing an ruu (if there is one) for the latest ics build solve this?
When I try to unlock the bootloader through htcdev, everything works fine up until the confirmation screen on my phone asking if I want to unlock the bootloader or not. For some reason, the power button won't work to press yes. It does work normally for saying no and everything else though. I have tried using the adb to force it to use the power button, but in its "unlock the bootloader" state it isnt connected.
some relevant info for the phone:
hboot version - 1.05.0000
radio - 1.49.00.0406w_1 - should be the radio from 2.11.605.19
So I'm basically making this a "fix my problems" thread, because I've got a lot of problems, and no solutions.
My phone is rooted running Sense 6 on Android 4.4.2, and ever since I rooted it about a month ago it's been a little... quirky.
For one thing, the stock weather app is no longer animated for me. The scene changes accordingly, but is completely static and doesn't play any sound effects even when the option is checked on. I texted a friend who has the same phone and also has it rooted, and he said his is animated and works just fine. It's more of a minor inconvenience than anything and doesn't bug me too much, but it'd be nice to have it function properly.
A more problematic... problem is that I'm no longer receiving push notifications for Twitter, Snapchat or Instagram in the notification bar. I looked it up and tried revoking access to the Android Twitter app from the web and logging in again, and nothing happened. I'd like to think it's a bug in the newest versions of the apps, but I didn't see any mention of notification issues in the Play Store reviews and the fact that all three stopped working simultaneously seems abnormal to me.
My phone also seems to have picked up an annoying habit of getting itself stuck in a bootloop whenever I reboot the phone. Once it powers on, it will then proceed to reboot itself about four to five times and then continue to function like normal afterwards. The other night it did the same thing, except it rebooted about seven or eight times and THEN stopped.
I have a sneaking suspicion that all of this has something to do with SuperSU. Shortly after I rooted the phone, the app prompted me to update the binary, which I attempted to do using the "update with TWRP/SCM" option that, according to the app, is recommended for HTC devices. My phone then had one of its bootloop episodes, lost root access, and has been doing it ever since. A few days ago I downloaded the latest SuperSU update from the web, transferred it to my phone via USB and flashed it with TWRP. When I booted it back up, SuperSU had vanished from the phone entirely. I reinstalled it from the Play Store and that seemed to do the trick at the time, but now I've suddenly lost root access after not even having touched SuperSU at all. I'm wondering if this affects apps that previously had superuser permissions, such as Battery Doctor. It had been stable until shortly after the root, after which it started behaving erractically - sometimes it works, sometimes opening it from the app drawer will pull up a black screen, and in most cases the widget either doesn't work at all, is extremely delayed, or will simply give the "Battery Doctor has been given superuser permissions for an interactive shell" message and then do nothing. So my question is, are all these problems being caused by a conflicting Play Store and binary version? And if so, how do I update it without screwing my phone up even further?
JayWulf said:
So I'm basically making this a "fix my problems" thread, because I've got a lot of problems, and no solutions.
My phone is rooted running Sense 6 on Android 4.4.2, and ever since I rooted it about a month ago it's been a little... quirky.
For one thing, the stock weather app is no longer animated for me. The scene changes accordingly, but is completely static and doesn't play any sound effects even when the option is checked on. I texted a friend who has the same phone and also has it rooted, and he said his is animated and works just fine. It's more of a minor inconvenience than anything and doesn't bug me too much, but it'd be nice to have it function properly.
A more problematic... problem is that I'm no longer receiving push notifications for Twitter, Snapchat or Instagram in the notification bar. I looked it up and tried revoking access to the Android Twitter app from the web and logging in again, and nothing happened. I'd like to think it's a bug in the newest versions of the apps, but I didn't see any mention of notification issues in the Play Store reviews and the fact that all three stopped working simultaneously seems abnormal to me.
My phone also seems to have picked up an annoying habit of getting itself stuck in a bootloop whenever I reboot the phone. Once it powers on, it will then proceed to reboot itself about four to five times and then continue to function like normal afterwards. The other night it did the same thing, except it rebooted about seven or eight times and THEN stopped.
I have a sneaking suspicion that all of this has something to do with SuperSU. Shortly after I rooted the phone, the app prompted me to update the binary, which I attempted to do using the "update with TWRP/SCM" option that, according to the app, is recommended for HTC devices. My phone then had one of its bootloop episodes, lost root access, and has been doing it ever since. A few days ago I downloaded the latest SuperSU update from the web, transferred it to my phone via USB and flashed it with TWRP. When I booted it back up, SuperSU had vanished from the phone entirely. I reinstalled it from the Play Store and that seemed to do the trick at the time, but now I've suddenly lost root access after not even having touched SuperSU at all. I'm wondering if this affects apps that previously had superuser permissions, such as Battery Doctor. It had been stable until shortly after the root, after which it started behaving erractically - sometimes it works, sometimes opening it from the app drawer will pull up a black screen, and in most cases the widget either doesn't work at all, is extremely delayed, or will simply give the "Battery Doctor has been given superuser permissions for an interactive shell" message and then do nothing. So my question is, are all these problems being caused by a conflicting Play Store and binary version? And if so, how do I update it without screwing my phone up even further?
Click to expand...
Click to collapse
You need to start over from scratch
post your fastboot getvar all (minus you serial.no and IMEI)
Most likely your using AT&T so if you have s-off you can flash these two and get back two stock. take the OTA Update then re flash recovery and root.
flash this first
http://fs1.d-h.st/download/00101/a1w/4.18.502.7 Custom Firmware.zip
fastboot oem rebootRUU
fastboot flash zip 4.18.502.7 Custom Firmware.zip
fastboot flash zip 4.18.502.7 Custom Firmware.zip
fastboot reboot bootloader
now stay on the bootloader
and run this RUU from your PC > http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
Take the Over the air update and your all set to start rooting again.
clsA said:
post your fastboot getvar all (minus you serial.no and IMEI)
Click to expand...
Click to collapse
What is this, and how do I do it?
JayWulf said:
What is this, and how do I do it?
Click to expand...
Click to collapse
go to the folder where fastboot and adb are
open a command window (right click / command prompt here)
with the phone plugged into the PC
Type fastboot getvar all
it will output all the specs for your phone
remove the serial no and IMEI when posting it
what if your s-on
I'm having all the exact same problems except I'm 4.3 and s-on. Help please!
Gonna kinda bump this thread a bit because I've got another question - what about the "full unroot" option within SuperSU? Will this help the situation at all, or make it worse?
I have a sprint note 4. I don't have it activated currently and use it as a tablet of sorts. Recently it's been giving me problems and I've wanted to break it. I got it about 2 years ago, and since then I rooted it, then installed twrp recovery, then flashed custom software. The software I used was called Dr.Ketans I believe, it combined the note 5 and s6 edge plus softwares. It started to crash occasionally so I installed cyanogenmod onto it. It worked for a bit, but now when Turing the device on, it takes like 10-15 minutes to boot up. And it only stays on for 5 minutes before it crashes and freezes. When it does that, the only way I can boot it up again is take the batter out and put it back in a few times because sometimes I get an error message. The error message barely happens but it says something along the line of "cant boot up". If I use twrp, my phone doesn't freeze. I've tried reinstalling the software, I've tried formatting the entire phone and refreshing. Nothing seems to work. I've even tried changing my kernel but I'm not entirely sure what it is, and how it affects the phone. I'm not the smartest with phones, but I'm good with following directions and googling. If anybody can help me I'd greatly appreciate it cause I've been dealing with this issue for 3 months.
Reinstall the original firmware and make sure it doesn't freeze / crash with it and then you can reinstall the custom software. Make sure that you have the required recovery, bootloader, and baseband version to run the newer custom roms. The requirements should be located in the OP.
I appreciate the response. I will try this as soon as possible. Should i use odin to flash or would it be possible to use twrp recovery? Also, what do you mean when you say the requirements are in the OP?
You should use Odin to recover to make sure you have a fresh start.
The requirements of the rom you pick afterwards should be in the OP.
Ive had this i605 since a few months after it came out, brand new. rooted it within 5 min as i got home. only issue i've had with it was the power button and usb port didn't work but i replaced those.
2 nights ago, running cm13 last official version. was just on facebook and i got the boot logo. it's happened before so i didnt think anything of it. except this time, it was boot looping the first logo. ok, something happened to OS, so i went into recovery, erased all but external SD card and installed slimkat, this time it would get to the slimkat logo about 2% and reboot. fine.. back to stock and reroot. INstalled MC3 stock. when it came back up and it did, it hangs on verizon activation until wifi only.. great. go to status, baseband unknown. no radio, bluetooth and wifi still work, but doesn't detect simcard. this phone is my only internet connection as i tether. trying to root with casual and now, even though i can go in download mode and usb is found and i can flash with odin stock rom all day, once i get to android home screen, my computer is not seeing the USB file system, mtp, but it is charging. anyone had this happen before?
this phone has never had an OTA update, was on 4.1.2 when i got it
Update: Loaded back fresh MC3 stock build to start over again, saw a post somewhere about accessing hidden menu,
Go to Phone Dialer and type *#22745927
Enable Hidden Menu
Go to Phone Dialer and type *#7284#
Set USB to PDA, save and exit, rebooted back into android and was able to get USB access for CASUAL to root. FInally got it rooted, in TWRP newest version
Funny thing when it booted back into android before CASUAL root, it showed SDCrd and Internel memory. SDCArd was fine, but internal memory was -1636237227 so i'm thinking that memory is a problem, because when i reloaded stock mc3, it would never boot up after odin, i had to go into recovery and do a factory reset and then it would boot into Android, but no USB access, could get USB access in download mode, but not in recovery or android. I just found it weird.
Now, when i load my custom rom, it just hangs at the ROMs loading screen and just stays there. I'm really thinking this is a memory problem and i'm really upset about it. I'm wondering if anyone knows how to just reset the memory, without messing with EFS.