I accidently formatted my internal storage and system partision through TWRP recovery. Now im stuck with an unbootable Nexus 4 since there is no rom installed. How can i push a zip into my device? I can only access TWRP and Fastboot. and never really used ADB. I used a Toolkit to Root my phone (WugFresh's Toolkit) cant really use that since i cant boot my device to turn on USB Debugging. Any help?
Update: Searched several hours on xda, i cant manage to set up adb. Redownloaded Android SDK. Installed/updated adb (v). Tried multiple drivers (from official google usb drivers to univeral usb driver from Koush). Every time i open cmd and type "adb device" and long list of adb commands and other stuff appear. every time i type adb and any word infront of it, that happens. adb doesnt want to run or something. This is getting fustrating. and when i run adb.exe (from toolkit folder) it closes really quickly. only odd thing i see is under device manager my Nexus 4 is being displayed as Google Galaxy Nexus ADB Interface???
What operating system you're using?
Look here: http://forum.xda-developers.com/showthread.php?t=2010312
only this drivers worked for me
http://forum.xda-developers.com/showthread.php?t=1992345
Threadz said:
I accidently formatted my internal storage and system partision through TWRP recovery. Now im stuck with an unbootable Nexus 4 since there is no rom installed. How can i push a zip into my device? I can only access TWRP and Fastboot. and never really used ADB. I used a Toolkit to Root my phone (WugFresh's Toolkit) cant really use that since i cant boot my device to turn on USB Debugging. Any help?
Update: Searched several hours on xda, i cant manage to set up adb. Redownloaded Android SDK. Installed/updated adb (v). Tried multiple drivers (from official google usb drivers to univeral usb driver from Koush). Every time i open cmd and type "adb device" and long list of adb commands and other stuff appear. every time i type adb and any word infront of it, that happens. adb doesnt want to run or something. This is getting fustrating. and when i run adb.exe (from toolkit folder) it closes really quickly. only odd thing i see is under device manager my Nexus 4 is being displayed as Google Galaxy Nexus ADB Interface???
Click to expand...
Click to collapse
Hi the command is 'adb devices' if it's showing you the commands adb is set up correct. You don't actually need adb for this though, get your phone in fastboot mode and type 'fastboot devices' with your phone connected. If it outputs anything you're ready to flash a factory rom and fix your phone.
I'm stuck right here as far as download mode goes.
I installed TWRP on a d800 rooted with stock 4.2.2. The TWRP install went ok but it never booted afterward.
I can get into twrp, but can't sideload anything because the computer does not connect to the device, I hear the connection noise the computer makes but nothing in the device manager.
any ideas?
May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)
bender_007 said:
May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)
Click to expand...
Click to collapse
Thanks, I get
error: closed
I was wrong about my computer not seeing my device, it's in the device manager under Android and the adb drivers are installed.
I also renamed the rom to "update" to make it simpler
What's up now ?
Sorted it out or still issues there ?
I also tried the adb shell method.
I also tried this method through TWRP terminal and nada.
If I did something wrong here let me know, hopefully I can get it up and going
bender_007 said:
May I suggest you use "adb push rom.zip /sdcard/rom.zip" instead of sideload (the sideload doesn't have to be enabled)
Click to expand...
Click to collapse
This is what I get when I do the above. The CMD prompt in located in the same directory as the adb files
ADB sees my device as this #
Gabriel51 said:
This is what I get when I do the above. The CMD prompt in located in the same directory as the adb files
ADB sees my device as this #
Click to expand...
Click to collapse
ok, let's do it like this
1. copy rom to c:\rom.zip
2. while in adb folder "adb push c:\rom.zip /sdcard/rom.zip"
that should work, you don't need sideload to be enabled.
Please test and report.
bender_007 said:
ok, let's do it like this
1. copy rom to c:\rom.zip
2. while in adb folder "adb push c:\rom.zip /sdcard/rom.zip"
that should work, you don't need sideload to be enabled.
Please test and report.
Click to expand...
Click to collapse
I moved the file to the root of my C drive changed the name to "rom.zip"
Copied the command you supplied and got this result
I know my phone is connected because I can reboot it by using the command " adb reboot"
I used this;
adb push C:\Android\sdk\platform-tools\rom.zip
And it is now ready to install through TWRP!
Hold your breath.......
Edit;
Failed but at least it's in the twrp list
"unable to open zip"
I think I got it, I was able to access the firmware update screen.
Sorry fir these incomplete responses, I don't want you to keep looking for a resolve while I do this.
If your still here?
I'll be back!
Success!
After nothing would work except for loading the rom through adb I decided to wipe the whole thing.
I reloaded the rom and when selected for install it opened instead of preparing for install so I thought I would reboot and when I did I was prompted by su that my device may have lost root and gave me the option to reinstall it, I chose yes and when rebooting it hung (normal) at the LG logo, however this time the charge light was flashing! I attempted to access "download" and was successful in loading the stock rom.
In the end it looks like TWRP was the culprit, it used to be my favorite but not for this device
All is well, thanks for your help...
I would really appreciate some help on this one... I attempted to flash the updated Mahdi Rom (09/20 build) this morning. I'm using the latest Philz Recovery if that matters. I performed the normal wipe procedure and when I went to flash the rom it told me the file was invalid. I think I might have tried to use a zip that wasn't fully downloaded.
I didn't have any other recoveries on my phone (I know... not smart) so I need to figure out how to flash a new rom without using recovery. I'm not completely hopeless and I'm willing to do what it takes to get my phone back!
Any help would be great! Thanks.
Have you tried adb? Your phone will be called sideload when you command adb devices.
Sent from my LG-D800 using Tapatalk
I haven't yet been able to since I don't have access to a windows PC at the moment, just a MAC. Can it be performed there?
Rogueharvest said:
I haven't yet been able to since I don't have access to a windows PC at the moment, just a MAC. Can it be performed there?
Click to expand...
Click to collapse
You can load adb on Mac. I believe there's a zip somewhere on xda with only the three files need, or download the package from Android. Place it in whatever your username folder is too make life easier. Also add ./ (dot slash) before every command.
Here's the command order for my setup.
cd Android/platform-tools
./adb devices
./adb sideload **DRAG FILE INTO TERMINAL**
Thank you for your help. I got ADB to load on my mac but it won't accept the prompt to sideload. Am I missing something perhaps?
Update: I think I figured it out. The command prompt needed to be reinitiated.
Thanks again for you help! Moments like that are always a little scary!
Rogueharvest said:
Thank you for your help. I got ADB to load on my mac but it won't accept the prompt to sideload. Am I missing something perhaps?
Click to expand...
Click to collapse
Does it recognize sideload when you type ./adb devices? If not and you're in adb on Philz unplug/replug the charger.
So I decided to install PA 4.6 BETA4 on my Nexus 4, 4.3 JWR66Y Phone which is unlocked and rooted. I used the Nexus Root Toolkit to install the latest TWRP recovery, put the pa_mako-4.6-BETA4-20141007.zip and pa_gapps-stock-4.4.4-20141011-signed.zip onto my phone. Went into recovery to flash the two. The PA ROM went successful, tried flashing the gapps and it just says failed. I tried redoing the ROM flash then gapps again but that doesn't work.
I had the dumb idea of moving my nandroid backup to my computer and now I can't transfer it back to my phone using adb sideload. I go into ADB sideload in TWRP, and it just says no devices found when trying to transfer maually. When I try using NRToolkit, it fails as well.
Any advice? I feel like I've searched everywhere. I don't know what the next step to take is. Maybe Flash Stock + Unroot option on the NRToolkit? Have I somehow flashed incompatible zip files?
sirmot said:
So I decided to install PA 4.6 BETA4 on my Nexus 4, 4.3 JWR66Y Phone which is unlocked and rooted. I used the Nexus Root Toolkit to install the latest TWRP recovery, put the pa_mako-4.6-BETA4-20141007.zip and pa_gapps-stock-4.4.4-20141011-signed.zip onto my phone. Went into recovery to flash the two. The PA ROM went successful, tried flashing the gapps and it just says failed. I tried redoing the ROM flash then gapps again but that doesn't work.
I had the dumb idea of moving my nandroid backup to my computer and now I can't transfer it back to my phone using adb sideload. I go into ADB sideload in TWRP, and it just says no devices found when trying to transfer maually. When I try using NRToolkit, it fails as well.
Any advice? I feel like I've searched everywhere. I don't know what the next step to take is. Maybe Flash Stock + Unroot option on the NRToolkit? Have I somehow flashed incompatible zip files?
Click to expand...
Click to collapse
UPDATE: I got the gapps to install successfully. I installed Wifi File Explorer through NRToolkit in order to transfer files to my phone. And transferred the same exact file to my phone. I tried flashing the file and it worked... I'm guessing the wired transfer corrupted the file somehow. Thank you NRT for that option to install apks.
Hi,
Good to know that you managed to get it working . Could you add a [SOLVED] tag on the title of your thread?
Also, I'd like to point out that when you tried to copy the backup file via adb sideload it had a reason to not work! Adb sideload was born to flash zips which are transfered via adb to the device. Loading then as soon as they are loaded. To copy the files back to your device using adb you should have used the "adb push" command, which is like a "copy/paste" on the shell . Hope this helps in the future.
~Lord
XxLordxX said:
Hi,
Good to know that you managed to get it working . Could you add a [SOLVED] tag on the title of your thread?
Also, I'd like to point out that when you tried to copy the backup file via adb sideload it had a reason to not work! Adb sideload was born to flash zips which are transfered via adb to the device. Loading then as soon as they are loaded. To copy the files back to your device using adb you should have used the "adb push" command, which is like a "copy/paste" on the shell . Hope this helps in the future.
~Lord
Click to expand...
Click to collapse
Ah of course that makes sense. I think I tried just pushing the file when I was in the bootloader as well, but it also gave me devices not found. Not sure why, but anyways thanks for the reply. Hopefully this might help out someone.
sirmot said:
Ah of course that makes sense. I think I tried just pushing the file when I was in the bootloader as well, but it also gave me devices not found. Not sure why, but anyways thanks for the reply. Hopefully this might help out someone.
Click to expand...
Click to collapse
Hi,
In bootloader you mean fastboot right? If so, you can't use adb on this mode. To push a file via fastboot is only the stock image using "fastboot install" or "fastboot boot".
~Lord
"Dream On! Dream Until Your Dreams Come True!" - Dream On (Aerosmith)
Sent from my GT-I9505
XxLordxX said:
Hi,
In bootloader you mean fastboot right? If so, you can't use adb on this mode. To push a file via fastboot is only the stock image using "fastboot install" or "fastboot boot".
~Lord
"Dream On! Dream Until Your Dreams Come True!" - Dream On (Aerosmith)
Sent from my GT-I9505
Click to expand...
Click to collapse
Oh I see. So the adb push can only be used when the phone is on normally and connected via adb? Is there a way to transfer files to a phone if it were stuck in fastboot?
sirmot said:
Oh I see. So the adb push can only be used when the phone is on normally and connected via adb? Is there a way to transfer files to a phone if it were stuck in fastboot?
Click to expand...
Click to collapse
Hi,
If you're stuck in fastboot you can flash a recovery or use the "fastboot boot" to boot in recovery and then use adb push from there .
~Lord
Hi Everyone.
After look up for a 2nd hand phone works for one hours, and just dead. the google logo bootloop.
after a ton of google, i choose Nexus root toolkit to understand if that is really a "hardware fail" as everyone says, or just another OS issue.
i saw that was nothing happening after some tries (google logo still looping) to re-flash, and left the phone and goes for lunch, when i´m back suddenly i have a few different screens randomly:
1- from google logo goes for the 4 animated dots.
2- from google logo goes to "encrypt unsuccessfull"
3- from google logo goes to android animated logo.
Nexus toolkit still showing "waiting device" and no other action there.
may the brute force or persistent attempts have any different effects on that massive issue?
thanks
erico.albino said:
Hi Everyone.
After look up for a 2nd hand phone works for one hours, and just dead. the google logo bootloop.
after a ton of google, i choose Nexus root toolkit to understand if that is really a "hardware fail" as everyone says, or just another OS issue.
i saw that was nothing happening after some tries (google logo still looping) to re-flash, and left the phone and goes for lunch, when i´m back suddenly i have a few different screens randomly:
1- from google logo goes for the 4 animated dots.
2- from google logo goes to "encrypt unsuccessfull"
3- from google logo goes to android animated logo.
Nexus toolkit still showing "waiting device" and no other action there.
may the brute force or persistent attempts have any different effects on that massive issue?
thanks
Click to expand...
Click to collapse
The common denominator of the BLOD is not being able to get into recovery mode at all. Are you able to get into recovery mode, and are you using a custom recovery (TWRP) or stock recovery? If stock have you tried doing a factory reset? The first boot will take a long time while it is encrypting.
Sounds like you are unlocked and maybe ADB debugging is enabled? Next method would be to get ADB/Fastboot installed on your PC and flash the stock Google image using the flash-all. bat file. But.... since you already have NRT running, you could open "Advanced Utilities" and fastboot format cache, system and userdata (check all 3 boxes). Then go back to the main menu and run "Flash Stock and Unroot". Use the "bootloop/semi-bricked" option. For now, don't root or install a custom recovery. Just see if you can boot into the OS.
v12xke said:
The common denominator of the BLOD is not being able to get into recovery mode at all. Are you able to get into recovery mode, and are you using a custom recovery (TWRP) or stock recovery? If stock have you tried doing a factory reset? The first boot will take a long time while it is encrypting.
Sounds like you are unlocked and maybe ADB debugging is enabled? Next method would be to get ADB/Fastboot installed on your PC and flash the stock Google image using the flash-all. bat file. But.... since you already have NRT running, you could open "Advanced Utilities" and fastboot format cache, system and userdata (check all 3 boxes). Then go back to the main menu and run "Flash Stock and Unroot". Use the "bootloop/semi-bricked" option. For now, don't root or install a custom recovery. Just see if you can boot into the OS.
Click to expand...
Click to collapse
i tried with the adb sideload the Stock one and it keeps o loop. no changes on the screen.
i'm not unlocked at all, its shows on the recovery screen. i will re-try some root and another windows7 and mac for this.
as you say, if BLOD consist to not get in to recovery, i'm safe for now, just need to figure out how to make it works.
thanks a lot so far.
erico.albino said:
i tried with the adb sideload the Stock one and it keeps o loop. no changes on the screen.
i'm not unlocked at all, its shows on the recovery screen. i will re-try some root and another windows7 and mac for this.
as you say, if BLOD consist to not get in to recovery, i'm safe for now, just need to figure out how to make it works.
thanks a lot so far.
Click to expand...
Click to collapse
You said "i'm not unlocked at all" So do you mean your bootloader is LOCKED? Also, the status of bootloader is shown in BOOTLOADER MODE not recovery mode. Perhaps you need to research the difference and answer whether your bootloader is locked (yes/no) and whether you are able to access RECOVERY MODE, or not (yes/no). And whether that is stock recovery? I have no problem with English being your second language, but you need to try to be clear in your answers so we all understand where you are so we can help you. Cheers.
How to enter Recovery Mode: https://www.youtube.com/watch?v=wq_gzT-fV2E
v12xke said:
You said "i'm not unlocked at all" So do you mean your bootloader is LOCKED? Also, the status of bootloader is shown in BOOTLOADER MODE not recovery mode. Perhaps you need to research the difference and answer whether your bootloader is locked (yes/no) and whether you are able to access RECOVERY MODE, or not (yes/no). And whether that is stock recovery? I have no problem with English being your second language, but you need to try to be clear in your answers so we all understand where you are so we can help you. Cheers.
How to enter Recovery Mode: https://www.youtube.com/watch?v=wq_gzT-fV2E
Click to expand...
Click to collapse
thanks for all the word, V12...!
dont have english as my mother language is complicated. specially when you need help on some topics that is not available or dont have good places to go here! (brazil).
anyway, i'm following your first suggestions, and i'm going to share the results soon.
the nexus screen on recovery mode shows:
Console:NULL
Battery OK
Device is LOCKED
Qfuse status ENABLED
off-mode Chager ENABLED
download mode DISABLED.
on my first attempts, i was able to enter on ADB upload menu as you indicate on the video, was able to load the stock rom but stop on the boot loop.
the second shot was my main topic status, using nexus root toolkit with "flash stock+unroot" selecting "softbrick+bootloop". three different screen results on loop.
thanks a lot for the help, bro!
:good:
erico.albino said:
thanks for all the word, V12... Device is LOCKED.... on my first attempts, i was able to enter on ADB upload menu as you indicate on the video, was able to load the stock rom but stop on the boot loop. the second shot was my main topic status, using nexus root toolkit with "flash stock+unroot" selecting "softbrick+bootloop". three different screen results on loop.
Click to expand...
Click to collapse
Because your bootloader is locked, the only real option is to sideload an OTA from the stock recovery. Not possible to flash a full image. You will need to find an OTA that is newer than your current build. If it won't boot, try a factory reset and boot again. If that doesn't work, try fastboot formatting (only) userdata and cache partitions and try the OTA again.
ps: encryption unsuccessful keeps on 7.1.1 NUFK26Kversion, after 30min google bootloop. will give a try with another versions, but my default built is NRD90T 7.0. that is what is showing on the recovery screen (the second one, on the power+volume up on recovery mode). runnning the nexus root toolkit and flash+unroot.
ps: i',m supposed to be almost there, just need to figure out
erico.albino said:
ps: encryption unsuccessful keeps on 7.1.1 NUFK26Kversion, after 30min google bootloop. will give a try with another versions, but my default built is NRD90T 7.0. that is what is showing on the recovery screen (the second one, on the power+volume up on recovery mode). runnning the nexus root toolkit and flash+unroot.
ps: i',m supposed to be almost there, just need to figure out
Click to expand...
Click to collapse
Firstly, NRT doesn't work flashing for you because your bootloader is locked (it even tells you this) and you need to be sure you are using an OTA image. You cannot flash a full stock image. The Flash Stock + Unroot option in NRT downloads the full image. You are supposed to use the ADB side load option from your phone's recovery and send it from your PC. Not that it makes a huge difference, but you are also using the wrong image for Verizon only in the U.S... You need N4F26O not NUFK26K. What happens when you do a factory reset from recovery mode? There is another update out next week (March Security Update) you can try that OTA when it is posted to the link above.
v12xke said:
Firstly, NRT doesn't work flashing for you because your bootloader is locked (it even tells you this) and you need to be sure you are using an OTA image. You cannot flash a full stock image. The Flash Stock + Unroot option in NRT downloads the full image. You are supposed to use the ADB side load option from your phone's recovery and send it from your PC. Not that it makes a huge difference, but you are also using the wrong image for Verizon only in the U.S... You need N4F26O not NUFK26K. What happens when you do a factory reset from recovery mode? There is another update out next week (March Security Update) you can try that OTA when it is posted to the link above.
Click to expand...
Click to collapse
-Factory reset/wipe data goes OK. if i restart the system, it back to bootloop.
-for some reason, my adb sideload command is not been recognized on prompt. (windows 7 32bit)
-adb devices works and show my current device on prompt.
-NRT sideload option is aborted as "verification filed" after some steps and pointing to factory image or automatic img from NRT.
-at NRT, adb sideload device is been recognized, fastboot device recognized but adb recovery device not found status its showing up in the end.
i'm sure i'm doing something wrong, just cant figure out where..... =(
erico.albino said:
-
-for some reason, my adb sideload command is not been recognized on prompt. (windows 7 32bit)
-adb devices works and show my current device on prompt.
-NRT sideload option is aborted as "verification filed" after some steps and pointing to factory image or automatic img from NRT.
-at NRT, adb sideload device is been recognized, fastboot device recognized but adb recovery device not found status its showing up in the end.
i'm sure i'm doing something wrong, just cant figure out where..... =(
Click to expand...
Click to collapse
What is the name of the file you are trying to sideload, and is it an OTA? (angler-ota-n4f26o-6a853f19.zip)
What happens when you follow the method #1 on this page? You will have to "adb push" the OTA file to your phone. If you can't do this, you may not have the correct drivers installed or not have adb installed correctly.
Not sure what you mean by "for some reason, my adb sideload command is not been recognized on prompt. (windows 7 32bit)"- can you elaborate?
v12xke said:
What is the name of the file you are trying to sideload, and is it an OTA? (angler-ota-n4f26o-6a853f19.zip)
What happens when you follow the method #1 on this page? You will have to "adb push" the OTA file to your phone. If you can't do this, you may not have the correct drivers installed or not have adb installed correctly.
Not sure what you mean by "for some reason, my adb sideload command is not been recognized on prompt. (windows 7 32bit)"- can you elaborate?
Click to expand...
Click to collapse
OTA file name: angler-n4f26o-factory-c53f0a50 (1).zip
download page/link: https://developers.google.com/android/images
i cant access internal storage. so i cant run step 1 on that page.
if i hit "adb sideload angler-n4f26o-factory-c53f0a50 (1).zip" on command prompt on windows, i receive this:
R:\Desktop\nexus\Fastboot\Fastboot>adb devices
List of devices attached
84B7N15C21000379 host
R:\Desktop\nexus\Fastboot\Fastboot>adb sideload angler-n4f26o-factory-c53f0a50.z
ip
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP
disconnect <host>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
here some images: https://goo.gl/photos/zLZ9CEh1dtpgPJf17
erico.albino said:
OTA file name: angler-n4f26o-factory-c53f0a50 (1).zip
download page/link: https://developers.google.com/android/images
i cant access internal storage. so i cant run step 1 on that page.
if i hit "adb sideload angler-n4f26o-factory-c53f0a50 (1).zip" on command prompt on windows, i receive this:
Click to expand...
Click to collapse
You are not flashing the OTA. You are attempting to sideload the full image. I'm still reading through the rest of your post, but go ahead and download the correct file.
https://developers.google.com/android/ota#angler
v12xke said:
You are not flashing the OTA. You are attempting to sideload the full image. I'm still reading through the rest of your post, but go ahead and download the correct file.
https://developers.google.com/android/ota#angler
Click to expand...
Click to collapse
forget the long post, i was missing the quotes on the image file name.
i'll run your suggestion now...
erico.albino said:
i cant access internal storage. so i cant run step 1 on that page.
Click to expand...
Click to collapse
You can use adb push to move transfer the file over to your phone. "adb push ota.zip /sdcard/ota.zip" then use the "apply update from sdcard" option in recovery. To avoid typos/syntax errors, simply rename the file you are using to ota.zip first. I still think you might have issues with your adb/driver installation.
v12xke said:
You can use adb push to move transfer the file over to your phone. "adb push ota.zip /sdcard/ota.zip" then use the "apply update from sdcard" option in recovery. To avoid typos/syntax errors, simply rename the file you are using to ota.zip first. I still think you might have issues with your adb/driver installation.
Click to expand...
Click to collapse
thanks at all for all the help. unfortunately, after successfully sideload the OTA file, boot loop still here
Sorry to hear that. See if you are allowed to fastboot FORMAT userdata and cache from your PC and try the OTA again. You may get an error formatting userdata. Remember, next week brings a new March security update, and if you haven't given up on your device you can try to flash that OTA when it is posted by Google. You can now get back to your math homework...
Before you go, does your Recovery screen still say NRD90T or did it update to N4F26O?
i can see 7.1.1 N4F26O on recovery screen.
you can bet i will not git it up on this, lol. it was a very good deal based o the value of the device here in brazil.
i'll keep this post up to date about this and let you know about any news.
thanks again for all the help bro, much appreciate it!
cheers from brazil!
erico.albino said:
i can see 7.1.1 N4F26O on recovery screen.
Click to expand...
Click to collapse
March Security Update OTA's posted on Google. Boom!
v12xke said:
March Security Update OTA's posted on Google. Boom!
Click to expand...
Click to collapse
no chanfes unfortunately
There is any specific variant of nexus that can be down for this kind of brick?
Sent from my iPhone using Tapatalk