Unlock bootloader without wipe data ? - ZTE Axon 7 Questions & Answers

Hi i need to do a fastboot to do the command fastboot erase modemst1 bit my botloader is locked I think so I can not do this right? So please how to unlock the bartender without wipe data? I already try but none work

Yough said:
Hi i need to do a fastboot to do the command fastboot erase modemst1 bit my botloader is locked I think so I can not do this right? So please how to unlock the bartender without wipe data? I already try but none work
Click to expand...
Click to collapse
You can't unlock your bootloader without wiping the /data partition. That would be a huge security flaw.
Edit: Besides, why are you trying to wipe your modem? That is a terrible idea.

Related

[Tutorial] Restore Nexus 9 to Stock

I have a defective device and in preparing to return it, I locked the bootloader and found a nasty little message at the top of the screen when booting:
Code:
This is a development device not intended for production use.
I was afraid that the N9 was like the N5 & 7 with the "tamper" flag, but after some digging (and advice from others out here), I decided to restore the factory image to see if that would overwrite the image. Yes! No more big fat red "I unlocked my bootloader and may have voided my warranty" message.
I can't take credit for this, but I thought I would consolidate everything I was finding in the Q&A threads into one spot, so I put this little tutorial together. Thank you @Pilz, @jd1639 & @PhilDX for your various posts.
Step 1 - Prepare your system
[Windows]
Since your bootloader is unlocked, you probably already have ADB and fastboot, but if not, grab the SDK from here, unzip and add the "platform-tools" directory to your PATH statement
If your drivers are set up properly and your device has Android debugging enabled, connect USB and execute `adb devices` from a command prompt you should see your device listed
Download the factory image for "volantis" here
The image is double zipped, so unzip, untar, then unzip the image-volantis-lrx21q.zip file into the same directory that contains the bootloader*.img file
Step 2 - Unlock bootloader
If you locked your bootloader, unlock again:
Code:
adb reboot bootloader
fastboot oem unlock
Step 3 - Flash stock image
The flash-all.bat script is broken, so you have to do it by hand:
Open a command prompt
cd into the directory where you unzipped the factory image files
Code:
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
fastboot reboot-bootloader
fastboot erase system
fastboot erase recovery
fastboot erase cache
fastboot erase boot
fastboot erase userdata
fastboot erase vendor
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
Before rebooting, relock the bootloader:
Code:
fastboot oem lock
Your N9 will reboot and do another factory reset (even though an oem lock is not supposed to).
Typo: fastboot oem unlock
hirndurst said:
Typo: fastboot oem unlock
Click to expand...
Click to collapse
Hahaha! Thanks.
always good to know! thanks!
Just a question, I'm still a beginner at adb fastboot flashing.
But doesn't the oem unlocking and subsequent oem lock, erase everything anyway, so are the erase commands still required?
AjunNg said:
Just a question, I'm still a beginner at adb fastboot flashing.
But doesn't the oem unlocking and subsequent oem lock, erase everything anyway, so are the erase commands still required?
Click to expand...
Click to collapse
The erase commands are required. I believe that a factory reset only clears userdata (and probably cache). You need to run the others to clear those partitions to make room for the factory images. Each of those commands run pretty quick anyway.
DarthSudo said:
The erase commands are required. I believe that a factory reset only clears userdata (and probably cache). You need to run the others to clear those partitions to make room for the factory images. Each of those commands run pretty quick anyway.
Click to expand...
Click to collapse
You could also use fastboot -w instead of the erases
Sent from my Nexus 9 using XDA Free mobile app
Thanks for this thread. Great guide.
jd1639 said:
You could also use fastboot -w instead of the erases
Click to expand...
Click to collapse
According to the fastboot "help", -w only formats userdata and cache, does it actually format the other partitions as well? This wouldn't be the first time the documentation is wrong...
Code:
-w erase userdata and cache (and format
if supported by partition type)
Thanks for this. I RMA'd my Nexus 9 and sending it back tomorrow
DarthSudo said:
According to the fastboot "help", -w only formats userdata and cache, does it actually format the other partitions as well? This wouldn't be the first time the documentation is wrong...
Code:
-w erase userdata and cache (and format
if supported by partition type)
Click to expand...
Click to collapse
It only formats userdata and cache. But you don't need to erase the other partitions
Sent from my Nexus 5 using XDA Free mobile app
AjunNg said:
Just a question, I'm still a beginner at adb fastboot flashing.
But doesn't the oem unlocking and subsequent oem lock, erase everything anyway, so are the erase commands still required?
Click to expand...
Click to collapse
jd1639 said:
You could also use fastboot -w instead of the erases
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
jd1639 said:
It only formats userdata and cache. But you don't need to erase the other partitions
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
You guys are all right. I looked back at some of my notes and I've flashed plenty of devices w/o formatting the other partitions first. Just userdata and cache. Thanks!
Hey guys, just wanted to thank you for the fixed "script". This is now my flash-stock.sh script I use whenever I need to flash a nexus device as the one delivered by google just doesn't work (reboot loop due to crashing apps on startup or "missing system.img").
Works perfect and I always like to not dirty but rather make a clean flash as it just reduces the number of possible faults .
Cheers
Creamy
Just got my N9. First thing I did was to apply all updates, then unlock bootloader, boot into TWRP and make a system image. Then I flashed TWRP and rooted. Now if I want to take an OTA update, all I have to do restore the system image and flash the stock recovery, right? Am I missing anything? Thx.
Sent from my Nexus 6 using Tapatalk
bruce7373 said:
Just got my N9. First thing I did was to apply all updates, then unlock bootloader, boot into TWRP and make a system image. Then I flashed TWRP and rooted. Now if I want to take an OTA update, all I have to do restore the system image and flash the stock recovery, right? Am I missing anything? Thx.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
The OTA will run a check and will fail if the image isn't basically stock. For you, just do a full unroot in the SuperSU app (under Settings), then you need to replace TWRP with the stock recovery from fastboot:
Code:
fastboot flash recovery recovery.img
Reboot then take the OTA.
Of course, you will need to install TWRP and re-root again after the OTA...
DarthSudo said:
The OTA will run a check and will fail if the image isn't basically stock. For you, just do a full unroot in the SuperSU app (under Settings), then you need to replace TWRP with the stock recovery from fastboot:
Code:
fastboot flash recovery recovery.img
Reboot then take the OTA.
Of course, you will need to install TWRP and re-root again after the OTA...
Click to expand...
Click to collapse
Thx, that seems simple enough. But I made the initial system (stock) backup before I rooted. That's why I was thinking restoring that would work. I just wasn't sure about the recovery, whether the restore would put the stock recovery back or not.
Sent from my Nexus 6 using Tapatalk
DarthSudo said:
I have a defective device and in preparing to return it, I locked to bootloader and found a nasty little message at the top of the screen when booting:
Code:
This is a development device not intended for production use.
Your N9 will reboot and do another factory reset (even though an oem lock is not supposed to).
Click to expand...
Click to collapse
Hi,
is there a way to get rid of that red message if your bootloader is locked and you cannot boot into OS?
Thanks!
EDIT* Nevermind
Hey. Sorry for reviving this thread.
I installed Remix OS on my N9 and (after discovering that performance is horrible, with ~80% RAM usage on idle) after a reboot, Remix OS won't get past it's boot splash. I am attempting to flash my device back to stock.
I never touched the bootloader (never did any 'fastboot flash bootloader ...' or anything), so it it still necessary to flash the bootloader image, or can I just flash the system.img, boot.img, vendor.img etc.?
The bootloader had never changed so there is no reason to flash it.
Sent from my Nexus 9 using XDA Free mobile app

How can I relock Bootloader?

I need to relock my bootloader and it won't do so. I have tried Fastboot oem lock and it says it finishes it but changes nothing on the device. I need to return, PLEASE HELP!
jdellingson7 said:
I need to relock my bootloader and it won't do so. I have tried Fastboot oem lock and it says it finishes it but changes nothing on the device. I need to return, PLEASE HELP!
Click to expand...
Click to collapse
Why do you need to return?
I bought the 16gb because I couldn't not find a 32gb anywhere. Amazon had the 32 available yesterday so I bought one
You can lock it back up. However it will still give you the unlocked bootloader screen, and it will show status 2 in the bootloader menu.
There is no way to reset it without leaving flags that it was unlocked
Sent from my Nexus 6 using Tapatalk
I wouldn't worry about it, if I were you. Flash the stock logo.bin, relock it, and don't worry about what it says in the recovery menu. I'm not making any promises, but that's the way I would play it.
jaben2 said:
You can lock it back up. However it will still give you the unlocked bootloader screen, and it will show status 2 in the bootloader menu.
There is no way to reset it without leaving flags that it was unlocked
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Is there a physical fuse that pops a la modern Samsung phones? Or are we still waiting for developers to figure out how to reset the flags on this particular model? I know that I've seen threads for other devices that walk you through resetting flags, so if it is only done with software on this device, we should be able to restore to 100% stock soon enough.
Here is Motorola's page on re-locking:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Unfortunately they don't have the stock image available yet for the Moto X 2015 (scroll down).
I'm returning mine due to a damage claim and wanted to re-lock but we can't yet, at least officially. Moto still records when you unlocked, now listed under 'My Support History' in my Profile, so there's no way to hide that you unlocked if you did it through their site. The good news is it didn't affect my warranty claim in talking to a few support staff, and of course made sure not mention it myself but nobody there brought it up, so I tend to doubt it will affect your return. I did use the Restore to Stock tool (worked great!) and then removed the Unlocked warning, so it's just as if it had a factory reset.
I just relocked mine, no white screen on boot.
but it says
Device is LOCKED. Status Code: 2
Software status: Modified
Here's how I did it.
download this
open cmd, navigate to the folder extracted from the zip in the link above, this will erase your entire phone, reset to stock firmware and relock the bootloader
boot into bootloader pwr+vol down
run these commands
Code:
fastboot oem lock begin
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 system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
Now If I can figure out how to remove the status code and make the software status official.
It's probably impossible, for now at least.
Thanks this worked but it didn't remove the bootloader unlock warning. So I just flashed the boot logo and it's good to go. I'm pretty sure Best Buy is no educated on these things.
tylerwatt12 said:
I just relocked mine, no white screen on boot.
but it says
Device is LOCKED. Status Code: 2
Software status: Modified
Here's how I did it.
download this
open cmd, navigate to the folder extracted from the zip in the link above, this will erase your entire phone, reset to stock firmware and relock the bootloader
boot into bootloader pwr+vol down
run these commands
Code:
fastboot oem lock begin
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 system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
Now If I can figure out how to remove the status code and make the software status official.
It's probably impossible, for now at least.
Click to expand...
Click to collapse
jdellingson7 said:
Thanks this worked but it didn't remove the bootloader unlock warning. So I just flashed the boot logo and it's good to go. I'm pretty sure Best Buy is no educated on these things.
Click to expand...
Click to collapse
Lol I'll be very surprised if someone knows lol. Most of them probably use iPhone anyway. It feels good being a geek ?
if they can change the software status on an M9 i see no reason why they couldn't on the MXP
jdellingson7 said:
Thanks this worked but it didn't remove the bootloader unlock warning. So I just flashed the boot logo and it's good to go. I'm pretty sure Best Buy is no educated on these things.
Click to expand...
Click to collapse
I tried flashing the logo.bin, but that didn't replace the bootloader unlock warning. Where did you get the boot logo to replace the warning and to what partition did you flash it?
http://forum.xda-developers.com/mot...o-remove-unlocked-bootloader-warning-t3201141
Tanker Bob said:
I tried flashing the logo.bin, but that didn't replace the bootloader unlock warning. Where did you get the boot logo to replace the warning and to what partition did you flash it?
Click to expand...
Click to collapse
jdellingson7 said:
http://forum.xda-developers.com/mot...o-remove-unlocked-bootloader-warning-t3201141
Click to expand...
Click to collapse
Thank you! That worked perfectly.
Good deal, sending mine back this week this will come in handy
Just to let you know, I returned mine unlocked. Unlocked has more to do with warranty claims, it doesn't void returns. That's a mandated law. Moto will just relock it and restore it to stock.
Sent from my Nexus 7 (2013) using XDA Free mobile app
sent mine back, wasn't completely locked, still had the flag set. I got my money back, just wanted to let everyone know.
Will this restore the stock bootloader as well? In rooting mine it called for installing twrp...so wondering if this is a method back to complete stock?
Also, anyone know if rooted twrp will get ota's?
mcdonsco said:
Will this restore the stock bootloader as well? In rooting mine it called for installing twrp...so wondering if this is a method back to complete stock?
Also, anyone know if rooted twrp will get ota's?
Click to expand...
Click to collapse
The email you get with the unlocked bootloader contract says no OTA's
tylerwatt12 said:
sent mine back, wasn't completely locked, still had the flag set. I got my money back, just wanted to let everyone know.
Click to expand...
Click to collapse
nikeman513 said:
Just to let you know, I returned mine unlocked. Unlocked has more to do with warranty claims, it doesn't void returns. That's a mandated law. Moto will just relock it and restore it to stock.
Sent from my Nexus 7 (2013) using XDA Free mobile app
Click to expand...
Click to collapse
I'm returning mine as well and was stressing over this my bootloader being unlocked. Thank you both for your feedback on what happened after you returned it. People tend to forget to give details about the outcome on threads like this. So I give :good::good: to you guys
Don't worry too much about the unlocked bootloader status messages, especially if you flash the logo.bin to remove the giant notice on bootup.
When you return a phone, the RMA department is interested in just processing the return as fast as possible, and moving on to the next return. They are not in the business of checking every single individual device for voided warranties, for purposes of playing "gotcha" to find reasons to reject a return.
The fact of the matter is that it is a very small minority of people that will unlock / root a phone, and return it. And an even smaller portion of that minority that cause warranty-vouding damage as a result of those software-related changes.
Will there be people that abuse this return policy, and process illegitimate returns? Yes, of course. But it will cost Motorola (or Amazon) more time/money to individually check each return for voided warranties, than it would to just process the RMA as fast as possible and move on.
Sometimes, even if you KNOW people are stealing from you, it's still cheaper to just let then steal, than to take the time to try and stop that theft.
Sent from my XT1575 using Tapatalk

Fastboot rom for Moto G4 PLUS XT1643 NPJS25.93-14-15

Hii !! How long will it take for the fastboot rom to arrive for Moto g4 plus Indian retail xt1643 ... With 1st Feb 2018 security patch ???
Vs1607 said:
Hii !! How long will it take for the fastboot rom to arrive for Moto g4 plus Indian retail xt1643 ... With 1st Feb 2018 security patch ???
Click to expand...
Click to collapse
https://drive.google.com/file/d/1qR9MUUQCNUQ6sAivz2OTkc4TW88vmszv/edit
Already available since a month.
smog2699 said:
https://drive.google.com/file/d/1qR9MUUQCNUQ6sAivz2OTkc4TW88vmszv/edit
Already available since a month.
Click to expand...
Click to collapse
Where'd you find it ?? I mean I've been searching this whole time and couldn't find it ?
.
.
.
Just curious ! ?
Vs1607 said:
Where'd you find it ?? I mean I've been searching this whole time and couldn't find it Just curious ! ?
Click to expand...
Click to collapse
It was posted in the forum at least three times.
thorin0815 said:
It was posted in the forum at least three times.
Click to expand...
Click to collapse
Hi thorin0815, Vs1607,
Just a off thread question. If a flash this image it will wipe the data? My issue is described on below link. Please help me.
https://forum.xda-developers.com/moto-g4-plus/help/stock-moto-g4-plus-getting-rebooted-t3781480
hardythaker said:
Hi thorin0815, Vs1607,
Just a off thread question. If a flash this image it will wipe the data? My issue is described on below link. Please help me.
https://forum.xda-developers.com/moto-g4-plus/help/stock-moto-g4-plus-getting-rebooted-t3781480
Click to expand...
Click to collapse
If you want to avoid wiping your data whilst flashing the fastboot stock ROM, you can omit the 'fastboot erase userdata' command and you do not have to re-lock your bootloader (re-locking will wipe your data).
However, if you are experiencing instabilities as you mentioned, a data wipe is a useful troubleshooting step, and may help you determine if your data is corrupted or whether you may have a more serious hardware/firmware issue.
echo92 said:
If you want to avoid wiping your data whilst flashing the fastboot stock ROM, you can omit the 'fastboot erase userdata' command and you do not have to re-lock your bootloader (re-locking will wipe your data).
However, if you are experiencing instabilities as you mentioned, a data wipe is a useful troubleshooting step, and may help you determine if your data is corrupted or whether you may have a more serious hardware/firmware issue.
Click to expand...
Click to collapse
Okay thanks for your comments. I will give it a try. Just one question is that the latest firmware. Because I had recently updated the ROM.
hardythaker said:
Okay thanks for your comments. I will give it a try. Just one question is that the latest firmware. Because I had recently updated the ROM.
Click to expand...
Click to collapse
NPJS25.93-14-15 as of writing is the latest firmware, Feb 2018 security patch. What ROM did you update to?
echo92 said:
NPJS25.93-14-15 as of writing is the latest firmware, Feb 2018 security patch. What ROM did you update to?
Click to expand...
Click to collapse
April ota is the last , but no one have it
leap_ahead said:
April ota is the last , but no one have it
Click to expand...
Click to collapse
Yeah the update note appears to be up but as you mentioned it's not been released yet to any channel. So for now the latest firmware we have is the Feb 2018 build.
echo92 said:
If you want to avoid wiping your data whilst flashing the fastboot stock ROM, you can omit the 'fastboot erase userdata' command and you do not have to re-lock your bootloader (re-locking will wipe your data).
However, if you are experiencing instabilities as you mentioned, a data wipe is a useful troubleshooting step, and may help you determine if your data is corrupted or whether you may have a more serious hardware/firmware issue.
Click to expand...
Click to collapse
Can i use this below commands. Also my bootloader is already locked, I have not unlocked the bootloader. Should I have to add any addtional command to above script like fastboot oem lock begin command.
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 dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
[STRIKE]fastboot erase userdata[/STRIKE]
fastboot erase customize
fastboot erase clogo
fastboot reboot
hardythaker said:
Can i use this below commands. Also my bootloader is already locked, I have not unlocked the bootloader. Should I have to add any addtional command to above script like fastboot oem lock begin command.
<Snip>
Click to expand...
Click to collapse
Okay, as your bootloader is locked, there's no need for the OEM lock commands. Using them, regardless of if your bootloader is locked or not, will erase your data.
Those commands look okay, just ensure in your flashing script that you have that erase userdata command removed (not just struck out). Your command list a look like:
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 dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot reboot
If this flash doesn't get your device going, you may have to wipe your data or consider a service repair as a locked bootloader gives us limited options for rescue.
echo92 said:
Okay, as your bootloader is locked, there's no need for the OEM lock commands. Using them, regardless of if your bootloader is locked or not, will erase your data.
Those commands look okay, just ensure in your flashing script that you have that erase userdata command removed (not just struck out). Your command list a look like:
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 dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot reboot
If this flash doesn't get your device going, you may have to wipe your data or consider a service repair as a locked bootloader gives us limited options for rescue.
Click to expand...
Click to collapse
Thanks mate. Am going to flash this tomorrow. Will surely let you know the outcome. Anyway if all this allow me to use my phone at least for an hour, I will take the backup of the necessary data and then will proceed with wipe data/factory reset.
echo92 said:
Okay, as your bootloader is locked, there's no need for the OEM lock commands. Using them, regardless of if your bootloader is locked or not, will erase your data.
Those commands look okay, just ensure in your flashing script that you have that erase userdata command removed (not just struck out). Your command list a look like:
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 dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot reboot
If this flash doesn't get your device going, you may have to wipe your data or consider a service repair as a locked bootloader gives us limited options for rescue.
Click to expand...
Click to collapse
Okay so I have flash the phone using above commands, but no luck, exact same issue is persists and even nothing has been changed on the phone, not even lock screen wallpaper.
So now do you have any more suggestion please let me know if not will proceed with Data Wipe. Also Even if I wipe user data and after that can I recover files using some Andrioid File Recovery Tools out there.
Waiting for your reply and will proceed as you will suggest. Thanks.
hardythaker said:
Okay so I have flash the phone using above commands, but no luck, exact same issue is persists and even nothing has been changed on the phone, not even lock screen wallpaper.
So now do you have any more suggestion please let me know if not will proceed with Data Wipe. Also Even if I wipe user data and after that can I recover files using some Andrioid File Recovery Tools out there.
Waiting for your reply and will proceed as you will suggest. Thanks.
Click to expand...
Click to collapse
That's not good, if a flash doesn't fix things.
1)Try to wipe your data via a factory reset. I think you can try to keep your internal storage by selecting to only wipe userdata in the stock recovery (boot to recovery, hold the power key then press the volume up key to get past the 'No Command screen', then under wipe data/factory reset, there should be an option to wipe userdata only). Then wipe cache/Dalvik in that same menu, and see if your device boots. I do not know if file recovery tools will work on non-rooted devices (due to restrictions on reading the data partition).
2)If that doesn't work, your device may have a serious hardware fault that only a service centre can resolve.
echo92 said:
That's not good, if a flash doesn't fix things.
1)Try to wipe your data via a factory reset. I think you can try to keep your internal storage by selecting to only wipe userdata in the stock recovery (boot to recovery, hold the power key then press the volume up key to get past the 'No Command screen', then under wipe data/factory reset, there should be an option to wipe userdata only). Then wipe cache/Dalvik in that same menu, and see if your device boots. I do not know if file recovery tools will work on non-rooted devices (due to restrictions on reading the data partition).
2)If that doesn't work, your device may have a serious hardware fault that only a service centre can resolve.
Click to expand...
Click to collapse
Okay so seems like am in serious trouble.
1) Done wipe data (user data only) with no luck.
2) Done wipe data with userdata and personalized content, still...
3) Flash stock ROM along with "Fastboot Erase userdata", but no joy.
Should I unlock the bootloader now and try to install TWRP and from there if I can go some where
And now I have kept the phone on Welcome Screen, its not getting rebooted, Am able to go till Select WIFI, even am able to connect to WIFI. Then on next screen it is asking me to "Accept Moto T&C", after that it will show me Checking Connectivity > Checking For Update > Checking Info.......and this is the point where it get restarted. Can you guess what is the issue, seems like its some network or connectivity hardware issue.
hardythaker said:
Okay so seems like am in serious trouble.
1) Done wipe data (user data only) with no luck.
2) Done wipe data with userdata and personalized content, still...
3) Flash stock ROM along with "Fastboot Erase userdata", but no joy.
Should I unlock the bootloader now and try to install TWRP and from there if I can go some where
And now I have kept the phone on Welcome Screen, its not getting rebooted, Am able to go till Select WIFI, even am able to connect to WIFI. Then on next screen it is asking me to "Accept Moto T&C", after that it will show me Checking Connectivity > Checking For Update > Checking Info.......and this is the point where it get restarted. Can you guess what is the issue, seems like its some network or connectivity hardware issue.
Click to expand...
Click to collapse
You'd only be able to unlock your bootloader if you enabled OEM unlocking in Settings>Developer Options, and you can only get to Developer Options if you can properly boot into the system (as a security measure)....
Hmm, if it's holding on the Setup Assistant now, can you use mobile data to set up instead of Wi-Fi? If it is an issue with the Wi-Fi, maybe using the mobile signal could get around that.
echo92 said:
You'd only be able to unlock your bootloader if you enabled OEM unlocking in Settings>Developer Options, and you can only get to Developer Options if you can properly boot into the system (as a security measure)....
Hmm, if it's holding on the Setup Assistant now, can you use mobile data to set up instead of Wi-Fi? If it is an issue with the Wi-Fi, maybe using the mobile signal could get around that.
Click to expand...
Click to collapse
Tried with mobile data too, but still same issue. Anyway am in service center now let's see what they say.
echo92 said:
You'd only be able to unlock your bootloader if you enabled OEM unlocking in Settings>Developer Options, and you can only get to Developer Options if you can properly boot into the system (as a security measure)....
Hmm, if it's holding on the Setup Assistant now, can you use mobile data to set up instead of Wi-Fi? If it is an issue with the Wi-Fi, maybe using the mobile signal could get around that.
Click to expand...
Click to collapse
Okay so after one-month of stupidity from service center and some other guys finally I myself resolved the issue.
1) Service center tried to flash the rom but didn't resolved the issue.
2) They changed the battery, but still the same issue.
3) They said that this is motherboard issue and it will cost 5200 INR.
Then gave my phone on yaantra .com to repair it they kept the phone for 5 days and said the same thing that it is a motherboard issue as network circuit is not working properly.
( In between this I end up buying OnePlus 6 :victory: :victory: )
Then I bought one new damaged phone in which motherboard was working fine. I replaced that motherboard with mine and still the same issue. After this I started disconnecting parts one by one which are there on display pannel. After checking speaker, vibrator, flash, when I disconnected the fingerprint sensor and rebooted the phone it was totally fine and no more reboots.
I never thought that a corrupted/damaged fingerprint scanner can do this kind of wired issue to a phone. .Now this will be a spare phone without fingerprint scanner. Thanks for your help @echo92

[Guide] Relock Oreo bootloader, go back to stock ROM and get OTA

This method is only works, if you are in Oreo
unlocked bootloader, and use custom rom,
DISCLAIMER
Not taking responsibility if it goes wrong
We have found a way to get back to stock, and relock the bootloader! for now, it only works for the XT-1635-02 because we dont have a signed stock image for any other phone model.
you can use this on any software channel!
How it works.
YOU NEED TO BE ON A CUSTOM ROM TO RELOCK THE BOOTLOADER!
1 - Download Stock ROM in the first post down below
2 - install adb minimal fastboot
3 - after install adb minimal fastboot, go to the install location and paste all the files there
5 - Copy all commands how is in this site and past it on the cmd screen and wait. (you need to press enter for the last command)
Stock Oreo Signed ROM
If u are in June bootloader Kindly use June Security Patch rom, otherwise, phone should be Brick
June Security Patch
Commands
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
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 system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash 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 system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash boot boot.img
fastboot oem lock
Now youre phone will reboot, and your phone is locked again.
I'm using this ROM here:
[ROM][Stock+] [7.1.1] Dec. Patch NPNS26.118-22-2-12 Prerooted
https://forum.xda-developers.com/moto-z-play/development/rom-nov-patch-npns26-118-22-2-8-t3717037
Do I need to perform any procedures before starting this installation?
I think fast boot erase modemmst 1 & 2 may get a result of IMEI 0 error.
talktosam said:
DISCLAIMER
Not taking responsibility if it goes wrong
We have found a way to get back to stock, and relock the bootloader! for now, it only works for the XT-1635-02 because we dont have a signed stock image for any other phone model.
you can use this on any software channel!
Click to expand...
Click to collapse
talktosam said:
So how does this differ from the method below that was posted here months ago by someone else on doing the same thing? Looks like you copied and pasted....
https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190
Click to expand...
Click to collapse
Jimi Mack said:
talktosam said:
DISCLAIMER
Not taking responsibility if it goes wrong
We have found a way to get back to stock, and relock the bootloader! for now, it only works for the XT-1635-02 because we dont have a signed stock image for any other phone model.
you can use this on any software channel!
Click to expand...
Click to collapse
talktosam said:
So how does this differ from the method below that was posted here months ago by someone else on doing the same thing? Looks like you copied and pasted....
Yes, text is copied, but rom is different Oreo... procedure is same...
https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190
Click to expand...
Click to collapse
Click to expand...
Click to collapse
talktosam said:
Thanks for clearing that up. So the older was to fully restore to Nougat and yours it to restore to Oreo. So being I never updated to Oreo I should restore with the old file, as I am sure yours would cause issues being I never updated to Oreo. You should clearly document that in the thread as well and not just the Title as well if this is the case. Just because most people do not thoroughly read but skim quickly and then jump without looking.
Click to expand...
Click to collapse
Jimi Mack said:
talktosam said:
Thanks for clearing that up. So the older was to fully restore to Nougat and yours it to restore to Oreo. So being I never updated to Oreo I should restore with the old file, as I am sure yours would cause issues being I never updated to Oreo. You should clearly document that in the thread as well and not just the Title as well if this is the case. Just because most people do not thoroughly read but skim quickly and then jump without looking.
Click to expand...
Click to collapse
Yes, if you are in 0xC182 Oreo bootloader, in title i mentioned its works only if u are in oreo bootloader unlocked
Click to expand...
Click to collapse
Can I use this tutorial if I have 0xC114 bootloader (february patch)???
gercdgcat said:
Can I use this tutorial if I have 0xC114 bootloader (february patch)???
Click to expand...
Click to collapse
Yes, but u are in custom rom, u can,
I was in AOSP 8.1 with Oreo bootloader (I had stock oreo before installing the ROM) and just did this procedure, everything went fine ! IMEI is safe and system works as intended, thank you !
If I have the bootloader blocked and I want to update to OREO with your tutorial which commands would I have to skip?
Dude you are a lifesaver..
---------- Post added at 12:32 PM ---------- Previous post was at 12:30 PM ----------
Mario3DS said:
I was in AOSP 8.1 with Oreo bootloader (I had stock oreo before installing the ROM) and just did this procedure, everything went fine ! IMEI is safe and system works as intended, thank you !
Click to expand...
Click to collapse
I am in the exact same situation as you. I will give this a try and report
djdelarosa25 said:
Dude you are a lifesaver..
---------- Post added at 12:32 PM ---------- Previous post was at 12:30 PM ----------
I am in the exact same situation as you. I will give this a try and report
Click to expand...
Click to collapse
Just do exactly what OP says and everything will be fine, I even recovered my Software Channel (attmx) somehow
oh and btw, you can "fix" the navbar bug in stock Oreo changing the theme with Custom Navigation Bar (it's an app)
I just did it and it fixed it completely
Mario3DS said:
Just do exactly what OP says and everything will be fine, I even recovered my Software Channel (attmx) somehow
oh and btw, you can "fix" the navbar bug in stock Oreo changing the theme with Custom Navigation Bar (it's an app)
I just did it and it fixed it completely
Click to expand...
Click to collapse
Your software channel isn't supposed to change anyway
Safety net failed, help
CTS profile match only failed. Is it because of unlocked bootloader?
The bootloader unlocked screen doesn't seem to want to go away
EDIT: My bootloader is still unlocked.
EDIT: Fixed. It wasn't mentioned that you need to enable OEM unlocking in Developer options, noobs like me might get confused. Lucky I got that sorted out
djdelarosa25 said:
The bootloader unlocked screen doesn't seem to want to go away
EDIT: My bootloader is still unlocked.
EDIT: Fixed. It wasn't mentioned that you need to enable OEM unlocking in Developer options, noobs like me might get confused. Lucky I got that sorted out
Click to expand...
Click to collapse
So... Now are you in Oreo stock with locked bootloader? In boot image only shows motorola logo? Nothing of bad key or any notification?
gercdgcat said:
So... Now are you in Oreo stock with locked bootloader? In boot image only shows motorola logo? Nothing of bad key or any notification?
Click to expand...
Click to collapse
Yup, 100% stock. No more bootloader warning message. The guide did not mention that within the custom ROM that you are using, you must have OEM Unlocking under Developer options turned on before you flash the commands.
djdelarosa25 said:
Yup, 100% stock. No more bootloader warning message. The guide did not mention that within the custom ROM that you are using, you must have OEM Unlocking under Developer options turned on before you flash the commands.
Click to expand...
Click to collapse
I think OEM Unlocking only exists in the stock ROM. Regardless of whether you're on a stock ROM already or are flashing the stock ROM, as you mentioned, OEM unlocking must be turned on for the OEM locking commands to work.
Of course, with re-locking your bootloader, it's up to you if you wish to keep OEM Unlocking enabled or disabled afterwards. If you disable it, your device will not be unlockable until you boot into system, which can be more secure but if you have any boot issues, then troubleshooting is a lot more difficult, plus you have no warranty. If you leave OEM unlocking on, then you could unlock your bootloader, but then so can anyone else with physical access to your device.
echo92 said:
I think OEM Unlocking only exists in the stock ROM. Regardless of whether you're on a stock ROM already or are flashing the stock ROM, as you mentioned, OEM unlocking must be turned on for the OEM locking commands to work.
Of course, with re-locking your bootloader, it's up to you if you wish to keep OEM Unlocking enabled or disabled afterwards. If you disable it, your device will not be unlockable until you boot into system, which can be more secure but if you have any boot issues, then troubleshooting is a lot more difficult, plus you have no warranty. If you leave OEM unlocking on, then you could unlock your bootloader, but then so can anyone else with physical access to your device.
Click to expand...
Click to collapse
OEM unlocking also exists in custom ROMs. The reason that relocking your bootloader is not possible with the stock ROM is that the option is greyed out if you have your bootloader unlocked, thus making the bootloader lock commands not work. With a custom ROM, I was able to toggle OEM unlocking on, even when my bootloader was already unlocked. This allowed the bootloader lock commands to work and make the warning message disappear.

Help me : How to restore factory image

Hi guys. Sorry for being noob.
Wanna asking (confused).
My Nexus 7 (2012 Wifi) used Omni Rom 4.4.4
I wanna restore back to Stock Rom.
Do i need to Unroot & Unlock my nexus first before click " flash-all.bat " ??.
I worry might be soft brick if wrong step.
Many many thanks ^_^v
suaji said:
Hi guys. Sorry for being noob.
Wanna asking (confused).
My Nexus 7 (2012 Wifi) used Omni Rom 4.4.4
I wanna restore back to Stock Rom.
Do i need to Unroot & Unlock my nexus first before click " flash-all.bat " ??.
I worry might be soft brick if wrong step.
Many many thanks ^_^v
Click to expand...
Click to collapse
No, you were previously on OmniROM means your bootloader is already unlocked. You just need to boot into bootloader/fastboot mode and flash stock image. Do make sure you have the correct drivers installed. You could use the Universal Naked Drivers if you don't have the correct drivers installed.
rahimali said:
No, you were previously on OmniROM means your bootloader is already unlocked. You just need to boot into bootloader/fastboot mode and flash stock image. Do make sure you have the correct drivers installed. You could use the Universal Naked Drivers if you don't have the correct drivers installed.
Click to expand...
Click to collapse
Noted!.
TQ Sir for replying me ^_^v
i saw inside flash.bat got code :
so that mean i need to do manual oem lock right?.
Code:
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
sleep 10
fastboot -w update image-nakasi-lmy47v.zip
suaji said:
Noted!.
TQ Sir for replying me ^_^v
i saw inside flash.bat got code :
so that mean i need to do manual oem lock right?.
Code:
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
sleep 10
fastboot -w update image-nakasi-lmy47v.zip
Click to expand...
Click to collapse
If you mean re-lock the bootloader, yes, you will have to do that manually. It's supposed to be a risky procedure so do so at your own risk.
By the way, your signature shows Next 7 3G, that would be the Tilapia rather than Grouper. Make sure before you flash please.
rahimali said:
If you mean re-lock the bootloader, yes, you will have to do that manually. It's supposed to be a risky procedure so do so at your own risk.
By the way, your signature shows Next 7 3G, that would be the Tilapia rather than Grouper. Make sure before you flash please.
Click to expand...
Click to collapse
thanks for helping sir.
now I can use stock rom back..

Categories

Resources