Guys. I just overclocked using SetCpu. the clocks were at Min clock at 800 MHZ. the max was 1110
So my phone kept rebooting. then i flashed the normal rom
and my phone was at normal state. I flashed Recovery. It went OK and i flashed my preferred custom (thewhisp)
CM10.1 and now my phone is stuck at the bootloader. it takes like forever to boot up.
PLEASE HELP MEH D:
Try reflashing stock rom via odin
Wype data and cache
Sent from my GT-S6500D using xda app-developers app
xfim said:
Try reflashing stock rom via odin
Click to expand...
Click to collapse
in the text i re flashed via odin3 stockrom. I left it for a min. then i flashed recovery reboot as normal.
then flashed via cwm 6.0.3.3 cm10.1 thewhisp trying to boot takes forever
Mini2Fan said:
in the text i re flashed via odin3 stockrom. I left it for a min. then i flashed recovery reboot as normal.
then flashed via cwm 6.0.3.3 cm10.1 thewhisp trying to boot takes forever
Click to expand...
Click to collapse
Sry, i didnt read carefully.
First boot after flashing takes4-10mins so 1min is not enough
xfim said:
Sry, i didnt read carefully.
First boot after flashing takes4-10mins so 1min is not enough
Click to expand...
Click to collapse
but mine from now is like 1 hour 10 mins
boot into recovery then clear cache and data then reboot
EDIT: maybe you had the CPU overclock set to high, if you had that frequently set on boot then maybe that's what was causing the bootloop.
Fixed
pryerlee said:
boot into recovery then clear cache and data then reboot
EDIT: maybe you had the CPU overclock set to high, if you had that frequently set on boot then maybe that's what was causing the bootloop.
Click to expand...
Click to collapse
I lowered my cpu mhz in setcpu in gingerbread. now its normal thx
Related
Hi
I'm having a problem with the i9000
this is how the phone was before:
rooted stock firmware (2.3.3) with Galaxian Kernel (used ODIN to install that)
then I downloaded ROM Manager and used that to flash the latest CWM
next: rebooted to recovery, made a nandroid backup and flashed AOKP milestone 4 and GAPPS
when I rebooted it got into bootloop: boot logo, cyanogenmod logo, black screen with white text and reboot
then I tried to restore the nandroid backup (can still get into CWM)
now it's stuck at Loading kernel...
I can still get into CWM. Can somebody tell me what I did wrong and how I should fix this?
Boot to cwm, FLASH kernel with ICS support like - Semaphore. Reflash ROM, if still in boot loop flash kernel again ;-). It should work ;-)
NoXiScz said:
Boot to cwm, FLASH kernel with ICS support like - Semaphore. Reflash ROM, if still in boot loop flash kernel again ;-). It should work ;-)
Click to expand...
Click to collapse
Did that, but instead of booting the ROM it immediately boots to recovery. Flashed the kernel with ODIN and the ROM with CWM
Flash the kernel via CWM, the semaphore!! not the galaxian, the galaxian is for 2.3.3!
NoXiScz said:
Flash the kernel via CWM, the semaphore!! not the galaxian, the galaxian is for 2.3.3!
Click to expand...
Click to collapse
yes, working with the semaphore now
but it should be flashed with CWM, not ODIN?
Okey, try to flash the ROM again, than again the kernel ;-) Everything via CWM, i think ODIN is bit risky to use, cause of possible USB fail ;-) (sorry for slover responses i don't have verified account )
NoXiScz said:
Okey, try to flash the ROM again, than again the kernel ;-) Everything via CWM, i think ODIN is bit risky to use, cause of possible USB fail ;-) (sorry for slover responses i don't have verified account )
Click to expand...
Click to collapse
it's working
You are welcome buddy, remmeber if you have access to CWM don't use odin ;-)
Oh and BTW i hope, that you did not forget to wipe - data,cache and dalvik cache?
NoXiScz said:
You are welcome buddy, remmeber if you have access to CWM don't use odin ;-)
Oh and BTW i hope, that you did not forget to wipe - data,cache and dalvik cache?
Click to expand...
Click to collapse
No no, I know about that This is not my phone. I have a Nexus S, Asus Slider and X10 Mini Pro, I flashed over 100 ROMs and kernels
it was just the first one from Samsung
ahh right, hell of a job to flash a different phone than yours. (yestarday was flashing my GFs x10i, spend the whole f**** day doing it.... and still she gets like 5 WLODS per day...)
NoXiScz said:
ahh right, hell of a job to flash a different phone than yours. (yestarday was flashing my GFs x10i, spend the whole f**** day doing it.... and still she gets like 5 WLODS per day...)
Click to expand...
Click to collapse
only phones that are easy to flash are Nexus devices and maybe an unlocked HTC
... guess i have some bad luck with this rom or with my cell because everytime i end up here asking for help.
RR11 was released today and i followed the procedure coming from rr10: wipe cache and dalvik, install rr11. sounds easy and wasn't ever a problem before.
the flashing procedure lasted for about 30 minutes then i decided it was stuck (nothing happened, anymore the progress bar was stuck for about 20 minutes between 1/3 and 1/2) modem and kernel were flashed already sucessfully.
cwm was 5.8.1.8, now it reboots into 6.0.1.2, so this update was sucessfull too, i tried to flash again; no progressbar moving only message was "RocketRom"- again. The device is not getting hot but only warm.
md5 is correct.
anything i could do or try before i do something stupid (again, that i'm no aware of), a flash of rr10 was not sucessful either.
Do a fullwipe
Whiskeyjack4855 said:
Do a fullwipe
Click to expand...
Click to collapse
definetly not doing this without more info.
I did it the longer (more secure way) way ollowing the procedure by dr ketan (prerooted gb rom) and flashed rr11 again.
by now i already setting things up again.
Have you tried just put on the power and see?
Sent from my GT-N7000 using xda app-developers app
I think you just had to give it more time to finish .
Sent from my GT-N7000 using xda premium
Have you tried just put on the power and see?
Click to expand...
Click to collapse
after the stuck flash, the system booted into recovery on its own, not even the charging mode worked after poweroff and pulled battery, still booted into recovery.
I think you just had to give it more time to finish .
Click to expand...
Click to collapse
disagree, everytime before the a flash was successfully done within 5-7 minutes, i waited 20 more minutes after i realised that nothing changed.
Flash abyss kernel 4.2 its on eybees op and do full wipe this is a safe kernel to use I'm also on RR v11 and always do full wipe when flashing ROMs and I've never had any problems...
Sent from my Xoom using XDA Premium HD app
i've already solved the problem two days ago as stated above; by flashing the prerooted gb rom by dr. ketan with pc odin 1.85, afterwards the abyss kernel 4.2, advanced -> reboot into recovery full wipe and sucessfully flashed the "desired" rom rr11.
Today I was with Cyanogenmod 10.1 but I decieded to put Stock 2.3.6. I downloaded it from samfirmware and flashed it via ODIN. Then phone rebooted as normal but stuck ot samsung logo, vibrated and then vibrated two fast times. I putted CMW but I can't get into it. I can only get into download mode. The phone is just rebooting.. I reflashed with ODIN but no result. What to do ?
Reflash stock rom then flash cwm and then wipe data cache dalvik format system and reflash stock rom.
Same problem after installing Cyanogenmod 10, i can't enter in recovery i try to reflash many times recovery and firmware but nothing...
I can only enter in download mode, because i get bootloops in samsung logo.
Any idea?
and what do you mean by "can enter recovery?"
TheWhisp said:
and what do you mean by "can enter recovery?"
Click to expand...
Click to collapse
if i press home+power+volumeup+volumedown it doesn't do nothing
sando99 said:
Today I was with Cyanogenmod 10.1 but I decieded to put Stock 2.3.6. I downloaded it from samfirmware and flashed it via ODIN. Then phone rebooted as normal but stuck ot samsung logo, vibrated and then vibrated two fast times. I putted CMW but I can't get into it. I can only get into download mode. The phone is just rebooting.. I reflashed with ODIN but no result. What to do ?
Click to expand...
Click to collapse
follow these :
1. flash stock gb using odin
2. by pressing the button for ur phone which takes u into stock recovery mode, do a factory reset..
3. now reboot and u wont have any boot loops..
the method in 2nd post is not at all suggested since stock GB has nothing to do with insecure/nand recovery...it only makes things unstable afaik..
gudluck..
just hold the buttons a little longer.. I had the same problem like ~2-3 months ago. Make sure you wipe data before re-flashing stock, since Odin is not doing that.
TheWhisp said:
just hold the buttons a little longer.. I had the same problem like ~2-3 months ago. Make sure you wipe data before re-flashing stock, since Odin is not doing that.
Click to expand...
Click to collapse
Nothing happens...
TheWhisp said:
just hold the buttons a little longer.. I had the same problem like ~2-3 months ago. Make sure you wipe data before re-flashing stock, since Odin is not doing that.
Click to expand...
Click to collapse
I hold the buttons for 2-3 minutes, but nothing...
And after flashing CMW 5.0.2.8 or 6.0.2.8 with ODIN nothing happens too...
flash with re-parition (select pit file).. but I have never done that, so... I guess that's the only way to wipe data. I had a similar problem, flashed stock without wiping data and got bootloop. At first I couldn't get into recovery, but later on I somehow could. When exactly you get bootloop? After the GT-S6500 boot logo? What device D/I/T etc. What ROM/recovery you had when you flashed stock? (including dates and versions)
Next time provide more info, we don't have a crystal ball.
I have an idea - can somebody give me stock 2.3.6 but full firmware package (PIT, BOOTLOADER, PDA, PHONE and CSC).
There is no bootloader to flash. Those one-package tars are the only packages. Answer to the above questions. Learn to describe your problem properly.
TheWhisp said:
flash with re-parition (select pit file).. but I have never done that, so... I guess that's the only way to wipe data. I had a similar problem, flashed stock without wiping data and got bootloop. At first I couldn't get into recovery, but later on I somehow could. When exactly you get bootloop? After the GT-S6500 boot logo? What device D/I/T etc. What ROM/recovery you had when you flashed stock? (including dates and versions)
Next time provide more info, we don't have a crystal ball.
Click to expand...
Click to collapse
Sorry xD
Then:
- I get booloop after GT-6500 logo, i have samsung bootanimation, after the phone vibrates two times and get booloops
- My device is a 6500(noD)
- ROM was CM 10 24/03 (With first libcam and otg) and recovery CWM 6.2.0.8
Tryed to flash with .pit file - NOTHING ! DAMN IT !
sando99 said:
Tryed to flash with .pit file - NOTHING ! DAMN IT !
Click to expand...
Click to collapse
Did you activate repartiton checkbox?
Sent from my GT-S6500D using xda app-developers app
Porobu said:
Did you activate repartiton checkbox?
Sent from my GT-S6500D using xda app-developers app
Click to expand...
Click to collapse
Yeah, it checks automatically when I select the .pit file.
Take out battery for some time, put it back in and then try.
Porobu said:
Did you activate repartiton checkbox?
Sent from my GT-S6500D using xda app-developers app
Click to expand...
Click to collapse
Me yes, and it doesn't work because odin fail
now i had this problem 10 min ago
i just went to downloading mod then installed cwm6
then went to recovery mod then wiped data/factory reset and wiped cache partition and wiped dalvick cach and formated emmc and system then reboot my phone and again went to downloading mod and reinstalled ROM.
finished
I am in latest 10.2 nightly. Wanted to go to semaphore 3.3.0s +hughemem libs. I was on sema3.3.0. Flashed sema3.3.0s via cwm --> stuck on boot.
Flashed 3.3.0s.gar via Odin --> starts, but after restart my phone did not Boot.
So i reflashed 3.3.0 via Odin.
What is wrong with it?
Sent from my GT-I9000 using xda app-developers app
Update:
s3icc0 said:
lordlambda said:
s3icc0 said:
lordlambda said:
s3icc0 said:
lordlambda said:
s3icc0 said:
lordlambda said:
s3icc0 said:
lordlambda said:
s3icc0 said:
lordlambda said:
s3icc0 said:
lordlambda said:
Hello,
i am not able to ask in semaphore channel...so i want to ask you.
I falshed latest cm10.2 nightly, semaphore 3.3.0s and last but not least the hugemem libs via CWM.
after this my phone stucked on boot. Maybe you know the problem?
Many thanks in advance!!
Lordlambda
Click to expand...
Click to collapse
hugemem libs are not required, so the problem has nothing to do with hugemem libs (you only won't be able to record 720p video), but the fact you are stuck on boot maybe connected with something else ... from what firmware you were flashing? can you describe me your whole procedure (or just try to simply flash CM several times until it will boot and then reboot and instal semaphore ...)
Click to expand...
Click to collapse
I was on cm 10.2 (5.12.) and on kernel 3.3.0. Then i wanted to test the 3.3.0s kernel. so i downloaded it, go to recovery and flashed itvia cwm (Kernel is on external SD). There are no problems with the "normal" kernal version. Only by flashing the "s" my phone stuck on boot. In addition, i clean dalvik and normal cache.
And ofcause, i want to flash hugemem libs if the "s" version will boot normaly.
Many Thanks!
Click to expand...
Click to collapse
Strange, maybe try to reflash from internal storage (u can use file manager in cwm, or mount the phone to pc over usb from recovery to upload the files) and make sure you have the right files (as flashing CM11 accidentally with recovery from semaphore 3.3.0 will not boot). I recommend to redownload carefully both files, place on internal and reflash ... should be fine then.
Click to expand...
Click to collapse
My phone can boot, i falshed 3.3.0.tar via odin....thats not the problem. but i try to flash 3.3.0.s from internal storage. Maybe i have to mound or cleare something more than dalvik and normal cache? mound the sd?
Many Tanks!
Click to expand...
Click to collapse
no ... leave everything default in recovery ... so maybe try flashing 3.3.0s via odin too??? there should be no problem switching between standard and "s" kernel ... make sure you have the same size and MD5 version as in the semaphore topic ...
Click to expand...
Click to collapse
I checkes md5 summ....if i flash 3.3.0s via Odin phone starts but in Nest restart i stuck in Boot too.(in sumsung s screen, cant geht to recovery) same behavior AS after flashing "s" in cwm.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
So try to flash CM only .. boot with CM ... remove semaphore app, then reboot to cwm, install "s" version, turn off the phone (dont reboot system from cwm), boot to recovery adn reflash "s" version again, reboot system, instal semaphore app ...
Click to expand...
Click to collapse
I will give it a try after visiting my dentist. Thank you!
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
np, until I will have ideas I'd like to help
Click to expand...
Click to collapse
install cm10.2, deinstall semaphore app, insatll 3.3.0.s, turn off phone---no chance to get back in cwm
Click to expand...
Click to collapse
strange ... can you send me the locations were you downloaded the 3.3.0s (link to the file)
Click to expand...
Click to collapse
http://78.46.194.137/kernels/Semaphore_JB_3.3.0s.zip
Click to expand...
Click to collapse
sorry, I can't help you more, better to ask in the thread ... as it must be something else in your phone .... or if you don't mind loosing all your data I would recommend to go through odin from stock samsung, just to be sure (that is what I will do in this situation ... complete reinstalation ...) - it will take no more than 30 minutes to get back to stock and back to CM10.2
Click to expand...
Click to collapse
Solution: Flashing 3.3.0s.tar 3times via Odin. After each Flash i let the phone reboot!
Thanks for the info ...but it is strange ...in my 10.2-time i flashed Sema-Kernel only via Odin and it was never a problem ...
Amazing technology sometimes it works perfect and sometimes it doesn`t ...
Good to hear that it works now ...
lordlambda said:
I am in latest 10.2 nightly. Wanted to go to semaphore 3.3.0s +hughemem libs. I was on sema3.3.0. Flashed sema3.3.0s via cwm --> stuck on boot.
Flashed 3.3.0s.gar via Odin --> starts, but after restart my phone did not Boot.
So i reflashed 3.3.0 via Odin.
What is wrong with it?
Sent from my GT-I9000 using xda app-developers app
Update:
Solution: Flashing 3.3.0s.tar 3times via Odin. After each Flash i let the phone reboot!
Click to expand...
Click to collapse
Hi! When I change to another ROM and I wipe data, my SGS+ boots fine but, when I reboot it, ALWAYS get stuck on kernel logo... What can I do? When it happens I always flash with Odin but I don't want to do that every time I want to change the ROM
Slash137 said:
Hi! When I change to another ROM and I wipe data, my SGS+ boots fine but, when I reboot it, ALWAYS get stuck on kernel logo... What can I do? When it happens I always flash with Odin but I don't want to do that every time I want to change the ROM
Click to expand...
Click to collapse
Could you give a fair idea of how much time you waited for?
Gokulbalram said:
Could you give a fair idea of how much time you waited for?
Click to expand...
Click to collapse
It keeps freezed 5 minutes on the kernel logo and then, automatically it shutdowns. If I try to power it on happens the same.
How often do you keep changing ROMs?
At least it boots upto the kernel right? That's awesome, because the last time, mine wouldn't go beyond the Samsung logo. Just let me know if the next time this happens, it atleast boots to Recovery mode.
Good Luck! Hit Thanks if I'm helpful!
Could be a conflict of init.d files, i always delete my init.d files before flashing another rom.
Gokulbalram said:
How often do you keep changing ROMs?
At least it boots upto the kernel right? That's awesome, because the last time, mine wouldn't go beyond the Samsung logo. Just let me know if the next time this happens, it atleast boots to Recovery mode.
Good Luck! Hit Thanks if I'm helpful!
Click to expand...
Click to collapse
It boots untill "Samsung Galaxy S Plus - cyanogenmod blablabla" but the bootanimation doesn't appear. After 5 minutes it goes off automatically.
pryerlee said:
Could be a conflict of init.d files, i always delete my init.d files before flashing another rom.
Click to expand...
Click to collapse
Then, if now I want to flash MiUI 4.2.2 and I'm in PAC·ROMS 4.4.2, I must wipe data, dalvik and... how can I wipe the Init.d data?
just use "root explorer" and goto /system/etc/init.d and delete the files that are in there before flashing a custom rom.
pryerlee said:
just use "root explorer" and goto /system/etc/init.d and delete the files that are in there before flashing a custom rom.
Click to expand...
Click to collapse
That could be a solution. Although, you never told me if you're able to boot into recovery mode!
yeah sorry forgot to ask you, anyway if you have a custom rom installed then most roms have init.d and a custom recovery already, you could even boot into recovery and also wipe system before flashing custom rom (which will wipe init.d folder) but make sure you have a nandroid backup first just in case.
Gokulbalram said:
That could be a solution. Although, you never told me if you're able to boot into recovery mode!
Click to expand...
Click to collapse
Yes, I'm able. Haha. Always. I can make it boot one time making a factory reset but, after reboot, it doesn't boot again.
Slash137 said:
Yes, I'm able. Haha. Always. I can make it boot one time making a factory reset but, after reboot, it doesn't boot again.
Click to expand...
Click to collapse
If you're able to boot into recovery mode, why do you fret? Just boot into recovery mode and flash the file once again. At times, when you flash a new ROM, it first only flashes the kernel (Don't know why) and then you have the ability to boot to system.
Hit thanks if I helped!
Sent from my GT-I9000 using XDA Premium 4 mobile app
Gokulbalram said:
If you're able to boot into recovery mode, why do you fret? Just boot into recovery mode and flash the file once again. At times, when you flash a new ROM, it first only flashes the kernel (Don't know why) and then you have the ability to boot to system.
Hit thanks if I helped!
Sent from my GT-I9000 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried to flash more than one time and it doesn't boot... f*ck
Ouch. That's bad to hear. Now all you can do is the Odin stuff. Even if a phone won't boot, it'll always go into download mode (I'm guessing you already knew that)
Sent from my Magic Talking Parrot. Which is an i9000
Gokulbalram said:
Ouch. That's bad to hear. Now all you can do is the Odin stuff. Even if a phone won't boot, it'll always go into download mode (I'm guessing you already knew that)
Sent from my Magic Talking Parrot. Which is an i9000
Click to expand...
Click to collapse
So, every time I want to change ROM I must flash first with Odin???? Damn.
Slash137 said:
So, every time I want to change ROM I must flash first with Odin???? Damn.
Click to expand...
Click to collapse
Could you give a list of some ROMs you used?
Gokulbalram said:
Could you give a list of some ROMs you used?
Click to expand...
Click to collapse
CM11, MK4.4.2, PAC4.4.2, RemICS JB v4.2, Beam_Kat4.4.2 ((HALO)) v9.2.0, M.O.W ROM JB 4.2.2 v4.1.
Every time I changed any ROM I always made a factory reset, I wiped cache and dalvik cache.
Slash137 said:
CM11, MK4.4.2, PAC4.4.2, RemICS JB v4.2, Beam_Kat4.4.2 ((HALO)) v9.2.0, M.O.W ROM JB 4.2.2 v4.1.
Every time I changed any ROM I always made a factory reset, I wiped cache and dalvik cache.
Click to expand...
Click to collapse
I'm actually clueless about why this is happening. I'll try and let you know after some research.
Sent from my Magic Talking Parrot. Which is an i9000
Gokulbalram said:
I'm actually clueless about why this is happening. I'll try and let you know after some research.
Sent from my Magic Talking Parrot. Which is an i9000
Click to expand...
Click to collapse
Something new?
Slash137 said:
Something new?
Click to expand...
Click to collapse
(Obvious Question) You do wipe your '/system' partition right?