Database Users

Can't flash bootloader, system.img?

Hello,
Sorry but I have ran into a pretty big problem and I was an idiot and did not make a NAN backup.
I am capable of going to the bootloader and I can flash recovery but I can't do much else as far as updating the bootloader from 4.18 to 4.23 (not a huge issue at least right now) but the bigger issue is that I cannot flash system.img as it will just timeout on "sending system" through fastboot. Sending myself a custom rom through ADB and attempting to flash recovery does not work either due to system partition errors. erased and retried to send system and no luck, continues to time out. I believe this might be due to my previous custom rom perhaps resizing the system partition too small? But shouldn't this be solved when erasing/using flash-all.bat??
Please not sure what to do at this point. I've been using the Nexus Root Toolkit trying to flash 4.2.2, as I don't have the bootloader for 4.3 on my device (can't update it anyhow.. again that's a problem but I should be able to at least flash 4.2.2 for right now?) and doing it manually with fastboot and ADB but I am have no luck getting system to write/finish sending.
Any recommendations would be greatly appreciated!!

You can boot into recovery (boot/stock ) directly from botloader via fastboot. Hard to say if it is usefull to you.

Unfortunately not. I can get to recovery and flash custom recoveries with no problem, it is sending the system.img and getting it to write the problem.
Is a picture of the problem, just times out when sending the system.img even if I leave it on for 1 hr.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The same happens at sending the bootloader you see but I disconnect and reconnect quick to make sure it gets past this (I have the 4.18 bootloader already loaded, and I cannot update this but this seems like a second issue compared to sending the system.img). Doing it manually through fastboot and flash-all.bat doesn't help, still times out. Sending myself a rom to flash through recovery doesn't work as I have system and cache partition issues that won't let it install.
Not sure what to do at this point other than keep trying and maybe I'll get luck?

xdaNoobTutorial said:
Unfortunately not. I can get to recovery and flash custom recoveries with no problem, it is sending the system.img and getting it to write the problem.
Is a picture of the problem, just times out when sending the system.img even if I leave it on for 1 hr.
The same happens at sending the bootloader you see but I disconnect and reconnect quick to make sure it gets past this (I have the 4.18 bootloader already loaded, and I cannot update this but this seems like a second issue compared to sending the system.img). Doing it manually through fastboot and flash-all.bat doesn't help, still times out. Sending myself a rom to flash through recovery doesn't work as I have system and cache partition issues that won't let it install.
Not sure what to do at this point other than keep trying and maybe I'll get luck?
Click to expand...
Click to collapse
Just to update ** I am using Windows 8 and think this might potentially be just a driver problem. Not sure exactly why, since I can easily write recovery and boot images... but this is the only thing I can think of preventing the bootloader and system to write/send?

*** UUPDATE********
Soooo Sucesss!
Was the mother front-dooring USB port the entire time. Tried it on another laptop /w Windows 7 and had issues, went back to my Winodws 8 and plugged it into my OTHER usb port (oddly enough, the USB 3.0 port) and SUCESS!!! Flashed the bootloader again (probably didn't need to but I wanted to for spite), flash recovery, flashed boot.img, flashed system.img, and started and now I am back at stock firmware ready to go play the dangerious game of custom roms again, since I never learn from my misfortunes.
Also oddly enough my data partition was taking up EVERYTHING too, so this might have added to the issues. Why it took up the entire free space on the internal sd I do not know, likely just a bunch of 0's for some reason or another. So formatting that through TWRP might have also helped.
For others who might run into this problem:
First of all wipe everything via fastboot or TWRP (i prefer fastboot in case)
fastboot erase system
fastboot erase data
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
then re-flash from the stock firmware from google (extract the .img files from the .zip on the tarball) and flash through flashboot
fastboot flash system system.img (or a custom ROM img if you'd like)
fastboot flash recovery recovery.img (or a custom recovery img if you'd like)
fastboot flash boot boot.img (or a custom boot img if you like)
MOST IMPORTANTLY IF YOU'RE NOT ABLE TO FLASH MAKE SURE YOU TRY OTHER USB PORTS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
HTH to anyone in the future

xdaNoobTutorial said:
*** UUPDATE********
Soooo Sucesss!
Was the mother front-dooring USB port the entire time. Tried it on another laptop /w Windows 7 and had issues, went back to my Winodws 8 and plugged it into my OTHER usb port (oddly enough, the USB 3.0 port) and SUCESS!!! Flashed the bootloader again (probably didn't need to but I wanted to for spite), flash recovery, flashed boot.img, flashed system.img, and started and now I am back at stock firmware ready to go play the dangerious game of custom roms again, since I never learn from my misfortunes.
Also oddly enough my data partition was taking up EVERYTHING too, so this might have added to the issues. Why it took up the entire free space on the internal sd I do not know, likely just a bunch of 0's for some reason or another. So formatting that through TWRP might have also helped.
For others who might run into this problem:
First of all wipe everything via fastboot or TWRP (i prefer fastboot in case)
fastboot erase system
fastboot erase data
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
then re-flash from the stock firmware from google (extract the .img files from the .zip on the tarball) and flash through flashboot
fastboot flash system system.img (or a custom ROM img if you'd like)
fastboot flash recovery recovery.img (or a custom recovery img if you'd like)
fastboot flash boot boot.img (or a custom boot img if you like)
MOST IMPORTANTLY IF YOU'RE NOT ABLE TO FLASH MAKE SURE YOU TRY OTHER USB PORTS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
HTH to anyone in the future
Click to expand...
Click to collapse
You just saved my ass! i was experiencing this exact problem! i could not for the life of me figure out why my shield tablet was flipping out when i tried to flash the system image! read this post, switched USB ports, and BOOM!
thanks dude!

Bootloop

Hi,
My phones memory was full and I didn't care much because I was really busy with other things in life. So i was moving away time to clean it up and flash another rom on it because the stock rom is a pain in the arsch.
Now my phone stays in a bootloop for almost 2 hours, already cleared cache. It loops until it shows "optimizing apps".
Is there any way to recovery a few photo's from my devices? I have not made a recent backup of a few photo's. I feel so bad now... It really sucks

So I got my phone to be detected after several bootloops when it starts the android OS and is "optimizing apps"..
So I quickly did adb reboot botloader
@ Echo off
adb reboot bootloader
fastboot -i 0x2b4c boot twrp.img
echo booting TWRP
pause >nul
And it now shows me :
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.328s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.343s
booting TWRP
Edit.. I am ****ed over now?
< waiting for device >
...
FAILED (remote: oem unlock is not allowed)
finished. total time: -0.000s
downloading 'boot.img'...
OKAY [ 0.320s]
booting...
FAILED (remote: bootimage: incomplete or not signed)
finished. total time: 0.320s
booting TWRP
Bootloader is locked
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ffs
Edit2:
my last idea and last hope for recovery is,
bootloop until "Android is being started, App x of x optimizing.."
open adb shell
push my fresh boot.img to the root direcotory
reboot to bootloader
open recovery
flash and hope for the best
all the files are still on the device, if I do adb shell I can see all files.. if this doesn't work I will have to do it manually !! x_x

NiTrOwow said:
Hi,
My phones memory was full and I didn't care much because I was really busy with other things in life. So i was moving away time to clean it up and flash another rom on it because the stock rom is a pain in the arsch.
Now my phone stays in a bootloop for almost 2 hours, already cleared cache. It looops until it shows "optimizing apps".
Is there any way to recovery a few phones from my devices? I have not made a recent backup of a few photo's. I feel so bad now... It really sucks
Click to expand...
Click to collapse
Seems you dirty flashed a new ROM over your actually rom which isn't the same as before. You can try to flashing the same rom within twrp again again.

strongst said:
Seems you dirty flashed a new ROM over your actually rom which isn't the same as before.
Click to expand...
Click to collapse
The bootloader is locked, and the Android rom is original. So this means your answer is not right.
I think the nandflash memory on the system partition went bad, when I go in recovery and look in the recovery log it shows me several blocks have been moved. I can't read or copy all of it to look carefully at it, but I still have adb shell access so there's a small chance to recovery a few photo's and call it a day (I hope).
I think I will buy the same model again and this time unlock the bootloader, flash a custom rom on it and keep regular backups (always good to do anyways).
PS the Android version I had on it was COS 12.1 from Lenovo itself.

NiTrOwow said:
The bootloader is locked, and the android rom is original. So this means your answer is not right.
I think the nandflash memory on the system partition went bad, when I go in recovery and look in the recovery log it shows me several blocks have been moved. I can't read or copy all of it to look carefully at it, but I still have adb shell access so there's a small chance to recovery a few photo's and call it a day (I hope).
I think I will buy the same model again and this time unlock the bootloader, flash a custom rom on it and keep regular updates.
Click to expand...
Click to collapse
I just give some thoughts based on your input
Save your pics and try to flash the stock rom again so the partition will be rewritten and see if there are really nand problems.

strongst said:
I just give some thoughts based on your input
Save your pics and try to flash the stock rom again so the partition will be rewritten and see if there are really nand problems.
Click to expand...
Click to collapse
Yes, I have tried this.
I got my hands on the shell, after a few reboots with a authorized machine (my Android dev VM).
So i had shell I did cat /system/build.prop
I verified that I had the same rom .zip. So I went intro recovery mode and did a ADB sideload. It failed somehow, because nothing changed.
The bootloader is locked too, I can't try a custom recovery like TWRP or others. I tried, but it gave me a error (see post 2).
So my last hope was do to lots of reboots until I gain adb shell access again. I did this, I tried to push the rom zip (700mb) to /sdcard. But before the transfer was complete the phone crashed again.
Maybe I can push two parts splitted in half and then rejoin them again and install it from recovery. If this doesn't work my last resort is to do recovery by shell, e.g list dirs, and pull the files I need (painful and a lot of work..)

I got lucky.. It worked, it now runs my ****ty script to scrape all missing files from the phone that I was missing in my last backup (also lots of bs like you see in the image below)..

RIP!

No OS installed mate 9

Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...

scrutnizing said:
Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...
Click to expand...
Click to collapse
Do you have adb/fastboot drivers installed? If not: https://forum.xda-developers.com/showthread.php?t=2317790
When you have that installed, boot into TWRP then tap on the Reboot button and then on the Bootloader button.
Plug in USB and open a command prompt, type the following command:
fastboot oem get-build-number
Post the result here

i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.

scrutnizing said:
i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.
Click to expand...
Click to collapse
Ah, then you're on Nougat.
The reason I asked about fastboot was to find out what build/fw you were on, then go from there to install stock firmware.
You could update to Oreo using: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108

hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.

scrutnizing said:
hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.
Click to expand...
Click to collapse
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/

ante0 said:
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/
Click to expand...
Click to collapse
@ante0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can you give a hand, please ?
I unlocked the bootloader and flashed the recovery, the system booted successfully.
I tried to flash a ROM after that, it showed errors and didn't complete the flashing. since that time the phone has bootloop.
Unlocked bootloader and FRP
fastboot oem get-build-number : MHA-L29 8.0.0.374(C185)
I can access the TWRP recovery and erecovery and bootloader&fastboot
what I have already tried :
1-Fastboot flash ramdisk and kernel .
2-Tried to flash the stock firmware via TWRP.
3-Tried HurUpdater0.3
4- Extract update.app & HOWTA
5-Flash ramdisk and kernel from inside TWRP

is possible unbrik Mate9 Oreo , using only fastboot method ?
can help umbrik only commands fastboot?

Recent Firmware Update Failed - Onn 7" Surf gen 2 10015685

Anybody else have the gen 2 7" Onn tablet from Walmart and get a recent firmware upgrade (within the past few weeks)?
I have two of these devices. I got them all set up and secured for my two young kids for Christmas presents. Between when I finished configuring them and Christmas morning, some kind of update was pushed out. Now every time I start them up, I get a notice to try to install a firmware upgrade. The kids can't bypass it easily and it has become quite the inconvenience. When I try to complete the update, it fails.
I'm running both the tablets with unlocked bootloaders and rooted with Magisk. I assume this is why the update fails. If it even is a real update. The link in the message goes to an RCA website that doesn't exist. I don't care about the update, but I hate that it tries to install it every time I boot up the tablets. I have disabled "Automatic System Updates" from Developer Options. I have the Google Play store disabling auto-updates as well. I don't want to re-lock the bootloader and have to then unlock it again, and re-install/configure the tablet from scratch again.
Anyone have any ideas on A) how to get the update to work or B) How to ignore the update and get it to stop bothering me? I'm happy to push a new system image if anyone has successfully figured out what can be updated.
Here's what is displayed on the screen and what the update process shows. My guess is the problem lies with the patched boot.img but I'm not ready to wipe it back to stock yet because I'm not good at pulling it back off. Luckily after failing to update I can reboot without trouble. Also I can dismiss this message easily, but my kids can't, and it seems to be unpredictable when it will actually pop up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I am having the same issue, but only on one of my two tablets. I haven't been able to figure it out either. I have tried to download it and apply from recovery. I have tried sideloading from ADB. Every time it fails. I haven't figured out how to ignore it either. The only time it seems to pop up is when I first start the tablet. I just use the nav bar to close the update window and go on.

Okiera29 said:
I am having the same issue, but only on one of my two tablets. I haven't been able to figure it out either. I have tried to download it and apply from recovery. I have tried sideloading from ADB. Every time it fails. I haven't figured out how to ignore it either. The only time it seems to pop up is when I first start the tablet. I just use the nav bar to close the update window and go on.
Click to expand...
Click to collapse
From the error messages I get I'm guessing it's a problem with the boot.img as it's patched by Magisk. I can reflash the stock boot.img but then I loose root. If it does update, I don't have root and am not skilled enough to pull the new updated boot.img without root.
If anyone out there has a good tutorial on doing that I'd be happy to try to get the new updated image files to flash.

I'm having a related issue with the same tablet (10015685-E): I got the request to update the firmware, accepted, it appeared to install over the course of ~5 minutes, and after reboot, it is now stuck in an infinite loop in which it boots to the onn logo screen, goes black, and repeats. I assume it's crashing during boot.
I am able to enter recovery mode (see attached pic), but doing a cache wipe and factory reset from the recovery screen did not remedy this sad state of affairs.
I'm happy to load a stock ROM if that would restore functionality, but I don't have one. Any advice welcome. Thanks.

chromoly said:
I'm having a related issue with the same tablet (10015685-E): I got the request to update the firmware, accepted, it appeared to install over the course of ~5 minutes, and after reboot, it is now stuck in an infinite loop in which it boots to the onn logo screen, goes black, and repeats. I assume it's crashing during boot.
I am able to enter recovery mode (see attached pic), but doing a cache wipe and factory reset from the recovery screen did not remedy this sad state of affairs.
I'm happy to load a stock ROM if that would restore functionality, but I don't have one. Any advice welcome. Thanks.
Click to expand...
Click to collapse
Do you have the stock ROM? You can try to just flash the boot.img which isn't altered during a factory reset. It would reverse the update but it appears the update isn't working anyway.

PleaseBeNicetoMe said:
Do you have the stock ROM? You can try to just flash the boot.img which isn't altered during a factory reset. It would reverse the update but it appears the update isn't working anyway.
Click to expand...
Click to collapse
I don't; I'd appreciate a link to the stock ROM or boot.img. Thanks.

chromoly said:
I don't; I'd appreciate a link to the stock ROM or boot.img. Thanks.
Click to expand...
Click to collapse
You can try my files from here
Google Drive: Sign-in
Access Google Drive with a Google account (for personal use) or Google Workspace account (for business use).
drive.google.com

PleaseBeNicetoMe said:
You can try my files from here
Google Drive: Sign-in
Access Google Drive with a Google account (for personal use) or Google Workspace account (for business use).
drive.google.com
Click to expand...
Click to collapse
Thanks. I got your files and tried a couple of things, neither of which worked:
I tried loading your stock image via ADB, but got "Signature verification failed. Error 21" after loading.
I tried flashing just magisk_patched boot.img via ADB in fastboot mode, but got "Download is not allowed on locked devices".
So perhaps the device has to be unlocked before #2 will work. Any thoughts on #1?
Thanks again.

chromoly said:
Thanks. I got your files and tried a couple of things, neither of which worked:
I tried loading your stock image via ADB, but got "Signature verification failed. Error 21" after loading.
I tried flashing just magisk_patched boot.img via ADB in fastboot mode, but got "Download is not allowed on locked devices".
So perhaps the device has to be unlocked before #2 will work. Any thoughts on #1?
Thanks again.
Click to expand...
Click to collapse
Did you try flashing the boot.img this way with the vbmeta.img first?
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase cache
fastboot flash boot boot.img
fastboot reboot

For all of those three fastboot commands (vbmeta, cache, boot), I get "not allowed on locked device" errors.
Also, do you have the stock boot.img, vs. "magisk_patched boot.img"?
I appreciate the help.
Code:
$ fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
target reported max download size of 536870912 bytes
sending 'vbmeta' (4 KB)...
FAILED (remote: Download is not allowed on locked devices)
finished. total time: 0.001s
$ fastboot erase cache
erasing 'cache'...
FAILED (remote: Erase is not allowed on locked devices)
finished. total time: 0.000s
$ fastboot flash boot boot.img
error: cannot load 'boot.img': No such file or directory
$ fastboot flash boot ../magisk_patched_boot.img
target reported max download size of 536870912 bytes
sending 'boot' (9152 KB)...
FAILED (remote: Download is not allowed on locked devices)
finished. total time: 0.000s

Ok, here's one. I have the same tablet, not rooted, not modified, just stock. The update fails because it says update.zip isn't found after the download... Anyone have a way to fix? After the error, the whole tablet locks up and I have to force reboot...

chromoly said:
For all of those three fastboot commands (vbmeta, cache, boot), I get "not allowed on locked device" errors.
Also, do you have the stock boot.img, vs. "magisk_patched boot.img"?
I appreciate the help.
Code:
$ fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
target reported max download size of 536870912 bytes
sending 'vbmeta' (4 KB)...
FAILED (remote: Download is not allowed on locked devices)
finished. total time: 0.001s
$ fastboot erase cache
erasing 'cache'...
FAILED (remote: Erase is not allowed on locked devices)
finished. total time: 0.000s
$ fastboot flash boot boot.img
error: cannot load 'boot.img': No such file or directory
$ fastboot flash boot ../magisk_patched_boot.img
target reported max download size of 536870912 bytes
sending 'boot' (9152 KB)...
FAILED (remote: Download is not allowed on locked devices)
finished. total time: 0.000s
Click to expand...
Click to collapse
The stock boot.img should be in the STOCK ROM .zip file in my GDrive folder above. I reuploaded it just in case.
My guess is the bootloader is locked. Did you unlock it before? Try running
fastboot flashing unlock
Follow the prompts. If that worked then try flashing vbmeta and the other steps from above. That's my only idea right now.

chromoly said:
For all of those three fastboot commands (vbmeta, cache, boot), I get "not allowed on locked device" errors.
Also, do you have the stock boot.img, vs. "magisk_patched boot.img"?
Click to expand...
Click to collapse
If you did not unlock your bootloader before all this happened, then I believe you will not be able to flash via fastboot commands. You can try to use the SP Flash Tool to install the earlier stock ROM. If you look through my thread from earlier, you will find a full dump of the original pre-update ROM
Try this post... Hang on, that was for the A variant. Look for a post by Fred, he dumped the entire ROM with scatter file(needed for SP tools to function properly) You may still need my super.img referenced below
Do not use the one from Tytydraco as it is for the A variant of the tablet and will cause some screwy issues(personal experience on my E variant) If you are looking for the super.img you can use the one I pulled from my tablet.
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader
Onn Surf 7" gen 2 on sale for 28$ today. Bought one... Was able to unlock bootloader So, stopped at walmart this morning for stuff and saw the Onn Surf is now on Gen 2. 2.0 GHz quad core, 16gb storage and 2 gb ram. Seemed pretty decent for...
forum.xda-developers.com

Okiera29 said:
I am having the same issue, but only on one of my two tablets. I haven't been able to figure it out either. I have tried to download it and apply from recovery. I have tried sideloading from ADB. Every time it fails. I haven't figured out how to ignore it either. The only time it seems to pop up is when I first start the tablet. I just use the nav bar to close the update window and go on.
Click to expand...
Click to collapse
We're you ever able to find a work around? I may have fixed it, at least this works for me because I don't care about the update ever. I don't know your level of expertise with these. I'm definitiely just proficient enough to be dangerous. I can give more details than this if you need it.
You'll need a rooted tablet with Magisk and the Terminal Debloater (Terminal Emulator) module installed.
Start your Terminal Emulator app (I use Termux), type su (grant superuser if you haven't already) and start the Debloater by typing "debloat"
From the menu I choose 1 - System Apps and for me on the second menu #13 is Firmware Update
Choose that to uninstall, restart the tablet, and the popup error is gone!
This works for me for my 7" version. I have a 10" version too that doesn't have the same app, but it's called Wireless Update, and I uninstalled that using the same process successfully.
It's a great way to ge tall those pesky Walmart apps off too, PLUS I disabled the extra Walmart nav button (It didn't disappear but nothing happens when tapped, so it's one less thing to help my kids escape from when they get stuck in it).
Hope this helps a bit.

PleaseBeNicetoMe said:
We're you ever able to find a work around? I may have fixed it, at least this works for me because I don't care about the update ever. I don't know your level of expertise with these. I'm definitiely just proficient enough to be dangerous. I can give more details than this if you need it.
You'll need a rooted tablet with Magisk and the Terminal Debloater (Terminal Emulator) module installed.
Start your Terminal Emulator app (I use Termux), type su (grant superuser if you haven't already) and start the Debloater by typing "debloat"
From the menu I choose 1 - System Apps and for me on the second menu #13 is Firmware Update
Choose that to uninstall, restart the tablet, and the popup error is gone!
This works for me for my 7" version. I have a 10" version too that doesn't have the same app, but it's called Wireless Update, and I uninstalled that using the same process successfully.
It's a great way to ge tall those pesky Walmart apps off too, PLUS I disabled the extra Walmart nav button (It didn't disappear but nothing happens when tapped, so it's one less thing to help my kids escape from when they get stuck in it).
Hope this helps a bit.
Click to expand...
Click to collapse
Worked like a champ on both tablets. I only use them for reading, light gaming and watching youtube in bed. So like you, the updates are not imperative for me.

I Cant install twrp on my moto g6 plus!

Hello every one!
i cant install my twrp and i need help
C:\Users\admin\OneDrive\Desktop\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
(bootloader) slot-suffi: not found
target reported max download size of 536870912 bytes
sending 'recovery' (29252 KB)...
FAILED (remote: unknown command)
finished. total time: 0.003s
the file what i used
https://eu.dl.twrp.me/evert/twrp-3.2.3-0-evert.img.html (i renamed file name to twrp.img)
UPDATE!!!!!!!!
i have boot file but i cant install twrp permanently
UPDATE 2!!!!!!!
my computer does not recognize my phone

Install LineageOS on evert | LineageOS Wiki
wiki.lineageos.org
I don't have the device, but the manual says to flash to the boot partition, not to recovery.

ze7zez said:
Install LineageOS on evert | LineageOS Wiki
wiki.lineageos.org
I don't have the device, but the manual says to flash to the boot partition, not to recovery.
Click to expand...
Click to collapse
ok i will try

Seems you have downloaded the website instead of the recovery
(Therefore the ending with *.html. Changing the filename won't change the filetype...)
On your mentioned website, click on the download-link which is named
Download twrp-3.7.0_9-0-evert.img​Now you should get a file, which is really a *.img

ze7zez said:
Install LineageOS on evert | LineageOS Wiki
wiki.lineageos.org
I don't have the device, but the manual says to flash to the boot partition, not to recovery.
Click to expand...
Click to collapse
it didnt work

chrysopra said:
Seems you have downloaded the website instead of the recovery
(Therefore the ending with *.html. Changing the filename won't change the filetype...)
On your mentioned website, click on the download-link which is named
Download twrp-3.7.0_9-0-evert.img​Now you should get a file, which is really a *.img
Click to expand...
Click to collapse
i can just delete ".html" in my link or add it to yours so tell me how does it works?
just saying

For me the easiest way to install twrp and not break anything is to download the installer zip and img rename the img to twrp.img then copy the installer zip to sd card and use "fastboot boot twrp.img" while in fastboot then click on install and install the zip.

Perhaps you could try downloading fom an alternative site:
Download TWRP for evert
Download TWRP Open Recovery for evert
dl.twrp.me
I wonder, if you got a complete file. Download-size is 32.5 MB. Sending recovery command gave a lower value (29252 KB) . Maybe itś correct and there is some file-overhead, but itś worth a try...?

10Maximus10 said:
For me the easiest way to install twrp and not break anything is to download the installer zip and img rename the img to twrp.img then copy the installer zip to sd card and use "fastboot boot twrp.img" while in fastboot then click on install and install the zip.
Click to expand...
Click to collapse
i tryed to boot twrp but it didnt work

Unknown_PL said:
i tryed to boot twrp but it didnt work
Click to expand...
Click to collapse
Uninstall Minimal ADB and Fastboot, check if you have unlocked the bootloader and use >Google platform-tools<.
In addition to the comment "does not work", include the results of your commands.
Nobody but you can see them.

Unknown_PL said:
Hello every one!
i cant install my twrp and i need help
Click to expand...
Click to collapse
Yeah flashing twrp on boot worked, but now i cant turn on system

I recently ran into a similar situation. Try booting into recovery. In TWRP check if the Folder "data" is mounted. On my device, the 3.7.0 had problems. Formatting data as ext2 and back to ext4 made it readable, although of course formatting deleted all data. That worked until the next boot...
Solution was, to flash an older version of TWRP (3.2.x), afterwards it could be reflashed with the most recent version which now worked without problems.
Also, on some systems, if you flash TWRP once and try to reboot into System, the boot partition is being "repaired" by your system an TWRP is gone...

chrysopra said:
I recently ran into a similar situation...
Click to expand...
Click to collapse
then what i need to do?
use 3.2.3-0 and flash it to the boot?

Exactly. Flash 3.2, reboot into recovery. Within TWRP you can mount USB drive, which lets you easy install anything else. (TWRP 3.7, root, ROM...)

Unknown_PL said:
use 3.2.3-0 and flash it to the boot?
Click to expand...
Click to collapse
Did you ever heard of A/B slots? The Moto G6+ uses A/B slots and does not have a partition /recovery. Of course there is a recovery but it 's merged in the boot.img. So the boot.img is able to boot into recovery and also into system.
Your TWRP image is recovery only and isn't able to boot into system!
***
What will happen when flashing TWRP to partition /boot?
In that case your boot.img = twrp.img and will only boot into recovery.
How to install TWRP permanently on your device?
First of all you should have a look at https://twrp.me/motorola/motorolamotog6plus.html
TWRP provides an installation guide for every device and it´s recommended to follow these steps.
***
Here´s a more detailed guide:
1. In your case you have to restore the boot.img since it got overwritten by flashing your twrp.img to /boot.
If available use a backup of /boot. Otherwise flash the stock boot.img from your current running firmware version. Firmware builds can be found here:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
(take care of your software channel, i.e. RETUS)
*** Be aware that by flashing your stock boot.img Magisk will be deinstalled from ***
your device and as a result of this you will LOOSE ROOT ACCESS!! ​
2. Run
fastboot boot <TWRP.IMG>
3. On TWRP main screen go to Advanced => Install Recovery Ramdisk and pick the twrp.img:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

WoKoschekk said:
Did you ever heard of A/B slots? The Moto G6+ uses A/B slots and does not have a partition /recovery. Of course there is a recovery but it 's merged in the boot.img...
Click to expand...
Click to collapse
Yeah I think that will work but you need other link beauce that one twrp link is not working
Can I try it on normal evert twrp link?
And what one folder (from lolnet) should I pick?

Unknown_PL said:
Yeah I think that will work but you need other link beauce that one twrp link is not working
Click to expand...
Click to collapse
It's fixed.
Unknown_PL said:
And what one folder (from lolnet) should I pick?
Click to expand...
Click to collapse
It depends on your software channel:
RETAIL = general software build, w/o any region
RETUS = builds for U.S. region
RETIN = builds for India region
...and so on.
Beside that, there are also builds for carrier branded phones.
To find your software channel:
a) Open a terminal app and run
getprop ro.carrier
b) settings > about the phone > software channel
c) fastboot getvar all has also an entry for that, but I don't know exactly what name it is.
d) the specific model no.: XT1926-???
The last digit depends on your software channel.

WoKoschekk said:
It's fixed.
It depends on your software channel...
Click to expand...
Click to collapse
Well I booted twrp and install recovery rom but what file from lolnet should I pick i know what folder but where are 4 files and I don't know what I need to do

Unknown_PL said:
but where are 4 files and I don't know what I need to do
Click to expand...
Click to collapse
I don't know what you mean. What folder? Which 4 files? The downloaded firmware is a ZIP file with one folder inside. Inside that folder are more than 20 files.

WoKoschekk said:
I don't know what you mean. What folder? Which 4 files? The downloaded firmware is a ZIP file with one folder inside. Inside that folder are more than 20 files.
Click to expand...
Click to collapse
sorry i mean there not were and i used RETEU and there is 5 files