Related
I've been trying to unlock the bootloader since the A5CN701 update. Here's how i've tried:
1. Go to developer options -> Tick OEM Unlocking
2. Use the launcher.bat from IntelAndroid-FBRL-05-16-2015.7z from this topic http://forum.xda-developers.com/nokia-n1/general/play-store-howto-t3118965
3. Use the T4 option and the tablet ends up like this (because the bootloader is locked):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Use fastboot and enter this code:
Code:
fastboot oem unlock
Then the cmd console and the tablet should look like this:
5. Select ''Yes: change device state'' using the UI on the N1 but here's all i've received:
The result is :''Fail: couldn't change state''
So that's pretty much about how i've tried to unlock the bootloader. I don't know why i couldn't change the device state! Is there anyone that can help me?
I posted this topic so that everyone can join and make suggestions & solutions to rooting the A5CN701 firmware!
Any help would be much appreciated!
P/s: sorry for the sloppy photos, i didn't have time to crop and edit them
it's no use,I use the same way and i get my device state-unlocked.
C：\Dociments and Settings\fldministrator>cd C:\platform-tools
C：\platform-tools>adb reboot bootloader
C：\platform-tools>fastboot oen unlock
<bootloader) Please confirm the device state action using the UI-<bootloader) Userdata erase required, this can take a while ---
OKAV [ 5.844s]
finished- total time： 5.844s
C：\platform-tools>
and then I use the old way to root the device,only end like this.
copy needed files to our deuice
target reported nax download size of 536870912 bytes
sending ^/tmp/recouery.zip^ <3477 KB> • • •
OKAV [ 0.297s]
writing ^/tmp/recovery.zip^ • • •
FAILED <remote： not allowed to flash this partition>
finished, total tine： 0.516s
target reported max download size of 536870912 bytes
sending ^/tmp/recouerv. launcher^ <400 KB> • • •
OKAV [ 0.203s]
writing '/tmp/recouerv. launcher' • • •
FAILED <remote： not allowed to flash this partition>
finished, total tine： 0.422s
we need to stop logcat before replacing it
<bootloader> Start partitioning
OKAY [ 0.406s]
finished, total tine： 0.406s
target reported max download size of 536870912 bytes
sending ^/system/bin/logcat'<178KB
OKAY 【0.219s】
writing '/systen/bin/logcat^•••
FAILED <remote： not allowed to flash this partition>
finished, total tine： 0.422s
issue fastboot oem ''stop.partitioning command to start cwn recouerv：
<bootloader> Stop partitioning
OKAY 【0.391s】
finished, total tine： 0.391s
sorry，can't upload img
PS:if you unlock,the device only stay in bootloader,if you want to open and normal use device,you must lock it.
乄Rain丶Man said:
it's no use,I use the same way and i get my device state-unlocked.
C：\Dociments and Settings\fldministrator>cd C:\platform-tools
C：\platform-tools>adb reboot bootloader
C：\platform-tools>fastboot oen unlock
<bootloader) Please confirm the device state action using the UI-<bootloader) Userdata erase required, this can take a while ---
OKAV [ 5.844s]
finished- total time： 5.844s
C：\platform-tools>
and then I use the old way to root the device,only end like this.
copy needed files to our deuice
target reported nax download size of 536870912 bytes
sending ^/tmp/recouery.zip^ <3477 KB> • • •
OKAV [ 0.297s]
writing ^/tmp/recovery.zip^ • • •
FAILED <remote： not allowed to flash this partition>
finished, total tine： 0.516s
target reported max download size of 536870912 bytes
sending ^/tmp/recouerv. launcher^ <400 KB> • • •
OKAV [ 0.203s]
writing '/tmp/recouerv. launcher' • • •
FAILED <remote： not allowed to flash this partition>
finished, total tine： 0.422s
we need to stop logcat before replacing it
<bootloader> Start partitioning
OKAY [ 0.406s]
finished, total tine： 0.406s
target reported max download size of 536870912 bytes
sending ^/system/bin/logcat'<178KB
OKAY 【0.219s】
writing '/systen/bin/logcat^•••
FAILED <remote： not allowed to flash this partition>
finished, total tine： 0.422s
issue fastboot oem ''stop.partitioning command to start cwn recouerv：
<bootloader> Stop partitioning
OKAY 【0.391s】
finished, total tine： 0.391s
sorry，can't upload img
PS:if you unlock,the device only stay in bootloader,if you want to open and normal use device,you must lock it.
Click to expand...
Click to collapse
If you have got your device unlocked, can you boot into the recovery menu where the option ''Install update from ADB'' is? I can't seem to boot into the recovery menu on the A5CN701? If we can get there, I'm sure we'll figure it out
When running "fastboot flash fastboot droidboot.img" and "fastboot flash boot boot.img" with the files from A5CN507_update.zip i get the IntelAndroid-FBRL-07-24-2015 to run TWRP or CWM.
Drivknuten said:
When running "fastboot flash fastboot droidboot.img" and "fastboot flash boot boot.img" with the files from A5CN507_update.zip i get the IntelAndroid-FBRL-07-24-2015 to run TWRP or CWM.
Click to expand...
Click to collapse
you reboot into the Temporary CWM success?
Xkernels said:
you reboot into the Temporary CWM success?
Click to expand...
Click to collapse
Yes
Drivknuten said:
Yes
Click to expand...
Click to collapse
please, you could post your image?
colorado48 said:
If you have got your device unlocked, can you boot into the recovery menu where the option ''Install update from ADB'' is? I can't seem to boot into the recovery menu on the A5CN701? If we can get there, I'm sure we'll figure it out
Click to expand...
Click to collapse
No,if you unlock device,only stay in bootloader,no matter what your choice，reboot to recovery or power off or anything else. yesterday，i see Root Dell Venue 8 7840 on Android 5.1 Lollipop, which also intel device and run android 5.1.1, it must Flashing Old Firmware and Droidboot,then use the old way to root it, just like the #4 said, but i don't have the N1's old Firmware and Droidboot, so i can't try. now,we just wait #4 upload the img and do what need to do.
---------- Post added at 04:30 AM ---------- Previous post was at 04:25 AM ----------
Drivknuten said:
When running "fastboot flash fastboot droidboot.img" and "fastboot flash boot boot.img" with the files from A5CN507_update.zip i get the IntelAndroid-FBRL-07-24-2015 to run TWRP or CWM.
Click to expand...
Click to collapse
I have the A5CN507_update.zip,could you please tell me how to flash the old droidboot.img and boot.img,
Thx~ plaese
---------- Post added at 04:34 AM ---------- Previous post was at 04:30 AM ----------
p233 said:
please, you could post your image?
Click to expand...
Click to collapse
do you mean you need A5CN507_update.zip?
I have it, it's in a Chinese cloud drive，if you want it ,i can give you the url.
乄Rain丶Man said:
No,if you unlock device,only stay in bootloader,no matter what your choice，reboot to recovery or power off or anything else. yesterday，i see Root Dell Venue 8 7840 on Android 5.1 Lollipop, which also intel device and run android 5.1.1, it must Flashing Old Firmware and Droidboot,then use the old way to root it, just like the #4 said, but i don't have the N1's old Firmware and Droidboot, so i can't try. now,we just wait #4 upload the img and do what need to do.
---------- Post added at 04:30 AM ---------- Previous post was at 04:25 AM ----------
I have the A5CN507_update.zip,could you please tell me how to flash the old droidboot.img and boot.img,
Thx~ plaese
---------- Post added at 04:34 AM ---------- Previous post was at 04:30 AM ----------
do you mean you need A5CN507_update.zip?
I have it, it's in a Chinese cloud drive，if you want it ,i can give you the url.
Click to expand...
Click to collapse
Here is the original old version download link
http://forum.xda-developers.com/nokia-n1/general/nokia-n1-chinese-version-5-1-1-update-t3183529 #3
p233 said:
please, you could post your image?
Click to expand...
Click to collapse
Right now my device is in a bootloop and i have too much work to get anything done with the device right now. So no pic right now.
乄Rain丶Man said:
I have the A5CN507_update.zip,could you please tell me how to flash the old droidboot.img and boot.img,
Thx~ plaese
---------- Post added at 04:34 AM ---------- Previous post was at 04:30 AM ----------
Click to expand...
Click to collapse
1. extract the droidboot.img & boot.img from the A5CN507_update.zip.
2. adb reboot recovery
3. fastboot oem unlock
4. fastboot flash boot boot.img
5. fastboot flash boot boot.img
6. download "IntelAndroid-FBRL-07-24-2015" unzip, run launcher.bat type "ACCEPT" select number 4 or 5 (i have only tested those two). Then option T4 if i remember correctly.
7. Now the device should start receiving the files and start in TWRP or CWM depending on the choices you have made.
Drivknuten said:
Right now my device is in a bootloop and i have too much work to get anything done with the device right now. So no pic right now.
1. extract the droidboot.img & boot.img from the A5CN507_update.zip.
2. adb reboot recovery
3. fastboot oem unlock
4. fastboot flash boot boot.img
5. fastboot flash boot boot.img
6. download "IntelAndroid-FBRL-07-24-2015" unzip, run launcher.bat type "ACCEPT" select number 4 or 5 (i have only tested those two). Then option T4 if i remember correctly.
7. Now the device should start receiving the files and start in TWRP or CWM depending on the choices you have made.
Click to expand...
Click to collapse
2.adb reboot bootloader?
can you provide some pic?
Xkernels said:
2.adb reboot bootloader?
can you provide some pic?
Click to expand...
Click to collapse
Yes that should be adb reboot bootloader.
NO pics possible, my device is in a bootloop and i dont have the time to fix the device until the weekend.
Hi, i seem to have the same problem. ie, N1 stuck in fastboot mode. i have folowed the instructions above, ie;
- successfully unlocked it (fastboot mode reports DEVICE STATE - unlocked)
- extracted boot.img and flashed using fastoboot flash boot boot.img (successful) twice
however, when i run the FBRL script, using option T4 the same problem remains as per the earlier post, ie, it fails at the following point;
writing ^/tmp/recovery.zip^ • • •
FAILED <remote： not allowed to flash this partition>
the script then fails in the same way for recovery.launcher and logcat.
any ideas?
my device now stays in fastboot mode, whether i try chose recovery mode, normal boot etc nothing chances and each time i power cycle it comes back to fastboot mode.
please help. thanks
pdt100 said:
Hi, i seem to have the same problem. ie, N1 stuck in fastboot mode. i have folowed the instructions above, ie;
- successfully unlocked it (fastboot mode reports DEVICE STATE - unlocked)
- extracted boot.img and flashed using fastoboot flash boot boot.img (successful) twice
however, when i run the FBRL script, using option T4 the same problem remains as per the earlier post, ie, it fails at the following point;
writing ^/tmp/recovery.zip^ • • •
FAILED <remote： not allowed to flash this partition>
the script then fails in the same way for recovery.launcher and logcat.
any ideas?
my device now stays in fastboot mode, whether i try chose recovery mode, normal boot etc nothing chances and each time i power cycle it comes back to fastboot mode.
please help. thanks
Click to expand...
Click to collapse
Try "fastboot flash fastboot droidboot.img" with the droidboot.img from the A5CN507_update
Drivknuten said:
Try "fastboot flash fastboot droidboot.img" with the droidboot.img from the A5CN507_update
Click to expand...
Click to collapse
Hi, i was able to submit the command successfully however no change unfortunately. any other ideas? thanks
Drivknuten said:
Right now my device is in a bootloop and i have too much work to get anything done with the device right now. So no pic right now.
1. extract the droidboot.img & boot.img from the A5CN507_update.zip.
2. adb reboot recovery
3. fastboot oem unlock
4. fastboot flash boot boot.img
5. fastboot flash boot boot.img
6. download "IntelAndroid-FBRL-07-24-2015" unzip, run launcher.bat type "ACCEPT" select number 4 or 5 (i have only tested those two). Then option T4 if i remember correctly.
7. Now the device should start receiving the files and start in TWRP or CWM depending on the choices you have made.
Click to expand...
Click to collapse
Then did you root your device successfully？or did you rollback to old version？
乄Rain丶Man said:
Then did you root your device successfully？or did you rollback to old version？
Click to expand...
Click to collapse
Nah i bricked it,
the same thing to me, after i relock bootloader, it jump into a big problem: bootloop, whenever i turn on devices, it just show "android" screen
It's been a while now, can anybody confirm that a root for A5CN701 is on the way?
Drivknuten said:
Nah i bricked it,
Click to expand...
Click to collapse
Oflyt...
Can anyone pls tell me where I can download stock rom for (lenovo) p2 preferable in zip format . And is there any unbricking tutorial .
I want this too...? if anyone can help...
I have found the stock ROM, I bricked my device in the rooting process, and am unable to flash the complete stock image, because the device reports "unable to flash bootloader on unlocked device"
itsjustbilly said:
I have found the stock ROM, I bricked my device in the rooting process, and am unable to flash the complete stock image, because the device reports "unable to flash bootloader on unlocked device"
Click to expand...
Click to collapse
Hi, because you should not flash bootloader.
you can try those 2 solutions:
the fast one, it should work. The flashall command flash every.img files he find in the fastboot directory. So try to remove the bootlader.img and execute the flashall command.
the manual one (longer one):
Put only the recovery.img, boot.img, and the system.img files ( you should have something like 13 , named "systemchunk0/12.img") in your fastboot directory and flash with fastboot ( the command is always the same: fastboot flash recovery recovery.img, fastboot flash boot boot.img, and for every single part of system.img you should flash like "fastboot flash systemchunk0(until 12).img " so you flash flash 13 times the system with avery 13 parts .
Sorry for my english i hope you solved that
itsjustbilly said:
I have found the stock ROM, I bricked my device in the rooting process, and am unable to flash the complete stock image, because the device reports "unable to flash bootloader on unlocked device"
Click to expand...
Click to collapse
Then share it no
I'll post links when I get to my computer, but they're not Cwm flash able zips, they are fast boot files that you flash from DOS on a pc
---------- Post added at 09:39 AM ---------- Previous post was at 09:37 AM ----------
aleleo87 said:
Hi, because you should not flash bootloader.
you can try those 2 solutions:
the fast one, it should work. The flashall command flash every.img files he find in the fastboot directory. So try to remove the bootlader.img and execute the flashall command.
the manual one (longer one):
Put only the recovery.img, boot.img, and the system.img files ( you should have something like 13 , named "systemchunk0/12.img") in your fastboot directory and flash with fastboot ( the command is always the same: fastboot flash recovery recovery.img, fastboot flash boot boot.img, and for every single part of system.img you should flash like "fastboot flash systemchunk0(until 12).img " so you flash flash 13 times the system with avery 13 parts .
Sorry for my english i hope you solved that
Click to expand...
Click to collapse
I did try this, but I still have no signal because the modem file is part of the bootloader, and no modem means no mobile signal
itsjustbilly said:
I'll post links when I get to my computer, but they're not Cwm flash able zips, they are fast boot files that you flash from DOS on a pc
---------- Post added at 09:39 AM ---------- Previous post was at 09:37 AM ----------
I did try this, but I still have no signal because the modem file is part of the bootloader, and no modem means no mobile signal
Click to expand...
Click to collapse
Ah ok i didnt understand that you have this modem issue. I don't kno how to help you...you phone is bricked so you can test few solutions without more risks .
before flash the original recovery , boot and system by fastboot, you can try to install TWRP again and flash only the bootloader from TWRP (should support .zip and .img files). Then you turn the phone in fastboot mode and flash other stuff .
Taken from post 4 of the TWRP page on lenovo P2 forum
smaranramesh said:
Then share it no
Click to expand...
Click to collapse
Factory Images & Systemless Mode
Q: I messed up help me?!
So you screwed up and didn't follow Rule Number One in the IT-Handbook?
Which is: Always create a backup before working on a system?
Download the Factory State Images. Which are all flashable with fastboot: https://goo.gl/JTCwKj
Place the files you want replaced into the "Minimal ADB & Fastboot" installation directory and start it's shell:
If you want to flash back the stock image. Simply run:
Code:
Code:
fastboot flashall
You can also replace all partitions if required.
itsjustbilly said:
Download the Factory State Images. Which are all flashable with fastboot: https://goo.gl/JTCwKj
Click to expand...
Click to collapse
Thanks, I was on P2a42_S038...TMO (T-Mobile, checking OTA update = you are using latest software) flashed this P2a42_S048_ and got OTA info to download latest ROM P2a42_S062_170117_ROW (103MB) :good:
veimus said:
Thanks, I was on P2a42_S038...TMO (T-Mobile, checking OTA update = you are using latest software) flashed this P2a42_S048_ and got OTA info to download latest ROM P2a42_S062_170117_ROW (103MB) :good:
Click to expand...
Click to collapse
Witaj. Mozesz napisać jak wgrałeś czysty soft do Lenovo p2. Tez mam rom z t.mobile a nigdzie nie ma poradnika jak wgrać czysty soft.Pozdrawiam
itsjustbilly said:
Taken from post 4 of the TWRP page on lenovo P2 forum
Factory Images & Systemless Mode
Q: I messed up help me?!
So you screwed up and didn't follow Rule Number One in the IT-Handbook?
Which is: Always create a backup before working on a system?
Download the Factory State Images. Which are all flashable with fastboot: https://goo.gl/JTCwKj
Place the files you want replaced into the "Minimal ADB & Fastboot" installation directory and start it's shell:
If you want to flash back the stock image. Simply run:
Code:
Code:
fastboot flashall
You can also replace all partitions if required.
Click to expand...
Click to collapse
Is there an alternative download link? What is Mega? I want to avoid these third party download utility if I can...
I put the following into a BAT file and placed it into ADB / Fastboot directory:
Code:
fastboot flash partition gpt_both0.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 system systemchunk0.img
fastboot flash system systemchunk1.img
fastboot flash system systemchunk2.img
fastboot flash system systemchunk3.img
fastboot flash system systemchunk4.img
fastboot flash system systemchunk5.img
fastboot flash system systemchunk6.img
fastboot flash system systemchunk7.img
fastboot flash system systemchunk8.img
fastboot flash system systemchunk9.img
fastboot flash system systemchunk10.img
fastboot flash system systemchunk11.img
fastboot flash system systemchunk12.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
pause
Extract all the files listed in the BAT file or simply extract the entire archive to ADB / Fastboot and launch the BAT file.
Does this work?? @Undesirable
the above post
Oh yeah, it unbricked me and put me back to stock so I could get OTA updates for Nougat. You need the archive posted earlier in the thread though.
@Undesirable Nice and elegant solution man! Typing all this stuff was so annoying.
For those who need an alternative download source, I offer this magnet link:
Code:
magnet:?xt=urn:btih:ef05ea3af4da8a0cbb137c10621942f3ae16d46f&dn=P2a42_S048_161111_ROW_fastboot.7z
It's slow unless lots of people help to seed it.
Is it possible to flash this firmware 2a42_S048_161111_ROW_fastboot.7z on the P2c72 with firmware build number: V3.5_1652_5.1342.1_ST_p2c72 ???
I bought this phone 4GB Ram/64GB from china, but I want to put the international firmware on it.
Thanks!
itsjustbilly said:
Taken from post 4 of the TWRP page on lenovo P2 forum
Factory Images & Systemless Mode
Q: I messed up help me?!
So you screwed up and didn't follow Rule Number One in the IT-Handbook?
Which is: Always create a backup before working on a system?
Download the Factory State Images. Which are all flashable with fastboot: https://goo.gl/JTCwKj
Place the files you want replaced into the "Minimal ADB & Fastboot" installation directory and start it's shell:
If you want to flash back the stock image. Simply run:
Code:
Code:
fastboot flashall
You can also replace all partitions if required.
Click to expand...
Click to collapse
how can I replace my data partition? It's not getting formatted due to an encryption error
If fastboot erase userdata doesn't work, then use TWRP to change user data file system to EXT4 then change it back to F2FS again.
Need help...
I flashed back the stock ROM (due to encryption error in custom 7.0 ROM) using fastboot commands, but my SIGNAL WON'T WORK after I started d phone . I've tried reflashing the stock firmware (and also custom ROMs) but my phone won't detect the signal. "About phone" settings show unknown baseband and IMEI... how to get it back
---------- Post added at 08:58 AM ---------- Previous post was at 08:06 AM ----------
I've flashed 'ROW' variant of stock ROM. Is there a different version for Indian variant?
[GUIDE][Perry(Qualcomm)][Windows, macOS & Linux] Flash Stock Firmware and Recovery
*This has only been personally done and tested using a Sprint Qualcomm variant of the Moto E4. I will be working on expanding this guide to cover all specific models of the Perry to avoid potential confusion as there are minor differences, so if anyone wants to pass along their firmware's flashfile.xml into my inbox it would be greatly appreciated.*
Links:
ADB and Fastboot mini .zip for macOS/Windows (Linux users make sure to have android-sdk installed, no need for this download)
All Stock Firmwares (sperry is Sprint firmware, perry is the rest of the Qualcomm models (Thanks to proudlytm) https://mirrors.lolinet.com/firmware/moto//
What you need:
A Windows/macOS/Linux computer
A USB cable
ADB and Fastboot files
Stock Firmware
Your phone
*Disclaimer* Your warranty is now void if you modify your phone. I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Let's get started! First, backup to your computer/Dropbox/etc. all the files you wish to save. This will wipe all data off your phone including root (Not data saved on any cloud services, such as Google, OneDrive, Dropbox, etc.)
Second, boot your phone into the bootloader. This can be done in certain ROM power menus, or with the ADB command "adb reboot bootloader" in Command Prompt/Terminal, or also by turning off your phone and then holding the power and volume down buttons at the same time. After booting into the bootloader, plug your phone into your computer.
The firmware file will look similar to This when extracted
Make sure to look in the firmware folder to see if you need to change a few lines during flashing. If you are unsure, check the flashfile.xml
Next open up Command Prompt if on Windows, Terminal if on macOS/Linux.
Navigate in CMD Prompt/Terminal to the directory you downloaded and extracted the stock firmware. Copy the Fastboot and ADB files into the same directory as the stock firmware files.
For Windows and Linux users, enter the following commands in Command Prompt/Terminal (use sudo before each command in Linux, or use sudo -s beforehand):
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 oem oem.img_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
For macOS, enter the following in Terminal:
./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 oem oem.img_sparsechunk.0
./fastboot flash oem oem.img_sparsechunk.1
./fastboot erase cache
./fastboot erase userdata
./fastboot erase DDR
./fastboot oem fb_mode_clear
./fastboot reboot
Click to expand...
Click to collapse
Hope it helps!
*Reserved*
This is good for the XT1766, but the other variants firmwares have differences. Some have an extra system sparsechunk and an oem.img rather than 2 oem sparsechunks.
</poorly_coded> said:
This is good for the XT1766, but the other variants firmwares have differences. Some have an extra system sparsechunk and an oem.img rather than 2 oem sparsechunks.
Click to expand...
Click to collapse
Thanks for letting me know, I'll add a note
Hello, I have followed all of the directions and when I reboot the device, it says "bad key" then it goes to a screen where it says "erasing" and just keeps on doing this. Any help would be appreciated. Thanks
codyalan said:
Hello, I have followed all of the directions and when I reboot the device, it says "bad key" then it goes to a screen where it says "erasing" and just keeps on doing this. Any help would be appreciated. Thanks
Click to expand...
Click to collapse
Because your bootloader is unlocked.
codyalan said:
Hello, I have followed all of the directions and when I reboot the device, it says "bad key" then it goes to a screen where it says "erasing" and just keeps on doing this. Any help would be appreciated. Thanks
Click to expand...
Click to collapse
I have restored stock on my E4's (I have two, one with a cracked screen) a whole bunch of times, from soft-bricked stock and also from custom ROM's. The key for me was to NOT flash gpt.bin. Leave that step out.
First thing I'd try is re-flashing just the stock boot.img, then see if you can get boot normally... if not...
Try re-flashing stock bootloader and stock recovery, reboot to stock recovery and factory reset. Reboot to bootloader and start stock flashing again (thanks @acejavelin), but don't flash the gpt.bin.
If that fails, one thing that worked for me when I was bootlooped was to completely install a custom ROM and Recovery (I used LineageOS and TWRP), get it up and running, then go ahead and restore the whole business back to stock.
The bad key thing.... it will say that for a few seconds (up to 30 seconds, maybe?) on boot when you restore stock but should get past it. I think it keeps echoing that every time you restart until you've replaced your recovery with a custom one, then the message turns into 'N/A'.
HTH
Ok so I wanted to update this thread. I have the XT1768 and the instructions are a bit different. For the XT1768 there is a Sparsechunk.5 and also for the XT1768 there is only a oem.img. By changing those steps I was able to get unstuck and back in business.
Vicpdx18 said:
Ok so I wanted to update this thread. I have the XT1768 and the instructions are a bit different. For the XT1768 there is a Sparsechunk.5 and also for the XT1768 there is only a oem.img. By changing those steps I was able to get unstuck and back in business.
Click to expand...
Click to collapse
Do you happen to have a copy of the flashfile.xml for your model number you could send to me? I've been wanting to further expand this guide to encompass each individual QComm model
fireball0093 said:
Do you happen to have a copy of the flashfile.xml for your model number you could send to me? I've been wanting to further expand this guide to encompass each individual QComm model
Click to expand...
Click to collapse
For the Xt1768??
codyalan said:
For the Xt1768??
Click to expand...
Click to collapse
Yes, if you have one for it that'd be awesome
fireball0093 said:
Yes, if you have one for it that'd be awesome
Click to expand...
Click to collapse
No Problem,
Would you by chance have a stock rom for the XT1769? Anything I would need to know about restoring it to stock?
---------- Post added at 02:45 AM ---------- Previous post was at 02:43 AM ----------
And not sure if there is a thread for this, if there is could you point me in that direction?Is there a way to create a ROM from a stock phone?
McTRASH692 said:
Would you by chance have a stock rom for the XT1769? Anything I would need to know about restoring it to stock?
---------- Post added at 02:45 AM ---------- Previous post was at 02:43 AM ----------
And not sure if there is a thread for this, if there is could you point me in that direction?Is there a way to create a ROM from a stock phone?
Click to expand...
Click to collapse
https://forum.xda-developers.com/ap...perr-s-kitchen-v3-0-0-0-t3601702/post72168885
How to start building
madbat99 said:
https://forum.xda-developers.com/ap...perr-s-kitchen-v3-0-0-0-t3601702/post72168885
How to start building
Click to expand...
Click to collapse
Thanks heaps, it'd be nice to create stock rom before root just incase the phone bricks.
McTRASH692 said:
Would you by chance have a stock rom for the XT1769? Anything I would need to know about restoring it to stock?
---------- Post added at 02:45 AM ---------- Previous post was at 02:43 AM ----------
And not sure if there is a thread for this, if there is could you point me in that direction?Is there a way to create a ROM from a stock phone?
Click to expand...
Click to collapse
I built the XT1765 Flashable rom in Assaayd's Kitchen. Followed the instructions to a T, and had no problems. Try him out too.
Articul8Madness said:
I built the XT1765 Flashable rom in Assaayd's Kitchen. Followed the instructions to a T, and had no problems. Try him out too.
Click to expand...
Click to collapse
Cheers mate,
I have since found a stock rom for my phone and fixed it completely,
Thank you for helping though,
Hi guys,
Could someone please post the contents of their stock build.prop file? I have corrupted mine and can't find one anywhere,
Device is moto e4 xt1769
Hello Guyz this is my first post to xda . nearly 10 days ago i unlocked bootloader and installed twrp and rooted with magisk but i wanna relock my bootloader since my device was on latest security update so it was very difficult to find the right file for my device . but after lot of search i got the file which i am sharing here with you guyz its free and 100% working for Indian Variant
Things You Need:-
1.Minimal ADB
2.Moto Stock Rom Link:- forum.gsmhosting.com/vbb/12979714-post229.html
Steps To Relock The Bootloader:-
1.Install Minimal ADB
2.Download And Extract Moto Stock Rom to any folder
3.Open The folder where you extracted the stock rom and copy all file to Minimal ADB folder.
4.Now Connect Your Device In Fastboot Mode
5.Open Minimal ADB And Type each command one by one
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 boot boot.img
fastboot oem lock
This Will Restart Your Device..
link doesn't work
nihal28 said:
link doesn't work
Click to expand...
Click to collapse
Working 100% bro
pv.singh26 said:
Working 100% bro
Click to expand...
Click to collapse
Can you please upload a mirror link. Maybe Google Drive, this link is not working for me. Thanks in advance.
nihal28 said:
Can you please upload a mirror link. Maybe Google Drive, this link is not working for me. Thanks in advance.
Click to expand...
Click to collapse
Sure
pv.singh26 said:
Sure
Click to expand...
Click to collapse
http://forum.gsmhosting.com/vbb/12979714-post229.html
try this
pv.singh26 said:
http://forum.gsmhosting.com/vbb/12979714-post229.html
try this
Click to expand...
Click to collapse
Tried downloading from the link, but it says that I don't have permission to download (See screenshot in the attachment). I tried using downloader apps, still doesn't work. Apparently certain indian broadband connections has blocked access to secure motorola servers. Can you please download and re-upload the firmware to Google Drive or Mega. Thanks!
nihal28 said:
Tried downloading from the link, but it says that I don't have permission to download (See screenshot in the attachment). I tried using downloader apps, still doesn't work. Apparently certain indian broadband connections has blocked access to secure motorola servers. Can you please download and re-upload the firmware to Google Drive or Mega. Thanks!
Click to expand...
Click to collapse
Uploading
Link Updated
https://drive.google.com/open?id=165BmLRzGiGF_Veo0AuHgUp6jpn01l9UD :fingers-crossed:
pv.singh26 said:
https://drive.google.com/open?id=165BmLRzGiGF_Veo0AuHgUp6jpn01l9UD :fingers-crossed:
Click to expand...
Click to collapse
Thanks! But this is the not the Indian variant version, you uploaded NPNS25.137-93-4
Please upload the Indian variant one NPNS25.137-92-4
Thanks Again!
nihal28 said:
Thanks! But this is the not the Indian variant version, you uploaded NPNS25.137-93-4
Please upload the Indian variant one NPNS25.137-92-4
Thanks Again!
Click to expand...
Click to collapse
Sorry Wrong File Uploaded
Try This
https://drive.google.com/open?id=1xnlnyR8BmuQMGyYO2EYTELULmNqrHBGg
pv.singh26 said:
Sorry Wrong File Uploaded
Try This
https://drive.google.com/open?id=1xnlnyR8BmuQMGyYO2EYTELULmNqrHBGg
Click to expand...
Click to collapse
Thanks A Lot, It's working!
nihal28 said:
Thanks A Lot, It's working!
Click to expand...
Click to collapse
welcome #Happy2Help
retin config service stopped... help me out. Lost my Sim signal
PsYkOvSkY said:
retin config service stopped... help me out. Lost my Sim signal
Click to expand...
Click to collapse
Show me screenshot
The most important question....
pv.singh26 said:
Hello Guyz this is my first post to xda . nearly 10 days ago i unlocked bootloader and installed twrp and rooted with magisk but i wanna relock my bootloader since my device was on latest security update so it was very difficult to find the right file for my device . but after lot of search i got the file which i am sharing here with you guyz its free and 100% working for Indian Variant
Things You Need:-
1.Minimal ADB
2.Moto Stock Rom Link:- forum.gsmhosting.com/vbb/12979714-post229.html
Steps To Relock The Bootloader:-
1.Install Minimal ADB
2.Download And Extract Moto Stock Rom to any folder
3.Open The folder where you extracted the stock rom and copy all file to Minimal ADB folder.
4.Now Connect Your Device In Fastboot Mode
5.Open Minimal ADB And Type each command one by one
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 boot boot.img
fastboot oem lock
This Will Restart Your Device..[/QUOTE
Is VoLTE working? And I am using pixel experience rom with February security patch, so this firmware work for me?
Click to expand...
Click to collapse
bishal360 said:
pv.singh26 said:
Hello Guyz this is my first post to xda . nearly 10 days ago i unlocked bootloader and installed twrp and rooted with magisk but i wanna relock my bootloader since my device was on latest security update so it was very difficult to find the right file for my device . but after lot of search i got the file which i am sharing here with you guyz its free and 100% working for Indian Variant
Things You Need:-
1.Minimal ADB
2.Moto Stock Rom Link:- forum.gsmhosting.com/vbb/12979714-post229.html
Steps To Relock The Bootloader:-
1.Install Minimal ADB
2.Download And Extract Moto Stock Rom to any folder
3.Open The folder where you extracted the stock rom and copy all file to Minimal ADB folder.
4.Now Connect Your Device In Fastboot Mode
5.Open Minimal ADB And Type each command one by one
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 boot boot.img
fastboot oem lock
This Will Restart Your Device..[/QUOTE
Is VoLTE working? And I am using pixel experience rom with February security patch, so this firmware work for me?
Click to expand...
Click to collapse
First tell before installing custom rom on which month of security update u were !
Click to expand...
Click to collapse
Important question
nihal28 said:
Thanks A Lot, It's working!
Click to expand...
Click to collapse
Is VoLTE working on that stock rom?
---------- Post added at 07:43 PM ---------- Previous post was at 07:38 PM ----------
pv.singh26 said:
bishal360 said:
First tell before installing custom rom on which month of security update u were !
Click to expand...
Click to collapse
I am using Pixel experience rom with February security patch.
Click to expand...
Click to collapse
bishal360 said:
Is VoLTE working on that stock rom?
---------- Post added at 07:43 PM ---------- Previous post was at 07:38 PM ----------
pv.singh26 said:
I am using Pixel experience rom with February security patch.
Click to expand...
Click to collapse
I asked on which security patch of stock rom u were
Click to expand...
Click to collapse
https://cloud.anshumanmishra.me/
Here you can get Indian variant
He extracted everything and zip file is also available
Credits :: anshuman mishra
This morning I've just received the February 2019 security update, I've downloaded it but when the installation starts then it fails. Any idea why this happens?
Somebody has the same issue?
Thanks
Restart, connect charger and start again when above 60%.
Sent from my Mi A2 Lite using Tapatalk
locovibe said:
Restart, connect charger and start again when above 60%.
Click to expand...
Click to collapse
I'm going to try and then I'll let you know.
Thank you very much!
locovibe said:
Restart, connect charger and start again when above 60%.
Sent from my Mi A2 Lite using Tapatalk
Click to expand...
Click to collapse
Not work for me. Since January I have this problem.
Xmata said:
Not work for me. Since January I have this problem.
Click to expand...
Click to collapse
You need to reflash whole rom with miflasher and unlock bootloader.
Some people solved the issue by stopping the download, turning on mobile data and resuming download on mobile data. Don't forget to turn off your WiFi. Try this before flashing the stock rom again and losing all your data.
Check the log and reflash touched partitions
konan82 said:
This morning I've just received the February 2019 security update, I've downloaded it but when the installation starts then it fails. Any idea why this happens?
Somebody has the same issue?
Thanks
Click to expand...
Click to collapse
I had the same even after reflashing (fastboot flash boot boot.img) of boot image: I do use Magisk. I checked what is happening during the failing update by
adb logcat -e update_engine
It will report you where and what is failing.
In my case it was complaining on system checksum:
02-20 10:06:56.298 2188 2188 I update_engine: [0220/100656.298722:INFO:delta_performer.cc(386)] Applying 4096 operations to partition "system"
02-20 10:06:56.409 2188 2188 E update_engine: [0220/100656.408950:ERROR:delta_performer.cc(990)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
So I reflashed system and the update went on well.
Thus you need a computer with adb and fastboot available and stock image from http://en.miui.com/download-354.html of the same version as currently installed.
yakovpol said:
I had the same even after reflashing (fastboot flash boot boot.img) of boot image: I do use Magisk. I checked what is happening during the failing update by
adb logcat | grep update_engine (under Linux)
It will report you where and what is failing.
In my case it was complaining on system checksum:
02-20 10:06:56.298 2188 2188 I update_engine: [0220/100656.298722:INFO:delta_performer.cc(386)] Applying 4096 operations to partition "system"
02-20 10:06:56.409 2188 2188 E update_engine: [0220/100656.408950:ERROR:delta_performer.cc(990)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
So I reflashed system and the update went on well.
Thus you need a computer with adb and fastboot available and stock image from http://en.miui.com/download-354.html of the same version as currently installed.
Click to expand...
Click to collapse
Does this format all data?
wenna.speedy said:
You need to reflash whole rom with miflasher and unlock bootloader.
Click to expand...
Click to collapse
Unlock of bootloader will format all partitions and erase all my data, right?
konan82 said:
Unlock of bootloader will format all partitions and erase all my data, right?
Click to expand...
Click to collapse
reflashing rom lock your bootloader. it will erase your data.
unlocking bootloader via adb erase your data again.
if you have rooted phone you can't use OTA
Finally i have also got feb security update after a long waiting period.
IO13 said:
if you have rooted phone you can't use OTA
Click to expand...
Click to collapse
No my phone isn't rooted. I'm still with locked bootloader
marstonpear said:
Some people solved the issue by stopping the download, turning on mobile data and resuming download on mobile data. Don't forget to turn off your WiFi. Try this before flashing the stock rom again and losing all your data.
Click to expand...
Click to collapse
I've tried to download the entire update without WiFi, using mobile data but nothing to do
IO13 said:
if you have rooted phone you can't use OTA
Click to expand...
Click to collapse
Of course you can,
read this:
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
I followed the instructions and updated my phone.
I had no problems
konan82 said:
Does this format all data?
Click to expand...
Click to collapse
Of course, not.
Reflashing of boot or system partition doesn't touch you data partition.
---------- Post added at 07:21 PM ---------- Previous post was at 07:04 PM ----------
wenna.speedy said:
reflashing rom lock your bootloader. it will erase your data.
unlocking bootloader via adb erase your data again.
Click to expand...
Click to collapse
It depends how you reflash. Some scripts provided with the stock ROM do contain bootloader lock command. Some do erase data. The performing actions follow from script names. If you are not sure, open a script and check the commands inside.
In a case you have a problem with the OTA update, it is unlikely connected to your data partition. So no need in reflashing it/reflashing entire phone and loosing your data.
---------- Post added at 07:31 PM ---------- Previous post was at 07:21 PM ----------
konan82 said:
Unlock of bootloader will format all partitions and erase all my data, right?
Click to expand...
Click to collapse
There is a way to unlock bootloader on this phone without loosing data, see https://forum.xda-developers.com/mi-a2-lite/how-to/guide-how-to-unlock-bootloader-erasing-t3878453
You do not have to unlock bootloader if you want to flash stock ROM images.
Something interesting
I've had done something interesting recently. I'm not a "pro" user, just a normal. I couldn't install the February update through OTA, every time the install failed.
I had download from the new dump post the full rom. (Sorry i'm a new user and i can't url posting)
k4sh44 said:
Here is the zip file with all images.
But as i told already, i wasn't able to boot with fastboot command the boot.img i extracted.
Click to expand...
Click to collapse
I have saved all my datas in my phone, then in the pc unzip all the files what i downloaded and installed the new rom with this method in fastboot mode.
HoangP05 said:
These are image files that are extracted from the payload of the android P OTA:
Warning: You will erase all of your data
Code:
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash rpm_a rpm.img
fastboot flash rpm_b rpm.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
fastboot flash aboot_a aboot.img
fastboot flash aboot_b aboot.img
fastboot flash sbl1_a sbl1.img
fastboot flash sbl1_b sbl1.img
Run the code and then factory reset in recovery, and you will have android P.
Click to expand...
Click to collapse
After that when my phone first rebooted, the most interesting thing was for me, all of my files and apps were in my phone, anything lost, and everything is working. I don't understand why, the new rom works good, and no need restoring.
Only the magisk wasn't good. With the magisk manager I had made a patched boot img file from the full rom files. Then I booted the new patched boot img with fastboot, and then the magisk is perfect too. (but in magisk everything had to reinstalling)
yakovpol said:
I had the same even after reflashing (fastboot flash boot boot.img) of boot image: I do use Magisk. I checked what is happening during the failing update by
adb logcat | grep update_engine (under Linux)
It will report you where and what is failing.
In my case it was complaining on system checksum:
02-20 10:06:56.298 2188 2188 I update_engine: [0220/100656.298722:INFO:delta_performer.cc(386)] Applying 4096 operations to partition "system"
02-20 10:06:56.409 2188 2188 E update_engine: [0220/100656.408950:ERROR:delta_performer.cc(990)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
So I reflashed system and the update went on well.
Thus you need a computer with adb and fastboot available and stock image from http://en.miui.com/download-354.html of the same version as currently installed.
Click to expand...
Click to collapse
Do you think a factory reset (done from the attached image) without flashing the Rom could fix the problem?
I had same problem. Something broke when I used Adaway adblocker.
Unlocking OEM with volume down button didn't work.
And than I downloaded this image http://bigota.d.miui.com/V10.0.3.0....0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz
This is January image.
All other images here are for months before. 10.0.3 is Jan, 10.0.2 is Dec and so on
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Unzipped with 7zip this image
_________________________________________
step 1: install adb and fastboot. ( On windows follow this link https://forum.xda-developers.com/sho....php?t=2588979 )
enable the developer menu on your phone (launch settings, go to system->"about phone" and press repeately on build number)
from the developer options ( launch settings, go to system->"about phone"->developer options ) enable adb and allow bootloader unlock
connect the phone to your PC and give adb permissions to your PC. here I used in cmd
Code:
adb devices
so it would ask for permission from PC
turn off the phone
reboot by pressing power + vol down
_________________________________________
Then with adb in recovery I used:
Code:
fastboot oem unlock
then i repeated step 1, becouse of factory reset with unlocking oem
Code:
fastboot getvar current-slot
if i got A i used A in next string, if B, i used B, where ? is used
Code:
fastboot flash boot_? boot.img
Code:
fastboot flash system_? system.img
Code:
fastboot oem lock
Rebooted phone and
then I updated, and everything worked as it should.
konan82 said:
Do you think a factory reset (done from the attached image) without flashing the Rom could fix the problem?
Click to expand...
Click to collapse
No, it will not: Data partition is not being checked during the update process.
What you can do:
(a) try to find out the reason why the update is failing. It is as simple as starting adb logcat during the update and watching through strings containing update_engine for "error" or "fail" words. Then you will know for sure what is wrong in your phone.
or
(b) reflash your current android version with flash_all_except_storage.bat (if you are under Windows) or flash_all_except_storage.sh (if you are under Linux) script which are part of the whole package http://bigota.d.miui.com/V10.0.3.0....0.PDLMIXM_20190114.0000.00_9.0_e8d8d4a6d0.tgz
Most likely you will be able to download and perform the update after this.
or
(c) wait for a few hours: Xiaomi must grant a download link for February 10.0.4.0 version at http://en.miui.com/download-354.html and then do what is in (b) option above with the newer version. You will get updated system right away. Or at your own risk use a dump of this version that someone has already provided (find the link above in the same forum).
Wish you success.