Hey guys!
This is my first ever thread on XDA! And my problem goes like
I have a Asus max Pro m2 device. And also I'm familiar with things like custom ROMs, custom recovery, rooting and all that stuff. I have been using custom ROMs, etc etc.. from a long time. And I use TWRP as my recovery system. Recently I tried to install lineage OS on my phone, but it gave me an error 7. Then I searched on google about what is error 7. Tried all the solutions, nothing worked. Then I thought it's happening because of my phone's modem. So I searched for the latest modem file for my device, then I got a file on XDA. And that was a TWRP backup file of the Modem and the EFS. So I downloaded it and restore the file through TWRP. And from there, I'm not able to install any custom rom on my device. I tried many of them but couldn't. All of them have me an error 7.
But before that everything was fine. I was in evolution X custom rom. And that file ruined my device completely. Now I'm completely helpless, clueless. So what to do. Any expert suggestions?
PLEASE RESPOND!!!
Hi, if you didn´t solve this problem watch this video that has the solution for asus zenfone max pro m2 brick devices. Keep in mind that when you do this, the phone gonna be with the first oreo version, relock bootloader and unroot your device so you have to uptade manually.
Copy the zip ROM file to your PC and unzip it using your favorite archiver (for example, 7-zip);
After unpacking find META-INF folder and go the META-INF/com/google/android line. In the last directory you will find two files called "update-binary" and "updater-script". We are interested in the latter one;
Rename "updater-script" to "updater-script.txt" and open it in any text editor (for instance, Notepad++);
Now remove the line starting with "assert" to the next semi-colon. Usually it is the first or a few first lines in the beginning of the text file;
Save the modified file;
Rename "updater-script.txt" back to "updater-script";
Update all files you have unpacked;
Copy the modified zip-file on your phone;
Reboot your Android device to recovery mode and try to update it again. Status Error 7 should be gone.
Related
http://forum.sdx-developers.com/index.php?topic=7108.0
On the original post by inxane he says to 2. Download the recovery and put it in C:\Program Files (Program Files (x86) if you are on 64 bit)\Samsung Electronics\SWUpgrade\Models\Binary. DELETE THE FILE ALREADY IN THERE OR YOU MAY PERMA-BRICK YOUR INTERCEPT...
Is the recovery just the cm01 tar file at the top because this link >http://www.sdx-downloads.com/devs/inxane/intercept/recoveryv14.tar can no longer be found.
sorry first time working with the intercept, i was going to try adb method but i heard the recovery goes away after you reboot.
From my experience, the CM01.tar file needs the recovery.rfs extracted. When you download SWUpgrade, you want to delete the file inside the Binary Folder and replace it with the recovery.rfs which happens to be Inxane's CM Recovery. The latest should be 2.5.1.0.
The reason it exists as a .tar file is becuse CM Recovery recognizes system files as .tar extensions. So if there was a case you wanted to reflash CM Recovery for some reason, you can do it inside CM Recovery so long as it's in the .tar container. Otherwise, you need the recovery.rfs file on the PC side.
From my experience, If you move CM01.tar to the Binary folder and run SWUpgrade, the upgrade won't start and it'll just hang.
alpha-niner64 said:
...the upgrade won't start and it'll just hang.
Click to expand...
Click to collapse
THANK YOU!!! I was wondering why it was hanging/just rebooting...
[Wrong link! My bad!]
I read that the Intercept can re-install it's stock recovery after rebooting the phone.
Recovery
Read this too
Basically someone is suggesting to just flash a root kernel (SlapKernel) with SW Upgrade. I'm going to try it out right now.
[EDIT] Flashing SlapKernel worked fine (and I wasn't rooted before...), and it's way more responsive so far. I suggest you follow these instructions
well,these days i got a secondhand mx2 CN version,but the things don't go like what i thought cause there's something wrong with the flyme accout,it always say locked, but i don't have a passcode to unlock it. the chinese seller didn't mention this either.
so i just want to flash the phone a new rom with the BL locked,all my plan is like that:
1.extract the update.bin with the bin2zip tool,has finished
2.write the root access to the system,which contains superuser.apk and su file. finished.
3.unpack the recovery-uboot.img(i don't know which tool can do this:crying&modify the sbin\recovery file to skip the code check.then pack it back,making a new ing file. unfinished (as there is no tool for unpacking)
4.pack all file to a zip rom and transfer it 2 bin file ,flash back.
i have tried many times without the img file changes,the rom can be read by the phone,but it will crash at about 30% for the first check.
so i just want to know is there anyone has ever done this and did u got a tool to unpacking the recovery-uboot.img file,thk
hi sir, did you manage to flash custom rom on your meizu mx2 cn version?
I wonder whether there is help for someone who thought he knew how to flash a kernel but apparently is deluded. I have the original nexus seven Wi-Fi tablet android version 4.3 build number JWR66V. The system still wants to update me to 4.3 because I ripped some files out of the cache directory to prevent OTA updates. I have both fastboot and adb. I have read the stickies about flashing.
The phone is rooted and the bootloader is unlocked. I use TWRP custom recovery, and it's a good thing, because I solidly bricked myself up just trying to get my lollipop. I know there are tools to root a nexus seven even with stock lollipop, so I thought I'd upgrade my phone to stock lollipop and then use one of those methods. I tried both the stock lollipop kernel and the one provided by chain fire, which I understand is rooted already. (I'm assuming upgrading to lollipop will lose me my root, unless I want to recover back to 4.3.)
I tried to do these things a couple of different ways. When I tried fast boot, I got the message "error: neither -p product specified nor ANDROID_PRODUCT_OUT set". There was a YouTube video suggesting how to deal with this error message. I'm pretty sure I followed the instructions but no go. (I was using the "flash all" command.) This was after I had put the file containing lollipop in the directory, both zipped and unzipped (so that I had an .img file instead of a zip file). I tried using both the zip file with all of the lollipop partitions and the system image file individually. No go. I also had a message that android-info.txt could not be found, even though it was in the same, working directory.
I could be wrong but I don't think you can install a complete updated kernel from a file on the device. I think that works only with update.zip.
I'm still thinking fastboot is my best bet, but there are dependencies apparently and I don't know what files to include in its directory. Then, am I wise to go to stock and then root, or should I simply flash the stock kernel already rooted? I assume that's what chainfire is providing, correct?
I notice the lollipop official ROM nor Chainfire’s supposedly-rooted image have any file named nakasi. I have only .img files, no .zip files.
I found a dozen sets of instructions on how to flash a kernel but something I need is missing from all of them. Does anyone know what it is or can anyone offer some helpful advice?
Thank you,
Leon M.
I am trying to flash an image onto a zenfone 5 using the recovery. I have tried sideloading and also pushing the zip to the SD card. It just seems to hand randomly.
I then tried checking the uploaded zip file (to /sdcard) by running md5um on it and the value changes each time I run md5sum. I have tried a few versions of the TWRP recovery and the all seem to have the same problem. Is there one that works?
I just rooted my friend's Zenfone 5 with an auto installer. Here's the link on google drive LINK . Just extract the zip and follow instructions in the "help file.txt". It's a script that automates all the commands. I don't remember where I got this from, but if someone else knows, please link the original for credits.
Hello.
I'm trying to get my phone back to stock rom.
I'm using the TWRP from the [All In One] post: https://forum.xda-developers.com/re...overy-unofficial-twrp-touch-recovery-t3921637
And I'm trying to install the file I got from: http://en.miui.com/download-360.html
But when I flash the file (miui_LAVENDERGlobal_V10.3.5.0.PFGMIXM_a5cabeca22_ 9.0.zip) I get the error attached.
Can anyone help me with this error?
Download the zip file again from miui.com, if you’re using a custom rom go to ‘Wipe’ -> ‘Advanced Wipe’ and wipe the ‘Cache’, ‘Dalvik/ART Cache’, ‘Data’ and ‘System’ partitions.
Once you are done, go back and tap on the ‘Install’ button and browse the rom file.
If this doesn't work, try the fastboot method with the miui flash tool.
delete compatibility.zip in rom file and flash normally
Thanks for the replies. I already formatted and wiped, and tried redownloading the stock rom file, but got the same error. I also tried the MIUI flash tool but got an error after doing the last step.
However... I did end up fixing the problem moments ago.
As I was leaving work, a nerd directed to a wepage that had instructions that worked:
https://www.androidexplained.com/redmi-note-7-unbrick
16. May 2020: the tip: unzipping - deleting - zipping and flash that new file worked for me also. Redmi Note 7 Lavender; Rom Lineage 17.1 20200215. Very nice. Ernest from Germany
FligMupple said:
Hello.
I'm trying to get my phone back to stock rom.
I'm using the TWRP from the [All In One] post: https://forum.xda-developers.com/re...overy-unofficial-twrp-touch-recovery-t3921637
And I'm trying to install the file I got from: http://en.miui.com/download-360.html
But when I flash the file (miui_LAVENDERGlobal_V10.3.5.0.PFGMIXM_a5cabeca22_ 9.0.zip) I get the error attached.
Can anyone help me with this error?
Click to expand...
Click to collapse
Why not orangefox?