(Sorry if you guys don't like me using the term soft brick :S)
Phone version: Samsung Galaxy S II I9100
Problem: Rooted phone using [galaxys2root's method] (Odin + Jeboo Kernel + Clockworkmod) and then installed CyanogenMod using [WiredMash's method] (sorry can't post youtube links)
Followed the procedure and everything was working perfectly. Afterwards, I messed a few settings up so I thought it would be easy to simply do the process above again to start with a clean slate.
I don't particularly remember the order in which I messed things up, but I went back to Clockworkmod, cleared literally everything (including the internal SD, meaning I lost CyanogenMod) and then went back to Odin and tried to flash Jeboo Kernal on again.
Current Status of Phone:
Stuck at the Loading Screen with the Yellow Exclamation Mark.
Downloading mode states I've done Binary Flash 8 times (woops)
CyanogenMod no longer initiates.
Still able to access CWM, but can't flash any Zips on because there's nothing on the memory
What should I do? Would this simply be fixed by popping down to the store to grab a MicroSD and going on my computer, putting CyanogenMod on it and then flashing it using CWM?
If it works, would I have screwed up anything? Would I have to clear some stuff using CWM? Would it be like nothing happened? (I have a weird obsession that requires everything to be perfect)
Ok....it's not *really* a brick....it's not even a bootloop.....it's (as you said) a lack of os.
You have an accessible CWM, which basically puts you in the clear.
You suggested your solution.....buying a microSD card, copying a rom to it and using cwm to flash it.
I basically was in the same situation as you, and if I'd had a microSD card that my laptop recognised, that is the solution I'd have used. My issue was that my XP laptop doesn't like high capacity memory cards (mine is 32Gb)....if you are running XP, it might be a good idea to get a (maximum) 4Gb card.
The above method will also require you to flash GApps as well......
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
No need to buy an external sd-card. Your phone has an internal storage which can be accessed / mounted via CWM. Just boot the phone in recovery mode (ClockworkMod) and head over to 'mounts and storage > mount USB storage'. Now use your cable to connect your device to your computer. It should only take a few seconds until your phone pops up in Windows Explorer. Then you're able to put your ROM .zip file onto the card. Choose to 'unmount USB storage' and install the ROM. Don't forget to wipe before Much luck,
experience7
Dude...you learn something new every day.....if I'd have known that when I had my issue (similar to the OP) I wouldn't have had to f**t around with odin installing a firmware in order to get at least *something* back on my phone to get it to boot again.....thanks for the share....gonna have to remember this tip
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
No, always go stock.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from...this is not even my S2
Why should he go to stock if he desires his phone to run a custom ROM? Sounds like he accidentally formatted the system partition plus the internal storage. As soon as he flashes the CM zip file his phone has a working system directory and he should be able to. boot it up again
I was trolling keith.
Sent from...this is not even my S2
I guess the only reason for your inappropriate posts is to push your post count to its limit. Well done, sir.
That's so funny, why would anyone do that?
I want you to tell me, you got 2 min to make something up.
Be creative.
Sent from...this is not even my S2
Off-topic, 'nuff said. Now stop it please
Thought so
Be good now.
Sent from...this is not even my S2
experience7 said:
No need to buy an external sd-card. Your phone has an internal storage which can be accessed / mounted via CWM. Just boot the phone in recovery mode (ClockworkMod) and head over to 'mounts and storage > mount USB storage'. Now use your cable to connect your device to your computer. It should only take a few seconds until your phone pops up in Windows Explorer. Then you're able to put your ROM .zip file onto the card. Choose to 'unmount USB storage' and install the ROM. Don't forget to wipe before Much luck,
experience7
Click to expand...
Click to collapse
So I''ve done the USB storage method, shoving CyanogenMod, SuperSU and GApps onto the internal. I installed SuperSU and now I'm trying to install CyanogenMod and I'm getting the (Status 7, Installation Aborted) message. Am I missing anything required?
Re download the ROM, the files might be corrupted.
Sent from...this is not even my S2
No need to copy over SuperSU. There's a superuser app coming with CM Alternatives are in Google Play Store
Well, you're running Jeboo kernel. Stock based kernels sometimes cause errors when you try to install a custom ROM. Don't get me wrong, CM comes with its own kernel anyways, but there's still the chance that the installation fails like in your case. To solve your problem flash a custom kernel (I'd choose dorimanx - you can grab a copy here: dorimanx.shine.sk <- 8.x is for stock based ROMs, 9.x is for custom ROMs) So pick 9.35 and flash it. Then reboot the phone in recovery mode again. You've got a different Recovery system now. This time it will allow you to install CM followed by GApps
Edit: Don't forget that Dorimanx will be overwritten by CM kernel as soon as you flash CM. But if you're new to CM I recommend this kernel anyways
experience7 said:
No need to copy over SuperSU. There's a superuser app coming with CM Alternatives are in Google Play Store
Well, you're running Jeboo kernel. Stock based kernels sometimes cause errors when you try to install a custom ROM. Don't get me wrong, CM comes with its own kernel anyways, but there's still the chance that the installation fails like in your case. To solve your problem flash a custom kernel (I'd choose dorimanx - you can grab a copy here: dorimanx.shine.sk <- 8.x is for stock based ROMs, 9.x is for custom ROMs) So pick 9.35 and flash it. Then reboot the phone in recovery mode again. You've got a different Recovery system now. This time it will allow you to install CM followed by GApps
Edit: Don't forget that Dorimanx will be overwritten by CM kernel as soon as you flash CM. But if you're new to CM I recommend this kernel anyways
Click to expand...
Click to collapse
Hmm I seem to be getting the Status 7, Installation aborted problem with Dorimanx too :S I even tried 9.34 and redownloading 9.35
EDIT: Managed to get back to CyanogenMod. Thank you
Nice one mate. ...now if you want to go back to stock there's a handy little app called Mobile Odin. ...look for the thread here on XDA......
Sent from my rooted, de bloated, stock JB powered S2 via PhilZ kernel and XDA developers app
Related
Hi all,
I purchased the Rom Manager, and flashed the new clockworkmod recovery, but like this I cannot acces my older nand backups.
I have a few, older backups, and maybe i will need them ! What can I do?
thx
legycsapo said:
Hi all,
I purchased the Rom Manager, and flashed the new clockworkmod recovery, but like this I cannot acces my older nand backups.
I have a few, older backups, and maybe i will need them ! What can I do?
thx
Click to expand...
Click to collapse
If you made your older backups with AmonRA recovery you won't be able to use them in CWM recovery. You will have to flash AmonRA to use them. That is pretty simple, thanks to ciaox who shared flashable recovery zips here.
borrow thread awhile,
just now i root my phone using gingerbreak 1.2
after root,then download rom manager free version from market
then i choose flash clockwork Mod recovery,and choose lg optimus one as my device
and wait it to load finish the bar
after finish,it shows this :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
so now what should i do ??
XeactorZ said:
borrow thread awhile,
just now i root my phone using gingerbreak 1.2
after root,then download rom manager free version from market
then i choose flash clockwork Mod recovery,and choose lg optimus one as my device
and wait it to load finish the bar
after finish,it shows this :
so now what should i do ??
Click to expand...
Click to collapse
Are you sure you granted ROM Manager superuser privileges?
22VIN said:
Are you sure you granted ROM Manager superuser privileges?
Click to expand...
Click to collapse
just now don't have
so i root my phone again,and its work already
but after i flash clockworkMod recovery,and reboot into recovery
then i use the guide that u last time teach me at my thread
22VIN said:
1. root your phone
2. install a custom recovery (the easiest way is to install ROM Manager from Market and select "flash cwm recovery"
3. download a custom kernel (I'm using franco's) and copy it on your sdcard
4. boot into custom recovery: turn off your phone and then press vol down + home + power and release at lg logo
5. make a nand backup
6. wipe dalvik cache (in cwm recovery it's in advanced menu)
7. select install zip from sdcard, select your kernel from the sdcard and flash it.
8. start your phone and install setcpu; use max 729mhz
That's it
Click to expand...
Click to collapse
so after finish flash franco kernel
i choose reboot,then my phone stuck at LG logo
i wait very long,then unplug the battery and put it back
and turn on phone as usual,same also stuck at there
i do it a lot times
so i give up,and do a Nand restore,but its also stuck at LG logo ==
then the only way is i go emergency mode and use kdz updater to flash back
luckily my phone no problem
so now got other way to flash custom recovery instead using rom manager ??
because i google it quite a lot people also got the same case as me,stuck at LG logo after reboot ~
XeactorZ said:
so after finish flash franco kernel
i choose reboot,then my phone stuck at LG logo
i wait very long,then unplug the battery and put it back
and turn on phone as usual,same also stuck at there
i do it a lot times
so i give up,and do a Nand restore,but its also stuck at LG logo ==
then the only way is i go emergency mode and use kdz updater to flash back
luckily my phone no problem
so now got other way to flash custom recovery instead using rom manager ??
because i google it quite a lot people also got the same case as me,stuck at LG logo after reboot ~
Click to expand...
Click to collapse
Well I also got stuck at lg logo on some occasions when flashing kernels/themes, it happens. But I can't understand why you got stuck after restoring backup.
When did you make your backup? Did you make a backup before flashing stuff on your ROM?
And what do you mean by "got stuck"? Sometimes it takes longer to boot after you flash something. How much did you wait to consider that your phone is stuck?
To install a custom recovery the classic way check out step 3 here.
By the way, your problems aren't related to the recovery's installation. You're saying you rebooted into recovery, so the instalation of CWM with ROMmanager was succesful.
22VIN said:
Well I also got stuck at lg logo on some occasions when flashing kernels/themes, it happens. But I can't understand why you got stuck after restoring backup.
When did you make your backup? Did you make a backup before flashing stuff on your ROM?
And what do you mean by "got stuck"? Sometimes it takes longer to boot after you flash something. How much did you wait to consider that your phone is stuck?
To install a custom recovery the classic way check out step 3 here.
By the way, your problems aren't related to the recovery's installation. You're saying you rebooted into recovery, so the instalation of CWM with ROMmanager was succesful.
Click to expand...
Click to collapse
i also duno why after i restore from the nand backup that i do yesterday night still stuck at LG logo
the backup i make at yesterday night,which before flashing franco kernel
yes i got a backup before flashing franco kernel,and i no flash any ROM coz i wan use stock rom
erm,my phone stuck at LG logo more than 10minutes already,its too long than normal
i know sometime will take longer time,but sure won't over 10minute
so now i gonna try another method to flash custom recovery
thanks for ur link ~
Hey guys. I keep getting this ridiculously annoying error when trying to either install 'Cyanogen' or even 'Cyanogen Nightie' as well as just boot into Recovery Mode.
I open Rom Manager (Premium).
I have installed Clockwork Recovery Mod (Version 4.0.1.5)
I click 'Reboot Into Recovery'
The phone reboots.
But when booting into recovery mode I get this error:
Android system recovery <3e>
Enter: OK Key, Select : Vol UP / Vol Down
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
_______________________________________________________
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
E: Failed to verify whole-file signature
E: Signature verification failed
Installation aborted.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is really annoying the hell out of me. Rom Manager is the most expensive app I have ever purchased and I can't even install Cyanogen... I've spent all night trying to find a way around this. I'm not your average noob with such things either, usually I can find a way around an issue myself. This however, has just got me entirely stumped..
I've even tried rebooting by pressing:
Volume UP (NOT DOWN)
Home
Power
and THEN trying to install from .zip (update-cm-7.1.0-GalaxyS2-signed.zip)
I get the same error. No matter what I try.
Please don't tell me to boot into CWM first and then do any of this. I CAN'T EVEN BOOT INTO CWM.
I am really frustrated over this, I need a cold beer and a maybe even a cone. I've done everything I can to figure this out.
I am running:
Samsung Galaxy S 2 (Rooted) [GT-I9100]
Android Version:
2.3.4
Baseband Version:
I9100XXKi1
Kernel Version:
2.6.35.7-I9100XWKI4-CL575468
[email protected] #2
Build Number:
Gingerbread.XWKi4
I have installed CWM through Rom Manager... as I stated. I can't boot into it either by selecting the option (as before stated) or when I select 'Install from SD Card' then choose the .zip (which I named above in bold)
Same error, all the time. I have absolutely NO idea what to do. I also can't 'disable verification' because I can't even get into Clockwork Recovery... so frankly none of this works.
Does anyone have a PROPER way to get around this without already having a way into Clockwork Recovery or anything. Because frankly I can't even get into recovery to install Cyanogen..
Please help me out, I'm about to put my SGS2 in the toaster -.-
Before you ask I've read every other thread here and in other forums on the internet with other people having the same problem. All of them are outdated and 95% of them are for people who already have at least some version of CWM installed and they can boot into it.
Flash the zImage of your Root kernel via CWM with option Flash Kernel. Before that I hope you know you need to flash the Stock Kernel (Kernel of your current ROM, i.e KI4 I believ) via Odin.
After doing that READ THIS,
Q: How do I install this?
A:
Latest version: http://download.cyanogenmod.com/?device=galaxys2 (for when nightlies are working normally)
Check the md5sum if you want to be sure that the download worked (different OSes have different programs that do md5, on ubuntu it is md5sum that you run against the zip you download and compare to the md5sum number shown on the download website). ROMManager does this automatically for ROMs you download via ROMManager.
- First time flashing CM 7 to your Galaxy S2 (or coming from another ROM)?
Only for the International version of the Galaxy S2, US versions like the AT&T have their own device specific builds.
Note: sometimes you need to flash twice back to back without a reboot in the middle. The install should take a little time, if it happens very quickly, flash again.
Install via ClockworkMod (do not use ROMManager for initial install):
Make sure you're running a rooted device.
Root your device and install ClockworkMod Recovery (http://forum.xda-developers.com/showthread.php?t=1118693)
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition) - do it for real.
Install the ROM from internal sdcard using ClockworkMod Recovery.
Do not reboot! We mean it - do nothing except choose zip and continue next step (if you come back to us with permission issues in install, we will know you did not read the directions and will call you an idiot). If it just plain hangs, reboot directly back into ClockworkMod recovery and continue at the next step.
Install the ROM from internal sdcard using ClockworkMod Recovery, again (due to a bug in the install).
Reboot
Install the Google Addon through ROMManager which is easiest, but you can
download the gapps.zip and install via ClockworkMod recovery instead.
Click to expand...
Click to collapse
Assuming you get to my post beneath the 700px signature above:
leijonasisu said:
I open Rom Manager (Premium).
I have installed Clockwork Recovery Mod (Version 4.0.1.5)
I click 'Reboot Into Recovery'
Click to expand...
Click to collapse
CyanogenMod 7 (w/ Gingerbread 2.3.7) for Galaxy SII Q&A
atinm said:
do not use ROMManager for initial install
Click to expand...
Click to collapse
oinkylicious said:
Assuming you get to my post beneath the 700px signature above:
Click to expand...
Click to collapse
Anything is over pixelated for you when you have a decade old internet connection. Stop barking about the same thing.
Hey.
I have followed your 'Q: How do I install this?' instructions to the letter, however every time I try this method I get stuck in a boot loop.
Any suggestions?
Thanks.
---------- Post added at 02:28 PM ---------- Previous post was at 01:39 PM ----------
Hey.
I have followed your 'Q: How do I install this?' instructions to the letter, however every time I try this method I get stuck in a boot loop.
Any suggestions?
Thanks.
I've solved some hours ago:
flash again the CF-Root for your firmware via Mobile Odin, DO NOT USE ROM MANAGER, then via the app called CWM(CF-Root install this),click reboot recovery and then flash the rom you want to install via CWM(You should put the zip file in the /sdcard folder)
its not cwn recovery screen
Did anyone noticed in screeshot, its not CWM recovery screen but android system recovery e3.
ok i am very new to this too. but i am having same problem of signature verification, and daa i then noticed i was imnot in.cwm recovery. some how i am unable to get cwm recovery screen.
I own a Samsung Galaxy S II i777. I've already rooted the phone. I'm about to flash UnNamed ROM over my stock ROM, but I have questions before I feel comfortable doing anything.
(1) I read about backing up my data and stock ROM. I've backed up my data using Titanium Backup, but the ROM is giving me problems. I've installed the ROM Manager app (via Android Market) and flashed the Clockwork Mod 3e through the app. But when I try to backup my stock ROM, at the reboot screen the app gives me an error "E: can't find signature" or something like that, and the backup fails. How can I make a backup (I think it's called a Nandroid backup?) of my stock ROM in case I want to revert?
(2) The procedure I want to follow for everything is here. My goal is to flash anything & everything without incrementing the flash counter (using Mobile Odin Lite, as outlined in the procedure). Is this realistic? What, in general, should I avoid so as not to increment the flash counter?
(3) The app I'm going to be using to flash is Mobile Odin Lite. Is that the same as flashing with Clockwork Recovery? Does using Clockwork Recovery Mod to flash increment the flash counter?
(4) Let's say I want to install a different custom ROM, or an update for UnNamed ROM comes out. Will I be able to do that with Mobile Odin Lite, and without incrementing the flash counter? Can I just flash (using Mobile Odin Lite) over the previous ROM?
Completely_Clueless said:
I own a Samsung Galaxy S II i777. I've already rooted the phone. I'm about to flash UnNamed ROM over my stock ROM, but I have questions before I feel comfortable doing anything.
(1) I read about backing up my data and stock ROM. I've backed up my data using Titanium Backup, but the ROM is giving me problems. I've installed the ROM Manager app (via Android Market) and flashed the Clockwork Mod 3e through the app. But when I try to backup my stock ROM, at the reboot screen the app gives me an error "E: can't find signature" or something like that, and the backup fails. How can I make a backup (I think it's called a Nandroid backup?) of my stock ROM in case I want to revert?
(2) The procedure I want to follow for everything is here. My goal is to flash anything & everything without incrementing the flash counter (using Mobile Odin Lite, as outlined in the procedure). Is this realistic? What, in general, should I avoid so as not to increment the flash counter?
(3) The app I'm going to be using to flash is Mobile Odin Lite. Is that the same as flashing with Clockwork Recovery? Does using Clockwork Recovery Mod to flash increment the flash counter?
(4) Let's say I want to install a different custom ROM, or an update for UnNamed ROM comes out. Will I be able to do that with Mobile Odin Lite, and without incrementing the flash counter? Can I just flash (using Mobile Odin Lite) over the previous ROM?
Click to expand...
Click to collapse
(1) DO not use rom manager. It has problems on this phone. You can install a custom kernel and then make a nandroid backup of the stock system plus custom kernel. However, there is a return to stock package which you can flash to get total stock.
(2) (3) (4) Please go to the guide you linked, scroll down to the bottom of the guide, and read step 4. Then if you have an analytical mind and want to know more about how things work, click on the link at the end of the Discussion section titled "Here is some additional information for noobs about the tools and techniques used in this guide."
Please be assured that you can flash custom binaries without tripping the flash counter. That is what the guide is all about, after all.
creepyncrawly said:
(1) DO not use rom manager. It has problems on this phone. You can install a custom kernel and then make a nandroid backup of the stock system plus custom kernel. However, there is a return to stock package which you can flash to get total stock.
Click to expand...
Click to collapse
Ah OK, and I think I did find the return-to-stock package; is it the "Odin3 One-Click Downloader Stock I-777 UCKH7 No Bootloaders" you posted here?
creepyncrawly said:
(2) (3) (4) Please go to the guide you linked, scroll down to the bottom of the guide, and read step 4. Then if you have an analytical mind and want to know more about how things work, click on the link at the end of the Discussion section titled "Here is some additional information for noobs about the tools and techniques used in this guide."
Please be assured that you can flash custom binaries without tripping the flash counter. That is what the guide is all about, after all.
Click to expand...
Click to collapse
Okay, sorry for coming across as noob. I read the noob-explanation post, and from what I gather, as long as I don't use Odin or Heimdall, I shouldn't trip the flash counter and get that yellow exclamation point? EDIT: Nevermind, figured this one out.
Now, I've already installed ROM Manager and used it to flash the custom kernel. If I uninstall using Titanium Backup, will that undo the flashing that it did? It won't conflict when I flash using Mobile Odin Lite, will it?
Completely_Clueless said:
Now, I've already installed ROM Manager and used it to flash the custom kernel. If I uninstall using Titanium Backup, will that undo the flashing that it did? It won't conflict when I flash using Mobile Odin Lite, will it?
Click to expand...
Click to collapse
I'm not sure what you mean. To my knowledge you cannot install a kernel with ROM Manager. However, I have not installed or even looked at the program since I acquired the SGS II in early October. When I used ROM Manager on the Captivate in Fall 2010, when Captivate was still on Eclair (Android 2.1), it used the stock recovery to install a custom recovery as an update. But since our phone has 3e recovery, requiring files that are flashed to be signed by Samsung, my understanding it that ROM Manager can not flash a ClockworkMod Recovery onto our phone. To my knowledge, you can flash a custom kernel on our phone only with Odin3, Heimdall, adb, Android Terminal Emulator, Mobile Odin, or ClockworkMod Recovery.
I don't see why you would keep ROM Manager, since there is very little that it can do to help you.
As far as how to proceed, I think it would be advisable to follow the Guide from the beginning, even if it means doing something redundantly.
Oops, I think I got the terminology mixed up. I meant I used ROM Manager to flash ClockworkMod Recovery.
Here's a picture of what I'm talking about (taken from the ROM Manager page on the Android Market website, not my phone, but the option is still the same). I did the first option, and I was just wondering if the "flash" was permanent even if I uninstalled the app itself using Titanium Backup. I was just concerned that if I flashed using two tools, then there would be a problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But I followed your guide, and I just successfully flashed my first custom ROM! My phone booted without a hitch, so I assume flashing ClockworkMod Recovery with ROM Manager first didn't have any negative impact. I also didn't see any yellow exclamation point.
Thank you very much for your help ! I've bookmarked your threads about going back to stock and about how to flash without increasing the flash counter.
Not sure if you actually flashed anything from rom manager, regardless of what the screen says.
Anyway, success is sweet. Enjoy your phone.
After spending two whole days trying to flash my Galaxy S2 with MIUI 2.1.6 (also tried the latest Cyanogenmod and DarkyROM) and with nothing to show for it, it's time to ask for help.
My main goal is to install MIUI 2.1.6. The starting point is stock Gingerbread 2.3.5 (XXKI3). This is what I did:
- flashed stock 2.3.5 (XXKI3) via Odin
- rooted XXKI3 with CF-Root
- copied MIUI 2.1.6 on SD card (the zip file)
After that comes the part where I have to flash ClockworkMod Recovery and that's where the troubles start. My phone comes with 3e recovery which gives me the "failed to verify whole file signature" error after I try to flash CWM via the ROM Manager.
After browsing XDA forums, a lot of reading and trying both methods of overriding that bloody signature check (Untermensch's script method and Existenz's method of placing the Recovery file in /system/bin), none of them worked for me.
Untermensch's script method starts doing its thing but at one point it gives me an error message and suggests that my phone isn't rooted (which it definitely is, as I'm able to use Superuser, Root Explorer, AdBlock and every other root-only app).
Existenz's method of manually putting the Recovery file in /system/bin swaps the 3e recovery with CWM (orange letters, if I recall correctly), but after doing all the neccessary wipes and installing MIUI (or Cyanogenmod) from a zip file on my SD card, all I get is a boot loop. DarkyROM won't install at all, it simply gives me an error at the very beginning of the installation process.
At this moment I'm running stock Gingerbread 2.3.5, rooted by CF-Root and flashed with SpeedMod kernel. When I try to enter recovery, I'm getting CWM Recovery 5.0.2.3 (blue letters). However, if I try to wipe the phone and install MIUI from zip, all I get is another boot loop. And I'm back on 3e recovery.
Perhaps it's also worth mentioning my 3e recovery menu has no "reinstall packages" option which was mentioned in several threads on this forum that were vaguely related to my issue.
Anything I'm missing? Any ideas at all?
Thanks in advance and kind regards!
YouLaxy said:
My main goal is to install MIUI 2.1.6
Click to expand...
Click to collapse
Try the MIUI forums for support.
1) Flash CF-root
2) Copy the Miui zip into the sdcard
3) flash the Miui zip twice
4) reboot into CWM recovery
5) Flash the miui zip again
6) wipe cache/data
7) reboot into miui
oinkylicious said:
Try the MIUI forums for support.
Click to expand...
Click to collapse
The thing is, I'd ultimately like to be able to install any custom ROM, not just MIUI. So far none of them worked (MIUI, Cyanogenmod, DarkyROM), I'm guessing due to that nasty 3e recovery (nothing else comes to mind)
veyka said:
1) Flash CF-root
2) Copy the Miui zip into the sdcard
3) flash the Miui zip twice
4) reboot into CWM recovery
5) Flash the miui zip again
6) wipe cache/data
7) reboot into miui
Click to expand...
Click to collapse
I'll give that a go later today and post back the results. Cheers!
Nope, that didn't work. After flashing with MIUI twice via CWM and powering the phone off, I'm unable to enter recovery to flash MIUI for the third time, as the phone goes into boot loop.
Any other ideas, anyone? Thanks in advance!
Your not using rom manager are you?
Maybe its a bad miui download, where did you get the zip from?
Nope, I'm flashing the zip via CWM recovery, so after turning the phone off and doing the three-key thingy. I got the MIUI zip from MIUIAndroid.com and downloaded it three times, just to be sure there's not an issue with the zip.
YouLaxy said:
Nope, I'm flashing the zip via CWM recovery, so after turning the phone off and doing the three-key thingy. I got the MIUI zip from MIUIAndroid.com and downloaded it three times, just to be sure there's not an issue with the zip.
Click to expand...
Click to collapse
I have no clue then, it should work
Maybe you could try galnet miui?
Have you tried flashing other custom roms, eg hyperdroid or checkrom?
I did try to flash CyanogenMod (ended up with a boot loop, just like MIUI), as well as DarkyROM (got an error shorty after the start of the installation, can't remember what it was anymore). Seems my SGS2 simply isn't up for anything but stock ROMs. Bastard.
YouLaxy said:
I did try to flash CyanogenMod (ended up with a boot loop, just like MIUI), as well as DarkyROM (got an error shorty after the start of the installation, can't remember what it was anymore). Seems my SGS2 simply isn't up for anything but stock ROMs. Bastard.
Click to expand...
Click to collapse
CM7 does need doubleflashing, so when you go into CWM double flash the zip before wiping/rebooting.
And what was the error on the stock rom? Have you tried others.
Try this.
Its the resurrection edition of darkyrom. Its something to fall back on when other roms failI, it completely repartions your phone and should replace 3e with CWM and you'll have a nice darky custom rom
Make sure you follow the instruction to the letter
http://www.darkyrom.com/community/i...arkyrom-hd-v1-0-r5-resurrection-edition.6565/
veyka said:
CM7 does need doubleflashing, so when you go into CWM double flash the zip before wiping/rebooting.
And what was the error on the stock rom? Have you tried others.
Click to expand...
Click to collapse
Just tried to doubleflash CM7 and then do the wipe. Ended up in yet another boot loop (and unable to get into recovery). Then I restored the stock 2.3.5, rooted with CF-Root and tried to flash DarkyROM (via CWM recovery, of course). This is the message that it gives me:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So now I'm back on stock 2.3.5 once again. Blimey.
thteddieboii said:
Try this.
Its the resurrection edition of darkyrom. Its something to fall back on when other roms failI, it completely repartions your phone and should replace 3e with CWM and you'll have a nice darky custom rom
Make sure you follow the instruction to the letter
http://www.darkyrom.com/community/i...arkyrom-hd-v1-0-r5-resurrection-edition.6565/
Click to expand...
Click to collapse
I'll give it a go in a couple of minutes and post back with the results. Thanks for your input!
Wait you have an sgs 2? Well the darkyrom your trying to flash in your pic is for the galaxy one
This will seriously mess up your phone.. try the link.I posted should work
thteddieboii said:
Wait you have an sgs 2? Well the darkyrom your trying to flash in your pic is for the galaxy one
This will seriously mess up your phone.. try the link.I posted should work
Click to expand...
Click to collapse
Hahah, really? wow, hes lucky it didnt brick it, good old status 0 (oops should have noticed that, it means that the firmware isnt for this the phone you are trying to flash it on)
veyka said:
Hahah, really? wow, hes lucky it didnt brick it, good old status 0 (oops should have noticed that, it means that the firmware isnt for this the phone you are trying to flash it on)
Click to expand...
Click to collapse
Yeah I noticed cause it was darky 10.2.2 which I remember from my s1 days of flashing.. I was wondering why the 0 was there. Very lucky its not bricked
Let us.know how you go with the darkyrom HD resurrection.. darkyrom HD is for galaxy s 2 just in case you wanted to update in future and so you don't get confused
Feeling like a bit of a dumbass right about now. And just when I thought I tripple checked everything... Okay, that explains the DarkyROM issue, however still no clue what's wrong with MIUI and/or CM7. I'm sure I downloaded correct versions of those
I'm downloading the ROM from your link at this very moment, trying it shortly.
YouLaxy said:
Feeling like a bit of a dumbass right about now. And just when I thought I tripple checked everything... Okay, that explains the DarkyROM issue, however still no clue what's wrong with MIUI and/or CM7. I'm sure I downloaded correct versions of those
I'm downloading the ROM from your link at this very moment, trying it shortly.
Click to expand...
Click to collapse
All good. Its not hard to get mixed up. I remember how overwhelming it was when I first started learning to flash
Bit scary for a while til I learnt more and understood things better
Hmm I'm not to sure about the miui issue or cm7
Never used them, except for cm9 cause I like the aosp ICS..
Let us know how darkyrom HD goes for ya
Well, that worked. Had to flash twice to get it to work, though (got stuck on step #14 for 10 scary minutes and then just turned the phone off an reflashed)
I'll give DarkyROM a go. I do have one more question though. If I decide to try to flash MIUI once again, would it be enough to boot into CWM recovery and try to install it from zip (so, without doing anything to my DarkyROM installation) or do I have to go back to stock ROM for that?
Thanks a ton for your help guys, my SGS2 can run custom ROMs after all! Horray!
Hello.
I am currently trying to bring my Samsung Galaxy SII (GT-I9100) to a current CM version. The phone is completely untouched and has never had any custom upload or anything similar.
The problem now is, while there are loads and loads of guides out there, all of them seem very old - and different. One says i need heimdall, other says odin, others seem way easier just adding the files to my SD card and installing through recovery - and basically all that does is confusing the hell out of me.
So, first things first - the most important thing seems to get root access - i've done that successfully using the "How To Root Samsung Galaxy SII GT-I9100"
The one thing that confuses me now is - where is CWM? I thought i installed it using that root method?
Another method i tried before updated my recovery while it was running from the stock one to CWM - but after rebooting into recovery it was the stock one again.
SO i am even more confused now as before.. At least i hope that my phone is and stays rooted, so that is a plus.
The question now is, what am i missing?
Were all of these CWM things i've "installed" just temporary? Where do i get the full version, and how do i install it?
Basically what i'm asking is, is there a current guide for all of the flashing? Can anyone maybe guide me through it? I mean, nowadays it seems the S2 should be flashed very easily, and i'm guessing it's just getting the correct CWM version and flashing it via recovery - but since i'm not sure, i'm asking for some guidance.
The easiest way to get a CWM custom recovery is to flash PhilZ recovery through your standard stock 3e recovery.
Look for your Android build number (under settings>>about device/phone) then go to the PhilZ thread......
http://forum.xda-developers.com/showthread.php?t=1877270
download the matching kernel/recovery zip (NOT .tar), copy to a micro SD card (or possibly even internal storage I can't be sure of that....It's been a while since I rooted my S2), boot into recovery and flash......
Simple as......
Edit....The thread states 'external sd card' so forget about using internal storage......
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks a lot, worked flawlessly!
I hope it is okay that i just ask about the next steps here.. Since i immediately ran into new problems.
So, i booted into the CWM and tried to push my cm package that i want to install via mfastboot-v2 and it failed stating the following errors:
Warning: No file_contextdetected filesystem ext4 for /dev/block/mmcblk0p9
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E: Error in /tmp/update.zip
(Status 7)
Installation aborted
It seems obvious ofcourse that i need to do a factory reset before, but the S2 is probably susceptible to a superbrick and i should not do that factory reset on my stock rom.
The question is - what now? Also i was not able to mound the external SD card in CWM.
ThePatchelist said:
Thanks a lot, worked flawlessly!
I hope it is okay that i just ask about the next steps here.. Since i immediately ran into new problems.
So, i booted into the CWM and tried to push my cm package that i want to install via mfastboot-v2 and it failed stating the following errors:
Warning: No file_contextdetected filesystem ext4 for /dev/block/mmcblk0p9
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
E: Error in /tmp/update.zip
(Status 7)
Installation aborted
It seems obvious ofcourse that i need to do a factory reset before, but the S2 is probably susceptible to a superbrick and i should not do that factory reset on my stock rom.
The question is - what now? Also i was not able to mound the external SD card in CWM.
Click to expand...
Click to collapse
1) I can't comment on mfastboot v2 as I have no experience of using it.
2) which CM package are you trying to install?
3) the super brick bug only affects android 4.0.4 Icecream Sandwich....
And PhilZ kernels have removed/patched the EMMC_cap_erase command that activates the 'bug' anyway.
4) if your CM package came from XDA or the CM website, then it should install through PhilZ recovery.
5) what are you trying to achieve that requires external SD to be mounted?
The cm i'm trying to install is the latest stable one, being cm-12.1-20151116-SNAPSHOT-YOG7DAO1JN-i9100
About the superbrick, i did not know that the philZ kernels fixed that, good to know.
And i tried to simply put the ROM image onto the external SD card to simply flash it from the CWM - but since that external SD card cannot be mounted, i tried using the adb push method.
Could i use the internal storage and simply apply update from zip file from there? Thought that might be an issue due to it being erased in the process?
CM 12 is lollipop base isn't it? The last CM I flashed to my S2 was 11.....but then my eldest son asked me for a phone so I returned it to stock and loaned it to him.
Obviously haven't been able to flash it since.
As for CM12, I've read that overall, it's not as stable as 11 (contains more bugs) and is heavier on the battery. I'm sure I've also read that the S2s memory partitions have to be re - mapped @gsstudios maybe you can help here as I'm not sure)
As far as I am aware, installing the rom from internal storage shouldn't be an issue......The only time data on that partition is compromised is if you perform a factory reset....and you would only have to do this (if at all) AFTER you have installed the rom. I'm also fairly sure that you have to have a specific version of CWM installed to be able to install newer CM roms, but again, I'd have to suggest waiting for @gsstudios to comment here......
ThePatchelist said:
The cm i'm trying to install is the latest stable one, being cm-12.1-20151116-SNAPSHOT-YOG7DAO1JN-i9100
About the superbrick, i did not know that the philZ kernels fixed that, good to know.
And i tried to simply put the ROM image onto the external SD card to simply flash it from the CWM - but since that external SD card cannot be mounted, i tried using the adb push method.
Could i use the internal storage and simply apply update from zip file from there? Thought that might be an issue due to it being erased in the process?
Click to expand...
Click to collapse
Hi,
There are a few points I will give:
- cm-12.1-20151116-SNAPSHOT-YOG7DAO1JN-i9100 is an old build of CM12.1. It doesn't have all of the latest features like Isorec (isolated recovery for TWRP 3 recovery support), hence it should be avoided. Instead, use CM12.1 Unofficial by CNBLACK or CM12.1 Unofficial by Markox89. Although they are unofficial builds, these are considered more stable than the CM12.1 snapshot build being offered.
- You can install CM12.1 via internal storage. It won't get erased during the flashing process, instead, this only happens when you re-partition your phone using a .pit file. You will need to increase you system partition size in order to flash gapps (google play store, etc) using Lanchon's repit tool. Documentation is already provided.
- Once you've installed CM12.1, it is recommended to change the recovery to TWRP (preferred) or CWM. This is because CM recovery is very limited and will become a problem later if you decide to flash CM13.
gsstudios
Hey there again.
First of all, thank you very much! I successfully flashed one of the cm's you posted @gsstudios and so far it works.
Now though i am struggling with the TWRP installation since i have to increase the partition size for gapps.. As i've read it TWRP must be flashed via heimdall (back to square one..) and there i am having problems with the connection (claiming interface error, was googling for 2 hours now, nothing helped)
Basically what i am now looking for is a way to get TWRP without having to flash via heimdall, but rather installing it through the cm recovery which seems not possible?
I am really sorry that i continue to post my issues here since i'm sure you guys helping out are really annoyed by this.. But currently i am again running my head into a brick wall not knowing how to proceed :/
Edit: jesus..
I have no idea how or why, but apparently i got it now.
I installed ROM manager externally and it showed me that i have CWM and TWRP already installed.. At first i was confused and set up TWRP as my recovery, but that only booted into the normal cm recovery. Then i tried the CWM one and when going into recovery i am now in TWRP.. Am reformatting my partitions, so far without any errors.
I am not less confused but close to being happy. As soon as i can flash gapps afterwards all of this is over and done.
Thanks still, for all the help guys! And sorry for being the usual annyoing user..
No problem fella....but in future, STAY AWAY from rom manager.....It sometimes doesn't play nice with the S2.
In the past I've read that it can 'fubar' recovery and can cause boot loops. (So up til now, you've been lucky).
For further info, Heimdall simply isn't needed.....The primary method of TWRP installation is via Odin. I'm a bit concerned that rom manager said you have both CWM and TWRP installed....Some investigation is in order....
Whichever recovery you boot into with the button combination is the recovery you have installed.....