Guys,
So I'm on CM12.1 - all great and what not, but I've had enough, and want to try a fresh Stock install. I've downloaded the latest 5.0 build from Sammobile
My questions are
1. What happens to root?
2. What happens to KNOX 0x1?
3. Will ODIN wipe clean the storage? [I expect it to wipe all installed apps, but will it wipe local data? i.e do i need to move 10gb+ of stuff and then move it back?]
4. Will I be able to get OTA updates?
5. Will my recovery still be there? TWRP currently.
6. Will there be a modem/baseband problem with going from 5.1.1. to 5.0 ?
Cheers
Usually when you flash to stock, you want to preform a factory reset to clean and clear the system.
Root should be removed.
KNOX counter is invisible but should still be tripped.
You will be able to get OTA I believe ( not sure, haven't had one in a while).
Recovery will be lost.
I did not have any problems with my modem/baseband ( I think it resets to stock)
+1
Right, cool.
I get that you should probably clear the lot out to start fresh. But I'd still like to know if Odin will do it for you or not. So the internal storage, if I left a folder in there called XDA with a file called XDA.txt and I ran the ODIN process to get back to stock - will I boot into a fresh stock TW install and then find my XDA.txt file still there or not?
Cheers for your time guys!
I think it should be there, but the phone will boot in a crazy way such as no ui. In order to even use the phone after a factory flash you need to make sure factory reset it.
Maybe if you connect it to the pc you will be able to get in and save your data, but I highly doubt it. Be cautious as sometimes the phone can get stuck in a boot loop until you factory reset.
Vyker said:
Right, cool.
I get that you should probably clear the lot out to start fresh. But I'd still like to know if Odin will do it for you or not. So the internal storage, if I left a folder in there called XDA with a file called XDA.txt and I ran the ODIN process to get back to stock - will I boot into a fresh stock TW install and then find my XDA.txt file still there or not?
Cheers for your time guys!
Click to expand...
Click to collapse
your XDA.txt file should be still there.
Many users are finding it difficult to root Lollipop.......Even with CF Root......
My advice would be to flash a KitKat firmware, root it and then Flashfire to Lollipop (and use Flashfire to inject root to the LP firmware)......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Related
Hi, i am in the uk and had my i9505 for around 2 weeks, just wondering the best way to now root and is there anyway which is the safest / recommended?
also, can rom's still be updated afterwards via ota or kies if i root, i know i would have to root again but would my phone still be supported by kies and look for new fw's after rooting?
thanks
james
Personally, I use the pre-rooted stock roms in the Android Development section:
http://forum.xda-developers.com/showthread.php?t=2250824
Very easy to use, just download and flash via Odin3. There may be easier ways, but for me this is the easiest.
All you need to do then is flash custom recovery and you're done.
Edit: Not sure about Kies, but it's easy enough to flash back to a stock rom and then reset your phone to Official again.
Some custom roms offer OTA updates, but personally, I prefer just staying on a stock rooted and update via Odin as and when needed
Thanks for the reply, if I flash the pre rooted Rom will it wipe my phone or will settings and apps still be the same afterwards?
james_lpool said:
Thanks for the reply, if I flash the pre rooted Rom will it wipe my phone or will settings and apps still be the same afterwards?
Click to expand...
Click to collapse
If you install pre rooted rom, all your apps, settings etc will remain. Odin3 doesn't touch the data partition, so you'll still have everything.
I usually clear cache/data after installing a new rom, so I start from fresh, but it's really upto you really
One thing to be aware of though is that flashing a pre-rooted rom will clear your custom recovery, so you'll have to reflash recovery after installing an updated pre-rooted rom
I've been reading the 4.3 release thread in the "general" forum, and the other relevant threads over there, and am confused after reading thru' 50+ pages of experiences...
I'm on the stock MF9 ROM, rooted, with hotspot mod installed, and camera shutter sound disabled in xml file), and TWRP custom recovery.
I'd like to get to MJA, rooted, with hotspot mod installed, and TWRP custom recovery. (if possible, I'd like to get there without tripping the KNOX counter, but if that is not possible, so be it)
From what I've read, it looks like I need to
Nandroid backup (optional)
Install stock MF9 tar file using ODIN (recovery, ROM, Modem, kernel) - http://forum.xda-developers.com/showthread.php?t=2485502
Take OTA (or use update file from google server link on http://forum.xda-developers.com/showthread.php?t=2504349)
Reboot (Don't install any apps at this time)
Use CF Auto to root using ODIN - http://forum.xda-developers.com/showpost.php?p=41743640&postcount=3
Factory reset just in case
Install goo manager, and flash custom recovery TWRP
Reboot
Reinstall apps
Install new MJA odexed hotspot mod http://forum.xda-developers.com/showthread.php?t=2256950
Nandroid backup
Is this about right? (and are the links to the right files/posts?)
Is there an easier/safer way of doing this?
Is there any way to not trip the knox counter? Or does the flash of CF Auto to root always trip it?
Any other troubleshooting steps in case things go wrong?
Example:
If phone gets stuck in bootloop at any step - what steps should be attempted before pulling battery, and trying to reflash in ODIN?
If phone shows android lying down with red exclamation mark, what should be attempted?
If root doesn't stick after reboot, what should be attempted?
If custom recovery doesn't stick, what should be attempted?
Hopefully, this will help others like me as well.
Thanks!
looks good, sounds right...
jj14 said:
I've been reading the 4.3 release thread in the "general" forum, and the other relevant threads over there, and am confused after reading thru' 50+ pages of experiences...
I'm on the stock MF9 ROM, rooted, with hotspot mod installed, and camera shutter sound disabled in xml file), and TWRP custom recovery.
I'd like to get to MJA, rooted, with hotspot mod installed, and TWRP custom recovery. (if possible, I'd like to get there without tripping the KNOX counter, but if that is not possible, so be it)
From what I've read, it looks like I need to
Nandroid backup (optional)
Install stock MF9 tar file using ODIN (recovery, ROM, Modem, kernel) - http://forum.xda-developers.com/showthread.php?t=2485502
Take OTA (or use update file from google server link on http://forum.xda-developers.com/showthread.php?t=2504349)
Reboot (Don't install any apps at this time)
Use CF Auto to root using ODIN - http://forum.xda-developers.com/showpost.php?p=41743640&postcount=3
Factory reset just in case
Install goo manager, and flash custom recovery TWRP
Reboot
Reinstall apps
Install new MJA odexed hotspot mod http://forum.xda-developers.com/showthread.php?t=2256950
Nandroid backup
Is this about right? (and are the links to the right files/posts?)
Is there an easier/safer way of doing this?
Is there any way to not trip the knox counter? Or does the flash of CF Auto to root always trip it?
Any other troubleshooting steps in case things go wrong?
Example:
If phone gets stuck in bootloop at any step - what steps should be attempted before pulling battery, and trying to reflash in ODIN?
If phone shows android lying down with red exclamation mark, what should be attempted?
If root doesn't stick after reboot, what should be attempted?
If custom recovery doesn't stick, what should be attempted?
Hopefully, this will help others like me as well.
Thanks!
Click to expand...
Click to collapse
Hi,
It'll be awhile, I live on my boat & Connectivity can be slow this time of day, but I'm dwnldg & will let you know how it goes. I'm praying this is it I'm going on13=14 hrs screwing around with it. Thanks for your style of posting,too, very user friendly.
ms.samsprung said:
Hi,
It'll be awhile, I live on my boat & Connectivity can be slow this time of day, but I'm dwnldg & will let you know how it goes. I'm praying this is it I'm going on13=14 hrs screwing around with it. Thanks for your style of posting,too, very user friendly.
Click to expand...
Click to collapse
Thank you
Is this how it's supposed to be done?
http://forum.xda-developers.com/showthread.php?t=2509605
Oh boy, I really screwed this one up...
I purchased a used Note 3 from eBay, hoping to be able to root it after it arrived. Much to my surprise, it arrived rooted with Safestrap, Hyperdrive ROM in Stock slot, and a different Hyperdrive ROM in Slot1. I was also impressed that KNOX had not been tripped. (It said Custom, but the KNOX flag showed 0x00)
Sweet looking phone in hand, I was thrilled! I wasn't going to have to cut my teeth on rooting the device myself prior to having an opportunity to explore a rooted Android and a custom ROM. The very first thing I did was to use Safestrap to backup both the Stock slot and Slot1. After the backups, I booted the stock slot first, to see how a factory Note 3 should look. Surprise again, the stock slot booted a Hyperdrive ROM. I was a bit nervous that I didn't have a truly stock ROM, but wasn't too worried about it because I had no plans to resell or seek repairs under warranty.
I then spent a couple of days tinkering with the device. Unfortunately, half asleep during the wee hours of the morning, I was tinkering around with SuperSU -- setting grant/deny/prompt flags for different apps. Somewhere in the midst of that, SuperSU informed me that I had lost root. I checked with RootChecker, and sure enough NO Root.
Things got worse from there, as I'm sure you can imagine. RootChecker had a button to relaunch SuperSU, so I tapped it. This time, SuperSU wanted to re-install itself. Being the ignorant noob that I am, I told SuperSU to proceed, and crossed my fingers. After a few seconds of thrashing around, SuperSU wanted to reboot, so I said okay...
Now the device attempts to go into recovery, reboots itself, attempts recovery, reboots, again, and again... boot loop... and no way to charge the battery... I believe I am around 55% to 60% charged at the moment.
So I read great things about Odin and downloaded a copy -- not yet sure exactly what I was going to do with it. I have been trying to wrap my head around this for a couple of days now, but I have several questions that I hope somebody can shed some light on.
Does the rooting take place in the boot image, or in the ROM image? I am assuming it has to be in the boot image, but then I've heard you can have rooted and unrooted ROMs in different slots.
If I use Odin to flash fresh firmware, will this firmware will have a functional recovery tool bundled with it?
Since the phone is no longer rooted, the recovery will not be able to re-flash a ROM onto the device?
If an Odin installed recovery can't re-flash a ROM due to being unrooted, am I faced with JTAG options only?
If I were to use Odin to flash this firmware: http://forum.xda-developers.com/showthread.php?t=2726558 , could I perhaps get SafeStrap back and be able to restore the backups I made? The links on that page appear to be to the same (or very similar) firmware that was running prior to this disaster. NC2, Safestrap, etc.
If I can't use Odin to flash the firmware linked in the previous paragraph, and get Safestrap to restore my backups, can I use the firmware, ROMs, and PIT file linked here: http://forum.xda-developers.com/showthread.php?t=2576104 to restore the phone to factory conditions and re-root from there?
Finally, is there any way for me to avoid tripping KNOX at this point? I'm not really sure I care if it gets tripped, but if I can avoid it then I probably should. Am I likely to need KNOX container support on a private device in the near future? Is there any other reason to be spooked about losing KNOX? I really don't care much about the warranty.
Any help with this mess will be **greatly** appreciated!
lintex said:
If I were to use Odin to flash this firmware: http://forum.xda-developers.com/showthread.php?t=2726558 , could I perhaps get SafeStrap back and be able to restore the backups I made? The links on that page appear to be to the same (or very similar) firmware that was running prior to this disaster. NC2, Safestrap, etc.
Click to expand...
Click to collapse
Ok, if anybody comes across this thread looking for answers -- I did successfully use Odin to get this firmware back onto the device. Upon booting, I had Safestrap, was able to boot Slot1, and had root. When I boot from the Stock slot, still no root.
I have not yet attempted to restore the Stock slot backup, because I first want to see if I can boot Slot1 (to get root), and then find/mount the Stock slot image and see if I can find a way to re-root it manually.
lintex said:
Ok, if anybody comes across this thread looking for answers -- I did successfully use Odin to get this firmware back onto the device. Upon booting, I had Safestrap, was able to boot Slot1, and had root. When I boot from the Stock slot, still no root.
I have not yet attempted to restore the Stock slot backup, because I first want to see if I can boot Slot1 (to get root), and then find/mount the Stock slot image and see if I can find a way to re-root it manually.
Click to expand...
Click to collapse
Using any other slot other then stock is going to be problematic. So use the stock slot. You are using the nc2 firmware if you have the reboot to recovery bootloop issue. You can flash the nc4 patched firmware in beans firmware thread if you want. Reboot to recovery is not the same as reboot to safestrap. Download a fresh rom. Wipe everything but external sd under the advanced wipe button in safestrap. Flash your new rom making sure stock slot is the active slot. Setup phone like normal. Make a backup with your now freshly setup rom. Rinse and repeat for new roms. Label your backups if you want to rom jump. Always use stock slot. Odin the nc2 kernel if you have a blackscreen on first boot of a new rom.
RomsWell said:
Using any other slot other then stock is going to be problematic.
Click to expand...
Click to collapse
In my case, Slot1 is simply a rooted ROM that I can use when the Stock slot gets messed up. I have no desire or intent to tinker with Slot1. I consider it as an emergency tool only. It does seem to have an issue though. It never seems to want to power all the way down for some reason.
RomsWell said:
So use the stock slot. You are using the nc2 firmware if you have the reboot to recovery bootloop issue. You can flash the nc4 patched firmware in beans firmware thread if you want. Reboot to recovery is not the same as reboot to safestrap.
Click to expand...
Click to collapse
I am using the NC2 firmware, but I no longer have the bootloop problem. After using Odin to re-install the NC2 firmware from BeansTown, the device was once again able to boot to Safestrap. From there, I was able to select and boot either of the existing slots. Slot1 still boots to root, Stock slot is still unrooted. I should be able to use Safestrap to restore my Stock slot backup and regain root on Slot1, right?
The only reason I have not yet attempted to restore the Stock slot backup is because I hope to boot my rooted Slot1 ROM, mount the Stock ROM image, and fix the Stock ROM image. If not, then I will try to restore the Stock slot backup.
RomsWell said:
Download a fresh rom. Wipe everything but external sd under the advanced wipe button in safestrap. Flash your new rom making sure stock slot is the active slot.
Click to expand...
Click to collapse
I definitely plan to flash a new ROM, soon. I want a fresh clean ROM for personal use, and I also need to find a ROM that supports HDMI -- because I want to get Debian to display on a larger screen. My ultimate goal is to create my own ROMs. I have a bit of experience with kernel tweaking/building, and created a bootable Linux-based DVD image by hand. I believe I will someday be able to tweak phone ROMs as well, but I'm still fuzzy about much of the Android system. Stuff like locks and KNOX seem like quite a mine field and make me very nervous. A blank DVD coaster is one thing, an expensive smartphone is scary.
lintex said:
In my case, Slot1 is simply a rooted ROM that I can use when the Stock slot gets messed up. I have no desire or intent to tinker with Slot1. I consider it as an emergency tool only. It does seem to have an issue though. It never seems to want to power all the way down for some reason.
I am using the NC2 firmware, but I no longer have the bootloop problem. After using Odin to re-install the NC2 firmware from BeansTown, the device was once again able to boot to Safestrap. From there, I was able to select and boot either of the existing slots. Slot1 still boots to root, Stock slot is still unrooted. I should be able to use Safestrap to restore my Stock slot backup and regain root on Slot1, right?
The only reason I have not yet attempted to restore the Stock slot backup is because I hope to boot my rooted Slot1 ROM, mount the Stock ROM image, and fix the Stock ROM image. If not, then I will try to restore the Stock slot backup.
I definitely plan to flash a new ROM, soon. I want a fresh clean ROM for personal use, and I also need to find a ROM that supports HDMI -- because I want to get Debian to display on a larger screen. My ultimate goal is to create my own ROMs. I have a bit of experience with kernel tweaking/building, and created a bootable Linux-based DVD image by hand. I believe I will someday be able to tweak phone ROMs as well, but I'm still fuzzy about much of the Android system. Stuff like locks and KNOX seem like quite a mine field and make me very nervous. A blank DVD coaster is one thing, an expensive smartphone is scary.
Click to expand...
Click to collapse
As long as you stick to the known exploits like safestrap and towelroot then theres no worrys about knoxs. And no real way to perma brick the device. Make sure you stick to offical firmware when using odin and abuse your device like you would any other.
I recently upgraded today from 4.4.2 to 5.0 OC4 and kept root using this method: http://forum.xda-developers.com/ver...0-keeproot-t3068546/post59791648#post59791648
However, I had no Idea it would be so hard (impossible?) to get xposed back. Is there any way in which I could install xposed ARM without having a custom recovery on my verizon G900V running lollipop?
I also read an article on another website that said you can flash safestrap with odin, go into safestrap, install anything necessary, and then reflash current ROM? I am not TOO knowledgable with all of this, however I have found my way around all this enough to ensure myself root and all needed features. Any help or information would be amazing.
Article: http://www.droidforums.net/threads/galaxy-s5-safestrap-after-the-lollipop-update.279867/
I was considering flashing the xposed ARM file with flashfire, however I read someone else was stuck in a bootloop who tried this. Would this not work? Is there any method? I was also looking into flash gordon which lets you flash .zip files without requiring custom recovery. Thanks!
EDIT: Just did some more research and found this thread: http://forum.xda-developers.com/galaxy-s4-att/general/nc1-flasher-odin-to-safestrap-t3082620
It seems as if its possible, however this thread is for the OC3 version, while I flashed the OC4... Anyone out there done anything like this before, or knows how to provide the needed steps? Thanks again.
Go to the xposed thread and read any comment at all. It doesn't work on touchwiz based lollipop architecture. PERIOD. you didn't need a new thread in this forum to learn that...
I see, is there some way that I could downgrade. I've been looking into that for awhile now to go back to my 4.4.2 but there's a ton of methods and I am not sure which is required for my device. I canno't seem to find a specific method for my g900v s5. Thanks for you're reply, and I hope I can downgrade.
synkro1 said:
I see, is there some way that I could downgrade. I've been looking into that for awhile now to go back to my 4.4.2 but there's a ton of methods and I am not sure which is required for my device. I canno't seem to find a specific method for my g900v s5. Thanks for you're reply, and I hope I can downgrade.
Click to expand...
Click to collapse
You can use this guide: http://forum.xda-developers.com/showthread.php?t=3088571 it might need some modification for 4.4.2, however.
synkro1 said:
I see, is there some way that I could downgrade.j I've been looking into that for awhile now to go back to my 4.4.2 but there's a ton of methods and I am not sure which is required for my device. I canno't seem to find a specific method for my g900v s5. Thanks for you're reply, and I hope I can downgrade.
Click to expand...
Click to collapse
You can go up and down as often as you like. I would Odin the NCG tar from the link below and reroot.
You probably still have safestrap. You could try this first. Go to download mode and Odin the NE9 kernel. When your phone starts booting up you should see the safestrap option to boot into recovery. Boot into recovery, install a rooted NE9 ROM of your choice. Boot back into download mode via safestrap and Odin the NE9 firmware. Let your phone boot all the way up and you should be good to go. Use NCG kernels and firmware-roms if you would rather be on NGC.
http://forum.xda-developers.com/ver...ment/stock-collection-kernels-modems-t2842069
If safestrap doesn't show up, Odin the full NCG tar file and reroot your phone.
Thanks so much for your help, the only problem is I never installed safestrap on my phone. So I do not currently have safe strap, or any custom recovery. So i can just use the odin method then, correct?
[PHP[/PHP]
synkro1 said:
Thanks so much for your help, the only problem is I never installed safestrap on my phone. So I do not currently have safe strap, or any custom recovery. So i can just use the odin method then, correct?
Click to expand...
Click to collapse
Yes, sir. That would be correct. Since you are rooted, there is an app called Flashfire you could use that doesn't even require a computer but if you are familiar with Odin that is a good way to go as well.
I have flashfire installed, in fact I used it to upgrade to lollipop. What settings should I use with flashfire to downgrade to lollipop? Do i have to clear cache or anything? And will the file from the notes #4 from here work?: http://forum.xda-developers.com/ver...0-keeproot-t3068546/post59791648#post59791648
synkro1 said:
I have flashfire installed, in factj I used it to upgrade to lollipop. What settings should I use with flashfire to downgrade to lollipop? Do i have to clear cache or anything? And will the file from the notes #4 from here work?: http://forum.xda-developers.com/ver...0-keeproot-t3068546/post59791648#post59791648
Click to expand...
Click to collapse
What ROM do you want to have on your phone?
Just a normal stock 4.4.2 ROM works fine for me.
synkro1 said:
Just a normal stock 4.4.2 ROM works fine for me.
Click to expand...
Click to collapse
Download this ROM onto your SD card. I prefer deodex
http://forum.xda-developers.com/showthread.php?t=2793931
Download the NGC retail firmware from here.
http://forum.xda-developers.com/ver...ment/stock-collection-kernels-modems-t2842069
In Flashfire, select firmware and navigate to your firmware. Just check boot and recovery
Next select zip-ota, navigate to your ROM. Leave auto mount unchecked.
Select firmware again. This time check boot, recovery, modem, and firmware. Flashfire will ask if you want them in separate zips. Click yes
Now select wipe. Check everything but SD card.
Now arrange everything in this order
Wipe
Firmware-boot recovery
Zip-rom
Firmware modem firmware
Firmware-boot recovery
Ever root- inject supersu
Boot normal
That should do it. You should be rooted on 4.4.2
Tulsadiver said:
Download this ROM onto your SD card. I prefer deodex
http://forum.xda-developers.com/showthread.php?t=2793931
Download the NGC retail firmware from here.
http://forum.xda-developers.com/ver...ment/stock-collection-kernels-modems-t2842069
In Flashfire, select firmware and navigate to your firmware. Just check boot and recovery
Next select zip-ota, navigate to your ROM. Leave auto mount unchecked.
Select firmware again. This time check boot, recovery, modem, and firmware. Flashfire will ask if you want them in separate zips. Click yes
Now select wipe. Check everything but SD card.
Now arrange everything in this order
Wipe
Firmware-boot recovery
Zip-rom
Firmware modem firmware
Firmware-boot recovery
Ever root- inject supersu
Boot normal
That should do it. You should be rooted on 4.4.2
Click to expand...
Click to collapse
Ur amazing. I'll try it and let you know. Thanks so much for your help.
Thanks so much! It worked perfectly! I had a problem initially after installing towelroot and xposed and got an error when rebooting the phone called "Process system isn't responding". My phone kept freezing and was super slow because of this. I believe it was due to me restoring contacts from titanium backup. I restored the contacts system app as a whole. I didn't realize that at the time however, and just system restored my phone again, and did everything the same yet didn't restore my contacts, and the message is now gone. I am not running root with xposed on 4.4.2. Your amazing!
Is it possible, I've seen a video where it is done but need to go to LP first, I much prefer kk on s5 as running a ported s5 kk on my s4 and wish to keep it. Any time I flash a kk stock based rom via twrp it boots to boot animation and then freezes and reboots. Any one done the downgrade?
SM-G900F Unlocked.
Baseband- G900FXXU1CPB8
Sent from my GT-I9505
I did it, straight from 6.0.1 to 4.4.2. But I did it using kdz files. I think you also need to downgrade the modem. etc.
Just make sure you reset your phone, clear cache/dalvik before you go to download mode. You will have boot loops otherwise. Which is easily fixed by going to recovery...and resetting, clearing cache.
Of course this means you can not keep your data. Do backup with TB, etc. and restore after.
s3nr1 said:
I did it, straight from 6.0.1 to 4.4.2. But I did it using kdz files. I think you also need to downgrade the modem. etc.
Just make sure you reset your phone, clear cache/dalvik before you go to download mode. You will have boot loops otherwise. Which is easily fixed by going to recovery...and resetting, clearing cache.
Of course this means you can not keep your data. Do backup with TB, etc. and restore after.
Click to expand...
Click to collapse
I don't suppose u have a link to these files? With my s4 it was lp - kk and we used a modded tar file ( full rom) via Odin then flashed which ever stock kk we wanted. I feel stock 4.4.2 deodexed rooted with busy box is best for me.
Sent from my GT-I9505
jimbomodder said:
I don't suppose u have a link to these files? With my s4 it was lp - kk and we used a modded tar file ( full rom) via Odin then flashed which ever stock kk we wanted. I feel stock 4.4.2 deodexed rooted with busy box is best for me.
Sent from my GT-I9505
Click to expand...
Click to collapse
Just get the stock 4.4.2 rom and flash it with odin you don't really need to do nothing special for that, anyways I would recommend to just install Cyanogenmod 13 and fell good about having a good rom, unlike us with the H variant stuck with ****ty touchwiz lol