Hello XDA
Again I need your help!
My Note is bricked (I think), because it always stuck @DATA.IMG or @DATAFS. So I found the way with the patched pit file. Whatever I'm able to flash ROM's with patched PIT and ODIN.
So I flashed a 3-part GB with custom PIT -> Worked
Than I flashed 1-part ICS without custom PIT -> Works (I did many reboots until "Install Applications" went away)
CF-Root + CWM for that ROM (LQ3) -> Works
But then when I try to flash a Custom ROM (I'd like to have Rocket ROM) with AbyssKernel (Which I flashed in CWM) the ROM flashes, everything OK. But when I try to boot, sometimes it's stuck @N7000 Logo or it boots and stucks @SAMSUNG Logo or sometimes the ROM even loads but hangs everytime or reboots all the time (Totaly unusable). But all that only with CUSTOM ROM.
Why I'm able to use the stock ROM's but the CUSTOM ROM's (Like Rocket ROM) aren't usable? Any help? :/
Thanks in advance!
Any suggestions? :/ Thanks!
If stock roms work then custom roms should also work. Still the procedures to install custom rom may differ from one rom to another. And sometime a certain rom may not work for you. Should try one or few more other customs and it should work.
cheers,
Hii check your internal storage if it is around 8 gb, as you said you bricked then flashed with patched pit, then you wont be able to flash big custom roms, try for small custom roms or rather Asylum or PA rom or if you want TW roms look for rom which is under 400 MB.
from abyss kernel, do data/cache/dalvik wipe and reinstall your custom rom again.
Sent from my GT-P1010 using XDA
Related
Hi, I succesfully rooted Galaxy Note and flash CWM recovery, but I have problem with all Custom ROM's. After flash from recovery still have black screen. Only Custom ROM functional is Cassies XLR. ClockworkMod Recovery has strange behavior, sometimes lag in wiping or another action. I trying another Recovery - Thor Touch Recovery and has similiar problem, wiping or flashing is not completed (abort or reboot recovery). Why are you doing?
Thank you for answer
Regards Krysoft
http://forum.xda-developers.com/showthread.php?t=1329360
follow this thread for rooting and flashing.. this would help you..
Well yours is another note fussy about the quality of the rom installed. Lol
When i made lc1 rom i did so with chainfires latest kernel. However after i tries to boot i would get tje blackscreen.
I had to switch to francos kernel before i released the rom as that did not give the blackscreen. Several reports of this in cf thread.
Not sure what rom base you rootes from and which kernel.cwm packaged you installed.
Also are all roms u tried lc1. Can you try a la6 rom and see
Sent from my GT-N7000 using xda premium
Thank you for answer, but nothing solution is worked. Only possible solution is Chainfire ICS Repack, after flash is now working every AOSP's.
Problem solved, thank you for help.
You can now lock
Regards Krysoft
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
Hi, I'm stuck with installing new rom, so I hope, that you'll help me.
There are steps what I've done:
- followed THIS topic and ROOT the device with ODIN and CF-Root 4.4 file.
- OKAY, I'm rooted, so let's flash the new ROM
- entered in Clockworkmod Recovery and format EVERYTHING ( /data, /system, /cache, /sdcard etc.... just everything) for clear system
- next I load package with ROM and than INSTALLL
and here is the most important part
- when installed ROM gets something like bootloop but with restart - ROM is loading and after about 40 sec its RESTART
- and the same thing over and over again - restart ->loading->restart.... System never start up correctly to the end
- then when I saw that it does not work, I tried go into the CWM, but there was no CWM (!!!) - it was erased (by installing new ROM maybe???)
- so I must flash (old and stock) ROM via ODIN and again root device with CF-Root (with CWM) - that was only functional rom, what I was able to run, and again did this procedure
I tried this way, perhaps with millions of different ROM and EVERY was stucked (restart) while loading.
I think there are some non-deleted files in device, which should be erased (and which cannot be erased by CWM) for clear start of new installed ROM, what do you think?
Would someone please help me? I don't want old Gingerbread with Kies
Thanks for every responce!
Does it say in the thread that you have to flash a custom kernel?? Give.me the link for the thread so I can make sure that you've done everything right
Sent from ma 5assak
there is a link, but in hypertext THIS, i repost it in full text:
http://forum.xda-developers.com/showthread.php?t=788108
I think, when I've root and CWM, there is no problem and install a new rom will be very least, so not as it seems
Dude this is a kernel not a rom what's the matter with you??:what:
Sent from ma 5assak
please read all my topic - i flash this kernel only for clockworkmod recovery
through CWM I can flash any other rom
through ODIN only stock - cant find any ICS or JB rom which I can flash via ODIN (.tar file)
What variant of i9000 do you have? Are you sure that the rom you are trying to flash is made exactly for your variant?
EDIT: Try Darky ROM, they have an ODIN flashable version called "Resurrection Edition" or something.
I mean give me the link for the Rom you are using not kernel
Sent from ma 5assak
Samsung Galaxy S I9000, i'm sure 100%. NOT I9001, NOT Samsung Galaxy S2. Tried many roms from Development section for I9000, tried from get.cm etc... always the same result bootloop with restart
donhashem.dh said:
I mean give me the link for the Rom you are using not kernel
Sent from ma 5assak
Click to expand...
Click to collapse
OK. For example: this rom cm-9.0.0-galaxysmtd and cm-9-20120815-NIGHTLY-galaxysmtd from http://get.cm/?device=galaxysmtd
Or this one last ([ALPHA][ROM][4.1.1] CyanogenMod 10 for Samsung Galaxy S) http://forum.xda-developers.com/showthread.php?t=1778526 and 20120808 build.
and [ROM][PORT][ANDROID 4.1.1][BETA] TAJB: Jelly Bean port for Galaxy S V7.1 http://forum.xda-developers.com/showthread.php?t=1747042
and this too [4.0.4][ROM] Dark Knight 5.5 [27/4/2012] http://forum.xda-developers.com/showthread.php?t=1510940
and many more....
realy unhappy from this
Nikishek said:
Samsung Galaxy S I9000, i'm sure 100%t
Click to expand...
Click to collapse
I meant I9000 or I9000B or I9000M or I9000T there's a difference between them
I9000 only, checked it several times
Ok so you can flash Darky Rom Resurrection Edition through ODIN with no problem. Its GingerBread if i remember correctly, but it should give you a recovery mode and fully operating phone. From this point you can flash whatever you want.
....And there is one more important thing:
When I have a stock kernel and stock rom from Samsung, cant get into recovery mode - VOLUME UP and POWER non functional. Only when I type: "adb reboot recovery" in terminal.
Just after when I flash a new pre-rooted kernel with CWM, VOLUPE UP and POWER is now functional
k4Z3666: OK, I try and give you an echo I think, when I format everything in CWM, there will be no sign of the earlier system and ALL WILL BE CLEAR
Nikishek said:
I9000 only, checked it several times
Click to expand...
Click to collapse
ok, flashing ICS, may need to be done twice, as first flash may bootloop, IF you want to return to stock to get out of this mess, since you are not sure as to where you are now, due to flashing many roms, use any kit from My Android Collections, link below to get you to a booting ROM, than add a kernel with CWM (use EZbaze package with kernels)
that's helped me too thank you
Sent from my GT-I9000 using xda app-developers app
Hi
Ive been trying different cm7.2 based roms for the last few months (apocalypse,droidace etc etc) and yesterday i wanted to try one of the stock based roms (stocklite, stock on fire, stockrom evolution etc etc).
Ive had problems installing all three of them that i never had when i was flashin the cm7 ones. Phone doesnt boot after flashing them. just stuck. and ive given it a good 10-15 mins for the 1st boot...
Is it something im doing wrong? can i flash the stock ones if i was previously using cm7 roms? or do i have to do something before i flash em?
thanks
dblane79 said:
Hi
Ive been trying different cm7.2 based roms for the last few months (apocalypse,droidace etc etc) and yesterday i wanted to try one of the stock based roms (stocklite, stock on fire, stockrom evolution etc etc).
Ive had problems installing all three of them that i never had when i was flashin the cm7 ones. Phone doesnt boot after flashing them. just stuck. and ive given it a good 10-15 mins for the 1st boot...
Is it something im doing wrong? can i flash the stock ones if i was previously using cm7 roms? or do i have to do something before i flash em?
thanks
Click to expand...
Click to collapse
I'd recommend flashing a stock Samsung ROM via Odin first.
I go from Rom to Rom with out ever flashing with odin and never have boot loops or stuck but sometimes after flashing a Rom you have to reboot recovery an do a factory reset wipe that helps me when i get stuck in a boot loop hope it helps you too
Sent from my GT-S5830 using xda app-developers app
Wipe data/factory reset
Wipe cache
Wipe dalvik cache
Format system
And then try to install
If that doesnt work flash stock rom via odin and root and install cwm 5 again
Sent from Ace on CM 10.1
I will try to be as detailed as possible. I have been long time user here, but this is the first time I'm posting. I usually read the instructions and posts and that usually suffices my needs. I was on a rooted galaxy note running chasmodo's assylum rom for quite some time now. For Flashing a new rom, I used to go to recovery mode, flash abbysnote kernel (v 3.9) and install a new rom. A few days ago i tried to flash Ezaechiel XXLT6 KM edition - V2.1. I guess I should have checked md5 of the downloaded rom coz after flashing it, my phone refused to boot up. It always took me to the recovery mode screen where i tried to install abyssnote kernel and reinstall assylum. but it didn't work. So I went to dr. ketan's post and tried to flash a pre rooted rom (SGN_XX_OXA_KJ1_FACTORYFS.zip) using pc odin. Now my phone works fine but i'm on ginger bread. I tried to flash new roms using recovery mode (abbyssnote kernel method) but no new rom can be installed. Everytime I try to install a new rom i face boot loop or get stuck on the setup screen. So I follow the PC odin method to flash the same pre rooted rom (SGN_XX_OXA_KJ1_FACTORYFS.zip) to get my phone working again. I would like to go back to assylumrom because i got used to aosp jellybean so much now. Anybody who has faced a similar problem in the past, please help
Use one of PhilZ kernels and then in his recovery prepare your device for a clean install (there is an option that does more than only "factory reset". With the old ones you didn't clean /preload.
Then follow the instructions to install your preferred Rom.
Thanks
ThaiDai said:
Use one of PhilZ kernels and then in his recovery prepare your device for a clean install (there is an option that does more than only "factory reset". With the old ones you didn't clean /preload.
Then follow the instructions to install your preferred Rom.
Click to expand...
Click to collapse
Thanks for the quick reply thaidai. I will try the method and get back to you I used to do a clean wipe every time.
Mate first upgrade your stock ROM to ICS or JB. The ROMs like Asylum aren't supposed to be installed in GB, so first upgrade, then root and do a full wipe (data,cache,preload,dalvik) and get back to flash the ROM. No need to flash the Abyssnote every time, why do you do that?
Varad297 said:
Mate first upgrade your stock ROM to ICS or JB. The ROMs like Asylum aren't supposed to be installed in GB, so first upgrade, then root and do a full wipe (data,cache,preload,dalvik) and get back to flash the ROM. No need to flash the Abyssnote every time, why do you do that?
Click to expand...
Click to collapse
I tried installing Cassies Xtraliterom XLC1 after the PC odin method. Got boot loop. What I'm basically saying is, after trying the PC odin method to rescue the device, I can't seem to install any other rom on it using the recovery mode route. Not even other GB roms. What am I to do??
Varad297 said:
Mate first upgrade your stock ROM to ICS or JB. The ROMs like Asylum aren't supposed to be installed in GB, so first upgrade, then root and do a full wipe (data,cache,preload,dalvik) and get back to flash the ROM. No need to flash the Abyssnote every time, why do you do that?
Click to expand...
Click to collapse
I started using abyssnote kernel to install new roms after the "brick scare" of last year after which a lot of developers started recommending the method. I used to change between GB, ICS and JB roms easily using the abyssnote kernel. Don't know why it's not working anymore.