ive just bought the op3.
and i want to side load the latest community build 3.5.1.
installed latest androidSDK and OP3 Drivers.
when i hit the "adb devices" command in cmd prompt window
it does not show any device...
ive searched and read in a lot of threads and forums before posting here and would appreciate any help!
im running the latest oxygenOS (no Root, Bootloader still locked)
ADB + OEM unlocking is on.
PC: Windows 8.1 x64
tnx
If ADB is enabled on device, then I can only assume that it's a driver issue.
Installed drivers properly as well, tried 2 different (op) cables...
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
arikbenami said:
Installed drivers properly as well, tried 2 different (op) cables...
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Click to expand...
Click to collapse
Try connecting another device by USB and make sure your drivers are working and if then try adb wireless .(root) if it's working, then the problem might be with the port. Is USB working correctly in media mode?
Sent from my ONEPLUS A3003 using Tapatalk
Nexus5 working properly. Media working fine.
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
arikbenami said:
Nexus5 working properly. Media working fine.
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Click to expand...
Click to collapse
Does fastboot working?
Sent from my ONEPLUS A3003 using Tapatalk
When you attach USB cable does device show up at all? Can you for instance access it with a pc file explorer?
I had that issue with one of my One Plus Ones. No problem with one of them but the other one wouldn't connect with adb no matter what. Fastboot devices worked but adb devices would not. I finally used an OTG cable. Loaded files onto the computer, transferred them to a flash drive, then used the flash drive and OTG cable to install them on the phone.
One person suggested an Android app which worked sort of----once. It was so much trouble I uninstalled it.
I had other issues with the OnePlus 3. TWRP would install but not stick when I rebooted. Finally fixed that with the Tookit.
Good Luck
zulu657 said:
I had that issue with one of my One Plus Ones. No problem with one of them but the other one wouldn't connect with adb no matter what. Fastboot devices worked but adb devices would not. I finally used an OTG cable. Loaded files onto the computer, transferred them to a flash drive, then used the flash drive and OTG cable to install them on the phone.
One person suggested an Android app which worked sort of----once. It was so much trouble I uninstalled it.
I had other issues with the OnePlus 3. TWRP would install but not stick when I rebooted. Finally fixed that with the Tookit.
Good Luck
Click to expand...
Click to collapse
The USB + OTG cable is a bit to advance for my skills.
But thank you for the explanation. Much appreciated.
Does anyone else have a different solution?
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
arikbenami said:
The USB + OTG cable is a bit to advance for my skills.
But thank you for the explanation. Much appreciated.
Does anyone else have a different solution?
Click to expand...
Click to collapse
Did you open cmd in the adb folder ?
Sent from my OnePlus3 using XDA Labs
zulu657 said:
I had other issues with the OnePlus 3. TWRP would install but not stick when I rebooted.
Click to expand...
Click to collapse
That's to be expected. If you install a custom recovery then reboot directly to system, the custom recovery will be overwritten by the stock one. In order to prevent this, you need to reboot into recovery right after you install it. It discusses this in the installation instructions on the official TWRP webpage for the One Plus 3:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
fadedout said:
That's to be expected. If you install a custom recovery then reboot directly to system, the custom recovery will be overwritten by the stock one. In order to prevent this, you need to reboot into recovery right after you install it. It discusses this in the installation instructions on the official TWRP webpage for the One Plus 3:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
Thank you. That's the part I didn't know. After several frustrating tries, I was finally able to fix it with the Toolkit. I generally don't use those but in this case it worked well. The toolkit had an earlier version of TWRP, so I used it to install that one. Then I booted into TWRP and replaced the earlier version with the latest one. After a reboot, no more problems.
During all of this I asked for help several times in appropriate threads with no responses......
Related
I'm new to the forums and I've been searching and reading all over for help. This was my first time rooting. I was trying to flash a rom in TWRP and somehow erased everything, no OS or anything. Now when I boot up it only says google. It won't load past that. I can get into the fastboot screen but the adb options don't work. And now since trying two different tool kits to flash to stock image, I can't get on TWRP anymore. Any help would be great thanks. I'm not even sure what I did but I can try to add more information. Thanks
You can boot in fastboot and flash it back to stock.
I see Google hasn't posted the factory images out there yet, your tablet is fixable, but you need the image. Maybe someone else can chime in with a image I haven't found yet. BTW, you can fastboot flash the recovery if its a .IMG file to get that back.
Note: you'll need the android SDK because you'll need the fastboot drivers and the fastboot.exe program to flash back.
Sent from my Nexus 7 FHD using Tapatalk 2
trssho91 said:
Can you boot into fastboot mode by holding all three buttons for 5 seconds with the device off? It doesn't need a os or recovery just as long as you didn't kill the bootloader. Once in fastboot just flash it back to stock.
Download your image here: https://developers.google.com/android/nexus/images
Don't freak out yet, its hard to brick a nexus device
Edit, I just saw you said you can get fastboot. Use the link I posted to download your image, if you need the android SDK because you'll need the fastboot drivers and the fastboot.exe program to flash back.
Sent from my Nexus 7 FHD using Tapatalk 2
Click to expand...
Click to collapse
Obviously ADB would not work in fastboot. Erasing your ROM and recovery is no where near being bricked. You get into bootloader by holding Power + Volume down. Google has not released the official image package yet so flash the stock images from these -
http://forum.xda-developers.com/showthread.php?t=2381438
http://forum.xda-developers.com/showthread.php?t=2381582
I'll try this all out in the morning. It's getting late here. Thank you and I'll be back to give you all an update!
You could even skip flashing the stock recovery and reflash TWRP. Rename it "recovery.img" put it in platform-tools... Then:
fastboot flash recovery recovery.img
TWRP should be flashed. Install a stock deodex or odex ROM and wipe data before install. Should be good.
But, everyone else's solutions will also work too (ie you are NOT bricked )
Sent from my Nexus 4 using Tapatalk 4 Beta
I need help also im trying to restore with the images but its hanging when i get to the flash system part it just sits there and i dont have a system to bootup to if i wanted to what can i do ??
Okay i guess i just had to wait a lil bit longer its finally flashing the system
Sent from my Nexus 4 using Tapatalk 4 Beta
I think I'm having some problems trying to download things in the correct folders, seeing as I don't understand most of the lingo. I used a all in one tool to unlock the bootloader and root but when I tried putting things in the folder it wouldn't load properly. I deleted everything off of my pc and I'm going to redownload everything and try again.
Tried http://forum.xda-developers.com/showthread.php?t=2381582 early this morning and it wouldn't load properly. I ran it and it said ?????? fastboot and then said some files were missing. Let me get back at it though.
You're just gonna have to own up and install the SDK. It only takes a few commands once it's downloaded.
http://developer.android.com/sdk/index.html
Sent from my Nexus 4 using Tapatalk 4 Beta
Installing the SDK isn't necessary.
All you need is fastboot.exe and the ADB files.
I really wish people would stop telling others to install the entire Android SDK, because it really is a waste of time.
Geodude074 said:
Installing the SDK isn't necessary.
All you need is fastboot.exe and the ADB files.
I really wish people would stop telling others to install the entire Android SDK, because it really is a waste of time.
Click to expand...
Click to collapse
Yea thats correct zedomax made a zip on here that only has the files u need
Sent from my Nexus 7 using Tapatalk 4 Beta
Geodude074 said:
Installing the SDK isn't necessary.
All you need is fastboot.exe and the ADB files.
I really wish people would stop telling others to install the entire Android SDK, because it really is a waste of time.
Click to expand...
Click to collapse
+1 I didn't know somebody compiled that for the new N7. I was mostly trying to get this fellow to shy away from the toolkits - not that they're bad... But when they mess up, it's a headache to recover.
Sent from my Nexus 4 using Tapatalk 4 Beta
When I post on here I think its better to assume I'm posting to a noob rather assuming they know something they don't and making their situation more stressful. The SDK is a blanket install and you know everything is there. For someone inexperienced its better than: get this driver, and this one, and these files...move them here..you get the idea.
Sent from my SAMSUNG SGH-I747 running CyanogenMod.
Anisak said:
Tried http://forum.xda-developers.com/showthread.php?t=2381582 early this morning and it wouldn't load properly. I ran it and it said ?????? fastboot and then said some files were missing. Let me get back at it though.
Click to expand...
Click to collapse
The guide on that thread should work really well, but I will just point out that for me, ADB wasn't working (yet) while I was still trying to flash TWRP on it, so the 'ADB reboot bootloader' line in the "Recovery_Nexus7.bat" was pointless. In my case, I go to the bootloader/fastboot mode by holding the power button + volume down.
Once in fastboot/bootloader mode, ensure that fastboot can see your N7 2013 by typing 'fastboot devices'. If you see your device there, you are good to proceed with flashing all the files that are in that zip file. It even roots your device. Good luck and let me know if you need any further help.
zeppelin101 said:
The guide on that thread should work really well, but I will just point out that for me, ADB wasn't working (yet) while I was still trying to flash TWRP on it, so the 'ADB reboot bootloader' line in the "Recovery_Nexus7.bat" was pointless. In my case, I go to the bootloader/fastboot mode by holding the power button + volume down.
Once in fastboot/bootloader mode, ensure that fastboot can see your N7 2013 by typing 'fastboot devices'. If you see your device there, you are good to proceed with flashing all the files that are in that zip file. It even roots your device. Good luck and let me know if you need any further help.
Click to expand...
Click to collapse
Oh disregard my last comment. I got it to work! Thank you everyone for the help!
Anisak said:
When I type fastboot devices nothing comes up. And I can't seem to unlock or lock it now. (Was testing that command)
Click to expand...
Click to collapse
Are you logging in from your administrator account and is it windows 8 by any chance ?
Well, Rule is log into from your administrator account and windows 8 will need manual drivers installation for your Nexus 7 (2013). Try downloading USB drivers from SDK.
I am also attaching fastboot drivers which I hope will work
Good luck
Hnk1 said:
Are you logging in from your administrator account and is it windows 8 by any chance ?
Well, Rule is log into from your administrator account and windows 8 will need manual drivers installation for your Nexus 7 (2013). Try downloading USB drivers from SDK.
Good luck
Click to expand...
Click to collapse
I'm on windows 7 but I did read about something about being on admin and that did the trick. Before it wasn't letting me run anything and not warning me to do so either. But I got it! Thanks to everyone for the help and advice. :victory:
Hi guys. I recently flashed the Glitched Kernel (http://forum.xda-developers.com/showthread.php?t=2449919) to my Nexus, but I accidently downloaded the wrong one. Not knowing this, I flashed it via TWRP and now my device crashes completely (my computer won't even recognize it) on the lock screen. I can still boot into the bootloader, TWRP, and MultiROM easily. I just can't boot up Cyanogenmod (Only rom I have on the device as of now). I really don't know what to do. I've tried connecting via USB in the bootloader, my computer won't even pick up the device. I've also tried adb sideload a new rom and a new kernel, but I get the error 'protocol fault (no status)' which is weird, because ADB recognizes my device (I typed the 'adb devices' command in CMD) How can I flash the stock kernel back onto it?
Thanks in advance,
~NascarBoy119
Just clean flash cyanogenmod again if you have the Rom as .zip on your device. If not use ADB to get a Rom for flashing on your device.
Restore your backup (nandroid).
detoxN said:
Just clean flash cyanogenmod again if you have the Rom as .zip on your device. If not use ADB to get a Rom for flashing on your device.
Click to expand...
Click to collapse
I can't download anything to my device. ADB sideload won't work also (I get the error 'protocol fault [no status]), as I stated above.
Also @wantabe
Shortly before this I ran Clean Master on my device. Turned out it deleted my backups... After that, all this drama happened. Probably kinda my fault as I used the TWRP backup feature instead of NanDriod.
NascarBoy119 said:
I can't download anything to my device. ADB sideload won't work also (I get the error 'protocol fault [no status]), as I stated above.
Also @wantabe
Shortly before this I ran Clean Master on my device. Turned out it deleted my backups... After that, all this drama happened. Probably kinda my fault as I used the TWRP backup feature instead of NanDriod.
Click to expand...
Click to collapse
adb is your friend. There is plenty of opportunities. You could download a ROM on your computer and sideload or push it in adb. You could also download stock images and fastboot it in the bootloader. Simple...
Sent from my Nexus 7 using Tapatalk
NascarBoy119;49329133]I can't download anything to my device. ADB sideload won't work also (I get the error 'protocol fault [no status]).
Click to expand...
Click to collapse
nikr123 said:
adb is your friend. There is plenty of opportunities. You could download a ROM on your computer and sideload or push it in adb. You could also download stock images and fastboot it in the bootloader. Simple...
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
As you see the text that I put in bold, ADB sideload/pushing gives me an error. I might try the fastboot thing though but then I'll lose all my data, right?
NascarBoy119 said:
As you see the text what I put in bold, ADB sideload/pushing gives me an error. I might try the fastboot thing though but then I'll lose all my data, right?
Click to expand...
Click to collapse
what android version are your running?
anyways grab the gltiched kernel for your device this time.
then put your device i to recovery: up/down volume plus power when device is off
once in recovery type thus from your computer.
fastboot flash boot boot.img
you will need to extract the image from the glitched-kernel.zip
no this will not wipe your data. it is the manual way of flashing a kernel.
hope that helps.
NascarBoy119 said:
As you see the text what I put in bold, ADB sideload/pushing gives me an error. I might try the fastboot thing though but then I'll lose all my data, right?
Click to expand...
Click to collapse
Fastboot is your friend in this case, as long as you didn't relock your bootloader you can flash without losing your data.
userdelroot said:
no this will not wipe your data. it is the manual way of flashing a kernel.
hope that helps.
Click to expand...
Click to collapse
^this
Not using cleanmaster to delete your backups was a lesson you learned the hard way, but it is not unrecoverable and you can chalk it up as a learning experience.
Let us know how it worked out, everything will be fine as long as you take your time and relax. This is something that happens to most people sooner or later and is a great confidence builder (once you work through it).
To avoid this I keep all my backups, zips and other flashaholic stuff on a USB drive mounted using an USB OTG cable. You can mount it and use it in recovery.
megabatteryman said:
To avoid this I keep all my backups, zips and other flashaholic stuff on a USB drive mounted using an USB OTG cable. You can mount it and use it in recovery.
Click to expand...
Click to collapse
This may very well be the top reason to buy an OTG cable and/or OTG Micro SD reader / hub device
Sent from my Nexus 7 using XDA Premium HD app
userdelroot said:
what android version are your running?
anyways grab the gltiched kernel for your device this time.
then put your device i to recovery: up/down volume plus power when device is off
once in recovery type thus from your computer.
fastboot flash boot boot.img
you will need to extract the image from the glitched-kernel.zip
no this will not wipe your data. it is the manual way of flashing a kernel.
hope that helps.
Click to expand...
Click to collapse
oldsoldier2003 said:
Fastboot is your friend in this case, as long as you didn't relock your bootloader you can flash without losing your data.
Not using cleanmaster to delete your backups was a lesson you learned the hard way, but it is not unrecoverable and you can chalk it up as a learning experience.
Let us know how it worked out, everything will be fine as long as you take your time and relax. This is something that happens to most people sooner or later and is a great confidence builder (once you work through it).
Click to expand...
Click to collapse
I did what you guys said and it work flawlessly. Thank you so much! I was worried I permanently bricked my device. I though about buying an OTG cable, but now I think I'm buying it for sure. I'll try to store some backups on it too.
Awesome, glad we could help
I had some problems with sound and couldn't get anything to fix it. So i rebooted the bootloader and was going to hard reset the device. But i accidently hit the wrong one and it deleted my OS. I don't know how to put android back on and my computer won't detect my device. My bootloader is unlocked and i have Team Win Recovery. What should i do?!
GabuscusMason said:
I had some problems with sound and couldn't get anything to fix it. So i rebooted the bootloader and was going to hard reset the device. But i accidently hit the wrong one and it deleted my OS. I don't know how to put android back on and my computer won't detect my device. My bootloader is unlocked and i have Team Win Recovery. What should i do?!
Click to expand...
Click to collapse
You will need to use the ADB sideload feature of TWRP to upload a rom to install. Research ADB on how to use it as well as the sideload feature of TWRP. You will need to connect the tablet to your PC for this,.
What he said ^^
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
NRT has and does everything you need:
http://forum.xda-developers.com/showthread.php?t=2389107
As long as you can get the ADB drivers installed on your PC, you can click Advanced Utilities "Launch," then "Flash Zips" and select a rom zip on your desktop to flash to the tablet.
And as for adb drivers, here is a link to a post by Koush with a driver install that should work without any issues.
https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
DaveRichardson said:
NRT has and does everything you need:
http://forum.xda-developers.com/showthread.php?t=2389107
As long as you can get the ADB drivers installed on your PC, you can click Advanced Utilities "Launch," then "Flash Zips" and select a rom zip on your desktop to flash to the tablet.
Click to expand...
Click to collapse
I've done what the OP has done, and if I recall, getting the device into download mode will allow Wug's Toolbox to pick it up from there. I reinstalled the OEM rom, rerooted and reinstalled TWRP. You can download the OEM rom from the toolbox.
I wiped the internal storage on my phone by mistake and now my phone has no OS or ROM to flash it back on. I tried to sideload with TWRP but the feature wouldn't start. I flashed the stock recovery and tried to sideload it there but I get an "error: protocol fault (no status)"... I tried to mount storage on TWRP but that feature didn't seem to work on it either. It's a good thing that I still have my OnePlus One to use, but I would appreciate your help!!
Sent from my A0001 using Tapatalk
I had the same issue the first time I tried to add side load the stock rom, I tried it again and it worked. my suggestion is to try the side load again. Make sure your using the full rom zip.
k.s.deviate said:
I had the same issue the first time I tried to add side load the stock rom, I tried it again and it worked. my suggestion is to try the side load again. Make sure your using the full rom zip.
Click to expand...
Click to collapse
I tried like a thousand times on both stock and TWRP to no avail. When I reflashed TWRP and tried to sideload one last time it told me that I needed ADB version 1.0.32 which is what I should have because I installed the "15 seconds ADB Installer v1.4.3" from the stickied guide here on the OP3 forums... Anyway, I got access to the TWRP folder and the internal storage by just being in the TWRP recovery, not sure if it was always like that, but I just dragged and dropped the ROM and other flashables onto the phone... lol Maybe I was freaking out too much to notice, but why would anyone sideload anything if you could just drag and drop stuff while in TWRP and just flash? Maybe reflashing TWRP fixed something or I was using an older beta OP3 version before, I re-downloaded everything.
Sent from my A0001 using Tapatalk
I screwed up when I tried to update to 3.2.0 OOS. I were rooted so the installtion failed and I restored a corrupt backup with TWRP that resulted in a stuck boot logo.
I did this too fix this. boot into fastboot (if you still can) then make sure its connection properly. "fastboot devices". Then in your ADB folder place a TWRP.img and type "fastboot boot twrp.img" wait like 10 seconds, it will seem like it doesn't work but if you are a functional TWRP img it should boot up just fine. Select allowed modifications and then you can also access storage. There is a post on the oneplus forums where you can download signed full zips of the ROMS. download any of them. I will past in the post if I can find it later. Not home atm. Just copy the .zip onto the phone and then do a factory reset and flash the full rom and then reboot should work just fine. You don't need too flash TWRP just boot it if you still wanna keep stock recovery.
rickyx32 said:
I wiped the internal storage on my phone by mistake and now my phone has no OS or ROM to flash it back on. I tried to sideload with TWRP but the feature wouldn't start. I flashed the stock recovery and tried to sideload it there but I get an "error: protocol fault (no status)"... I tried to mount storage on TWRP but that feature didn't seem to work on it either. It's a good thing that I still have my OnePlus One to use, but I would appreciate your help!!
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Bro don't worry.
All you gotta do is to download a stock image.
Boot into fastboot.
Then use a toolkit like this one.
http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Then use his toolkit to download and boot in twrp.
Now copy paste a full signed zip onto the phone by connecting it to your PC .
http://forum.xda-developers.com/oneplus-3/how-to/mirrors-official-oxygen-os-roms-ota-t3410870
Do a system and cache clean.
Flash the zip and make it boot before rooting it.
Done..!!
Joyo-rocker said:
Bro don't worry.
All you gotta do is to download a stock image.
Boot into fastboot.
Then use a toolkit like this one.
http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Then use his toolkit to download and boot in twrp.
Now copy paste a full signed zip onto the phone by connecting it to your PC .
http://forum.xda-developers.com/oneplus-3/how-to/mirrors-official-oxygen-os-roms-ota-t3410870
Do a system and cache clean.
Flash the zip and make it boot before rooting it.
Done..!!
Click to expand...
Click to collapse
It worked bro thanks I was having data issues too before and now it all just works.
Sent from my ONEPLUS A3000 using Tapatalk
rickyx32 said:
It worked bro thanks I was having data issues too before and now it all just works.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
No prob bro...!
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