i was trying to flash the cm7 rom with glitch kernel for my telus fascinate
http://forum.xda-developers.com/showthread.php?t=1115090
i followed most of the steps correctly but made a mistake on one thing,
on the instruction, there were two different methods and i mixed them up
by formatting system, data, cache when i wasn't required to, since i was using the second method.
installation and everything was successfully completed but the phone won't turn on
for glitch kernel, it would not proceed after the point where galaxy s with glitch logo appears
i've tried flashing different kernels, the ones i used to use and still they have same problem and won't turn on..
i'm guessing maybe i should flash a stock rom
p.s. i'm having a problem entering recovery mod with this phone also..
thanks for your help
start over, flash back to stock, reroot, flash recovery, then continue...
Related
why can't i flash rom's no more.
When i flash a new rom(froyo, toxic) i get :
formating update
formating system
formating data
deleting files
copying files
and then instalation complete en then it reboots and this is whithin a minute. And ofcourse the rom do not work correctly so i have to odin back to stock. I wipe and reset to factory, tryed other roms( zen, biwinning) same thing happens. Olso my nandroid backups will not work, they all hang at bali kernel screen(palmtree). So now i am stuck with stock waiting for a solution. thanks
After you ODIN to JFD... can you explain what steps you are taking?
The more detail, the better.
after i odin back to stock, i root the phone, install rom manager, flash clockworkmod recovery. If i do a nandroid restore i get samsung screen followed by bali screen with a female robot voice saying something about paritioning 2 min and counting then it hangs. I also do a wipe before the restore. If i flash a rom in rom manager or in recovery mode i only get wat i mention above, i do not get a loading bar. Thank you for the reply
Don't restore, your nandroid has voodoo enabled, likely causing issues.
Try this:
Odin to jfd (assuming you have no issues, if you do, try my )
download my option b update.zip (from noob guide) - this allows you to avoid ROM Manager/cwr.
Download a good ROM, I would suggest miui revamped or birgertime's cm7 build (my preference)
Download Bali for cm7/miui
Move all 3 to internal sd
Hold in both volumes + power (can be done with phone on after going to jfd and moving files to phone)
Release at vibrant screen
This is stock 2e recovery, reinstall packages (2x maybe)
Should be in cwr now
Flash ROM
Flash Bali
Reboot phone (don't do anything else)
After it boots, wait 10, reboot
Restore ONLY non-system apps, reboot
Enjoy bad ass phone.
Let me know...
Ok I will try this tomorrow, I will let know, thanks again.
For the roms you mention I do not need bootlaoders right.
Correct. That's about the most dangerous thing you can do also.
I flashed ss-6 miui. So far everything works, calling, sms/mms, even gps and wow this is a really nice rom. I am really happy now, stock is so boring and slow. But leaves me wondering why i could not flash froyo roms. Thanks and greetings from a happy island(aruba) i got a lot of custumizing to do so cheers
Glad you are up and running with my guide. You could repeat those steps with froyo roms, no problem
Sent using the XDA app.
Hi Everyone! just a rookie here in need of a bit of advice.
I'm a Galaxy S II I9100 owner and have my phone rooted and all setup with custom roms and been comfortable with flashing for some time now. My ROM of choice recently was Vanilla Rootbox and have to say the ROM has been fantastic with very few bugs to report. Last night i recieved the OTA update via Goo Manager for Vanilla Rootbox 3.4. I downloaded the full update over wifi and flashed with all wipes no worries. Next step was to flash the latest GAPPS and i figured there would be nothing wrong with flashing the GAPPS zip i had on my sd card that i had downloaded the last time i was notified of a GAPPS update via Goo manager as well. After flashing, wiping everything and rebooting again. My phone then booted up to a series of dialog boxes indicating that many google processes had stopped functioning. apps.google.com etc etc. A similar error has been reported in the Vanilla Rootbox thread by another user but i wasnt able to report this bug their either because my post count is too low to post in a development forum. So after seeing this error i rebooted into recovery to flash my last backup but CWM recovery came back with an error messaging stating it couldnt mount either ext or int sdcard. i did a factory reset which made no difference to the problem whatsoever. I then downloaded ODIN and the latest stock ICS Rom and flashed it via ODIN with no reported errors. My phone now boots through the optus boot animation and is stuck at the Galaxy S 2 screen with the flashing red and yellow animation over the S. If i turn off the phone with the power button, the phone turns off and immediately starts again and gets stuck at the flashing s screen. I've taken the battery sim and ext sd card out and put it all back in only for the problem to persist.
If anyone could help me there's a donation and my thanks in it!
Much appreciated
Nick
tried to re flash another stock ROM?
If so, tried factory reset the phone after the flash?
As long as you can get to DL mode, you are good to keep on flashing till you are up & running.
And then you got this
Remember to update your kies and make sure you close it all up before flashing with odin. If you are in 4.0.4 beware of the brick bug.
gastonw said:
tried to re flash another stock ROM?
If so, tried factory reset the phone after the flash?
As long as you can get to DL mode, you are good to keep on flashing till you are up & running.
And then you got this
Remember to update your kies and make sure you close it all up before flashing with odin. If you are in 4.0.4 beware of the brick bug.
Click to expand...
Click to collapse
Kies has never been installed on this computer but i did use the usb drivers mentioned in the soft brick recovery guide you linked. I used some information from the guide to flash this stock rom but i couldnt flash or wipe the partition because im unsure where to get the .PIT file required? i cant get past the boot animation so no factory reset possible and yes i can still get into download mode!
darkstar117 said:
Kies has never been installed on this computer but i did use the usb drivers mentioned in the soft brick recovery guide you linked. I used some information from the guide to flash this stock rom but i couldnt flash or wipe the partition because im unsure where to get the .PIT file required? i cant get past the boot animation so no factory reset possible and yes i can still get into download mode!
Click to expand...
Click to collapse
wow wow, leave pit files alone for now, they are nasty.
What stock ROM did you flash? 4.0.4 or 4.0.3?
You can factory reset via recovery mode.
Try installing kies anyway, it can't never hurt. Just make sure all applications are closed before you re-flash.
here's jb leak, might help:
http://www.sammobile.com/2012/11/15/i9100xxlsj-%E2%80%93-galaxy-s-ii-android-4-1-2-jelly-bean-test-firmware/
Right so i flashed I9100XWLP8 stock rom (4.0.3). Just then i flashed Siyah Kernel and attempted to use the factory reset function in recovery there, i get a message down the bottom mentioning that it can't mount my internal SD.
darkstar117 said:
Right so i flashed I9100XWLP8 stock rom (4.0.3). Just then i flashed Siyah Kernel and attempted to use the factory reset function in recovery there, i get a message down the bottom mentioning that it can't mount my internal SD.
Click to expand...
Click to collapse
Tell me your:
Model
Firmware
Country
Carrier
Always mention this
try flashing jb leak (ROM, modem & kernel package).
Hey guys!
Since I tried building Firefox OS -Boot2Gecko- on my Samsung Galaxy S2 (i9100) (FYI: I followed this walkthrough) , I'm having quite a hard time making my phone boot on any ROM I try to install. I still have an access to CWM Recovery and to the Download mode
* After failing to flash B2G's Gaia on my phone, I tried to flash the kernel back to the original one and to restore the CM 10.1 NIGHTLY backup I made before doing all this mess. No changes: stuck at CM's boot screen.
* Tried to get back to a stock firmware and ROM, stucks at boot screen ("Samsung Galaxy S II GT-I9100" screen), even after a wipe data/factory reset, wipe cache and wipe dalvik cache.
(In fact, I achieved to boot on a stock ROM once, but after some other manipulations to get my CM 10.1 back, I now can't get it to boot on any of them anymore.)
* I tried to follow the rooting + CyanogenMod walkthrough on CM's wiki, but the same happens: stucks on boot screen. However, after a wipe data, I reach CM's boot animation, which runs indefinitely.
* Right now I tried flashing with Siyah's Kernel, since the flash counter is not any of my concerns anymore. Whatever I try, I can't get anything to get past the "Booting the primary ROM" message.
However, I installed a stable CM9 on the secondary ROM and... it actually works. But even when cloning 2nd ROM to the 1st ROM, can't get the first to boot anyway.
I am not an expert in Android OS architecture, but could it be related to some kind of modifications made by B2G's build & flashing? Maybe some files in the /data or /system partitions have been altered and are not replaced when fllashing, leading to ROMs not loading up?
Any advice on this is welcome.
PS: English is not my main language, sorry if things aren't explained clearly. Tell me if you need any clarifications about it!
hey there,
i have a similiar problem.
i got the info to reflash it using ODIN.
one user told me, that maybe the NAND-RW could be corrupted....
so iam trying it right now...
good luck
Wipe kernel/rom data with a cleaning script. You can find them in dev sections.
Well I flashed it many times with Odin (or Heimdall when I was on Linux) and I saw no improvement.
I don't think my NAND-RW is corrupted, as I can still boot on Download or Recovery mode.
Just found this tutorial, is it worth the try?
Sakujou_Kei said:
hey there,
i have a similiar problem.
i got the info to reflash it using ODIN.
one user told me, that maybe the NAND-RW could be corrupted....
so iam trying it right now...
good luck
Click to expand...
Click to collapse
Well I flashed it many times with Odin (or Heimdall when I was on Linux) and I saw no improvement.
I don't think my NAND-RW is corrupted, as I can still boot on Download or Recovery mode.
Just found this tutorial, is it worth the try?
TheATHEiST said:
Wipe kernel/rom data with a cleaning script. You can find them in dev sections.
Click to expand...
Click to collapse
This one http://forum.xda-developers.com/showthread.php?t=1363738 (Kernel) and this one http://forum.xda-developers.com/showthread.php?t=2100558&highlight=script (ROM) ?
Ok so I tried the cleaning scripts I linked on my previous message, no changes. I can still boot on Siyah's second ROM, but can't get past the "Booting primary ROM" message.
Ideas anyone?
Any ideas why this could happen?
What I do everytime:
Flash XXLPB with ODIN 1.85, root with CF-Root v5.2 CWM, reboot, all fine.
Then I flash for ex. Carbon ROM Nighlty, GAPPS, reboot and it's stuck at triangle screen. Can't go to recovery, only download mode works.
I also tried "old" Carbon 1.8, and even other ROMS that worked like a charm some time ago.
All started when I tried yesterday to flash 4.3 Carbon nightly over 4.2.2 (1.8) Carbon w/o wiping...
Please help as for now I'm stuck with my 3310 xD
Back to stock via Odin/download mode (you don't really have another option), make sure you do a wipe/factory reset, try flashing the rom again.
I tried 4-5 times, and always the same is coming out! Is there any minimum requirement for flashing let's say 4.2.2? Shouldn't matter, right?
It shouldn't matter but we see cases on here all the time where for whatever reason, Odin flashes don't take on the first/second.....eighth (as an example), and for whatever reason, the ninth flash works. In other words, you need to persevere. Try different stock roms for your carrier (different Android versions, not just the recent ones - but don't use 4.0.4 in case you forget when you re-root your phone & do a wipe which will brick your phone). And keep trying. There's no easy fix for these situations unfortunately (search for Hopper8's 'Odin won't flash' thread, there's stuff in that thread you can try).
Actually the ODIN flash of the stock rom always works. But then I flash a rom through CWM and it bricks...
Is there a way to flash those roms with ODIN?
No. Almost all custom roms are CWM flashable.
OK...What I suggest you do is this...
*Clean install of stock with wipe/factory reset.
*Root your phone by flashing a custom kernel like PhilZ or Siyah (or Dorimanx).
*Do not flash a separate CWM or any other mod after you've rooted the phone.
*Read the first page of the thread devoted to the rom you want to flash very carefully. Flash the rom with CWM/follow the instructions to the letter (do not use Rom Manager or the CWM app from your homescreen; boot the phone into recovery & flash that way).
If you're seeing specific errors in CWM having done those steps (And do them again now even if you've done them previously), you need to tell us exactly what's going wrong in CWM. We're not mindreaders.
Edit - Your phone isn't bricked. Bricked phones don't boot. At all.
Thanks for the detailed answer.
Actually that's what I'm doing every time!
I'm trying to install 4.3 nightly build of carbon
I tried also stable build which was working well before...
There are no specific instructions, but I think it's pretty much standard:
1. Wipe Data/Factory Reset
2. Flash zip
3. Flash GAPPS
4. Wipe Dalvik Cache
5. Reboot
Thanks!
EDIT: After flashing the custom rom the phone doesn't boot, it gets stuck at kernel panic upload mode. Once I managed to get into CWM but there I couldn't perform any action, it was freezed.
Hi Again,
it looks like everything worked fine. Maybe I had a strange version, or the CWM was to old (5).
Now I could flash what I wanted and it's not stuck at boot anymore!
Thanks for the help!
Perseverance is a beautiful thing.
i'm on "I9100XWLST_I9100ODDLSE_INU" 4.1.2 india official firmware
i tried flashing "GT-I9100_JB_ClockworkMod-Recovery_6.0.2.9" recovery and flashed it successfully.
after reboot it went into recovery but my phone doesn't boot up like normal and struck at samsung logo with a caution symbol.
tried installing slimbean final build but still the same....
can any body help me to install recovery and slimbean
thnx
Do a factory reset in recovery mode, if you have no recovery mode or the reset doesn't fix the bootloop, get a stock rom from Samfirmware & flash it with Odin following the instruction in thread stickied near the top of Q&A to get a clean slate. Then...
Pro tip 1: Read the instructions for what you were trying to do thoroughly & understand exactly what you need to do this time, the issues you're seeing are almost always caused by not doing something that's required, flashing a wrong file, etc.
Pro tip 2: If you flash CWRecovery independently, it will only persist till the next reboot because recovery is baked into the kernel. I recommend you root your phone by flashing a custom kernel, this will give you permanent CWRecovery & you can flash whatever rom/kernel you want from there. The thread I referred to above also has a very simple root method which involves flashing a custom kernel.
I dont think the kernel supports the Roms you tried.. find a compatible one..
Sent from my GT-I9100 using xda app-developers app