Related
Hi,
after flashing from TeamRocket ICS 1.3b (which worked very well for me) to MIUI 4 Note v8 to get Livewings Edition ( I used cwm for that, but did all wipes properly) I stuck at the Logo mentioned in the threadtitle.
The problem is now: I cant get out of this.
cwm works fine, but I cant start any Rom. Tried to flash several ones, but I still keep stucking...
Has someone an idea ?
Laus007 said:
Hi,
after flashing from TeamRocket ICS 1.3b (which worked very well for me) to MIUI 4 Note v8 to get Livewings Edition ( I used cwm for that, but did all wipes properly) I stuck at the Logo mentioned in the threadtitle.
The problem is now: I cant get out of this.
cwm works fine, but I cant start any Rom. Tried to flash several ones, but I still keep stucking...
Has someone an idea ?
Click to expand...
Click to collapse
Try downloading abyss kernel 3.9 and flash it in recovery and stay in recovery and reboot recovery. Then flash any rom after wiping all the cache and dalvik and data before final rebooting the system (after flashing the rom)
This should work !!
Is it possible to flash a stock rom with odin to get back to out of the box ?
im also stuck in a bootloop when i tried flashing a stockrom over ics rom
please help
poope said:
Is it possible to flash a stock rom with odin to get back to out of the box ?
im also stuck in a bootloop when i tried flashing a stockrom over ics rom
please help
Click to expand...
Click to collapse
Use the above method i mentioned. It should work.
If nothing works then flash any rootable rom via PC Odin and you will be back to stock and then can root again and flash any other rom of your choice! Check out Dr Ketan's guide in the stickies post in development section of note forum !
got also the same predicament, just stuck in Samsung Galaxy N7000 bootup logo screen after I went to the recovery mode to format/system, format/cache..
I tried to follow the instructions actually on how to upgrade my CheckRom RevoHd v5 to Version 6...
The instructions were to format /system and format /cache... then copy the ROM to a new folder in the internal SD card...
Now the question is.. how can I copy the CheckRom RevoHD version 6.zip if I can't even boot back in recovery mode..
when I booted back.. it just stucks on that bootup logo screen.. ..
Bro how much time did you wait ? I was having the same problem! At least thats what i used to think... But turns out that the first boot takes REALLY long... took me approx 25 mins with rocketrom v22
If nothing works then flash any rootable rom via PC Odin and you will be back to stock and then can root again and flash any other rom of your choice!
Click to expand...
Click to collapse
Thanks but i'm still stuck in bootloop after flashing a stockrom with odin.
letters_to_cleo said:
got also the same predicament, just stuck in Samsung Galaxy N7000 bootup logo screen after I went to the recovery mode to format/system, format/cache..
I tried to follow the instructions actually on how to upgrade my CheckRom RevoHd v5 to Version 6...
The instructions were to format /system and format /cache... then copy the ROM to a new folder in the internal SD card...
Now the question is.. how can I copy the CheckRom RevoHD version 6.zip if I can't even boot back in recovery mode..
when I booted back.. it just stucks on that bootup logo screen.. ..
Click to expand...
Click to collapse
to boot in recovery press and hold volume up home button and power button all at same time in any screen and keep pressing till the time the samsung logo again shows up. Then leave the buttons...it should now boot in recovery.
abhisahara said:
to boot in recovery press and hold volume up home button and power button all at same time in any screen and keep pressing till the time the samsung logo again shows up. Then leave the buttons...it should now boot in recovery.
Click to expand...
Click to collapse
I already did that sir but It would really not open up recovery mode. I can however go to Download mode(with the Volume down) but what good is that anyway, right?
anyway, I have already fix my issue by reflashing it back via PC Odin...
I guess its either the instructions of flashing to the new version of CheckRom RevoHd v.6 is pretty much vague (though I really followed it to a tee) or simply the instructions are not that just well emphasized...
can you direct me to the rom you flashed via odin?
I tried flashing stock rom but i'm still in bootloop
Razor-1911 said:
Bro how much time did you wait ? I was having the same problem! At least thats what i used to think... But turns out that the first boot takes REALLY long... took me approx 25 mins with rocketrom v22
Click to expand...
Click to collapse
Was waiting for 2,5 hours , but I will try the Steps with Abyss kernel.
EDIT:
Can confirm that your method worked @ abhisahara.
Thank you very much !
poope said:
can you direct me to the rom you flashed via odin?
I tried flashing stock rom but i'm still in bootloop
Click to expand...
Click to collapse
Download any of the directly rootable rom from Dr Ketan's guide here- http://forum.xda-developers.com/showthread.php?t=1424997
and flash via PC odin !
Thanks, i'm out of bootloop, but i now i have the null keyboard error
edit solved: forgot to flash csc aswell
see my sig
what you need now to download a GB custom kernel then flash it with the current cwm: then do the following to get it right and rooted ics
1-right after flash the GB kernel go to advance and then reboot recovery.
2-boot into the new recovery flash any custom rom like darkynote.
3-bootup get mobile odin and get the chainfire repack ics LP1.
4-start mobile odin flash the chainfire repack and make sure all the boxes are ticked and wipe data also ticked.
5-after the flash is done it will reboot auto in to cwm flash the miui and all is done.
this log steps I'm telling you to follow so you won't encounter the banry count and yellow triangle.
enjoy
Hi all. I also have the same problem. Initially I'm using LiquidSmooth rom. And then I went to Criskelo rom to try the rom...and didn't like it. And I tried to restore to LiquidSmooth and failed. Now I'm stuck in bootloader and when I try to flash anything on CWM, it hangs. Even if I leave it for awhile on the menu, it'll hang too. What should I do?
Stuck on Samsung Startup Screen
I tried various Stock Roms, but unable to go ahead of Samsung bootcreen. I can get into recovery menu & also download screen, so I assume my Note is not bricked. However I tried to flash old directly rootable GB ROM, ICS ROM, Latest GB ROM(Wipe) but nothing works. While flashing latest GB ROM "N7000XXLC1 (Wipe)" ODIN was stuck in data.fs, so flash was incomplete, In other ROMS flash was complete but I was stuck on Startup screen. I tried flashing "Q1_20110914_16GB.pit" file also but no luck. I also flashed Abyss Note Kernel 3.9 & 4.2 in ICS ROM, but I don't know how to flash this kernel in GB ROM as I'm unable to get into external memory card where I transferred kernel zip file. Please help me save my Note.
Hi there.
I am trying to install 4.1.1 Rom, and I've got this problem, no matters which rom I choose. Here are the steps I follow:
1.- Install Official 2.3.6 firmware with Odin
2.- Install Clockworkmod with Odin
3.- Go into Recovery Mode and follow the install instructions from the ROM (wipe data..., install from sd card)
4.- And here it goes. I got "Samsung Galaxy Logo - ROM Logo - Installation init" again and again. The installation shows log messages that I don't have enough time to read (something about E unknown, or can't mount. I've tried flashing with dbdata.rfs.tar, but with no luck)
Any help? Thanks in advance.
Reflash you have to flash twice and also I recommend flashing on top is cm not GB as it seems to stop imei issues
Sent from my Awesome I9000 running Slim Bean
Keep pressed the Recovery Combo until you see the Samsung Galaxy S first screen. It will force to enter Recovery mode.
Then wipe again and reflash
Instead of directly installing clockwork mod, install the cf-root kernel instead, which gives you root and CWM. That's what I normally do anyway.
He/ She doesn't need too there flashing straight to another ROM don't need root
Sent from my Awesome I9000 running Slim Bean
Thank you all for the replies.
I'll try them tonight and I'll let you know if it works out
It does that to me everytime I want to upgrade frome Gb to ICS or ICS to JB
I pull out the battery to stop the bootloop, then put it back in and get in recovery mode with three-buttons combo, then flash again the rom, it shouldnt bootloop again.
I started with last solution (remove battery and flash rom again) and it has worked out! The thing is that after removing the battery and flashing it again, "another" recovery mod is loaded and then it all goes perfect. So, thanks all for the help!
Yes as it changes the partition table and needs a different recovery to handle it properly
Sent from my Awesome I9000 running Slim Bean
Just got my Galaxy S back from my Mum today (After I bricked it and sent for repair) she got a note2 omg... Decided to flash a custom rom..
Here goes..
First I followed this guide completelyhttp://http://wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Full_Update_Guide. After I flash the CM 10, my recovery was upgraded to v6.0.1.5 after reboot. But I cannot get pass the recovery. I will have the cm boot animation, then back to recovery again. Tried reflashing the rom, doesnt say any errors but still gets stuck at recovery.
Then I went thru the method at the wiki.cyanogenmod again and successfully flashed cwm recovery 2.5 again. Tried flashing the CM10 rom again but this time round, It shows a long error message ending with "status 7"
I am still able to go into download mode.
Was on stock unrooted 2.3.3 DXJV9.
I made the super no.1 noob mistake of not making a backup........... But, why is rooting and flashing of this phone so hard.....
Pls, any help is greatly appreciated.
Btw, I have manage to flash the stock image via odin but is still stuck in a boot loop.. after Odin completed and reboot, I am back into the stock recovery with the below error messages.
It will work
scpion said:
Btw, I have manage to flash the stock image via odin but is still stuck in a boot loop.. after Odin completed and reboot, I am back into the stock recovery with the below error messages.
Click to expand...
Click to collapse
When u see red error message in stock recovery........u just wipe cache and reboot.......it will work.....
i have wiped everything many times over. but I am still stuck in the bootloop. the red error messages looked serious though.
try this
scpion said:
i have wiped everything many times over. but I am still stuck in the bootloop. the red error messages looked serious though.
Click to expand...
Click to collapse
U just use GB jw4(your region) ROM (don't use single file like PDA).........you use files separately like this [PDA,phone,CSC,pit(512 or 513)]...............use Odin 1.85 for flashing files......,when u complete the flashing it automatically reboot to fulfill the flashing...........then also it gives red error means........ clear only wipe cache and don't clear wipe all data...........reboot your system..... I think this will work for u...........:fingers-crossed:
Thanks. Have it solved. Flashed with another rom with seperate files. I was using the the all in one previously. Got it to run CM10 nightly though till now still not too sure how... But, I m real happy now. It works great so far and I couldnt understand why Sammy refuse to roll out official ones even for 4.0..
Still trying to figure out how to root, flash SGS though.. I have done so for many other device but by far,... this phone is the most complicating....
Aj rocker root
By processor only we not getting stock ICS rom but we getting custom ROM by hacking processor.............
For rooting the ROM u want to be in stock GB ROM like 2.3.5 or 2.3.6 and then u want to download this file(http://download.chainfire.eu/132/CF-Root/SGS/CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS.zip)............. after download u want to open Odin 1.85 and select PDA then choose the downloaded file...........select start to flash the file.........reboot and enjoy the root bosssss......if u like this press thanks:fingers-crossed:
Just to make sure..
What I did was,
Flashed Android 2.3.5 XXJVS Firmware and rooted with CF-Root-XX_OXA_JVS-v4.1-CWM3RFS.zip
Flashed the speedmod kernel via heimdall
Wiped data/cache. Flashed Latest CM10 nightly
( at this point, there was a error "status 0" installation aborted. When I reboot, the CM10 boot animation flashed twice and it brought me straight to CWM 6.0.1.5. Is this normal behaviour?? Then, not too sure what to do, I wipe data/cache and flashed CM10 and gapps again. this time round, installation successful and after reboot it boot into CM10. )
Is the above normal behaviour?
Next time I wish to change rom, from where I now( CM10) just need to wipe Data/cache and flashed the other rom?
Try to see if you can flash another custom Rom, if that works then it could be that your files are corrupted..
Have you stated your problem over at CM forums..
# Sent from my blazing slimbean SGS i9000 using Tapatalk 2 #
scpion said:
Just to make sure..
What I did was,
Flashed Android 2.3.5 XXJVS Firmware and rooted with CF-Root-XX_OXA_JVS-v4.1-CWM3RFS.zip
Flashed the speedmod kernel via heimdall
Wiped data/cache. Flashed Latest CM10 nightly
( at this point, there was a error "status 0" installation aborted. When I reboot, the CM10 boot animation flashed twice and it brought me straight to CWM 6.0.1.5. Is this normal behaviour?? Then, not too sure what to do, I wipe data/cache and flashed CM10 and gapps again. this time round, installation successful and after reboot it boot into CM10. )
Is the above normal behaviour?
Next time I wish to change rom, from where I now( CM10) just need to wipe Data/cache and flashed the other rom?
Click to expand...
Click to collapse
OK fine first u want to know something boss......... every firmware having different layout........ correct procedure of flashing is u want to go step by step for enjoy the full features of the ROM ....... u r in GB ROM means then next u want to go ICS ROM........If u r in ICS ROM means then next u want to go jellybean rom and this the correct procedure to use new ROM without the problems...........:good:
scpion said:
Just to make sure..
What I did was,
Flashed Android 2.3.5 XXJVS Firmware and rooted with CF-Root-XX_OXA_JVS-v4.1-CWM3RFS.zip
Flashed the speedmod kernel via heimdall
Wiped data/cache. Flashed Latest CM10 nightly
( at this point, there was a error "status 0" installation aborted. When I reboot, the CM10 boot animation flashed twice and it brought me straight to CWM 6.0.1.5. Is this normal behaviour?? Then, not too sure what to do, I wipe data/cache and flashed CM10 and gapps again. this time round, installation successful and after reboot it boot into CM10. )
Is the above normal behaviour?
Next time I wish to change rom, from where I now( CM10) just need to wipe Data/cache and flashed the other rom?
Click to expand...
Click to collapse
OK fine first u want to know something boss......... every firmware having different layout........ correct procedure of flashing is u want to go step by step for enjoy the full features of the ROM ....... u r in GB ROM means then next u want to go ICS ROM........If u r in ICS ROM means then next u want to go jellybean rom and this the correct procedure to use new ROM without the problems...........:good:
Most times from GB to JB u have 2 flash custom 2, 3 times. So its normal when flashing custom the first time it takes u to bootanimation and hangs (take out battery and go to recovery with 3 button combo and flash again till it says install is completed) or directly into recovery.
If u wanna flash other jb rom just full wipe and flash new custom. Make sure u make a nandroid backup so u can go back easily
I wanted to flash custom rom on my galaxy S. I flashed clean rom, then kernel with CWM, but there is a problem. Everytime I try to flash rom it ends with bootloop. I tried cm7, cm10, rootbox, miui 2.4. Every time is the same. It starts installing (only few secodns), then screen becames brighter, then restart and bootloop. I tried different kernels, roms but still same result.
ps. sorry for my english
Hi, here is a great guide to fix bootloops:
http://forum.xda-developers.com/showthread.php?t=1660596
Usually, doing factory reset, wipe cache and wipe dalvik cache before and after intalling the ROM should fix the issue though.
I'm doing all necessary wipes, I can recover from bootloop easly but I want flash custom rom and I can't. Istalling zip lasts few second, not few minutes, there is a problem.
Sorry if this is too basic, but are you using the right ROM for your phone?
of course...
I don't know if I'll be able to help you, but can you please list the exact model of your phone just in case? You can see the different variants here:
http://en.wikipedia.org/wiki/Samsung_Galaxy_S#Variants
It is just GT-I9000. Now I managed to flash CM7.2 but if I want install CM9 or CM10 im getting bootloop and can't enter recovery mode ;o
Sorry, I can't really give you an answer with that information. If you are following the steps in each ROMs thread, you should have no problems patching as far as I know (someone more knowledgeable than me may say otherwise).
Maybe posting the exact steps you are following would help me or others to find out what the issue is.
I'm following right steps. It's not my first phone. I know how it should be but it isn't. Here are my steps:
Flash stock ROM w/ODIN v1.85 - OK
Flash CF-Root w/ODIN v1.85
Wipe Data/Wipe Cache
Phone now rooted OK
Boot to CWM Recovery
Install zip from sdcard
Select update on SDCard (cm-7.1.0 from CM site)
Flash completes in just a few seconds
Phone reboots automatically
Now stuck in boot loop
Remove battery
Go to CWM again and reflash CM7.1 zip
Now i have CM7
Reboot to recovery, facotry reset, wipe cache, wipe dalvik
Flash CM9/CM10, finishes in few sec, reboots, then black screen, can't go to recovery mode ;(((
Flashing stock with odin again...and every time is the same, sometimes when I choose CM10 i see info: "Incompatible Partition Layout" so it may be the reason (something with partition, idk)
My phone has never rebooted like that, so I'm not sure what the problem is. I do know I use ODIN v3.07. I also have CWM 6.0.2.7
Best of luck finding a solution, sorry I could no be of more help.
I think CWM6 would help but I can't find this version for cm7
IGNORE ALL LINKS BELOW, they are for the wrong phone
I don't think it matters what CM you have on your phone, you should be able to upgrade CWM from recovery: Maybe not in i9000...
http://forum.xda-developers.com/showthread.php?t=1843825
Doesn't work in i9000 as far as I can tell: You can also try installing TWRP, which I like better than CWM and have in a different device:
http://forum.xda-developers.com/showthread.php?t=1694617
Finally, and don't take me on this because is just a guess, maybe your bootloader is not working properly? I don't really remember how to do this myself:
You are showing me links to CMW and TWRP for i9001, I have i9000...
You are right, please ignore those links... I do know I patched CWM 6.0.2.7 through ODIN on my phone, so maybe that's the only way. In any case, I'll let you look for the actual links.
Hi,
So basically I ended up with a boot loop somehow..long story. I cannot access my recovery..only my download mode.
I've already tried the following :
- Flash stock ROMs(All - JB, ICS, GB using Odin)
After flashing, All stocks ROM's go in a boot loop of the intro animation and glowing Samsung repeating again and again.
- Tried a FULL Flash - used a PIT file with a md5 of a stock ROM. Re-partition basically. Still boot loops.
Anyone has any clue what's going on here? Tried everything and thought it through and can't figure why it won't boot even after a re-partition happened successfully.
Would appreciate any help,
Cheers
Why can't you access recovery? What happens when you press the 3 button combo? Try with and without the USB cable plugged in. You could also try flashing philz kernel from Odin and then try if you have access to recovery. Then a data wipe should get you booted.
Flash some kernel with cwm, go to cwm and wipe data. After that just flash any ROM You want and it should work.
Sent from note, a phone like never before
its will be fixed with flashing the right rom..
im facing that kind of trouble too last night.. but succesfully fixed it with flashing with jellybean firmware..