How long do I wait for reboot after flash SuperNexus? - Galaxy S II Q&A, Help & Troubleshooting

Hello,
Newbie here. Followed all instructions on the SuperNexus ROM and did the flash, hit reboot and now I have been waitong on a loading screen with a nice colourful X for around 20 mins...
How long do I wait?

Maybe try to reflash the rom. Don't know about Supernexus specificaly, but 20 minutes is in general too long for a reboot after flashing a rom.
Sent from the Matrix

BlandyDoes said:
Hello,
Newbie here. Followed all instructions on the SuperNexus ROM and did the flash, hit reboot and now I have been waitong on a loading screen with a nice colourful X for around 20 mins...
How long do I wait?
Click to expand...
Click to collapse
Reboot into recovery and wipe data/factory reset and then reboot and should boot to rom. As mentioned above 20 mins is generally too long, 5 mins usually max I would wait.
Whenever you flash a new rom you should wipe data/factory reset before flashing. Only times you shouldnt is if you're simply installing a rom update like a CM nightly etc. Rom/kernel cleaning scripts that you flash via cwm are also good for cleaning old crap and avoid issues. You can backup/restore all your apps/appdata with Titanium Backup Pro.

Even 5 minutes is a long time, the average bootscreen I get after flashing a new ROM is 2-3 minutes. 20 minutes is definately a boot loop. Just go back into CWM wipe data and reflash.
If you have information you don't want to wipe though then try and reflash the ROM you were previously on and boot up, or use a cleaning script to try and get past the bootloop. However, you're going to need to wipe at some point or it will be very unstable.

postfatal said:
Even 5 minutes is a long time, the average bootscreen I get after flashing a new ROM is 2-3 minutes.
Click to expand...
Click to collapse
I didnt say 5 mins is average, I said 5 mins would be the max I would wait before wiping/reflashing etc.
postfatal said:
20 minutes is definately a boot loop.
Click to expand...
Click to collapse
lol, no it isnt. A "bootloop" is when your device just keeps rebooting in a loop, ie goes to a logo/kernel screen reboots and goes back and does same, hence "loop". If its stuck on a screen for 20 mins its just stuck, not in a "loop".
postfatal said:
Just go back into CWM wipe data and reflash.
Click to expand...
Click to collapse
No real need to re-flash just yet as 9/10 you can simply wipe data, although flashing aswel wouldnt hurt.
postfatal said:
If you have information you don't want to wipe though then try and reflash the ROM you were previously on and boot up,
Click to expand...
Click to collapse
Or restore from backup user made. (If he had enough sense to make one).

Well then it's stuck, if I slipped up and said bootloop does it really matter, the effects are the same in that his device isn't working. If I wipe data I always reflash afterwards, and a backup would be a great suggestion, but given he is "newbie" and this is his first post, and he's obviously got about as much clue about these things as Inspector Clouseau in a coma, restore a backup probably isn't going to happen. If he does have a backup though (meaning he has some clue), why on earth has this thread ever been made?
I'm not really sure why you addressed me directly over some totally unimportant points but thanks, I like to write stuff.

postfatal said:
Well then it's stuck, if I slipped up and said bootloop does it really matter, the effects are the same in that his device isn't working. If I wipe data I always reflash afterwards, and a backup would be a great suggestion, but given he is "newbie" and this is his first post, and he's obviously got about as much clue about these things as Inspector Clouseau in a coma, restore a backup probably isn't going to happen. If he does have a backup though (meaning he has some clue), why on earth has this thread ever been made?
I'm not really sure why you addressed me directly over some totally unimportant points but thanks, I like to write stuff.
Click to expand...
Click to collapse
Nothing personal dude, was just that I was addressing the 5 minute thing so thought I would split it up a bit
I personally use cleaning scripts for rom/kernel before every flash now except for cm nightly updates.

Thanks to everyone who replied. Not sure why people end up arguing in these threads though. lol
In a nutshell I left it for over an hour just in case, then I turned it off and on, powered into recovery with CWM did the data wipe and then rebooted again into recovery to flash in the SuperNexus file and the Google Apps file. I did one at a time with a reboot after each file flash, that speeds up the process a lot. Took about 2 mins per flash to work.
This is awesome!

Related

rooted phone 1.4 installed warmtwopointthree and now

it wont load past the HTC screen..
flashed WARM-3.5-evo3d-unofficial-r100.zip
from sdcard.
had down a factory wipe initially.. tried clearing dalvik cache again but still cannot get past htc screen. ugh
correction i flashed to r119.zip
Did you wipe system as well? How long are you giving it at the HTC Splash screen before you decide it's frozen? I haven't been keeping up to date with the Warm train lately, so I'm not sure if there have been any issues with the builds. I know back in the day, sometimes the build bot that myn used would bork a build from time to time and it wouldn't flash. Have you tried flashing any other builds, or just r119?
yes i did a complete wipe initially.. flashed.. got stuck at screen.. i left it there for 2-3 mins with no response.. just hovering at the HTC screen. I have not tried flashing any other roms as I wasnt sure what if any adverse affect this may have on the current problem
tre976 said:
yes i did a complete wipe initially.. flashed.. got stuck at screen.. i left it there for 2-3 mins with no response.. just hovering at the HTC screen. I have not tried flashing any other roms as I wasnt sure what if any adverse affect this may have on the current problem
Click to expand...
Click to collapse
Before you go any further in trying to figure it out, I would let it sit at the HTC screen a bit longer than a couple minutes. I've had it hang there for 5 or 6 minutes on certain sense roms that I flash, especially on the first boot. Give it a solid 7 minutes or so, and if it's still hanging there..then yea it's stuck. After that, I would simply try flashing something else and see if it works. Perhaps you got a bad download as well, maybe try re downloading it.
suggestions on how to move rom to sdcard if phone isnt booting hence PC isnt seeing the drive?
is it possible to go back to stock rom if this doesnt work?
tre976 said:
suggestions on how to move rom to sdcard if phone isnt booting hence PC isnt seeing the drive?
is it possible to go back to stock rom if this doesnt work?
Click to expand...
Click to collapse
Transfer it to the SD card from recovery. I'm not sure what recovery you're on, but every recovery has the feature to mount the sd card from within recovery. It's like USB MS Toggle or something to that nature. In TWRP 2, I think it's under the 'mount' tab.
Did you just try turning it on again yet, and seeing if it will eventually get past the HTC Screen? Again, it could take a bit more than 2 or 3 minutes on the first boot.
EDIT: And yea, you should be able to get back to a stock ROM no problem, or at least get back to a functioning phone, lol. Did you make a nandroid of your stock setup right after you rooted, before you tried flashing warm?
no i didnt make a nandroid backup sadly. im letting it sit for 10 mins before i give up on tyhis version
I don't think that ROM will boot as I'm pretty sure it has no boot image in it. Joelz was doing some stuff on the later builds and removed the bootimage.
Go into the thread and look for Vin's post. He is on the front page or on post 2. He has been the one updating the ROM for Joelz. the last version I knew of was around 01/12 or so?
tre976 said:
no i didnt make a nandroid backup sadly. im letting it sit for 10 mins before i give up on tyhis version
Click to expand...
Click to collapse
Again, you said you're hboot 1.4, right? So you S-offed with revolutionary? Cuz if you're 1.5, then we're missing an important step....
Sent from my PG86100 using Tapatalk
Never mind, 01/27/12 was his last update.
Here ya go, flash this one.
http://forum.xda-developers.com/showpost.php?p=21019364&postcount=279
KB112 said:
I don't think that ROM will boot as I'm pretty sure it has no boot image in it. Joelz was doing some stuff on the later builds and removed the bootimage.
Go into the thread and look for Vin's post. He is on the front page or on post 2. He has been the one updating the ROM for Joelz. the last version I knew of was around 01/12 or so?
Click to expand...
Click to collapse
LOL, that would certainly explain his problems. As I said, I haven't been keeping up to date with the warm team
Sent from my PG86100 using Tapatalk
Yeah, I read his post too fast. I didn't realize he was flashing Sense 3.5 version. Vins version is really nice and clean, he's done an excellent job helping JoelZ and keeping the ROM alive.
k2buckley said:
Again, you said you're hboot 1.4, right? So you S-offed with revolutionary? Cuz if you're 1.5, then we're missing an important step....
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
no it was 1.4 from revolutinary.io.. it has the nandroid option i missed that step in the instructions before flashing. Thanks i'll try the link above
k2buckley said:
Transfer it to the SD card from recovery. I'm not sure what recovery you're on, but every recovery has the feature to mount the sd card from within recovery. It's like USB MS Toggle or something to that nature. In TWRP 2, I think it's under the 'mount' tab.
Did you just try turning it on again yet, and seeing if it will eventually get past the HTC Screen? Again, it could take a bit more than 2 or 3 minutes on the first boot.
EDIT: And yea, you should be able to get back to a stock ROM no problem, or at least get back to a functioning phone, lol. Did you make a nandroid of your stock setup right after you rooted, before you tried flashing warm?
Click to expand...
Click to collapse
gives me a Mount system or mount /data..
oh i see it i mounted sdcard.. oddly windows doesnt see the card tho as a drive still
tre976 said:
gives me a Mount system or mount /data..
oh i see it i mounted sdcard.. oddly windows doesnt see the card tho as a drive still
Click to expand...
Click to collapse
What recovery are you using?
It should be Toggle USB or something like that
i used my wifes phone sdcard to bypass the problem. that flash got me to a loading phone boot now. thanks! but i'm apparently not connecting to sprint. lol. go figure..
fwiw im using twrp 1.0.3
Ok, now you may have to call them ask to have your data reset. There is a specific thing to ask for. It's in the threads on how to root the Evo 3D.

Unable to flash any other ROM after PhantomTask

hi everyone,
I am actually a long time custom ROM flasher started since Desire days, but registered recently because of this problem I have with the Tab 10.1 Wifi.
Despite me trying everything I can think of, I couldn't flash any other ROMs now, including GalaxyTask, Overcome, AOKP CM9, except the stock Honeycomb sans TouchWiz ROM, and of course PhantomTask. I am pretty sure PhantomTask is the last ROM I've flashed until this problem comes up.
I have made sure that I have done a full clean wipe every time before I flash any of them, wipe data -> cache -> dalvik cache, I even format /system partition, but still none of them works. They always get stuck at boot screen, unless the either one of the two ROMs I've mentioned, stock or PhantomTask.
I am sure that my downloads are complete too, as I've checked MD5 for each of them.
So I really don't know what to do now, any ideas?
I'd really want to test out AOKP
How much time are you giving it to boot up?
I've tried flashing CM9 yesterday, and I left it overnight to boot, it still didn't boot pass the logo, and the battery drained out.
I'll give it another try later
Which version of CWM are you using? If you aren't using one of these try updating:
ClockworkMod - 5.0.2.7
http://forum.xda-developers.com/showthread.php?t=1090289
Overcome Recovery v5.1.2.6
http://forum.xda-developers.com/showthread.php?t=1348533
ok I've tried everything I can, and still can't get this to work.
Then finally I've decided to try to unroot and restore everything to stock.
I've followed each and every step of this guide
http://forum.xda-developers.com/showthread.php?t=1474971
After everything is done, Odin is showing the pass sign, according to the video its suppose to reboot into Android, but weirdly its stuck at a black screen. So I unplugged it from the PC rebooted it by holding down power button. But now its stuck at the boot logo, and won't proceed, its been more than 10 mins.
I am still able to boot into download mode, but when I boot into recovery wanting to do a factory reset, it shows a black screen and nothing else.
any idea what's going on?
try using the overcome recovery posted above. there's a link in the post that will take you to the over come site. look for the restore yet tab section and use Odin to restore. follow their instructions exactly an make sure it's relevant to your device first.
this has helped MANY people who had some of the strangest problem start fresh. if you want or need specific links just ask I'll go to my PC where its easier to show you.
hth
Sent from my GT-P7510 using one stinky finger.
OMG
Benzoman said:
try using the overcome recovery posted above. there's a link in the post that will take you to the over come site. look for the restore yet tab section and use Odin to restore. follow their instructions exactly an make sure it's relevant to your device first.
this has helped MANY people who had some of the strangest problem start fresh. if you want or need specific links just ask I'll go to my PC where its easier to show you.
hth
Sent from my GT-P7510 using one stinky finger.
Click to expand...
Click to collapse
I can't believe it WORKED!! THANKS MAN!!
j3nnning said:
I can't believe it WORKED!! THANKS MAN!!
Click to expand...
Click to collapse
COOL! Thanks to you for posting that it worked. Knowing we help is one reason we keep trying to help.
For me personally it's the self gratification of just knowing.
It's kinda selfish I know but it makes me feel good and keeps me trying to help even in the littlest ways my limited knowledge allows.
Again thanks back at you.
Sent from my GT-P7510 using XDA Premium HD app

Android is updating

I've seen a post about this one in the EVO area, but not here amongst us SGS3 owners:
When I reboot my phone, it always goes through an "Android is updating, application xxx of 3xx" counting up - and takes two or three minutes every reboot.
Is this normal under ICS?
Hmm, I'd say this is Not normal. One of the big "selling points" of the gs3 and ICS is the quick boot time. For me it is very quick. Maybe u should try doing a factory reset and see if it stops this behavior??
Sent str8 from my half eaten Banilla Ice Cream Samich
ratledge said:
I've seen a post about this one in the EVO area, but not here amongst us SGS3 owners:
When I reboot my phone, it always goes through an "Android is updating, application xxx of 3xx" counting up - and takes two or three minutes every reboot.
Is this normal under ICS?
Click to expand...
Click to collapse
If you're rebooting your phone after you wipe your dalvik cache, than that is normal. Reason being is that it stores applications for optimization so that the OS can run more smoothly. When you wipe your dalvik, it clears them out, and then when you reboot, it rebuilds the cache for all applications. Just do a normal reboot without wiping anything and see if it still does it.
That is not normal if it is happening on every boot, only if you wipe your dalvik cache then yes it will update.
id_twin said:
If you're rebooting your phone after you wipe your dalvik cache, than that is normal. Reason being is that it stores applications for optimization so that the OS can run more smoothly. When you wipe your dalvik, it clears them out, and then when you reboot, it rebuilds the cache for all applications. Just do a normal reboot without wiping anything and see if it still does it.
Click to expand...
Click to collapse
Yep, just a simple reboot or even a fault / reboot does the same thing. I'm not wiping the Dalvik cache or anything. Happens every time I boot my phone, and I've noticed over the past few days that I never seem to go into 4G/LTE mode any more. Curious - I guess I've laid the hammer on it a bit too much.
Are you using a custom rom or rooted? Or are you completely stock?
Sent from my SCH-I535 using Tapatalk 2
ratledge said:
Yep, just a simple reboot or even a fault / reboot does the same thing. I'm not wiping the Dalvik cache or anything. Happens every time I boot my phone, and I've noticed over the past few days that I never seem to go into 4G/LTE mode any more. Curious - I guess I've laid the hammer on it a bit too much.
Click to expand...
Click to collapse
what rom r u using ????
with aokp there are setting to which the user can wipe cache and dalvik on every reboot
I read on another forum that a TitaniumBackup odex file may cause this on certain phones. Try uninstalling the apk and then re-install it.
krackerjac said:
what rom r u using ????
with aokp there are setting to which the user can wipe cache and dalvik on every reboot
Click to expand...
Click to collapse
Sure sounds like it. I'm using the "Route66" rooted ROM with the Invisiblek overclocking kernel in place of the recovery.
Most likely the overclock. i ran the stock rooted 66 with no issue. I also have titanium backup installed without that issue.
id_twin said:
I read on another forum that a TitaniumBackup odex file may cause this on certain phones. Try uninstalling the apk and then re-install it.
Click to expand...
Click to collapse
Worth a shot. I'll give it a rip and report back... Thanks!
hmmm... Uninstalled and replaced Titanium Backup, reflashed the stock recovery: no joy there. I'm still getting the rebuild every time I boot. I suppose when I have more time (read next weekend, I'm working 12 hours every day this weekend, then my niece is in town for a week), I'll blow it to hades and start over.
ratledge said:
hmmm... Uninstalled and replaced Titanium Backup, reflashed the stock recovery: no joy there. I'm still getting the rebuild every time I boot. I suppose when I have more time (read next weekend, I'm working 12 hours every day this weekend, then my niece is in town for a week), I'll blow it to hades and start over.
Click to expand...
Click to collapse
Oh, well - factory reset, re-route66, invisiblek's v2 overclocked kernel. I'm good, no "Android is updating..." every time, and no mo unlocked icon on the main screen.
I dunno what I did, but the Sammy din't like it!
Thanks, guys!

Stuck in Boot Animation

I flashed AndroWook onto my prime, and I cannot get past the Star-Wars-Text boot screen (it just keeps repeating).
I can get into TWRP, but mounting the system won't let my prime be recognized by the computer.
How can I get a new zip onto my prime to re-flash? Can I use fastboot somehow? Can I fastboot Clockwork Recovery instead and use that to mount?
Wipe everything and flash again, dont select bravia and sql mods. after flash wipe cache again and dalvik too
Unless you know how to use ADB, don't wipe everything.
Do a factory reset and reflash Androwook from TRWP. The first time it runs, it can as long as 5 minutes to fully load. Let it go, don't stop it just be patient and wait. If after 10 minutes nothing is going on, then reset and try to revert to your backup.
I understand what you guys are telling me to do, but I hate to say that I just don't know exactly how to do it.
Care to help out a little more and elaborate? I'd really appreciate it.
Johnotronz said:
I understand what you guys are telling me to do, but I hate to say that I just don't know exactly how to do it.
Care to help out a little more and elaborate? I'd really appreciate it.
Click to expand...
Click to collapse
Did you make a backup?
I told it to when I flashed with Goo manager, yes.

[Q] Need Help

guys i have a funny issue wonder if i can get some help. I flashed FlappJaxx Beta 3 and had a bad down load or something so anyway tons of reboots and nothing just the non stop vibrate.. well i i finally got it back to the down load screen after pulling the battery several times. and got it Odin back to unrooted and turn on followed the unroot instruction well i left it stock and have had same issue where i click something and it flashes and just vibrates over and over until i pull battery.. well is this phone dead is there a fix?
I odin back again and same thing im going to odin back to stock again then do a stock root and flash another room but its doing the stupid reboot over and over vibrate thing even with the non-rooted stock rom. i just can't seem to find any direction on how to fix this or is it just a lost cause. wanted it to hold on till Note 2 hit shelves but looks like a s3 in my futures.
OK didnt work still FC and boot looping this time i installed Kies and put in download mode and updated the firmware and im getting same thing. GOSH DOGGIT hahaha.. Yea i need some advise i tried everything ive read i must be missing something somewhere.
i guess no one has ever had this before? still no solution i have tried everything format the internal disc but want to know if i do that will i be able to flash odin back to stock any help there?
walkerkd said:
i guess no one has ever had this before? still no solution i have tried everything format the internal disc but want to know if i do that will i be able to flash odin back to stock any help there?
Click to expand...
Click to collapse
First of all, I'm no pro at this stuff but I feel your pain.
It sounds like you are getting stuck in a boot loop of sorts.
What I would do if I was you, after flashing a rom, go back into Recovery mode on the phone and clear out the cache partion, wipe Dalvik cache, and then wipe data/factory reset. After that, reboot your phone - it should start up normally. This is what I do to my phone to get it to function as it should.
Hope that helps
i went in to the advance tab and formatted everything hahah.. it juts wiped and odin back to stock again bout to wipe it and try to odin root see if i can get it done. worth a try ive tried to much stuff im bout to take phone out get my 338 tape to a zombie target and have some fun!
walkerkd said:
i went in to the advance tab and formatted everything hahah.. it juts wiped and odin back to stock again bout to wipe it and try to odin root see if i can get it done. worth a try ive tried to much stuff im bout to take phone out get my 338 tape to a zombie target and have some fun!
Click to expand...
Click to collapse
What language are you using here? I have no idea what you are saying.
kmacsouris said:
First of all, I'm no pro at this stuff but I feel your pain.
It sounds like you are getting stuck in a boot loop of sorts.
What I would do if I was you, after flashing a rom, go back into Recovery mode on the phone and clear out the cache partion, wipe Dalvik cache, and then wipe data/factory reset. After that, reboot your phone - it should start up normally. This is what I do to my phone to get it to function as it should.
Hope that helps
Click to expand...
Click to collapse
Agreed ...
When returning to stock via Odin ...you must reboot into your recovery and wipe data and factory reset the device prior to rebooting.
Even though you wiped prior to flashing the stock Odin .tar image.
These devices stay dirty even after wiping data on occasion ...g
gregsarg said:
Agreed ...
When returning to stock via Odin ...you must reboot into your recovery and wipe data and factory reset the device prior to rebooting.
Even though you wiped prior to flashing the stock Odin .tar image.
These devices stay dirty even after wiping data on occasion ...g
Click to expand...
Click to collapse
Yea i think thats what happen. it was not a clean wipe but i think i got it now i have gotten two fc & reboot i can live with that. thanks you guys for your help.
walkerkd said:
Yea i think thats what happen. it was not a clean wipe but i think i got it now i have gotten two fc & reboot i can live with that. thanks you guys for your help.
Click to expand...
Click to collapse
Boot into your recovery, and "fix permissions "...then reboot.
That should clear up the rest of the issues ...g
gregsarg said:
Boot into your recovery, and "fix permissions "...then reboot.
That should clear up the rest of the issues ...g
Click to expand...
Click to collapse
oh really? wow i didnt even think about that im wiping again and flashing odin to stock but this time after it boots i will wipe factory reset. then root factory reset and fix permissions. thank for the help!
Always welcome ....
Fixing permissions is overlooked a lot ...
And the wrong permissions will cause FC's all over the build ..
I always fix permissions after any flash or modification ....it's just a good habit to get into ...IMHO ...g

Categories

Resources