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
Related
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!
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 all.
I'm trying to update my phone (a rooted Samsung Galaxy S - GTi9000), to Cyanogenmod Nightly build. I have Mobile Odin and Rom Manager installed. And have downloaded the latest Cyanogenmod Nightly.
I have read some tutorials, but I seem to be stuck on two parts:
1) When I try to get into the clockworkmod boot recovery, it doesn't work and boots into the android recovery instead.
2) In mobile odin, when I find my file and load it, it doesn't load anything in the main list that says "kernel, system, dbdata", etc. It just says "none" in all of them.
From looking at some youtube vids at least some of them should load...right?
Now, I may well be doing something simple wrong (hopefully!), but I'm fairly new to all this and its kinda getting to me. Plus, trying to get my head around all the jargon is a bit of a challenge!
If someone would kindly take the time and patience to kindly guide me in the right direction, I would be very, very appreciative! :thumbup:
Also, because of these problems, I haven't tried flashing any roms yet for fear of bricking...
why you dont take cwm via 3 button combo?
there you can add zip and let it install.
Did you read any tutorial? I read about 5h and then i flashed it with problems and i knew what to do. Such questions should be answered in good ones.
Yes, I have tried the 3 button combo. But when I press them it takes me to the stock android boot recovery and not the CWM recovery.
I have Rom Manager installed, shouldn't this give me CWM recovery, or am I going about this wrong?
KieranY8 said:
Yes, I have tried the 3 button combo. But when I press them it takes me to the stock android boot recovery and not the CWM recovery.
I have Rom Manager installed, shouldn't this give me CWM recovery, or am I going about this wrong?
Click to expand...
Click to collapse
Flash a semaphore GB kernel to solve your problem from My Android Collections
Got it sorted guys.
Thankfully it was a simple fix. I removed the battery briefly earlier, but nothing happened. Took it out for a good 30-40 seconds and it finally booted into CWM Recovery!
I'm now on ICS.
Thanks a million for trying to help me.
The learning curve is beginning to flatten out!
:thumbup:
Try To reFlash
I Think that it would be best to flash the 3 odin files on again
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?
okay, first of all i will say that im sorry if what im writing is full on faulty language. enlgish isnt my best. aaaanuslut i got my brothers old gt n7000 with a broken touchpad and screen for free. i repaired that with 160€ and my brother said that the phone was rooted. i found out he had allso overclocked the device. But after a few restarts to the phone it just said something what i think was in spanish or something "bla bla bla dos sistema". After that came not your old samsung logo, but purple blueish circles just circling. Ant thats it, it would not start. So i read about bricked devices, and as much as i understood i had a soft brick. so i was looking aroun the forum for some easy fixes becasue im totally stranger to this kind of hacking. i finaly found this http://www.youtube.com/watch?v=F97qo1moAR4 and i downloaded custom jb N7000XXLSZ_N7000OPSLS6_N7000XXLSO_HOME.tar. it did work but again after i tried to restart the phone it was stuck.
So since i dont want any custom stuff i think to my self why not stock rom. so i found this http://forum.xda-developers.com/showthread.php?t=1424997. But since i dont like JB as much as ICS i will try ICS. Her is the question: i allready did the factory reset and cache wipe but this instruction says not to FROM ICS.
Warning :
Don't wipe anything from stock ICS recovery
Don't factory reset/Hard reset on stock ICS.
Don't flash any Wipe version of ICS ROM
Does that mean that i have allready gone wrong or does that mean that you have to have ICS on youre phone and then you cant do any of those things? its really confusing and i dont want to fk up my phone.
Did you make a wipe on stock ICS recovery?
zai89 said:
Did you make a wipe on stock ICS recovery?
Click to expand...
Click to collapse
My brother said that he had custom ice cream on it when i first made the wipe and tried jelly
orizont said:
My brother said that he had custom ice cream on it when i first made the wipe and tried jelly
Click to expand...
Click to collapse
can your phone boot to recovery mode now?
zai89 said:
can your phone boot to recovery mode now?
Click to expand...
Click to collapse
Yes i can
flash via recovery phils kernel, (a newer one) reboot in recovery and perform the wipe for new rom option.
That should clean your device good.
Then flash what you want. After that download an emmc check app and check. Shouldnt be needed, but its nice to check.
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
flash via recovery phils kernel, (a newer one) reboot in recovery and perform the wipe for new rom option.
That should clean your device good.
Then flash what you want. After that download an emmc check app and check. Shouldnt be needed, but its nice to check.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Allright, thankyou, since i am new to all this stuff i will try to locate a tutorial. i dont have any idea for instance, what is recovery phils kernel.
at own risk, here http://forum.xda-developers.com/showthread.php?t=1901191. Download zip, keep zipped and put on external sd. Reboot recovery and flash via install from sd option.
Since we are going to wipe latest version will do fine. However if you plan to reflash the original Samsung rom one that is same or likewise version is best to quickly root after flashing rom, so you can flash speedmod kernel (better battery life) after. Find in original dev thread of this forum.
Remember, via factory format on phills kernel recovery(reboot in recovery) you have the option to do a wipe for new rom.
Otherwise on Phills kernel recovery do factory, cache wipe. In advanced dalvik cache, in mounts all(warning take out external sd before so you dont wipe that)
Then your phone is clean, you shouldnt have to wipe efs anyway, so dont tick that option ever in pc odin when flashing rom with odin.
This is the cleanest way to get rid of All leftovers and generally the way to go before flashing any new rom. However risk of loosing photos and whatever you have not backed up. In general backing up is bad as old files/db/etc are put back (risk of unforeseen stuff happening) Check one of my 5 threads for what backups there are. Via my profile you find them
Enjoy!
Sent from my GT-N7000 using Tapatalk 2
Okay, im thankful for all this information, useful stuff, got the PhilZ-cwm6-XXLT6-XSA-5.06.1-signed.zip.
let us know how it went, ok?
OOOKAY! so i finaly did what baz77 described. and rooted with another phils kernel witch i chose after my downloaded rom. Did root it, and after powering down and waiting about 3-5 sec. i started it, and it worked, no more getting stuck on gt n7000 screen and so on. and i also downloaded emmc check app, but unfortunatley it said. Brick bug: YES. Insane Chip.
sorry for double post, how do i delete? all i can do is use edit/delete button but it only edits the post, how can i delte it?
You cant but thats ok.
all n7000 have the brickbug to my knowledge, the test should state if the bug has been triggered, if not then super, if it has, best to secure the broken emmc sectors. Tricky.
I think having it clean now should eliminate earlier issues Enjoy your n7000
Thank you, i will, lately my n7000 has been rebooting randomly, any fix or know issue why this occures?
orizont said:
Thank you, i will, lately my n7000 has been rebooting randomly, any fix or know issue why this occures?
Click to expand...
Click to collapse
not sure how that is happening. Maybe a logcat (logfiles) shows whats happening when it happens. Could be app. Maybe rom issue. Method of elimination counts here.
On safe kernel, try dalvik cache, cache wipes and fix permissions in recovery, reboot and check if reoccurs.
Otherwise, updated versions, clean install I would recommend.
You can check also before with that emmc app if there are bad sectors. I dont expect it but you never know
Okay, its been a long time since i did that stuff. And it worked allirght. i got my phone working and rooted. Great stuff here
Sorry for updating old topic. Since people who have helped me with my phone allready are familiar with my case. I was wisiting a friend of mine in england and after i returned home my phone is f**ked. Everything works okay, but when i turn on mobile data or wifi it instantly freezes. Takes about 15-20 sec. and then phone does an automatic restart which restarting gets into boot loop. I have to hold down bower button to reboot again. When it asks me for sim unlock code, i have to be quick when im inserting it because i need to turn off mobiledata/wifi as soon as ia get my phone running again, otherwise it will freeze and crash again. Can it be somekind of virus or something? Is it most likely that i have to again format and install philz kernel and all that stuff? Thanks in advance.
that would be the best way to start..IMO
I really dont have the time or opportunity to format and reflash, but i guess its really difficult, near imbossible to tell whats wrong with my samsung. Bust still, any other suggestions?