Hello to everyone!
I need help about my s9, few days ago I installed LightROM on my s9(over the TWRP lastest version),everything worked fine,I was curios about installing the other kernel, which I did, I installed(whitewolf kernel) and after that Im not possible to boot my phone into the ROM, in case if LightROM is installed its looping in SAMSUNG logo, if AOSP is installed it boots into Download mode. Dont know why is phone acting this wierd now. Im downloading the default stock rom right now, Ill try to install it with Odin, hope that will reset everything back to normal. Im writing this thread in meantime while Im waiting maybe some of you knows the fix, so I dont have to download the stock rom(firmware).
Tried installing the stock kernel from AROMA installer, it doesnt change anything. If I set TG kernel to be installed, it passes the samsung logo but gives me encryption failed. I tried also installing the by pass for encryption but it gives me error "1" in TWRP.
Hope someone helps,Im out of ideas!
Thanks have a great day(atleast better than mine)
Related
I have been running CivZ ROM on my new Note 8.0 WiFi. Yesterday I tried the unofficial CyanogenMod port and this morning the tablet powered off of it's own accord. When I turned it back on it was stuck on the initial splash screening saying "Galaxy Note 8.0 N5110" etc. I definitely flashed the correct file and it worked for a while.
But, now I can't boot. I can boot into TWRP recovery, but whatever I flash, the tablet still won't boot. Any suggestions?
You will probably have to install the kernel separately.
cruise350 said:
You will probably have to install the kernel separately.
Click to expand...
Click to collapse
I just got back home planning to flash a kernel as you suggested. Before the kernel, I first did a total wipe and reflashed the CivZ FlexBeam ROM. And then it just worked, no separate kernel needed
Good news, of course. But I'd still like to know why that didn't work the time before. I think last time AROMA installer froze just before the end, so maybe it was failing to flash the kernel for some reason... Guess I'll never know for sure, just glad I have my tablet again.
Thanks for your help!
What's up guys!
Using ROM installer I flashed vanir 4.4 along with 4.4 gapps on my sprint gs3 sph l710. I wiped the cache and it looked as if it were installing fine but winded up getting stuck in boot loop mode instead. Now when I try to boot into recovery the twrp screen flashes and then it goes straight into bootlop mode from there. Now i cant acsess any of my backups. I can get into down load mode but unfortunately my computers messed up right now. I can't hit the run button on Odin because the screen is too big. I know it sucks!!! Does anyone know some tricks I can use or have any recommendations. Your help would be greatly appreciated! BTW.. I was running illusion 4.3 when this happened.
ddray said:
What's up guys!
Using ROM installer I flashed vanir 4.4 along with 4.4 gapps on my sprint gs3 sph l710. I wiped the cache and it looked as if it were installing fine but winded up getting stuck in boot loop mode instead. Now when I try to boot into recovery the twrp screen flashes and then it goes straight into bootlop mode from there. Now i cant acsess any of my backups. I can get into down load mode but unfortunately my computers messed up right now. I can't hit the run button on Odin because the screen is too big. I know it sucks!!! Does anyone know some tricks I can use or have any recommendations. Your help would be greatly appreciated! BTW.. I was running illusion 4.3 when this happened.
Click to expand...
Click to collapse
Can you try using this? http://forum.xda-developers.com/showthread.php?t=1746680
Maybe that'll work, you can use it to return to stock, and if anything I would recommend going back to stock before doing anything else. Also, it may not be the consensus of the site here but in my own opinion, I don't like using rom installer or goo manager or anything. I like doing it all myself in recovery. I've heard one too many stories of people getting hardbricked because their rom installer or whatever downloaded the international version of the rom they wanted :/ always best to check your own md5 checksums and make sure you're downloading the rom for your phone from your phone's forum.
As for the exact reason your phone did that? I couldn't tell you, maybe with a little more info someone more knowledgeable here could tell you
So i got my computer fixed. I havent tried the tool kit in the thread you recommeded. I decided first to use a stock file i have on odin first that has saved me from softbricks in the past. I set everything up hit start, watched the process complete with the pass. Now it shows the stock boot animation but still stuck in bootloop mode. I put it into recovery,which is now stock instead of twrp, wiped cache, davlik cache and factory reset then i reconnected to odin and reflashed the stock file. Still stuck in bootloop mode!!!! Plain reboot and same thing :/ so for the hell of it, i wanted to see if i can to my backups by restoring twrp. So i flashed my cf auto root and then flashed my twrp file and bam!!!! Twrp was full functioning with all my backups!!! :laugh: next i restored my latest illusion 4.3 rom and wala! Ive got a fully functioning rooted phone with a custom rom. I flipped through everything to make sure it looks good and it does. Except.... any photos and music that are saved to phone and not sd card are gone I dont understand, everthing else is backed. Contacts, call logs, messages, text messages, apps, customised settings etc...I even flashed my carbon rom that had the same music and pics. When i open gallery it shows the photo count in snapseed and others im looking for but then they all start dissapearing!!! i also dont understand why the stock file which has saved me from softbricks before didnt work. I dont know anything about checking md 5 checksums but if its worth the time ill do my research! Im happy i got my phone working but i would like to be more solid in what im doing. Maybe someone can help shed some light on this.
Hi.
Recently, I decided to unlock my bootloader and install TWRP onto my Moto G(2014), as I wanted to use a custom ROM. After much debate between CyanogenMod and Paranoid Android, I decided to go with ParanoidAndroid.
So today, I downloaded the ROM ZIP file, loaded it up onto my SD Card, and flashed away. After the flash, I started my phone (kinda.). The phone wouldn't start, it got stuck on the boot animation. Weird, I decided.
I turned my device off, redownloaded the ROM, put it onto my SD Card, and reflashed. Same problem, in fact, the phone is sitting right next to me as I type this, on the Paranoid Android loading screen.
I was wondering if I should keep waiting, or if this is a problem. If it's a problem, how can I solve it?
Thanks.
EDIT: New Problem. It got past the boot, but now it keeps saying "Encryption Failed". It tells me to factory restore the phone, and when I do that and restart the phone, it says the same error. It's a viscious cycle. Any help please? I completely forgot to make a backup of my original stock ROM, so I have no way to use my phone anymore. The faster the reply, the better.
Thanks.
Hit your device forums and ask. It's a device specific issue.
I recently rooted and installed TWRP on my 2018 Moto G6 Play so I could try pixel experience pie ROM and had similar issue... I finally had to go find the factory stock ROM and reflash it to my device... Then I tried again with a custom kernal with no dm- verity from github source... That worked for me.. If you have Ann questions PM me...
Sent from my SM-G965U using Tapatalk
Hi everyone,
I just had a very frustrating experience tonight and I really need help because I don't understand why my phone would behave like that.
I wanted to update my phone and go to android 6.0 marshmallow, I tried to flash the latest builds of both SkyDragon and CandySix but here's what happened :
_Concerning SD, the flashing stopped while installing busybox and it said something like "Some symlinks failed"
_Concerning CandySix, the flashing went all the way completely right, everything was OK but when I tried to boot the ROM, it would just boot into teh recovery instead.
Please excuse my english and help me, I really want to update my phone to marshmallow...
Hello Everyone,
I've been up literally all night (I know, that old line) trying to fix what happened. I bought this phone last year. It was unlocked and rooted. I never updated because it was never giving me issues. But the lagging and battery has finally got to me. So I decided to upgrade to this new rom(http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-0-t3094423).
It looked clean and minimal bloat, just the way I like it. However, I didn't get past updating the Bootloader. As soon as I did in Odin it went into a bootloop. Try as I might I couldn't get into recovery. Luckily I can still get into download mode. So I read up and found that I should flash the original firmware. Unfortunately it failed because I tried to upload an older version. Is there anyway I can flash this rom via odin? Sorry for the noobish questions here but it's past 8am and I've just about given up. If I see recovery is not seandroid enforcing or rev check fail s6 device 3 binary 2 I'm going to lose my mind lol. I did have TWRP installed if that makes a difference. Just can't access it. Any help would be greatly appreciated. Thanks guys
P.S. I know I used buy instead of buy but can't fix it. It was really early in the morning haha
Ok I managed to download the stock MM version for my phone. I still have bootloop issues but I'm in recovery mode at least. However not TWRP though, if I try downloading a custom recovery it says the dreaded "recovery is not seandroid enforcing" also it says Device does not have DRK. Any guesses here?
Well, I've just about given up. I've searched extensively and it appears that the fix is to download a different kernel. However, the G925T has no support yet for any custom MM kernels. I made a backup of my phone via TWRP before this whole mess but the problem is I can't get to it. And to be honest I'm not entirely sure if it's still there. Here are the steps I have taken thus far.
1. Downloaded MM Bootloader: this was the start of my issues. Started bootloop, couldn't get into recovery.
2: Attempted to download original LP firmware: Odin denied it, there was another version I download from zidroid called "downgradeable". Obviously did nothing because I was still running MM bootloader and was effectively the same thing.
3. Downloaded stock MM firmware: Finally was able to boot into recovery but it was useless as it was the stock one. Also wouldn't boot up due to "Device does not have DRK" and boots straight into download mode. Tried to download recovery but none of them worked. Kicked me back to "Recovery not Seandroid enforcing".
So this is where I'm at, I just want to get back to my old device I honestly would rather have a clunky phone than one that doesn't work at all. Is it possible to downgrade back to LP and get back into TWRP and flash my backup? Do I still have root after taking all those steps? Any help would be greatly appreciated because this has officially ruined my weekend?
I guess I'm talking to myself here but if anyone ever encounters this issue at least it will be documented if I ever do fix it.
I managed to get into TWRP. Although arter doesn't have a kernel that supports our system yet. The twrp recovery he has does, ours is compatible with the fi variant. Again that's only the recovery no the kernel.
So I was at a cross roads, do I restore my backup or do I continue with the download. Unfortunately none of those options worked. When restoring the backup I get stuck on the samsung page with "kernel not enforcing" or whatever. Do be fair, before I did this with my device it had already said that. So I gave it some time, but alas no luck. And the same issue with the when I tried to continue the download. I'm a little lost as to how to continue now. I just want my device back.
try dd the mm firmware
Nickle60 said:
I guess I'm talking to myself here but if anyone ever encounters this issue at least it will be documented if I ever do fix it.
I managed to get into TWRP. Although arter doesn't have a kernel that supports our system yet. The twrp recovery he has does, ours is compatible with the fi variant. Again that's only the recovery no the kernel.
So I was at a cross roads, do I restore my backup or do I continue with the download. Unfortunately none of those options worked. When restoring the backup I get stuck on the samsung page with "kernel not enforcing" or whatever. Do be fair, before I did this with my device it had already said that. So I gave it some time, but alas no luck. And the same issue with the when I tried to continue the download. I'm a little lost as to how to continue now. I just want my device back.
Click to expand...
Click to collapse
Not sure what state your phone is in. To begin with, the not Seandroid message with recovery is normal, if you are on marshamallo. If you are on LP then you get the same with the Kernel message when it boots up. BOTH are normal depending on which Firmware you are on. But that said you shouldn't be trying to downgrade, if that's even possible. Have you tried smartswitch and the emergency software restore function. It will wipe out everything on your phone but at least will boot up with the latest MM. Then simply Odin the arter TWRP and then install XTRESTOL which I am using NO PROBLEMS on my TMobile 925T variant. NOT sure about the DRK root key problem. But when you install stock MM with smartswitch you should have also gone into settings and enable developer settings to make sure OEM unlock was enabled before doing anything else.
Lastly, the Arterkernel will actually work fine as far as booting up. The ONLY issue is call audio which we all are waiting for a patch, or a kernel that supports everything. But, I have TWRP installed that arter kernel, and the phone boots up just fine. You just do NOT have call audio. My suggestion at this point is smartswitch. Just know your serial number so that when asked you can plug that in to the menus smartswitch goes thru before wiping and restoring current MM latest and greatest.
Docmjldds said:
Not sure what state your phone is in. To begin with, the not Seandroid message with recovery is normal, if you are on marshamallo. If you are on LP then you get the same with the Kernel message when it boots up. BOTH are normal depending on which Firmware you are on. But that said you shouldn't be trying to downgrade, if that's even possible. Have you tried smartswitch and the emergency software restore function. It will wipe out everything on your phone but at least will boot up with the latest MM. Then simply Odin the arter TWRP and then install XTRESTOL which I am using NO PROBLEMS on my TMobile 925T variant. NOT sure about the DRK root key problem. But when you install stock MM with smartswitch you should have also gone into settings and enable developer settings to make sure OEM unlock was enabled before doing anything else.
Lastly, the Arterkernel will actually work fine as far as booting up. The ONLY issue is call audio which we all are waiting for a patch, or a kernel that supports everything. But, I have TWRP installed that arter kernel, and the phone boots up just fine. You just do NOT have call audio. My suggestion at this point is smartswitch. Just know your serial number so that when asked you can plug that in to the menus smartswitch goes thru before wiping and restoring current MM latest and greatest.
Click to expand...
Click to collapse
Thanks for the reply, I don't have the box for the phone and couldn't boot it up so that was a no go. But luckily for me I decided to give that rom one more go. I flashed bootloader and modem again, then flashed TWRP, and finally installed the rom. And boom! It worked, and it's better and faster than ever. I'm not sure what all that other mess was but I am going to say I have everything I need at the moment and won't be flashing anything anytime soon. I've learned a great deal through this process though. Thanks for everyone's help.