I've been trying to flash Hanthesolo's rom for the Samsung Galaxy Player 4.0 US (http://forum.xda-developers.com/showthread.php?t=1729566) and I at first tried Klin's Kernel and it worked fine, phone booted up fine. Then I flashed Hans rom (yes I read it will sit at boot for a while) and let it sit at the boot screen for about an hour. Restored via CWM (wouldn't restore system?). Went back into download and flash Terra Kernel and Hans rom again. Currently at boot animation.
Dridge93 said:
I've been trying to flash Hanthesolo's rom for the Samsung Galaxy Player 4.0 US (http://forum.xda-developers.com/showthread.php?t=1729566) and I at first tried Klin's Kernel and it worked fine, phone booted up fine. Then I flashed Hans rom (yes I read it will sit at boot for a while) and let it sit at the boot screen for about an hour. Restored via CWM (wouldn't restore system?). Went back into download and flash Terra Kernel and Hans rom again. Currently at boot animation.
Click to expand...
Click to collapse
What version of the ROM?
Okay, you need to get into recivery, wipe cache/dalvik, theb reflash the kerbel then my rom. If it sticks at the bootlogo again, simply reboot into recovery, wipe cache/dalvik abd fix pernissions in the advanced.menu. It should work after that!
Related
Hi
Urgent help needed bought another galaxy s2 for someone. Successfully rooted, cwm using odin and unlocked using Galaxy_S Unlock app from the market.
Then I got bit carried away and installed mui rom from rom manager, went ok went fine.
I got further excited and flashedstock Kernel_I9100XWKK5 via odin. It flashed fine boot galaxy boot screen turns on but then screen goes blank and nothing.
Still got cwm.
Flashed original rom BVKE2 but still same problem
Please help not sure what to do!!!!!!!
Hey, it seems a corrupt kernel is the culprit... in CWM, do:
- a wipe of a cache partition
- a wipe of dalvik cache
- install zip from sdcard -> Samsung Ultimate Kernel Cleaning Script
- flash a kernel, like SiyahKernel 2.6.5
- reboot
if it doesn't work, try reflashing any custom rom (for example VillainRom)
thanks mate i think realised the error i made just flashed kernel and not the rom!!!
trying it now i've got boot loop now. step closer
I have S-off Hboot 1.4
Was running Cleanrom 1.1 reborn. & Twrp
Flashed over to CM9 Nightly, worked fine.
Decided I wanted to go back to a sense ics rom, so I flashed the latest ICS meanrom.
Phone went into bootloop
Went back into recovery, flashed superwipe, then did factory reset/wipe cache
Flashed ICS Meanrom again, still boot loop.
Restored TWRP backup I have of stock rom, booted fine.
Tried flashing Cleanrom 1.1 reborn, went into boot loop.
Restored my stock rom, booted fine again.
Changed recovery to Ext4... didn't make a backup in ext 4.
Tried flashing both Cleanrom GB, Meanrom, sends me to boot loop on both.
What happened? I was able to use cleanrom before where as now it just sends it to boot loop, I can't restore my twrp backup as I am on ext4 now.
What do I do?
http://forum.xda-developers.com/showthread.php?p=26381636#post26381636
j4keg said:
I have S-off Hboot 1.4
Was running Cleanrom 1.1 reborn. & Twrp
Flashed over to CM9 Nightly, worked fine.
Decided I wanted to go back to a sense ics rom, so I flashed the latest ICS meanrom.
Phone went into bootloop
Went back into recovery, flashed superwipe, then did factory reset/wipe cache
Flashed ICS Meanrom again, still boot loop.
Restored TWRP backup I have of stock rom, booted fine.
Tried flashing Cleanrom 1.1 reborn, went into boot loop.
Restored my stock rom, booted fine again.
Changed recovery to Ext4... didn't make a backup in ext 4.
Tried flashing both Cleanrom GB, Meanrom, sends me to boot loop on both.
What happened? I was able to use cleanrom before where as now it just sends it to boot loop, I can't restore my twrp backup as I am on ext4 now.
What do I do?
Click to expand...
Click to collapse
maybe Cleanrom 1.1 isnt good......
j4keg said:
What happened? I was able to use cleanrom before where as now it just sends it to boot loop, I can't restore my twrp backup as I am on ext4 now.
What do I do?
Click to expand...
Click to collapse
Not that this solves your problem, but you could switch back to twrp to use your nandroid backup.
Sent from my PG86100
coal686 said:
Not that this solves your problem, but you could switch back to twrp to use your nandroid backup.
Sent from my PG86100
Click to expand...
Click to collapse
Sorry took so long to follow up.
Later on that day, I realized that my phone wasn't accepting the flash of zipped files. It go through the flashing process in like 5 seconds.
I did switch over to ext4, this was causing the same problem.
Couldn't boot into any rom, so I had to use fastboot and adb to send twrp to the phone. Finally restored my stock rom and was able to flash fine since.
j4keg said:
Sorry took so long to follow up.
Later on that day, I realized that my phone wasn't accepting the flash of zipped files. It go through the flashing process in like 5 seconds.
I did switch over to ext4, this was causing the same problem.
Couldn't boot into any rom, so I had to use fastboot and adb to send twrp to the phone. Finally restored my stock rom and was able to flash fine since.
Click to expand...
Click to collapse
Glad to hear it. Thanks for the followup.
Hi,
CF rooted today and cheked out supernexus but decided to revert back to my backup (official 4.1). I booted into recovery and did a full wipe, and restored the backup. Upon reboot the boot seems to be stuck at the SAMSUNG logo - it still glows but nothing happens. It's been like this for 10 min. or so!
Would a stock rom Odin flash do the trick or am I screwed...
HoundDK said:
Hi,
CF rooted today and cheked out supernexus but decided to revert back to my backup (official 4.1). I booted into recovery and did a full wipe, and restored the backup. Upon reboot the boot seems to be stuck at the SAMSUNG logo - it still glows but nothing happens. It's been like this for 10 min. or so!
Would a stock rom Odin flash do the trick or am I screwed...
Click to expand...
Click to collapse
wipe cache and dalvik in recovery and reboot
mikep99 said:
wipe cache and dalvik in recovery and reboot
Click to expand...
Click to collapse
I wiped data/factory reset, cache and dalvik the first time around. Tried wiping cache and dalvik again at no avail. :crying:
have you got any other ROMs on your SDCARD you could flash through recovery?
HoundDK said:
Hi,
CF rooted today and cheked out supernexus but decided to revert back to my backup (official 4.1). I booted into recovery and did a full wipe, and restored the backup. Upon reboot the boot seems to be stuck at the SAMSUNG logo - it still glows but nothing happens. It's been like this for 10 min. or so!
Would a stock rom Odin flash do the trick or am I screwed...
Click to expand...
Click to collapse
Hi you are stuck on bootloop
you can flash another firmware to sort this out go to sammobile.com and download a firmware there.. but you have to have an account there so if you don't have one yet, you can register there for free also, after you have downloaded the firmware, use PDA in odin to flash..
i hope this helps cheers!
Thanks guys
Luckily I still had the supernexus rom on my internal sdcard, so I was able to flash that with success. Guess my inital ROM backup was corrupted!
I'm sure the sammobile solution will come in handy next time!
well I was flashing MIUI V5 UNIVERSAL - v. 3.7.12 for the 3vo and it got stuck in a bootloop. to try and fix it I tried to restore a backup and that rom played a little of the boot animation but then gets stuck in a bootloop. I also tried to wipe/format everything but, that didn't work. If a logcat would help i would appreciate a link on how to do that without being able to boot. I can boot to 4ext recovery. The cause could be that while flashing I selected the file to flash, I selected a file that didn't finish downloading. Thanks in advance for any help
Also if it matters my original rom was negalite blurom.
cdog1213 said:
well I was flashing MIUI V5 UNIVERSAL - v. 3.7.12 for the 3vo and it got stuck in a bootloop. to try and fix it I tried to restore a backup and that rom played a little of the boot animation but then gets stuck in a bootloop. I also tried to wipe/format everything but, that didn't work. If a logcat would help i would appreciate a link on how to do that without being able to boot. I can boot to 4ext recovery. The cause could be that while flashing I selected the file to flash, I selected a file that didn't finish downloading. Thanks in advance for any help
Also if it matters my original rom was negalite blurom.
Click to expand...
Click to collapse
I ran into your same problem today.
At the time my phone was on latest sprint firmware, ICS coolrom (latest rom and kernel) with hboot 1.58 unlocked s-off.
The steps I did preparing to install MIUI was
1) wipe data/factory reset from 4EXT
2) format all (except sdcard)
3) Install MIUI > chose mirage kernal
4) rebooted
after reboot it was stuck at the logo, at least I thought it was, let it sit for about 5 minutes.
Pulled the battery and tried steps 1-4 again.
Kept getting bootloop at that point. Boot splash -> logo -> reboot.
Next I tried flashing the latest mirage kernel from 4ext.
No luck, same issue.
Tried repeating steps 1-4 again.
No luck stuck in bootloop.
At that point I tried to run recovery from a backup I knew was working.
Wiped all data and format all -> selected recovery from 4ext.
Result: still boot loop.
At that point I tried changing bootloader to 1.58.58 jbear. and wiping/formatting all and trying recovery again from known working cool ics backup.
Result: still bootloop.
Switched back to 1.58 bootloader and tried fresh install of CoolICS rom. (I always wipe all data and format all before any rom change.)
Result: still bootloop.
At this point I was getting frustrated but I had an idea that the MIUI install when selecting mirage kernel may have messed up the partition size for the kernel since the mirage kernel states it must be flashed from the flash gui app first to resize the boot partition.
Next I downloaded pacman rom and attempted that install.
result: could not install due to wrong bootloader.
Next I downgraded bootloader to 1.50.50 jbear.
Wiped everything and retried pacman rom.
Install success, before starting the reboot from recovery, I received a message that the boot image has changed and will make a backup/format/flash the new boot image.
upon reboot I was able to successfully boot into pacman rom.
At that point I tried to wipe all again and install CoolICS rom again.
result: bootloop, but probably because of bootloader version. Did not fully test it as at this point I just wanted a working phone again and wanted to try out MIUI.
Rebooted to recovery and wiped everything again.
Installed MIUI using stock kernel option. This time on reboot I let it sit at the rom logo without touching anything. I think it restarted once on its own.
Result: Success. Phone working normally now. such a headache I am just leaving it as is for now.
Jeffjb said:
I ran into your same problem today.
At the time my phone was on latest sprint firmware, ICS coolrom (latest rom and kernel) with hboot 1.58 unlocked s-off.
The steps I did preparing to install MIUI was
1) wipe data/factory reset from 4EXT
2) format all (except sdcard)
3) Install MIUI > chose mirage kernal
4) rebooted
after reboot it was stuck at the logo, at least I thought it was, let it sit for about 5 minutes.
Pulled the battery and tried steps 1-4 again.
Kept getting bootloop at that point. Boot splash -> logo -> reboot.
Next I tried flashing the latest mirage kernel from 4ext.
No luck, same issue.
Tried repeating steps 1-4 again.
No luck stuck in bootloop.
At that point I tried to run recovery from a backup I knew was working.
Wiped all data and format all -> selected recovery from 4ext.
Result: still boot loop.
At that point I tried changing bootloader to 1.58.58 jbear. and wiping/formatting all and trying recovery again from known working cool ics backup.
Result: still bootloop.
Switched back to 1.58 bootloader and tried fresh install of CoolICS rom. (I always wipe all data and format all before any rom change.)
Result: still bootloop.
At this point I was getting frustrated but I had an idea that the MIUI install when selecting mirage kernel may have messed up the partition size for the kernel since the mirage kernel states it must be flashed from the flash gui app first to resize the boot partition.
Next I downloaded pacman rom and attempted that install.
result: could not install due to wrong bootloader.
Next I downgraded bootloader to 1.50.50 jbear.
Wiped everything and retried pacman rom.
Install success, before starting the reboot from recovery, I received a message that the boot image has changed and will make a backup/format/flash the new boot image.
upon reboot I was able to successfully boot into pacman rom.
At that point I tried to wipe all again and install CoolICS rom again.
result: bootloop, but probably because of bootloader version. Did not fully test it as at this point I just wanted a working phone again and wanted to try out MIUI.
Rebooted to recovery and wiped everything again.
Installed MIUI using stock kernel option. This time on reboot I let it sit at the rom logo without touching anything. I think it restarted once on its own.
Result: Success. Phone working normally now. such a headache I am just leaving it as is for now.
Click to expand...
Click to collapse
well I went to go try and boot P.A.C. and my phone just booted normally. So thanks for the help
Hi my phone is behaving as though it is bricked but its never been flashed until now. the phone was working fine all of a sudden the phone wont boot up in normal mode but will boot in download mode and recovery.
if i do a battery pull and the power on phone it boots straight to recovery. I have tried flashing two different stock roms and also installed siyah kernel and a custom rom but same issue when trying to boot up with a reboot in recovery the screen stays black and the computer recognises it a Sec S5PC210 Test B/D
Phone boots okay in recovery and download just not normal mode
Edit when i put siyah kernel and add second rom it starts booting but then the rom is in bootloops ????
Are u flashing roms through odin? If so try flashing it via cwm recovery. Before u do that try wiping cache, Dalvik cache and then Flash rom.
santhosh502 said:
Are u flashing roms through odin? If so try flashing it via cwm recovery. Before u do that try wiping cache, Dalvik cache and then Flash rom.
Click to expand...
Click to collapse
when flashing through cmw it boots rom bot rebooting the phone it crashes and with odin phone jus boots into recovery
I think you flashed siyah kernel with non stock rom. Siyah works only with stock based ROMs. Were you in Stock rom and kernel when your phone acted strangely?
santhosh502 said:
I think you flashed siyah kernel with non stock rom. Siyah works only with stock based ROMs. Were you in Stock rom and kernel when your phone acted strangely?
Click to expand...
Click to collapse
no the phone was never flashed i went into download mode to flash with odin and ever since its been acitng strange
chwads2k8 said:
no the phone was never flashed i went into download mode to flash with odin and ever since its been acitng strange
Click to expand...
Click to collapse
at moment i jus managed to get wanam lite on it and it boots up and acts fine when on but sometimes phones turns off when screens off i have to do a battery pull and power back on it boots back up. when the phones on everything works fine which is why i dont think its hardware related
still dont understand why it wont boot up properly even with full clean odin flash, i tried using oding and nand erase all but odin just froze on erase and didnt go further so not sure what prob is
I don't know bud. Even when your phone was never flashed it acted strange. Since it works now, u may try wiping data, cache, dalvik cache, system, battery stats and Flash new rom via cwm recovery. And make sure u flash compatible kernel too.
santhosh502 said:
I don't know bud. Even when your phone was never flashed it acted strange. Since it works now, u may try wiping data, cache, dalvik cache, system, battery stats and Flash new rom via cwm recovery. And make sure u flash compatible kernel too.
Click to expand...
Click to collapse
this is soooo wierd . i tried to flash kernel on the rom but went back to square 1. so flashed with odin and flashed siyah kernel and added second rom. phone rebooted ok but stuck in bootloops so this time i decided to do a full wipe and install wanam lite without updating kernel and modem. This has worked and now phone is fully working tested it for 12 hours no random reboots phone boots up normally ok.
So why doesnt it work if its flashed with stock from odin. iv have had many android phones so kinda know what am doin but the issue with this S2 is baffling. not gna flash this now as at moment its working perfect
chwads2k8 said:
this is soooo wierd . i tried to flash kernel on the rom but went back to square 1. so flashed with odin and flashed siyah kernel and added second rom. phone rebooted ok but stuck in bootloops so this time i decided to do a full wipe and install wanam lite without updating kernel and modem. This has worked and now phone is fully working tested it for 12 hours no random reboots phone boots up normally ok.
So why doesnt it work if its flashed with stock from odin. iv have had many android phones so kinda know what am doin but the issue with this S2 is baffling. not gna flash this now as at moment its working perfect
Click to expand...
Click to collapse
LOL this just gets worse now my mobile network disconnects completly and comes back up so wierd and annyoing time to throw the samsung crap away and go for nexus