Database Develop

Trying to install 4.4 Rom, falling at every hurdle.

Hi There,
Just wondering if anyone had any ideas why my phone refuses to co-operate!
Basically, after getting bored of the stock rom when I first got my phone, I somehow managed to install a CM based rom. That worked, but I got bored of the fact that the camera never seemed to work right, and some apps didn't work/ were graphically buggy. Assuming it was just a badly ported graphics driver or whatever, I found a way, using FlashTool, to revert to the stock rom (C6603_10.3.1.A.0.244_Generic UK to be precise). I wasn't sure exactly what it did, but it was back how it used to be. sorted.
So, since kitkat made it's way to the XZ, I thought I'd try one of those roms, being the curious bugger that I am. The process I ended up going with eventually was:
>Downgrading Kernel to a lower version because the root explot wouldn't work on 10.3.1.A.0.244
>Rooting using "DooMLoRD_Easy-Rooting-Toolkit_v18"
>Upgrading kernel to one that would accept a recovery
>Installing TWRP
>Booting into recovery, CWM appeared instead. Strange, I thought. Oddly, mount USB wouldn't work at all, so I had to boot the phone back up to transfer the kitkat rom over
>Trying to flash the rom gave me an error number 7
>Boot Loop, at which point I just flashed 10.3.1.A.0.244 again.
I've tried this twice now, first with DooM Kernel, and then once with a different one. Neither CWM or TWRP have worked properly. Any help? Or am I just cursed?
Cheers

Tried this again, did literally everything I could think of and still no dice. Help? Have I somehow forced my phone to be on stock software forever?

If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk

eryen said:
If you dont unlock your bootloader, you can not use any kind of custom kernel.
That means aosp or aokp based firmwares can not run over locked bootloader.
Locked bootloader checks sign of kernel, if not certificated you will stuck on bootloop.
If you want to use any kind of custom rom... basicly.
1. Backup ta partition. " so you can revert any time you want."
2. Copy firmware zip file tou your internal or external sdcard.
3. Flash custom kernel. "Most of kernel have recovery option build in".
4. Boot in recovery mod. "Mostly press volume down while booting"
5. Insall custom rom.
6.a wipe dalvik-cache
6.b factory reset
Old setting might work or not with new rom. So first try to wipe dalvik- cache. If you stuck on boot loop or any kind of problem, just boot in recovery again and run factory reset.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Hey, thanks for your reply!
I had unlocked the bootloader when I first got the phone and just assumed it would be permanent. Would flashing it back to stock firmware re-lock the bootloader?
But yes, assuming my boot loader is still unlocked ( I have tried to check and it doesn't seem to be locked) I have been through those steps basically. I am fine to flash a kernel with a recovery but the recovery never works properly/ at all. I can root the phone no problem though.

Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app

shoey63 said:
Best to extract the boot.img from the zip file of the ROM you want to flash, and flash that first. Then flash the ROM from its recovery.
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone

SuburbanKnight said:
Cheers, I'll give that a go - I was under the impression that you weren't supposed to flash kernels that weren't designed for the currently installed ROM though? It just seems that any kernel I flash isn't working properly so I didn't think doing that would play any nicer with the phone
Click to expand...
Click to collapse
You're not actually going to boot into your current rom after flashing the kernel.
Flash the kernel via fastboot, then boot into recovery and flash the rom.
All this should be covered in the installation instructions of whatever rom you're trying to flash in any case....
Sent from my C6603 using Tapatalk

Well, that seems to have done it! Thanks very much for your help.
So, I guess the moral here is that if you're on stock and need a recovery to flash a new ROM, always use the boot.img from the ROM you'll be using.
Thanks again - I'd never seen that said before but quite possibly I wasn't paying attention!

Tried to flash a rom and now I've wrecked my phone!

So I flashed the Alliance Rom for my t-mo Note 4 and all I get is the boot logo.
I've gone through with Odin and the CF auto root junk, used TWRP to wipe and flash this rom.
I got TWRP on there, but I can't seem to put any files onto my phone. Like I select mount, and when I try to drag a file over, windows wont let me.
You see, I've got this error, and it says Kernel is Not SEandroid enforcing. I have looked for a fix, and people say that I need to flash a file called stocK_kernel, which I have.
I can't get this file onto the device it seems. Anyone have any ideas of what is going on?
EDIT: tried flashing another rom using odin and now all i get the t-mobile logo...
and I can't register for sammobile because I can't pass the captcha !! It's frustrating... I can't download what I think I need >_>
Any help would be awesome
I know this is a typical problem, I've been around XDA for a while, but never made an account until I decided to actually root and try to flash my device.

DaltonMplz said:
So I flashed the Alliance Rom for my t-mo Note 4 and all I get is the boot logo.
I've gone through with Odin and the CF auto root junk, used TWRP to wipe and flash this rom.
I got TWRP on there, but I can't seem to put any files onto my phone. Like I select mount, and when I try to drag a file over, windows wont let me.
You see, I've got this error, and it says Kernel is Not SEandroid enforcing. I have looked for a fix, and people say that I need to flash a file called stocK_kernel, which I have.
I can't get this file onto the device it seems. Anyone have any ideas of what is going on?
EDIT: tried flashing another rom using odin and now all i get the t-mobile logo...
and I can't register for sammobile because I can't pass the captcha !! It's frustrating... I can't download what I think I need >_>
Any help would be awesome
I know this is a typical problem, I've been around XDA for a while, but never made an account until I decided to actually root and try to flash my device.
Click to expand...
Click to collapse
A ROM using ODIN? Which one? If it's Lollipop...and you are on the T-Mobile logo screen, how long did you wait? It takes ~10 minutes to boot. But, if you are on the Samsung screen, there is a problem. So, I'm currently thinking you are not waiting long enough?

Try putting your rom in the extsd or internal and flash from there.
I would grab the stock firmware and flash that using Odin. Don't forget to factory reset using stock recovery after flashing stock firmware.
Just start over.
Then root and install twrp, once your back at square one, then put your rom of choice on either of the SD locations and flash using twrp.
A bootloop after flashing a rom is usually, in my experience, a kernel issue. So it couldn't hurt to have an alternate compatible kernel to flash if you need it.

If you have TWRP all is not lost. If you flashed the stock ROM then you probably don't have TWRP anymore. Its just about impossible to wreck this phone by flashing ROMs. I would ODIN to the stock COD6 build. I believe there is a thread with all the files you need in one zip. Follow those instructions and it should get you back to stock rooted and you can go from there with flashing ROMs again.
Sent from my SM-T900 using XDA Free mobile app

No the rom doesn't use Odin. But I imagine the person had to root and flash a custom recovery as well. The rom of course had to be flashed in recovery.

[ROM][ROOT][RECOVERY][XPOSED]EVERYTHING YOU NEED for Tab S2 9.7 LTE (T815)

This is a sum up of most resources I found online for Tab S2 9.7 LTE(T815/T815c) for those of you who don't want to find anymore
including ROM, ROOT, RECOVERY, XPOSED FRAMEWORK and KERNEL
ROM:
Original stock ROM, UNROOT and UNMODIFIED.
choose from here and download
Chinese special version ROM(T815c)
Download from Dropbox
Download from BaiduYun (for Chinese users) with password: tdfv
Flash with Odin
Open Odin, click AP and select the file above, then flash.
Also a website for sum up of modified ROMs, here
RECOVERY:
TWRP 3.0.0, download from here, flash with Odin with the same steps above.
ROOT:
Flash CF auto root with custom recoveries(like TWRP above), download from here
XPOSED FRAMEWORK:
Flash from here with custom recoveries, then install Xposed app to control the modules.
KERNEL:
Flash with Odin
PERMISSIVE KERNEL for normal T815 devices, here.
PERMISSIVE KERNEL for Chinese T815c devices, here.
Source, details and further issues, go to: https://forum.xda-developers.com/tab-s2/development/kernels-exynos-regular-permissive-t3523348
Please let me know if you have further problems, or directly go to the source pages for details.
Cheers!

Hi OP!
Thanks for this article, it really is helpful,but I have 2 questions about it:
if I want to use the linked "ROM: Original stock ROM, UNROOT and UNMODIFIED." on my rooted, TWRP recovery 815 device , I will have to unroot my device also have to install stock recovery beforehand, am I right? Because if I try to install it via Odin it will brick my Tab S2.
I am asking it, because it was more than half a year since I updated my Tab S2, because it has stock ROM on it, with TWRP and root and I didn't wanted to deal with everything before update (unroot, stock recovery, ROM install via odin, twrp install again, root again etc.), since there is not stock update that I could istall via TWRP unfortunately.
My other question is what is Chinese special version ROM(T815c)? Why is it special? I am European so I don't speak Chinese either, not to mention my device is the basic 815, not 815c.
Thanks.

NandorHUN Hi OP!
Thanks for this article, it really is helpful,but I have 2 questions about it:
if I want to use the linked "ROM: Original stock ROM, UNROOT and UNMODIFIED." on my rooted, TWRP recovery 815 device , I will have to unroot my device also have to install stock recovery beforehand, am I right? Because if I try to install it via Odin it will brick my Tab S2.
I am asking it, because it was more than half a year since I updated my Tab S2, because it has stock ROM on it, with TWRP and root and I didn't wanted to deal with everything before update (unroot, stock recovery, ROM install via odin, twrp install again, root again etc.), since there is not stock update that I could istall via TWRP unfortunately.
My other question is what is Chinese special version ROM(T815c)? Why is it special? I am European so I don't speak Chinese either, not to mention my device is the basic 815, not 815c.
Thanks.
Click to expand...
Click to collapse
Hi, if you want to update your system to the latest version, I'm afraid in most of the cases you'll need to unroot at least unless your supersu has a recover OTA option in it, otherwise if you want to flash ROMs that I listed or other ROMs need to be flashed with Odin, you'll need to clear all the data in your device and flash, of course you can directly flash it without any wipe, but possibly something will go wrong. In your case if you only want to upgrade your system, you can find other ROMs here in xda and flash it with recovery, but even if you use recovery, there's no guarantee that nothing will go wrong without wiping anything. My suggestion is to backup your data first, and maybe find a recovery update package and directly flash it with recovery, no need to unroot or wipe other than Cache, but in case anything went wrong, you can use ROMs provided here and flash them with Odin to recovery your device, of course, if something went wrong, you'll have to wipe everything to do that.
About the Chinese version, if you don't use the T815c version, thedn you don't need to care about that, it's for Chinese buyers who bought the Chinese version.
Let me know if you have further questions.

Jackz314 said:
Hi, if you want to update your system to the latest version, I'm afraid in most of the cases you'll need to unroot at least unless your supersu has a recover OTA option in it, otherwise if you want to flash ROMs that I listed or other ROMs need to be flashed with Odin, you'll need to clear all the data in your device and flash, of course you can directly flash it without any wipe, but possibly something will go wrong. In your case if you only want to upgrade your system, you can find other ROMs here in xda and flash it with recovery, but even if you use recovery, there's no guarantee that nothing will go wrong without wiping anything. My suggestion is to backup your data first, and maybe find a recovery update package and directly flash it with recovery, no need to unroot or wipe other than Cache, but in case anything went wrong, you can use ROMs provided here and flash them with Odin to recovery your device, of course, if something went wrong, you'll have to wipe everything to do that.
About the Chinese version, if you don't use the T815c version, thedn you don't need to care about that, it's for Chinese buyers who bought the Chinese version.
Let me know if you have further questions.
Click to expand...
Click to collapse
Thanks!
Could you send me a description how to unroot? After that I should flash the stock recovery via Odin and flash the ROM via Odin as well, am I right?

NandorHUN said:
Thanks!
Could you send me a description how to unroot? After that I should flash the stock recovery via Odin and flash the ROM via Odin as well, am I right?
Click to expand...
Click to collapse
Actually what you should do is to wipe all the data in the phone and then flash the ROM, no need to unroot or flash recovery separately, wipe can do all that for you, of course if you don't want to wipe all the data, you can try and directly flash the ROM(it's risky but sometimes it also works perfectly), then if something went wrong, you can wipe the data and flash again to recover.

Jackz314 said:
Actually what you should do is to wipe all the data in the phone and then flash the ROM, no need to unroot or flash recovery separately, wipe can do all that for you, of course if you don't want to wipe all the data, you can try and directly flash the ROM(it's risky but sometimes it also works perfectly), then if something went wrong, you can wipe the data and flash again to recover.
Click to expand...
Click to collapse
I did not know it should be that simple, I owned a HTC, LG and Huawei phones but in all of them I have to unroot and install the stock recovery.
Oh, ok. I should do a full Wipe with Odin? I know there's an opinion in TWRP too.

Help needed - Samsung J5-sm10fn (touchwiz) stuck booting into TWRP recovery

So I tried installing Xposed Framework by flashing it's ROM, but after I did it, I rebooted my phone, but every time I do it, it always boots into TWRP recovery. I tried fixing it by looking in the setting and I used a backup I made before doing all this crap and I restored, but my phone still boots only into TWRP recovery mode. I would really appreciate it if anyone could help me. Thanks.
PS. My phone is rooted and it has TWRP

TribalPaint said:
So I tried installing Xposed Framework by flashing it's ROM, but after I did it, I rebooted my phone, but every time I do it, it always boots into TWRP recovery. I tried fixing it by looking in the setting and I used a backup I made before doing all this crap and I restored, but my phone still boots only into TWRP recovery mode. I would really appreciate it if anyone could help me. Thanks.
PS. My phone is rooted and it has TWRP
Click to expand...
Click to collapse
Is it possible that you used the wrong Xposed for your device or SDK version? I can't imagine that restoring a backup didn't fix it. Did you try wiping system in TWRP first?
Things you can try:
- Flash the "Xposed Uninstaller" zip file in TWRP, which should always be on your device when you are flashing new versions of Xposed.
- Reflash TWRP in Odin. This should fix a recovery loop.
- Wipe system, data, dalvik, cache in TWRP, then try restoring your backup.
- As a last resort, you can download the latest stock firmware for your device from the sammobile site, flash it in Odin, let it boot once, reflash TWRP, wipe in TWRP and restore your backup (if you were running a custom rom you liked or something), then flash the correct Xposed for your device & android version.
Hope this helps!
Sent from my SM-N920T using Tapatalk

bogarty said:
Is it possible that you used the wrong Xposed for your device or SDK version? I can't imagine that restoring a backup didn't fix it. Did you try wiping system in TWRP first?
Things you can try:
- Flash the "Xposed Uninstaller" zip file in TWRP, which should always be on your device when you are flashing new versions of Xposed.
- Reflash TWRP in Odin. This should fix a recovery loop.
- Wipe system, data, dalvik, cache in TWRP, then try restoring your backup.
- As a last resort, you can download the latest stock firmware for your device from the sammobile site, flash it in Odin, let it boot once, reflash TWRP, wipe in TWRP and restore your backup (if you were running a custom rom you liked or something), then flash the correct Xposed for your device & android version.
Hope this helps!
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Hello. I already tried zipping the uninstaller for xposed but it did nothing, I also tried wiping dalvik cache and all, but no luck. I also think that my backups are just not functional. Now I'm left to just reflashing TWRP and if that doesn't work I'll have to flash the original stock firmware for my phone. I have spent already 2 days with constant searching for ways to fix my phone and not being able to do other things because this has been taking up my time and my patience, so I really appreciate every bit of fixing my phone that I get. Since I am new to all this I would be very grateful if you could send me the links to the correct files for my device and also give me a tutorial on what to do. As I appreciate any support, so I'm thankful for you helping me But until then my device is still not able to boot regulary but rather boots to TWRP

TribalPaint said:
Hello. I already tried zipping the uninstaller for xposed but it did nothing, I also tried wiping dalvik cache and all, but no luck. I also think that my backups are just not functional. Now I'm left to just reflashing TWRP and if that doesn't work I'll have to flash the original stock firmware for my phone. I have spent already 2 days with constant searching for ways to fix my phone and not being able to do other things because this has been taking up my time and my patience, so I really appreciate every bit of fixing my phone that I get. Since I am new to all this I would be very grateful if you could send me the links to the correct files for my device and also give me a tutorial on what to do. As I appreciate any support, so I'm thankful for you helping me But until then my device is still not able to boot regulary but rather boots to TWRP
Click to expand...
Click to collapse
Also, if I try to reflash TWRP, do I have to reflash the original firmware first, or I can just go straight ahead and just reflash TWRP?

TribalPaint said:
Also, if I try to reflash TWRP, do I have to reflash the original firmware first, or I can just go straight ahead and just reflash TWRP?
Click to expand...
Click to collapse
Update:
I fixed my phone, and here's what I did, so if anyone is new here with the same issue I had, I hope this can help you. So first of all as I said I kept booting to TWRP, later I tried reflashing TWRP, but I remembered that I missed something in ODIN, so I just pulled the cord and my screen after rebooting just said something along the lines of "An unexpected error occurred while updating software, please recover using Samsung Smart Switch." after that, I tried Samsung Smart Switch, but it was no luck for me, so then I used the last resort. I went on sammobile.com, I searched stock firmware for the exact model I had and then I checked the stock firmware that was available. Since I'm from Latvia, I picked the Baltic region, then I downloaded the latest stock firmware. After a long time, I downloaded the file, and I checked the instructions on how to flash it, I flashed the stock firmware, and then my problem was fixed, my phone was working again and now I have Android 7.1.1 as I used to have Android 6.0.1 and I had ZERO file loss However as you flash the stock firmware, TWRP get "flashed" out and same with root if you have it, and in that case if you want TWRP and root again, I highly suggest Meziani's YoutTube channel, because he gives simple and working tutorials on how to do it I'm glad if this helped anyone.

General Flash / Rooting Question S10e (970F)

Hi guys
Hope you are well, just wanted to find out, i rooted my phone using the patching method (Magisk). Thereafter i installed TWRP (Placing TWRP / VBMETA file in one archive) Flashed it, and it worked, i was able to log into recovery, i then formatted data, rebooted and wiped Dalvik etc etc. (Note i did not install the Multidisabler (The instructions i followed did not mention anything about it) I then installed LOS with GAPPS,
I know would like to try and either install Beyond ROM, or if need be back to complete stock (CTF3) as im missing DEX.
Can i just log back into TWRP - WIPE and installed Beyond ROM? (As we used to do in the old days - jumping between ROMS) Or should reflash MAGISK TWRP process everytime? If this is the case i would want to rather move back to stock...
Can i just flash back in ODIN and all will be good? Or is there any risks? (Ie in bricking the device etc)

Have you checked out this thread?
https://forum.xda-developers.com/galaxy-s10/how-to/proper-to-root-s10-device-twrp-s10-10e-t4015813

StoneyJSG said:
Have you checked out this thread?
https://forum.xda-developers.com/galaxy-s10/how-to/proper-to-root-s10-device-twrp-s10-10e-t4015813
Click to expand...
Click to collapse
Hi there! Thank you very much, this is a fantastic guide. Exactly what i was looking for