Hi, I installed TWRP 3.2.1-0 (newer versions like 3.5.x have a poor interface) for my Samsung Galaxy Core Prime SM-G360T. I used it to install Magisk first from patching boot.img using the magisk app. After flashing I pulled the battery, and when I booted the phone, a message displaying "Set Warranty Bit : kernel" is shown on my screen while also showing "Samsung GALAXY CORE Prime POWERED BY android", and won't continue any further. I tried again using TWRP's reboot option instead of pulling the battery, and the same thing appears.
I also tried installing using the Magisk zip method after reflashing the stock OS (which works fine by the way, the stock OS), and the same issue appears.
It also appears when plugging the phone in to charge and the battery icon is displayed, normally a battery percentage is displayed and a little animation appears from near the charge port, but it doesn't continue past the initial screen either.
I am using the latest Magisk, v25.1 from their github page.
Is there anything I can do here? I really want to use magisk since they are open source, but am open to other methods by now since I have spent 10 hours on this.
(By the way, learned my lesson, not buying carrier phones ever again, only unlocked from now on, but I'd still like to root this one)
Related
update, read at the bottom.
Hi, I have a Samsung Galaxy Note 4 SM-910C which I have rooted after flashing a stock Samsung rom. If I recall correctly, I flashed a stock android 4 rom trough ODIN, did it a CF-Auto-Root and eventually updated android 5 through wifi (OTA). SuperSU was installed.
I have attempted to do a native full-disk encryption trough the default Security menu; the phone went into a black screen with a green outline android robot in the center, with no progress bar or text of any kind (I found the image online, but can't post it due to account lack of privilege) . It has been on this same screen for over 8 hours now.
The device was NOT in USB-debugging mode.
What are your suggestions? Should I try some kind of reset? Is it possible the process will resume and is taking so long due to the amount of files? Or I shouldn't expect it to work since I tried encrypting a rooted device?
I'm not worried about any files in it, but I'd like to make sure to be able to recover the phone without bricking it. I'll be leaving the phone plugged to the outlet and untouched for the foreseeable future...
Thank you very much.
UPDATE: I powered off the device (had to remove the battery) and when turned it on again was met with the "Encryption unsuccessful" screen. Then I turned it off and went into recovery mode by pressing and holding POWER+VOLUME UP+HOME. Even tough it displayed a warning - dm-verity verification failed - I chose wipe/factory reset and then rebooted the system and it seems to have worked fine. After the start splash screen and a notification that is was installing applications (bloatware), it brought me the Welcome to Samsung Galaxy configuration wizard.
I installed a few days ago AospExtended Nougat ROM, along with Lambda Kernel and Magisk
I worked fine for a few days, apart from Magisk haing a bug with "hide magisk"
Yesterday I plugged in my phone to my PC and I selected MTP mode and, as it was usual, it crashed and rebooted
This has been for me normal behaviour for about a year, so I wasn't worried
But it never booted back
It now boots ad infinitum, loading the LG screen for much more than usual and then launching the Android boot animation and never going into the ROM; I tried leaving it out for about two hours, it just won't boot
I also can't access recovery mode, pressing VolDown+PwrBtn just reboots it and then shuts it off
I was able to get it to boot in download mode but I never used it so I don't really know what I can or should do with it
Is there any way to recover my phone, let alone the data?
Should I just trash it and go buy a new one?
So i have flashed everything from android 4.3 to 6 and the same thing happens, powered by android and then boot loop at the blue screen (boot animation). Lineageos boots just fine, but the two roms i have found don't charge at all unless i put it in downloading mode and still just 65%, also camera did not work, and a lot of other stuff. Currently struggling to edit that boot.img thing but, it's just too much, i don't know this stuff. Worst case i'll wait for the official lineageos.
Bump !
Or to say it in other words, any solution for this ?
I am on the latest 6.01 b147 version and would love to boot w/o EDP attached.
Ender
Hi
I am stuck with Pulsing blue LED and the "Powered by Android" screen,
have access to both the recovery and the download Mode,
I also have Odin (version 3.13) on my computer along with TWRP (3.1.1 trlte and 3.2.1 version)
My device is a Samsung Galaxy Note 4 N910F bought in shop, no special carrier. It was bought in the Netherlands.
I have tried everything that I have read. The furthest that I can go is the Second Samsung Logo with the Flashing Light
Whenever I try to Flash the stock Firmware for my N910F, everything goes well in Odin but then when the phone reboots, it (sometimes) install the system update until 30% then shows erasing then either crashes right there and then or load the system update bar, completes it then shuts down.
I have tried multiple firmwares, even recovery firmwares. All the same problem. I can see the firmware is flashed, because when I enter recovery mode after I flashed a different ROM, it shows the version I flashed.
I cannot seem to install TWRP because it was never rooted.
Whatever I do, at some point, my phone either gets stuck in a bootloop, freezes with the LED light or shuts down.
And I have also proceeded to use different batteries.
Do you have any options?
Thank you
Heat????
I'm far from an expert here, but I've just experienced a similar problem where my N910F started boot looping / freezing within 15s to 2 min after unlocking. Unfortunately my micro Sd (SanDisk 256GB) was corrupted a week ago, so before doing anything else I did some research (XDA/YouTube) and probably found pretty much what you've found. I frequently change batteries so I could discount that as an issue. Someone suggested using the Samsung Smart switch here https://www.samsung.com/uk/getting-started/smart-switch/, but I haven't used it (yet) so I can't tell. I presume you had the latest firmware from Sams https://www.sammobile.com/firmwares/galaxy-note4/SM-N910F/.
My issue was that I needed to recover data, docs, photos, phone numbers etc. When boot looping the note 4 got very hot . In particular around and to the left of the camera (looking at the rear). Thinking it could possibly be the dreaded eMMC problem which also manifests itself by creating heat, I thought cooling the device might help. I placed the Note on a cooler box freezing block and voilà! No boot loop. I was able to remove all, but necessary apps and do a full copy to my PC. Storage was reduced from around 90% to 50% and memory 80% to 60%. It's now been stable for 12 hours, but the jury is still out. Next will be full reset with he latest available firmware 6.0.1 as mine was still on 5.1.1.
Good luck and hope this may be of some help.
I've got this problem, too, when using the unofficial Lineage 15.1 rom. SIM death and boot loop. After flashing the latest stock rom through odin, it passed but the screen was black and no system was installed. The blue notification light was constantly stuttering, though. And I couldn't even go to recovery!
When flashing, a 910F can get hot - use a cool temperature room and/or a fan blowing onto the device.
If it's not too late...
I have an S5 with stock Samsung ROM which I rooted some years ago with Magisk and TWRP recovery. For the last few years it has only been used as an alarm clock and I have forgotten how I set it all up in the first place, in fact I had forgotten that I ever rooted it. Up until now it has been working fine but I wanted to give it to my 9 year old daughter to use, so I did a factory reset on it through the normal Android menu. After that the phone works but will only charge in Recovery, not when its off or when its booted normally. Same cable and charger that I have been using up until now and I also tried others but didn't make any difference.
When the phone is off and I plug in the charger,it vibrates, the battery symbol comes up for a second and it displays the message "set warranty bit: kernel" then the screen goes off. The charging LED does not come on. Then after about 10 sec it does the same thing again: vibrate, battery symbol, message, screen off and just keeps going round that loop but never charges. When the phone is booted in normal mode it doesn't seem to detect the charger at all, nothing happens. In Recovery it charges perfectly but its a bit inconvenient!
I tried restoring the last TWRP backup that I had which seemed to contain all the partitions but it hasn't made any difference to the charging problem. It seems the phone has power and CAN charge but is deciding not to. Any ideas please how I can get it back into operation?
Model: SM-G901F
Android 6.0.1
Kernel 3.10.40-9709634
Build MMB29M.G901FXXU1CRH1
Magisk 19.3
Magisk Manager 7.3.4
Magisk version is old but I have not attempted to update it yet in case that makes the situation worse.
spencetj said:
I have an S5 with stock Samsung ROM which I rooted some years ago with Magisk and TWRP recovery. For the last few years it has only been used as an alarm clock and I have forgotten how I set it all up in the first place, in fact I had forgotten that I ever rooted it. Up until now it has been working fine but I wanted to give it to my 9 year old daughter to use, so I did a factory reset on it through the normal Android menu. After that the phone works but will only charge in Recovery, not when its off or when its booted normally. Same cable and charger that I have been using up until now and I also tried others but didn't make any difference.
When the phone is off and I plug in the charger,it vibrates, the battery symbol comes up for a second and it displays the message "set warranty bit: kernel" then the screen goes off. The charging LED does not come on. Then after about 10 sec it does the same thing again: vibrate, battery symbol, message, screen off and just keeps going round that loop but never charges. When the phone is booted in normal mode it doesn't seem to detect the charger at all, nothing happens. In Recovery it charges perfectly but its a bit inconvenient!
I tried restoring the last TWRP backup that I had which seemed to contain all the partitions but it hasn't made any difference to the charging problem. It seems the phone has power and CAN charge but is deciding not to. Any ideas please how I can get it back into operation?
Model: SM-G901F
Android 6.0.1
Kernel 3.10.40-9709634
Build MMB29M.G901FXXU1CRH1
Magisk 19.3
Magisk Manager 7.3.4
Magisk version is old but I have not attempted to update it yet in case that makes the situation worse.
Click to expand...
Click to collapse
Never mind, I got it working with a different charger. Very strange. The first charger works fine with my Huawei P20, maybe too high power for the S5? Although I thought the device only draws the power it needs even if the charger is capable of more.