I'm relatively new to the rooting community, but I think I'm doing pretty good. I have my DX2 running Eclipse 2.0.1 and am about to install Speedy v7. I am supposed to flash the .zip using BSR, which is no problem. My question is, what all does flashing involve? Should I automatically know to wipe cache when flashing? Just curious
Another questions while I'm here. I'm running Eclipse 2.0.1, let's say I wanted to try out another rom (such as Liberty), do I just flash (like above) the new rom? Or do I have to do something special for flashing roms as opposed to mod scripts (such as speedy v7)? And if I nandroid Eclipse before flashing a new rom, can I easily restore my nandroid?
Big big big thanks!
"Flashing" is just a term that means to overwrite something to make changes. Thats as much as I can tell you about that. lol
If you are wanting to flash other ROMs over your eclipse rom, you need to be on the same kernel. Since you are using Eclipse 2.0.1, I think its safe to say you are running Android 2.3.5. If you have another ROM that is built off of Android 2.3.5 then you should be safe to wipe cache, dalvik cache and flash right over it. Some might require you to do a factory reset but its not always necessary. But if you want to use a ROM based off of 2.3.4, like I think Liberty is (I'm not sure if its been updated), then you have to first be on stock 2.3.4. Which means going through the process of downgrading your OS first.
And about wiping cache and all, I would say just do it before flashing anything. It doesnt hurt and doesnt take long. Before you use any scripts though, make sure it has been updated for 2.3.5 ROMs. Otherwise you will get a bootloop and be stuck.
I hope that sheds some light on your question and didnt confuse you more. lol
No that definitely clears some things up for me, thanks
As far as downgrading the OS. Does that require the RSD/SBF process? If so, I'm familiar with that.
wesf90 said:
No that definitely clears some things up for me, thanks
As far as downgrading the OS. Does that require the RSD/SBF process? If so, I'm familiar with that.
Click to expand...
Click to collapse
Yes. Thats all you need. Just use the right SBF file. Ive been told you can SBF to a lower Android OS but I havent done it yet.
jsgraphicart said:
Yes. Thats all you need. Just use the right SBF file. Ive been told you can SBF to a lower Android OS but I havent done it yet.
Click to expand...
Click to collapse
You can SBF to the original 2.2 froyo the X2 had and either stay there or ride the two OTA updates back to 2.3.4
Thanks to both of you. I feel pretty confident now. Hopefully this topic will help someone else along the way with the same questions
wesf90 said:
Thanks to both of you. I feel pretty confident now. Hopefully this topic will help someone else along the way with the same questions
Click to expand...
Click to collapse
No problem. Hey since its solved put (Solved) in the OP subject line in front of the orginial subject so people will know
Good call. Done
jsgraphicart said:
"Flashing" is just a term that means to overwrite something to make changes. Thats as much as I can tell you about that. lol
If you are wanting to flash other ROMs over your eclipse rom, you need to be on the same kernel. Since you are using Eclipse 2.0.1, I think its safe to say you are running Android 2.3.5. If you have another ROM that is built off of Android 2.3.5 then you should be safe to wipe cache, dalvik cache and flash right over it. Some might require you to do a factory reset but its not always necessary. But if you want to use a ROM based off of 2.3.4, like I think Liberty is (I'm not sure if its been updated), then you have to first be on stock 2.3.4. Which means going through the process of downgrading your OS first.
And about wiping cache and all, I would say just do it before flashing anything. It doesnt hurt and doesnt take long. Before you use any scripts though, make sure it has been updated for 2.3.5 ROMs. Otherwise you will get a bootloop and be stuck.
I
I hope that sheds some light on your question and didnt confuse you more. lol
Click to expand...
Click to collapse
In reference to your comment about bootloop.
If u make a nandroid before flashing something (and u don't wipe data before rebooting) and you get stuck in boutloop,
Just pull battery and plug in.
BSR will come up an you can restore your nandroid and will be up and running again no problem.
Is it wise to make superwipe every time when flashing a new rom?
Can this damage the phone?Beacause every time when i flash a new rom i make superwipe.
Before the EVO i had an ideos x5 and before the flashing i was making clean cache ,dalvin cache and manualy format the system partition.
yannis_labs said:
Is it wise to make superwipe every time when flashing a new rom?
Can this damage the phone?Beacause every time when i flash a new rom i make superwipe.
Before the EVO i had an ideos x5 and before the flashing i was making clean cache ,dalvin cache and manualy format the system partition.
Click to expand...
Click to collapse
No, it won't damage the phone in any way.
Its always a good idea to do when flashing a new rom.
Only if your flashing an updated version of the same rom with same base, its not necessary and you would probably want to keep all your data and settings.
zcink said:
No, it won't damage the phone in any way.
Its always a good idea to do when flashing a new rom.
Only if your flashing an updated version of the same rom with same base, its not necessary and you would probably want to keep all your data and settings.
Click to expand...
Click to collapse
I agree in all counts except to add that sometimes it is necessary to wipe, even on the same Rom. For example, if the dev changes from odex to deodex or vice versa, you should wipe. I recommend you follow whatever is suggested by the dev.
Sent from my PG86100
I've never used super wipe and get along just fine. I've flashed GB roms, ICS roms, sense, cm, miui back and forth many times.
"How come you are not baptized?"
You dont really need it per-say but it always handy to have on the sd card. No damage is caused.
Latest Superwipe
hi all, sorry to bring up this thread back to front...some questions;
1. wondering if this thread's superwipe is still in use..?
2. i found other superwipes in the OP's ROM thread, which one is the latest? is it the 'Modified_Superwipe.zip (2.232 Mb)'
3. can i use this to flash any roms? (unless the OP has a particular included)
thanks in advance
RNZart said:
hi all, sorry to bring up this thread back to front...some questions;
1. wondering if this thread's superwipe is still in use..?
2. i found other superwipes in the OP's ROM thread, which one is the latest? is it the 'Modified_Superwipe.zip (2.232 Mb)'
3. can i use this to flash any roms? (unless the OP has a particular included)
thanks in advance
Click to expand...
Click to collapse
1. I use it sometimes and it seems to work well.
2. Not sure if that's the latest, but I do use Chad's Modified Superwipe most of the time.
3. I believe so. The only thing I've heard lately is to NOT do a superwipe before flashing on of the CyanogenMod 9 ports as that has caused people to have bootloops.
Hey guys. I'm fairly new to flashing and changing ROMs. I've read through a bunch of the stuff about it but I have a few questions and instead of posting in a bunch of different places I figured I'd ask it all in one post.
First off using TWRP I have rooted the phone, unlocked the bootloader, and installed Charmeleon ROM without any problems. Here's where the questions come in. Lets say I wanted to flash a mod or something. Would I just flash it the way I did the Charmeleon ROM, but only clearing the cache and the davlik cache? Do I even need to clear those chaches? Also, if a new version of the ROM came out would I need to clear anything special or just flash it?
I'm assuming if I want to try out a new ROM that I'd do a full wipe (cache, davlik cache, factory reset, and system) and flash it.
And hopefully my last question is if I wanted to go back to the stock ROM would I just restore my nandroid backup?
Again sorry about all the questions? I just don't want to accidentally mess up my new phone.
Thanks
crown drinker said:
Hey guys. I'm fairly new to flashing and changing ROMs. I've read through a bunch of the stuff about it but I have a few questions and instead of posting in a bunch of different places I figured I'd ask it all in one post.
First off using TWRP I have rooted the phone, unlocked the bootloader, and installed Charmeleon ROM without any problems. Here's where the questions come in. Lets say I wanted to flash a mod or something. Would I just flash it the way I did the Charmeleon ROM, but only clearing the cache and the davlik cache? Do I even need to clear those chaches? Also, if a new version of the ROM came out would I need to clear anything special or just flash it?
I'm assuming if I want to try out a new ROM that I'd do a full wipe (cache, davlik cache, factory reset, and system) and flash it.
And hopefully my last question is if I wanted to go back to the stock ROM would I just restore my nandroid backup?
Again sorry about all the questions? I just don't want to accidentally mess up my new phone.
Thanks
Click to expand...
Click to collapse
1. As long as its a flashable zip yes. Its always good practice to wipe dalvik and caches when flashing mods.usually you can just flash over rhe old one unless stated otherwise.
2.yes full wipe.
3.thats correct.
Sent from my EVO using xda premium
You dont need a full wipe if its a update to the ROM.
Sent from my EVO using XDA
Thanks guys
If I install a kernel, do I have to reinstall everything? Like.. Does it work as an update on the phone, or does it work like a reinstallation?
I tried to search, but I couldn't find anything that answered it.
Btw the kernel is EternityProject
Thanks in advance!
mortenmoulder said:
If I install a kernel, do I have to reinstall everything? Like.. Does it work as an update on the phone, or does it work like a reinstallation?
I tried to search, but I couldn't find anything that answered it.
Btw the kernel is EternityProject
Thanks in advance!
Click to expand...
Click to collapse
If you are just flashing a kernel, it will not touch the rom, so you shouldn't lose your data. Just make sure that the kernel is compatible with the device and the rom in question. If you flash a ROM, or a ROM/KERNEL combo, you will likely lose everything and start from scratch.
Best practice is to make a nandroid backup of your device before you flash *anything*, just in case, and as an extra precaution, copy the nandroid backup to your computer for safe keeping. It's also not always required, but I recommend wiping your cache and dalvik cache when flashing a kernel, just in case, but this will cause your first boot to take longer, in some cases (and on some older devices specifically) this can take several minutes, but usually doesn't take that long.
If you need anything else, feel free to send me a PM, I'll see if I can help.
Hi,
I rooted my GSII, using step 2c from the guide found here: http://forum.xda-developers.com/showthread.php?t=1311081 with the UCKK6 Stock + Root package found here: http://forum.xda-developers.com/showthread.php?t=1286432
Afterwards, I used CWM to flash PhoneBricker v2.7 (http://forum.xda-developers.com/showthread.php?t=1560759). After only a few minutes of use, my phone began locking up and rebooting randomly. It didn't matter what I was doing at the time. After reading through some threads, I tried wiping cache, factory reset, and flashing only the ROM again, to no avail. I also noticed the phone would get pretty hot when it would lock up.
I thought the ROM was the issue, so I flashed Mystic's Glory ROM (v.4.9.2beta) after wiping cache, factory reset. Same behavior.
I've resorted to restoring the first nandroid backup I did, which is just stock + root.
Would anyone have any suggestions? Thank you.
I'm not sure i have a suggestion, but i do have a couple of questions, maybe these will at least rule out some obvious possibilities:
- first, the obvious. This is probably not the issue in your case, but since this happens so often i figured I'd ask: we often see people here who have a different SGS2 variant than the I-777 the ROMs on this forum are for. Which variant of the SGS2 do you have? To use the ROMs here it should be I-777, which is AT&T's version of the SGS2, but NOT the skyrocket. If you have a skyrocket or a non-AT&T version, you need to get the ROMs from the appropriate forums.
-Since the FCs are happening with different ROMs, maybe the problem is being caused by an app or app restore method. Do the problems start before you even restore or install your apps, or after? If you are restoring apps with Titanium Backup, make sure you don't restore any system apps, only user apps. Restoring system apps with TiBu is known to cause problems, specially if you restore system apps that you backed up from a different base
Edit: still in the spirit of ruling out the obvious, when you wipe cache before installing the ROM, i assume you are ALSO wiping the dalvik cache?
wgoldfarb said:
I'm not sure i have a suggestion, but i do have a couple of questions, maybe these will at least rule out some obvious possibilities:
- first, the obvious. This is probably not the issue in your case, but since this happens so often i figured I'd ask: we often see people here who have a different SGS2 variant than the I-777 the ROMs on this forum are for. Which variant of the SGS2 do you have? To use the ROMs here it should be I-777, which is AT&T's version of the SGS2, but NOT the skyrocket. If you have a skyrocket or a non-AT&T version, you need to get the ROMs from the appropriate forums.
-Since the FCs are happening with different ROMs, maybe the problem is being caused by an app or app restore method. Do the problems start before you even restore or install your apps, or after? If you are restoring apps with Titanium Backup, make sure you don't restore any system apps, only user apps. Restoring system apps with TiBu is known to cause problems, specially if you restore system apps that you backed up from a different base
Edit: still in the spirit of ruling out the obvious, when you wipe cache before installing the ROM, i assume you are ALSO wiping the dalvik cache?
Click to expand...
Click to collapse
wgoldfarb,
I do, in fact, have the I777 variant.
Can you please tell me what you mean by FCs?
The random lockups/reboots began even before I started installing other apps. I do not have Titanium Backup. I installed the apps from the Play store.
Yes, I made sure to do a factory reset, wipe cache, and wipe dalvik cache.
Could it be an issue with the way the ROM is handling CPU usage? Perhaps there is a preset that is on by default that may be causing lockups.
I'm also wondering rooting using the UCKK6 package was the correct way, as opposed to rooting back to the UCKH7.
I appreciate your help.
What kernel are you running? That sounds like the issue to me
jthatch12 said:
What kernel are you running? That sounds like the issue to me
Click to expand...
Click to collapse
jthatch,
When I rooted, it remained as stock kernel (2.6.35.7).
When I flashed PhoneBricker and Mystic's Glory, I stayed with the kernels that were supplied by the ROM zip package.
wwjd3 said:
jthatch,
When I rooted, it remained as stock kernel (2.6.35.7).
When I flashed PhoneBricker and Mystic's Glory, I stayed with the kernels that were supplied by the ROM zip package.
Click to expand...
Click to collapse
You can't flash a "rom zip package" from the stock kernel with 3e recovery. You need to install a custom kernel with ClockworkMod Recovery first before you install a "rom zip package". So what you are saying is not making sense.
I really don't think it would make any difference whether you used the UCKK6 plus root or the UCKH7 plus root.
Whenever you change base, it is necessary to perform a wipe data/factory reset, and also recommended to wipe cache and to wipe dalvik cache. These should be performed from within Recovery. The wipe data/factory reset should not be performed from the phone settings.
If you flash a new firmware after doing the proper wipes in recovery before flashing, then the new firmware should run without problems, unless the download was bad, causing a bad flash. You should also check the md5 sum of the downloaded file to verify a good download before you flash it.
creepyncrawly said:
You can't flash a "rom zip package" from the stock kernel with 3e recovery. You need to install a custom kernel with ClockworkMod Recovery first before you install a "rom zip package". So what you are saying is not making sense.
I really don't think it would make any difference whether you used the UCKK6 plus root or the UCKH7 plus root.
Whenever you change base, it is necessary to perform a wipe data/factory reset, and also recommended to wipe cache and to wipe dalvik cache. These should be performed from within Recovery. The wipe data/factory reset should not be performed from the phone settings.
If you flash a new firmware after doing the proper wipes in recovery before flashing, then the new firmware should run without problems, unless the download was bad, causing a bad flash. You should also check the md5 sum of the downloaded file to verify a good download before you flash it.
Click to expand...
Click to collapse
I'm sorry. I failed to mention that after rooting, I used MobileOdin to flash a custom kernel (Siyah 2.6) with CWM (step 3a in the first link I provided). From there, before flashing PhoneBricker, I did a factory reset, cache wipe, dalvik cache wipe, all from within CWM. I did NOT perform factory reset from phone settings.
I have not performed a md5 sum check. I guess that would be the next step.
Wwjd3
You are now getting help from extremely knowledgeable people, so i wont even try to add any suggestions...you are in excellent hands
I only wanted to answer your question about "FCs". By FCs I meant forced closes...it's when an app has a problem or stops responding and you get a message saying the app had a problem and had to close. When you said your phone locks up i assumed you meant you were experiencing forced closes.
wgoldfarb said:
Wwjd3
You are now getting help from extremely knowledgeable people, so i wont even try to add any suggestions...you are in excellent hands
I only wanted to answer your question about "FCs". By FCs I meant forced closes...it's when an app has a problem or stops responding and you get a message saying the app had a problem and had to close. When you said your phone locks up i assumed you meant you were experiencing forced closes.
Click to expand...
Click to collapse
Ah, I understand. What I meant by lockup is that the system freezes. The capacitive buttons no longer respond. Neither do the volume/power buttons. The screen simply freezes, and I have to force a restart by holding down the power button for a number of seconds. I hope that makes sense.
Wow. Well, I hate to say it, but...lol I would go back to stock 2.3.4 with Odin, wipe everything, and try again. I mean that answer sucks. But it may help rule out some things and give u an idea if its hardware or software related. U could also try different kernels and using the kernel cleaning script, just Google it with xda in the search and it'll come up.
Sent from my SGH-I777 using Tapatalk 2
Phalanx7621 said:
Wow. Well, I hate to say it, but...lol I would go back to stock 2.3.4 with Odin, wipe everything, and try again. I mean that answer sucks. But it may help rule out some things and give u an idea if its hardware or software related. U could also try different kernels and using the kernel cleaning script, just Google it with xda in the search and it'll come up.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Phalanx7621,
heh. That's what I'm thinking of doing. Can someone clarify, though: according to the forum stickies, when flashing a custom kernel with CWM after rooting, there are only two available, correct? Daily Driver and Siyah.
Secondly, can you briefly describe what the kernel cleaning script accomplishes. I've seen the term in some posts, but didn't think it was relevant. Thank you.
wwjd3 said:
Phalanx7621,
heh. That's what I'm thinking of doing. Can someone clarify, though: according to the forum stickies, when flashing a custom kernel with CWM after rooting, there are only two available, correct? Daily Driver and Siyah.
Secondly, can you briefly describe what the kernel cleaning script accomplishes. I've seen the term in some posts, but didn't think it was relevant. Thank you.
Click to expand...
Click to collapse
1. Short answer - yes. Long answer - no (I remember a few other options floating around). For all intents and purposes, just pick one of those; either will accomplish what you need.
2. From what I remember about looking at the script, it wipes dalvik cache and deletes the contents of /etc/int.d (to prevent incompatible scripts across kernels - not exactly relevant since you're doing clean installs). No rom should have kernel specific scripts anyway. I think it wipes some system caches or something also.
Simba501 said:
not exactly relevant since you're doing clean installs). No rom should have kernel specific scripts anyway. I think it wipes some system caches or something also.
Click to expand...
Click to collapse
If I read correctly, Phalanx was offering up a secondary option to try out before taking the complete stock route which would make it relevant. However, if he does the return to stock... Then you're right, not gonna do much for him. (though it wouldn't hurt)
Clay
Team Pirate
Sent from my PINK SGH-I777
You've described following the correct procedure for rooting and flashing a custom firmware. I don't see anything in that procedure that could cause firmware problems, except perhaps corrupt downloads. But the odds are against getting two corrupd downloads in a row.
If it were my phone, I would probably flash back to stock, and run it a few days to see if it runs correctly, to rule out hardware problems. If there is developing hardware issues, bad memory perhaps, then it should be evident even on straight stock.
The next thing is to just start from scratch, and do everything over again. When I flashed SHOstock2 1.4.1 over 1.3.2 (change of base) I did everything right, but I got apps freezing and other problems, so much that the phone was unusable. I went back to 1.3.2 for a week, then flashed 1.4.2 successfully. So the answer could be just a bad flash even though you can't put your finger on the exact reason.
creepyncrawly said:
You've described following the correct procedure for rooting and flashing a custom firmware. I don't see anything in that procedure that could cause firmware problems, except perhaps corrupt downloads. But the odds are against getting two corrupd downloads in a row.
If it were my phone, I would probably flash back to stock, and run it a few days to see if it runs correctly, to rule out hardware problems. If there is developing hardware issues, bad memory perhaps, then it should be evident even on straight stock.
The next thing is to just start from scratch, and do everything over again. When I flashed SHOstock2 1.4.1 over 1.3.2 (change of base) I did everything right, but I got apps freezing and other problems, so much that the phone was unusable. I went back to 1.3.2 for a week, then flashed 1.4.2 successfully. So the answer could be just a bad flash even though you can't put your finger on the exact reason.
Click to expand...
Click to collapse
I just used your guide to return back to stock UCKH7. I am attempting to root again, this time using DooMLoRD's Easy Rooting Toolkit. Not having any luck with that one (complaining about "cannot stat files"). I'm looking through the I777 forums but there is no chatter about this issue. There is for other phones, however. And the search continues. Thanks for your help!
wwjd3 said:
I just used your guide to return back to stock UCKH7. I am attempting to root again, this time using DooMLoRD's Easy Rooting Toolkit. Not having any luck with that one (complaining about "cannot stat files"). I'm looking through the I777 forums but there is no chatter about this issue. There is for other phones, however. And the search continues. Thanks for your help!
Click to expand...
Click to collapse
How did you root your phone b4? which method?
Use that.
votinh said:
How did you root your phone b4? which method?
Use that.
Click to expand...
Click to collapse
I used method 2c, Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package with Modem using Odin3 One-Click Downloader previously. I was thinking of using a different method, since I ran into problems using Entropy512's method. Try something different.
-------------------------------------------------
EDIT:
I'm sorry, I was wrong. Since I had UCKK6 build previously I used Odin to flash the Kernel + cache + rooted UCKK6 system package found here: http://forum.xda-developers.com/showthread.php?t=1286432
So, using method 2c would, in fact, be a different method altogether. I'm beginning to think that initially rooting using Odin+UCKK6 package is what got me into trouble in the first place.
wwjd3 said:
I'm beginning to think that initially rooting using Odin+UCKK6 package is what got me into trouble in the first place.
Click to expand...
Click to collapse
It's as good a theory as any other... I guess.