I want to share my problem to understand and try to solve
I bought my notes Firware KKA
root procedures performed with CF, no problem
created a custom wipe smoothly functioning
problems began with the outputs of the next firmware
by KKA can not install anything, the problems stem from other installations doing firmware with the only result of a bootloop ..
not to have problems you need to install anything starting from KKA
KKA be no problem at LA4, LA4 to be Jkay ie the result is a loop
tried everything ..
wipe, full wipe, right wipe, odin, odin mobile deep clean 1 and 2, but the end result is always
at the beginning I thought it was a problem the updater script used .. but the problem is not just my rom but all those tested
have solutions?
yes be more patient, you wont always get a reply in less than an hour and half
you have posted in the wrong section this for DEVS ONLY not for questions, post in the Q&A section next time
so custom roms/mods boot loop does a stock rom boot loop?
I have a lot of patience and no rush
I noticed the wrong section but I can not move
loop only with custom roms
stockrom are ok with odinmobile
I came from kka. First flashed chainfire's cwm kernel. Then I tried to flash rocketROM but didn't worked. I was glad I made a back up (for the first time ever, and I have a long history with flashing) today I tried again with the ROM from Chris x. Now no problems. Flashed the abbyss kernel afterward no problem v 3.5 b
Sent from my GT-N7000 using xda premium
pglmro said:
I have a lot of patience and no rush
I noticed the wrong section but I can not move
loop only with custom roms
stockrom are ok with odinmobile
Click to expand...
Click to collapse
All you have to do is hit the report button and ask that it be moved - which it has been.
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
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
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
Firstly I apologize for posting in Q&A's, due to the 10 post restriction I was unable to post in the rocket rom thread in android development and Q&A's seemed the second most ideal place.
After a day of horror, I tried merely flashing Abyss Kernel 4.2 but I ended up somehow in a soft brick accessing the recovery and download modes only. After ages I decided to try my luck installing Rocket rom v7 and it thankfully worked and my phone is up and running.
However, I have faced a couple of issues with it, of which the major one is the lack of response when hitting the home (center key) on my international version of the galaxy note. It doesn't work whatsoever, I've also noticed that the lock screen has disappeared too, so when I put the phone to sleep and wake it I get taken to the page I closed on rather than the lock screen. The latter I have fixed by using widgetlocker, although I am still oblivious as to how to fix the home key losing it's function.
Any advice etc? (especially if it's kept in layman terms, and nothing drastic... I despise flashing!!)
Moreover I was just wondering is there a set of instructions one could follow to return to a stock rom on the galaxy note via CWM?
Kind regards and thanks for your time
9009i said:
Firstly I apologize for posting in Q&A's, due to the 10 post restriction I was unable to post in the rocket rom thread in android development and Q&A's seemed the second most ideal place.
After a day of horror, I tried merely flashing Abyss Kernel 4.2 but I ended up somehow in a soft brick accessing the recovery and download modes only. After ages I decided to try my luck installing Rocket rom v7 and it thankfully worked and my phone is up and running.
However, I have faced a couple of issues with it, of which the major one is the lack of response when hitting the home (center key) on my international version of the galaxy note. It doesn't work whatsoever, I've also noticed that the lock screen has disappeared too, so when I put the phone to sleep and wake it I get taken to the page I closed on rather than the lock screen. The latter I have fixed by using widgetlocker, although I am still oblivious as to how to fix the home key losing it's function.
Any advice etc? (especially if it's kept in layman terms, and nothing drastic... I despise flashing!!)
Moreover I was just wondering is there a set of instructions one could follow to return to a stock rom on the galaxy note via CWM?
Kind regards and thanks for your time
Click to expand...
Click to collapse
on what rom did you flash v7 ?
iam currently running it no issues at all, everything works maybe you 'll have to do a clean install just flash abyss kernel full wipe with it and reflash the rocketrom v7 using it dont not reboot until you flash the ROM since you flash a GB kernel on an ICS system....... wont boot just softbrick. watch it!
sounds like the system files a corrupt somehow and btw if case you changed kernel let us know too....
REVERSiN said:
on what rom did you flash v7 ?
iam currently running it no issues at all, everything works maybe you 'll have to do a clean install just flash abyss kernel full wipe with it and reflash the rocketrom v7 using it dont not reboot until you flash the ROM since you flash a GB kernel on an ICS system....... wont boot just softbrick. watch it!
sounds like the system files a corrupt somehow and btw if case you changed kernel let us know too....
Click to expand...
Click to collapse
Ah yes sorry wasn't clearn.
I was firstly on ICS 4.0.3 stock rom XXLPY, I kept getting nagged about the kernel instability so I went and tried to flash Abyss kernel 4.2 (somehow stuffed it up ended up soft bricked). So I then flashed Rocket Rom v5 (after properly flashing Abyss kernel) via CWM. I think follow the steps to upgrade to v7.
Tbh I really do not want to mess with flashing and ODIN again >.> have become paranoid.
9009i said:
Ah yes sorry wasn't clearn.
I was firstly on ICS 4.0.3 stock rom XXLPY, I kept getting nagged about the kernel instability so I went and tried to flash Abyss kernel 4.2 (somehow stuffed it up ended up soft bricked). So I then flashed Rocket Rom v5 (after properly flashing Abyss kernel) via CWM. I think follow the steps to upgrade to v7.
Tbh I really do not want to mess with flashing and ODIN again >.> have become paranoid.
Click to expand...
Click to collapse
Grr couldn't find the post edit button, but tbh I do think it's a setting issue or so I am hoping I did play around with the rocket rom tweakbox and I imagine that may have been the cause of this issue or so I am hoping
Dont worry reboot to recovery and flash v7 again and reboot (no need to wipe or flash other kernels )
Sent from my GT-N7000 using Tapatalk 2
REVERSiN said:
Dont worry reboot to recovery and flash v7 again and reboot (no need to wipe or flash other kernels )
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Wouldn't that just give me 2 copies of rocket rom and cause issues? Or will it install missing files?
So I should just install zip from SD and that's all?
Ok I am redownloading now and going to give it a shot.
Moreover, I would love for any advice on how I can return to stock rom... any advice would be most welcome. I'd prefer only to use CWM.
Or if there is perhaps another fix the issue above? Any comments would be most appreciated!
First of all yes you can install zip from as and select v7 (no it won't harm it will overwrite all files Yes, I understand want have duplicates unless they are from another rom but again full wipe would have removed them from before so you are ok.
Well idunno about CWM stock rom I prefer you use either pc odin or mobile odin (recommended) just charge the phone to 100% and install mobile odin set you stick firmware on sdcard and select open file in mobile odin then in case you want the root keep options as they are and select wiping option both. In case you don't want root deselect the object superuser options and still check the willing one
About home key issue might be a script issue one of hardware files is messed up so I can't tell for sure which but mostly the files are at system/usr/
Sent from my GT-N7000 using Tapatalk 2
REVERSiN said:
First of all yes you can install zip from as and select v7 (no it won't harm it will overwrite all files Yes, I understand want have duplicates unless they are from another rom but again full wipe would have removed them from before so you are ok.
Well idunno about CWM stock rom I prefer you use either pc odin or mobile odin (recommended) just charge the phone to 100% and install mobile odin set you stick firmware on sdcard and select open file in mobile odin then in case you want the root keep options as they are and select wiping option both. In case you don't want root deselect the object superuser options and still check the willing one
About home key issue might be a script issue one of hardware files is messed up so I can't tell for sure which but mostly the files are at system/usr/
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for all your help REVERSiN, just to update you.
I tried re-installing v7 rocketrom and flashing however still faced the same issue of the home key etc. So I kept a stock rom in my external SD went to CWM recovery and did a full wipe, delvik cache wipe and cache wipe tried installing the stock rom however CWM had issues opening it and aborted. So I installed rocketrom v7 again and voila it works perfectly now and seems brilliant.
I think I still want to return to stock eventually, but I refuse to use Odin, I tried using odin twice and both times it froze the first on factorycs (although my phone wasn't bricked) and the second time yesterday on cache so yah I have had terrible luck with ODIN and I refuse to use it,.
Nonetheless if there is way to flash stock rom using CWM would be epic. However, until I am 100% sure on how to do it I'll be sticking to rocketrom.
Thanks again for all your help and time!
Hello All,
I've spent the last 6 months learning how to flash roms, realise you need the right kernel and made many mistakes which resulted in bricking my phone. I've learnt a lot and as you often suggest on this site, read and learn. I've been trying my best to do this over the months and have managed to even use Odin, after about 70 hours reading, track down a kernel XXLT to get my phone back into recovery and many other painful experiences.
I thought i had the basics down pat by now but i've bricked my phone this time and I'm truly stumped as it brings up an EMMC message and nothing i do with Odin or flashing kernels afterwards brings the phone back at all. I'm sure it's on here somewhere and you will point it out to me but I have tried as it's the only way to learn. Now, if you are willing, i could really benefit from some expert advice?
I have been running CM11 for the last week, really enjoying how it worked on my n7000. I was doing some further reading and came across the page for the Forest Kernel for CM11 on the n7000. I thought no problem, download file, follow flash instructions (wipe dalvik) and proceed as normal. But the zip file would not load and the recovery aborted. I was using CWM touch and in the malaise that followed, i now can't rememer which one it was but it was the grey screen one with the touch functionality.
I thought maybe i didn't have the right CWM to flash this file so I thought I would try a later version of CWM but use PHilz' touch version - using the 'about in recovery' it has v 6.0.3.7.
So i flashed the file again using Philz' version and then i just got a lot of fast scrolling text and I was stuck in recovery from that point on. I tried wiping for reinstall , installing raw kernels and everything i think i know about trying to fix it myself.
However, with lots of fast scrolling text going by, i started looking more closely at it and noticed this message:
Created filesytem with 11/32768 inodes and 4206/131072 blocks
warning wipe_block_device: wipe via secure discard suppressed due to bug in emmc.
now flash a new rom
Since this message, nothing works from the flashing a new ROM in recovery onwards. I just get message like cannot load .ini or failed to open zip etc.
Now i did spend time months ago reading about teh ICS emmc recovery problem but because I've been on 4.4.3 to begin with i thought I'd already surpassed the problem.
I've been running Slimsaber and recently CM11 on KK 4.4.4 so i didn't think i could initiate an 'emmc' problem.
So now i'm stuck and of course, bricked my phone just when i need it most. I only undertook flashing the Forest kernel because it seemed such a low level risk, wipe dalvik and flash.
If any of you could offer some advice, yes, even if you tell me to read it etc, I will understand. It's just after having taught myself so much from these pages I seem to have met my match this time in recovering my phone, so any advice or assistance will be appreciated.
I understand though if asking for this help is inappropriate.
Thanks in advance.
Regards,
Paul
For my part I simply do not understand when you did what thing in which order. It's a little bit chaotic.
So if you want to check if you really bricked your device:
download a stock rom and try to flash it with PC Odin.
If there are errors post them with snapshots.
No need to write a complete story...
Did you try to flash a stock Samsung JB rom using Odin and start fresh?
I didn't read the complete post, title is enough for me, I had same problem some time ago. Flash a 2.3.6 Rom, do wipe data from recovery and then flash 4.1.2 rom.
Greetings.
ThaiDai said:
For my part I simply do not understand when you did what thing in which order. It's a little bit chaotic.
So if you want to check if you really bricked your device:
download a stock rom and try to flash it with PC Odin.
If there are errors post them with snapshots.
No need to write a complete story...
Click to expand...
Click to collapse
Dear ThaiDai,
Sorry, when it goes wrong, it certainly is chaotic. The whole process of going wrong snowballs.
I'll try and follow your advice, thanks for your help.
Cheers,
nokiamodeln91 said:
Did you try to flash a stock Samsung JB rom using Odin and start fresh?
Click to expand...
Click to collapse
Hello Nokiamodel. Thanks for your help. No, i didn't. As i ended up stuck in Philz touch recovery, I tried pushing a raw kernel on via Odin.
When i bought this phone, it came with Gingerbread on it so does that mean i should use gingerbread to return to stock?
cheers,
p
majaretilla said:
I didn't read the complete post, title is enough for me, I had same problem some time ago. Flash a 2.3.6 Rom, do wipe data from recovery and then flash 4.1.2 rom.
Greetings.
Click to expand...
Click to collapse
Majaretilla, thanks for this advice.
I was about to do this when i remembered reading somewhere on another forum that sometimes taking the battery out can sort something like this out. I took out the battery, and when i put it back in, it did not boot into philz touch recovery but what i now realise is the stock recovery. It's the one where you move the cursor by using power and volume keys.
This recovery flashed over the kernel and then roms I had onboard the phone until i got it back to CM11.
The only thing I can't crack now is why that Forest CM11 kernel won't flash using CWM or Philz. It gets aborted. I've tried v2, v4 and v5 and it never works.
I can't find out why or how to overcome the problem so I think i'll leave well alone. It's justfrustrating not knowing why it doesn't.
Thanks again for your help,
p