Stuck on installing ROM - Huawei MediaPad M2

So as a fan of Android and ICT literate I decided to root, new recovery and install a new ROM to get my favourite MediaPad M2 8.0 LTE as stock Android as possible.
I unlocked the bootloader, installed TWRP successfully and it works.
However on my haste I messed up my android ROM install. No problem: got TWRP, just find a new stock ROM to install except unlike my phone it seems it's not that simple with this tablet?
I'm picking up that you cannot install a true stock Huawei ROM without losing TWRP. Not great but okay.
Downloaded a stock ROM, used Huawei extracter to pull the recovery IMG and flashed via TWRP.
Booted up and it goes straight to Huawei's own fastboot screen and Huawei's own software won't recover.
I've flashed TWRP back again for now.
So I basically need a ROM I can install from fresh which will install via TWRP.
Am I right that the official Roms are out due to the recovery requirements?
Have I missed something obvious to get this tablet alive again?

TheOnlyPaulV said:
So as a fan of Android and ICT literate I decided to root, new recovery and install a new ROM to get my favourite MediaPad M2 8.0 LTE as stock Android as possible.
I unlocked the bootloader, installed TWRP successfully and it works.
However on my haste I messed up my android ROM install. No problem: got TWRP, just find a new stock ROM to install except unlike my phone it seems it's not that simple with this tablet?
I'm picking up that you cannot install a true stock Huawei ROM without losing TWRP. Not great but okay.
Downloaded a stock ROM, used Huawei extracter to pull the recovery IMG and flashed via TWRP.
Booted up and it goes straight to Huawei's own fastboot screen and Huawei's own software won't recover.
I've flashed TWRP back again for now.
So I basically need a ROM I can install from fresh which will install via TWRP.
Am I right that the official Roms are out due to the recovery requirements?
Have I missed something obvious to get this tablet alive again?
Click to expand...
Click to collapse
First of all, I'm not sure whether flashing the official Huawei partition images will work if they are flashed from TWRP (I've never tried it). However, I do know that it works without problems when flashed in fastboot mode. Secondly, if TWRP was flashed as the recovery and you chose the TWRP inbuilt root option, it would have replaced your BOOT partition as well. So to repair this, you'd have to flash the official Huawei BOOT partition as well. BTW, I was in a similar state (bootloop/no boot) a couple of times (see my post here) and both times was able to recover by flashing the official Huawei BOOT.img and RECOVERY.img partitions to my device.
So, to get your device back into a decent shape, try flashing the BOOT.img as well as the RECOVERY.img from the official Huawei ROM for your device, performing the flashing in fastboot mode. I have written a guide which details extracting and flashing official Huawei partitions. Best of luck

It is obvious that I am missing something very simle here and I'm very interested in finding out what it is I'm doing wrong
So I have a TWRP booting tablet.
I downloaded the latest image from the roms thread on this forum which gives me a zip file called "M2-801LC100B205.zip".
I extract this and open it in Huawei extracter tool.
I extract the BOOT, RECOVERY, SYSTEM and CUST to separate .img files.
I flash all 4, one after the other using the commands listed in your guide:
fastboot flash boot BOOT.img
fastboot flash recovery RECOVERY.img
fastboot flash system SYSTEM.img
fastboot flash cust CUST.img
They all flash okay (it seems), an exmaple of the flash is:
C:\platform-tools>fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (454239 KB)...
OKAY [ 17.471s]
writing 'system' 1/6...
OKAY [ 5.909s]
sending sparse 'system' 2/6 (449072 KB)...
OKAY [ 16.927s]
writing 'system' 2/6...
OKAY [ 5.788s]
sending sparse 'system' 3/6 (459356 KB)...
OKAY [ 17.035s]
writing 'system' 3/6...
OKAY [ 5.894s]
sending sparse 'system' 4/6 (442527 KB)...
OKAY [ 17.781s]
writing 'system' 4/6...
OKAY [ 5.713s]
sending sparse 'system' 5/6 (447342 KB)...
OKAY [ 20.828s]
writing 'system' 5/6...
OKAY [ 5.736s]
sending sparse 'system' 6/6 (67700 KB)...
OKAY [ 2.524s]
writing 'system' 6/6...
OKAY [ 0.864s]
finished. total time: 122.498s
C:\platform-tools>
But still I have a tablet that is stuck on the boot screen. I can still get back to the fastboot recovery so I can still flash but I seem to be missing WHAT to flash?
Surely there must be a complete .img file some where I can flash in flash boot which will just get the thing back and working?
It seems like I'm flashing lots of small simple things when I just want a complete image from some where to flash?
I cant flash the downloaded zip files via fast boot it seems?
Does one exist of have I missed some thing?
Update:
I downloaded a ZIP file of a full rom as detailed above, installed TWRP and tried to flash the zip: it fails stating it could not mount the system partition and radio firmware does not exist. I assume this is because the file downloaded is an update and not a complete rom?
I used TWRP to format and resize the system partition and it reports 0mb in size and fails.
I really think I just need a plain original simple complete rom to flash, in a ZIP format for TWRP: the updates all seem to assume its being flashed onto a working system as an update and I don't have a full base install.
Surely this base simple rom must exist some where?

Any one?
Next step for this tablet is to return it unfortunately as I'm totally beat
Does any one have a TWRP backup I can flash for a media pad m2 lte 8.0?

TheOnlyPaulV said:
Any one?
Next step for this tablet is to return it unfortunately as I'm totally beat
Does any one have a TWRP backup I can flash for a media pad m2 lte 8.0?
Click to expand...
Click to collapse
Hmmm... I expected you to only flash the boot and recovery images as mentioned in my previous reply (and not other partition images, the example text in my guide was just that - an example) from your original ROM version, not from a downloaded ROM version. If your original ROM was a lollipop ROM and not marshmallow, B205 is a mm ROM and would require a full ROM flash, and in this case a bits-and-pieces flash would not work, and cause a non-booting device. A bits-and-pieces flash especially of any device partition other than BOOT and RECOVERY should ideally be done only with the ROM version which is currently installed and (previously known to be) working.
If you can connect the phone to your computer long enough to transfer over the full ROM image to the device, you should be able to flash that using the original Huawei recovery. The instructions are present on the forum thread where you found the ROM. Alternatively, if you know what version the original ROM was on your device, you can flash its SYSTEM and CUST over.

Yes, that's what I would like to do and I can do that, fast boot still works, but it's where do I get a FULL ROM from? Everything on this forum I have found is an update and relies on another working ROM to be present.
Where do I get the full ROM from, do we know the name of one which is not an upgrade ROM?
It's this full ROM I've been looking for to no avail

Please confirm your device model and I'll try to find a full ROM image download (Marshmallow) for you.
EDIT: by full I mean a ROM which is a complete image (about 2-3GB) instead of a partial OTA update. Also, I'm not certain that you can flash a full Huawei official ROM image from fastboot; it requires booting into the recovery. AFAIK Booting into the recovery does not need a working ROM system partition.

Thanks for this! So as I cannot get into android, I've looked on the physical back of the device and it says it's a m2-801L. I purchased a Huawei MediaPad 8.0 LTE. I can flash the Huawei standard recovery and boot fine, I can flash from that and have tried to flash parts of Roms from that so I assume a full ROM is a similar process?
Also would a full TWRP backup also not work?
Thanks again for all your help however, I'm happy to buy you a beer (or non alcoholic beverage of your choice!l

Sorry to bug but have you, or any one else, had any luck in finding a full rom?
Any one have a twrp backup of a basic fulll booting rom I could try?
I do appreciate all the help!

TheOnlyPaulV said:
Thanks for this! So as I cannot get into android, I've looked on the physical back of the device and it says it's a m2-801L. I purchased a Huawei MediaPad 8.0 LTE. I can flash the Huawei standard recovery and boot fine, I can flash from that and have tried to flash parts of Roms from that so I assume a full ROM is a similar process?
Also would a full TWRP backup also not work?
Click to expand...
Click to collapse
Sorry for the delayed reply, I've been pretty ill for the last few days.
Here are links to what I'm pretty certain are the OEM Lollipop full ROMs for the 801L. All those links are 1.4GB zipped, which means that they should unzip to about 2.5-3GB, which indicates that it is a full ROM:
801L B006 on Huawei Malaysian support site: http://download-c.huawei.com/download/downloadCenter?downloadId=57706&version=181649&siteCode=my
801L B007 on Huawei Malaysian support site: http://download-c.huawei.com/download/downloadCenter?downloadId=71503&version=254039&siteCode=my
801L B003 on Huawei Russian support site (): http://download-c.huawei.com/download/downloadCenter?downloadId=71523&version=254048&siteCode=ru
You'll need to get the unzipped ROM folder onto your external SD card somehow, to be able to flash it with the Huawei recovery.
Here are some steps you can follow:
Part 1: Download ROM, extract it and then copy extracted ROM directory to sdcard on phone
In this part, we will download the ROM, extract it, and transfer the extracted ROM to your M2 using TWRP and ADB. Make sure that you have the Mediapad drivers installed, and adb and fastboot installed and available.
If you're on Windows and need the ADB and fastboot binaries, you can install the "15-second ADB installer" found in this thread.
On Linux, just install the Android Command Line tools from Google.
For the phone drivers, just install HiSuite from Huawei - this will install the Mediapad device drivers. You can then uninstall HiSuite - the drivers will still continue to remain installed even if HiSuite is uninstalled, and this way you won't clutter up your computer with the useless HiSuite.
Now download one of the ROMs listed above (I suggest starting with B007. If that doesn't work, try B003 and then B006).
Unzip the downloaded ROM onto some location on your computer's hard drive. Let's say that on Windows, you unzip it to D:\MYROM
In D:\MYROM, you should find a directory called dload
Make sure that you have TWRP as the recovery on the phone. Flash TWRP onto the phone if you need to (since you already know how to do this, I won't go into more detail).
Boot into the TWRP recovery on the phone (since you already know how to do this, I won't go into more detail).
In TWRP, make sure that MTP mode is off. To do this, in the TWRP main menu, press "Mount". In the "Mount" screen, check whether the second (right-hand-side) button on the bottom reads "Enable MTP". If it says "Enable MTP", then you do not need to do anything else here, go back to the main TWRP screen. If the button says "Disable MTP", press it so that the button now reads as "Enable MTP". Setting MTP mode off will ensure that you can connect via ADB to your phone.
Now open a terminal/command-prompt window on your computer (Run->"cmd" or search for "cmd" on Windows).
In the terminal window, navigate to the directory where the unzipped ROM is present. On Windows, using the above example ROM unzip location, you would type
Code:
d:
cd D:\MYROM
Type the following ADB command to make sure that your phone is recognized by ADB:
Code:
adb devices
If it works, you should see something like
Code:
List of devices attached
ABCD1234567890 recovery
where "ABCD1234567890" will actually be your device ID string, and not literally "ABCD1234567890"
If you see a string like the above, good news, it means that your phone is recognized by ADB, and we can now transfer the unzipped ROM to your SD card. If you do not see anything after the "List of devices attached" string, make sure that you have turned off MTP mode in TWRP as detailed above. If you still don't get anything, you will have to transfer the unzipped ROM to your sdcard by some other means - perhaps by putting the SD card in another phone. Skip the rest of the steps here and see Part 1.5 below.
Now type the following command in your computer's terminal window (command below is for Windows; on Linux, replace "D:\dload" with the appropriate path to the dload directory):
Code:
adb push D:\MYROM\dload /sdcard
This will copy the extracted ROM's "dload" directory to the root of your internal SD card. To copy it to the root of your external SD card, replace "/sdcard" in the above command with "/external_sd".
If all went well with the above command, then at this point your extracted ROM's "dload" directory should have been copied over from your computer to your phone (either on the root of the internal SD if you used "/sdcard" in the "adb push" command, or on the root of the external SD if you used "/external_sd" in the "adb push" command. Go to Part 2 below.
Part 1.5: Copy extracted ROM directory to external sdcard on phone using another phone.
SKIP THIS PART IF YOU SUCCESSFULLY COMPLETED ALL STEPS IN PART 1 ABOVE, AND GO TO PART 2 BELOW!
Remove the external SD card from your M2.
Insert the external SD from the M2 into some other phone/device.
Connect that phone to your computer via USB.
Transfer the unzipped ROM's "dload" folder to the root of the SD card.
Remove the SD card from the other phone and put it back into your M2.
Part 2: Flash official Huawei BOOT.img and RECOVERY.img and installed extracted ROM using official Huawei Recovery
In this part, we will replace TWRP with the official Huawei recovery and boot partitions, and use the official Huawei recovery to flash the ROM on the phone.
From the ROM you downloaded in Part 1 above, extract BOOT.img and RECOVERY.img using the Huawei Update Extractor. Since you already know how to do this, no further details will be given.
Flash the official Huawei BOOT.img and RECOVERY.img partitions (for safety, do not flash any other partitions) onto your M2. to refresh your memory on how to do this, see my guide.
After successfully flashing the official Huawei BOOT.img and RECOVERY.img partitions to your M2, you can flash the downloaded ROM as an update by booting into the Huawei recovery which you just flashed onto your M2. After booting into the Huawei recovery, it should automatically detect and start installing the downloaded ROM.
Hope this helps. Good luck!
TheOnlyPaulV said:
Thanks again for all your help however, I'm happy to buy you a beer (or non alcoholic beverage of your choice!l
Click to expand...
Click to collapse
That won't be necessary, but thanks for the offer I'm just trying to help out people wherever I can; I don't want anything in return

Hello, "different customer" here
I came into the same situation, a while ago I wiped a lot of things (through TWRP) making my tablet unbootable, I was trying to recover from a bootloop.
I followed this well written guide but the stock recovery won't detect the new ROM (I have a dload folder with META-INF directory inside and UPDATE.APP).
I flashed the BOOT.img and the SYSTEM.img while at fastboot mode. At the sdcard there is a folder dload with the rest.
Booting up with pressed + and - is starting to "Installing update" but hangs at 5%
What should I do

Well finally I managed to fix it, twice! here is the story.
After I left it for half an hour saying "Installing update 5%" I decided to reboot.
Tablet booted ok but there was problem with WiFi, couldn't switch to On.
I decided to reflash http://update.hicloud.com:8180/TDS/d...1LC100B206.zip once again but still nothing, I tried B002, B005 but no success with the WiFi (this wifi problem is something I did when I was fing around at the bootloader with fastboot).
Then I decided to flash the SimplyGoogle, that got me in a bootloop.
Ok I said now I will fix it once and for all.
Then I entered TWRP, wiped EVERYTHING and I got this http://update.hicloud.com:8180/TDS/d...1LC100B206.zip uploaded to the /sdcard/dload.
Next step was fastboot mode, flashed BOOT.img, System.img and recovery.img from the extracted UPDATE.APP of the M2-802L once again (keep in mind I have the M2-801L).
Now it was time to poweron with + and - pressed so the recovery to understand I need a system update/flash.
Again it was stuck at 5% but now I knew just left it hanging for an hour and rebooted.
And it worked.

At this point I want to give a big thanx to beast.in.black for his awesome instructions for how to recover a dead tablet.

lepidas said:
At this point I want to give a big thanx to beast.in.black for his awesome instructions for how to recover a dead tablet.
Click to expand...
Click to collapse
You're welcome, glad I could be of assistance
Your posting of your experiences may help someone else who runs into a similar issue, so thank you for taking the trouble to post in detail :good:

Im afraid I am not quite as advanced as your self, I dont know what a 'META-INF directory inside and UPDATE.APP' is so please bear with me, especially if im preaching to the converted.
My problem was that I had a, basically, blank device.
The only thing that remained was the boot and recovery.
The first thing I got wrong is that the device is partitioned into multiple parts, its not one rom image for it all thus flashing a update rom wont write over all the partitions to recover the device, it will only flash the ones its updating thus you need an image that has alll the partitions to recover from a wiped device.
Second problem I has was that the TWRP recovery will not allow flashing of complete roms and I didnt have a backup of a complete rom.
Third problem I had was getting a hold of a 'complete image'.
So the link above allow you to download a complete image. part1 done.
then extract the boot partition from the complete image as the complete rom will only install/boot from its own boot partition: you cant install a complte from from a TWRP partition.
flash the bootimage from the complete rom.
copy it to the SD card, install it from there.
Then, once you have your system up and running, install your updates ot get the unit back.
Hope that makes sense and ive not just repeated things you already know, but thats as far as my knowledge goes

Related

the dm-verity is not started in enforcing mode and may not work properly

My phone is the ASUS Zenfone 3 deluxe (zs550kl) model and its bricked only can enter fastboot or adb still but my os will not boot I tried going to asus website for stock firmware (UL-Z018-WW-11.40.71.37-user.zip) and stock kernel (ZS550KL_Kermel_11_40_71_37.zip). how do I install these to fix my phone unless there is a better way to make it boot. by the way im new to android I always had iphone jailbroken until last year I am android now but give me noob instructions for the how to. maybe I should add this I already have adb/fastboot installed and the commands for adb devices or fastboot devices when in fastboot mode both recognize my device so maybe my commands are wrong or something but I tried every way I could toinstill firmware and not sure what to flash kernel as the zip or the file unzipped please help thanks in advance. Not sure why this happened exactly but my bootloader is unlocked already but was never rooted so if there is another way to install another custom firmware besides stock I would like those instructions also thanks again
first off your phone is soft brick meaning all you have to do is flash the stock android software back onto your phone.
install to sd card -> boot into recovery (stock or twrp whatever you have works)
flash from sd
let it load (this will work if you have the correct files)
it will reboot and will work good as new again.
you shouldnt have to flash the kernal, just the UL-Z0 file.
That would have worked yesterday but im having another issue now basically instead of waiting for a response on here I went ahead and did other stuff now my recovery menu is not showing up so I cant install from sd now the only option I'm getting is fastboot so is there a way to fix the stock recovery option or even install a custom recovery which might be eaiser because my bootloader is already unlocked. I was going to try to flash stock recovery my self but not sure how exactly I know I use fastboot flash recovery (recovery file name in the folder) and I think it's .img but not sure so I think it will be either .zip or .img file type but not sure what it will be called if it's stock or custom and not sure where to find either. Last issue I'm not sure of is the actual files I downloaded from asus.com the firmware for my specific phone model not working when I try to flash it as the .zip file so my question is do you need to do something with it such as edit the script of something inside the zip of it and I also downloaded the kernel for my specific phone model from the Asus site and not sure if I needed it when flashing stock rom back to device or how to even flash it on the device please help if you can and I know some questions might be dumb to you but remember I'm a noob when it comes to Android recently left iPhone and I was a pro there every phone had a jailbreak and all types of stuff so I know I can get this just takes time I'm sure
I have this exact issue with a new Padfone Infinity A86... No access to stock recovery, only fast boot... But in my case I'm even unable to flash the recovery.img from a firmware package...
I'm wondering if you guys can help this person, maybe there is something in that solution for my Padfone
1: download the full firmware package
2: use sdat2img to convert the sparse system image to a regular one
3: use fastboot to flash the stock boot.img & the newly converted system.img
4: hoping you didn't flash the recovery partition, if you did, reflash the stock dump from the file in my Bootloader unlock thread via fastboot
5: reboot to recovery & do a factory reset
Read the documentation at each step, do your research, learn the process.

How to go back to stock EMUI 5.0 after flashing TWRP/Custom roms (Guide)

Tested Devices:
Huawei GR5 BLL-L22.
Hello all,
I just wanted to put this guide out there for anyone struggling with restoring stock after flashing a custom nougat rom/TWRP. It took me several days to figure out this method, which has never failed to get me back to stock after screwing with my phone. You can also use this if you accidentally wiped data without removing your fingerprint.
Prerequisites:
- Stock firmware for your device. If you were using a BLL-L22, you need the firmware which matches your phone's model and it has only been tested with the same firmware version. You can use the Huawei firmware update finder to get it.
- You'll need HuaweiUpdateExtractor, find it here: https://forum.xda-developers.com/showthread.php?t=2433454 . All credit goes to the original creator of the tool, @worstenbrood .
- You also need a Micro SD card in your phone, along with a micro SD card reader/ SD card reader (if you have a micro SD to SD card converter).
- You need a functioning computer with ADB commands installed system wide.
Anyways, here goes:
1. Unzip the update zip file, and ensure you have the update.app .
2. Using Huawei Update Extractor, extract only the boot.img, recovery.img, system.img, and vendor.img from the update.app . Those are the only files you need.
3. Boot into TWRP and format data. then wipe ALL partitions.
HINT: If you had your Micro SD card merged with internal storage, MAKE SURE you partition your micro SD card in TWRP via the partition SD card functionality, using EXT3/4.
4. Reboot into TWRP, and flash the vendor.img using the install image functionality in TWRP.
5. Wipe all partitions and format data as well, and reboot into the bootloader (fastboot).
6. Flash the BOOT, RECOVERY, and SYSTEM images, in that order, using fastboot.
7. Reboot into fastboot, and remove your micro SD card.
8. Create a folder called dload in the folder where the update.app file is located, and place the update.app file inside the dload folder.
9. Copy the dload folder to the micro SD card you have connected to your PC via a card reader.
10. Place the micro SD card back inside the phone, and then hold power + volume up + volume down.
11. This should begin the flashing process, wait till it finishes flashing and reboots.
12. Boot into the stock recovery, and factory reset and also clear data.
13. Reboot.
14. PROFIT! You should be back on EMUI 5.0 with a fully functional phone once more.
If you have any questions at all, feel free to ask. Also, if the guide worked for you, please let me know and I'll compile a list of devices it has been tested on. Thanks guys!
DISCLAIMER: This method works flawlessly for me, and I have used it countless times with my Huawei GR5 2017 (BLL-L22). I am not responsible for any damage done to your phone, nor can I guarantee this will work on every single variant of the Honor 6X. Do to this at your own discretion.
Hit thanks if I helped.
Nice guide dude!
Awesome job bro keep it up
very nicely put together mate. nice work.
I backed up my stock emui 5 boot,system,vendor but after restoring backup I stucked on boot animation what i can do now
Sent from my HONOR-6X using Tapatalk
arshilhonor6x said:
I backed up my stock emui 5 boot,system,vendor but after restoring backup I stucked on boot animation what i can do now
Click to expand...
Click to collapse
This guide concerns rolling back via dload, not via TWRP. You'd be better off asking in the TWRP thread, or asking the OpenKirin team.
I haven’t follow this guide
I just used dload directly with the same firmware (i was only rooted)
Phone doesn’t enter fastboot using volume down and power
But i can go to fastboot using adb command (adb reboot bootloader)
I am actually exactly doing this right now. Honor was not able to help me, after the BETA UEMI 5.0 put the system into a non-upgradable state. I tried to upgrade it/rollback etc. but that made it worse.
So- my current problem is, I don't have TWRP (It is installed, but won't start because I am in the rollback-version of the firmware). what can I do to actually go on with it?
When you say: 3. Boot into TWRP and format data. then wipe ALL partitions.
So - I used the recovery from HAWEI to format the data partition (That should do it).
As I said - I only have fastboot at hand right now.
Also - the vendor image flash returns this:
Code:
$ fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending 'vendor' (419273 KB)...
OKAY [ 11.443s]
writing 'vendor'...
FAILED (remote: Command not allowed)
finished. total time: 11.448s
Any hints?
Use dload method to flash full latest firmware from firmware finder
Sent from my BLN-L22 using Tapatalk
---------- Post added at 09:33 AM ---------- Previous post was at 09:32 AM ----------
If u are unable to boot any recovery then go to service centre they will replace your mobo
Sent from my BLN-L22 using Tapatalk
arshilhonor6x said:
Use dload method to flash full latest firmware from firmware finder
Sent from my BLN-L22 using Tapatalk
---------- Post added at 09:33 AM ---------- Previous post was at 09:32 AM ----------
If u are unable to boot any recovery then go to service centre they will replace your mobo
Click to expand...
Click to collapse
No, it just won't allow me to write the vendor image.
I can go into the regular recovery etc., but I can' t do anything. Not even reset the system etc.
xda_jm said:
No, it just won't allow me to write the vendor image.
I can go into the regular recovery etc., but I can' t do anything. Not even reset the system etc.
Click to expand...
Click to collapse
Flash twrp using fastboot or use dload method
Sent from my BLN-L22 using Tapatalk
arshilhonor6x said:
Flash twrp using fastboot or use dload method
Click to expand...
Click to collapse
I have the BLN-L21C432 device (Berlin). You know which TWRP I have to flash?
Using the twrp from https://dl.twrp.me/berlin/ ->
twrp-3.1.1-0-berlin.img
That twrp won't show up. Probably because I don't have the right Vendor-image or so. No logs available etc. A real bummer ... :crying:
Stuck here:
Code:
You're device has been unlocked and can't be trusted.
To learn more, visit:
Blabla UYRL ...
Your device is booting now...
My assumption is that I have a mismatch between Vendor/recovery/system and boot.img files. Only, how do I look into these images (I could mount them as loopback device under linux? Linux only here, no windows). And I need to identify the verison of these images/build to flash the right versions for the dload to actually handle the right upgrade.
xda_jm said:
You know which TWRP I have to flash?
Using the twrp from https://dl.twrp.me/berlin/ ->
twrp-3.1.1-0-berlin.img
That twrp won't show up. Probably because I don't have the right Vendor-image or so. No logs available etc. A real bummer ... :crying:
Click to expand...
Click to collapse
That TWRP won't work, sadly even if hosted on official site it never worked. Grab the TWRP from here https://forum.xda-developers.com/honor-6x/development/twrp-t3583413 and flash via fastboot, it'll surely works. Vendor partition is separated from recovery one, so don't worry because even with an incorrect vendor.img it'll works anyway
RedSkull23 said:
That TWRP won't work, sadly even if hosted on official site it never worked. Grab the TWRP from here https://forum.xda-developers.com/honor-6x/development/twrp-t3583413 and flash via fastboot, it'll surely works. Vendor partition is separated from recovery one, so don't worry because even with an incorrect vendor.img it'll works anyway
Click to expand...
Click to collapse
Yeah. That was it.
So I am able to actually get into the TWRP recovery. Nice
Now - following your guide, I am unable to format data partition:
Code:
Full SELinux support is present
MTP Enabled
Formating data using mkfs.f2fs
mkfs.f2fs -t 0 /dev/block/mmcblk0p49 process ended with ERROR: 255
unabel to wipe data
unable to format to remove encryption
Any idea?
Shall I continue with the process?
I could change the filesystem of data to ext4 or so for testing?
UPDATE: Actually changing data to ext4, formating it as ext4 + rebooting into recovery and changing back to f2fs and formating f2fs worked in the end. What a crap.
I'll write down exactly what I do!
So - everything worked, except the factory reset showed a red exclamation mark.
It is now rebooting. And - no. I still have the BETA EMUI 5.0 showing, BuildNr. BLN-L21C900B300
Opening a new post for the next steps...
So - the cleaning has not worked.
After checking the imags in the update package, I noticed they are all different.
Why did the system-reset fail at all? Where does that come from?
Here the file-checksums:
Code:
$ cat BLN-L21C432B360-FullOTA-MF-PV/md5sums.txt
cbc1a5b85deb8caca46d7ed691f1d5d7 BOOT.img
78ccf0ff58d189284293e219f2aa8ce2 CACHE.img
eef4f7d2c4187b7cd195df1c1139950e CRC.img
f6594819938b923bccf075349b250347 CURVER.img
a181b39b6095f221ffb207268d10d540 DTS.img
aa3a0518794c16bb22849676c13ba55c EFI.img
0f1fcd32afb2db5183d86e527510c6b4 FASTBOOT.img
8379cfc96d5ddd57993da668c0e68da7 FW_HIFI.img
d60eb96f274cab285fe1bc5cb8ac874c FW_LPM3.img
afd9223813961adfbf71b0a51c310f66 MODEM_FW.img
176c0d4b0489a639f5bd371b5445a466 MODEMNVM_UPDATE.img
f07fcca53b5337e003e9894ec4b231e6 PRODUCT.img
40c8ce310fb8dde705c6b29ce316a215 RECOVERY2.img
a3883873ca0054ec12fb8d0a71835ca9 RECOVERY.img
cd22975bcc99a3436a74d6123e9c2796 SENSORHUB.img
2c4fab4df4b00c7dcb08fd8a47c0228f SHA256RSA.img
0565a9f075122ebf46c9f623eb6b22d2 TEEOS.img
e6a5b518daa00ea67a2a360408534dd9 TRUSTFIRMWARE.img
09e9dcef68ffddce4c1a41f1bbeae435 UPDATE.APP
19324f9cd1351119b4efdfa5c235200e VENDOR.img
9219d25ed7eb999fb08c03bf493929a3 VERLIST.img
83c5d8c7866c34f4ff901e17536ad3b4 XLOADER.img
Code:
$ cat RollBack_DE/md5sum.txt
6682ebf3c4c59b58e27cac42bc0a5760 BOOT.img
c9026aa21284a5c6575573bad6c67531 CACHE.img
643062216ba9a1a9c43091a56407b4e4 CRC.img
e665793d69c041c1a67ce25e342bb665 CURVER.img
862d05d2ac39567d48db9d4a996698e8 CUST.img
0c66cff221dd1adade7060d93f9f14db DTS.img
997a84cac4901d8d47a13d03a41645c1 EFI.img
cfdb3c574a4e22e6918021eb551af744 FASTBOOT.img
6534c81facf064c61fbe838a844bcf53 FW_HIFI.img
2c6cf6c896c17ed938563779d4bc015d FW_LPM3.img
330f6c5fe86c9c716ba675ade522a4c4 MODEM_FW.img
77ca34a576955b1aa7b09adcc43183aa MODEMNVM_UPDATE.img
bf696a2a9eb149bf3d409ab3fab8da1b RECOVERY2.img
ba1a5ef8d2d77dd03a4e5a3fb8be724b RECOVERY.img
e73ae0c33807474e61caaf2f5864bd93 SENSORHUB.img
53d8a3d3afcfd61a73d4446d37602249 SHA256RSA.img
713c288402f5d540efc722e442218fc0 SYSTEM.img
29a07ee1454ece337416b595101a016f TEEOS.img
15a226f7741aee2d026d760f755d6991 TRUSTFIRMWARE.img
b8100f45c08c2b54ec089e52d945fae9 VERLIST.img
7eb918861de29526259611fe95365e90 XLOADER.img
The rollback one is supposed to be an intermediate entry - C900B300 - which was supposed to make a rollback to EMUI 4.x (Tried that route, because I couldn't update any EMUI 5 releases).
Any idea what to do?
Reloaded twrp. When I chec the internal storqage, I see:
Cache
Data
System
Vendor
Product
Micro SDCard
USB OTG
Could it be the Product partition? What's inside?
xda_jm said:
Reloaded twrp. When I check the internal storage, I see:
Cache
Data
System
Vendor
Product
Micro SDCard
USB OTG
Could it be the Product partition? What's inside?
Click to expand...
Click to collapse
Actually, there are 48 Partitions *lol* Amazing.
And - to write an image manually using adb shell in twrp (That's where it works), the extracted images from UPDATE.APP need to be uncompressed first with:
Code:
/external_sd # simg2img PRODUCT.img PRODUCT.raw
/external_sd # dd if=PRODUCT.raw of=/dev/block/mmcblk0p48
393216+0 records in
393216+0 records out
201326592 bytes (192.0MB) copied, 7.405686 seconds, 25.9MB/s
Alas, the images are identical. So no changes.
Still debugging under the hood.
If anyone has an idea, let me know :}
So - last post from me probably. It has not worked.
My wife decided to stay with the beta EMUI 5.0.0.1 until a decent Lineage OS 14.1 version is there (Stable). I'll then put it on the Honor 6x.
It is amazing to see that actually 8GB of space from the disk is reserved for HUAWEI and GOOGLE tools, dispersed in 48 partitions, all to prevent people from using the device freely.
And I bet in future it will get worse and worse. Anyway - have learned a lot regarding the tools and how to use these, and what to take into account when doing things with phones.
I personally still use an old BQ E4.5 Aquaris Ubuntu phone which does most of what I need very nicely IO know why I hate Apple devices, and not so much Android devices.
in 5% i get failed
software install failed
my build is NRD90M test-keys
after write system recovery boot but faild in dload mode
bootloader is unlock
dark_boy99 said:
in 5% i get failed
software install failed
my build is NRD90M test-keys
after write system recovery boot but faild in dload mode
bootloader is unlock
Click to expand...
Click to collapse
I'll PM you the files. Certain update.app files fail to write, I don't know why. Give me a few hours to get the files to you.
Can someone please help me link to Stock firmware for my device? I honestly don't know what's my model number
What do I download?

PSA - Going back to stock from Treble.

I've noticed that many in this forum for the Honor 7x / Mate SE want to try a few ROMS, and then eventually go back to stock - Some just want to go back to stock. I had my own issues and thankfully there were others to help along the way. This method does not use fastboot to flash partitions, it uses TWRP, so the assumption is you have a working TWRP. Also I am not responsible for any bricks, I am just explaining what I did to get back to stock (And based on all the issues people are having, I'm staying there)
If you've tried a Treble ROM or others, the route I took to get back to stock was as follows:
1.) Download your firmware from Firmware finder or the Pro-TeamMT website:
http://pro-teammt.ru/firmware-database/?firmware_model=bnd-l34&firmware_page=0
In this example, mine is the Mate SE..
You should have downloaded 3 files. The important one we want right now is the Update.zip - Extract this file. You should see UPDATE.APP within this folder.
2.) Download the Huawei extractor software by worstenbrood:
https://forum.xda-developers.com/showthread.php?t=2433454
3.) Use this software to extract the files from the Update.App - You may need to disable the Checksum checks under "Settings". When you select the UPDATE.APP file, you should get a list of the files that are compiled or compressed into the app. The main 4 files you want are Ramdisk, Vendor, System, and if you'd like the Stock recovery (Recovey_Ramdisk). Copy these files to your SD card.
4.) Assuming you still have the functioning TWRP, reboot into TWRP and wipe everything but the SD card.
5.) Flash the images to the appropriate partition, Ramdisk = Ramdisk, Vendor = Vendor Image, and System = System Image - Ensure you're flashing the image partitions. Ramdisk is necessary if you've ever rooted or used Magisk.
At this point you should be able to reboot and get back into stock...But you'll notice Themes do not work properly..That's because you've wiped / formatted data at some point in TWRP, and now the Data/hw_int has been wiped. You can fix this by flashing the update on top of itself by the instructions in this thread (Thanks to mrmazak):
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
See the "Flash update while on Oreo"...This has worked twice now to get me back my themes after wiping /data.
I counted on my TWRP backup to get me back to stock after trying a Treble ROM, and I ended up bricked. So hopefully this helps someone!
PS, if anyone has more to add this this, the more help the better.
Wait, wouldn't the recovery be the file "RECOVERY_RAMDIS.img"
???
crayonicle said:
Wait, wouldn't the recovery be the file "RECOVERY_RAMDIS.img"
???
Click to expand...
Click to collapse
You are correct...That is the name of the actual image in the UPDATE.APP, but I was basing the name off of the actual partition.
Corrections, please add to original post
smokinjoe2122 said:
You are correct...That is the name of the actual image in the UPDATE.APP, but I was basing the name off of the actual partition.
Click to expand...
Click to collapse
Just learned today that you can't flash Vendor through Fastboot, so you have to copy all the necessary files onto a SD card or USD OTG.
The files needed are: "SYSTEM.img" "RECOVERY_RAMDIS.img" and "VENDOR.img"
Flash them through twrp in the required partitions, the partition names are literally the file names.
TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=28883
crayonicle said:
Just learned today that you can't flash Vendor through Fastboot, so you have to copy all the necessary files onto a SD card or USD OTG.
The files needed are: "SYSTEM.img" "RECOVERY_RAMDIS.img" and "VENDOR.img"
Flash them through twrp in the required partitions, the partition names are literally the file names.
TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=28883
Click to expand...
Click to collapse
System image can fail too...that's why I said to flash everything in TWRP...Plus, flashing the update on-top of itself will not only give you theming back, but stock recovery.
crayonicle said:
Just learned today that you can't flash Vendor through Fastboot, so you have to copy all the necessary files onto a SD card or USD OTG.
The files needed are: "SYSTEM.img" "RECOVERY_RAMDIS.img" and "VENDOR.img"
Flash them through twrp in the required partitions, the partition names are literally the file names.
TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=28883
Click to expand...
Click to collapse
Is this working ? Did you try ? I'm on RR ROM and couldn't get adb recognize my device. This is my only hope to return to stock as of now.
Adithya Krishnakumar said:
Is this working ? Did you try ? I'm on RR ROM and couldn't get adb recognize my device. This is my only hope to return to stock as of now.
Click to expand...
Click to collapse
Yes, I tried it. It works flawlessly.
How can I get themes to work? I don't understand the original post, it makes no sense when explaining how to get themes to work properly. I do not know what to do with the link provided in the original post.
crayonicle said:
How can I get themes to work? I don't understand the original post, it makes no sense when explaining how to get themes to work properly. I do not know what to do with the link provided in the original post.
Click to expand...
Click to collapse
What part are you stuck on?
Essentially mrmazak created a flashable file that will take the 3 firmware files you download and flash them on top of your current firmware. This is helpful for doing an update or just reloading the firmware completely (Which is what you're trying to do)...
I'd follow the exact instructions that he's put out on that thread, but the 10,000 ft overview:
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
1.) Download files from link for your device
2.) Create a correctly named folder on your SD card, along with those files properly named in that folder (Ensure these files are named properly also.)
3.) Ensure you have the stock recovery on the SD card also.
4.) Copy the "xxx_Update.zip" he created onto your SD
5.) Flash the "xxx_Update.zip"...It will will flash the stock recovery, then boot into update mode and update with the 3 files you downloaded and put into that folder. This will basically "reflash" the firmware and give you back themes.
I would go step by step on his action list and follow them to a "T". I've verified it works perfectly. He also has a "Basic-Instructions" write up in the zip also.
My device build number was BND-L21C185, I bricked my device once but I managed to get it back. Since then I have strange build number which is system 8.0.0.046(063f). Does this method fix it?
This info helped me bring my phone back to life,thank you sir for the step by step instructions.
Found a way to get back to stock without all this hassle lol
So I thought this was the only way to get back to stock... turns out there is a much easier way
This method also enables themes, I checked myself.
https://forum.xda-developers.com/honor-7x/how-to/getting-to-stock-emui-super-easily-t3804722
Is it possible to flash all of the partitions from fastboot?
I have the BND-L34 and I am unsure as to what happened.
I have been running the RROS surdu_petru posted for about 3 weeks now and it was running fine.
2 days ago I grab my phone and it was booted into error mode. Now when I try to boot into twrp I get an error code for my recovery. When I try to boot into the system it throws a different error code for boot image.
I have a twrp backup stored on an sd card, and all 3 OTA's I saved back during the June update. I have the Pro-TeamMT app on my pc and have found/extracted every file for the brick method only get the same errors, 1 right after the other.
I am no noob, (although I am not a Senior Member with a giant banner either ) but I have been rooting android devices going on 8 years now, and have never completely bricked any of them.
My last 2 phones were Oneplus 1 and Oneplus 3, so I am familiar with flashing all the partitions using fastboot. But with those phones there were about 9 different individual flashes that needed to be done in a particular order.
Any help or advice would be greatly appreciated.

Rooting Blackview A20

I have a blackview A20 which is a low spec phone running android oreo go.
I would like to use this phone for experimentation with android development and learning about android on a cheap device without risk of breaking my main phone. To do this I would like it rooted and as a bonus with a custom recovery so I can test custom ROMs.
State of device:
Unlocked bootloader
Unchanged ROM
Unchanged Recovery
OEM unlocking enabled
USB debugging enabled
What I have tried:
Flashing recovery images with fastboot
Using fastboot flash recovery recovery.img with some TWRP and CWM recovery images all yield:
target reported max download size of 134217728 bytes
sending 'recovery' (4690 KB)...
OKAY [ 0.169s]
writing 'recovery'...
OKAY [ 0.276s]
Click to expand...
Click to collapse
finished. total time: 0.448s
or similar. Then I restart phone and select boot into recovery mode. The phone hangs for a small while before restarting and booting into the normal OS. On restart into recovery the unchanged recovery is there still.​
Various 'one-tap' methods
All of which were unsuccessful. If needed I can give details.​
Installing SuperSU zip from recovery
In a futile attempt I tried to use the android recovery to push a SuperSU zip with its update from zip option. I knew this wouldn't work but I found something interesting. On the Apply update from SD card option I get an error saying couldn't mount /sdcard​
Booting recovery images with fastboot
I have tried the fastboot boot recovery.img command to try to boot directly into the images. I get this
downloading 'boot.img'...
OKAY [ 0.211s]
booting...
OKAY [ 0.047s]
finished. total time: 0.261s
Click to expand...
Click to collapse
output but the device just restarts and boots normally into the normal OS.​
What I would like from this question (In order of importance):
A way to root the device
A way to access a custom recovery (even if temporary)
Ability to install custom ROMs
A permanent custom recovery
mejakep said:
I have a blackview A20 which is a low spec phone running android oreo go...
Click to expand...
Click to collapse
I don't have this device but, you may find the following threads helpful because they, apparently, are compatible with your specific device. Don't be afraid to ask for some member guidance within one of them too.
https://forum.xda-developers.com/showthread.php?t=3709659
https://forum.xda-developers.com/showthread.php?t=3767690
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Hello,
I'm also trying to root the Blackview A20 with no success. Where you able to find a way?
Thanks!!
I'm afraid I still haven't found a way. Other than TWRP or something making a custom recovery specifically for this phone I don't see a way to root it at all. Sorry
I have a Blackview A20 Pro (note this is probably different in specification to the A20) - Here is how I rooted it by using Magisk on a boot image read and written using SPFlash tools. I had previously unlocked the bootloader on the phone by using the Developer option for OEM unlock and then fastboot unlocking as standard.
- Obtain the MT6739_Android_Scatter file from an archive of the a20 stock rom available by googling
- Install Magisk manager apk on the phone
- Run the latest version of SP Flash tools on the PC with the associated drivers. Load the scatter file in to it.
- Work out the size of the boot partition by subtracting the start value of the next partition (Logo) from the start position of (Boot)
- I did using Windows calculator in programmer mode - set to hex, subtract the two values. Note the start position of the boot partition
- Go to the Read Back page, add an item to read back, enter a filename to save it like a20-stock-boot-image.img and then enter the start position of the boot partition and the size you calculated. Make sure to get them exactly correct and avoid changing the number of digits in the entry box as I don't know how fussy sp-flash tools is.
- Unplug the phone from PC if it is plugged in and remove the battery.
- Tell SP Flash tools to start the read-back
- Plug the phone in, within a few seconds it should read and save the boot partition from the phone. Keep this backed up. File should be something between 8-25mb I would expect.
- Put the battery in the phone and power it up and unplug/plug it in to the PC via usb and then in the notification area on the phone select "Transfer Files" from the very bottom so it appears to your PC as a drive.
- Drag over the stock boot image from your PC somewhere on the phone - like the Downloads folder.
- On the phone open magisk and select install - when prompted select to use local boot image, select the stock boot image file you transferred
- Magisk should now patch this file - make sure the text it outputs looks like it recognized the boot image and is working.
- Now unplug and replug the phone to PC as I found PC doesn't seem to see new files on the phone. Pull over the patched boot image Magisk has made. Don't worry if this is smaller than the original file. The extra bytes were likely just zeros.
- Using SP Flash tool, go back to the Download screen and select the patched boot image for the boot partition. This will write the new boot image to your phone.
- Power down the phone and remove the battery.
- Tell SP flash tool to start and then plug the phone in with no battery. It should then flash the patched boot image.
- Put the battery back in and boot the phone. When you open magisk app on the phone now it should say you are rooted.
Enjoy!
If it doesn't work, repeat the download process with the stock boot image you saved and that should restore things to how they were before. I assume if it doesn't work it will just be because you need to unlock the bootloader or because your phone is different to the scatter file, but in that case I would expect Magisk to fail to patch it before you get to that stage.
How do you remove the battery? Have I missed something?
Sorry, wrong phone!!

Question Find Device storage corrupted. Your device is unsafe now.( POCO F3 and Other MIUI Devices)

Last night I do have a problem with the custom rom that I have installed, because of the battery problem keeps on dropping, so I decided to go back to the official stock rom which is for global however after flashing the fastboot rom via Miflash Tool, I have a welcome message that says Find Device storage corrupted. Your device is unsafe now. I thought that I just need to activate this to the device admin, after a reboot I tried to check it out if this message if this message will still pop up, and it keeps on popping up. I have flashed the rom again and it keeps on happening.
Things that I have Tried:
So I tried to check for other ways that I could get rid of this but this doesnt work on the terminal via TWRP. "
[GUIDE] How to fix "Find Device storage corrupted. Your device is unsafe now".
[GUIDE] How to fix "Find Device storage corrupted. Your device is unsafe now". How to fix "Find Device storage corrupted. Your device is unsafe now" ? (At your own risk... I'm not responsible for damage or brick) Required : - Be rooted and...
forum.xda-developers.com
".
The one that works:
Things that you needed:
1. Download Mi Flash Tool(https://www.xiaomiflash.com/)
2. Minimal ADB and Fastboot
3. 7zip or BreeZip
4. TWRP A12(
TWRP A12.rar
drive.google.com
) if you are using other MIUI and devices and want to check it this will work then just use your twrp that is recommended for your mui device.
5. Global Rom (https://xiaomifirmwareupdater.com/miui/alioth/stable/V12.5.6.0.RKHMIXM/)
warning: make sure that you are using the right rom for your device, my device that I am using is a global variant so I need to flash a global version, if you are using other MIUI device and want to check it out just download the miui that works for you must be on a later update of the rom if the latest current rom that you are working on right now didnt work.
Steps to follow.
1. Extract the Rom which you have downloaded using the 7zip or BreeZip, so for me I extracted the version 12.5.6.0 take note that this is not the latest rom but for this to work we need to be in a later update this rom is an android version 11.
2. after extracting the fastboot rom file type TGZ you will notice that the one that you extracted is on a TAR file type, and you need to extract the TAR file type for you to have the folder "alioth_global_images_V12.5.6.0.RKHMIXM_20220210.0000.00_11.0_global_62b4f5d6ca"
3. Using the Mi Flash Tool, just pick the clean all and start the flashing.
4. After flashing the rom set up the phone but do not update it.
5. On your extracted folder for the rom go to the folder that says images and look for 'persist" this is an img file. copy the persist img file and paste it on your Internal memory of your phone.
6. Turn off your phone and go to fastboot by pressing the volume down as well as the power button. You will notice that the fastboot logo is the older version since we are using an older rom.
7. Extract the TWRP A12 and you should have the disc recovery image of it, copy and paste it on your Minimal ADB and Fastboot folder and rename it "recovery".
8. While you are on the Minimal ADB Fastboot folder make sure that your phone is plug in to the usb port on your computer, click the cmd here on the Minimal ADB and Fastboot Folder and you should able to run the cmd.
9. run the following commands:
fastboot devices (then press the enter)
warning: make sure that the fastboot devices is able to see your device.
after seeing the device run this command:
fastboot boot recovery.img (then press enter)
the device should boot to the twrp if its on chinese look for settings and set it to english. we are not flashing the twrp we are just going to use it temporarily thats why we are only going to boot it to twrp recovery.
10. On your twrp, go to install, click the install image and look for your persist.img that we have copied earlier to your internal memory
you should find it on the sdcard folder. just flash and you will see that you have successfully flashed the persist image and then just reboot your phone.
After rebooting your phone you will notice that the "Find Device storage corrupted. Your device is unsafe now." will not prompt. Since I already have the current fastboot rom I have tried to flash the current fastboot rom and locked my device and fixed the problem permanently without any problem.
You wrote too much for something that could be written in a few sentences. And why would anyone downgrade an android or flash a clean fastboot ROM? (Android or MIUI version doesn't matter)
Summary guide:
1. Download the fastboot ROM from here and extract the "persist.img" image or dump the "persistbak" partition from your device and rename this file to "persist.img"
2. Put persist.img into your device's internal memory and go to TWRP
3. In TWRP, go to: Install> select install image> select file persist.img> select "Persist" partition
4. Restart the device, it should work fine
uvzen said:
You wrote too much for something that could be written in a few sentences. And why would anyone downgrade an android or flash a clean fastboot ROM? (Android or MIUI version doesn't matter)
Summary guide:
1. Download the fastboot ROM from here and extract the "persist.img" image or dump the "persistbak" partition from your device and rename this file to "persist.img"
2. Put persist.img into your device's internal memory and go to TWRP
3. In TWRP, go to: Install> select install image> select file persist.img> select "Persist" partition
4. Restart the device, it should work fine
Click to expand...
Click to collapse
Wrote it down for the newbies that doesnt know how to fix anyway thanks for the summary. I have to downgraded it because the latest current rom doesnt work give me "invalid sparse file format at header magic" error as I flash the persist.img file, via twrp.
mizuhored said:
Wrote it down for the newbies that doesnt know how to fix anyway thanks for the summary. I have to downgraded it because the latest current rom doesnt work give me "invalid sparse file format at header magic" error as I flash the persist.img file, via twrp.
Click to expand...
Click to collapse
If you are using TWRP from Nebrassy then use skkk TWRP or OrangeFox. Flashing persist should work fine on both recoveries (I did it myself recently).
uvzen said:
If you are using TWRP from Nebrassy then use skkk TWRP or OrangeFox. Flashing persist should work fine on both recoveries (I did it myself recently).
Click to expand...
Click to collapse
Thats great but this is the one that works for me anyways. At least we have found out the things that we needed in order for it to be fixed. Just sharing my ideas and how did I fixed the problem myself. Thanks for sharing of your ideas. Hoping that we could share our ideas to others as well. Been on a nightmare last night cant sleep because of this problem. Trying to figure out what to do since using the cmds via terminal on twrp doesnt work for me. Need to downgrade for me to fix it.
mizuhored said:
Thats great but this is the one that works for me anyways. At least we have found out the things that we needed in order for it to be fixed. Just sharing my ideas and how did I fixed the problem myself. Thanks for sharing of your ideas. Hoping that we could share our ideas to others as well. Been on a nightmare last night cant sleep because of this problem. Trying to figure out what to do since using the cmds via terminal on twrp doesnt work for me. Need to downgrade for me to fix it.
Click to expand...
Click to collapse
Could you please confirm if flashing persist.img doesn't mess up with sensor like fingerprint, l1, compass etc..? I have seen other forums talking about possibility of losing these in case perist is flashed from rom. I have this message for some time now, but all other sensors work fine, even l1 certification and saftynet. Thanks in advance.

Categories

Resources