Bought this second hand Note II (NO WARRANTY) which had a 'modified' status, I first used this guide to remove that status and reset the binary counter and remove the root- http://forum.xda-developers.com/showthread.php?t=2339704.
Ever since I have done this my Note 2 has been experiencing issues, these issues consist of noticeable lag(when starting up the Samsung start up logo lags) and this is most noticable in the camera when moving it fast it lags up (see video), also when locking the device it sometimes shuts down and to restart it I have to hold the power button. I have another Note 2 next to me with everything stock and this one does not have these issues.
Now, I have flashed stock firmware onto the device several times in an attempt to fix this problem, I have also flashed a Custom ROM (Omega) onto it in an effort to resolve my issue, to no avail. I have also cleared the cache, reset to factory settings through the Android menus and Recovery mode, I have also tried to find out if it is an issue such as SDS(sudden death syndrome) I have followed this guide in an attempt to fix it (http://www.roytanck.com/2013/06/04/note-2-update-sudden-death-syndrome/) and I have now found out that my note 2 has an insane chip.
Honestly this whole ordeal is driving me mad, but I dont have a spare phone until I sort this out so im here for the long haul!
Please help!!!
EDIT: It was working fine, before I attempted to remove the modified status.
spinazania said:
Bought this second hand Note II (NO WARRANTY) which had a 'modified' status, I first used this guide to remove that status and reset the binary counter and remove the root- http://forum.xda-developers.com/showthread.php?t=2339704.
Ever since I have done this my Note 2 has been experiencing issues, these issues consist of noticeable lag(when starting up the Samsung start up logo lags) and this is most noticable in the camera when moving it fast it lags up (see video), also when locking the device it sometimes shuts down and to restart it I have to hold the power button. I have another Note 2 next to me with everything stock and this one does not have these issues.
Now, I have flashed stock firmware onto the device several times in an attempt to fix this problem, I have also flashed a Custom ROM (Omega) onto it in an effort to resolve my issue, to no avail. I have also cleared the cache, reset to factory settings through the Android menus and Recovery mode, I have also tried to find out if it is an issue such as SDS(sudden death syndrome) I have followed this guide in an attempt to fix it (http://www.roytanck.com/2013/06/04/note-2-update-sudden-death-syndrome/) and I have now found out that my note 2 has an insane chip.
Honestly this whole ordeal is driving me mad, but I dont have a spare phone until I sort this out so im here for the long haul!
Please help!!!
Click to expand...
Click to collapse
Why dont you return it? It's clearly gotnprblems
Sent from my GT-N7100 using xda app-developers app
Justinhopaolo said:
Why dont you return it? It's clearly gotnprblems
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
It didn't have problems until I started messing with it.
Can u flash with odin?
Sent from my GT-N7100 using xda premium
exzess78 said:
Can u flash with odin?
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Yes, I have flashed with odin several times with stock firmware and also a Custom ROM. Both still have the same problem
Related
Ok I am having problems rooting my galaxy S3. Every time I try to root my phone I get touchwiz has stopped working. The only way to fix this is to take out the battery and while hold volume up, power, and home button to do a factor reset. Not sure what the problem is, but I am using the most current version of odin3 and following the directions on how to root my phone. odin says it's complete and my phone restarts with no errors, but when it restarts I start getting stopped working pop ups and then touchwiz stopped responding. Anyone having this problems, and is there a fix for this? Any help would be appreciated.
I have used this with success many times. http://forum.xda-developers.com/showthread.php?t=1746682
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Confused about which rooting method
Hi,
I have a Galaxy S3 Roger sgh-i747m and android 4.0.4 with I747MVLLH1. I want to root it, able to do a full backup with Titanium or equivalent apps and install/modify rom, new os.
::
There are any methods for rooting, but I want to know which one should I use? I see this method:
http://forum.xda-developers.com/showthread.php?t=1739426
I'm not sure if it's working correctly for my phone.
What does it cause if the counter is tripping, only avoiding the warranty?
Thanks!
I think the S3 snapdragon toolkit that I posted above will work for rogers as well.
Also there is an app called 'triangle away' to reset the counter.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
lordzeager said:
Hi,
I have a Galaxy S3 Roger sgh-i747m and android 4.0.4 with I747MVLLH1. I want to root it, able to do a full backup with Titanium or equivalent apps and install/modify rom, new os.
::
There are any methods for rooting, but I want to know which one should I use? I see this method:
http://forum.xda-developers.com/showthread.php?t=1739426
I'm not sure if it's working correctly for my phone.
What does it cause if the counter is tripping, only avoiding the warranty?
Thanks!
Click to expand...
Click to collapse
I'm with Rogers too, I used this method and it worked perfectly. Just follow the steps closely and make sure you download the right complete files before doing it.
Trip counters and rooting does void the warranty. But if anything happens to your phone unrelated to you tampering with it, just rest flash counter and flash back to stock and they will still honor the one year warranty.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
bcb325ci said:
Ok I am having problems rooting my galaxy S3. Every time I try to root my phone I get touchwiz has stopped working. The only way to fix this is to take out the battery and while hold volume up, power, and home button to do a factor reset. Not sure what the problem is, but I am using the most current version of odin3 and following the directions on how to root my phone. odin says it's complete and my phone restarts with no errors, but when it restarts I start getting stopped working pop ups and then touchwiz stopped responding. Anyone having this problems, and is there a fix for this? Any help would be appreciated.
Click to expand...
Click to collapse
touchwiz is crap go sd maid and delete touchwiz and install apex or something
I rebooted my note 8 after making some changes with MultiWindowManager. After reboot the launcher wasn't responsive so I powered off by keeping the power button pressed. This happened another time after which it showed a black screen with 2-3 lines like: SD Card Mode. EMMC something. SD Copy (or update) completed.
Now it won't turn on at all, nothing shows up on the screen. Is there any troubleshooting I can do myself or should I send it back?
Have you tested the download odin menu by pressing vol - and power?
Just tried it now. Nothing happens. The battery was at ~45% plus I've left it on the charger so I'm sure its not that.
Edit: Is there a way to do a battery pull?
Testing support 30s the Power button ...
Pressing power button for 30s and then releasing doesn't do anything either..
I could not help you more .... Arranges you to completely discharge the battery of your tablet ...!
Perhaps you can use samsung toolkit?
http://forum.xda-developers.com/showthread.php?t=2251033
Did you patch it in the app? If I recall some other posts said that essentially bricked their device. Was it just a reboot after editing apps?
Sent from my GT-N5110 using XDA Premium HD app
The first version of the application did not allow to patch NOTE8 but after an update it is possible and without incident brickage
Bonisaur said:
Did you patch it in the app? If I recall some other posts said that essentially bricked their device. Was it just a reboot after editing apps?
Sent from my GT-N5110 using XDA Premium HD app
Click to expand...
Click to collapse
Patch what in the app? Can you point me to where it talks about bricking and I'll look into that as well. All I did was add some apps to the enabled list and rebooted when it asked me to. Previously this had worked fine and I don't think I did anything differently this time either.
Edit: I just found this thread (http://forum.xda-developers.com/showthread.php?p=41167471) and it seems to be a very similar issue. I had patched it when I first installed it a couple of days ago (I can't remember but it was an .apk that I backed up using Titanium before patching). Anyway, it seems like it is dead and Multi Window is a likely culprit in both these scenarios?
Btw, are there others here who are using Multi Window Manager without issues? Multi windows is the biggest reason I got this tablet and if I can't put custom apps on there I'm thinking of doing a return instead of an exchange.
ammarr said:
I rebooted my note 8 after making some changes with MultiWindowManager. After reboot the launcher wasn't responsive so I powered off by keeping the power button pressed. This happened another time after which it showed a black screen with 2-3 lines like: SD Card Mode. EMMC something. SD Copy (or update) completed.
Now it won't turn on at all, nothing shows up on the screen. Is there any troubleshooting I can do myself or should I send it back?
Click to expand...
Click to collapse
Did you by any change say ÿes" to the n7000 (if I remember correctly) patch option?
I cant remember the exact message it showed but is looked like something your quoting
My device was bricked and I returened it to samsung.
(10 days ago, not yet returned)
I use it and I never patched it. It doesn't have any issues. Hopefully you can figure out the best way to fix it.
Sent from my GT-N5110 using XDA Premium HD app
I see. So it seems like if I don't say yes to the patching option I should be able to avoid getting into this issue again.
HANSB57 said:
Did you by any change say ÿes" to the n7000 (if I remember correctly) patch option?
I cant remember the exact message it showed but is looked like something your quoting
My device was bricked and I returened it to samsung.
(10 days ago, not yet returned)
Click to expand...
Click to collapse
Yes I think I said yes to it as well. We've both run into the same issue.. perhaps we should let the dev know that choosing yes results in bricked devices and maybe that popup should not be shown on the note 8.
No problem with this application for me
micger21 said:
No problem with this application for me
Click to expand...
Click to collapse
Did you do the patch?
Yes
Thanks. Then I'm not sure why there have been a couple of bricks right after using this app.
Did you root using Framaroot or flashing an insecure bootloader and putting on a custom recovery? Could that be a factor? I used Framaroot for rooting.
I root using Framaroot and flashing an insecure bootloader and a custom recovery!
ammarr said:
Thanks. Then I'm not sure why there have been a couple of bricks right after using this app.
Did you root using Framaroot or flashing an insecure bootloader and putting on a custom recovery? Could that be a factor? I used Framaroot for rooting.
Click to expand...
Click to collapse
Framaroot here.
Bricked after multi window app
I was running SlimBean 6.8 with Ktoonsez Kernel from 6/8/13. I was running this for roughly 1 week with no issues. I was taking pictures, listening to music, playing games, all without issue.
Yesterday I was using Google Navigation to get to New Orleans. I was using it for around 1 hour with no problem. At some point (when I needed to actually navigate around downtown) I looked down and noticed that it had rebooted and was stuck on the Kernel splash screen. I tried several things to no avail. I tried re-installing the kernel, re-installing the ROM, factory reset, back-up/restore. No matter what I did it kept getting stuck at the kernel splash screen. I was able to ODIN back to stock and now it's working again. Any idea what might have caused this?
Its not called a brick. But soft brick a lot of people get confused and called it a brick. A brick is when its completely unresponsive and doesn't boot up at all... As to your issue I've honestly haven't heard of that before. Have you reinstalled Slim?
Sent from my SGH-I747 using Tapatalk 4 Beta
jayRokk said:
Its not called a brick. But soft brick a lot of people get confused and called it a brick. A brick is when its completely unresponsive and doesn't boot up at all... As to your issue I've honestly haven't heard of that before. Have you reinstalled Slim?
Sent from my SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Ok, good to know. I went back to Task's. So far so good.
ya i have had this issue before. what i do to fix it is i usually un-root and flash stock via odin and then use odin to re-root my phone and then flash roms just like usual. that has worked for me for all my soft-bricks. hope that helps.
i root SGH i777 said:
ya i have had this issue before. what i do to fix it is i usually un-root and flash stock via odin and then use odin to re-root my phone and then flash roms just like usual. that has worked for me for all my soft-bricks. hope that helps.
Click to expand...
Click to collapse
That's what I did and it worked fine. However, I was in the middle of navigated to a town I've never been to. Luckily, I remembered the name of the street that the hotel was on and was able to find it after a few loops. I'd like to know what caused it so I can potentially avoid something like this in the future.
Hi,
I have a Galaxy Nexus GT-i9250. I used to use it to play around with ROMs and all. But the last time I flashed a CM11 and DirtyV Kernel, the phone started stuttering during boot and when I tried to flash a new ROM, the ROM just wouldn't take, it just kept coming back to the same version of CM11. I've even tried returning to stock using Root Toolkit and the like but still doesn't work.
Is there a way to fix it? I really really like my Galaxy Nexus, so I'm willing to spend a few bucks, but not too much that it'd make sense to buy another phone.
Go into recovery mode n see if u can just use one of your backups from there
Sent from my Galaxy Nexus using XDA Free mobile app
rob420jones said:
Go into recovery mode n see if u can just use one of your backups from there
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
I tried. No luck.
It's a strange thing. A lot of Galaxy Nexus had that kind of problem in these days, and many thread on xda confirms that.
That thing happened to me as well. No luck. No way to fix the problem by software ways for me.
There was no way to unlock the bootloader, I mean, I did it by fastboot but after every reboot it came back locked.
No recovery worked, even a custom recovery booted temporary didn't help. Wipe data etc but after the reboot the device booted as I haven't wipe anything..
Odin didn't work, same as before. It took time, it seems that was working on something, but no luck after reboot, everything was the same as before, as if I haven't done anything.
Couldn't enable usb debug to use ADB 'cause I activate that but after the reboot (guess what?) it was disabled again..
I tried almost every way..
An xda user said that "if you unlock the bootloader and after the reboot it's locked again, the emmc is fried".
So sad
I have done almost everything to fix it.
But i dont think i can i have tried numerous of times of diffirent roms in the past but still havent been able to overcome this situation. i always check the correct modle and version before flashing. The just at random one day choose to freeze up. I thought it was lag or some sort nothing serious so i just Restarted it an left it.
When i had come to it was stuck on the logo.
I even took it to thoes small retail shops for a repair
they came out with the same conclusion as i had it isnt fixable.
In my personal opinion i think its damaged from the inside some chip or something i dont knoe anything about the phone inside.
The rom i was using is Ditto note 4
version 4.4.4
Modle Gt-1700
Name samsung galaxy note 2
Device rooted
Once i gave up on it i left it out away for about a year and it still has the name problem.
Someone please give a solution Thanks
Did you tried stock rom using odin?
Try flashing the latest ROM from sammobile.com or update.com with Odin, perform a factory reset from stock recovery, and boot the phone.
Nitaro said:
I have done almost everything to fix it.
But i dont think i can i have tried numerous of times of diffirent roms in the past but still havent been able to overcome this situation. i always check the correct modle and version before flashing. The just at random one day choose to freeze up. I thought it was lag or some sort nothing serious so i just Restarted it an left it.
When i had come to it was stuck on the logo.
I even took it to thoes small retail shops for a repair
they came out with the same conclusion as i had it isnt fixable.
In my personal opinion i think its damaged from the inside some chip or something i dont knoe anything about the phone inside.
The rom i was using is Ditto note 4
version 4.4.4
Modle Gt-1700
Name samsung galaxy note 2
Device rooted
Once i gave up on it i left it out away for about a year and it still has the name problem.
Someone please give a solution Thanks
Click to expand...
Click to collapse
Can you enter recovery? What recovery you have?