Develop Bugs

[Q] Bricked my nexus - Fastboot still almost working

I Think my device is lost. It´s locked in boot of my Gummynex rom.
I´m not allowed to flash anything else, it´s like my filesystem is broken.
I have attached som screenshots of the error´s i get in galaxy nexus toolkit 5.6
{
"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 Have also tryed with Odin, but i cant seem to get odin to connect with the phone in fastboot.
If i try to go into recoverymode i get the android man lying on his back with and Red triangle inside.
Hope someone have any idea of what i should try next.

on the phone itself, can you get to bootloader?

Tomcat27 said:
I Think my device is lost. It´s locked in boot of my Gummynex rom.
I´m not allowed to flash anything else, it´s like my filesystem is broken.
I have attached som screenshots of the error´s i get in galaxy nexus toolkit 5.6
I Have also tryed with Odin, but i cant seem to get odin to connect with the phone in fastboot.
If i try to go into recoverymode i get the android man lying on his back with and Red triangle inside.
Hope someone have any idea of what i should try next.
Click to expand...
Click to collapse
Try using fastboot commands to flash the stock img files instead of the toolkit.

jhernand1102 said:
Try using fastboot commands to flash the stock img files instead of the toolkit.
Click to expand...
Click to collapse
But when i download the files from Google´s homepage there is only 1 file.
Shouldn´t it be enough ?
It´s the yakju-imm76d-factory-c6e807a1.tar file for my phone.

Tomcat27 said:
But when i download the files from Google´s homepage there is only 1 file.
Shouldn´t it be enough ?
It´s the yakju-imm76d-factory-c6e807a1.tar file for my phone.
Click to expand...
Click to collapse
extract the files.

But when i extract the files with winrar, i still only get 1 file ?

Tomcat27 said:
But when i extract the files with winrar, i still only get 1 file ?
Click to expand...
Click to collapse
Extract it again.
Sent from my Galaxy Nexus using xda premium

I´ve extracted the files again. now i have 6 img files.
boot
bootloader
radio
recovery
system
userdata
Flashed all the files to the phone, each time i get an error like before, but i can see in the fast boot screen that baseband versions ect. changes.
But unfortunatly the phone still won´t boot.
I have locked it again, and will take it to the store for repair if someone don´t have some good ideas
Thank you in advance

unlock the bootloader ( fastboot oem unlock )
5) Open up Command Prompt or Terminal, navigate to the folder you've extracted it all too and enter the following commands waiting for each to finish
Windows
fastboot-windows flash bootloader bootloader-maguro-primekk15.img
fastboot-windows reboot-bootloader
fastboot-windows flash radio radio-maguro-i9250xxkk6.img
fastboot-windows reboot-bootloader
fastboot-windows -w update image-yakju-icl53f.zip
Linux
./fastboot-linux flash bootloader bootloader-maguro-primekk15.img
./fastboot-linux reboot-bootloader
./fastboot-linux flash radio radio-maguro-i9250xxkk6.img
./fastboot-linux reboot-bootloader
./fastboot-linux -w update image-yakju-icl53f.zip
OSX
./fastboot-mac flash bootloader bootloader-maguro-primekk15.img
./fastboot-mac reboot-bootloader
./fastboot-mac flash radio radio-maguro-i9250xxkk6.img
./fastboot-mac reboot-bootloader
./fastboot-mac -w update image-yakju-icl53f.zip
6) The last step is to lock the bootloader. Restart the phone into the bootloader
7) Open CMD in the location of Superboot and type:
fastboot-windows oem lock

Help Needed
Guys,
I need any help possible although I fear I may be beyond recovery. Basically my Galaxy Nexus is bricked, I had been running 4.0.4 (IMM76D) on it. The phone is rooted and unlocked.
When switching the phone on, all I get is Google and the unlocked keypad. Will not progress further. I can boot into fastboot mode, and sometimes into recovery however although I have files showing on the SD, when I choose them I get a message declaring the path empty.
My main issue is that the handset is not recognised by my computer (running windows 7 and also since yesterday a dual boot of Ubuntu). This results in my Nexus toolkit and the AdamOutler tool being of no use as they do not recognize the device.
Any help/advice will be greatly appreciated as I'm at my wits end

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.

How to re-lock Bootloader of all Potter version

Hi guys, finally I succed in relock my XT1685 Bootloader on RETEU, so I will guide you to relock your bootloader.
DISCLAIMER:
Code:
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed.
YOU are choosing to make these modifications,
and if you point the finger at me for messing up your device, I will laugh at you.
and I am also not responsible for anything happens as a result of flashing these files
What you need :
1- Motorola drivers :
64-bit
32-bit
2- Minimal ADB and Fastboot:
Minimal ADB and Fastboot
3- Stock Fastboot flashable official firmware.
Here is the donwload of NPNS25.133-37-11 it should be perfect for lock BL for all RETEU users:
Mirror 1 (MEGA)
Mirror 2 (GoogleDrive)
ATTENTION:
You will need the appropriate version of the firmware according to your device version
You need the same or later version of firmware that you have when you unlock your BL
Example: If when you unlock your bl you was on NPNS25.137-33-11 you need the same (or later) complete firmware because you can't downgrade.
Now let's start with the guide.
1- Install Minimal ADB and Fastboot.
2- Extract stock firmware to any folder.
3- Now copy all the stuff that is in Minimal ADB and Fastboot folder in the folder where you extract the firmware.
4- Connect your device in fastboot mode (power off the device and while you press VOL down button insert the USB cable).
5- Open ADB and Fastboot terminal (press SHIFT+right click on the folder where you extract the firmware and select "open command window here").
6- Now type in Fastboot terminal "fastboot devices" (without commas) to be sure that your device is recognized.
7- Type these command one by one on terminal
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 boot boot.img
fastboot oem lock
Now your device will restart and your BL will be locked.
Now for be sure reflash all the complete firmware repeat the point from 5 to 7 but insert this code now
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Now you will be able to receive the OTA update with your locked BL.
{
"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"
}
Thanks to @Nirbhay2

aSaro12 said:
You will need the appropriate version of the firmware according to your device version
You need the same or later version of firmware that you have when you unlock your BL
Click to expand...
Click to collapse
Thank you!
I like to comment that these two topics are the key points to do it right. :highfive:

manos78 said:
Thank you!
I like to comment that these two topics are the key points to do it right. :highfive:
Click to expand...
Click to collapse
Yes, this is a little but important thing. :good::good:

Duplicate Thread
Read before posting
There is already thread for relocking bootloader : https://forum.xda-developers.com/g5-plus/how-to/lock-bootloader-moto-g5-plus-indian-t3638835

siddhesh9146 said:
Duplicate Thread
Read before posting
There is already thread for relocking bootloader : https://forum.xda-developers.com/g5-plus/how-to/lock-bootloader-moto-g5-plus-indian-t3638835
Click to expand...
Click to collapse
That thread is specific for Indian Variant.
And if you read carrefully I've mentioned the writer of the thread that you've posted.

Thank you!!
That worked perfectly on XT1685. Much appreciated.

Thanks
It's works. I'm successfully re-locked my bootloader. But i have a question.
Can i get OTA updates if bootloader says me "Software status: Modified"?

SeRi0uS007 said:
It's works. I'm successfully re-locked my bootloader. But i have a question.
Can i get OTA updates if bootloader says me "Software status: Modified"?
Click to expand...
Click to collapse
My Software status is also Modified and I never got ota's I always had to manually clean flash stock images. If someone found a way I would love to know how to get ota's on stock rom.

Thank you. my phone can get OTG now.

I tried yesterday on a XT1685 with the RETAIL firmware... and I broke something because my g5 plus cannot connect to GSM anymore (PIN asked but no LTE and no call possible). Bootloader is locked so I try to send back my phone to amazon for repair (exchange)... Sometimes **** happens !

pfufux said:
I tried yesterday on a XT1685 with the RETAIL firmware... and I broke something because my g5 plus cannot connect to GSM anymore (PIN asked but no LTE and no call possible). Bootloader is locked so I try to send back my phone to amazon for repair (exchange)... Sometimes **** happens !
Click to expand...
Click to collapse
same as here... revert back to stock but no signal..
i had xt1685 RETAIL too.. what did you flashed?
what happen with Amazon?

tufoz said:
same as here... revert back to stock but no signal..
i had xt1685 RETAIL too.. what did you flashed?
what happen with Amazon?
Click to expand...
Click to collapse
I don't remember what I flashed... but I think it's what I found in this post (NPNS25.133-37-11). I sent my phone to Amazon (fr) and it should be back today; I think I won't try again to flash Lineage or other because it seems to cause some troubles with IMEI when returning to stock, as I saw here and here.

pfufux said:
I don't remember what I flashed... but I think it's what I found in this post (NPNS25.133-37-11). I sent my phone to Amazon (fr) and it should be back today; I think I won't try again to flash Lineage or other because it seems to cause some troubles with IMEI when returning to stock, as I saw here and here.
Click to expand...
Click to collapse
My phone is back with a new motherboard... and so, a new IMEI. More details :
BASEBAND : M8953_37.46.07.47R POTTER_EMEADSDS_CUST
BUILD : NPN25.137-93

pfufux said:
My phone is back with a new motherboard... and so, a new IMEI. More details :
BASEBAND : M8953_37.46.07.47R POTTER_EMEADSDS_CUST
BUILD : NPN25.137-93
Click to expand...
Click to collapse
Everyone else is getting the 137-92 update, why does yours say 137-93?

I don't know but the update came from OTA.

pfufux said:
I don't know but the update came from OTA.
Click to expand...
Click to collapse
you confirm me that amazon replaced your phone? i think i will do the same thing

Ok .. i tried the procedure again.. I used 137.33.11 cid 50 NPNS but i got this error messages..
when flashing system: invalid signed image
when flashing bootloader "security downgrade version"...
any hint?

tufoz said:
you confirm me that amazon replaced your phone? i think i will do the same thing
Click to expand...
Click to collapse
I confirm Amazon changed the motherboard of my phone. I have a new IMEI number.

I can't re lock bootloader
Hi, i am trying to install stock rom and relock bootloader because after installing custom rom, i am not getting network in my device. but now after installing stock rom(see below image for version), i cant relock my bootloader. it gives me error like security downgrade issue.

Thanks a lot
:good::good::good::good:
the indian variant relock is not correctly explained
You Have Explained It
Listen all
You will need the firmware which you were using before unlocking your bootloader then only you can relock it again
Now i can give it for warranty Thanks a Lot

Found a way to recover hard brick bootloader

Hello guys,
I have found a way to restore hard brick "flashing led", but the problem is that now i have device with erased system and locked bootloader, cant flash anything due to "(bootloader) Preflash validation failed", tryed to download few firmware files to try but nothing can be flashed so far.
Do you guys know how to flash kernel and stock recovery img files with locked bootloader.
Note*: Cant unlock bootloader since "Oem unlocking" is not enabled and cant enable it since it cant boot, fastboot oem unlock gives "(bootloader) feature disabled".
So to summarize this, got bootloader back, cant boot, cant unlock bootloader, need official signed latest boot.img and recovery.img.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

magix01 said:
Hello guys,
I have found a way to restore hard brick "flashing led", but the problem is that now i have device with erased system and locked bootloader, cant flash anything due to "(bootloader) Preflash validation failed", tryed to download few firmware files to try but nothing can be flashed so far.
Do you guys know how to flash kernel and stock recovery img files with locked bootloader.
Note*: Cant unlock bootloader since "Oem unlocking" is not enabled and cant enable it since it cant boot, fastboot oem unlock gives "(bootloader) feature disabled".
So to summarize this, got bootloader back, cant boot, cant unlock bootloader, need official signed latest boot.img and recovery.img.
Click to expand...
Click to collapse
How have you managed to enter the "bootloader" mode?

You don't need an unlocked bootloader to flash stock firmware via fastboot
Just download the firmware and use fastboot to flash it (all parts)
https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897
Plus what did you use to re-image the bootloader?

I cant flash stock i tryed from that page "Moto G5 - Nov 2017 firmware NPP25.137-93", when it gets to boot/recovery imgs it says:
Method i tryed to get bootloader.img back is related to dissasembly of the phone and shorting emmc pins to get unrestricted access to the memory and while mounted you can use dd to flash bootloader, unfortunately it doesnt boot for some reason so i must flash other system files with bootloader which i cant. I will reveal entire method if i suceed to boot it, but its locked.

magix01 said:
I cant flash stock i tryed from that page "Moto G5 - Nov 2017 firmware NPP25.137-93", when it gets to boot/recovery imgs it says:
Method i tryed to get bootloader.img back is related to dissasembly of the phone and shorting emmc pins to get unrestricted access to the memory and while mounted you can use dd to flash bootloader, unfortunately it doesnt boot for some reason so i must flash other system files with bootloader which i cant. I will reveal entire method if i suceed to boot it, but its locked.
Click to expand...
Click to collapse
try rewrite bootloader, I don't know if it will work, but try.

magix01 said:
I cant flash stock i tryed from that page "Moto G5 - Nov 2017 firmware NPP25.137-93", when it gets to boot/recovery imgs it says:
Method i tryed to get bootloader.img back is related to dissasembly of the phone and shorting emmc pins to get unrestricted access to the memory and while mounted you can use dd to flash bootloader, unfortunately it doesnt boot for some reason so i must flash other system files with bootloader which i cant. I will reveal entire method if i suceed to boot it, but its locked.
Click to expand...
Click to collapse
Pls. provide the method to unbrick we will try flash firmware other versions.
Please give full info how to unbrick. Thanks.

if you share the method
ASHDCBZ said:
Pls. provide the method to unbrick we will try flash firmware other versions.
Please give full info how to unbrick. Thanks.
Click to expand...
Click to collapse
if you share the method, so faster we can find a way to revive the g5 and you would help us all
si comparte el metodo, asi mas rapido podremos buscar la forma de revivir el moto g5 y nos ayudarias a todos

This method is derived from reverse engeneering an exploit from a hardware box released on gsm forums i cant share it now, not until i have full method with system booting then i will share.

magix01 said:
This method is derived from reverse engeneering an exploit from a hardware box released on gsm forums i cant share it now, not until i have full method with system booting then i will share.
Click to expand...
Click to collapse
You have to flash the entire firmware in order - not just boot.img (which is the kernel)
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot

I tryed that and get the same message as soon as it gets to boot.img "Preflash Validation Failed", i flashed 7.1 android bootloader on it, it looks like i am flashing older roms and i cant find latest rom download, tryed version 93 same thing?

magix01 said:
I tryed that and get the same message as soon as it gets to boot.img "Preflash Validation Failed", i flashed 7.1 android bootloader on it, it looks like i am flashing older roms and i cant find latest rom download, tryed version 93 same thing?
Click to expand...
Click to collapse
Hi,
I think you have to flash a newer bootloader and ROM like this one : https://drive.google.com/file/d/1hlNzlFhLCEj6xigfKrYcvnwH9jy3f5j3/view (XT1676 CEDRIC_NPPS25.137-93-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml)

006fazer said:
Hi,
I think you have to flash a newer bootloader and ROM like this one : https://drive.google.com/file/d/1hlNzlFhLCEj6xigfKrYcvnwH9jy3f5j3/view (XT1676 CEDRIC_NPPS25.137-93-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml)
Click to expand...
Click to collapse
I think that should work because he is having the bootloader version B8.24 and the rom posted on XDA having B8.23

006fazer said:
Hi,
I think you have to flash a newer bootloader and ROM like this one : https://drive.google.com/file/d/1hlNzlFhLCEj6xigfKrYcvnwH9jy3f5j3/view (XT1676 CEDRIC_NPPS25.137-93-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml)
Click to expand...
Click to collapse
Still cant flash it, however i tried your firmware, flashed bootloader, now version changed from B8.23 to B8.25, but when i get to fastboot flash boot boot.img i still get:
sending 'boot' (16384 KB)...
OKAY [ 20.642s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 20.830s
This happens on B8.25 new version, got anything else to try?
Edit: I flashed B8.23 bootloader and it bricked the phone again to Qcom loader... this time it wont flash bootloader with exploit again so its dead 100% i think.

Obviously don't try and downgrade the bootloader
Can you just flash twrp recovery & access recovery mode to flash a custom rom?

Cant, the bootloader i flashed was locked, and to flash twrp you need to unlock it wich i cant because of no oem unlock.

magix01 said:
Cant, the bootloader i flashed was locked, and to flash twrp you need to unlock it wich i cant because of no oem unlock.
Click to expand...
Click to collapse
You would have to say how you rreimaged the bootloader so those with unlocked bootloaders can try
I take it you used something like z3x or similar software

I used JTAG flasher from GSM forum, but the thing is my bootloader used to be unlocked then after flash it went to locked status and CID was 0xDEAD, basically now i cant every fix it with jtag so its dead totally.

try with RSD Lite, is automated

Tried still same problem just this time it fails with gpt.bin, also the phone is totally bricked again so ...

magix01 said:
I tryed that and get the same message as soon as it gets to boot.img "Preflash Validation Failed", i flashed 7.1 android bootloader on it, it looks like i am flashing older roms and i cant find latest rom download, tryed version 93 same thing?
Click to expand...
Click to collapse
Yeah, that's pretty ****ed up

How to flash stock firmware on my XT2045-2?

Recently I rooted my Moto G8 (XT2045-2) phone, booted up TWRP and tried to install LineageOS. But somethign went wrong (I don't know what exactly) and my phone only booted into bootloader mode.
So now I am unsuccessfully trying to restore the stock firmware.
I downloaded the firmware (version RAV_RETAIL_10_QPJS30.63-35-1-15_subsidy-DEFAULT_regulatory-DEFAULT_CFC) and tried flashing it by doing the following commands:
Code:
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 flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
Every single one of those commands completed successfully, but booting the phone still only gets me to the bootloader screen.
Trying to boot into recovery mode also just gets me to the bootloader.
Next I tried to just flash TWRP by doing:
Code:
fastboot flash recovery twrp-3.4.0-0-rav-test6.img
.
Command completes successfully, but booting into recovery mode afterwards still only gets me to the bootloader screen.
I can boot into TWRP via
Code:
fastboot boot twrp-3.4.0-0-rav-test6.img
.
Any idea what the problem is with my phone?
Or what my next step could be to salvage this phone?

You have to be in fastbootd mode when you flash firmware. Try this out from the bootloader...
Code:
fastboot reboot fastboot
That should switch you to fastbootd mode. If it doesn't, then boot up twrp, and from the menu select reboot>fastboot.

Thanks.
When I try
Code:
fastboot reboot fastboot
I just get
Code:
fastboot: usage: unknown reboot target fastboot
TWRP also doesn't show me fastboot option.
The only reboot options I have are:
- System
- Power Off
- Recovery
- Bootloader
- Edl
- Slot A
- Slot B
Any other ideas?

Try updating fastboot/adb.

Spaceminer said:
Try updating fastboot/adb.
Click to expand...
Click to collapse
Thanks, I got one step further with that.
The command actually went through but the phone just booted in normal bootloader mode again and i got the following error:
Code:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

Chaos156 said:
Thanks, I got one step further with that.
The command actually went through but the phone just booted in normal bootloader mode again and i got the following error:
Code:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Click to expand...
Click to collapse
That sounds promising. Try this... Flash your stock recovery then rerun that command.

.

Spaceminer said:
That sounds promising. Try this... Flash your stock recovery then rerun that command.
Click to expand...
Click to collapse
Flashing the stock recovery did not work. it said the flashing process was successfull, but the phone still only boots into bootloader mode when I try to boot recovery after flashing.
The following got me into fastbootd though:
Code:
fastboot boot recovery.img
Where recovery.img is the stock recovery.
I tried flashing the stock ROM in fastbootd mode and at first it seemed to be successfull. No error messages.
But rebooting afterwards just gets me back into bootloader mode. Neither system nor recovery are booting.

I think that I have an idea that will work. Boot up twrp. Unzip this and copy the entire folder to /sdcard/TWRP. Then use twrp to restore this recovery image. (The backup name is "z") After that reboot to recovery and see if it works. If it does, then use stock recovery to switch to fastbootd, and try flashing your firmware again.

I unzipped and copied the BACKUP to /sdcard/TWRP.
But sadly I encountered the next problem almost immediately.
My TWRP restore screen looks like 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"
}
The only "package" to restore was the empty cache folder.
I tried to switch the storage, but the Micro SD card option and the USB Storage option were not selectable at all.
Next I used TWRPs file manager to copy the BACKUP from sdcard to /cache. Had no luck with that though either.
The cache folder on the Restore screen was still empty.
I selected the cache package just to see what would happen if I try to restore it.
The following happened:
The stuff below [RESTORE STARTED] are the error messages for the restore process.
All the error messages above happen every time i boot into TWRP.

@Chaos156
I'm not sure what to make of that but I have a few ideas. It looks like /data is trashed in some way.
Idea #1
Boot twrp, then wipe>format>type "yes" to continue. Then reboot directly to the bootloader, and from there, boot up twrp again and try restoring that recovery image.
Idea #2
Boot twrp. Rename recovery.emmc.win to recovery.img and try directly flashing it using twrp's install image option.
Idea #3
Also grab the latest twrp from Vache and try using that. I believe we're up to twrp 3.5.0. It should be posted in the development threads.

I got the newest TWRP and did the format/wipe. I think that fixed 50% of my problem!
I no longer get the "failed to mount /data" errors. But the "Failed to mount /metadata" errors continue.
Any idea on how to fix the metadata partition too?
Installing that image didn't work. The installation went well, but after rebooting I was just back in bootloader mode.

Chaos156 said:
I got the newest TWRP and did the format/wipe. I think that fixed 50% of my problem!
I no longer get the "failed to mount /data" errors. But the "Failed to mount /metadata" errors continue.
Any idea on how to fix the metadata partition too?
Installing that image didn't work. The installation went well, but after rebooting I was just back in bootloader mode.
Click to expand...
Click to collapse
From the bootloader try,
Code:
fastboot erase metadata
Edit: If that doesn't work, try it with twrp using fasbootd.

I erased the metadata, but even after flashing an image it just boots into bootloader mode still.
I tried it twice; once from bootloader and once from TWRP fastbootd.
It says your image was flashed successfully but it still doesn't boot afterwards.
The metadata partition errors also still persist.
I can also no longer boot the stock recovery via "fastboot boot stock_recovery.img". It just shows the "No command" error. Same if I try to boot your recovery.img directly via "fastboot boot recovery.img".

You can try to run BlankFlash to fix it

Chaos156 said:
I erased the metadata, but even after flashing an image it just boots into bootloader mode still.
I tried it twice; once from bootloader and once from TWRP fastbootd.
View attachment 5212679
It says your image was flashed successfully but it still doesn't boot afterwards.
The metadata partition errors also still persist.
I can also no longer boot the stock recovery via "fastboot boot stock_recovery.img". It just shows the "No command" error. Same if I try to boot your recovery.img directly via "fastboot boot recovery.img".
Click to expand...
Click to collapse
This is probably your best bet at this point. In order for fastbootd to work, you need either twrp or the stock recovery to flash properly to the recovery partition. You should be able to install the stock recovery from the bootloader since it's not a dynamic partition. Then just reboot into fastbootd and get it fixed up. For some reason, that doesn't seem possible. So I'm not sure what's going on with your phone at this point. Scope out lolinet. They probably have a blank flash for our device. If not, let me know and I'll trying digging one up from some folks on the gsmhosting forums. If you need QPST utilities to run the blank flash, also let me know and I'll link it.

lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com

I found the blank flash on lolinet and it included the qboot utility version 3.86.
I tried using the bash script :
Code:
./blank-flash.sh
But it just just said "< waiting for device >" without ever detecting my phone.
Calling "./qboot devices" directly did not list my device where both "fastboot devices" and "adb devices" found my phone.
I tried searching for qboot to see if a newer version than 3.86 might exist, but I can't find any source for qboot at all.

Did you run from bootloader, fastboot oem blanklash

Chaos156 said:
I found the blank flash on lolinet and it included the qboot utility version 3.86.
I tried using the bash script :
Code:
./blank-flash.sh
But it just just said "< waiting for device >" without ever detecting my phone.
Calling "./qboot devices" directly did not list my device where both "fastboot devices" and "adb devices" found my phone.
I tried searching for qboot to see if a newer version than 3.86 might exist, but I can't find any source for qboot at all.
Click to expand...
Click to collapse
You need to be in EDL (emergency download mode) to use a blank flash. Try booting twrp and check the reboot options. It should be there. I'm just not sure if it'll work. If it does work, it might not look like anything is going on. My G7 play in EDL mode, just had a black screen and looked like it was turned off, but the backlight was on. When connected to my PC, it appeared as something like QHUSB in my device manager.