Guys, I'm on N900XXUEBOK2 stock deodexed rooted.
The problem is, the stock kernel unable to boot up the deodexed ROM, is it LL specific problem?
Coz when I restore the odexed rooted System, the stock kernel can boot it up correctly.
When I deodex it again, only *OLD* custom kernel (SueMax v2.2) can boot it properly but with some glitches like Security Policy menu in Settings FC.
Also, the Find My Device's remote controls toggle unable to stay on. Is it LL problem or bcoz I'm using custom recovery. Coz in previous KK, I can enable it no mater the kernel/recovery.
Related
I can't seem to find a thread where there are steps from how to get custom rom when you begin with stock without root.
I had an s2 and I could flash philz recovery (temporary recovery) and install custom rom from there, but I don't know how to do it on the S4.
Is there any tutorial from how to get the custom rom installed on the s4?
(this is the hardest part, the rest is simple)
ps: yes, I know how to recover and fix broken phone, I always use a AOSP rom, but I can't seem to understand how to get a custom rom installed on a phone that is 100% stock without root.
Nevermind, I know how to do it.
Hello all, i need some help returning to stock as i'm out of ideas.
I was using prerooted 4.3 firmware without KNOX files, then i flashed Carbon Rom based on CM. It is not working (as you are not able to remove apps) so i decided to go back to stock (standard stock with KNOX) So i downloaded latest firmware from sammobile and flashed it using Odin.
Just after flash phone reboots than tries to run recovery (and says SECURE FAIL: Recovery). Then it reboots and system is up and running but there is no WiFi,
How can i go to clean and not modified stock firmaware?
What firmware you exactly flash on your device? Same version that comes out the box?
Hi.
I have a telecom new zealand i9505. I attempted to install a custom recovery but I'm not sure if it worked. I do have a recovery mode I can boot into but it doesn't have many options and I assume it's the stock Samsung recovery. My phone is currently running Android 4.3 but doesn't autoupdate bc I now have a modified the recovery.
Can someone suggest either
1. What stock rom should I flash to. Do I have to flash to another stock 4.3 rom using odin or can I flash a 4.4.3 rom? If I flash using odin can I use the autoupdate feature under settings?
2. Is there a fast stable rom that has built in auto updates without having to worry about flashing and backing up etc.
The reason I want to update is.
1. The phone is sometimes sluggish.
2. There was a Google update that caused a bug whereas every time I pah home button it askes which home screen and it will not remember the defaults and the ONLY solution was to uninstall the updates which means I don't have Google now anymore.
Thanks
Kiwi
Guys i have 910F...Running ANK4 KITKAT. I tried to root it with CF-Auto-Root-trlte-trltexx-smn910f. The rooting tutorial said i had to disable auto reboot and should perform a battery pullout after rooting....everything went fine untill i pulled out the battery and put it back in after root...the phone turns on and says "RECOVERY IS NOT SEANDROID ENFORCING" And just restarts...i am stuck in a bootloop whenver i try to root it.....i was able to get the phone back online after flashing stock 4.4.4 in ODIN, but what am i doing wrong here....why cant i root this phone?
This happened to me yesterday - you cannot root a stock rom v5.1.1 with CF Auto Root, if you try it will end up in a bootloop. There is a way around this if you search the Note 4 CF Auto Root thread - pages 121 and 124 if i remember rightly.
But i am not on 5.1 i am on stock 4.4.4....anyone else might wana help?
dork997 said:
But i am not on 5.1 i am on stock 4.4.4....anyone else might wana help?
Click to expand...
Click to collapse
4.4.4 what the hell is that?
If you try gingerbread, you will never update a rom. The best android on earth. (just after the eclair, froyo was a major disappointment)
dork997 said:
Guys i have 910F...Running ANK4 KITKAT. I tried to root it with CF-Auto-Root-trlte-trltexx-smn910f. The rooting tutorial said i had to disable auto reboot and should perform a battery pullout after rooting....everything went fine untill i pulled out the battery and put it back in after root...the phone turns on and says "RECOVERY IS NOT SEANDROID ENFORCING" And just restarts...i am stuck in a bootloop whenver i try to root it.....i was able to get the phone back online after flashing stock 4.4.4 in ODIN, but what am i doing wrong here....why cant i root this phone?
Click to expand...
Click to collapse
Are you trying to keep a stock ROM and root it?
I would upgrade to lolipop. I run AICP on my n910f and I love it, best ROM for our phone at the moment in my opinion. To go to a custom lolipop from kitkat you'll need to first flash a lolipop stock ROM, here Then you can flash your custom recovery via odin. Then you can flash any custom ROM via zip file from your recovery software as usual. Custom ROMs are usually rooted by default already so once you've flashed it you're already rooted. If you search the forum you can find a rooted stock ROM if that is your preference.
guts100 said:
Are you trying to keep a stock ROM and root it?
I would upgrade to lolipop. I run AICP on my n910f and I love it, best ROM for our phone at the moment in my opinion. To go to a custom lolipop from kitkat you'll need to first flash a lolipop stock ROM, here Then you can flash your custom recovery via odin. Then you can flash any custom ROM via zip file from your recovery software as usual. Custom ROMs are usually rooted by default already so once you've flashed it you're already rooted. If you search the forum you can find a rooted stock ROM if that is your preference.
Click to expand...
Click to collapse
stock 4.4.4 rom
dork997 said:
stock 4.4.4 rom
Click to expand...
Click to collapse
Did you try a factory data reset after using autoroot? Go into the stock recovery and do a factory data reset after auto root and it may boot after that. If you want to keep 4.4.4 stock ROM then just flash an already rooted stock ROM. They're in the ROM section for your device. That's what I would do if you're having issues with cf auto root.
I have a J5 Pro SM-J530Y variant.
I installed several Custom ROMs from ROM Section. Most of them said that their Custom ROMs support all models of J5 Pro (2017). But, after I install it, it has a bug on Baseband which is Unknown. I tried many ways to fix it, like restoring EFS and Modem backup, reflash Modem And BL file via Odin, and also reinstall ROM twice. They said that I need to upgrade my device's bootloader (firmware) to the latest one. I did it but still Baseband became unknown Everytime I install their Custom ROM.
Then I doing a research. The problem is on Kernel. I tried to restore "Magisk Patched Stock Kernel" after installing those custom ROMs, Baseband is fixed. I also tried other way by replacing boot.img-dtb and boot.img-zImage from stock kernel to custom kernel, and it's fixed the problem. Problem solved here for OneUI custom kernels only, because there's only OneUI with working Baseband kernel for my device (stock kernel obviously).
But, then, I found a thread that we can install GSI on this device. I tried to install one (treble GSI). Most of them are bootable, but the problem come again. Baseband Unknown. I tried to fix it using the way I did before but it got bootloop. I also tried to replace boot.img-dtb and boot.img-zImage from stock kernel (OneUI) to custom treble kernel for my device, it got bootloop. Of course, because I use stock kernel base OneUI not AOSP.
How to fix this? Anyone please help me to fix this issue. There's no development for my J5 Pro SM-J530Y variant. I need guidance to fix the Baseband Unknown which is causing by Kernel. I also need a guidance to fix or edit boot.img-dtb and boot.img-zImage, do I need a device tree blob files? Please tell me how to do. Please help