Database Users

N910F problems - emmc read fail/ flashing stock no longer boots the phone.

Hello. I had gotten this Note 4 phone which had a custom recovery installed on it but the rom seemed to be official, on 5.1
The first thing I did was go to samfirmware and flash a 6.0.1 rom, it went fine, phone was working properly. Then I got greedy and wanted to test a Note 7 ported rom. Flashed TWRP recovery and from within I flashed RamROM http://forum.xda-developers.com/note-4/snapdragon-dev/rom-sm-n910g-ramrom-t3400349 , I downloaded the one from post#2 , the N910F one that my phone is and after it flashed to ROM it simply stopped working. My phone no longer booted, was booting me directly into Download mode with emmc read error. I kept trying to flash the stock rom which I previously flashed and it would fail.
Afterwords I used Smart Switch to reinitialize the phone, writing my phones S/N and that failed as well but at least that made my phone boot into a different recovery where it said to connect to Kies. Once again I used Smart Switch and this time it was successful 100%. My phone even booted into the OS and was working, however, while using it, after 10 minutes the phone restarted into Download mode with emmc read error.
So all in all the phone is functional but it starts to lag and restart. Now I'm kinda stuck again since I've tried to flash the firmware I got from Samfirmware through Odin, it succeded but it just doesn't boot, it goes to Recovery, tries to apply an update and I get an error.
Is there anything I can do? I can't believe the emmc could've broken just from trying to flash that custom rom, especially that afterwards I was even able to boot into the phone.
Thanks for reading and I appreciate the help.

engwee said:
Hello. I had gotten this Note 4 phone which had a custom recovery installed on it but the rom seemed to be official, on 5.1
The first thing I did was go to samfirmware and flash a 6.0.1 rom, it went fine, phone was working properly. Then I got greedy and wanted to test a Note 7 ported rom. Flashed TWRP recovery and from within I flashed RamROM http://forum.xda-developers.com/note-4/snapdragon-dev/rom-sm-n910g-ramrom-t3400349 , I downloaded the one from post#2 , the N910F one that my phone is and after it flashed to ROM it simply stopped working. My phone no longer booted, was booting me directly into Download mode with emmc read error. I kept trying to flash the stock rom which I previously flashed and it would fail.
Afterwords I used Smart Switch to reinitialize the phone, writing my phones S/N and that failed as well but at least that made my phone boot into a different recovery where it said to connect to Kies. Once again I used Smart Switch and this time it was successful 100%. My phone even booted into the OS and was working, however, while using it, after 10 minutes the phone restarted into Download mode with emmc read error.
So all in all the phone is functional but it starts to lag and restart. Now I'm kinda stuck again since I've tried to flash the firmware I got from Samfirmware through Odin, it succeded but it just doesn't boot, it goes to Recovery, tries to apply an update and I get an error.
Is there anything I can do? I can't believe the emmc could've broken just from trying to flash that custom rom, especially that afterwards I was even able to boot into the phone.
Thanks for reading and I appreciate the help.
Click to expand...
Click to collapse
read this - http://forum.xda-developers.com/note-4/help/note-4-issues-t3453048
there are links to more threads related to your issue.
Short version though:
it is dying. install wake lock application, add it to start up and set settings to #4.
accept the fact that your phone will eat the battery faster and one day WILL die completely

Thanks for your response. Regarding the Wake lock application, I'm starting to look into it, I asume I'll have to be rooted. I'll try to recover it again using Smart Switch and then I can only hope I can install TWRP and still have it functional.
Previously when I was able to get it working with Smart Switch, entering the recovery messed everything up. It said it was applying an update and that got stuck.

engwee said:
Thanks for your response. Regarding the Wake lock application, I'm starting to look into it, I asume I'll have to be rooted. I'll try to recover it again using Smart Switch and then I can only hope I can install TWRP and still have it functional.
Previously when I was able to get it working with Smart Switch, entering the recovery messed everything up. It said it was applying an update and that got stuck.
Click to expand...
Click to collapse
no need to be rooted, just download, install and set it to autostart

I'll try it if I somehow manage to get the phone working again, Smart Switch just fails now midway through.

golden_m said:
no need to be rooted, just download, install and set it to autostart
Click to expand...
Click to collapse
Is this the app you're talking about? https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en
What exactly does it do?
I managed to restore it eventually with Smart Switch, it took quite a few tries, then I switched to my Macbook when I saw the app was available on it too and the 3rd try succeded. I only did it because I saw the 2nd try had the % much higher than the first.

engwee said:
Is this the app you're talking about? https://play.google.com/store/apps/details?id=eu.thedarken.wl&hl=en
What exactly does it do?
I managed to restore it eventually with Smart Switch, it took quite a few tries, then I switched to my Macbook when I saw the app was available on it too and the 3rd try succeded. I only did it because I saw the 2nd try had the % much higher than the first.
Click to expand...
Click to collapse
yes, that is the app.
i've read it does not allow your phone to go to sleep mode.
drains the battery faster, but this is the only way to keep note 4 working without swapping its motherboard...

I have a question, my gf recently bought a note 4 and we may swap our phones and if we do, i'll flash CM and tinker with it because i find this phone very interesting, just a question, does this bug affect the N910C (exynos) model? Do i have something to worry about? Because the phone is warrianty protected and if it's the case, i don't want to break it. I hope someone will shed some light on this

pattern passcode lockout issue

Hi all. had an issue while trying to load up LinageOS last night. Was having trouble with keeping root. Seem to have solved that by using Magisk 11.6 and the SUaddon rather than any superuser version.
Anyhow as part of this i went back to a TWRP backup of which i had 3 different versions (stock and lineage) available being a bit ocd with backups. They all flashed ok, but for ALL of them, when the phone booted it kept telling me had wrong pattern when i tried to unlock. Not good. Thought only way back was to factory reset and do all the app loading and setup again.
After a bit of searching found this thread and this post.
https://forum.xda-developers.com/showpost.php?p=69189392&postcount=65
Worked a treat.
The other methods didn't and i suspect are obsolete.
Anyow, posted for info if anyone else runs into this problem. Success dependent on having working TWRP and being able to boot to that as you need to use the File Manager capability in TWRP.
Seeyahs!

Same thing happened to me last week, when I tried lineage, found the answer on HTC forum,.
So avoid that from happening , before you make a backup, unlock all securities( pin, password, fingerprint) then make a backup, next time you restore your backup, it will boot without any issues.

ta for that. will try.

7.0 Update Crashed my Device. Custom Roms won't take. Stock Rom crashes, too

I received an update push from Motorolla that installed Nougat. After that, my phone would crash every 3-10 minutes. I did all the troubleshooting I could find online. I contacted support and they wanted me to spend $150 to get it "refurbished." Of course, it sure seems like a software problem, so that wouldn't help me anyways...
I turned to custom. After rooting, installing SuperSU and TWRP, I couldn't get several versions of AICP or Lineage to ever boot (stuck on loading screens). I also tried all the advice from this thread.
I went back and installed the stock Rom using f2fs , and the phone would get to the "hello moto" part of the boot up, then crash and reboot. I tried again using EXT4, and it worked, but just like before I ever begun, my phone was crashing every 3-10 minutes. However, the first crash wasn't until after I made a phone call, and my phone had been crash free for about 20 minutes before that call.
I'm a I.T. guy, but I'm not a "phone" guy. But it seems to me that there must be some other software that was modified during the update that is causing the problems that isn't part of ROMs. Something in the Kernal, or a driver folder or something?
Also, is there a way to get crash reports? So maybe if I at least go back to the default ROM and wait for it to crash, I have some info to work with?
Any help is greatly appreciated, thanks!

Flash full stock 6.0x for your model/region.
Important:
Without bootloader, gpt. Don't try locking BL.
Links you can find in my signature.
Try normal boot and after success any custom.
You cannot allow any ota update after it.
Some customs are only for Nougat modem/radio - don't flash it. @Kaivian

Ok, I got most of that, except I don't know what gpt refers to and am not getting any hits on search.

My signature - flashing stock - without bootloader & gpt.

So, I installed a 6.0 stock ROM and got tons of errors. I tried a 2nd time, still got tons of errors. Needless to say, stock 6.0 didn't boot. I decided, "The heck with it" and tried installing Lineage 7.1 again... and it worked! It finally booted up entirely. However, now I get a "Sim card missing" notification. Can I just reinstall part of something... like the modem? so I can keep this "working" lineage boot? Or am I starting over yet again?

Repeat
from
fastboot flash modem ...
to
...fsg.

dzidexx said:
Repeat
from
fastboot flash modem ...
to
...fsg.
Click to expand...
Click to collapse
This caused it to not boot.
I went back to 6.0 and turned off auto-updates. I'll try again sometime when I have time. I did like the custom rom a lot, just couldn't use it as a phone xD

Softbricked my phone, Noob needs help.

Hey!
So I got the 9.0 pie on my Xiaomi MiA1 and I decided to test it and I was pretty disappointed, so I decided to try to revert back to 8.1 oreo. I unlocked the phone, fastbooted twrp, wiped the data and tried using miflash to install the rom and also tried flashing it through twrp. I have been having this problem for 2 days now, i successfully install the OS but then I get stuck in a boot loop and now I can't even get past the android one logo and it keeps loading there. I didn't do a backup, I regret that. I can't remember how many times I already try flashing different roms but nothing really seems to work, in fact seems like it's getting worse since before it would actually boot until it asked me to put my SIM card PIN but then it would reboot constantly, but as I said before now it wont get past android one screen. Also maybe its worth mentioning that i try using lazyflasher already a few times and that there was a time that it actually worked but it got automatically updated to 9.0 pie again so back to the start and, as i thought that i knew what i was doing, i just tried redoing what i did before to install 8.1 again and disable automatic updates before connecting to the internet. I can go to fastboot mode and I can use twrp doesn't seem like I have a problem there, any help is appreciated!

maybe just can let 9.0 install , looks like is the only way that u have for a dayle phone

Mig979 said:
Hey!
So I got the 9.0 pie on my Xiaomi MiA1 and I decided to test it and I was pretty disappointed, so I decided to try to revert back to 8.1 oreo. I unlocked the phone, fastbooted twrp, wiped the data and tried using miflash to install the rom and also tried flashing it through twrp. I have been having this problem for 2 days now, i successfully install the OS but then I get stuck in a boot loop and now I can't even get past the android one logo and it keeps loading there. I didn't do a backup, I regret that. I can't remember how many times I already try flashing different roms but nothing really seems to work, in fact seems like it's getting worse since before it would actually boot until it asked me to put my SIM card PIN but then it would reboot constantly, but as I said before now it wont get past android one screen. Also maybe its worth mentioning that i try using lazyflasher already a few times and that there was a time that it actually worked but it got automatically updated to 9.0 pie again so back to the start and, as i thought that i knew what i was doing, i just tried redoing what i did before to install 8.1 again and disable automatic updates before connecting to the internet. I can go to fastboot mode and I can use twrp doesn't seem like I have a problem there, any help is appreciated!
Click to expand...
Click to collapse
You can install stock Pie via Mi Flash tool.
Sent from my Mi A1 using XDA Labs

Unable to flash RN7

Hello everyone xda users / developers. I got one problem. I sat on the MiRoom firmware. After that, I wanted to install EvoX. Before installation, I made a backup of MiRoom so that if something comes back to it. Everything worked well. And I decided to return to MiRoom. So I installed backup and rebooted smart. I noticed that the phone was loading for a long time. But the phone turned on. But I could not unlock it. I installed a script that removes the lock password. Everything worked fine but there were bugs. And after that I decided to return to Official Rom Stable. But I could not install it. Since the phone was not detected in Fastboot. The problem is that I can’t even go into Recovery because the smartphone hangs on the Redmi splash screen. I decided to install the firmware via EDL but could not. Since I get the error Only nop and sig tag can be recevied before authentication. How to solve this problem? And is there any way to solve this problem?