Since about a week I'm having the following problems:
It is extremely difficult to get my phone running ICS. I tried like 10 different ROMs, the only one currently working is Dark Knight. In between I managed to run CM9 Nighlty (2 days) and Infinitum 2.2 (3 days)
Why is it so difficult? Well - I believe, I'm doing all the correct steps: Flashing JVZ with Odin, rebooting, flashing CF Root, rebooting. Enter CWM, wipe data, cache, dalvik, format system -> Install any ICS rom
Currently, CM9 doens't work at all, I get boot loops after the initial reboot and can't enter recovery
Well, when I finally manage to install any rom (method: install Dark Knight - 5.5 atm - install any rom afterwards - my phone boots up correctly and is perfectly usable
But: Whenever I reboot, I keep getting boot loops with no chance of entering recovery. None of the usual methods work.
Stupid thing: I don't need to reboot. But every other day the phone tends to reboot itself (at least that is what I experienced and sorta guess)
Result: I take it out of my pocket or look at it on my desk and see boot loops after 2 or 3 days
What can I do, why is that? I don't want to run Gingerbread
I am not a noob - I have been running any rom before for one and a half years without problems and flashed mostly without any problems
Believe me - I have tried everything for several days. Flashing the recovery fix with Odin doens't help either. Afterwards I am a able to boot intro recovery but can't install any rom due to build.prop errors. However, I can flash a kernel... Result: boot loop. Solution: Start over with Gingerbread and Odin
The more I think about it, the more I belive there could be an underlying hardware problem. Maybe something with the internal NAND?
I am greatful for any help or new ideas which I haven't tried so far... Thanks a lot in advance!
I know it's a long shot, but maybe you have issues with datadata folder? Use root explorer and see how much free space you have there...
Maybe try this:
After Odin, When in CWM, flash first a new kernel (try devil.072). Make sure to mount folders with CWM before. After flushing, go to advanced and reboot recovery. Now you have a new version of CWM (which supports screen tuch...). Now, from mounts and storage, format everything. Now flush the rom you want - in this case, I recommend Slim 3.4. Don't install anything yet - just let it run after flushing. Just login to your google account.
See if it works.. hope it helps
Thanks a lot! Unfortunately, it didn't work.
I tried your method which didn't even end up in a bootloop but in recovery after every flash/try to reboot.
/edit: Speaking of reboots - I tried to install CM9 afterwards/instead -> boot loop
Hmmm u have a interesting problem. Do u wipe everything and have u tried starting from a different stock gb
If you like my posts hit thanks
Rom: Dark knight 4
Kernel: Devil Kernel
Keep it ANDROID!!!!!!!!
Yes, I wipe everything and tried JVZ and JVU as a starting point. Are there any other recommendations?
which firmware are you odining? maybe bad download?
Bara2 said:
Thanks a lot! Unfortunately, it didn't work.
I tried your method which didn't even end up in a bootloop but in recovery after every flash/try to reboot.
/edit: Speaking of reboots - I tried to install CM9 afterwards/instead -> boot loop
Click to expand...
Click to collapse
Just try it again but do NOT select reboot recovery. It is a common bug that you won't be able to leave recovery again. Just reboot the phone and be sure to quickly press 3 button combo again to get into recovery again. You should then be able to format / reflash and so on. Just make sure you never select reboot recovery when you just came the long way from odin. In doubt just do as I stated: normal reboot and press 3 button combo quickly.
Good luck!
shaharofir said:
which firmware are you odining? maybe bad download?
Click to expand...
Click to collapse
I agree many try a firmware from stock firmware from xda
If you like my posts hit thanks
Rom: Dark knight 4
Kernel: Devil Kernel
Keep it ANDROID!!!!!!!!
swent said:
Just try it again but do NOT select reboot recovery. It is a common bug that you won't be able to leave recovery again. Just reboot the phone and be sure to quickly press 3 button combo again to get into recovery again. You should then be able to format / reflash and so on. Just make sure you never select reboot recovery when you just came the long way from odin. In doubt just do as I stated: normal reboot and press 3 button combo quickly.
Good luck!
Click to expand...
Click to collapse
Ok, That shall be my next try Btw: Another strange effect: I flashed Dark Knight 5.5, did nothing but click through the setup assistant rebooted - and voilà - boot loop.
Will report back in a few minutes Thanks a lot, guys!
/Edit: Well - a litte success... I was able to boot into the system. First thing I did was change lcd density and rebooted - everything was fine. As I didn't have wifi or data connection I wanted to flash another kernel (devil) and hit reboot recovery from the power menu.
--> Boot loop again.
To the other guys: I tried JVU and JVZ with different downloads and two different laptops. Which starting base should I try next?
/Edit2: I'm going to stay on Gingerbread for the day. I need my phone and intend to enjoy the fantastic weather for the rest of the day... Will be back this evening. I am glad for further feedback and ideas
Bara2 said:
Ok, That shall be my next try Btw: Another strange effect: I flashed Dark Knight 5.5, did nothing but click through the setup assistant rebooted - and voilà - boot loop.
Will report back in a few minutes Thanks a lot, guys!
/Edit: Well - a litte success... I was able to boot into the system. First thing I did was change lcd density and rebooted - everything was fine. As I didn't have wifi or data connection I wanted to flash another kernel (devil) and hit reboot recovery from the power menu.
--> Boot loop again.
To the other guys: I tried JVU and JVZ with different downloads and two different laptops. Which starting base should I try next?
Click to expand...
Click to collapse
Umm well I use jvu and have no problems. This might sound stupid but when I had a similar prob (I flashed a kernel on dark knight 4 and got into a bootloop and couldn't enter recovery) I did a factory restset after backing up my SD card data and flashing jvu, then I reflashed jvu. Rooted, wiped rebooted recovery, wiped again, rebooted recovery again, then I flashed dk 3 then dk 4 without a wipe, the restored my apps and copyed my SD data back - I hadn't been able to flash a rom since the bootloop I got it working with dk 3 but then I got no boot animation and I just stopped there, the above process worked for me I know u on dk 5.5 but try dk 3 you should find the link in the dk thread around April 12-16 this year.
If you like my posts hit thanks
Rom: Dark knight 4
Kernel: Devil Kernel
Keep it ANDROID!!!!!!!!
You may flash the new kernel right away after flashing the desired rom. Maybe that would stabilize everything... can't make any more sense of it right now, sorry :/ Maybe you could try to use the ultimate kernel cleaning script AFTER flashing the rom and BEFORE flashing the new kernel (with no reboot in between).
Script is somewhere out there, I'm gonna search it right now...
/EDIT: Wasn't really hard to find after all, there you go: Ultimate Kernel Cleaning Script
try this firmware for odin:
https://www.sugarsync.com/pf/D6246658_3937073_82911
Related
Please Help I installed a custum ROM and now I am stuck in a loop a skull comes up and droid and it continues till the battery is dies. I have tried to factory reset and nothing the only way to turn it off is to remove the battery can someone please Help
If the ROM is what's causing the problem, doing a factory reset won't change anything; it'll stil keep the same ROM in place. What you might want to do is download a more popular ROM, like a CM7 nightly, put it on your microSD card (using another phone or a microSD adapter, of course) and boot into recovery and flash that.
If that doesn't work, I dunno then. I got a bootloop the other day after using ROM Manager to flash a new kernel. Turns out it was the kernel because after a factory reset, it booted up fine. So I just chose another kernel and it's all good now.
You just might have a screwy ROM. Try reflashing it if you can. What was the custom ROM, btw?
Yeah I'd agree with the above; install another ROM and make sure to wipe cache and dalvik and if it still doesn't work wipe data as well. Note that wiping data will wipe pretty-much everything on your phones memory (SMS messages, contacts, accounts etc)
when it is cm7 than you should take an other kernel
Please, if you are experiencing random reboots (that involve the M logo) or prolonged screen freezes, you should revert to an older beta kernel that is free of the DSI errors. To do so, replace the boot.img in the update-cm-7...zip package with this one (from 0.04 version): http://code.google.com/p/cyanogenmod4milestone/downloads/detail?name=bootimg0.04.zip
Click to expand...
Click to collapse
Stole that from another Thread:
_Flash with any rom you have
_Milestone will auto reboot after flash done and loop
_Don't worry about that, remove battery in 5s and re-plugin
_Turn on your milestone: hold X and POWER to access Recovery. Select Wipe and reboot
Do you have a Droid or a Milestone? If you have a Milestone, which country is the device from?
I had a boot loop issue too on my UK Milestone when I tried to install CM6.1.2, version 28.01.2011 0.07-11.01.28. (http://android.doshaska.net/cm6)
This is what I did to fix the problem...
- Flashed UK 2.1 SBF file
- Flashed Vulnerability Recovery
- Rooted the phone
- Installed and booted into OpenRecovery
- Installed 15.01.2011 0.06-11.01.15 version (phone booted fine)
- Rebooted into OpenRecovery > Wiped Dalvik Cache
- Applied 28.01.2011 0.07-11.01.28 version
One more thing, you may need to update and/or change your baseband files.
I hope this helps.
Thx for the help guys I,m back up an running. Greatly appreciated
Sent from my Droid using XDA App
My SGS was confiscated at school about 2 months ago by the school adminstration because bringing phones to schools wasn't allowed. I had removed the battery and SIM when it was confiscated. By then it was running on Onecosmic's ICS 4.0.3 RC3.1 ROM. It was working perfectly with a custom boot animation. Today I got my SGS back and it wont fully boot. When I turn it on I can see the Galaxy S GT-I9000 text plus the 'WITH OUR POWERS COMBINED WE ARE...PLATYPUS KERNEL' logo but it stays black after this. The menu and back button light up on touch but there is no response or activity on the screen. I have tried almost everything from
wiping every data to re-rooting it, blah...blah. I installed 2.3.5 and it works, 2.3.6 ValuePack works too and even CM7 works fine. But it won't accept ICS. Any idea why, please help?
PS: I can enter both recovery mode and download mode.
Fully wipe, install stock firmwares in Odin and did all step to install custom ICS rom.
yup did all that. Flashed stock 2.3.5 first, then flashed 2.3.6 valuepack, then rooted it, after that installed cm7. Everything is perfect upto this. After that wiped all data plus cache, and tried installing ics onecosmics 4.0.3 rc3.1, after reboot phone stays blank after the logos. The menu and back buttons light up on touch, but no vibration no action and no response.
I did the same with success but from 2.3.6 directly and with that :
1. Boot into Clockwork Mod Recovery Mode using volume buttons.
2. (optional) Backup your current ROM.
3. Select "install zip from sdcard".
4. Select "choose zip from sdcard".
5. Select the .zip that you downloaded and confirm it.
*(optional) Flash newer kernel if you want to.
6. Reboot the phone.
7. Wait for phone to boot (this may take up to ten minutes)
tried it from 2.3.6 just now, still no luck. Phone just stays blank...
Why not move to rc4.2. Also have you tried flashing twice. One after the other. Not sure why but this sometimes helps.
Also in recovery advanced menu have you cleared dalvik cache, cleared init'd and ns tools settings?
Sent from my GT-P7500 using xda premium
scubadude said:
Why not move to rc4.2. Also have you tried flashing twice. One after the other. Not sure why but this sometimes helps.
Also in recovery advanced menu have you cleared dalvik cache, cleared init'd and ns tools settings?
Sent from my GT-P7500 using xda premium
Click to expand...
Click to collapse
Read the bold. I've seen this in a handful of tutorials on how to flash to ICS. After you've flashed to ICS and you're stuck in a bootloop, simply go into CWM (Recovery) and reflash it. This should fix your problem.
Good luck!
thanks ya all, finally managed it n it works now. I just installed another ics rom (i dont exactly know what it is, its got a boot screen of android rocketing with the galaxy logo) and installed onecosmic's rc3.1 again n it works now.
tamrat_a said:
thanks ya all, finally managed it n it works now. I just installed another ics rom (i dont exactly know what it is, its got a boot screen of android rocketing with the galaxy logo) and installed onecosmic's rc3.1 again n it works now.
Click to expand...
Click to collapse
When you get a bootloop flashing to ICS, simply flash again—as in, flash twice in a row. This is effectively what you did by trying another ROM, as they both have the same base. Keep that in mind for the future.
Have fun!
Hi all. Yes I am a Noob first ever post in fact. I am however good at following directions and reading first. So far found nothing to address my issue.
Intro: First time flashing a Custom ROM although I did previously successfully install Cf-Root and Stock ICS from Sam Mobile using excellent instructions found here.
Background: 1) Decided to move from Rooted Stock ICS to new Aliance ICS -- spent all weekend reading up before developing courage to attempt. 2) Today Successfully downgraded to Gingerbread (Flashing the Darky Resurrection rom and following instructions exactly). 3) Uninstalled DarkyOTA and Cleared app data as specified in instruction 4) Installed Alliance OTA and ROM Config as specified 3) Successfully flashed a XXLPY repack via ODIN per http://forum.xda-developers.com/showpost.php?p=27199210&postcount=4instructions 5) Copied the Alliance ICS Rom Zip to external SD 6) Went into CWM as instructed and flashed file.
Result: received notices -- Preparing for Installation ... Cleaning the phone etc -- through to "Installing Extra Apps" ----- Have been staring at this part for 45 minutes now as no progress has been made.
Current situation: Staring dumbly at phone with fading hopes that the process will complete. Wondering how long my Mugen battery will hold out while I wait. Utterly clueless what to do next. Regretting my courage in attempting this.
Can someone help please?
Where did u come up with DARKY ICS it should be Alliance ICS, just recheck because DARKY ICS is for S2 did u flash S2 rom on Note......
bhasg1007 said:
Where did u come up with DARKY ICS it should be Alliance ICS, just recheck because DARKY ICS is for S2 did u flash S2 rom on Note......
Click to expand...
Click to collapse
You make a very good point --- but i can confirm that the zip was the following:\AllianceROM_N7000_ICS-v1.zip
Still hung (80 minutes now) on "Installing extra apps"
mutineer33 said:
You make a very good point --- but i can confirm that the zip was the following:\AllianceROM_N7000_ICS-v1.zip
Still hung (80 minutes now) on "Installing extra apps"
Click to expand...
Click to collapse
Download the Alliance rom again and reflash it, you might have a corrupted rom.
gee2012 said:
Download the Alliance rom again and reflash it, you might have a corrupted rom.
Click to expand...
Click to collapse
Thank you ---- I will try --- but first how do I get out of this hung install --- no button works --- if I just power down or pull the battery out before this flash has finished , will my phone still be usable?
mutineer33 said:
Thank you ---- I will try --- but first how do I get out of this hung install --- no button works --- if I just power down or pull the battery out before this flash has finished , will my phone still be usable?
Click to expand...
Click to collapse
Haven`t you made a cwm recovery (backup) before you went to flash the rom.
If so pull the battery, wait 30 seconds, insert the battery and go in recoverymode and restore your backup. If there is no backup go in downloadmode and reflash a stock rom and reroot this rom and start over.
gee2012 said:
Haven`t you made a cwm recovery (backup) before you went to flash the rom.
If so pull the battery, wait 30 seconds, insert the battery and go in downloadmode and restore your backup. If there is no backup go in downloadmode and reflash a stock rom and reroot this rom and start over.
Click to expand...
Click to collapse
OK will try --- Thank you and "Thanks" added
gee2012 said:
Haven`t you made a cwm recovery (backup) before you went to flash the rom.
If so pull the battery, wait 30 seconds, insert the battery and go in recoverymode and restore your backup. If there is no backup go in downloadmode and reflash a stock rom and reroot this rom and start over.
Click to expand...
Click to collapse
Ok -- and thanks again. The Good News is after pulling and reinserting the battery the phone booted up and into Alliance (it looks fantastic by the way) and appears to be working. A bit scary as the Flash process itself never actually completed. Since I am as of yet unfamiliar with the ROM I have no idea if I am missing anything (mostly just the wall paper and google search, play store, and Nova settings are displayed --- but app drawer has 49 apps and 36 widgets). So now I would be very interested in opinions as to ---
1) Anyway to validate whether EVERYTHING that was supposed to have flashed on this Rom is in fact there? Or can I assume that since the phone has booted up and is working in terms of voice and data connections that I have been lucky and all has gone well after the initial panic?
2) Related to the above should I reflash this ROM over itself to see if it fully completes this time?
Thank you again.
Congrats on getting past the hanging issue - it is always a nervous time when that happens. I would recommend you reboot the phone and check that it starts up again. If all is good, run with current system for a few days. If you start to notice anything wacky then would be the time to reflash ROM.
I'm a firm believer in "If it ain't broke don't fix it" Hopefully your Note will just work now.
Just before reflashing just confirm if you are fully rooted, install root explorer and check if u can paste in system if yes then for safety purposes just flash abyss 4.2 redpill kernel boot into the kernels cwm and perform wipe and reinstall the rom
TempusFudgeIt said:
Congrats on getting past the hanging issue - it is always a nervous time when that happens. I would recommend you reboot the phone and check that it starts up again. If all is good, run with current system for a few days. If you start to notice anything wacky then would be the time to reflash ROM.
I'm a firm believer in "If it ain't broke don't fix it" Hopefully your Note will just work now.
Click to expand...
Click to collapse
Thank you for the feedback. As it stands I Re-flashed again ---- and the flash hung again (this time @ "Cleaning phone". Started over a 3rd time and it went through perfectly.
No idea why the first two attempts failed -- but it looks like I am good to go.
bhasg1007 said:
Just before reflashing just confirm if you are fully rooted, install root explorer and check if u can paste in system if yes then for safety purposes just flash abyss 4.2 redpill kernel boot into the kernels cwm and perform wipe and reinstall the rom
Click to expand...
Click to collapse
Thank you for the suggestion. Per my post above, I think I am sorted out now.
I've got the same problem, are you on speedmod kernel???
Try to mount system and data from the mount menu.
I hope this can help you
I have the same problem... First I installed successfully the ROM but then i messed up something and my phone started to restart and then I went to recovery, Wiped Cache, Dalvik and then Wiped data, then i mount Data, started installing and it went to Installing extra apps and just froze... I hold the power button and it booted alliance rom only with nova launcher... No other launchers... I want to do this again but im afraid if it is going to get even worse Should I try again of doing this? I'm sure that the rom wasn't corrupted because the first time it worked... Shall i try flashing HydraCore and then flash alliance rom again?
EDIT: I've just flashed it again and it worked.. I have no idea what exactly happend, but it doesn't matter - it worked
My N7000 just shows a black screen indefinitely after the 'Samsung Galaxy Note GT-N7000' logo.
The soft keys light up when I press them, so it is on during this time.
It is rooted and does this when I flash any of the official CM10 JB nightlies after October 3. (October 1 nightly still works)
Apart from this there is no indication there is anything wrong with my phone.
It is overclocked and undervolted but safely so (it only crashed when I was testing the voltages 2 months ago) (it usually runs at 1.6 GHz and 1250mV)
The only other things i flash are Hydracore 5.4 and SuperSU 0.96, and I've tried booting without these to no avail.
What do i do??????
Thanks in advance!
flash stock ROM and start again, Stick to stock voltages and stock CM kernel and see if it works then.
If not, we can look a bit deeper in to the cause
Edit: forgot to mention that I was already running PA 2.16 with Hydra 5.4oC.
I had the same problem last night, after flashing PA 2.17 it didn't boot up anymore.
It's stopped after the N7000 logo.
I flashed a stock rooted GB ROM with ODIN PC (Dr Ketan guide) and was able to boot once.
When I went back to the CWM recovery it got stuck in the recovery itself and I had to start all over again but with the SGN_XX_OXA_KJ1_FACTORYFS rom there was no improvement, it always booted back in the recovery and there was no way to leave it, factory reset didn't solve the problem either.
Then I flashed N7000XXLA6_N7000XEULA1_XEU with separate CSC and modem and since that moment it came back alive and I restored my last back up.
It took me damn 2 hours to get it back running again.
Note to myself, never flash a rom again before going to sleep.
azzledazzle you were right! Its a kernel problem.
After flashing SGN_XX_OXA_KJ1_FACTORYFS, I installed cm-10-20121005-NIGHTLY-n7000.zip, and it worked!
The thing is any non-stock kernels still cause the original problem.
Stock kernels are fine with me, but do you know how it might be fixed?
Got no clue if it's a kernel problem or how it can ben fixed.
I'm running PA 2.16 + Hydra 5.4 and all is fine again.
Will keep it that way for a while.
Edit: nevermind.
Glad you got it to work
guitarplayerone said:
Edit: nevermind.
Glad you got it to work
Click to expand...
Click to collapse
Ive done the same thing to mine, or shall i say similar.....i was rooting mine to cm10 jelly bean and it booted up fine, i tried to restore it to its former rom and my battery was low and the phone just died on me:silly:
now the logo comes on and after that nothing, blank screen...
it go's in to download mode but not recovery mode....
by the way....am a complete noob:crying:
anyone HELP!!!
aky47 I suggest:
flash SGN_XX_OXA_KJ1_FACTORYFS which is here: d-h.st/HJM using this method: forum.xda-developers.com/showpost.php?p=20963718&postcount=2
put the desired ROM on your phone
enter recovery (hold home+vol up+power until 'Samsung Galaxy Note GT-N7000')
select 'install zip from sdcard'
select 'choose zip from internal SD' (can't quite remember the exact text - its the last option though)
choose the ROM
confirm
wipe data/factory reset from main recovery menu (optionally wipe cache and wipe dalvik cache)
reboot
Note (<(Y)) this worked for me. If it doesn't work for you, I'm not responsible.
And don't do this if you have important stuff on your phone cos you'll lose it.
YABLP (Yet Another Boot Loop Problem)
Hi,
I'm having a devil of a time installing CM7 on my GalaxyS I9000. Description of my procedure and problem below.
I've been beating my head against a wall for a week so any help GREATLY appreciated.
-John
Phone: Galaxy S "I9000"
Trying to Flash: CM7.2.0 using CWM Recovery
What I did:
Flash stock ROM w/ODIN v1.85 - OK
Wipe Data/Wipe Cache
Flash ChainFire (CF-Root-XX_OVA_JVU_2.3.6-v4.3-XWM3RFS.tar) 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.2.0-galaxysmtd.zip from CM site)
Flash completes in just a few seconds - much too quick!
Phone reboots automatically
Now stuck in boot loop
Screens in boot loop:
1. GalaxyS/GTI9000/Samsung
2. GalaxyS/Cyanogen(mod)
3. CWM menu scrolls by too quickly to read
Back to 1.
Tried Heimdall but complained about missing XML file
Tried installing "Datafix". Would not install (says not compatible with device)
Tried STFW: many reports of same problem but no solutions seemed relevant & appropriate
Clues:
After CF flash, disk use as follows
/system: used 27.3M, free 9.4M (97%) (seems pretty full)
/data: used 47M, free 1916M (2%) (seems pretty empty)
Me thinks maybe /system is too small/full to accept update?
This is the 3rd I9000 I've flashed. First 2 went Ok but this time it failed although identical files/procedures used (I think).
HELP!
I've seen a similar problem on my I9000 - I think the CWM scroll complains about "can't mount /data".
I'm in a similar position, I can't get anything to flash and boot though : http://forum.xda-developers.com/showthread.php?t=1967982
This happens pretty much every time you flash any kind of CM rom from stock. All you need to do is flash CM7, it will go in to bootloop with various text scrolling through thats too fast to read. You just pull battery while in the bootloop. Then replace battery, three button combo to recovery and flash the same CM7 zip again. This time the install will take a while longer. Afterwards flash gapps and reboot and you should be good to go.
I tried this - but same result, just spins round on the CM boot screen
Where do the wipe data and wipe cache commands fit in to this? Before/after both installs?
I don't normally bother with gapps - just trying to get it loaded. Does that make a difference?
Also, no SIM card in at all during all this...
IT WORKED!
Bless you BandiBp!
I'll be sending my first-born by return mail (please don't tell my wife
Yeah that happens because its flashes a kernel with a new partition system. Dunno why only a few roms warn people about this.
Sent from my GT-I9000 using xda premium
You're welcome mate, yeah the reasons are the new partition changes on different roms. I agree that rom flashers should be warned in advance about this. Would reduce problems A LOT. My general rule is if a Rom installs in under 5 secs, then you should always flash again.
Anyways have fun.