I think I know the solution in that case. Flashing a new modem should fix it.
If you don't have one to hand, a very recent one can be found here. Flash it (as PHONE) using Odin.
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Problem backing up ROM on Galaxy S II via ROM Manager
- Thread starter borgmanjayce
- Start date
-
- Tags
- samsung galaxy s2
I think I know the solution in that case. Flashing a new modem should fix it.
If you don't have one to hand, a very recent one can be found here. Flash it (as PHONE) using Odin.
borgmanjayce
Newbie
I take it that if I flash the modem using Odin, it shouldn't affect the VillainROM ROM? I also take it that I should leave Odin as is without ticking any boxes?
Correct on both counts. Just run Odin with the default settings.
borgmanjayce
Newbie
I tried to flash the Modem and I got the following message:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File Analysis..
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
So it looks like it didn't work. I'm going to try and connect it again and check what I did wrong before trying it again.
EDIT: I made a mistake in that I didn't know I needed to go into Download Mode so I followed the instructions followed here and it flashed properly.
EDIT 2: Just tested it and it still says that the Baseband is unknown which means that the SIM is still unrecognised. I read in the VillainROM thread that the Modem you gave me a link to is supposed to work with it.
EDIT 3: I managed to get the Version information using the *#1234# trick found in the link that I posted in this post.
This is the information that I managed to get:
PDA: I9100XWKI4
PHONE: Unknown
CSC: Unknown
Build Info: Wed Sep 14 20.34:11 KST 2011
I'm not going to give up and send it to the insurance company. I'm determined to get this fixed with the help of the people here as well as the people at XDA-Developers where the Modem is concerned because I now know the Modem somehow got corrupted, as long as that can be fixed, all I need to do is back it up to my Dropbox account for safe keeping.
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File Analysis..
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
So it looks like it didn't work. I'm going to try and connect it again and check what I did wrong before trying it again.
EDIT: I made a mistake in that I didn't know I needed to go into Download Mode so I followed the instructions followed here and it flashed properly.
EDIT 2: Just tested it and it still says that the Baseband is unknown which means that the SIM is still unrecognised. I read in the VillainROM thread that the Modem you gave me a link to is supposed to work with it.
EDIT 3: I managed to get the Version information using the *#1234# trick found in the link that I posted in this post.
This is the information that I managed to get:
PDA: I9100XWKI4
PHONE: Unknown
CSC: Unknown
Build Info: Wed Sep 14 20.34:11 KST 2011
I'm not going to give up and send it to the insurance company. I'm determined to get this fixed with the help of the people here as well as the people at XDA-Developers where the Modem is concerned because I now know the Modem somehow got corrupted, as long as that can be fixed, all I need to do is back it up to my Dropbox account for safe keeping.
M
Member518272
Guest
I've had all of the above problems and mine still isn't fixed, managed to back up current ROM via CWM, but can't install any other because that involves using ROM manager and that keeps throwing up the error at the start of the thread 
Why not use CWM to install them? Or boot into recovery and use install ZIP from sdcard?
Anythingbuthum
Lurker
I had the same problem here me out please.
So i rooted my samsung galaxy s2 with this method: http://forum.xda-developers.com/show....php?t=1125414
then reinstalled the original kernel to get rid of the yellow triangle.
Then I thought it would be best to back up everything before I mess around and i understand Rom manager could do that, so I:
Installed the app,
Selected flash clockwork mod recovery option in rom manger,
Chose backup current rom
it came up with this error:
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
So i found this thread which sometime said would fix it on some forum
http://www.inspiredgeek.com/2011/06/...-s2-ii-how-to/
did what it said, went into rom manager selected backup current rom again, and it froze with a yellow triangle and android guy showing. I switched it off and on again then it went through the backup process...
Have I done things correctly?
how can I get rid of the yellow Triangle again and still beable to backup?
Was the freeze screen one moment away from me bricking my phone?
and finally how do I restore the back up I made if anything goes wrong?...
I mainly rooted to freeze bloat ware and get access to certain apps so I'm not planning to do anything drastic.
Thank you for your time.
So i rooted my samsung galaxy s2 with this method: http://forum.xda-developers.com/show....php?t=1125414
then reinstalled the original kernel to get rid of the yellow triangle.
Then I thought it would be best to back up everything before I mess around and i understand Rom manager could do that, so I:
Installed the app,
Selected flash clockwork mod recovery option in rom manger,
Chose backup current rom
it came up with this error:
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
So i found this thread which sometime said would fix it on some forum
http://www.inspiredgeek.com/2011/06/...-s2-ii-how-to/
did what it said, went into rom manager selected backup current rom again, and it froze with a yellow triangle and android guy showing. I switched it off and on again then it went through the backup process...
Have I done things correctly?
how can I get rid of the yellow Triangle again and still beable to backup?
Was the freeze screen one moment away from me bricking my phone?
and finally how do I restore the back up I made if anything goes wrong?...
I mainly rooted to freeze bloat ware and get access to certain apps so I'm not planning to do anything drastic.
Thank you for your time.
SuperOneClick seems to cause as many issues as it solves. I advise using the CF-Root method - it's nice and simple, and installs a GS2-compatible version of ROM Manager (CWM) and Clockworkmod Recovery.
You were halfway there in removing the boot triangle; after flashing the stock kernel back with Odin you have to reflash the root kernel using CWM to regain the custom recovery.
You were halfway there in removing the boot triangle; after flashing the stock kernel back with Odin you have to reflash the root kernel using CWM to regain the custom recovery.
Anythingbuthum
Lurker
I see...
Could you link me which CF-root download I need pls
hate to be a hassal but my kernal now says this and i'm unsure:
2.6.35.7
codeworkc@cyanogenmod #12
I used XWKF3 kernels to root the first time if thats any help.
Also before I do this CF-root do i need to doing to my phone before I start up Odin and flash it like I have been doing?
Thanks in advance.
Could you link me which CF-root download I need pls
hate to be a hassal but my kernal now says this and i'm unsure:
2.6.35.7
codeworkc@cyanogenmod #12
I used XWKF3 kernels to root the first time if thats any help.
Also before I do this CF-root do i need to doing to my phone before I start up Odin and flash it like I have been doing?
Thanks in advance.
It looks like ROM Manager has installed a CM7-compatible kernel along with the recovery. Unfortunately that gives problems with the stock ROM.
Flash the TAR file contained within this package via Odin (with handset in Download Mode) and you should be good to go.
Once it's flashed and rebooted you'll find a CWM app in the drawer. That's a version of ROM Manager that's been modified to work correctly with the GS2.
p.s. you'll have the "yellow triangle of root" back again but as it's only a cosmetic blip don't worry about it - it's easy to get rid of once you've got everything stabilised.
Anythingbuthum
Lurker
Great the black colors are bk to normal on the device and I've created a new bkup with CWM...
so now say if I wanted to put: Lite'ning Rom on there.
I just install the rom how it says in the thread and if I want to get rid of it I just restore my backup?
Can I install modded rom's on top of modded rom's or is it best to just restore backup each time?
Correct. The CWM backup will restore your handset to how it was... apps, data, settings... it's an exact mirror of the device state at the moment of backup.
That's strongly not advised. It's always safest to do a full wipe (dalvik-cache, cache and data) when flashing a different firmware. It's a bit of extra work setting everythign up again, but you avoid the chance of leftovers from the previous firmware causing problems with the new one.
Updating to a later version of the same ROM is, however, usually safe with just a dalvik and cache wipe.
Anythingbuthum
Lurker
Thank you very much all is running ok 
Just a quick note CF-root comes with CMW manager app but its been taken off when I wiped the data and cache as the social hub was forcing to close... (fixed after wipe)
is there anyway to get this app back, I know I can still back up through recovery mode but its a brilliant app.
Just a quick note CF-root comes with CMW manager app but its been taken off when I wiped the data and cache as the social hub was forcing to close... (fixed after wipe)
is there anyway to get this app back, I know I can still back up through recovery mode but its a brilliant app.
Reflashing the CF-Root package via Odin is the easiest method unless you have it backed up with TiBackup.
Hey all
Please please help. Im brand new to this and after research I wanted to install a custom rom.Heres what I done and the problem.
I rooted the phone ok using insecure kernal XWKI4 (which is the same as the stock kernal) then installed rom manager to back up but got this message on phone reboot
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Which looks like the same as the OP. Im so deflated its silly.Ive read all these replies but Im so confused with all the jargon.Can anyone tell me what I need to do to get back on track in really simple terms please ?
I will really really appreciate any help.Thanks a lot in advance
Joe.
Please please help. Im brand new to this and after research I wanted to install a custom rom.Heres what I done and the problem.
I rooted the phone ok using insecure kernal XWKI4 (which is the same as the stock kernal) then installed rom manager to back up but got this message on phone reboot
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Which looks like the same as the OP. Im so deflated its silly.Ive read all these replies but Im so confused with all the jargon.Can anyone tell me what I need to do to get back on track in really simple terms please ?
I will really really appreciate any help.Thanks a lot in advance
Joe.
Cheers for the reply slug.
There is no cwn in my apps, just rom manager. Its driving me nuts.
Right Ive taken a couple pictures to show exactly whats happening
1. The phone is in root mode (has been for 3 days now), I go into rom manager and press back up current os and I get this
2. Then I try turning off phone, holding vol up,power and menu button as Ive read you can back up that way but I get this
How hard can it be to back it up ? Please help this dumb dumb.
vantiveman
Member
Hi Guys,
Facinating thread, and very informative.
I have an unlocked (Sim-Free) Galaxy S2 with KI4 Kernale and KI4 Build (after recent OTA update from 2.3.3 to 2.3.4).
Like the previous guy, I also flashed an insecure kernal, also at KI4, so that I could use root apps.
I have CWM in apps drawer and have also purchased the premium version of Rom Manager.
I also wanted to backup my existing ROM from within ROM Manager and got exactly the same as at the start of the thread.
I have taken a backup using Titanium, and have also backed up using CWM app. Titanium allows the backup folder to be selected, so I have backup up to external SD. The backup I took using CWM did not allow the destination to be selected so I went to the intyernal SD card so, because of free space problems, I have moved it to the external SD.
I gather that the cause of the original problem posted about error messages trying to backup under ROM manager is simply a problem with ROM Manager on Galaxy S2? and that I can just use CWM to do the same thing.
My question (finally!) is that if I get bricked at some point in the future (I will eventually try a new ROM) and can only use the CWM recovery option to boot into, it won't be able to find the backup because I have moved it to the external card - so in that case, how do I recover from being bricked? Do I always have to have the CWM backup on the internal card?
If that is the case, wouldn't it be a good idea for the developer of CWM to allow the location of the backup to be selected, or, at least, have the option of a default folder on internal OR external card?
Many Thanks,
Alan.
Facinating thread, and very informative.
I have an unlocked (Sim-Free) Galaxy S2 with KI4 Kernale and KI4 Build (after recent OTA update from 2.3.3 to 2.3.4).
Like the previous guy, I also flashed an insecure kernal, also at KI4, so that I could use root apps.
I have CWM in apps drawer and have also purchased the premium version of Rom Manager.
I also wanted to backup my existing ROM from within ROM Manager and got exactly the same as at the start of the thread.
I have taken a backup using Titanium, and have also backed up using CWM app. Titanium allows the backup folder to be selected, so I have backup up to external SD. The backup I took using CWM did not allow the destination to be selected so I went to the intyernal SD card so, because of free space problems, I have moved it to the external SD.
I gather that the cause of the original problem posted about error messages trying to backup under ROM manager is simply a problem with ROM Manager on Galaxy S2? and that I can just use CWM to do the same thing.
My question (finally!) is that if I get bricked at some point in the future (I will eventually try a new ROM) and can only use the CWM recovery option to boot into, it won't be able to find the backup because I have moved it to the external card - so in that case, how do I recover from being bricked? Do I always have to have the CWM backup on the internal card?
If that is the case, wouldn't it be a good idea for the developer of CWM to allow the location of the backup to be selected, or, at least, have the option of a default folder on internal OR external card?
Many Thanks,
Alan.
vantiveman
Member
By the way, for finding CF Root - ' links in the sticky thread'.
What is the sticky thread? I would also like to find this if it is able to put back missing apps in the apps drawer. Could be useful if I lose them after any other flashing that I might do.
Thanks,
Alan.
What is the sticky thread? I would also like to find this if it is able to put back missing apps in the apps drawer. Could be useful if I lose them after any other flashing that I might do.
Thanks,
Alan.
I wanted to ask this too but didnt wanna sound silly lol.
But yeah what is the sticky thread please ?
Look at the top of this sub-forum's index page - there's a topic entitled Samsung Galaxy S2 Root Guide "stuck" at the very top.
vantiveman
Member
Great. Many thanks.
By the way, could you please advise for my previous question (though I think I know the answer..)
My question (finally!) is that if I get bricked at some point in the future (I will eventually try a new ROM) and can only use the CWM recovery option to boot into, it won't be able to find the backup because I have moved it to the external card - so in that case, how do I recover from being bricked? Do I always have to have the CWM backup on the internal card?
If that is the case, wouldn't it be a good idea for the developer of CWM to allow the location of the backup to be selected, or, at least, have the option of a default folder on internal OR external card?
All the best,
Alan.
By the way, could you please advise for my previous question (though I think I know the answer..)
My question (finally!) is that if I get bricked at some point in the future (I will eventually try a new ROM) and can only use the CWM recovery option to boot into, it won't be able to find the backup because I have moved it to the external card - so in that case, how do I recover from being bricked? Do I always have to have the CWM backup on the internal card?
If that is the case, wouldn't it be a good idea for the developer of CWM to allow the location of the backup to be selected, or, at least, have the option of a default folder on internal OR external card?
All the best,
Alan.
The current version of CWM Manager (v3.0) does exactly that.
It also displays both internal and external SD backups in the "Restore" screen, and the latest ClockworkMod Recovery (v.5.0.2.7) also gives the option to restore from either location.