Hi All,
I'm really not sure how to go about with this so hopefully I can get some help here. I have a Note 4 (N910T) model which was never able to do OTA update from it's 5.1.1 state. It'd download the patch and upon reboot, it'd say installation fail.
Eventually I went into the rabbit hole and used Odin to try to update the phone to 6.0.1. No luck either as it'd just get stuck on aboot. I rebooted the phone and tried to use Smartswtich from samsung and hoped that it'd update using that. Not only does it not work and stuck in the "Odin Mode (fast track)" screen, it eventually tell me that I need to go through recovery to get it back.
I didn't know what to do at that point, so I've decided to try my luck again with Odin. This time, the patch went through successfully with my surprise. However upon reboot after the patch is installed, it gave me an error "DRK not found" error. I simply reboot the phone and all seems to be working. On 6.0.1, no lagging issue, no wireless/mobile network issue, nothing.
However, I do want to know if I still have an error of DRK not found, and would like to patch that hole before any problem occurs. Can any one help? I haven't rooted the phone yet.
bump, any help would be welcomed. Thanks!! :crying:
Is it still giving that error upon every reboot or it was only on the first reboot? If you aren't having other issues and your IMEI / service / etc is fine, then nothing to worry about.
You also kept mentioning "patch". This is not common usage. What file did you flash via Odin?
Thanks for the reply!! this is what i downloaded to update the firmware using Odin:
rootmygalaxy.net/download-install-n910tuvu2epe3-marshmallow-t-mobile-note-4 (http at front)
the IMEI seems fine, and it doesn't show the error upon reboot except the first time. However the phone seems to freeze quite often now for no reason at all. Not sure how to troubleshoot that one.
es0tericcha0s said:
Is it still giving that error upon every reboot or it was only on the first reboot? If you aren't having other issues and your IMEI / service / etc is fine, then nothing to worry about.
You also kept mentioning "patch". This is not common usage. What file did you flash via Odin?
Click to expand...
Click to collapse
oc9653 said:
Thanks for the reply!! this is what i downloaded to update the firmware using Odin:
rootmygalaxy.net/download-install-n910tuvu2epe3-marshmallow-t-mobile-note-4 (http at front)
the IMEI seems fine, and it doesn't show the error upon reboot except the first time. However the phone seems to freeze quite often now for no reason at all. Not sure how to troubleshoot that one.
Click to expand...
Click to collapse
Did you install the 1st link there from the Download button or the 2nd one for the n910t3 file located @ androidfile?
I actually used another firmware today and so far it seems to not lag AS much.. but still freezes with no apparent reason:
http://forum.xda-developers.com/note-4-tmobile/development/roms-10-29-2014-t2922618
The one that I downloaded was N910TUVS2EPG2_N910TTMB2EPG2_TMB = v6.0.1 = Build date Thu, 07 Jul 2016 13:33:23 +0000 = NEWEST UPLOADED FIRMWARE
The reason I flash again is because I tried to root my device using CF_auto root, which upon reboot, caused an error of "Kernel is not Seandroid enforcing" on boot menu.
Oh and the DRK error comes back everytime after i flash the firmware, but it only appears once, and no more on subsequent reboots. My IMEI looks fine but my S/N upon typing *#60# is (none)
bump .. phone is rebooting more and more, and it's freezing more often now... help please!!
Related
I've had Cyanogenmod 9 nightlies on my SGS2 since April. I didn't install every single one, but pretty much only those with good ratings, specifically those that had no complains about battery drain and heating...
Currently on the 06-28-2012 nightly. This ran fine at first, but over time, it started to occasionally crash into Kernel Panic. I figured I'd just pick a new nightly, but then I ended up having to travel and installation of a new nightly got delayed.
Now I'm home, and I can't use the phone at all, cause it crashes into Kernel Panic almost as soon as I unlock the screen after Android finishes booting. The last thing I see up in the message bar is "WhatsApp error" and the screen goes dark. It won't stay on long enough for me to uninstall WhatsApp or select factory reset from the system menu.
I don't think its a problem with WhatsApp, cause WhatsApp used to run fine, while Kernel Panics originally mainly seemed to happen after I got a "storage full" message. In response, I deleted a load of pictures after rebooting, to make sure there's free space, but it kept crashing occasionally, till now, its just unusable.
I've tried to flash a stock Samsung ROM (I9100XWLPG_I9100XXLPX_I9100NEELP4_HOME.tar.md5) but that hasn't been working either.
Kies drivers are installed on my Laptop. Odin sees the phone too.
I followed the instructions from the rom page, changed no settings in Odin, just picked PDA and selected the ROM.
Odin goes "Added" when I plug in the phone, verifies the ROM, then the whole thing hangs on "setting up connection"
So I unplug, pull the battery and then reboot, which works fine, but once booted, it won't stay on longer than a few seconds.
Anyway, does anyone have any clever ideas how I can get out of this Kernel Panic loop?
Tsais said:
It won't stay on long enough for me to uninstall WhatsApp or select factory reset from the system menu.
<snip>
Anyway, does anyone have any clever ideas how I can get out of this Kernel Panic loop?
Click to expand...
Click to collapse
What's preventing you from factory resetting from recovery?
Lack of knowledge is preventing me!
How do you factory reset from the "Kernel Panic Download Mode"...?
Download Android Commander from here:
http://androidcommander.com/
Boot your phone, don't unlock.
Start Android Commander, navigate to /data/apps and delete WhatsApp's apk (com.whatsapp1.apk or something like that) or rename it to .apk.bak
Restart your phone without unlocking.
Hope the errors gone.
I have a sprint note 4. I don't have it activated currently and use it as a tablet of sorts. Recently it's been giving me problems and I've wanted to break it. I got it about 2 years ago, and since then I rooted it, then installed twrp recovery, then flashed custom software. The software I used was called Dr.Ketans I believe, it combined the note 5 and s6 edge plus softwares. It started to crash occasionally so I installed cyanogenmod onto it. It worked for a bit, but now when Turing the device on, it takes like 10-15 minutes to boot up. And it only stays on for 5 minutes before it crashes and freezes. When it does that, the only way I can boot it up again is take the batter out and put it back in a few times because sometimes I get an error message. The error message barely happens but it says something along the line of "cant boot up". If I use twrp, my phone doesn't freeze. I've tried reinstalling the software, I've tried formatting the entire phone and refreshing. Nothing seems to work. I've even tried changing my kernel but I'm not entirely sure what it is, and how it affects the phone. I'm not the smartest with phones, but I'm good with following directions and googling. If anybody can help me I'd greatly appreciate it cause I've been dealing with this issue for 3 months.
Reinstall the original firmware and make sure it doesn't freeze / crash with it and then you can reinstall the custom software. Make sure that you have the required recovery, bootloader, and baseband version to run the newer custom roms. The requirements should be located in the OP.
I appreciate the response. I will try this as soon as possible. Should i use odin to flash or would it be possible to use twrp recovery? Also, what do you mean when you say the requirements are in the OP?
You should use Odin to recover to make sure you have a fresh start.
The requirements of the rom you pick afterwards should be in the OP.
Hey all,
My phone updated today and ever since I cannot move past the initial lock screen. When unlocked, the UI appears to crash and send me back to the lock screen. My pin code works for turning the phone off, restarting the phone and putting it into emergency mode, which indicates some sort of UI crash.
Because this is a new account I can't post a link to a video of the issue directly, but the YouTube video code is: 8ZhlH-Tt-NU
I have tried the standard fixes like wiping the cache partition and booting into safe mode, but these don't seem to make any difference. Unfortunately I never logged into my Samsung account on this device, so their 'Find My Mobile' service is not an option. I am however signed into my Google account on the device and it does have wifi/network enabled.
The phone is running PPR1.180610.011/G965FXXU2CSA8
On the phones internal memory is a bunch of photos from a recent trip to Japan, I'm a fool for not backing these up sooner but I would hate to lose them.
Has anybody experienced anything like this before, and is there any way for me to get back into the phone, or atleast recover the photos that I took?
Thanks!
Edit:
One potential route out of this I can see is sideloading the same or a subsequent OTA update using ADB to hopefully fix the issue. Unfortunately despite some digging I can't find any updates that will allow installation from: PPR1.180610.011/G965FXXU2CSA8
If anybody has any information on this specific firmware version (Is it beta 3? beta 4? ect.), its installation path and where files relating to it may be listed/hosted it would be appreciated. Also how disasterous would it be to take a mismatched OTA upgrade and modify the metadata to allow it to be sideloaded onto the phone? I assume this would almost certainly break the OS completely but I'm not too sure.
You can try to flash your firmware again with ODIN, but with the HOME_CSC (Important!)
profi_fahrer said:
You can try to flash your firmware again with ODIN, but with the HOME_CSC (Important!)
Click to expand...
Click to collapse
Thanks for the reply Profi I had no idea using HOME_CSC would retain user data. I have tried flashing a few different versions of Pie (wish HOME_CSC) using Odin but with no luck, every time the phone boots I have the same problem. Do you know if there is a sure way to downgrade to Oreo while retaining user data? I have seen a few posts of people attemping this and getting stuck in bootloops, eventually requrining them to factory reset.
To give a final update on this. I attempted the Oreo downgrade, upon reboot the phone was stuck in a bootloop so I updated to Pie again. When the phone booted I tried the pin code as quickly as I could, and after some glitchy graphics on the screen it unlocked. From here I turn on the stay awake while plugged in feature in the developer options and managed to transfer all my data over to PC.
I don't believe it was the firmware changes that actually made any difference, because any further attempts to put my pin in, to remove the pin code for example, failed and cause the same crashing behaviour.
All data is recovered, I have factory reset the phone and all appears to be behaving as normal again. If anybody stumbles upon this with the same issue, all hope is not lost, but unfortunately I was unable to determine a realiable way to overcome it. It seems in this case it was just dumb luck.
Thanks for the assistance.
Hi, after playing a lot with my SM-A510F it seems that I managed to brick it I did so many things I barely remember But I believe the important things are:
- I had a custom ROM (with Android 7 if I remember correctly). Playing with the options, I accidentally reenabled OEM lock, which triggere the FRP lock and now I cannot boot it.
- I tried installing a stock ROM (not sure if the proper one) but it failed and now it says "An error has ocurred while updating... Use the emergency recovery function in the Smart Switch PC software"
- I tried installing again TWRP to install ROMs from there but the FRP lock does not allow it.
- I tried installing other ROMs but couldn´t find the appropiate one. With some ROMs it throws the error "Sw check failed, Device 4 Binary 1" And with others "Device 8 Binary 7".
I am currently donwloading some more ROMs from other posts I saw but it will take some, so I would like to get some help as I assume the same problems will persist.
Also, how the hell do I force power off? The things I saw didn´t work. If I press VOL DOWN + PWR it always restarts and goes into the Error screen again.
Thank you for the help!
DrJotauVe said:
Hi, after playing a lot with my SM-A510F it seems that I managed to brick it I did so many things I barely remember But I believe the important things are:
- I had a custom ROM (with Android 7 if I remember correctly). Playing with the options, I accidentally reenabled OEM lock, which triggere the FRP lock and now I cannot boot it.
- I tried installing a stock ROM (not sure if the proper one) but it failed and now it says "An error has ocurred while updating... Use the emergency recovery function in the Smart Switch PC software"
- I tried installing again TWRP to install ROMs from there but the FRP lock does not allow it.
- I tried installing other ROMs but couldn´t find the appropiate one. With some ROMs it throws the error "Sw check failed, Device 4 Binary 1" And with others "Device 8 Binary 7".
I am currently donwloading some more ROMs from other posts I saw but it will take some, so I would like to get some help as I assume the same problems will persist.
Also, how the hell do I force power off? The things I saw didn´t work. If I press VOL DOWN + PWR it always restarts and goes into the Error screen again.
Thank you for the help!
Click to expand...
Click to collapse
[emoji24][emoji24][emoji24][emoji24][emoji24] Dude you should of stood on stock like who goes in developer settings and re-enables oem unlocked
([emoji3590]09-09-18[emoji3590])
PoochyX said:
[emoji24][emoji24][emoji24][emoji24][emoji24] Dude you should of stood on stock like who goes in developer settings and re-enables oem unlocked
([emoji3590]09-09-18[emoji3590])
Click to expand...
Click to collapse
Yeah... I didn't know what that was until I screwed up. I had some roaming issues and I was checking that everything was OK...
DrJotauVe said:
Yeah... I didn't know what that was until I screwed up. I had some roaming issues and I was checking that everything was OK...
Click to expand...
Click to collapse
If you can get into download mode it should have a line saying AP SWREV B:? K:? S:?
The B:? Is your bootloader ( binary ) number. You will have to flash this version number or higher. You can not downgrade firmware. Bootloader number is the 5th number from right of firmware being downloaded.
You could try flashing stock firmware and if you know your Google account may let you back in to your system ( requires internet connection ).
spawnlives said:
If you can get into download mode it should have a line saying AP SWREV B:? K:? S:?
The B:? Is your bootloader ( binary ) number. You will have to flash this version number or higher. You can not downgrade firmware. Bootloader number is the 5th number from right of firmware being downloaded.
You could try flashing stock firmware and if you know your Google account may let you back in to your system ( requires internet connection ).
Click to expand...
Click to collapse
Yeah that worked! I tried one of the ROMs I was downloading and followed that numbering that you mention. Thank you very much!! I got tired of trying random ROMs.
I'm having a strange issue after flashing latest firmware on my Tab S7 (SM-T870)...
When I try to flash an update with odin I'm using "HOME_CSC" as I want to keep the data on the device. However it results in a boot loop to recovery where I have 3 options
1. Restart the phone
2. Factory reset
3. Check logs
Restarting the phone just restarts it and boots to the same menu.
I've checked the logs and saw an error saying:
Unable to set property "ro.boottime.init.mount.cache"
I've tried wiping cache in recovery as well, but that didn't help.
Anyone here who can help me out?
Thanks!
Lif3mau5 said:
I'm having a strange issue after flashing latest firmware on my Tab S7 (SM-T870)...
When I try to flash an update with odin I'm using "HOME_CSC" as I want to keep the data on the device. However it results in a boot loop to recovery where I have 3 options
1. Restart the phone
2. Factory reset
3. Check logs
Restarting the phone just restarts it and boots to the same menu.
I've checked the logs and saw an error saying:
Unable to set property "ro.boottime.init.mount.cache"
I've tried wiping cache in recovery as well, but that didn't help.
Anyone here who can help me out?
Thanks!
Click to expand...
Click to collapse
Maybe try to reflash previous firmware version.
There is no need to run after the lastest update.
Vntnox said:
Maybe try to reflash previous firmware version.
There is no need to run after the lastest update.
Click to expand...
Click to collapse
No I tried it but only factory reset does help -.-
This is why I hate Samsung for Security reasons after a f***ing Update ...
I have the same problem, but i didn't update from Odin.
Just OTA september update, and the phone randomly goes in bootloop like once in a week.
Same here. Does anyone have any news?
same here. im in a bootloop and not even factory reset helps. i can access recovery and download mode and have flashed newest firmware three times via Odin with "pass," wiped cache, name it i've done it. I'm despondent. Does
Samsung not have the equivalent of Oneplus's MSM tool? four days have i worked furiously to save my phone.
sorry to revive, but I'm having this issue as well on my z fold 4.
Factory reset helped for about a week, and back to bootloops every 3 min or so.
PASS received in Odin, had to use micro usb cable with C-adapter as c->c did not allow Odin to complete flash (stuck at ~95% on "Super").
Not sure which error in the logs apply, but the "unable to set property "ro.boottime.init.mount.cache" to "0": error code: 0xb, try count 1-3" seem to be cause for alarm.
Has anyone fixed this?