Hi guys.
I have some question, mostly out of interest really that may help me understand flashing etal better.
When in CWM recovery, if I want to flash a new ROM, I use a fullwipe.zip that I found on this site, to, well, wipe the phone
The last thing wipe.zip says is make sure you install a new ROM.
Now, as I have, afaik, performed a full wipe, if I were to reboot after the wipe and before flashing a new ROM, would I brick the phone, or would it just boot into bootloader etc...
Would CWM recovery still be present on the phone after the wipe is it just running in ram or something?
I also have a load of other questions. But they can wait.
Cheers dudes.
Greg.
Sent from my Desire HD using Tapatalk
I've never done this, so I'm curious to know what happens exactly.
But as far as i'm aware if you were to boot the phone without a rom installed, you would just get a blank screen or maybe the splash screen. Recovery stays installed, which is good news because you need to get back there to install a rom or the phone won't work. So to do that you would have to plug the phone in and use adb to get back to recovery with "adb reboot recovery" or if that doesn't work, pull the battery, hold vol down + power to get to bootloader and then get to recovery that way to install a rom.
If you run the phone without os you get stuck in a bootloop i think. After that not sure what happeness. It's always easier to install 4EXT recovery, dowload any ROM you like from here and flash through 4EXT. No need for any full wipe scripts since a full wipe is format data/system/cache, erase dalvik which is very simple in 4EXT.
Sent from my Desire HD using XDA App
answer on your question:
CWM still works, even if you flashed a fullwipe or "superwipe".
But, i just want you to know, that you get other problems if you tried to unlocked your bootloader via htcdev, within flashin new roms.
Lol i dont get it,you wiped her,why would you want to blast off into oblivion
Interesting though,rather start picking my rom out?
Theres so much choice now
Sent from my Desire HD using XDA Premium App
If you do that you will be stuck in boot loop as no OS is installed and yes you will still have CWM available. To get out of the boot loop just remove the battery. And then just press vol down and power to get into hboot and then you can get into recovery from there.
Sent from my HTC Desire HD using xda premium
arknailed7754 said:
Lol i dont get it,you wiped her,why would you want to blast off into oblivion
Interesting though,rather start picking my rom out?
Theres so much choice now
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
Hey dude. It was purely out of interest.
I was thinking about this after i flashed the LC ICS ROM.
I used CWM to full wipe and flash the new rom zip, but it seemed to install very quickly.
So quickly in fact I thought that it couldn't have installed correctly.
I didn't want to reboot incase the rom hadn't taken and I bricked my DHD so I ended up restoring a nandroid backup I'd made before wiping the phone.
But if CWM recovery would remain on the phone even after a wipe, then I can take the gamble that it had installed.
Cheers for your answers dudes.
TeamDraven said:
Hey dude. It was purely out of interest.
I was thinking about this after i flashed the LC ICS ROM.
I used CWM to full wipe and flash the new rom zip, but it seemed to install very quickly.
So quickly in fact I thought that it couldn't have installed correctly.
I didn't want to reboot incase the rom hadn't taken and I bricked my DHD so I ended up restoring a nandroid backup I'd made before wiping the phone.
But if CWM recovery would remain on the phone even after a wipe, then I can take the gamble that it had installed.
Cheers for your answers dudes.
Click to expand...
Click to collapse
Lords ICS does install pretty fast. But it just works... so there's little/no risk there. I try to always do a full wipe before installing but lately with his builds, I've only been wiping dalvik and cache and updating with the newest build. If something doesn't work, then I wipe and see if I get the same behavior with a full wipe. Multiple Nandroid backup points let me restore to whatever point in time that I want. It's a great approach.
Best of luck and have fun!
djmasoda said:
Lords ICS does install pretty fast. But it just works... so there's little/no risk there. I try to always do a full wipe before installing but lately with his builds, I've only been wiping dalvik and cache and updating with the newest build. If something doesn't work, then I wipe and see if I get the same behavior with a full wipe. Multiple Nandroid backup points let me restore to whatever point in time that I want. It's a great approach.
Best of luck and have fun!
Click to expand...
Click to collapse
Cheers dude.
I just flashed it onto my DHD.
Runs well, the otly first poopy impression I have is the pictures from the camera!
Any suggestion on a 3rd party Camera app?
Cheers.
Greg
I've found better luck with Pudding Camera and Camera 360. For me, the camera is the only hit or miss item atm. Folks have been posting ideas to get it working right, such as disabling the flash or putting it in burst mode with on 1 photos set. Also try clearing the data from the app too. Peruse the development thread... There's a lot of camera tweaks being offered here and there.
Another note, video is also problematic in the rom too... Really, so long as I can scan barcodes using amazon, I can get by otherwise. I look forward to your thoughts as you dig in... More updates are coming daily from Lord!
Sent from my HTC Inspire 4G using xda premium and Lord's ICS
Hey dude.
The camera is a real deal breaker for me. With two kids and one on the way I want a good camera and camcorder.
Cheers for your comments though guys.
Greg.
Related
I saw that the final release of cm7 came out and I'm super excited for it! I've been running RC3 for awhile and it's been working fine, but there have been some issues that I would like to have fixed with the update.
My question is: Is there a way to update the rom without losing all of my data or having to do a full wipe?
Any help is appreciated. Thanks!
You wont need to do a full wipe, just download the ROM to your sd card, boot in to recovery and do a nandroid backup. Then select wipe cache. Once that has finished head to advanced and select wipe dalvik cache (some people say to do this some don't, I do) then flash the ROM.
You will only lose all your apps and setting if you select wipe data, you only need to do this if you are have serious issues that cant be fixed by any other means. Or if you changing to a completely different ROM.
And remember to do a nandroid before touching anything else in the recovery menu
That's it? Awesome! I know what I'll be doing tonight.
Or you can just do it from rom manager and not check the wipe data. I swear some of you just like taking the long way.
Always do a nandroid?No. Nandroid your original rom? YES. Nandroid custom rom? Only if you like it..but to do a nandroid every single time you flash new rom is ****
Sent from my Vision using XDA Premium App
Spastic909 said:
Or you can just do it from rom manager and not check the wipe data. I swear some of you just like taking the long way.
Always do a nandroid?No. Nandroid your original rom? YES. Nandroid custom rom? Only if you like it..but to do a nandroid every single time you flash new rom is ****
Sent from my Vision using XDA Premium App
Click to expand...
Click to collapse
ROM Manager can some time cause issues when you flash directly from the app, Some people prefer to do it manually. Ok it might not be totally necessary to wipe the cache's between flashes but does really hurt?
And I resent you saying that doing a nandroid is "F'in Retarded" how frequently do we see people on these forums who have flashed something there not supposed and there most recent backup was weeks ago. It never hurts to do a nandroid it adds 5 minutes to the total time it takes flash something.
As some one who does do a nandroid every time I take your insult personally. And that sort of language is not appropriate in a forum where people of all ages can view.
LOL i don't even have a nandroid of my original ROM. I just got 1 image of RC4...
So I wanted to be 'better off safe than sorry', and I did a nandroid backup (using the latest CWM) before doing a CM7 RC3 -> CM7 Final non-full data wipe upgrade. I had a bunch of problems from the get go, and wanted to revert back to my RC3 backup as I didn't have time to fiddle with everything to get it tweaked from scratch...
However I can't for the life of me get Clockwork to recover my backup. It stops half way through and I'm left sitting at the main orange menu with no confirmation or details on what happened.
Any thoughts?
cjward23 said:
Glad its not just be with this mentality. Better to be safe than sorry. I haven't had to start from scratch since the first nightly, because I all ways have a recent nandroid, some times things do go wrong.
Click to expand...
Click to collapse
I did the backup (2 actually) and just installed the update. Everything seems totally fine so far and I'm really happy with it! Seriously stepping up to cm7 has made my G2 go from a decent phone with a nice keyboard to a flipping fantastic phone!
Many thanks!
raitchison said:
Your definition of *** seems to be basically the opposite of mine. What if an update breaks something (especially if you are cutting corners by not wiping or by using ROM manager) if you don't have a nandroid of your phone before you flashed that update you are screwed, you will need to start over from scratch.
Click to expand...
Click to collapse
Yeah, I agree with you completely. Doing a nandroid takes 5 minutes. Then later you can just move it to your desktop computer, to not take up space on your SD card. I have 3 TB of storage on my desktop, so no worries about saving as many nandroid backups as I feel like.
I've seen random issues pop up on my phone for no obvious reason, with no clear fix. But reverting to a nandroid cleared it up.
Really no reason NOT to do it.
Okay, so after rooting my G2 I decided to flash this rom.
http://forum.xda-developers.com/showthread.php?t=1012763
Now after I used Rom Manager, I checked the back up etc.
After it backuped it installed the new Rom, at the moment I am at the HTC screen and it keeps rebooting not sure what it's doing exactly.
Shows HTC screen, after a few mins, it turns black plays the HTC sound and shows the HTC splash page again.
What to do?
Boot into recovery and wipe cache/data.
theSpam said:
Boot into recovery and wipe cache/data.
Click to expand...
Click to collapse
And if that doesent work try to flash the rom again.
I ran the adb command to go into recovery, then restored it from a back up I made.
Going to try another ROM, thanks guys!
Does anyone have MSN?
I flashed cyanogen, but it has the same issue, the splash screen comes up then dissapers and the cynaogen screen comes back again.
What to do? Is there something wrong with my phone?
You didn't have to restore your backup.
If you had wiped the /cache and /data partitions, everything would have been fine. There is nothing wrong with with your phone.
DroidStation said:
I flashed cyanogen, but it has the same issue, the splash screen comes up then dissapers and the cynaogen screen comes back again.
What to do? Is there something wrong with my phone?
Click to expand...
Click to collapse
This may be a ROM manager that produce this boot loops, Skip rommanger . Boot into recovery -power-wolume down . Navigate to recovery . Chose wipe data/ factory reset. Then wipe cache and /data partitions, flash cm7 and gapps.
First off let your phone sit for 20 minutes after installing a new rom. The first boot takes a good long time. If after 20 min it doesnt start then come post about it. Make sure you post exactly what screen comes up when it reboots ect.
Sent from my HTC Vision using XDA App
Cleared the data and cache all is fine now, thanks!
Have a side question about overclocking, how do I do it and what's the recommended amount?
Depending on the ROM's install a kernel
You have a lot of options. It's not necessary but if you still want to first install the app 'setcpu' or 'cputuner' and then download a kernel and flash it the same way that you flashed the ROM's. Best of luck!
Which rom did you end up flashing? A lot of them come overclocked. As the above person posted you will need one of those apps anyway.
Sent from my HTC Vision using XDA App
I used the one on the main post, seems that SetCPU is not free.
Downloading CPUTuner..
With only reading the heading of that rom i would assume there is no OC built in as it is untouched. You will need to flash a kernel for sure to OC. I cant recomend any for that rom as i have never used it.
Sent from my HTC Vision using XDA App
DroidStation said:
I used the one on the main post, seems that SetCPU is not free.
Downloading CPUTuner..
Click to expand...
Click to collapse
SetCPU is free for XDA members:
http://forum.xda-developers.com/showthread.php?t=505419
If you're still using the ROM in your OP, I don't think there are over-clockable Sense Gingerbread kernels yet.
I rooted my phone fine. I unlocked my phone fine.
I installed clockworkmod recovery fine. I flashed clockworkmod. I backed up my rom at the stage after rooting and unlocking.
I then downloaded cyanogenmod from the app's download page. I downloaded it and installed it. I used the default selections which is "wipe delvich cache"
When I turned on my phone, it stays at the blue screen with the alien forever.
Any help on what to do? Thanks!
Reflash the ROM using these instructions. You probably wiped the wrong way.
http://forum.xda-developers.com/showthread.php?p=32532260
Sent from my SGH-T989 using xda premium
I had same problem installing cm10 with cwm. In order to get past boot animation you have to use the dark side cache wipe after flashing ROM. Ideally you should -darksidesuperwipe then flash ROM then darksidecachewipe. I like to let it boot without gapps first. Set up WiFi and all that.
Try rebooting and flash darksidecachewipe. Then reboot. I always had lingering problems until I flashed twrp. After twrp is installed there is no need for darkside scripts.
Worth it to just get twrp and redo.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
ctrlaltdeln said:
I had same problem installing cm10 with cwm. In order to get past boot animation you have to use the dark side cache wipe after flashing ROM. Ideally you should -darksidesuperwipe then flash ROM then darksidecachewipe. I like to let it boot without gapps first. Set up WiFi and all that.
Try rebooting and flash darksidecachewipe. Then reboot. I always had lingering problems until I flashed twrp. After twrp is installed there is no need for darkside scripts.
Worth it to just get twrp and redo.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Wow very informative and helpful too bad the OP could not at least give you some props and let you know he saw this and you helped him out. People panic come on here and ask questions then never come back to thank or at least acknowledge the help... Hey for that I will give you your first xda Thanks.... :good:
Try returning to stock and try again. Do things in this order: 1. Root, CWM, ETC. 2. CM7 or another 2.3 ROM (usual wipe) 3. CM9 (again, wipe)
Hi all, ive had my Tmobile samsung galaxy s2 for awhile now, and i finally decided to root it (and did it successfully) a few days ago (yay)
Ive done a bit of research for what I can do while rooted, basically after CPU setting, save battery life when idle... Simple things
But ive been meaning to try flashing a ROM. But I want to make sure i know absolutely everything needed to know to flash one. I had a samsung tmobile sidekick that I was able to root and flash Gingerclone on, but I remember it had alot of little details while installing that simply missing one could seriously screw up your phone
So first off, if anyone has had the sidekick: Is flashing/ installing roms as complex on the sgh-t989 as it is on sidekick 4g?
And secondly... After rooting my galaxy, i no longer have the stock android recovery (obviously)...... Instead it is replaced with CWM-based recovery (i think 5.0.2.2?). Is there a difference between this and Clockworkmod recovert (which should show an orange screen)?
I wanted to use ROM manager but opted not to when it told me that I "needed clockworkmod recovery installed" to work.
A little help, please?
Thanks!
heyitsmeyo2 said:
Hi all, ive had my Tmobile samsung galaxy s2 for awhile now, and i finally decided to root it (and did it successfully) a few days ago (yay)
Ive done a bit of research for what I can do while rooted, basically after CPU setting, save battery life when idle... Simple things
But ive been meaning to try flashing a ROM. But I want to make sure i know absolutely everything needed to know to flash one. I had a samsung tmobile sidekick that I was able to root and flash Gingerclone on, but I remember it had alot of little details while installing that simply missing one could seriously screw up your phone
So first off, if anyone has had the sidekick: Is flashing/ installing roms as complex on the sgh-t989 as it is on sidekick 4g?
And secondly... After rooting my galaxy, i no longer have the stock android recovery (obviously)...... Instead it is replaced with CWM-based recovery (i think 5.0.2.2?). Is there a difference between this and Clockworkmod recovert (which should show an orange screen)?
I wanted to use ROM manager but opted not to when it told me that I "needed clockworkmod recovery installed" to work.
A little help, please?
Thanks!
Click to expand...
Click to collapse
There the same
Sent from my HTC PH39100 using xda app-developers app
XxSHaDoWxSLaYeRxX said:
There the same
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
Okay, great! Glad it was so simple lol.
Now about my other question... Let me explain. When I would install a custom ROM on my sidekick, i remember having to do all sorts of things like unmount system/ unmount SD card before installing and remount them after (i dont remember the exact methods... Dont quote me on that).
I know the general procedure of basically Wiping data, Wiping cache, Wiping delvik cache... But does the galaxy s2 require checking of all of that unmounting/mounting?
heyitsmeyo2 said:
Okay, great! Glad it was so simple lol.
Now about my other question... Let me explain. When I would install a custom ROM on my sidekick, i remember having to do all sorts of things like unmount system/ unmount SD card before installing and remount them after (i dont remember the exact methods... Dont quote me on that).
I know the general procedure of basically Wiping data, Wiping cache, Wiping delvik cache... But does the galaxy s2 require checking of all of that unmounting/mounting?
Click to expand...
Click to collapse
Flashed many roms, and no need for all that. Just make sure you wait the 10 minutes after flashing a rom.
FlaShing roms on this phone is so simple "that even a caveman can do it". I would also advise to ditch clockwork recovery and install twrp, also never use rom manager to flash roms. Just follow the op's instructions on what steps to follow to flash the rom successfully. Also no need to mount and unmount anything. Good luck.
Awesome! Thank you all for your replies, glad to here that flashing is much simpler on this phone
I really wouldnt recommend anyone rooting a sidekick as a beginner. It was my phone, i soft bricked ot my first time. Ugh, it was such a hassle! And it left me a little traumatized to try anything on this. lol!
Thanks for all the help!
Here are the genreric steps to follow to flash a rom (and yes, TWRP is recommended instead of CWM):
- place the rom zip on the internal storage
- place a copy of the radio zip that you have on the internat storage (for safety reasons)
- copy Google Apps zip if it is not included in the rom (most roms do not have these included, but the dev might provide a tuned version)
- reboot phone and enter the recovery menu (hold vol up + vol down pressed while booting)
# In recovery mode
- wipe data
- wipe system
-(Use Darkside Super wipe if still on cwm 5.0.2.7 or below)
- flash rom
- flash gapps (if missing from the rom)
- wipe cache/ dalvik cache.
- reboot and wait 10 mins
- reboot and wait 1 minute
- enjoy
If you are planning on flashing a Rom on your phone of course twrp recommended and you should definitely try Jedi mind trick x2 for the t989 Hercules. It is the most stable Rom on the Samsung galaxy s2 T989 T-Mobile. The instructions above are the best instructions you should follow. And read it carefully or you will brick your device. If using twrp follow the twrp method. And if using cwm make sure you use the extra cwm steps. It is super important you follow them unless you want a fancy paper weight.
Sent from my SGH-T989 using xda premium
I just flashed my phone last night to the Liquid smooth rc 9. This was my first root and flash. I used titanium backup for the apps, used ROM manager to flash to the latest cwm. Here is a link I used
http://forum.xda-developers.com/showthread.php?t=1926754
Great instructions! Good luck!
Sent from my SGH-T989 using xda app-developers app
TomThom said:
I just flashed my phone last night to the Liquid smooth rc 9. This was my first root and flash. I used titanium backup for the apps, used ROM manager to flash to the latest cwm. Here is a link I used
http://forum.xda-developers.com/showthread.php?t=1926754
Great instructions! Good luck!
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
You have it all wrong. Use twrp and use app 2 zip
Sent from my SGH-T989 using xda premium
Hey fellow gnex community! I recently left stock rom due to freezes and random reboots. I've tried out various rom and kernel combinations this week such as xylon/AK, Purity/AK, AOKP/franco/lean, CM10.1/trinity/franco, Rasbean/trinity, PA/lean/franco/trinity/AK and Xenon.
The problem is they all freeze and reboot constantly after 2 minutes of use. I never changed the kernel settings and this is only happening on 4.2.1 roms. My favorite rom/kernel combo would be purity/AK, Xylon/AK but they freeze, wifi disconnects and never connects back and reboots constantly.
So the question is why is this happening to my phone recently and are there specific kernel settings that will stabilize the roms or is it just my phone?
Any help would be great,
thanks.
I haven't had that problem before, and I have flashed several roms (though not a custom kernel in a while)
Faulty hardware perhaps?
Sent from my Transformer Pad TF300T using Tapatalk HD
Lord Yurij said:
I haven't had that problem before, and I have flashed several roms (though not a custom kernel in a while)
Faulty hardware perhaps?
Sent from my Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
but this never happened on 4.1, 4.0.4 etc. That's what's worrying me.
4.2.1 isn't exactly highly regarded for its stability....
I reccomend going back to a good 4.1.2 rom. You aret missing anything anyway
nav200 said:
but this never happened on 4.1, 4.0.4 etc. That's what's worrying me.
Click to expand...
Click to collapse
I would do a full wipe and fastboot flash the stock images from Google to see if this helps. Mind you, your internal memory will be wiped so back up all of your photos etc..
crixley said:
4.2.1 isn't exactly highly regarded for its stability....
I reccomend going back to a good 4.1.2 rom. You aret missing anything anyway
Click to expand...
Click to collapse
but I heard people change the kernel settings and the phone will become smoother/stable? I really love some of the features from 4.2.1 that's the reason I'm a bit hesitant to go back to 4.1.2
Try a full wipe, and fast boot a stock image on and proceed from there.
Sent from my A100 using xda app-developers app
plznote said:
Try a full wipe, and fast boot a stock image on and proceed from there.
Sent from my A100 using xda app-developers app
Click to expand...
Click to collapse
I've done that twice already and usually wipe after it freezes but then still happens
Are you sure you know how to flash? Not trying to offend but it saves a lot of time if your a noob.
I currently wipe dalvik cache 3x, cache 3x, and factory reset 3x in twrp. I read somewhere its safer to wipe like this or use super wipe scripts or w.e
I am running the latest rasbeanjelly with latest rasbean gapps and latest lean kernel. I haven't had any resets and haven't tweak anything. May I also add that when I do get errors with roms normally when I flash extra mods I always go back to recovery and hit fix permissions. Idk why but it does solve some issues.
Good luck
Sent from a slice of Galaxy Nexus with some Rasbean Jelly!
lol. Ya I've been flashing roms for like a year and it's only recently these issues are popping up. I do pretty much what everyone does - wipe data, wipe cache, wipe dalvik, flash rom, flash gapps and flash kernel. I never use mods so nothing to worry about there.
Try flashing rom and gapps only without a custom kernel.
If you've fully formatted your drive, have updated recovery, and are positive you have good downloads then your problem is most likely hardware related
Try the kernel cleaner script before flashing/changing between kernels.
It's a cwm flashable .zip.
Alright will do as suggested
How about fastboot flashing the stock rom's .img-es? (Galaxy Nexus ToolKit is the easiest way to do it)
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Alright so it seems like the rom HumberOS with built in kernel did the job. Been using the phone for about 4 hours non stop and no freezes or reboots so far. Finally something stable for my phone! Thanks for the help everyone!
update: After a day without any hiccups on the humber os rom, my phone finally froze and rebooted. Since I was using cwm, I decided to see if twrp would solve the problem. I restored my phone to stock and started from scratch by installing twrp. Then I decided to give PA a try and to my surprise no reboots or freezes at all but will have to wait a day to confirm.
nav200 said:
update: After a day without any hiccups on the humber os rom, my phone finally froze and rebooted. Since I was using cwm, I decided to see if twrp would solve the problem. I restored my phone to stock and started from scratch by installing twrp. Then I decided to give PA a try and to my surprise no reboots or freezes at all but will have to wait a day to confirm.
Click to expand...
Click to collapse
You did restore the factory images by running the update script included in the package right? This will make sure all data is up to date.. Fastboot erase all partitions first as well..
Sdobron said:
You did restore the factory images by running the update script included in the package right? This will make sure all data is up to date.. Fastboot erase all partitions first as well..
Click to expand...
Click to collapse
yup did all that and everything seems to be going fine so far
So... what would be causing the problem you think?
You installed TWRP and PA both at the same as I can read in the previous posts?
So that way we will never know if it's a recovery problem, or ROM problem...
Well, as long as your device doesn't freeze and/or reboot we should be happy I guess.