I recently installed TWRP custom recovery on my phone so I could install the "Carbon" custom ROM. When it turned out that I apparently need CWM, not TWRP in order to do this, I had already installed TWRP. Some other things I can't remember well enough to describe happened while I was tinkering further, and what I know now is that there is NO operating system installed on my phone, just TWRP (which is the only thing into which my phone will boot) and it's telling me it's "unable to mount preload." I vaguely remember it telling me something to the effect of "you may need to [some action here] before you'll be able to use 'data' again" when the process of trying to install Carbon through TWRP failed. Now I can't seem to put the stock firmware back on the phone. When I select the ZIP file to install, it tells me "skipping MD5 check: no MD5 file found" even though the ZIP file is definitely on the SD card. I'm guessing this has something to do with its inability to mount "preload"? I honestly don't know. I just know I'm stuck.
What I want to do is reinstall the stock firmware and recovery program that comes with my phone, get rid of TWRP completely, and then try installing CWM from the play store, the simple way. All this bootloader stuff is too advanced and risky for me. But first I need to get my phone working/booting into the android OS in the first place.
Can anyone give me instructions on how to fix this? If so, please be *extremely* specific and explicit, tell me every single step very clearly, as though you were explaining it to a child. Please don't assume I know what you're referring to with slang, shorthand or anything else. This is my first experience with custom recovery managers and ROMs, so please don't take anything for granted.
Related
Hi
I am running a Stock LSD 4.1.2 JB Rom on my I9100 and do not wish to Root my phone. Yes it was rooted once but I have a specific reason for not wanting to revert back to root.
On a few occasions over the past year I have wanted to flash an app via "Recovery Mode", a .zip file located on the phone's external SD card.
On trying to flash, the following is displayed in yellow: -
E: failed to verify whole-file signature
E signature verification failed
Installation aborted.
I have searched and searched this and other forums and although I can find many many instances when this has ocurred with other people I have not yet seen a generic solution to this problem.
It must ocurr because of a certain situation being prevelant within my phone and the references to it on forums usually suggest they are because someone is messing with a Custom Rom and/or a Rooted Kernal etc etc.
Could someone please tell what is happening, why this is the case and what can be done to sort it please.
I would say that my phone is just over 18 months old, never has had a problem, has been flashed with "Stock Roms" quite a few times and all without wiping or restoring to the factory settings. I do not want to wipe it to sort this problem out and am hoping an easy fix is available.
Hope someone can help
ps - I am trying to install the 4.2 Camera via the patched.zip and have tried to install the "Temporary" Clockwork Recovery" app with exactly the same problem. I stress I do not want to Root.
Anyone please?
rozel said:
Hi
I am running a Stock LSD 4.1.2 JB Rom on my I9100 and do not wish to Root my phone. Yes it was rooted once but I have a specific reason for not wanting to revert back to root.
On a few occasions over the past year I have wanted to flash an app via "Recovery Mode", a .zip file located on the phone's external SD card.
On trying to flash, the following is displayed in yellow: -
E: failed to verify whole-file signature
E signature verification failed
Installation aborted.
I have searched and searched this and other forums and although I can find many many instances when this has ocurred with other people I have not yet seen a generic solution to this problem.
It must ocurr because of a certain situation being prevelant within my phone and the references to it on forums usually suggest they are because someone is messing with a Custom Rom and/or a Rooted Kernal etc etc.
Could someone please tell what is happening, why this is the case and what can be done to sort it please.
I would say that my phone is just over 18 months old, never has had a problem, has been flashed with "Stock Roms" quite a few times and all without wiping or restoring to the factory settings. I do not want to wipe it to sort this problem out and am hoping an easy fix is available.
Hope someone can help
ps - I am trying to install the 4.2 Camera via the patched.zip and have tried to install the "Temporary" Clockwork Recovery" app with exactly the same problem. I stress I do not want to Root.
Click to expand...
Click to collapse
You need root access to flash apps or modify your system
pasanjay said:
You need root access to flash apps or modify your system
Click to expand...
Click to collapse
Ermm, do not think so. Please review this thread before making wild comments like this: -
http://forum.xda-developers.com/showthread.php?t=2082103
I know in some way though that you probably thought you were helping.
Surely this problem has a cause and a solution?
rozel said:
Ermm, do not think so. Please review this thread before making wild comments like this: -
http://forum.xda-developers.com/showthread.php?t=2082103
I know in some way though that you probably thought you were helping.
Surely this problem has a cause and a solution?
Click to expand...
Click to collapse
u have to first flash the 'Temporary CWM recovery .zip' then select 'reboot to recovery' option in stock recovery to enter 'temporary cwm recovery' there u select the 'Camera zip file' to flash.
PS- after flashing 'Temporary CWM recovery.zip' do not reboot ur phone the normal way by doing so u will lose ur temporary recovery.
each time before flashing any zip file u have to flash 'temporary cwm.zip' file first.
Hi thanks but I know this.
Can we get back to my topic please? I would not have posted if I could flash the Temp CWM Recovery. zip file
I just need to know what causes the error I am getting and how I can irradicate it.
rozel said:
Can we get back to my topic please? I would not have posted if I could flash the Temp CWM Recovery. zip file
I just need to know what causes the error I am getting and how I can irradicate it.
Click to expand...
Click to collapse
As the error indicates, it fails to verify the file's signature. You can't flash unsigned packages via stock recovery. The solution is exactly what was already mentioned to you:either root and install a custom kernel/recovery (you don't want it, that's fine), or use a temporary custom (non-stock) recovery. While I had problems with the stock recovery flashing unsigned zips (obviously), I never had an issue with flashing a temp recovery. Try redownloading and reinstalling it - it could be a corrupt file. Which recovery are you trying to use? I recommend the temp touch CWM by Phil (the dev of the PhilZ kernel; use link in his signature). Always works like a charm.
kt-Froggy said:
Try redownloading and reinstalling it - it could be a corrupt file.
Click to expand...
Click to collapse
Nice one! Thank you
It must have been a duff file (temp touch CWM by Phil) as the one I just downloaded, installed without a problem. It was the very same program file but from a different source.
Just installed the 4.2 Camera too so now going to play
Thank you again
Well, there's not much to say other than I factory resetting and wiped EVERYTHING on my phone besides the Bootloader files, and Recovery, there is no System file from which to boot from, so I can not boot past HTC Logo, I am able to go into Recovery and Bootloader, but can not flash ANYTHING over ADB/Fastboot because of multiple errors, some being "Not Allowed" and "unable to read zip file." I need help bad, I tried RUUs, RUU Zips, Everything, all the same (Except RUUs, which are stupid since they never work, they either say Error: 155, or dont go past 5%). Nothing is working, I am unable to flash nothing....
If you need more information (that I can be able to pull, I can't pull stuff like ROM details since that doesn't even exist anymore) I can try to put it up, if I can get it.
Thanks in advanced!
(Information in my Signature is outdated, only things that are current are the RADIO, RECOVERY, HBOOT, S-ON, BOOTLOADER, and Root is...I dont know if I am still rooted)
Was able to 'somehow' mount my Internal Storage through TWRP and installed ROM, and GApps.
UPDATE: I somehow got my Device to get mounted and was able to access the Internal storage through my PC for idk how long, so I instantly copied the ROM and GApps I had to the phone, which was a success, I got them on my phone and was able to install the .zips through TWRP (Had to update to TWRP 2.8.1.0) and now I am awaiting to see if the ROM works.
The ROM install was a success, got my phone working again. Someone change post to resolved? Thanks.
Hi guys
Apologies if this has been posted in the wrong section.
I have recently inherited a Galaxy S2 (GT-I9100) running the CyanogenMod 12.1, Android Version 5.1.1
I have spent the last two day trying to and failing miserably to install Xposed Installer V3.0 Alpha 2, I have searched Google and read through numerous forums on how to resolve this, but the more I read the more confusing it becomes. I would really appreciate any help/assistance in helping me fix the problem, so that I can run the app without any issues. When I access the app's log it states:
data/data/de.robv,android,xposed.installer/log/error.logpen failed. ENOENT (No such file or directory)
Also, when I try to run Titanium Backup 6.1.0, I get an error stating:
Sorry, I could not acquire root privileges. This application will *not* work! Please very that your ROM is rooted, and try again.
This attempt was made using the "/system/xbin/su" command.
I have gone into Developer Options and set Root Access to Apps and ADB.
As I new to Android my understanding (please correct me if I am wrong) that the CyanogenMod 12.1 was actually a ROM and therefore Titanium Backup should work. FYI SD Maid not working.
Any help on both of these issues would be most appreciate, please bear in mind I am a noob where Android and Galaxy S2 are concerned.
Thanks in advance.
The forum for the i9100 is located here, but because it's so close to the i777 we can probably help a bit.
Sounds to me like your phone isn't rooted, as none of the apps you mention will work without root privileges. Install the latest SuperSU; you should be getting access prompts if you're correctly rooted.
If you are not prompted for root access when opening apps such as Titanium Backup, you'll need to install Framaroot and use the Aragorn exploit in order to easily root your device. Let us know if either of these work for you.
Hi Steve
Thanks for the reply.
I should have mentioned that I already have Super SU installed and for certain apps it does ask me to grant access. If open Super SU it displays the following apps:
Titanium Backup
Root Explorer
pops1368 said:
Hi Steve
Thanks for the reply.
I should have mentioned that I already have Super SU installed and for certain apps it does ask me to grant access. If open Super SU it displays the following apps:
Titanium Backup
Root Explorer
Click to expand...
Click to collapse
Strange. In that case have you tried doing a complete wipe in recovery, then reinstalling the ROM? In your case you would boot into recovery, wipe /system and dalvik cache, then install ROM and gapps. Just make absolutely certain you're running a custom recovery before doing this, such as CWM (ClockworkMOD) or TWRP (TeamWin), or you could damage your device if you're on stock recovery. And, of course, make sure you have the ROM/gapps already on your device before wiping everything!
Because you inherited the device the best method would normally be to flash back to stock and start all over - if for nothing else it's a good learning experience. Hope this helps.
Hi Steve
Thanks for the reply and your advice/information, very informativinformativ.
I was trying to avoid a complete wipe and reinstalling the ROM again, as Android is new to me and I don't want to mess up the installation and wreck the phone, even it was free. However, I think I have no choice and will have to bite the bullet and do it.
Thanks once again.
pops1368 said:
Hi Steve
Thanks for the reply and your advice/information, very informativinformativ.
I was trying to avoid a complete wipe and reinstalling the ROM again, as Android is new to me and I don't want to mess up the installation and wreck the phone, even it was free. However, I think I have no choice and will have to bite the bullet and do it.
Thanks once again.
Click to expand...
Click to collapse
As long as you have a custom recovery there's very little that can go wrong with a full wipe. I would suggest booting into recovery first (power button + both volume keys, then release at the Samsung logo) and make sure you're running either CWM or TWRP. While in recovery do a backup first, as a "just in case". You can always restore your device fully from a backup.
The next thing to remember is to make sure your ROM/gapps are compatible with one another. For instance, if you're installing a CM12 (Android 5.0+) ROM make sure your gapps are also 5.0+.
Best of luck!
When I attempt to go into Recovery Mode it does so, but opens a CyanogenMod screeb, it dies not show any options to backup/restore, it foes however have the complete wipe option. When I run ROM Manager I have done the following Recovery Setup, which now shows Recovery Already Installed:
ClockworkMod Recovery
TWRP
But I don't understand what I'm doing wrong, for neither option to be available in Recovery Mode?
pops1368 said:
When I attempt to go into Recovery Mode it does so, but opens a CyanogenMod screeb, it dies not show any options to backup/restore, it foes however have the complete wipe option. When I run ROM Manager I have done the following Recovery Setup, which now shows Recovery Already Installed:
ClockworkMod Recovery
TWRP
But I don't understand what I'm doing wrong, for neither option to be available in Recovery Mode?
Click to expand...
Click to collapse
Best option for you is to go to the i9100 forum and download a kernel for your phone that is compatible with the OS version you want to install (CM12, which is 5.1. in your case). With your device (as well as our i777), the kernel and recovery are fused together, so you cannot use ROM Manager to install a recovery to a separate partition.
Once you have an i9100 5.1 kernel downloaded on your phone you can flash it through the current recovery you have, then immediately reboot back into recovery. You'll then have the correct recovery and can proceed as normal with the ROM installation.
CWM absolutely has a backup/restore option, but it's hidden in a sub menu. My personal recommendation is to use TWRP recovery, as it's still being developed and is more robust/user friendly.
So as a general rule stay away from ROM Manager for system specific changes.
Thank you so much for the information/advice, I really do appreciate all of it.
Hello there,
Well, to preface what has led me into the situation that I am in right now, I had installed SS in the hope of creating a virtual ram disk and installing a custom rom within it. Where I messed up is that, despite me having the virtual rom created, I flashed a ROM zip over the stock android rom and not on the virtual rom slot, thus locking me out of my phone. I had done a standard factory wipe before installing the new rom and (unless I am incorrect) have wiped out the usb debugging functionality I had previously enabled as a result. When starting my phone, I am still able to access the custom recovery that SS has installed (I545 Safestrap 3.75 (TWRP v2.7.10)). However, from there I attempt to boot the phone into system, I get an error notice to the effect of "There is software Verizon doesn't supprot please take this to your nearest Verizon store, etc, etc." With a notice at the top saying kernel failed - and at that point if I attempt to start the phone by pulling out battery and restarting, it negates the option to log into SS/TWRP recovery and leads me to that verizon incompatibility screen all over again.
This is where it get interesting though
(I would use link functionality to post a Heimdall screenshot but I couldn't remember my old xda account info and it prohibits users w/ less than 10 posts from posthing links)
If I attempt to reflash the MDK kernel through Heimdall, despite it saying that it failed in the log, my phone reboots and it once again brings me to the SS splash screen at the ability and I able to get back into the SS/TWRP recovery yet again. Very weird.
I have been primarily following instructions from this site: droidview's "how-to-install-latest-official-firmware-on-samsung-galaxy-s4-all-models" (which you can find easily via those terms in google without me posting link)
I have been using the original .pit file that I have pulled from my own phone from heimdall myself (before I locked myself out of stock rom compeltely) but do have a PIT file copy from the website where I have been referencing before.
I have yet to try to flash a zip file of a 4.4.2 verizon ROM via the SS/TWRP recovery because I don't have any SD card readers in my computer and had previously put the custom firmware I had wished to install on my sd card via mounting my phones SD card through the stock ROM to my pc before I messed up overwriting it. The functionality for SS mounting sd card via the recovery itself seems to be broken so that isn't an option. However, I could borrow a phone from someone else and mount my SD card through their phone and access it from my PC that way.
All attempts of reflashing via ODIN on my windows partition have failed as well. ODIN recognizes my device but, following the instuctions from the instructions I referenced earlier, have resulted in it displaying a "FAIL" message almost immediately.
Thanks for taking the time to read this much and I'd appreciate any help I can get.
I am trying to install the Flumics rom 3.0 its installs fine but the problem is when i reboot it reboots but then goes back to TWRP. I also get a message saying
'TWRP can leave your ststem partition unmodified to make it easier for you to take offical updates. TWRP will be unable to prevent the stock ROM from replacing and will not offer to root your device'
Installing zips of performing ADB operations may still modify the system partition
I really want this rom to work on my phone Im not sure what to do now.
I followed this forum to get my recovery
https://forum.xda-developers.com/redmi-note-3/help/official-twrp-askibg-password-to-t3492362
Your help would really really be appreciated.
Thanks