Related
I have a serious problem guys...I flashed last version of paranoidandroid but since my phone was too slow I tried to reflash last version but it was slow again. Then I tried to restore a previous backup but it restored it only in 60 seconds and indeed the rom didn't boot (stuck on google logo). After that any rom I try to install does not boot, I tried previous versions of paranoid and also google stock image (deodexed and rooted). I don't know what to do, but I cannot wipe the whole sd card because I have some important data I cannot afford to loose...please help me guys I'm desperate.
I know the solution to this problem is always, wipe everything with the toolkit and flash google image, but I have some sensible data I cannot loose. Moreover I don't own a microsoft computer anymore so I wouldn't be able to use the toolkit. Is there anything else I can try?
Hmmm.. did you dirty flashed? :/ can you try again with wiping system, factory reset and cache and dalvik ... do you have any other ROM in your phone the one you had before?? try installing that again with wiping everything nd give it atleast 10 mins to start up i remember my phone stared really late with PA .. i know i might not be of that much help but i'm spitballin' here
irizwan said:
Hmmm.. did you dirty flashed? :/ can you try again with wiping system, factory reset and cache and dalvik ... do you have any other ROM in your phone the one you had before?? try installing that again with wiping everything nd give it atleast 10 mins to start up i remember my phone stared really late with PA .. i know i might not be of that much help but i'm spitballin' here
Click to expand...
Click to collapse
Yes I tried to wipe everything 20 times, and I tried a couple of versions of PA and the stock deodexed rom which is all what I had on my phone, and nothing worked. I'll try to leave the phone for 10 minutes and see if it finally boots up. Cheers mate
mariottide said:
Yes I tried to wipe everything 20 times, and I tried a couple of versions of PA and the stock deodexed rom which is all what I had on my phone, and nothing worked. I'll try to leave the phone for 10 minutes and see if it finally boots up. Cheers mate
Click to expand...
Click to collapse
Are you using the most up to date version of TWRP or CWM when you flash your ROMs?
mariottide said:
I have a serious problem guys...I flashed last version of paranoidandroid but since my phone was too slow I tried to reflash last version but it was slow again. Then I tried to restore a previous backup but it restored it only in 60 seconds and indeed the rom didn't boot (stuck on google logo). After that any rom I try to install does not boot, I tried previous versions of paranoid and also google stock image (deodexed and rooted). I don't know what to do, but I cannot wipe the whole sd card because I have some important data I cannot afford to loose...please help me guys I'm desperate.
I know the solution to this problem is always, wipe everything with the toolkit and flash google image, but I have some sensible data I cannot loose. Moreover I don't own a microsoft computer anymore so I wouldn't be able to use the toolkit. Is there anything else I can try?
Click to expand...
Click to collapse
Try to update your recovery to latest version as older recovery versions could face problems related to new file system structure.
Odesláno z mého Galaxy Nexus pomocí Tapatalk 2
[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.)
Hey there, I just flashed my DHD with CM11, but I have a small problem. CM11 works fine, but everytime when I install GAPPS (Tried many versions for CM11) The phone just boots, I insert PIN and there it starts. It starts flooding me with messages what crashed. Almost everything crashes and when i close it, it appears again (especially keyboard, com.google.process.gapps). Can someone help me? Thanks for all answers
kosil said:
Hey there, I just flashed my DHD with CM11, but I have a small problem. CM11 works fine, but everytime when I install GAPPS (Tried many versions for CM11) The phone just boots, I insert PIN and there it starts. It starts flooding me with messages what crashed. Almost everything crashes and when i close it, it appears again (especially keyboard, com.google.process.gapps). Can someone help me? Thanks for all answers
I solved this myself, I just formatted /system , Installed CM11 and GAPPS 20131107
Click to expand...
Click to collapse
try the GAPPS here.
if that does not work, do a clean flash of rom and boot into phone witout GAPPS, then go back into recovery and flash GAPPS , clear cache, and reboot. After that you should be good to go. :good:
Thanks
TheJokah said:
try the GAPPS
if that does not work, do a clean flash of rom and boot into phone witout GAPPS, then go back into recovery and flash GAPPS , clear cache, and reboot. After that you should be good to go. :good:
Click to expand...
Click to collapse
Yeah, I did this... some things still crash, but it wasnt so big flood so I clicked into Apps and disabled that apps what made problems. Solved
Hello, I really need some help!
I have the GT i9195 and I've flashed it with CM13 and the proper GApps. I have TWRP Recovery and it's all 100% functional.
The problem here is, I flash the ROM, ok. I flash the GApps, ok. Then i wipe every cache and stuff and reboot. It takes a lots of time to reboot, but it's okay. After, maybe 1 hour, more or less, he finally starts.
Now here's what is wrong. ALL the GApps don't work. The phone is working fine, all sensors, cameras and even calling is fine, but the GApps don't work.
So, I've tried to downgrade to CM12.1 with the proper GApps, same. I've changed the ROM to another version of the CM13, nothing. I've downloaded all GApps, from Pico to Custom, nothing...
What can I do? Can anyone help me out?
Flash Opengapps select ARM Platform,use pico version. Wipe data,cache,dalvik cache then flash rom & gapps. OR flash separately, flash rom reboot system. Then wipe cache,dalvik cache flash gapps.
Leandro Avlis said:
Hello, I really need some help!
I have the GT i9195 and I've flashed it with CM13 and the proper GApps. I have TWRP Recovery and it's all 100% functional.
The problem here is, I flash the ROM, ok. I flash the GApps, ok. Then i wipe every cache and stuff and reboot. It takes a lots of time to reboot, but it's okay. After, maybe 1 hour, more or less, he finally starts.
Now here's what is wrong. ALL the GApps don't work. The phone is working fine, all sensors, cameras and even calling is fine, but the GApps don't work.
So, I've tried to downgrade to CM12.1 with the proper GApps, same. I've changed the ROM to another version of the CM13, nothing. I've downloaded all GApps, from Pico to Custom, nothing...
What can I do? Can anyone help me out?
Click to expand...
Click to collapse
Its hard to tell by your wording but you are flashing GAPPS and the ROM at the same time and not booting into rom first right?
I have had a lot of Play Services FC's lately and had to wipe data from play services and market to get them working after I was rooting and un-rooting back and forth.
civicsr2cool said:
Its hard to tell by your wording but you are flashing GAPPS and the ROM at the same time and not booting into rom first right?
I have had a lot of Play Services FC's lately and had to wipe data from play services and market to get them working after I was rooting and un-rooting back and forth.
Click to expand...
Click to collapse
I flashed all at same time (following some instructions I saw) then I only flashed the ROM and after the GApps. Even so, they are not working!
I've tried all GApps for this device, none are working.
My best solution so far was download the stock Firmware and Flash it trough Odin.
It's stock, but is working fine without any issues until now.
But I really really want to put CM13 or CM12.1 in this phone.
Leandro Avlis said:
I flashed all at same time (following some instructions I saw) then I only flashed the ROM and after the GApps. Even so, they are not working!
I've tried all GApps for this device, none are working.
My best solution so far was download the stock Firmware and Flash it trough Odin.
It's stock, but is working fine without any issues until now.
But I really really want to put CM13 or CM12.1 in this phone.
Click to expand...
Click to collapse
you're doing something wrong. Im running an old official cm13 build on my LTE, give that a shot?
civicsr2cool said:
you're doing something wrong. Im running an old official cm13 build on my LTE, give that a shot?
Click to expand...
Click to collapse
The problem here is the GApps. The ROM is working fine! CM13, CM12.1... etc. They're all working 100%, the GApps aren't working with non official Firmware.
Leandro Avlis said:
The problem here is the GApps. The ROM is working fine! CM13, CM12.1... etc. They're all working 100%, the GApps aren't working with non official Firmware.
Click to expand...
Click to collapse
Something in your process is wrong regardless if its rom or gapps. try this Gapps, its running right now on my official cm13.
https://drive.google.com/open?id=0Bx5gPVuLapkKZVl1N3o5RzlqcFk
This is the latest stable release that Im runnning as well
https://download.cyanogenmod.org/get/serranoltexx-snapshot.zip
Hello,
I would like to install Lineage on my OnePlus5T, as the OxygenOS system does not seem to have an option for the Albanian language. Lineage does.
However, since Wednesday July 28, I have been trying and failing. Here are the steps:
1. Unlock bootloader (worked perfectly.)
2. Flash TWRP (No issue there either.)
3. Wipe Data, System, Dalvik, Cache (All okay so far...)
4. Flash Lineage and Gapps (both worked fine). I'm flashing lineage 18, with the pico gapps package for android 11.
5. Wipe dalvik and cache again, then reboot. But I got stuck on the spinning wheel. I had backed up all the data with TWRP, but apparently restoring it won't put me backk on OxygenOS. The backup must've been corrupted when copying to a computer.
I also erased system and vendor with fastboot, which wiped all else from the phone and then I tried again, still no luck.
I have tried flashing OxygenOS again, and that now gives me "zip trebble compatibility error, invalid zip file format".
But all partitions were empty, before flashing the system. What have I done wrong? Or what should/can I try to get the system installed?
Many thanks for any help... Sorry for the long message.
Hmm. Did you try without flashing GAPPS? How would your phone behave with system being flashed only?
dedq said:
Hmm. Did you try without flashing GAPPS? How would your phone behave with system being flashed only?
Click to expand...
Click to collapse
I feel that could work. However, just before I do, I should ask, does Lineage have the core google apps already installed? Google play, etc? If so, I'll give that a try at my earliest convenience.
Many thanks for the help.
Lineage doesn't have anything related to Google. It's totally debloated.
Give flashing without GAPPS a try and you will be able to identify the problem.
dedq said:
Lineage doesn't have anything related to Google. It's totally debloated.
Give flashing without GAPPS a try and you will be able to identify the problem.
Click to expand...
Click to collapse
If this works, how would I be able to get the google apps installed? Would I need to try a different gapps package, maybe?
Many thanks again, and sorry for all the questions.
First see if it works at all after flashing system and we will see after it.
Tobias101 said:
If this works, how would I be able to get the google apps installed? Would I need to try a different gapps package, maybe?
Many thanks again, and sorry for all the questions.
Click to expand...
Click to collapse
It's always worth an attempt to boot after flashing system only. If your phone boots you should reboot to recovery and flash your Gapps. Hopefully your phone wool boot again then.
KeinePanik said:
It's always worth an attempt to boot after flashing system only. If your phone boots you should reboot to recovery and flash your Gapps. Hopefully your phone wool boot again then.
Click to expand...
Click to collapse
Thank you so much, I'm going to give that a try when I can.
Hello,
The system booted without gapps, but didn't boot with it. So I downloaded the nano package, which was the only other available one for android 11, and it now works flawlessly.
Many thanks for all the help!