Database Develop

[Q] cwm missing!!!

HI, I just rooted my galaxy note N7000 using dr kernel method.
I downgrade my firmware from 2.3.6 to 2.3.5 rootable stock firmware, after that i got superuser and cwm,
then i update to new stock firmware which is N7000DXLC2-2.3.6
now my
baseband Version: N7000DXLC1
Kernel Version: 2.6.35.7-N7000DXLC2-CL1039404
the point is, after i update to newer firmware, my CWM is missing but still got superuser and SuperSU.
can someone help me please??
(btw i readed a couple post before how to restore CWM, but i didn't found cf root kernel for LC2, which im sure needed to flash it via mobile odin)
THanks

I don't know for CWM but like you, I had both superuser and supersu after flashing.
After wiping data cache and dalvik, superuser was gone.

sp_setsuna said:
I don't know for CWM but like you, I had both superuser and supersu after flashing.
After wiping data cache and dalvik, superuser was gone.
Click to expand...
Click to collapse
Ok i'll tried to wipe data cache and dalvik.

Download cf root kernel for lc1, extract zimage file n put on sd card
Now.select kernel tab on mobile Odin, point to zimage file n flash.
Thats it, you.will get cwm.
Sent from my GT-N7000 using xda premium

dr.ketan said:
Download cf root kernel for lc1, extract zimage file n put on sd card
Now.select kernel tab on mobile Odin, point to zimage file n flash.
Thats it, you.will get cwm.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
thank you for the guide dr

dr.ketan said:
Download cf root kernel for lc1, extract zimage file n put on sd card
Now.select kernel tab on mobile Odin, point to zimage file n flash.
Thats it, you.will get cwm.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
i do as you said, flasih the kernel using zimage lc1, but after that my note restart everytime i turn on. what should i do??

go to recovery(vol up+home+powr), wipe cache, wipe delvic cache

Factory Reset my S6 with Odin No Network!

I rooted with ping pong root, followed these guides to do my "OTA" updates:
http://forum.xda-developers.com/att-galaxy-s6/general/g920aucu2aof3-flashfire-update-t3156221
http://forum.xda-developers.com/att-galaxy-s6/general/g920aucu2aof3-to-of4-flashfire-update-t3181135
Then I used this file with Odin, to factory reset:
http://forum.xda-developers.com/att-galaxy-s6/general/odin-tar-files-sm-g920a-t3103835
Now it seems to have factory reset it but it says I have no IMEI, network unknown, etc....
I am suspecting that its something to do with those updates I did and flashing the Modem drivers, which maybe need to be downgraded now? or if i can update my software somehow with a legit version?
Any help is greatly appreciated.
Gavin

To my understanding, the downgrade to OE2 from OE3 or OF4 causes these issues with the imei and such.
Sent from my SAMSUNG-SM-G920A using Tapatalk

from what I have gathered... seems right.
so I am thinking now if I can upgrade to OE3, or OF4 in a legit way... then my modem will work again....
but If i use the upgrades mentioned on those 2 threads, those are pre rooted? so ill just be rooted again (but working modem)
correct?

My files are working fine. the problem is that you're trying to keep root and the modem you flashed is NOT compatible with the bootloader you current have.

Sunderwear, no problem with your files at all, I think the problem is with me.
I am trying to remove root.
How can I put a bootloader on my device that will be compatible with my modem?

I had the same issues. I ended up using Odin to go to OCE, then OE2 then I used PPR to root, and used FF to go to OF3 then OF4. Cause a BUNCH of problemt so I went to BBuy and had them force a flash of the full OF4.
You could always try doing the Odin OI2 files and see if that leaves you fully updated with everything working. You will lose root and will not be able to downgrade.

Well, depending on your desired outcome (rootless OF4, or 5.1.1), you'll have to do slightly different things, both will wipe your phone completely.
To move to rootless OF4, just download the Full OTA from the bottom of the first post at this link this is where things get different.
The next step is to reboot your device to recovery, not download mode (hold power home and vol up). You may see a updating android icon, but nothing should be happening yet.
You should now see the manual menu for the recovery, select the sideload update option
On your computer with ADB, sideload the OTA zip Do not unplug your phone
Your phone should reboot and you're now running OF4 while rootless
For 5.1.1
Flash the ODIN files with ODIN

Please note, you must be already rooted for this to work: I made the same mistake of upgrading to of4. Here's what I did, and my phone works just awesome and is still rooted with the Of4 base band.
1. Odin 3.10.6 OCE2
2. Reboot, at this point you'll have no carrier signal/data.
3. Ping pong root, install flash fire.
4. Install Rayman's ROM, Clean ROM, or Dennis ROM with flashfire (wipe first!).
5. Download the of4 root update here. forum.xda-developers.com/att-galaxy-s6/general/g920aucu2aof3-to-of4-flashfire-update-t3181135 ONTO YOUR PC. unrar. Flash via Odin the two files you unrar'd according to these instructions:
In Odin put boot.tar.md5 in the AP slot.
Put modem.tar.md5 in the CP slot.
Leave all other settings alone and click start.
Reboot, and you should be up and running with cell data and carrier signal.

dave812 said:
Please note, you must be already rooted for this to work: I made the same mistake of upgrading to of4. Here's what I did, and my phone works just awesome and is still rooted with the Of4 base band.
1. Odin 3.10.6 OCE2
2. Reboot, at this point you'll have no carrier signal/data.
3. Ping pong root, install flash fire.
4. Install Rayman's ROM, Clean ROM, or Dennis ROM with flashfire (wipe first!).
5. Download the of4 root update here. forum.xda-developers.com/att-galaxy-s6/general/g920aucu2aof3-to-of4-flashfire-update-t3181135 ONTO YOUR PC. unrar. Flash via Odin the two files you unrar'd according to these instructions:
In Odin put boot.tar.md5 in the AP slot.
Put modem.tar.md5 in the CP slot.
Leave all other settings alone and click start.
Reboot, and you should be up and running with cell data and carrier signal.
Click to expand...
Click to collapse
Worked like a charm thxs

Won't boot...please help a fella out!

My phone won't boot past the att logo screen. I have been running a custom mi9 jellybean rom since early last year. I decided to upgrade to jellybean finally. I wiped and flashed carl1961's deodexed rom and super su both of which were successful. I tried flashing the oc1patch firmware that was next in his instructions but it failed. I decided to continue on with the next instruction and flash the oc2 firmware file, it was successful. Then I rebooted from SS reboot menu. The "galaxy note 3" screen comes on and hangs for a while goes away and comes back on for a while. Then the att logo screens starts and freezes. That's as far as it gets. I'd like to either restore my backup from SS or upgrade to LP w/root. Do I use Walter whites Odin files to get LP? Or Odin to KK, root, then upgrade to LP? TIA!!!

jbryson16 said:
My phone won't boot past the att logo screen. I have been running a custom mi9 jellybean rom since early last year. I decided to upgrade to jellybean finally. I wiped and flashed carl1961's deodexed rom and super su both of which were successful. I tried flashing the oc1patch firmware that was next in his instructions but it failed. I decided to continue on with the next instruction and flash the oc2 firmware file, it was successful. Then I rebooted from SS reboot menu. The "galaxy note 3" screen comes on and hangs for a while goes away and comes back on for a while. Then the att logo screens starts and freezes. That's as far as it gets. I'd like to either restore my backup from SS or upgrade to LP w/root. Do I use Walter whites Odin files to get LP? Or Odin to KK, root, then upgrade to LP? TIA!!!
Click to expand...
Click to collapse
The best way to upgrade to OC1/OC2 (atleast with the least probabilities of a bootloop occurring) is to first flash NC2 wipe tars via odin and then flashing carl1961's OC2 deodexed rom (with SuerSU).
1. Download the NC2 odin flashable files from https://mega.nz/#F!wg5wRQrQ!vR7a6pze9dgSWjbaRSyhWA (Caution: These are wipe tars and will format the phone's internal storage, so backup everything from the phone memory). Flash them via odin, and your phone will boot into NC2 KitKat.
2. Once the phone boots up and you've completed the crappy startup questions, install towelroot (https://towelroot.com/) and root your phone. Install supersu and busybox from playstore and install them. Download and install safestrap (Safestrap-HLTEATT-NC2-3.75-B03.apk)
3. Download carl1961's rom and a few other things:
The rom (https://mega.nz/#!qc8QHI6T!_8x88BL-ivTM0yj5uhbmNITernym8HMr2VKJJZB9JeE)
OC1 Patch Firmware (https://mega.nz/#!fQ8nSbbA!qzw9IzKf6BzwY0IOHGjGFOmV1QgWoYv-AV4NsjyuiT8)
OC2 Patch Firmware (https://mega.nz/#!iF8xBS6Z!XQNgLscWM5SOOddlkunQYBCQp2QO03raEMN91sF1g34)
Xposed Framework (optional) (http://forum.xda-developers.com/attachment.php?attachmentid=3454433&d=1440761913)
SuperSU (http://forum.xda-developers.com/attachment.php?attachmentid=3478515&d=1442612185)
Optional OC2 fixes/addons from http://forum.xda-developers.com/note-3-att/development/8-24-15-t3185574
4. Boot into safestrap and follow the following steps:-
Factory wipe
Flash ROM
Flash SuperSU
Flash Xposed (optional)
Flash OC1 patch firmware
Flash OC2 patch firmware
Flash OC2 Addons/Fixes
Wipe Dalvik Cache
Reboot

sam.stalker1608 said:
The best way to upgrade to OC1/OC2 (atleast with the least probabilities of a bootloop occurring) is to first flash NC2 wipe tars via odin and then flashing carl1961's OC2 deodexed rom (with SuerSU).
1. Download the NC2 odin flashable files from https://mega.nz/#F!wg5wRQrQ!vR7a6pze9dgSWjbaRSyhWA (Caution: These are wipe tars and will format the phone's internal storage, so backup everything from the phone memory). Flash them via odin, and your phone will boot into NC2 KitKat.
2. Once the phone boots up and you've completed the crappy startup questions, install towelroot (https://towelroot.com/) and root your phone. Install supersu and busybox from playstore and install them. Download and install safestrap (Safestrap-HLTEATT-NC2-3.75-B03.apk)
3. Download carl1961's rom and a few other things:
The rom (https://mega.nz/#!qc8QHI6T!_8x88BL-ivTM0yj5uhbmNITernym8HMr2VKJJZB9JeE)
OC1 Patch Firmware (https://mega.nz/#!fQ8nSbbA!qzw9IzKf6BzwY0IOHGjGFOmV1QgWoYv-AV4NsjyuiT8)
OC2 Patch Firmware (https://mega.nz/#!iF8xBS6Z!XQNgLscWM5SOOddlkunQYBCQp2QO03raEMN91sF1g34)
Xposed Framework (optional) (http://forum.xda-developers.com/attachment.php?attachmentid=3454433&d=1440761913)
SuperSU (http://forum.xda-developers.com/attachment.php?attachmentid=3478515&d=1442612185)
Optional OC2 fixes/addons from http://forum.xda-developers.com/note-3-att/development/8-24-15-t3185574
4. Boot into safestrap and follow the following steps:-
Factory wipe
Flash ROM
Flash SuperSU
Flash Xposed (optional)
Flash OC1 patch firmware
Flash OC2 patch firmware
Flash OC2 Addons/Fixes
Wipe Dalvik Cache
Reboot
Click to expand...
Click to collapse
Thanks! Can I backup my sd even though my phone won't boot?

jbryson16 said:
Thanks! Can I backup my sd even though my phone won't boot?
Click to expand...
Click to collapse
For backing up your internal memory, you need to dirty flash with a stock firmware (ie. a non-wipe odin flashable NC2 tar). Download it from here: bit.ly/1q98wGU, and flash this in the AP section of Odin, keep all others (BL, CP and CSC) empty. This way, the flashing won't erase the phone's internal memory. Although I think it factory resets and erases your apps (and their data), but doesn't erase user downloaded/added data.

[REQ-DEV HELP] Experienced user and flasher stuck on DOK2 mounting partitions problem

Hello XDA members and devs. I have stumbled upon an issue that seems to be close to un-fixable. I have the SM-N910T obviously. I am on DOK2, every rom Touch Wiz and Cyanogenmod flashed correctly a couple of months ago. Now the only things I can flash are DOK2 stock firmware via ODIN, and then I can successfully flash TWRP 2.8.7.0, the only ROM I can flash is Maximum Overdrive 4.0.1 +(all upper updates.) I got a hold of Max OD dev and he said it's because of the 3 mount lines he added to the top of his updater-script. So I added those lines to updater-scripts of other roms and none worked. Some other roms have many other mount points and important lines of code in the updater-script that should not be removed or edited. I want to go back to Cyanogenmod, and others either 12.1 nightlies, or the new CM Remix 13.0 which worked before all the others stopped working at the same time.
Yes I also tried this.
Quote:
Originally Posted by sudoBacon
I tried before. Doesnt work onlky DOK2 or maximum ods 4.0.1 + no other roms
After you flash D0K2 firmware - Use the stock Recovery and Factory Reset - That will get you out of the bootloop - Just remember that your internal storage will be wiped!
I also get the same issue after attempting to downgrade which always fails. Used to be able to downgrade and upgrade firmware's as well, now I cant. I got the dev of Max OD rom to pull a DOK2 pit file even flashing that does not fix my issue. I also posted on Reddit, so I will copy and paste this post.
Reddit Post.
I have a T-Mobile Note 4 was working fine for a long time flashed many ROM's multiple times over and over again never had a problem until I flashed DOK2 I assume. With ODIN. I did flash to stock from COD6 to DOK2 can't seem to downgrade back to COD6 with ODIN get error cant downgrade note 4 SW REV CHECK FAIL : [aboot]Fused2 > Binary 1 [1] eMMC write fail : ABOOT , that appears on Download mode. Then every time I install TWRP I try to install a ROM from OTG usb or ext sd and nothing flashes, rom files work used them before. I can only seem to install DOK2 and can't downgrade or flash other roms. I need help so I can flash other roms. Yes I tried flash stock DOK2 and boot stock recovery then clearing cache and factory reset, to downgrade to COD6 still failing and can't install other roms. every time i try to flash version lower then DOK2 using odin get this error ; SW REV CHECK FAIL : [aboot]Fused2 > Binary 1 [1] eMMC write fail : ABOOT
At one point I installed CWM trlltexx or something like that through TWRP, and did format and all of that. But after that went back to stock flashed TWRP 2.8.7.0 because couldn't flash roms with CWM because the roms thought I was on trltexx. Formatted all partitions with CWM. Anyways tried to get back to Cyanogenmod and or Tekxodus and other roms all fail. Minus Maximum Overdrives 4.0.1.
The first 3 lines that Overdrive mentioned that must make my roms flash able are.
HTML:
run_program("/sbin/busybox", "mount", "/system");
run_program("/sbin/busybox", "mount", "/cache");
run_program("/sbin/busybox", "mount", "/data");
Anyways please contact me on Google+ Hangouts or respond here if you know how to fix my issue also have Skype but PM me for that info. Add Bacon Seeds first and last name to Google + Hangouts that G+ Hangouts email is [email protected] . I am experienced in compiling roms extracting, de compiling as well. Life on my Note 4 without some Cyanogenmod had been technologically heartbreaking. I like flashing multiple roms and swapping back and forth. Now I cant even test others stuck on Max OD which is a good and awesome rom but sometimes get tired of Touch Wiz.

I would install the ROM you can, then dirty flash an aosp ROM, then try to flash the ROM you want.

therealjwkware said:
I would install the ROM you can, then dirty flash an aosp ROM, then try to flash the ROM you want.
Click to expand...
Click to collapse
I'll give this a shot but I seriously doubt this will work if other methods didn't.

sudoBacon said:
I'll give this a shot but I seriously doubt this will work if other methods didn't.
Click to expand...
Click to collapse
Use Kies to recover your phone. It should be able to fit any issues with partitions etc.

Odd how using the PIT file does not fix this issue. It's literally setting up your phone's partition table all over again and it isn't working. Also, on DOK2's bootloader, it is impossible to rollback bootloader. I tried going from DOK2 -> ANIH (Kitkat original) and it didn't work. You can still run older ROMs, just not the older bootloader. That's why you're getting the 'Binary 2 > Fused 1' message.
-
By the way, you should be using ODIN3.10.7. It is the latest version. Load up the full stock DOK2 firmware (I suggest downloading using SamFirm -- make sure to check Binary Nature for a full firmware), follow this guide:
http://forum.xda-developers.com/showthread.php?t=2610757
They used a PIT and Stock to fully wipe, with the exception in this case being that this is 5.1.1 and not 4.4.4

ShrekOpher said:
Use Kies to recover your phone. It should be able to fit any issues with partitions etc.
Click to expand...
Click to collapse
I tried that and now after doing factory reset in the stock firmware I can not even flash Maximum OD only DOK2 via odin.

sudoBacon said:
I tried that and now after doing factory reset in the stock firmware I can not even flash Maximum OD only DOK2 via odin.
Click to expand...
Click to collapse
do you have a working DOK2 stock firmware running on your phone. Once you upgrade to DOK2 you can only flash ROMs based on 5.1.1 or ROMs that include a kernel. If you want to flash a ROM based on 5.0.1 you will need to flash either the Emotion Kernel or the Beast mode kernel as well before you reboot the device.
If you have Stock TW firmware running and you have TWRP installed your phone should be fixed. As long as you use compatible ROMs with it.

ShrekOpher said:
do you have a working DOK2 stock firmware running on your phone. Once you upgrade to DOK2 you can only flash ROMs based on 5.1.1 or ROMs that include a kernel. If you want to flash a ROM based on 5.0.1 you will need to flash either the Emotion Kernel or the Beast mode kernel as well before you reboot the device.
If you have Stock TW firmware running and you have TWRP installed your phone should be fixed. As long as you use compatible ROMs with it.
Click to expand...
Click to collapse
Still didn't work.
Edit : Now i cant seem to install any rom nor Max OD. only DOK2 via odin. TWRP log says
E:Mount: Unable to find partition for path /sdcard
E:UnMount: Unable to find partition for path /sdcard
E:Mount: Unable to find partition for path /sdcard

sudoBacon said:
Still didn't work.
Edit : Now i cant seem to install any rom nor Max OD. only DOK2 via odin. TWRP log says
E:Mount: Unable to find partition for path /sdcard
E:UnMount: Unable to find partition for path /sdcard
E:Mount: Unable to find partition for path /sdcard
Click to expand...
Click to collapse
Looks like you corrupted your partitions. You might need to flash the pit file to fix it. I think there is a thread related to that somewhere.

Request thread closed, resolved!
Steps taken not in any order.
Find a legit us TRLTE pit file. Message me for the TRLTE pit file or I'll make a separate thread for it.
Flash DOK2 stock firmware + proper pit file and have re-partition checked, along with flash BL and EFS clear.
Format ext SD card.
Downloaded the roms onto the formatted SD card.
Flash the latest TWRP recovery
Wipe all not including system x3 times.
Go to Wipe and then Format, check system format system type Yes
Go to install select your ROM.
Then select your GApps and custom kernel whatever else you want.
You might have to do the stock flashing and wiping and formatting several times before this works along with the re-partitioning.
Note a legit TRLTETMO pit file can be found : http://www.sammobile.com/forum/showthread.php?t=29568
The legit pit file name for TRLTETMO should be labeled: TRLTE_USA_TMO.pit

sudoBacon said:
Request thread closed, resolved!
Steps taken not in any order.
Find a legit us TRLTE pit file. Message me for the TRLTE pit file or I'll make a separate thread for it.
Flash DOK2 stock firmware + proper pit file and have re-partition checked, along with flash BL and EFS clear.
Format ext SD card.
Downloaded the roms onto the formatted SD card.
Flash the latest TWRP recovery
Wipe all not including system x3 times.
Go to Wipe and then Format, check system format system type Yes
Go to install select your ROM.
Then select your GApps and custom kernel whatever else you want.
You might have to do the stock flashing and wiping and formatting several times before this works along with the re-partitioning.
Note a legit TRLTETMO pit file can be found : http://www.sammobile.com/forum/showthread.php?t=29568
The legit pit file name for TRLTETMO should be labeled: TRLTE_USA_TMO.pit
Click to expand...
Click to collapse
Congrats!

Hey bacon. I'm glad you figured it out. But in was wondering if you think me doing the pit file would work for my situation. Currently my phone is on a loop every time I flash dok2. And twrp will not flash any huge files. I can get kernels too flash but not roms. Any insight would be greatly appreciated. I can't even get the firmware too boot up. Thanks in advance

Jamonguyen said:
Hey bacon. I'm glad you figured it out. But in was wondering if you think me doing the pit file would work for my situation. Currently my phone is on a loop every time I flash dok2. And twrp will not flash any huge files. I can get kernels too flash but not roms. Any insight would be greatly appreciated. I can't even get the firmware too boot up. Thanks in advance
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24369303960684492
Here's a pit for the N910T, grabbed from the latest DOK2.

eduardog131 said:
https://www.androidfilehost.com/?fid=24369303960684492
Here's a pit for the N910T, grabbed from the latest DOK2.
Click to expand...
Click to collapse
I'm trying to get stock to boot without success. I would really appreciate any help.

Longshark said:
I'm trying to get stock to boot without success. I would really appreciate any help.
Click to expand...
Click to collapse
Have you flashed the full ODIN package? Try erasing NAND and Re-Partition (with .pit in ODIN package)
I will usually just go about it that way when I go to stock to start off fresh.

eduardog131 said:
Have you flashed the full ODIN package? Try erasing NAND and Re-Partition (with .pit in ODIN package)
I will usually just go about it that way when I go to stock to start off fresh.
Click to expand...
Click to collapse
So I'm flashing the full ODIN package. PDA for stock, PIT from the link you posted, Checked boxes are Auto Reboot. Re-Partition, F. Reset Time and NAND Erase All. This is with ODIN 3.07.
What do I do when it finishes?
---------- Post added at 10:45 PM ---------- Previous post was at 10:43 PM ----------
eduardog131 said:
Have you flashed the full ODIN package? Try erasing NAND and Re-Partition (with .pit in ODIN package)
I will usually just go about it that way when I go to stock to start off fresh.
Click to expand...
Click to collapse
It's done but boot looping with RECOVERY BOOTING... screen. Do I flash TWRP now? I have 2.8.7. Is that sufficient?
Thanks

Longshark said:
So I'm flashing the full ODIN package. PDA for stock, PIT from the link you posted, Checked boxes are Auto Reboot. Re-Partition, F. Reset Time and NAND Erase All. This is with ODIN 3.07.
What do I do when it finishes?
---------- Post added at 10:45 PM ---------- Previous post was at 10:43 PM ----------
It's done but boot looping with RECOVERY BOOTING... screen. Do I flash TWRP now? I have 2.8.7. Is that sufficient?
Thanks
Click to expand...
Click to collapse
It shouldn't be bootlooping, in fact it has to reboot into recovery right after ODIN flashes the stock package, it needs to erase + verify / flash CSC contents. It should pretty much boot up into stock. If you really want to flash TWRP (to flash a custom ROM), flash it. Right after you flash it, make sure you take the battery out and you reboot into recovery manually. Stock system prevents recovery from being overwritten.

eduardog131 said:
It shouldn't be bootlooping, in fact it has to reboot into recovery right after ODIN flashes the stock package, it needs to erase + verify / flash CSC contents. It should pretty much boot up into stock. If you really want to flash TWRP (to flash a custom ROM), flash it. Right after you flash it, make sure you take the battery out and you reboot into recovery manually. Stock system prevents recovery from being overwritten.
Click to expand...
Click to collapse
Sorry I'm fairly new to this. So it did boot into custom recovery. I just want the phone back to stock without TWRP or any bells or whistles.
Its on the stock recovery interface. Should I wipe data/factory reset? Or reboot system now?

Longshark said:
Sorry I'm fairly new to this. So it did boot into custom recovery. I just want the phone back to stock without TWRP or any bells or whistles.
Its on the stock recovery interface. Should I wipe data/factory reset? Or reboot system now?
Click to expand...
Click to collapse
Once it's done with verification of CSC, just reboot system. It should take a few minutes to set itself up, then will throw you into the setup wizard. Once you're there you're good to go.

eduardog131 said:
It shouldn't be bootlooping, in fact it has to reboot into recovery right after ODIN flashes the stock package, it needs to erase + verify / flash CSC contents. It should pretty much boot up into stock. If you really want to flash TWRP (to flash a custom ROM), flash it. Right after you flash it, make sure you take the battery out and you reboot into recovery manually. Stock system prevents recovery from being overwritten.
Click to expand...
Click to collapse
Also does it matter the dm-verity verification failed is showing at the bottom?

android oreo with odin and root

I'm rooted and if i flash BL,CP,CSC through odin then will my twrp recovery stay without any problem? and I'll be in the oreo? currently I'm on a custom rom..

Yes you won't loose TWRP. You'll only loose it if you flash AP which contains stock recovery. Might be better of flashing CSC with TWRP using on of the CSC zips. Same goes for BL & CP, if you have an F, there are a few devs that have flashable zips for TWRP. I never use Odin to flash anything anymore, really no need if you have TWRP.

with twrp though, you can actually flash the wrong bootloader where as in odin it simply wont flash.
gotta be careful with those flashable zips...
as for csc, chances are that wont work as it needs to install it self via stock recovery update script after you flash. flashing bl and cp for your phone model should be insufficient. but that doesn't put you on oreo per say.

bober10113 said:
with twrp though, you can actually flash the wrong bootloader where as in odin it simply wont flash.
gotta be careful with those flashable zips...
as for csc, chances are that wont work as it needs to install it self via stock recovery update script after you flash. flashing bl and cp for your phone model should be insufficient. but that doesn't put you on oreo per say.
Click to expand...
Click to collapse
this is the answer i was looking for..thanks...i didn't want to go fully stock... that's the point of my question... thanks bro..i got what i needed