My Venue 8 started with a whiter bar at the bottom of the screen. I've updated it as this link "opensource.dell.com/releases/Venue_8_3840_Merrifield". It's ok but slowly. So I edit some line in "P802_flash_device_wifi_only.bat". I added 2 line "fastboot erase config" and "fastboot erase factory" in partitioning command. After that, my Venue can't boot. After Dell logo, screen is black. It still can go to fastboot. I try flash rom again with original "P802_flash_device_wifi_only.bat" but there is no diffrence. May 2 lines I added cause this problem? If so, how to resolve the problem? Please help me.
original "P802_flash_device_wifi_only.bat"
Code:
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase cache
fastboot erase data
fastboot erase logs
fastboot oem stop_partitioning
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash splashscreen_7 oemlogo_7.bin
fastboot flash splashscreen_8 oemlogo_8.bin
fastboot flash dnx dnx_fwr_PRQ.bin
fastboot flash ifwi for_product_ifwi_PRQ.bin
pause
fastboot reboot
Related
Was wondering if someone can explain the difference in the set of commands, as I see it on different guides in regards to flashing a new rom. does "Flashing" a partition technically erase it, overwrite it? Overwrite it leaving extra junk behind?
Code:
>fastboot erase boot
>fastboot erase recovery
>fastboot erase system
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
VS
Code:
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
Necro bump
morbid_bean said:
Was wondering if someone can explain the difference in the set of commands, as I see it on different guides in regards to flashing a new rom. does "Flashing" a partition technically erase it, overwrite it? Overwrite it leaving extra junk behind?
Code:
>fastboot erase boot
>fastboot erase recovery
>fastboot erase system
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
VS
Code:
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Lemme see if I can shed a little light...
>fastboot erase boot - Tells fastboot to erase the boot partition
>fastboot erase recovery - Tells fastboot to erase the recovery partition
>fastboot erase system
>fastboot flash system system.img - Tells fastboot to flash the system partition with system.img
>fastboot flash boot boot.img - Tells fastboot to flash the boot partition with boot.img
>fastboot flash recovery recovery.img
Flashing a partition overwrites the existing contents. I should mention that using fastboot to install a ROM is a slow way to go. Fastboot is typically used for quick simple flashes or repairs, like changing your kernel/boot image. Also, fastboot makes a device practically unbrickable.
Yes they are different, read:
The flash command shouldn't erase the partition unless the host fastboot tool sends an erase command first. This allows flashing a very large partition in multiple smaller chunks using multiple sparse images that start with a "skip" block to seek over the already-written area. Creating these images on demand is already handled by the fastboot host side tool.
This is from https:// source.android.com/devices/bootloader/images
(fill in the space, they wouldnt let me post a url)
Hi guys, I've tried all the threads so far and have got no where. I unlocked my device and flashed a custom rom, that worked fine. I then noticed no way to go back to stock so I tried the odexed version with no luck. Now any rom I flash does not boot, just loops back to twrp. I would like to get as close to stock as possible even if it's another region. Has anyone had any luck on getting their phones booting after this?
I've tried flashing stock firmware from 6.0.1 then flashing ota through side load
Flashing other countries firmware (which always ends in fail messages)
I've tried multiple rom from the forum which just loop.
I've spent about 6 hours trying different combinations of recovery, boot and other images with no luck.
Any help is appreciated.
Sent from my iPhone using Tapatalk
criptix said:
Hi guys, I've tried all the threads so far and have got no where. I unlocked my device and flashed a custom rom, that worked fine. I then noticed no way to go back to stock so I tried the odexed version with no luck. Now any rom I flash does not boot, just loops back to twrp. I would like to get as close to stock as possible even if it's another region. Has anyone had any luck on getting their phones booting after this?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I have gotten stuck with bootloops a couple times now, for me re-flashing a backup or custom rom or custom kernel didn't fix it either. Keep in mind that you cannot go back to 6.0.1 once you have flashed 7.0, the bootloader won't allow it. I have had to flash back to a stock firmware from https:// firmware.center/firmware/Motorola/Moto%20Z/Stock/XT1650-03/ (remove the space after https:// ) and re-fastboot flash TWRP, re-root, and restore my Titanium Backups to get going again.
It's extremely helpful if you create a servicefile.bat to flash all the firmware parts in the right order. This is the one I made for flashing the RETMX 7.0 image (the main difference I noticed between different firmwares from that link is the number of sparsechunks, so add or delete lines as necessary. I'm sure all this info is available elsewhere, but I didn't manage to find it all in one shot. So I figured I would post it to help others out that are in the same boat. Also note that even though you are re-flashing the bootloader.img it does not re-lock your bootloader.
Code:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash oem oem.img
fastboot erase carrier
fastboot oem fb_mode_clear
pause
fastboot reboot
exit
Copy the above text and paste it into a new text file and change the name to "servicefile.bat" without quotes (not servicefile.bat.txt), and drop it in with the extracted firmware files. Then either copy-paste your adb and fastboot files into that folder or drop all that folder's contents into your Users/*YOURNAME*/App Data/Local/Android/sdk/platform-tools/ folder. Or better yet, add "%USERPROFILE%\AppData\Local\Android\sdk\platform-tools" to your Path in your system's Environment Variables. The latter will make adb and fastboot work from any command prompt window, then you can just press shift+right-click in the folder that already has the firmware files and choose "Open command window here" and then just type servicefile.bat and press enter. Hope this helps! Good Luck and Happy Flashing!
HippieFlasher said:
I have gotten stuck with bootloops a couple times now, for me re-flashing a backup or custom rom or custom kernel didn't fix it either. Keep in mind that you cannot go back to 6.0.1 once you have flashed 7.0, the bootloader won't allow it. I have had to flash back to a stock firmware from https:// firmware.center/firmware/Motorola/Moto%20Z/Stock/XT1650-03/ (remove the space after https:// ) and re-fastboot flash TWRP, re-root, and restore my Titanium Backups to get going again.
It's extremely helpful if you create a servicefile.bat to flash all the firmware parts in the right order. This is the one I made for flashing the RETMX 7.0 image (the main difference I noticed between different firmwares from that link is the number of sparsechunks, so add or delete lines as necessary. I'm sure all this info is available elsewhere, but I didn't manage to find it all in one shot. So I figured I would post it to help others out that are in the same boat. Also note that even though you are re-flashing the bootloader.img it does not re-lock your bootloader.
Code:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash oem oem.img
fastboot erase carrier
fastboot oem fb_mode_clear
pause
fastboot reboot
exit
Copy the above text and paste it into a new text file and change the name to "servicefile.bat" without quotes (not servicefile.bat.txt), and drop it in with the extracted firmware files. Then either copy-paste your adb and fastboot files into that folder or drop all that folder's contents into your Users/*YOURNAME*/App Data/Local/Android/sdk/platform-tools/ folder. Or better yet, add "%USERPROFILE%\AppData\Local\Android\sdk\platform-tools" to your Path in your system's Environment Variables. The latter will make adb and fastboot work from any command prompt window, then you can just press shift+right-click in the folder that already has the firmware files and choose "Open command window here" and then just type servicefile.bat and press enter. Hope this helps! Good Luck and Happy Flashing!
Click to expand...
Click to collapse
Dude, you are awesome. Worked like a charm. Was missing fastboot getvar max-sparse-size andbfastboot oem fb_mode_set plus I was flashing the modem after the chunks. Thanks again!
Sent from my iPhone using Tapatalk
Anytime! Glad I could help!
As the Title suggests , its better not to unlock the bootloader for rooting, if you plan to re-sell the phone, because till now there has not been found any sure shot way to lock the bootloader again.
The motorola official site does'nt have the stock firmware for Moto Z2 Play variants yet, so until then atleast, please be patient.
For me, the only reason to maintain bootloader locked is the garantee.
totally fake, u can relock it, use any retail firmware and this commands
@Echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot flash modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash boot boot.img
fastboot oem lock
fastboot oem fb_mode_clear
pause
PAUSE
fastboot reboot
EXIT /b 0
I've sold several phones with unlocked bootloaders.
What's your worry?
This are the comands to lock bootloader without loose the imei, after lineageOS.
Comands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash boot boot.img
fastboot oem lock
I have successfully been able to Lock the Bootloader and return to stock rom like a new Moto Z2 Play ,
Thanks to xda member Kacike27 , i dowloaded the Firmware he has posted the link for, and followed all the steps in his thread
https://forum.xda-developers.com/z2-play/how-to/close-bootloader-lineageos-losing-imei-t3769479
DISCLAIMER
I am not to be held responsible for any of the damage that occurs to your device during this process. You are yourself responsible for any damage done (if) to your device during this process.
REQUIREMENTS
1. Make sure your device is charged above 80%.
2. We recommend creating a backup of all your important files before beginning with this process.
HOW TO INSTALL STOCK ROM IN MOTO G5 PLUS And LOCK THE BOOT LOADER
1. Download Moto G5s Plus Stock Firmware and other necessary files from the download link.
2. Extract and install ABD Fastboot Drivers drivers
3. Install ADB Fastboot Driver on your PC.
4. Install the Latest Motorola Drivers
5. Now extract stock firmware in ADB Fastboot folder
6. Now, turn off your device and boot into bootloader by pressing volume down button +power button simultaneously.
7. Now, connect your device to your PC via a USB Cable.
8. Open a command prompt or PowerShell window and type the following commands:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Now Setup the phone properly till you reach the main screen, don't skip any steps
Now use this second command
Code:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash boot boot.img
fastboot oem lock
Flash the phone again with the first command and set it up again then boot to the fastboot again and flash the phone twice with the second command and your Motorola G5S PLUS should have a locked bootloader, keep in mind older Firmware would not work for this process to work, if you see any errors regarding bootloader.img not signed, don't worry and proceed with it.
Downloads:
HTML:
https://drive.google.com/drive/folders/1lWCQAjZBXM_iYHNwBO-5xKU4RY1FK9QV?usp=sharing
Kindly copy the full link to your browser and download the files, all the required files are present on the link
WIsh you guys all the best, I locked my bootloader the same and hope it will solve your problems too if you follow the instructions properly, I am no developer, I learned the hardway
Please Rate and comment if you liked my post helped you.
Shampak said:
DISCLAIMER
I am not to be held responsible for any of the damage that occurs to your device during this process. You are yourself responsible for any damage done (if) to your device during this process.
REQUIREMENTS
1. Make sure your device is charged above 80%.
2. We recommend creating a backup of all your important files before beginning with this process.
HOW TO INSTALL STOCK ROM IN MOTO G5 PLUS And LOCK THE BOOT LOADER
1. Download Moto G5s Plus Stock Firmware and other necessary files from the download link.
2. Extract and install ABD Fastboot Drivers drivers
3. Install ADB Fastboot Driver on your PC.
4. Install the Latest Motorola Drivers
5. Now extract stock firmware in ADB Fastboot folder
6. Now, turn off your device and boot into bootloader by pressing volume down button +power button simultaneously.
7. Now, connect your device to your PC via a USB Cable.
8. Open a command prompt or PowerShell window and type the following commands:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Now Setup the phone properly till you reach the main screen, don't skip any steps
Now use this second command
Code:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash boot boot.img
fastboot oem lock
Flash the phone again with the first command and set it up again then boot to the fastboot again and flash the phone twice with the second command and your Motorola G5S PLUS should have a locked bootloader, keep in mind older Firmware would not work for this process to work, if you see any errors regarding bootloader.img not signed, don't worry and proceed with it.
Downloads:
HTML:
https://drive.google.com/drive/folders/1lWCQAjZBXM_iYHNwBO-5xKU4RY1FK9QV?usp=sharing
Kindly copy the full link to your browser and download the files, all the required files are present on the link
WIsh you guys all the best, I locked my bootloader the same and hope it will solve your problems too if you follow the instructions properly, I am no developer, I learned the hardway
Please Rate and comment if you liked my post helped you.
Click to expand...
Click to collapse
hi, i have tried the same as you gave command. but unfortunately it doesn't work for me. i had installed soak test OREO then moved to Android P custom ROM, finally rolled back to android N to relock the bootloader. now i couldn't relock it.
i am getting error "still require valid signed image"
i am using sanders.
kindly assist me
Thanks
---------- Post added at 06:39 PM ---------- Previous post was at 06:35 PM ----------
hi, i have tried the same as you gave command. but unfortunately it doesn't work for me. i had installed soak test OREO then moved to Android P custom ROM, finally rolled back to android N to relock the bootloader. now i couldn't relock it.
i am getting error "still require valid signed image"
i am using sanders.
kindly assist me
Thanks
arunkumar.rp said:
hi, i have tried the same as you gave command. but unfortunately it doesn't work for me. i had installed soak test OREO then moved to Android P custom ROM, finally rolled back to android N to relock the bootloader. now i couldn't relock it.
i am getting error "still require valid signed image"
i am using sanders.
kindly assist me
Thanks
---------- Post added at 06:39 PM ---------- the Previous post was at 06:35 PM ----------
hi, I have tried the same as you gave the command. but unfortunately, it doesn't work for me. i had installed soak test OREO then moved to Android P custom ROM, finally rolled back to android N to relock the bootloader. now I couldn't relock it.
i am getting the error "still require valid signed image"
i am using sanders.
kindly assist me
Thanks
Click to expand...
Click to collapse
Don't worry about the signed image. Try the locking command twice back to back. Hope this helps
how to remove a custom operating system from a Motorola g power (2021) phone?
jazzybird2009 said:
how to remove a custom operating system from a Motorola g power (2021) phone?
Click to expand...
Click to collapse
If you did a nandroid backup (e.g., TWRP etc.), do a full 'clean restore (i.e., wipe cache, Dalvik cache, system AND format data > Yes (important).
If not, do the same full wipe, reboot to fastboot and flash the stock rom. You could also try the Motorola "Rescue and Smart Assistant" but I'm not sure it will work in your particular case.
If you want to go back to stock ROM or "OS" consider this method unofficial works on RETCA not sure about other devices, Verizon for sure needs its own software, The requirements of this method are Windows 10/11, Motorola's USB Drivers and a working Fastboot. Download the stock ROM from here https://mirrors.lolinet.com/firmware/motorola/borneo/ match the model of the device, Extract the firmware guessing it's in Downloads folder open that folder in the Terminal here's an example "cd C:\Users\smoke\Downloads" then here are commands to flash converted from the xml files
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
This has worked for me never had a problem don't expect the same outcome, I would read the terms and services you agreed to when unlocking the bootloader.
Mind if I ask what custom ROM you were using? I haven't seen any for this phone yet