Related
So, you've unlocked your bootloader and are enjoying some rooted goodness on your phone. You then realise you've got an issue with the phone and forgot to make a backup of your stock ROM! Not to fear, this guide is for you! This will reset the phone back to it's out-the-box state, locked bootloader and all, running the latest ZNH2KAS3P0 build so you can return it for RMA/sell it. This also works to go back to CM13.1.2 from Oxygen OS.
It's recommended that you have adb/fastboot in your System Path. This makes it easier to run commands as you don't always have to 'in' your adb/fastboot folder to run the commands. This guide should help you with this but if you don't want to do this, please copy/extract any files into your adb/fastboot folder before continuing...
1. Download the factory image
Cyanogen released the factory image for the OPO but didn't include any batch files to automate the process. I've repackaged the images into two seperate ZIPs:
ZNH2KAS3P0 16GB: DOWNLOAD
md5: be471f6bfc707f86a0af1eb175ec9aad
ZNH2KAS3P0 64GB: DOWNLOAD
md5: c371bc0cb4ef67999d21f5275c5a587b
*** These ZIPs are not flashable so cannot be flashed via TWRP ***
2. Extract the factory image
Using your favourite file extraction program to extract the package to your Desktop (I use 7-ZIP). *** Remember, if you don't have adb/fastboot in your Path, extract the image into your adb/fastboot folder ***
3. Flash the factory image
Once you've unlocked the bootloader, and rebooted the phone, turn the phone off and back on into fastboot mode and reconnect it to the PC. You can now run the flash-all.bat (Windows) or flash-all.sh (Linux) file. These automate the flashing process. Once complete, the phone will reboot.
*** Some users have had issues using the script in Linux so in these cases extract the ZIP file and flash each IMG individually ***
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img (the filename is the same in both ZIPs so make sure you're using the right one for your device)
fastboot reboot
4. Reset the tamper flag/lock the bootloader
There is a flag/bit on the phone that is triggered when you unlock the bootloader and even relocking it won't change this flag back to standard. Luckily, @Mnt-XDA has a script that you can flash which resets these flags so OP/anyone else is none the wiser! To do this, read and follow THIS thread
5. Reboot the phone
Says it all really - you're done!
EddyOS said:
3. Unlock the bootloader on your OPO
Click to expand...
Click to collapse
And why do you need to unlock the bootloader to flash the factory image ????
RalphLauren said:
And why do you need to unlock the bootloader to flash the factory image ????
Click to expand...
Click to collapse
Because you need access to flash the partitions. If the bootloader is locked you cannot do this. If you're device is still locked from day 1, this guide isn't for you as you're already 100% stock and a factory reset will do this job just fine
EDIT: Actually, it's a bit redundant as why would you need this if you're NOT unlocked! I'll edit the OP
EddyOS said:
Because you need access to flash the partitions. If the bootloader is locked you cannot do this. If you're device is still locked from day 1, this guide isn't for you as you're already 100% stock and a factory reset will do this job just fine
EDIT: Actually, it's a bit redundant as why would you need this if you're NOT unlocked! I'll edit the OP
Click to expand...
Click to collapse
Somehow I was thinking that if the signatures match, flashing the FACTORY image would be allowed without unlocking bootloader, hence the question has arisen.
In a way, you are right that if someone is 100% stock, why to bother flash a stock...
But the reasons could be different, like from pure laboratory experiment to the unable to install OTA (for whatever reason) and need to update OS...
May be worth including this work here by Mnt-XDA
If you are returning to stock for selling / returning etc people may want to reset the tamper flag too.
RalphLauren said:
Somehow I was thinking that if the signatures match, flashing the FACTORY image would be allowed without unlocking bootloader, hence the question has arisen.
In a way, you are right that if someone is 100% stock, why to bother flash a stock...
But the reasons could be different, like from pure laboratory experiment to the unable to install OTA (for whatever reason) and need to update OS...
Click to expand...
Click to collapse
I know what you mean, but it's the same with Nexus devices - you cannot flash the image unless the bootloader is unlocked
indesisiv said:
May be worth including this work here by Mnt-XDA
If you are returning to stock for selling / returning etc people may want to reset the tamper flag too.
Click to expand...
Click to collapse
Yeah was looking to add that in at some point, this is still a work in progress as it were...I'll add it in when I get a chance
EDIT: Added
To make this thread more useful for those who aren't familiar with command line, make sure to tell them to:
1) Download the zip file and extract it onto desktop (what a mess)
2) command line cd desktop
3) Enter each one of those command lines
4) Be happy in the end.
lemonspeakers said:
To make this thread more useful for those who aren't familiar with command line, make sure to tell them to:
1) Download the zip file and extract it onto desktop (what a mess)
2) command line cd desktop
3) Enter each one of those command lines
4) Be happy in the end.
Click to expand...
Click to collapse
To be fair, of someone doesn't know how to do that they really shouldn't be here in the first place!
Sent from my HTC One_M8 using XDA Premium 4 mobile app
This should be a sticky!
banjotrold said:
This should be a sticky!
Click to expand...
Click to collapse
I agree! This definitely should be a sticky.
Sent from my One using XDA Premium 4 mobile app
Which one of these files would be the kernel? I am having wifi issues and am wondering if I would be able to reflash and fix it.
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64g.img (or userdata.img for 16G version)
fastboot oem lock (if you wish to relock the bootloader. If not, ignore this part)
fastboot reboot
boot.img
EddyOS said:
boot.img
Click to expand...
Click to collapse
Thank you. Any reason why I can't just fast boot the boot.img file only (ala carte)? I am on CM11s rooted with TWRP.
I fastboot flashed the boot.img file sucessfully. It did not fix my wifi problem. So, I tried fastboot flashing the NON-HLOS.bin file. It appears to have an error code. Here is the result.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Kevin work>cd desktop/android-sdk-windows/platform-tools
C:\Users\Kevin work\Desktop\android-sdk-windows\platform-tools>fastboot devices
9f66970a fastboot
C:\Users\Kevin work\Desktop\android-sdk-windows\platform-tools>fastboot flash mo
dem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (56241 KB)...
FAILED (data transfer failure (Too many open files in system))
finished. total time: 0.306s
C:\Users\Kevin work\Desktop\android-sdk-windows\platform-tools>fastboot reboot
< waiting for device >
^C
C:\Users\Kevin work\Desktop\android-sdk-windows\platform-tools>
Any idea as to why it failed?
reboot time
I had done all the steps above but stuck at the boot screen now for 10 minutes is it so post to take this long
Xeon_IV said:
I had done all the steps above but stuck at the boot screen now for 10 minutes is it so post to take this long
Click to expand...
Click to collapse
As you can see from my command prompt script mine did not want to reboot. I ended up unplugging the phone and rebooting.
i get this message on mine
C:\>fastboot flash system system.img
sending 'system' (765700 KB)...
FAILED (remote: data too large)
finished. total time: 0.015s
and will not restore any ideas please
---------- Post added at 10:41 AM ---------- Previous post was at 10:35 AM ----------
Xeon_IV said:
i get this message on mine
C:\>fastboot flash system system.img
sending 'system' (765700 KB)...
FAILED (remote: data too large)
finished. total time: 0.015s
and will not restore any ideas please
Click to expand...
Click to collapse
I just want to get back to stock and quit playing with rooting for my customizations now its dead
Xeon_IV said:
i get this message on mine
C:\>fastboot flash system system.img
sending 'system' (765700 KB)...
FAILED (remote: data too large)
finished. total time: 0.015s
and will not restore any ideas please
---------- Post added at 10:41 AM ---------- Previous post was at 10:35 AM ----------
I just want to get back to stock and quit playing with rooting for my customizations now its dead
Click to expand...
Click to collapse
Is your phone the Chinese OPO or the CM OPO?
CM OPO coming from paranois android
I managed to soft brick my Storm with one of the CM13 updates (both normal boot and recovery just resulted in a black flickering screen), it seems others are having similar issues so here are instructions for restoring your phone to the stock image, this fixed the brick for me.
You need fastboot so download and install the Android SDK if not already present: http://developer.android.com/sdk/installing/index.html
Download and uncompress the stock Cyanogen OS fastboot zip: https://cyngn.com/support
Boot your phone into fastboot mode, (plug in USB then hold down vol+ and power until rebooted, keep holding vol+ until in fastboot)
Start a shell/command prompt on your computer to execute the commands below.
THIS WILL WIPE EVERYTHING!!! - THIS IS A COMPLETE STOCK RESTORATION!!!
Execute these fastboot commands from within the extracted stock zip directory:
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
If the cache command gives an error try continuing anyway.
If you want to try to save your user data skip the userdata command, but no guarantees.
Search the other threads on XDA for instructions on booting or flashing custom recoveries, ROMs, root etc.
I've also bricked my Storm with cm13 update in January . I flashed every img using fastboot and it recovered. i skipped the other files and it still works. Good that someone written tutorial for others. I was planning to write it by myself but you were faster
I have made a simple batch script that executes the commands by itself. You need to unzip and place these 2 files into images direction. It should look like this:
View attachment 3656958
Click on picture to make it bigger
then just connect your device in fastboot mode and open the FLASH-ALL.bat file. Press enter. It will flash all the images. IT WILL ONLY WORK IF FILES WILL BE PLACED LIKE ON THE SCREENSHOT!!
I got blinking brick. I can not go into fastboot
@up Don't connect the usb cord. While it's blinking press and hold vol up+ power for 10 seconds, release power button and it should go into fastboot.
If no, let it fully discharge, and then try volup + power
95% of the time flashing system should do the trick. Otherwise the flashall argument should save you a lot of typing.
aciupapa said:
I've also bricked my Storm with cm13 update in January . I flashed every img using fastboot and it recovered. i skipped the other files and it still works. Good that someone written tutorial for others. I was planning to write it by myself but you were faster
Click to expand...
Click to collapse
my storm is dead, i cant get into recovery or download mode....any advice...i did get it rooted and the recovery...i flash the cm 13 kipper and it went dead...red light comes on when charging or usb connection.
miSAKe said:
I managed to soft brick my Storm with one of the CM13 updates (both normal boot and recovery just resulted in a black flickering screen), it seems others are having similar issues so here are instructions for restoring your phone to the stock image, this fixed the brick for me.
You need fastboot so download and install the Android SDK if not already present: http://developer.android.com/sdk/installing/index.html
Download and uncompress the stock Cyanogen OS fastboot zip: https://cyngn.com/support
Boot your phone into fastboot mode, (plug in USB then hold down vol+ and power until rebooted, keep holding vol+ until in fastboot)
Start a shell/command prompt on your computer to execute the commands below.
THIS WILL WIPE EVERYTHING!!! - THIS IS A COMPLETE STOCK RESTORATION!!!
Execute these fastboot commands from within the extracted stock zip directory:
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
If the cache command gives an error try continuing anyway.
If you want to try to save your user data skip the userdata command, but no guarantees.
Search the other threads on XDA for instructions on booting or flashing custom recoveries, ROMs, root etc.
Click to expand...
Click to collapse
Perfect, thanks.
Would have worked FIRST time if I'd read your instructions properly, instead it worked the SECOND time. Important to download "the stock Cyanogen OS fastboot zip" from the Cyngn support page - there are two similar looking files and obviously I picked the wrong one first.
Thanks again.
miSAKe said:
Hello,
As you know, cyngn.com is unavailable. i need kipper files, specially original recovery.img
do you know any alive link(s)? or can you upload/send to me?
thanks very much
Click to expand...
Click to collapse
ftabashir said:
miSAKe said:
Hello,
As you know, cyngn.com is unavailable. i need kipper files, specially original recovery.img
do you know any alive link(s)? or can you upload/send to me?
thanks very much
Click to expand...
Click to collapse
here
https://www.androidfilehost.com/?w=files&flid=59917
Click to expand...
Click to collapse
ghertas said:
ftabashir said:
here
https://www.androidfilehost.com/?w=files&flid=59917
Click to expand...
Click to collapse
thanks. but this is the whole ROM. i downloaded it and couldn't find "recovery.img". how can i find original recovery for kipper (wileyfox storm)?
Click to expand...
Click to collapse
ftabashir said:
ghertas said:
thanks. but this is the whole ROM. i downloaded it and couldn't find "recovery.img". how can i find original recovery for kipper (wileyfox storm)?
Click to expand...
Click to collapse
cm-13.1.2
instal via ADB Fastboot
youtube help you to how instal
recovery.
https://www.androidfilehost.com/?fid=24727376692773052
full rom
https://www.androidfilehost.com/?fid=24727369092694607
Click to expand...
Click to collapse
ghertas said:
ftabashir said:
cm-13.1.2
instal via ADB Fastboot
youtube help you to how instal
recovery.
https://www.androidfilehost.com/?fid=24727376692773052
full rom
https://www.androidfilehost.com/?fid=24727369092694607
Click to expand...
Click to collapse
Thanks. but I downloaded recovery from this link.
Then i tried to run "fastboot flash recovery cm-13.1.2-ZNH2KAS3NA-kipper-boot-debuggable-6c1a30b194.img"
but it said:
OEM locked device can't boot unsigned image. Do you want to continue?
Yes
No
I pressed no and it said:
target reported max download size of 268435456 bytes
sending 'recovery' (20866 KB)...
OKAY [ 0.791s]
writing 'recovery'...
FAILED (remote: Image could brick the device. Flashing canceled.)
finished. total time: 2.129s
I ran the command again and this time I chose Yes and it said:
target reported max download size of 268435456 bytes
sending 'recovery' (20866 KB)...
OKAY [ 0.783s]
writing 'recovery'...
OKAY [ 16.962s]
finished. total time: 17.751s
but as it said, when i try to boot recovery i saw this message: OEM locked device can't boot unsigned image. oem unlock or flash signed boot image.
I need a signed recovery, but i couldn't find such recovery anywher. Please help me
Also when i try to run fastboot oem unlock it says that: FAILED (remote: oem unlock is not allowed)
So the only solution would be installing a signed recovery.
Note: 3day ago i installed a custom recovery without oem unlock. now my device stops at boot animation and i cant boot into android. also i can't boot into recovery because oem is locked and recovery is not signed. I need a signed recovery.
Click to expand...
Click to collapse
miSAKe said:
I managed to soft brick my Storm with one of the CM13 updates (both normal boot and recovery just resulted in a black flickering screen), it seems others are having similar issues so here are instructions for restoring your phone to the stock image, this fixed the brick for me.
You need fastboot so download and install the Android SDK if not already present: http://developer.android.com/sdk/installing/index.html
Download and uncompress the stock Cyanogen OS fastboot zip: https://cyngn.com/support
Boot your phone into fastboot mode, (plug in USB then hold down vol+ and power until rebooted, keep holding vol+ until in fastboot)
Start a shell/command prompt on your computer to execute the commands below.
THIS WILL WIPE EVERYTHING!!! - THIS IS A COMPLETE STOCK RESTORATION!!!
Execute these fastboot commands from within the extracted stock zip directory:
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
If the cache command gives an error try continuing anyway.
If you want to try to save your user data skip the userdata command, but no guarantees.
Search the other threads on XDA for instructions on booting or flashing custom recoveries, ROMs, root etc.
Click to expand...
Click to collapse
How did you enter fastboot without enabling usb debugging/developer option?
Hello,
So I decided to unlock and root my Pure today. Originally I was going to flash Lineage, but I later decided not to. Anyway, I was following the instructions here.
So I unlocked and installed TWRP succesfully. Then I decided to root. And that's where I screwed up.
Following these instructions, I now have a phone that won't boot past the "M" logo. Apparently my mistake was not using the current SU version.
I have been Googling for an hour now, but almost every solution I've come across has involved plugging the phone into the computer. My issue is that my computer isn't recognizing the phone when I plug it in, so my knowledge of how to fix this is limited (and my expertise in this topic was minimal to begin with...). I can get to recovery mode, and have tried a factory reset. No dice. I also put the latest official factory image from Motorola on the SD card, but when I went to install it, it wouldn't show up.
As you can tell I am quite stuck here. I haven't tried to root a phone since my Incredible back in the day. Any help would be greatly appreciated.
Thanks!
Did you use TWRP to make a nandroid backup before attempting to root? If so, just restore it.
If not, you're going to have to either fastboot flash it back to stock. More info in the firmware thread.
Or you could give a custom rom, or this TWRP flashable stock rom a try. I've never used the TWRP flashable stock rom, but it might be an easy way out of your predicament if you aren't comfortable and familiar with fastboot and want to stay stock.
For future rooting attempts of the stock rom I'd recommend Magisk. It always works systemless, so there's no need to force it to install systemless like SuperSU. Just flash the zip in recovery and install the Magisk manager from the Play Store and you're rooted. No more soft bricks.
jason2678 said:
Did you use TWRP to make a nandroid backup before attempting to root? If so, just restore it.
If not, you're going to have to either fastboot flash it back to stock. More info in the firmware thread.
Or you could give a custom rom, or this TWRP flashable stock rom a try. I've never used the TWRP flashable stock rom, but it might be an easy way out of your predicament if you aren't comfortable and familiar with fastboot and want to stay stock.
For future rooting attempts of the stock rom I'd recommend Magisk. It always works systemless, so there's no need to force it to install systemless like SuperSU. Just flash the zip in recovery and install the Magisk manager from the Play Store and you're rooted. No more soft bricks.
Click to expand...
Click to collapse
Ok, first, thanks for the response.
I think somehow I didn't actually install TWRP. Not sure how.
I followed that thread link and tried everything, but to no avail. Maybe I was doing it wrong? I did this:
- Downloaded everything under "6.0 MPH24.49-18 FIRMWARE"
- Put it on my SD card
- Booted into recovery
- Selected Install from SD Card
And there was nothing listed. I tried the same with the "6.0 MPH24.49-18-3 FIRMWARE".
I also did the "AutoFlashFirmwareScript", but I'm assuming that didn't work since I can't turn on USB Debugging. Is there a possibility I somehow wiped the entire OS and there isn't anything to boot into?
bootloopohgod said:
Ok, first, thanks for the response.
I think somehow I didn't actually install TWRP. Not sure how.
I followed that thread link and tried everything, but to no avail. Maybe I was doing it wrong? I did this:
- Downloaded everything under "6.0 MPH24.49-18 FIRMWARE"
- Put it on my SD card
- Booted into recovery
- Selected Install from SD Card
And there was nothing listed. I tried the same with the "6.0 MPH24.49-18-3 FIRMWARE".
I also did the "AutoFlashFirmwareScript", but I'm assuming that didn't work since I can't turn on USB Debugging. Is there a possibility I somehow wiped the entire OS and there isn't anything to boot into?
Click to expand...
Click to collapse
okay so you are wrong here..
firmware needs to be flashed via fastboot they are not available in flashable zips they are .xml file.. you need to follow the instructions given here
https://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
or if you want latest firmware of any version of style or pure
download from here
https://firmware.center/firmware/Motorola/
and follow the same instructions given in the first link
hope this helps
Sagar_1401 said:
okay so you are wrong here..
firmware needs to be flashed via fastboot they are not available in flashable zips they are .xml file.. you need to follow the instructions given here
https://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
or if you want latest firmware of any version of style or pure
download from here
https://firmware.center/firmware/Motorola/
and follow the same instructions given in the first link
hope this helps
Click to expand...
Click to collapse
This definitely seems helpful, but when I tried it gave me a bunch of Failures.
For "fastboot flash partition gpt.bin":
Code:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.382s
And then a Failure for every command from "fastboot flash boot boot.img" to "fastboot flash system system.img_sparsechunk.8" (the build I used doesn't have sparsechunk 9 or else I'd assume that would have been a failure as well). It is encouraging to know I can at least somewhat communicate with the phone, for some reason yesterday I couldn't even do that.
bootloopohgod said:
This definitely seems helpful, but when I tried it gave me a bunch of Failures.
For "fastboot flash partition gpt.bin":
Code:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.382s
And then a Failure for every command from "fastboot flash boot boot.img" to "fastboot flash system system.img_sparsechunk.8" (the build I used doesn't have sparsechunk 9 or else I'd assume that would have been a failure as well). It is encouraging to know I can at least somewhat communicate with the phone, for some reason yesterday I couldn't even do that.
Click to expand...
Click to collapse
ignore that partition error
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
fastboot reboot
make sure
while flashing NON-HLOS.bin you might get error
dont worry
when you reach that step do type it again when you see that error and it'll successful flash the NON-HLOS.bin which is your main step for your modem
im sure this will 100% work
edit: all the files have different no of system system.img_sparsechunk
if you are flashin sept patch it should have 8 i assume but if you just type system system.img_sparsechunk.9 it'll say file not found u won't encounter any error by that
Hi, I'm having issues with booting recovery.
I've successfully rooted my phone before, but because of an OTA update, had to revert back to the flashing of recovery (TWRP), booting recovery, then flashing Magisk steps.
So, I have my recovery.img file which I renamed to "twrp.img" (no double twrp.img.img file extensions). It looks like I'm able to flash it successfully, giving something that looks like this when I run "fastboot flash recovery twrp.img" (in the directory where the recovery image is located):
target reported max download size of 536870912 bytes
sending 'recovery' (24496 KB)...
OKAY [ 0.530s]
writing 'recovery'...
OKAY [ 0.156s]
finished. total time: 0.691s
Click to expand...
Click to collapse
However, after I try the "fastboot boot recovery twrp.img" command, it gives me:
cannot load 'recovery': No such file or directory
Click to expand...
Click to collapse
When I try to restart into recovery, it just boots into stock recovery, and not TWRP.
Any help would be super useful, I'm really not able to figure this out. I've done a lot of research, even going through disabling/uninstalling the Kedacom USB drivers and turning airplane mode on and installing adb/fastboot drivers from XDA.
Thanks!
Why are you flashing two recovery images? Maybe I'm missing something but I'm not understanding what it is that you are doing.
Your problems could also be related to whatever version of TWRP you are flashing on whatever OS you are running. Maybe there is a compatibility issue between the two but without more specific information it's pretty much impossible to say.
I'm just flashing one recovery.img file (TWRP), which doesn't display any errors in the flashing in command line. But when I try to boot it in command line, it gives me the above error that the recovery doesn't exist. When I try to boot it by advanced restart -> recovery, it just takes me to the stock recovery.
I'm on Oxygen 4.5.14. Let me know if there's anything else I can provide.
Rename your Recovery file to twrp.img
Seems like you forgot to do that according to your command
k0byf1ch said:
Hi, I'm having issues with booting recovery.
I've successfully rooted my phone before, but because of an OTA update, had to revert back to the flashing of recovery (TWRP), booting recovery, then flashing Magisk steps.
So, I have my recovery.img file which I renamed to "twrp.img" (no double twrp.img.img file extensions). It looks like I'm able to flash it successfully, giving something that looks like this when I run "fastboot flash recovery twrp.img" (in the directory where the recovery image is located):
However, after I try the "fastboot boot recovery twrp.img" command, it gives me:
When I try to restart into recovery, it just boots into stock recovery, and not TWRP.
Any help would be super useful, I'm really not able to figure this out. I've done a lot of research, even going through disabling/uninstalling the Kedacom USB drivers and turning airplane mode on and installing adb/fastboot drivers from XDA.
Thanks!
Click to expand...
Click to collapse
Edit:Sorry I kind of Missed that its already Done
Please Ignore My Upper Message
Possible another Solution:
Download Another Recovery File and Do the Same again
I've renamed the file since, and it still has been a problem.
Both recovery.img and twrp.img and the original name of the file "twrp-3.1.1-cheeseburger-84-20170820-194433-CEST.img" wouldn't take.
The file name is irrelevant. But it seems like your command to boot into recovery is the problem: fastboot boot only takes one argument (the file to boot into) whereas the fastboot flash command takes two arguments (partition and file to flash).
fastboot flash recovery twrp.img
fastboot boot twrp.img
Okay, I'll give that a shot but I'm still booting into the stock recovery when I advance restart into recovery.
I have flashed so many custom roms on this device and usually never encountered a problem, but just a few days ago,
I flashed a Android 8.1 ROM, with Gapps , Shield Blobs and TOS.
After this my device was stuck in a bootloop and it could never boot into recovery, the Volume + and Power button never really respond,
the only mode working was Fastboot,
But funnily enough, when i entered fastboot, i tried flashing all versions of the Stock Fastboot ROMs, but it never booted into the system, it just stayed in the MI logo screen and continued to either boot again into the MI logo or again to the Fastboot screen.
I tried using all versions of the MI flash tool, thinking maybe it was something wrong with the tool, and since im on Windows 10, tried multiple compatibility modes, such as Windows 7 and 8 but nothing worked.
I thought i had screwed up the partitions in the system since i merged the system 1 and 2 partitions for installing custom roms, but it was not possible to flash a zip file using only fastboot,
Since i was not able to enter recovery i couldnt use ADB.
But today morning,
I was looking at some of the documentations for the Nvidia SOC and found some very valuable instructions, will post them down below,
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra<version>.dtb
The stock ROMs do NOT contain the stock blob file which is needed to actually flash and boot the ROM properly,
So, i downloaded the stock blob file for MI Pad 1 mocha and tried doing it manually by using CMD in fastboot,
Below are the steps which i did,
Firstly, Erase the existing partitions using these commands(order is not important)
fastboot erase boot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot erase bootloader
fastboot erase recovery
fastboot erase tos
Then installing the fastboot rom which you can get online, download them and extract them, then go to the image folder inside the ROM folder, and you'll find all the files necessary for the commands below EXCEPT the stock blobs, for which ill add a link here or attach the file.
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash tos tos.img
fastboot flash dtb tegra124-mocha.dtb
For the last command, just copy and paste the name of dtb file which you're going to flash and continue normally.
Of all the steps only the 5th and 7th step are really important, which is highlighted.
After finishing flashing all these commands ONE BY ONE ,
Boot your device back into fastboot mode and use the available MI flash tool and continue to flash the fastboot rom again,
After all these steps, if you're lucky, you can successfully boot into your new stock rom,
If you're still experiencing boot loops, as a last resort you can try to short your device using the memory card slot, but be careful you have to disassemble the battery first.
I'll attach all the sources at the end of this thread.
Good luck!
Sources:-
https://docs.nvidia.com/gameworks/content/devices/shield_flashing_from_image.htm
https://forum.xda-developers.com/shield-tablet/general/adb-fastboot-shield-recovery-image-t2860340
https://forum.xda-developers.com/mi-pad/how-to/tut-how-to-unbrick-revive-totally-t3417604
https://forum.xda-developers.com/mi-pad/how-to/mi-pad-1-hard-brick-revival-how-t3878311
Hi, it feels so good to see that I'm not the only one suffering (suffered in your case) with this problem. I just have a doubt.
We are erasing bootloader in your steps but while again installing all these files we are neither installing any bootloader img nor it is there in the rom package. Now I that that if your bootloader is gone, your device is as good as a brick, for real. Could you shed some light on this?
Awaiting your reply.
Thanks and regards.
EDIT:
I think my tab just died, while flashing tos from minimal adb and fastboot, I noticed the screen was pulsing, fastboot logo was still there but like flickering and fastboot message came back that it failed to write. I disconnected usbcable and reconnected and tab isnt detected, fastboot says target didnt report max download size and windows doesnt see the tab.
I switched off and tried to reboot to fastboot but the tab wont respond anymore. Screen doesnt come on.
What to do?
It is working
The guide was working, although flashing the dtb file wasn't succesfull its working. Later I will update to Custom ROM.
Thanks a lot, got my Pado back to life. As Guy.brush said dtb fails but it still works.
Failed Flashing DTB
I got this error flashing dtb:
C:\adb>fastboot flash dtb C:\adb\mipad\tegra124-mocha.dtb
target reported max download size of 645922816 bytes
sending 'dtb' (82 KB)...
OKAY [ 0.016s]
writing 'dtb'...
FAILED (remote: (BadParameter))
finished. total time: 0.031s
---------- Post added at 03:31 PM ---------- Previous post was at 03:01 PM ----------
C4DXYZ-XDA said:
I got this error flashing dtb:
C:\adb>fastboot flash dtb C:\adb\mipad\tegra124-mocha.dtb
target reported max download size of 645922816 bytes
sending 'dtb' (82 KB)...
OKAY [ 0.016s]
writing 'dtb'...
FAILED (remote: (BadParameter))
finished. total time: 0.031s
Click to expand...
Click to collapse
but it still work.. my mipad is back to life..
adi4u4882 said:
I have flashed so many custom roms on this device and usually never encountered a problem, but just a few days ago,
I flashed a Android 8.1 ROM, with Gapps , Shield Blobs and TOS.
After this my device was stuck in a bootloop and it could never boot into recovery, the Volume + and Power button never really respond,
the only mode working was Fastboot,
But funnily enough, when i entered fastboot, i tried flashing all versions of the Stock Fastboot ROMs, but it never booted into the system, it just stayed in the MI logo screen and continued to either boot again into the MI logo or again to the Fastboot screen.
I tried using all versions of the MI flash tool, thinking maybe it was something wrong with the tool, and since im on Windows 10, tried multiple compatibility modes, such as Windows 7 and 8 but nothing worked.
I thought i had screwed up the partitions in the system since i merged the system 1 and 2 partitions for installing custom roms, but it was not possible to flash a zip file using only fastboot,
Since i was not able to enter recovery i couldnt use ADB.
But today morning,
I was looking at some of the documentations for the Nvidia SOC and found some very valuable instructions, will post them down below,
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra<version>.dtb
The stock ROMs do NOT contain the stock blob file which is needed to actually flash and boot the ROM properly,
So, i downloaded the stock blob file for MI Pad 1 mocha and tried doing it manually by using CMD in fastboot,
Below are the steps which i did,
Firstly, Erase the existing partitions using these commands(order is not important)
fastboot erase boot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot erase bootloader
fastboot erase recovery
fastboot erase tos
Then installing the fastboot rom which you can get online, download them and extract them, then go to the image folder inside the ROM folder, and you'll find all the files necessary for the commands below EXCEPT the stock blobs, for which ill add a link here or attach the file.
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash tos tos.img
fastboot flash dtb tegra124-mocha.dtb
For the last command, just copy and paste the name of dtb file which you're going to flash and continue normally.
Of all the steps only the 5th and 7th step are really important, which is highlighted.
After finishing flashing all these commands ONE BY ONE ,
Boot your device back into fastboot mode and use the available MI flash tool and continue to flash the fastboot rom again,
After all these steps, if you're lucky, you can successfully boot into your new stock rom,
If you're still experiencing boot loops, as a last resort you can try to short your device using the memory card slot, but be careful you have to disassemble the battery first.
I'll attach all the sources at the end of this thread.
Good luck!
Sources:-
https://docs.nvidia.com/gameworks/content/devices/shield_flashing_from_image.htm
https://forum.xda-developers.com/shield-tablet/general/adb-fastboot-shield-recovery-image-t2860340
https://forum.xda-developers.com/mi-pad/how-to/tut-how-to-unbrick-revive-totally-t3417604
https://forum.xda-developers.com/mi-pad/how-to/mi-pad-1-hard-brick-revival-how-t3878311
Click to expand...
Click to collapse
Thanks, where could I find rom to get dtb file? Thanks
Wow it is working
Even i got the same error
"sending 'dtb' (82 KB)...
OKAY [ 0.016s]
writing 'dtb'...
FAILED (remote: (BadParameter))"
then I did flash ,using Mi flash tool..
Now it is working fine..
after (2015-2019)so many years.. Today 31st May 2020 device came back to normal..
I tried many methods.. Nothing works..
Thank you so much for this post..
I went to three different MI service center..and many other mobile repair shop..no one did..
You did big help..
Thank you so much..
I followed all the instructions one by one. The process was completed successfully too, except dtb (which error many others have faced). Rebooted. Then flashed the same ROM using MiFlash tool. BUT still my tab is stuck in mi logo. I don't know what to do. Is there anything I am missing during following the instructions? I can still enter into fastboot mode and also recovery; so the tab isn't completely hardbricked though. Please help. I am just stuck in the mi logo.
In my case even it doesn't go to fastboot mode neither recovery. Stuck in mi logo. Please someone help me
While flashing I found that recovery.img and tos.img exists in both the fastboot file and the blobs file. Which one should I use? I tried using the fastboot files but it didn't work out and i'm stuck on the mi logo.
Also while flashing via miflash, got an error :
error:Not catch checkpoint (\$fastboot -s .* lock),flash is not done.
which I found out is to be ignored and the flash will still work. It is just a checkpoint fail because the device wasn't locked during the flashing process. Could it be the issue ?
My Mipad is bricked now,,so I'm working on short mydevice using the memory card slot,.. its kind of tricky to get it back to life again,,hihihihhi,,
Just registered an account to say thank you. I tried flashing original fastboot rom thousands times but no luck. Your guide helped.
{
"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"
}
I'm trying like this,, and it worked..
It worked for me.
The "tegra124-mocha.dtb" file can be found within the fastboot rom package that I downloaded named "Xiaomi_Mi_Pad_V8.1.2.0.KXFCNDI_20161128_China_4.4_XFT"
via:
Xiaomi Mi Pad Stock ROM Firmware (Fastboot Flash File)
Download the official Xiaomi Mi Pad Stock ROM Firmware (Flash File) for your Xiaomi Smartphone. We also provide Stock ROM for other Xiaomi devices.
xiaomistockrom.com
Intend to move onto custom rom LOS15 or later...
Wish me luck, read that camera is broken in LOS15-16 for mocha
Now to reinstall TWRP
via:
Download twrp-3.4.0-0-mocha.img
Download page for twrp-3.4.0-0-mocha.img
dl.twrp.me
Then re-merge the partitions.
"Repartition_MI_Pad_1_2GB_zardMi3.zip"
via:
Repartition_MI_Pad_1_2GB_zardMi3.zip | by ANHTUAN9791 for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Miui 8 : How To?
Hi, On the recent post, miui 8 is available for the mipad. But before update we need to merge the both partitions. "For Xiaomi MiPAD 1 is required to merge both system partitions" We are invite to follow à link : http://en.miui.com/thread-118294-1-1.html Ok.....but I just understand...
xiaomi.eu
[GUIDE][HOW TO]Flash TWRP And Merge Partitions on Mi Pad 1 (Mocha)
Screenshots will be added later on /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have...
forum.xda-developers.com
LineageOS 16.0 | 19.04.2020 | Shield blobs
LineageOS 16.0 Requirements: 1) active system1 2) merged system partition 3) BRAIN, READING SKILL and presence of basic knowledge about firmware (in the absence need learn to independently) Instruction 1) download TosForPSCI-0.1.zip...
forum.xda-developers.com
This thread & the blob saved my device. Thanks a lot.
Thank you sooo much! It helped to revive my Mi Pad!