Encountered this error message when trying to manually flash the N Dev 3 image, not via the flash-all bat. I'm very familiar when it comes to flashing images on my devices, fwiw.
I tried rebooting my PC, redownloading the image, and updating SDK Tools. No luck.
I've been able to reflash to mtc19t successfully.
My goal was to upgrade to the N Dev 3, then flash the decrypted modified N boot.img from Tigerstown in order to root.
Your fastboot is out of date or you have a bad download.
Sent from my SM-G930V using Tapatalk
Thanks. I'll give this a shot [TOOL]Minimal ADB and Fastboot [4-27-16]:
http://forum.xda-developers.com/showthread.php?t=2317790
bostonirishguy13 said:
Encountered this error message when trying to manually flash the N Dev 3 image, not via the flash-all bat. I'm very familiar when it comes to flashing images on my devices, fwiw.
I tried rebooting my PC, redownloading the image, and updating SDK Tools. No luck.
I've been able to reflash to mtc19t successfully.
My goal was to upgrade to the N Dev 3, then flash the decrypted modified N boot.img from Tigerstown in order to root.
Click to expand...
Click to collapse
You don't need to decrypt or flash a modified boot.img in order to root.
bobby janow said:
You don't need to decrypt or flash a modified boot.img in order to root.
Click to expand...
Click to collapse
Should have mentioned I'd prefer TWRP, too.
I ended up not using the unencrypted boot.img and rooted with CF Autoroot.
had same issue use fastboot from latest sdk
Related
I got the OTA update downloaded but could not install.Read somewhere if you have CWM ota update wont work.So i have downloaded the stock image for 4.0.2 and its in .tgz format
How can i upgrade to 4.0.2 using CWM or odin and not loose my data and setup.?
Please advice
Hussainally said:
I got the OTA update downloaded but could not install.Read somewhere if you have CWM ota update wont work.So i have downloaded the stock image for 4.0.2 and its in .tgz format
How can i upgrade to 4.0.2 using CWM or odin and not loose my data and setup.?
Please advice
Click to expand...
Click to collapse
Check out Chainfire's thread. He posted a no-wipe version flashable through Odin. Follow the instructions there and make sure you download the correct version for your phone (GSM/LTE)!
mbroeders said:
Check out Chainfire's thread. He posted a no-wipe version flashable through Odin. Follow the instructions there and make sure you download the correct version for your phone (GSM/LTE)!
Click to expand...
Click to collapse
hi thanks for your reply.His update you will not be updating to new bootloader am i right?
Hussainally said:
hi thanks for your reply.His update you will not be updating to new bootloader am i right?
Click to expand...
Click to collapse
Indeed, it won't touch your data, recovery or bootloader. They're all safe afaik
mbroeders said:
Indeed, it won't touch your data, recovery or bootloader. They're all safe afaik
Click to expand...
Click to collapse
thats the prob...4.0,2 has a new bootloader right?i want that.
ok what if i just want to install fresh clean stock 4.0.2...how do i do that?
Hussainally said:
thats the prob...4.0,2 has a new bootloader right?i want that.
ok what if i just want to install fresh clean stock 4.0.2...how do i do that?
Click to expand...
Click to collapse
If you want fresh clean stock then you can do two things:
1) on linux, extract the contents of the tgz package and use the sh script inside to flash.
2) since that's not possible on windows, you could use Chainfire's odin files first and next manually flash the bootloader and/or radioimage with fastboot. You can extract the bootloader and radio yourself from the tgz/tar package or look for them in the development section, someone posted them there.
mbroeders said:
If you want fresh clean stock then you can do two things:
1) on linux, extract the contents of the tgz package and use the sh script inside to flash.
2) since that's not possible on windows, you could use Chainfire's odin files first and next manually flash the bootloader and/or radioimage with fastboot. You can extract the bootloader and radio yourself from the tgz/tar package or look for them in the development section, someone posted them there.
Click to expand...
Click to collapse
You can flash it in windows using fastboot, you don't need to use odin for anything:
Extract the factory images
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
fastboot update image-yakju-icl53f.zip
Thanks everyone...will give it a go.....Cheers
krohnjw said:
You can flash it in windows using fastboot, you don't need to use odin for anything:
Extract the factory images
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
fastboot update image-yakju-icl53f.zip
Click to expand...
Click to collapse
Thanks. Just checking, if I would like to do this, but without a wipe, can't i just flash the bootloader and radio like you suggested, and then use Odin to flash Chainfire's no-wipe version right? Just so i fully understand, thanks!
mbroeders said:
Thanks. Just checking, if I would like to do this, but without a wipe, can't i just flash the bootloader and radio like you suggested, and then use Odin to flash Chainfire's no-wipe version right? Just so i fully understand, thanks!
Click to expand...
Click to collapse
What I posted does not wipe. There's little reason to use Odin. Using Odin you *can* easily brick your device (Ask all of the folks in the Nexus S forums that used Odin to flash the wrong package for their device).
fastboot update image-yakju-icl53f.zip <-- This does not wipe
fastboot -w update image-yakju-icl53f.zip <-- This wipes (-w wipes)
mbroeders said:
Thanks. Just checking, if I would like to do this, but without a wipe, can't i just flash the bootloader and radio like you suggested, and then use Odin to flash Chainfire's no-wipe version right? Just so i fully understand, thanks!
Click to expand...
Click to collapse
ok guys please bare with me here,Never done this before.when i run command adb-windows.exe,it works,thenwhen i run fastboot-windows.exe devices it works
then when i go to bootloader more...the green android with word start on top when i type fastboot flash bootloader bootloader-maguro-primekk15.img,nothing happens and it says on the phone bad command or something
please advice
Nevermind guys...I DID IT.Thanks so much...excellent guide
Hussainally said:
ok guys please bare with me here,Never done this before.when i run command adb-windows.exe,it works,thenwhen i run fastboot-windows.exe devices it works
then when i go to bootloader more...the green android with word start on top when i type fastboot flash bootloader bootloader-maguro-primekk15.img,nothing happens and it says on the phone bad command or something
please advice
ok i lost root after flashing to 4.0.2 using this guide and re did install superboot windows .bat and now the phone rebooted and its stuck on google screen...how long do i wait and what do i do next???
Click to expand...
Click to collapse
Hussainally said:
Hussainally said:
ok guys please bare with me here,Never done this before.when i run command adb-windows.exe,it works,thenwhen i run fastboot-windows.exe devices it works
then when i go to bootloader more...the green android with word start on top when i type fastboot flash bootloader bootloader-maguro-primekk15.img,nothing happens and it says on the phone bad command or something
please advice
ok i lost root after flashing to 4.0.2 using this guide and re did install superboot windows .bat and now the phone rebooted and its stuck on google screen...how long do i wait and what do i do next???
Click to expand...
Click to collapse
Give it some time, if it doesn't boot all is not lost. Pull the battery and restart.
Click to expand...
Click to collapse
ok..fingers crossed...how much time?
Halleluyah....Praise the lord....thanks a million...All is well
Hussainally said:
ok..fingers crossed...how much time?
Click to expand...
Click to collapse
I think that it depends on how many apps do you have...usually 2-3 minutes max. !
I tried flash-all and it's not flashing a recovery. What's the special sauce for flashing the stock recovery image?
You could try fastboot. Install recovery that way. Should overwrite twrp
tcarave said:
You could try fastboot. Install recovery that way. Should overwrite twrp
Click to expand...
Click to collapse
Where does one find the factory recovery images? They aren't contained in the Factory zips.
measter said:
Where does one find the factory recovery images? They aren't contained in the Factory zips.
Click to expand...
Click to collapse
In a zip inside the zip. Boot.img
But I almost guarantee if you update to latest SDK Platform Tools thru android studio that flash-all will probably work..
Sent from my sailfish using XDA Labs
nednednerb said:
In a zip inside the zip. Boot.img
But I almost guarantee if you update to latest SDK Platform Tools thru android studio that flash-all will probably work..
Click to expand...
Click to collapse
It will work, as I've done it to return to stock
Sent from my Google Pixel XL using XDA Labs
measter said:
Where does one find the factory recovery images? They aren't contained in the Factory zips.
Click to expand...
Click to collapse
Go here > https://developers.google.com/android/images
Managed to get it back to stock with the Skipsoft toolkit. What is it that makes the toolkit different in the way it flashes the file versus the flash-all?
measter said:
Managed to get it back to stock with the Skipsoft toolkit. What is it that makes the toolkit different in the way it flashes the file versus the flash-all?
Click to expand...
Click to collapse
When I had my Nexus 6 I never used a toolkit. I'll probably never use one for my pixel either. The flash all is extremely efficient. I have heard people using toolkits before and them getting bricks because there bootloader locked and they couldn't unlock again and then they bootlooped. Edit: mostly because of Enable OEM Unlock button.
Whats the process to flashing a custom rom on the pixel devices? i read something about having to flash stock first?
xSpartacusx said:
Whats the process to flashing a custom rom on the pixel devices? i read something about having to flash stock first?
Click to expand...
Click to collapse
Your bootloader, radio and vendor should match whatever ROM you want to flash.
Basically you should flash and boot March stock first, set up and set pin
Download rom, twrp installer zip
Remove screen lock pin
Fastboot boot (twrp.img)
Factory reset
Flash rom + twrp installer
Reboot system
If you want to flash a 9 based ROM like carbonrom you'll have to format userdata and flash and boot August factory image then repeat the steps above
Either way you should learn the fastboot commands and do things manually, it comes in handy updating both slots if needed.
oh yea i got it figured out! now, if i go back to stock from a custom rom, using the stock March image, will i still get OTA updates or will i need to flash through the OTA images that are provided?
xSpartacusx said:
oh yea i got it figured out! now, if i go back to stock from a custom rom, using the stock March image, will i still get OTA updates or will i need to flash through the OTA images that are provided?
Click to expand...
Click to collapse
You'll need to relock your bootloader, just make sure you're full stock on both slots or you will brick your phone. I personally don't think it's worth the risk and just update through twrp or fastboot
While unlocking camera 2 api It says failed (remote:dtb not found) in fastboot boot patchedboot.img step, any idea whats wrong?I tried with latest magisk as well as with the one in the patched boot file. Bootloader is unlocked and my phone is in the latest build 11.0.4.0 stock.
Samir 120 said:
While unlocking camera 2 api It says failed (remote:dtb not found) in fastboot boot patchedboot.img step, any idea whats wrong?I tried with latest magisk as well as with the one in the patched boot file. Bootloader is unlocked and my phone is in the latest build 11.0.4.0 stock.
Click to expand...
Click to collapse
I suppose you are trying to flash the patched boot.img. If that's the case, the command is "fastboot flash boot patched_boot.img".
Neon丶 said:
I suppose you are trying to flash the patched boot.img. If that's the case, the command is "fastboot flash boot patched_boot.img".
Click to expand...
Click to collapse
Im trying to install gcam without root. It says fastboot boot patched_boot.img in every guide i have seen so far, are you sure i need to add flash? Im dont have much knowledge in these things dont want to cause problems dor my device.
Samir 120 said:
Im trying to install gcam without root. It says fastboot boot patched_boot.img in every guide i have seen so far, are you sure i need to add flash? Im dont have much knowledge in these things dont want to cause problems dor my device.
Click to expand...
Click to collapse
No, not flash. Just boot.
Sounds like you are not running the command from the folder with the patched boot file. Or the file has a different name.
Hey i was attempted to install TWRP and got stuck in download mode boot loop. Fixed it by flashing stock firmware. I noticed a small error with my camera so i tried to lock bootloader again to see if that would fix the issue. But after flashing stock firmware a second time after locking the bootloader it didnt work and im stuck in download mode boot loop again. Only this time i dont get the option to unlock the bootloader and i cant enter the OS in order to enable OEM Unlock.
Here is the error screen: https://prnt.sc/q8vmG--mTHxY
Anyone know how to get out of this mess? Thanks
Am i doomed?
cheen11 said:
Hey i was attempted to install TWRP and got stuck in download mode boot loop. Fixed it by flashing stock firmware. I noticed a small error with my camera so i tried to lock bootloader again to see if that would fix the issue. But after flashing stock firmware a second time after locking the bootloader it didnt work and im stuck in download mode boot loop again. Only this time i dont get the option to unlock the bootloader and i cant enter the OS in order to enable OEM Unlock.
Here is the error screen: https://prnt.sc/q8vmG--mTHxY
Anyone know how to get out of this mess? Thanks
Click to expand...
Click to collapse
You can't lock your bootloader when your phone have unsigned binaries such as TWRP/Magisk installed. Have you tried to flash again the stock firmware (BL/CP/AP/CSC)?
EDIT: by looking at the error it seems like your bootloader and vbmeta aren't from the same build (bootloader: DVK5, vbmeta: DVL2), I highly suggest you to flash the latest firmware available for your country
BlackMesa123 said:
You can't lock your bootloader when your phone have unsigned binaries such as TWRP/Magisk installed. Have you tried to flash again the stock firmware (BL/CP/AP/CSC)?
EDIT: by looking at the error it seems like your bootloader and vbmeta aren't from the same build (bootloader: DVK5, vbmeta: DVL2), I highly suggest you to flash the latest firmware available for your country
Click to expand...
Click to collapse
I can try other countries but im not sure what the exact country version is. Im from denmark and my country is not on the list so i just choose UK.
cheen11 said:
I can try other countries but im not sure what the exact country version is. Im from denmark and my country is not on the list so i just choose UK.
Click to expand...
Click to collapse
Shouldn’t be a big deal unless there’s something Carrier specific required by your phone. Just make sure you don’t lock your bootloader again while using custom binaries or you might soft brick your device again. To bypass the camera lock you can use a SafetyNet fix module for Magisk which will spoof the bootloader status to the camera HAL
cheen11 said:
I can try other countries but im not sure what the exact country version is. Im from denmark and my country is not on the list so i just choose UK.
Click to expand...
Click to collapse
You can try also the NEE for Nordic Countries...
BlackMesa123 said:
You can't lock your bootloader when your phone have unsigned binaries such as TWRP/Magisk installed. Have you tried to flash again the stock firmware (BL/CP/AP/CSC)?
EDIT: by looking at the error it seems like your bootloader and vbmeta aren't from the same build (bootloader: DVK5, vbmeta: DVL2), I highly suggest you to flash the latest firmware available for your country
Click to expand...
Click to collapse
Am i supposed to flash only AP or all of them? I have only ever flashed AP and worked without problems but after locking the bootloader i only get the above error boot loop.
cheen11 said:
Am i supposed to flash only AP or all of them? I have only ever flashed AP and worked without problems but after locking the bootloader i only get the above error boot loop.
Click to expand...
Click to collapse
The error in your device happens for this exact reason: vbmeta partition in the AP tar can’t verify other system binaries since they’re older and you didn’t update them (DVL2 vs. DVK5). First flash the whole firmware package via Odin (BL, CP, AP and CSC), if you wanna root your device make sure you flash TWRP+a patched vbmeta image to avoid this error to happen again. Also do not relock your bootloader again while your phone has custom binaries flashed, if you wanna lock your bootloader flash the whole stock firmware package before.
BlackMesa123 said:
The error in your device happens for this exact reason: vbmeta partition in the AP tar can’t verify other system binaries since they’re older and you didn’t update them (DVL2 vs. DVK5). First flash the whole firmware package via Odin (BL, CP, AP and CSC), if you wanna root your device make sure you flash TWRP+a patched vbmeta image to avoid this error to happen again. Also do not relock your bootloader again while your phone has custom binaries flashed, if you wanna lock your bootloader flash the whole stock firmware package before.
Click to expand...
Click to collapse
Ah, once choosing all the files it worked, thanks a bunch
BlackMesa123 said:
The error in your device happens for this exact reason: vbmeta partition in the AP tar can’t verify other system binaries since they’re older and you didn’t update them (DVL2 vs. DVK5). First flash the whole firmware package via Odin (BL, CP, AP and CSC), if you wanna root your device make sure you flash TWRP+a patched vbmeta image to avoid this error to happen again. Also do not relock your bootloader again while your phone has custom binaries flashed, if you wanna lock your bootloader flash the whole stock firmware package before.
Click to expand...
Click to collapse
I dont know if im using the right files but i still get the same boot loop (https://prnt.sc/1lCk2FQEymPn) after adding twrp-3.7.0_12-2-a52sxq.img.tar to AP and vbmeta_disable.tar to USERDATA.
cheen11 said:
I dont know if im using the right files but i still get the same boot loop (https://prnt.sc/1lCk2FQEymPn) after adding twrp-3.7.0_12-2-a52sxq.img.tar to AP and vbmeta_disable.tar to USERDATA.
Click to expand...
Click to collapse
Are you flashing the patched vbmeta in the TWRP XDA thread or another one? Also the latest TWRP version is 3.7.0-3 so flash that one.
BlackMesa123 said:
Are you flashing the patched vbmeta in the TWRP XDA thread or another one? Also the latest TWRP version is 3.7.0-3 so flash that one.
Click to expand...
Click to collapse
Im using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-note10-lite-exynos.4350891/
I tried flashing that along with this: twrp-3.7.0_12-3-a52sxq.img.tar
But i still get the boot loop. Not sure if i can keep trying to re-flash these if the boot loop already happened
cheen11 said:
Im using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-note10-lite-exynos.4350891/
I tried flashing that along with this: twrp-3.7.0_12-3-a52sxq.img.tar
But i still get the boot loop. Not sure if i can keep trying to re-flash these if the boot loop already happened
Click to expand...
Click to collapse
You must use the patched vbmeta linked in the a52s TWRP thread, flash that one and you should boot fine in TWRP.
BlackMesa123 said:
You must use the patched vbmeta linked in the a52s TWRP thread, flash that one and you should boot fine in TWRP.
Click to expand...
Click to collapse
Hmm i tried using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-0-3-for-galaxy-a52s-5g.4488419/
But this time i got a fail with odin: https://prnt.sc/9HfVrQtC-gSO
cheen11 said:
Hmm i tried using the vbmeta from this thread: https://forum.xda-developers.com/t/recovery-official-twrp-3-7-0-3-for-galaxy-a52s-5g.4488419/
But this time i got a fail with odin: https://prnt.sc/9HfVrQtC-gSO
Click to expand...
Click to collapse
I think it has something to do with the space in “New folder” name, try to copy the TWRP tar in a path that has no spaces
BlackMesa123 said:
I think it has something to do with the space in “New folder” name, try to copy the TWRP tar in a path that has no spaces
Click to expand...
Click to collapse
Oh yeah good catch, i renamed the folder and didnt consider that it might not be updated it odin. It finally worked, thanks again for the help very much appreciated
Hmm i guess problems keep popping up. I guess its best that i just post here instead of creating a new thread. Im successfully in the TWRP UI but now i cant boot to system, it will just restart 2 times and then boot to TWRP. Also it fails to backup the boot image (with the error "Unable to mount storage") which i read in a tutorial that you were supposed to do.
cheen11 said:
Hmm i guess problems keep popping up. I guess its best that i just post here instead of creating a new thread. Im successfully in the TWRP UI but now i cant boot to system, it will just restart 2 times and then boot to TWRP. Also it fails to backup the boot image (with the error "Unable to mount storage") which i read in a tutorial that you were supposed to do.
Click to expand...
Click to collapse
As mentioned in the TWRP thread guide, you must format your data partition in TWRP in order to be able to boot back in the OS.