I have downloaded a file for flashing stock firmware from telus with july updates, it contains several files. I have rooted and installed xposed on my stock firmware and I want to get rid of the installed system root and xposed flashes. The only way I can figure is to flash a stock rom back. What do I flash to do this? AP/CSC? seeing as this rom is an update as well I imagine I will have to flash bootloader too. Any advice or general walkthroughs or links would be greatly appreciated.
anyone?
in case anyone finds this I was able to flash and YES it flashes the boot.img and recovery.img but not csc or home. Which I dont really mind at all. When flashing over previous stock rom it upgraded the rom and all my stuff and cleaned out the system too! encryption is back and i can lock the phone, rooted it and was able to still have lock and encryption
Related
Hello,
This is will be my first XDA post ever since I always fix the most "brickiest" problems with all the Android based devices I have ever owned but not this time.
My Galaxy S4 has been updated to the latest MJA OTA (with successful CF root) and I have attempted to re-mod the hotspot service but this caused the annoying knox message to show. When attempting to restore the JAR and ODEX files, I think I have either overwritten the files in the incorrect order (ODEX -> JAR) and the phone rebooted as FX was trying to do that. So services.odex got corrupted and it was time for my to ODIN flash the MDC full stock rom as that USED to be my solution until Samsung's brand new knox protected bootloader. ODIN is not an option for me now, since the bootloader will prevent me flashing things like the pit, aboot and probably most of the other files inside the tarball. I can flash custom recovery and the MDC kernel successfully and that's about it. With custom recovery I have flashed rooted MF8 for the base operating system, and they applied the rooted MJA rom on top. The phone shows the S4 branding but then it reboots; It cannot boot into the operating system. I do not know the condition of the flash counter atm since I cannot check that in TriangleAway but it will stay "Official" under download mode, I think. I also do not know the versions of the firmware installed either in case something from MDC tar had an succession in replace some of the partitions. I am pretty sure the kernel however is still at MDC while I managed to install the system image of the MJA stock rom.
So my question is, what can I do bring back the working MJA stock rom image (/system and kernel) using TWRP recovery? Else I will have to go to Sprint and saying that the update from OTA has bricked my phone and that I have no idea how phones work.
Thank you.
45553543 450
Sorry, I forgot to add that I know that once you have MJA flashed, you cannot downgrade back unless of course someone figured out how to disable all the bootloader security but I really do not see that happening.
Fixed my own problem. Downloaded the official MJA stock tar.md5 rom from sammobile and flashed it, and managed to restore all my data using Titanium backup. This thread can be now closed.
Hello, so even though I'm fairly new to the world of custom ROM's I feel as though this website has provided me with more than sufficient information for me to keep on flashing. I've flashed a few ROM's in the past but I'm currently stuck as for what I should do next. I currently have an S4 ATT MF3 which I would like to upgrade to MK2 so that I can put a 4.4.2. ROM via Safestrap using the Deadly Venom method.
Based on the guide (http://forum.xda-developers.com/showthread.php?t=2573080) I need to boot into the stock recovery and flash stock MF3 then MK2 which I can then root and safestrap. When I added my first ROM on this device I replaced the stock ROM (I have a hatred for TouchWiz) and replaced with a GPE ROM.
My phone can no longer boot into the stock Samsung recovery, it merely just bootloops instead, but I can still flash via Safestrap. So what should I do? Can I get the stock recovery back? Would I have any issues if I flash the MK2 update via Safestrap instead of the stock recovery? Will flashing the MF3 stock tar via Odin be all that I need to do? Any advice would be appreciated!
DarthVayda said:
Hello, so even though I'm fairly new to the world of custom ROM's I feel as though this website has provided me with more than sufficient information for me to keep on flashing. I've flashed a few ROM's in the past but I'm currently stuck as for what I should do next. I currently have an S4 ATT MF3 which I would like to upgrade to MK2 so that I can put a 4.4.2. ROM via Safestrap using the Deadly Venom method.
Based on the guide (http://forum.xda-developers.com/showthread.php?t=2573080) I need to boot into the stock recovery and flash stock MF3 then MK2 which I can then root and safestrap. When I added my first ROM on this device I replaced the stock ROM (I have a hatred for TouchWiz) and replaced with a GPE ROM.
My phone can no longer boot into the stock Samsung recovery, it merely just bootloops instead, but I can still flash via Safestrap. So what should I do? Can I get the stock recovery back? Would I have any issues if I flash the MK2 update via Safestrap instead of the stock recovery? Will flashing the MF3 stock tar via Odin be all that I need to do? Any advice would be appreciated!
Click to expand...
Click to collapse
If you don't mind losing your user data (back up anything you want from internal storage) just flash the MK2 full ODIN. Otherwise, there is a thread somewhere with just the MF3 recovery image and if you have root you could use an app to manually flash that (don't remember the app).
DeadlySin9 said:
If you don't mind losing your user data (back up anything you want from internal storage) just flash the MK2 full ODIN. Otherwise, there is a thread somewhere with just the MF3 recovery image and if you have root you could use an app to manually flash that (don't remember the app).
Click to expand...
Click to collapse
The app is flashify
Sent from my Nexus 5 using XDA Free mobile app
Possible to restore stock recovery?
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
pravus87 said:
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
Click to expand...
Click to collapse
I would flash in Odin the stock mf3 tar file, but out will wipe the device. All his apps and data. If you can find the mf3 recovery image file you could try to flash that in flashify, if you're rooted
Edit, found this. I didn't download the file but I'm guessing it's a .img file. You could flash that in flashify or use the dd command
Sent from my Nexus 5 using XDA Free mobile app
pravus87 said:
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
Click to expand...
Click to collapse
In addition to the above post from jd, the CM installer will not work on our device as our bootloader is locked. There is no way to run any AOSP based ROM once your phone is on MF3 firmware or higher.
DarthVayda said:
Hello, so even though I'm fairly new to the world of custom ROM's I feel as though this website has provided me with more than sufficient information for me to keep on flashing. I've flashed a few ROM's in the past but I'm currently stuck as for what I should do next. I currently have an S4 ATT MF3 which I would like to upgrade to MK2 so that I can put a 4.4.2. ROM via Safestrap using the Deadly Venom method.
Based on the guide (http://forum.xda-developers.com/showthread.php?t=2573080) I need to boot into the stock recovery and flash stock MF3 then MK2 which I can then root and safestrap. When I added my first ROM on this device I replaced the stock ROM (I have a hatred for TouchWiz) and replaced with a GPE ROM.
My phone can no longer boot into the stock Samsung recovery, it merely just bootloops instead, but I can still flash via Safestrap. So what should I do? Can I get the stock recovery back? Would I have any issues if I flash the MK2 update via Safestrap instead of the stock recovery? Will flashing the MF3 stock tar via Odin be all that I need to do? Any advice would be appreciated!
Click to expand...
Click to collapse
pravus87 said:
So after (stupidly) assuming that I knew what I was doing since I have been rooting/flashing/breaking/fixing my S3 for two years now that I would be able to easily install CM11 on my dad's S4 since he is always complaining about AT&T bloatware. He is running the absolute latest update from AT&T and never rooted or anything. I was able to successfully root it using the extSdCard method, but then made the mistake of trying to flash TWRP.
After a couple of failures, I went onto these forums to see that it is well documented that custom recoveries do not work with the latest firmware. Noted, and I will keep an eye out for updates to this issue.
My questions:
Since the goal was only to install Cyanogenmod 11, I would have just run the CM Windows Installer if I wasn't trying to create a full stock backup first (hence why I tried rooting and installing TWRP first). Since that is no longer an option, has anyone attempted to use the CM Windows Installer on the MF3 build? I assume that if a custom recovery cannot be installed that this method will not work, but was just wondering if anyone has had success.
The more important questions...
Since the stock recovery is now gone, will this create an issue if a new OTA update is released and he attempts to install? I am wondering if the OTA updates rely on the existing recovery to complete the update or if the OTA will rebuild it before installing the update?
Lastly, are there reliable methods for restoring the stock recovery?
Thanks everyone!
Click to expand...
Click to collapse
Here is the MF3 stock recovery, flash in PDA slot in Odin(AP in Odin v3.09+): https://mega.co.nz/#!klcz1B4J!BVAno0CcaJ7aXc9tHgUtpQ0vy_NF5ceh7RogLR6JBTU
muniz_ri said:
Here is the MF3 stock recovery, flash in PDA slot in Odin(AP in Odin v3.09+): https://mega.co.nz/#!klcz1B4J!BVAno0CcaJ7aXc9tHgUtpQ0vy_NF5ceh7RogLR6JBTU
Click to expand...
Click to collapse
Thanks to everyone for all the information, and thank you especially for sharing the link. I am staying with my parents short-term in a very rural area with awful internet and I was dreading downloading the 2+GB stock firmware file just to get recovery back. This is perfect. Thanks again!
Hey guys i followed this youtube guide for rooting 5.1.1 using TWRP Method https://www.youtube.com/watch?v=qpsGX_Xoxcg
i downloaded all the files but the firmware (not listen i have n910W8 = telus)
I have odin, supersu, TWRP (which n910w8 is listed) and samsung drivers.
I moved superSU and the TWRP file to root directory of note 4 5.1.1. rebooted into download mode, saw the blue indicator on odin and loaded the file. Rebooted holding volume up this time and tried to load the kernal but it doesnt exist.
I think im confused the TWRP file is NOT the kernal? Where can I get a kernal for n910W8 (telus)
thanks in advance!!
So I found this
http://www.sammobile.com/firmwares/download/56498/N910W8VLU1COI4_N910W8OYA1COI4_TLS/
which is telus 5.1.1 Rom. ill move this to my root directory and load the 910W8 TWRP file in odin and flash? Ill give it a try now wish me luck lol
ok i followed a guide online and now my phone just keeps restarting. I think im in big trouble. Im able to load openrecovery-twrp-2.8.1.0-trltecan.img into odin and boot to TWRP but now i cant load kernels? looked so easy to do now im down a phone? any help is much appreciated thanks!!!
You need to odin (bell, rogers, telus) 5.1.1 then odin TWRP then twrp a custom kernel. Our 5.1.1 needs a custom kernel in order to work rooted. Or.....you can load a custom 5.1.1 rooted rom that is W8 compatible or any Tmobile rom such as Tekxodus which i am running.
ok so i loaded openrecovery-twrp-2.8.1.0-trltecan.img in AP (for my device) copied the custom rom
" cm-12.1-20150423-NIGHTLY-trltetmo" which was suppose to work with my 910w8 (910T) used recovery to flash it and also supersu it flashed OK... I restart and i see a little blue guy and its stuck optimizing apps. Suck in restart loop.
what did i do wrong? try a different kernel ?
thanks in advance
EDIT 1
im trying the " Tekxodus" rom. this file is way larger whats going on with that. Is it the same procedure to flash it?
EDIT 2
Flashed to tekxodus rom optimizing apps... now its stuck System UI has stopped. and I cant do nothing. Any suggestions? ?? ?
EDIT 3
Do I need to flash a certain BootLoader along with the recovery for my device (BL and AP) ? , reboot in recovery and flash the custom rom ie "Tekxodus" ?
found this guide for 910C
http://www.ibtimes.co.uk/how-root-galaxy-note-4-n910c-android-5-1-1-lollipop-1518168 with these steps
"Step-1: Download the flashable root package and transfer it to the storage of the phone
Step-2: Download Android 5.0.1 bootloader package. Extract it using any extracting tool and you should find a folder containing Odin flashable tar package and Odin binaries"
so confused lol
All you have to do is Odin stock 5.1.1 rom (COI4 i believe) then Odin TWRP then flash Tekxodus V3.2. Let everything optimize and let it sit there for a good 10 mins after optimization. Ignore what its doing. It will just work. No need to flash anything else unless you want Xposed, then you flash that right after flashing Tek (do not boot in between)
any idea where to get a custom kernel for 910w8 5.1.1 to root stock rom?
Im running this rom (flashed using odin)
http://www.sammobile.com/firmwares/download/56498/N910W8VLU1COI4_N910W8OYA1COI4_TLS/
stock telus rom. I loaded this rom by clicking BL in odin and selecting it (along with my recovery for telus 910w8). This was the only was to get my phone back into working order.
______-
I loaded my recovery for telus into odin and went to download mode.
booted into TWRP
Flashed Tekxodus V3.2.
Optimized apps for about 10 minutes and it just restarted and optimized again and again.
One time it said System UI has stopped and I was hooped.
not sure where I went wrong?
thanks for the response btw I really want to get this going cheers
equlizer said:
You need to odin (bell, rogers, telus) 5.1.1 then odin TWRP then twrp a custom kernel. Our 5.1.1 needs a custom kernel in order to work rooted. Or.....you can load a custom 5.1.1 rooted rom that is W8 compatible or any Tmobile rom such as Tekxodus which i am running.
Click to expand...
Click to collapse
can i use any carrier software for the COI4? That's my only question. Thanks for helping!!
Hi, I have an N910T running update LineageOS (TWRP), and I a couple of apps recently won't run on a rooted phone. So I have tried to restore the stock ROM. I downloaded from Sammobile (tried 4.4 and 5.1) but neither will load using ODIN (log shows failure before any .img files loaded).
Can anyone suggest how to go back in time on this phone?
Thanks for any help!
miltf said:
Hi, I have an N910T running update LineageOS (TWRP), and I a couple of apps recently won't run on a rooted phone. So I have tried to restore the stock ROM. I downloaded from Sammobile (tried 4.4 and 5.1) but neither will load using ODIN (log shows failure before any .img files loaded).
Can anyone suggest how to go back in time on this phone?
Thanks for any help!
Click to expand...
Click to collapse
An updated bootloader, as I assume you already have, will NOT let you flash an older version of the stock rom.
When you have that (updated bootloader) , for security reasons you are no longer able to roll so much back as 4.4 or 5.1 roms.
Only 6(MM) and up roms are allowed anymore.
So , look here for the latest stock rom for your phone/model and flash it using odin
https://updato.com/firmware-archive-select-model/?q=SM-N910t&rpp=15&order=date&dir=desc&exact=1
OK Got my prior issue sorted out and got the tablet back up and running with the original Firmware.
I have the bootloader unlocked, but not able to gain root. Want to remove a lot of bloat and need root based Ad Blocker.
Tried the root method that was posted but it wont boot with patched boot.img flashed in Odin, I suspect it is due to it being Android 13 and the release that came out earlier this month.
Can't seam to get the original firmware to flash completely either with Odin either.
Any know ways that work with current Software?
Thanks for input