When I wrote command 'adb reboot bootloader' It went off and after it didn't restart when I plug it in to computer it detects Qualcomm Hs-Usb Qdloader 9008
Any fix
OusaifShaka said:
When I wrote command 'adb reboot bootloader' It went off and after it didn't restart when I plug it in to computer it detects Qualcomm Hs-Usb Qdloader 9008
Any fix
Click to expand...
Click to collapse
Try pulling the battery. Then put it back in and hold power and volume down.
Did you erase the bootloader? What else did you do? Just rebooting bootloader would not do that. Did you erase the system or something? ADB commands only work while booted to system. Fastboot commands are for use in bootloader. Fastboot reboot bootloader
madbat99 said:
Try pulling the battery. Then put it back in and hold power and volume down.
Did you erase the bootloader? What else did you do? Just rebooting bootloader would not do that. Did you erase the system or something? ADB commands only work while booted to system. Fastboot commands are for use in bootloader. Fastboot reboot bootloader
Click to expand...
Click to collapse
I didn't erase anything. I just wanted to flash my E4 with RSDLite, but RSDLite was showing error in flashing gpt.bin failed or flash boot.img failed or flash recovery.img failed. Then I searched about it I found a way to flash firmware with Fastboot commands In Fastboot Commands I flashed some files but after that same error in Fastboot that FLash gpt.bin/boot.img/recovery.img was failed then I restarted my phone and it started and then I searched How to unlock bootloader of Moto E4 I found a video by following it I entered command adb reboot bootloader and when I pressed enter the phone went off and after it never restarted just shows black screen and nothing happens When I connect it to computer computer detects it as Qualcomm HS-USB QDLoader 9008 (COM5)
Please tell me any fix
OusaifShaka said:
I didn't erase anything. I just wanted to flash my E4 with RSDLite, but RSDLite was showing error in flashing gpt.bin failed or flash boot.img failed or flash recovery.img failed. Then I searched about it I found a way to flash firmware with Fastboot commands In Fastboot Commands I flashed some files but after that same error in Fastboot that FLash gpt.bin/boot.img/recovery.img was failed then I restarted my phone and it started and then I searched How to unlock bootloader of Moto E4 I found a video by following it I entered command adb reboot bootloader and when I pressed enter the phone went off and after it never restarted just shows black screen and nothing happens When I connect it to computer computer detects it as Qualcomm HS-USB QDLoader 9008 (COM5)
Please tell me any fix
Click to expand...
Click to collapse
Were you trying to flash an older firmware than what was on the device? If you flashed an older bootloader than what you had, you have a hard brick. Paperweight
madbat99 said:
Were you trying to flash an older firmware than what was on the device? If you flashed an older bootloader than what you had, you have a hard brick. Paperweight
Click to expand...
Click to collapse
Actually I have XT1766 Variant so There is only one firmware of this variant
See at firmware.center
I don't know it is older or newer
Please help me get out of this
OusaifShaka said:
Actually I have XT1766 Variant so There is only one firmware of this variant
See at firmware.center
I don't know it is older or newer
Please help me get out of this
Click to expand...
Click to collapse
No. There are many firmwares for xt1766. It's SPerry, aka sprint, boost, virgin mobile,etc version. They all use the same firmware, but there are many updates/full firmware packages.
https://androidfilehost.com/?w=files&flid=195327
Look towards the bottom at the Sperry firmwares. See? You likely flashed one older than the device had (you don't even know the firmware version?) And now have a hard brick.
I have the same device, and have seen others do what you did. It's dead. Your only chance is trying to return it to Motorola. Others have gotten replacement devices from Motorola saying it was a bad update.
But yeah, it's hard bricked. No coming back from that one.
The newest I've seen is SPERRY_SPRINT_NCQS26.69-64-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
So if you took ota updates, you were likely close to this build at least. You cannot flash a bootloader older than the one you are on.
madbat99 said:
No. There are many firmwares for xt1766. It's SPerry, aka sprint, boost, virgin mobile,etc version. They all use the same firmware, but there are many updates/full firmware packages.
https://androidfilehost.com/?w=files&flid=195327
Look towards the bottom at the Sperry firmwares. See? You likely flashed one older than the device had (you don't even know the firmware version?) And now have a hard brick.
I have the same device, and have seen others do what you did. It's dead. Your only chance is trying to return it to Motorola. Others have gotten replacement devices from Motorola saying it was a bad update.
But yeah, it's hard bricked. No coming back from that one.
The newest I've seen is SPERRY_SPRINT_NCQS26.69-64-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
So if you took ota updates, you were likely close to this build at least. You cannot flash a bootloader older than the one you are on.
Click to expand...
Click to collapse
My device is sperry_sprint This is firmware version of my device : XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
I tried to flash this but RSDLite and Fastboot gave me error
Please sir there should be something to unbrick it
madbat99 said:
No. There are many firmwares for xt1766. It's SPerry, aka sprint, boost, virgin mobile,etc version. They all use the same firmware, but there are many updates/full firmware packages.
https://androidfilehost.com/?w=files&flid=195327
Look towards the bottom at the Sperry firmwares. See? You likely flashed one older than the device had (you don't even know the firmware version?) And now have a hard brick.
I have the same device, and have seen others do what you did. It's dead. Your only chance is trying to return it to Motorola. Others have gotten replacement devices from Motorola saying it was a bad update.
But yeah, it's hard bricked. No coming back from that one.
The newest I've seen is SPERRY_SPRINT_NCQS26.69-64-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
So if you took ota updates, you were likely close to this build at least. You cannot flash a bootloader older than the one you are on.
Click to expand...
Click to collapse
I can't return my device to Motorola because I have bought it as a refurbished and in my city there is no Motorola service center
HeLP ME
OusaifShaka said:
I didn't erase anything. I just wanted to flash my E4 with RSDLite, but RSDLite was showing error in flashing gpt.bin failed or flash boot.img failed or flash recovery.img failed. Then I searched about it I found a way to flash firmware with Fastboot commands In Fastboot Commands I flashed some files but after that same error in Fastboot that FLash gpt.bin/boot.img/recovery.img was failed then I restarted my phone and it started and then I searched How to unlock bootloader of Moto E4 I found a video by following it I entered command adb reboot bootloader and when I pressed enter the phone went off and after it never restarted just shows black screen and nothing happens When I connect it to computer computer detects it as Qualcomm HS-USB QDLoader 9008 (COM5)
Please tell me any fix
Click to expand...
Click to collapse
So you tried to flash it before you unlocked the bootloader? You can't flash anything before the bootloader is unlocked. So did it ever unlock? If an older bootloader actually flashed in all that crazy bass ackwards flashing you did, it's toast. Nothing can be done. Sorry dude.
If you can get it to fastboot mode, you can still use rsdlite. Flashing the latest firmware of course. But not likely.
Related
Found a way to reboot to edl mode from fastboot
All credits to @emuzychenko
1) Download modified fastboot file
2) Reboot your phone to fastboot
3) Double click on edl.cmd
4) You are on 9008/edl mode
5) Flash any fastboot image from Mi flash
You successfully unbricked your device
Hi
Try with that method also. It seams to work .
Next time I brick it again (trust me, it will happen) I will give those a try.
This is the solution www(dot)htcmania.com(/)showthread(dot)php?t=1163463
Cheked by me, the brick was to try to unlock the bootloader without the Xiaomi message.
Sorry for my english, bu ti hope to be helpful.
To restore the default Bootloader copy paste the emmc_appsboot.mbn from Fastboot Rom to the Adb foldee
and type command on cmd
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot reboot
For those who have failed and stuck on "HS USB 900E" and the bootloader stick locked here is the solution :
1. Enter fastboot by holding vol down + power
2. Plug your RN3Pro to PC
2. Flash original bootloader from official fastboot firmware
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
3. Type again :
fastboot reboot
and quickly hold volume up untuk it enter "sideload" mode
4. Install Mi PC Suite from this link en.miui.com/thread-225600-1-1.html
5. Let the Mi PC Suite download the latest chinese firmware, just sit and wait until it done
6. Lets Brick the beast again
parfetto said:
Hi
Try with that method also. It seams to work .
Click to expand...
Click to collapse
this method only works for few very people, everyone cant access adb through recovery.
apixbuanget said:
For those who have failed and stuck on "HS USB 900E" and the bootloader stick locked here is the solution :
1. Enter fastboot by holding vol down + power
2. Plug your RN3Pro to PC
2. Flash original bootloader from official fastboot firmware
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
3. Type again :
fastboot reboot
and quickly hold volume up untuk it enter "sideload" mode
4. Install Mi PC Suite from this link en.miui.com/thread-225600-1-1.html
5. Let the Mi PC Suite download the latest chinese firmware, just sit and wait until it done
6. Lets Brick the beast again
Click to expand...
Click to collapse
Have you tested this method yourself? I think this is for people who bricked the device but had stock recovery inside, what about people who has twrp and bricked the device? Also I dont think you can flash anything through fastboot in locked bootloader
IT WORKS
apixbuanget said:
For those who have failed and stuck on "HS USB 900E" and the bootloader stick locked here is the solution :
1. Enter fastboot by holding vol down + power
2. Plug your RN3Pro to PC
2. Flash original bootloader from official fastboot firmware
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
3. Type again :
fastboot reboot
and quickly hold volume up untuk it enter "sideload" mode
4. Install Mi PC Suite from this link en.miui.com/thread-225600-1-1.html
5. Let the Mi PC Suite download the latest chinese firmware, just sit and wait until it done
6. Lets Brick the beast again
Click to expand...
Click to collapse
Worked like a magic. I can confirm for sure. Was stuck at HS USB 900E with locked bootloader.
Rajdip said:
Have you tested this method yourself? I think this is for people who bricked the device but had stock recovery inside, what about people who has twrp and bricked the device? Also I dont think you can flash anything through fastboot in locked bootloader
Click to expand...
Click to collapse
Yeah i bricked mine with twrp .. and i cannot enter into recovery mode now.. only fastboot works and i cannot flash stock recovery too because the bootloader is locked :/ stupid Mi :/
Dharani_V said:
Yeah i bricked mine with twrp .. and i cannot enter into recovery mode now.. only fastboot works and i cannot flash stock recovery too because the bootloader is locked :/ stupid Mi :/
Click to expand...
Click to collapse
So, did you try above mentioned method?
amsmu said:
So, did you try above mentioned method?
Click to expand...
Click to collapse
Yes i did .. and its not allowing me to flash anything .. Getting Error Device is locked :/
failed bro, getting error device is locked using QFIL.:crying:
Guys, please mention the reason behind your device getting bricked too when you are reporting what worked and what didn't. Like whether during unlock bootloader process(without xiaomi's permission) or flashing custom ROM(most probably MIUI official updates) via twrp.
Dharani_V said:
Yes i did .. and its not allowing me to flash anything .. Getting Error Device is locked :/
Click to expand...
Click to collapse
What were you doing when it bricked?
Go to service center. They will repair it
mine happened same..... hard bricked my mobile after restoring original bootloader.......
QFIL cannot do a thing ..... all the eror i get is unable to go to EDl mode......
nothing for me except download mode and fastboot......
so toook to service centre and got it repaired for free in 2hrs
puli where do u live[emoji14]
Sent from my Redmi Note 3 using XDA-Developers mobile app
Rajdip said:
Have you tested this method yourself? I think this is for people who bricked the device but had stock recovery inside, what about people who has twrp and bricked the device? Also I dont think you can flash anything through fastboot in locked bootloader
Click to expand...
Click to collapse
i've tried this myself. In HS USB 900E you can flash aboot through fastboot whether you stock recovery or twrp before bricked.
Rajdip said:
I have found few ways by which people may unbrick from HS USB 900E state without test point, but those guides are for other devices, needs thorough testing for Redmi note 3.
Tools needed:-
1) QPST http://www.androidbrick.com/downloa...qcn-for-lollipop-android-5-0-6-0-marshmallow/
2)Nubia tool studio https://drive.google.com/folderview?id=0BwtoIMKf470SRUxfdHA5cU14ZTQ#
Now follow these guides for reference,
1)http://www.androidbrick.com/ultimat...ide-snapdragons-are-unbrickable-qhsusb_dload/
2)http://www.androidbrick.com/unbrick...-you-have-the-right-kind-of-rom-qhsusb_dload/
Only people with hardbrick(900E) and locked bootloader can this test methods, Please try and leave your feedback, maybe we will find a way to unbrick without opening the phone and voiding warranty. Good Luck
Click to expand...
Click to collapse
Does anyone success ? Please share a guide !
apixbuanget said:
i've tried this myself. In HS USB 900E you can flash aboot through fastboot whether you stock recovery or twrp before bricked.
Click to expand...
Click to collapse
wow!!! thats great, but before you flashed aboot through fastboot did you check whether your bootloader was locked or not?
Dear All,
I have a Problem with my Moto X play XT 1562. I have brought it a year back.
For some strange reason, My phone stopped working all of a sudden.
when I connect it to a PC via USB I'll get a boot-loader menu which says "StartUp failed Please connect the phone to a software repair assistant on the PC". Though I have figured out the problem I am unable to do anything about it.The problem is simple yet complex at the same time,
Problem: Though I have rooted many android phones previously, I never rooted this one. So My boot-loader is locked. I have got the Unique unlock key from Motorola site But when I get to this commad
HTML:
fastboot oem unkock [MY_UNLOCK_KEY]
I get an error message saying "Check 'Allow unlock OEM' in developer options". But my phone is not booting so far so that I can check that.
The basic problem is, My phone's OS is corrupted and I am unable to boot a new OS to it, As the boot loader is locked, I am unable to unlock the boot loader because I have not checked on 'Allow OEM unlock'. I am unable to check 'Allow OEM Unlock' because I The os is corrupted. - (This looks like a riddle )
1.Is there any way I can either bypass this?
2.Is there any way I can check 'Allow unlock OEM' using fastboot or any other tool?
I have tried the following already,
1.tried to clear user data and cache with fastboot - Still remains the same
2.tried to flash a recovery image even though the boot-loader is locked - No Use.
3.contacted service centre just to realise that I have to change the PCB which will cost me a new phone!
Can anyone of you please help me out with this.
Thanks a Ton in Advance.
pldeep said:
Dear All,
I have a Problem with my Moto X play XT 1562. I have brought it a year back.
For some strange reason, My phone stopped working all of a sudden.
when I connect it to a PC via USB I'll get a boot-loader menu which says "StartUp failed Please connect the phone to a software repair assistant on the PC". Though I have figured out the problem I am unable to do anything about it.The problem is simple yet complex at the same time,
Problem: Though I have rooted many android phones previously, I never rooted this one. So My boot-loader is locked. I have got the Unique unlock key from Motorola site But when I get to this commad
HTML:
fastboot oem unkock [MY_UNLOCK_KEY]
I get an error message saying "Check 'Allow unlock OEM' in developer options". But my phone is not booting so far so that I can check that.
The basic problem is, My phone's OS is corrupted and I am unable to boot a new OS to it, As the boot loader is locked, I am unable to unlock the boot loader because I have not checked on 'Allow OEM unlock'. I am unable to check 'Allow OEM Unlock' because I The os is corrupted. - (This looks like a riddle )
1.Is there any way I can either bypass this?
2.Is there any way I can check 'Allow unlock OEM' using fastboot or any other tool?
I have tried the following already,
1.tried to clear user data and cache with fastboot - Still remains the same
2.tried to flash a recovery image even though the boot-loader is locked - No Use.
3.contacted service centre just to realise that I have to change the PCB which will cost me a new phone!
Can anyone of you please help me out with this.
Thanks a Ton in Advance.
Click to expand...
Click to collapse
You can still flash the firmware that is meant for your model/carrier without unlocking bootloader. run getvar all command in fastboot to determine what firmware exatly do you need if unsure.
minimale_ldz said:
You can still flash the firmware that is meant for your model/carrier without unlocking bootloader. run getvar all command in fastboot to determine what firmware exatly do you need if unsure.
Click to expand...
Click to collapse
Can you please guide me trough the steps in a very vauge way(I'll be able to folllow) thanks a ton for the response
pldeep said:
Can you please guide me trough the steps in a very vauge way(I'll be able to folllow) thanks a ton for the response
Click to expand...
Click to collapse
Connect your phone in fastboot mode and type this command:
Code:
fastboot getvar all
in output look for this:
Code:
(bootloader) ro.build.fingerprint:
It's the firmware version that you currently have on your phone. Download exactly the same one and you'll be able to flash it with bootloader locked.
minimale_ldz said:
Connect your phone in fastboot mode and type this command:
Code:
fastboot getvar all
in output look for this:
Code:
(bootloader) ro.build.fingerprint:
It's the firmware version that you currently have on your phone. Download exactly the same one and you'll be able to flash it with bootloader locked.
Click to expand...
Click to collapse
Hey Sorry minimale_ldz,
I got it till this step. I wanted to know what command should I use to flash the os into the phone.
I know how to do Recovery though
HTML:
Fastboot flash recovery recovery.img
I want to know how to do the same with OS.
Thanks again
pldeep said:
Hey Sorry minimale_ldz,
I got it till this step. I wanted to know what command should I use to flash the os into the phone.
I know how to do Recovery though
HTML:
Fastboot flash recovery recovery.img
I want to know how to do the same with OS.
Thanks again
Click to expand...
Click to collapse
You've got instructions in this thread:
https://forum.xda-developers.com/mo...de-how-to-flash-factory-image-return-t3261486
Mind that you'll likely have more system.img_sparsechunk files, so make sure you flash all of them (just change commands accordingly).
Guys I had no luck in doing that.
When ever I try to flash the contents of the stock os, I get a error message which says Pre Flash validation failed.
Can any one help me please
pldeep said:
Guys I had no luck in doing that.
When ever I try to flash the contents of the stock os, I get a error message which says Pre Flash validation failed.
Can any one help me please
Click to expand...
Click to collapse
Your emmc ship is corrupt. That means your whole storage is broken and not fixable.
But i am able to flash some of the contents of the stock ROM. I get this "Pre flash validation failed" error only when I try to flash some of the files like (system.img_sparsechunk.0-9,recovery.img and gpt.bin). I even tried to reset the emmc_chip, I says that the command was succesfully executed.
Is there any other option left??
I am fighting this battle since a week now.
pldeep said:
Dear All,
I have a Problem with my Moto X play XT 1562. I have brought it a year back.
For some strange reason, My phone stopped working all of a sudden.
when I connect it to a PC via USB I'll get a boot-loader menu which says "StartUp failed Please connect the phone to a software repair assistant on the PC". Though I have figured out the problem I am unable to do anything about it.The problem is simple yet complex at the same time,
Problem: Though I have rooted many android phones previously, I never rooted this one. So My boot-loader is locked. I have got the Unique unlock key from Motorola site But when I get to this commad fastboot oem unkock [MY_UNLOCK_KEY]
I get an error message saying "Check 'Allow unlock OEM' in developer options". But my phone is not booting so far so that I can check that.
The basic problem is, My phone's OS is corrupted and I am unable to boot a new OS to it, As the boot loader is locked, I am unable to unlock the boot loader because I have not checked on 'Allow OEM unlock'. I am unable to check 'Allow OEM Unlock' because I The os is corrupted. - (This looks like a riddle )
1.Is there any way I can either bypass this?
2.Is there any way I can check 'Allow unlock OEM' using fastboot or any other tool?
I have tried the following already,
1.tried to clear user data and cache with fastboot - Still remains the same
2.tried to flash a recovery image even though the boot-loader is locked - No Use.
3.contacted service centre just to realise that I have to change the PCB which will cost me a new phone!
Can anyone of you please help me out with this.
Thanks a Ton in Advance.
Click to expand...
Click to collapse
Bull**** about the PCB. Use RsdLite, had the same issue. Flash the latest package and use the USB at the back of the PC
kpamkar said:
Bull**** about the PCB. Use RsdLite, had the same issue. Flash the latest package and use the USB at the back of the PC
Click to expand...
Click to collapse
Hey Kpamkar,
I have tried it with RSD Lite, But no luck. on the RSD interface it says that flash failed,
On the mobile it says
version downgraded for primary_gpt
Can you please help me out with the latest stock rom for Moto x play, I am unable to get the exact stock rom any where, I have looked at this link: https://github.com/motoxplay/stock
My phone finger prints details are as follows(I got it with
HTML:
fastboot getvar all
command):
ro.build.fingerprint[0]: motorola/lux_retasia_ds/lux_uds:6.
ro.build.fingerprint[1]: 0.1/MPDS24.107-70-1-5/5:user/relea
ro.build.fingerprint[2]: se-keys
ON the phone these are the details that are shown:
baseband version:M8936_2020632.44,03.21.57R LUX_EMEA_DSDS_CUST
Product/Variant: LUX XT1562 32GB P2C
It wold be great if you could please share with me any kind of links that you have used which can guide me through this whole process.
Thanks a lot again!
pldeep said:
Hey Kpamkar,
I have tried it with RSD Lite, But no luck. on the RSD interface it says that flash failed,
On the mobile it says
version downgraded for primary_gpt
Can you please help me out with the latest stock rom for Moto x play, I am unable to get the exact stock rom any where, I have looked at this link: https://github.com/motoxplay/stock
My phone finger prints details are as follows(I got it with fastboot getvar all
command):
ro.build.fingerprint[0]: motorola/lux_retasia_ds/lux_uds:6.
ro.build.fingerprint[1]: 0.1/MPDS24.107-70-1-5/5:user/relea
ro.build.fingerprint[2]: se-keys
ON the phone these are the details that are shown:
baseband version:M8936_2020632.44,03.21.57R LUX_EMEA_DSDS_CUST
Product/Variant: LUX XT1562 32GB P2C
It wold be great if you could please share with me any kind of links that you have used which can guide me through this whole process.
Thanks a lot again!
Click to expand...
Click to collapse
In my case I had. 52 version of the ROM. I had a locked bootloader boot loop. But I was able to fix it using rsdLite. Are you using the latest version of the firmware and connecting the ports at the back of the pc? Also install proper drivers
You need to use RETASIA DS, the most recent version
@pldeep
firmware is here.
minimale_ldz said:
@pldeep
firmware is here.
Click to expand...
Click to collapse
Tried this. But no luck.
It still shows the same error "version downgrade for gpt_bin"
pldeep said:
Tried this. But no luck.
It still shows the same error "version downgrade for gpt_bin"
Click to expand...
Click to collapse
try flashing it without gpt.bin and bootloader
Try booting into twrp without flashing it. Use fastboot boot command
---------- Post added at 08:44 PM ---------- Previous post was at 08:29 PM ----------
pldeep said:
Tried this. But no luck.
It still shows the same error "version downgrade for gpt_bin"
Click to expand...
Click to collapse
What are you trying to flash?
Same problem over here... Did you solve it?
Downloading right now the latest rom image for Moto X Play from this site.... //firmware.center/firmware/Motorola/Moto%20X%20Play/Stock/XT1563/
Hey install Fastboot files and download twrp image for Lux and place it in the Fastboot folder.
Then run :- Fastboot reboot recovery.img
It will boot to twrp.
Any update for this? I'm in a similar situation now :-/
Tried RSD, it doesn't see my device (fastboot and adb works fine)
install Fastboot files and download twrp image for Lux and place it in the Fastboot folder.
Click to expand...
Click to collapse
How can I do that?
Also, someone mentioned emmc_chip reset - how to do that?
Thanks
I came back from LOS 16.0. Flashed A2017G_B10_NOUGAT_FULL_EDL in EDL but there's a warning that my bootloader is locked. I wanted to relock it but the warning prevents me from entering bootloader or fastboot (or maybe they are not even present....). Next I flashed A2017U_FASTBOOT_UNLOCK_EDL in MiFlash but it did not do anything. It flashed OK but I still cannot access fastboot. Should I flash some marshmallow rom? Thanks in advance.
I have the same problem. Cannot enter fastboot mode on Nougat ROM.
Ok I found the way usin Axon 7 Toolkit
1. Set the Android version to 7 using option 13
2. Perform unlock bootloader
Following instruction Axon & Tookit gives you EDL image of the proper fastboot partition giving the possibility to enter fastboot mode
then fasboot oem lock
I wanted to say thanks that works, but apparently my phone is bricked now - it hangs on green ZTE logo. PC recognizes it as DFU. Cannot enter EDL either. I guess I look for some guide how to recover from this situation
Managed to fix that. Somehow I was able to enter fastboot. It said my bootloader was locked so i flashed TWRP and from TWRP using ADB installed stock Nougat rom
ma_ko said:
I wanted to say thanks that works, but apparently my phone is bricked now - it hangs on green ZTE logo. PC recognizes it as DFU. Cannot enter EDL either. I guess I look for some guide how to recover from this situation
Managed to fix that. Somehow I was able to enter fastboot. It said my bootloader was locked so i flashed TWRP and from TWRP using ADB installed stock Nougat rom
Click to expand...
Click to collapse
If you was able flash twrp mens your boolaeder was unlocked?
No there's a TWRP that works on locked bootloader.
ma_ko said:
No there's a TWRP that works on locked bootloader.
Click to expand...
Click to collapse
Seems that TWRP was inatlled before the bootloder was locked again.
I had hardbricked my devices while installing an OTA update and the device was Hardbricked .
I blank flashed the device and it booted and bootloader.
Now the problem starts here.
I flashed the OEM_Lock.bat as I wanted to relock the bootloader. I'm not sure what went wrong but the flash didn't complete and stuck in middle.
The problem remains here is it shows
Fastboot Reason: Failed to initialize partition table
I am unable to flash anything now. Recovery.img fails, bootloader.img fails, twrp flashing fails.
Nothing flashes as Bootloader is locked.
I went to Motorola Service Centre. They also couldn't do anything and simply said that their software doesnt read the phone.
Is there anyone whoe can really help me out with anything left to do?
Any method to force flash recovery, even twrp?
Phone is detected as Fastboot athene_16mp S in computer. It doesnt detect as "Qualcomm HS-USB QDLoader 9008".
What firmware are you attempting to flash?
Your device looks like it's still on the blank flash provided bootloader, which means you have to flash at least the GPT and bootloader. The lack of a serial number and the generic identifier implies you have not been able to flash an actual GPT and bootloader. Also, OEM_locked is normal until you get an actual bootloader flashed over the blank flash bootloader, which usually means trying to flash a GPT and bootloader at least as new as the latest version you had on your device (regardless of downgrades).
I'd suggest downloading the latest Nougat stock ROM we have from here. Do not use any of the scripts at this time.
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Unzip the file, delete any old stock ROMs from your ADB folder and copy over the new stock ROM. Try to flash just the GPT and bootloader then reboot to fastboot. See if you reboot into a fastboot screen with details.
If you do, I would proceed to flash the rest of the new ROM without locking your bootloader. If your device boots then, then you can reflash with the locking commands.
Edit - also, this post probably is better suited to the Q and A section...
echo92 said:
What firmware are you attempting to flash?
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Unzip the file, delete any old stock ROMs from your ADB folder and copy over the new stock ROM. Try to flash just the GPT and bootloader then reboot to fastboot. See if you reboot into a fastboot screen with details.
If you do, I would proceed to flash the rest of the new ROM without locking your bootloader. If your device boots then, then you can reflash with the locking commands.
Click to expand...
Click to collapse
The files in mentioned firmware did the trick. It flashed GPT and Bootloader and showed the needed info.:highfive: After that I flashed the same firmware via fastboot commands and device has booted to the stock 7.0 - Bootloader Unlocked. How crazy was I to ignore the proper files to flash? I probably tried 100 times to flash files (wrong once for sure). Thanks alot though for providing the link and instructions. :silly:
Now one last thing, should I flash OEM_Lock file to lock the bootloader so that I can get the lastest Oreo update? I might even think fo selling the device after locking the bootloader. Need your genuine opinion on this as well.
mysteryno46 said:
The files in mentioned firmware did the trick. It flashed GPT and Bootloader and showed the needed info.:highfive: After that I flashed the same firmware via fastboot commands and device has booted to the stock 7.0 - Bootloader Unlocked. How crazy was I to ignore the proper files to flash? I probably tried 100 times to flash files (wrong once for sure). Thanks alot though for providing the link and instructions. :silly:
Now one last thing, should I flash OEM_Lock file to lock the bootloader so that I can get the lastest Oreo update? I might even think fo selling the device after locking the bootloader. Need your genuine opinion on this as well.
Click to expand...
Click to collapse
Eh, you live and learn. Besides, you've now got your device running now!
Honestly, it's up to you. Having a locked or unlocked bootloader will not affect your ability to receive OTA updates - you should still receive updates so long as your firmware matches your software channel (and since your device was XT1643, the NPJS25.93-14-18 April 2018 security update should be the correct firmware). At this moment in time, you'll have to use the NPJS25.93-14-18 firmware to re-lock your bootloader - we don't have the stock Oreo firmware at this time. Thus, if you update to stock Oreo, you will not be able to re-lock your bootloader until you can get a leak of the Oreo firmware.
If you're selling, I'd choose to re-lock the bootloader. Else, a potential buyer who is not used to flashing custom ROMs might wonder if there's any tampering with the device (the bootloader unlocked warning, to someone not used to flashing custom firmware, might scare off potential buyers).
Back to Locked Bootloader, complete stock.
echo92 said:
Eh, you live and learn. Besides, you've now got your device running now!
If you're selling, I'd choose to re-lock the bootloader. Else, a potential buyer who is not used to flashing custom ROMs might wonder if there's any tampering with the device (the bootloader unlocked warning, to someone not used to flashing custom firmware, might scare off potential buyers).
Click to expand...
Click to collapse
I am back to Locked Bootloader as feel the same as you said that anyone buying might get scared by looking the warning sign. Thanks for helping out. :highfive:
Oreo Update via OTA has already started rolling out as per the news I've been reading. I just wanted to see the oreo 8.1 before I sell the phone.
Anyways I got a new device now, Realme C1, 3|32GB as my smartphone usage has declined a lot recently and might remain similar. This device will suffice my requirements.
Thanks for the help and support. :victory:
So, I bricked it. All I have is fastboot. It thinks it's locked after I messed with twrp. Partition table is gone, I think, flashing another one is declined due to locked bootloader. The device is unrecognizable in lmsr, thus unable to flash. Deep flash seems to be the only option, but how do I get to there? I'm new with this phone, just 2 days old now. Is possible to open the device up
EDIT: the trick is fastboot oem blankflash