Hi,
I have a OnePlus One and I was having a lot of battery and network issues on Cyanogen 13.1 build version MHC19Q. I tried to do a factory reset but my phone would just not boot after the reset. It was stuck on the Cyanogen logo for over 50 minutes. So I tried to shut it down and redo the whole thing multiple times but I was facing the same issue.
So I tried to flash the ROM (downloaded from the Cyanogenmod support page). I did this through ADB but every time the installation stops midway because of
"signature verification failed"
And my computer does not recognize my phone on fastboot mode. I can only get to recognize the device when I go to recovery mode, do apply update from ADB
Please help!! I do not know how to fix this and I cannot do anything with my phone any more
Related
I did a factory reload of a rooted phone with CWM.
Now for the CWM issue the Moto G loaded OK and then said there was an update for android to fix some bugs. This was 4.4.3. I loaded it and it gets half way and it then says
"Signature verification fail"
at the bottom of the screen and
" Install Untrusted Package"
The options are yes, no or go back
at the top....
whichever one I try it then tries to boot shows the Android / Motorola screen and starts up gets a txt message for 2-3 seconds... it then goes back to Android CWM recovery with the same options as above and repeats the process. again and again and again. No function keys will stop this cycle which just repeats again. This continues until the battery dies.
any ideas ? how can I override this action in CWM v6.0.4.6 and force it to do a factory reload ? any help or advice much appreciated.
The following thread had a similar problem and was fixed... http://forum.xda-developers.com/showthread.php?p=53404637
NerdNoob1210 suggested...
"If you can still power your phone, can you still access the boot loader? If so, I would suggest using adb from a computer to flash Phillz recovery. CWM always gave me a lot of random errors when flashing items. You could use PhillZ to flash the stock ROM for 4.4.2. After that, just follow the same process I did. Download the update zip via the OTA download when it prompts you. Once it's finished, DON'T boot back into Android. Boot into Phillz recovery from the boot loader, move the zip out of the cache and onto sdcard or your computer, and then flash it either straight from the phone or by sideloading it from your computer. Then you'll have a working version of vanilla 4.4.3, and you can flash over a custom ROM in the future if you so choose."
unfortunately I can't get into bootloader. I can connect usb and it makes no difference. therefore adb commands dont work. it just goes straight into screen described with those three options. I'm hoping that there is an override action in CWM which isn't power and volume down which do nothing.
If not how can I force it into bootloader instead please ? any suggestions appreciated.
I bricked my phone while downgrading from the Brazilian lollipop to Asian Kit Kat, I did it directly which I think was my mistake. My phone won't boot up android or even the recovery (twrp). When I do a fastboot and choose recovery it will reboot into the recovery and show the flickering screen (different from the one you get after downgrading) and shows the android symbol with a warning sign. I tried to flash a new cm12 while the recovery was working and it said it was successful, which caused the damage to the recovery. At that point my phone could no longer be detected by my windows PC (tried on a different PC with ubuntu). I took my phone to some stores thinking it can be repaired but they failed, they only managed to get the recovery to work again (cwm). I tried installing a cm12 again using otg, it seemed as if it was successful but when I restarted my phone it failed and broke the recovery again. I just left the phone till it ran out of battery since it won't turn off. I'm hoping someone out there might have a solution, I tried most of what I could find on the net but alas.
Is there no one with a solution :crying:
Hello,
This morning I wanted to update my Galaxy i9505 to the latest CM 13 nightly, and this time I tried to install it from the built-in updater and not manually from the recovery.
So the phone automatically rebooted in recovery and I saw an android image for one second, and then I got stuck in bootloop. I tried every combination of removing battery / holding multiple keys at once to try to get it into normal recovery or download mode, but nothing works.
Now, when turn it on, I see the Samsung logo with the indication that it is booting in recovery, and then black screen and nothing happens. I don't know which state the phone is at this time, but when I plug it to my computer, it appears in the device manager in "other devices". So I tried fastboot, but it says the device is unauthorized.
Does anyone have an idea of what I can do ?
Click to expand...
Click to collapse
Edit : I managed to enter download mode and install TWRP recovery, then the phone started normally, but when I restarted it, it automatically tried to apply the update and the same bug appeared. Is there any way to wipe everything and install CM 13 through download mode ?
Thanks in advance.
Mod Edit
Thread Closed per [OP] request.
jackeagle
Forum Moderator
Hello,
I apologise for any mistakes as this is my first time posting here.
I recently changed the screen on my brothers OnePlus One. The installation went really smoothly and the phone displayed on startup.:good:
But for some reason now when ever it it starts up you get a 1+ logo and then it has the android man with the red triangle. It then puts you into recovery . My brother has never tried custom roms on his opo, so he has the stock recovery. I try to install some zips using the ADB sideload method but it gets about 80% done and then says that the signature verification failed even on roms downloaded from the official site. I think the phone would work if I could get TWRP installed and install the rom through there, but I can't get into fastboot mode. My brother has never been in fastboot so I don't know if you had to enable it in the OS first or something like that. If I press reboot bootloader in advance settings in the recovery it just restarts the phone back into recovery. I am not sure whether to try some type of brick fix method however it isn't hard bricked because it turns on and in soft bricked you have to use fastboot for every method that I've seen.
Any help would be brilliant.
Thanks!
Hi there, having just the old casual phone crisis. I was running cyanogenmod 12.1 for awhile and decided to finally upgrade to a nougat 7.1 build.
I tried using this one https://forum.xda-developers.com/google-nexus-5/development/rom-dark-rom-t3492150 using adb sideload as I had tried a earlier one and the gapps messed up so I wasn't able to put twrp back on the phone. The rom said it had installed successfully but I wasn't able to sideload gapps, I kept getting an error status 255. I went ahead and just tried to load the rom without gapps and see if I could install it slowly through APKs. I managed to get past the initial android load and the services started up, and it got in an endless crash loop because the phone service wouldn't start. So I went to try and flash another rom and was going to delete the cache. When I went to delete the cache the phone hung for about an hour so I tried to just reset it into recovery mode again.
Now when I hold the power button and volume down key to into fastboot mode I can. I have access to the initial screen with the four options, but when I try to start recovery mode or start the phone my screen goes black, and it'll flash the dead android symbol with the error saying unable to mount cache, it only flashes it for like half a second then goes black and repeats every 10-15 seconds.
I tried holding power down, doing volume up, and letting go to do a hard factory reset but it does nothing. I also can't seem to access the adb sideloading anymore, I'm very scared that it's hard bricked, is there anything I can do at all to fix this.
Flash a new version of the recovery via fastboot. Then do a full wipe. After that install the ROM only! Reboot recovery (not system but recovery) then reflash the ROM (no wipe) and add everything else. Hope this helps you out.
The phone may not boot the ROM without wiping data if installing a 7.1 ROM over a 5.1.1 ROM.