Related
I've looked around for a little while and can't find any thread that says how to go from one build of a custom ROM to another... I feel extremely noobish asking this as well. I'm on build 11 of bean's custom JB ROM and there have been three new builds and I'm wondering if I need to do a full wipe as if I were flashing a ROM from stock, or if I just go ahead and do a dirty flash... Thanks in advance for the help
Sent from my SCH-I535 using xda app-developers app
jonnyboiii said:
I've looked around for a little while and can't find any thread that says how to go from one build of a custom ROM to another... I feel extremely noobish asking this as well. I'm on build 11 of bean's custom JB ROM and there have been three new builds and I'm wondering if I need to do a full wipe as if I were flashing a ROM from stock, or if I just go ahead and do a dirty flash... Thanks in advance for the help
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
It's really at your own discretion. You can dirty flash, but you might have issues, but clean flashes are always the best path to take. Although, sometimes the devs do recommend a clean flash on some releases when they change something major.
Sent from my SCH-I535 using xda app-developers app
Personally I always dirty flash. A couple of times I've encountered problems, made a backup then wiped to troubleshoot the problem, but its never fixed anything so I just revert to my backup. YMMV
Just read and follow the install instructions for the specific rom.
Sent from my Galaxy SIII
PaulG1488 said:
Just read and follow the install instructions for the specific rom.
Sent from my Galaxy SIII
Click to expand...
Click to collapse
So you're saying I should do a clean wipe and start fresh?
Sent from my SCH-I535 using Tapatalk 2
jonnyboiii said:
So you're saying I should do a clean wipe and start fresh?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
In a nutshell, yes
Sent from my SCH-I535 using xda app-developers app
jonnyboiii said:
So you're saying I should do a clean wipe and start fresh?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
The OP usually tells you what you need to do. If there are major changes, they will tell you to wipe. Sometimes, dirty flashing is okay, just make sure that you follow the directions from the dev that created the ROM.
Sent from my SCH-I535 using xda premium
HHF2 said:
The OP usually tells you what you need to do. If there are major changes, they will tell you to wipe. Sometimes, dirty flashing is okay, just make sure that you follow the directions from the dev that created the ROM.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
But if you encounter errors after dirty flashing, always do a full wipe and reflash before reporting them.
Sent from my GT-I9300 using Tapatalk 2
Just dirty flash it. Backup your apps and etc... prior just in case you do run into issues.
jonnyboiii said:
I've looked around for a little while and can't find any thread that says how to go from one build of a custom ROM to another... I feel extremely noobish asking this as well. I'm on build 11 of bean's custom JB ROM and there have been three new builds and I'm wondering if I need to do a full wipe as if I were flashing a ROM from stock, or if I just go ahead and do a dirty flash... Thanks in advance for the help
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Format and flash.
As a general rule, I do an App backup (I tend to like My Backup Pro for app backups), a full nandroid backup, then dirty flash (wiping dalvik/cache) and see how it goes. Best case, everything works and I save myself a ton of time not having to restore apps/reapply settings. Worst case, if I have problems that don't seem to be generally reported, I do a full wipe and clean install.
jonnyboiii said:
I've looked around for a little while and can't find any thread that says how to go from one build of a custom ROM to another... I feel extremely noobish asking this as well. I'm on build 11 of bean's custom JB ROM and there have been three new builds and I'm wondering if I need to do a full wipe as if I were flashing a ROM from stock, or if I just go ahead and do a dirty flash... Thanks in advance for the help
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I'm rooting a friends at&t skyrocket tomorrow that is on official ics update from at&t and was wondering if that brick bug was still present.I know i might be a little late with this. I was told by a friend that it was only present on the ics leaks for this phone and just wanted to make sure now that this has official ics that i won't have any problems worrying about a brick on my hands by wiping data factory reset in cwm. Go easy on me please I was on the OG evo when all of this brick stuff happened so I never payed much attention to it
Thanks in advance
Sent from my SPH-L710 using xda app-developers app
I could be wrong but I thought the bug was only present in the i777 gs2...
Sent from my SAMSUNG-SGH-I727 using xda premium
Vfan23 said:
I could be wrong but I thought the bug was only present in the i777 gs2...
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I thought it was for all gs2 variants
Sent from my SPH-L710 using xda app-developers app
Regardless, wiping data/factory reset using cwm won't effect anything. I'm pretty sure that problem was the result of wiping in the phones settings menu (if I remember right).
btm fdr said:
Regardless, wiping data/factory reset using cwm won't effect anything. I'm pretty sure that problem was the result of wiping in the phones settings menu (if I remember right).
Click to expand...
Click to collapse
O okay wasn't it a kernel issue ? Like it had a erase command or something?
Sent from my SPH-L710 using xda app-developers app
evo4gnoob said:
O okay wasn't it a kernel issue ? Like it had a erase command or something?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Honestly, i'm not sure. I never really worried about it. Always use CWM for wiping and never had a problem with anything.
I think it happens when you try to format the internal SD card. Its an emmc bug (I think) but I don't have the bug and my i777 doesn't have it. I thought it was on the specific kernel for the i777 and the international variants.
Sent from my SAMSUNG-SGH-I727 using xda premium
Thanks for the info guys hopefully nothing goes wrong when i try flashing AOKP on his phone when im done rooting it
evo4gnoob said:
Thanks for the info guys hopefully nothing goes wrong when i try flashing AOKP on his phone when im done rooting it
Click to expand...
Click to collapse
No sense in rooting if your gonna flash aokp. Just push cwm with Odin and flash away:thumbup: you can flash without rooting as long as you have a custom recovery installed
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
evo4gnoob said:
Thanks for the info guys hopefully nothing goes wrong when i try flashing AOKP on his phone when im done rooting it
Click to expand...
Click to collapse
Just follow the sticky here - http://forum.xda-developers.com/showthread.php?t=1652398
Once you get it rooted with CWM, i'd suggest updating CWM to this version - http://forum.xda-developers.com/showthread.php?t=1777970
If you're looking for the JellyBean version of AOKP, i'd really suggest this - http://rootzwiki.com/topic/34092-aokp-unofficial-galaxy-s-ii-skyrocket-i727-nov-04-milestone-1/
As far as flashing it, I:
-wipe data/factory reset
-wipe cache
-mounts & storage [format /system]
-advanced [wipe dalvick cache]
-flash rom
-flash gapps
-reboot
*you can do these x2 or x3 each if you wish just to be sure everything is clear*
Hopefully some of this will help if you already don't know any of it. Any other questions, shoot me a pm if you need or i'm sure someone here can help.
cdshepherd said:
No sense in rooting if your gonna flash aokp. Just push cwm with Odin and flash away:thumbup: you can flash without rooting as long as you have a custom recovery installed
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
i know its that he wants to backup apps ect so i need root to use titanium backup before i start wiping and flashing
btm fdr said:
Just follow the sticky here - http://forum.xda-developers.com/showthread.php?t=1652398
Once you get it rooted with CWM, i'd suggest updating CWM to this version - http://forum.xda-developers.com/showthread.php?t=1777970
If you're looking for the JellyBean version of AOKP, i'd really suggest this - http://rootzwiki.com/topic/34092-aokp-unofficial-galaxy-s-ii-skyrocket-i727-nov-04-milestone-1/
As far as flashing it, I:
-wipe data/factory reset
-wipe cache
-mounts & storage [format /system]
-advanced [wipe dalvick cache]
-flash rom
-flash gapps
-reboot
*you can do these x2 or x3 each if you wish just to be sure everything is clear*
Hopefully some of this will help if you already don't know any of it. Any other questions, shoot me a pm if you need or i'm sure someone here can help.
Click to expand...
Click to collapse
i already had that version of aokp and have everything installed and in a folder im prepared . And that the same process i use on my GS3 but i use TWRP. Yea i was looking at that updated version i was gonna flash TWRP through odin for his phone but looks like CWM touch looks better on this phone then it was for my original evo and GS3
edit: do you have any kernel recommendations for this phone? I was gonna flash this kernel http://forum.xda-developers.com/showthread.php?t=1949828 but i dont have this phone so i wouldnt really know which kernel work best. He really wants to overclock so thats the only preference he wants to be able to do
Hi, I used this method for my gs2 international. Using the zip method of Cwm and it worked without problems. http://forum.xda-developers.com/showthread.php?p=28178105 The big bug is also details in the links. Good luck.
Sent from my GT-I9100 using xda app-developers app
Macros_the_Black said:
Hi, I used this method for my gs2 international. Using the zip method of Cwm and it worked without problems. http://forum.xda-developers.com/showthread.php?p=28178105 The big bug is also details in the links. Good luck.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
thanks ill be sure to take a look at it
evo4gnoob said:
i know its that he wants to backup apps ect so i need root to use titanium backup before i start wiping and flashing
Click to expand...
Click to collapse
Make sure not to restore system apps.
evo4gnoob said:
i already had that version of aokp and have everything installed and in a folder im prepared . And that the same process i use on my GS3 but i use TWRP. Yea i was looking at that updated version i was gonna flash TWRP through odin for his phone but looks like CWM touch looks better on this phone then it was for my original evo and GS3
edit: do you have any kernel recommendations for this phone? I was gonna flash this kernel http://forum.xda-developers.com/showthread.php?t=1949828 but i dont have this phone so i wouldnt really know which kernel work best. He really wants to overclock so thats the only preference he wants to be able to do
Click to expand...
Click to collapse
I always use the stock kernel. I don't mess with oc/uv or anything. I don't see a need for it.
evo4gnoob said:
thanks ill be sure to take a look at it
Click to expand...
Click to collapse
Personally, i'd stick with the Odin method.
btm fdr said:
Make sure not to restore system apps.
I always use the stock kernel. I don't mess with oc/uv or anything. I don't see a need for it.
Personally, i'd stick with the Odin method.
Click to expand...
Click to collapse
im aware that you should never restore system apps. Hmm looks like i have to test these kernels out on his phone and yea odin method is the method i used to root a friends Skyrocket a while back
evo4gnoob said:
yea odin method is the method i used to root a friends Skyrocket a while back
Click to expand...
Click to collapse
Me me me me....hi Albert
----------------------------------------------
Sent from my Skyrocket i727 running Liquid
One does not simply use the search button
Mike on XDA said:
Me me me me....hi Albert
----------------------------------------------
Sent from my Skyrocket i727 running Liquid
One does not simply use the search button
Click to expand...
Click to collapse
Stalking smh
Sent from my SPH-L710 using xda app-developers app
So I've been looking for a fix w/ my problem and haven't come across anything that works.
I installed CM 10.1 6/30 nightly. Phone worked great...but then all of a sudden my phone has stopped working.
I Odin'd back to stock...but my camera is still failing. I'm back at MF1 now...but I'm just trying to find a fix to get my camera working again.
Anyone have any info that could possibly help me out?
Thanks
Dep
Try clearing data and cache for the camera, reboot to recovery, and fix permissions. Let us know how it goes!
Sent from my SAMSUNG-SGH-T999 using Tapatalk 2
What's your baseband version?
Sent from my SCH-I535 using Tapatalk 4 Beta
cleared data/cache for camera, rebooted to recovery and did fix permissions. it didn't work.
i'm running the i535vrbmf1 baseband.
idk why my camera won't work. it just keeps failing. any help would be most appreciated.
TheKucho said:
Try clearing data and cache for the camera, reboot to recovery, and fix permissions. Let us know how it goes!
Sent from my SAMSUNG-SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Addiso said:
What's your baseband version?
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Camera failing...
deputyvanhalen said:
cleared data/cache for camera, rebooted to recovery and did fix permissions. it didn't work.
i'm running the i535vrbmf1 baseband.
idk why my camera won't work. it just keeps failing. any help would be most appreciated.
Click to expand...
Click to collapse
Try flashing the VRBMB1 baseband. The new updates didnt play well with roms using the older base and caused camera issues.
Yeah but he's on mf1 rom not mb1
Sent from my SCH-I535 using Tapatalk 4 Beta
Just need to flash a new kernal. I flashed KT747 AOSP version & didn't have any issues.
Sent from my SCH-I535 using xda app-developers app
Ok, I'll give a new kernel a shot.
sjpritch25 said:
Just need to flash a new kernal. I flashed KT747 AOSP version & didn't have any issues.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
So I'm on the latest CM nightly 7/16. I just flashed a new kernel hoping that would help (KT747).
Phone still has a "can't connect to camera" message pop up when I try my camera. This is getting quite worrying. Nothing I do seems to be working.
I'm desperate for your help.
Addiso said:
Yeah but he's on mf1 rom not mb1
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
sjpritch25 said:
Just need to flash a new kernal. I flashed KT747 AOSP version & didn't have any issues.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
dustin_b said:
Try flashing the VRBMB1 baseband. The new updates didnt play well with roms using the older base and caused camera issues.
Click to expand...
Click to collapse
deputyvanhalen said:
Ok, I'll give a new kernel a shot.
Click to expand...
Click to collapse
Also just as an fyi. I've odin'd back to stock, etc. Even then my camera failed. Something with my firmware is messed up...I really appreciate any help.
Okay so I bought a Blaze a few days ago and I was messing around with it and I rooted it. When I rooted it I flashed a ROM and when the ROM booted up and got to the welcome screen it instantly turned rebooted itself, so I let it boot up again but it constantly reboots. Then I went back to a backup of the stock ROM and it still does the same thing. So I followed a guide that updated me to the ICS update in hopes of it fixing it but it still does the same thing! Now I don't know what to do with it. I was hoping maybe someone can help or if this has happened to anyone? Thanks in advance
Favelarx said:
Okay so I bought a Blaze a few days ago and I was messing around with it and I rooted it. When I rooted it I flashed a ROM and when the ROM booted up and got to the welcome screen it instantly turned rebooted itself, so I let it boot up again but it constantly reboots. Then I went back to a backup of the stock ROM and it still does the same thing. So I followed a guide that updated me to the ICS update in hopes of it fixing it but it still does the same thing! Now I don't know what to do with it. I was hoping maybe someone can help or if this has happened to anyone? Thanks in advance
Click to expand...
Click to collapse
did you wipe data/cache/dalvik in recovery?
Yes I did all of that like a billion times and still nothing
I see you only have ten post so my first question is are you just new to xda and have knowledge and experience with root and recovery and custom roms or is this all new to you?
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
Jserrano56 said:
I see you only have ten post so my first question is are you just new to xda and have knowledge and experience with root and recovery and custom roms or is this all new to you?
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've been a member for a while I just don't post much but no this is not all new to me, I have some experience and knowledge with rooting, and installing ROM's and such. I am new to this phone though.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
What ROM and kernel were you trying to flash? What recovery did you flash?
Romman0 said:
What ROM and kernel were you trying to flash? What recovery did you flash?
Click to expand...
Click to collapse
I was trying to flash the MIUI build and I think it came with a kernel that I had to download but I'm not sure. I flashed CWM I forgot what version it was
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Yes, the miui we have has a link to racing's blue lightning. I would try miui or another ROM again, but make sure to format /system along with wiping data, cache, and davlik. Or use black hole wipe. If you don't have anything important on the internal SD (or back it up) it might be worth it to format the emmc also.
Romman0 said:
Yes, the miui we have has a link to racing's blue lightning. I would try miui or another ROM again, but make sure to format /system along with wiping data, cache, and davlik. Or use black hole wipe. If you don't have anything important on the internal SD (or back it up) it might be worth it to format the emmc also.
Click to expand...
Click to collapse
Well I already went back to stock with one of the guides posted and it still does the same thing I don't know what to do with it anymore
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
I dirty flashed 4.2.2 to 4.3 no problem but I'm having issues lately, is it safe to go back?
Thanks
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Full wipe. You dirty flashed already and are experiencing issues. It does not make sense if you were to dirty flash again.
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
Full wipe. You dirty flashed already and are experiencing issues. It does not make sense if you were to dirty flash again.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
It was working alright until a newer version that was also 4.3 came out and I flashed that.
Plus I've had to format data because I messed something up with killjoy and tkmod and experience the problems I had before that so I don't think the dirty flash is the issue.
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Aight, well you have your answer then.
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
Aight, well you have your answer then.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I don't get how I have my answer..?
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Maphack said:
I don't get how I have my answer..?
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
It's pretty simple, do a clean flash. Anytime you flash different android versions you should never dirty flash. You do realize Android 4.2.2 and Android 4.3 are completely different versions right?
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
It's pretty simple, do a clean flash. Anytime you flash different android versions you should never dirty flash. You do realize Android 4.2.2 and Android 4.3 are completely different versions right?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I guess I didn't make myself clear, I dirty flashed, had to reformat my data and flashed 4.3 again but still had the exact same problem that I did when I dirty flashed. A data format would be a clean flash amirite?
You do realize that flashing from 4.2.2 isn't like flashing 3.0 to 4.0?
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Maphack said:
I guess I didn't make myself clear, I dirty flashed, had to reformat my data and flashed 4.3 again but still had the exact same problem that I did when I dirty flashed. A data format would be a clean flash amirite?
You do realize that flashing from 4.2.2 isn't like flashing 3.0 to 4.0?
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
OK that's much more clear, a clean flash is factory reset, wipe cache and wipe dalvik cache. You can also wipe system to clear out the old rom before flashing a new one.
I don't see how data formatting would fix your bugs, but keeping your data and dirty flashing 4.3 on top of 4.2.2 would certainly give you problems.
I think a clean flash will fix everything, as long as you don't restore system data from titanium backup or something.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
OK that's much more clear, a clean flash is factory reset, wipe cache and wipe dalvik cache. You can also wipe system to clear out the old rom before flashing a new one.
I don't see how data formatting would fix your bugs, but keeping your data and dirty flashing 4.3 on top of 4.2.2 would certainly give you problems.
I think a clean flash will fix everything, as long as you don't restore system data from titanium backup or something.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I had to format data because I messed with ktoons and cputuner from killjoy because I'm an idiot.
I was just hoping someone had personal experience flashing between the two and could give me their personal experience. I was able to find a stable 4.3 version so it didn't even matter in the end.
I figured if I was asking a question like this it could be assumed I'm already aware that clean flashing is always the best thing to do and restating that really is of no use...
Thanks though.
And yeah, dirty flashing from 4.2.2 on PA is no problem if anyone cared.
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Maphack said:
I had to format data because I messed with ktoons and cputuner from killjoy because I'm an idiot.
I was just hoping someone had personal experience flashing between the two and could give me their personal experience. I was able to find a stable 4.3 version so it didn't even matter in the end.
I figured if I was asking a question like this it could be assumed I'm already aware that clean flashing is always the best thing to do and restating that really is of no use...
Thanks though.
And yeah, dirty flashing from 4.2.2 on PA is no problem if anyone cared.
Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
I'm really confused what you're getting at here. You asked a question, you got your answers, then you're saying that by the way you stated your question we should already assume that you know what you're doing?
The way you stated your question didn't really sound like you understood the difference between a dirty and clean flash. Wiping your data will have an insignificant effect if there's a problem with the rom itself because you decided to dirty flash.
Snoop obviously knows his stuff, he tells you to clean flash and you ignore it and still point out the issues you're having. If you already know what you're doing then don't waste our time and ask questions you already have your answer to.
Maybe you should point out you're looking for another experience similar to yours, we were simply giving you pointers on how to fix it, which is exactly what this forum is used for.
Just a heads up, if your cpu was giving you issues, then flashing the kernel again would've fixed your problem also. Wiping your data alone won't fix anything, you essentially just erase your own data and do nothing to the rom or kernel itself.
Hopefully your problem is fixed now.
Sent from my SCH-I535 using Tapatalk 2