Related
Hello,
Ive got a phone from a customer saying it wont boot up, also said he just OTAed, It only enter bootloader mod (stuck on black screen when trying yo enter recovery).
It also says Secure Boot - enable
and I cant flash anything of course , What can I do to boot it up ?
is his bootloader unlocked?
---------- Post added at 01:09 PM ---------- Previous post was at 01:08 PM ----------
try and use this https://developers.google.com/android/nexus/images
---------- Post added at 01:09 PM ---------- Previous post was at 01:09 PM ----------
try and use this https://developers.google.com/android/nexus/images
theyau said:
is his bootloader unlocked?
---------- Post added at 01:09 PM ---------- Previous post was at 01:08 PM ----------
try and use this https://developers.google.com/android/nexus/images
---------- Post added at 01:09 PM ---------- Previous post was at 01:09 PM ----------
try and use this https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Its always locked, if I unlock the bootloader its automatically re-locking after reboot
Bump
any one has any idea please ?
deadwolf666 said:
Hello,
Ive got a phone from a customer saying it wont boot up, also said he just OTAed, It only enter bootloader mod (stuck on black screen when trying yo enter recovery).
It also says Secure Boot - enable
and I cant flash anything of course , What can I do to boot it up ?
Click to expand...
Click to collapse
Secure boot is enabled on all Nexus 4's, and you cannot disable it. By the way, Secure boot has nothing to do with the lock state of the bootloader -- it has to do with the secure boot chain of the AQP8064 chipset.
Unlock the booloader using "fastboot oem unlock" and then flash the factory images. See here.
If simply flashing factory images, an unlock should not be necessary. Is customer wanting you to try and preserve data?
efrant said:
Secure boot is enabled on all Nexus 4's, and you cannot disable it. By the way, Secure boot has nothing to do with the lock state of the bootloader -- it has to do with the secure boot chain of the AQP8064 chipset.
Unlock the booloader using "fastboot oem unlock" and then flash the factory images. See here.
Click to expand...
Click to collapse
Thanks for the answer but the wierd problem is that after I unlock the bootloader and try to flash any thing I get":
sending 'bootloader' (2188 KB)... FAILED (command write failed (Unknown error))
Click to expand...
Click to collapse
and after I reboot it shows that the bootloader is locked
I managed to boot into twrp recovery but no screen by "fastboot boot recovery.img" and I get adb access.
ant thing I can do from here ?
deadwolf666 said:
I managed to boot into twrp recovery but no screen by "fastboot boot recovery.img"
Click to expand...
Click to collapse
You are seeing a black screen because you are not using the correct command. It should be: fastboot -c "lge.kcal=0|0|0|x" boot recovery.img
efrant said:
You are seeing a black screen because you are not using the correct command. It should be: fastboot -c "lge.kcal=0|0|0|x" boot recovery.img
Click to expand...
Click to collapse
Thank you it helped abit
now I tryed twrp and it asked me for decryd pass, and cant mount any partition.
cwm can sideload but wipe will give errors (cant mount) and after reboot the bootloader is locked againg and wont boot.
stock just reboots.
can it be HW ? or any other solution ?
btw where did you learend this switch and where can I read about it ? "lge.kcal=0|0|0|x"
Thanks again
deadwolf666 said:
Thank you it helped abit
now I tryed twrp and it asked me for decryd pass, and cant mount any partition.
cwm can sideload but wipe will give errors (cant mount) and after reboot the bootloader is locked againg and wont boot.
stock just reboots.
can it be HW ? or any other solution ?
btw where did you learend this switch and where can I read about it ? "lge.kcal=0|0|0|x"
Thanks again
Click to expand...
Click to collapse
Two options before we decide it's hardware.
Procedure #1:
1) Download the LATEST version of fastboot.exe from here and extract it to C:\android.
2) Download the latest factory image from Google's dev page and verify the checksum with what is posted on the website.
3) Extract all the images from all the .tgz, .tar, .zip files within and put the 6 image files in C:\android
4) Reboot your device into the bootloader and plug into your PC.
5) Open a command prompt in that same directory and type the following commands:
Code:
fastboot oem unlock
fastboot reboot-bootloader
fasltboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
Does that work? If so then continue with flashing the radio, boot, system and recovery images. If not, then go to procedure number 2:
Procedure #2
Follow the instructions in this thread.
deadwolf666 said:
btw where did you learend this switch and where can I read about it ? "lge.kcal=0|0|0|x"
Thanks again
Click to expand...
Click to collapse
Have a look here.
efrant said:
Two options before we decide it's hardware.
Procedure #1:
1) Download the LATEST version of fastboot.exe from here and extract it to C:\android.
2) Download the latest factory image from Google's dev page and verify the checksum with what is posted on the website.
3) Extract all the images from all the .tgz, .tar, .zip files within and put the 6 image files in C:\android
4) Reboot your device into the bootloader and plug into your PC.
5) Open a command prompt in that same directory and type the following commands:
Code:
fastboot oem unlock
fastboot reboot-bootloader
fasltboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
Does that work? If so then continue with flashing the radio, boot, system and recovery images. If not, then go to procedure number 2:
Procedure #2
Follow the instructions in this thread.
Have a look here.
Click to expand...
Click to collapse
Procedure #1 is not working I get FAILED command write failed unknown error
Procedure #2 I tryed a few times on different pc (also different OS) and never got the software to recognize the phone (any way Ill try again and update)
thanks for the link will read it soon ^^
Cant make the NPST recognize the phone ;\
while booting custom recovery I cant mount any partition and the bootloader remains locked after reboot.
Any thing else to try ?
Warning: some people have said following these instructions on Nougat bricks your phone. I have done them to restore stock after upgrading to Nougat and have had no issues but you may want to conduct further research before attempting.
I had trouble finding the correct instructions for restoring the stock firmware when I needed it a few months ago so I decided to make a simple guide to help people that may be having the same issues I was.
Firstly, ensure your bootloader is unlocked and USB debugging is enabled in developer options. I'd assume this is already the case if you're needing to restore to stock.
Download the stock firmware for your update channel from https://mirrors.lolinet.com/firmware/moto/addison/official/
Extract the zip file into a directory of your choice
Right click and "Open command window here"
Execute, line by line:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0 (repeat up to 10)
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
Reboot device
Thank you! This is very helpful restoring the device. Is there also command to re-lock the bootloader to enable OTA? The info is so fragmented... Many thanks
Yes same question. Is it possible to relock the bootloader after that? If so how to do this?
slainer68 said:
Yes same question. Is it possible to relock the bootloader after that? If so how to do this?
Click to expand...
Click to collapse
I dont remember who tell this "once you unlock your device, you can never ever lock it again."
Sent from my XT1635-02 using XDA Labs
There's a lot of devices that you can relock...
fastboot oem lock
should relock the bootloader...
Relock usually does make no sense. Unlock does not prevent OTA update. Relocked is "locked again", but won't help you in any way.
Under which circumstances do you fear that someone gets access to your device and flashes something? This is what gets prevented by relock.
Relock works only if we have a signed firmware. Without that there is no way to relock the bootloader.
tag68 said:
Relock usually does make no sense. Unlock does not prevent OTA update. Relocked is "locked again", but won't help you in any way.
Under which circumstances do you fear that someone gets access to your device and flashes something? This is what gets prevented by relock.
Click to expand...
Click to collapse
Relock to use Android Pay
In NOUGAT your script flash MM brick phone
Remove
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Donwgrade Bootloader Brick Phone
You really should add a warning. This breaks your phone if you already upgraded to Android N (specifically, the bootloader).
This other thread helped me downgrade the right way
https://forum.xda-developers.com/mo...irmware-downgrade-t3558118/page2#post71404455
Specifically the version of the script in the comments by -=MoRpH=-
graphitenexus said:
I had trouble finding the correct instructions for restoring the stock firmware when I needed it a few months ago so I decided to make a simple guide to help people that may be having the same issues I was.
Should this be unzipped in the ADB folder?
Click to expand...
Click to collapse
marsisabar said:
You really should add a warning. This breaks your phone if you already upgraded to Android N (specifically, the bootloader).
This other thread helped me downgrade the right way
https://forum.xda-developers.com/mo...irmware-downgrade-t3558118/page2#post71404455
Specifically the version of the script in the comments by -=MoRpH=-
Click to expand...
Click to collapse
I've restored to it from N without issue
Jimi Mack said:
I had trouble finding the correct instructions for restoring the stock firmware when I needed it a few months ago so I decided to make a simple guide to help people that may be having the same issues I was.
Firstly, ensure your bootloader is unlocked and USB debugging is enabled in developer options. I'd assume this is already the case if you're needing to restore to stock.
Download the stock firmware for your update channel from https://mirrors.lolinet.com/firmware/moto/addison/official/
Extract the zip file into a directory of your choice
Right click and "Open command window here"
Execute, line by line:
Should this be unzipped in the ADB folder?
Click to expand...
Click to collapse
Not necessary if you have ADB added to your path
graphitenexus said:
Not necessary if you have ADB added to your path
Click to expand...
Click to collapse
Thank you, but sorry I do not understand., an old guy here and the whole thing with command lines confuse me.
---------- Post added at 11:28 AM ---------- Previous post was at 11:06 AM ----------
I have all the files in the ADB folder, I keep getting "Slot Counts not found" on the 2nd entry on the list. All want to do is flash my screw up back to stock.... LOL.
I do not even have an "oem fb_mode_set" in the folder, I have an "oem.img"
Jimi Mack said:
Thank you, but sorry I do not understand., an old guy here and the whole thing with command lines confuse me.
Click to expand...
Click to collapse
Don't worry about path then. Unzip to platform-tools in the ADB folder then shift+right click and select open command window here. Then run the commands in the OP
graphitenexus said:
Don't worry about path then. Unzip to platform-tools in the ADB folder then shift+right click and select open command window here. Then run the commands in the OP
Click to expand...
Click to collapse
I am running the commands one by one but the 2nd one get me stuck as I noted above. The no slot think has be confused, what should I see after entering each command?
---------- Post added at 12:10 PM ---------- Previous post was at 11:44 AM ----------
Got It
graphitenexus said:
I've restored to it from N without issue
Click to expand...
Click to collapse
In the future... when you receive a "new" OTA you may brick your phone... (ghost user experience)
CsR0501 said:
In the future... when you receive a "new" OTA you may brick your phone... (ghost user experience)
Click to expand...
Click to collapse
Original Moto X, had one and loved it and yes lots of bricks.
graphitenexus said:
Relock to use Android Pay
Click to expand...
Click to collapse
I've never had that problem? My bootloader was unlocked on my Moto X Pure and the only time Android pay didn't work was when I rooted. I reverted back to complete stock and it worked fine.
SixShots said:
I've never had that problem? My bootloader was unlocked on my Moto X Pure and the only time Android pay didn't work was when I rooted. I reverted back to complete stock and it worked fine.
Click to expand...
Click to collapse
Unlocked bootloader now breaks safetynet
Hello. I am in desperate need of help. My moto G4 always starts on fastboot mode. It does work wen I press start but I don't want it starting on fastboot. I recently gained the problem of battery draining and I'm supposed to recalibrate the battery by letting the phone turn off and putting it to charge all night while is off but I dont think it'll work if it is on fastboot all night. Please help D:
While in the bootloader connect to your PC and flash this command from fastboot - "fastboot oem fb_mode_clear"
Tried it.
Rempala said:
While in the bootloader connect to your PC and flash this command from fastboot - "fastboot oem fb_mode_clear"
Click to expand...
Click to collapse
I tried that once. Didn't work. And now I don't even have a pc so I need a solution through the phone itself
I had the same problem.
try these commands in order.
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
Hi I'm new on this can you please make me a list step by step how do it?
---------- Post added at 08:31 PM ---------- Previous post was at 08:10 PM ----------
Manusanchez said:
Hi I'm new on this can you please make me a list step by step how do it?
Click to expand...
Click to collapse
nevermind i already done it
This is my first time posting on XDA, so sorry if the formatting is bad.
I've tried to root my P9 lite installing TWRP and Magisk, everything went fine, until the last reboot that caused a bootloop.
Trying to fix this I mistakenly wiped the System partition (instead of Data), reading online people adviced to flash the update.zip, when i tried it I had "unable to mount /vendor" and "unable to mount /product".
I tried the update.app method and the eRecovery tool, but still nothing.
I read that the problem was probably caused by en error in boot.img or recovery.img, so i extracted those files from the firmware and flashed them using TWRP. By doing so i deleted TWRP itself leaving me unable to flash system.img.
I tried to flash it using fastboot, but every time i try to write a command regarding flashing i get a FAILED (remote: command not allowed).
Now i have a bricked phone, i can access fastboot but it doesnt seem to be working. I cant access adb since i can't access the recovery (at least i dont know how to ).
Any advices?
Do you have bootloader unlock code?
Dino_S said:
Do you have bootloader unlock code?
Click to expand...
Click to collapse
Yes I do.
Unlock bootloader again and in fastboot flash system.img and boot from firmware,I used b370
---------- Post added at 12:46 AM ---------- Previous post was at 12:38 AM ----------
Extract from update.zip file update.app and use huawei update extractor and extract files from that system.img and boot.img and put in fastboot folder and flash it
Dino_S said:
Unlock bootloader again and in fastboot flash system.img and boot from firmware,I used b370
---------- Post added at 12:46 AM ---------- Previous post was at 12:38 AM ----------
Extract from update.zip file update.app and use huawei update extractor and extract files from that system.img and boot.img and put in fastboot folder and flash it
Click to expand...
Click to collapse
I can't, whenever I try using a fastboot command I get "FAILED (remote: command not allowed)
How much is internal data memory in twrp
Dino_S said:
How much is internal data memory in twrp
Click to expand...
Click to collapse
Around 10 gb, by the way I can't access twrp anymore, since I flashed recovery.img
TinkyWinkyJr said:
Around 10 gb, by the way I can't access twrp anymore, since I flashed recovery.img
Click to expand...
Click to collapse
It is showing in fastboot mode unlocked both
Dino_S said:
It is showing in fastboot mode unlocked both
Click to expand...
Click to collapse
Bootloader unlocked and FPR locked (or is it FRP?)
I have same prob yesterday,and showing me same thing,but i flashed twrp again and format data and system to ext4,and from fastboot flash system and boot img and it booted,it is confusing to undestand yours problem
---------- Post added at 01:15 AM ---------- Previous post was at 01:14 AM ----------
TinkyWinkyJr said:
Bootloader unlocked and FPR locked (or is it FRP?)
Click to expand...
Click to collapse
Mine showing FRP unlocked
hey guys
i have the same problem, had rr marshmallow on my p9 lite and tried to flash the new recovery for nougat by old droid. since then i cant enter nowhere without fastboot. phone unlocked and frp unlocked. does anybody have another idea. flashing stock recovery did not work, flashing twrp did also not work. need more ideas, erecovery and dload method do not work, i have acces to fastboot
Try to flash the correct oem.info.I've had the same problem with my P9(EVA-L09).
hi guys can some one help me to recover the device, phone stuck at logo i can acces fastboot but i cant acces recovery mode. I flashed a fastbootm rom i found on the web, now the phone is bricked
Black Shark QNA
Hi, @damond share your mobile device model (is it shark 2 pro or shark) also let me know if these commands are working in your fastboot mode, fastboot devices
fastboot reboot bootloader
fastboot reboot recovery (this will lead you to phone recovery mode try formatting through this, it works always) if it doesn't, confirm.
Also, share the your device origin (like it was on global rom or CN rom) and if bootloader is unlocked or not.
If required, will create a fastboot rom for your device.
Thanks
---------- Post added at 10:07 AM ---------- Previous post was at 09:55 AM ----------
damond said:
hi guys can some one help me to recover the device, phone stuck at logo i can acces fastboot but i cant acces recovery mode. I flashed a fastbootm rom i found on the web, now the phone is bricked
Click to expand...
Click to collapse
Hi, @damond share your mobile device model (is it shark 2 pro or shark) also let me know if these commands are working in your fastboot mode, fastboot devices
fastboot reboot bootloader
fastboot reboot recovery (this will lead you to phone recovery mode try formatting through this, it works always) if it doesn't, confirm.
Also, share the your device origin (like it was on global rom or CN rom) and if bootloader is unlocked or not.
If required, will create a fastboot rom for your device.
Thanks
Shubhendu Shubham Sharma said:
Hi, @damond share your mobile device model (is it shark 2 pro or shark) also let me know if these commands are working in your fastboot mode, fastboot devices
fastboot reboot bootloader
fastboot reboot recovery (this will lead you to phone recovery mode try formatting through this, it works always) if it doesn't, confirm.
Also, share the your device origin (like it was on global rom or CN rom) and if bootloader is unlocked or not.
If required, will create a fastboot rom for your device.
Thanks
---------- Post added at 10:07 AM ---------- Previous post was at 09:55 AM ----------
Hi, @damond share your mobile device model (is it shark 2 pro or shark) also let me know if these commands are working in your fastboot mode, fastboot devices
fastboot reboot bootloader
fastboot reboot recovery (this will lead you to phone recovery mode try formatting through this, it works always) if it doesn't, confirm.
Also, share the your device origin (like it was on global rom or CN rom) and if bootloader is unlocked or not.
If required, will create a fastboot rom for your device.
Thanks
Click to expand...
Click to collapse
hi thanks for answering the model is black shark 2, skw-a0, i dont know if its posiblle to flash a global rom. Thanks in advance.
damond said:
hi thanks for answering the model is black shark 2, skw-a0, i dont know if its posiblle to flash a global rom. Thanks in advance.
Click to expand...
Click to collapse
Have you tried running fastboot commands( just copy paste the commands as it is in fast boot mode one by one
1. Fastboot reboot bootloader
2. Fastboot reboot recovery (use it to format your phone)
3. Fastboot erase userdata
Shubhendu Shubham Sharma said:
Have you tried running fastboot commands( just copy paste the commands as it is in fast boot mode one by one
1. Fastboot reboot bootloader
2. Fastboot reboot recovery (use it to format your phone)
3. Fastboot erase userdata
Click to expand...
Click to collapse
no i have not tried those commands, but i will as soon as a i get back home.
Shubhendu Shubham Sharma said:
Have you tried running fastboot commands( just copy paste the commands as it is in fast boot mode one by one
1. Fastboot reboot bootloader
2. Fastboot reboot recovery (use it to format your phone)
3. Fastboot erase userdata
Click to expand...
Click to collapse
Fastboot reboot bootloader, Fastboot erase userdata was succesfully, but Fastboot erase userdata gives error. And it still stuck at logo
damond said:
Fastboot reboot bootloader, Fastboot erase userdata was succesfully, but Fastboot erase userdata gives error. And it still stuck at logo
Click to expand...
Click to collapse
You ran twice same commands. One time it was successful and the other time it failed can you share the error.
Also, try this command (just copy paste it)
Fastboot devices
Fastboot reboot recovery.
Then try wiping out the phone.
C:\adb>Fastboot reboot recovery.
fastboot: usage: unknown reboot target recovery.
C:\adb>Fastboot reboot recovery
Rebooting into recovery OKAY [ 0.000s]
Finished. Total time: 0.000s
C:\adb>
But the phone does not enter recovery mode, it goes black and then black shark logo, it looks like there is no recovery partition.
Cool, give me a day or two, will create and share the fastboot rom to flash.
thanks ill be wating
MP6_Pie-ROM_Black_Shark_2_Pro
damond said:
thanks ill be wating
Click to expand...
Click to collapse
Hi, steps to flash this rom.
1. Download files from the Link (cannot post the link due to XDA Restriction)
2. Once download is completed, extract the zip file.
3. Run the Flash_All as administrator.
4. Allow the process to complete.
Once done, enjoy your phone
If this works do give me a thumbs up. If you face any issue let me know.
Share an email id of place where I can share the link.
Thanks.
hi bro i send you a pm with email
h, can you send me the link please?
Update On Issue
damond said:
h, can you send me the link please?
Click to expand...
Click to collapse
As per our discussion over the email. I hope your issue is resolved. If not let me know.
Thanks
Shubhendu Shubham Sharma said:
Bro plz help me.
I've flashed cn beta on global bs2 and now i can't receive ota.
I want joy ui cn with working ota on my device.
*Sry 4 my bad English.
Click to expand...
Click to collapse
Mohit 22 said:
Shubhendu Shubham Sharma said:
Bro plz help me.
I've flashed cn beta on global bs2 and now i can't receive ota.
I want joy ui cn with working ota on my device.
*Sry 4 my bad English.
Click to expand...
Click to collapse
Hi Mohit, is your bootloader still unlocked. Confirm
Click to expand...
Click to collapse
Shubhendu Shubham Sharma said:
Hi, @damond share your mobile device model (is it shark 2 pro or shark) also let me know if these commands are working in your fastboot mode, fastboot devices
fastboot reboot bootloader
fastboot reboot recovery (this will lead you to phone recovery mode try formatting through this, it works always) if it doesn't, confirm.
Also, share the your device origin (like it was on global rom or CN rom) and if bootloader is unlocked or not.
If required, will create a fastboot rom for your device.
Thanks
---------- Post added at 10:07 AM ---------- Previous post was at 09:55 AM ----------
Hi, @damond share your mobile device model (is it shark 2 pro or shark) also let me know if these commands are working in your fastboot mode, fastboot devices
fastboot reboot bootloader
fastboot reboot recovery (this will lead you to phone recovery mode try formatting through this, it works always) if it doesn't, confirm.
Also, share the your device origin (like it was on global rom or CN rom) and if bootloader is unlocked or not.
If required, will create a fastboot rom for your device.
Thanks
Click to expand...
Click to collapse
Sorrys I work for 16h. My model is BS2, no PRO.
now I am going to test the commands that you have recommended me to use. Thanks, when I try them I comment on the result ^^
sorry i got confused from post.
yesterday I started a topic with a similar problem and I thought it was my post. I think some moderator deleted it because I can't find it. I just created another post with my case
Dude what issue you are facing please explain in detail. I am here to help .
damond said:
C:\adb>Fastboot reboot recovery.
fastboot: usage: unknown reboot target recovery.
C:\adb>Fastboot reboot recovery
Rebooting into recovery OKAY [ 0.000s]
Finished. Total time: 0.000s
C:\adb>
But the phone does not enter recovery mode, it goes black and then black shark logo, it looks like there is no recovery partition.
Click to expand...
Click to collapse
it happens the same to me. it does not restart me in recoveri mode.
Yesterday I don't remember how, but I managed to get into recovery mode. I only had 3 options. I remember making wipes and deleting the data but the mobile remained the same
Deke79 said:
it happens the same to me. it does not restart me in recoveri mode.
Yesterday I don't remember how, but I managed to get into recovery mode. I only had 3 options. I remember making wipes and deleting the data but the mobile remained the same
Click to expand...
Click to collapse
Hi deke what issue are you facing. Please help me with that, will try to resolve.