I was at work when i entered a bootloop. I was doing nothing special maybe using the camera. I was bootloader unlocked rooted on latest twrp and on the latest official dirty unicorn I think 10.4 and everything was fine.
After the bootloop started I tried entering recovery in which it only boot loops. I can only access the bootloader screen. I Can see my device in fastboot devices.
I think my next step is to flash some Google factory images in fastboot. But I was wondering if my device be encrypted with fingerprints and a pin will affect it because I've ran into a problem last year when flashing a new version of TWRP it asked for passcode when one was not set.
I'd love to be able to recover some of my data but I guess if it's Encrypted that is not a chance, so I guess I will fastboot Flash the original images.
Is there going to be any problems when I try to flash Nexus images while it is encrypted with a passcode, Any suggestions?
Yeah, standard answer here is to flash the fastboot images. It'll be wiping/overwriting system and vendor so you shouldn't have any issues with the previous fingerprints. It'd be a good idea to wipe data once you get into TWRP afterwards but I wouldn't worry about wiping/formatting userdata.
Heisenberg said:
Yeah, standard answer here is to flash the fastboot images. It'll be wiping/overwriting system and vendor so you shouldn't have any issues with the previous fingerprints. It'd be a good idea to wipe data once you get into TWRP afterwards but I wouldn't worry about wiping/formatting userdata.
Click to expand...
Click to collapse
Thanks... I was just re reading your huge thread for the 4th time this year.
Heisenberg said:
Yeah, standard answer here is to flash the fastboot images. It'll be wiping/overwriting system and vendor so you shouldn't have any issues with the previous fingerprints. It'd be a good idea to wipe data once you get into TWRP afterwards but I wouldn't worry about wiping/formatting userdata.
Click to expand...
Click to collapse
I flashed the stock images mtc19x and its bootlooping to hell. Is it time for me to call Google? To see if I can get a new one I bought it in November when it came out
dontbeweakvato said:
I flashed the stock images mtc19x and its bootlooping to hell. Is it time for me to call Google? To see if I can get a new one I bought it in November when it came out
Click to expand...
Click to collapse
It's worth trying the latest (MTC20F) images first. And if that doesn't work I'd try formatting userdata too.
Heisenberg said:
It's worth trying the latest (MTC20F) images first. And if that doesn't work I'd try formatting userdata too.
Click to expand...
Click to collapse
Hey man, you think i can relock the bootloader with only access to the bootloader screen. I can't access anything accept for bootloader.... It won't boot up or go into recovery.
I'm returning it for rma
dontbeweakvato said:
Hey man, you think i can relock the bootloader with only access to the bootloader screen. I can't access anything accept for bootloader.... It won't boot up or go into recovery.
I'm returning it for rma
Click to expand...
Click to collapse
Yeah, relocking the bootloader is easy, just put it in bootloader mode and issue this command:
Code:
fastboot flashing lock
Heisenberg said:
Yeah, relocking the bootloader is easy, just put it in bootloader mode and issue this command:
Code:
fastboot flashing lock
Click to expand...
Click to collapse
I did that exactly. It returned with the list of commands
Fastboot flashing lock
I think it can't. When I type devices it comes back with a serial number and I could even flash boot system and all that from the system image. But when I type fastboot flashing lock it acts like it can't complete that request. Hopefully Huawei or Google won't care if my bootloader is unlocked although i did Flash the factory images and unrooted it
dontbeweakvato said:
I did that exactly. It returned with the list of commands
Fastboot flashing lock
I think it can't. When I type devices it comes back with a serial number and I could even flash boot system and all that from the system image. But when I type fastboot flashing lock it acts like it can't complete that request. Hopefully Huawei or Google won't care if my bootloader is unlocked although i did Flash the factory images and unrooted it
Click to expand...
Click to collapse
That usually means your fastboot isn't up to date.
Heisenberg said:
That usually means your fastboot isn't up to date.
Click to expand...
Click to collapse
Yea that dawned on me and yea it worked. I was thinking there was an error because the board is fried.
Thanks
Related
Hi all,
on my Nexus 9, update to LRX21Q failed: After reboot, the android icon was shown with "error" below.
I suppose, update failed as my system is rooted with the method Chainfire posted in the development forum.
After an additional reboot, the previous firmware is still shown. The system does not offer the update anymore but claims to be up-to-date.
Any hints? Thanks in advance.
Maybe it's the modified kernel from Chainfire. Try to get back to the stock kernel and try again.
Download the factory image, flash recovery, boot, system & vendor.
Your software will be updated and you won't lose any data. You will lose root however.
I got the same error from OTA with no root. Only had 9 for 2 days, got OTA rite out of box no issue.
Yesterday for new build i get little error android icon upon reboot/install.
Obviously, something that is being changed by the "root" process is being checked DURING the update process. Probably a checksum on the boot partition. If it doesn't match, it bails on the update.
The likely reason for this is they acknowledge that you don't want to lose your root.
All it means is that you need to do the update manually.
It may be possible for a modified recovery to bypass this check, or possibly even be made to auto-root new boot images.
Thanks, guys. Will try as suggest above and post results.
Update: worked perfectly, needed to root again though.
StuMcBill said:
Download the factory image, flash recovery, boot, system & vendor.
Your software will be updated and you won't lose any data. You will lose root however.
Click to expand...
Click to collapse
has anyone tried this? i would like to update without losing data...
Flash through fastboot and you will be fine. Thats what I did then rerooted with CF autoroot
mk92595 said:
Flash through fastboot and you will be fine. Thats what I did then rerooted with CF autoroot
Click to expand...
Click to collapse
What's the fastboot command for the img? Do you flash as boot, system, etc?
zeebone said:
What's the fastboot command for the img? Do you flash as boot, system, etc?
Click to expand...
Click to collapse
Fastboot flash bootloader bootloader.img
Fastboot reboot-bootloader
Fastboot flash system system.img
Fastboot reboot-bootloader
Fastboot flash boot boot.img
Fastboot reboot-bootloader
Fastboot flash vender vendor.img
Fastboot reboot-bootloader
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot reboot
Not sure if I forgot one but I think thats all of them
mk92595 said:
Fastboot flash bootloader bootloader.img
Fastboot reboot-bootloader
Fastboot flash system system.img
Fastboot reboot-bootloader
Fastboot flash boot boot.img
Fastboot reboot-bootloader
Fastboot flash vender vendor.img
Fastboot reboot-bootloader
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot reboot
Not sure if I forgot one but I think thats all of them
Click to expand...
Click to collapse
Should there be a - sign between reboot and bootloader .. And is fastboot flash vender or vendor... Just making sure .
pantmunu said:
Should there be a - sign between reboot and bootloader .. And is fastboot flash vender or vendor... Just making sure .
Click to expand...
Click to collapse
Yes there should be a - sign and vendor. Sorry i'm not home so I don't have the files near me.
mk92595 said:
Yes there should be a - sign and vendor. Sorry i'm not home so I don't have the files near me.
Click to expand...
Click to collapse
Thank you sir .
Where can i find the images for download. Thx
Google for nexus factory image.
Sent from my Nexus 9 using XDA Premium HD app
Update failed on me too. Completely stock
UPDATE:
Apparently *some* devices didn't get the recovery updated with the last update (LRX21L).
The new update (LRX21Q) requires the newer version of the recovery to install.
Google really messed up the launch of the Nexus 9 with all the HW/SW quality control issues
Serious f#ck-up from Google really
Interesting thing I noticed: I restored factory images manually in order to unroot and the OTA was no longer available. I verified I was still running on L. I manually installed the update and it went in just fine.
Now waiting on the root package to be updated for the Q kernel. You can re-root but you will be running on the L kernel, not the Q kernel.
maarten08 said:
Update failed on me too. Completely stock
Click to expand...
Click to collapse
My too fck Google
Mine failed and Im not even rooted
And im not sure if it did the update as its not showing a new one. Im on L
Hi all,
To cut a long story short, around the time MM was being released I cracked my display and broke the digitiser. Before sending the phone off for repair I got the update notification -.- but sent it away without updating as I couldn't accept it. Phone returned and working but no OTA notification, factory reset a few times, sim out and try again, all the usual tricks. They flashed my phone in the factory (came back wiped) and for some reason this firmware isn't getting the OTA update.
So after persevering with Lollipop (and cracking the display again, and fixing it myself this time) I'm getting Marshmallow one way or another. I just would like to know the best way.
I'd rather keep everything as stock as possible (in terms of bootloaders and rooting) and my current plan was to flash TWRP and try running a MM OTA file. I'm just looking to verify this would work and if so, any pitfalls (future OTAs) or things that could go horribly wrong by doing something idiotic.
I'm on an EU XT1572 so I'm assuming a general EU OTA file will work?
Thanks in advance for any assistance,
Phil
clarkey586 said:
Hi all,
To cut a long story short, around the time MM was being released I cracked my display and broke the digitiser. Before sending the phone off for repair I got the update notification -.- but sent it away without updating as I couldn't accept it. Phone returned and working but no OTA notification, factory reset a few times, sim out and try again, all the usual tricks. They flashed my phone in the factory (came back wiped) and for some reason this firmware isn't getting the OTA update.
So after persevering with Lollipop (and cracking the display again, and fixing it myself this time) I'm getting Marshmallow one way or another. I just would like to know the best way.
I'd rather keep everything as stock as possible (in terms of bootloaders and rooting) and my current plan was to flash TWRP and try running a MM OTA file. I'm just looking to verify this would work and if so, any pitfalls (future OTAs) or things that could go horribly wrong by doing something idiotic.
I'm on an EU XT1572 so I'm assuming a general EU OTA file will work?
Thanks in advance for any assistance,
Phil
Click to expand...
Click to collapse
Easy-peasy.
*NOTE - Using TWRP to flash the OTA.zip IS NOT an option, it WILL fail. You can however use the stock recovery and ADB sideload it.. but the following is how I would probably do it. It's also easier IMO.
I'm assuming your bootloader is unlocked since you were talking about using TWRP so grab the WHOLE 6.0 firmware for your phone (I'm guessing your're RETEU so -> XT1572_CLARK_RETEU_6.0_MPHS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml.zip - It's 1.3GB in size) and then reboot the phone into the bootloader (Fastboot mode) and use the files in it to flash everything (this process will wipe the phone so backup anything important first) with fastboot and you will be on a clean completely stock 6.0 with the february patch.
Code:
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 system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Standalone Fastboot & adb installer - LINK
WHOLE Firmware - LINK
Good luck! If your bootloader is not already unlocked and you don't want to unlock it there is still hope.. it will just be a bit different process by using the OTA zips and the stock recovery.. let me know if you MUST go down this route.. it's a bit more of a PITA IMO.
EDIT* If terminal commands are not your thing you can also try using RSDLite.(Official Moto tool). but I've not personally tried it with my Moto X Pure... I like the terminal
DaMadOne said:
Easy-peasy.
*NOTE - Using TWRP to flash the OTA.zip IS NOT an option, it WILL fail. You can however use the stock recovery and ADB sideload it.. but the following is how I would probably do it. It's also easier IMO.
I'm assuming your bootloader is unlocked since you were talking about using TWRP so grab the WHOLE 6.0 firmware for your phone (I'm guessing your're RETEU so -> XT1572_CLARK_RETEU_6.0_MPHS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml.zip - It's 1.3GB in size) and then reboot the phone into the bootloader (Fastboot mode) and use the files in it to flash everything (this process will wipe the phone so backup anything important first) with fastboot and you will be on a clean completely stock 6.0 with the february patch.
Code:
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 system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Standalone Fastboot & adb installer - LINK
WHOLE Firmware - LINK
Good luck! If your bootloader is not already unlocked and you don't want to unlock it there is still hope.. it will just be a bit different process by using the OTA zips and the stock recovery.. let me know if you MUST go down this route.. it's a bit more of a PITA IMO.
EDIT* If terminal commands are not your thing you can also try using RSDLite.(Official Moto tool). but I've not personally tried it with my Moto X Pure... I like the terminal
Click to expand...
Click to collapse
Thanks a million.
I've not unlocked my bootloader, but I don't think it should be a problem there's plenty of tutorials etc for that.
Ideally, I'd not like to wipe my phone but alas it looks like that's going to be the case and I'll trust your advice rather than looking for a lazy way out haha. Is there any way to back up everything (even just apps, etc) without root though?
Cheers :good:
clarkey586 said:
Thanks a million.
I've not unlocked my bootloader, but I don't think it should be a problem there's plenty of tutorials etc for that.
Ideally, I'd not like to wipe my phone but alas it looks like that's going to be the case and I'll trust your advice rather than looking for a lazy way out haha. Is there any way to back up everything (even just apps, etc) without root though?
Cheers :good:
Click to expand...
Click to collapse
Yea, your warranty is void at this point anyways so why not just unlock it! I root and use TiBu.. so I've not tested other backup methods but I'm pretty sure there are backup apps on the playstore that don't require root you could try.
BUT, the step "fastboot erase userdata" is what erases your installed apps/setting and personal files, etc. Really you can just SKIP that step and you SHOULD be ok. Then your apps and settings will be there when you boot 6.0. I was just providing instructions for a fully clean flash. I would say you have a 98% chance it will be just fine though if you don't erase userdata.
EDIT* oh and IIRC you will probably get an error or weird msg with the gpt.bin part of the flash.. ignore it..
EDIT 2* Here is one such app that doesn't look like it requires root. If you go this route make sure you copy everything over to your PC after using the backup app if you are going to run the "fastboot erase userdata" command.
GOOD LUCK!
---------- Post added at 06:38 PM ---------- Previous post was at 06:07 PM ----------
Just out of curiosity.. I've just read some posts on here about people getting their phones back from repair and their bootloader says "Device is ENGINEERING" instead of "Device is LOCKED" or "Device is UNLOCKED".
What does yours say? I'm mainly just wondering if it being in ENGINEERING mode is why you are not getting the OTA...
DaMadOne said:
Yea, your warranty is void at this point anyways so why not just unlock it! I root and use TiBu.. so I've not tested other backup methods but I'm pretty sure there are backup apps on the playstore that don't require root you could try.
BUT, the step "fastboot erase userdata" is what erases your installed apps/setting and personal files, etc. Really you can just SKIP that step and you SHOULD be ok. Then your apps and settings will be there when you boot 6.0. I was just providing instructions for a fully clean flash. I would say you have a 98% chance it will be just fine though if you don't erase userdata.
EDIT* oh and IIRC you will probably get an error or weird msg with the gpt.bin part of the flash.. ignore it..
EDIT 2* .... is one such app that doesn't look like it requires root. If you go this route make sure you copy everything over to your PC after using the backup app if you are going to run the "fastboot erase userdata" command.
GOOD LUCK!
---------- Post added at 06:38 PM ---------- Previous post was at 06:07 PM ----------
Just out of curiosity.. I've just read some posts on here about people getting their phones back from repair and their bootloader says "Device is ENGINEERING" instead of "Device is LOCKED" or "Device is UNLOCKED".
What does yours say? I'm mainly just wondering if it being in ENGINEERING mode is why you are not getting the OTA...
Click to expand...
Click to collapse
Haha suppose you're right! Sure I'll probably just wipe my device in the end, be nice to have a clean go at MM haha.
The bootloader status was indeed locked so I don't know what's causing the issue?
Anyway, thanks a million for the help I'll update if/when all goes well :good:
Despite my best efforts, it seems to have been in vain. I'm getting an error when trying to unlock the bootloader (something along the lines of no backup available, please try again) which is common to people who have sent their phone in for repair.
I'm just wondering if I could flash the firmware regardless of bootloader (Odin maybe?) At this point I'm happy to root suit and boot I'm just a bit sick of moto at this stage so want to be able to control my phone haha.
Any help much appreciated
clarkey586 said:
Despite my best efforts, it seems to have been in vain. I'm getting an error when trying to unlock the bootloader (something along the lines of no backup available, please try again) which is common to people who have sent their phone in for repair.
I'm just wondering if I could flash the firmware regardless of bootloader (Odin maybe?) At this point I'm happy to root suit and boot I'm just a bit sick of moto at this stage so want to be able to control my phone haha.
Any help much appreciated
Click to expand...
Click to collapse
Odin is for Samsung. Moto has RSDLite. But if your bootloader is locked the firmware package must be signed by Moto and I don't thing the ones floating around the web are.
So this is the point where it seems you're stuck with the (possibly) more PITA way. What you need to do is find the OTA zip that goes from 5.1.1 -> 6.0 and use the stock recovery to flash that with ADB. Boot to stock recovery, press button sequence to get the menu (I THINK at the fallen android dude you hold vol up for a few seconds then hit the power button while still holding it.. it's something like that to get the actual useful menu) then towards the bottom is an update via ADB, plug phone into pc via usb and select that and then in terminal do "adb sideload <OTA_file>.zip" and it will flash the OTA, assuming your device passes it's check it will feel like it's taking forever. This method won't wipe your phone either.
EDIT* HERE is a post with a link to the EU OTA and much better instructions than mine You can flash it with adb sideload or like that post says by copying it to your phone before booting the recovery and flashing it.
And then.. assuming you get to 6.0 using that OTA hopefully you can trigger the february OTA to auto download. If not... HERE is a link to a post with the february OTA zip for your phone. Flash it the same as last one.
If flashing the OTA with a locked bootloader and stock recovery doesn't work I'm afraid you're either stuck or your phone is on a return path to Moto again.
DaMadOne said:
Odin is for Samsung. Moto has RSDLite. But if your bootloader is locked the firmware package must be signed by Moto and I don't thing the ones floating around the web are.
So this is the point where it seems you're stuck with the (possibly) more PITA way. What you need to do is find the OTA zip that goes from 5.1.1 -> 6.0 and use the stock recovery to flash that with ADB. Boot to stock recovery, press button sequence to get the menu (I THINK at the fallen android dude you hold vol up for a few seconds then hit the power button while still holding it.. it's something like that to get the actual useful menu) then towards the bottom is an update via ADB, plug phone into pc via usb and select that and then in terminal do "adb sideload <OTA_file>.zip" and it will flash the OTA, assuming your device passes it's check it will feel like it's taking forever. This method won't wipe your phone either.
EDIT* HERE is a post with a link to the EU OTA and much better instructions than mine You can flash it with adb sideload or like that post says by copying it to your phone before booting the recovery and flashing it.
And then.. assuming you get to 6.0 using that OTA hopefully you can trigger the february OTA to auto download. If not... HERE is a link to a post with the february OTA zip for your phone. Flash it the same as last one.
If flashing the OTA with a locked bootloader and stock recovery doesn't work I'm afraid you're either stuck or your phone is on a return path to Moto again.
Click to expand...
Click to collapse
Ah sure I'll give that a go! Just checking if there are any precautions I should be taking for this? Don't want to brick the phone without the ability to flash it back to life again!
clarkey586 said:
Ah sure I'll give that a go! Just checking if there are any precautions I should be taking for this? Don't want to brick the phone without the ability to flash it back to life again!
Click to expand...
Click to collapse
You should be fine. The OTA zip is going to check all of the files it is going to patch first and only upgrade if everything passes. If it finds ANYTHING amiss... it will refuse to flash it. If it refuses to flash it your only hope is to send it to Moto unfortunately.
DaMadOne said:
You should be fine. The OTA zip is going to check all of the files it is going to patch first and only upgrade if everything passes. If it finds ANYTHING amiss... it will refuse to flash it. If it refuses to flash it your only hope is to send it to Moto unfortunately.
Click to expand...
Click to collapse
You, my friend, are a hero.
That seems to have done the trick with no issues (going to see if I can potentially unlock the bootloader now) and I'm finally on MM haha. Seems I have to perform the Feb security update separately too for some reason but I'm not too worried about doing things manually.
Sent you a small token of my appreciation, have a pint on me
Thanks once again
clarkey586 said:
You, my friend, are a hero.
That seems to have done the trick with no issues (going to see if I can potentially unlock the bootloader now) and I'm finally on MM haha. Seems I have to perform the Feb security update separately too for some reason but I'm not too worried about doing things manually.
Sent you a small token of my appreciation, have a pint on me
Thanks once again
Click to expand...
Click to collapse
Sweet! Thanks for the pint! Glad you're updated now. Did it end up giving you the OTA for the February patch or did you have to use the 2nd OTA?
DaMadOne said:
Sweet! Thanks for the pint! Glad you're updated now. Did it end up giving you the OTA for the February patch or did you have to use the 2nd OTA?
Click to expand...
Click to collapse
Had to use the 2nd OTA.zip but I didn't really try any of the remove sim card stuff or waiting long. No unlockable bootloader either but I'm satisfied for the moment haha.
So i was recording a video, when it entered a state where I had to reboot the phone. I did so, and it got stuck. I did a hard reset. The phone then gets stuck at bootloader unlocked. I entered fastboot, selected recovery, and it gets stuck at the twrp logo. Any ideas? I also re-flashed twrp and it still get stuck.
Can you boot TWRP with 'fastboot boot twrp.img' and do anything? (Replace 'twrp.img' with your TWRP image filename)
If not, try fastboot flashing back to stock, but it kind of sounds like your emmc (internal storage chip) might have take a dump. Very unusual, but not unheard of.
acejavelin said:
Can you boot TWRP with 'fastboot boot twrp.img' and do anything? (Replace 'twrp.img' with your TWRP image filename)
If not, try fastboot flashing back to stock, but it kind of sounds like your emmc (internal storage chip) might have take a dump. Very unusual, but not unheard of.
Click to expand...
Click to collapse
I used a restore-to-stock tool. It didn't actually restore me to stock. I have NO CLUE what it did, but suddenly i saw my custom boot animation again, and was able to boot into twrp, altough my nandroids are gone. I flashed a rom, and it didn't recognize the sim card. I flashed a new rom, and it recognizes the card, but i get no service (in my house where i always get service). Any ideas?
thebaconbox said:
I used a restore-to-stock tool. It didn't actually restore me to stock. I have NO CLUE what it did, but suddenly i saw my custom boot animation again, and was able to boot into twrp, altough my nandroids are gone. I flashed a rom, and it didn't recognize the sim card. I flashed a new rom, and it recognizes the card, but i get no service (in my house where i always get service). Any ideas?
Click to expand...
Click to collapse
This is why one-click tools are bad... You need to flash the full stock image manually, and not downgrade, you must use the same or newer version of stock firmware than you device last had installed.
acejavelin said:
This is why one-click tools are bad... You need to flash the full stock image manually, and not downgrade, you must use the same or newer version of stock firmware than you device last had installed.
Click to expand...
Click to collapse
How do I do that?
thebaconbox said:
How do I do that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/mot...de-return-to-stock-relock-bootloader-t3489110
acejavelin said:
http://forum.xda-developers.com/mot...de-return-to-stock-relock-bootloader-t3489110
Click to expand...
Click to collapse
Could I just flash the NON-HLOS.bin modem in fastboot and nothing else?
thebaconbox said:
Could I just flash the NON-HLOS.bin modem in fastboot and nothing else?
Click to expand...
Click to collapse
No, I don't think so, but you could do it like this:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin (optional)
acejavelin said:
No, I don't think so, but you could do it like this:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin (optional)
Click to expand...
Click to collapse
And i can do this with twrp installed and the pure nexus custom rom installed and it should work just fine?
thebaconbox said:
And i can do this with twrp installed and the pure nexus custom rom installed and it should work just fine?
Click to expand...
Click to collapse
Yes
acejavelin said:
Yes
Click to expand...
Click to collapse
Alright, I flashed everything and my cell service now works flawlessly.
thebaconbox said:
Alright, I flashed everything and my cell service now works flawlessly.
Click to expand...
Click to collapse
Awesome!
hy,
my purenexus rom was running perfectly but today i was installing spotify and it hanged and then i had to retsart but now it stucks on bootloader warning screen .recvory also stucks on twrp logo . now what should i do .i googled and found this thread.please guide me which thread do i need to follow ..will my bootloader get locked again ? where do i have to start it from? i also have nandroid backup of previous custom rom which is truepure rom. please guide me.
Flash(with fastboot) again twrp(wipe system, cache, data, dalvik) and restore your backup. @azzammalik
dzidexx said:
Flash(with fastboot) again twrp(wipe system, cache, data, dalvik) and restore your backup. @azzammalik
Click to expand...
Click to collapse
if i flash twrp again then it would stuck again on twrp logo as this op suggested . by flashing through fastboot you meant stock firmware then can you please guide me which file i have to download so i can just flash it using fastboot. and is there any way so i dont loose my data thanks
azzammalik said:
if i flash twrp again then it would stuck again on twrp logo as this op suggested . by flashing through fastboot you meant stock firmware then can you please guide me which file i have to download so i can just flash it using fastboot. and is there any way so i dont loose my data thanks
Click to expand...
Click to collapse
Only with twrp you can save your data.
What version did you used? Try with another, maybe don't flash - only boot.
"fastboot boot NameOfTwrp.img"
If it boot copy your data to pc.
Stock you can flash with fastboot, here is "how to", download and flash the highest version for you model:
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
Read carefully, don't lock bootloader.
Long story short. I had an Axon 7 A2017 B11 which I updated to B13. I was able to unlock the bootloader, root the phone then flash a custom rom Z.A.D.Mix7_v0.3. I was having fun with the phone but I did something very stupid when I realised I could not use Android pay due to unlocked boot loader. Without doing enough research, I went to fastboot and did a fastboot oem lock. The command was successful but I could no longer boot into the system or recovery or fastboot. I tried MiFlash with B07 which was posted in this forum, but it did not work, came back an error of bad format. Then I used axon7tool to flash TWRP 3.0.2 and the boot.img which I extracted from B13. I am now able to boot into TWRP and fastboot. But I still do not have a working system. I tried fastboot oem unlock, it does not let me do it. I flash ZAD Mix7 again but once I flash that it does not boot anymore. I am now really stuck. What should I do to go back to stock then start everything again. Thanks a lot for the help.
I understand your device doesn't boot into system anymore, but can adb on your pc detect it at all? If so, you can try following all steps after "B)" in my tutorial. I think your aboot img and fbop partition are messed up. If you can use adb to replace the files in aboot and fbop with files that allow the fastboot oem unlock command to be executed, it should be unlockable again. After that, custom ROMs should boot.
Stock bootloader
Controllerboy said:
If you can use adb to replace the files in aboot and fbop with files that allow the fastboot oem unlock command to be executed, it should be unlockable again. After that, custom ROMs should boot.
Click to expand...
Click to collapse
I'm having a similar issue. Although my phone boots to stock rom I seem to have messed up my bootloader. I had TWRP and unlocked bootloader. I, similarly, locked the bootloader and things seemed to be fine. After attempting to install Nougat received from OTA I realized my bootloader is corrupted. When I hold the power and volume up the phone seems to just turn off (or go to EDL mode? I'm not sure) I can always just hold power and it'll boot up normally. Is there a way to get the stock bootloader to work and keep it locked?
I also bricked my A7 after relocking my bootloader. I used tenfar's tool to make TWRP my boot.img, then flashed ZTE's stock B20 image. Here's the thread where I found the file links.
From there I updated all the way up to the OTA Nougat, but I suppose you can decide where you want to go after it's unbricked. Hope this helps.
Why are so many people relocking bl? Regardless, always take an ota before locking to ensure you are completely shock.
Stock bootloader
lafester said:
Why are so many people relocking bl? Regardless, always take an ota before locking to ensure you are completely shock.
Click to expand...
Click to collapse
Don't you have to be running a locked bootloader in order to be able to install OTAs?
aabnamak said:
Don't you have to be running a locked bootloader in order to be able to install OTAs?
Click to expand...
Click to collapse
Of course not.
aabnamak said:
Don't you have to be running a locked bootloader in order to be able to install OTAs?
Click to expand...
Click to collapse
No, you do not. I thought that was the case at first as well, but I was mistaken. You do, however, need the stock recovery and an untouched system partition.
My problem is that I don't seem to have a recovery at all. I realized once the ZTE logo pops up I can hold down both volume keys and get to the bootloader. The bootloader is locked but does not display a bootloader version or basedband version. I tried the tenfar tool (axon7root.exe) and now my phone doesn't boot into the system either. I really need help...
Just an update to everyone that helped.
I finally managed to fix it.
I used axon7tool to flash a signed TWRP, so that i can boot into TWRP. The signed TWRP is the only way to make it work. Then I downloaded the A2017 B11 from this thread
https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
There are two zip files. The boot stack and the rom. Because it is a stock rom, I can boot into the system. The next thing I did was to enable the developer option and turn back on the option to allow OEM unlock.
I went back to TWRP. boot into the fastboot screen. Then I simply typed in 'fastboot oem unlock'.
I went back to TWRP, which says can't read encrypted device. I formated everything. mount the USB then flash the custom rom again.
Hola, phone fixed. Made me sweat for the whole day.
deleted...forgot I had a micro sd card. Flashed stock update from the card and it worked. Phew!
I did not see this posted anywhere, nor do I see it on Google's Factory Image website/instructions.
Based on testing... When re-locking the bootloader, "fastboot flashing lock" does NOT seem to lock the critical partition.
After following Google's steps to a T and locking the regular bootloader, It was indeed locked. I even attempted to lock regular bootloader again, and received a message stating it was already locked. Bootloader screen also says everything is locked. All is fine and dandy, right?
For ****s and giggles, I tried performing "fastboot flashing lock_critical". It indeed asked me if I wanted to lock the critical partition. After re-locking critical, I was not able to lock critical again. Safe to say, critical does not get re-locked when re-locking regular bootloader.
Safe to say... to re-lock the bootloader completely, you probably want to perform "fastboot flashing lock_critical" then perform the regular "fastboot flashing lock".
bigblueshock said:
I did not see this posted anywhere, nor do I see it on Google's Factory Image website/instructions.
Based on testing... When re-locking the bootloader, "fastboot flashing lock" does NOT seem to lock the critical partition.
After following Google's steps to a T and locking the regular bootloader, It was indeed locked. I even attempted to lock regular bootloader again, and received a message stating it was already locked. Bootloader screen also says everything is locked. All is fine and dandy, right?
For ****s and giggles, I tried performing "fastboot flashing lock_critical". It indeed asked me if I wanted to lock the critical partition. After re-locking critical, I was not able to lock critical again. Safe to say, critical does not get re-locked when re-locking regular bootloader.
Safe to say... to re-lock the bootloader completely, you probably want to perform "fastboot flashing lock_critical" then perform the regular "fastboot flashing lock".
Click to expand...
Click to collapse
we unlocked bootloader then unlocked critical
so it makes sense to lock critical then lock bootloader as you said
abogrhen said:
we unlocked bootloader then unlocked critical
so it makes sense to lock critical then lock bootloader as you said
Click to expand...
Click to collapse
Oh believe me, I agree. I thought it was strange re-locking the critical isn't part of Googles Instructions. Not even sure if it matters, but just an extra security precaution
Thank You very much for the heads up. Saved me a headache
So the process for stock and locked would be to install a factory image to wipe and bring back to stock, fastboot flashing lock_critical, and fastboot flashing lock?
rester555 said:
So the process for stock and locked would be to install a factory image to wipe and bring back to stock, fastboot flashing lock_critical, and fastboot flashing lock?
Click to expand...
Click to collapse
Correct :good: However, I wouldn't do it unless you plan to RMA it, or sell it
Badger50 said:
Correct :good: However, I wouldn't do it unless you plan to RMA it, or sell it
Click to expand...
Click to collapse
Hmmmm what about if you are worried about theft. You can still wipe the phone and login with another account can't you with the bootloader unlocked? Where as the phone will always be tied to the last google account logged in if the bootloader is locked, making the phone useless to sell even overseas. I could be wrong though.
When re-locking my bootloader on my Pixel 2 XL, I only needed to enter "fastboot flashing lock_critical" first. When I entered "fastboot flashing lock" afterwards, this error was returned:
FAILED (remote: ' Device already : locked!')
Seems you only need one step not both. My device is now 100% stock and bootloader is locked and ready for RMA.
rspkt said:
When re-locking my bootloader on my Pixel 2 XL, I only needed to enter "fastboot flashing lock_critical" first. When I entered "fastboot flashing lock" afterwards, this error was returned:
FAILED (remote: ' Device already : locked!')
Seems you only need one step not both. My device is now 100% stock and bootloader is locked and ready for RMA.
Click to expand...
Click to collapse
Yes. just "fastboot flashing lock_critical" will completely lock your bootloader
Looking to sell my phone. So is there detailed instructions I can follow to return to stock and relock bootloader?
def-g said:
Looking to sell my phone. So is there detailed instructions I can follow to return to stock and relock bootloader?
Click to expand...
Click to collapse
Clean fastboot the factory and let it wipe your device. Then factory reset, then lock the bootloader. You must be 100% stock before you lock it down my friend :good:
Badger50 said:
Clean fastboot the factory and let it wipe your device. Then factory reset, then lock the bootloader. You must be 100% stock before you lock it down my friend :good:
Click to expand...
Click to collapse
If data is wiped once I flash the factory image. Why would I need to factory reset it? Your wisdom is appreciated.
def-g said:
If data is wiped once I flash the factory image. Why would I need to factory reset it? Your wisdom is appreciated.
Click to expand...
Click to collapse
Just an extra precaution my friend to make sure that puppy is squeaky clean!
Badger50 said:
Just an extra precaution my friend to make sure that puppy is squeaky clean!
Click to expand...
Click to collapse
Hahaha. :good:
Is the OEM unlocking supposed to be grayed out?
JarMagic said:
Is the OEM unlocking supposed to be grayed out?
Click to expand...
Click to collapse
Usually it's greyed out if it's already unlocked or a verizon phone