Develop Bugs

jUST BOOTLOADER SCREEN JUST

NO RECOVERY JUST BLUE SCREEN NO DOWNLOAD MODE JUST BLUE SCREEN
fastboot command in bootloader screen gives error FAILED (remote: cannot flash this partition in s-on state)
{
"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"
}

What did you do to get to this state? Please try to list the exact steps in order. Also, what had you done to the phone before you started whatever happened here, i.e., what rom/firmware were you on?

iElvis said:
What did you do to get to this state? Please try to list the exact steps in order. Also, what had you done to the phone before you started whatever happened here, i.e., what rom/firmware were you on?
Click to expand...
Click to collapse
htc m9 asia tw
s-on
firmware update to 5.1 (2.10.709.1) through RUU mode sudden mobile reset and now when it on after that gives blue blank screen just....
just bootloader screen come while pressing vol + and vol - and power button. bt no recovery no download mode no RUU mode while going to download mode blue screen error.
plz someone help. what to do.

We need more detail than that to help.
What file did you try to flash? How exactly did you do it? By "RUU mode" do you mean you used the fastboot oem rebootRUU command, or something else? Or were you running a RUU.exe file? Which one?
You were unlocked; were you running a custom rom before this? Which one? How did you relock?

iElvis said:
We need more detail than that to help.
What file did you try to flash? How exactly did you do it? By "RUU mode" do you mean you used the fastboot oem rebootRUU command, or something else? Or were you running a RUU.exe file? Which one?
You were unlocked; were you running a custom rom before this? Which one? How did you relock?
Click to expand...
Click to collapse
HTC m9 asia tw it was with firmware 1.40.709.8 then i unlocked bootloader from htcdev.com and used venom rom...
after that i started to update to 5.1 i used following commands,
To re-lock your bootloader, in the command prompt, type: fastboot oem lock.
fastboot oem rebootRUU
fastboot flash zip firmware-2.10.709.1.zip
fastboot reboot-bootloader
firmware updated successfully but it stuck at htc logo.
then i flash again firmware.zip sudden mobile reset and this blue screen appears. now when going to RUU, download, recovery mode this blue screen appears.
bootloader screen come while pressing vol + and vol - and power button but can't flash anything. while using command on bootloader screen fastboot gives error FAILED (remote: cannot flash this partition in s-on state)
FAILED (remote: Not allow when s-on)

solve this problem
please reply

how can you solve the problem ???

hoang555 said:
how can you solve the problem ???
Click to expand...
Click to collapse
not solved yet....

mnhs1010 said:
not solved yet....
Click to expand...
Click to collapse
theirs nothing you can do but send it to HTC. any fix would require you get into download mode at least

clsA said:
theirs nothing you can do but send it to HTC. any fix would require you get into download mode at least
Click to expand...
Click to collapse
no download mode. no recovery just bootloader screen. otherwise blue screen just......
i have sent it to htc service center in dubai but they did not repair it. they its on our country set. send it to asia tw for repairing. what the hell is this...

mnhs1010 said:
no download mode. no recovery just bootloader screen. otherwise blue screen just......
i have sent it to htc service center in dubai but they did not repair it. they its on our country set. send it to asia tw for repairing. what the hell is this...
Click to expand...
Click to collapse
any solution please tell

hoang555 said:
how can you solve the problem ???
Click to expand...
Click to collapse
please u have any solution please tell me.

https://docs.google.com/spreadsheets/d/15K6xhb6wtosp9j8yu4xHBZ6n9v5OaFSW6ZVWxC4u_qc/pubhtml#
inset Firmware Packs
"WARNING: HTC introduced a new "security feature" with the 2.XX.XXX.X firmware. This "feature" blocks the Bootloader Unlock if the option "OEM unlocking" in the Developer Options isn't activated. Because of that it's not recommended (especially to S-ON Users) to relock the Bootloader and flash these files if you want to update to Firmware 2.XX.XXX.X or newer. You better use a RUU and the Update Function in "Settings>About" for that purpose."
Flash stock rom, RUU.exe

finally replacement of mainboard

Possible Solution!
If anyone is having this problem more recently I have found a solution. Please Follow the instructions as I have put it, this has helped me and several others. Believe me I was close to throwing my phone at the wall before I fixed it with the below solution:
Notes:
You will need to be S-Off for this solution to work.
Your phone may reboot several times during this process - just let it reboot back to bootloader again before carring on where you left off from.
1. Download a fresh copy of Minimal ADB and Fastboot Package and install it.
2. Re-download a copy of the most recent firmware that WORKED on your phone as a zip format and place it in the same folder you installed Minimal ADB/Fastboot
2. Hold the Volume up button and the Power button to get the phone out of the loop - If you're phone is salvageable this should bring you to the bootloader however if you press on any option other than reboot to boot loader it will throw your phone back into infinite blue screen loop or to a blue screen so don't even try.
3. Plug the phone into your PC and make sure its been detected by task manager if there is a question mark you will need to re-install the correct HTC Drivers (Normally uninstalling HTC Sync Manager and re-installing it does the trick).
4. Once the phone is recognized by windows start up the file "MAF32" in the ADB/Fastboot folder on windows.
5. Extract the Firmware Zip file you downloaded in step two into the same folder you installed ADB/Fastboot.
6 Type the flash commands below exactly as they are written below (or copy and paste) (If boot.img is not part of the firmware you downloaded you can skip that file).
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash adsp adsp.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sdi sdi.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
fastboot reboot
This should bring your phone back to life and you should be able to access your recovery and download mode again (you may have to flash custom recover again depending on where you got your firmware from) - Now your phone is ready for a ROM Install.
Let me know how you guys get on

lizard2k5 said:
If anyone is having this problem more recently I have found a solution. Please Follow the instructions as I have put it, this has helped me and several others. Believe me I was close to throwing my phone at the wall before I fixed it with the below solution:
Notes:
You will need to be S-Off for this solution to work.
Your phone may reboot several times during this process - just let it reboot back to bootloader again before carring on where you left off from.
1. Download a fresh copy of Minimal ADB and Fastboot Package and install it.
2. Re-download a copy of the most recent firmware that WORKED on your phone as a zip format and place it in the same folder you installed Minimal ADB/Fastboot
2. Hold the Volume up button and the Power button to get the phone out of the loop - If you're phone is salvageable this should bring you to the bootloader however if you press on any option other than reboot to boot loader it will throw your phone back into infinite blue screen loop or to a blue screen so don't even try.
3. Plug the phone into your PC and make sure its been detected by task manager if there is a question mark you will need to re-install the correct HTC Drivers (Normally uninstalling HTC Sync Manager and re-installing it does the trick).
4. Once the phone is recognized by windows start up the file "MAF32" in the ADB/Fastboot folder on windows.
5. Extract the Firmware Zip file you downloaded in step two into the same folder you installed ADB/Fastboot.
6 Type the flash commands below exactly as they are written below (or copy and paste) (If boot.img is not part of the firmware you downloaded you can skip that file).
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash adsp adsp.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sdi sdi.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
fastboot reboot
This should bring your phone back to life and you should be able to access your recovery and download mode again (you may have to flash custom recover again depending on where you got your firmware from) - Now your phone is ready for a ROM Install.
Let me know how you guys get on
Click to expand...
Click to collapse
i have this issus before, that will fix it but for now his phone is S-on so im afraid it will not work

I Did say S-OFF only but thanks for your input - I know a few people who were stuck with S-OFF too.
Arthas92 said:
i have this issus before, that will fix it but for now his phone is S-on so im afraid it will not work
Click to expand...
Click to collapse

I'm stuck at same problem. Does anyone can help?
Is XTC an option?

lizard2k5 said:
If anyone is having this problem more recently I have found a solution. Please Follow the instructions as I have put it, this has helped me and several others. Believe me I was close to throwing my phone at the wall before I fixed it with the below solution:
Notes:
You will need to be S-Off for this solution to work.
Your phone may reboot several times during this process - just let it reboot back to bootloader again before carring on where you left off from.
1. Download a fresh copy of Minimal ADB and Fastboot Package and install it.
2. Re-download a copy of the most recent firmware that WORKED on your phone as a zip format and place it in the same folder you installed Minimal ADB/Fastboot
2. Hold the Volume up button and the Power button to get the phone out of the loop - If you're phone is salvageable this should bring you to the bootloader however if you press on any option other than reboot to boot loader it will throw your phone back into infinite blue screen loop or to a blue screen so don't even try.
3. Plug the phone into your PC and make sure its been detected by task manager if there is a question mark you will need to re-install the correct HTC Drivers (Normally uninstalling HTC Sync Manager and re-installing it does the trick).
4. Once the phone is recognized by windows start up the file "MAF32" in the ADB/Fastboot folder on windows.
5. Extract the Firmware Zip file you downloaded in step two into the same folder you installed ADB/Fastboot.
6 Type the flash commands below exactly as they are written below (or copy and paste) (If boot.img is not part of the firmware you downloaded you can skip that file).
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash adsp adsp.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sdi sdi.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
fastboot reboot
This should bring your phone back to life and you should be able to access your recovery and download mode again (you may have to flash custom recover again depending on where you got your firmware from) - Now your phone is ready for a ROM Install.
Let me know how you guys get on
Click to expand...
Click to collapse
Hi. I have the same problem which is blue screen on download mode. I tried this method but nothing happen. My HTC is verizon version. I tried to flash all the img from 3.37.605.7 firmware but still the same.

Zenfone 2 ver 2.17.40.12 bootloops after flashing Wrong TWRP

TWRP recovery request fastboot command
I tried to flash twrp.img on my Zenfone 2 ver 2.17.40.12 (rooted). I guess there was a version mismatch, because I ended up with the screen saying "Fastboot cmd waiting". I am allowed to power down and normal boot, which work, but options "recovery mode" and "restart bootloader" return me back to the same screen saying Fastboot cmd waiting.
I tried to do a factory reset, but I got the same screen and nothing else. I downloaded ZIP file with the correctoriginal recovery for my version and tried to use fastboot command update, but it failed with message saying that archive does not contain android-info.txt and neither android-product.txt.
I will appreciate your advice to resolve my problem.

Well, fastboot is showing error because you're trying to flash ZIP file for the recovery mode(like TWRP) that doesn't have compatibility with fastboot mode.
You have to flash the .img file for your zenfone2(Z00A or Z008) with the command below.
Code:
fastboot flash recovery twrp.img
And also, model number(Z00A or Z008) is shown on the screen when booting in fastboot mode.

Phone now boot into fastboot but not system

Hi
I was trying to install Lineage OS on my device, but I failed, now the phone does not have TWRP anymore, and when I power up, it goes into fast boot only.
I have done quite a lot of work to save my phone, and the last thing that I did was download the stock fastboot rom and run flash_all.bat from it.
(I can not get the Miflash tool working on my PC because when I startup the program, it asks me to download 5 drivers, but it failed to download and throw me an error)

luckyvictor said:
Hi
I was trying to install Lineage OS on my device, but I failed, now the phone does not have TWRP anymore, and when I power up, it goes into fast boot only.
I have done quite a lot of work to save my phone, and the last thing that I did was download the stock fastboot rom and run flash_all.bat from it.
(I can not get the Miflash tool working on my PC because when I startup the program, it asks me to download 5 drivers, but it failed to download and throw me an error)
Click to expand...
Click to collapse
First of all - if your phone boots to fastboot, there seems to be a problem with your bootloader or kernel.
To fix that, you need to reflash aboot.img and boot.img via fastboot.
Boot.img depends on the version, you want to install. Copy both files into your fastboot folder and
Code:
fastboot flash boot_a boot.img
Code:
fastboot flash boot_b boot.img
Code:
fastboot flash aboot_a aboot.img
Code:
fastboot flash aboot_b aboot.img
Now your phone shouldn´t stuck @ fastboot anymore.
Ok, to save your data, you could try to boot twrp:
Code:
fastboot boot twrp.img
If you´re lucky, it can decrypt your data - then you can backup data and internal storage...
If it´s not able to decrypt, you need to install twrp.
To install a fastboot rom without miflash look here
I suggest you to install caf-kernel via twrp. Sometimes your phone boots up with it - magic

Voodoojonny said:
First of all - if your phone boots to fastboot, there seems to be a problem with your bootloader or kernel.
To fix that, you need to reflash aboot.img and boot.img via fastboot.
Boot.img depends on the version, you want to install. Copy both files into your fastboot folder and
Code:
fastboot flash boot_a boot.img
Code:
fastboot flash boot_b boot.img
Code:
fastboot flash aboot_a aboot.img
Code:
fastboot flash aboot_b aboot.img
Now your phone shouldn´t stuck @ fastboot anymore.
Ok, to save your data, you could try to boot twrp:
Code:
fastboot boot twrp.img
If you´re lucky, it can decrypt your data - then you can backup data and internal storage...
If it´s not able to decrypt, you need to install twrp.
To install a fastboot rom without miflash look here
I suggest you to install caf-kernel via twrp. Sometimes your phone boots up with it - magic
Click to expand...
Click to collapse
Thanks, will give it a try.
Just for my knowledge, what are these boot_a and boot_b please? they relate to the two sim slot in this device?

luckyvictor said:
Thanks, will give it a try.
Just for my knowledge, what are these boot_a and boot_b please? they relate to the two sim slot in this device?
Click to expand...
Click to collapse
Boot.img from fastboot rom... To be flashed in partition boot_a and boot_b. Our device is a AB-device. That means all partitions are doubled (except of data). If your system breaks, you can switch to the other slot by "fastboot set_active a" or b if you are on a.... Btw perhaps that fixes your phone too! Boot twrp and you can see which slot is active (under reboot)

Rooting Motorola G6 Play gone wrong

Hi everyone,
I bought a Motorola G6 play model XT1922-3 type 374B and wanted root acces on this device.
So I started by succesfully unlocking my bootloader using the following tutorial.
After this a started tried to root the device using this tutorial.
This tutorial doesn't link to boot images anymore so I was able to find the moto-g6-play-jeter-patched-twrp.img somewhere else.
I did the following things:
- reboot to bootloader [Succesfull]
- fastboot boot moto-g6-play-jeter-patched-twrp.img [Unsuccesfull]
The device did boot the twrp image but I was unable to interact with it in any way. I couldn't swipe or press buttons.
I made a short video to show this.
I wanted to retry the whole thing so I did reboot to bootloader but then I accidently entered the following command:
fastboot flash boot moto-g6-play-jeter-patched-twrp.img picture of command prompt
After this I wasn't able to normally boot my device. When I try to do so the screen goes black and says n/a in the left corner.
Please does anyone know how I could either be able to boot my normal stock rom again or to have a rooted rom?
Kind regards Sven Onderbeke

Hi Sven,
This isn't going to be the most advanced reply, as I'm not very experienced with this stuff either, but it seems you have accidentally flashed your twrp image to 'boot', wherever that is, which is why the phone isn't able to boot to system.
Can you still boot into bootloader and recovery (twrp)?
If so, then I'd suggest using fastboot to flash a sock or custom ROM. I'm not sure exactly which one though, you have basically the same model as me and that seems to use the JETER ROMS a list of which are over here (can't post links yet, so you will just have to search on mirrors . lolnet . com /firmware/moto/jeter/official/ or remove the spaces
I seem to have somehow lost the partitions on mine, but will start a new thread question about that.

Sven Onderbeke said:
Hi everyone,
I bought a Motorola G6 play model XT1922-3 type 374B and wanted root acces on this device.
So I started by succesfully unlocking my bootloader using the following tutorial.
After this a started tried to root the device using this tutorial.
This tutorial doesn't link to boot images anymore so I was able to find the moto-g6-play-jeter-patched-twrp.img somewhere else.
I did the following things:
- reboot to bootloader [Succesfull]
- fastboot boot moto-g6-play-jeter-patched-twrp.img [Unsuccesfull]
The device did boot the twrp image but I was unable to interact with it in any way. I couldn't swipe or press buttons.
I made a short video to show this.
I wanted to retry the whole thing so I did reboot to bootloader but then I accidently entered the following command:
fastboot flash boot moto-g6-play-jeter-patched-twrp.imgpicture of command prompt
After this I wasn't able to normally boot my device. When I try to do so the screen goes black and says n/a in the left corner.
Please does anyone know how I could either be able to boot my normal stock rom again or to have a rooted rom?
Kind regards Sven Onderbeke
Click to expand...
Click to collapse
Just flash a stock boot.img to boot. Then just flash TWRP to recovery. In TWRP, format data. Type yes. Then reboot recovery. Then Use TWRP to flash magisk. Done.

Hi again Sven,
I just wanted to let you know that I just downloaded the following RETAIL ROM
ALJETER_RETAIL_9.0_PPPS29.55-35-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
and used the following fastboot commands, one at a time.
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 boot boot.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 oem oem.img
fastboot flash vendor vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
Which rebooted into bootloader so pressed "start" and all booted fine now. It looks like we have the same device, so hopefully that will work for you too.

(Bootloader) Permission denied [SOLVED]

Hi, I used Carbon ROM on XT1670, when I wanted to change ROM I ran:
Code:
fastboot -w
And i got this:
{
"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 also tried to remove them:
In TWRP I tried to do something but all I get is something similar to this:
Am I missing something? Thanks for your help.

I've been reading the question and answer forum, apparently it's a problem with the encryption.
I don't have the Moto G5 right now, I can try it in a couple of hours, what other solution could I have anyway?

In twrp go to wipe
Then press the option on the right to format data
Reboot to recovery
Note this is different from wipe data from the advanced wipe menu.
The fastboot command would be
fastboot erase userdata

TheFixItMan said:
In twrp go to wipe
Then press the option on the right to format data
Reboot to recovery
Note this is different from wipe data from the advanced wipe menu.
The fastboot command would be
fastboot erase userdata
Click to expand...
Click to collapse
Hello, good (and bad) news
I did and now I have MTP for TWRP.
But still CMD says "Bootloader is logical @@@ not found"
"@@@" is depending on what you are trying to flash, be it system or recovery.
I was also able to change the filesystem I did it for DATA / CACHE / SYSTEM I went from FAT and then to EXT4 again.
Insert a ROM and it flashed without problems but it starts again in fastboot, the same if I do it with ADB Sideload.
I also tried flashing Stock ROM, everything seems to be written without problem but with the first line of "Bootloader logical ... not found" and again start in fastboot.
It makes me believe that something is still encrypted.
I mean this.

I also tried
Code:
fastboot format:ext4 userdata
But I have this:

Bootloader is logical not found - this is normal output
Why are you trying to change formats? You are going to have issues especially with encryption. Use twrp to format not fastboot if you are messing with formatting but make sure you know what you are doing!

TheFixItMan said:
Bootloader is logical not found - this is normal output
Why are you trying to change formats? You are going to have issues especially with encryption. Use twrp to format not fastboot if you are messing with formatting but make sure you know what you are doing!
Click to expand...
Click to collapse
I flash a rom (no apparent problem, even Stock ROM) but it only boots to fastboot or the robot with an open belly.
What exactly should I do, I will follow step by step, I really need to get it back. Thank you very much for your help.

Hello again, I saw you in another post that apparently has the same problem as me, it is this:
Decryption unsuccessfull
Hi guys, I have a problem with my motorola moto g5. It turns out that I upgraded to android oreo and at the time of associating the fingerprint I asked for a pin for security which I put. En el twrp me pide el pin, el cual ingresa y ya podia...
forum.xda-developers.com

I have the same bugs, do you think I should run the command to decrypt?

Dislekzi4 said:
Ok, I'll get to the point.
I flash a rom (no apparent problem, even Stock ROM) but it only boots to fastboot or the robot with an open belly.
What exactly should I do, I will follow step by step, I really need to get it back. Thank you very much for your help.
Click to expand...
Click to collapse
In twrp format data
That is by selecting wipe
Then the option on the right to format data
Reboot to recovery
Everything should now be mountable
Make sure you are flashing stock rom correctly
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
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 system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Making sure you are flashing the same or newer firmware version than already on your phone
If your phone keeps booting to recovery (android with an open stomach or twrp) then do this
Boot into twrp then connect phone to PC and in cmd/terminal type
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
Reboot and your device will boot normally (assuming you have a working rom)

Hi, it work!
Thank you very much for your time and help, I am very grateful, for a moment I thought it was really a hardware problem.

I get device unauthorized. Please check the confirmation dialog on your device. and it won't let me do anything

Rod_Ems said:
I get device unauthorized. Please check the confirmation dialog on your device. and it won't let me do anything
Click to expand...
Click to collapse
Enable adb debugging on your device in dev options
Make sure you are using the latest platform tools
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Unzip
Navigate your cmd window to to the platform tools directory
In cmd type
adb devices
Look on your phone and a window will pop up asking you to confirm authorisation - tick the box to allow always if you want to
Then type
adb devices
And your device is authorised

TheFixItMan said:
In twrp format data
That is by selecting wipe
Then the option on the right to format data
Reboot to recovery
Everything should now be mountable
Make sure you are flashing stock rom correctly
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
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 system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Making sure you are flashing the same or newer firmware version than already on your phone
If your phone keeps booting to recovery (android with an open stomach or twrp) then do this
Boot into twrp then connect phone to PC and in cmd/terminal type
Code:
adb shell dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
Reboot and your device will boot normally (assuming you have a working rom)
Click to expand...
Click to collapse
mine show the following error message: device '(null)' not found

danniel_sx said:
mine show the following error message: device '(null)' not found
Click to expand...
Click to collapse
Either
Your phone is not connected to pc
Faulty cable
You haven't installed Motorola USB drivers
You are using the wrong commands
If in fastboot mode type
fastboot devices
If in recovery mode type
adb devices
Your device should be listed if correctly connected

I found a solution, i'm argentinian so sorry if my english is bad
the fastboot menu of the combination power + volume down have no permissions to all modifications
You have to acces to the recovery fastboot menu, to do this, move to "recovery mode" enter here with power
Now if in the screen appears "No command" you have to press power + volume down for 3 sec and press vol up without press the another 2, then release the 3 buttons
Now go to "fastboot" in the recobery mode, and ta daaa. You have permissions