Well, anybody or devs who can explain to me why the official OTA would trip flash counter for noob like me?
I did flash CWM 5.5.0.4 via ODIN that caused counter to become 1.
Then flashed Super User v0.87 (now updated v0.93) via CWM, and counter stayed at 1.
I did not get into download mode after that, nor flashed anything via CWM.
No custom Rom installed yet.
Installed insecure boot using Samsung Tool Kit V1.0 by Mksip (great tool):good:
Then OTA update this morning.
It downloaded fine, and after backing up Google search by TB, I tried to install.
I went into recovery automatically, and gave me "installation aborted. unverified signature"
So I went into download mode to check, and it shows flash counter now upto 3.
And shows as custom binary, and custom Rom.
I know I did not install any custom ROM yet, why does it think as custom rom and binary?
Is it because of insecure boot I installed?
Any light to this is so much appriciated for my learning for android.
Thanks in advance.
Related
I tried to backup my ROM using Rom Manager. In order to proceed, I tried to flash ClockworkMod Recovery via Rom Manager.
The phone rebooted but in recovery (3e), I had the signature verification error in Red.
Due to the rave reviews for ROM Manager, I'd rooted my phone with S2Root as CF-Root will not work with it.
So now, as I want to backup my phone, I would like to re-root my phone over S2Root with CF-Root .
Will this cause any problems?
You need to a flash a cf-root kernel that gets rid of signature verification, then in cwm you can backup your rom.
Use this kernel if you want rom manager+cwm recovery.
Or you can flash cf-root and use CWM manager (app) it does most of the same stuff, just none over the OTA download/flash stuff.
ok guys i odin the stock rom with root, how in the heck i get into recovery mode and install cm7? i tried rom manager and it didnt work any other ideas?
Rom manager does not work correctly on stock. (It will work once you are on cm7.) You need to install a kernel that contains ClockworkMod Recovery. If you install the kernel with Odin or Heimdall, it will increment the flash counter and cause the initial I9100 boot screen with yellow warning triangle. If this is a concern to you, use the Guide linked in my signature to avoid that.
Hi All,
I am having trouble with Galaxy S2. Months ago I rooted my phone, installed cwm and installed a ROM into it. Now they have released a new version of the ROM which I want to install it.
This is the ROM:
http://galaxys2root.com/galaxy-s2-roms/resurrection-ics-rom-v2-0-for-galaxy-s2-i9100-best-ics-rom/
however, I am unable to boot into CWM Recovery.
If I do the POWER+VOLUP+HOME button its going directly to Android Recovery
I tried opening the CWM Manager, and I get this prompted:
"This version of CWM Manager should be used with CF-Root v5.0 or newer. It appears you are running a different kernel. Various features have been disabled"
I remember Flashing a Kernel to remove the Triangle Logo on the Loading Part.
So how can I flash the Kernel back? And install the newest updated ROM
Flash cf-root first it seems that you're not rooted.
Sent from my GT-I9100 using xda premium
Flashing the original kernel to remove the yellow triangle also takes you back to stock 3e recovery. You are still rooted though. Reflash the unsecure kernel through cwm manager or if that doesnt work, download ktool from google play and reflash from there.
This will give you CWM recovery without increasing binary flash counter. Reboot into recovery and do full wipe, before flashing new firmware.
Sent from my GT-I9100 using Xparent ICS Tapatalk 2
umleo23 said:
Hi All,
I am having trouble with Galaxy S2. Months ago I rooted my phone, installed cwm and installed a ROM into it. Now they have released a new version of the ROM which I want to install it.
This is the ROM:
http://galaxys2root.com/galaxy-s2-roms/resurrection-ics-rom-v2-0-for-galaxy-s2-i9100-best-ics-rom/
however, I am unable to boot into CWM Recovery.
If I do the POWER+VOLUP+HOME button its going directly to Android Recovery
I tried opening the CWM Manager, and I get this prompted:
"This version of CWM Manager should be used with CF-Root v5.0 or newer. It appears you are running a different kernel. Various features have been disabled"
I remember Flashing a Kernel to remove the Triangle Logo on the Loading Part.
So how can I flash the Kernel back? And install the newest updated ROM
Click to expand...
Click to collapse
flash the CF-root kernel using odin or siyah kernel(for me siyah is much smoother) and everything should be fine, also use triangle away to remove the triangle (u can get in google play for donation to the dev or on XDA for free)
Hi,
My phone quits during the update process to JB in recovery at around 32% and then once booted back into android displays a popup saying failed to update software, try again using kies or use a samsung service centre. It doesn't connect to kies (stays stuck at connecting) and pretty sure samsung will just wipe the phone which I'd rather not do.
I originally had the phone rooted with Siyah 1.5.3 but have since reflashed the stock i9300 3e android recovery, reset the flash counter to 0 and official binary with triangle away and fully removed root from within SuperSU. I have also wiped the cache, any ideas on why the update is still not applying? I would like to stick the stock rom and avoid wiping.
Same here,
Stock Rooted S3 with CWM and busybox. Used Mark Skipper's toolbox for that, and also used that to unroot, flash stock recovery and uninstall busybox. JB update also gets an error at 32%. Do I have to uninstall SU too? Really don't want to do a complete reinstall since CMW didn't manage to backup my phone...
Aladdin Sarsippius said:
Same here,
Stock Rooted S3 with CWM and busybox. Used Mark Skipper's toolbox for that, and also used that to unroot, flash stock recovery and uninstall busybox. JB update also gets an error at 32%. Do I have to uninstall SU too? Really don't want to do a complete reinstall since CMW didn't manage to backup my phone...
Click to expand...
Click to collapse
Haven't tried to update since I unrooted (ota is only available during a few hours in the afternoon here and hasn't become available yet) but it removed the SuperSU.apk when I unrooted. Stweaks app is still there but doesn't work due to the lack of root. The only other non-stock thing left is the kernel but I don't think that should matter seeing as I've used triangle away and reset the counter and binary to official. I'll post on whether it works next time around
Try removing cwm somehow, many people find that this is a problem, same happens with me, apparently cwm fixed it in newer updates.:good:
CWM is the culprit. I really don't know why people insist on using that. It is utterly useless.
Download the ROM you want from samsung-updates.com or through CheckFUSDownloader, extract the .MD5 file from the downloaded ZIP, copy the .md5 file to the device, and flash using MobileOdin.
Then, if you want, just flash SiyahKernel again using Odin.
I had already removed cwm recovery and replaced it with the stock i9300 3e recovery but still didn't work, I downloaded the ota update manually and found it be a small incremental update which still didn't flash in the stock recovery due to a mount error..
in the end I checked the latest update available from checkfus, downloaded it from samfirmware.com and flashed it using odin.. and now got jelly bean without wiping! Reflashed siyah & su binary and everything is good now. Only issue now is the OS sees the device being modified (even after triangle away reset) so a future ota updates is off the cards.
this worked for me.
viva.fidel said:
I had already removed cwm recovery and replaced it with the stock i9300 3e recovery but still didn't work, I downloaded the ota update manually and found it be a small incremental update which still didn't flash in the stock recovery due to a mount error..
in the end I checked the latest update available from checkfus, downloaded it from samfirmware.com and flashed it using odin.. and now got jelly bean without wiping! Reflashed siyah & su binary and everything is good now. Only issue now is the OS sees the device being modified (even after triangle away reset) so a future ota updates is off the cards.
Click to expand...
Click to collapse
in triangle away there is a box that says something like modified workaround, tick that then run triangle away, when it restarts your status will be normal, then go to application manager and remove triangle away. after about 15 minutes go into superSU and unroot.
Hello everyone,
I recently picked up a couple GS2's for dirt cheap just to mess around with. I am having a very hard time getting any custom recovery installed on them and I was wondering if there is a trick to it that I am not seeing. I've tried flashing various CWM modified kernels using odin with no luck. They flash successfully but still boot to 3e when I boot into recovery. I tried flashing a modified update.zip from the CM website and it fails with the error "failed to verify whole-file signature". Most recently I did a complete restore using odin with a rooted image, then used Rom manager to install CWM. Rom managed says it is successful, but when I reboot into recovery it launches 3e and attempts to do something that returns the same error "failed to verify whole-file signature". Any input of suggestions would be appreciated.
Bklynrx7 said:
Hello everyone,
I recently picked up a couple GS2's for dirt cheap just to mess around with. I am having a very hard time getting any custom recovery installed on them and I was wondering if there is a trick to it that I am not seeing.
Click to expand...
Click to collapse
The recovery is compiled into the kernel on this phone, but it seems that you understand that already. The kernel and system must match. You probably need to be rooted. You have not given any specifics about the firmware, what is already installed, what specific item you are trying to install, etc.
I've tried flashing various CWM modified kernels using odin with no luck. They flash successfully but still boot to 3e when I boot into recovery.
Click to expand...
Click to collapse
This does not actually seem logical. I'm wondering if you are not mentioning something that I would need to know to determine why you are getting this result. If you install a custom kernel containing a custom recovery, you should then be able to boot into the custom recovery. If you still have 3e recovery, it indicates that you still have the stock kernel installed.
I tried flashing a modified update.zip from the CM website and it fails with the error "failed to verify whole-file signature".
Click to expand...
Click to collapse
I would not expect that to be successful. Among other things, it is probably not specific for the I777.
Most recently I did a complete restore using odin with a rooted image, then used Rom manager to install CWM. Rom managed says it is successful, but when I reboot into recovery it launches 3e and attempts to do something that returns the same error "failed to verify whole-file signature". Any input of suggestions would be appreciated.
Click to expand...
Click to collapse
Do not use Rom manager. It does not work with the I777, and can cause unrecoverable damage in some cases. There is a sticky post about it here in the forums.
You can find various resources in the Download Repository. See the link in my signature.
Here's what I would do:
Flash the latest stock Jellybean firmware, UCMD8, from the Repository.
Root using Framaroot with the Aragorn exploit.
Flash the AJK v4.9 NoSwap kernel using Mobile Odin Pro or Mobile Odin Lite. You have to extract the boot.img from the kernel zip and flash that, but don't let it boot into system. Instead, you can boot directly into CWM and flash the AJK v 4.9 NoSwap kernel zip, or if you prefer, you can flash some other custom firmware at this point.
creepyncrawly said:
The recovery is compiled into the kernel on this phone, but it seems that you understand that already. The kernel and system must match. You probably need to be rooted. You have not given any specifics about the firmware, what is already installed, what specific item you are trying to install, etc.
This does not actually seem logical. I'm wondering if you are not mentioning something that I would need to know to determine why you are getting this result. If you install a custom kernel containing a custom recovery, you should then be able to boot into the custom recovery. If you still have 3e recovery, it indicates that you still have the stock kernel installed.
I would not expect that to be successful. Among other things, it is probably not specific for the I777.
Do not use Rom manager. It does not work with the I777, and can cause unrecoverable damage in some cases. There is a sticky post about it here in the forums.
You can find various resources in the Download Repository. See the link in my signature.
Here's what I would do:
Flash the latest stock Jellybean firmware, UCMD8, from the Repository.
Root using Framaroot with the Aragorn exploit.
Flash the AJK v4.9 NoSwap kernel using Mobile Odin Pro or Mobile Odin Lite. You have to extract the boot.img from the kernel zip and flash that, but don't let it boot into system. Instead, you can boot directly into CWM and flash the AJK v 4.9 NoSwap kernel zip, or if you prefer, you can flash some other custom firmware at this point.
Click to expand...
Click to collapse
Sorry if I want clear. The phones are currently on 2.3.6. I tried using framaroot but it was not successful. The app said it was successful, but there was no supersu after I rebooted. I successfully got the phone rooted using one of the one-click odin flashers posted on these forums that are said to return it to factory + root. I then tried to use rom manager which said it was successful, but wasn't. That makes sense now that you're telling me its not compatible. Ill try upgrading to the JB firmware first, then ill try framaroot. Thanks for the suggestion
I just wanted to update the thread and say that this worked. Thanks again. I'm having an issue getting Gapps flashed but that's another topic. My big concern was that the phones wouldn't charge without boot looping because they had the wrong battery installed. The Stock Jellybean with the kernel you suggested fixed that.
Bklynrx7 said:
I just wanted to update the thread and say that this worked. Thanks again. I'm having an issue getting Gapps flashed but that's another topic. My big concern was that the phones wouldn't charge without boot looping because they had the wrong battery installed. The Stock Jellybean with the kernel you suggested fixed that.
Click to expand...
Click to collapse
Maybe I could help. What error does it give when you flash gapps?