I wiped, guess i wiped the wrong thing, now rom wont boot. i can get to recovery, twrp, but how do i now get a rom zip on to the phone since i cant boot? mount in twrp im not seeing anything on my computer. ATT X+. thanks in advance!
OK.
1) Download the quick adb push zip attached
2) Download the ALL-IN-ONE TOOLKIT from dev forum. Unzip to a location in C: drive
3) Download the stock ATT ROM from the dev forum
4) Go into TWRP recovery and go to mount. Click on "Mount USB"
5) Go into the command prompt, go to the unzipped "ALL-IN-ONE"/data directory and type "adb devices"
6) If you see your device "HT2BAW301147 recovery" good
7) if (6) doesn't show up. Go to advanced on TWRP, click on "ADB sideload". This will start the ADB on the recovery. Cancel the process.
8) on the command prompt type "adb devices", you should now see your device
9) Open the quickadbpush from (1). select the ROM from (3) and push to /sdcard/
10) Install the ROM from TWRP.
I tested all the above wrote this instructions.
Hope this helps.
Always do a nandroid
pradeepd said:
OK.
1) Download the quick adb push zip attached
2) Download the ALL-IN-ONE TOOLKIT from dev forum. Unzip to a location in C: drive
3) Download the stock ATT ROM from the dev forum
4) Go into TWRP recovery and go to mount. Click on "Mount USB"
5) Go into the command prompt, go to the unzipped "ALL-IN-ONE"/data directory and type "adb devices"
6) If you see your device "HT2BAW301147 recovery" good
7) if (6) doesn't show up. Go to advanced on TWRP, click on "ADB sideload". This will start the ADB on the recovery. Cancel the process.
8) on the command prompt type "adb devices", you should now see your device
9) Open the quickadbpush from (1). select the ROM from (3) and push to /sdcard/
10) Install the ROM from TWRP.
I tested all the above wrote this instructions.
Hope this helps.
Always do a nandroid
Click to expand...
Click to collapse
I actually started a ruu install before reading your reply. found one! lol its installing now. if that doesnt work i will for sure give this a try. Thanks so much for the detailed instructions.
Just installed the new nightly which I found out after the fact was to version 12.1 (Android 5.1) from version 12.0. This of course means installing a new version of gapps for this version. I found and downloaded the new gapps, then went to reboot into recovery (it had been working prior to this). This time when I hit the volume down button on reboot, it just continued to boot normally. I even tried booting with the up button: same result. I can't access the play store because the gapps has to be updated first. Is there another way to get into recovery mode to install gapps? or alternatively another way to install it without recovery mode?
Found part of the answer
OK, found out how to reboot recovery with ADB. For anybody else who wants to know:
Install ADB on your computer if you haven't already
Run command shell (cmd)
Go to the platform-tools directory under where you installed ADB
If you're using ADB over network, type: adb connect {ip address of tablet}
type : adb reboot recovery
And that should get you into recovery mode
Now I just gotta get the correct version of gapps, the first one I got isn't working.
My android (jellybean) tablet was turned off in middle of update and now is in boot loop. It was rooted with USB debugging on.
I MUST recover files (PDFs, .doc, .wav .JPEG, etc ) without erasing them.
Questions:
1 Do I use Odin and TWRP together?
2 Will Odin flash Samsung stock firmware erase files on device?
3. Will TWRP .img file erase everything?
4. Are these instructions correct?
I recommend you install TWRP recovery. It's the most feature-rich of all the recoveries I have used, and I will be assuming that is the recovery you use for the rest of this.
1. Boot into TWRP. (how? TWRP is an .img file )
2. Push your ADB public key to your device to force authentication.
____On Windows, do: adb push %UserProfile%\.android\ad
bkey.pub /data/misc/adb/adb_keys
3. Reboot into Android. Try adb shell and see if you get a shell prompt. If so, great! Exit it and run adb logcat, and read the huge error log for problems. If you didn't get the shell, well, then I think you're screwed, unless someone has cooked up a recovery zip for enabling adb.
What happens after ADB logcat?
Thank you..
I was trying to install TWRP on my NX529J.
"Adb reboot bootloader command" is working but when i try to install TWRP with command "Fastboot flash recovery recovery.img", it dosent work.
It shows "waiting for devices"
Tried " fastboot devices" NO device there
I tried updating all drivers installed fastboot drivers and zte drivers but still no device found.
In developer settings OEM unlock, USB debugging is on.
and adb mode is also on with *#7678#.
Plz Help.
teji007 said:
I was trying to install TWRP on my NX529J.
"Adb reboot bootloader command" is working but when i try to install TWRP with command "Fastboot flash recovery recovery.img", it dosent work.
It shows "waiting for devices"
Tried " fastboot devices" NO device there
I tried updating all drivers installed fastboot drivers and zte drivers but still no device found.
In developer settings OEM unlock, USB debugging is on.
and adb mode is also on with *#7678#.
Plz Help.
Click to expand...
Click to collapse
sudo fastboot -i 0x19d2 boot recovery.img
sudo command not recognized in windows
anish.mvj said:
sudo fastboot -i 0x19d2 boot recovery.img
Click to expand...
Click to collapse
Sir.
i tried this command also but windows didnt recognized sudo command.
Plz any other way?
teji007 said:
Sir.
i tried this command also but windows didnt recognized sudo command.
Plz any other way?
Click to expand...
Click to collapse
That is ubuntu command.
For windows run CMD as administrator and then run
fastboot -i 0x19d2 boot recovery.img
Thanks and a little more help
anish.mvj said:
That is ubuntu command.
For windows run CMD as administrator and then run
fastboot -i 0x19d2 boot recovery.img
Click to expand...
Click to collapse
Thank you very much
Sir i upgraded my nx529j to 6.0.1, is there anyway to root it or downgrade to 5.1.1?
teji007 said:
Thank you very much
Sir i upgraded my nx529j to 6.0.1, is there anyway to root it or downgrade to 5.1.1?
Click to expand...
Click to collapse
Yes its possible.
Rooting is absolutely not required.
Follow the steps below
1. Download the latest 1.40 firmware from nubia india website support page. [Direct Link]
2. Then open the zip file and extract the recovery.img to local folder. Transfer the zip as it is to SD card
3. Goto fastboot/bootloader and run following
Code:
fastboot -i 0x19d2 flash recovery recovery.img
4. Then select reboot to recovery from bootloader menu.
5. Select wipe all application
6. Then install the downloaded zip [i hope you have already know how to do that]
It will automatically reboot.
That's it you are done downgrading
Failed
anish.mvj said:
Yes its possible.
Rooting is absolutely not required.
Follow the steps below
1. Download the latest 1.40 firmware from nubia india website support page. [Direct Link]
2. Then open the zip file and extract the recovery.img to local folder. Transfer the zip as it is to SD card
3. Goto fastboot/bootloader and run following
Code:
fastboot -i 0x19d2 flash recovery recovery.img
4. Then select reboot to recovery from bootloader menu.
5. Select wipe all application
6. Then install the downloaded zip [i hope you have already know how to do that]
It will automatically reboot.
That's it you are done downgrading
Click to expand...
Click to collapse
It says wiping failed(please wipe again or do it after reboot) everytime.
and nothing is working even app wipe or data wipe, only cache wiped works and choose from phone storage is also n ot working and sd card is also being not dtetected.
even in TWRP
anish.mvj said:
Yes its possible.
Rooting is absolutely not required.
Follow the steps below
1. Download the latest 1.40 firmware from nubia india website support page. [Direct Link]
2. Then open the zip file and extract the recovery.img to local folder. Transfer the zip as it is to SD card
3. Goto fastboot/bootloader and run following
Code:
fastboot -i 0x19d2 flash recovery recovery.img
4. Then select reboot to recovery from bootloader menu.
5. Select wipe all application
6. Then install the downloaded zip [i hope you have already know how to do that]
It will automatically reboot.
That's it you are done downgrading
Click to expand...
Click to collapse
I insatlled TWRP recovery, even in that wiping is not working. is there any way to install custom roms without rooting.
i actully installed official 6.0.1 update from their official nubia site and installed it.
teji007 said:
I insatlled TWRP recovery, even in that wiping is not working. is there any way to install custom roms without rooting.
i actully installed official 6.0.1 update from their official nubia site and installed it.
Click to expand...
Click to collapse
Dude please be clear what you want to do? Stock rom or custom?
Custom
anish.mvj said:
Dude please be clear what you want to do? Stock rom or custom?
Click to expand...
Click to collapse
.
Sir i want custom Rom. and sir now i am bricked
teji007 said:
.
Sir i want custom Rom. and sir now i am bricked
Click to expand...
Click to collapse
what do you mean by your are bricked?
If you want custom rom
Goto TWRP wipe everything
if above fails then try out following
Option 1:
Goto Bootloader mode and from that menu goto emergency recovery. Try wiping from there if successful, flash a stock rom [Kitkat] and boot to system. After first boot goto settings and reset factory settings. Then goto TWRP and wipe, it will wipe for sure. then you can install any custom rom
Option 2:
Download the oldest firmware from the nubia site [1.37] and flash recovery from there [extract the recovery from zip and flash it in bootloader]. Then use
Code:
fastboot -i 0x19d2 boot TWRP.img
to boot to twrp, don't flash it. Then goto advanced and select adb sideload. swipe to start sideload. after that open the zip you downloaded and got to
Code:
/META-INF/com/google/android/
and open updater-script with any of the text file. Delete the first line and save. update the zip.
open cmd from that folder where zip is located. then type
Code:
adb sideload NX529J_Z69_EN_NSXPK1JD00K137.zip
and press enter. let it complete and then reboot. it should boot to factory firmware. Follow the same procedure to factory reset from settings menu then flash TWRP and flash custom rom
Use the above steps. If all fails then revert back.
Thanks going to try
anish.mvj said:
what do you mean by your are bricked?
If you want custom rom
Goto TWRP wipe everything
if above fails then try out following
Option 1:
Goto Bootloader mode and from that menu goto emergency recovery. Try wiping from there if successful, flash a stock rom [Kitkat] and boot to system. After first boot goto settings and reset factory settings. Then goto TWRP and wipe, it will wipe for sure. then you can install any custom rom
Option 2:
Download the oldest firmware from the nubia site [1.37] and flash recovery from there [extract the recovery from zip and flash it in bootloader]. Then use
Code:
fastboot -i 0x19d2 boot TWRP.img
to boot to twrp, don't flash it. Then goto advanced and select adb sideload. swipe to start sideload. after that open the zip you downloaded and got to
Code:
/META-INF/com/google/android/
and open updater-script with any of the text file. Delete the first line and save. update the zip.
open cmd from that folder where zip is located. then type
Code:
adb sideload NX529J_Z69_EN_NSXPK1JD00K137.zip
and press enter. let it complete and then reboot. it should boot to factory firmware. Follow the same procedure to factory reset from settings menu then flash TWRP and flash custom rom
Use the above steps. If all fails then revert back.
Click to expand...
Click to collapse
Thank you very much sir.
Can i contact you by any other means? whatsapp or any other
teji007 said:
Thank you very much sir.
Can i contact you by any other means? whatsapp or any other
Click to expand...
Click to collapse
Check your private message
adb sideload not working
anish.mvj said:
what do you mean by your are bricked?
If you want custom rom
Goto TWRP wipe everything
if above fails then try out following
Option 1:
Goto Bootloader mode and from that menu goto emergency recovery. Try wiping from there if successful, flash a stock rom [Kitkat] and boot to system. After first boot goto settings and reset factory settings. Then goto TWRP and wipe, it will wipe for sure. then you can install any custom rom
Option 2:
Download the oldest firmware from the nubia site [1.37] and flash recovery from there [extract the recovery from zip and flash it in bootloader]. Then use
Code:
fastboot -i 0x19d2 boot TWRP.img
to boot to twrp, don't flash it. Then goto advanced and select adb sideload. swipe to start sideload. after that open the zip you downloaded and got to
Code:
/META-INF/com/google/android/
and open updater-script with any of the text file. Delete the first line and save. update the zip.
open cmd from that folder where zip is located. then type
Code:
adb sideload NX529J_Z69_EN_NSXPK1JD00K137.zip
and press enter. let it complete and then reboot. it should boot to factory firmware. Follow the same procedure to factory reset from settings menu then flash TWRP and flash custom rom
Use the above steps. If all fails then revert back.
Click to expand...
Click to collapse
Sir, its been 5 mins its "starting ADB sideload feature" but nothing
adb sideload failed
anish.mvj said:
Check your private message
Click to expand...
Click to collapse
Sir ,
ADB sideload failed
teji007 said:
Sir ,
ADB sideload failed
Click to expand...
Click to collapse
Hi how did your device visible in fastboot devices?
I installed adb drivers and all but my device is not listed in fastboot devices..
It is being listed in adb devices but not on fastboot devices. Can you help me with this?
---------- Post added at 08:51 PM ---------- Previous post was at 08:50 PM ----------
teji007 said:
I was trying to install TWRP on my NX529J.
"Adb reboot bootloader command" is working but when i try to install TWRP with command "Fastboot flash recovery recovery.img", it dosent work.
It shows "waiting for devices"
Tried " fastboot devices" NO device there
I tried updating all drivers installed fastboot drivers and zte drivers but still no device found.
In developer settings OEM unlock, USB debugging is on.
and adb mode is also on with *#7678#.
Plz Help.
Click to expand...
Click to collapse
Hi how did your device visible in fastboot devices?
I installed adb drivers and all but my device is not listed in fastboot devices..
It is being listed in adb devices but not on fastboot devices. Can you help me with this?
There's a ton of information out there, but finding it can sometimes be a challenge, especially for a newbie. And then there's posts to read through, in case a process has changed and it's only talked about in a single place, buried any number of pages back. So this is my attempt to put all Pixel 3 how-to's into a single thread. Everything below is what worked for me, from start to finish, with a fresh phone directly from Google that was bootloader-locked, unrooted, and running stock Android. Comments are welcome and encouraged: if something doesn't work for you, or you have a better/quicker/more reliable way of doing something, or maybe I made a mistake...let me know!
A few things:
Everything in this guide was tested on a "regular" Pixel 3 (blueline). It should all work exactly the same on a Pixel 3 XL (crosshatch), as long as you download the appropriate files (specifically the factory/OTA images and TWRP). I'm posting this in both blueline and crosshatch forums.
This first post will have links to files and the tools you need, as well as general things (like how to enable debugging and boot into recovery). The second post has how-to's for the big stuff (flashing images, TWRP, unlocking, etc).
I'm not responsible for anything you do. Follow these guides at your own risk. Doing so may also void your warranty.
Files and URLs
Official Android files
Factory (wipes device and requires unlocked bootloader): https://developers.google.com/android/images
Full OTA (leaves data intact, can be done via ADB sideload): https://developers.google.com/android/ota
Preview/beta OTA: https://developer.android.com/preview/download-ota.html
TWRP
XDA thread: https://forum.xda-developers.com/pixel-3/development/twrp-3-2-3-0-pixel-3-t3861622
Download: https://dl.twrp.me/blueline/
Magisk
XDA thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
GitHub: https://github.com/topjohnwu/Magisk/releases
ADB and Fastboot
Google USB drivers: https://developer.android.com/studio/run/win-usb
SDK platform tools: https://developer.android.com/studio/releases/platform-tools
Download the ZIP and open (no need to extract the whole thing)
Copy the files below to their own directory (you will use this directory for all ADB/Fastboot commands):
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
General
Enable USB debugging
Download Google USB drivers (see above)
Download SDK platform tools and copy required files to their own directory (see above)
Enable USB debugging (Settings > About > tap Build 7 times > back > Developer options)
Plug phone into computer and when "Allow USB debugging" box comes up, check the box and allow (may need to have adb daemon running on the computer already, see below)
Fastboot mode (using hardware keys) aka bootloader
Power off
Hold VOL- and press/hold PWR until bootloader (fastboot) comes up
Recovery mode (using hardware keys)
Get into Fastboot mode (see above)
Use VOL buttons to find Recovery in the list, use PWR to select (should boot to broken android image)
Hold PWR and press VOL+ once to get into recovery
Useful ADB and Fastboot commands
Enable USB debugging (see above)
ADB (used while phone is "on" and booted up):
Use "adb devices" to ensure the computer is authorized
Use "adb reboot bootloader" to get into Fastboot
Fastboot mode
Use "fastboot devices" to verify computer can see your phone
Update #1: Items below marked through were removed since they don't really apply to Android 10.
Update #2: Edited to reflect changes in root with Android 11.
A quick note: everything below is assuming you're using Windows 10. When it says "Type...", this assumes you've opened a command window in the location of adb/fastboot and that all files referenced are in the same directory and (in some cases) renamed as I reference them (short names without spaces simplifies things). If you're using Powershell, you will probably need to change "adb" and "fastboot" to read ".\adb" and ".\fastboot" so Powershell will use the local files.
Unlocking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
In Developer Options, enable OEM unlocking and confirm (it may ask you to input fingerprint or PIN/pattern/password)
Boot into Fastboot mode (see above)
Type to unlock:
Code:
fastboot flashing unlock
Use VOL+ key to get the options on the screen to read "Unlock the bootloader" and use PWR button to select
Type to reboot:
Code:
fastboot reboot
Locking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Boot into Fastboot mode (see above)
IMPORTANT: restore stock recovery if you replaced it with TWRP (this should prevent the "Can't find valid operating system" issue)
Type to lock:
Code:
fastboot flashing lock
Use VOL buttons to find "Lock the bootloader" and use PWR to select
Type to reboot:
Code:
fastboot reboot
Factory reset via fastboot (can also do this without wiping data)
THIS COULD WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Download factory image ZIP and unzip all files into their own folder
Unlock bootloader (see above)
Reboot into Fastboot mode
You have 2 options:
Register the location of fastboot.exe with the PATH system variable and run "flash-all.bat"
Wipe data: just run "flash-all.bat" and call it a day
Do not wipe data: open "flash-all.bat" in a text editor (careful not to double-click and run it!), remove the "-w" from the last line to disable the wiping of data, then save, close, and run
Move the 3 files (bootloader IMG, radio IMG, image ZIP) into the ADB folder, rename for simplicity if you want, launch cmd or Powershell, and run the commands below (which come from "flash-all.bat")
Wipe data: type out commands below, but at last line, add "-w" flag: fastboot -w update image.zip
Do not wipe data: type out commands below as written (no "-w" flag)
The commands:
Code:
fastboot flash bootloader bootloader-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot flash radio radio-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot update image-blueline-XXXX.zip
Note: The last command (update image) will launch the red "fastbootd" screen, so don't worry and be patient while the command line tells you what's happening. The phone will reboot on its own into the Android system (not fastboot) afterward.
Root Android 10+ using Magisk (Canary channel)
This must be done after every update, and you cannot use the patched file from a different phone!
Unlock bootloader (see above)
Download factory image (not OTA, see link above)
Download and install Magisk Manager Canary (see link above)
In Magisk Manager settings, set Update Channel to "Canary"
Extract boot.img from image-blueline-XXXX.zip found in the factory image you downloaded
Place boot.img on your phone's internal storage
Open Magisk Manager and do:
tap "Install" button (next to "Magisk" in first block on the main screen)
"Select and Patch a File" option
Find boot.img file you just placed on your phone
tap "Let's Go"
When finished, move the newly-created magisk_patched.img file over to your computer's ADB directory
Reboot into bootloader
Type:
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Open up Magisk Manager and make sure everything's good!
Note : if you get stuck in fastboot mode or in a boot loop, flash the stock boot.img to both slots and try again
Code:
fastboot flash boot boot.img --slot all
Optional:
for adblocking, tap "Systemless hosts" in Magisk Manager, then install AdAway using F-Droid
install a performance kernel like Kirisakura for Bluecross (R)
Updating Android 10+ while rooted
You can't take an OTA while rooted, so updating Android 10+ (as in monthly updates) can be one of two ways.
Method #1 (faster, but more chance for issues)
Download OTA ZIP and move it to ADB folder (don't unzip it)
This does not require an unlocked bootloader, but does require USB debugging (see above)
Get boot.img from the factory image (see first post on where to download this) and place your ADB directory
Reboot into bootloader / fastboot and type to restore stock boot to both slots:
Code:
fastboot flash boot --slot all boot.img
fastboot reboot bootloader
[wait for reboot]
Use VOL buttons to select "Apply update from ADB"
Type (where filename is the name of the file you want to sideload):
Code:
adb sideload filename.zip
Wait for it to finish, will take you back to Recovery when it's done
Reboot using menu
Method #2 (takes longer, but best bet for minimal issues)
Follow "Factory reset via fastboot" instructions (see above, make sure you don't wipe your data!)
Take the OTA in the official way (through Android)
Follow "Root Android 10+ using Magisk Canary" instructions (see above)
Boot into TWRP (3.3.0-0 or higher)
Download TWRP IMG and place in ADB folder (rename the file to twrp.img)
If not already done, unlock the bootloader (see above)
Reboot into bootloader
Type to boot TWRP (it will restart and should boot into TWRP):
Code:
fastboot boot twrp.img
OPTIONAL: Replace recovery by installing TWRP
Your phone should automatically mount, so move twrp.img from PC to Download folder on phone's internal storage
Advanced > Install Recovery Ramdisk > choose TWRP IMG > Swipe to install
Back > Fix Recovery Bootloop > Reboot System > Do Not Install when asked if TWRP should install app
Root using Magisk (18.1 or higher)
Download Magisk ZIP and move to device
Boot into TWRP (see above)
Enter your PIN/pattern/password to decrypt (unnecessary if you are not using security on your phone)
Swipe to Allow Modifications (to system)
Install > find and select the Magisk ZIP > Slide to install
Wipe cache > Reboot system > Do Not Install when asked if TWRP should install app
Open Magisk Manager to verify latest and to install modules
"Can't find valid operating system" booting issue
Unlock your bootloader again (see above)
Follow steps for "Factory reset via fastboot" (see above) and keep the wipe flag
After it reboots, power off (press PWR and select "Power off" from menu)
Follow steps for "Locking the bootloader" (see above)
After it reboots into Fastboot mode, have it start using the PWR button
Android Recovery / "Cannot load Android system" booting issue
This can happen for a number of reasons, but the fix is the same: "Factory reset via fastboot" (see above). You probably do not need to wipe user data, so you can omit the "-w" flag.
If you still get the error message, select the "Try again" option. If it still doesn't work, try "Factory reset via fastboot" again, as well as "Try again". If it doesn't work this time, you probably have no choice but to do a factory reset (in which you will definitely lose your data).
If it happens after flashing Magisk in TWRP, though, you've got a slightly different issue and the problem will persist no matter how many times you flash the factory images and re-install Magisk. This is probably due to something leftover in the previous Magisk installation that conflicts with the new installation. There are two ways to handle this.
First and easiest: uninstall Magisk Manager app before rebooting into the bootloader and running fastboot commands. Then proceed as usual (sideload OTA or flash factory images via fastboot, boot TWRP, and flash Magisk). All guides for this are above. This method preserves any modules you have installed.
Second and more complete (if the above method still gives you trouble):
download to your phone the Magisk ZIP, Magisk Uninstaller ZIP, and Magisk APK from this XDA thread
uninstall the Magisk Manager app
reboot to bootloader
using fastboot, boot into TWRP using IMG (you don't need to replace boot with TWRP)
flash Magisk Uninstaller ZIP
wipe Dalvik
flash Magisk ZIP
wipe Dalvik
reboot system (do not install TWRP)
install Magisk Manager APK and re-install any modules
Number 3 in "Applying OTA via ADB sideload" should be flash stock boot.img I think.
wangdaning said:
Number 3 in "Applying OTA via ADB sideload" should be flash stock boot.img I think.
Click to expand...
Click to collapse
I wrote it like that because the file isn't actually called "boot.img", but rather "bootloader-blueline-blahblahblah.img" where "blahblahblah" is the release. Since it changes, I figured just calling it the "bootloader IMG" would make more sense.
rczrider said:
I wrote it like that because the file isn't actually called "boot.img", but rather "bootloader-blueline-blahblahblah.img" where "blahblahblah" is the release. Since it changes, I figured just calling it the "bootloader IMG" would make more sense.
Click to expand...
Click to collapse
Was my misunderstanding. I thought you were implying people should go back to stock recovery to flash ota. You are talking about flashing ota in twrp. You might clear that up a little bit in that section.
Great post.
Unfortunately, if you are writing a process, then writing everything out is a requirement. Especially with item numbers or using an outline format. Not everyone understands shortcuts taken or abbreviated words, unless they are spelled out in the beginning. IMO, wrote and read too many processes. Including software requirement documentation.
Hi,
thanks for the thread :good:
wangdaning said:
Number 3 in "Applying OTA via ADB sideload" should be flash stock boot.img I think.
Click to expand...
Click to collapse
Yes, I think so too.
rczrider said:
I wrote it like that because the file isn't actually called "boot.img", but rather "bootloader-blueline-blahblahblah.img" where "blahblahblah" is the release. Since it changes, I figured just calling it the "bootloader IMG" would make more sense.
Click to expand...
Click to collapse
The boot.img is into "image.zip"
Then I suggest to flash into a and b (or both)
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
or
fastboot flash boot --slot all boot.img
Edit
be careful here: Factory reset via ADB sideload (can also do this without wiping data)
bootloader is bootloader, boot is boot, bootloader.img isn't boot.img
so, maybe better to write:
fastboot flash bootloader nameofbootloader.img or if simply renamed fastboot flash bootloader bootloader.img
deleted, bug.
trouble flashing files
When I try to flash twrp.img or boot.img this is what I get back " FAILED (Write to device failed in Send Buffer() (Too many links)) fastboot: error: Command failed.
Any thoughts?
fyrmd said:
When I try to flash twrp.img or boot.img this is what I get back " FAILED (Write to device failed in Send Buffer() (Too many links)) fastboot: error: Command failed.
Any thoughts?
Click to expand...
Click to collapse
Please read the instructions carefully. You cannot flash twrp directly. "fastboot boot twrp.img" then when twrp boots you can use it or make it permanent by flashing the install zip or the internal twrp option. I go with the install zip as it seems more stable to me (placebo I suppose).
wangdaning said:
Please read the instructions carefully. You cannot flash twrp directly. "fastboot boot twrp.img" then when twrp boots you can use it or make it permanent by flashing the install zip or the internal twrp option. I go with the install zip as it seems more stable to me (placebo I suppose).
Click to expand...
Click to collapse
Thanks, but still no luck.
fyrmd said:
When I try to flash twrp.img or boot.img this is what I get back " FAILED (Write to device failed in Send Buffer() (Too many links)) fastboot: error: Command failed.
Any thoughts?
Click to expand...
Click to collapse
Turns out it was the cable, it is an expensive one from Amazon so not sure what I should be purchasing for next time.
fyrmd said:
Turns out it was the cable, it is an expensive one from Amazon so not sure what I should be purchasing for next time.
Click to expand...
Click to collapse
I always buy Anker cables and chargers. All have been good so far.
Now,my pixel 3 can not work,the bootload is locked.when I select recovery by fastboot,The phone noticed me can not find vaild operating system,the device will not start.
xiaowei666 said:
Now,my pixel 3 can not work,the bootload is locked.when I select recovery by fastboot,The phone noticed me can not find vaild operating system,the device will not start.
Click to expand...
Click to collapse
Are you able to get into recovery? If so, download the full ota to your pc and side load it with adb.
xiaowei666 said:
Now,my pixel 3 can not work,the bootload is locked.when I select recovery by fastboot,The phone noticed me can not find vaild operating system,the device will not start.
Click to expand...
Click to collapse
i same issue
rczrider said:
[*]Copy the files below to their own directory (you will use this directory for all ADB/Fastboot commands):
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
Click to expand...
Click to collapse
why not copy all files?
---------- Post added at 11:58 AM ---------- Previous post was at 11:55 AM ----------
fyrmd said:
Thanks, but still no luck.
Click to expand...
Click to collapse
boot to the twrp.img and flash the twrp.zip, unless you are on android 10 you should have no problem unless you are doing it wrong. not exactly hard to do.
How to enable oem unlock in this case?
pedro5148 said:
How to enable oem unlock in this case?
Click to expand...
Click to collapse
There are a few suggestions at https://www.theandroidsoul.com/how-to-fix-oem-unlock-greyed-out-or-oem-unlock-disabled-problem/
However, if the network carrier has locked the bootloader, you cannot unlock it. In the U.S., Verizon and AT&T phones generally cannot be unlocked due to locked bootloaders.