So i was loading up a new rom after GPS wouldnt work on the previous one, got everything downloaded to internal sd and was verifying it was their via cw rom manager app. I then clicked on the link to boot into recovery and the phone came up with sgs2 and the little triangle but then nothing, pulled the battery did it manually same thing, no matter what i did it wont boot normally anymore or can i get into recovery. I am able to get into download mode so i am trying to recover my semi bricked phone. Has anyone had this happen before? For reference this is the rom i was in http://forum.xda-developers.com/showthread.php?t=1436854
This was the first time i ever started messing with the rom manager app and now it will be my last.
You are not the first and probably wont be the last. Rom Manager should not be used on the i9100. It will cause plenty of problems when used to install roms and such.
Kaze105 said:
You are not the first and probably wont be the last. Rom Manager should not be used on the i9100. It will cause plenty of problems when used to install roms and such.
Click to expand...
Click to collapse
While I don't like or use ROM Manager, this isn't entirely true.
The issue is that CF-Root/CWM4 is NOT compatible with ROM Manager. So if you rooted with CF-Root, or have CWM4 installed, then try to use ROM Manager, that is where your issues start.
Apparently you can use ROM Manager on the i9100 as long as you don't have CWM4 or CF-Root.
But I don't recommend using ROM Manager anyways, as most flavors of CWM do everything ROM Manager can do anyways.
It happened alot with me as my previous device was HTC desire hd. I was used to rom manager.
Boot your device into download mode. Run addin n make sure you downloaded Cwm too. Hook the usb, able to your phone. Through addin flash Cwm. Next boot into recovery rock n roll
Sent from my GT-I9100 using xda premium
Rom manager is horrible, i always tell people to root and flash following xda guides, Rom manager is responsible for a lot of issues on phones, id avoid it completely if you can.
I hear it and read it often too, rom manager cause plenty of issues, i wouldn't use it.
Binford... more power!
Well got it fixed last night, was 3am when i finally got to bed, and this morning i re rooted it and and im recovering my system now. Thanks for the help guys.
Related
Hi all, I have a problem that I am struggling to find an answer for.
When ever I try to do a back up using ROM Manager I get :-
opening update package...
verifying update package...
E:failed to verify whole-life signature
E: signature verification failed
Installation aborted
When I first got my phone I rushed into rooting it and flashing it without really knowing in my head what I was doing but just following instructions off the net. The rom I installed was :-
lite'ning rom v6.1 xxkh3
I also installed kernal '2.6.35.11-ninphetamine-2.0.5+ [email protected]#', as I believe this was the correct one at the time.
My baseband version is 'I9100xxkh3' (If needed)
From the research I have done I think it is the kernel that is causing the problem as I have read you need a compatible cwm kernel and I'm guessing this isn't???
I'm wanting to flash a newer ROM now but as I'm more clued up(but even more confused) I want to create a back up first but as I can't I'm stuck with this ROM.
Can any one help me here regards what kernel I need? If that is the suspected problem??
Thanks
Mark
Your rom manager is causing a lot of problems as most roms do not work very well with it.
If you are rooted you can use cwm to make a back up.
the kernal is not causing the problem as you can mix and match kernal with out any problems.
Stop using rom manager, just boot into recovery if you want to install/backup roms and wipe phone.
^^ +100
I've only used Rom Manager twice. First time to to a backup, broke pretty much everything. No recovery & bootloop. Obvious incompatibility issue at the time between it & CW Recovery. Until recently was doing everything thru recovery. Tried flashing a kernel this week thru Rom Manager again & it worked just fine.
Obviously you're having problems with it, so rather than tempt fate, I'd stick with Peachpuff's most excellent suggestion of doing everything thru recovery rather than risk causing yourself unnecessary grief.
Thanks cosmic blue!!
Followed your instructions and worked first time.
I confirmed this by going into rom manager and it now shows a back up.
I always thought Rom manager and cwm was the same thing but now I know.
Is Rom manager still something worth installing though? Or is it just a reliability?
Thanks again all those that helped.
Mark
I would uninstall RM & just use CWM, as suggested earlier. You might want to install Mobile Odin (Market), in case at some point you need to flash another kernel that includes CWM.
Sent by Tapatalk from my rotary phone, using sparks.
Your welcome
Rom manager is not worth installing as there are other ways of doing the same functions of rom manager.
using cwm, titantium back up and root explorer will do the same job as a rom manager.
titantiuam baclk up and root explorer are free apps on the market there are also paid versions of the apps which are upgrades.
try the free versions, if you like them then buy the pro versions.
Hey all,
I'm very new to Cyanogen, so sorry if this is a very n00b question.
The ROM Manager doesn't appear to work. It keeps telling me I'm not running ClockWorkMod recovery, and cannot connect to the web to download. I purchased the premium version thinking it would solve this (as well as to support the dev), but no luck. Is it just an issue with the nightlies not capable of handling ROM manager yet, or is it a setting of some sort that I'm neglecting? It's not a huge deal, but it looks like such a nice, simple way to stay up-to-date with the nightly builds as opposed to updating through CWM, wiping, etc.
I saw a post mentioning to go into developer tools and enable root access. The closest I found was in settings and I allowed apps and ADB root access, but this didn't help.
Any suggestions would be greatly appreciated, thanks!
I'm a bit confused, Why do you require ROM manager? The CWM that is built in with the ICS Kang releases should be doing everything that is required, then again, your reply would matter.
I think I am having the same issue. When I try to Flash ClockworkMod Touch in Rom Manager it keeps telling me I need to first install ClockworkMod Recovery even though I have Recovery 5.5.0.4 currently installed. It did the same thing when I had Recovery 4.0.0.4 installed.
I even tried to "Flash ClockworkMod Recovery" (First option in ROM Manager) and it does nothing.
Any ideas?
BEcause the same menu is in the CWM recovery lol
I'm following one of the threads that updates the kang build every 3 days, and as opposed to having to boot through CWM, wipe, install, then re-install apps and replace widgets, I thought I could update through ROM Manager instead.
It sounds like Sn0warmy and I are having similar issues.
From what I've heard the ROM Manager doesn't really work for the tab yet. If you want to update without replacing all your apps you can just flash the zip file in CWM without doing a wipe. If it causes problems then you could do a wipe & reflash afterwards.
Dolfan058 said:
I'm following one of the threads that updates the kang build every 3 days, and as opposed to having to boot through CWM, wipe, install, then re-install apps and replace widgets, I thought I could update through ROM Manager instead.
It sounds like Sn0warmy and I are having similar issues.
Click to expand...
Click to collapse
ROM manager works but it's wonky on the ICS kangs. It doesn't do anything that you can't already do in recovery, so there's no real advantage anyways. Oh, and don't use ROM manager to install a new recovery, and CWR touch doesn't work for the GT10.
^You saved me the trouble of insisting Why thank you good sir.
Thanks for the replies. I'll keep updating through CWM.
Coffeebeans, obviously I'm following your thread (thanks for the good work!) and I tried flashing over once but I got a ton of process media FCs so I figured wiping was the best way to go and have done so ever since. Probably should invest in titanium backup at this point so I don't have to reinstall from market everytime I wipe.
Thanks again for the help y'all.
It worked once with 4/17 build of CM9. After that, it has never worked again. It boots into recovery and pretends its flashing, but stops half a second later and restarts.
Something odd happened today when I tried to update. It rebooted and phone locked up and screen went black. I took out the battery and put it back in then held up and power to go into CWM. All of a sudden Rom Manager took over and flashed the rom as well as the additional zips successfully and rebooted. Everything works.
CWM tries to flash from /emmc. Rom Manager tries to flash from /sdcard and fails. It may be due to the swapped mount points on CM9. in CWM they are still swapped, even if you check the use internal storage box and everything shows up properly in CM9.
This is the first time I rooted my phone and I used step 6 on this link in your forum http://forum.xda-developers.com/showthread.php?t=1238070 . Everything went fine but I then downloaded rom manager and when I select flash clockworkmod it only gives me the choice of choosing the samsung epic4g or the samsung galaxyS i9000. It does not give me the option of choosing the fascinate. I selected the i9000 but stopped there because I figured that I should try to fix this situation and be able to select the fascinate, before I move foward. Please help me move foward so I will be able to put a rom on my phone. Any help would be greatly appreciated.
Thanks
lucash312 said:
This is the first time I rooted my phone and I used step 6 on this link in your forum http://forum.xda-developers.com/showthread.php?t=1238070 . Everything went fine but I then downloaded rom manager and when I select flash clockworkmod it only gives me the choice of choosing the samsung epic4g or the samsung galaxyS i9000. It does not give me the option of choosing the fascinate. I selected the i9000 but stopped there because I figured that I should try to fix this situation and be able to select the fascinate, before I move foward. Please help me move foward so I will be able to put a rom on my phone. Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
rom manager is useless for the fascinate...
I also ran into this issue. If your CWM is not "sticky" (it goes to System Recovery <3e> when you reboot recovery), you must flash the appropriate version of CWM with ODIN before a ROM flash. (CWM ALL.tar for bml roms [anything that is not cm7, MIUI, or ICS] or cwm4_fixed_for_cm7.tar for MTD ROM's [cm7, MIUI, or ICS])
MultipleMonomials said:
I also ran into this issue. If your CWM is not "sticky" (it goes to System Recovery <3e> when you reboot recovery), you must flash the appropriate version of CWM with ODIN before a ROM flash. (CWM ALL.tar for bml roms [anything that is not cm7, MIUI, or ICS] or cwm4_fixed_for_cm7.tar for MTD ROM's [cm7, MIUI, or ICS])
Click to expand...
Click to collapse
if the op would of followed the guides instructions correctly, he would not of ran into that issue in the first place...
droidstyle said:
rom manager is useless for the fascinate...
Click to expand...
Click to collapse
But if that's the case, why does Koushik make a ROM for the fascinate and have it available on his site?
(Does the Epic4G simply represent all CDMA phones, and the i9000 GSM? Don't see why that would matter anyway tho)
(I can't post a direct &#% link yet, but it's on his website.
This makes absolutely no sense!? He's got ROMs up there for just about every Android phone on the market, all to be used with ROM Manager.
I wanted to install it via Odin but naturally that would be too simple: it's a zip file and Odin won't recognize anything but tar and 2 others formats.
You can flash any .zip ROM with CWM. There's no need for ROM Manager. BTW, you can post a link if you uncheck "parse links in text automatically."
Nymblz said:
But if that's the case, why does Koushik make a ROM for the fascinate and have it available on his site?
(Does the Epic4G simply represent all CDMA phones, and the i9000 GSM? Don't see why that would matter anyway tho)
(I can't post a direct &#% link yet, but it's on his website.
This makes absolutely no sense!? He's got ROMs up there for just about every Android phone on the market, all to be used with ROM Manager.
I wanted to install it via Odin but naturally that would be too simple: it's a zip file and Odin won't recognize anything but tar and 2 others formats.
Click to expand...
Click to collapse
all you need to do is boot into cwm recovery via the power menu and flash away. the problem with rom manager on the fascinate is getting into the right recovery...causes more problems than its worth on this device. make sense yet? probably not since you have not been down this road yet, but many of us have. so take the advice given or dont and learn the hard way.
Honestly, I am trying to take the advice given but not all of it fit my situation.
I'm definitely something of a noob to Android (Not to linux or IT though). I've had my phone for all of a month and rooted it only days ago.
It's all starting to come together, finally. It's tricky for a noob because there are so many different versions of the phone hardware, versions of Android, this or that kernel that only works with these ROMs, old/newer versions of those, old posts and advice, newer posts with adjusted advice.. etc.. It's been a week long crash course!
Anyhoo, I couldn't flash/upgrade CWM because it didn't stick from the original Odin install. When I rebooted, I'd always return to the stock <3e> recovery. Even after two more installs of CWM via Odin.
I used the cwm-recovery-all.tar in your guide, Droidstyle. (great job BTW)
I followed the directions in Section 6 to the letter. I even printed it out and highlighted key sections.
So you see, I was in a catch-22; I needed CWM to flash CWM? Odin was my only option at that point.
Then I read on another thread here about renaming the /system/recovery-from-boot.p script, and installing CWM once more.
That worked, so now I can finally boot into CWM recovery like a happy man. (I also tried a more specific version of CWM for good measure: cwm4-bml-i500.tar, not really sure if that made a difference)
So I made my first real nandroid backup last night.
Next on my list is a new kernel. Still deciding between KGB, lean, and whatever else is out there.
I still don't get the whole mess with ROM Manager though. I agree with you, DS, I just don't get why he'd have zips for every phone under the sun but his own app doesn't seem to allow them to be used. It's bizarre. The latest reviews on the market are not flattering either.
Nymblz said:
It's tricky for a noob because there are so many different versions of the phone hardware
Click to expand...
Click to collapse
You are on the Samsung Fascinate. If it is Verizon then it is model number i500. If it doesnt say Fascinate or i500 it isn't for your device and you don't need to worry about it. If you flash something that isn't stated as being for the i500 or VERIZON Fascinate then you will have a lovely new temporary paper weight.
Nymblz said:
Anyhoo, I couldn't flash/upgrade CWM because it didn't stick from the original Odin install. When I rebooted, I'd always return to the stock <3e> recovery. Even after two more installs of CWM via Odin.
I used the cwm-recovery-all.tar in your guide, Droidstyle. (great job BTW)
I followed the directions in Section 6 to the letter. I even printed it out and highlighted key sections.
Click to expand...
Click to collapse
You couldn't have followed it to the letter because it is a well known fact that if you boot up with a stock kernel still flashed it will replace your recovery. Droidstyle certainly knows this and certainly accounted for it in his guide. So, you need to either boot directly into CWM or flash a non-stock kernel prior to rebooting the phone.
Nymblz said:
Then I read on another thread here about renaming the /system/recovery-from-boot.p script, and installing CWM once more.
That worked, so now I can finally boot into CWM recovery like a happy man. (I also tried a more specific version of CWM for good measure: cwm4-bml-i500.tar, not really sure if that made a difference)
So I made my first real nandroid backup last night.
Click to expand...
Click to collapse
Yeah it sounds like that will work...not the most elegant way to take care of it...but it sounds like it would be okay.
Nymblz said:
Next on my list is a new kernel. Still deciding between KGB, lean, and whatever else is out there.
Click to expand...
Click to collapse
We already talked about the kernel situation. Consider Geewiz if you want something thats all-in-one and pretty much impossible to mess up. KGB is good. Leankernel always gave me the best battery life but YMMV.
Nymblz said:
I still don't get the whole mess with ROM Manager though. I agree with you, DS, I just don't get why he'd have zips for every phone under the sun but his own app doesn't seem to allow them to be used. It's bizarre. The latest reviews on the market are not flattering either.
Click to expand...
Click to collapse
He showed no interest in helping the devs here get ROM manager working (again) on the phone. If you gave him money, blame him for not providing the support and resources to get it working on this phone. Some people are umm...."lacking in people skills."
Oh, and as great as the Gingerbread ROMs are...the mtd ICS roms blow them out of the water
Hey guys,
I just installed Rom Manager and wanted to try out to make a backup of my current Rom. The Rom Manager asked me if I wanted to Install Clock Mod Recovery, which was kind of strange since I thought I had it installed with the Siyah Kernel 3.3.3d but I proceeded and installed it, and after that it asked my Galaxy Model, I picked Galaxy SII of course and then it rebooted. However after the Galaxy SII Logo (With the yellow Triangle) nothing happened. Black Screen. So I tried to go into Recovery Mode. Doesn`t work either. Normal Boot also doesn`t work any more.
Download Mode is working however.
So I thought to try to flash the Siyah Kernel trough Odin to get it to work the way it was. Should I flash the Kernel or try to flash a normal Firmware through Odin?
Any advice on how to proceed?
Flash the kernel first. Hopefully that fixes things. If it doesn't work, then back to stock, re-root your phone & restore a backup/flash whatever rom you want to use.
Don't use Rom Manager on a phone that has CWM/Recovery installed, it's not uncommon for Rom Manager to break CWM and/or cause bootloops (as you've discovered). I'd freeze/uninstall Rom Manager if you're using a kernel that has CWM/Recovery.
MistahBungle said:
Flash the kernel first. Hopefully that fixes things. If it doesn't work, then back to stock, re-root your phone & restore a backup/flash whatever rom you want to use.
Don't use Rom Manager on a phone that has CWM/Recovery installed, it's not uncommon for Rom Manager to break CWM and/or cause bootloops (as you've discovered). I'd freeze/uninstall Rom Manager if you're using a kernel that has CWM/Recovery.
Click to expand...
Click to collapse
Flashing the Kernel didn`t work, same as before
Going back to Stock ICS Samsung Firmware now and will apply root afterwards. I Just hope that works and that I didn`t brick my phone.
You should be fine, I can't recall seeing any instances of Rom Manager bricking a phone outright when this happens. It's just really annoying that you have to go back to stock/re-root/restore backup/etc. Happened to me when I tried Rom Manager out not long after I got my phone when I was running Miui GB. Pain in the neck but I'd be surprised if you can't fix it ;-)
MistahBungle said:
You should be fine, I can't recall seeing any instances of Rom Manager bricking a phone outright when this happens. It's just really annoying that you have to go back to stock/re-root/restore backup/etc. Happened to me when I tried Rom Manager out not long after I got my phone when I was running Miui GB. Pain in the neck but I'd be surprised if you can't fix it ;-)
Click to expand...
Click to collapse
Ok everything works now again, thanks for the support
Installed Stock ICS 4.0.3 Firmware but then I got stuck at the Galaxy SII Bootanimation.
Then I flashed Chainfire Kernel and got into CWM and then without a full wipe just installed my old rom and it worked. All apps are still there.
One thing I know for sure though, I will never use Rom Manager again
Good news. Not losing your apps & so on certainly saves you a fair bit of time. No probs, happy to help. Yeah, use CWM/Recovery to do all your flashing/backups/restores/etc instead of Rom Manager. Main thing is you recovered fairly easily ;-)
New to this - I really apologize if this has been covered before but I've been searching all evening and not coming up with a definitive answer.
What's the easiest way to remove a custom recovery (like twrp) and go back to stock? Still on the stock rom, just have custom recovery. I manually deleted a nandroid backup using a file manager from my sd card yesterday, and now when booting into recovery it sits on the twrp screen for easily 10-15 minutes. I can't fathom why that would have an effect on the start up time but that's all I can think of that changed. I've tried re-installing twrp via goomanager - no change.
Is there a way to do so without using usb? I'm curious because the first S4 I had, the usb port went bad after only a month and I was in a panic that I wouldn't be able to get it back to stock (until I finally got it to work long enough to flash it with odin). Really don't want to risk that happening again.
Looking to run some roms once I think I understand at least half of what I'm doing, but trying to be cautious. I'd like to keep twrp but I want to make sure it's working right by loading a clean install of it.
Thanks in advance.
A lot of users are experiencing the lag with TWRP version installed by Goo Manager - (TWRP 2.6.0).
The link below has a flashable zip to version 2.5.0.2, this version seems to be stable and doesn't lag at the TWRP screen for most people including myself.
I would try flashing this and I think it will solve your problem.
http://forum.xda-developers.com/showpost.php?p=45006486&postcount=289
gadget! said:
A lot of users are experiencing the lag with TWRP version installed by Goo Manager - (TWRP 2.6.0).
The link below has a flashable zip to version 2.5.0.2, this version seems to be stable and doesn't lag at the TWRP screen for most people including myself.
I would try flashing this and I think it will solve your problem.
http://forum.xda-developers.com/showpost.php?p=45006486&postcount=289
Click to expand...
Click to collapse
Thank you. I'm a little stumped on what to do with the zip now that I have it though and all my searching for "loading recovery with goo manager" just shows the method to load the newer version. Or if you're supposed to load it via pc, what do you use? Odin doesn't like any of those file types.
Sorry if this is a dumb question. Probably just not searching for the right thing.
bretbretterson said:
Thank you. I'm a little stumped on what to do with the zip now that I have it though and all my searching for "loading recovery with goo manager" just shows the method to load the newer version. Or if you're supposed to load it via pc, what do you use? Odin doesn't like any of those file types.
Sorry if this is a dumb question. Probably just not searching for the right thing.
Click to expand...
Click to collapse
You flash it via recovery. Put in your sdcard/internal boot to recovery amd use the install zip option. Navigate to where it is and flash away.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free
bretbretterson said:
Thank you. I'm a little stumped on what to do with the zip now that I have it though and all my searching for "loading recovery with goo manager" just shows the method to load the newer version. Or if you're supposed to load it via pc, what do you use? Odin doesn't like any of those file types.
Sorry if this is a dumb question. Probably just not searching for the right thing.
Click to expand...
Click to collapse
Yes, it is a flashable zip, just flash it in the recovery you have now.
I found this post based on the OP's original question, "how to remove TWRP recovery".
I have been flashing rooted ROMs for a while now via ODIN, but am just now starting to foray into the realm of custom recoveries. Before I install TWRP though, I wanted to know how to remove it just in case something ever goes wrong. That is, I've been avoiding the use of a custom recovery so far because if something ever happened to my device, I could just flash the stock ROM, and having already used Triangle Away, Samsung will never be the wiser and would service my device, but with a custom recovery installed, they would be able to see I'm not running totally stock.
So, is there a way to completely return my device to 100% stock after installing TWRP? And if so, how would I go about doing that?
My device is a Samsung Galaxy Note 10.1 GT-N8013, currently running a root injected stock ROM, 4.1.2
EDIT: I just noticed that this is in the S4 forum, which my N8013 obviously is not, but the answer to my question should be the same regardless, yes?
margentieri said:
I found this post based on the OP's original question, "how to remove TWRP recovery".
I have been flashing rooted ROMs for a while now via ODIN, but am just now starting to foray into the realm of custom recoveries. Before I install TWRP though, I wanted to know how to remove it just in case something ever goes wrong. That is, I've been avoiding the use of a custom recovery so far because if something ever happened to my device, I could just flash the stock ROM, and having already used Triangle Away, Samsung will never be the wiser and would service my device, but with a custom recovery installed, they would be able to see I'm not running totally stock.
So, is there a way to completely return my device to 100% stock after installing TWRP? And if so, how would I go about doing that?
My device is a Samsung Galaxy Note 10.1 GT-N8013, currently running a root injected stock ROM, 4.1.2
EDIT: I just noticed that this is in the S4 forum, which my N8013 obviously is not, but the answer to my question should be the same regardless, yes?
Click to expand...
Click to collapse
Answer would be device specific
Sent from my cm_tenderloin using xda app-developers app
Thanks Gadget, Hex. TWRP 2.5.0.2 works great. But just for future reference, is the only way to revert to the stock recovery by flashing a stock device image via odin over usb? So if the USB port were to fail entirely, I would be SoL - correct?