I'm on a Verizon Note 4 (N910V). Bootloader unlocked, rooted, and TWRP installed. It is on the stable version of hsbadr's Unofficial CM13 6.0.1. The bootloader version is CPD1. Flashfire has special instructions for Samsung devices with protected partitions. There is no data on the phone that I care about. I just want to keep root, TWRP and the unlocked bootloader. I assume that I uncheck "boot" and "Recovery", but I'm interested what people have done with the protected partitions. Chainfire recommends a technique for flashing some thru ODIN after flashing the System on Flashfire. Any suggestion are needed and very welcome.
Related
so from what i understand about updating the bootloader to MJB, i can only flash custom ROMs based off TouchWiz 4.3 and up, correct?
but AOSP/CM based ROMs can be any version? as long as the bootloader is supported on that ROM? and worst case scenario, i can flash CM10.1.3 (Android 4.2.2)?
currently i'm on S3Rx 2.2, which uses Android 4.1.2. there would be no point in making a nandroid backup, since the bootloader would be updated and i could no longer use this ROM, correct?
i was going to follow this guide:
http://forum.xda-developers.com/showthread.php?t=2321310
and then use this ROM:
http://forum.xda-developers.com/showthread.php?t=2252932
***************SOLVED:***************
flash the MJB bootloader via custom recovery following the above guide.
then flash the MJB modem via custom recovery with this guide:
http://forum.xda-developers.com/showthread.php?t=1831898
reboot to phone (i did, not sure if necessary tho)
then reboot to recovery, flash new custom ROM.
done.
a mistake i did was i only flashed the bootloader first. rebooted, then flashed new ROM. in which case i had no wifi and data. so i flashed the modem, rebooted, no wifi and data still. rebooted into recovery, factory reset, wipe cache, wipe dalvik, and everything worked fine after that.
mrhomiec said:
so from what i understand about updating the bootloader to MJB, i can only flash custom ROMs based off TouchWiz 4.3 and up, correct?
but AOSP/CM based ROMs can be any version? as long as the bootloader is supported on that ROM? and worst case scenario, i can flash CM10.1.3 (Android 4.2.2)?
currently i'm on S3Rx 2.2, which uses Android 4.1.2. there would be no point in making a nandroid backup, since the bootloader would be updated and i could no longer use this ROM, correct?
i was going to follow this guide:
http://forum.xda-developers.com/showthread.php?t=2321310
and then use this ROM:
http://forum.xda-developers.com/showthread.php?t=2252932
Click to expand...
Click to collapse
You could install the MJ2 bootloader and MJB modem which would allow you the ability to go back. Once you are on MJB bootloader, there is not going back without bricking. If you ever find that you need to revert back for any reason you will be stuck. If this does not bother you, then go for it.
aybarrap1 said:
You could install the MJ2 bootloader and MJB modem which would allow you the ability to go back. Once you are on MJB bootloader, there is not going back without bricking. If you ever find that you need to revert back for any reason you will be stuck. If this does not bother you, then go for it.
Click to expand...
Click to collapse
i read somewhere that MJ2 was unstable or something. cause it was a preview leak?
but back to my first question, MJB makes it so i can only flash TouchWiz-based ROMs 4.3 and up? so i will be good to use AOSP-based ROMs of any version?
For clarification purposes:
If you upgrade to MJB you will have the 4.3 KNOX apps (OS) and KNOX bootloader (Firmware). You can easily root following this guide: http://forum.xda-developers.com/showthread.php?t=2538991
Once rooted by following the guide noted above you will have the 4.3 KNOX (OS) removed BUT not the KNOX bootloader. With the KNOX bootloader you will never be able to downgrade the bootloader. What that means is that you can never use odin to flash an older firmware or you will brick!
Now that your MJB is rooted you can flash any ROM you want 4.1.2, 4.2.2, 4.3, 4.4.2 since most custom ROMS dont include the bootloader in the ROM package.
Hope this clears things up?
flynhawn2002 said:
For clarification purposes:
If you upgrade to MJB you will have the 4.3 KNOX apps (OS) and KNOX bootloader (Firmware). You can easily root following this guide: http://forum.xda-developers.com/showthread.php?t=2538991
Once rooted by following the guide noted above you will have the 4.3 KNOX (OS) removed BUT not the KNOX bootloader. With the KNOX bootloader you will never be able to downgrade the bootloader. What that means is that you can never use odin to flash an older firmware or you will brick!
Now that your MJB is rooted you can flash any ROM you want 4.1.2, 4.2.2, 4.3, 4.4.2 since most custom ROMS dont include the bootloader in the ROM package.
Hope this clears things up?
Click to expand...
Click to collapse
Yes it does! Thank you!!
I'm on the latest bootloader and modem and I haven't had any trouble flashing any aosp based roms. Only thing I was told you might have to take the bootloader line out of the update script, but so far I haven't had to at all.
flynhawn2002 said:
If you upgrade to MJB you will have the 4.3 KNOX apps (OS) and KNOX bootloader (Firmware). You can easily root following this guide: http://forum.xda-developers.com/showthread.php?t=2538991
Click to expand...
Click to collapse
just wanted to clarify, i'm already rooted, so i was going to follow the guide from my first post (since this guide has ZIP files i can flash in CWM):
http://forum.xda-developers.com/showthread.php?t=2321310
Flashing in recovery
If you've downloaded a flashable .ZIP from above, copy it to your SD card or internal storage. Reboot your phone into recovery mode (you can do this by holding "Volume Up" and "Home" while powering on your device; let go of the buttons when you see "Recovery booting..." in blue text in the top left of the screen) and install the .ZIP as an update. Reboot, and you're done.
Note: After flashing in recovery, you need to reboot before you (and ROM installers) actually see the new version number.
Click to expand...
Click to collapse
would i reboot first, then flash a new ROM?
or should i flash the bootloader, then immediately flash the new ROM?
UPDATE: so i ended up just following the ZIP file guide:
http://forum.xda-developers.com/showthread.php?t=2321310
and now i don't have data or wifi. i flashed the modem from here:
http://forum.xda-developers.com/showthread.php?t=1831898
ANOTHER UPDATE:
after i went into recovery, factory reset, wipe cache, wipe dalvik. the phone is recognizing wifi and data now. woo!
Confused about rooting with T999UVUEOH1
ok
If the phone is running a stock 4.3 Samsung ROM, the phone will have knox. Best thing to do would be to run OTA updates until the phone is running the latest ROM. This will ensure that the phone has the most recent bootloader and modem.
Once updated, you can easily root the phone by flash TWRP for the d2tmo via Odin. After installing TWRP, you can flash supersu 2.45 or 2.46 via TWRP and have root access.
Note that flashing TWRP will trip the knox counter.
Ok
The method I recommended should not cause any loss of data. To be safe, always backup before flashing anything.
Is there any warranty left on the phone? If not, tripping knox isn't going to matter.
Any attempts to downgrade the bootloader may result in a bricked phone.
Looks like the root66 method involves flashing a prerooted stock ROM. If you want to try the root66 method, just make sure the root66 ROM's bootloader and modem are the same or newer than the phone's version. If the phone has oh1, I would not use the root66 method.
Ok
Flashing TWRP and supersu from TWRP is the easiest in my opinion.
Just make sure to get the tar version of TWRP to flash in Odin.
audit13 said:
Flashing TWRP and supersu from TWRP is the easiest in my opinion.
Just make sure to get the tar version of TWRP to flash in Odin.
Click to expand...
Click to collapse
Nahh!! The easiest way is use TowelRoot
Only need to press a button! I'm using that firmware so I CONFIRM that it's working
I guess it depends on the rom. It wouldn't work on stock 4.4.2 for me.
The kernel was patched against Towelroot in 4.4.2. We were never updated past 4.3 so it should work fine.
Sent from my SGH-T999 using Tapatalk
How do I root my tmobile m8 running Android 5.0.1 and bootloader unlock. Also custom recovery so I can flash a 6.0 ROM
You're saying your bootloader is already unlocked? It may already have custom recovery installed. Just pick "recovery" from bootloader, and see if TWRP boots.
If not, just flash TWRP with fastboot.
You don't need to root, if you are going to go and flash a custom ROM anyway. Depending on the ROM, it may already be rooted. Otherwise, flash the appropriate SuperSU version.
redpoint73 said:
You're saying your bootloader is already unlocked? It may already have custom recovery installed. Just pick "recovery" from bootloader, and see if TWRP boots.
If not, just flash TWRP with fastboot.
You don't need to root, if you are going to go and flash a custom ROM anyway. Depending on the ROM, it may already be rooted. Otherwise, flash the appropriate SuperSU version.
Click to expand...
Click to collapse
No its not unlocked, I want to unlock it. And can I go from stock 5.0.1 to a custom 6.0 ROM?
I got everything situated thanks
NexusS4gFreak said:
No its not unlocked, I want to unlock it. And can I go from stock 5.0.1 to a custom 6.0 ROM?
Click to expand...
Click to collapse
I know you got it sorted out. But its best to post your solution, for the benefit of others that my have the same issue/questions and be looking at the thread in the future:
For a completely stock device on Lollipop, the suggested sequence to install a custom ROM:
1) Unlock the bootloader by HTCDev.com (the process is rather self-explanatory if you follow the instructions on the website)
2) Install custom recovery TWRP 2.8.7.0 by fastboot
3) Flash the MM ROM of your choice. Most will work with Lollipop firmware (meaning, if your phone was on LP when you were stock) but check the thread of the particular desired ROM to be sure.
4) Most ROMs are pre-rooted. But again, check the desired ROM thread to confirm (as root on MM is a little different from past builds).
I want to have a rooted stock Android Nexus 5X with stock recovery. I also want to keep my boot loader locked. But I've read that automatic OTA updates don't work on a rooted phone. Then I found out about FlashFire.
But I also read that FlashFire doesn't allow flashing of the radio and boot loader. Chainfire himself said "FlashFire can flash both bootloaders and modems on most Nexus devices. However, I would only flash the modem and not the bootloaders, to be on the safe side. Or, use the full size OTAs available from Google rather than the Fastboot package, and circumvent the issue (those flash both bootloader and modem if necessary, with less risk when doing the bootloaders)."
So I've got 2 questions:
1. Is it possible to flash everything, including the radio and boot loader on the 5X?
2. If the boot loader is flashable, what are the potential drawbacks of flashing it with Flashfire instead of fastboot?
Thanks
Hello,
I have rooted my HTC One m8(No S-OFF). It also has TWRP and it's on Android 5.0.1/HTC Sense 6
I googled and read about reverting to stock recovery and then doing an OTA upgrade of the OS. But I'd rather not go back to stock and then TWRP back again.
Is there any way or instructional to follow that can enable me to update to Android 6 whilst keeping TWRP and my root settings on.
Any help is appreciated
My experience, is that Marshmallow ROMs work fine on Lollipop firmware. I've been doing so since December, for no better reason than I've been too lazy to update my firmware.
So that means you should be able to just restore the proper Marshmallow TWRP backup for your version, and just run that without updating anything else. Although, be sure to leave yourself an escape plan, just in case it doesn't work (either your own LP backup, or be prepared to use one from the collection).
However, for best compatibility, you should really update your firmware. And doing so, either by flashing stock firmware, OTA, or RUU by "official" means (and official/signed means are what you need to use, since you are s-on) will by definition wipe out TWRP.
But honestly, flashing TWRP back to the phone is easy. You just download the .img file to your computer, than flash with a single fastboot command, with the phone connected. This is actually a fast and simple process, when compared to the other stuff you are talking about doing (restoring stock backup and recovery, OTA update).
Plus, since you are updating to Marshmallow, you'll also want to update to TWRP 3.0.2 anyway.
redpoint73 said:
My experience, is that Marshmallow ROMs work fine on Lollipop firmware. I've been doing so since December, for no better reason than I've been too lazy to update my firmware.
So that means you should be able to just restore the proper Marshmallow TWRP backup for your version, and just run that without updating anything else. Although, be sure to leave yourself an escape plan, just in case it doesn't work (either your own LP backup, or be prepared to use one from the collection).
However, for best compatibility, you should really update your firmware. And doing so, either by flashing stock firmware, OTA, or RUU by "official" means (and official/signed means are what you need to use, since you are s-on) will by definition wipe out TWRP.
But honestly, flashing TWRP back to the phone is easy. You just download the .img file to your computer, than flash with a single fastboot command, with the phone connected. This is actually a fast and simple process, when compared to the other stuff you are talking about doing (restoring stock backup and recovery, OTA update).
Plus, since you are updating to Marshmallow, you'll also want to update to TWRP 3.0.2 anyway.
Click to expand...
Click to collapse
Thanks redpoint73.
My chief motivation behind moving to Android 6 is a sound problem I've been having lately. I installed the AcousticX sound mod but when I listen to audiobooks, I hear a clipping sound sometimes.
The developer over @ AcousticX suggested a few things and one of which was making the switch to marshmallow.
thread: http://forum.xda-developers.com/showthread.php?p=68881108#post68881108
From some reading and your suggestions, I gathered the right way to go about this is, is to flash stock recovery(overriding twrp). Do an OTA upgrade(1.6 gb download/install) and afterwards reinstall TWRP and whatever else was previously done.
Am I correct in surmising this?
Thanks
AadilK said:
From some reading and your suggestions, I gathered the right way to go about this is, is to flash stock recovery(overriding twrp). Do an OTA upgrade(1.6 gb download/install) and afterwards reinstall TWRP and whatever else was previously done.
Am I correct in surmising this?
Click to expand...
Click to collapse
Not only the stock recovery, but you also need to restore the unrooted TWRP backup (never rooted ROM, "unrooting" doesn't work). Since having root will prevent OTA.
The full process is described here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
The other option, depending on what M8 version you have, may be to RUU to Marshmallow. That allows you skip a lot of the steps needed in the previous method (restoring a never rooted TWRP backup, restoring stock recovery, OTA updated) but adds a couple other steps (relock bootloader to RUU, unlock it again after RUU to flash TWRP); plus the RUU will wipe all user data on the device.
So its a judgment call for you (if your version has RUU) what path is preferred.