Hey all,
After some browsing on here recently, it looks like a somewhat experimental exploit has been found to gain temporary root access long enough for Sunshine to do its thing. I am planning to use the "Kingroot" method to root and permanently s-off my HTC M8.
It has been some time since I seriously rooted any android phone so I wanted to compile a checklist of the steps I will need to take to fully downgrade my operating system from Lollipop back to Kit Kat once all is said and done. My questions are as follows:
-is it necessary to flash a stock 4.x.x sense rom before flashing a custom 4.x.x build?
- from a stability/performance standpoint what sense kit Kat rom do you find to be the best? I prefer sense for the great widgets and features it provides.
- is flashing a kernel necessary for going from 5.x.x to 4.x.x? I recall doing this to my OG droid several times.
- will flashing new radios be necessary or are the still included in rom builds?
- Is twrp the preferred recovery for the m8 or do alternatives exist which you'd recommend?
Please let me know of any other important steps I will need to take before attempting the downgrade. Thanks in advance.
x25064 said:
Hey all,
After some browsing on here recently, it looks like a somewhat experimental exploit has been found to gain temporary root access long enough for Sunshine to do its thing. I am planning to use the "Kingroot" method to root and permanently s-off my HTC M8.
It has been some time since I seriously rooted any android phone so I wanted to compile a checklist of the steps I will need to take to fully downgrade my operating system from Lollipop back to Kit Kat once all is said and done. My questions are as follows:
-is it necessary to flash a stock 4.x.x sense rom before flashing a custom 4.x.x build?
- from a stability/performance standpoint what sense kit Kat rom do you find to be the best? I prefer sense for the great widgets and features it provides.
- is flashing a kernel necessary for going from 5.x.x to 4.x.x? I recall doing this to my OG droid several times.
- will flashing new radios be necessary or are the still included in rom builds?
- Is twrp the preferred recovery for the m8 or do alternatives exist which you'd recommend?
Please let me know of any other important steps I will need to take before attempting the downgrade. Thanks in advance.
Click to expand...
Click to collapse
Once s-off if you want stock experience, I would flash kk ruu
This should be in Q&A, not development. Maybe @moderator an move it?
x25064 said:
Hey all,
After some browsing on here recently, it looks like a somewhat experimental exploit has been found to gain temporary root access long enough for Sunshine to do its thing. I am planning to use the "Kingroot" method to root and permanently s-off my HTC M8.
It has been some time since I seriously rooted any android phone so I wanted to compile a checklist of the steps I will need to take to fully downgrade my operating system from Lollipop back to Kit Kat once all is said and done. My questions are as follows:
-is it necessary to flash a stock 4.x.x sense rom before flashing a custom 4.x.x build?
Click to expand...
Click to collapse
You mean after being s-off? No
- from a stability/performance standpoint what sense kit Kat rom do you find to be the best? I prefer sense for the great widgets and features it provides.
Click to expand...
Click to collapse
Totally personal preference. I like CleanROM
- is flashing a kernel necessary for going from 5.x.x to 4.x.x? I recall doing this to my OG droid several times.
Click to expand...
Click to collapse
The kernel is part of the rom you flash. You can flash a different kernel after installing a rom. Just gotta make sure it's compatible with the rom
- will flashing new radios be necessary or are the still included in rom builds?
Click to expand...
Click to collapse
On HTC devices you have to distinguish between firmware and rom. The firmware is radios, hboot and such. The rom is seperate. In general you have to have 4.4 firmware to run a KK rom and 5.x firmware to run a LP rom. Although I know of people who flashed the 5.0.1 firmware and then went back to CleanROM 3.x (which is KK) without a problem. YMMV
Is twrp the preferred recovery for the m8 or do alternatives exist which you'd recommend?
Click to expand...
Click to collapse
Everybody seems to be running TWRP
Please let me know of any other important steps I will need to take before attempting the downgrade. Thanks in advance.
Click to expand...
Click to collapse
You cannot downgrade to KK unless you are s-off. Once you are s-off, flash the firmware for the rom you want to run, then flash the rom
Thanks for the info, that is exactly what I need. I finally have some time today to give this a shot so I will report my results.
Looks like I am already running into issues with Kingroot not opening on my phone. It will install, then once selected from my app drawer it just flashes the screen with no result.
I got another version from a download list on XDA heres the progress so far:
- kingroot gains root after 2-3 tries, no big deal
- sunshine installed and given su permission
- sunshine verifies, I pay them, final tests are run and it reboots
- phone fully rebooted, sunshine asks to continue
- I hit home and minimized Sunshine, went back to kingroot, installed - reboot - Sunshine pops up, minimize, kingroot - repeat until root is successful
- maximize Sunshine from apps tray, continue - s-off successfully
- rebooted the phone into the boot menu and verified that the bootloader is unlocked and s-off has been successfully achieved
I do also concur with other postings that the modified flag has been placed when I enter the boot menu.
Also just to clarify - I CAN download RUU 4.4.3, place it on my root SD directory (FAT32), and go into hboot mode and flash accordingly? This won't brick my phone going from 5.0.1 to 4.4.3 as long as the phone is s-off unlocked?
Ok.. I flashed 4.4.3 which worked.. then went into the play store to grab TWRP - tried to install the recovery and it said something went wrong. I chose to reboot the phone into recovery to check if one was already installed (I thought RUU was bone stock..) and now I can't get kitkat to boot up.. it just goes to TWRP or gives me the red exclamation point....... not sure what to do here but I don't think adb will work since it requires drivers I can't install without the phone being fully booted up..
EDIT: Since I still had a recovery and an SD card with the 4.4.3 RUU on it, I just wiped the system and booted up into the hboot to reinstall the RUU again. Phew..
Now I'm just confused as to why TWRP did that to my phone in the first place? I don't want to install it again now because that was such a pain, but I want to get a rom loaded..
TWRP Manager sucks. The partition layout is slightly different between KK and LP and probably TWRP Manager flashed the recovery to the system partition. That's why it booted straight to recovery.
Use fastboot to flash TWRP.
Thanks man, that makes sense. I'll give it a shot tomorrow!
I was able to RUU TWRP no problem with a RUU zip I found on here. Worked like a charm.
I have to say I didn't realize how bad the official lollipop OTA is compared to running a 4.4.3 version of viperrom. It's like night and day and my battery life is excellent now. So glad the kingroot exploit worked!
x25064 said:
I was able to RUU TWRP no problem with a RUU zip I found on here. Worked like a charm.
I have to say I didn't realize how bad the official lollipop OTA is compared to running a 4.4.3 version of viperrom. It's like night and day and my battery life is excellent now. So glad the kingroot exploit worked!
Click to expand...
Click to collapse
Thanks for this whole thread! Your detailed process has given me the confidence to finally do this on mine, can't wait to be back to KK and have a working device again!
Related
I'm on the latest official OTA of 4.2.1
Do I need to unlock the bootloader to root?
I read this http://forum.xda-developers.com/showthread.php?t=2187982
and I'm still not sure whats happening... Do I need to downgrade to root, and do I need to unlock the bootloader to flash TWRP?
I know a bit of what I'm doing as I have rooted and flashed roms on an htc desire and a samsung s2x (t989).
On 4.2.1 theres the occasional hiccup and freezes when I use chrome... Is this still an issue in the custom roms? Also my Settings app crashes when I try to load the "Running" tab in the apps section of settings lol
Can someone point me in the right direct?
Chris9446 said:
I'm on the latest official OTA of 4.2.1
Do I need to unlock the bootloader to root?
Click to expand...
Click to collapse
Well, you have two basic options:
Get root without unlocking.
That is good, if you want to stick with stock ROM, but want to run Apps that need root access.
Or if you don't want to unlock for any reason.
More details in this thread: [JB ROOT] motochopper works! (Root JB 4.1.1 & 4.2.1 with locked bootloader!)
Unlock and install the patched TWRP for -4.2.
This will allow you to root stock ROM easily or you can install custom ROMs.
Be careful: You have the boot loader 4.2, which means you need to pick the patched TWRP for that boot loader and you need to pick one of the ROMs supporting the 4.2 boot loader.
People have bricked their TF300Ts not using the patched TWRP -4.2 version.
There are currently only two ROMs available, but more should be coming soon, as Asus has finally released the new kernel source code.
If your preferred custom ROM supports only the 4.1 boot loader, you need to downgrade. Or just wait a little, as you like...
I read this http://forum.xda-developers.com/showthread.php?t=2187982
and I'm still not sure whats happening... Do I need to downgrade to root, and do I need to unlock the bootloader to flash TWRP?
Click to expand...
Click to collapse
No and yes.
You can use the tool from the tread above just get root; no downgrading, no unlocking.
But yes, if you want to install TWRP, you need to unlock your device first.
You only need to downgrade for installing a custom ROM that does not (yet) support the 4.2 boot loader.
On 4.2.1 theres the occasional hiccup and freezes when I use chrome... Is this still an issue in the custom roms? Also my Settings app crashes when I try to load the "Running" tab in the apps section of settings lol
Click to expand...
Click to collapse
I have not used stock ROM for a while, but generally people report that most custom ROMs run much smoother than stock Asus ROM:
I would suggest downgrading ti the 4.1.1 bootloader, as there is a much larger variety or ROMS available.
f69m said:
Well, you have two basic options:
Get root without unlocking.
That is good, if you want to stick with stock ROM, but want to run Apps that need root access.
Or if you don't want to unlock for any reason.
More details in this thread: [JB ROOT] motochopper works! (Root JB 4.1.1 & 4.2.1 with locked bootloader!)
Unlock and install the patched TWRP for -4.2.
This will allow you to root stock ROM easily or you can install custom ROMs.
Be careful: You have the boot loader 4.2, which means you need to pick the patched TWRP for that boot loader and you need to pick one of the ROMs supporting the 4.2 boot loader.
People have bricked their TF300Ts not using the patched TWRP -4.2 version.
There are currently only two ROMs available, but more should be coming soon, as Asus has finally released the new kernel source code.
If your preferred custom ROM supports only the 4.1 boot loader, you need to downgrade. Or just wait a little, as you like...
No and yes.
You can use the tool from the tread above just get root; no downgrading, no unlocking.
But yes, if you want to install TWRP, you need to unlock your device first.
You only need to downgrade for installing a custom ROM that does not (yet) support the 4.2 boot loader.
I have not used stock ROM for a while, but generally people report that most custom ROMs run much smoother than stock Asus ROM:
Click to expand...
Click to collapse
Thanks was a lot of great information! I rooted my pad and did a few speed optimization things such as re-trimming and now its much smoother! Maybe I'll try a custom rom later but as for now, I'm happy with the updates that Asus provides
cmendonc2 said:
I would suggest downgrading ti the 4.1.1 bootloader, as there is a much larger variety or ROMS available.
Click to expand...
Click to collapse
I'll keep that in mind but I believe there should be more soon as f69m, stated that asus release the kernel for 4.2
I signed that petition in your signature as well
I'd say go for the 'full experience'. Having an unlocked device also allows you to reflash ROMs at will and can also help in a pinch when it comes to backups/restores. Also, if you happen to lose root, it's easily re-rootable through the bootloader.
I'd just be careful of the current TWRP 4.2.1 recovery blob. I just flashed the one released this morning and I am currently getting this weird double screen thing. Best bet is to sit tight at the moment; an update should be out shortly.
danjng said:
I'd just be careful of the current TWRP 4.2.1 recovery blob. I just flashed the one released this morning and I am currently getting this weird double screen thing. Best bet is to sit tight at the moment; an update should be out shortly.
Click to expand...
Click to collapse
Well, stay away from the TWRP 2.5.0.0-4.2 provided in some thread today, but TWRP 2.4.4.0-4.2 should still be working fine.
Sent from my TF300T using Tapatalk HD
So i held out taking the otas for a while to avoid losing root and am still on 4.2.2 post camera update. I know, it's sad, but I have root so i haven't been dying to update.
However, i just saw that sunshine will unlock my bootloader, which I'm going to do. What I'm confused about though is once i unlock my bootloader, how do I get to 4.4.4? Can I just revert everything to stock and take all of the otas (and then flash twrp to get root)? I heard that something in one of the otas changed something with the bootloader, so i don't know if taking that would cause problems with an unlocked bootloader or make me lose my unlocked status. Either way, could i just flash a 4.4.4 image directly from 4.2.2? If so where do i get a stock image to flash? Thanks for any help!
Once you have successfully unlocked, make sure you are status 3 unlocked in fastboot.
Once confirmed, you can use the rsd lite, and use the stock firmware from:
http://sbf.droid-developers.org/
Next, flash twrp for the ghost from their website.
Lastly if you want root flash supersu.
So can I flash a different OS version from the site that you linked? Or is that just to return to stock in anticipation of flashing TWRP and using that to flash a later android version?
rule of thumb is you cannot downgrade, only upgrade or revert to the same version you are already on
This seemed like the easiest route to a rooted 4.4.4... Unlock bootloader via Sunshine, and proceed as instructed here: http://forum.xda-developers.com/droid-ultra/general/unlocked-boot-xt-1080-restore-4-4-4-pre-t2883131
Data remains intact, unlocked bootloader warning on boot logo fixed, and TWRP (or Philz) flashed as recovery. Super easy. Good times.
Deleted. Redundant post.
Sent from my DROID Maxx
I'm in the same situation. I'm currently rooted on the post camera update and held off on the new ota's for a while. I want to do the sunshine unlock. My question is should I do the sunshine unlock, upgrade to the newest 4.4.4 then install twrp to root? This youtube.com/watch?v=_xVyJMtLDPgvideo gives pretty good instructions but I also want to take future OTA's. I understand you won't be able to unless you put the recovery back to stock.
Thanks in advanced
rcji said:
I'm in the same situation. I'm currently rooted on the post camera update and held off on the new ota's for a while. I want to do the sunshine unlock. My question is should I do the sunshine unlock, upgrade to the newest 4.4.4 then install twrp to root? This youtube.com/watch?v=_xVyJMtLDPgvideo gives pretty good instructions but I also want to take future OTA's. I understand you won't be able to unless you put the recovery back to stock.
Thanks in advanced
Click to expand...
Click to collapse
Yep true. Can't take OTAs with out stock recovery. But it is easy to flash Stock Recovery then back to TWRP after the OTA. Of course safest option is to flash stock fxz without wiping data before taking OTAs.
Personally have my own recovery and logo.bin script I keep for just this reason. Run RSDlite with the stock software take OTA (if no fxz yet for the OTA) then full bit and setup and finally flash the recovery and logo.bin I use.
Many ways of doing it just find its easier for me this way probably cause this is how I learned from trial and error is all. Probably an easier way though.
Just a quick question here since I don't see a guide anywhere. My brother is getting an M8 from Verizon in several weeks (he's getting a new contract and the M8 looks like the best free/cheap phone available). So I can assist him, what is the current status on unlocking the bootloader and rooting? Looks like it will ship with Lollipop according to Verizon's site.
I don't need detailed guides on doing everything (I'm familiar with the concepts; I have a Nexus 5 myself), but just a quick "Bootloader can't be unlocked, so no root" or whatever the case is would be greatly appreciated.
Thank you!
www.theroot.ninja
Sunshine 3.x now unlocks/ s-offs VZW M8 with LP 5.0
Not 100% on rooting.
I literally just flashed TWRP to mine via ADB fastboot method about 4 minutes ago and am running a stock nandroid backup as I type this.
I was on 4.4.4 when I S-offed, then took the LP update to 5.0, then flashed TWRP recovery (right now) in order to flash SuperSU. That's about all I know. Everyone said to S-off BEFORE taking the OTA update in order to obtain root on LP.. so I did. Now i'm just trying to figure out where I get this SU to install for perm root. Now your guess is as good as mine for why I needed to S-off BEFORE taking the OTA. The new sunshine that was released (3.x) is able to S-off after the update so I'm really not sure what the difference would be whether you S-off on 4.4.4 or 5.0 and then do the same process to install supersu. Anyways, hope this kind of helps.
Oh, and I suppose if you S-offed , you could flash TWRP then just install a pre-rooted stock ROM which i'm sure is somewhere out there.
baune7 said:
www.theroot.ninja
Sunshine 3.x now unlocks/ s-offs VZW M8 with LP 5.0
Not 100% on rooting.
I literally just flashed TWRP to mine via ADB fastboot method about 4 minutes ago and am running a stock nandroid backup as I type this.
I was on 4.4.4 when I S-offed, then took the LP update to 5.0, then flashed TWRP recovery (right now) in order to flash SuperSU. That's about all I know. Everyone said to S-off BEFORE taking the OTA update in order to obtain root on LP.. so I did. Now i'm just trying to figure out where I get this SU to install for perm root. Now your guess is as good as mine for why I needed to S-off BEFORE taking the OTA. The new sunshine that was released (3.x) is able to S-off after the update so I'm really not sure what the difference would be whether you S-off on 4.4.4 or 5.0 and then do the same process to install supersu. Anyways, hope this kind of helps.
Oh, and I suppose if you S-offed , you could flash TWRP then just install a pre-rooted stock ROM which i'm sure is somewhere out there.
Click to expand...
Click to collapse
You needed to s-off before taking the ota because sunshine still does not work on VERIZON M8s on lollipop
BladeRunner said:
You needed to s-off before taking the ota because sunshine still does not work on VERIZON M8s on lollipop
Click to expand...
Click to collapse
Ahhhh.. OK.
Glad I didn't update then before I ran Sunshine. I'm sure Jcase and his buddy are working on getting VZW ironed out soon. Just finished Flashing TWRP, and to the OP.. when you flash TWRP, it roots it for you pretty much, it must be bundled in there. After I made the backup, and went to reboot it asked if I wanted to install superSU since it saw I wasn't rooted yet. It did and I just rebooted and it was there, updated the binaries no problems and now I'm on stock VZW LP-rooted.
baune7 said:
Ahhhh.. OK.
Glad I didn't update then before I ran Sunshine. I'm sure Jcase and his buddy are working on getting VZW ironed out soon. Just finished Flashing TWRP, and to the OP.. when you flash TWRP, it roots it for you pretty much, it must be bundled in there. After I made the backup, and went to reboot it asked if I wanted to install superSU since it saw I wasn't rooted yet. It did and I just rebooted and it was there, updated the binaries no problems and now I'm on stock VZW LP-rooted.
Click to expand...
Click to collapse
Would you know what should a newbie do to root an unlocked, S-off, Android 4.4.4, htc6525lvw?
sambaba said:
Would you know what should a newbie do to root an unlocked, S-off, Android 4.4.4, htc6525lvw?
Click to expand...
Click to collapse
Did you even read the last 3 posts?????
Flash TWRP in fastboot, boot back into it and it will root the phone....
hello
i want to upgrade my nexus to the latest version of google-marshmallow, is there any rom that it's just stock+root build in or there is option that i will install the stock from google + install afterwards the root cause i saw that chainfire isn't work so well on the last version (MRA58N)?
basicly all i need is to record calls and the control on the led light so if there is option to do these two without root so i will install the stock rom from google
thank you
I7210I said:
hello
i want to upgrade my nexus to the latest version of google-marshmallow, is there any rom that it's just stock+root build in or there is option that i will install the stock from google + install afterwards the root cause i saw that chainfire isn't work so well on the last version (MRA58N)?
basicly all i need is to record calls and the control on the led light so if there is option to do these two without root so i will install the stock rom from google
thank you
Click to expand...
Click to collapse
Without root, just flash the google images or bat file if it works for you-never has for me. With root, I recommend Wugfresh NRT (http://forum.xda-developers.com/showthread.php?t=2517778). If you go with google, you need to alter the google bat file for no wipe. Don't run user data img if flashing each file. You still need to know basics in case you run into a problem. Be sure to make a backup through recovery. Sounds like you're on MM so you can run the "no wipe" mode. Follow directions as he presents them. Check the android development thread for roms.
Sent from my Nexus 9 using Tapatalk
first i'm in 4.4.4 but i want to upgrade ...and it's look like for these two things i need root, so how to install the root let's say i'm installing from the google developer site the last version ...what about the root?
thanks
First, I will recommend a complete wipe from LP to MM. To root, you need custom recovery which you flash from fastboot just like you flash stock recovery. Then, you need a modified stock kernel or a custom kernel. After flashing those, download latest SUPERSU, boot into recovery, flash the supersu apk (actually, I think the app will do this for you). This is exactly what the toolkit does for you which is why I recommend it. He pulls all the needed files for you and automates everything except actually rooting. He pushes the files to your device then boots you into recovery where you will flash the required files. His kit creates a log which you can submit if a problem occurs. You can read the thread about rooting, etc in general subforum. I'll get URL.
http://forum.xda-developers.com/showthread.php?t=3050789
Sent from my Nexus 5 using Tapatalk
thank you for the help
so i need an modified kernel+stock rom+root
which kernel is most likely close to the stock one?
so,now i have the 4.4.4 plus twrp recovery and stock kernel.
if i will install these kernel http://forum.xda-developers.com/google-nexus-5/orig-development/kernel-elementalx-n5-0-44-t2519607 and twrp recovery and stock 6 last version (MRA58N)
what to do next to make root?
as i read here http://forum.xda-developers.com/goo...e-update-rooted-device-to-5-1-lmy47d-t3050789
he doesn't recomend in these situation to install root...so what to do in my methood?
thanks
Do Not Flash This On Unlocked Bootloaders Or You Will Relock Your Bootloader!!!​Once your on MM 6.0.1 you cannot restore a Lollipop Backup using SafeStrap or vice versa. Follow the link at bottom of post for guide and files to downgrade back to Lollipop
Ok the first thing I want to make clear is YOU WILL NOT HAVE ROOT! You will still have the use of Safestrap Recovery even though phone will not be rooted. What this will allow you to do is boot the non rooted rom back into safestrap. While in Safestrap you can do what you have always done, Flash Zips, Make Backups,Etc. This will also make it easy if you want to go back to PB1 rooted rom.
You must be on A rooted rom preferably A PB1 rom running SafeStrap
If Running FlashFire
Make sure latest busybox is installed
Install MM_Safestrap.apk
Reboot to safestrap
Wipe Data,Cache,System
Install VZW_QA1_STOCK_SAFESTRAP_ONLY_V2.zip
Roms will take a long time to boot up be patient!
This will put you on pure stock rom MM QA1 rom but from here you can get to safestrap to flash other roms or mods
To return to Safestrap you will need to flash a kitkat kernel NI2_stock_kernel.tar.md5 using odin then when phone reboots click on enter safestrap recovery. When leaving safestrap you must flashMM_KERNEL_SS-FF_Flashable.zip. Which will be located on your internal storage In a folder called MM_KERNEL_SS-FF_Flashable
If you want to flash other custom roms a guide can be found HERE
Useful zips
View attachment ADBlocking_2_5_17.zip
View attachment DebloatScript.zip
Thanks Jkruse!
Question... I tried your stock PB1 before and it worked well. I however hosed myself flashing the incorrect firmware and USB bulk mode occured when I attempted to go back to PHX11 5.0 ROM. I flashed firmware as when I reloaded the backup of PHX 11 I had no data or wifi.
I saved the phone however and need to know what is the correct procedure to go back to LP backups if I try this and decide not to stay? I want to avoid bulk mode again!
Thank you!!
ridenickel9 said:
Thanks Jkruse!
Question... I tried your stock PB1 before and it worked well. I however hosed myself flashing the incorrect firmware and USB bulk mode occured when I attempted to go back to PHX11 5.0 ROM. I flashed firmware as when I reloaded the backup of PHX 11 I had no data or wifi.
I saved the phone however and need to know what is the correct procedure to go back to LP backups if I try this and decide not to stay? I want to avoid bulk mode again!
Thank you!!
Click to expand...
Click to collapse
Once your on this rom The link at the bottom of the OP has a guide and files for going back to lollipop BP1 build without having to reroot. It's in the second post of that guide
jrkruse said:
Once your on this rom The link at the bottom of the OP has a guide and files for going back to lollipop BP1 build without having to reroot. It's in the second post of that guide
Click to expand...
Click to collapse
I'll read up! Thank you!!
Would this be the same procedure for OG5 just substitute the PB1 caution firmware with OG5 caution firmware? I assume just match the ROM you go to with the caution zips that don't contain the bootloader.
Pretty sure I didn't use the caution firmware before and that what caused my issues.
ridenickel9 said:
I'll read up! Thank you!!
Would this be the same procedure for OG5 just substitute the PB1 caution firmware with OG5 caution firmware? I assume just match the ROM you go to with the caution zips that don't contain the bootloader.
Pretty sure I didn't use the caution firmware before and that what caused my issues.
Click to expand...
Click to collapse
If you goback to lollipop it will need to be PB1
Added debloat script to post 2 that can be flashed with safestrap
jrkruse said:
If you goback to lollipop it will need to be PB1
Click to expand...
Click to collapse
OK thank you for clarifying. I use PHX 11 and always need to flash the OG5 kernal from safe strap so I assumed I'd need OG5 firmware for that particular situation.
Also thanks for updating the OP about using backups to and from MM - that will help others avoid issues.
I'll stop clogging the thread now! Appreciate all the information and work you do!!
Hey, thanks for this great site and all of your guides. It really helps.
I just rooted my s5 g900v and Im still on KITKAT NK2. Would it be possible for me to update from that version to this one following your guide?
Sorry for asking really basic questions. My phone at the moment is sim unlocked and rooted, but CID starts with 11 so I cannot unlock the boatloader, right? Then I assume this ROM is my best option. I want to be really sure that I will still be sim unlocked on the new ROM, its got nothing to do with it, right?
Many many thanks in advanced!
nachoalt said:
Hey, thanks for this great site and all of your guides. It really helps.
I just rooted my s5 g900v and Im still on KITKAT NK2. Would it be possible for me to update from that version to this one following your guide?
Sorry for asking really basic questions. My phone at the moment is sim unlocked and rooted, but CID starts with 11 so I cannot unlock the boatloader, right? Then I assume this ROM is my best option. I want to be really sure that I will still be sim unlocked on the new ROM, its got nothing to do with it, right?
Many many thanks in advanced!
Click to expand...
Click to collapse
Yes you can update to this rom and also verizon phones are all sim unlocked so it will rermain sim unlocked. Just remember if your still on kitkat when you flash anything with safestrap do not use rom slots flash on the stock rom slot. If you dont know what this means then dont worry about it
jrkruse said:
Added debloat script to post 2 that can be flashed with safestrap
Click to expand...
Click to collapse
Thanks for the hard work, unfortunately my cid 15 just took a nice fat swim and i had to get a replacement and got a cid 11 instead (##$$%@@@!#[email protected]). Your guides have been great to get to this point but got a couple questions:
Any link to what the debloat script removes? I just ran it and it doesn't seem to remove anything (ran it at same time as addblock). Going to reboot and flash it again see if it does. Any way we can remove the stuff we don't want? (all the VZW junk)