Hi all,
Within the last month I successfully unlocked my 5x, rooted it, installed a custom recovery and have kept it on stock ROM with a custom kernel (ElementalX) and some minor tweaks (AdAway, Viper4Android). So far, so great.
However, when I was locked and unrooted, I used to use ADB and the sideload OTA function to update to the newest builds, usually within 3-5 days after the binaries first drop.
Now, with the desire to remain on an updated stock ROM, keep root, custom recovery, and the minor tweaks noted above, I wanted some confirmation from the great minds here as I navigate Heisenberg's thread and use fastboot on my own for the first time.
What I've done so far: Download and extract the binaries from my current build (MHC19Q) as well as today's new build (MTC19T).
Compared them and see there is a new radio that I'll have to flash.
I want to keep my custom recovery (TWRP) and boot image (ElementalX kernel), so I believe I leave those untouched.
So, my process here is:
1. Boot into bootloader mode. Open a command prompt and confirm via fastboot devices that my device is connected/recognized through USB.
2. Enter "fastboot flash radio {insert radio.img here}"
3. Enter fastboot reboot-bootloader
4. Enter "fastboot erase cache"
5. Enter "fastboot flash cache {insert cache.img here}", repeat step 3
6. Enter "fastboot flash system {insert system.img here}, repeat step 3
7. Enter "fastboot flash vendor {insert vendor.img here}
My 2 questions are - will this process above succeed in updating my security/build and leave my recovery and kernel untouched? And will I keep root and modifications, or have to reflash TWRP, SuperSU, AdAway, Viper4Android, etc.?
Thanks for the patience, all. Once I do this once or twice, I'm sure it'll become old hat!
Moonboots said:
Hi all,
Within the last month I successfully unlocked my 5x, rooted it, installed a custom recovery and have kept it on stock ROM with a custom kernel (ElementalX) and some minor tweaks (AdAway, Viper4Android). So far, so great.
However, when I was locked and unrooted, I used to use ADB and the sideload OTA function to update to the newest builds, usually within 3-5 days after the binaries first drop.
Now, with the desire to remain on an updated stock ROM, keep root, custom recovery, and the minor tweaks noted above, I wanted some confirmation from the great minds here as I navigate Heisenberg's thread and use fastboot on my own for the first time.
What I've done so far: Download and extract the binaries from my current build (MHC19Q) as well as today's new build (MTC19T).
Compared them and see there is a new radio that I'll have to flash.
I want to keep my custom recovery (TWRP) and boot image (ElementalX kernel), so I believe I leave those untouched.
So, my process here is:
1. Boot into bootloader mode. Open a command prompt and confirm via fastboot devices that my device is connected/recognized through USB.
2. Enter "fastboot flash radio {insert radio.img here}"
3. Enter fastboot reboot-bootloader
4. Enter "fastboot erase cache"
5. Enter "fastboot flash cache {insert cache.img here}", repeat step 3
6. Enter "fastboot flash system {insert system.img here}, repeat step 3
7. Enter "fastboot flash vendor {insert vendor.img here}
My 2 questions are - will this process above succeed in updating my security/build and leave my recovery and kernel untouched? And will I keep root and modifications, or have to reflash TWRP, SuperSU, AdAway, Viper4Android, etc.?
Thanks for the patience, all. Once I do this once or twice, I'm sure it'll become old hat!
Click to expand...
Click to collapse
Yes, that will keep your recovery untouched, however you might want to wait until flar2 and/or other kernel devs confirm there are no changes to the kernel before you upgrade your system. More often than not, there are improvements to the kernel source.
About Adaway, Viper4Android, etc... I'm almost sure you will have to reflash those, as they are part of the system.
I am myself waiting for confirmation about the kernel stuff, but in the meantime will flash bootloader and radio.
redsmith said:
Yes, that will keep your recovery untouched, however you might want to wait until flar2 and/or other kernel devs confirm there are no changes to the kernel before you upgrade your system. More often than not, there are improvements to the kernel source.
About Adaway, Viper4Android, etc... I'm almost sure you will have to reflash those, as they are part of the system.
I am myself waiting for confirmation about the kernel stuff, but in the meantime will flash bootloader and radio.
Click to expand...
Click to collapse
Excellent, thank you for the quick reply. I'll put a subscription on the ElementalX Kernel thread and keep an eye out before making any changes.
Also, if I'm reading the updates correctly, the bootloader remains unchanged at version bhz10m. In your experience, are there changes under the hood there that don't appear in the version number, or is there no need to flash the "new" bootloader, as it's identical?
I would like to have a sort of ota to install just the updated files that leaves my system mod untouched. But I think there is no way to keep everything...
redsmith said:
Yes, that will keep your recovery untouched, however you might want to wait until flar2 and/or other kernel devs confirm there are no changes to the kernel before you upgrade your system. More often than not, there are improvements to the kernel source.
About Adaway, Viper4Android, etc... I'm almost sure you will have to reflash those, as they are part of the system.
I am myself waiting for confirmation about the kernel stuff, but in the meantime will flash bootloader and radio.
Click to expand...
Click to collapse
To be a little bit more specific, you have to flash again whatever you have flashed so far.
Adaway is an app, you don't have to flash it nor reinstall.
Same for xposed, you have to flash over the framework, but your installed modules will remain and work once you have reflashed xposed for instance.
exploreresp said:
To be a little bit more specific, you have to flash again whatever you have flashed so far.
Adaway is an app, you don't have to flash it nor reinstall.
Same for xposed, you have to flash over the framework, but your installed modules will remain and work once you have reflashed xposed for instance.
Click to expand...
Click to collapse
Thank you for the clarification. I've been keeping an eye on the ElementalX thread and it appears everything works with the newest build without a need for an update to the kernel.
With that being said, do I need to flash the new boot.img and recovery.img, then re-flash TWRP and ElementalX, or can I just not push the new binaries for boot and recovery, and just do radio, system, and vendor?
Moonboots said:
Thank you for the clarification. I've been keeping an eye on the ElementalX thread and it appears everything works with the newest build without a need for an update to the kernel.
With that being said, do I need to flash the new boot.img and recovery.img, then re-flash TWRP and ElementalX, or can I just not push the new binaries for boot and recovery, and just do radio, system, and vendor?
Click to expand...
Click to collapse
Don't think it'll hurt to try
I already avoided to flash the recovery img last month but it still got patched and had to flash TWRP again so I'm not sure...
Anyway, don't think this May update is worth all the trouble... Only security updates that haven't even been reported by users. Unless you're really worried about smtg, this won't bring you anything.
exploreresp said:
Don't think it'll hurt to try
I already avoided to flash the recovery img last month but it still got patched and had to flash TWRP again so I'm not sure...
Anyway, don't think this May update is worth all the trouble... Only security updates that haven't even been reported by users. Unless you're really worried about smtg, this won't bring you anything.
Click to expand...
Click to collapse
Confirming here for the group and anyone that hasn't used fastboot before - totally easy and worked like a charm. I know you mentioned there wasn't much to the May update but I still wanted to do it as an academic exercise for myself so I know how to do it in the future.
I flashed the new radio.img, vendor.img and system.img. Bootloader stayed the same. Recovery held at TWRP and the kernel (boot.img) patched over ElementalX on first boot. I flashed SuperSU, ElementalX and the Viper4Android drivers and everything was back up and running, fully updated. The whole thing took about 15 min.
Thanks for the help and encouragement, all.
Related
Dear XDA Members,
I currently run stock 5.1.1 (14.6.A.1.236) with no modifications whatsoever and a locked bootloader.
I would like to install a custom rom (PAC-ROM LP-MR1 5.1.1) on my Z1C.
I did some research and these are the steps i came up with:
1. install sdk and drivers
2. unlock bootloader
3. fastboot flash recovery "fota.img" (shouldn't it specify somehow that i need it to be flashed on the fota partition?)
4. factory reset/wipe
5. install custom rom + gapps
Coming from a locked bootloader a fully stock phone is there anything else i need to do like a new bootloader or something?
Also I'll be doing it through Win 10 64bit, I hope that isn't a problem.
Any advice will be highly appreciated.
Thank you very much
ursidae1 said:
Dear XDA Members,
I currently run stock 5.1.1 (14.6.A.1.236) with no modifications whatsoever and a locked bootloader.
I would like to install a custom rom (PAC-ROM LP-MR1 5.1.1) on my Z1C.
I did some research and these are the steps i came up with:
1. install sdk and drivers
2. unlock bootloader
3. fastboot flash recovery "fota.img" (shouldn't it specify somehow that i need it to be flashed on the fota partition?)
4. factory reset/wipe
5. install custom rom + gapps
Coming from a locked bootloader a fully stock phone is there anything else i need to do like a new bootloader or something?
Also I'll be doing it through Win 10 64bit, I hope that isn't a problem.
Any advice will be highly appreciated.
Thank you very much
Click to expand...
Click to collapse
First things first... Root. If you already did that then you're on the right track.
1. If you're not doing major development stuff, don't install the whole sdk. See here - http://forum.xda-developers.com/showthread.php?p=48915118 There may be issues you'll have to work with on newer versions of Windows. I haven't done it on anything later than 7. Keep in mind, though, that you won't need the computer to flash your boot img or rom, but you will need it to unlock the bootloader.
2. -
3. You can do this with an app called Rashr on your phone with root. Just download a recovery img, then open Rashr and follow the instructions.
4-5. Boot into recovery, full wipe, (system data and caches), flash rom zip and gapps zip. Maybe best to not flash more than that at once to start, in case there's a problem and you have no way to figure out what it is.
BTW, PacMan is a great choice. I've been using it for months.
levone1 said:
First things first... Root. If you already did that then you're on the right track.
1. If you're not doing major development stuff, don't install the whole sdk. See here - http://forum.xda-developers.com/showthread.php?p=48915118 There may be issues you'll have to work with on newer versions of Windows. I haven't done it on anything later than 7. Keep in mind, though, that you won't need the computer to flash your boot img or rom, but you will need it to unlock the bootloader.
2. -
3. You can do this with an app called Rashr on your phone with root. Just download a recovery img, then open Rashr and follow the instructions.
4-5. Boot into recovery, full wipe, (system data and caches), flash rom zip and gapps zip. Maybe best to not flash more than that at once to start, in case there's a problem and you have no way to figure out what it is.
BTW, PacMan is a great choice. I've been using it for months.
Click to expand...
Click to collapse
Thanks a lot for your reply.
I was reading on the cyanogen mod wiki how-to for our phone and it doesn't require a prior root.
I did those steps on my xperia m and it worked and i had never rooted it, the only difference is that i flashed cyanogen recovery and install cm12 which basically roots the phone and then flashed fota recovery.
Should i go this way again to gain root or would you recommend an easier root method for my stock build which is the newest.
If you recommend another root method when should it occur? prior unlocking the bootloader or afterwards?
Thanks
If this is your first time unlocking your bootloader, make sure you backup your DRM-Keys! You need to be rooted for that.
They are lost when bootloader gets unlocked. Some features in regards of camera performance are lost for example.
ursidae1 said:
Thanks a lot for your reply.
I was reading on the cyanogen mod wiki how-to for our phone and it doesn't require a prior root.
I did those steps on my xperia m and it worked and i had never rooted it, the only difference is that i flashed cyanogen recovery and install cm12 which basically roots the phone and then flashed fota recovery.
Should i go this way again to gain root or would you recommend an easier root method for my stock build which is the newest.
If you recommend another root method when should it occur? prior unlocking the bootloader or afterwards?
Thanks
Click to expand...
Click to collapse
True, if bl is unlocked, then you can flash the kernel and recovery via fastboot, then flash your rom. You may need the boot.img from your rom zip file. Then use commands 'fastboot flash boot' for the boot img, and 'fastboot flash recovery' for recovery. If you're rooted already, you can just do it on the phone.
levone1 said:
True, if bl is unlocked, then you can flash the kernel and recovery via fastboot, then flash your rom. You may need the boot.img from your rom zip file. Then use commands 'fastboot flash boot' for the boot img, and 'fastboot flash recovery' for recovery. If you're rooted already, you can just do it on the phone.
Click to expand...
Click to collapse
This is fantastic.
Do you think itll be ok to fastboot flash boot boot.img from cm12.1 rom zip then fastboot flash recovery fota.img instead of the cyanogen recovery that comes with cm12.1?
Do you think that might cause an issue?
ursidae1 said:
This is fantastic.
Do you think itll be ok to fastboot flash boot boot.img from cm12.1 rom zip then fastboot flash recovery fota.img instead of the cyanogen recovery that comes with cm12.1?
Do you think that might cause an issue?
Click to expand...
Click to collapse
Should be fine. It's also a 1 second operation to extract boot.img from your rom zip, which you need already downloaded and on your SD card before you flash imgs. You might even be fine without flashing the boot img - can't hurt to try. Just flash the recovery and reboot and see if you get a purple light. Then, volume button changes purple to orange, and you're in recovery. Some recoveries don't work with some kernels, (been my experience).
levone1 said:
Should be fine. It's also a 1 second operation to extract boot.img from your rom zip, which you need already downloaded and on your SD card before you flash imgs. You might even be fine without flashing the boot img - can't hurt to try. Just flash the recovery and reboot and see if you get a purple light. Then, volume button changes purple to orange, and you're in recovery. Some recoveries don't work with some kernels, (been my experience).
Click to expand...
Click to collapse
I now have cm12.1 with cyanogen recovery.
Which recovery is best for our phone, which one do you use?
I can find 2 options:
FOTA TWRP 2.8.6.0 (http://forum.xda-developers.com/sony-xperia-z1-compact/general/fota-twrp-recovery-amami-t2909719)
XZDualRecovery (http://forum.xda-developers.com/showthread.php?t=2647480)
Thanks a lot
ursidae1 said:
I now have cm12.1 with cyanogen recovery.
Which recovery is best for our phone, which one do you use?
I can find 2 options:
FOTA TWRP 2.8.6.0 (http://forum.xda-developers.com/sony-xperia-z1-compact/general/fota-twrp-recovery-amami-t2909719)
XZDualRecovery (http://forum.xda-developers.com/showthread.php?t=2647480)
Thanks a lot
Click to expand...
Click to collapse
I have only used xzdr with stock rom. I think in the past I've had it not work for me on CM, so I just stick to straight twrp by default. I know NUT has always been hard at work and has made steady improvements, so maybe not an issue now. Personally I realized that I only need 1 recovery anyway. There's a newer Twrp here - http://forum.xda-developers.com/crossdevice-dev/sony/twrp-v2-8-6-0-f2fs-z1-z1c-z2-z3-z3c-t3098573
One important fact that has already been probably mentioned is that installing custom roms on your XPERIA will worsen your camera, esp the front one. Keep this in mind.
Good afternoon folks, sorry for what may appear to be a silly question but I wanted to confirm I understood what I needed to do before I committed.
I have a Verizon XL, DePixel8 and SuperSu'd the week they came out. Currently running ElementalX 3.18.31-ElementalX-0.05 with SuperSU 2.79. This is android 7.1 with security patch from October 5th. Looks like to update the kernal I need to flash TWRP. BUT if I need to go through that dont I need to put the stock kernal back on?
Is this what I need to do?
-Backup my stuffs
-factory reset
-Flash Stock firmware kernal bootloader and then twrp
-factory reset/clear cache and all that good stuff for good measure?
-TWRP RC1
-At this point, Its fine, I COULD tryPure Nexus or some other rom on here but I would at the very least like to patch the security vulnerabilities. So....?
-Activate/install SuperSU
Then I am back in business?
Side note, Certain apps, like stupid snapchat recognize the hankypanky going on, but sometimes doesnt. It literally sometimes works. Is this fixed in later updates/supersu/roms? Or are we waiting for xposed? or Am i missing something?
Greensystemsgo said:
Good afternoon folks, sorry for what may appear to be a silly question but I wanted to confirm I understood what I needed to do before I committed.
I have a Verizon XL, DePixel8 and SuperSu'd the week they came out. Currently running ElementalX 3.18.31-ElementalX-0.05 with SuperSU 2.79. This is android 7.1 with security patch from October 5th. Looks like to update the kernal I need to flash TWRP. BUT if I need to go through that dont I need to put the stock kernal back on?
Is this what I need to do?
-Backup my stuffs
-factory reset
-Flash Stock firmware kernal bootloader and then twrp
-factory reset/clear cache and all that good stuff for good measure?
-TWRP RC1
-At this point, Its fine, I COULD tryPure Nexus or some other rom on here but I would at the very least like to patch the security vulnerabilities. So....?
-Activate/install SuperSU
Then I am back in business?
Side note, Certain apps, like stupid snapchat recognize the hankypanky going on, but sometimes doesnt. It literally sometimes works. Is this fixed in later updates/supersu/roms? Or are we waiting for xposed? or Am i missing something?
Click to expand...
Click to collapse
So, your bootloader is Unlocked? If so you can flash the newest 7.1.1 .imgs from Google via fastboot. It wont re-lock ur bootloader. From there flash TWRP and flash any Rom you like. All ROMs keep pretty up to date on the security patches. RR included. Which is here
BDogg718 said:
So, your bootloader is Unlocked? If so you can flash the newest 7.1.1 .imgs from Google via fastboot. It wont re-lock ur bootloader. From there flash TWRP and flash any Rom you like. All ROMs keep pretty up to date on the security patches. RR included. Which is here
Click to expand...
Click to collapse
Really? So i guess my issue is with Elemental-X then stating it needs TWRP to be updated. Does that mean I should just dump Elemental-X? OR update Elemental-X Manually over fastboot and not on the phone itself? This is my screen so It looks like it is unlocked.
I will look at your Rom recommendation, I know it will overwrite my existing kernel which I dont care about I just though I needed to revert it back to stock BEFORE I update it.
So, I have an unlocked bootloader, BUT no recovery, so basically everything is done over fastboot which is what I am used to, all TWRP does is add a nice graphical interface to it? But doesnt modify the bootloader persay? So really I dont even NEED TWRP but it may be nice. Really I could just stick a rom on there via fastboot and be on my merry way? I think that was where my confusion was stemming from. I read your roms page and sounds like a solid option. Thankyou!
Greensystemsgo said:
Really? So i guess my issue is with Elemental-X then stating it needs TWRP to be updated. Does that mean I should just dump Elemental-X? OR update Elemental-X Manually over fastboot and not on the phone itself? This is my screen so It looks like it is unlocked.
I will look at your Rom recommendation, I know it will overwrite my existing kernel which I dont care about I just though I needed to revert it back to stock BEFORE I update it.
So, I have an unlocked bootloader, BUT no recovery, so basically everything is done over fastboot which is what I am used to, all TWRP does is add a nice graphical interface to it? But doesnt modify the bootloader persay? So really I dont even NEED TWRP but it may be nice. Really I could just stick a rom on there via fastboot and be on my merry way? I think that was where my confusion was stemming from. I read your roms page and sounds like a solid option. Thankyou!
Click to expand...
Click to collapse
No my friend, U def still need TWRP. Fastboot and TWRP are 2 very different things. Follow TWRP instructions for installation. You want to flash TWRP RC1.
Sorry for not being clear, I was accidentally using bootloader and twrp interchangeably.
Heres how I did it;
- Backup my junk
- Factory reset
- Flash NMF26V-vendor.img via fastboot
- Boot into twrp via fastboot
- Clear Cache
- Flash rom via twrp
- Clear cache
- Flash twrp via twrp
- Flash su via twrp
- Clear Cache
- Factory reset
- Profit.
I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!
bdsuser said:
I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!
Click to expand...
Click to collapse
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
1. Download a ROM. A stock version is probably in the forums somewhere if that's what you want.
2. Download TWRP image and zip from the TWRP thread.
3. Download SuperSU from the SuperSU thread.
4. Download a vendor image. There's no "official" vendor image thread AFAIK, but you can grab one from the Pure Nexus rom thread. NMF26V is compatible with all 7.1.1 ROMs & stock.
Now you have two options:
Fast: Put the ROM, TWRP(zip only), SuperSU and vendor image on USB flash drive, then connect the USB 3 to USB C adapter to your flash drive. Don't connect it to the phone yet. An external HDD/SSD should also work if that's all you've got.
Slow: While in TWRP(Instructions below) push the ROM, TWRP(zip only), SuperSU and vendor image files to your phone through ADB with "adb push C:\file_path\ /sdcard/" sans quotes. You will need to do this for each file, or alternatively push a folder containing the four files. adb file transfer is very slow.
5. Boot your phone to the bootloader, and connect it to your computer. This can be achieved by holding volume down and power from an off state.
Note: If your device is still bootlooping you won't be able to get to the bootloader. Hold volume up and power until the device shuts off to get out of the bootloop temporarily, then boot to bootloader.
6. In a command window, "fastboot boot twrp.img"
7. Connect your flash drive to your phone if you chose that option, or push the files through adb if you chose that option
8. Flash TWRP zip, ROM and vendor image. STAY IN TWRP
9. Return to TWRP's home screen > advanced > file manager. Scroll down until you see 'fstab.marlin'(in the root '/' directory). Tap on 'fstab.marlin' and delete it. Skipping this step means SuperSU won't install.
10. Flash SuperSU zip, reboot to system and you're done.
SDK
TonikJDK said:
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
Click to expand...
Click to collapse
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.
bdsuser said:
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.
Click to expand...
Click to collapse
The link to the proper adb and fastboot are in the post i pointed you to.
Help with root and TWRP
TonikJDK said:
The link to the proper adb and fastboot are in the post i pointed you to.
Click to expand...
Click to collapse
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?
bdsuser said:
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?
Click to expand...
Click to collapse
I dont do it that way on this phone. TWRP and SU are modifying the same parts of the phone, and there are cases where it could conflict. Rare, not a big deal, but since i don't need TWRP installed i don't.
To install it ypu first boot to it.
Fastboot boot twrpFilename.
Then from within TWRP you install the TWRP zip.
Make sure it is TWRP RC1
All set
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!
You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.
TonikJDK said:
You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.
Click to expand...
Click to collapse
Perfect! Thanks yet again. Have a great remainder of the day!
bdsuser said:
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!
Click to expand...
Click to collapse
Im running pure and elementalx with excellent results.
?Tapped from my pure pixelXl?
have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.
bdsuser said:
have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.
Click to expand...
Click to collapse
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.
noidea24 said:
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.
Click to expand...
Click to collapse
There is absolutely no need to delete the fstab file anymore. That only needed to be done when TWRP was still alpha 2, and almost three versions of su earlier.
ALL roms replace TWRP with stock recovery unless you are using lineage then you will get Cyanogenmod recovery, so reflashing TWRP before booting into system is a must.
If you are flashing root and or custome kernel and end up in a bootloop, flashing the stock boot.img to both slots via:
'fastboot flash --slot _a boot boot.img'
'fastboot flash --slot _b boot boot.Img'
will fix the issue and you will be able to boot up just fine. Again you will have to reboot into TWRP from the bootloader and reflash the zip. When you are done flashing the boot.img's you might as well just
'Fastboot boot TWRP-file.img'
Then install the zip!
Hi,
Googled a while and looked around in the forum but did not find anyone with the exact same issue as me so here goes.
Maybe someone could tell me where exactly I am doing wrong.
I have a LG Nexus 5X, latest Oreo 8.1 official update.
I want to install a custom kernel to improve performance and/or battery life.
Never rooted or anything like that so I googled around to know what to do.
So I unlocked the bootloader and flashed the latest TWRP custom recovery (v3.2.1-0).
The first strange thing unlike what I kept reading in tutorials and forums is that, although I did reboot directly into recovery after flashing TWRP, and completed flashing TWRP using its interface, I was never able to reboot into TWRP unless I flashed it again. As if TWRP could not avoid being overridden by the stock recovery. So to get back to TWRP I always have to:
reboot into the bootloader: adb reboot bootloader
flash TWRP: flash recovery twrp-3.2.1-0-bullhead.img
reboot bootloader: fastboot reboot
immediately start into to bootloader (power + vol down)
choose 'Recovery Mode' from there
Which seemed odd, that TWRP wouldn't 'stick', although I was not root yet.
Which gets me to the second part. All I wanted was to root my phone.
So after not finding a consistent way to do it - it seemed every website I visited gave me slightly different instructions to do so, I took the chance and did the following:
download latest SuperSU flashable zip file (v2.82) and copy it to internal storage
go through the process I describe in the list above to get into TWRP
install SuperSU zip file (via Install TWRP option, logs seemed ok, warned me it would take a while to boot again)
reboot, wait until it boots
But the phone got stuck in the boot screen - OS does not start to load - for at least half an hour.
Luckily, probably because the OS did not load, TWRP was not overridden and so I have access to it.
My main problem at this point is that, as a newbie on this, I am not sure what can I do in TWRP to try to restore the OS.
I have tried to restore a Nandroid backup I performed before all this, and also tried to Wipe Data / Cache and Dalvik.
Both did not work - OS still won't load.
What can I do at this point? Wipe System partition? Wouldn't that delete my Nandroid backup?
Maybe 'sideload' (not sure if the right term) an official google image for my Nexus?
Sorry again if questions like this can be easily found around the forum, but from the threads I checked I did not bump into the exact same scenario...
Thank you in advance
So in the meantime I have wiped system partition, no success either.
Ended up restoring my Nandroid backup and sideloading the latest OTA from Google, which successfully restored my phone.
Of course TWRP was overridden once again.
So back to the start: can anybody help me out on the best way to permanently flash TWRP and root the phone?
Thanks!
Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)
jbaumert said:
Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)
Click to expand...
Click to collapse
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?
disacrol said:
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?
Click to expand...
Click to collapse
Here's the guide stickied that should walk you through the TWRP install. https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
As for Magisk. There is a whole forum dedicated to it - https://forum.xda-developers.com/apps/magisk - Short story install the latest stable version (16.0) and call it good. I haven't had any issues with recent kernel builds including Franco, EX, etc.... One thing to keep in mind is that Magisk always gets flashed after the kernel install as it does some patching of the boot.img as part of its process.
jbaumert said:
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
Click to expand...
Click to collapse
Yes, flash, not boot.
Thanks a bunch for all your help. I didn't meant to be lazy to start by reading sticked topics, but it's so much new information for a newbie that I didn't exactly know where to start. Thanks again for sharing the links.
I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Click to expand...
Click to collapse
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..
disacrol said:
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..
Click to expand...
Click to collapse
What version of super su are you using? Use 2.82 SR 3 or 5
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
What version of super su are you using? Use 2.82 SR 3 or 5
Click to expand...
Click to collapse
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.
disacrol said:
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.
Click to expand...
Click to collapse
3 or 5 work on Oreo. I'm not sure about stable. I don't use it.
Sent from my [device_name] using XDA-Developers Legacy app
SR5 worked like a charm. I just wish there was a compatibility matrix somewhere in their website to avoid so many forum threads and misinformation on the subject and avoid all the hustle. The whole process is dead simple but it took me days and tailored help from you guys to figure this one out.
Thanks again to all of you for your assistance.
i had that issue with a nex 6 and flashing supersu fixed it. when i got a 6p i tried the same and get stuck on the boot logo and had to sideload factory firmware to get back to go. i have a 5x on the way maybe i will try magisk.
so after i flash twrp reboot the bootloader, i open twrp and flash supersu sr5 and all is well, no more disappearing act for twrp and no more stuck on the "google"?
This has happened to me before, I think -- I restarted, and my phone unrooted itself. What's that about, again? How do I stop it?
My guess is when you flashed the magisk_patched boot.img you only used fastboot boot instead of fastboot flash so on reboot it reverted to stock.
ctfrommn said:
My guess is when you flashed the magisk_patched boot.img you only used fastboot boot instead of fastboot flash so on reboot it reverted to stock.
Click to expand...
Click to collapse
I feel like I did fastboot flash, but I'll try to fix that. I've done a lot of setup since then, though... Could I just go back into my bootloader and flash the patched boot.img, or do I need to do something fancy now? Do I need to clear my phone to reroot it?
DanHakimi said:
I feel like I did fastboot flash, but I'll try to fix that. I've done a lot of setup since then, though... Could I just go back into my bootloader and flash the patched boot.img, or do I need to do something fancy now? Do I need to clear my phone to reroot it?
Click to expand...
Click to collapse
You can just go flash the patched boot again.
ctfrommn said:
You can just go flash the patched boot again.
Click to expand...
Click to collapse
Welp... I did that, and now my phone is stuck booting, it won't go past the G screen.
I haven't tried this, but you can probably fastboot flash your stock boot.img file from wherever your stock img is stored on your PC/laptop. I'm not sure if you need to extract it first though, but still that's one possible option. You can also fastboot boot twrp-x.x.x.-x.img(boot command, not flash) to temporarily boot into twrp and flash a custom kernel...I think Dank kernel is still a 9.0 kernel that may work for you.
& All this is assuming the boot.img got f'd; if it's system that's f'd somehow - you may need to start fresh. If you need to start fresh and want to keep your data, alter the flash-all script file - eliminate " -w " and your data will not be wiped.
*Also, in the future for root, you can download the magisk zip file, temporarily fastboot boot twrp, and flash the zip file to gain root; imo it's an easier option than patching the boot.img through magisk, etc. It's just a temporary boot of twrp so it will not be stored on your device.
Bob nesta said:
I haven't tried this, but you can probably fastboot flash your stock boot.img file from wherever your stock img is stored on your PC/laptop. I'm not sure if you need to extract it first though, but still that's one possible option. You can also fastboot boot twrp-x.x.x.-x.img(boot command, not flash) to temporarily boot into twrp and flash a custom kernel...I think Dank kernel is still a 9.0 kernel that may work for you.
& All this is assuming the boot.img got f'd; if it's system that's f'd somehow - you may need to start fresh. If you need to start fresh and want to keep your data, alter the flash-all script file - eliminate " -w " and your data will not be wiped.
*Also, in the future for root, you can download the magisk zip file, temporarily fastboot boot twrp, and flash the zip file to gain root; imo it's an easier option than patching the boot.img through magisk, etc. It's just a temporary boot of twrp so it will not be stored on your device.
Click to expand...
Click to collapse
Aaaaaand... nope, it's still in a bootloop. I guess I'll try it with the wipe. Edit: yeah, the wipe worked, now let me root it again...
I don't need a custom kernel, I'm not flashing to min/max my battery life or anything, I just want to get this thing working, rooted, and, if possible, with the clock on the right side of the notification bar.
DanHakimi said:
Aaaaaand... nope, it's still in a bootloop. I guess I'll try it with the wipe. Edit: yeah, the wipe worked, now let me root it again...
I don't need a custom kernel, I'm not flashing to min/max my battery life or anything, I just want to get this thing working, rooted, and, if possible, with the clock on the right side of the notification bar.
Click to expand...
Click to collapse
I only mentioned flashing a custom kernel since your patched boot.img messed you up so I threw that out there because sometimes it's a way to get out of a boot problem. (I'm not trying to plug other peoples' kernels/work or anything like that.)
But you got things up and running, so...carry on