Hi everyone,
So today I came home from a trip as my HTC One S, that for like.. 2 months was on CyanogenMOD 12, was working all perfectly fine, showed up that there's an update available (usual stuff, these updates come often). After it finished downloading the update, it restarted and installed it.. after that the only thing that was showing up was the loading screen from CM (pulsing logo). I waited for more than 1 hour and still nothing happened. So then I decided to open the recovery and install the update again. As I did that, I restarted the phone but still it stopped at the loading screen and nothing happened. After that I decided to Factory Reset everything and download the update from the official CM website.. I tried to apply it from the fastboot through the
Code:
./fastboot flash zip *file*
but it showed me an error: FAILED (remote: not allowed) After reading countless threads and forums about why this might happen and stuff like that I figured out that it might be caused by the adb and because my device is S-ON, and I can't make it S-OFF because adb doesn't see my phone connected to the computer (using a mac). And so I'm stuck in a situation I can't find answer to. I have to make the adb work because I can't do anything through the fastboot, it just doesn't want to copy the zip.
Also, yes:
I did unlocked the bootloader through the HTC's website
I have TWRP installed (v.2.8.1.1)
I tried to delete the cache/dalvik. Advanced wipe through the TWRP
It says "tempered" in the bootloader
I tried to switch the cable (as I read that that might work)
I tried to stop/restart the adb server – still nothing
Edit: I managed to make the adb work through recovery. I sideloaded CMod again and Gapps. I went all back to the original problem – booting animation. I still can't figure out how to make it work.
Related
Hey,
i've got a few problems with my HTC One S, running Cyanogenmod 11 (4.4.4) with TWRP as recovery.
Since a few days nearly every app crashes, ca. 3 minutes after I start the phone. In these minutes everything is working. After that there are only messages that "android.process.acore", "com.google.process.gapps" and nearly every other app has been closed. When I press OK, the message appears again.
So I tried to flash another ROM, which isn't possible because I first can't copy anything to the phone, the copying process stops after the half. I also couldn't download a ROM directly to the phone. Then I tried to flash again my actual ROM which is still on the phone, I selected the .zip in TWRP, but then the phone is restarting and nothing happened.
There are also other problems:
1. I tried a soft reset in the settings, isn't possible because nothing happens when i press the "Confirm" button
2. Clear storage and Factory reset in the boot loader isn't possible, when I select one of that the phone only starts into the recovery, without anything has been resetted
3. Pushing a zip with ADB doesn't work, it says I don't have permissions to copy anything on the storage
4. The ADB sideload mode doesn't start in TWRP
5. I tried to flash CWM as recovery, it says "successful", but when I start into recovery there is still TWRP..
6. Relocking the bootloader doesn't work, it also says "successful" but in the bootloader appears "*** unlocked ***" After that I tried to turn back to stock ROM with the RUU exe by HTC, but when the process starts, the phone just turns off.
Does anyone have a idea? Do I maybe have a virus? Sometimes it appears to me that there are problems with the storage or anything like that..
I really tried to do everything, and also searched in this forum and in other but I didn't find anyone with the same problem..
Thank you!
Give the Mount option a try in TRWP and see if you can copy a ROM over to the phone.
Okay I had to install the right driver for adb..
Then adb push worked, I could select the .zip in the Install option in TWRP, but the phone again just restarts without installing the rom..
ADB Sideload also worked with the driver, but after I tried to ADB sideload the ROM it said "* failed to write data 'protocol fault (no status)' *"..
Hi,
last month I received an OTA update on my stock OPO Cyanogen 12.1, ever since then my settings app have disappeared (cannot access it at all, not even from safe mode)
a week ago I started receiving an OTA notification to update to the latest firmware (20MB download) (I think it's Yog4pas3jl)
anyway I was not able to update it, i would get booted back into recovery (OnePlus recovery)
*this phone does not have its USB debugging let alone developer options enabled.
in recovery I attempted to factory reset the phone (after half way attempting to unlock bootloader using Android SDK, Universal ADB and CMD)
now it appears that my phone has been "reset" but at the selecting language screen I keep getting Unfortunately CyanogenStats has stopped, and also getting Unfortunately Setup Wizard has stopped working (after tapping on language)
I can't use my phone now as I can't get past the setup wizard,
it does not appear that I am able to boot into recovery as well, please help me!
*UPDATE able to enter Cyanogen Recovery, tried wiping cache/factory reset, still stuck at Setup Wizard has stopped working. Oh no..
Try flashing a custom recovery and wipe dalvik+chache+data (doing that will not delete your sdcard). I also got such FCs in the past and that fixed it for me.
Try to flash system partition (or full firmware) via fastboot. Just follow this guide: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471, "8. How To Flash The Cyanogen OS Fastboot Images".
P.S.
You could get full firmware here: http://builds.cyngn.com/cyanogen-os.../cm-12.1-YOG4PAS3JL-bacon-signed-fastboot.zip
I searched the forums before posting. 73 results came up and I read through and followed instructions of 7 different posts that seemed similar to mine (including the ones that appear when making a new thread), but nothing has worked or I haven't found a situation like mine.
Hi.
I have a HUGE problem and need help.
I was on Cyanogen OS 12.1 and decided to install the latest Cyanogen OS 13.1. I downloaded the flashable zip. Booted into TWRP recovery and installed the zip file. I had always allowed my phone to reinstall Super SU in the past with great succes, but it seems I shouldn't have done that according to someone in Oneplus forums. Now my phone is stuck on the bootup animation that says "Cyanogen MOD ready". I also cannot boot into the recovery or safe mode using hardware keys. Please help! I don't want to lose my phone or my data!
Thanks for any advice.
note: I used the signed flashable zip from here.
EDIT: I was able to boot into recovery using the command "fastboot boot recovery.img". I cleared dalvik cache and flashed COS 13.1 zip. Currently waiting for phone to boot. Hope it doesn't get stuck on the bootup screen again.
EDIT2: It looks like my phone has booted successfully and is now optimizing apps for COS update! If I don't follow up, it means everything worked out great again!
EDIT 3: My phone finished "optimizing" apps. I thought it would take me to my launcher as all other times I've updated. To my surprise, the phone seemed to reboot and was stuck on the "splash screen" (Cyanogen MOD ready). After that, I got the "Android is starting" "Optimizing app xx of xxx" message again, which is incredibly weird and I think my phone might be in a bootloop. PLEASE HELP!
EDIT 4: I remembered that I did a nandroid backup last February so I restored it with "restore" in TWRP. My phone has been stuck on the "Cyanogen" boot screen for about 40 minutes. I'm lost.
To recap everything:
1. I was trying to manually upgrade from COS 12.1 to COS 13.1
2. My phone was rooted, had TWRP recovery and ADB debugging was enabled in dev options. I can enter fastboot mode using hardware keys. I cannot enter recovery using hardware keys (shows a blank screen), but I can enter recovery using "fastboot boot recovery.img.
3. After I flashed COS 13.1, I was asked (in TWRP) if I wanted to install SU and I said yes and flashed it. This is when I was in a loop of being stuck on COS 13.1 splash screen for about 5-10 minutes and then my phone was "optimizing app xx of xxx" for 15 minutes and then rebooted and did everything all over again.
4. I tried to restored a nandroid backup using "restore" in TWRP, but phone is stuck in "cyanogen" splash screen for more than 40 minutes.
No replies...
Not sure what to do at this point.
I ended up wiping data and performing a factory reset through TWRP. Might try to upgrade again in the future.
Hello,
My unrooted 1+1 got stuck in recovery mode after running out of battery. I have no bootloader and no access to internal memory. The only ADB command working is sideload. I have tried wiping my device and side loading more than 20 different builds from complete OTA cm11 to cm13, all goes well until 47% and then eventually exists, sometimes without any error but rebooting the device afterward always goes back to recovery mode. I also tried to sideload the google apps after it with the same result. forcing a reboot to the bootloader is showing me a quick error before going back to the recovery menu. Perhaps my method is correct but I'm unlucky to find the right builds. Googling this issue it seems that I'm not alone.
Hello everyone,
The starting situation is the Google Pixel of my mother was stuck on android 8.0. While showing there was an update available, the update would always fail to install after the reboot in the process. I found advice to factory reset the phone and then update, but this didn't help.
So my first thought was, if the update won't install the normal way I will do it manually. Google OTA installation guide says, get file (latest), reboot to recovery, plug in to USB, choose apply update by adb.
At this point the guide loses me, because the recovery screen I get to only lists reboot, reboot bootloader, simlock tool and device info tool (see picture). The device info will only tell "failed to update device info". The simlock tool just says "failed to enable simlock". Further while on this screen the phone isn't visible as an ADB device any more.
Next thing to try cause this didn't work was getting the image file (latest) from Google and flashing it through fastboot flash all, which led to a boot loop and the phone not starting at all. So I went and flashed back to the android 8 that was on it before and the phone booted again, but I'm still not any step further.
Next idea was maybe the recovery is broken somehow, so I went to install TWRP. Following the instructions I copied the latest version zip onto the phone and booted the img through fastboot. So far everything is fine, but when I install the zip I will get several errors about "can't mount /persist". And the installation won't work.
At this point I am out of ideas, so maybe someone here can tell me if and how this can be fixed? I wasn't able to find any information on this issue, aside from some xiaomi phones can show similar errors with the /persist partition and TWRP.
Any help would be welcome.