I have:
Infuse
Infused ROM V2
So today I downloaded "ROM Manager" and "ROM Manager Premium" from the market. AFAIK, this means they are up to date as of today.
Then installed CWM Recovery.
Then installed the 3e mod fix.
Then booted to CWM and did a nandroid backup.
Then booted normally.
Then attempted to install MYUI via ROM Manager download.
It bricked the phone.
Restored the phone with Odin.
Rooted.
Then installed both ROM Managers.
Then installed CWM Recovery.
Then installed the 3e mod fix.
Then booted to CWM and did a restore from the new backup done earlier in the day.
Now it just hangs at the Samsung splash screen.
Any ideas? I have a LOT of investment in the backed up ROM and don't want to lose it.
CZ Eddie said:
I have:
Infuse
Infused ROM V2
So today I downloaded "ROM Manager" and "ROM Manager Premium" from the market. AFAIK, this means they are up to date as of today.
Then installed CWM Recovery.
Then installed the 3e mod fix.
Then booted to CWM and did a nandroid backup.
Then booted normally.
Then attempted to install MYUI via ROM Manager download.
It bricked the phone.
Restored the phone with Odin.
Rooted.
Then installed both ROM Managers.
Then installed CWM Recovery.
Then installed the 3e mod fix.
Then booted to CWM and did a restore from the new backup done earlier in the day.
Now it just hangs at the Samsung splash screen.
Any ideas? I have a LOT of investment in the backed up ROM and don't want to lose it.
Click to expand...
Click to collapse
I dont know what ALOT of investment is.......but what i think happened here is this<<
You were on Gingerbread right, Infused v2.x.x and you made a Nandroid(thats fine)
u installed miUi and didnt have the luck you wanted...Thats fine
You went back to stock, and rooted and modded the Recovery so you could restore your nandroid....Thats fine
But if you went back to stock(Froyo Right) and try to load up a Gringerbread Nandroid on top it shouldnt work. Nandroids only back up the ROM not the Kernel......so you were in a sense trying to run a Gingerbread Rom on a Stock Froyo Kernel......
Go into CWM flash your Kernel, or use odin and flash a Ginger Kernel then go into CWM and RESTORE.
Happy FLashing
Didn't know that! That may explain a lot of my ROM frustrations.
I'll try this and report back.
Off to go find a suitable kernel....
I really should get my post count up so I can get past this horrible 10 post restriction.
Did you try initiating the flash through CWM or through ROM Manager? Honestly I don't prefer to do any work via ROM Manager, I always have more luck going through CWM and starting a flash from there. Kernel is the first place I'd start but you should also Factory Wipe and Cache Wipe each time you move between ROMs, sometimes you get very lucky and don't need to, most times you bork your phone, and if you're nandroiding back from a backup wiping before you restore is good practice just to make sure you don't leave anything behind from your old ROM.
I installed a gingerbread kernel:
http://forum.xda-developers.com/showthread.php?t=1212485
Version 1.1.
But it didn't work out.
So now I'm fighting with trying to get a stock Infused V2 ROM on there.
No luck yet. Once I do, I'll try the recovery again.
Btw, I'm using CWM for everything.
Go to mounts and storage in clockwork recovery then select format system then do your nand restore ...
Sent from my Samsung Infuse 4G - 1.6ghz
Wow, I was totally making some rookie (which I am) Android mistakes today.
Every time I tried to restore the backup image, I was doing it in CWM by selecting "install .zip from SD card". When I SHOULD have been using the "backup/restore" function.
I'm up & running again. All original apps/settings are restored. Great!
Now to start breaking things again, since I know how to restore from backup now.
Related
So here's the deal:
I've been working with a pretty decently running version of Cognition for the last two weeks on my Captivate. I decided to give Perception II a try and check out some gingerbready goodness. That's where the problem started. Perception for some reason wouldn't allow me back into Recovery Mode no matter what I try so I forced the phone to download and flashed back to 2.1 stock with ODIN. I then reinstalled CWM Recovery and tried to flash back to my Cognition backup I made in ROM manger.
The process looks like everything completed fine but when my phone boots, it loads the AT&T screen for a minute or two and then reboots into recovery mode.
What's the deal?
The details I had when using Cognition was:
CWM Recovery (I believe with LagFix)
Overstock Kernel
It didn't work with my original 2.2 backup either, I still get the same boot into recovery problem.
Any ideas?
Nandroid backups don't actually restore the rom, just your settings and **** of that particular rom. You have to Flash cognition then restore the backup and it'll be like you never changed anything.
Handalaan said:
So here's the deal:
I've been working with a pretty decently running version of Cognition for the last two weeks on my Captivate. I decided to give Perception II a try and check out some gingerbready goodness. That's where the problem started. Perception for some reason wouldn't allow me back into Recovery Mode no matter what I try so I forced the phone to download and flashed back to 2.1 stock with ODIN. I then reinstalled CWM Recovery and tried to flash back to my Cognition backup I made in ROM manger.
The process looks like everything completed fine but when my phone boots, it loads the AT&T screen for a minute or two and then reboots into recovery mode.
What's the deal?
The details I had when using Cognition was:
CWM Recovery (I believe with LagFix)
Overstock Kernel
It didn't work with my original 2.2 backup either, I still get the same boot into recovery problem.
Any ideas?
Click to expand...
Click to collapse
Let me guess, you didn't convert back to RFS before flashing??
Try Factory reset. And don't use the backup you have for Cognition, Flash a fresh full ROM. Your backup could be messed up.
EDIT: Studa beat me to it.. Grrrr
studacris said:
Nandroid backups don't actually restore the rom, just your settings and **** of that particular rom. You have to Flash cognition then restore the backup and it'll be like you never changed anything.
Click to expand...
Click to collapse
This is exactly what I needed to do. Apparently, (after finding a link I somehow overlooked before posting this) it had something to do with the format of the partition so upgrading the Stock to Cognition forced the RFS to EXT3 change allowing -all- of my backups to work. Thanks guys for getting me in the right direction.
Perhaps Im a little Slow
So Im suffering the same issue. Running Serendipity 7 update 2
I looked down at my phone one day and it was in clockwork recovery v2.5.1.2
I figured I had loaded it by an errant button press. So I selected reboot system now. It goes back into Clockwork right after the serendipity 7 splash screen.
Tried Factory Reset
Tried doing a restore
Tried doing a serendipity 7 re install Original and update.
I can install zips from sd card including the external one.
Any Recommendations ?
Could ROM Manager fake Flash Clockworkmod recovery be responsible for bricking phones on LG update? Let me explain what I mean - Lots of people, like myself, installed ROM Manager and its CWM because we did not know it's not real Flash. Then We switched to "real" CWM. Now the question is when we do normal stock recovery in order to get official GB update, does this CWM of ROM manager still remains in the phone? If so, could it be that it contributed to the troubles updating through LG tool? How can I make sure I removed it from the phone?
Thanks!
Yes. Many people have confirmed that not having the stock recovery on the device is a road to Bricksville. Even though you are fake flashed there is code inserted somewhere to redirect to the fake flash, and the recovery images for flash (normally installed every boot) have been deleted or renamed. You should flash stock recovery with NVFlasher to make sure you are back at a clean stock recovery before using the LG Update tool.
Thanks but what I mean is that AFTER I realized it's fake flash I installed "real" CWM. So when I do stock on this "real", does CWM rom manager still remains in the phone and how can I remove it?
post deleted by poster
so I am a little confused I used CWM to make a backup before I did anything to my phone. And I was already on the 2.3.3 lg update. So if I restore that I should be back to stock and CWM should still be there right? But lets say LG comes out with another update (Doubtful) and I want to use it I should use the NVflash to reture the phone to stock? if I use NVflash will that put me back on froyo 2.2.2 or GB 2.3.3?
Also I used rom manager to make a backup of the rom I was on which was the stock rooted so is that fake or what the hell is fake? is it the first option in rom manager the CWM recovery? is it the same if I use CWM stock recovery? in cwn itself? Oh I am so confused someone help me
ROM Manager cannot flash directly to the phone so it "fake flashes" CWM recovery. It only installs a few files to the system so that when you run recovery the stock recovery runs an "upate" and that launches CWM recovery from your SD card. Just return the phone to GB 2.3.3 stock and be happy with it. If you restore using CWM it will remain there, so you should use NVFlash to restore stock recovery also.
jboxer said:
ROM Manager cannot flash directly to the phone so it "fake flashes" CWM recovery. It only installs a few files to the system so that when you run recovery the stock recovery runs an "upate" and that launches CWM recovery from your SD card. Just return the phone to GB 2.3.3 stock and be happy with it. If you restore using CWM it will remain there, so you should use NVFlash to restore stock recovery also.
Click to expand...
Click to collapse
I have BOTH - CWM AND CWM through the ROM Manager. So if use NV Flash to go to stock, is the CWM from ROM manager still in the phone and how can I remove it?
Thanks!
so what I am getting out of this is rom manager is crap and dont use it. If you just use CWM to do your flashing and backups and recoverys you should be ok.
Charlie
mojorisin7178 said:
so what I am getting out of this is rom manager is crap and dont use it. If you just use CWM to do your flashing and backups and recoverys you should be ok.
Charlie
Click to expand...
Click to collapse
Thanks but my questions are:
1. If I go to stock using NV Flasher, is ROM Manager's CWM still going to be in the phone, since I have BOTH?
2. Can it BRICK my phone if I do the LG update then?
3. How can I make sure I removed BOTH - NV Flash CWM AND ROM Manager CWM?
Hi guys I really hope someone can help me with this. I was running CM7 Nightly rom and decided to try and flash eaglesblood 2.3.5 and it flashed ok but the problem is that when I tried restoring my back-up on it I get an clockworkmod recovery error. Any Ideas?
what does the error say?
most likely it was a bad backup and slim chance of restoration
did u do a full wipe before restoring?
Yes I did a full wipe before flashing and also before I tried to restore my black-up thru rom manager.I have flashed plenty of roms and this phone am not a total noob when it comes to this phone. I have never encountered this problem before. Before i tried going into recovery thru rom manager to restore back up thru CWm 4.0 etc, and it says I need CWM 5.0. I updated the rom manager to 5.0 etc and when I reboot and go into recovery (not thru rom Manager) and it says that it is the 4.0 etc version.Also is the 5.0 etc version blue? it jumps from 4.0 to 5.0 back to 4.0. This is a lil weird I went into recovery and did a restore from there and when I try in RM it comes up with error message Cannot restore cuz my CWm is 4.0 etc. thats when it jumps back from 5.0 to 4.0. I know this is confusing and by the way all the etcs you see are because I don't know the exact version. Any helps and thnx to whomever does.
deder21 said:
Yes I did a full wipe before flashing and also before I tried to restore my black-up thru rom manager.I have flashed plenty of roms and this phone am not a total noob when it comes to this phone. I have never encountered this problem before. Before i tried going into recovery thru rom manager to restore back up thru CWm 4.0 etc, and it says I need CWM 5.0. I updated the rom manager to 5.0 etc and when I reboot and go into recovery (not thru rom Manager) and it says that it is the 4.0 etc version.Also is the 5.0 etc version blue? it jumps from 4.0 to 5.0 back to 4.0. This is a lil weird I went into recovery and did a restore from there and when I try in RM it comes up with error message Cannot restore cuz my CWm is 4.0 etc. thats when it jumps back from 5.0 to 4.0. I know this is confusing and by the way all the etcs you see are because I don't know the exact version. Any helps and thnx to whomever does.
Click to expand...
Click to collapse
You need to update thru NVFlash. Here is the link and everything should be fine after that. http://forum.xda-developers.com/showthread.php?t=1054492
Thanks guys u rock. I got the new CWM on there for nvflash. Now I am moving my saved back up zipped file from downloads to CWM on sd card after I zip it, so well see how this goes right now. THanks again
With the G2X don't use rom manager for your backup/restore. Boot directly into the clockworkmod that you installed with nvflash and do the backup/restore from there.
I recently put the newest ICS Lite'ning Rom onto my S2 having backed up everything onto my SD card using CWM. I was previously running Lite'ning V4.2.
The new Rom was successful but when I went to restore all my apps/layout etc from CWM the phone went back to how it was before (V4.2).
I realise that this probably sounds obvious but I had (wrongly) assumed that the CWM backup would restore everything but keep the new Rom.
I am quite new to this, but is there anyway I can download the new ICS Rom and then restore everything I used to have on it without going back to the old Rom.
Please don't flame the newbie!
Ohhh lol its fine. Everyone makes mistakes.
Let me cover the basics. Cwm will restore everything( system, SD card...etc)
OK just download a supported rom. Best to do a clean install. (Search that) . Flash the from, flash the gapps. Reboot once, flash kernel if you want only after the reboot. Sync your email and install the apps.
Unless you did a back up before you stuffed this up just re install back up.
Sent from my Nexus S using XDA
Thanks TigaTiger - great help. All done and very happy.
I have the Verizon Galaxy S3.
I had no modifications on my phone at all; it was stock everything. I wanted to install Hyperdrive on the phone so I went through the usual steps.
1) Root
2) Flash CWM
3) Create nandroid back up within CWM
4) Flash Hyperdrive ROM
I used Hyperdrive for a few weeks, but then I wanted to go back to stock, so I restored my backup. I was on stock for another few months and then OTA updates started coming in. I know that I cannot install OTA updates with a custom recovery. (I assumed I still had CWM)
So here is the thing...I thought that the backup I made was in the state of being rooted with CWM and stock ROM. So I assumed that after restoring the backup, I was rooted with CWM and stock ROM. So I double checked and found that I was not rooted and I had stock recovery installed. Does anyone know how this happened?
longphant said:
I have the Verizon Galaxy S3.
I had no modifications on my phone at all; it was stock everything. I wanted to install Hyperdrive on the phone so I went through the usual steps.
1) Root
2) Flash CWM
3) Create nandroid back up within CWM
4) Flash Hyperdrive ROM
I used Hyperdrive for a few weeks, but then I wanted to go back to stock, so I restored my backup. I was on stock for another few months and then OTA updates started coming in. I know that I cannot install OTA updates with a custom recovery. (I assumed I still had CWM)
So here is the thing...I thought that the backup I made was in the state of being rooted with CWM and stock ROM. So I assumed that after restoring the backup, I was rooted with CWM and stock ROM. So I double checked and found that I was not rooted and I had stock recovery installed. Does anyone know how this happened?
Click to expand...
Click to collapse
After you rooted and installed CWM did you let your phone bootup first, then boot back down into CWM then do the backup? Seems like you didn't do that. Your Root, CWM did not loaded when you run the CWM backup.
longphant said:
I have the Verizon Galaxy S3.
I had no modifications on my phone at all; it was stock everything. I wanted to install Hyperdrive on the phone so I went through the usual steps.
1) Root
2) Flash CWM
3) Create nandroid back up within CWM
4) Flash Hyperdrive ROM
I used Hyperdrive for a few weeks, but then I wanted to go back to stock, so I restored my backup. I was on stock for another few months and then OTA updates started coming in. I know that I cannot install OTA updates with a custom recovery. (I assumed I still had CWM)
So here is the thing...I thought that the backup I made was in the state of being rooted with CWM and stock ROM. So I assumed that after restoring the backup, I was rooted with CWM and stock ROM. So I double checked and found that I was not rooted and I had stock recovery installed. Does anyone know how this happened?
Click to expand...
Click to collapse
It does not backup your recovery, but you can backup your recovery partition separately. If you restore to stock it will still nag you to update. To stop it you need to freeze sdm1.0 and rename fwupdater.apk.
The update should fail, but if you're unlucky it'll go through enough to lock you down and stick you on 4.3. So either change the rom as soon as possible or freeze and rename the apks.
Sent from my SCH-I535 using Tapatalk 2
I believe I used a 1 step script to root and install my recovery. Something very similar to http://forum.xda-developers.com/showthread.php?t=2332825
I had my phone booted up, plugged into my PC and I allowed the 1-click script root it install CWM. Then I rebooted into CWM, and did a backup. So by not rebooting my phone after doing all this, then the root and CWM were not in the backup? Why is that the case? if I am able to boot into CWM, doesn't that mean the CWM already sits in my recovery partition? Thus, if I do a backup of it, shouldn't I get CWM in the recovery?
longphant said:
I believe I used a 1 step script to root and install my recovery. Something very similar to http://forum.xda-developers.com/showthread.php?t=2332825
I had my phone booted up, plugged into my PC and I allowed the 1-click script root it install CWM. Then I rebooted into CWM, and did a backup. So by not rebooting my phone after doing all this, then the root and CWM were not in the backup? Why is that the case? if I am able to boot into CWM, doesn't that mean the CWM already sits in my recovery partition? Thus, if I do a backup of it, shouldn't I get CWM in the recovery?
Click to expand...
Click to collapse
A nandroid doesn't backup your recovery, only your data, sd card, and caches. It's the same cwm installed by casual.
Sent from my SCH-I535 using Tapatalk 2
If that's the case, then how could I possibly be on stock recovery? I definitely needed CWM to install Hyperdrive and to create the Nandroid backup that I used to restore.
Currently I'm not running latest cwm, but I'm runing TWRP and it does backup recovery and efs by default. I'm sure that cwm can do the same but is it set by default? I don't know. here the info I found on cwm:
http://imageshack.us/a/img69/3563/image6resize.png
buhohitr said:
Currently I'm not running latest cwm, but I'm runing TWRP and it does backup recovery and efs by default. I'm sure that cwm can do the same but is it set by default? I don't know. here the info I found on cwm:
http://imageshack.us/a/img69/3563/image6resize.png
Click to expand...
Click to collapse
Some roms are capable of reinstalling a stock recovery. Sometimes if it's not taken out of a rom, it will sense you have a custom recovery and reinstall the stock recovery over it.
Most of the time it's taken out of the touchwiz roms, but I guess in this case it wasn't.
That's the only way it could happen.
Additionally, that isn't even cwm, that's philz touch recovery, those features are unique to that recovery only.
Sent from my SCH-I535 using Tapatalk 2