So this weekend, this is the 3rd incident. Senior developers kindly help resolve the issue.
1.Bootloader unlocked. Rooted. Custom ROMs used and then flashed stock ROM. Everything worked fine.
2.Flashed stock ROM and locked Bootloader. Still fine.
3.Unlocked Bootloader again and installed custom ROMs. Still fine.
4.Flashed stock ROM and phone hard bricked.
Phone LED just keeps blinking. No vibration or screen on. Cannot boot into bootloader.
This may be because of flashing conflicting versions of the bootloader (or older over newer).
Similar incidence reported with Moto G5 Cedric. This also means installing OTA might hardbrick the phone (after reflashing stock after unlocking the bootloader). We don't yet have the blankflash file to repair G5S from hardbricks(or do we?).
Is there a particular version of stock ROM we are supposed to flash?
Senior developers kindly guide, and issue the appropriate warning to prevent further phones from hard bricks(if this is an issue).
@lohanbarth @kalyansundhar @govind1233 @vaserbanix
It turns out that the hard brick is a result of flashing older bootloader over newer one and installing OTA after returning to stock (happens in Cedric too).
So how do we recover the phone now? Blankflash method?
It turns out that the hard brick is a result of flashing older bootloader over newer one and installing OTA after returning to stock (happens in Cedric too).
So how do we recover the phone now? Blankflash method?
ShattrdChain said:
So this weekend, this is the 3rd incident. Senior developers kindly help resolve the issue.
1.Bootloader unlocked. Rooted. Custom ROMs used and then flashed stock ROM. Everything worked fine.
2.Flashed stock ROM and locked Bootloader. Still fine.
3.Unlocked Bootloader again and installed custom ROMs. Still fine.
4.Flashed stock ROM and phone hard bricked.
Phone LED just keeps blinking. No vibration or screen on. Cannot boot into bootloader.
This may be because of flashing conflicting versions of the bootloader (or older over newer).
Similar incidence reported with Moto G5 Cedric. This also means installing OTA might hardbrick the phone (after reflashing stock after unlocking the bootloader). We don't yet have the blankflash file to repair G5S from hardbricks(or do we?).
Is there a particular version of stock ROM we are supposed to flash?
Senior developers kindly guide, and issue the appropriate warning to prevent further phones from hard bricks(if this is an issue).
@lohanbarth @kalyansundhar @govind1233 @vaserbanix
Click to expand...
Click to collapse
EDIT.
i see your last post!
your pc see the phone?
Yes. But as qualcomm hs dloader 9008 = EDL mode.
ShattrdChain said:
Yes. But as qualcomm hs dloader 9008 = EDL mode.
Click to expand...
Click to collapse
Yes please provide the solution soon.
Any Information regarding blank flash files moto G5s MSM8937.
Please help us, there's any solution? I don't care if im not able to use stock roms again, i just want my phone back, can anyone help us?
Please provide solution as Motorola service centers also not helping they said cant do on unlocked bootloader.
I wants to help you, but you have to give me some information.
ShattrdChain said:
1.Bootloader unlocked. Rooted. Custom ROMs used and then flashed stock ROM. Everything worked fine.
2.Flashed stock ROM and locked Bootloader. Still fine.
3.Unlocked Bootloader again and installed custom ROMs. Still fine.
4.Flashed stock ROM and phone hard bricked.
Click to expand...
Click to collapse
Which versions of stock ROM's did you flash? The previous one and the last one(with link please).
Did you also tried ZUI ROM?
ShattrdChain said:
This may be because of flashing conflicting versions of the bootloader (or older over newer).
Click to expand...
Click to collapse
Yes, and maybe you flash gpt.bin.
If you have your phone connected. You see qualcomm hs dloader 9008. Are the drivers good installed? Can you find the phone with fastboot? If you can flash. Flash this bootloader and maybe gpt.bin(http://www.mediafire.com/file/bbnhi...bsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) source: https://forum.xda-developers.com/mo...h-official-firmware-moto-g5s-montana-t3687768
If you succeeded to boot into the bootloader. Flash TWRP and never flash stock ROM again.
https://forum.xda-developers.com/mo...h-official-firmware-moto-g5s-montana-t3687768 This Stock ROM.
Now bootloader cannot be accessed. Phone just keeps blinking notification light and nothing else happens. Cannot enter into fastboot mode. So nothing can be flashed.
More and more Moto G5S getting hard bricked every day. Guys, DO NOT FLASH STOCK ROM IF YOU HAVE APPLIED OTA. There is no blankflash file available so there is no way to recover the phone. Your phone is dead. BE CAREFUL.
https://forum.xda-developers.com/moto-g5s/how-to/blank-flash-montana-t3765150
hope this thread helps you!
even i got my device bricked after flashing zui rom
something new with the flash blank
Related
Hi Guys,
Not sure if much can be done, so before I flashed a rom for 5.1.1, I decided to flash the required, firmware 2.9.710.x, but before flashing that, I re-locked my bootloader, as I have s-on. Before that, I was trying to get the OTA to work but it didn't as I had mounted system as r/w. So I had stock recovery, s-on and relocked bootloader. After I flashed the firmware, I could not unlock the bootloader as there is some new developer setting that I am required to enable. BUT the I am still on old 5.0 ROM that will not boot anymore and is stuck on the splash screen - I've tried wipe cache and factory reset. I have an RUU for 1.32 which I cannot use because now I have 2.9.710.x firmware. I've also tried to sideload the OTA but that will not work because system was mounted r/w
Is there anything I can do to get it to work? I feel like I've tried all avenues, but if there is something you guys think I can do to make it work again, I'd be over the moon!
anshuashmeet said:
Hi Guys,
Not sure if much can be done, so before I flashed a rom for 5.1.1, I decided to flash the required, firmware 2.9.710.x, but before flashing that, I re-locked my bootloader, as I have s-on. Before that, I was trying to get the OTA to work but it didn't as I had mounted system as r/w. So I had stock recovery, s-on and relocked bootloader. After I flashed the firmware, I could not unlock the bootloader as there is some new developer setting that I am required to enable. BUT the I am still on old 5.0 ROM that will not boot anymore and is stuck on the splash screen - I've tried wipe cache and factory reset. I have an RUU for 1.32 which I cannot use because now I have 2.9.710.x firmware. I've also tried to sideload the OTA but that will not work because system was mounted r/w
Is there anything I can do to get it to work? I feel like I've tried all avenues, but if there is something you guys think I can do to make it work again, I'd be over the moon!
Click to expand...
Click to collapse
Never relock if your phone is not 100 % stock. Otherwise it won't boot. Besides there are already numerous post written by people that made the same mistake as you did. Even if your phone could boot you wouldn't be able to enable the OEM Unlock option since it's not implemented in the 1.XX roms and by flashing the firmware you do not update your rom.
I guess the only possibility to recover your phone is using this RUU service.
Just because I'm curious: Why didn't you use one of the backups that are provided here?
Flippy498 said:
Never relock if your phone is not 100 % stock. Otherwise it won't boot. Besides there are already numerous post written by people that made the same mistake as you did. Even if your phone could boot you wouldn't be able to enable the OEM Unlock option since it's not implemented in the 1.XX roms and by flashing the firmware you do not update your rom.
I guess the only possibility to recover your phone is using this RUU service.
Just because I'm curious: Why didn't you use one of the backups that are provided here?
Click to expand...
Click to collapse
Thanks for your reply!
I've submitted an enquiry form to them. Didn't know that service existed. Hopefully they have the RUU file that I need.
I did download the stock backup file from that link but I thought before I give it a go, I'll try and get an OTA and get an official update. That failed so I decided to flash the firmware before going to the latest rom. Forgetting I just locked my bootloader with stock recovery, completely unaware of this 5.1 developer option issue. My fault for not doing research, but I didn't know such issue could exist as for the last few years, I haven't had an issue like this. Normally issues occur if I flash a newer ROM without firmware so was trying to avoid that.
I'm an idiot who just assumed that the unlocked phone he bought new in Europe was the European version (dual-SIM) and didn't first take a backup of all the partitions before messing around with it.
I'm wondering if I got sold some other region's hardware by a shady seller. How can I tell? Do I just have to flash every firmware out there until I get it to boot, or is there another way?
Model: XT1635-02
Type: M1D64
And dual-SIM.
I unlocked the bootloader, flashed TWRP, decided that I wanted to take the OTA, reflashed recovery to stock from the latest EU package...and it would no longer boot. Flashed back to TWRP, same. Reflashed the entire firmware package following these instructions, but it still won't boot.
Thanks.
--
Update: after considerable fiddling, I reloaded TWRP and got it to install and boot the Cyanogenmod 14.1 release, meaning my device is not permanently trashed beyond repair-- it just doesn't like any of the firmwares I've tried to feed it. Obviously this is still sub-optimal since CM requires some blobs that Moto haven't yet released to support the camera etc., but it's better than nothing. My goal is still to get stock firmware back onto this phone.
Update2: buoyed by my CM14.1 success, I decided to try to apply a similar methodology to get the stock firmware running. I failed utterly. Maybe if I build a TWRP-flashable copy of the stock RETEU package I could get it to flash fully and boot, but all it does at this point is loop over the bootloader unlock warning screen and occasionally attempt to auto-erase itself in Recovery before bootlooping again.
Update3: aaaand my IMEI is "0." This seems bad.
boot to fastboot screen and take a pic of it and post it.
I know its bootloader is locked, but what happens if I try to flash trough fastboot? I mean, in the black kinda console screen after you press Power button + Vol Down button.
ADB interface recognize this, but I'm pretty afraid to make my Moto Z a hard dead block. So, have anyone did this?
Just in case, I want to do exactly this https://www.youtube.com/watch?v=d_YO__aYM7M&t=448s but on my Droid version, the tutorial is on spanish but I know you will understand the video
rusa-raus said:
Just in case, I want to do exactly this https://www.youtube.com/watch?v=d_YO__aYM7M&t=448s but on my Droid version, the tutorial is on spanish but I know you will understand the video
Click to expand...
Click to collapse
So if I've understood you correctly, you're looking to flash Android Oreo onto your device via fastboot?
With a locked bootloader, it's pretty difficult to hard brick your device whilst flashing, just be careful that you have a stable power supply (both to your computer and to your device, and that you have plenty of time). With a locked bootloader, you can only flash the same or newer firmware than you currently have on your device, the bootloader will otherwise block you from flashing older firmwares.
That being said, you'd need the Verizon stock ROMs to flash on a Droid if I recall correctly. The retail Oreo stock ROM we have here may not work and your locked bootloader may force you to flash only Verizon firmwares, so your best bet may be to either wait for the Verizon Oreo OTA, find the Verizon OTA on XDA or hope that someone uploads the Verizon Oreo firmware.
echo92 said:
So if I've understood you correctly, you're looking to flash Android Oreo onto your device via fastboot?
With a locked bootloader, it's pretty difficult to hard brick your device whilst flashing, just be careful that you have a stable power supply (both to your computer and to your device, and that you have plenty of time). With a locked bootloader, you can only flash the same or newer firmware than you currently have on your device, the bootloader will otherwise block you from flashing older firmwares.
That being said, you'd need the Verizon stock ROMs to flash on a Droid if I recall correctly. The retail Oreo stock ROM we have here may not work and your locked bootloader may force you to flash only Verizon firmwares, so your best bet may be to either wait for the Verizon Oreo OTA, find the Verizon OTA on XDA or hope that someone uploads the Verizon Oreo firmware.
Click to expand...
Click to collapse
Understood, seems like Verizon is not gonna update Moto Z Play...
Hi guys,
I have a problem I need some advice for. A year ago, I purchased my Amami for the purpose of GPS-navigation on my bicycle. It always worked fine and I was able to charge it with my dynohub without any issues. The charging is giving me a headache now though, and all troubleshooting points at the phone being the problem.
Now, a couple months ago I decided to ditch 4.4 and go for a custom ROM (I've tried Oreo and Pie) which worked fine, but the phone doesn't charge as well as it used to on my bike. I'd like to go back to stock to see if that's what is causing the issue and used the Xperia Flashtool to revert to a stock image, but the ones that used to work on the phone now give me bootloops after I've flashed TWRP and ResurrectionRemix and Lineage OS.
Is there anything I need to know before I flash a stock firmware with the tool? Any input would be appreciated.
Sounds like to have not updated to Lolipop and therefore you do not have real recovery. Is your bootloader unlocked? Then you can try EMMA to update to Lollipop.
jho55 said:
Sounds like to have not updated to Lolipop and therefore you do not have real recovery. Is your bootloader unlocked? Then you can try EMMA to update to Lollipop.
Click to expand...
Click to collapse
My bootloader is unlocked, I have TWRP installed and am currently running Lineage OS (Android 8). It doesn't matter if I flash Sony's original Kitkat or Lollipop; both will have bootloops. No offense, but I'm not sure you understood my original post: I'd like to go back to an old stock ROM, because 4.4 is the one that I'm sure have me no trouble with charging on my bike.
Proper BL relock:
https://forum.xda-developers.com/xperia-z/general/tutorial-relock-xperia-z-bootloader-t2191907https://forum.xda-developers.com/xperia-z/general/tutorial-relock-xperia-z-bootloader-t2191907
If you use twrp in fotakernel partition maybe necassary to write back original fotakernel.sin (inside stock.ftf) before relock with flashtool. Remember! After relock with flastool the new BL unlock key here: DEVICESERIAL \ unlock.txt
Hi folks,
I searched the forum and did not find a suitable thread that answered my question.
My Moto G5 has a charging problem and I want to give it back for a repair - it still has warranty.
I have read that flashing a custom rom does not necessarily invalidate the warranty, but to ensure that Motorola will repair the phone I would like to flash a stock (nougat) rom.
Is it possible without the risk of losing IMEI or other stuff?
Or do you recommend to send it back to Motorola with the custom rom installed?
Thank you VERY MUCH in advance!!!
Kind regards
Wolf
They will be able to see you have unlocked the bootloader regardless of whether you re-lock it
Just download the latest stock firmware and flash it via fastboot
If your base firmware is already oreo you can skip flashing gpt and bootloader to avoid risking hard brick
Don't downgrade your base firmware eg if it's oreo don't flash nougat (base firmware is stock firmware not custom rom)
I would flash it back to stock rom so at least they can't blame custom rom
Thanks!! I'm not sure, if it was delivered with Android 7 or 8. But I can flash 8 in any case, because its no downgrade?
And a last question: can I flash it also with TWRP? It's installed anyways...
moped2000 said:
Thanks!! I'm not sure, if it was delivered with Android 7 or 8. But I can flash 8 in any case, because its no downgrade?
And a last question: can I flash it also with TWRP? It's installed anyways...
Click to expand...
Click to collapse
Yes flash android 8 - note if it was never updated to android 8 you will also have to flash gpt and bootloader as well the rest of the firmware
You will need to flash the firmware via fastboot
Flashing via twrp is just like flashing a custom rom with no modifications & you will still have twrp installed and not stock recovery & still have a modified system partition etc
Thanks! Android 8 was definitely installed, only possibly not as stock firmware, but only as custom rom.
But I guess it's okay if I just flash all the files to make sure?
Motorola says, I have lost my warranty because I have opened the bootloader. They won't even fix it for money ****.
moped2000 said:
Motorola says, I have lost my warranty because I have opened the bootloader. They won't even fix it for money ****.
Click to expand...
Click to collapse
Depends what country you are in
In America or Europe you can argue and would most likely win in court that if your issue is totally unrelated to the unlocking of the bootloader they must repair it
Eg if the camera doesn't work because of a faulty component they must fix it
However if the camera stop working because you unlocked the bootloader & did some modifications causing it to no longer work then you're not covered
This would be the same for boot issues - If your phone no longer boots and you have unlocked the bootloader they can claim you have done a modification that now stops it booting
The general rule is if you unlock the bootloader than software/firmware booting issues are not covered but hardware faults unrelated to a bootloader unlock are
Again it varies depending on your country but the above is true for USA & the majority of Europe (EU)