So, just to preface, I am a rooting beginner. I'm not sure if the damage that has obviously been done is a result of some sort of incompatibility or a failure on my part.
In short, I'm using an N910F (Vodafone, UK), and I attempted to root my device after becoming somewhat impatient waiting for Vodafone / Samsung to pull thumbs out of relative asses and release Marshmallow.
I rooted using CF Root, version LMY47X.N910FXXS1COK2 - going onto a device running 5.1.1. After this, I installed Resurrection Remix, which ran for a small period of time.
After this, I started experiencing black screens, and failures to boot, as well as boot loops.
So, after this, I flashed stock 5.0.1 back to the phone, which wasn't 100% stable in the beginning. So, I factory reset, and flashed again, and here I am.
I am currently suffering from major hanging issues, as well as random shutdowns, which can only be solved by removing the battery, it might seem.
Model Number - N910F
Android Version - 5.1.1
Build Number - LMY47X.N910FXXS1CPC6
Knox 2.4.1
All Rom's were flashed with Odin on a Windows PC.
Thanks in advance, all.
Bread:silly:
Related
Hello XDA community, I'm panicking a bit and am new to this whole smartphone thing.
So, yesterday I got an LG G2 and spent the majority of the day downloading apps and whatnot. Today I asked some friends and got the phone rooted, installed Xposed and some Modules, and decided to give flashing a new Kernel a try.
I have the LG G2 VS980 (Verizon) and flashed Dorimanx's v6.8 kernel successfully after making a Backup in TWRP.
Upon going back to basic usage, I realized the Navigation Buttons were gone. All of them. I tried swiping up and down and all around, thinking that maybe the Xposed Tweaks may have done something to them, but nothing made them appear. Also, the default Weather Widget failed to load, originally attempting to load and then defaulting to a "Failed to load widget" generic window. I went to google the issue when I got a "LG Keyboard Failed to load" error.
I immediately went and restored my backup, but the issues were still present. I tried multiple Factory Hard Resets through TWRP and even attempted Flashing an older version of Dorimanx's kernel (before anyone asks, yes I was using the VS980 version), nothing helped. In my latest desperation attempt, I used TWRP to reformat the partitions, so now my backup is gone.
Now I'm stuck, because I can't get through the VZW Setup Wizard since I apparently can't connect to the Backup Assistant network (which apparently has something to do with EFS? I'm not really sure), can't skip it without Navigation buttons, and can't access Wifi without the keyboard to type in the password to my home network. I've been avidly googling for the past 2-3 hours, but no one seems to have my exact issues. Currently, I'm following this guide to return to complete stock, and hopefully if the problem persists I can return the phone under warranty.
Can anyone offer me some help/advice in the meantime? I'm really curious as to what happened and of course I'm panicking due to potentially losing a phone after 1 day (the salesperson kept pushing their insurance on me as well, which I denied repeatedly). After the restore and then factory reset, the phone should be fully stock (the settings support this, showing the original kernel/build/everything) yet the errors persist.
Many thanks in advance!
EDIT: Here's some more detailed info:
Android version: 4.4.2
Baseband version VS98024A...
Kernel version: 3.4.0-perf
SirZer0 said:
Can anyone offer me some help/advice in the meantime? I'm really curious as to what happened and of course I'm panicking due to potentially losing a phone after 1 day (the salesperson kept pushing their insurance on me as well, which I denied repeatedly). After the restore and then factory reset, the phone should be fully stock (the settings support this, showing the original kernel/build/everything) yet the errors persist.
Many thanks in advance!
EDIT: Here's some more detailed info:
Android version: 4.4.2
Baseband version VS98024A...
Kernel version: 3.4.0-perf
Click to expand...
Click to collapse
Returning to stock will solve any software problems you might have. I understand why you had issues with xposed, I get them too sometimes. Its always best to flash your kernel first and then do your mods.
Hi, I'm kinda lost ma mind right now.
Here's the story, my friend has note 4 SM-N910F Qualcomm , suddenly it began restarting with abnormal battery dropping.
I began repairing by trying to perform factory reset, to enter into a boot loop (without a root till the moment). Then I charged it fully which made it work.
I tried to root then install CM to replace stock rom (to repair any system issues), which was quite difficult, as I tried to install CM 12.1, it keeps fail due to incompatibility (the CM rom for trltexx and mine trlte as the root keeps shows me)
BTW the root I used was ( openrecovery-twrp-2.8.4.0-trltexx.img.tar ) *yea it confusing*
Finally I downloaded official stock 5.1.1 , and installed it, it finished well and booted also quite well, as language selection screen appeared, same original issue reappeared again ( *keeps rolling in boot loop* )
Now I'm worrying about hardware malfunctioning.
:silly::silly::silly::silly::silly::silly::silly::silly:
I accidentally posted in Android development. so sorry
I've seen this issue on my friend's tab s. The screen would freeze then it would reboot. This got worse as the battery power doped to the point that swiping to unlock would cause a reboot. The problem turned out to be the battery. It may be worth buying a new battery for very little money to see if this fixes it.
Dr.DL said:
Hi, I'm kinda lost ma mind right now.
Here's the story, my friend has note 4 SM-N910F Qualcomm , suddenly it began restarting with abnormal battery dropping.
I began repairing by trying to perform factory reset, to enter into a boot loop (without a root till the moment). Then I charged it fully which made it work.
I tried to root then install CM to replace stock rom (to repair any system issues), which was quite difficult, as I tried to install CM 12.1, it keeps fail due to incompatibility (the CM rom for trltexx and mine trlte as the root keeps shows me)
BTW the root I used was ( openrecovery-twrp-2.8.4.0-trltexx.img.tar ) *yea it confusing*
Finally I downloaded official stock 5.1.1 , and installed it, it finished well and booted also quite well, as language selection screen appeared, same original issue reappeared again ( *keeps rolling in boot loop* )
Now I'm worrying about hardware malfunctioning.
:silly::silly::silly::silly::silly::silly::silly::silly:
Click to expand...
Click to collapse
Did you try a Factory Reset?
Sent From My SM-N910W8 Running CMRemix 6.01
fatboyinlycra said:
I've seen this issue on my friend's tab s. The screen would freeze then it would reboot. This got worse as the battery power doped to the point that swiping to unlock would cause a reboot. The problem turned out to be the battery. It may be worth buying a new battery for very little money to see if this fixes it.
Click to expand...
Click to collapse
I'm in a doubt about the battery, I think it's slightly swollen.
I guess I'll give it a try.
shaggyskunk said:
Did you try a Factory Reset?
Sent From My SM-N910W8 Running CMRemix 6.01
Click to expand...
Click to collapse
First thing I did.
Dr.DL said:
Hi, I'm kinda lost ma mind right now.
Here's the story, my friend has note 4 SM-N910F Qualcomm , suddenly it began restarting with abnormal battery dropping.
I began repairing by trying to perform factory reset, to enter into a boot loop (without a root till the moment). Then I charged it fully which made it work.
I tried to root then install CM to replace stock rom (to repair any system issues), which was quite difficult, as I tried to install CM 12.1, it keeps fail due to incompatibility (the CM rom for trltexx and mine trlte as the root keeps shows me)
BTW the root I used was ( openrecovery-twrp-2.8.4.0-trltexx.img.tar ) *yea it confusing*
Finally I downloaded official stock 5.1.1 , and installed it, it finished well and booted also quite well, as language selection screen appeared, same original issue reappeared again ( *keeps rolling in boot loop* )
Now I'm worrying about hardware malfunctioning.
:silly::silly::silly::silly::silly::silly::silly::silly:
Click to expand...
Click to collapse
Install Custom recovery thro' ODIN (philz_touch)
Flash Nameless Kernel v 6 thro custom recovery.
And I think you are done.
If you tried factory reset and flashed a fresh stock rom and its still happening, the battery is the problem and also check if there is a micro sd inserted. If so, remove the card and check.
No custom rom or kernal will be better since they come with thier own bugs and not as stable as official firmware period!
dineshh said:
Install Custom recovery thro' ODIN (philz_touch)
Flash Nameless Kernel v 6 thro custom recovery.
And I think you are done.
Click to expand...
Click to collapse
Battery issue, solved with replacement
jetbruceli said:
If you tried factory reset and flashed a fresh stock rom and its still happening, the battery is the problem and also check if there is a micro sd inserted. If so, remove the card and check.
No custom rom or kernal will be better since they come with thier own bugs and not as stable as official firmware period!
Click to expand...
Click to collapse
Solved with battery replacement
huge thanx
Do you see all the threads about restoring a ''bricked'' N910C from CM13 to stock?
Well they all require you to have a functioning CM13 ROM in the first place.
I do not have that.
My N910C refuses to boot past logo no matter what the ROM is, CM or Stock or anything else. I have tried installing COMPLETE firmwares with PIT files and repartitioning, but all this still leads to the same bootloop screen.
I even took my phone to some guy who has a box shaped device that supposedly formats all phone hardware data to factory setting. Nope that didn't work. Still bricked.
The only thing that changed since all my failed trials is the release of Polands 6.01 MM for the N910C. Will flashing that even be of any use? What on earth am I supposed to do except getting a $100 motherboard replacement.
Also, this all didn't start because I was thick headed enough to roll back my android without knowing the consequences. The ''unofficial'' CM13 actually crashed while the flash-light was on, and started bootlooping by itself, forcing me to look for other ROMS.
Hello, i will try to be as elaborate as I can cause I know you guys here are really knowledgeable when it comes to smartphones. So, here are the issues I am currently experiencing with my G900F phone. Just a background, everything in my phone is stock (rom, recovery, kernel) no changes done yet. It currently runs MM with a security patch of February 2017. As of now, I can't boot into the phone.
1. . I was able to successfully root it with CF auto root.
2. I started experiencing random restarts. I tried obtaining the last kmsg however it does not exist.
3. I tried flashing a new ROM thinking maybe there is some rare bug in the stock rom i currently have. I flashed TWRP via Odin, to be able to flash a new ROM. Odin successfully flashed the recovery however when i proceed to install a new ROM through TWRP the phone gets stuck in a bootloop. I do not experience this in the stock recovery
4. I was able to restore the phone through Smart Switch device intialisation. However, with everything stock I still experience the random reboots.
Bottomline: Is there anyway I can fix this on the software side (e.g. flash/update this or that)? And if not, do you think this is a hardware problem? Worth mentioning it's got a yellow screen bug but if i press hard on the back of the phone it disappears. Also, I can boot into stock recovery and download mode without any problems.
Thanks and sorry for the long post really need your insights.
Sorry you are having issues. I apologize if I missed this, but have you tried downloading the official firmware for your device from sammobile or similar sites, then flash that through Odin?
Hey guys, I've encountered a thorny problem on my wife's N910T3, and am running out of ideas about what this could be... so, could really use some help.
Some background: The phone's been working fine for over a year of ownership, mostly on the stock ROM, which gets pretty laggy at times. A few weeks ago I installed a custom ROM (the Acapolypse-X N7 port) to improve performance, and for the past few weeks it's been working perfectly fine on the custom ROM no problem.
Today, when my wife went to check Twitter, the phone crashed and started bootlooping. I had seen a similar issue on my Note 3 before (which turned out to be a specific issue with the kernel I was using), so I figured I would just go into recovery, flash a different kernel or at worst, do a clean install of the ROM.
That's when things started getting weird: The phone would crash while INSIDE recovery during ROM installation (I've never seen a phone crash inside recovery before...) After failing to successfully flash a ROM or, even in cases when it succeeds, fails to boot, I decided to do a full flash back to the latest unmodified stock ROM (since I couldn't find an ODIN-flashable image to download, I used Samsung Kies for this - typically this resolves any kind of left over from previous installations).
On the first attempt, it succeeded - the phone booted into the stock ROM and I was able to start customizing settings. Figuring the issue has been resolved, I went ahead and attempted to root by flashing TWRP through ODIN, and that's when the phone went back to rapidly bootlooping again (it reboots every 2 seconds, I can't even get into recovery when this is occuring). The only way I can return to Recovery is by flashing it again in ODIN (typically this trick will only work once; upon rebooting the phone after that it is prone to start bootlooping again).
Based on the symptoms I suspected the NAND going bad. However, I receive no emmc read/write errors during flashing - all write operations in ODIN results in success and my friend even ran a full storage check via ADB and this phone just doesn't seem to have any bad sectors (I almost wish it were since that would resolve the mystery).
Anyone have any ideas what may be the problem? I have a decent amount of experience installing custom roms on my phones and troubleshooting installation issues, but I've never seen anything like this (crashing/bootlooping directly inside recovery).