Hi Guys,
I've rooted my S3, and installed PhilZ Touch 5. Then I clear Data/Factory & Cache along with Delvik. I then proceed to install the custom rom from a zip.
It all installs fine, and says it has done so. But when it reboots, it gets stuck on the GalaxyS3 logo, with a little red Exclimatin mark in the top left corner and stays on that screen until I remove battery or reboot into download or recovery mode...
It seems I just can't load the newley installed roms. I've tried multipul, Archidroid, LiquidSmoot, pureLook HD, etc..
Has anyone run into this problem?
Its an Australian S3, so its the International i9300 btw.
Thanks in advance for any help!
Also, is there a way to completely wipe the phone and start from scratch, as I keep seeing ArchiDroid folders in the SD.
To start completely new you can use mega wipe. It will delete anything but the ext sdcard, hence be careful.
Sent from my Nexus 7 (2013)
Thanks, I'm thinking a MegaWipe would be the best bet, and then start fresh with a custom rom. I need to read more first so I don't screw up the phone..
just to update. the problem was solved with a mega wipe, i installed a new rom, and everything booted normally .
thanksssss
same problem i think except the red exclamation on the corner
Mr. John. i have the same problem now. You removed the battery after being stucked at the logo of samsung right? i wonder, were you able to go back to the home screen after removing the battery? thanks
perseidionix said:
Mr. John. i have the same problem now. You removed the battery after being stucked at the logo of samsung right? i wonder, were you able to go back to the home screen after removing the battery? thanks
Click to expand...
Click to collapse
No, if the phone won't boot after installing a new rom then no amount of battery pulling is going to make it boot.
Flash the super wipe .zip from recovery, assuming you've followed the instructions from your rom chef correctly.
survived the stucked screen
boomboomer said:
No, if the phone won't boot after installing a new rom then no amount of battery pulling is going to make it boot.
Flash the super wipe .zip from recovery, assuming you've followed the instructions from your rom chef correctly.
Click to expand...
Click to collapse
I already escaped the stuck screen. thankfully i have a nandroid back up (and i can still access the recovery mode). i was able to recover my old phone status.
thank you!
I was able to boot into recover & download mode, I was able to flash via odin any custom recovery and boot into it, I was able to wipe the cache/settings & delvik via recovery and then install any rom I liked, I could however not boot into any new/custom rom.
I then ran the MEGAWIPE.Zip in Philz, which I believe wiped some framework or something that was left behind stopping new roms to boot. I then installed a New rom, and it booted right away. No trouble what so ever...
Related
ok im stuck on my boot logo for my motorola droid 2. its a liberty logo, no the original M logo, ive held in x when it starts up and then it takes me to the triangle and then i hold the search button down and then it takes me to a menu saying this:
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
ive already tried just rebooting it and then it does the same thing again and just gets stuck at the boot logo, so please help. thanks!
Have you tried pulling the battery out for about 15 seconds?
See if that clears it up.
with it unplugged and turned off?
Yes Sir. Unlug it and turn it off.
yes i just did that and it didnt work, its still at the boot logo, the only thing i can do is go to that recovery menu that i said about in my 1st post, but idk what to do when i get there?
Try wipe data/factory reset.
Obviously you're gonna have to tweak your settings again.
okay, is there anyway i can get my settings back like a recovery? or something
Well, you might want to head in to the Droid 2 forums to get better responses related to your phone.
Here is a link to start with.
As far as recovery goes, I don't think you have a custom recovery installed. Sounds like you have a stock phone. So, there's no way of backing your stuff up.
i have it rooted and a rom on it but nothing custom, but thanks for all your help
Zimm814 said:
i have it rooted and a rom on it but nothing custom, but thanks for all your help
Click to expand...
Click to collapse
If you have it rooted, did you ever perform a Nandroid backup ?
Do you have a non standard recovery installed?
EDIT: Sorry re-read last few post and come to conclusion that you probably don't.
sorry but doesnt rds lite 4.8 and the correct sbf file let u flash back to stock?
If your phone is rooted then you have changed your kernal.It might be a fault with the kernal.I had a similar thing happen in an SGS.It was rooted and when i flashed the kernal againh via CWM it also got stuck on the same as you.The only way to solve it was boot to download mode and flash via odin again.
Hi guys, I got a SGS2 just over a week ago, on Bell/Virgin network in Canada. Suffered from the battery drain issue due to being stuck with crappy UGKG2 firmware which my provider still hasn't updated.
I decided to update it myself, and did a ton of research. I successfully got Root tonight by flashing CF-Root-SGS2_ZS-OZS_KG2-v4.1-CWM4 kernel with Odin. In case it matters, I did NOT flash back my stock Kernel, so I still had the insecure kernel installed. From there, I backed up my apps with Titanium.
Went into CWM and selected boot into CWM Recovery. I followed the steps on the wiki, including creating a backup file. My only hint of what I might have done wrong was I originally selected to flash update.zip, and that process failed. I then went to the directory in which cyanogenmod is stored on my SD card, and selected that, then it installed ok. I had downloaded update-cm-7.10-GalaxyS2-signed and that's what I put on the phone. I then also installed the Google Apps.
I then hit reboot, and it only goes to the Samsung screen with the yellow triangle and just hangs there for a few minutes. Not knowing what else to do, I popped the battery out. I have since learned that I can turn it on and off, but it never goes past that screen. Wouldn't go into the recovery or download modes, always that screen. Luckily, I saw somewhere to do the 3 button thing WHILE in that screen, and that works. So I can get to recover, and download modes. So, I think I'm ok. I checked, and it does connect to Odin still.
I just want to know EXACTLY what I should do at this point. I don't want to fully brick it. There are actually two recovery files on the phone... not sure why... Or which one to pick. Should I just flash stock firmware back with Odin? One of my main goals is to get off 2.3.3 so I can have more than 8 hours of battery...
Thanks,
Rob
Boot into tecovery, do a full wipe again. (Wipe data/factory reset, wipe cache partition, advanced>wipe dalvik cache).
Now install CM7 zip twice in a row without reboot. It may take a few minutes for reboot since system is rebuilding dalvik cache. Be patient. After you see the home screen, reboot again.
Sometimes, CM won't install properly with CF root recovery. In that case reboot into download mode, flash codeworkx cwm kernel via ODIN.
http://forum.xda-developers.com/showthread.php?t=1118693
Now reboot into recovery and do full wipe and twice-install !
Ok, working now with the flash twice thing. Well that's weird, would be great if it was in the wiki page...
Thanks!
Rob
Ok so I'm fairly new to the rooting scene, and these forums, but so far everything has been pretty good, except for one small problem. I installed a custom boot logo, and afterwards my phone was lagging a bit. I contacted the boot logo programmer, with no response, so I decided to wipe my system and use the backup from right before I installed the custom boot logo. Unfortunately, the boot logo has not changed, and my phone 'fails' whenever I try to flash something from Odin. Anyone know what to do in this situation.
If you want to do a full wipe of you device,cos it sounds like tha boot logo is corrupt,then boot to recovery and wipe cache partition and dalvik cache.then go to "storage and mounts" and format system,data and cache.Select "Go Back" and factory reset your phone and reboot.If it doesnt go past the boot logo after 1min then pull the battery,put it back in and turn it back on.Its a pain in the arse but it will completely clean up your device and if you where rooted you will need to probably reroot but berfore hand plug in your phone to your PC so it gets recognized again.
EDIT:Just incase,first of all download titanium backup from the market and backup your apps!!!!
Sting Rray said:
Ok so I'm fairly new to the rooting scene, and these forums, but so far everything has been pretty good, except for one small problem. I installed a custom boot logo, and afterwards my phone was lagging a bit. I contacted the boot logo programmer, with no response, so I decided to wipe my system and use the backup from right before I installed the custom boot logo. Unfortunately, the boot logo has not changed, and my phone 'fails' whenever I try to flash something from Odin. Anyone know what to do in this situation.
Click to expand...
Click to collapse
You need to wipe usb storage, sd card, then put phone in download mode, flash stock ROM using Odin. You need to fully wipe everything.
Sent from my Sexynos SGH-i777 using XDA Premium.
I've trying reflashing the stock ROM and kernel; however, it gives me a FAIL and says can't open the serial (COM) port.
I have solved the problem by closing Samsung Kies and wiping the system, thanks for all the help offered.
As the thread title states...I was on 7.1 and downloaded/updated it to 7.2 Now the phone doesn't boot up and all I get is the Kernel Panic Upload Mode.
Anyway I can fix this? And if so, is there a way of doing it without completely formatting my phone and losing all my apps?
Oh and if it makes any difference I had to install that Siyah Kernel or whatever it was called to get out of the bootloop issue that I had with CM7.1. I'm thinking that that may be causing the problem....? But then again what do I know
wipe cache only.
valentinrascu said:
wipe cache only.
Click to expand...
Click to collapse
How? I've been trying [Power+Volume Up+Home] and it hasn't been doing anything. Can I do it through download mode somehow?
Had this problem when i flashed Lite'ning rom. Had to go into download and flash stock with odin. Took me a few tries to actually get the rom to work. As far as I know, that'd be your only option, seeing as recovery doesn't work for you.
take a deep breath and read, there is a very small chance of bricking your phone just so you know. Flash back original with Odin and start everything again
thanks for the replies...looks like i'm gonna flash the stock firmware back and see what i can do about getting to CM7.2 to work. hopefully flashing stock firmware is enough. I can't imagine how this would completely brick my phone and render it unusable.
As an aside...wtf is the point of this "recovery mode" when the thing doesn't even work half the time?
Anywho...downloading the stock .exe file now from here: http://devsrom4android.blogspot.ca/2011/10/samsung-galaxy-s2-firmwares-bell-canada.html[/url
Ok so I flashed the stock rom and now I'm in Android system recovery: Should I just reboot system now or do I wipe data/factory reset or wipe cache partition??
nubreed000 said:
Ok so I flashed the stock rom and now I'm in Android system recovery: Should I just reboot system now or do I wipe data/factory reset or wipe cache partition??
Click to expand...
Click to collapse
If you flashed stock, you should be fine just rebooting.
Its stuck on the boot screen. I tried just rebooting, then wiping/factory reset, then both wipes...reinstalled stock a few times and nothing worked each time. I'm suck on the Samsung Galaxy SII GT-I9100 screen
:-\...when I go into recovery, I get a ton of red messages/errors
I'm gonna try somethig other than stock firmware see if that helps.
edit Ok so I rooted the phone and it got past the first boot screen and now appears to be stuck on the "animated S" boot screen...progress!!
nubreed000 said:
thanks for the replies...looks like i'm gonna flash the stock firmware back and see what i can do about getting to CM7.2 to work. hopefully flashing stock firmware is enough. I can't imagine how this would completely brick my phone and render it unusable.
As an aside...wtf is the point of this "recovery mode" when the thing doesn't even work half the time?
Anywho...downloading the stock .exe file now from here: http://devsrom4android.blogspot.ca/...msung and their changes to Android framework.
Click to expand...
Click to collapse
Ok everything back to somewhat normal. Stock ROM didn't work but 2.3.6 did, so I'm on that. Now do I wanna go back to CM is the question...
Either way, thanks again for all the replies and helping me out with this. Greatly appreciated!
So I have been following the unofficial cm-10.2 ROM. I have dirty flashed probably 3 times without issue. I flash the ROM, a pinlock removal zip and gapps. Then wipe dalvik/cache and reboot. I started doing this with twrp 2.6.
So this morning I grab the latest update, backup, flash.l, reboot.... nothing.
Stuck at LG logo to a black screen. I can get into bootloader, blindly vol down twice and into recovery, now twrp 2.5, so I try to recover by backup, reboot.... black screen.
So I try wiping/factory reset, clean flash, reboot.... black screen...
Now I am a little concerned. I read up and find out about TeenyBin, so I setup my machine to flash the standard zip and that doesn't really work, it flashes fine, reboots but is stuck at LG logo and the tool reports disconnected, so the tool fails kind of. So I try the alternate, same sort of thing, but now it says Google instead of LG and is stuck there. I can get into bootloader, can see text now (nice!) and get into recovery, still 2.5. Tried restoring, wiping/flashing, nothing working..... stuck at Google logo.
So, then I went and formatted internal storage. Bingo! Now I can flash/restore/whatever and I can reboot and get into ROM!
Woah, woah, woah... Not so fast.
So now if I wipe anything, cache/dalvik/system/ANYTHING it soft bricks. I have to again format internal, then flash. That doesn't seem right to me. Sure, I have a functioning phone, but updating is a bigger ***** now that I have to completely format before flashing.
So my question to you all, how do I fix this? Do I need to completely go back to stock image and reroot? I appreciate all your suggestions.
daveerickson said:
So I have been following the unofficial cm-10.2 ROM. I have dirty flashed probably 3 times without issue. I flash the ROM, a pinlock removal zip and gapps. Then wipe dalvik/cache and reboot. I started doing this with twrp 2.6.
So this morning I grab the latest update, backup, flash.l, reboot.... nothing.
Stuck at LG logo to a black screen. I can get into bootloader, blindly vol down twice and into recovery, now twrp 2.5, so I try to recover by backup, reboot.... black screen.
So I try wiping/factory reset, clean flash, reboot.... black screen...
Now I am a little concerned. I read up and find out about tinyrom, so I setup my machine to flash the standard zip and that doesn't really work, it flashes fine, reboots but is stuck at LG logo and the tool reports disconnected, so the tool fails kind of. So I try the alternate, same sort of thing, but now it says Google instead of LG and is stuck there. I can get into bootloader, can see text now (nice!) and get into recovery, still 2.5. Tried restoring, wiping/flashing, nothing working..... stuck at Google logo.
So, then I went and formatted internal storage. Bingo! Now I can flash/restore/whatever and I can reboot and get into ROM!
Woah, woah, woah... Not so fast.
So now if I wipe anything, cache/dalvik/system/ANYTHING it soft bricks. I have to again format internal, then flash. That doesn't seem right to me. Sure, I have a functioning phone, but updating is a bigger ***** now that I have to completely format before flashing.
So my question to you all, how do I fix this? Do I need to completely go back to stock image and reroot? I appreciate all your suggestions.
Click to expand...
Click to collapse
Give CWM a shot and see if it does the same thing?