Hi all, I could really really use some help.
Today I decided to try and flash CM9 RC2 and I seem to have messed up big time.
I startred by rooting, using Dr Ketan's guide. That all went smoothly, and root was working.
I put the CM9 zip file on the SD card, turned off my phone, got back into CWM recovery, and most tutorials recommended, selected full data wipe... this is where something seemed to go wrong. While perfoming the data wipe, it seemed to freeze. I let it sit for a while, hoping it would sort itself out, but it didn't, and then it rebooted itself and went into a boot loop.
I can't get back into recovery mode, but I can get into download mode. So I thought the best thing to do would be to flash a stock firmware using odin.
I downloaded the latest german LRG firmware (which I was on before I started) from Sammobile, connected my phone to odin, selected the MD5 file, and pushed start. Again, this is where I got stuck. It just hangs on Nand write start. I've tried this twice now, and it gets stuck at the same stage (about 90% finished)
I have no idea what to do now and really need help. I'm not a total n00b, or at least I thought I wasn't, but I seem to have gotten in way over my head. What should I do?
Edit: see you tried already...
Sent from my GT-N7000 using xda app-developers app
This is classical case of super brick.
You should not hav to wipe on ics. I think u must be on stock kernel. Every corner you may see warning, wiping and reset on ics can brick device, but its unfortunate you didn't notice it.
Anyway check your flash counter is zero and send it to service.centre to claim ur warranty.
If u running out of warranty, fing.a link for 'how to revice bricked note from my signature. And try it.
Edit : i wud like to know, as you said u went to cwm recovery, so at the time of wiping you wr on which kernel?
Sent from my GT-N7000 using xda premium
purple zebra said:
Hi all, I could really really use some help.
Today I decided to try and flash CM9 RC2 and I seem to have messed up big time.
I startred by rooting, using Dr Ketan's guide. That all went smoothly, and root was working.
I put the CM9 zip file on the SD card, turned off my phone, got back into CWM recovery, and most tutorials recommended, selected full data wipe... this is where something seemed to go wrong. While perfoming the data wipe, it seemed to freeze. I let it sit for a while, hoping it would sort itself out, but it didn't, and then it rebooted itself and went into a boot loop.
I can't get back into recovery mode, but I can get into download mode. So I thought the best thing to do would be to flash a stock firmware using odin.
I downloaded the latest german LRG firmware (which I was on before I started) from Sammobile, connected my phone to odin, selected the MD5 file, and pushed start. Again, this is where I got stuck. It just hangs on Nand write start. I've tried this twice now, and it gets stuck at the same stage (about 90% finished)
I have no idea what to do now and really need help. I'm not a total n00b, or at least I thought I wasn't, but I seem to have gotten in way over my head. What should I do?
Click to expand...
Click to collapse
Hi Bud,
From your predicament, first let me tell you what you have done wrong.... You mentioned you're in LRG Rom already and you wanted to flash CM9 after that.... right?
Well, I guess the process you did was totally wrong. You have to download stock GB N7000(from Dr. Ketan's thread) and using that stock GB Rom, that is the time you can install AbysNote kernel to root and install CWM on your phone. Now after that, download mobile ODIN (from google playstore) and flash the CM9 from there.
THAT's the one you should have done before. Remember, there are no easy way of jumping ROMS especially if your already in ICS... IF YOU WANT TO FLASH TO ANOTHER ICS ROM.
My rule of law would be to downgrade first to STOCK GB and from there, ROOT, install CWM and mobile ODIN and that'll be the time you can flash already to the new ICS ROM of your choice.
So here's what your going to do. Since your still able to boot in download mode, Download any stock GB ROM and flash it using PC ODIN. After that, seee if you can bootup your Note already to STOCK GB ROM. If and If you are able to already, then download a clean kernel preferably Abyss Kernel and flash it with your STOCK GB so that you can gain root and have CWM installed. From there, download Mobile Odin pro and flash the CM9 (that you ultimately want to be installed on your Note)
Hope everything's going to be fine and Good luck bud! :fingers-crossed:
Cheers!
Hello, I know its been several days, but I just wanted to update on the situation.
Thank you SO much to Dr.Ketan for pointing me in the right direction. A combination of these 2 guides (http://forum.xda-developers.com/showthread.php?t=1661590&page=2 http://forum.xda-developers.com/showthread.php?t=1667886) has managed to help me repartition my internal memory and get up and running again. I've got a stock gingerbread rom running, and all seems to be well.
I realise I was very stupid to do a wipe on an ICS kernal. I read about the problem for 1 particular Kernal back in may, and hadn't read the updates since, and so didn't realise it effected EVERY ICS kernal since then. It's my own stupid fault for not re-reading the warnings. Let this be a lesson kiddies, a little bit of knowledge is a dangerous thing.
Again, thank you so much for the help, to all involved, you are an asset to the community!
Related
Hi all,
I upgraded to Gingerbread and Juwe's ROM last night and all went well. That is until today when I ran the script to convert the filesystem to ext4. It rebooted into CWM and all seemed to go well except my phone is now stuck in a boot-loop. It gets as far as the initial "Galaxy S GT-I9000 Samsung" screen and then restarts to it every few seconds.
Background:
I followed the instructions as given in Juwes thread. Initially flashed XWJVB XEE firmware with bootloaders from this thread (this exact firmware I think) with re-partition,etc checked. After that I flashed CF-Root-XW_XEE_JVB-v3.1-CWM3RFS (no-repartition) and flashed ROM. ROM was working perfectly till I ran ext4.
Does anyone know of any way to fix this problem? I can boot into Download mode and CWM Recovery v3.0.0.5. I'm trying to avoid reflashing the ROM but if I can't get a solution soon I guess I'll just have to do that
Hmmm,
Are you able to get into recovery or download mode?
Edit: Just noticed you can.
Another question,
What did you use to convert to ext4?
Did you install Chainfire's ext4 addon?
electrotune1200 said:
Another question,
What did you use to convert to ext4?
Did you install Chainfire's ext4 addon?
Click to expand...
Click to collapse
Ya it's Chainfire's ext4 addon I used. Although it's just occurred to me that I think I used the one packaged with the ROM instead of the newest one from Chainfire's thread. Could it be an older version?
Yeah I really don't know about that. When we get the phone sorted, I would install his most recent addon to see if that's the issue.
As far as I know, you may only have 2 options.
First, you can try to do a factory reset in CWM.
If that fails, I'd start from the beginning, flashing with a 512 pit and re-partion.
electrotune1200 said:
Yeah I really don't know about that. When we get the phone sorted, I would install his most recent addon to see if that's the issue.
As far as I know, you may only have 2 options.
First, you can try to do a factory reset in CWM.
If that fails, I'd start from the beginning, flashing with a 512 pit and re-partion.
Click to expand...
Click to collapse
I was afraid you'd say that. Just got the phone setup as I wanted it
Just tried the factory reset in CWM and no joy. Guess I'll re-partition when I get home. Should probably be doing some work at the moment anyway
Sorry man,
Next time, set everything up after you convert it to ext4. Might save you another headache.
Also, make sure you have some free space on your internal sd card. I try to leave 1.5gb free for file system conversions.
Oh and,
get some work done already
Before you go and flash everything again.
Try flashing Chainfire's 3.1 kernal again. It might pull it out of the boot loop. Worth a shot though before starting all over.
Hopefully it works out for you without starting all over.
I tried reflashing the kernel but no joy. Just went with the complete reflash in the end. Was painless enough because I had everything set up to go from the night before
Thanks for all the help electrotune! Appreciate it
Hello everyone.
For a few days I've been having an annoying issue with my SGS.
For months I've been flashing many ROMs, especially ICS ones, and I never had any problems when I followed the instructions.
But since last tuesday, I regularly get bootloops with no reason. An hour ago, I flashed Gummy 1.2 on my phone, set everything up, configured my account and everything else. Then, I put one of the latest builds on my phone, tried to reboot to recovery as usual, but it began to bootloop. I didn't flash anything new for it to happen, and I can't seem to get why it does it.
I can't access to Recovery (freezes at kernel startup screen), only to Download mode. This means I have to reflash GB with Odin everytime it happens, then CM9 back, and then a custom ICS.
It never happened before tuesday, and it seems recurrent now, no matter what ROM, Kernel or Modem I use.
I've had my phone for almost two years, is it getting used up?
I'd appreciate if somebody could help me!
Have you tried a complete wipe including format internal sd? Then flash fresh gingerbread base.
Slim 4.2_Semaphore 1.2.5s_Cobalt Theme
If you lose recovery flashing the Odin semaphore kernel usually does the trick
vanisleryan said:
Have you tried a complete wipe including format internal sd? Then flash fresh gingerbread base.
Click to expand...
Click to collapse
Not really sure it would work..
slaphead20 said:
If you lose recovery flashing the Odin semaphore kernel usually does the trick
Click to expand...
Click to collapse
Yeah, I also think that'll do the trick if it happens again. But i'd rather prevent it than fix it every time. Thanks anyways
You could try flashing back to gb using my recovery kit, see if it helps, in the zip is all you need
Ezodin
Ezbase jvu ROM
Cf root kernel
Pit
Instructions with diagrams!
Here's link to it
http://db.tt/MOGZx01S
slaphead20 said:
You could try flashing back to gb using my recovery kit, see if it helps, in the zip is all you need
Ezodin
Ezbase jvu ROM
Cf root kernel
Pit
Instructions with diagrams!
Here's link to it
http://db.tt/MOGZx01S
Click to expand...
Click to collapse
Thanks mate, really, but I have no problem flashing back to GB.
My issue is that i'm getting Bootloops without any reason.
Flashed Gummy 1.2 back, no problem since yesterday, recovery's clean for now.
Sent from my GT-I9000 using xda app-developers app
Little "update". So far so good since yesterday, but could it be kernel-related?
Every time I had this issue, I ran Semaphore 1.2.2s.
Anyways, thanks a lot for trying to help me, I appreciate it, and if it happens again, be sure I'll try what you told me
Hello, i have had my galaxy note for a couple of weeks now.
bit of this and that, you know how it is, flashing a few roms, checking things out, keeping it safe and stuff.
idiotic of me, didn't do a backup.
now
everything was working perfectly fine.
'till i decided to put some music on my sdcard
so i shut the phone down, open it up, take out the battery, take the sdcard, put it in pc, put some music (music i had on it before, so the files could've somehow magically ****ed up the device) then but it back on.
ever since, my device won't boot, it will go to CWM recovery, it will go to download mode, but not like, properly boot. all it does is show the Samsung Galaxy Note N7000 thingie, then screen goes black, and back again to Samsung Galaxy Note N7000, then black again, over and over again.
i figured, it must be something wrong with the bootanimation, had a custom one put there, so i deleted it, cuz that way it goes back to stock.
did that, didn't help, same thing.
then, decided to flash the rom again, even tho it was working perfectly for a few days now, (stock 4.0.4 deodexed zipaligned with hydracore safe kernel)
reflashed, didn't help, nothing happened.
things were weird, i thought i should go back to a GB rom, that always...fixes the problem.
tried to flash with ODIN, stuck at factoryfs, when i pulled the cable out, it would tell me the thingummyjig with firmware update has encountered an issue please bla bla kies.
then, I EVEN TRIED the kies, it won't connect, even tho my drivers are right, and i used kies with it before.
NOW, i thought to myself, ****, the phone won't go to recovery anymore, won't boot normaly, just in download, well, download a speedmod kernel which is safe and flash it, that should give you a CWM and safe kernel to flash from
did that, worked.
flashed the stock 4.0.4 rom again, then flashed philz latest kernel for the rom, and i'm back to square one.
nothing changed, i still can't use my note.
WHAT. DO?
right, well, i tried flashing alliance rom, and it gets stuck at mounting partitions....
the blue bar goes on and on till it gets out of the designated loading space
i can't wipe cache, i can't wipe dalvik, it just gets stuck.
Etnoscope said:
... tried to flash with ODIN, stuck at factoryfs ...
Click to expand...
Click to collapse
I just quoted the bad line in your post. This is a strong indicator that you have a bricked device.
So you should try to install a different stock GB or ICS Rom with Odin again. If it stucks there again: bricked.
Then you can try to use the workaround described in hg42's thread with repartition. Or send your device for a motherboard replacement to Samsung.
hg42 has a partition scanner which allows to check for emmc problems. Try this.
ThaiDai said:
I just quoted the bad line in your post. This is a strong indicator that you have a bricked device.
So you should try to install a different stock GB or ICS Rom with Odin again. If it stucks there again: bricked.
Then you can try to use the workaround described in hg42's thread with repartition. Or send your device for a motherboard replacement to Samsung.
hg42 has a partition scanner which allows to check for emmc problems. Try this.
Click to expand...
Click to collapse
Thing is, phone worked flawlessly before, safe kernel,could flash anything,then this just happened....
Phone doesnt have warranty, sending it to some service would only have me end up with extra costs for putting the motherboard there, which i can do myself
right, welll
i tried flashing speedmod kernel with odin, it worked.
then i tried installing a GB rom via CWM
works well till it gets stuck at flashing modem.
what does this mean?
Etnoscope said:
...what does this mean?
Click to expand...
Click to collapse
As I wrote before: possibility that you have a bricked device.
Why don't you try the partition scanner or why don't you try to flash a stock GB and check if you get stuck again with factoryfs.img.
As long as you try different things without a "plan" what you want to test you'll get nothing in the end.
ThaiDai said:
As I wrote before: possibility that you have a bricked device.
Why don't you try the partition scanner or why don't you try to flash a stock GB and check if you get stuck again with factoryfs.img.
As long as you try different things without a "plan" what you want to test you'll get nothing in the end.
Click to expand...
Click to collapse
tried flashing a stock gb with odin (tried 1 file in pda before, now i tried with 3 files(modem, rom, csc), same thing happened.)
stuck at factoryfs again
i didn't want to get to the partition scanner yet, wanted to clear out any other possibility first, using the scanner as a last resort.
what about pit files?
***
also, i really wanna thank you for showing some interest in my issue, means a lot to me, just wanted to let you know i really appreciate it, and i acknowledge the fact that you're a good, helping member.
thanks bro, you're awesome.
If you have tried also with the correct original pit, then it's time for the scanners to do its job
nokiamodeln91 said:
If you have tried also with the correct original pit, then it's time for the scanners to do its job
Click to expand...
Click to collapse
right
so, i've checked out this thread, about the pit method, and after i opened the emmc_find_brick_start.zip, it started scanning normally, and it finished without being stuck anywhere, and then at the end it said scanned 15027 MiB = 15757 MB completed --> OK then the ---end thingie and done.
so the brick start isn't there, which i assume means my phone is NOT bricked, at least not by the emmc thingummyjig
but if so, what the hell am i to do? like really?
tried flashing gb with cwm, stuck at flashing modem
tried flashing gb with odin, stuck at factoryfs
what the ****?
Get the pit file from this thread
http://forum.xda-developers.com/showthread.php?t=1424997
Then flash the GB rom using pc odin. Make sure pit is selected and the repartition is ticked.
Also if you still have access to cwm try to install a CM10 rom first before trying out the above method.
SOOOOO
bit of an update.
right, after the whole emmc scanning brick mbs and stuff, decided to try and flash allianceROM 4.0.4 final
did it, worked, the flashing.
now i'm stuck at a non blinking, non changing non nothing, Smasung Galaxy Note GT-N7000 screen, with the yello jello triangle, same as before, but its not blinking now.
Ok. Try booting into recovery and performing a full wipe.
nokiamodeln91 said:
Ok. Try booting into recovery and performing a full wipe.
Click to expand...
Click to collapse
full wipe means:
factory reset
wipe cache
wipe dalvik
reboot.
right?
did that, as soon as i hit reboot, it got stuck again there, the frozen CWM screen.
battery in/out, back to square 1
Still try a cm rom as it's small in size and easier to download. CM10.1 flash from recovwey
nokiamodeln91 said:
Still try a cm rom as it's small in size and easier to download. CM10.1 flash from recovwey
Click to expand...
Click to collapse
official 4.2.1 will do?
Yeah
nokiamodeln91 said:
Yeah
Click to expand...
Click to collapse
any way we could talk via IM?
would be much better conversation-wise
We could but where I am, it's 4 am. And I will be off to sleep in a while. Hehe
nokiamodeln91 said:
We could but where I am, it's 4 am. And I will be off to sleep in a while. Hehe
Click to expand...
Click to collapse
i get status 7 error when i try to flash a CM rom btw, i know what to do, updating philz kernel as we speak
i want you to know i really appreciate this bro, couldn't have come so far without you. thanks a lot man.
right, well, i was using kangbang kernel, tried to install the cm rom, and it gets stuck at installing update...
been there for too long now,so i guess thats a safe bet.
gonna try with a different cm rom
right, well, apparently anything i try to flash gets stuck at installing update....
any solutions?
When my phone boots it only gets to the samsung logo
I am able to use the recoverymode and downloadmode.
Wiping data won´t work. Wiping cache works.
Can´t flash a CustomROM from my SDcard through CWM
I was able to connect my phone to the PC. ADB finds the phone but adb shell won´t work. (No such file or directory <2>)
How can I install either a regular Androidversion or a CustomROM now.
found this but only for Galaxy S3, so the files won´t help me
http://forum.xda-developers.com/showthread.php?t=1840030
Hope you can help me
Tobias
Download a Stock Rom from sammobile.com or one of the prerooted Roms (I always use a GB LC1 from bodivas for this) and install it with the PC version of Odin.
tried that, Odin stops at "NAND write start!!"
AW: Softbrick N7000 Need Help
What Rom did you have and what did you do before this happened?
Sent from my GT-N7000 using xda premium
Now I used a regular Android 4.0.4. ROM
Before that I tried with a 2.3.1 ROM. This is probably the reason for the trouble, isn´t it?
Tobias H. said:
tried that, Odin stops at "NAND write start!!"
Click to expand...
Click to collapse
I wrote to download a new rom and to try it with Odin. 15 min later you said: did this.
So I want to ask: Did you really download a new Rom or did you use one you had already?
And what Rom exactly?
And what did you do before stopping at boot logo?
ThaiDai said:
I wrote to download a new rom and to try it with Odin. 15 min later you said: did this.
So I want to ask: Did you really download a new Rom or did you use one you had already?
And what Rom exactly?
And what did you do before stopping at boot logo?
Click to expand...
Click to collapse
I was already downloading the 4.0.4. ROM. Because I read somewhere it´s not possible to go from ICS to Gingerbread.
The download just finished right after you answered and I tried. I am 100% sure i got the right ROM.
Before getting all these Problems, I wanted to get a CustomROM on my phone. Android 4.0.4 was installed at that point of time.
I rooted my phone and did a backup with CWM. Then i chose wipe data, while doing that I started to charge my phone (I don´t know if that matters). I didn´t see what happen exactly because i wasn´t looking at my phone all the time, but when i looked at it again there was only the charging sign shown. Then I tried to get into recoverymode again. This wouldn´t work. I tried to flash CWM with Odin which worked after some time. Then I tried to Wipe data and cache again. wipe data wouldn´t work. Wipe cache worked. I tried to install the backup. After waiting for more then 1 hour it looked like nothing happend and the installation was stuck. But the regular recovery of Android was installed.
Because flashing a ROM through CWM wouldn´t work, I tried to flash it through Odin. First time I tried with a Gingerbread Version. I was thinking, I don´t care which version as long as it works and try again to install a CustomROM from there on. Odin stopped at NAND Write Start!!. Tried it with the ICS Stock version. Same thing.
This is where I am at now
Did you use cwm.zip?
To use with Odin? No
When I started it from the regular Android Recoverymode? Yes
Don´t you think this might be exactly the problem I have?
http://forum.xda-developers.com/showthread.php?t=1840030
Tobias H. said:
I was already downloading the 4.0.4. ROM. Because I read somewhere it´s not possible to go from ICS to Gingerbread.
The download just finished right after you answered and I tried. I am 100% sure i got the right ROM.
Before getting all these Problems, I wanted to get a CustomROM on my phone. Android 4.0.4 was installed at that point of time.
I rooted my phone and did a backup with CWM. Then i chose wipe data, while doing that I started to charge my phone (I don´t know if that matters). I didn´t see what happen exactly because i wasn´t looking at my phone all the time, but when i looked at it again there was only the charging sign shown. Then I tried to get into recoverymode again. This wouldn´t work. I tried to flash CWM with Odin which worked after some time. Then I tried to Wipe data and cache again. wipe data wouldn´t work. Wipe cache worked. I tried to install the backup. After waiting for more then 1 hour it looked like nothing happend and the installation was stuck. But the regular recovery of Android was installed.
Because flashing a ROM through CWM wouldn´t work, I tried to flash it through Odin. First time I tried with a Gingerbread Version. I was thinking, I don´t care which version as long as it works and try again to install a CustomROM from there on. Odin stopped at NAND Write Start!!. Tried it with the ICS Stock version. Same thing.
This is where I am at now
Click to expand...
Click to collapse
Why did u buy SGN? To brick it?
Do you even read and search before doing something for the first time?
LOOK, READ AND LEARN THIS for stock ROMs and kernels, specialy for ICS:
- http://forum.xda-developers.com/showthread.php?t=1424997
-http://forum.xda-developers.com/showthread.php?t=1371007
-http://forum.xda-developers.com/showthread.php?t=1827394
To run ur device find something and READ.
Try leaked JB custom ROM and stock rooted kernel with safe emmc_cap_erase block (emmc bug fix) -Philz Kernel
READ and LEARN.
Have fun
P.S. Maybe you will need our friend hg42 and his famous .PIT files so here it is: http://forum.xda-developers.com/showthread.php?t=1667886
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