Hi,
I've been trying to get the Tab to boot all day long, but I still get stuck on first bootscreen.
I followed every word here but no matter what (Heimdall/Odin/CMW), all flashes fine, but after applying the ext4 converter and directly flashing Overcome Rom (and then flashing Koxudaxi's kernel - did both, no difference) the tab just doesn't boot.
I'm pretty tired out right now, as so many stated it beeing no problem.
What did I miss?
Thanks in advance.
Related
I've been trying to get ICS on my Galaxy S but every single ICS rom I install causes my phone to bootloop.
I'm on JVU firmware in combination with:
This is the December 29, 2011 / Android 2.3.6 / JVU / Value Pack ? build:
CF-Root-XX_OXA_JVU_2.3.6-v4.3-CWM3RFS.zip
So far I've tried to flash CM9, Slim ICS and Team ICSSGS RC4.2.
What happens when I try to flash any of these roms:
Progress bar show up, it starts installing
At 5% phone reboots
Boot logos show up
Phone enters recover again and some lines of text show up (not long enough to be able to read but looks like error messages)
After less than 1 second the phone reboots again and the process repeats itself
Does anyone have an idea how to fix this? Would be much appreciated because this issue has left me frustrated and I just want to have working ICS on my phone.
Thanks in advance.
When installing ICS over the top of Gingerbread there is a requirement to Flash the ROM twice.
Once to upgrade the bootloader to ICSSGS 4.2 version and second for the ROM to fully install.
I did this and was able to successfully upgrade to ICS.
Searching the thread for ICSSGS 4.2 would have provided the answer for this issue.
If this is unsuccessfull flash back to a gingerbread ROM using Odin Darky's 10.2 worked for me. allow the phone to fully boot. then retry you ICS ROM
Before flashing ICS you also must disable anny lagfix that is applied.
I tried flashing twice already, didn't work. I'm flashing darky 10.2 atm and will try flashing an ics rom again when it's done. Thanks for the tip.
I had kind of the same problem, although my boot loop was a little different i think. I Odin'd Darky's 10.1 a few times, but in the end also tried 9.2. That worked. No idea of that made the difference, you could give it a try.
Sent from my SGH-I9000 using XDA
Allright flashing Darky's 10.2 first and then ICS twice was the solution, so weird. Thanks for the help
Hi, i'm running Teamhacksungs build 17, and just tried upgrading to new Semaphore 1.2 (regular and s version).
Started by running kernel cleaner script from CWM.
First tried the regular version, and phone would not boot anymore past the Semaphore kernel splash screen.
Then i tried the s version (aka. bigmem configuration), and after succesful flash trough cwm and boot, now my phone freezes at kernel splash screen. To make matters worst, CWM through three button combo is not working anymore!
Bootloader still works, so i was wondering, is it possible to flash new ics kernel with CWM through odin? I really dont want to re-stock my phone with GB and then start the whole ics upgrade process all over again, specially cos my backups are not fresh . (I know, stupid me).
Any help would be great!!
I think you can flash mid night kernel using odin.
Sent from my GT-I9000 using Tapatalk 2
Try another rom
This rom cleanAOKP 1.0.2 have already update to semaphore 1.2
http://forum.xda-developers.com/showthread.php?t=1552124
Hi I was running Helly Bean and I was experiencing some lag that i couldnt fix so i decided it was time to start fresh (phone was getting to be a mess anyways) so i formatted my phone and one-click to a stock rom. (rogers i896 2.3.3 with bootloader). I used heimdell to flash kernel with recovery, then flashed devil kernel, reboot recovery, then flashed helly bean as per thread instruction and my phone kept booting into recovery only. So i tried to start over 2 more times with the same results, I even tried to flash CM9 stable release and it yielded the same results.
Can anyone shed some light as to what i messed up? My only option now is to use stock app since i cant seem to get anything else to work...(pleas dont make me go back to touchwiz)
Any help is appreciated,
Thanks.
PS phone works fine on stock rom
This happened to me once... I think it has to do with repartitioning and Devil kernel. If you flash devil first, it seems that something is telling the CM installer that the partitions are all good to go, even though it is clearly not the case. So use heimdall to flash the first kernel, and go straight to the ROM install, making sure to flash the ROM a second time after it reboots into the new recovery.
korockinout13 said:
This happened to me once... I think it has to do with repartitioning and Devil kernel. If you flash devil first, it seems that something is telling the CM installer that the partitions are all good to go, even though it is clearly not the case. So use heimdall to flash the first kernel, and go straight to the ROM install, making sure to flash the ROM a second time after it reboots into the new recovery.
Click to expand...
Click to collapse
Thanks, works first time!!! Looks like im going to have IMEI problems but thats another battle lol
odin to stock 2.3.6, charge to 100%, then go to recovery, 4w, 2f, then install helly bean.
just went thru this last week.... accidentally flashed incorrect ROM to Captivate and phone started acting wiered.
Then came to know i have the wrong bootloaders and kernel. Just installed GB bootloaders and phone started booting to recovery.
then tried to flash ics rom and soft bricked my phone.
Used the "hold both volume buttons and plugin the USB cable to computer" to get into download. then ODIN to stock GB. then used KKroot and then flashed Slim ICS. Now the phone works great.
Hello!
I've been having a lot of trouble flashing recovery, rooting and installing custom rom for my Mini 2. After a lot of researching and trying I have successfully rooted and after installed Cyanogenmod 10.1 and now I got the JellyBean 4.2.2. And now I would like to find out whether or not I should upgrade/change the kernel. Can anyone tell me please if there is another kernel for CM10.1 and for my device specifically, and will it make my phone more faster or not. I have tried to install Semaphor (I don't think this is compatible with my device), Devil (Same here) and Franco (Which is same) for all three of them I have got the status 7 error. I have also tried to install some kind of kernel update for my device which completely messed up everything (different colored display, some glitchy stuff and random reboot every 0.5 seconds ), so I had to install the stock rom (because the cm didn't work) and then the cm.10.1 again (now I'm good). Also to let you know my current kernel version is 2.6.38.6-1214151 (that's what says settings -> about phone -> kernel version). If there is nothing better then don't worry, my phone at the moment runs smoothly anyways!!!
Thanks in advance.....
Please...
Anyone???
I had that error on cwm 6.xxx
Then i flashed cwm 5.0.2.8 and there was no error, it worked
Just wipe everything and go to mounts and storage->format /system and after that mount /system
Make sure you have backup of your working rom. If your device wont boot after flashing (if its just booting in recovery, flash stock rom
(get into downlad mode voldown+home+power, hold power button until samsung logo.)
If thats what you have problem with...
No, don't install something that won't work for your phone. Kernel are main controllers in your phone. You change the kernel, you change how your phone works. If you lucky, you get your phone booting, but with glitch everywhere. If you aren't lucky your phone will dead, no matter if you install a custom ROM, or a fresh stock ROM.
THX
F4uzan said:
No, don't install something that won't work for your phone. Kernel are main controllers in your phone. You change the kernel, you change how your phone works. If you lucky, you get your phone booting, but with glitch everywhere. If you aren't lucky your phone will dead, no matter if you install a custom ROM, or a fresh stock ROM.
Click to expand...
Click to collapse
I appreciate the reply, so as far as I understand, Kernel is completely separated from the ROM. So if I get any error or problem with the Kernel, it's going to be hard to fix, because re-flashing the ROM will not change anything. If what you said is right then I will not risk it, because my phone has got already CM10.1 installed and is working nice and smoothly, however I got another question. I'm not sure what Kernel version I had previously but when I installed CM I think it changed the Kernel, because the name of it is not the same as I've seen when I had stock ROM (It says 2.6.38.6-1214151 [email protected]#1 Sat Mar 23 11:49:35 EET 2013). I am really happy with what I've got at the moment so I will not change it, because if my phone ends up bricking, or anything else, I can't afford to buy another one for now (sometime later yeah )
Anyways thanks for your help!!
Hey!
I've flashed kernel and firmware on my Note successfully several times, but now I encountered a problem:
I'm on Asylum_CM10.1_20130311_n7000 ROM and was using Asylum_CM10.1_20130311_n7000 kernel, all working fine.
Then I flashed a new kernel, HydraCoreNirvana Kernel for Galaxy Note GT-N7000. After this I've been in hell, every time I try to start/boot the phone, it jams on the Asylum startup animation. I tried both from the SD and when the phone wouldn't start, via Odin. Then I tried flashing back to the working kernel above, no help. Now I'm stuck with two non-working kernels and a useless phone. I hope I haven't ruined it already...
I was flashing with the instructions @ rootgalaxynote. com
Any help would be greatly appreciated!
-Larson
larson80 said:
Hey!
I've flashed kernel and firmware on my Note successfully several times, but now I encountered a problem:
I'm on Asylum_CM10.1_20130311_n7000 ROM and was using Asylum_CM10.1_20130311_n7000 kernel, all working fine.
Then I flashed a new kernel, HydraCoreNirvana Kernel for Galaxy Note GT-N7000. After this I've been in hell, every time I try to start/boot the phone, it jams on the Asylum startup animation. I tried both from the SD and when the phone wouldn't start, via Odin. Then I tried flashing back to the working kernel above, no help. Now I'm stuck with two non-working kernels and a useless phone. I hope I haven't ruined it already...
I was flashing with the instructions @ rootgalaxynote. com
Any help would be greatly appreciated!
-Larson
Click to expand...
Click to collapse
Please, I'm drunk and freaking out with this phone (I know 1st world problems).
Do a wipe data in recovery (if u can go to) or ODIN. Then try to see if the phone boots, if it doesn't you can do a clean install of Asylum ROM again. If nothing works(!) Go back to flash a stock ROM via ODIN and then use Philz kernel to re-root.
Varad297 said:
Do a wipe data in recovery (if u can go to) or ODIN. Then try to see if the phone boots, if it doesn't you can do a clean install of Asylum ROM again. If nothing works(!) Go back to flash a stock ROM via ODIN and then use Philz kernel to re-root.
Click to expand...
Click to collapse
Tried all that (went straight to stock). No help, I guess somethings gone wrong with the boot sequence, I flashed Philz kernel and now it loops on the samsung animation. Before, it sometimes showed "Android is upgrading 1/83 (or something similar), the number would go up a while, then the start-up animation again and all over again from 1/83. It always seems to jam on the ****ing animation... Gonna jump off the roof.
larson80 said:
Tried all that (went straight to stock). No help, I guess somethings gone wrong with the boot sequence, I flashed Philz kernel and now it loops on the samsung animation. Before, it sometimes showed "Android is upgrading 1/83 (or something similar), the number would go up a while, then the start-up animation again and all over again from 1/83. It always seems to jam on the ****ing animation... Gonna jump off the roof.
Click to expand...
Click to collapse
I got the phone working again. Did a factory reset from recovery and after that the phone started up. After that installed the HydraCoreNirvana Kernel again and now it works just fine. Thanks very much for the help!