Can't boot into Clockworkmod Recovery? - Android Q&A, Help & Troubleshooting

I know this forum emphasizes a lot on obviously finding other threads which will likely have the answer to your questions, however everything I've looked at so far has a similar problem, but not entirely the same or the solution for them doesn't work for me. So do forgive if this is something ridiculously simple, I am new to rooting!
So I'm on a Galaxy S2 running Gingerbread 2.3.4, my baseband version is I9100XXKI1 and my kernel version is [email protected] #2
Using Odin3 v1.85 and S2 Root. (Superoneclick kept freezing on me)
My aim is to install Cyanogenmod 7.1.
So far I started off by trying to flash it with XWKDD Insecure, which I believe is wrong? However after rooting it, I installed ClockworkMod Recovery, downloaded the ROM and tried installing it - which is where the problem started - I kept getting the error in recovery mode 'Invalid whole-file signature'.
It just wouldn't boot in to ClockworkMod Recovery.
So after some digging around I managed to find a file to flash to my device for the CWM Recovery mode, tried it, and it worked. However, I still couldn't install Cyanogenmod from my SDcard.
I tried it a few times, wiped/formatted a few times and ended up getting my device stuck in a bootloop.
So, I've managed to get it out of the boot loop, and started fresh...
I flashed it with XWKH4 Insecure, unrooted, rerooted etc.
I've downloaded CWM again, downloaded the Cyanogenmod again, tried installing it, and once again it's gone back into Androids recovery and failed to install because of the 'whole-file signature' and failing to verify it.
Any help would be extremely appreciated, sorry it's a bit of a long read,
Thanks in advance!
Adam

Related

[Q] flashing cwm causes bootloop

Ok, because I was so happy with cyanogenmod on my galaxy s I decided to try to install it on my SII.
Silly me, I decided to follow the instructions. couldn't get my trusty odin working, even after a couple of reboots and reinstalls of kies. Heimdall turned out to be the 64 bit version so I needed to find the 32 bit version. Long story short, the instructions sucked...
Then, I tried to install the suggested cwm. After a reboot, my phone entered a bootloop. I could enter recovery but trying to flash cm10 gave me "Status 7 blabla".
So, I searched on the web for a stock rom to at least get my s2 working again, found one and flashed it. Market keeps on crashing and it's version 4.0.3.
I tried reflashing cwm, cf-root and time and time again it kept creating a bootloop after which I had to reflash the rom with the broken market to get everything working again.
My questions are:
where did I go wrong in flashing cwm? Is there a different version I should flash? what's up with the extremely bad cyanogenmod instructions? Can someone get the market working again?
can someone guide me step by step through the process?
Why don't you flash it via recovery?
Sent from the little guy
gastonw said:
Why don't you flash it via recovery?
Sent from the little guy
Click to expand...
Click to collapse
because it gives the error "status 7"
I can't install a cwm that doesn't bootloop (I can however enter recovery) and in recovery I can't flash a thing because it throws errors at me
Assuming that you are on stock samsung ICS ROM, flash Siyah kernel from Odin
http://d-h.st/Bcf
After this you will get CWM recovery from which you can flash any i9100 CM version.
Sent from my GT-N7100 using Tapatalk 2
quick follow-up:
I had another laptop laying around that was never poisoned by samsung kies, so I decided to give it a try. installed the usb-drivers and used odin to flash another stock-rom version (that actually worked this time )
Then, I flashed cf-root and upgraded to cyanogenmod without any problem.

[Q] Phone stuck in recovery boot SGS2

Hi, I'm pretty new to rooting and whathaveyou, and followed a guide to installing Siyah-s2-v6.0b5, and everything was working fine, until I came across Cyanogen, which I'd saw a while back and looked quite interesting. I tried to install Cyanogen once the phone was rooting, but the installer on my PC said that my device was unavailable for the installation, for which I appointed to the fact that it was rooted.
I downloaded the Cyanogen install zip for my SGS2, and in the recovery menu used "install zip from sdcard" from which I selected the Cyanogen zip. The installation failed, and any attempt at starting the phone would lead me to the CWM-based Recovery v6.0.1.2.-Siyah, and no further. I'm able to access the download mode.
I attempted using Odin3 v3.07 to install a stock kernel onto the phone, but I was left with the boot, maybe I was doing it wrong?
I'd really appreciate some help, thanks.
- Brad

[Q] Soft Brick. Cyanogen recovery loop. Will you please help?

Hello, i will try to be thorough.
BUT, i am a noob and didnt write down everything i did.
Have a I717 at&t note 1. with the 4.1.2 update originally OTA installed by keis.
I recently rooted it using Saferoot. it went well and i didnt see any problems. i flashed a custom rom and didnt like it so using clockworkmod recovery i went back to the 4.1.2. I then tried pac lollipop >pac_quicyatt_lp.beta-1.unofficial_20150327< i liked this rom but needed to flash Gapps.
This is where the trouble started. i didnt/dont know the proper procedure to flash the Gapps on top of or into the rom.
I first tried >gapps-5.0.x-20150404-minimal-edition-signed.zip< and it looked like it loaded correctly. but nothing appeared in the phone. the pac rom was still working well.
I then did more research and tried >gapps-lp-20150222-signed.zip< , again it looked like it loaded well but nothing showed up "in" the phone.
right here is where things got screwy. i had been using clorkworkmod for recovery and rebooting. and i think somewhere in developer settings i clicked something about how rebooting is handled.
because after trying to install the Gapps it went into Cyanogen recovery... and loops.
no matter what i do it goes back to cyanogen recovery.
I never knowingly installed cyanogen and dont know why it all of a sudden is going into cyanogen recovery over and over.
a list of things that may have bearing:
1. i tried reinstalling the pac rom. it loads and completes but it still just goes to recovery.
2. tried different ways of clearing cache and data wipes.
3. computer, kies, and odin 3.09 do not recognize phone.
4. have proper drivers on computer. phone was previously recognized by kies and cpu (4.1.2).
5. currently the only way to get anything into phone is by pulling sd card and reinstalling with info on it then using cyanogen recovery.
6. i have searched for about 11 hours and tried a bunch of things. but just restarts in cyanogen recovery
7. i was scared to fully try things i found that wernt specifically for the i717.
8. i could not find an original gingerbread rom. they all seemed fishy (needed downloaders. or ended in .zip.rar)
9. had backed up with clockworkmod and with titanium recovery (while in 4.1.2).
I dont know if i can reach the clockworkmod save through cyanogen recovery.... if so it seems like a great option.
10. at the bottom of the screen while loading rom is.... ---->>> E: cannot load volume /misc
11. only pac rom will successfully re-flash (even though it still just goes back to cyanogen). any other flash and it crashes halfway through.... i then restart and it just loops back to cyanogen recovery.
I searched here and tried the five recommended posts.
I could not try a lot of the "fixes" because the phone isnt recognized by cpu or odin (computer does beep when connected but doesnt show up anywhere).
Can you help me get back my phone please?
Randall
added
This is the only site i am asking for help on. I am willing to reply quickly and put in the time!
Thank you very much for reading this far.
Randall

Stuck in a bootloop - furthest I get is "Upgrading android apps"

So. My phone was lying on the desk and all of a sudden, it turned off beeped a couple of times for "low battery" and went into a bootloop. As stated in the title, the furthest I have gotten it to is "Upgrading android apps" or something along these lines (I dont remember the exact wording) but ALWAYS after that steps it loops. I have access both to recovery (tried flashing ArchiDroid through CWM, tried wiping etc) and download. Nothing I did so far seemed to have helped. It does go past the boot animation but even logcat didn't offer any suggestions aside from the phone dying on the "upgrade" step.
I was running cyanogen mod (can't remember the precise version number atm) when it happened along with barebones CWM. No tweaks were made besides whatever CM did.
Also, this may be relevant: I am getting this error when trying to wipe dalvik: E:unable to mount sd-ext . No idea why.
The only idea I have left currently is to try and use Odin to reflash pit, maybe bootloader and then stock firmware followed by rooting via Chainfire AutoRoot. Any tips, suggestions or ideas as to what may be causing this?
/thread
FIxed it myself by flashing a stock galaxy rom via odin + stock recovery. Followed by Chainfire AutoRoot, then ROM manager for easy CWM recovery download and then flashing ArchiDroid

TWRP will flash but disappears at boot.

I recently purchased a Samsung Galaxy SII, GT-I9100 and have been trying to install LineageOS using this guide:
https://wiki.lineageos.org/devices/i9100/install
I'm at the point where I need to flash TWRP. I've downloaded TWRP 3.2.3.0 and using Heimdall, I'm able to successfully flash the image to my phone, Heimdall's output doesn't mention any errors. However, when I afterwards shut down the phone and then reboot to recovery mode, it's still the old stock recovery present.
I have spent the entire weekend trying to troubleshoot a ton of things and trying many suggested solutions, some not working, others throwing me further down the pit of despair. One of the things I've tried was to flash CF Root. My build number ends in KWMS2, so I've been trying to find a CF root build for that but the only thing I found was this post:
https://forum.xda-developers.com/galaxy-s2/help/cf-root-download-ms2-t2880023
Which then had a link to SuperSU which I sideloaded with adb, but that didn't do anything. I also found this post:
https://forum.xda-developers.com/showpost.php?p=35682278&postcount=4
And flash the CF Root image, but that also didn't help with TWRP. I've also looked at the CF Root site but it doesn't list the GT-I9100 and Firmware.Mobi lists all i9100 versions as incompatible with CF-Auto-Root (which I'm assuming is the same as CF Root).
So because of all the trouble I've had, I'm now stuck with a phone that can boot into download and recovery mode, but can't actually boot into Android and that won't install TWRP for some odd reason.
I hope someone can tell me, in detail, what I'm supposed to do to get TWRP to actually work and not just being flashed, because I'm at my wits end.
Follow this guide (the post literally one below yours!) and you will be up and running in no time.
https://forum.xda-developers.com/galaxy-s2/help/guide-tutorial-samsung-galaxy-s2-i9100-t3538601

Categories

Resources