my sons sg i9000 was rooted with a custom rom but then started playing up, now when i've wiped it and tried put new rom on it, all it does it force crash everything that was existing on his phone, so it looks like it is not wiping the phone anymore for some reason, i've tried flashing rom by odin but still the same effect, is there anything out there that totally wipes the phone for sure and then will allow me to put phone back to stock and then reroot.
many thanks if anyone can help as i am totally stuck now and my son is without his phone.:fingers-crossed:
If you restock via odin, usually all datas are deleted and wipes are done.
In this thread you will find many usefull things, also slappys rescue kit, in Android rescue, Recovery Kits content, which I used often and helped me a lot of times: i9000 Rescue EzBase Rescue with CF Root & semaphore root by nitr8 & chainfire, repacked by slaphead20
btw: the problem you mention seems to me more that you probably flashed a wrong ROM, which is not compatible to your device, or something went wrong during the installation?
rodman01 said:
If you restock via odin, usually all datas are deleted and wipes are done.
In this thread you will find many usefull things, also slappys rescue kit, in Android rescue, Recovery Kits content, which I used often and helped me a lot of times: i9000 Rescue EzBase Rescue with CF Root & semaphore root by nitr8 & chainfire, repacked by slaphead20
btw: the problem you mention seems to me more that you probably flashed a wrong ROM, which is not compatible to your device, or something went wrong during the installation?
Click to expand...
Click to collapse
thank you for the advise i will try and see what i can do
still having trouble with the phone, every time i reflash stock rom with odin it keeps starting up but then i have a lot of force close box popping up saying about all his old apps and and setting force closing and then when it get to the start up wizard it says it has forced closed and then can not go any further, this is why i cant understand why when i wipe all data and system it is not wiping it for some reason,im waiting on a download recovery for it but if anyone can understand what i mean and no a fix i will be most grateful as i have spent many hours now searching through xda for a answer and can not find any.:fingers-crossed::fingers-crossed:
Could you give us some more information? What device do you have? And which ROMs did you try to flash? Which stock and which custom ROMS? And when do have the problems? After reboot from flashed stock rom or after flashing the custom rom? I think the stock rom you try to flash does not fit to your device?
i have tried the stock rom from samfirmware and my device is a galaxy s i9000, the custom rom was a old gingerbread rom, the problem comes when i have flashed the new stock rom with odin, it flashes with odin not a problem but then when it boots up and starts to go through the first 6 or 7 steps of the phones steps, ie ( keyboard use, packed data settings, wifi on or off and so on) it keeps popping up little dialog boxes saying sorry google play is not working force close and goes through a whole load of stuff saying the same thing for them all, hope this helps a little but is hard to describe
I would suggest to flash an other rom via odin. Try the rescue pack from slappy. Inside that pack, there should be a txt file, where additional infos are included how to use the different files. It could be that the sam firmware is not fully compatible with your phone or sometimes the download is corrupt or something else...
rodman01 said:
I would suggest to flash an other rom via odin. Try the rescue pack from slappy. Inside that pack, there should be a txt file, where additional infos are included how to use the different files. It could be that the sam firmware is not fully compatible with your phone or sometimes the download is corrupt or something else...
Click to expand...
Click to collapse
ok thank you i will try that,
thank you for all the help today but think the phone is knackered nothing will work anymore on it nothing will boot up properly :crying:
no problem and you welcome...better would have been if my proposals had worked...but perhaps you are right and there is a hardware defect or something else...perhaps even a fluid defect....or it is only stressed for today and tomorrow all is fine again ! So head up, and don't give up.
Hope you flashed Stock GB ROM with pit file and Re-partition ticked
Related
Apologies if this is answered elsewhere but I've been looking around the forums and a lot of information/posts from people seem to conflict or the information is only valid for X kernel or Y kernel etc and it can still be a little overwhelming even after lots of nice people have posted guides.
I bought a German Note about a month ago and upgraded to 4.0.3 through the devices own update method (I have not flashed any ROMs on this device), leaving me on XX-LPY. I have since rooted the device, and did not perform any kinds of wipes doing this, this was the only time I even used CWM, I havent booted into CWM since (or used any of the normal recovery features).
The device has been working fine for around a week, I've restarted it several times without issue. However today after restarting it gets stuck on the Samsung logo and will not boot properly. The only thing I have used root for is to uninstall Kies and the SNS Push stuff (which seemed to save me a lot of battery life) and install ad-free android. I also installed the Carbon Tweaks app and applied the Carbon Booster stuff along with the Beats Audio and Bravia Engine stuff (nothing else).
I am able to get into recovery mode however I seem to be unable to put it into download mode (Edit: finally got it to do it once, wont do it every time though) so I have a few questions:
Can anyone tell me if its ruined or why its doing this?
Is it safe to just factory reset/wipe cache through normal android recovery (not CWM?).
Is it safe to try to flash another ROM through CWM (I'm on XX-LPY) and if so which one is safe for me to flash?
Is it safe to try to flash through Odin and if so which ROM should I flash?
I really dont care about the data on it or wiping it w/e. I just dont want to turn it into a paperweight if I can help it.
Thanks
Edit: Also if it makes any difference, this is the method I used to root the device:
http://forum.xda-developers.com/showpost.php?p=20963730&postcount=3
Nope, don't go around flashing stuff with CWM on that device.Also, you can't wipe as that may trigger the MMC_CAP_ERASE causing superbrick.Judging by what you say you've done, I'd say I don't know why it happened but it isn't ruined.
You can try to flash a stock GB rom of your country by following dr.ketan's guide in the dev section and then rooting it (if you want).Alternatively,you could just take it to a Samsung service center as there is no yellow triangle.But I'd try to flash the GB rom as flashing a stock kernel via PC Odin doesn't increase the flash counter.
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!
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