I downloaded the latest January Update. I did my reboot to bootloader, flash bootloader/radio, did update image.zip.
This failed with: failed (remote: variable not found).
Google says it's because not updated fastboot. I updated now i'm getting:
error: failed to load 'image-blueline-qq1a.200105.003.zip': Not enough space
When I google this error, it mentions doing a complete manual install of a and b slots, but fastboot flash system system.img doesn't work anymore. Anyone know how I can update?
Welp 1 computer I tried it on, gave the above problems. Tried it on my main home computer, worked. Don't know what's different TBH.
dardack said:
Welp 1 computer I tried it on, gave the above problems. Tried it on my main home computer, worked. Don't know what's different TBH.
Click to expand...
Click to collapse
Different driver versions perhaps?
dcarvil said:
Different driver versions perhaps?
Click to expand...
Click to collapse
Think fastboot. I have no clue where i got the adb/fastboot i use on the computer that worked.
dardack said:
Think fastboot. I have no clue where i got the adb/fastboot i use on the computer that worked.
Click to expand...
Click to collapse
The official source for fastboot is platform tools at https://developer.android.com/studio/releases/platform-tools
You should always check for a new version if you run into problems. Actually, I always check for a new version before I try to do an update.
And never use the version from the Linux apt repository for anything but setting permissions. After that, use a ./ to run the current version downloaded (or installed with SDK tools or Studio) separately with the folder opened directly in terminal. Probably off topic, but that version of fastboot is old AF and there have been a handful of new commands like "fastboo reboot fastboot" to get to fastbootd.
Related
Here is the deal. Got my wifi only on launch day. Soon there after rooted. Installed bigdogrush 1.3 kernel. Tried to update to sdcard support. Each time I tried it would screw up my wifi....so I eventually gave up. Here is the real problem. Now I can't install recently released 3.1 update. Can anyone explain to me how to return to the stock kernel? I understand this will allow me to install the 3.1 update. Thanks for any help.
xhuck1 said:
Here is the deal. Got my wifi only on launch day. Soon there after rooted. Installed bigdogrush 1.3 kernel. Tried to update to sdcard support. Each time I tried it would screw up my wifi....so I eventually gave up. Here is the real problem. Now I can't install recently released 3.1 update. Can anyone explain to me how to return to the stock kernel? I understand this will allow me to install the 3.1 update. Thanks for any help.
Click to expand...
Click to collapse
try this, i just did it and works great. you basically need to download the stock images and use adb to push them. btw i assume you have a us version wifi only xoom. i would skip the last step about relocking it, if you plan to upgrade your kernel after your on 3.1.
http://developer.motorola.com/products/software/
once your back to stock everything, you can safely update to 3.1
I appreciate your help. Problem is I don't know how to do the things you are talking about. I've downloaded the images and the sdk. I'm not sure where I should put them on my zoom. Also when I try to run fastboot I get a device not found message. I also get a AdbWinApi.dll not found. I have no idea how to fix any of this. Yes I have a U.S. WIFI. I used the one click rook method. Is there a one click method out there that would help me?
If you're using windows, open the SDK folder and browse to the tools folder. Copy the img files to that folder.
Now open a command prompt and browse to the SDK Folder\tools folder (this folder as the fastboot.exe file that we're going to use and now the img files are also here!)
Now reboot your XOOM into fastboot mode (turn off the xoom, then turn the XOOM back on and while at the "Dual Core" logo, start pressing volume down until you see "--> Fastboot" up on the top left corner then press volume up to start the fastboot protocol).
Once you're in fastboot mode, in the command prompt, type fastboot devices to make sure your xoom is listed on there. If not, check to make sure your system isn't missing drivers, if so, download the xoom drivers again or if you have the Motorola Mobile Drivers installed already, open the Motorola Mobile Driver Installer and do an update to make sure you have the latest drivers).
Once you've confirmed that fastboot can talk to your xoom, run this commands:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Your xoom will then relock itself, format, and reboot.
This is as clear as I can be.
If need to, re-run the SDK Manager and make sure you have the correct packages installed needed.
xhuck1 said:
Here is the deal. Got my wifi only on launch day. Soon there after rooted. Installed bigdogrush 1.3 kernel. Tried to update to sdcard support. Each time I tried it would screw up my wifi....so I eventually gave up. Here is the real problem. Now I can't install recently released 3.1 update. Can anyone explain to me how to return to the stock kernel? I understand this will allow me to install the 3.1 update. Thanks for any help.
Click to expand...
Click to collapse
I'm betting the reason your wifi isn't working is because you didn't push the .ko files. Think of those as driver files. You probably just flashed the boot partition.
Hey guy's only wanted to do a factory reset but I idiot just wiped everything...
So nothing was anymore on it. I downloaded this file:
OTA_M4_UL_K44_SENSE60_MR_HTC_Europe_4.09.401.3-3.10.401
As I have 4.09.401, CID-HTC__102...
So I was very lost and extracted firmware.zip out of it and flashed it over "fastboot oem rebootRUU" - "fastboot flash zip firmware.zip"
It is also now "Relocked" with S-OFF....
I'm stuck, I need my phone the next few days very often...
I dont know what to do anymore if I try to do the same with the OTA zip file it says FAILED (remote: 24 parsing android-info fail)
(When I tried before with TWRP ADB Sideload before I flashed the firmware.zip, it told me "file_getprop failed to stat /system/build.prop"
What can I do now to get my phone working again
Which version of hboot?
Which version of TWRP?
Are you able to connect to your phone via fastboot?
Are you able to connect to your phone via adb (from within TWRP)?
jollywhitefoot said:
Which version of hboot?
Which version of TWRP?
Are you able to connect to your phone via fastboot?
Are you able to connect to your phone via adb (from within TWRP)?
Click to expand...
Click to collapse
- HBOOT 2.22.000
- openrecovery-twrp-2.7.1.0-m4.img (It's the only version where I even can see my devices with "adb devices")
- Yes I am
- Not really I can go with ADB Sideload but using "adb sideload" does not work...
It tells me:
sending: 'rom.zip' 100%
On my phone it's saved under /data/media/sideload.zip but it tells me:
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Error executing updater binary in zip '/data/media/sideload.zip'
Click to expand...
Click to collapse
I had a similar issue. Adb only seemed to work on older version of twrp, except in reality, it wasn't working at all. First thing you need to do is get adb working fully to where you can push a Rom to your phone. The problem is likely your Windows drivers and not your phone, so quit trying to flash firmware to fix your phone. For me, I installed a clean copy of Windows xp on an old computer and then set fastboot and Adb up on it. I've also gotten adb and fastboot working using ubuntu live CD. I'll try and find instructions for that method (it's super easy and will run on your CD drive, so you don't need to format hd out install anything).
Once adb works, you can just push any sense6 Rom and then install in twrp and you'll be good to go.
Edit: read posts 17 & 22 here for information on getting ubuntu live CD to work.
http://forum.xda-developers.com/htc-one-mini/help/help-urgent-os-recovery-t2859034/page2
jollywhitefoot said:
I had a similar issue. Adb only seemed to work on older version of twrp, except in reality, it wasn't working at all. First thing you need to do is get adb working fully to where you can push a Rom to your phone. The problem is likely your Windows drivers and not your phone, so quit trying to flash firmware to fix your phone. For me, I installed a clean copy of Windows xp on an old computer and then set fastboot and Adb up on it. I've also gotten adb and fastboot working using ubuntu live CD. I'll try and find instructions for that method (it's super easy and will run on your CD drive, so you don't need to format hd out install anything).
Once adb works, you can just push any sense6 Rom and then install in twrp and you'll be good to go.
Edit: read posts 17 & 22 here for information on getting ubuntu live CD to work.
http://forum.xda-developers.com/htc-one-mini/help/help-urgent-os-recovery-t2859034/page2
Click to expand...
Click to collapse
The problem is that I cant install the ROM.
I've push'ed it do the ROM but as you can see my post above TWRP only gives me error :/
LuvMyHTC21 said:
Hey guy's only wanted to do a factory reset but I idiot just wiped everything...
So nothing was anymore on it. I downloaded this file:
OTA_M4_UL_K44_SENSE60_MR_HTC_Europe_4.09.401.3-3.10.401
As I have 4.09.401, CID-HTC__102...
So I was very lost and extracted firmware.zip out of it and flashed it over "fastboot oem rebootRUU" - "fastboot flash zip firmware.zip"
It is also now "Relocked" with S-OFF....
Click to expand...
Click to collapse
just try to flash not OTA, but ROM
version 2 from here will be Ok
Sweet Jesus, finally after 9 hours (no joke) I got it working, thank you so much !
hey everyone really struggling with this I'm stuck in a bootloop keeps saying Android system is corrupt factory reset I have tried that with still no luck tried to flash factory image through fastboot with a chromebook running linux everything flashes except system image it says failed no partition not sure if that its why its resulting in bootloop still but any help would be appreciated
yunghunter said:
hey everyone really struggling with this I'm stuck in a bootloop keeps saying Android system is corrupt factory reset I have tried that with still no luck tried to flash factory image through fastboot with a chromebook running linux everything flashes except system image it says failed no partition not sure if that its why its resulting in bootloop still but any help would be appreciated
Click to expand...
Click to collapse
Are you sure you are running the latest version of platform tools - here?
If you are using the latest version, you could try the Deuces script to try to fix your issue. I have heard good things about it, but have never actually used it, just follow the instructions in the thread.
HTH!
Try flashing 8.0 then flashing 8.1.
yunghunter said:
hey everyone really struggling with this I'm stuck in a bootloop keeps saying Android system is corrupt factory reset I have tried that with still no luck tried to flash factory image through fastboot with a chromebook running linux everything flashes except system image it says failed no partition not sure if that its why its resulting in bootloop still but any help would be appreciated
Click to expand...
Click to collapse
What was you trying to do before bootloop?
Daandofreak said:
What was you trying to do before bootloop?
Click to expand...
Click to collapse
root
Duhman72 said:
Are you sure you are running the latest version of platform tools - here?
If you are using the latest version, you could try the Deuces script to try to fix your issue. I have heard good things about it, but have never actually used it, just follow the instructions in the thread.
HTH!
Click to expand...
Click to collapse
Tried the Deuces and updated the platform tools now after the deuces it reboots to bootloader with a error highlighted in yellow saying LoaImageAndAuth Failed: Load Error
yunghunter said:
Tried the Deuces and updated the platform tools now after the deuces it reboots to bootloader with a error highlighted in yellow saying LoaImageAndAuth Failed: Load Error
Click to expand...
Click to collapse
I ran into this error recently which seemed to be fixed by updating my not-new-enough platform tools and reflashing.
cntryby429 said:
I ran into this error recently which seemed to be fixed by updating my not-new-enough platform tools and reflashing.
Click to expand...
Click to collapse
how would I go about doing that what would my next step be I'm sorry just dont where to go next
yunghunter said:
how would I go about doing that what would my next step be I'm sorry just dont where to go next
Click to expand...
Click to collapse
what do you get when you type the below commands?:
adb --version
fastboot --version
Duhman72 said:
what do you get when you type the below commands?:
adb --version
fastboot --version
Click to expand...
Click to collapse
with adb command it gives me all the commands I can do and with the fastboot command it says unreconized option
yunghunter said:
with adb command it gives me all the commands I can do and with the fastboot command it says unreconized option
Click to expand...
Click to collapse
I believe you said you are on Linux.. those work on windows. look thru the adb commands and you should see the proper syntax.. same for fastboot if you maybe just type fastboot help or fastboot -h.
There should be an option for getting the versions. It will return something like this (except not windows paths):
C:\Users\UserName>adb --version
Android Debug Bridge version 1.0.39
Version 0.0.1-4500957
Installed as C:\adb\platform-tools\adb.exe
C:\Users\UserName>fastboot --version
fastboot version 0.0.1-4500957
Installed as C:\adb\platform-tools\fastboot.exe
Duhman72 said:
I believe you said you are on Linux.. those work on windows. look thru the adb commands and you should see the proper syntax.. same for fastboot if you maybe just type fastboot help or fastboot -h.
There should be an option for getting the versions. It will return something like this (except not windows paths):
C:\Users\UserName>adb --version
Android Debug Bridge version 1.0.39
Version 0.0.1-4500957
Installed as C:\adb\platform-tools\adb.exe
C:\Users\UserName>fastboot --version
fastboot version 0.0.1-4500957
Installed as C:\adb\platform-tools\fastboot.exe
Click to expand...
Click to collapse
adb version is 1.0.32 fastboot I cannot find the fastboot version
yunghunter said:
adb version is 1.0.32 fastboot I cannot find the fastboot version
Click to expand...
Click to collapse
I don't think you are using the latest version.
Download the latest versions for Windows/Mac/Linux here.
Run the adb version command again to see if it has updated.
Duhman72 said:
I don't think you are using the latest version.
Download the latest versions for Windows/Mac/Linux here.
Run the adb version command again to see if it has updated.
Click to expand...
Click to collapse
downloaded from the file posted for latest version still came up same version tried using dueces toolkit runs everything ok until the end then it says fastboot unrecognized option set active=a
yunghunter said:
downloaded from the file posted for latest version still came up same version tried using dueces toolkit runs everything ok until the end then it says fastboot unrecognized option set active=a
Click to expand...
Click to collapse
are you sure you don't have an old installation of the tools somewhere else on you computer? That error sounds to me like it is an old version of fastboot.
can you run the adb version by pointing it to that actual path you have installed the new one you downloaded? I am not real familiar w/ Linux, but in windows it would be something like this - straight from my computer where i have adb.exe installed in 2 different paths:
--OLD VERSION OF TOOLS
C:\Users\UserName>c:\adb\adb.exe version
Android Debug Bridge version 1.0.26
--CURRENT VERSION OF TOOLS
C:\Users\UserName>c:\adb\platform-tools\adb.exe version
Android Debug Bridge version 1.0.39
Version 0.0.1-4500957
Installed as c:\adb\platform-tools\adb.exe
I made sure to set environment variable to always reference the one in path c:\adb\platform-tools\, so i get the newer version and don't have the errors you are seeing. (again I use windows, so I have very little Linux knowledge)
It really sounds like you are using old version of the tools.
yunghunter said:
adb version is 1.0.32 fastboot I cannot find the fastboot version
Click to expand...
Click to collapse
Saw that you mentioned you were using Linux; it appears that the latest Ubuntu binaries are not up to date. After I finally tracked down the version number installed on my laptop I realized I wasn't on the latest version and downloaded them from Google. You should ultimately end up with fastboot version 0.0.1-4500957. As it turns out this is the only version of fastboot that actually returned a valid version number for me.
Download all the files and unzip the platform-tools folder and move apk and boot to the phone memory
first we have to download magisk apk .. install and open
then we will install magisk, a window will open and we will install it and it will ask us to patch a boot image
we look for the boot image that we download ... then we click on it and the boot image will be patched ...
the patched image of awaits in in download in internal storage ..
we go to the computer and move the patched image to the desktop ..
we go to the platform-tools folder and open it and give alt and right click in an empty space and open the powershell or cmd window .. once it starts in the command window we will give it a series of commands
first: we have to activate the cell phone's usb debug and connect to the computer
in the command window we put:
cmd
adb devices (we have to detect the device)
adb reboot bootloader (or start bootloader manually)
fasboot devices (we have to detect the cell phone)
fastboot flash boot (and we move the patched image in the command window next to the last command or this one)
we give space and we give enter and the image will be installed and we give ..
fastboot reboot
and ready you have root just open magisk and it is already installed https://drive.google.com/drive/folders/1UjyAzSZeMUBIwSTvlNo1CFL7BO3dMLPW?usp=sharing
https://drive.google.com/open?id=1HtjdNjdJ3XiSaOAUNVwZ8E-tGv3xr2Ly
https://drive.google.com/open?id=1eFpvFeUe_xLRUFnBbT2ZzKdTgX8-nyYQ
I will try it and see that it breaks this time
Marakas89 said:
Download all the files and unzip the platform-tools folder and move apk and boot to the phone memory
first we have to download magisk apk .. install and open
then we will install magisk, a window will open and we will install it and it will ask us to patch a boot image
we look for the boot image that we download ... then we click on it and the boot image will be patched ...
the patched image of awaits in in download in internal storage ..
we go to the computer and move the patched image to the desktop ..
we go to the platform-tools folder and open it and give alt and right click in an empty space and open the powershell or cmd window .. once it starts in the command window we will give it a series of commands
first: we have to activate the cell phone's usb debug and connect to the computer
in the command window we put:
cmd
adb devices (we have to detect the device)
adb reboot bootloader (or start bootloader manually)
fasboot devices (we have to detect the cell phone)
fastboot flash boot (and we move the patched image in the command window next to the last command or this one)
we give space and we give enter and the image will be installed and we give ..
fastboot reboot
and ready you have root just open magisk and it is already installed https://drive.google.com/drive/folders/1UjyAzSZeMUBIwSTvlNo1CFL7BO3dMLPW?usp=sharing
Click to expand...
Click to collapse
Thanks for share
work fine in me
wirdan.hungkul said:
Thanks for share
work fine in me
Click to expand...
Click to collapse
by chance you don't have the ota? (zip), the last update available that I have is a security patch for 8.1
:c
djxpro said:
by chance you don't have the ota? (zip), the last update available that I have is a security patch for 8.1
:c
Click to expand...
Click to collapse
I don't have Ota update ..., you should re-flash your device
wirdan.hungkul said:
I don't have Ota update ..., you should re-flash your device
Click to expand...
Click to collapse
Well, remember something: I guess for it to work, the bootloader must be disabled, right?
:c
djxpro said:
Well, remember something: I guess for it to work, the bootloader must be disabled, right?
:c
Click to expand...
Click to collapse
bootloader must be activated ..
wirdan.hungkul said:
bootloader must be activated ..
Click to expand...
Click to collapse
I tried it with 8.1 files
and cmd show me a device locked error
It may be by the method in the wrong version.
djxpro said:
I tried it with 8.1 files
and cmd show me a device locked error
It may be by the method in the wrong version.
Click to expand...
Click to collapse
try this https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-unlock-bootloader-nokia-3-t3699344
if an error still occurs
try flash it https://forum.xda-developers.com/nokia-3/how-to/nokia-3-ta-1032-official-firmware-sp-t3744634
and if after Flash Dead And Vibrate only
https://www.youtube.com/watch?v=zW6srLB5fBM
wirdan.hungkul said:
try this https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-unlock-bootloader-nokia-3-t3699344
if an error still occurs
try flash it https://forum.xda-developers.com/nokia-3/how-to/nokia-3-ta-1032-official-firmware-sp-t3744634
and if after Flash Dead And Vibrate only
https://www.youtube.com/watch?v=zW6srLB5fBM
Click to expand...
Click to collapse
I tried the first thing and it throws me another different mistake.
something like unknown command.
or something concerning the communication with the device
and the other link is a 7.1 rom, right?
my device is the ta 1028...
technically it is the same
djxpro said:
I tried the first thing and it throws me another different mistake.
something like unknown command.
or something concerning the communication with the device
and the other link is a 7.1 rom, right?
my device is the ta 1028...
technically it is the same
Click to expand...
Click to collapse
is it already installed mtk driver?
https://androidmtk.com/download-mtk-driver-auto-installer
or
https://androidmtk.com/download-mtk-usb-all-drivers
yes, anothet link 7.0 and 7.1 rom...
or you can try https://forum.xda-developers.com/nokia-3/how-to/nokia-3-official-firmware-india-uae-t3674320
Firmware supported for below Nokia 3 Supported Models
- NOKIA 3 TA-1032 DS
- NOKIA 3 TA-1020 SS
- NOKIA 3 TA-1028 SS
- NOKIA 3 TA-1038 DS
Apparently it is an issue of the operator that I do not have the update yet.
I went back to 8.0 while I find out what happened to the ota.
And if it comes out I'll capture it.
wirdan.hungkul said:
is it already installed mtk driver?
https://androidmtk.com/download-mtk-driver-auto-installer
or
https://androidmtk.com/download-mtk-usb-all-drivers
yes, anothet link 7.0 and 7.1 rom...
or you can try https://forum.xda-developers.com/nokia-3/how-to/nokia-3-official-firmware-india-uae-t3674320
Firmware supported for below Nokia 3 Supported Models
- NOKIA 3 TA-1032 DS
- NOKIA 3 TA-1020 SS
- NOKIA 3 TA-1028 SS
- NOKIA 3 TA-1038 DS
Click to expand...
Click to collapse
well, finally, i have android 9.
but, i cant flash the patched boot
:c failed: unknown command
Well, I managed to root.
I got the OTA in a Russian forum.
After a couple of failed attempts, I managed to figure out how to mount the OTA.
Then, not working or rooting, and realize that the bootloader was not unlocked, I repeated all the steps.
I noticed that I am subnormal, and that the code I was using to unlock was not correct (several months to realize this).
Anyway, go down to 7.1, unlock the bootloader, flash to 8.1 (4.42) (orange state up)
I mounted OTA 5.20 through recovery
I did the steps in the post, and finally I have Pie with root
Orange State continues, but I will not block the bootloader again
djxpro said:
Well, I managed to root.
I got the OTA in a Russian forum.
After a couple of failed attempts, I managed to figure out how to mount the OTA.
Then, not working or rooting, and realize that the bootloader was not unlocked, I repeated all the steps.
I noticed that I am subnormal, and that the code I was using to unlock was not correct (several months to realize this).
Anyway, go down to 7.1, unlock the bootloader, flash to 8.1 (4.42) (orange state up)
I mounted OTA 5.20 thrgough recovery
I did the steps in the post, and finally I have Pie with root
Orange State continues, but I will not block the bootloader again
Click to expand...
Click to collapse
:good:
Well.....i thought let me give it a try.....but.....problem started then...
--- adb works fine.....both the commands (adb devices and adb reboot bootloader) gets executed
--- but my device doesn't get detected in fastboot mode
--- thinking that its problem with drivers...i tried every driver (adb and fastboot) out in the internet and nokia drivers...but got no luck
--- hoping that someone could help me i posted here.... thanks in advance
djxpro said:
well, finally, i have android 9.
but, i cant flash the patched boot
:c failed: unknown command
Click to expand...
Click to collapse
i found a way to flash the patched boot and unlock the bootloader on pie
Here
NulledRoot said:
i found a way to flash the patched boot and unlock the bootloader on pie
Here
Click to expand...
Click to collapse
actually, i have a rooted phone.
but, i lock the bootloader again, and now, i need connect to usb to start up
without usb, i give a red state
.-.)
my phone stuck at reboot loop can someone help me?
This is just a quick post to document an issue & solution I had when updating my Pixel 5 to the latest OTA and trying to re-root.
I had installed the latest OTA via system update, then downloaded the matching image from the Factory Images Page, pulled the boot.img out of there, transferred it to my Pixel, and used Magisk to patch it.
I then transferred it back to my computer and tried to flash it to the phone using fastboot flash boot boot_patched.img. At this point the phone entered a bootloop.
I booted into the bootloader menu and tried to flash the latest clean system image (without wiping data), when I ran into the following system errors causing the flash to fail when trying to flash the system partition:
Code:
FAILED (remote: Partition system not found)
(and later...)
FAILED (remote: Partition should be flashed in fastbootd)
I initially panicked but the way around this should you ever encounter these errors, is to literally just update your fastboot and adb binaries on your computer. You can grab the latest standalone binaries from here, and throw them where your PATH will find them. After running the flash script again, it worked without a hitch and my phone was up and running without issue.
CarteNoir said:
I initially panicked but the way around this should you ever encounter these errors, is to literally just update your fastboot and adb binaries on your computer. You can grab the latest standalone binaries from here, and throw them where your PATH will find them. After running the flash script again, it worked without a hitch and my phone was up and running without issue.
Click to expand...
Click to collapse
Just wanted to say thanks. I had this issue with my Pixel 6, and updating my ancient ADB/fastboot binaries resolved it!
It's always important to ensure your platform tools are updated! Glad you figured this out!
Thank you!
I had the latest universal ADB/Fastboot drivers installed... but this didn't make a difference
I downloaded latest platform tools, ran the flash-all.bat from there and BOOM, sorted
Thank you so much
Thank you so much. Can't believe the solution is so simple lol