Hi,
Since i'm new, I'm not able to post in Wanam's thread yet. I'm wondering if someone can help answer,
I'm currently on Wanam 5.3. It's been awhile since I last upgraded and wondering if moving to Wanam 6.5 I'll need to wipe/factory reset? Prior Wanam versions does not need to wipe but there's been many iterations since then. I prefer not to have to do a factory reset.
Also i currently have extsd2internalsd2 mod installed (for 64gb sdxc) along with Philz touchwiz.. Anyone have been using/tried all these combo and know if there's some known incompatibility issues? Certain apps like titanium backup are not too happy with some of these and had to do some workarounds before i can get it working.. that goes for backup frm cwm too.. thanks!
hexhybrid said:
Hi,
Since i'm new, I'm not able to post in Wanam's thread yet. I'm wondering if someone can help answer,
I'm currently on Wanam 5.3. It's been awhile since I last upgraded and wondering if moving to Wanam 6.5 I'll need to wipe/factory reset? Prior Wanam versions does not need to wipe but there's been many iterations since then. I prefer not to have to do a factory reset.
If the instructions say wipe you wipe .
jje
Click to expand...
Click to collapse
Thanks, but like I mentioned before this is normally a no-wipe rom. but in my case there's too big a version gap.
different base, usually = WIPE.
But try without? Then wipe if you get errors?
It literally takes an extra 20mins to set back up from a wipe so its not the end of the world anyway...
thanks! did as you suggested, upgrade went well, only had to reinstall extsd2internalsd2 mod with older version to get things working as normal. otherwise no wipe, so far no issues faced.
Related
Can anyone help.
I have recently started using Omega Rom...i previously was running stock JB.
I found Omega Rom V34 very slow, laggy and it crashed at least once a day.
I have just upgraded to V35 of omega.....its doing the same thing. Its just shocking.
With so many people using it and rating it so highly, it must be something ive done wrong as people would not use this rom as it is installed on my phone.
I used CWM recovery mode to install V34, i think its version 6.0.4? I got the CWM and rooted it etc through SGS3 Toolkit V6.
When i upgraded to V35, i simply, rebooted the phone into recovery mode using the new menu that i got from the V34 rom.
When it installs, it clears all the cache etc on its own.
When V34 installed i recovered all my apps using titanium backup. When V35 installed, for some reason all my apps were installed when it switched back on.
Any advice appreciated, im on the verge of going back stock!
Thanks
do a full wipe before updating
Glebun said:
do a full wipe before updating
Click to expand...
Click to collapse
I'm pretty sure that I did a full wipe using the Samsung galaxy S3 toolkit the time I stalled v34.
when I installed v35 just just used the installer so i don't think it did a full wipe.
Please advise the best tool for the full wipe. thanks
gaz_0001 said:
I'm pretty sure that I did a full wipe using the Samsung galaxy S3 toolkit the time I stalled v34.
when I installed v35 just just used the installer so i don't think it did a full wipe.
Please advise the best tool for the full wipe. thanks
Click to expand...
Click to collapse
i had been on omega and it was smooth as butter. perhaps there are apps that causes your phone to consume big memory and lag...
or you know, you can just flash another one if you are unhappy with it xD
saywhatt said:
i had been on omega and it was smooth as butter. perhaps there are apps that causes your phone to consume big memory and lag...
or you know, you can just flash another one if you are unhappy with it xD
Click to expand...
Click to collapse
Yeah,
I re-flashed with Android Revolution HD, and used the perseus Kernel.
Running sweet now!
Really happy with it so far.
If you're relying on the installer to clear your system and data partitions, that's where your lag and your crashes are coming from. You have to either use a Superwipe script which doesn't come with ARHD or Omega, or the much easier solution is to just clear cache/system/data partitions from recovery.
edit: let me know on here if you don't know how to do those things and I'll point you in the right direction to the best of my knowledge.
I have the same problem
Flashed latest version of OMEGA onto Samsung S3
Featurewise it's perfect, but there is an issue - like you say, it may be a clash with an installed app.
The lag is most noticeable when I bring up the Apps List, but I find over time it gets worse - if I reboot my phone it's improved again although the Apps List can still be slower than before to load.
I did think a likely candidate was avast, but I have the same issue if I don't use Avast.
Oh and I definitely wiped all relevant partitions prior to the install.
btw I'm not here to criticise OMEGA rom - didn't cost me a dime and lots of happy punters out there.
I just installed PM 4.3 and from what i read it should be compatible with newest UBER 3.0 kernal but it just stays stuck in splash (pacman roms, game over, instert coin etc.) I tried downgrading to previous twrp, reflashing rom and gapps, and also tried factory reset. Any help of info would be appreciated, sorry if this is wrong section.
l330n said:
I just installed PM 4.3 and from what i read it should be compatible with newest UBER 3.0 kernal but it just stays stuck in splash (pacman roms, game over, instert coin etc.) I tried downgrading to previous twrp, reflashing rom and gapps, and also tried factory reset. Any help of info would be appreciated, sorry if this is wrong section.
Click to expand...
Click to collapse
there is a compatible Uber for that. most developers will suggest at least 24 hours with kernel included in rom. you don't have to just suggested.
you mentioned a previous TWRP, but you didn't mention any specific versions.
2.6.0.1 is working great for me
2.6.0.3 seemed to have some issues, hence the reason I am still on 0.1
2.6.1.0 is most recent, but until I have problem with 0.1 im sticking with it.
you should always factory reset and it suggested to repeat 3-4 times to clear out any remaining leftover goop.
my routine an also used by others is...........
3 wipes, cleanliness is next to godliness
flash rom alone
flash rom again w/ gapps
wipe davlik and cache
boot up and let settle the 10 mins
reboot and set up
maybe overkill but has not failed me
captemo said:
there is a compatible Uber for that. most developers will suggest at least 24 hours with kernel included in rom. you don't have to just suggested.
you mentioned a previous TWRP, but you didn't mention any specific versions.
2.6.0.1 is working great for me
2.6.0.3 seemed to have some issues, hence the reason I am still on 0.1
2.6.1.0 is most recent, but until I have problem with 0.1 im sticking with it.
you should always factory reset and it suggested to repeat 3-4 times to clear out any remaining leftover goop.
my routine an also used by others is...........
3 wipes, cleanliness is next to godliness
flash rom alone
flash rom again w/ gapps
wipe davlik and cache
boot up and let settle the 10 mins
reboot and set up
maybe overkill but has not failed me
Click to expand...
Click to collapse
Cool, thanks for the tips, ill try them once i get home in the morning from work.
I saw someone recommend twrp 2.6.1.0 (still hangs), at first I had 2.6.3.0 (newest i believe) and still kept hanging on splash
Do you know which uber kernal is the correct one for that rom or is it just the one included in newest pacman rom 4.3?
I may just try out carbon and revolt, seems like more people running those roms. I was messing with some of the color setting in PA and phone locked up on me and it was weird, had like a greenish screen that got brighter and brighter and brighter eventually i just shut it off, it was fine when i restarted. Im not too worried about changing the colors really, i was just tryin it out.
So the other day my S3 gave up the ghost, and developed the hard-brick "QHSUSB_DLOAD" error. I have insurance so I was overnighted a new phone, and am sending the old one away. I believe this was related to a long-term power button issue I was having, perhaps a virus, or something. I had not changed anything to the ROM I was using since about October, and the issue just happened now in May.
At any rate, the new S3 I received is an MJB version, Android 4.3, Knox and all that other good stuff. After several failed attempts, I found a method to root this phone and disable Knox. The Warranty Bit is already tripped, so clearly I'm not sending this phone back until it hard bricks as well. I am trying to install the StockMOD ROM that is very popular, however I am being plagued by problem after problem.
I was able to flash a version of CWM Recovery onto my phone, but it was too old and couldn't mount any of the folders. Using ROM Manager, I was able to flash an update to my Recovery, and now it mounts and views all folders properly. However, when I go to install the StockMOD ROM, I continuously get a Status 7 error, something about "expects 5 args, got 3." I wiped the data, cache, and Dalvik, but kept getting this error. So, I had to recover my backup of stock, which didn't go well either. Once my backup was installed, all of my apps kept crashing. Gapps, ROM Manager, everything kept giving me constant FC errors. I had to wipe my data, cache, and Dalvik again and go back to factory default, and reinitialize the phone. Luckily I haven't installed anything of importance on here yet.
A quick search through here states that I need to use TWRP as my Recovery. I've flashed TWRP several times, first using the 2.6... version and then the most recent 2.7.0.0 version, and neither of these will mount any of my folders. It just gives me a litany of errors trying to mount the various locations. I've done Fix Permissions and everything else, TWRP will just NOT mount anything. Other folks say I need the latest PhilZ Recovery. I've downloaded the latest PhilZ Touch 6 and flashed it via Odin. It is giving me the same errors as regular CWM, Status 7, "expecting 5 args, got 3."
I don't know what else to do. My S3 that ran Android 4.0 was so much easier. I had that thing rooted and running a TW based ROM with Nova launcher in about 30 minutes. This phone has been a disaster since I turned it on. I'm just trying to get a 4.3 TW based ROM. I like the Samsung Camera, Calendar, Clock, Messaging, and Contacts apps far better than AOSP versions. But I also want much more customization to my notification drawer toggles. Stock TW doesn't have the toggles I use frequently like the data toggle as well as the torch toggle.
I don't know what I'm doing wrong, because unlike a lot of folks out there, once I find a ROM I like, I stick with it. I'm not constantly updating, changing, or searching for the newest version of Android. There's nothing wrong with that, it just isn't my cup of tea. So does anyone know what I need to do? At this point, I'm about to just give up and use Nova over top of rooted stock TW and call it a day.
Thanks!
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
nosphor said:
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
Click to expand...
Click to collapse
Everything is stock except the recovery. I'm using CWM 6.0.4.7 with PhilZ Touch 6. I'm still using the stock TW 4.3 ROM that shipped with the phone. The only exception is that I'm rooted now.
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
nosphor said:
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
Click to expand...
Click to collapse
Unfortunately, I've heard that it is not possible to revert to anything prior to 4.3 once a phone comes factory installed with 4.3, due to all of the security enhancements and etc. My kernel, modem, and baseband are all factory stock 4.3 MJB. Everyone else on the boards, under various other topics, warn of immediate and sudden death to the phone if you attempt to install a baseband prior to 4.3 MJB.
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
nosphor said:
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
Click to expand...
Click to collapse
I'm in the USA. The security features on the I747 US version are far different. I don't know how everyone else is succeeding. I am completely lost.
You are in the wrong forum, anything you try from here will hard brick your phone.
Sent from my GT-I9300 using Tapatalk
Sorry to tell you that, but what you say is not completely true.
Yes, there is a lot of people that rush to give an answer to the question, but there is also people that really like to help people that are in trouble :good:
Please, don't take most of the case for a generality
http://forum.xda-developers.com/showthread.php?t=1756338
Sent from my GT-I9300 using Tapatalk
Yes, i've read this, i know that, that's why i talk about the difference between country, different phone model
My apologies. Thought this was the 747 board. Go ahead and lock this, I'll repost in the correct forum.
Tried TWRP?
Hello,
I'd like to know when to do a full reset over the recovery when installing new ROMS or downgrading / upgrading a specific rom. I'm a Samsung Galaxy S5 user and I'm not sure when to do these steps. Some ppl say I have to wipe before I install the Firmware and others say I have to do a wipe after I've flashed the firmware.
So, what do you think and why?
Slurpslurp said:
Hello,
I'd like to know when to do a full reset over the recovery when installing new ROMS or downgrading / upgrading a specific rom. I'm a Samsung Galaxy S5 user and I'm not sure when to do these steps. Some ppl say I have to wipe before I install the Firmware and others say I have to do a wipe after I've flashed the firmware.
So, what do you think and why?
Click to expand...
Click to collapse
hello,
The way this works are actually multiple things, and you should be very carefull not to be switching them around. There are multiple wipe possibilities.
Dalvik cache / Data, Where certain app data is stored. This is almost always wiped when doing a major version or rom update, like from cyanogenmod 11 to 12.
System, This is where the actual rom is stored, when switching roms this is usually done automatically by the installer. BE CAREFULL when wiping this, as it could brick your device if you don't know what you are doing.
some other things can also be wiped, but are not nessesairy most of the time.
Most guides for installing roms etc. explain pretty good what needs to be wiped in order for the rom to work. can I ask what you need to wipe something for?
I hope this helps a little, you can always message me and I will gladly help you.
Sent with my ghost running bacon and my own software
Ghost_Developer said:
hello,
The way this works are actually multiple things, and you should be very carefull not to be switching them around. There are multiple wipe possibilities.
Dalvik cache / Data, Where certain app data is stored. This is almost always wiped when doing a major version or rom update, like from cyanogenmod 11 to 12.
System, This is where the actual rom is stored, when switching roms this is usually done automatically by the installer. BE CAREFULL when wiping this, as it could brick your device if you don't know what you are doing.
some other things can also be wiped, but are not nessesairy most of the time.
Most guides for installing roms etc. explain pretty good what needs to be wiped in order for the rom to work. can I ask what you need to wipe something for?
I hope this helps a little, you can always message me and I will gladly help you.
Sent with my ghost running bacon and my own software
Click to expand...
Click to collapse
I use the Galaxy S5 Knox 0x0 ROM for example. I won't use any other custom Roms like CM or such. I'm just confused about wiping because every thread says different methods or ways to wipe. In one thread it is recommend to wipe the phone before the installation of the rom and in another thread ppl say you have to wipe after the installation of the rom.
Installation: Downgrading from Lollipop to Kitkat 4.4.2 for TowelRoot.
Slurpslurp said:
I use the Galaxy S5 Knox 0x0 ROM for example. I won't use any other custom Roms like CM or such. I'm just confused about wiping because every thread says different methods or ways to wipe. In one thread it is recommend to wipe the phone before the installation of the rom and in another thread ppl say you have to wipe after the installation of the rom.
Installation: Downgrading from Lollipop to Kitkat 4.4.2 for TowelRoot.
Click to expand...
Click to collapse
So you are now installing Knox 0x0 kitkat over lollipop?
In that case follow normal instructions for installing kitkat.
1. Reboot into recovery
2. Install Kitkat
3. wipe data and dalvik (YOU WILL LOSE ALL YOUR APPS)
4. Restart
If this doesnt work, or results in a bootloop, try again, but this time before flashing kitkat wipe system.
hopefully this helps
Sent with my ghost running bacon and my own software
I have been running various flavors of AOKP ROM's on SG3's for several years now. I recently obtained a refurb S3 and set it up to do the usual.
It came with stock TW 4.4.
Using ROM Manager I installed CWM and made an image of the stock phone. I then installed my AOKP variant and loaded my apps, blah blah. All is good.
I've since decided I want to revert back to TW for awhile. I restored my nandroid and I get the interminable GAPPS failure messages. I have on occasion been able to get it to calm down and have a working phone, usually be uninstalling play app and clearing framework services cache. This is extraordinarily painful and doesn't always work. I've done all the usual, reinstall GAPPS, etc., and basically it is a MAJOR headache just trying to get the image to function.
But....When it does work the phone does not see my SIM card, IMEI, nothing.. I have no mobile connectivity. Restoring the AOKP nandroid brings me back to a fully functioning phone.
So my questions are:
Can anyone explain to me why the TW nandroid is giving all these GAPPS issues and how to circumvent/fix it?
Why is the system seeming to lose my IMEI/SIM info? Is there a way to fix that? Should I have done something different in my setup/nandroid creation?
Lastly - I don't quite understand how CWM works. There is a recovery image. When I do factory reset, is it resetting to this recovery image as opposed to the factory TW? I seem to think so, when I do a reset I see the android version is not what my factory one is.
Thanks all.