Hi Guys,
Hopefully this is in the right section
I have a Note 4 SM-N910G and its just turned absolutely useless since I factory flashed it. I have rooted it before and bricked it and un bricked it before so have some experience with it. I recently wiped my phone and did a firmware restore using Samsung Kies and since I did the phone is absolutely useless. It started out fine for an hour or two and now it lags by like a minute with any action, even trying to bring up the keyboard when typing. It will reset itself, lock itself, crash, just un useable. I've tried reflashing it again stock a couple times and still the same everytime. It went from perfectly fine to dreadful with the original mentioned restore. I did just recently get an error code of "sbl1 partition doesn't exist" in Boot recovery mode.
Does anyone know if this is fixable and not a hardware issue?
Should I try and just root it again and flash a non-oem rom? (I havent had the time to do it recently)
many thanks,
Tekkado
Hi Guys,
Also I should add that when I was rooted the phone was fine but when i went to unroot through super user the phone was still functioning as though rooted and I couldnt download software updates because my device was "modified".
So thats when i just flashed stock firmware and again now flashing through odin aswell it proceeds fine then the device will say installing updates and then give a no command error or seandroid not enforced. Everytime is basically a different message.
How can I just wipe everything and get back to stock?
Thanks
So to add to this is there any relationship between the firmware running and the bootloader? I just realised that before i tried to flash stock firmware i was rooted and didnt un root via superuser because in the past that did jack all.
I flashed dr. ketan rom this morning and the phone was operating as normal very snappy but as soon as i downloaded a new app from the play store (reddit and chrome) again it turned to absolute crap.
Is there a disconnect here that i missing that can be fixed?
Thanks
Related
Hi all,
I have a Nexus 5 bought In Israel. It came with 4.4.1 and I updated to 4.4.2 and I wanted a change so I installed PA ROM beta 4.
Now from here all hell broke loss...
For some reason my vibration motor stopped working completely and from time to time it gave me this weird vibration for maybe 2 hours and then disappeared again... I'm not blaming this on the ROM.
Yesterday I got an update that PA ROM beta 5 was out so I installed it through their OTA app.After the update I had no keyboard, my volume buttons did not respond well so I thought maybe the update was a bit off, So I did a Factory reset. after the reset the OS was still shaky and laggy so I wanted to go back to stock... I found a Stock odexed ROM, got into TWRP wiped everything except sd, and went on to install the new ROM.
(I did not make a backup).
Now my problem Is that I could not install the stock ROM, every time i tried to flash it it would stop and not install...
Now i'm stuck in TWRP without the ability to mount my phone to try and change the ROM... when I reboot it says I have no OS...
I tried working with the Nexus 5 toolkit and install stock from there and also nothing helps...
I tried installing the Stock from Google manually with fastboot commands and still no answer from the phone...
Please does anyone have an idea for me?
Muskito87 said:
Hi all,
I have a Nexus 5 bought In Israel. It came with 4.4.1 and I updated to 4.4.2 and I wanted a change so I installed PA ROM beta 4.
Now from here all hell broke loss...
For some reason my vibration motor stopped working completely and from time to time it gave me this weird vibration for maybe 2 hours and then disappeared again... I'm not blaming this on the ROM.
Yesterday I got an update that PA ROM beta 5 was out so I installed it through their OTA app.After the update I had no keyboard, my volume buttons did not respond well so I thought maybe the update was a bit off, So I did a Factory reset. after the reset the OS was still shaky and laggy so I wanted to go back to stock... I found a Stock odexed ROM, got into TWRP wiped everything except sd, and went on to install the new ROM.
(I did not make a backup).
Now my problem Is that I could not install the stock ROM, every time i tried to flash it it would stop and not install...
Now i'm stuck in TWRP without the ability to mount my phone to try and change the ROM... when I reboot it says I have no OS...
I tried working with the Nexus 5 toolkit and install stock from there and also nothing helps...
I tried installing the Stock from Google manually with fastboot commands and still no answer from the phone...
Please does anyone have an idea for me?
Click to expand...
Click to collapse
Then you have to flash the stock rom and start over, here is u tutorial http://forum.xda-developers.com/showthread.php?t=2513701 to flash the rom. Google rom`s https://developers.google.com/android/nexus/images?hl=nl.
I think you have to format data and the try flashing any rom, this has happened to me 2 times already. Twrp is the culprit i believe
Sent from my Nexus 5 using Tapatalk
Alright, this is a long story.
I own an LGMS500 from MetroPCS (or the LD500 Tmobile version).
A year back I rooted the phone, but a couple of months ago it started to act up Giving me the message "unfortunately, the process com.android.phone has stopped." at first a restart would fix it but a few days after it got to the point where I couldn't use it. So I set out to fix it.
I knew I needed to flash it back to stock ROM since a factory reset and a hard factory reset didn't do anything. But for some reason I decided that flashing a custom ROM was a better Idea. I ended up flashing the xperia ROM and it soft bricked it ( It turned on and booted but wouldn't let me past a black screen, yet I could lower the status bar).
Then I tried to flash the stock ROM or the "MS50010e_03.zip" to load with KDZ. from:
http://androidforums.com/threads/metropcs-unbrick-kdz-for-metropcs-updated-11-13-2013.788365/
But every time I tried it it came back with a parameter error, I changed many things with no avail, Then I figured that since the phone had a tmobile version I flashed the tmobile stock ROM onto the phone and it worked, even let me use data. But after a few days it stopped letting me use data, with a "Service Disabled message on the status bar where it should've shown the mobile carrier. When I went to check my phones mobile data status I noticed that My IMEI # was unknown.
After some research I came to the conclusion that something was wrong with my EFS folder since that's where all that information resides.
At the moment the phone restarts after about 3 minutes of usage, I should also mention that I rooted the phone after the tmobile stock ROM install because of what this thread suggested I should do.
http://forum.xda-developers.com/galaxy-s2/general/guide-recover-imei-9-steps-t1264021
Basically I need to know if my conclusions are correct and what kind of steps I should take to recover the phone if possible.
A
FIXED it
I just loaded the MS50012b_00.kdz from:
android creations on the weebly site (sorry I can't post links yet)
This is the only image that worked the first time. After that my phone worked normally, accessed the mobile network correctly and the crashing stopped.
I even installed the xperia ROM that is on that page. Everything is running smoothly now.
Today my apps were acting weird so i went to my superSU and it said
"there is no SU binary installed, and superSU cannot install it. This is a problem!"
Seems like I've tried everything to fix this problem. Flashed stock rom using Odin, reflash CF-root after that. Tried installation custom recovery (can't flash using recovery because my phone is encrypted unless there's a way to by pass that). Used different cords, ports, versions of odins. Still nothing. Had this problem since the morning it's now 8pm here so i decided to ask.
Anyone know how to fix this issue?
Hey, is there anyone who solved the problem ? I got the same issue with my brand new Galaxy S7, quite anoying ...
So have i with my S6. No cure so far, tried everything. Waiting for chainfire to jump in...
Verstuurd vanaf mijn SM-G920F met Tapatalk
I have also just experienced this. Everytime I try to remember root and run root checker it says not rooted.
try root with twrp and a kernel like "adam kernel" or a nearly stock one. Then try flash form recovery supersu 2.74
Ive got the same issue. I have G920i stock 6.0.1 rom and stock kernel and rooted using cf-root. However today i noticed my device is not rooted anymore. Also a week ago my phone completly froze and i had to go to download mode and reboot the device. Im not really sure if this incident was related for the device to become unrooted. Any help is appreciated
Same problem! I rooted my galaxy s7 with cf-root and odin and it worked fine for a while until I got no root privileges and had to reroot it. It worked once more and again - unrooted by itself, only this time rooting doesn't work! it says that it roots it but when I check supersu, it says no SU binary. Please someone help!
same issue
deveice is s6 and china version.
I just bought it one week
wait the solution.
Strange, same thing just happened to me today in Samsung S7. Phone restarted on its own and now no root access. I had it rooted like 2 months ago with Cf and Odin and had been working fine. What happened??
same here , S6 G920F... lost all access from rooted apps tried re-root with odin , also installing supersu again and again , deleted also all the required-rood apps ... nothing works
Hey guys this is already solved. Samsung pushed a security policy update that broke the root. So now the way to go is that you need to flash stock rom with odin. I used smart switch which is easier and worked too. Then after you have stock rom you root using the new cf-auto root by chainfire. Enjoy.
LAUNCHERMONKEY said:
Today my apps were acting weird so i went to my superSU and it said
"there is no SU binary installed, and superSU cannot install it. This is a problem!"
Seems like I've tried everything to fix this problem. Flashed stock rom using Odin, reflash CF-root after that. Tried installation custom recovery (can't flash using recovery because my phone is encrypted unless there's a way to by pass that). Used different cords, ports, versions of odins. Still nothing. Had this problem since the morning it's now 8pm here so i decided to ask.
Anyone know how to fix this issue?
Click to expand...
Click to collapse
This happened to me today, I fixed by restoring to stock using smart switch and then using cf-autoroot to re root.
I had same problem
r00tkiller said:
Hey, is there anyone who solved the problem ? I got the same issue with my brand new Galaxy S7, quite anoying ...
Click to expand...
Click to collapse
Basically I just fixed it by reflashing my ROM straight on top of my old ROM (ressurection remix) I did not wipe cache or dalvik just straight reflashed ROM and it fixed it
Nothing else I tried worked not sure if I will get the same error again but it worked for now
Plus I had error previously with su binary update think this is the cause
Hey all, need some advice... I recently rooted my phone and found it wasn't for me (way too many apps stopped working). Because of this I tried to unroot the phone, but got stuck in a boot loop and had to recover from scratch.
Anyways, I'm running stock now and the system is back to being rooted. Problem is, I can't seem to update the phone. I'm not getting an error message either. Both Smart Switch and the phone simply say I'm up to date, but I'm on APB7 when I should be able to get APD3.
Is there anyway to fix this? Will I need to factory reset the phone? I'm not sure how to get the phone to recognize an update now.
Same here. I rooted my phone, installed TWRP but battery drain and apps not working properly made me go back to stock. Now I cant get any updates. I flashed APEQ fw yesterday dated June 8 but still dont get the June 17 updates.
I used Smart Switch to do an Emergency Reinstall of the firmware. Had to start over from scratch with my phone... It installed the lastest firmware though.
Been researching as much as I can online and it seems the consensus is simply unrooting the phone does nothing. You have to factory reboot. Tripping Knox won't stop you from getting updates but an unrooted phone that wasn't factory reset still won't get updates. Fun times. Last time I root my phone... Things aren't the same since I last rooted in Android 4.0. Now too many apps and updates etc. check for root and stop working if they detect it.
Luuthian said:
Hey all, need some advice... I recently rooted my phone and found it wasn't for me (way too many apps stopped working). Because of this I tried to unroot the phone, but got stuck in a boot loop and had to recover from scratch.
Anyways, I'm running stock now and the system is back to being rooted. Problem is, I can't seem to update the phone. I'm not getting an error message either. Both Smart Switch and the phone simply say I'm up to date, but I'm on APB7 when I should be able to get APD3.
Is there anyway to fix this? Will I need to factory reset the phone? I'm not sure how to get the phone to recognize an update now.
Click to expand...
Click to collapse
Did you use Odin to flash back to stock?
malek777 said:
Did you use Odin to flash back to stock?
Click to expand...
Click to collapse
I used the Emergency Recovery function of Smart Switch which, from my understanding, is basically the same thing. I know how to use ODIN but it seemed a better idea to go with the official solution. Guess I'll find out if it worked once the June update is available in Canada.
I have had my Galaxy S7 for about 2 months, brand new from Verizon, I updated my firmware using their Samsung official update and when it booted it up, it said custom, but when I used a root checker it said it was not rooted, and I tried to use some superuser features and they would not work, but the phone still shows custom.
The phone worked fine up until a week ago when it started to freeze, then would reboot and take hours to turn on. The phone got to the point where it wouldn't even reboot, even after a master reset, and flashing the stock ROM via Odin. I took it into Samsung to get help, after they tried to flash it and it didn't get passed boot, I was turned away because the phone appeared to be rooted and I was told to send it in to Samsung. This is a problem I have never seen before. I did not try any attempt to root my device or download anything that wasn't official. I have sent my phone into Samsung so they can "investigate the issue" and I am awaiting the response. I have some questions.
1. Is this common?
2. How could this have happened?
3. Does flashing a stock rom via Odin trip Knox?
4. if Samsung turns me away what should I do?
Thanks.
-Greg
SirMilkaPeach said:
I have had my Galaxy S7 for about 2 months, brand new from Verizon, I updated my firmware using their Samsung official update and when it booted it up, it said custom, but when I used a root checker it said it was not rooted, and I tried to use some superuser features and they would not work, but the phone still shows custom.
The phone worked fine up until a week ago when it started to freeze, then would reboot and take hours to turn on. The phone got to the point where it wouldn't even reboot, even after a master reset, and flashing the stock ROM via Odin. I took it into Samsung to get help, after they tried to flash it and it didn't get passed boot, I was turned away because the phone appeared to be rooted and I was told to send it in to Samsung. This is a problem I have never seen before. I did not try any attempt to root my device or download anything that wasn't official. I have sent my phone into Samsung so they can "investigate the issue" and I am awaiting the response. I have some questions.
1. Is this common?
2. How could this have happened?
3. Does flashing a stock rom via Odin trip Knox?
4. if Samsung turns me away what should I do?
Thanks.
-Greg
Click to expand...
Click to collapse
This just happened to me and I the problem was that I had Secure Startup enabled under Lock screen and security. I just disabled it and re-rooted it and that fixed the problem. Hope it works for you.