Related
So im pretty new to this but here is what im trying to do. I just got an asus nexus 7 2013 and i want to install it in the dash of my car. I plan to use a usb dac (dragonfly) and i want to be able to hook a hard drive up to it for media storage. So far ive rooted and backed up the tablet using the wugfresh NRT, and i want to try out this kernel http://forum.xda-developers.com/show....php?t=2389022 because it has usb charging and it can charge the device at the same time. But i have no idea how to install something like this and i couldnt find anything after i searched. Thanx.
That link isn't taking me anywhere...
Basically you just download the .zip file, copy it to your internal memory/sdcard (which is /sdcard), boot into your custom recovery, I would recommend wiping /cache and Dalvik (but some people say you don't have to), then selecting "Install" then browsing your /sdcard to find the zip, then Install...Reboot.
Alrite so i have no idea what you just told me too do, i tried to boot it up by holding the VOL down and power buttons. I went to custom recovery, but from there, i cant understand what commands im supposed to give the tablet that would enable it to bootup on the new rom. but i figured out that i can install a custom recovery with my wugfresh nexus root tool kit. But my problem is when i try to select the rom file that i want to use, It wont show an actual img file. When i go to the page to download the rom, all i get is an automatic download for a zip file. The NRT wont flash the zip file, and when i extract it, theres no image for the NRT to target. So how do i get this rom to be an IMG file or is there another way to do this. thanx.
You flash zips from the custom recovery on the phone. You flash imgs from fastboot on the computer.
If you have a custom recovery installed, you don't need a computer at all to flash a kernel (or a ROM). Just the custom recovery on your phone. Select the kernel zip and install it.
Oh boy. You sure you have a custom recovery?
My advice.
Install GooManager from Play Store.
Open and click on the three dots.
Install OpenRecovery Script.
Click the option for Reboot Recovery.
Install.
Navigate to the zip file.
Swipe to install.
You may want to wipe or whatever but up to you.
I mean this is the basis for everything and you don't know. I'd suggest doing more research before blasting away on the tablet and asking these types of questions. This is all very basic.
Good luck.
Sent from my Nexus 7 using xda app-developers app
i went with goo.im and installed the elemental IX kernel. the only thing wierd that happened was that it wouldnt let me install it if i checked the verify zip box, so i just didnt verify it. everything else looks like it worked fine. thanx.
I want to be able to flash my stock recovery when I no longer want TWRP or CWM. How would I go about doing this?
tcmoffitt said:
I want to be able to flash my stock recovery when I no longer want TWRP or CWM. How would I go about doing this?
Click to expand...
Click to collapse
Hello,
Thanks for using XDA Assist.
What device do you have?
___
v7
XDA Assist
v7 said:
Hello,
Thanks for using XDA Assist.
What device do you have?
___
v7
XDA Assist
Click to expand...
Click to collapse
HTC One m8 Tmobile
Thanks for the help guys I really appreciate it. This forum is just so helpful............. ---____---
Which T-Mobile ?
If it is T-Mob US .. there's a dedicated section for T-Mob US and you can find any info there.
tcmoffitt said:
Thanks for the help guys I really appreciate it. This forum is just so helpful............. ---____---
Click to expand...
Click to collapse
This is not possible to backup your stock recovery. When you need that you can download it simply (base on your phone's build number). Also you can extract stock recovery frome your ota zip update(the file with img format inside of firmware folder)
Arsinn said:
This is not possible to backup your stock recovery.
Click to expand...
Click to collapse
Actually, the following usually works:
This has to be done before flashing custom recovery. Unlock bootloader, then fastboot boot recovery.img
With "recovery.img" being a TWRP file located in your fasboot folder. This will boot into TWRP without actually flashing it. From there, you can pick recovery in the backup options, to backup stock recovery.
But yes, I agree that stock recovery images are pretty easy to obtain from these forums, or extracting from a OTA or ROM.zip.
redpoint73 said:
Actually, the following usually works:
This has to be done before flashing custom recovery. Unlock bootloader, then fastboot boot recovery.img
With "recovery.img" being a TWRP file located in your fasboot folder. This will boot into TWRP without actually flashing it. From there, you can pick recovery in the backup options, to backup stock recovery.
But yes, I agree that stock recovery images are pretty easy to obtain from these forums, or extracting from a OTA or ROM.zip.
Click to expand...
Click to collapse
Hi, redpoint73...
Maybe I'm missing something here, but I'm not seeing an option to backup the Recovery in TWRP 2.8.7.0... Just Boot, Cache, System, Data and Android Secure are available (see attached screenshot). I remote booted TWRP from my laptop, as I did when I rooted Marshmallow around a fortnight ago, in order to keep the stock recovery intact.
It would certainly be useful to be able to backup the stock recovery via TWRP... I just haven't found a way of accomplishing it .
-----
But a possible option to backup the stock recovery would be to use the Flashify app...
Remote boot TWRP from your PC, acquire root, and then run Flashify...
Flashify PlayStore link...
https://play.google.com/store/apps/details?id=com.cgollner.flashify
XDA discussion thread...
http://forum.xda-developers.com/showthread.php?t=2349847
This app uses <dd=if/of> commands to backup and potentially restore the boot and/or recovery images.
Although it does require root to work.
I've used Flashify on my Nexus 7 and Nexus 9 in the past, but never on my M8, except to backup... never to restore, so I cannot personally vouch for it's safety on the M8.
-----
What I'm unsure of about Flashify...
@redpoint73, @ckpv5, maybe you guys could shed some light on this...
Would such a <dd=if/of> created backup of stock recovery be flashable via fastboot?
And would it be safe to do so?
I know that TWRP uses <dd=if/of> commands, having looked through TWRPs logs... but I'm not quite sure how fastboot works when it comes to flashing stuff, and I'm very wary about doing it myself or recommending it for others.
Normally, you'd just use the Flashify app to restore any recovery/boot.img backups you've previously made...
But Flashify requires root to work, and with an unrooted system, this is isn't viable. So could one use fastboot in the normal way to flash such a previously made backup of the stock recovery?
-----
Anyhow, it's not critical at the moment for me, because I've not flashed TWRP to my M8, my stock recovery remains intact.
-----
I would recommend anybody reading this seeking to root their Marshmallow M8 to just remote boot TWRP from their PC with fastboot boot twrp.img (ie., don't actually flash it), perform an unrooted Nandroid backup first...
...and then flash Chainfire in the usual way.
This leaves the stock recovery intact, which will be required for future OTAs.
And there still might be some...
My Nexus 9 receives monthly security patches from Google (probably after the StageFright debacle of last year), and it may well be that the M8 will also continue to receive security patches, despite it being nearly two years old.
So you need to be ready... with an unrooted/untouched Nandroid of your own creation and the stock recovery.
I know that Chainfires systemless root method is supposed to address this issue, but if you're going to mess with system, you should have a Nandroid backup anyway...
...just in case.
Rgrds,
Ged.
Funny, I use the fastboot boot option to boot into TWRP saving my original recovery.
Hello guys, i have a problem with my nexus 5X: the type-c port doesn't work anymore for pc transfers (i tried with 3 different cables and 2 PCs), i guess that only the data rail is gone because the charging still works.
My problem is that i don't have the stock rom and i need it to send it back for warranty so i'd like to ask if someone can give me a link to flash the stock rom (and recovery!!) to flash everything through twrp and if it is possible.
Thanks, Luca
harkan91 said:
Hello guys, i have a problem with my nexus 5X: the type-c port doesn't work anymore for pc transfers (i tried with 3 different cables and 2 PCs), i guess that only the data rail is gone because the charging still works.
My problem is that i don't have the stock rom and i need it to send it back for warranty so i'd like to ask if someone can give me a link to flash the stock rom (and recovery!!) to flash everything through twrp and if it is possible.
Thanks, Luca
Click to expand...
Click to collapse
What you're asking for only exists in one place.
https://developers.google.com/android/images
Your main option is to download the latest factory image. Unzip the archive so that you have the system, boot, and vendor images available. Boot into TWRP 3.0+ and do a factory reset then select Install/Install image to flash those three images individually. Bootloader and radio cannot be installed in this manner.
Your alternative is to use the Google stock Full OTA images:
https://developers.google.com/android/ota
Then use Flashfire to install this image:
https://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
What you're asking for only exists in one place.
https://developers.google.com/android/images
Your main option is to download the latest factory image. Unzip the archive so that you have the system, boot, and vendor images available. Boot into TWRP 3.0+ and do a factory reset then select Install/Install image to flash those three images individually. Bootloader and radio cannot be installed in this manner.
Your alternative is to use the Google stock Full OTA images:
https://developers.google.com/android/ota
Then use Flashfire to install this image:
https://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
thanks for you comment: i didn't know that i can flash stock rom too through twrp recovery
if i install flashfire i would be able to flash the recovery?
harkan91 said:
thanks for you comment: i didn't know that i can flash stock rom too through twrp recovery
if i install flashfire i would be able to flash the recovery?
Click to expand...
Click to collapse
Yes it can. Btw, stock recovery will replace TWRP on reboot if you flash Nougat images for boot, system, and vendor in TWRP.
Sent from my Nexus 5X using Tapatalk
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!
Hello everyone,
Since I'm facing difficulties connecting my Nexus 5X to my PC (believe me, I have tried nearly everything), I was wondering if it is possible to flash Magisk to my phone without the use of a PC. The bootloader is still unlocked because i've rooted my phone previously (when it still could connect to my PC). All the possibilities I ran into require either root or a PC.
I hope one of you guys knows a way how to handle this without losing all my data.
Thanks in advance!
Assuming you don't have a custom recovery installed either?? What's the "difficulty with trying to hook to a PC?
No, I don't have a custom recovery installed. There are more people facing this problem: https://forum.xda-developers.com/nexus-5x/help/unlock-bootloader-fastboot-detecting-t3236946/page4. Solution is not working for me for some reason.
To install magisk you need a custom recovery. And to install a custom recovery you need a pc.
Sent from my [device_name] using XDA-Developers Legacy app
I was afraid of that. Maybe i'll go with a factory reset then. Thanks tot the help anyways.
jd1639 said:
To install magisk you need a custom recovery. And to install a custom recovery you need a pc.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Not true, you just need a working adb connection with a computer. You can flash patched boot image with fastboot then
_Hitman47 said:
Not true, you just need a working adb connection with a computer. You can flash patched boot image with fastboot then
Click to expand...
Click to collapse
So..... The bottom line is..... You still need a PC.
_Hitman47 said:
Not true, you just need a working adb connection with a computer. You can flash patched boot image with fastboot then
Click to expand...
Click to collapse
You're right. You can flash a boot image with fastboot. Is there a boot image that has magisk as party of it?
Well, I have installed Magisk Manager, and it gives me the option to patch a boot image-file. When I choose this option it askes me to select te original boot image-dump (.img or .img.tar). Since I'm no expert and I don't know where to find this and what this does, I'm afraid of losing my data or bricking my phone.
bluesh4rk said:
Well, I have installed Magisk Manager, and it gives me the option to patch a boot image-file. When I choose this option it askes me to select te original boot image-dump (.img or .img.tar). Since I'm no expert and I don't know where to find this and what this does, I'm afraid of losing my data or bricking my phone.
Click to expand...
Click to collapse
You would use the boot.img from the factory image that your rom is based on. Find your device below and download the 1 GB zip. Inside this zip is another zip you'll need to open to find the boot image (boot.img). Flashing boot images doesn't wipe internal storage, but it does remove root if you had it installed.
Factory images:
https://developers.google.com/android/images?hl=en
There's not really a collection of stock boot images besides what's included in the factory image.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
You would use the boot.img from the factory image that your rom is based on. Find your device below and download the 1 GB zip. Inside this zip is another zip you'll need to open to find the boot image (boot.img). Flashing boot images doesn't wipe internal storage, but it does remove root if you had it installed.
Factory images:
https://developers.google.com/android/images?hl=en
There's not really a collection of stock boot images besides what's included in the factory image.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Instead of downloading the entire ROM, you might find what you need here: https://forum.xda-developers.com/nexus-5x/general/modified-boot-imgs-android-n-t3495169
bluesh4rk said:
Hello everyone,
Since I'm facing difficulties connecting my Nexus 5X to my PC (believe me, I have tried nearly everything), I was wondering if it is possible to flash Magisk to my phone without the use of a PC. The bootloader is still unlocked because i've rooted my phone previously (when it still could connect to my PC). All the possibilities I ran into require either root or a PC.
I hope one of you guys knows a way how to handle this without losing all my data.
Thanks in advance!
Click to expand...
Click to collapse
Hello there ,
I have same as your issue.
My pixel 2 xl non rooted with unlocked bootloader.
So, Is it possible to flash latest OTA update directly through the phone via stock recovery?
As you aware that with the known and common pixel 2 xl issue which you can't get it connected to PC.
I'm stuck on October update and I'd be glad if someone could help me out on this matter.
Hi I'm new to rooting. I have a ZTE n9137 tempo x looking to root .I can't get this done.no recovery no boot.img no custom recovery none what so ever .the olny I keep reading is that I have to have a PC I don't like I said I'm new to root but I'm trying anything to get this done I unlocked the oem but I don't thing that it is enabled.?.?and I don't think that the phone can do this ota so now what ?? If I'm wrong plzz tell me where at I'm wrong and how to gain root thanks for all the help
Update not got root
hi everybody i wanted to root a samsung a3 2018(idk what version it is because it is still my grandma's phone) and as i know there isn't any twrp version for that phone