So first i'll explain whats the problem.
I went from Slim ICS to stock android 2.3.5 XXJVT. After that I flashed the rooted kernel via Odin, including CWM.
So I got to the recovery and wiped everything and flashed the a cm9 nightly, this was in the instructions SlimICS If coming from stock GB. While installing it stopped after a few seconds and rebooted to recovery where a few lines came up amd rebooted again, alot of red letters flashed between the reboots and it kept rebooting.
I have tried other roms with a similar result:
-After install, comes to kernel loading screen reboots straight into recovery.
-Tried infinitum, succesfully installed actually started OS but got an error acreen in android itself, saying something about encryption or something (forgot it).
I know this is a long story but i've been trying to flash ics again for a lot of hours with a lot of fixes but nothing succesfull.
I hope you guys know more then me. If you need more info please ask, im pretty issed of by phone right now.
Thanks
On I9000
Pull out the battery.put back in.go to recovery and flash again.reboot.
It's does this because u need to be on an ics kernel for it to flash the rom properly.it's perfectly normal.don't worry
It only happens when upgrading the os or flashing cm9 the FIRST time
zodiaxe66 said:
Pull out the battery.put back in.go to recovery and flash again.reboot.
It's does this because u need to be on an ics kernel for it to flash the rom properly.it's perfectly normal.don't worry
It only happens when upgrading the os or flashing cm9 the FIRST time
Click to expand...
Click to collapse
Thanks! I'll try and see what it does. I'll let you know
Take a look here:
http://forum.xda-developers.com/showthread.php?t=1627689
ZioGTS said:
Take a look here:
http://forum.xda-developers.com/showthread.php?t=1627689
Click to expand...
Click to collapse
And how would this help non devs and noobs?????????????
If u have no intention of helping why post
Related
Hi,
I as of yet, am not going close to any ICS build till the issue gets solved by someone.
so I am experimenting with different gb roms. i was using checkrom v6 but didnt like it, so followed steps to install darkyrom/alliancerom extreme edition. i followed the steps as I was told to install allianceota and flash the rom through there. it didnt work. so instead using cmw i flashed through recovery, it did flash but there no root.
so now, i reflashed a stock la6 rooted rom from here; http://forum.xda-developers.com/showthread.php?t=1535025
this went smoothly with no problems, so i installed allianceota as normal, this time when i try to flash the following messages come up:
Installing Multi-CSC
Can't access to '/system/CSC/KOR/system/'
Successfully applied multi CSC"
and then it gives me the option to reboot, wipe cache and a few other options, not full recovery mode.
shall i just reflash the rom through recovery, or am I doing something wrong? and does the slight error above mean I have a problem with my note?
cheers in advance.
Let me just say that almost every ICS ROM out there now has disabled the MMC_CAP_ERASE code in the kernel that activates the eMMc bug and bricks your phone. If you want stock ICS, you can use SpeedMod or Franco kernels. If you want AOKP, there is that now. If you want CM9, there's a bunch of variations plus the official CM9 nightly. If you read through the OP and stickies, you will be okay.
Are you on stock recovery still? It sounds like it from the error you are getting. Try flashing CWM recovery and installing the GB rom with that. Follow Drketan's thread in Android Development.
hmmm, so would you advise me to use ics? is it much better? i dont want to use cm9 builds as i need the spen apps and so on. i have looked into kingdroid or alba.
I'll have to think hard about this. i may give it a shot soon though..
oh and btw, I fixed the problem, yep it was to do with cwm it wasn't installed with the stock rooted rom. as for allianceota, it still didnt flash the rom, i had to flash the rom through cwm manually.
cheers anyhow.
salespalace said:
hmmm, so would you advise me to use ics? is it much better? i dont want to use cm9 builds as i need the spen apps and so on. i have looked into kingdroid or alba.
I'll have to think hard about this. i may give it a shot soon though..
oh and btw, I fixed the problem, yep it was to do with cwm it wasn't installed with the stock rooted rom. as for allianceota, it still didnt flash the rom, i had to flash the rom through cwm manually.
cheers anyhow.
Click to expand...
Click to collapse
I love ICS a lot more than GB. If you want to use stock ICS, I would just use Franco or Speedmod kernels with it and be safe. Read both of their forums and decide what you want to do.
I had the same problem with rom deodex i had flash with odin 1.85 firmware gingerbread here ; http://www.hotfile.com/dl/152168378/f76281c/N7000XXLC1_N7000OXXLB3_ATO.zip.html... then i made wipe cache and cache dalvick .
I've just flashed AlBa repack latest one on xxlq2, I did it by following the steps,
I thought i had broken my phone, because when the flashing finished and i was rebooting, at the beginning when it welcome to galaxy note n7000 and then goes to the bootup video, it restarted that several times, then after like a few minutes it loaded the homescreen and startup.
salespalace said:
I've just flashed AlBa repack latest one on xxlq2, I did it by following the steps,
I thought i had broken my phone, because when the flashing finished and i was rebooting, at the beginning when it welcome to galaxy note n7000 and then goes to the bootup video, it restarted that several times, then after like a few minutes it loaded the homescreen and startup.
Click to expand...
Click to collapse
-Flash a stock GB rom with pc odin
-Root it
-Go to cwm and wipe all (factory reset,cache and dalvik and then Install the ics rom that you like
-Reboot system and now it should work
Sent from my GT-N7000 using Tapatalk 2
I have had my captivate for a while now and I have had a few problems with flashing Cyanogen based Roms since I went to CM7 then back to stock a while back.
I had CM7 running fine and went up to CM9 for months. I just recently went to REMics and had a problem with the sound and at the same time I had problems with my power button I the flashed to Paranoid Android for a few hours and was driving around so I took my phone to the AT&T warranty center to see about them replacing it and im out of warranty so I had them flash it to stock now I cant get my phone to CM7 I can get it to run Serendipity just fine but no CM7 can someone PLEASE help? It seems like I need to COMPLETELY clear the phone of all old rom data. Any solutions?
Try using one of these Stock I897UCKK4 Android 2.3.5 One Clicks and then flash the KK4 Corn Kernel version 7.0A to get the CWM Recovery u need to move on to what you are wanting to flash per that Rom's specific install instructions.
Done that
I have put my phone back to stock KK4 with and without bootloader. I had this problem before when I was going to CM7 the second time. Its just getting SO annoying now. Thanks though!
I forgot to say that when I go to flash the rom through CWM it starts reboots the phone the samsung Cyanogen screen comes up flashes onces then goes into CWM flashes a few things quickly and the last image I see is the "dead" androind laying on its back with the sign aboveits open front door.
I'm starting to think there is no help. Maybe I can trade my friend my captivate for his.
Have you tried flashing CM7 again after you see that CWM screen? I've always had to flash CM7 twice for it to take - once to get the MTD setup in place, a second time to actually flash the rom. You'll have to hold down V+/V-/Power to get to recovery while it's looping, but once it's there, try flashing CM7 again.
jmtheiss said:
Have you tried flashing CM7 again after you see that CWM screen? I've always had to flash CM7 twice for it to take - once to get the MTD setup in place, a second time to actually flash the rom. You'll have to hold down V+/V-/Power to get to recovery while it's looping, but once it's there, try flashing CM7 again.
Click to expand...
Click to collapse
I have tried with cm9 but not 7. I will try that once I get sick of Serendipity. I just set everything back up on this rom and installed my apps so I will wait a few more days.
Thanks You!
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.
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
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!