[Q] Galaxy note reset issue. - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

I know this is a shot in the dark, but I would really be interested in hearing what people have to say.
I am finding that I am having issues with my Galaxy Note - the main problem being the phone getting stuck and the screen not turning on - needing a soft reset or at times, needing the battery to be taken out. This problem is despite what ever rom I am using - the issue is also with almost all kernels tried.
I did have superbrick issue and I have tried going back to the original rom with the pit method, however, no luck.
I can confirm that this is happening with ICS/GB/MUIU/AOKP roms... there seems to be no obvious solution...
Does anyone else have this problem?
What is the solution if any - its frustrating when the phone becomes stuck randomly.
Is there a rom/radio/kernel combination that's highly stable??

Your phone is probably accessing a corrupt part of your Emmc.
You will need to take out a larger part of memory using a modified pit.
See HG42's thread for information

superbrick? what's that? sorry im a newbie

eidecedie03 said:
superbrick? what's that? sorry im a newbie
Click to expand...
Click to collapse
Ha! its best you are aware of the issue - but best not to know it personally - I would recommend not to flash any roms without a good understanding of it.

eidecedie03 said:
superbrick? what's that? sorry im a newbie
Click to expand...
Click to collapse
Read up on super brick stickies and ics kernels before you go any further. Does indeed sound like you've damaged your Emmc and will need to repartition. Stock roms will likely not work anymore as you'll lose around 3gb of internal storage.
Sent from my GT-N7000 using xda premium

I did a manual check for corrupt areas and despite that, still having reset issues.
Any solutions??

Mediaserver is the culprit who try to access the bricked emmc part and get stuck there.. do freeze it and tell us the results?
Sent from my GT-N7000 using Tapatalk 2

Related

[Q] Trying to rescue a bricked Note, help is appreciated!

I have a note here...its bricked, the owner tried flashing angelrom ICS, and bricked it.
It gets stuck when it starts writing factoryfs.img.
I have tried properly repartitioning it, installed a stock bootloader from a gt-n7000 stock rom, and that at least allowed me to get back into android system recovery. I wiped the data and cache and tried again.
I tried a stock rom that had multiple parts, and one that had the individual parts. I can flash all of the individual parts successfully but the PDA.
Anybody encounter this, and know a fix? I would really appreciate any tips or suggestions.
Just wanted to give some more information. I followed Ketan's guide to flash to stock rom, and tried multiple stock roms with the same results.
So I also tried repartioning with the proper pit file (the 16gb n7000) and that didn't work.
The only bootloader I could seem to find (because that was the next logical step to me) was "KERNEL_N7000XXKJ1_CL627135_REV02_eng_mid_ship.tar.md5" , would that be compatible with all stock roms or just a specific one?
I am sorry bro. You fried your flash drive, there is no way to revive it. The motherboard has to be replaced.
There isn't anything one can do if you flashed that kernel. If you have warranty head to Samsung service.
Yep, anilisanil is right. People who had found themselves in the same predicament tried absolutely everything, but there was no cure whatsoever. Data partition corrupted beyond repair, not even JTAG could help.
Motherboard replacement is the only thing that can be done.
anilisanil said:
I am sorry bro. You fried your flash drive, there is no way to revive it. The motherboard has to be replaced.
Click to expand...
Click to collapse
chasmodo said:
Motherboard replacement is the only thing that can be done.
Click to expand...
Click to collapse
+1
Sorry, it seems You have no option but to go service centre.
chasmodo said:
Yep, anilisanil is right. People who had found themselves in the same predicament tried absolutely everything, but there was no cure whatsoever. Data partition corrupted beyond repair, not even JTAG could help.
Motherboard replacement is the only thing that can be done.
Click to expand...
Click to collapse
How the duck is that physically possible? What an enormous embarrassment for angelom. I doubt hell ever post another kernel again...
Sent from my superior GT-N7000 using Tapatalk
Yeah...I figured it was beyond hope after reading through a lot of the threads....
I did reset the counter with a jig, and took away the yellow triangle...but I was told samsung won't warranty this model in the USA.
Thanks for your replies!
Just a little query. Whats the actual physics behind this? Like how can some software fry the drive? Just a little interested and wondered how it actually physically happened. Because my assumption before all this was that it cant be truly completely bricked (obviously i was wrong). but wondering how!
Sent from my GT-N7000 using Tapatalk

[Q] Super Bricked Gnote Revived But Lost Memory

Hello Dear friends,
This is Alvina Snow, a nooby nooby noob girl, who once liked to play with phones and would make fun of her buddies, carrying the stereo-typed GB versions on thier Note. I am no more interested in flashing Roms and not because i blame developers. They have always been great in thier job and i owe them for their coolest roms, but i blame myself and my hastiness in everything. Cutting the crap, let me come to the point.....
Last night, tired of the mediocre looks of Official ICS, i downloaded Paranoid Android 0.4a along with goodies and following the instructions, I opened Odin to downgrade to GB so i can install PA 0.4a safely. To my surprise, once the GB Rom installed successfully, it got stuck at bootloader, i rebooted it a few times, then i went to recovery and reset factory/ format, wiped cache and rebooted. Note stuck this time on the first screen. :fingers-crossed:
Presuming that Odin install may have been faulty, i redid the Odin method and this time, the install stuck at "factoryfs.rfs". From then on, i tried for hours to make it happen, swapped roms, used kernels, wiped everything... and ultimately i got a nice super brick on my hands. the notorious mobile-cum-triangle-cum-PC sign, asking me to use recovery through kies.
researched XDA all night and finally landed on Dr. Forest's "Easy guide for repartition workaround to fix super-brick Note"
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Did everything as directed. I used "standard 16 GB pit" and stable GB rom to resurrect my Note and we both came to life to my surprise, only to discover that now i have an 8.24 GB emmc space available, instead of previously held 11.4 GB something. :victory:
I have been praying for Dr. Forest and all esteemed developers and i will always be thankful to them. My questions to my learned seniors is that:-
- Is there any method, adopting which the missing 3 GB should be regained?
- Will I ever be able to regain the missing 3GB space?
- Having this notion in mind that now i have caged 3 GB of voracious malfunctioning space in my emmc, should i expect any further stability issues after revival of Note or it should work just fine.
Once again hats off to Dr. Forest and all other developers for thier compassionate assistance for us noobs. My thanks in advance for help. :angel:
-
alvinasnow said:
Hello Dear friends,
This is Alvina Snow, a nooby nooby noob girl, who once liked to play with phones and would make fun of her buddies, carrying the stereo-typed GB versions on thier Note.
Did everything as directed. I used "standard 16 GB pit" and stable GB rom to resurrect my Note and we both came to life to my surprise, only to discover that now i have an 8.24 GB emmc space available, instead of previously held 11.4 GB something. :victory:
I have been praying for Dr. Forest and all esteemed developers and i will always be thankful to them. My questions to my learned seniors is that:-
- Is there any method, adopting which the missing 3 GB should be regained?
- Will I ever be able to regain the missing 3GB space?
- Having this notion in mind that now i have caged 3 GB of voracious malfunctioning space in my emmc, should i expect any further stability issues after revival of Note or it should work just fine.
Once again hats off to Dr. Forest and all other developers for thier compassionate assistance for us noobs. My thanks in advance for help. :angel:
-
Click to expand...
Click to collapse
Thanks for the kind words which is a lovely reward to the people who contribute time and knowledge to the guides to help revive brick G-Note, including me :victory:!
I will try to answer some of the questions:
1- So far there has not been a known method to fix the faulty areas in the partition caused by the buggy ICS kernel yet. There seem to be some encouraging news from some senior developers who are in contact with Samsung developers and it is hope that there may be a Jtag method release. If the method is available then your device can also benefit from it since the re-partition is fully reversible. Let's just hope they can make it.
2- Will the phone be stable or not: for most people it seems to work well and stable. For some people who have a large damaged areas of space in former sdcard region due to the bug, there seem to be some problem of unstable system. In those cases it is likely that there are still some faulty blocks somewhere in cache or data partitions that has not been eliminated yet.
3- If you are comfortable with using adb method you can try again to explore the lost areas and in some cases can regain 1 or 2 GB of space. There is a free app call "eMMC Brickbug Check" from Gplay which can help to scan the whole chip and report the beginning of faulty blocks. Then you can use parted to make partitions in different areas within the lost range (from 281mb to 3322mb) while try to avoid the faulty blocks.
Hope it helps in some ways. cheers.
Thanx a Ton
Ex expected you came to my rescue and encouragement Sir Forest. . Thanx a million for taking time to answer my queries. I hope that Samsung will soon come up with some remedy. As advised by you, i will also try to use the regain method. Though am not sure
Thank you
forest1971 said:
3- If you are comfortable with using adb method you can try again to explore the lost areas and in some cases can regain 1 or 2 GB of space. There is a free app call "eMMC Brickbug Check" from Gplay which can help to scan the whole chip and report the beginning of faulty blocks. Then you can use parted to make partitions in different areas within the lost range (from 281mb to 3322mb) while try to avoid the faulty blocks.
Click to expand...
Click to collapse
Forest Sir, as you advised i used eMMC Brickbug Check", which says that:
Phone Model: Samsung GT-N7000
eMMC Chip
type: VYLOOM
Date: 03/2012
CID:15010056594c30304d19b9c9013c3fdd
FwRev: 0x19
Brick Bug? : YES. Insane Chip
Now when i check memory.. it started checking and showing something similar to seconds counting and the phone restarted after reaching 671 seconds..
Now pardon my noobness, but i am not clear if how am i gonna get help in determing defected areas out of this.
Help please. God Bless You
alvinasnow said:
Forest Sir, as you advised i used eMMC Brickbug Check", which says that:
Phone Model: Samsung GT-N7000
eMMC Chip
type: VYLOOM
Date: 03/2012
CID:15010056594c30304d19b9c9013c3fdd
FwRev: 0x19
Brick Bug? : YES. Insane Chip
Now when i check memory.. it started checking and showing something similar to seconds counting and the phone restarted after reaching 671 seconds..
Now pardon my noobness, but i am not clear if how am i gonna get help in determing defected areas out of this.
Help please. God Bless You
Click to expand...
Click to collapse
No, not yet all. In this case it does not allow to see where the faulty block is.
If you are confident and like to play again with adb then can explore using parted to create new partitions again in different ranges, with part 9 starting from 1174mb, and then move up by 300mb each time until parted is happy with the new area for part 9. with that approach you will probably save more space.
Otherwise, a external sdcard can also compensate more than all the loss of space in the internal sdcard . cheers.
Thank You Sir Forest for ur guidance. I think its time to get me a 32 GB micro sd
Amen !! I only use my internal SD to hold my Mods and ROMs, all the precious stuff is on the external, Just incase.
Plus i have dropbox and google drive to keep my stuff regularly backed up
azzledazzle said:
Amen !! I only use my internal SD to hold my Mods and ROMs, all the precious stuff is on the external, Just incase.
Plus i have dropbox and google drive to keep my stuff regularly backed up
Click to expand...
Click to collapse
Yea Sir, after getting bricked, I know realize its the best way to handle the unseen
Long Live my Seniors... Owe you people very much.:good:
alvinasnow said:
Thank You Sir Forest for ur guidance. I think its time to get me a 32 GB micro sd
Click to expand...
Click to collapse
If you get that 32GB micro-SD, you can use it as your phone's internal SD card with an easy vold.fstab swap. Your reduced capacity internal storage would then become your "external" SD card.
Sent from my GT-I9300 using XDA Premium HD app
Mister_Mxyzptlk said:
If you get that 32GB micro-SD, you can use it as your phone's internal SD card with an easy vold.fstab swap. Your reduced capacity internal storage would then become your "external" SD card.
Click to expand...
Click to collapse
:victory: Ahaa. Another good news after being delved in miseries for a full day. Let's google the Vold.fstab Swap.
Thank you Mister Mxyzptlk
My Options.
Considering my options, I got few questions in my mind...
a. My Note is International version and purchased from KSA, whereas I am in Pakistan now. So can I claim my warranty here with Samsung Service Centres?
b. If yes, I obviously need to reset my binary counter, which is 4 or 5 at the moment. I also need to restore my Note to stock rom and stock kernel. Is there any safe way except Angelo's kernel and USB Jig to reset binary counter? i was looking for "Triangle Away" in the market, but i somehow couldn't find it.
Help my seniors please. If with your help I can go to Samsung and my warranty is validated, all credits with be to you guys for saving me from big troubles. To be honest I had been a poor kinda girl and managed barely to pull off my Note. I can't afford to manage a board replace night now
Hi: I do not have answers to all questions, but for triangleaway.
you can file a free and paid version of your choice:
http://forum.xda-developers.com/showthread.php?p=22463153#post22463153
https://play.google.com/store/search?q=triangleaway&c=apps
cheers,
Thank You Sir, Forest. Hope this would work
Of you've repartitioned the note that will void your warranty I imagine.
What you really need is an untouched superbrick as Samsung won't be able to tell if it has any hits on the binary counter or if its ever been rooted or custom firmwares flashed...
So brick it again if you are able to claim warranty in Pakistan.
Sent from my GT-N7000 using xda premium
SpyderTracks said:
Of you've repartitioned the note that will void your warranty I imagine.
What you really need is an untouched superbrick as Samsung won't be able to tell if it has any hits on the binary counter or if its ever been rooted or custom firmwares flashed...
So brick it again if you are able to claim warranty in Pakistan.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
So, bricking its again seems a potentially dangerous job :fingers-crossed: besides what do you suggest, i should tell Samsung guys, how it happened. Coz i believe they are gonna ask me if how come the phone went dead and i have also learnt that they have ways to check binary count, even if the phone is Superbricked. I am in a fix, coz after investing 500$ on a Note, living without a 3GB phone space is pain in the a*s.
Help please
alvinasnow said:
So, bricking its again seems a potentially dangerous job :fingers-crossed: besides what do you suggest, i should tell Samsung guys, how it happened. Coz i believe they are gonna ask me if how come the phone went dead and i have also learnt that they have ways to check binary count, even if the phone is Superbricked. I am in a fix, coz after investing 500$ on a Note, living without a 3GB phone space is pain in the a*s.
Help please
Click to expand...
Click to collapse
The brick has been acknowledged by samsung, they've admitted it can happen on fully stock uprooted firmware update over kies. That's all you say, you were updating through kies, it failed and you're bricked. They can't check binary count under super brick because it's not possible to enter download mode therefor impossible to get any data or connection off the device. Simple.
Sent from my GT-N7000 using xda premium
SpyderTracks said:
The brick has been acknowledged by samsung, they've admitted it can happen on fully stock uprooted firmware update over kies. That's all you say, you were updating through kies, it failed and you're bricked. They can't check binary count under super brick because it's not possible to enter download mode therefor impossible to get any data or connection off the device. Simple.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Well Dear spyderTracks, it confuses me further to think whether i was superbricked at all? coz i could go to recovery and could also go to download mode. as far as i know, u r super bricked if ur phone does not installs any rom and through odin, the rom installation stucks at factoryfs. please correct me if am wrong.
thanx for ur time.
alvinasnow said:
Well Dear spyderTracks, it confuses me further to think whether i was superbricked at all? coz i could go to recovery and could also go to download mode. as far as i know, u r super bricked if ur phone does not installs any rom and through odin, the rom installation stucks at factoryfs. please correct me if am wrong.
thanx for ur time.
Click to expand...
Click to collapse
No, that's correct. Usually it disables download mode also, my apologies.
Sent from my GT-N7000 using xda premium

[Q] Galaxy Note Corrupt Processor

I've just got my processor replaced by Samsung. Apparently according to the technician the processor is corrupted. Mine me it cost me almost USD 250 to replace it because the phone has been rooted so its not covered under warranty. I've rooted my phone, flash some kernels (Abyss and latest Franco Kernel) a few times and changed several ROMS (Kingdroid, ROCKETROM). I've no idea how to processor can be corrupted but according to the technician because when i rooted it i deleted some files cause the processor settings to malfunction and therefore processor got corrupted. I' pretty sure i did not deleted any files from the root folders. Can someone please explain to me the truth behind what the technician said. I believe its a whole lot of gibberish. I believe i should be able to change ROMS and Kernels as i please but i really don't want to spent another USD 250 to replace another processor after i changed ROMS or Kernels. Please advise.
michaelw1979 said:
I've just got my processor replaced by Samsung. Apparently according to the technician the processor is corrupted. Mine me it cost me almost USD 250 to replace it because the phone has been rooted so its not covered under warranty. I've rooted my phone, flash some kernels (Abyss and latest Franco Kernel) a few times and changed several ROMS (Kingdroid, ROCKETROM). I've no idea how to processor can be corrupted but according to the technician because when i rooted it i deleted some files cause the processor settings to malfunction and therefore processor got corrupted. I' pretty sure i did not deleted any files from the root folders. Can someone please explain to me the truth behind what the technician said. I believe its a whole lot of gibberish. I believe i should be able to change ROMS and Kernels as i please but i really don't want to spent another USD 250 to replace another processor after i changed ROMS or Kernels. Please advise.
Click to expand...
Click to collapse
If you have ever flashed a ICS rom which didn't have a safe kernel and made a factory reset,there are chances of your getting super bricked.As to confirm that,switch on your phone and see if it gets past the splash screen.If doesn't,its 50% confirmed.
Next is to boot into download mode and flash some rom with Odin.If it gets stuck at factoryfs,its confirmed.Please do note that it may take 10mins to flash factoryfs.If it take longer than 15mins,I'm sorry you have super bricked.
There are guides in general section to revive it.you could refer that if you need
Sent from my GT-N7000 using xda app-developers app
corrupt processor.. ? not sure what he meant by that... u should have asked to give the more info as in if it was an emmc chip issue...
if that was the case possibly a wipe on stock kernel mite have caused it and they mite have changed the motherboard.. which costs around that kinda money if not under warranty.
When i asked him all he said "u rooted ur phone. You could have erase some processor setting files..so processor malfunction therefor corrupted so no warranty". He did gave me back the motherboard though. of course since the motherboard and processor is a single piece therefore the replace it. But till now i still dont know how that happens or what i did might ha e lead to this when i asked the tech he said dont root your and i was lile "duh"
hmmm... not root an android.., its like keeping all the goodies in a locked room... but personally i have not encountered any such problem till now,,, i have unrooted and rooted the phone so many times..
may be a bad move mite have caused it
I guess you had done a wipe on an unsafe kernel which lead to a super brick
I too had the same experience but luckily got it replaced under warranty
He he .. U lucky guy.
Sent from my GT-N7000 using xda premium
After days of searching and googling i believe like some more experienced users here said i might have caught the bug. But what i dont understand is i've also reflash the kernel to Abyss 4.2 kernel that changed my initial affected Kingdroid Rom to Rocketrom in hope to solve the problem, but unfortunately that didnt work. So basically if so unfortunately it happens to me in the future again, i guess ill just have to unroot and rrset the.binary counter..but by then the warranty might have expired already.
Sent from my GT-N7000 using xda premium[/QUOTE]
michaelw1979 said:
After days of searching and googling i believe like some more experienced users here said i might have caught the bug. But what i dont understand is i've also reflash the kernel to Abyss 4.2 kernel that changed my initial affected Kingdroid Rom to Rocketrom in hope to solve the problem, but unfortunately that didnt work. So basically if so unfortunately it happens to me in the future again, i guess ill just have to unroot and rrset the.binary counter..but by then the warranty might have expired already.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
[/QUOTE]
Maybe here will help you figure out
http://forum.xda-developers.com/showthread.php?t=1827394
.
michaelw1979 said:
When i asked him all he said "u rooted ur phone. You could have erase some processor setting files..so processor malfunction therefor corrupted so no warranty". He did gave me back the motherboard though. of course since the motherboard and processor is a single piece therefore the replace it. But till now i still dont know how that happens or what i did might ha e lead to this when i asked the tech he said dont root your and i was lile "duh"
Click to expand...
Click to collapse
Might relate to some kernel tweaking ... did often use processor O/C-ing???
Sent from my GT-N7000 using xda app-developers app
fr3ker said:
Might relate to some kernel tweaking ... did often use processor O/C-ing???
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Nope never oc my processor n ive always flash kernel from normal odin. Dont know how thos affected the emmc bug
Your technician is partly credible when he said you fried your procie....
perhaps he wasn't keenly elaborating it but he may have meant it to be your eMMC chip on your Note.
There are myriads of discussions already all over our beloved Note's forum regarding the eMMC chip which has most high end experts believe to be a faulty chip case and so henceforth, this chip would be toasted when a right scenario or pre-conditions are met thereof,, would trigger the superbrick bug.
Your tech guy might not be good in the right explanation of words.. but he is partly good in saying your 'procs' were fried... What I don't agree on him was that it was because 'you root' your phone... rooting does not in anyway enable the eMMc bug.... it is thru using an unsafe kernel and doing a full wipe of your phone that triggers it. Some are lucky they're not bitten first time when doing the wipe (with an unsafe kernel), few are not that lucky and the minute they wipe their device, instantaneously the bug would be triggered rendering their Note unbootable or stuck at data.img or factoryfs.img.
letters_to_cleo said:
Your technician is partly credible when he said you fried your procie....
perhaps he wasn't keenly elaborating it but he may have meant it to be your eMMC chip on your Note.
There are myriads of discussions already all over our beloved Note's forum regarding the eMMC chip which has most high end experts believe to be a faulty chip case and so henceforth, this chip would be toasted when a right scenario or pre-conditions are met thereof,, would trigger the superbrick bug.
Your tech guy might not be good in the right explanation of words.. but he is partly good in saying your 'procs' were fried... What I don't agree on him was that it was because 'you root' your phone... rooting does not in anyway enable the eMMc bug.... it is thru using an unsafe kernel and doing a full wipe of your phone that triggers it. Some are lucky they're not bitten first time when doing the wipe (with an unsafe kernel), few are not that lucky and the minute they wipe their device, instantaneously the bug would be triggered rendering their Note unbootable or stuck at data.img or factoryfs.img.
Click to expand...
Click to collapse
I have a super-bricked note too. What if I go to them with my counter reset? Will they refuse to replace my motherboard for free?
Well it depends entirely on the discretion of your SSC and the tech handling it. Normally most techs are not that stingy to repair your Note just as long as they've check your warranty and is satisfied that you really did not tinkered your phone. Just act and answer sheeply to them that you've bricked while upgrading thru Kies.
Word of advice. Never ever give yourself away... Never ever instigate in anyway to tell them first hand that you've rooted already your phone or have flashed any custom roms on it. They might think otherwise of voiding your warranty if you blurt them what you really did to your phone. Act and think plausibly.
Kapish? Ok..good.
Sent from my GT-N7000 using xda premium
letters_to_cleo said:
Well it depends entirely on the discretion of your SSC and the tech handling it. Normally most techs are not that stingy to repair your Note just as long as they've check your warranty and is satisfied that you really did not tinkered your phone. Just act and answer sheeply to them that you've bricked while upgrading thru Kies.
Word of advice. Never ever give yourself away... Never ever instigate in anyway to tell them first hand that you've rooted already your phone or have flashed any custom roms on it. They might think otherwise of voiding your warranty if you blurt them what you really did to your phone. Act and think plausibly.
Kapish? Ok..good.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I'd just tell them I've just received and OTA notification then the phone rebooted and didn't boot up again
Enviado desde mi GT-N7000 usando Tapatalk 2
kzshantonu said:
I have a super-bricked note too. What if I go to them with my counter reset? Will they refuse to replace my motherboard for free?
Click to expand...
Click to collapse
If you clrar your flash counter,they must do it under warranty
Just act like you never know what rooting is
rajsekhar.300 said:
If you clrar your flash counter,they must do it under warranty
Just act like you never know what rooting is
Click to expand...
Click to collapse
letters_to_cleo said:
Well it depends entirely on the discretion of your SSC and the tech handling it. Normally most techs are not that stingy to repair your Note just as long as they've check your warranty and is satisfied that you really did not tinkered your phone. Just act and answer sheeply to them that you've bricked while upgrading thru Kies.
Word of advice. Never ever give yourself away... Never ever instigate in anyway to tell them first hand that you've rooted already your phone or have flashed any custom roms on it. They might think otherwise of voiding your warranty if you blurt them what you really did to your phone. Act and think plausibly.
Kapish? Ok..good.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
msedek said:
I'd just tell them I've just received and OTA notification then the phone rebooted and didn't boot up again
Enviado desde mi GT-N7000 usando Tapatalk 2
Click to expand...
Click to collapse
Cool then... I'll flash angelom 1.2 kernel to reset the counter. Then take it to SSC and see what happens. Wish me best of luck pls. I miss my Gnote :crying:
kzshantonu said:
Cool then... I'll flash angelom 1.2 kernel to reset the counter. Then take it to SSC and see what happens. Wish me best of luck pls. I miss my Gnote :crying:
Click to expand...
Click to collapse
All the best:good:
@OP
don't fret, you'll get your polished Note soon with a brand new mobo inside... So it's all good bud.
there is no way to fire your processor in software level, may be oc'ng it may hurt it, but any modification in software will not affect the processor by any mean, he meant the emmc chip for sure, any way as long as you are using safe kernel, and reading before flashing, you are safe to go, and i think your processor is safe as far as you don't overclock it too much.

problems with my phone, need help

hey guys, im not your average noob but even though im not a noob i still have some learning to do... that said, i wanted to say that ive been having problems with my phone. im running utakas paranoid nov 17 nighty with hydracore v7 and what happens is that my phone randomly restarts and freezes from time to time... when it restarts, it sometimes is like a normal restart and sometimes from the boot screen (forgot what those are called). the volume too sometimes doesnt work well and have to restart it in order to work (ive installed the beats drivers, might be that) and my gallery doesnt let me view pics and vids that i just took...
i have re installed my rom and kernel, "cleaned" the device with app cleaners (even though it may or may not help), reformatted my inernal and external sd card....
is there anything i can do to make it work or could it be that my phones becoming defective? for that matter, i take good care of my phone, it hasnt gotten wet and clean out the dust it accumulates between the phone and the cover from time to time...
any help is appreciated, thanks in advance
psssst, we got a Q&A section (hint)
Why don't you flash a stock rom and kernel for a few days to see if it is really
your phone acting up, or maybe your actual rom and/or kernel, or maybe app
you installed ?
friedje said:
psssst, we got a Q&A section (hint)
Why don't you flash a stock rom and kernel for a few days to see if it is really
your phone acting up, or maybe your actual rom and/or kernel, or maybe app
you installed ?
Click to expand...
Click to collapse
sorry bout that, didnt realise i was in the wrong thread... and do i really have toooo? lol i was wanting to leave that till the end.... any other things i can check before trying that out?
Get the emmc brick bug app in the market and perform a full memory scan just to make sure your memory its alright before doing anything else
Tapatalking on my n7000
msedek said:
Get the emmc brick bug app in the market and perform a full memory scan just to make sure your memory its alright before doing anything else
Tapatalking on my n7000
Click to expand...
Click to collapse
damn! i think i do, it says "Brick Bug? YES. Insane chip." how do i fix the emmc brick bug?
It just said you have a defective chip like most of us.. Perform the test included with it
Tapatalking on my n7000
msedek said:
It just said you have a defective chip like most of us.. Perform the test included with it
Tapatalking on my n7000
Click to expand...
Click to collapse
Did that and said test was passed... what else could it be?
If passed its a good news... Just change roms maybe try another version of paranoid.. Or ask in the developer forum.. Seems like your hardware its okay
Tapatalking on my n7000
Yea like i said i try n take good care of it... it seemed like software from the beggining... kut of topic question but whats the best way on formatting my sd? Tw rom? Cm, aokp, pa rom? Or a certain app?
Before installing roms (and being sure I'm on a safe kernel) i do all wipes data/cache/Dalvik and also format data, system and preload... That way your device gets really clean of previous firmwares..
Tapatalking on my n7000
msedek said:
Before installing roms (and being sure I'm on a safe kernel) i do all wipes data/cache/Dalvik and also format data, system and preload... That way your device gets really clean of previous firmwares..
Tapatalking on my n7000
Click to expand...
Click to collapse
Preload? And im on hydracore v7 so its considered a safe kernel...

[Q] Samsung Galaxy S GT-i9000 freezes after around 30 seconds from reboot.

Hello everyone, thanks for taking your time and reading this.
I've owned a Samsung Galaxy S GT-i9000 for about two years now. This phone is not my primary phone, as I just use it as a secondary phone for different apps/backup, most of the times the phone is turned off.
But a few days ago, I turned the phone on, and once the homescreen had loaded, around 20-30 seconds later, the phone will freeze, and there's nothing else you can do other than take the battery out to turn it off.
A few details about the phone: the phone has never been flashed, and the OS has never been touched. It's basically at stock, but the only thing I remember is updating the official firmware through the Samsung link in the settings. The phone has never been modded, and that's what bugs me the most. (I've never had experience with 'modding' phones with custom ROMS and such)
So, after sitting at home all day looking for a fix, I couldn't find anyone else in my situation. There are a few similar situations, but I am yet to find something that replicates my problem exactly.
I've also tried rebooting the phone in many different ways, for example, taking out the memory card, then taking out the sim card, then taking them both out completely.
That's when I found a link which gave me information on how to factory reset the device. Since nothing else was working, I decided to go for it.
I held the VOLUME UP button + the HOME button, and hit the power button and got the menu up.
The menu works fine, I was flicking through the options for 10 whole minutes just to check if it freezes or not, and it works perfectly fine.
So then I factory reset the phone, wiped the system cache, and I also formatted the internal SD card.
Still, the problem persists. This time, the phone will reboot for a little while longer, since I expect the system files are getting set up, then it asks for the language, and before I can hit English, it freezes, and the screen stays like that until the battery is dead. All the hardware buttons don't do anything, it's basically fully dead with the screen still on the OS menu.
I was wondering if anyone knows what I should do?
I can provide more information if needed, and I can even upload a video to YouTube if you want a better aspect of the problem.
Any help is appreciated, thanks.
is it i9000 or 9100?
Sent from my GT-I9000 using xda premium
compacity said:
is it i9000 or 9100?
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Ah, sorry, got the title completely messed up there.
Yes it's the GT-i9000 and I think it had Froyo 2.2.1, forgot to include that in the main text.
Could try Rooting the phone and wiping all options in Recovery and Reboot
or
Could be that something maybe corrupted which is halting the system
Upload a video so that we can offer better advice
Which Rom / Firmware are you using?
Last option.
Would Recommend Downloading Rom (whichever you choose) and go from there....
Major UPDATE:
Okay, so after sticking at it the whole day and trying to get a better understanding of this situation, I've managed to work around the problem slightly. It's not fixed yet, though.
So after the screen had frozen for the (insert number here)th time, the battery was starting to go empty, so I stuck it on charge, but I forgot that I had left the frozen screen on (currently frozen on the 'Language Select' set up menu).
After about 20 minutes, the phone vibrated and a little message popped up, and it said that 'the process Soundhound.com.xxx.xxx was force closed', or something along the lines. I can't remember fully because it popped up for only around 4 seconds and disappeared.
As soon as I saw that, I quickly went to the application settings and deleted all of the soundhound cache/data and then removed the app completely. After that I thought it was fixed for sure, so I was messing around with the phone and using different apps to see if it freezes again, and it didn't.
But I had to restart the phone to see if the freeze issues happened again, and yep, it was there again, this time the same as the first issue, where it used to freeze up in the home screen. AND, I let it sit on the frozen screen for 15 minutes and it was that SAME soundhound app that got force closed, so once it got out of the frozen state, I quickly went to the application settings and the app was still there, it was like I didn't even delete it?
This leads to my new problem, the so called 'hard factory wipe/reset' doesn't actually reset EVERYTHING. As seen in my other post: http://forum.xda-developers.com/showthread.php?t=2305825
Now I'm completely confused as to what I should do.
I've pretty much tried everything, and i'm sure a FULL hard reset where EVERYTHING gets wiped out might just fix it? The thing is though, I don't know how? I've been trying to fix this phone for about 7 hours straight now.
My opinion Flash a Stock Rom or what ever you wish and then Root it...
If selling it just dont bother with Rooting it.
As you say you have been at it for Several hours and flashing takes less than an hour even for a newbie if following the procedure correctly
As going by what you say it seems that files are messed up on the phone and better to start fresh
ywasaf acquitted
EwOkie said:
My opinion Flash a Stock Rom or what ever you wish and then Root it...
If selling it just dont bother with Rooting it.
As you say you have been at it for Several hours and flashing takes less than an hour even for a newbie if following the procedure correctly
As going by what you say it seems that files are messed up on the phone and better to start fresh
Click to expand...
Click to collapse
Is there a legit way to flash it, maybe through Samsungs website? I don't want to mess around with custom files, as I would like to keep everything clean.
Oh, and also, I just went through the media files and found some of my old pictures too. So for some reason, the 'format internal SD' option in the recovery menu isn't working.
If I flash it, will I have to flash it to Froyo 2.2.1 which it is currently in right now?
Here's information I found on the 'About phone' menu:
Kernel version:
2.6.32.9
[email protected] # 1
Build number:
FROYO.XXJPY
Baseband version:
i9000XXJPY
Thanks for all the help so far.
Legit way your on XDA!
Flash a Stock 2.3.6 (Clean) which is the same as Samsung Site its in my How to Guide if you wish to follow it
Its the exact same Rom just not on there Site
EwOkie said:
Legit way your on XDA!
Flash a Stock 2.3.6 (Clean) which is the same as Samsung Site its in my How to Guide if you wish to follow it
Its the exact same Rom just not on there Site
Click to expand...
Click to collapse
Thanks.
Briefly read your guide, and it's all mind boggling to a newbie like me :silly: lol
I might just have to flash it, because this problem is getting a little bit annoying now.
Which parts of your guide should I follow exactly? And shouldn't I be sticking Froyo 2.2.1 back in? Won't a newer firmware (such as the 2.3.6) make the phone slower/drain more battery than usual?
Oh and one last thing, what's the difference between rooting and flashing a phone? Cheers.
Rooting briefly means :
Giving yourself root access to system files and the ability to change things that normally are marked read only
This allows you to change all kinds of things that normally you wouldn't be able to
Flashing : Erm.. Flashing a new Rom on your Phone or the process of over-writing your internal memory
2.3.6 will be ok for you if you wish to stay just Stock on your phone.
Plus the fact if you wish to move to another Rom later on its just a matter of Rooting the Phone and installing the Custom Rom
Just follow guide from the : HOW TO GUIDE : TUTORIAL TO FLASH 2.3.6 JVU + ROOT BEFORE INSTALLING CUSTOM ROM
and you will be ok.
EwOkie said:
Rooting briefly means :
Giving yourself root access to system files and the ability to change things that normally are marked read only
This allows you to change all kinds of things that normally you wouldn't be able to
Flashing : Erm.. Flashing a new Rom on your Phone or the process of over-writing your internal memory
2.3.6 will be ok for you if you wish to stay just Stock on your phone.
Plus the fact if you wish to move to another Rom later on its just a matter of Rooting the Phone and installing the Custom Rom
Just follow guide from the : HOW TO GUIDE : TUTORIAL TO FLASH 2.3.6 JVU + ROOT BEFORE INSTALLING CUSTOM ROM
and you will be ok.
Click to expand...
Click to collapse
So the 2.3.6 Firmware you provide, is that known a 'custom firmware'?
I've been searching for YouTube videos with people explaining how to flash, but all the videos sound like they're speaking about some rocket science sh** lol
Now I'm super confused, some guy on YouTube is flashing to 2.3.6 JVT while you're doing JVU, I don't even know what that means haha
I just don't want to brick the phone and make it completely dead, that's why I'm just making sure I understand the basics before I go ahead with it, sorry if I'm starting to sound annoying lol
You wont brick it if you follow it correctly...
2.3.6 JVU is the basis for all custom roms been flashed unless stated otherwise by Rom Developers.
As its basically a stock 2.3.6 then when you want to flash another Rom its just a matter of Rooting the 2.3.6
EwOkie said:
You wont brick it if you follow it correctly...
2.3.6 JVU is the basis for all custom roms been flashed unless stated otherwise by Rom Developers.
As its basically a stock 2.3.6 then when you want to flash another Rom its just a matter of Rooting the 2.3.6
Click to expand...
Click to collapse
Ah, okay.
Well, I'm in the process of downloading your files, THANKS for ALL the help you've given so far, sir!
I'll flash once all the files are downloaded. By the way, does 2.3.6 have Google Play store, and not the old Andropid Market?
I hope I can get this done before I head off to sleep in a few hours, been a very long day haha
I'll let you know of the results, cheers and have a good day sir.
No problem hope it all works out for you :good:
Not sure if Google Play is on it as its 2.3.6 Stock ...just upgrade it if possible
EwOkie said:
No problem hope it all works out for you :good:
Not sure if Google Play is on it as its 2.3.6 Stock ...just upgrade it if possible
Click to expand...
Click to collapse
why is it i cant see ur online status? is my app ...... nevermind that.
Sent from my GT-I9000 using xda premium
---------- Post added at 05:14 AM ---------- Previous post was at 05:13 AM ----------
f2k8 said:
Ah, okay.
Well, I'm in the process of downloading your files, THANKS for ALL the help you've given so far, sir!
I'll flash once all the files are downloaded. By the way, does 2.3.6 have Google Play store, and not the old Andropid Market?
I hope I can get this done before I head off to sleep in a few hours, been a very long day haha
I'll let you know of the results, cheers and have a good day sir.
Click to expand...
Click to collapse
GOOD LUCK N MAY LADY LUCK ON UR SIDE WHILE FLASHING
Sent from my GT-I9000 using xda premium
EwOkie said:
No problem hope it all works out for you :good:
Not sure if Google Play is on it as its 2.3.6 Stock ...just upgrade it if possible
Click to expand...
Click to collapse
Back again, haha.
I was just wondering, did you say I should root or not? As rooting it seems like a bit of a hassle? Plus, it says that I should install a custom rom zip file if I decide to root it, but I don't have one? I am using your 2.3.6 which was in your Odin Files download link, right?
So if I root, what do I do exactly?
compacity said:
why is it i cant see ur online status? is my app ...... nevermind that.
Click to expand...
Click to collapse
Hiding from the Tax Man :laugh:
Rooting takes 15 seconds to do
EwOkie said:
Hiding from the Tax Man :laugh:
Rooting takes 15 seconds to do
Click to expand...
Click to collapse
Okay, so I've rooted it also now, and unplugged the USB.
Now it's restarted, and the language set-up page is there, and guess what? .. It froze again :|
Exactly the same way before I flashed it :crying: :crying: lol
I actually feel like crying right now haha, I think the phone may be completely dead? Something is seriously corrupt with it I'm guessing?
I've never dropped it, or accidentally dropped liquid on it or anything like that.
I have absolutely no idea what to do now. Sigh.
Thanks for your help either way though.
can you upload a video on whats happening?
EwOkie said:
can you upload a video on whats happening?
Click to expand...
Click to collapse
how bout activate repartition?
Sent from my GT-I9000 using xda premium
---------- Post added at 05:49 AM ---------- Previous post was at 05:48 AM ----------
EwOkie said:
Hiding from the Tax Man :laugh:
Rooting takes 15 seconds to do
Click to expand...
Click to collapse
so thats why, i thought my app got error.
Sent from my GT-I9000 using xda premium

Categories

Resources