Develop Bugs

[Q] Help? I get this when flashing a new rom "Unfortunately setup wizard has stopped"

[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.)

[Q] BootLoop Problem for Custom ROMs

Hi Guys,
I have a Rooted Galaxy Nexus. From Last Month, I am facing a strange problem. I had two custom roms stored in my machine
1. JB Sourcery 5.2
2. Xylon Maguro 2.7.7
I downloaded JBSourcery Encore, and tried to install it through Recovery. I have TWRP.
The TWRP program said that Installation of the ROM with Gapps package was successful. But when I Rebooted my phone, It got Stuck on the JBSourcery Logo while booting.
Then I switched back to JBSourcery5.2. It got installed perfectly.
After Some time , I installed XYLON rom with the same procedure. It also installed correctly, But when again I tried to install JBSourcery 5.2,
I faced the same problem I faced with JBSourcery Encore.
So, I switched back to XYLON 2.7.X.
Last week I copied PA3.99 custom rom with Android4.3. I installed it yesterday with new gapps package and it got installed correctly. I didnt like that rom interface so, I decided to go back to Xlon as it was the only working rom left in my phone. But when I tried to Load XYLON rom this time, then I went into BootLoop with XYLON Logo on the screen.
In Short, whenever I install a new rom on my phone, and if I switch back to my prevoius rom, then my previously working rom goes into bootloop. (Please note that I wipe cache/dalvik cache every time I install a new rom.)
Can Someone please help me to solve this issue???????
Please......

pkalekar said:
Hi Guys,
I have a Rooted Galaxy Nexus. From Last Month, I am facing a strange problem. I had two custom roms stored in my machine
1. JB Sourcery 5.2
2. Xylon Maguro 2.7.7
I downloaded JBSourcery Encore, and tried to install it through Recovery. I have TWRP.
The TWRP program said that Installation of the ROM with Gapps package was successful. But when I Rebooted my phone, It got Stuck on the JBSourcery Logo while booting.
Then I switched back to JBSourcery5.2. It got installed perfectly.
After Some time , I installed XYLON rom with the same procedure. It also installed correctly, But when again I tried to install JBSourcery 5.2,
I faced the same problem I faced with JBSourcery Encore.
So, I switched back to XYLON 2.7.X.
Last week I copied PA3.99 custom rom with Android4.3. I installed it yesterday with new gapps package and it got installed correctly. I didnt like that rom interface so, I decided to go back to Xlon as it was the only working rom left in my phone. But when I tried to Load XYLON rom this time, then I went into BootLoop with XYLON Logo on the screen.
In Short, whenever I install a new rom on my phone, and if I switch back to my prevoius rom, then my previously working rom goes into bootloop. (Please note that I wipe cache/dalvik cache every time I install a new rom.)
Can Someone please help me to solve this issue???????
Please......
Click to expand...
Click to collapse
You noted in your post that you only wipe cache and davlik. When you install a rom your supposed to do a full system wipe. And for sh!ts and giggles, try using cwm instead of twrp to install your roms. I hear mixed things about twrp.
Sent from my Galaxy Nexus using xda app-developers app

mkuehl06 said:
You noted in your post that you only wipe cache and davlik. When you install a rom your supposed to do a full system wipe. And for sh!ts and giggles, try using cwm instead of twrp to install your roms. I hear mixed things about twrp.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
But if I perform System wipe, then all the data such as images, contacts, downloaded aplications will be wiped from my phone... right?
And if I take a backup of that data on PC, and then after installing a new rom, if I paste it back in the phone, will it work??

pkalekar said:
But if I perform System wipe, then all the data such as images, contacts, downloaded aplications will be wiped from my phone... right?
And if I take a backup of that data on PC, and then after installing a new rom, if I paste it back in the phone, will it work??
Click to expand...
Click to collapse
Yes you will loose all your user data when you do a full system wipe. ive never copied and pasted data from my phone to my pc and then back tbh, i just let it all sync with my google account. the applications will restore when you sync your google account to your phone after the wipe since you have to have a google account to use play store. if they are external applications (ones you downloaded the apks for and installed them manually) you will have to reinstall those, as playstore will not recognize them. just about every custom rom op gives you instructions on how to install the roms, and im pretty sure they all say you must wipe all data before installing. failure to do a system wipe, will cause boot loops.

You can use "titanium backup" Ort "helium" to save your apps and Data.
Images and music normaly won't be deleted. But you should make a Backup anyways.
Gesendet von meinem Galaxy Nexus mit Tapatalk 4

Not able to install any aosp based rom

My phone is a GT-N7100, currently running JellyKatv4. I'm on MJ5 bootloader and have TWRP recovery (the latest one). Last night I wanted to try a non TW rom, so I downloaded 4 different roms (AOSB, Cyanogen, Slim and SOKP) to try. Wiped cache, dalvik cache, system, data, format internal storage, flashed the first one, got the "successfully installed" message, again cleared cache/dalvik cache, rebooted, nothing. Phone got stuck on roms logo. Left it for 10 minutes, still nothing. Rebooted, repeated the procedure, flashed another of the above roms, "successfully installed" message, nothing, stuck again at the roms logo. This happened to every single one of them!! What am I missing here;! Where is the catch;! Thanks in advance!

chandoliasnikos said:
My phone is a GT-N7100, currently running JellyKatv4. I'm on MJ5 bootloader and have TWRP recovery (the latest one). Last night I wanted to try a non TW rom, so I downloaded 4 different roms (AOSB, Cyanogen, Slim and SOKP) to try. Wiped cache, dalvik cache, system, data, format internal storage, flashed the first one, got the "successfully installed" message, again cleared cache/dalvik cache, rebooted, nothing. Phone got stuck on roms logo. Left it for 10 minutes, still nothing. Rebooted, repeated the procedure, flashed another of the above roms, "successfully installed" message, nothing, stuck again at the roms logo. This happened to every single one of them!! What am I missing here;! Where is the catch;! Thanks in advance!
Click to expand...
Click to collapse
That's really unsual,only thing I can suggest is switch your recoveries to a previous TWRP perhaps 2.7.0 or 2.7.0.2 and flash the AOSP rom.

chandoliasnikos said:
My phone is a GT-N7100, currently running JellyKatv4. I'm on MJ5 bootloader and have TWRP recovery (the latest one). Last night I wanted to try a non TW rom, so I downloaded 4 different roms (AOSB, Cyanogen, Slim and SOKP) to try. Wiped cache, dalvik cache, system, data, format internal storage, flashed the first one, got the "successfully installed" message, again cleared cache/dalvik cache, rebooted, nothing. Phone got stuck on roms logo. Left it for 10 minutes, still nothing. Rebooted, repeated the procedure, flashed another of the above roms, "successfully installed" message, nothing, stuck again at the roms logo. This happened to every single one of them!! What am I missing here;! Where is the catch;! Thanks in advance!
Click to expand...
Click to collapse
I have seen a few people with this problem on other ROMs such as the DN3 recently, also happened to me on one of the weekly build 5 SlimKAT releases.
The fix for 95% of the people so far has been to
do the wipe of system, cache and Dalvik
flash rom and gapps
reboot, if it hangs, boot back into recovery and dirty flash the rom again

Thanks for the replies! My first attempt was with TWRP v 2.6.3.2, got stuck to roms logo as I described, after that I flashed the newest TWRP 2.7.2.1, got stuck again. Do you suggest to go to a previous than v.2.6.3.2 release?
I'll try what fatboyinlycra suggested and I'll report back.

No success.. I tried flashing and dirtyflashing, the same result always, gets stuck on roms logo. I even moved the files to the internal storage, through TWRP file manager and flashed from there, still the same.. Any other suggestion?

chandoliasnikos said:
No success.. I tried flashing and dirtyflashing, the same result always, gets stuck on roms logo. I even moved the files to the internal storage, through TWRP file manager and flashed from there, still the same.. Any other suggestion?
Click to expand...
Click to collapse
you are on an old version of TWRP, suggest you use the new one - download from here
http://techerrata.com/file/twrp2/t03g/openrecovery-twrp-2.7.2.1-t03g.zip
The only other question I have to ask you is, you are downloading the right ROM for your phone? not an N7105 or other variant by mistake?

Thanks for the reply, but if u see my second post I've tried with the latest version of TWRP (2.7.2.1) and it didn't work. I've already tried 8 different roms (non TW), stuck on all of them in roms logo. I'm very frustrated right now, don't have a clue what's happening.

fatboyinlycra said:
you are on an old version of TWRP, suggest you use the new one - download from here
http://techerrata.com/file/twrp2/t03g/openrecovery-twrp-2.7.2.1-t03g.zip
The only other question I have to ask you is, you are downloading the right ROM for your phone? not an N7105 or other variant by mistake?
Click to expand...
Click to collapse
Yes, I try the correct versions for my phone. Will try a TW based later, to see what will happen.

Try format internal memory and all the partitions and then flash AOSP ROM, after that try flash custom kernel.
Odesláno z mého SM-G900F pomocí Tapatalk

silver750 said:
Try format internal memory and all the partitions and then flash AOSP ROM, after that try flash custom kernel.
Odesláno z mého SM-G900F pomocí Tapatalk
Click to expand...
Click to collapse
I'm using TWRP and I do format all internal storage and wipe every partition EVERY SINGLE TIME!! I'll give it a try your suggestion about custom kernel.

chandoliasnikos said:
I'm using TWRP and I do format all internal storage and wipe every partition EVERY SINGLE TIME!! I'll give it a try your suggestion about custom kernel.
Click to expand...
Click to collapse
mybe u try switch to philz rcovery..and follow this step..
factory reset - clean install new rom
wipe cache partition
wipe dalvik cache
install rom and gapps
and reboot
hope this helpful[emoji6]
Sent from my GT-N7100 using Tapatalk

silver750 said:
Try format internal memory and all the partitions and then flash AOSP ROM, after that try flash custom kernel.
Odesláno z mého SM-G900F pomocí Tapatalk
Click to expand...
Click to collapse
You made my day my friend!! Your advice worked! I flashed SOKP rom and before reboot I've also flashed agni kernel! And finally I got it working!! Many many thanks again!! [emoji106][emoji106][emoji122][emoji122]
Sent from my GT-N7100 using Tapatalk

I'm happy with you
Sent from my Samsung Galaxy Note 4 (N910F)

Boot loop issue :( please help

Ok, so i was using the cyanogenmod nightlys just fine until i decided to want to try other roms (Pac-man, exodus, etc.) when i loaded the first i used clockwork recovery and it seemed to go smoothly and installed the Gapps, and BAM boot loop, i can still access the recovery menu and the Odin mode menus with the boot sequence, ive successfully side-loaded other roms and Gapps and nothing seems to work, everything just gives me the boot loop, Any help is much appreciated.
Edit: forgot to mention, sometimes it loads the rom but only for a few seconds and reboots again

Assume you did clean flash? Wiping data, cache, dalvik cache.
Also twrp recovery works a little better flashing lollipop roms.

madbat99 said:
Assume you did clean flash? Wiping data, cache, dalvik cache.
Also twrp recovery works a little better flashing lollipop roms.
Click to expand...
Click to collapse
yes, i did a clean flash, do you think it could be as simple as using twrp?

Could even be the gapps you're using. If you're using a very recent build of a rom, make sure you're using new gapps. Try open gapps.
It's also sometimes necessary to wipe internal storage.

madbat99 said:
Could even be the gapps you're using. If you're using a very recent build of a rom, make sure you're using new gapps. Try open gapps.
It's also sometimes necessary to wipe internal storage.
Click to expand...
Click to collapse
ive tried different versions of gapps but ill give open another shot, whats the best way to wipe the internal storage?

Shadow00f said:
ive tried different versions of gapps but ill give open another shot, whats the best way to wipe the internal storage?
Click to expand...
Click to collapse
In twrp. Wipe/advanced wipe/ internal storage. Make sure you have anything you need from internal backed up.

Bootloop in Clean AOKP install

I've installed AOKP 2016.12.25 Nightly ,and also 12.18. Both times I get a bootloop.
I've wiped everything but internal storage, but can't boot :crying:

lfuentes said:
I've installed AOKP 2016.12.25 Nightly ,and also 12.18. Both times I get a bootloop.
I've wiped everything but internal storage, but can't boot :crying:
Click to expand...
Click to collapse
Download the factory image that matches the OS/month OTA that AOKP is based on, extract then flash the vendor.img through fastboot. Mix and matching the vendor between different OSes will bootloop.
Sent from my Nexus 5X using Tapatalk