Hi, in the last minutes i've flashed the 2.7 build of LiquidSmooth Rom from the Paranoid Hello Halo rom... I've done the prcedure like XDA said : Wipe Wipe Wipe (cache, dalvik, system) Flash Rom Flash Gapps. It booted fine but all my apps that i've had on my previous rom was still there... all of them. The most disturbing is my settings were also like I've left them ( disabled pie wifi etc) also my Google Accound was already setuped and good to go. Is it a new feature from flashing 4.2.2 rom to an other 4.2.2 rom ? I've never seen that before. I've also rebooted to make sure it wont boot loop on reboot, and it booted like a charm!
Any clues ?
Weird, never seen that before. Tell us what recovery you have and exactly what you are wiping. Can't think of anything else at the moment I'm sure others will chime in.
Sounds to me like you're not wiping /data. This is where your apps and setting are stored and unless you factory reset using stock recovery, deliberately wipe/format /data, or flash a Rom that wipes it for you, all your apps and settings will remain.
Seems like normal behavior to me.
Sent from my SGH-T999L using xda premium
Ya I re-read it and he just wipes caches and system, definitely need to factory reset lol.
kruse1944 said:
Hi, in the last minutes i've flashed the 2.7 build of LiquidSmooth Rom from the Paranoid Hello Halo rom... I've done the prcedure like XDA said : Wipe Wipe Wipe (cache, dalvik, system) Flash Rom Flash Gapps. It booted fine but all my apps that i've had on my previous rom was still there... all of them. The most disturbing is my settings were also like I've left them ( disabled pie wifi etc) also my Google Accound was already setuped and good to go. Is it a new feature from flashing 4.2.2 rom to an other 4.2.2 rom ? I've never seen that before. I've also rebooted to make sure it wont boot loop on reboot, and it booted like a charm!
Any clues ?
Click to expand...
Click to collapse
Tapatalk.
mt3g said:
Ya I re-read it and he just wipes caches and system, definitely need to factory reset lol.
Click to expand...
Click to collapse
Got it that's why. I was sure wiping system would wipe data too. But do you think its dangerous to not wipe data? Because actually my ROM is rocking right now without issues? Should I reflash it for safety?
It just depends....
It's always best to start clean, especially if you were having problems. But if you want to keep data intact, you should be ok as long as you don't go to an entirely different rom, base, or build.
If you are updating to a newer version of the same build, you're fine. Also if updating to a newer build/version you should be ok, but may have a few hiccups.
However, anytime you go backwards (4.2.2 to 4.1.2) you should wipe it all. The same is true if you are moving to a different base, such as CM to TW. Keeping your internal sdcard data is usually ok, but sometimes it can cause some issues.
Sent from my SGH-T999L using xda premium
Related
Howdy y'all!
I'm currently running a 4.1.1 ROM, and would like to get on to MMuzzy's 4.2, but there are a ton of things I think I need to flash and want to make sure I get the order right. Your help will be much appreciated!
I am already using the latest version of TWRP.
I would like to flash the latest JB bootloader, and latest JB radios, but have never flashed either. Should I do these before flashing the ROM, or after? Should I do these before formatting cache? Should I format system or factory reset before flashing these, too?
I am planning to do factory reset, format cache and dalvik before flashing ROM, gapps and kernel. Do I need to do anything else to prep for flashing the ROM? Also, is it okay to flash all three at once, or should I do rom and gapps, let everything boot and restore from market, and only then flash kernel?
My main concern is the differences in file system between 4.1 and 4.2. I'm aware of the /0 subdirectory thing already, but I'd there anything else?
Thanks much!
Jamie
I wouldn't bother with the bootloader, but if you insist then you can flash the bootloader and the radios before or after. Doesn't matter.. Other than that, you do them ROM, gapps, kernel and I've done all three at once. Mmuzzy's is a good ROM. Enjoy.
First make a backup in TWRP
Factory reset
Wipe both caches
Install ROM, gapps, then kernel and reboot. (All at the sometime in that order)
I have heard its better to flash the kernel with the new ROM so just do it all in one flash.
Set everything up and let your phone sit for 15 minutes untouched and go for it.
Sent from my Galaxy Nexus using xda app-developers app
jrbedford said:
My main concern is the differences in file system tree between 4.1 and 4.2. I'm aware of the /0 subdirectory thing already, but I'd there anything else?
Thanks much!
Jamie
Click to expand...
Click to collapse
Just a small correction; file system change would mean switching from ext4 to f2fs, for example. That's not the case.
MartianCeo said:
First make a backup in TWRP
Factory reset
Wipe both caches
Install ROM, gapps, then kernel and reboot. (All at the sometime in that order)
I have heard its better to flash the kernel with the new ROM so just do it all in one flash.
Set everything up and let your phone sit for 15 minutes untouched and go for it.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Watch out with restoring backups. Don't restore app/system data. OP is switching major versions.
sent from my Google Galaxy Nexus
[Q] Help? I get this when flashing a new rom "Unfortunately setup wizard has stopped"
I have a Galaxy s3 and I have twrp installed. And so far I have tried flashing 4 or 5 different custom roms and every time I end up getting this message "Unfortunately setup wizard has stopped" and then some message about ".com.goolge gpapps has stopped".
I am flashing the rom's and gapps from trwp. And I get the success comment after both the rom and gapps flash. I then restart/reboot and the new rom's custom boot animation comes up, like with cm10 the blue clockwork logo spins, and then after 10 or 20 seconds I get the two error messages and thats its. And when I flashed liquid smooth, I got the Liquid Smooth boot animation.as well and the the two messages. I eventually get my phone tuned off and I get it booted back into twrp and restore my backup to my stock rooted setup which is what I currently have running and so far is the only thing I can get to boot up. I have tried cm10 nightlies from the past week and cm10 stable and liquidsmooth, and a couple others. I downloaded several from goo.manager but i most recently tried a cm nightly i downloaded directly from clockworks site.
Any Idea's. I have seen a couple other threads on other devices with a similar problem but most seemed to have the wrong gapps, and I am using the most current gapps, i even downloaded it from multiple sources to double check.
Does the fact my phone is android 4,1,1 and most these roms are 4.1.2 or newer matter? And if so what is the fix?
nwjimmy said:
I have a Galaxy s3 and I have twrp installed. And so far I have tried flashing 4 or 5 different custom roms and every time I end up getting this message "Unfortunately setup wizard has stopped" and then some message about ".com.goolge gpapps has stopped".
I am flashing the rom's and gapps from trwp. And I get the success comment after both the rom and gapps flash. I then restart/reboot and the new rom's custom boot animation comes up, like with cm10 the blue clockwork logo spins, and then after 10 or 20 seconds I get the two error messages and thats its. And when I flashed liquid smooth, I got the Liquid Smooth boot animation.as well and the the two messages. I eventually get my phone tuned off and I get it booted back into twrp and restore my backup to my stock rooted setup which is what I currently have running and so far is the only thing I can get to boot up. I have tried cm10 nightlies from the past week and cm10 stable and liquidsmooth, and a couple others. I downloaded several from goo.manager but i most recently tried a cm nightly i downloaded directly from clockworks site.
Any Idea's. I have seen a couple other threads on other devices with a similar problem but most seemed to have the wrong gapps, and I am using the most current gapps, i even downloaded it from multiple sources to double check.
Does the fact my phone is android 4,1,1 and most these roms are 4.1.2 or newer matter? And if so what is the fix?
Click to expand...
Click to collapse
Are you wiping system and data before flashing? This is most likely your issue.
zelendel said:
Are you wiping system and data before flashing? This is most likely your issue.
Click to expand...
Click to collapse
yes, cache and dalvik, and a factory reset.
nwjimmy said:
yes, cache and dalvik, and a factory reset.
Click to expand...
Click to collapse
Ok what you have to try is this.
Boot into recovery and wipe system and data (removes settings so you will need to reset up everything) They wipe delvic cache and normal cache, then flash the rom and the proper gapps for the rom.
zelendel said:
Ok what you have to try is this.
Boot into recovery and wipe system and data (removes settings so you will need to reset up everything) They wipe delvic cache and normal cache, then flash the rom and the proper gapps for the rom.
Click to expand...
Click to collapse
On the wipe screen in twrp there is a system option but for data it says format data? Do I need to wipe "system" and "format data"? or does the wipe system option take care of what i need to do? If I need to also select "format data" which do I do first ? format data or system wipe? will i need to wipe cache or dalvik as well, or will those be wiped in the system wipe? Sorry for all the ?'s I am a real noob at all of this.
nwjimmy said:
On the wipe screen in twrp there is a system option but for data it says format data? Do I need to wipe "system" and "format data"? or does the wipe system option take care of what i need to do? If I need to also select "format data" which do I do first ? format data or system wipe? will i need to wipe cache or dalvik as well, or will those be wiped in the system wipe? Sorry for all the ?'s I am a real noob at all of this.
Click to expand...
Click to collapse
No wiping the system doesnt format the data partition. Wipe system then format the data and then wipe the caches and then flash the rom.
Re: [Q] Help? I get this when flashing a new rom "Unfortunately setup wizard has stop
Sounds like your flashing the wrong version of gapps.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Re: [Q] Help? I get this when flashing a new rom "Unfortunately setup wizard has stop
matt_schieman said:
Sounds like your flashing the wrong version of gapps.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Agreed.
Double check your gapps and make sure uts the right version
sent from my 1920 overclocked note 2 running jedi xp12
What gapps should I be using ? I hav gapps jb -20121011. I havnt wiped the additional areas yet either but thats because I want to make sure im installing the correct zip files
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
nwjimmy said:
What gapps should I be using ? I hav gapps jb -20121011. I havnt wiped the additional areas yet either but thats because I want to make sure im installing the correct zip files
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Most rom threads have a download link to the gapps that work with the version of android that specific rom is on. Look in the rom thread for the one you're currently running. There are different gapps for each android version (4, 4.1, 4.2)
I have that same problem too
I was trying to install new roms for my phone i tried liquid smooth and avatar and CM 10. I also tried install a new kernel and also different recoveries but nothing seems to work. I never "dirty" flashed and i use the right gapps. Someone please help me here i hate stock roms!
No matter what Gapps version I've tried I still get this same error. This occurred after trying out the Dark ROM modeled after CM11, but now no matter what ROM I try, this error still occurs. The only time I was ever able to get passed it was using a backup, but that has mysteriously gone AWOL. With that in mind, has anyone actually figured this out? Is there anyone with any USEFUL input? So far all I'm seeing is a bunch of suggestions that don't work.
xantechie said:
No matter what Gapps version I've tried I still get this same error. This occurred after trying out the Dark ROM modeled after CM11, but now no matter what ROM I try, this error still occurs. The only time I was ever able to get passed it was using a backup, but that has mysteriously gone AWOL. With that in mind, has anyone actually figured this out? Is there anyone with any USEFUL input? So far all I'm seeing is a bunch of suggestions that don't
Is your recovery updated to the latest version? Do the roms you are trying support the recovery you are using?
Click to expand...
Click to collapse
fig03 said:
xantechie said:
No matter what Gapps version I've tried I still get this same error. This occurred after trying out the Dark ROM modeled after CM11, but now no matter what ROM I try, this error still occurs. The only time I was ever able to get passed it was using a backup, but that has mysteriously gone AWOL. With that in mind, has anyone actually figured this out? Is there anyone with any USEFUL input? So far all I'm seeing is a bunch of suggestions that don't
Is your recovery updated to the latest version? Do the roms you are trying support the recovery you are using?
Click to expand...
Click to collapse
That's a good point. You should be on TWRP 2.7.0.0 that's the latest version of that recovery.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I use the latest CWM. I'm a creature of habit. The first Samsung I ever put a custom ROM on was done with CWM, so I stick with it. I finally got it to go, but it constantly froze, tried to reset, stuck with the same issue. Never used TWRP, so if someone could actually point me in the right direction, that'd actually be helpful.
xantechie said:
I use the latest CWM. I'm a creature of habit. The first Samsung I ever put a custom ROM on was done with CWM, so I stick with it. I finally got it to go, though...it doesn't really look the way I remember it last it worked, but it's had the issue so long, I forget what it actually looked like before.
Click to expand...
Click to collapse
I have no idea how to use TWRP...it only lists a .img file and no instructions on how to use it. zip files can be used from the bootloader or recovery. WTF am I supposed to do with an .img file. And it can't be to use the terminal emulator because to do that I would have to be able to get passed the Setup Wizard...which is the issue.
I finally figured it out with CWM. Thankfully. The phone would've went flying otherwise.
If anyone else stumbles upon this thread (so they can find the answer for CWM also), you have to format the device from the CWM Recovery to get rid of the crap that is blocking it. I did the following:
Once in CWM Recovery, Remove your SD card to avoid formatting it by accident.
Use the Volume Key to scroll to "mounts and storage".
Format all existing options (this is why the SD needed to be removed); this will blank out the phone's system which was causing the Setup issue to begin with.
Put your SD card with the ROM to be installed back into the phone.
Follow the guide as normal after this (install ROM, then reboot, then KK_gapps, then wipe the two caches, then reboot.)
Hi Guys,
I was wondering if anyone could help me with a strange issue I have.
When I flash to stock root ROM my phone works fine, including my camera, however, when I flash to ANY custom ROM my camera only works when my flash is off. If I turn the flash on the camera attempts to take a picture and then freezes and I have to do a battery pull to get it back on.
I will through a curveball here and say that I have had extremely limited success (but success nonetheless) when I use my original OEM battery.
The flash itself works fine as I can use apps like flashlight no problem.
Oh and app's from the Play store work fine as well w/ flash on.
Anybody experience this before? I have searched and found nothing,
Thanks everyone.
How are you wiping before flashing? I recommend wipe data, cache, dalvik, format /system.
And by "any" ROMs do you mean 4.2 ROMs or both 4.1 and 4.2?
Well the stock ROM was 4.1.1.
The thing is I've had this problem for a long time now so it would be on both 4.1 and 4.2.
New development though, I just re- flashed to PKD ROM and the flash works intermittently. It seems when I take a picture if something closeup with flash it works but when the subject is far away the camera app just goes black.
So, about your wipe procedures...
xBeerdroiDx said:
So, about your wipe procedures...
Click to expand...
Click to collapse
Sorry,
So when I flash a ROM I wipe data/factory clear dalvik and clear cache.
I've done that from stock to custom.
The next time you flash, have everything backed up/saved to your sd card or pay and follow the wipe procedures I recommended above. It wipes the OS completely off, leaving you a completely blank slate for the new rom. Have your desired rom and gapps on your micro sd card
Blender7 said:
Sorry,
So when I flash a ROM I wipe data/factory clear dalvik and clear cache.
I've done that from stock to custom.
Click to expand...
Click to collapse
You forgot to format /system manually in mount/boot, that causes a lot of errors (it caused a bootloop issue when going from stock to Slim for me)
I have tried every method I can think of to get 4.3 to play nice with my phone. I have used Odin to flash stock and twrp, tried cwm recovery, tried beanstalk, hellybean, cm, and aokp. I changed twrp settings and infamous wipe. Everything I do always results with my phone getting stuck on the boot animation. Even if I clear caches, it will boot and get to the upgrading apps screen and then freeze and reboot and again stuck on the boot animation.
4.1.2 gets stuck on the kernel boot for me, 4.2.2 doesn't work with BT correctly. So frustrating.
Any suggestions are welcome.
4.3
dkrcubsfan said:
I have tried every method I can think of to get 4.3 to play nice with my phone. I have used Odin to flash stock and twrp, tried cwm recovery, tried beanstalk, hellybean, cm, and aokp. I changed twrp settings and infamous wipe. Everything I do always results with my phone getting stuck on the boot animation. Even if I clear caches, it will boot and get to the upgrading apps screen and then freeze and reboot and again stuck on the boot animation.
4.1.2 gets stuck on the kernel boot for me, 4.2.2 doesn't work with BT correctly. So frustrating.
Any suggestions are welcome.
Click to expand...
Click to collapse
Twrp 2.6.10 is the minimum. I am using 2.6.30. 2.6.00 will not work. Also wipe everything but SD. That includes android secure and preload.
stormannorman said:
Twrp 2.6.10 is the minimum. I am using 2.6.30. 2.6.00 will not work. Also wipe everything but SD. That includes android secure and preload.
Click to expand...
Click to collapse
Thanks, but I've tried all that.
Sent from my SGH-T989 using Tapatalk 4
dkrcubsfan said:
Thanks, but I've tried all that.
Sent from my SGH-T989 using Tapatalk 4
Click to expand...
Click to collapse
Twrp version 2.6.3.0 has bugs and is causing issues for a lot of people.
Make sure you use 2.6.1.0 and see how it goes.
Sent from my cellular telephone
kj2112 said:
Twrp version 2.6.3.0 has bugs and is causing issues for a lot of people.
Make sure you use 2.6.1.0 and see how it goes.
Sent from my cellular telephone
Click to expand...
Click to collapse
I have had Zero issues with 4.1 or 4.2 never bricked my phone---- until 4.3 I will tell you how i solved my problems - I have no boots, to 4.3 working but issues with data corruption and gapps crashing random apps crashing, finally after reading and reading i solved it.
1. Flash TWRP 2.6.1 (NOT 2.6.0, not 2.6.0.4 and especially NOT 2.6.3) any other recovery will not work properly - yes for some it may but some people seem to have some of the same problems.
2. Wipe data, Davlik, Cache and the prior rom. it has to be a clean wipe/flash
3. Flash Rom of choice (Black Liquid smooth is awesome)
4. Flash Standard gapps 08/13 (dont get fancy yet and flash slim gapps or inverted, just use the tried and true basic to get it working)
5. let the damn phone rest and settle 10 min minimum.
6. reboot to recovery, wipe Davlik and cache for good measure and fix permissions, reboot and enjoy.
dkrcubsfan said:
I have tried every method I can think of to get 4.3 to play nice with my phone. I have used Odin to flash stock and twrp, tried cwm recovery, tried beanstalk, hellybean, cm, and aokp. I changed twrp settings and infamous wipe. Everything I do always results with my phone getting stuck on the boot animation. Even if I clear caches, it will boot and get to the upgrading apps screen and then freeze and reboot and again stuck on the boot animation.
4.1.2 gets stuck on the kernel boot for me, 4.2.2 doesn't work with BT correctly. So frustrating.
Any suggestions are welcome.
Click to expand...
Click to collapse
if twrp keeps giving you problems like these maybe try doing it from cmw. ive read it gives way less problems than twrp:good:
Decimus Meridius said:
I have had Zero issues with 4.1 or 4.2 never bricked my phone---- until 4.3 I will tell you how i solved my problems - I have no boots, to 4.3 working but issues with data corruption and gapps crashing random apps crashing, finally after reading and reading i solved it.
1. Flash TWRP 2.6.1 (NOT 2.6.0, not 2.6.0.4 and especially NOT 2.6.3) any other recovery will not work properly - yes for some it may but some people seem to have some of the same problems.
2. Wipe data, Davlik, Cache and the prior rom. it has to be a clean wipe/flash
3. Flash Rom of choice (Black Liquid smooth is awesome)
4. Flash Standard gapps 08/13 (dont get fancy yet and flash slim gapps or inverted, just use the tried and true basic to get it working)
5. let the damn phone rest and settle 10 min minimum.
6. reboot to recovery, wipe Davlik and cache for good measure and fix permissions, reboot and enjoy.
Click to expand...
Click to collapse
This. 2.6.1.0 twrp.
Sent from my cellular telephone
Just dropped a rooted stock rom back on my t989 (from this thread), and I'm geting com.android.phone has stopped message. Came from Cyanogen, Infamous, and Jedi, no problems, but for some reason, the stock rom installed via twrp seems to fail. I need it more or less stock, and I'd really rather not Odin it. Any ideas?
SaddamHussein said:
Just dropped a rooted stock rom back on my t989 (from this thread), and I'm geting com.android.phone has stopped message. Came from Cyanogen, Infamous, and Jedi, no problems, but for some reason, the stock rom installed via twrp seems to fail. I need it more or less stock, and I'd really rather not Odin it. Any ideas?
Click to expand...
Click to collapse
Did you wipe system, cache, dalvik, cache, data, and android secure before flashing? If so, after flashing wipe data, cache, and dalvik cache and reboot
Sent from my SGH-T989
jrc2 said:
Did you wipe system, cache, dalvik, cache, data, and android secure before flashing? If so, after flashing wipe data, cache, and dalvik cache and reboot
Sent from my SGH-T989
Click to expand...
Click to collapse
Yep. Per the instructions, performed all of the above wipes, as well as darkside super wipe and wipe before installing the ROM.
Also wiped cache and dalvik after flashing, but haven't tried wiping data after flash...I'll give that a try this evening.
Last night, out of necessity to have SOMETHING running on the device, I threw on AOKP, which runs without issue. I've seen a few other debloated/rooted stock T989 UVMC6 roms floating around, but the comment threads underneath them seem to indicate problems of various types.
If someone knows of a UVMC6 TW ROM that is known good, and can be installed via installed via TWRP, I'd be very interested, even if it still has the bloat. Its the wifes phone and she is a bit of a touchwiz nazi, but hates all the custom boot logos, etc, that come with roms like Infamous. Stock is where she is at.
SaddamHussein said:
Yep. Per the instructions, performed all of the above wipes, as well as darkside super wipe and wipe before installing the ROM.
Also wiped cache and dalvik after flashing, but haven't tried wiping data after flash...I'll give that a try this evening.
Last night, out of necessity to have SOMETHING running on the device, I threw on AOKP, which runs without issue. I've seen a few other debloated/rooted stock T989 UVMC6 roms floating around, but the comment threads underneath them seem to indicate problems of various types.
If someone knows of a UVMC6 TW ROM that is known good, and can be installed via installed via TWRP, I'd be very interested, even if it still has the bloat. Its the wifes phone and she is a bit of a touchwiz nazi, but hates all the custom boot logos, etc, that come with roms like Infamous. Stock is where she is at.
Click to expand...
Click to collapse
AOSPA KitKat runs SOO much better than TW. You can change the boot animation to something else very easily.
Sent from my SGH-T989
I'd use the "infamous" wipes before flashing...just for anything touchwiz based. Not aosp. And don't use the darkside wipes...they are outdated.
Search Google or XDA..."t989 infamous wipes"
---------- Post added at 10:50 AM ---------- Previous post was at 10:49 AM ----------
You can also just Odin stock 4.1.2 and debloat it yourself with titanium backup. Freezing bloat, no sense in uninstalling it.