Hi,
I bought a nexus s that was already rooted with CWM and unlocked bootloader running CM 7.0.2
I'm getting the hang of ROMmanager and how to do NANDroid backups and load new roms.
Is there a stock gingerbread recovery image that already has root/cwm/unlocked bootloader, basically that I can use to do a small test but then quickly do a restore to my CM7.0.2 image?
Thanks.
p.s. the reason I want to try this is this problem I'm having with maps. I have cached tiles that I've been able in the past to move to different phones, but the NS won't read it. So I just want to go back to to stock to test copying this cache and see if maps see it. Maybe it's a CM thing.
here's my thread
http://forum.xda-developers.com/showthread.php?t=1068189
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 ?
I have looked really hard to find the answer to this, but I couldn't find it.
I have a HTC EVO Shift, which was already flashed to Boost Mobile before I bought it.
After looking at the Boot Animations and apps, I realized the phone was also running the MikShifted-G ROM.
I have been using the phone for some time now, but after I found that my phone was not getting the upgrade to ICS, I decided that I wanted to switch ROMs, especially ones that were ICS and stuff.
I followed many tutorials and I have done the following:
-I have rooted my phone.
-I have installed ROM Manager, and I have gotten ClockWorkMod to work.
-I backed up my data with the backup option.
Here are the questions I have:
-It says on most ROMS to "wipe everything." If I choose to Factory Reset/Wipe All in ClockWorkMod, will that un-flash my phone back to Sprint? I do not want to factory reset if my phone will not run on Boost Mobile, hence it is a lot cheaper.
-If I install another ROM and decide to go back to the ROM my phone used to have, does installing ROM Manager again on the new ROM allow me to use the backup I made to go back to how my phone used to be?
Thanks,
Sarcasticphoenix
I can't say for sure but doing a full wipe and flashing a ROM shouldn't have any affect on your phone working with boost. Search the EVO threads, I'm sure you'll find a lot of people on boost flashing various ROMs and kernels.
As far as actually flashing the ROM, you should get familiar with using recovery manually, not just relying on ROM manager to do everything for you. Here's a nice guide on how to flash ROMs http://forum.xda-developers.com/showthread.php?t=1266885. Be sure to make a nandroid backup before flashing any ROM (If you already made a backup using ROM manager it can be restored either via recovery or the ROM manager app.)
Also consider using Dread 7 Us's modified recovery. Based off Clockwork Mod but with some great differences: super wipe where you can choose which partitions to wipe and do it multiple times automatically(much less tedious than Clockword Mod's wipe each once method) and it also removes the ton of 'NO's' you have to scroll through to confirm an action in Clockwork Mod and others upgrades I don't recall.
http://forum.xda-developers.com/sho...RECOVERY] CW-Enhanced [v1.1b] Updated 5/22/12
Flash it just like Clockwork Mod but do a nandroid before just in case. Make sure to also flash the updated one as the first version had MD5 check issues.
roms
if i put a rom into my phone and do a backup... can i go back to rooted stock and put another rom and i i dont like it restore to the other rom?
tello2323 said:
if i put a rom into my phone and do a backup... can i go back to rooted stock and put another rom and i i dont like it restore to the other rom?
Click to expand...
Click to collapse
As long as you have s-off nandroid restore will work fine. As far as the roms it depends on if the roms have the boost mobile apn's in them or not. A.F.A.I.K. CM7 roms and variants have the most apn support. Might want to do a search on google if cm7 supports boost or not.
Ok so i've finally decided im ready to unlock and flash. My question is this: whats the deal with returning to stock and redoing everything on certain roms? Can anyone explain to me the variables here?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
once you have your device rooted and have a recovery installed, make a nandroid back up your stock rom, flash whatever rom you want, then if you need to go back to stock rom, just flash the nandroid back up you made. If you want to go 100%, then you will have to find the stock recovery image, and flash that over your custom recovery as well, then just use OTA Rootkeeper... and temp unroot your phone... and viola, your 100% stock again.... but if you plan to go back to 100% stock then DO NOT UNLOCK YOUR BOOTLOADER!! there is no way to lock it again once you unlock it.
I think it's worth while to note
currently the only custom recovery that is able to flash stock is CWM
TWRP is not able to flash a stock rom
KAD79 said:
I think it's worth while to note
currently the only custom recovery that is able to flash stock is CWM
TWRP is not able to flash a stock rom
Click to expand...
Click to collapse
If you flash a stock ROM using CWM you will lose all data on your device, including any backups you made using CWM. So be sure to backup those files to your PC (they're located in the clockworkmod/backup folder of your internal storage) before flashing the stock Asus ROM.
I've been changing my ROM's throughout the day and have basically memorized the process of flashing CWM, root, and ROM's by now
KAD79 said:
I think it's worth while to note
currently the only custom recovery that is able to flash stock is CWM
TWRP is not able to flash a stock rom
Click to expand...
Click to collapse
TWRP can flash stock. I've done it.
Sent from my SGH-I897 using xda premium
Ive read about problems reflashing ROMs when youre on the CM or AOKP. Need to return to stock, then flash other ROMs, dunno why exactly. So is it enough just to restore my stock nand backup or do I need to do something differently? :good:
This is exactly what im talking about. What are the rules when coming from cyan to a stock flavor?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
So lets say right now im ready to unlock and root. I would want to unlock the device, then root, then flash CWM (not twrp) so i could still retrain (and boot in to without reinstalling) my original rom? Because i still want to titanium my apps.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
not sure if I understand your question right, but yeah you can use your stock rom when you root or flash cwm. Untill you wont wipe anything within CWM, theres no reason you coulndt use it. But dont forget to do backup of your stock mate.
I think part of the confusion is defining what "stock" means, and I've got two different views on it over the past few days:
COMPLETE STOCK means flashing ASUS' original stock firmware, which completely wipes out everything on your tablet (including your nandroid backups) and CWM and takes you back to a fully stock tablet (except it will still have unlocked bootloader). From here, if you want to install ROM's like CleanROM or Hydro you have to re-flash CWM each time, then flash the appropriate ROM.
MODIFIED STOCK would be making a nandroid backup of your stock settings as soon as you flash the stock ROM, install CWM, then back it up and you can revert to it accordingly. I don't know if this would break things when you tried to flash Clean/Hydro and so maybe someone can clarify.
I wanted to try both hydro and cleanrom so I spent many hours yesterday flashing between stock/modified stock. Its kind of a pain, but all part of the learning process.
And one thing I want to note both for myself and for anyone else: if you flash stock without removing CWM it'll give you the broken bootloader logo (android on his back w/ exclamation point), and my solution has just been to do a 'wipe data' from the fastboot menu and the stock will work fine. What I mean by this is I've done this at least three times, where I flash STOCK from within CWM and when I try to boot into recovery, I'll get that android. That's because STOCK completely erases everything including CWM so in order to restore the normal operating procedure, you just need to 'wipe data' from within the tablet.
Hope my understanding of these situations is correct, if not anyone can feel free to correct me
People like to experiment with their tablet, they get easily bored with the same thing.
So they go back to stock and flash another rom like Hydro which is stock based because when you flash CM or AOKP it won't let you just flash to Hydro.
KAD79 said:
I think it's worth while to note
currently the only custom recovery that is able to flash stock is CWM
TWRP is not able to flash a stock rom
Click to expand...
Click to collapse
NOT TRUE!
It should be noted that TWRP is now more functional than CWM. TWRP can now flash stock ROMs just fine. It can now restore complete nandroids, including /boot, and it can now flash from and store to the external SD card. It was just recently updated for this, which is why all the information until now has said to use CWM to flash the stock ROM. So, go ahead and use TWRP. It's perfect now.
i have installed cm10 on htc one v primo-u (india gsm ) and i wish to revert to the original image.
i tried to flash India_1567201recovery_signed.img file but no success.
can someone help me with a procedure how to revert to either 1.56.720 or 2.09.720 image of the phone
romah1 said:
i have installed cm10 on htc one v primo-u (india gsm ) and i wish to revert to the original image.
i tried to flash India_1567201recovery_signed.img file but no success.
can someone help me with a procedure how to revert to either 1.56.720 or 2.09.720 image of the phone
Click to expand...
Click to collapse
How did you try to flash the RUU? You can not flash it like a normal ROM
Also if you are looking for the RUU try HERE
I see what you're trying to do, that won't work...you can't flash a recovery to get to stock because stock phone won't flash from recovery, which is why once you get root the first thing you do is flash a custom recovery. Use the RUU to flash it back to shipped state stock, or if you are trying to keep root and just want to use a different ROM. More clarification on what you are trying to accomplish would be nice.
If you did a Nandroid prior to flashing CM10 I would wipe all partitions except SD and restore the Nandroid, if all you want to do is get CM10 off your phone. Remember Nandroid Backups are your friend do them before flashing anything and save them to your PC if you don't want the SD space taken. Doing this has made flashing pain free and hassle free. If I don't like how my phone is running after a flash I can always get it right back to how it was when I was happy with it. Lastly there was a time when I had a Nandroid backup of a Sense ROM and was on AOSP and wanted to flash back to Sense, well my Backup wouldn't flash. After spending hours raising hell I did a clean install of the ROM booted once, then rebooted into recovery and flashed the Nandroid backup that had the settings I was using (when I was on Sense, it won't restore data and apps used on AOSP)...sorry if its not much help but more details are needed. But you have a starting point.
ItzCrooK2UxD said:
How did you try to flash the RUU? You can not flash it like a normal ROM
Also if you are looking for the RUU try HERE
I see what you're trying to do, that won't work...you can't flash a recovery to get to stock because stock phone won't flash from recovery, which is why once you get root the first thing you do is flash a custom recovery. Use the RUU to flash it back to shipped state stock, or if you are trying to keep root and just want to use a different ROM. More clarification on what you are trying to accomplish would be nice.
If you did a Nandroid prior to flashing CM10 I would wipe all partitions except SD and restore the Nandroid, if all you want to do is get CM10 off your phone. Remember Nandroid Backups are your friend do them before flashing anything and save them to your PC if you don't want the SD space taken. Doing this has made flashing pain free and hassle free. If I don't like how my phone is running after a flash I can always get it right back to how it was when I was happy with it. Lastly there was a time when I had a Nandroid backup of a Sense ROM and was on AOSP and wanted to flash back to Sense, well my Backup wouldn't flash. After spending hours raising hell I did a clean install of the ROM booted once, then rebooted into recovery and flashed the Nandroid backup that had the settings I was using (when I was on Sense, it won't restore data and apps used on AOSP)...sorry if its not much help but more details are needed. But you have a starting point.
Click to expand...
Click to collapse
i have installed CM10 without backing up any image, therefore i cannot restore the orifginal vendor's rom. Nandroid back would have prevented this situation. the second problem is that I couldnt find any RUU for this phone. indeed the link you attached seems to have it bu unfortunately it is in chineese and after pushing all the buttons i couldn't download the file. so my options are
1- to pray that someone will be kind enough to publish it in a manner that it is accessible
2- I have a friend with a simillar phone , can i somehow back up hus rom and restore it in mine ????
thank
romah1
Hey guys,
I searched around and only found some old posts for this topic.
I just bought this phone, I rooted it, simunlocked it, and added two day old CWM recovery. Its a S4 Canadian (Bell) version in case that helps..
Is there a way to apply the OTA update WITHOUT having to wipe my data and settings and reflashing a rom?
Hlep will be greatly appreciated!
THANKS :good:
I got the same thing going on. I have a TMOUS HTC One S stock with CWM Rooted and such. I just changed it back to the Stock recovery, but doesn't seem to help. Is there something else I need to do? Maybe I need to flash a newer recovery version?
I have the stock recovery from a MoDaCo topic I can't list because I don't have 10 posts yet.
its topic/353006-interim-clockworkmod-touch-recovery-for-the-htc-one-s-stock-download/ though.
Are you sure your Rom is absolutely stock. For example if the rom is tweaked in any way or if bloatware has been deleted then you won't recieve the update
Ok so I got the update to work. This is what I did: in CWM I backed up a nandroid. I flashed a stock BACKUP for the HTC One S (I moved the zip to the clockwork > backups folder on the sd card). Rebooted into bootloader, flashed a stock recovery from modaco, rebooted, ran the update (I had to update twice, from 1.53 to 1.84 to 2.35). Then I restored my original nandroid. Problem is, the update didn't stick. And now I'm getting an error when I try to turn on wifi. Any ideas? I feel like I got so close...
Tough to see what went wrong.
I had a brand new stock rom with no modifications.
Then I flashed stock recovery,
Did a root keeper (play store app)
Then did the update
And restored root.
Worked out fine for me!
I think you should flash a stock rom and not a backup..