Related
HI... i updated my phone with cyanogen 7 rc2, but after it booted up it's stuck in the animation that says cyanogen mod 7 , and the blue android sign... in comes than goes, again it comes... about 20 min stuck... what to do???
It sounds like you need to go into recovery mode and delete all your caches. If you are using ClockworkMod recovery do the following (make sure you are backed up first):
Delete all user data and info (under wipe data/ factory reset),
Wipe cache (under wipe cache partition),
Wipe Dalvik Cache (under advanced).
Then once you've done that try installing and running the ROM again.
i done that one time... for info im using AmonRA.. i cleaned all the cache and everything also... and installed again... nothing happens... fortunately i restored my nand backup and booted my phone with the OTA again... waiting for some answer.... do u think that installing stable version can fix this?
Sounds like a bad flash. I had rc2 running for a month or so with no issues. I've had times when the rom just doesn't install properly ans reflashing fixes it.
Download the zip again, if possible check md5 to make sure it's all good, make sure you have the desire/bravo GSM version, clear everything and flash just the rom and nothing else. If it boots, then go back and flash your gapps and whatever else you want.
Sent from my HTC Desire using XDA App
thx for replying.. as i was waiting for your reply, i download the cm 6 that is a stable version and checked, it has the same problem too.. i also downloaded GingerVillain 1.6 and it had the same problem too. do u think the problem might be that my phone is "s-on"? and how should i know if my phone is s-on or s-off... when i was rooting my phone with unrevoked, i checked the option that says disable security, but i'm not sure if it's disabled.... because i can't install un-signed zip packages....
any reply?
That definitely sounds odd. Its definitely not an issue with S-ON/OFF, nothing you've done here requires S-OFF to work properly.
Lets just make sure you're following all the steps.
In amonra, you've done your nandroid backup, so no need to do it again. There's no point having a non working backup
Go to wipe and wipe data/factory reset
Wipe davlik cache
Wipe sd-ext (shouldn't need to do this one as you don't have apps2sd yet, but better to be safe)
Now you flash your update.zip, then reboot and you should be fine. The only other thing I can perhaps suggest if every rom you flash sticks at boot is to perhaps try clockwork recovery instead of amonra. Apart from that we might have to wait for folks more knowledgeable than myself cause I'm all out of ideas.
thx for reply.... in meanwhile , i s-off ed my phone and it has the same problem too... i have problem with all cm and gingervillain roms.. but i don't have any problem with leedriod... one more question that maybe the problem is that i have android 2.2 installed, but gingervillain and cm use android 2.3 ... this maybe the problem.... and that's why leedroid works right, because it uses android 2.2.... i'm going to check OxyGen roms... i will post the result here...
i also faced same problem CM7 .. i tried CM6 and it went on fine..
heyyy... right after i posted the reply , i went to recovery and wiped anything, then installed gingervillain 1.6, and everything's fine now... it booted up and now im setting it up.... im going to check the cm 7 too.
i tried cm7 rc2 ... and it was fine and now im using it... here's a how to for solving the problem...:
1.S-OFF your device with AlphaRev : http://forum.xda-developers.com/showthread.php?t=805811
2.Install the AlphaRev Recovery(S-OFF Image will do it automatically).
3.Go to recovery and install the rom...
4.Boot up and it should not go to system and it should stay in loop as the problem was..
5.Now you should reboot your device into recovery... there are two ways to do this... either take the battery off and put it on, then boot to bootloader by pressing the volume down and the power key and select recovery , or the second way connect it to your computer and start adb and run this command:
adb reboot recovery
6.In AlphaRev recovery first wipe the cache partition , wipe user data, and factory reset...
7.then install the rom (either cm7 or gingervillain)...
8. boot up , and now you have the system running...
This solved my problem... reply if it didn't yours...
hooo.. it worked for me now. just kept update.zip in a new SD card and not flashed google apps..
im very happy that i solved one's problem.. ... thread marked as solved...
*UPDATE* : now i realized that we can mark it as solved.. !!! hehe.. Admin do it for us...
I just tried flashing salvage mod and its gapps and it wouldn't boot either time. I also cleared all cache. Anyone know what I can do?
it is salvage mod 1.2.1.
JerenOtt said:
I just tried flashing salvage mod and its gapps and it wouldn't boot either time. I also cleared all cache. Anyone know what I can do?
Click to expand...
Click to collapse
What ROM were you on before you flashed Salvage Mod? If it was a sense rom, you need to perform a full wipe (data/factory reset, cache, dalvik cache, boot, system) prior to flashing the new rom. When you said you cleared 'all cache', do you also mean you cleared dalvik cache as well? What recovery are you currently using? I'm on salvage 1.2.1 right now, and I've never had a problem booting it. When you say it won't boot, what does it do? Does it boot loop, or does it hang at the splash screen (white htc evo 4g screen)? The more info the better. I'd basically suggest doing a full wipe though, and try again.
k2buckley said:
What ROM were you on before you flashed Salvage Mod? If it was a sense rom, you need to perform a full wipe (data/factory reset, cache, dalvik cache, boot, system) prior to flashing the new rom. When you said you cleared 'all cache', do you also mean you cleared dalvik cache as well? What recovery are you currently using? I'm on salvage 1.2.1 right now, and I've never had a problem booting it. When you say it won't boot, what does it do? Does it boot loop, or does it hang at the splash screen (white htc evo 4g screen)? The more info the better. I'd basically suggest doing a full wipe though, and try again.
Click to expand...
Click to collapse
I was on stock rooted before this. I did clear dalvik cache but I need to do a factory reset like you said. Thanks.
I tried that and it's still doing the same thing. It just sits at a lit up black screen. Any other suggestions?
JerenOtt said:
I was on stock rooted before this. I did clear dalvik cache but I need to do a factory reset like you said. Thanks.
Click to expand...
Click to collapse
No problem man. It will boot up after a doing a full wipe, most likely.
JerenOtt said:
I tried that and it's still doing the same thing. It just sits at a lit up black screen. Any other suggestions?
Click to expand...
Click to collapse
Can you boot into the bootloader? Power off your device. Simultaneously press the DOWN volume button and the power button until your device starts. After a short pause, a few lines of text should scroll across the screen and then you will see a few options. One of the options will be recovery. Anyway, at the top of the screen, you should see either S-ON or S-OFF. Hopefully, it displays S-OFF. Anyway, select recovery from the set of options and then, as k2buckley has instructed, go to the wipe menu and wipe EVERYTHING except the SD card itself. When you're done, do not reboot. Go to the flash menu and flash the rom you want to flash. Do not flash the gapps zip yet. Reboot after flashing the rom. I want to make sure you're able to boot into the homescreen. If you're successful, reboot into recovery, wipe cache & dalvik and then flash the gapps.zip. afterwards, reboot. When you're all setup, go back I to recovery and make a nandroid backup.
posting & replying via the XDA Premium app.
also, make sure you got the full ROM, not just the patch for going from 1.2 to 1.2.1. I did that
I was having similar issues, mine went into a boot loop about twice before getting hung up at the initial setup with FCs. I was coming from CM7 Nightly 41 that was acting weird with FC's, I always double wipe cache/dalvik/factory reset. I thought that I might have had a bad download so I re-downloaded, wiped and flashed. I couldn't get past the initial setup so I went back to Ultimate Droid and have been running that for the last 4 days or so with out any major problems except for the Facebook update dicking things up and one random reboot that I had today... I really want to give Salvagemod a shot though since it's Evo-centric.
still not working for me
hey guys... i been trying to boot into salvage mod for the past 2 days... i get it to install just fine i do get the salvage screen up too...
then when the rom is supposed to be loaded up i get the Android dude with emergency call and a crash u keep pressing ok then it goes away and comes back right away... i just wiped everything again and reflashed it and now i am stuck with salvage screen re looping..
any help would be appreciated
thanks
The OP's problem was solved in a second thread by following the below instructions:
Download a fresh copy of both amon RA v2.3 (PC36IMG.zip) and Salvage-Mod 1.2.1 and place both on the root of your SD card. Make sure there is no other file named PC36IMG.zip. on the root of your card. If there is, put that particular file in a folder. Now shutdown your device. Boot into the bootloader screen. The bootloader will automatically detect the PC36IMG.zip file and prompt you to install. Follow the prompts to install. Installation should take less than 10 seconds. Afterwards, reboot into your new recovery. Go to the wipe menu and wipe everything except the SD card. Do not reboot. Go to the flash menu and flash Salvage-Mod. This *should* work.
posting & replying via the XDA Premium app.
dougjamal said:
The OP's problem was solved in a second thread by following the below instructions:
Download a fresh copy of both amon RA v2.3? (PC36IMG.zip) and Salvage-Mod 1.2.1 and place both on the root of your SD card. Make sure there is no other file named PC36IMG.zip. on the root of your card. If there is, put that particular file in a folder. Now shutdown your device. Boot into the bootloader screen. The bootloader will automatically detect the PC36IMG.zip file and prompt you to install. Follow the prompts to install. Installation should take less than 10 seconds. Afterwards, reboot into your new recovery. Go to the wipe menu and wipe everything except the SD card. Do not reboot. Go to the flash menu and flash Salvage-Mod. This *should* work.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Glad you got him going Doug. I had asked him to use RA in a PM, and he responded that he liked clockwork and rom manager better, and wouldn't use RA, lol. I'm glad you convinced him otherwise.
Sent from my PC36100 using XDA App
lol....Happy Easter, my friend...
posting & replying via the XDA Premium app.
dougjamal said:
lol....Happy Easter, my friend...
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Thank you Doug, happy Easter to you as well.
Sent from my PC36100 using XDA App
dougjamal said:
The OP's problem was solved in a second thread by following the below instructions:
Download a fresh copy of both amon RA v2.3 (PC36IMG.zip) and Salvage-Mod 1.2.1 and place both on the root of your SD card. Make sure there is no other file named PC36IMG.zip. on the root of your card. If there is, put that particular file in a folder. Now shutdown your device. Boot into the bootloader screen. The bootloader will automatically detect the PC36IMG.zip file and prompt you to install. Follow the prompts to install. Installation should take less than 10 seconds. Afterwards, reboot into your new recovery. Go to the wipe menu and wipe everything except the SD card. Do not reboot. Go to the flash menu and flash Salvage-Mod. This *should* work.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
hey thanks a bunch doug... that was the issue darn clockwork..lol.. got it running so far so good
so after i got it running decided to install the gapps stuff too from recovery...and there goes my phone again back to android with emergency call only... going to try installing again without gapps...any tips let me know please..
thanks
Did you wipe cache and dalvik before flashing gapps? Also, are you sure you're using the correct version of gapps for whichever rom you're on?
Sent from my PC36100 using XDA App
k2buckley said:
Did you wipe cache and dalvik before flashing gapps? Also, are you sure you're using the correct version of gapps for whichever rom you're on?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
yup did everything... weird but i got it working now..did everything the same way as b4...its really sweet.. and really fast... thanks a bunch for the help
nxtstep said:
hey thanks a bunch doug... that was the issue darn clockwork..lol.. got it running so far so good
so after i got it running decided to install the gapps stuff too from recovery...and there goes my phone again back to android with emergency call only... going to try installing again without gapps...any tips let me know please..
thanks
Click to expand...
Click to collapse
You're very welcome, my friend. I'm glad I was able to help. Take care and have a great day....
posting & replying via the XDA Premium app.
k2buckley said:
What ROM were you on before you flashed Salvage Mod? If it was a sense rom, you need to perform a full wipe (data/factory reset, cache, dalvik cache, boot, system) prior to flashing the new rom. When you said you cleared 'all cache', do you also mean you cleared dalvik cache as well? What recovery are you currently using? I'm on salvage 1.2.1 right now, and I've never had a problem booting it. When you say it won't boot, what does it do? Does it boot loop, or does it hang at the splash screen (white htc evo 4g screen)? The more info the better. I'd basically suggest doing a full wipe though, and try again.
Click to expand...
Click to collapse
You're a genius. I was doing a data/factory reset, cache, and dalvik, but not boot and system. When i did those, it worked. Thanks!
SHG-T989 on TMO. I was running CM 9.0 but wanted to update to 9.1. NOW I CANT DO ANYTHING!!! Here is what I did:
1. Downloaded the CM9.1. 2. did a backup through CWM. 3. wiped data through CWM, "wipe data/factory reset. 4. wiped cache partition through CWM. 5. did a Darkside Super Wipe through "install zip from internal sd card" (last time installing CM9 i got stuck in the boot screen and had to go back using Darkside Super Wipe, reinstall CM9 and it worked fine). 6. Reboot to recovery. 7. installed CM9.1 through "install zip from sdcard". 8. installed gapps through "install zip from sdcard". 9. Reboot.
It came up and was stuck in the CM9 boot screen. So I went back in through CWM and tried to "wipe data/factory reset" and it wont work! Tried to go back to stock through Odin and it wont work! When i try to wipe data, the process starts and completes the "formatting /data, then gets stuck at formatting /cache. Does the same thing if I try to wipe the cache.
Im completely stuck and have no phone.
Which recovery version are you using? It might a corrupted recovery.
Try this recovery TWRP is cwm flashable:
SGH-T989_TWRP_v2.2.2.0.zip - 6.72 MB
Then TDJs super wipe and then install the stock ROM or any other ROM.
http://forum.xda-developers.com/showthread.php?t=1858435
Sent from my SGH-T989 w/AOKP JB Sept-12-12 using XDA app.
any updates to this? i'm having basically the exact same problem, formatting cache or anything to do with that partition freezes up on me.
using cwm 5.0.2.7 did a darkside super wipe, flashed on a JB rom (P.A.Cman), flashed gapps (20121011), wiped cache, wiped dalvik cache, rebooted then got stuck on boot animation. rebooted back into cwm to try and wipe again and reinstall, no luck got stuck on formatting cache.
loaded up my nandroid which went fine, ended up installing twrp instead to see if that would help, rebooted into recovery and was stuck on the "teamwin" blue screen and wouldn't go further multiple times. so, put cwm back on (6.0.1.5) to see if the updated version would work. nope, same thing- can't do anything with the cache partition.
any ideas??
luckily my phone still works fine with the backup i made. running aokp ics build 40, streamline #27 kernel, uvle1 radio. been running that setup since july with no real problems, just wanted to try out JB finally and seems now i can't
any help is appreciated! thanks!
edit: will try the above post^ later tonight, just thought i'd see if i could get some more options to try out. thanks.
wwwwd83 said:
SHG-T989 on TMO. I was running CM 9.0 but wanted to update to 9.1. NOW I CANT DO ANYTHING!!! Here is what I did:
1. Downloaded the CM9.1. 2. did a backup through CWM. 3. wiped data through CWM, "wipe data/factory reset. 4. wiped cache partition through CWM. 5. did a Darkside Super Wipe through "install zip from internal sd card" (last time installing CM9 i got stuck in the boot screen and had to go back using Darkside Super Wipe, reinstall CM9 and it worked fine). 6. Reboot to recovery. 7. installed CM9.1 through "install zip from sdcard". 8. installed gapps through "install zip from sdcard". 9. Reboot.
It came up and was stuck in the CM9 boot screen. So I went back in through CWM and tried to "wipe data/factory reset" and it wont work! Tried to go back to stock through Odin and it wont work! When i try to wipe data, the process starts and completes the "formatting /data, then gets stuck at formatting /cache. Does the same thing if I try to wipe the cache.
Im completely stuck and have no phone.
Click to expand...
Click to collapse
Ok, the wipe scripts in CWM recovery v5 are broken! Got experience there because I got stuck on the PACman ROM boot animation.
So, for factory reset, use Darkside Super Wipe. Install zip from sdcard and choose the wipe. From there, install rom, then gapps, and then use the Darkside Cache Wipe. After that reboot and it should work (hopefully)
However the most important thing is that the wipes don't work in CWM recovery v6! It will do bad things!
So yeah, use super wipe to factory reset. Use cache wipe for cache. But follow the instructions to install the ROM.
Sent from my SAMSUNG-SGH-T989 using xda premium
m tr4nch said:
any updates to this? i'm having basically the exact same problem, formatting cache or anything to do with that partition freezes up on me.
using cwm 5.0.2.7 did a darkside super wipe, flashed on a JB rom (P.A.Cman), flashed gapps (20121011), wiped cache, wiped dalvik cache, rebooted then got stuck on boot animation. rebooted back into cwm to try and wipe again and reinstall, no luck got stuck on formatting cache.
loaded up my nandroid which went fine, ended up installing twrp instead to see if that would help, rebooted into recovery and was stuck on the "teamwin" blue screen and wouldn't go further multiple times. so, put cwm back on (6.0.1.5) to see if the updated version would work. nope, same thing- can't do anything with the cache partition.
any ideas??
luckily my phone still works fine with the backup i made. running aokp ics build 40, streamline #27 kernel, uvle1 radio. been running that setup since july with no real problems, just wanted to try out JB finally and seems now i can't
any help is appreciated! thanks!
edit: will try the above post^ later tonight, just thought i'd see if i could get some more options to try out. thanks.
Click to expand...
Click to collapse
got it all working again.. ended up odin flashing twrp 2.2 and i was able to boot into it, wipe everything, and install the new rom stuff.
Similar problem, but cannot make zips to work - HELP NEEDED
HI,
I hope you guys can help me. My T989 got stucked in the splash screen when I tried to update to a nightly CM10 ROM. I entered into Recovery MOde (ClockworkMod 6.0.2.7), then tried to use Darkside Super Wipe... but apparently the phone cannot open zip files. When I hit install zip from sdcard and then select one of the zips (I have tried different ones) it says "---Installing: /sdcard/sgh-t989_darkside.supe.wipe.zip"... but it does not move from there. After 3-4 minutes it reboots by itself and gets back to the splash animation, but never goes beyond that point.
I tried to sideload using ADB, but the phone is not recognized by my PC.
As you said, I think that the recovery mode is corrupted... but I cannot install a new version using a zip
Is there another way to reinstall a version of CWM that allows me to install zips so that I can follow the process you suggested (super wipe + installing ROMS)?
Help will be very much appreciated
Thanks for your time,
Enrique
thatdude02 said:
Ok, the wipe scripts in CWM recovery v5 are broken! Got experience there because I got stuck on the PACman ROM boot animation.
So, for factory reset, use Darkside Super Wipe. Install zip from sdcard and choose the wipe. From there, install rom, then gapps, and then use the Darkside Cache Wipe. After that reboot and it should work (hopefully)
However the most important thing is that the wipes don't work in CWM recovery v6! It will do bad things!
So yeah, use super wipe to factory reset. Use cache wipe for cache. But follow the instructions to install the ROM.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
kikorras said:
HI,
I hope you guys can help me. My T989 got stucked in the splash screen when I tried to update to a nightly CM10 ROM. I entered into Recovery MOde (ClockworkMod 6.0.2.7), then tried to use Darkside Super Wipe... but apparently the phone cannot open zip files. When I hit install zip from sdcard and then select one of the zips (I have tried different ones) it says "---Installing: /sdcard/sgh-t989_darkside.supe.wipe.zip"... but it does not move from there. After 3-4 minutes it reboots by itself and gets back to the splash animation, but never goes beyond that point.
I tried to sideload using ADB, but the phone is not recognized by my PC.
As you said, I think that the recovery mode is corrupted... but I cannot install a new version using a zip
Is there another way to reinstall a version of CWM that allows me to install zips so that I can follow the process you suggested (super wipe + installing ROMS)?
Help will be very much appreciated
Thanks for your time,
Enrique
Click to expand...
Click to collapse
Do NOT use that darkside superwipes with CWM recovery v6.X.X.X. Does bad things.
Use the scripts only for CWM v5.X.X.X.
Anyway, the damage is done and bad things have happened... So maybe check here
http://forum.xda-developers.com/showthread.php?t=1513359
Either that or you can search the forum and Google around and see what you can find. I am in by no means an expert, but depending if you can access the recovery mode or not might be the key here.
I wish you luck, and hope that you don't have a very expensive brick.
Sent from my SAMSUNG-SGH-T989 using xda premium
Use Odin. There is a tutorial on how to revert to stock GB (might be ICS) in the T989 development forum. It should be a sticky in that forum.
Ditto issues.. Thank good for search function. Read.. Read.. Read..
Sent from my SGH-T989 using xda app-developers app
Tried your suggestion, but Odin won't recognize my phone
Hi there,
Thank you very much for the answer. I actually spent hours trying to find something before I posted my question. Even before posting I found and tried the method using Odin... but my phone is not recognized by Odin. I followed the instructions but on step 4 I actually do not get any "warning" screen... and then the phone is not recognized.
In the meantime, I can get into recovery, but I cannot install any zips. I have tried to complete a factory reset, but the process gets stuck at "Formating /cache..." and then reboots. When I try to install a zip (any zip, the radio, a new ROM, gapps,... any zip really) it gets stuck too.
Any other ideas? I really appreciate your help.
thatdude02 said:
Do NOT use that darkside superwipes with CWM recovery v6.X.X.X. Does bad things.
Use the scripts only for CWM v5.X.X.X.
Anyway, the damage is done and bad things have happened... So maybe check here
http://forum.xda-developers.com/showthread.php?t=1513359
Either that or you can search the forum and Google around and see what you can find. I am in by no means an expert, but depending if you can access the recovery mode or not might be the key here.
I wish you luck, and hope that you don't have a very expensive brick.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
kikorras said:
Hi there,
Thank you very much for the answer. I actually spent hours trying to find something before I posted my question. Even before posting I found and tried the method using Odin... but my phone is not recognized by Odin. I followed the instructions but on step 4 I actually do not get any "warning" screen... and then the phone is not recognized.
In the meantime, I can get into recovery, but I cannot install any zips. I have tried to complete a factory reset, but the process gets stuck at "Formating /cache..." and then reboots. When I try to install a zip (any zip, the radio, a new ROM, gapps,... any zip really) it gets stuck too.
Any other ideas? I really appreciate your help.
Click to expand...
Click to collapse
The only other possible option I can think is to try and install another recovery....
However!
I have no clue how to do it, and in the end you might just end up making the issue worse.... Like hard brick it.
I might think of something later, but I don't know what else I can do for you. I will search around, but no promises...
Best of luck to you
--edit--
Ok try here possibly
http://forum.xda-developers.com/showthread.php?t=1777970
I have seen a few posts saying that they just install this recovery and then restore a backup.
Ok to be honest, try restoring a backup first and see if anything happens there, and then try this thread.
However like before, this may make the problem worse! Proceed with caution and read and understand everything before attempting.
Hope you can get your phone back to functional!
Sent from my SAMSUNG-SGH-T989 using xda premium
samsung jig
Thanks again for the answer. A couple of days ago I tried to install a functional backup that I had from CWM... but it does not work It runs for a long while, then reboots... but it still freezes on the splash screen (my theory is that the backup is not recovered, as I know for sure that the ROM I backed up did work fine)... I think that CWM is corrupted and not working properly.
Then I tried the solution from the thread you mentioned... but adb cannot find the phone when it is connected
I found somewhere that I can use a samsung jig (microUSB with a resistance) to make the phone enter into download mode, then reinstall CWM using ODIN and then try flashing a stable ROM... What do you guys think?
thatdude02 said:
The only other possible option I can think is to try and install another recovery....
However!
I have no clue how to do it, and in the end you might just end up making the issue worse.... Like hard brick it.
I might think of something later, but I don't know what else I can do for you. I will search around, but no promises...
Best of luck to you
--edit--
Ok try here possibly
http://forum.xda-developers.com/showthread.php?t=1777970
I have seen a few posts saying that they just install this recovery and then restore a backup.
Ok to be honest, try restoring a backup first and see if anything happens there, and then try this thread.
However like before, this may make the problem worse! Proceed with caution and read and understand everything before attempting.
Hope you can get your phone back to functional!
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
kikorras said:
Thanks again for the answer. A couple of days ago I tried to install a functional backup that I had from CWM... but it does not work It runs for a long while, then reboots... but it still freezes on the splash screen (my theory is that the backup is not recovered, as I know for sure that the ROM I backed up did work fine)... I think that CWM is corrupted and not working properly.
Then I tried the solution from the thread you mentioned... but adb cannot find the phone when it is connected
I found somewhere that I can use a samsung jig (microUSB with a resistance) to make the phone enter into download mode, then reinstall CWM using ODIN and then try flashing a stable ROM... What do you guys think?
Click to expand...
Click to collapse
I've heard about the jig method as well, but have no idea on how to go about doing it. Might be worth a shot. I don't think the jig costs that much anyway. I will see if I can find anything later.
Sent from my SAMSUNG-SGH-T989 using xda premium
Okay, I searched before posting. Here is my steps.
I was on SKYNOTE 8.2 and wanted to go back to stock and see what At&t's update was about.
Once back to stock, I rooted my phone and have been on this setup for about 2 weeks.
I was in the original thread and saw the new 4.2.2 Collective AoCP / CM10.1 ROM.
I wanted to try it out.
Using TWRP's latest, followed all instructions and when rebooting it still has stock root ROM.
What am I doing wrong?
I thought it was TWRP so I went to an earlier ver, still no change.
I've tried 4 times now to flash this 4.2.2 Rom and nothing.
Factory Reset
Wiped Dalvik
Install Zip
Install gapps
It says to wipe cache and data again
then boot up
It boots up alright, right into my old phone.
Any input I can get is appreciated guys !!!! Thanks.
Copy the ROM to your device (some storage folder)
Boot directly to TWRP
Manually install the ROM and the appropriate GAPPS
(watch the script window and see what it says.. look for errors)
Clear caches and dalvik
reboot
LuckyColdJohnson said:
Okay, I searched before posting. Here is my steps.
I was on SKYNOTE 8.2 and wanted to go back to stock and see what At&t's update was about.
Once back to stock, I rooted my phone and have been on this setup for about 2 weeks.
I was in the original thread and saw the new 4.2.2 Collective AoCP / CM10.1 ROM.
I wanted to try it out.
Using TWRP's latest, followed all instructions and when rebooting it still has stock root ROM.
What am I doing wrong?
I thought it was TWRP so I went to an earlier ver, still no change.
I've tried 4 times now to flash this 4.2.2 Rom and nothing.
Factory Reset
Wiped Dalvik
Install Zip
Install gapps
It says to wipe cache and data again
then boot up
It boots up alright, right into my old phone.
Any input I can get is appreciated guys !!!! Thanks.
Click to expand...
Click to collapse
Try wiping cache/delvik cache, then factory reset twice, then system wipe twice, Install .zip, Install GApps, then wipe cache/delvik again(don't wipe data after .zip is installed. That's how I always do it and it works great.
I think its my recovery Twrp. I changed something.
adam_wingert said:
Try wiping cache/delvik cache, then factory reset twice, then system wipe twice, Install .zip, Install GApps, then wipe cache/delvik again(don't wipe data after .zip is installed. That's how I always do it and it works great.
Click to expand...
Click to collapse
I have tried everything. Its got to be the recovery. No matter what I do in twrp, nothing changes. It says updating partitions and stimulating actions
. It also says successful. After updating to the newest twrp it started this. I changed something. ##[email protected] went into settings and reset....nothing. What if I flashed CWM and then went back to TWRP.
LuckyColdJohnson said:
I have tried everything. Its got to be the recovery. No matter what I do in twrp, nothing changes. It says updating partitions and stimulating actions
. It also says successful. After updating to the newest twrp it started this. I changed something. ##[email protected] went into settings and reset....nothing. What if I flashed CWM and then went back to TWRP.
Click to expand...
Click to collapse
Try cf auto root to reinstall stock then reinstall twrp through odin
Sent from my GT-N7105 using xda premium
What have I done ?
Android The Greek said:
Try cf auto root to reinstall stock then reinstall twrp through odin
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
Okay guys....This has made me sick to my stomach.....I have tried all the different methods. I even soft bricked my phone today using CWM.
Kies wouldnt even fix my phone.
I had to download stock firmware and flash via Odin to get back.
Installed TWRP
Rooted
Went into recovery and wiped everything again
Installed the custom ROM
Rebooted
TWRP didnt do anything even though it says it did.
My phone boots up like normal with Att logo and works but no Custom Rom and no wipes.
What is this? Im going to try other things but wow, this is crazy.
On my SD card I have alot of stuff. I also have a folder named TWRP, it has a back up in there. I wonder if I should remove that?
IDK,,,,,Stuck with Stock root for now. Help If you can. Never had this issue before. What a day
LuckyColdJohnson said:
Okay guys....This has made me sick to my stomach.....I have tried all the different methods. I even soft bricked my phone today using CWM.
Kies wouldnt even fix my phone.
I had to download stock firmware and flash via Odin to get back.
Installed TWRP
Rooted
Went into recovery and wiped everything again
Installed the custom ROM
Rebooted
TWRP didnt do anything even though it says it did.
My phone boots up like normal with Att logo and works but no Custom Rom and no wipes.
What is this? Im going to try other things but wow, this is crazy.
On my SD card I have alot of stuff. I also have a folder named TWRP, it has a back up in there. I wonder if I should remove that?
IDK,,,,,Stuck with Stock root for now. Help If you can. Never had this issue before. What a day
Click to expand...
Click to collapse
Might as well try everything. wipe your sd card in twrp,if that doesn't work reformat through android when booted. Then copy the custom rom over and try again. Only other thing I can think to try is to check that all partitions that are needed are mounted, or try CWM instead.
Also, how did you install TWRP? Through the app? that is the best way to do it, I have had problems flashing twrp through CWM or through the computer. If you aren't already, use goomanager to install it. TWRP has instructions on their website
I figured it out!!!!!!!
Doggydude said:
Might as well try everything. wipe your sd card in twrp,if that doesn't work reformat through android when booted. Then copy the custom rom over and try again. Only other thing I can think to try is to check that all partitions that are needed are mounted, or try CWM instead.
Also, how did you install TWRP? Through the app? that is the best way to do it, I have had problems flashing twrp through CWM or through the computer. If you aren't already, use goomanager to install it. TWRP has instructions on their website
Click to expand...
Click to collapse
It was the settings in TWRP. One of the boxes was checked. Sim actions for theming. I unchecked that and was on my way. Rocking The Collective AoCP now !!!!! Yes.....Thanks to all of you for your input. I'm going back to each and will hit thanks right now! Thanks again XDA members.
Lucky
I'm glad things worked out... isn't it amazing how attached we get to our toys
Sent from my GT-N7105 using 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.)