Update:
I just figured it out that it is a kernel (not ROM) issue and hopefully @djvoleur will update UniKernel soon to fix this....
Hey guys,
I am here to seek help for an issue my phone has after I flashed the Renegade OJ1-V1 Rom.
How I flashed Renegade:
Odin OJ1 stock ROM --> Odin Kernel --> Odin TWRP --> Swipe everything (except internal storage) and flash Renegade in TWRP.
Issue I have:
If the phone is off and I try to turn it on, it will get stuck in the splash screen (the screen showing "Samsung Galaxy S6 Edge" even before the boot animation) and will not boot into the system. There is a workaround to turn it on normally: that is, to first boot into TWRP (which is fine) and then boot to system from TWRP.
Some more information:
The "reboot" option still works fine. That is, if I directly reboot the phone (instead of turning it off and manually turning it on later), there is no problem.
If you guys have any idea how to fix this, I would definitely appreciate it.
Flash version 8 of the unikernel
Related
Hi all,
Recently I updated my Nexus 5 from Lollipop to Marshmallow 6.0.1 (MMB29Q) - latest build.
everything stock works fine but, once I flash a customer recovery, in my case TWRP it stops working...I get either a startup loop or TWRP gets erased by stock recovery.
I tried various steps ...
flashed TWRP 2.8.7.1 - rebooted to boot loader was able to get into TWRP but, once I reboot system, everything works but TWRP is gone/erased and replaced by stock recovery?
Flash TWRP 2.8.7.1, then flash latest TWRP 3.0, reboot to boot loader and can get into TWRP but once i reboot into system, I am stuck on the initial boot loop.
I have to start from scratch of flashing system and boot etc to get past the loop and it still replaces TWRP with stock recovery.
I can always get into Fastboot but when I go to recovery it seems its being replaced by stock recovery.
anyone experiencing this issue? thanks for your help.
I guess I am doing something stupid but, not sure what...and thanks for your help
If you give more detail on the steps you are taking it will be easier for someone to help. Also, have you tried doing a factory reset when it bootloops?
thanks for the response..here are the details..
I had Lollipop with TWRP 2.8.7.1
yesterday, I downloaded latest build from android site...extracted all files....booted into bootloader and flashed all files..
rebooted - Marshmallow works perfectly...offcourse it not rooted yet or its locedback due to this flash
Scenario:1
So downloaded TWRP 2.8.7.1 and flashed it as recovery, no errors nothing...i rebooted to bootloader and went to recovery to confirm TWRP is there
I rebooted the system - TWRP gives option to root which I said yes so its rooted. I reboot system, this goes into bootloop - I wait for say 5-10 min in this loop mode and I see that adb can recognize the device but nothing else....its stuck in loop
when I force shut down by holding power button for few sec - and go back bootloader/recovery - TWRP is still there
***note*** I did factory wipe in TWRP but that did not fix above condition.
Scenario2:
exact same steps but after I flashed twrp2.8.7.1, I rebooted bootloader and flashed twrp 3.0 as well confirmed twrp 3.0 is flashed and rebooted system - phone start normally no issues - when I restart to bootloader - no TWRP exists, its replaced by stock recovery
Scenario 2, I tried couple of other ways and still the same thing happens - twrp 3.0 get erased.
not sure what I am doing wrong but TWRP doesn't stick
since this is my active device - i flash system.img and boot.img to get the phone to working condition
thanks for your help
Try flashing the latest supersu to get root.
audit13 said:
Try flashing the latest supersu to get root.
Click to expand...
Click to collapse
That did the trick.....thank you very much. I was using older version of supersu thinking it was latest.....I downloaded V2.65 and installed it and that fixed all my troubles..
muchas gracias
Title pretty much says it, I have a custom rom installed which works, but when reboot my phone, TWRP is automatically opened after the initial samsung logo. I usually have to reflash my custom ROM (without wiping any data besides cache and dalvik) and the ROM installer will then reboot into the ROM, however this means when my phone turns off, my recovery is booted up instead of the ROM. I'm really confused
S6 is a SM-G920F / ROM= Tyrannus v 28.1
Some background into the problem - [This is a quote from my previous post: http://forum.xda-developers.com/gal...ing-stock-t3423351/post67859895#post67859895] "When i tried flashing however, somehow ODIN froze and i made another stupid mistake of restarting my phone from download mode which resulted in the phone being froze on a screen saying " an error has occurred while updating the device software use the emergency recovery function s6 "
So after this happened i then flashed TWRP with odin to solve the quoted error message and i think it was at that point that the bootloader was configured to initialize recovery on bootup as oppose to the actual ROM, not sure though so any help on the matter would be greatly appreciated.
TL ;DR : S6 boots recovery instead of ROM - Possibly bootloader error?
Sooo... it fixed itself. All is well.
If anyone else ever has this problem all i can really suggest is perhaps going into terminal on TWRP and writing reboot? However, my one just fixed itself so we all good!
I rooted my device. Everything's all good.
I flashed a rom (xposed framework) using Flashify.
My phone started going crazy after the reboot.
Now I'm stuck in the samsung logo screen.
I need help.
I dont have TWRP Recovery or anything else. My recovery is still the Android Recovery.
I have tried wipe cache and wipe/factory reset. Nothing works after rebooting.
My option right now is downloading a stock ROM and installing it via Odin.
Problem is, I don't know if my phone is region locked and I cannot find my region/country stock ROM.
So I'm going to assume any of them will work as long as it has the same android and build version as my phone.
I cannot access my phone.
Only able to go into recovery and download mode. A normal boot will just stay stuck on the samsung logo screen for hours.
Any help is appreciated. I am very new to this, please help me.
Which device?
I attempted to switch custom rom and end up in a brick situation.
What actually happened:
I rooted my device and installed twrp successfully.
Then I found this thread: https://forum.xda-developers.com/mi-4i/development/rom-lineageos-15-0-t3671815
I was really interested in switching to custom rom and downloaded all necessary stuff.
(Here comes my mistake) I boot to twrp and flashed the latest firmware (8.1.5.0), wipe cache, latest rom build (LOS 15.1),wipe cahe,gapps,wipe cache and reboot to system. (all process altogether)
Now device stucked at MI logo and never booted to system again. And unable to boot to twrp mode too.
What i tried to resolve(but failed):
Device was showing lineage battery icon but nothing else was happening. So i decided to return back. I flashed my device with latest stock flashboot rom "ferrari_global_images_V9.2.3.0.LXIMIEK_20180414.0000.00_5.0_global_680c582f20" and successfully flashed it as while charging i got led light back and stock battery icon but issue remain the same. Stucked at boot loop.
I also tried Fastboot Flash Through CMD-Prompt https://in.c.mi.com/thread-334-1-0.html
But still not working. I think it must be due to firmware upgrade to oreo and if downgrade is possible, issue can be resolved but not sure and don't really know how to execute that.
Please help me in solving this issue and whatever suggestion you give please provide proper guidance or link to guidance as I'm still new to all this.
Video showing bootloop on mi4i device : https://drive.google.com/open?id=1ufwk8TNIUmycJUdjTmDBXj38-1cPCrBu
I was trying to get lineageos on my s6 edge+ but it is stuck in a samsung logo loop after being unable to flash the rom and now it won't go back into TWRP either.
Initially I flashed the official TWRP for the zenlte which worked fine, it just did not want to install the rom due to apparently not having any device data. (Rom is for zenlte, this device is . (or something along those lines))
after a few attempts and doing a quick wipe I flashed an unofficial twrp and thats when it started looping without being able to get back into recovery mode.
Download mode does still work after a power off but flashing the official twrp again makes no difference.
This is a little beyond me and I'm not entirely sure what is going on.
The last phone I installed a custom rom on was an s4 so I'm a bit out of the loop with this new security stuff. I would have expected to at least be able to boot back into twrp.
Ok some progress:
Recovery mode worked again after leaving phone off (but still attached to computer) for a while. (I had given up but decided to try again after a few hours)
Partitions were missing / corrupted. Did a full format.
Installing rom still gave the 'device type is .' message.
Edited the rom zip to allow "" and " " ( in META-INF\com\google\android\updater-script )
Flashed rom + gapps + magisk in 1 go.
This ended up in LineageOS trying to start but rebooting into recovery after about 5 minutes.
Re-instralled just the rom, this gave a few errors about Magisk missing, re-installed Magisk as well before wiping cache and rebooting.
Now it came up with the welcome screen rather quickly.
Weird, but problem solved any ways.
Thanks! That was also my problem.