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
Hello all
I am having a little bit of trouble with my TWRP recovery after flashing an updated version of a custom ROM, i have been using for a while.
I am using the latest version of the Pure Nexus ROM, and am currently un-rooted. I earlier want to try and clear my davlik cache as i was having a few little issues with some things, and wiping this has previously fixed the issue, i rebooted into the TWRP, and was asked for a password, which i thought would have been the PIN i use to unlock my phone. This then failed, and it proceeded to try and decrypt the partition. I left it doing this for about 20 mins, but nothing happened.
After reading up a little more, and trying a few different potential passwords to no avail, i read up that the password that TWRP was asking me for was related to the fact i had my phone set to ask for password on boot.
I removed this, and tried again. This time, TWRP just got stuck on the splash screen when trying to boot. Nothing happened for a good 10 minutes.
After putting the PIN settings back on, it goes back to asking for a password, that it wont take.
Whats my next option here, im kinda stuck. I really dont want to have to wipe the phone as i have just spent the best part of a week after flashing my new ROM getting it all back to how it was after flashing the new custom ROM i am using..
All help, much appreciated, thanks in advance
What version of TWRP are you using ?
No issues on TWRP 3.2.0.3
Sent from my Nexus 6P using Tapatalk
I'm on version 30.20
Okay, so usually I'm quite savvy when it comes to technology, but this one's stumping me.
Yesterday afternoon, I turned my phone off to go into work. It was working quite normally before then. When I get on break, however, I find that my phone won't get past the main logo. I figure that my phone needs a reflash, so today I went to reflash the xXx rom. Still no luck. I tried flashing stock OOS Beta 3, but then my phone went into a recovery bootloop. I tried flashing those two roms several times, but now my phone just stays in a recovery bootloop.
I'm pretty sure this isn't software-related, but I want to be wrong. That's why I'm posting here first, just in case it isn't.
I didn't do anything for it to go into a bootloop, I just turned it off after a normal day, and now it won't turn back on.
If you are decrypted you need to flash the no verify zip for OOS to boot up. With xXx anything from the version of Magisk used to one of the mods you chose in the aroma installer can cause problems. Your best bet is to boot into TWRP, format the data on your phone using the option in the wipe tab, connect your phone to a computer--it will be recognized like an external harddrive--copy and paste a full ROM zip for stock OOS Oreo onto your phone and then flash it with TWRP. Also make sure you are using one of the recommended versions of TWRP for OOS Oreo. The best version right now is the one from Codeworks. Good luck.
Hi!
So i've recently had some issues with my Samsung galaxy s8+
With the introduction of the new Pie Beta update i thought it would be cool to try it out!
I had to downgrade my firmware and so i did via ODIN.
This failed initially duo to a bad cable, i quickly replaced with OEM one.
Alright! We are able to boot into the OS, i stuck my SD card in the phone and updated its firmware succesfully.
HOWEVER; My phone would reboot once in a while out of nowhere and i figured i was on a Beta that might cause issues
started removing all of my apps in hopes it would help. Unfortunately in either safe mode OR clean factory wipe.. I was still running into reboots.
Alright ok, eventho no one on the forum complained about reboots.. I'll take my loss and i'll just flash back to stock..
However; it seems like the phone just freezes up now in everything!
Freezes up in Download mode; Freezes up during boot of new OS
i was able to reflash via ODIN by the way it just wont let me load into the OS. I've tried different ROMS
I can't wrap my head around it!
Should i just take my loss and buy a pixel 3 ? i was hoping to extend my contract with the new Samsung Galaxy S10+ but i can't do without a phone for a month.
Thank you in advance!
UPDATE:
I've succesfully been able to load into the OS at the moment. Let's see how long this lasts!
Aaand about 6 Minutes later i get a reboot
Yeaaah, it's dead.. After rebooting more and more frequent
It doesn't turn on anymore.
GG
So tl;dr version - i was using my tablet, saw an update to magisk, installed it, now it boots to black screen while running sambones rom
[SM-P580] [BQK1] SaMBoNeS
TWRP 3.2.3.0 --> 3.3.1.0
longer story:
i was trying to get a game to run, it wasnt...and realized it has been a while for a restart, so i checked to see if anything needs to be updated and saw magisk needed an update. i didnt note what version it was before but it was a version or two earlier than what it was trying to install.
rebooted to blackscreen no samsung logo
have tried restarting a dozen times, booted to TWRP, tried to force normal system boot through the UI, nothing.
I tried installing a new kernal [SiriKernel], it made it to the samsung logo, waited 15 - 20 minutes and it never made it past. restored a backup using TWRP
updated TWRP to 3.3.1.0, still no luck.
i had this problem a long time ago, and cannot figure out how i fixed it....it may have fixed itself but it isnt this time. any advice would be appreciated. I am trying to avoid wiping and starting again if at all possible because the problem seems familiar. also trying to stick to a rom for use with adaptive storage. if i do have to wipe if that can be done on a newer stock OS that's fine as well but last time i messed with this tablet it wasnt