Database Info

OTA caused a boot loop?

My boot loader is unlocked and am rooted with the stock recovery. My model is XT1550 (dual sim variant in India). I received the OTA updates today.. I downloaded them and installed.. The installation looked like it went fine.. after the installation the phone restarted.. but it kind of went to a boot loop after that.. I can power off the phone pressing the power button for some time.. bu the phone powers off and restarts automatically... it does not progress beyond the few initial screens after which it just displays a blank display...
I am able to get into flashmode.. however, my pc does not recognize the device.. adb terminal shows no devices when I give "adb devices" command.. can someone help? Can I do a factory reset from the flashboot menu? what does the factory mode do? what else can be done to salvage the situation? Thanks.
Update: I went into the stock recovery and did a factory reset. It wiped the user data and did a factory reset. After this I tried rebooting the system. But again the same problem. The phone starts and after the first two -three screens of a boot animation it simply gives me a blank screen display. Really worried now.. Any help?

Flash STOCK FIRMWARE
coolmalayalee said:
My boot loader is unlocked and am rooted with the stock recovery. My model is XT1550 (dual sim variant in India). I received the OTA updates today.. I downloaded them and installed.. The installation looked like it went fine.. after the installation the phone restarted.. but it kind of went to a boot loop after that.. I can power off the phone pressing the power button for some time.. bu the phone powers off and restarts automatically... it does not progress beyond the few initial screens after which it just displays a blank display...
I am able to get into flashmode.. however, my pc does not recognize the device.. adb terminal shows no devices when I give "adb devices" command.. can someone help? Can I do a factory reset from the flashboot menu? what does the factory mode do? what else can be done to salvage the situation? Thanks.
Update: I went into the stock recovery and did a factory reset. It wiped the user data and did a factory reset. After this I tried rebooting the system. But again the same problem. The phone starts and after the first two -three screens of a boot animation it simply gives me a blank screen display. Really worried now.. Any help?
Click to expand...
Click to collapse
Hi, I have faced the same issue that you have faced. I will be resorting to flashing original STOCK ROM using the ADB commands.
There are other threads in this forum explaining the procedure.
Don't worry. If you follow the procedure correctly you will be able to reinstall the system and use your phone again.
After flashing STOCK ROM and before installing OTA update, please ensure that your phone has stock recovery and is not rooted. Other wise you will face similar issue.
To go to fastboot mode from the blank screen mode you may follow the steps below:
1. Keep the power key pressed for a few seconds till you can see that the screen has gone completely black (otherwise you will see the screen dimly lit)
2. Immediately after this step press the volume down button first followed by power button and hold for a second or two and release the buttons, you would be in the fastboot mode
3. You can connect your phone to the PC in this mode to flash the STOCK ROM using the flash boot commands
4. You will find the STOCK ROM in the following link
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
5. For installation procedure and fastboot commands refer this link:
http://www.gammerson.com/2015/08/how-to-flash-stock-firmware-of-Moto-g-3rd-gen.html
Hope this helps

arunhebbare; said:
Hi, I have faced the same issue that you have faced. I will be resorting to flashing original STOCK ROM using the ADB commands.
There are other threads in this forum explaining the procedure.
Don't worry. If you follow the procedure correctly you will be able to reinstall the system and use your phone again.
After flashing STOCK ROM and before installing OTA update, please ensure that your phone has stock recovery and is not rooted. Other wise you will face similar issue.
To go to fastboot mode from the blank screen mode you may follow the steps below:
1. Keep the power key pressed for a few seconds till you can see that the screen has gone completely black (otherwise you will see the screen dimly lit)
2. Immediately after this step press the volume down button first followed by power button and hold for a second or two and release the buttons, you would be in the fastboot mode
3. You can connect your phone to the PC in this mode to flash the STOCK ROM using the flash boot commands
4. You will find the STOCK ROM in the following link
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
5. For installation procedure and fastboot commands refer this link:
http://www.gammerson.com/2015/08/how-to-flash-stock-firmware-of-Moto-g-3rd-gen.html
Hope this helps
Click to expand...
Click to collapse
Thanks a lot. I can get into fastbot mod. However, when I type adb devices from the command prompt it doesnt list any devices. Will I be able to flash anything in such a situation? I already have the stock firmware extracted to my adb folder.
Update: I have flashed the stock firmware successfully. The device is back up and running now.. thanks a lot..

coolmalayalee said:
Thanks a lot. I can get into fastbot mod. However, when I type adb devices from the command prompt it doesnt list any devices. Will I be able to flash anything in such a situation? I already have the stock firmware extracted to my adb folder.
Update: I have flashed the stock firmware successfully. The device is back up and running now.. thanks a lot..
Click to expand...
Click to collapse
Can you please let us know what you did to over come the problem of your device not being able to be recognized by ADB fastboot?
Also which STOCK firmware did you use (there are two in the link)?
Could you download and update via the OTA?
Your reply would help others. Thanks

arunhebbare said:
Can you please let us know what you did to over come the problem of your device not being able to be recognized by ADB fastboot?
Also which STOCK firmware did you use (there are two in the link)?
Could you download and update via the OTA?
Your reply would help others. Thanks
Click to expand...
Click to collapse
Well, after getting into fastboot when I use the command "adb devices" it did not show anything under the list of devices. However, when I started giving the commands for flashing the stock firmware it was accepting the adb commands. I followed the commands here.
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
and I used the stock firmware XT1550_OSPREY_RETASIA-INDIA_DS_2GB_5.1.1_LPI23.72-47_cid7 for this purpose downloaded from
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 things were alright. But I need to say that the first command "fastboot flash partition gpt.bin" did fail in fastboot. But I went ahead and gave all the subsequent commands all of which were successful and in the end I was able to restart with the new factory image.
However, all my data lost, root lost, and my boot loader is still in unlocked status.
About OTAs, I don't know. I went to the system updates to see if there is an OTA.. it says my software is up to date.

Thanks
That was a fast reply. Thanks for elaborating.
Don't know what the consequences of not being able to flash the gpt.bin are...
I will post update after flashing stock rom after reaching home. Stuck in office still...

Hello,
A little info about adb/fastboot :
adb works only after boot.
fastboot works in fastboot mode.
When you boot to fastboot mode and try commands such as "adb devices" you won't see any output or may get an error as the device is connected in fastboot mode.
So using "fastboot devices" will return all device ids connected in fastboot mode.
Hope this helps other new users.

arunhebbare said:
That was a fast reply. Thanks for elaborating.
Don't know what the consequences of not being able to flash the gpt.bin are...
I will post update after flashing stock rom after reaching home. Stuck in office still...
Click to expand...
Click to collapse
This is the message I get after gpt.bin flashing.
sending 'partition' (32 KB)...
OKAY [ 0.059s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
Click to expand...
Click to collapse
Below is a response I saw in reddit on this error. Looks like it should be fine.
That normally happens when you try to downgrade. GPT.bin and motoboot should fail to flash if you're trying to downgrade; prevent a hardbrick. As long as all the other commands are flashing successfully you'll be fine.
Click to expand...
Click to collapse
https://www.reddit.com/r/MotoG/comments/3dxmso/xt_1032_mfastboot_preflash_validation_failed/

Edit: Deleted

Flashed Stock rom. up and about
I flashed the stock 23.72.47 version using fastboot commands.
The flashing of gpt.bin failed but all the other commands were successful.
I had unlocked my bootloader previously which is still showing as unlocked.
Yes, I made a mistake of using adb commands in fastboot. In bootloader we got to use fastboot commands and adb does not work.
I respect this forum for these exact reasons that things are no nonsense here and this is the place for really knowledgeable people.
Thanks for bearing noobs like me.
Lastly my beloved moto g3 is up and about and doing fine.
Oh BTW I too checked for updates and found that the the stock rom 23.72.47 seems to be the updated version with the Ota incorporated. Earlier I was on the 23.72.33 rom.
Thank you members.

boot loupe due to an update
i was used all commands in cmd prompt but in in cmd prompt it was saying like that
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
error: cannot load 'gpt.bin': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash motoboot motoboot.img
target reported max download size of 268435456 bytes
error: cannot load 'motoboot.img': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
error: cannot load 'logo.bin': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
error: cannot load 'boot.img': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
error: cannot load 'recovery.img': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash system system.img_spar
sechunk1
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparsechunk1': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash system system.img_spar
echunk2
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparechunk2': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash system system.img_spar
sechunk3
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparsechunk3': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
error: cannot load 'NON-HLOS.bin': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.062s]
finished. total time: 0.085s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
error: cannot load 'fsg.mbn': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.119s]
finished. total time: 0.120s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.975s]
finished. total time: 0.976s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot reboot
< waiting for device >
rebooting...
finished. total time: 0.007s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>
i was tried a lot in my motog3 device after rebooting also it was showing blank dimly light it was not turning on my device had got a ota update so i was updated after that update i was installed then restarted the mobile after that it was no starting at all showing blank in that case also i was factory data reset my phone in recovery mode but still also it was restating with moto logo and then showing blank please help

Out of curiosity I flashed the 23.72.33 and updated via ota. The version it shows is 23.72-47.4.
Observing the ota results.

pranaykumar3318 said:
i was used all commands in cmd prompt but in in cmd prompt it was saying like that
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
error: cannot load 'gpt.bin': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash motoboot motoboot.img
target reported max download size of 268435456 bytes
error: cannot load 'motoboot.img': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
error: cannot load 'logo.bin': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
error: cannot load 'boot.img': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
error: cannot load 'recovery.img': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash system system.img_spar
sechunk1
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparsechunk1': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash system system.img_spar
echunk2
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparechunk2': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash system system.img_spar
sechunk3
target reported max download size of 268435456 bytes
error: cannot load 'system.img_sparsechunk3': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
error: cannot load 'NON-HLOS.bin': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.062s]
finished. total time: 0.085s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
error: cannot load 'fsg.mbn': No error
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.119s]
finished. total time: 0.120s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.975s]
finished. total time: 0.976s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>fastboot reboot
< waiting for device >
rebooting...
finished. total time: 0.007s
C:\Users\Admin\Desktop\Mfastboot\Mfastboot>
i was tried a lot in my motog3 device after rebooting also it was showing blank dimly light it was not turning on my device had got a ota update so i was updated after that update i was installed then restarted the mobile after that it was no starting at all showing blank in that case also i was factory data reset my phone in recovery mode but still also it was restating with moto logo and then showing blank please help
Click to expand...
Click to collapse
Try it again using fastboot not mfastboot

i was done
thanks friend i was done finally i was installed stock firmwere thanks to xda developers
---------- Post added at 02:14 PM ---------- Previous post was at 02:00 PM ----------
arunhebbare said:
Hi, I have faced the same issue that you have faced. I will be resorting to flashing original STOCK ROM using the ADB commands.
There are other threads in this forum explaining the procedure.
Don't worry. If you follow After flashthe procedure correctly you will be able to reinstall the system and use your phone again.
after installing STOCK ROM and before installing OTA update, please ensure that your phone has stock recovery and is not rooted. Other wise you will face similar issue.
To go to fastboot mode from the blank screen mode you may follow the steps below:
1. Keep the power key pressed for a few seconds till you can see that the screen has gone completely black (otherwise you will see the screen dimly lit)
2. Immediately after this step press the volume down button first followed by power button and hold for a second or two and release the buttons, you would be in the fastboot mode
3. You can connect your phone to the PC in this mode to flash the STOCK ROM using the flash boot commands
4. You will find the STOCK ROM in the following link
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
5. For installation procedure and fastboot commands refer this link:
http://www.gammerson.com/2015/08/how-to-flash-stock-firmware-of-Moto-g-3rd-gen.html
Hope this helps
Click to expand...
Click to collapse
i was successfully installed stockfirmwere in my motog3 but still the bootloader is unlocked will you please say that if i unlock the bootloader and then update my device without root will i face the bootloupe problem?? and again i dont want to face bootloupe problems after an otp update will you please say that what type of rules i have to follow to not face this type of problem
and you said that the after installing STOCK ROM and before installing OTA update, please ensure that your phone has stock recovery and is not rooted. will you please say that how to ensure that my phone has stock recovery

my thought
coolmalayalee said:
My boot loader is unlocked and am rooted with the stock recovery. My model is XT1550 (dual sim variant in India). I received the OTA updates today.. I downloaded them and installed.. The installation looked like it went fine.. after the installation the phone restarted.. but it kind of went to a boot loop after that.. I can power off the phone pressing the power button for some time.. bu the phone powers off and restarts automatically... it does not progress beyond the few initial screens after which it just displays a blank display...
I am able to get into flashmode.. however, my pc does not recognize the device.. adb terminal shows no devices when I give "adb devices" command.. can someone help? Can I do a factory reset from the flashboot menu? what does the factory mode do? what else can be done to salvage the situation? Thanks.
Update: I went into the stock recovery and did a factory reset. It wiped the user data and did a factory reset. After this I tried rebooting the system. But again the same problem. The phone starts and after the first two -three screens of a boot animation it simply gives me a blank screen display. Really worried now.. Any help?
Click to expand...
Click to collapse
so far i have learned that before applying official ota one must have bootloader relock and everything official like recovery etc etc and may be no root (do not remember no root thing well)
i may be wrong but sharing is caring right?

umo4u said:
so far i have learned that before applying official ota one must have bootloader relock and everything official like recovery etc etc and may be no root (do not remember no root thing well)
i may be wrong but sharing is caring right?
Click to expand...
Click to collapse
It doesn't need bootloader relocked but you need stock rom(no Mods or root) and stock recovery to do ota
---------- Post added at 15:56 ---------- Previous post was at 15:53 ----------
pranaykumar3318 said:
thanks friend i was done finally i was installed stock firmwere thanks to xda developers
---------- Post added at 02:14 PM ---------- Previous post was at 02:00 PM ----------
i was successfully installed stockfirmwere in my motog3 but still the bootloader is unlocked will you please say that if i unlock the bootloader and then update my device without root will i face the bootloupe problem?? and again i dont want to face bootloupe problems after an otp update will you please say that what type of rules i have to follow to not face this type of problem
and you said that the after installing STOCK ROM and before installing OTA update, please ensure that your phone has stock recovery and is not rooted. will you please say that how to ensure that my phone has stock recovery
Click to expand...
Click to collapse
If you reflashed stock firmware then you will have stock recovery and not twrp to find out reboot into your bootloader then use arrow keys until get to option saying recovery then select if its stock it will look abit like cwm but call android 3e recovery or something close to that if not it will boot into twrp

minidude2012 said:
It doesn't need bootloader relocked but you need stock rom(no Mods or root) and stock recovery to do ota
---------- Post added at 15:56 ---------- Previous post was at 15:53 ----------
If you reflashed stock firmware then you will have stock recovery and not twrp to find out reboot into your bootloader then use arrow keys until get to option saying recovery then select if its stock it will look abit like cwm but call android 3e recovery or something close to that if not it will boot into twrp
Click to expand...
Click to collapse
once upon a time I used to have HTC phone and I landed in same problem and learned things from there so what I shared is half true though

minidude2012 said:
It doesn't need bootloader relocked but you need stock rom(no Mods or root) and stock recovery to do ota
---------- Post added at 15:56 ---------- Previous post was at 15:53 ----------
If you reflashed stock firmware then you will have stock recovery and not twrp to find out reboot into your bootloader then use arrow keys until get to option saying recovery then select if its stock it will look abit like cwm but call android 3e recovery or something close to that if not it will boot into twrp
Click to expand...
Click to collapse
thanks for your fast replay

Thanks
arunhebbare said:
Hi, I have faced the same issue that you have faced. I will be resorting to flashing original STOCK ROM using the ADB commands.
There are other threads in this forum explaining the procedure.
Don't worry. If you follow the procedure correctly you will be able to reinstall the system and use your phone again.
After flashing STOCK ROM and before installing OTA update, please ensure that your phone has stock recovery and is not rooted. Other wise you will face similar issue.
To go to fastboot mode from the blank screen mode you may follow the steps below:
1. Keep the power key pressed for a few seconds till you can see that the screen has gone completely black (otherwise you will see the screen dimly lit)
2. Immediately after this step press the volume down button first followed by power button and hold for a second or two and release the buttons, you would be in the fastboot mode
3. You can connect your phone to the PC in this mode to flash the STOCK ROM using the flash boot commands
4. You will find the STOCK ROM in the following link
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
5. For installation procedure and fastboot commands refer this link:
http://www.gammerson.com/2015/08/how-to-flash-stock-firmware-of-Moto-g-3rd-gen.html
Hope this helps
Click to expand...
Click to collapse
Thanks bro.

how to flash magisk patched boot.img?

boys please can u write me steps to flash patched boot. img with fastboot? thank you (european model)

Transfer the patched boot image to PC using 'adb pull' from the path showen in Magisk, boot phone into download mode and flash the patched boot image. 'fastboot flash boot patched_boot.img'

flas patched boot image
Slok 00 said:
boys please can u write me steps to flash patched boot. img with fastboot? thank you (european model)
Click to expand...
Click to collapse
If you flash Magisk from your sd-card, the boot.img is automatically patched by magisk.
Root HTC U11+ European model software number 1.10.401.23
To root your HTC U11+ thru twrp use version 3.2.0.0
1. make sure you got Magisk-15.2 on you sd-card
2. boot into TWRP and leave system read only
3.goto install and install Magisk (in my case 15.2) boot.img is automatically patched
4. you will get error, like "can't mount data" (not to worry)
5. after install GO BACK!! DO NOT REBOOT!!
6. format data AND THEN reboot!!
7 You'll have to setup your phone as a new one; finish that and install Magisk_Manager
8 your now rooted!!! check with root checker
Hope this will help you;
Click to expand...
Click to collapse

milesd said:
Transfer the patched boot image to PC using 'adb pull' from the path showen in Magisk, boot phone into download mode and flash the patched boot image. 'fastboot flash boot patched_boot.img'
Click to expand...
Click to collapse
I have unlocked my U11+ via htcdev.com
I have extracted the boot.img from my RUU
I have installed MagiskManager and patched boot.img
I am having problems flashing the patched_boot.img file ..
I boot to download mode and fastboot flash fails .. see below..
Code:
fastboot flash boot patched_boot.img
target reported max download size of 2399200000 bytes
sending 'boot' (37409 KB)...
FAILED (data write failure (Too many links))
finished. total time: 1.006s
E:\Temp
Can anyone help please!!
I am presently on 2Q4DIMG_OCEAN_M_DUGL_O80_SENSE90GP_HTC_India_SEA_1.24.400.2_Radio_8998-002772-1712011153_release_519104_signed_2_4

I boot to download mode and fastboot flash fails .. see below..
Code:
fastboot flash boot patched_boot.img
target reported max download size of 2399200000 bytes
sending 'boot' (37409 KB)...
FAILED (data write failure (Too many links))
finished. total time: 1.006s
E:\Temp
Can anyone help please!!
Click to expand...
Click to collapse
Try to get a newer htc-fastboot

milesd said:
Try to get a newer htc-fastboot
Click to expand...
Click to collapse
I have tried the fastboot bundled with HTC Sync Manager v3.1.88.3 as well as using the fastboot from platform-tools-v27.0.1-windows but no joy
AFIK there are the latest of the HTC one and the SDK one.
Should also point out I cannot flash the twrp recovery image either.. same error
---------- Post added at 10:56 PM ---------- Previous post was at 10:11 PM ----------
Another thing to mention is that I can erase the partitions without problem using fastboot erase but cannot flash any partitions. The only way I can restore the partitions is to reflash the RUU by putting the RUU zip o the SD card.
I wonder if there is an issue having the 128G sd card in the phone. Will try again tomorrow without the SD card inserted.
The CID's are HTC__060.

You are enable oem unlock in developer option?
Test the connectivity using the following command (provided your phone screen is unlocked)
adb devices
--------------------------------------------------------------------------------------------------------------------------
I think you must rename file patch_boot.img to boot.img
cmd: fastboot flash boot boot.img

newyesor said:
You are enable oem unlock in developer option?
Test the connectivity using the following command (provided your phone screen is unlocked)
adb devices
--------------------------------------------------------------------------------------------------------------------------
I think you must rename file patch_boot.img to boot.img
cmd: fastboot flash boot boot.img
Click to expand...
Click to collapse
I am not new to unlocking and rooting HTC phones I have been doing this since the beginning .. I had an original O2 XDA phone
The phone bootloader is unlocked 100% did it via htcdev and the bootloader screen on both phones says unlocked. There is no issue with connectivity either, adb devices shows the connected phone and other adb commands work fine .. as I said I can even fastboot erase partitions, but am unable to flash them...
I am now thinking it might be my drivers as I am using the windows drivers that came with the latest HTC Sync manager. Later today or tomorrow I might try uninstalling them and using the Universal Naked or the Universal ADB drivers..

Sidewindr said:
I am not new to unlocking and rooting HTC phones I have been doing this since the beginning .. I had an original O2 XDA phone
The phone bootloader is unlocked 100% did it via htcdev and the bootloader screen on both phones says unlocked. There is no issue with connectivity either, adb devices shows the connected phone and other adb commands work fine .. as I said I can even fastboot erase partitions, but am unable to flash them...
I am now thinking it might be my drivers as I am using the windows drivers that came with the latest HTC Sync manager. Later today or tomorrow I might try uninstalling them and using the Universal Naked or the Universal ADB drivers..
Click to expand...
Click to collapse
Have you tried flashing with
fastboot flash boot YOUR_DIRECTORY / patched_boot.img
Just an idea....

Yes tried absolute and relative paths.
Sent from my HTC One M8 using Tapatalk

Switch to another usb port and/or try with another usb cable
https://plus.google.com/+ArtemRussakovskii/posts/RwJ28EdYgCb
https://www.youtube.com/watch?v=5Omhpv7oYdc

Problem solved ... Tried it again after reboot and on a different USB port and it worked .. odd ..

Patched

milesd said:
Transfer the patched boot image to PC using 'adb pull' from the path showen in Magisk, boot phone into download mode and flash the patched boot image. 'fastboot flash boot patched_boot.img'
Click to expand...
Click to collapse
HI I would just like to clarify before I try the download mode.
I have been trying to patch the magisk patched_boot.img in bootloader mode on a HTC U11 with no joy.
This is the error I receive
PS E:\HTC\ADB tools with latest twrp.img Use this one 2019\platform-tools> fastboot flash boot magisk_patched.img
target reported max download size of 536870912 bytes
sending 'boot' (37589 KB)...
OKAY [ 0.915s]
writing 'boot'...
FAILED (remote: Not allowed on PRODUCTION device)
finished. total time: 0.924s
Is it safe to patch in the download mode as stated?
Thanks

[Help!]ADB devices not listed

Hi,
I'm tring to flash this twrp https://twrp.me/oneplus/oneplus6.html after unlocked the bootloader on my new OP6 but this is what I get from ADB:
D:\Trash\ADB>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (26748 KB)...
OKAY [ 0.562s]
writing 'recovery'...
FAILED (remote: (recovery_a) No such partition)
finished. total time: 0.578s
Any hints??
Thx in advance!
Edit: First time I got in fastboot mode (to unlock bootloader), when I sent command "ADB devices" I saw the usual serial. Now after unlocked the bootloader, once I go in fastbode mode, there's no more devices listed.
What went wrong??

zappomax said:
Hi,
I'm tring to flash this twrp https://twrp.me/oneplus/oneplus6.html after unlocked the bootloader on my new OP6 but this is what I get from ADB:
D:\Trash\ADB>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (26748 KB)...
OKAY [ 0.562s]
writing 'recovery'...
FAILED (remote: (recovery_a) No such partition)
finished. total time: 0.578s
Any hints??
Thx in advance!
Edit: First time I got in fastboot mode (to unlock bootloader), when I sent command "ADB devices" I saw the usual serial. Now after unlocked the bootloader, once I go in fastbode mode, there's no more devices listed.
What went wrong??
Click to expand...
Click to collapse
I don't get it. The TWRP site you posted said to fastboot into TWRP image, then flash recovery from TWRP itself. It seems like you tried to flash the image directly. As the TWRP site you posted explains, this is not how it works anymore.
Just follow the instructions from the site.
The OnePlus 6 uses the newer AB partition scheme first introduced on the Pixel 1. As such there is no recovery partition. Instead, the recovery is part of the boot image. You will temporarily boot TWRP to perform and later perform a more permanent TWRP installation. First download the TWRP zip file directly on your device. If you don't download the zip file to your device first for any reason, you will need to adb push the zip to the device because MTP is not currently working on the OnePlus 6 in TWRP. If you are unable to use adb, you can also use a USB stick with an OTG cable, if you have those handy. Power off the device. Hold volume up to get into fastboot mode. Run this command on your computer: fastboot boot twrp-3.2.1-0-enchilada.img
In TWRP, tap on Install and browse to the zip and install it (the zip will probably be in /sdcard/Downloads). TWRP will now be installed to both slots. TWRP is now installed and you can reboot and use your device as normal.
Click to expand...
Click to collapse

Command is "fastboot boot recovery.img" and when you're in twrp flash twrp zip
Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk

After unlocking the bootloader (and subsequent factory reset) did you reenable the developer menu and the USB debugging? Does your device asks for debugging permission?

akxak said:
After unlocking the bootloader (and subsequent factory reset) did you reenable the developer menu and the USB debugging? Does your device asks for debugging permission?
Click to expand...
Click to collapse
Sure

zappomax said:
Sure
Click to expand...
Click to collapse
Sounds like your usb drivers are faulty. Try a different computer. Happened to me before with a Pixel XL.

Sometimes it helps just to reconnect the phone.

Sorry to all...
I just needed to read the instructions carefully on TWRP site...
So stupid and hasty

There's no recovery on this device, it's included in the boot partition. So fastboot boot the image, and then flash the installer zip.

I have a similar problem.
My phone is rooted, bootloader unlocked, TWRP and magisk installed, oxygen is ver 10.3.12. fastboot devices detects my OP6 but adb can't.
I have usb debugging enabled, all necessary drivers installed in my computer. I also tried different usb preferences like MIDI, PTP, tethering etc but all in vain. never faced such problem earlier. Earlier I could all adb commands on this devices even after rooting and installing TWRP, but now I can't !
I tested my oneplus one and OnePlus 7 also. adb commands are properly working on them, but not on OP6. What can be the reason?
Now, after trying different drivers from Google, samsung and oneplus, I am sure that the problem is from phone's end because in all cases my oneplus1 and oneplus7 are detected in adb devices without fail. Request you to read carefully before replying, since i am out of options now, tried almost all remedies available elsewhere.

ashish_jha said:
I have a similar problem.
My phone is rooted, bootloader unlocked, TWRP and magisk installed, oxygen is ver 10.3.12. fastboot devices detects my OP6 but adb can't.
I have usb debugging enabled, all necessary drivers installed in my computer. I also tried different usb preferences like MIDI, PTP, tethering etc but all in vain. never faced such problem earlier. Earlier I could all adb commands on this devices even after rooting and installing TWRP, but now I can't !
I tested my oneplus one and OnePlus 7 also. adb commands are properly working on them, but not on OP6. What can be the reason?
Now, after trying different drivers from Google, samsung and oneplus, I am sure that the problem is from phone's end because in all cases my oneplus1 and oneplus7 are detected in adb devices without fail. Request you to read carefully before replying, since i am out of options now, tried almost all remedies available elsewhere.
Click to expand...
Click to collapse

ADB Driver Installer v6.0 for Windows 10 64 Bit (2023)
ADB Driver Installer v6.0 Latest for Windows 10> It helps you to connect Android Smartphones and Tablets to Windows 7/ 8/ 10/ XP/Vista x64/ x86
www.driversforum.net

[SOLVED]Oneplus 7 stuck in fastbootmode after trying to restore a backup from TWRP

My bootloader is unlocked, I was rooted with Magisk and i had twrp recovery installed as well. A few modules were installed and i had made a backup about 3 weeks ago. Yesterday i tried restoring the backup in twrp and it seemed to restore properly without errors . When i pressed reboot in the end the phone went to the fastboot mode screen and has since been there. All i can do is turn it off and regardless of what i pick, (START, Restart Bootloader, Recovery mode) it just starts into fastboot mode. Confused as to what i should do now and why this happened in the first place. All the threads i found were only for the 7 pro so i didnt want to risk anything by following those. Please advice on what i should do.
Edit : The problem was solved by flashing the STOCK ROM for android 9 which is what i was on when the device was softbricked.

hi
Hi, download adb fastboot and twrp recovery image for guacamoleb. then open a new command prompt (CMD) in the same location and run the following commands:
Code:
fastboot flash recovery (file name of twrp that you download).img
after that by holding volume up + power reboot to twrp recovery that you just installed via adb fastboot command.
when you enter on twrp recovery, install twrp recovery zip, and magisk 19.3 zip (download and copy on phone storage first, after you enter on twrp when reboot, you can connect your phone with computer or USB that contain twrp recovery zip and magisk or copy to phone storage) after this step install twrp zip first than magisk and then reboot.
i hope i helped.
sorry for my english , is not my native language.

klediY said:
Hi, download adb fastboot and twrp recovery image for guacamoleb. then open a new command prompt (CMD) in the same location and run the following commands:
Code:
fastboot flash recovery (file name of twrp that you download).img
after that by holding volume up + power reboot to twrp recovery that you just installed via adb fastboot command.
when you enter on twrp recovery, install twrp recovery zip, and magisk 19.3 zip (download and copy on phone storage first, after you enter on twrp when reboot, you can connect your phone with computer or USB that contain twrp recovery zip and magisk or copy to phone storage) after this step install twrp zip first than magisk and then reboot.
i hope i helped.
sorry for my english , is not my native language.
Click to expand...
Click to collapse
Thank you for the reply. Unfortunately i am stuck in the very first step. After typing C:\adb\Oneplus 7>fastboot flash recovery twrp-3.3.1-1-guacamoleb.img in cmd the following happens
target reported max download size of 805306368 bytes
sending 'recovery' (56612 KB)...
OKAY [ 1.220s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 1.228s
I have tried using fastboot boot recovery instead in cmd. The following error comes up
cannot load 'recovery': No such file or directory.
I have checked whether the device is connected by typing in fastboot devices and it shows as connected. Any other suggestions will be helpful.

wolfsbane169 said:
Thank you for the reply. Unfortunately i am stuck in the very first step. After typing C:\adb\Oneplus 7>fastboot flash recovery twrp-3.3.1-1-guacamoleb.img in cmd the following happens
target reported max download size of 805306368 bytes
sending 'recovery' (56612 KB)...
OKAY [ 1.220s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 1.228s
I have tried using fastboot boot recovery instead in cmd. The following error comes up
cannot load 'recovery': No such file or directory.
I have checked whether the device is connected by typing in fastboot devices and it shows as connected. Any other suggestions will be helpful.
Click to expand...
Click to collapse
Something similar happened to me, I was on OOS 10 stable and wiping the system and data from TWRP got in fastboot mode without being possible to do anything else. The way that I solved was flashing from fastboot the OOS 10 stable posted rom here: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478 This will erase all your data but you will unbrick your phone.
One important thing, if you are on android 10 you can't flash TWRP via fasboot, maybe that's the problem you are having right now.
Hope this helps

ryupunk said:
Something similar happened to me, I was on OOS 10 stable and wiping the system and data from TWRP got in fastboot mode without being possible to do anything else. The way that I solved was flashing from fastboot the OOS 10 stable posted rom here: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478 This will erase all your data but you will unbrick your phone.
One important thing, if you are on android 10 you can't flash TWRP via fasboot, maybe that's the problem you are having right now.
Hope this helps
Click to expand...
Click to collapse
Ok so thank you for the help and you were right. Now i have an all new different problem. In a nutshell i flashed the stock ROM for android 9 while i was in android 10. I completely forgot you aren't supposed to do that. As a result i cant even access fastboot mode now. Can you please tell me how i can fix this problem?

wolfsbane169 said:
Ok so thank you for the help and you were right. Now i have an all new different problem. In a nutshell i flashed the stock ROM for android 9 while i was in android 10. I completely forgot you aren't supposed to do that. As a result i cant even access fastboot mode now. Can you please tell me how i can fix this problem?
Click to expand...
Click to collapse
I think that you will need to use the MSM tool, it looks like you have a hard brick, the good news is that oneplus devices can be revived in almost all cases. I have never used the tool but I found some posts that might help you. Best of luck!
XDA Oneplus 7 thread
https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
XDA Oneplus 7 pro thread
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Oneplus forum guide
https://forums.oneplus.com/threads/...ide-for-a-hard-bricked-oneplus-7-pro.1041896/

ryupunk said:
I think that you will need to use the MSM tool, it looks like you have a hard brick, the good news is that oneplus devices can be revived in almost all cases. I have never used the tool but I found some posts that might help you. Best of luck!
XDA Oneplus 7 thread
https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
XDA Oneplus 7 pro thread
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Oneplus forum guide
https://forums.oneplus.com/threads/...ide-for-a-hard-bricked-oneplus-7-pro.1041896/
Click to expand...
Click to collapse
I have tried using it but the problem is that MSM download tool does not detect my phone. i have uninstalled and let windows automatically update qualcomm drivers. I have also made windows manually install them after uninstalling.

Pixel 3a - stuck on BootLoader with: error boot prepar

Hello,
I followed the steps on these two links:
https://forum.xda-developers.com/pixel-3a-xl/how-to/how-to-root-pixel-3a-3a-xl-twrp-t3928868
https://www.**********.com/unlock-pixel-3a-bootloader-and-root-pixel-3a-3a-xl/
To root my Pixel 3A. I unlocked it successfully, and then I did the final step of this command:
fastboot flash boot magisk_patched.img
But now my device is stuck on the bootloader screen. The bottom lines say:
Device state: unlocked
Boot slot: b
Enter reason: error boot prepare
I tried the options on the boot loader (rescue mode, recover mode, restart bootloader, powering off and restarting) but it only takes me back to the bootloader screen with same error.
From my MAC, I can still do the commands:
fastboot reboot (which does reboot the phone)
and
fastboot flash boot magisk_patched.img, which shows this:
Sending 'boot_b' (29136 KB) OKAY [ 0.760s]
Writing 'boot_b' OKAY [ 0.189s]
Finished. Total time: 1.219s
But not sure what else I can do to get out of the bootloader screen
Any help would be appreciated, as the phone is effectively bricked

DarthLuch said:
Hello,
I followed the steps on these two links:
https://forum.xda-developers.com/pixel-3a-xl/how-to/how-to-root-pixel-3a-3a-xl-twrp-t3928868
https://www.**********.com/unlock-pixel-3a-bootloader-and-root-pixel-3a-3a-xl/
To root my Pixel 3A. I unlocked it successfully, and then I did the final step of this command:
fastboot flash boot magisk_patched.img
But now my device is stuck on the bootloader screen. The bottom lines say:
Device state: unlocked
Boot slot: b
Enter reason: error boot prepare
I tried the options on the boot loader (rescue mode, recover mode, restart bootloader, powering off and restarting) but it only takes me back to the bootloader screen with same error.
From my MAC, I can still do the commands:
fastboot reboot (which does reboot the phone)
and
fastboot flash boot magisk_patched.img, which shows this:
Sending 'boot_b' (29136 KB) OKAY [ 0.760s]
Writing 'boot_b' OKAY [ 0.189s]
Finished. Total time: 1.219s
But not sure what else I can do to get out of the bootloader screen
Any help would be appreciated, as the phone is effectively bricked
Click to expand...
Click to collapse
Sounds like your magisk file is either the wrong version or corrupted. Download the full Google image, extract the boot.img from that and ash that image file using the fastboot flash boot boot.img command. Alternatively you could download the mvk kernel from here on xda and flash that. It's pre-rooted.

adm1jtg said:
Sounds like your magisk file is either the wrong version or corrupted. Download the full Google image, extract the boot.img from that and ash that image file using the fastboot flash boot boot.img command. Alternatively you could download the mvk kernel from here on xda and flash that. It's pre-rooted.
Click to expand...
Click to collapse
Thanks for that.. For whatever reason the MVK_Sargo_v10.22_magisk_patched.img version did not work, but the MVK_Sargo_v10.21_magisk_patched.img one did!

DarthLuch said:
Thanks for that.. For whatever reason the MVK_Sargo_v10.22_magisk_patched.img version did not work, but the MVK_Sargo_v10.21_magisk_patched.img one did!
Click to expand...
Click to collapse
If 21 worked but 22 didn't... Going from my faltering memory that means your not on March security, your on feb or earlier. 22 only worked on March, i am running it myself.

I got stuck here, too... I used the flash tool (flash.android.com) and it put me back to stock after about a 20 minute progress bar crawl

I have the same problem can someone help me?

YYa solucionaste ?