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.
Related
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
UnfriendlyTurtle said:
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
Click to expand...
Click to collapse
You can't update the "normal way" like that with a custom recovery. When you try to do that, it tries to boot into the stock recovery to update, but since you have a custom recovery, it will fail everytime if you do it that way. What you have to do is flash the OTA zip using TWRP. You can find the OTA zip in /cache on your device. Or you can just download the update zip from these forums.
UnfriendlyTurtle said:
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
Click to expand...
Click to collapse
Since 4.4.4 is out, just download the full firmware package from Google and flash system, boot. Only those two.
If you don't know how to do that, the Nexus 5 forums has some great stickies that are mostly relevant to this device.
charesa39 said:
You can't update the "normal way" like that with a custom recovery. When you try to do that, it tries to boot into the stock recovery to update, but since you have a custom recovery, it will fail everytime if you do it that way. What you have to do is flash the OTA zip using TWRP. You can find the OTA zip in /cache on your device. Or you can just download the update zip from these forums.
Click to expand...
Click to collapse
Right, thanks for the information. So I repeated and booted into TWRP again. Tapped 'Install', navigated to /cache, saw a couple of folders named 'back up', 'lost+found', and then a file name of a large string of letters followed by the recognisable "razor KTU70 from KOT49H", so I went ahead and flashed the latter, checking 'verify signature'. Runs through a few commands and in a few seconds comes back as failed, so I reboot into the OS.
Any ideas?
Aerowinder said:
Since 4.4.4 is out, just download the full firmware package from Google and flash system, boot. Only those two.
If you don't know how to do that, the Nexus 5 forums has some great stickies that are mostly relevant to this device.
Click to expand...
Click to collapse
I think I have an idea, but I'll check just to be sure. Thanks for the direction.
Exactly the same for me. Installing the ota sent me to my TWRP recovery. Reboot - > still in 4.4.2.
Reading this thread, I went to TWRP recovery, installed the update from cache and like you, it failed.
Any suggestions? Did your idea work?
Where do I find the 4.4.4 mentioned here and how do I flash it in TWRP? Is install the same as flash in TWRP?
Thanks.
Anderson2 said:
Exactly the same for me. Installing the ota sent me to my TWRP recovery. Reboot - > still in 4.4.2.
Reading this thread, I went to TWRP recovery, installed the update from cache and like you, it failed.
Any suggestions? Did your idea work?
Where do I find the 4.4.4 mentioned here and how do I flash it in TWRP? Is install the same as flash in TWRP?
Thanks.
Click to expand...
Click to collapse
If it fails look to see what the specific error is. It would help to know that. If you pulled it from your cache then I assume it was downloaded by itself and should be the correct OTA. I do NOT have the "Zip file signature verification." box checked or "Enable MD5 verification of backup files." but I am extremely careful to flash/install the correct files. The OTA installed fine for me two days ago using TWRP 2.7.1.0. The 4.4.4 mentioned earlier is the factory image. You will need adb and fastboot installed on your computer to flash the factory image or any image that is pulled from inside the factory image. Wug's toolkit will work also, I think, but I've never used any toolkits. Eventually there will be a stock 4.4.4 rom that you can flash/install in TWRP but I'm not aware of one right now.
You can take the normal updates with root and TWRP (I did), but a custom kernel will prevent them from installing.
I retried to install the downloaded ota file from cache, but this time I checked zip file verification and got the error message that zip verification failed.
File name was
df43279bcf6bb6a0ae403249c3e6f314d0a7eb77.signed-razor-KTU84L-from-KOT49H.df43279b.zip
So it seems the downloaded ota file may be corrupted. How do I get my Nexus 7 2013 to re-download a new one?
(The ota download for my Nexus 5 installed with no problems - but I think it didn't go through TWRP even though TWRP is installed there too).
Thanks
---------- Post added at 04:05 AM ---------- Previous post was at 03:59 AM ----------
Further
I renamed the ota file and in settings checked for system update and got a response that my system is upto date. But it is still 4.4.2.
Need to re-download the ota. How?
Changed the system date to 2 weeks earlier and succeeded in re-downloading the ota file.
So I retried installing it and it again took me to my TWRP recovery screen. I again installed the ota from cache and again the zip verification failed : 1
And the update failed again.
Still on 4.4.2
Did not change any system files as far as I know.
Need help.
Why don't you guys download the stock firmware from Google (link in my signature), and use fastboot to flash system.img, boot.img (DO NOT run the batch file)? If it's a lack of knowledge, all you need do is ask, and I or someone else would be happy to teach you how to use it (fastboot). If you're going to be modifying your Nexus device, you need to learn fastboot. You guys have got to learn the proper way to do things.
You've put forth so much effort to fix a system that is not meant for modified (rooted, customized) phones. You can't fix it, stop trying. Just do it the proper way. And do not use a toolkit. They don't teach you anything, they spoon-feed.
Aerowinder said:
Why don't you guys download the stock firmware from Google (link in my signature), and use fastboot to flash system.img, boot.img (DO NOT run the batch file)? If it's a lack of knowledge, all you need do is ask, and I or someone else would be happy to teach you how to use it (fastboot). If you're going to be modifying your Nexus device, you need to learn fastboot. You guys have got to learn the proper way to do things.
You've put forth so much effort to fix a system that is not meant for modified (rooted, customized) phones. You can't fix it, stop trying. Just do it the proper way. And do not use a toolkit. They don't teach you anything, they spoon-feed.
Click to expand...
Click to collapse
I don't use a toolkit and would be happy to flash the system.Img and boot.img but need instructions on how to do it. You said the stock firmware link is in your signature but it isn't.
I would like to skip 4.4.3 and go directly from 4.4.2 to 4.4.4. I'm talking about a nexus 7 2013 wifi.
So I need the following information to proceed .
1. The Link to download system.img and boot.img for the nexus 7 2013 wifi. Which files exactly?
2. I have fastboot and adb installed on my windows 7 laptop because I used them (once) to root but I don't remember how I used them that one time. How exactly do I use fastboot to flash 4.4.4 ?
3. I presume I will lose root. How do I regain it after the above.
Thank you.
Anderson2 said:
I don't use a toolkit and would be happy to flash the system.Img and boot.img but need instructions on how to do it. You said the stock firmware link is in your signature but it isn't.
I would like to skip 4.4.3 and go directly from 4.4.2 to 4.4.4. I'm talking about a nexus 7 2013 wifi.
So I need the following information to proceed .
1. The Link to download system.img and boot.img for the nexus 7 2013 wifi. Which files exactly?
2. I have fastboot and adb installed on my windows 7 laptop because I used them (once) to root but I don't remember how I used them that one time. How exactly do I use fastboot to flash 4.4.4 ?
3. I presume I will lose root. How do I regain it after the above.
Thank you.
Click to expand...
Click to collapse
1. The Google firmware link in my signature is the one you want. You say you have the 2013 wifi model, aka flo, aka razor. "Factory Images "razor" for Nexus 7 [2013] (Wi-Fi)" is the proper section for you. You want 4.4.4 (KTU84P), and that's at the bottom of the razor section. Click the link to download.
2. Download the most up to date ADB/Fastboot from the link in my signature (19.0.2 (API 19)). Don't extract it yet.
3. You will lose root. Download SuperSU from my signature. 2.00 is the current version. After you download that, you can put it on your device so you can flash it in recovery in a few minutes.
The firmware you downloaded is razor-ktu84p-factory-b1b2c0da.tgz. This is a compressed archive, and you will need to extract it. If you don't know how, 7-Zip should work.
So, you've extracted the files. Delete flash-all.bat, flash-all.sh, flash-base.sh (so you don't accidentally run them).
Now, all you have left is bootloader-flo-flo-04.02.img and image-razor-ktu84p.zip.
Extract image-razor-ktu84p.zip to the current directory, so you will now have bootloader-flo-flo-04.02.img, boot.img, cache.img, recovery.img, system.img, userdata.img, android-info.txt, image-razor-ktu84p.zip in your folder.
Delete userdata.img, flashing this on accident will wipe your data. Delete image-razor-ktu84p.zip, android-info.txt, cache.img, recovery.img (this is stock recovery, you want TWRP).
Now you have boot.img, bootloader-flo-flo-04.02.img, system.img.
Remember the ADB & Fastboot zip you downloaded from my signature? Extract it to the directory with bootloader-flo-flo-04.02.img, boot.img, system.img. All 4 files. This directory now contains 7 files.
Back out of the razor-ktu84p folder. Just one step back. Now, hold shift the right-click the razor-ktu84p folder. Select Open command window here.
Reboot your device to bootloader mode. Do so by shutting it down. Then while the power is off, hold volume down and press the power button. Release these buttons when you see the big green Android.
In your command window, type the command: fastboot devices
Your device with it's serial number should show up on the list. If it does not there is a problem and you need to stop here.
If the device shows up, let's update it.
fastboot flash bootloader bootloader-flo-flo-04.02.img
<wait for it to finish>
fastboot reboot-bootloader
<wait for it to reboot>
fastboot flash system system.img
<wait for it to finish>
fastboot flash boot boot.img
<wait for it to finish>
fasboot reboot-bootloader
Done with fastboot.
At this point, enter recovery (TWRP) and wipe cache and Dalvik under advanced wipe.
Remember the SuperSU you downloaded earlier and put on your device for later? Flash that now.
Reboot, all done. Most of this is just juggling files around. If you have any questions ask.
You are wonderful aerowinder. This is just what I needed to go ahead. Thank you so much.
About your signature, it doesn't show the links when viewed in my Tapatalk version, but I went to the Web view and got it from there. (just FYI if others ask about your links).
is it possible to just flash the system img in fastboot? It's still the same bootloader, not updated? Could I just flash the whole zip by sideloading in adb and TWRP? Just a lottle confused. Thanks!
droider137 said:
is it possible to just flash the system img in fastboot? It's still the same bootloader, not updated? Could I just flash the whole zip by sideloading in adb and TWRP? Just a lottle confused. Thanks!
Click to expand...
Click to collapse
If you were already on 4.4.3, all you need to do is fastboot flash system.img, that is correct.
No, you can't flash that firmware zip in recovery.
thanks
Hi Aerowinder
Thanks again for the excellent instructions. Everything went like clockwork until it didn't ?......
I got to the point where I issued the command fastboot devices which did show the tablet serial number. But my next command to flash the bootloader img gave me the error:
Cannot open 'bootloader-flo-flo-04.02.img
(I had copy pasted the command from your instructions).
The subdirectory below the command window contains that file (one of 7 files)
Sorry. What should I do?
In case you need the info, the device screen showed
Fastboot mode
Product name - flo
Variant - flo 32G
Hw version - rev_e
Bootloader version - flo-04.02
Carrier info = none
Serial number - xxxx
Signing - yes
Secure boot enabled
Lock state - unlocked
Thanks again.
Aerowinder, you are not only an expert but an excellent teacher. Your instructions above should be a sticky.
I'm all done. Everything is fine.
The problem I had above was a file path problem. Not sure why you told me to open the command window in the parent folder. When I opened it in the folder containing the seven files all your commands worked fine. (Except for your last one where you had a spelling mistake: fasboot instead of fastboot).
Thank you very much.
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.
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?
I upgraded my phone to android EMUI8 and tried to install the RR 8.1 ROM but my device wouldn't boot up. Then I tried to reflash the stock system.img but it won't let me. I don't have TWRP on my phone but I can acces fastboot. Does anyone know what to do? Thanks in advance :^l
jetzecazemier said:
I upgraded my phone to android EMUI8 and tried to install the RR 8.1 ROM but my device wouldn't boot up. Then I tried to reflash the stock system.img but it won't let me. I don't have TWRP on my phone but I can acces fastboot. Does anyone know what to do? Thanks in advance :^l
Click to expand...
Click to collapse
What is it you mean , it won't let you. Does it give a message. Failed?
Are you at frp locked?
mrmazak said:
What is it you mean , it won't let you. Does it give a message. Failed?
Are you at frp locked?
Click to expand...
Click to collapse
Well when I try to flash the stock 8.0 system.img it gives me a "Invalid sparse file format at header magi" and when I try to flash TWRP it gives me a "FAILED (remote: partition length get error) I am frp unlocked by the way.
jetzecazemier said:
Well when I try to flash the stock 8.0 system.img it gives me a "Invalid sparse file format at header magi" and when I try to flash TWRP it gives me a "FAILED (remote: partition length get error)
Click to expand...
Click to collapse
Ok, that does not seem too bad, yet.
I suppose you are using system.img downloaded from web.
That image has given many that same error.
Best to use your system.img.
And the error flashing twrp, is common when using the nougat command or nougat recovery on Oreo.
Solutions.
Find your firmware on pro-teammt
http://pro-teammt.ru/firmware-database/?firmware_model=Bnd-&firmware_page=0
Then download update.zip
Extract files.
Get hauwei update extractor.
https://www.google.com/url?sa=t&sou...FjAAegQIARAB&usg=AOvVaw0xkKEyI85nY9x4Fjr1AWJl
Extract the system.img
Then fastboot flash it.
Recovery:
Oreo command== fastboot flash recovery_ramdisk twrp_ramdisk
Twrp name depends on version used. I use build 4 from here
https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447
mrmazak said:
Ok, that does not seem too bad, yet.
I suppose you are using system.img downloaded from web.
That image has given many that same error.
Best to use your system.img.
And the error flashing twrp, is common when using the nougat command or nougat recovery on Oreo.
Solutions.
Find your firmware on pro-teammt
http://pro-teammt.ru/firmware-database/?firmware_model=Bnd-&firmware_page=0
Then download update.zip
Extract files.
Get hauwei update extractor.
https://www.google.com/url?sa=t&sou...FjAAegQIARAB&usg=AOvVaw0xkKEyI85nY9x4Fjr1AWJl
Extract the system.img
Then fastboot flash it.
Recovery:
Oreo command== fastboot flash recovery_ramdisk twrp_ramdisk
Twrp name depends on version used. I use build 4 from here
https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447
Click to expand...
Click to collapse
Okay so I've downloaded the latest firmware for my model but when I try to extract the update.app inside of the update.zip file the huawei zip extractor gives me "RECOVERY_RAMDIS.img: Invalid header crc - Expected: 15200 Got: 44917
jetzecazemier said:
Okay so I've downloaded the latest firmware for my model but when I try to extract the update.app inside of the update.zip file the huawei zip extractor gives me "RECOVERY_RAMDIS.img: Invalid header crc - Expected: 15200 Got: 44917
Click to expand...
Click to collapse
yes there is a bug either in the extractor or the update files. they all do it. Go to the settings tab and take check mark off verify header.
mrmazak said:
yes there is a bug either in the extractor or the update files. they all do it. Go to the settings tab and take check mark off verify header.
Click to expand...
Click to collapse
I flashed the system.img but now the phone bootloops. It could be possible I got the wrong system.img because I don't know exactly what firmware my phone was on before I messed up. I only know it was EMUI8. Is there a way to completely reflash everything?
jetzecazemier said:
I flashed the system.img but now the phone bootloops. It could be possible I got the wrong system.img because I don't know exactly what firmware my phone was on before I messed up. I only know it was EMUI8. Is there a way to completely reflash everything?
Click to expand...
Click to collapse
Yes. I have guide thread here for that.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
But also wipe in factory reset from stock recovery may solve the bootloop.
mrmazak said:
Yes. I have guide thread here for that.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
But also wipe in factory reset from stock recovery may solve the bootloop.
Click to expand...
Click to collapse
Alright, I'll try that before I have a look at that thread
mrmazak said:
Yes. I have guide thread here for that.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
But also wipe in factory reset from stock recovery may solve the bootloop.
Click to expand...
Click to collapse
I tried rebooting to stock recovery in order to factory reset but it only shows me the update, power off and reboot options so no factory reset possibility. I read through the entire thread you linked here but I'm very confused as to what to do with the full OTA file. I'm on a broken EMUI8 that bootloops and I'd like to clean flash EMUI8 again so I can flash an AOSP Oreo rom after that. What do I do?
jetzecazemier said:
I tried rebooting to stock recovery in order to factory reset but it only shows me the update, power off and reboot options so no factory reset possibility. I read through the entire thread you linked here but I'm very confused as to what to do with the full OTA file. I'm on a broken EMUI8 that bootloops and I'd like to clean flash EMUI8 again so I can flash an AOSP Oreo rom after that. What do I do?
Click to expand...
Click to collapse
Just made updates to guide last night. I think it is worded simple now.
Download my update "package" from step E
Extract it to a folder on your PC.
You are on emui8, so copy the HWOTA folder from the extracted zip to your sdcard
Also put hwota-update-7-8-auto.zip on sdcard.
Put the three (3) update files from pro-teammt.ru in the HWOTA8 folder on your sdcard
Put card into phone
Boot into twrp
Select install
Choose sdcard as source
Install hwota-update-7-8-auto.zip
mrmazak said:
Just made updates to guide last night. I think it is worded simple now.
Download my update "package" from step E
Extract it to a folder on your PC.
You are on emui8, so copy the HWOTA folder from the extracted zip to your sdcard
Also put hwota-update-7-8-auto.zip on sdcard.
Put the three (3) update files from pro-teammt.ru in the HWOTA8 folder on your sdcard
Put card into phone
Boot into twrp
Select install
Choose sdcard as source
Install hwota-update-7-8-auto.zip
Click to expand...
Click to collapse
So far so good but the FULLOTA update file I got from that website only has one file (update.zip) Do I need to extract that? And if so, what 3 files do I put on my sdcard?
jetzecazemier said:
So far so good but the FULLOTA update file I got from that website only has one file (update.zip) Do I need to extract that? And if so, what 3 files do I put on my sdcard?
Click to expand...
Click to collapse
No do not extract it.
On that site, next to link for update file, is "file list"
Click this. It gives links for all three files.
Put those three zip files into hwota folder
mrmazak said:
No do not extract it.
On that site, next to link for update file, is "file list"
Click this. It gives links for all three files.
Put those three zip files into hwota folder
Click to expand...
Click to collapse
Alright, I got it! Now I need to flash TWRP but the executable to install TWRP says my adb drivers are outdated. I have the minimal fastboot and adb installation from XDA.
jetzecazemier said:
Alright, I got it! Now I need to flash TWRP but the executable to install TWRP says my adb drivers are outdated. I have the minimal fastboot and adb installation from XDA.
Click to expand...
Click to collapse
That should be fine.
Usually means you have other adb also , probably from other tool.
If you have twrp , not need to use the terp recovery installer
mrmazak said:
That should be fine.
Usually means you have other adb also , probably from other tool.
If you have twrp , not need to use the terp recovery installer
Click to expand...
Click to collapse
Well the problem is I don't have TWRP and none of the versions i've tried to install work. The installer doesn't work either, it says closing adb daemon and stays on that.
jetzecazemier said:
Well the problem is I don't have TWRP and none of the versions i've tried to install work. The installer doesn't work either, it says closing adb daemon and stays on that.
Click to expand...
Click to collapse
Each step of the tool I put pause.
So it stopped on command and not closed.
Press spacebar
mrmazak said:
Each step of the tool I put pause.
So it stopped on command and not closed.
Press spacebar
Click to expand...
Click to collapse
Dude, you're the man! I got my device up and running again. I'll probably stay on EMUI8 since it's more stable than the current AOSP rom. I wanna root it tho so can I just use the lazy recovery tool to install twrp and simply install magisk?
jetzecazemier said:
Dude, you're the man! I got my device up and running again. I'll probably stay on EMUI8 since it's more stable than the current AOSP rom. I wanna root it tho so can I just use the lazy recovery tool to install twrp and simply install magisk?
Click to expand...
Click to collapse
Yes.
The lazy tool has recovery with encryption working
I got it working on EMUI8 but I decided to flash the aosp rom cuz i prefer stock android. Can't seem to get twrp to install tho. I keep getting "1 was unexpected at this time"
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.