Related
Hi A7 users,
Let's start this off be saying, bare with me English is not my primary language.....
OK now, the reason for this Thread is to find a definite solution for current users and future users who have run into boot issues cuz they were trying to :
A- Go back to Un-rooted and lock bootloader state.
B- Started Playing with root tools and make a huge mistake
C- Started playing with twrp not knowing what they were doing
D- All the above + started flashing images files and got worts.
E- Any other type of situation.
I Know we make mistakes and we learn from them and well here today we are going to try or rather say Find a permanent /define solution to all this issues with your help, so PLEASE ONLY POST IF YOU HAVE RUN INTO ANY OF THIS ISSUES AND HOW YOU GOT INTO THE ENCHILADA ( MESS ) .
If you have the solution to your previous boot problems send me a PM and I'll keep this Thread updated for everyone to see with your solution and of course credit to the user/s.
NOTE : Please mention which Axon 7 you are using e.g. :
- A2017 (Chinese Variant)
- A2017U (USA Variant)
-A2017G (UK/Europe/International Variant)
reserve 1
reserve 2
reserve 3
reserve solution 4
reserve solution 5
Anyone this issues please post you issue, how to got into the problem, device model and if you got it fix let us know.
https://www.youtube.com/shared?ci=05LD4Ja-h3k
You'd think with all the other posts about problems there'd be something here by now.
Always thank those who are helpful...and just ignore those who aren't.
Mine happened when I wiped Internal storage from twrp. This caused the phone to only see 4gb of internal storage. Came to xda and it was suggested to flash back original boot.img. once that was done 4gb issue was fixed and the radio was gone.
I did indeed try every solution offered (thanks again for all the effort, DrakenFX and others). But, I've come to the conclusion that this is not going to get fixed until XTE releases US images. For other people's sake I hope I am wrong, but I myself decided to proceed with the exchange where I bought it, as I was right at the end of my 14 days (newegg doesn't seem to give the 30 days that xte does). I may be out of an Axon 7 for a while, so for now I am on my amazon ads, Blu R1 HD (with ads defeated
Is there a guide to go back to stock for the A2017G?
i'm on B02 with root and the bootloader still locked.
Like to go back to stock now that ZTE is working on an update to give the A2017G an unlocked bootloader.
Hi all,
I am currently experiencing a bootloop on my Chinese Axon 7. Some of you regulars may have seen me asking in other threads because I've tried to fix it myself, but I've kind of run out of options. Sincerely hoping one of you can help me out!!! I'll buy the winner a beer or 2, haha!
Back story:
Was on B07 with root (tenfar's tool) with locked bootloader and had some issues with the ROM. Like vibrating when I opened the camera and battery drops. So I decided to upgrade to B09. Placed the OTA on SD card and went to: Settings -> update. Worked fine. So I connected it to my PC and made a dump (tenfar's dump tool) of my recovery and boot and stored them. Then I ran the Tenfar's tool, the B09 version and it went like the last one. But when I booted I didn't have wifi, and other issues came up. So I thought: did I make a mistake? So I read it again, checked the COM port again... all checked out. And used Tenfar's tool again. After that it didn't even boot anymore! It plays the nice boot animation and then gets stuck on the end screen with all the pictures.
So after that I restored my dumped recovery.img and boot.img. This is when I knew something was wrong: it still didn't boot! I reset data/cache in the stock recovery: no boot. Still stuck at the end of the boot animation.
What I've tried:
- Flashing the stock B09 update.zip with TWRP.
- Flashing the stock B09 update.zip without updater-script 'assert' and 'get-prop' line. TWRP says 'update.zip is corrupt'. Doesn't install.
- The I put it on SD card and internal memory and tried updating it with stock recovery: 'sorry you cant sdcard upgrade'. That's all it says.
- ADB sideload stock recovery: 'cannot load update.zip'.
I tried different ADB versions, Windows and Mac, different drivers... I tried formatting SD card as FAT32.. Tried different SD card.. Doesn't make a difference.
TWRP log says it can't pass the Zip verification when I try that. If I turn that off it says re.product.name is wrong. But I checked build.prop and updater-script. It's the same! But somehow TWRP comes up with a different one. Also tried removing getprop and assert lines from updater-script. But then it says: ZIP file is corrupt.
TWRP log after trying original, stock B09 flash:
http://pastebin.com/cJivE2TK
Build.prop: moved from /system with TWRP:
http://pastebin.com/b6rryc2n
Build.prop: ro.product.name=P996A03
Updater-script:
Code:
getprop("ro.product.device") == "ailsa_ii" || abort("This package is for \"ailsa_ii\" devices; this is a \"" + getprop("ro.product.device") + "\".");
assert(getprop("ro.product.name") == "P996A03");
But TWRP log: ro.product.name=cm_ailsa_ii
So, yeah, I've been trying on and off for the past couple of days in between work and travelling. Got a back-up phone so it's not that bad. But I really like this phone! It's just been such a pain in the ass the past few days...
I tried researching online and reading all the XDA posts. It is my fault this has happened and feel such a newb for not being able to fix it myself
Many thanks in advance!
aPexalpha said:
Hi all,
I am currently experiencing a bootloop on my Chinese Axon 7. Some of you regulars may have seen me asking in other threads because I've tried to fix it myself, but I've kind of run out of options. Sincerely hoping one of you can help me out!!! I'll buy the winner a beer or 2, haha!
Back story:
Was on B07 with root (tenfar's tool) with locked bootloader and had some issues with the ROM. Like vibrating when I opened the camera and battery drops. So I decided to upgrade to B09. Placed the OTA on SD card and went to: Settings -> update. Worked fine. So I connected it to my PC and made a dump (tenfar's dump tool) of my recovery and boot and stored them. Then I ran the Tenfar's tool, the B09 version and it went like the last one. But when I booted I didn't have wifi, and other issues came up. So I thought: did I make a mistake? So I read it again, checked the COM port again... all checked out. And used Tenfar's tool again. After that it didn't even boot anymore! It plays the nice boot animation and then gets stuck on the end screen with all the pictures.
So after that I restored my dumped recovery.img and boot.img. This is when I knew something was wrong: it still didn't boot! I reset data/cache in the stock recovery: no boot. Still stuck at the end of the boot animation.
What I've tried:
- Flashing the stock B09 update.zip with TWRP.
- Flashing the stock B09 update.zip without updater-script 'assert' and 'get-prop' line. TWRP says 'update.zip is corrupt'. Doesn't install.
- The I put it on SD card and internal memory and tried updating it with stock recovery: 'sorry you cant sdcard upgrade'. That's all it says.
- ADB sideload stock recovery: 'cannot load update.zip'.
I tried different ADB versions, Windows and Mac, different drivers... I tried formatting SD card as FAT32.. Tried different SD card.. Doesn't make a difference.
TWRP log says it can't pass the Zip verification when I try that. If I turn that off it says re.product.name is wrong. But I checked build.prop and updater-script. It's the same! But somehow TWRP comes up with a different one. Also tried removing getprop and assert lines from updater-script. But then it says: ZIP file is corrupt.
TWRP log after trying original, stock B09 flash:
http://pastebin.com/cJivE2TK
Build.prop: moved from /system with TWRP:
http://pastebin.com/b6rryc2n
Build.prop: ro.product.name=P996A03
Updater-script:
Code:
getprop("ro.product.device") == "ailsa_ii" || abort("This package is for \"ailsa_ii\" devices; this is a \"" + getprop("ro.product.device") + "\".");
assert(getprop("ro.product.name") == "P996A03");
But TWRP log: ro.product.name=cm_ailsa_ii
So, yeah, I've been trying on and off for the past couple of days in between work and travelling. Got a back-up phone so it's not that bad. But I really like this phone! It's just been such a pain in the ass the past few days...
I tried researching online and reading all the XDA posts. It is my fault this has happened and feel such a newb for not being able to fix it myself
Many thanks in advance!
Click to expand...
Click to collapse
PM I'll help you create a flashable zip base on B10 (Full update release), just make sure to have the following apps:
- 7Zip
- Notepad++
I am was rooting my axon a2017 on b10 chinnese version without any backup after rooting got password screen after boot then i was do factory reset and format data and all looking good but after that i saw that i dont have google play app so i installed macro gapps 6.0 after flashing phone stuck on axon screen (after zte logo) for long time i been wait up to 30 minutes and nothing was done..also i have the message on twrp about the modification(dont understand why i have this message all the time) i saw in xda forum that need to install supersu so i search on internet and was flash super su 2.65 and then when i am was boot device go to zte logo screen and then turning off when i connect the device as mtp device named as a2017u (whats worng with it??? I was flashed b10 root boot.img)
I regret about this root and want to back all to stock without any problems need help from someone
I need stock b10 boot.img if someone can upload
Many thanks!
---------- Post added at 04:23 AM ---------- Previous post was at 04:11 AM ----------
DrakenFX said:
PM I'll help you create a flashable zip base on B10 (Full update release), just make sure to have the following apps:
- 7Zip
- Notepad++
Click to expand...
Click to collapse
Its will help me too i think
Dear All,
ZTE Axon 7 A2017 (Chinese version) Stuck on Bootloader mode.
Device after power on will Stuck on ZTE logo even power button press longer also will Off and came back to square one and the only way to power off is via selection on bootloader page via volume button which consists of Recovery mode, Power Off, Bootloader and some other mode which I can't recall.
History of this issue. Please bear with long story.
Manage to install MM ROM with B13 via sd card installation via update software in phone setting. follow by Unlocked bootloader and Install TWRP 3.1.1.0 then try few different ROM until one day when I use Xiaomi flashtool my PC crash half way through during flashing resulting in device with Pure Chinese ROM and TWRP also got corrupted, when I said corrupted because I install TWRP 3.1.1.0 but when I go to Recovery mode it shows TWRP 3.0 something. with this corrupted TWRP when I try to install ROM it will show loading but end result is NIL meaning same ROM nothing change.
Until this stage I never did a TWRP backup because all this while the ROM is Not my type of ROM from this junction when I boot back to TWRP and I did Advance Wipe most of it except external sd card thinking that I may be able to install fresh TWRP but my Recovery TWRP is residing in phone storage resulting in No more TWRP recovery software. next thing I did was I connect phone to PC and ran adb fastboot tool to detect device and managed to detect device in recovery mode and I make decision to Locked back the bootloader and did just that and Locked bootloader is Succes and it also Erased everything during the process.
To cut short the story after Locked back bootloader only Bootloader mode is accessible and when I connect to PC and enable Recovery mode (Black screen) and EDL mode (Black screen) from Windows PC Device Manager COM port able to see Qualcomm 9008 for this 2 mode.
I must admit after few days of trying to resolve this Stuck Bootloader issue I almost give up.
Then I remember this Woodo magic by jcadduno which recommends XM flashtool version 2016.08.30.0 but unable to flash after trying few version Xiaomi flashtool and the very latest and I mean from Xiaomi Flashtool webpage http://xiaomiflashtool.com/
version 20170425 that break the ice and finally able to load A2017U ROM because this US ROM my phone No Network detected.
From here onwards I unlocked bootloader and install back TWRP (Installation of TWRP via Axon7toolkit) because of Network issue since I got TWRP I install back A2017 ROM but still Not satisfied because Chinese ROM certain Apps having issue because of Google services and I chance upon this Conversion A2017 to A2017U ROM (Hybrid ROM caused ROM is US and Modem from Chinese Modem)
that I'm stay put right now and my phone now is A2017U model.
I hope this experience can help others with similar Stuck bootloader and those who wish to convert A2017 to A2017U ROM.
below is the link that I described Woodo magic.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Straight forward Axon7toolkit, please don't use Chrome browser cause Chrome will Automatically Delete it after complete download for my case I used Microsoft Edge.
https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
below is the link to Hybrid ROM for A2017U
https://androidfilehost.com/?fid=457095661767154458 by Michael Warner After flash install No verity patch for the bootloader.
Cheers.
I am stuck in a position where I can restore my nandroid backups but get Error 7
when trying to reinstall any Rom on a2017u I was able to fix the unlocked bootloop
by the EDL method. The Rom's are the same as the backups. I think I tried to role back to B29 Causing the bootloop) and have had problems ever since.
Should I try flashing A2017Uv1.1.0B32_Bootstack_by_DrakenFX since the Rooms are all B32?
The B15 and B19 Nandroid's still Restore fine.
Hello all,
i don't get onto forums very often but i thought this was a nice one to add to. i've rooted a few motorolas, a few ztes, a cat; i've also bricked those ztes, cat & a few samsungs. i'm dealing with two Axon7U's; one is factory MM-b29, the other is N-b35.
while screwing around with TWRP, i bricked the b35 (the b29 has been bricked for a month at this time) after i had it almost perfected. by perfected i mean a custom recovery & root user access fully acquired. with DrakenFX's {YOURS; thanks so much. i'm learning to get along with linux} extensive files created to save people from themselves i was able to unbrick the b35. albeit its CELLULAR DATA became unhinged; that's something i could've lived with except it was a loaner and had NO CAMERA! it's camera (along with the ability to push both volume buttons at once for say EDL mode...) was damaged having been beaten across a steering wheel several times. so with my newfound unbricking superpowers i decided to take another crack at the b29. managed to get it unbricked but couldn't get it setup with both TWRP & SuperSU without losing one, the other or, both. at times it didn't even boot up. i was doing pretty much everything cited above for reasons 'why'. best way to learn is by trial & error (if one can afford it).
the b29 is rooted right at this moment; i'm working on it as soon as i leave this posting. i used Axon7_EDL_Tool. i used Axon7root. i used MiFlash. i used Fastboot. I used ADB App Controller software too. back & forth i fought for three days mostly due to downloading glitches and i prevailed. i manipulated a stock OTA full system update.zip by happenstance and it Auto_Updated over itself. in other words it already had the same ROM installed. i don't know what it tested to realize it needed to update to what it already had. it didn't have CELLULAR DATA either. just like the b35, it broke somehow while flashing TWRP or SuperSU. funny thing is it still wanted to update that same ROM after it did. while perusing the system update setting(s) i noticed it had downloaded N-b15 and it wanted to update b29 AGAIN! i opted for the Nougat update. it did alright and appears to have fixed it's CELLULAR DATA too. i haven't looked at it since but i'm confident i can gain root user access with a minimal amount of effort.
The main problem i've had with dealing with bricked devices is the age of the file downloads. most of them are simply GONE!, expired links and whatnot. if i'd had a clear path say from a custom recovery and rooted boot image of my factory version or the path that leads to it, i'd have been fixed up long ago. i've found partial 'paths' if you will that almost get me there but no quite all the way. flashing images & zips through fastboot are different from their counterparts entered through TWRP or Emergency Download Mode which of course are both different too. three different ways to get into one's phone makes it almost impossible to keep them perfected.
i'm not sure i did what i'm supposed to regarding this thread. Thank you DrakenFX for your time & knowledge; you've saved my old Axon7!
Hello all update;
b35 Nougat phone is retired. b29 managed to update itself to b35 7.1.1. however, its CELLULAR DATA is still broken. i haven't managed to figure out how or where it's broken so i cannot fix it.
what i'm trying to do now is flash Magisk instead of SuperSU and using a TWRP version 3.0.3-1. heck i've used all of TWRP's versions in my efforts to reacquire CELLULAR DATA.
crazy part is the phone knows its CELLULAR DATA carrier and freely displays all of its hookup info. this is very frustrating.
Since, the release of the Android M. Google make it hard to root your device. On MIUI 8 with marshmallow I have been trying to figure out a way to root my device. In almost every case I found myself in a boot loop. So after a long work i finally succeed to root my redmi note 3 with no error and bootloop.
I am not responsible for any damage to your devices,loss or damage caused, or alleged to have been caused, directly or indirectly, by the informations or ideas suggested or referenced, etc. If you get a boot loop you can get back to booting by simply flashing the stock "M" system image via fastboot. or Mi flash tool.
Please try at your own risk. Your warranty is now void.
PRE-REQUIREMENTS
1. redmi note 3 ( SD only) with official MiUI 8 6.9.9 developers rom (marshmallow update) :good:
2. officially unlocked bootloader.
3. TWRP recovery ( alka twrp recommended ).
4. patched boot image given below.
5.brain
METHOD RECOVERY METHOD.
1. Download boot.zip and SuperSu.zip
superSu.zip -https://www.androidfilehost.com/?fid=24727369092694142
boot.img - https://www.androidfilehost.com/?fid=24727369092694141
2. copy both the files (boot.img and SuperSu.zip) to your external SD card.
3. now reboot the device in recovery and go to mount section and mount all the partitions.
4. now go to install and go to SD card and flash SuperSu.zip.
5. as the super su is installed go back in install section and select install image.
6. now you will see only .img files so locate to boot.img and select it.
7. In next window you may see two option as " select partition to flash image:" select the first one option BOOT partition and slide the installation slider and reboot your redmi note 3 SD
boot up may take 5-10 mins so don't we panic. and please mention in the comment was it worked for you or not so I can edit boot image for you..
if i help you give me a thanks, by clicking on thanks button
I am on Miui8 6.9.15 Marshmallow, used supersu.zip, boot.img for rooting..., successfully rooted but some times when I restart the device network gone, sometimes bootloop is occurring.. So I need to flash boot.img again and again.. This is taking a lot of time.. What to do?
Just flash supersu stable using ZCX twrp. Head over supersu xda thread for latest stable flashable zip. Worked for me without any issue.
ubaid137 said:
I am on Miui8 6.9.15 Marshmallow, used supersu.zip, boot.img for rooting..., successfully rooted but some times when I restart the device network gone, sometimes bootloop is occurring.. So I need to flash boot.img again and again.. This is taking a lot of time.. What to do?
Click to expand...
Click to collapse
this boot image is only stable with MIUI 8 6.9.9. i am currently working on a universal boot image so no encryption problem occurred... please wait thanks
tsrajput said:
this boot image is only stable with MIUI 8 6.9.9. i am currently working on a universal boot image so no encryption problem occurred... please wait thanks
Click to expand...
Click to collapse
Also my wifi is not working after root..
Does AUX issue resolved in this ROM?
Yet nobody have solution on it hence; i asked.
Headphones work but AUX cable is not working.
Satav said:
Yet nobody have solution on it hence; i asked.
Headphones work but AUX cable is not working.
Click to expand...
Click to collapse
This is not a rom, its a rooting guide.
any news on this ? any new boot.img. I'm on 6.9.22 beta. thanks
The final steps to Remove "Vendor ROM" that does not have the Update Option in Settings Or Unbrick Le Max 2 or simply Update Le Max 2 to latest EUI.
NOTE: This method should address the following weird problems:
1. Le Max 2 TWRP Seeing 0MB in Internal Storage. Unable to access the ROM Storage
2. Encrypt Option Greyed Out In Settings-->Fingerprint and Security
2. Update Option missing in Settings.
3. Fingerprint Sensor not working... If it still gives trouble... Calibrate the FP Sensor in its settings. Or register the same fingerprint multiple times.
This method should work on ALL versions of Le Max 2 including X820 X829 X821
Before starting... Remove ALL USB peripherals that might interfere with the process. Use USB Ports on the PC/Laptop... DO NOT use USB Hubs... Even if the phone appears dead... Connect it Power Outlet and let it charge for an hour.
1. Download the latest Stable EUI... from LeEco Website Directly .
2. Download the FlashOne v1.9 And Service ROM From HERE.
UPDATE: FlashOne v2.0 has been released! Here's the LINK.. It is a bit more advanced and offers the ability to format User Data for a Cleaner Flash
3. Download Qualcomm Drivers
4. Put Le Max 2 in EDL (Emergency Download Mode) by pressing Volume +, Volume - and Power Button Simultaneously. For those having difficulty..... Here are few tips.
Connect the Phone to PC. If the phone is Switched/Powered On... Then Power Off the phone and Switch Back On with the Key Combinations.
OR
If the Phone is Switched Off... Then Use the Key Combination to put the phone in EDL Mode..
In either case..... the PC will make a sound of Disconnection and Reconnection of an USB peripheral. AND you will see Qualcomm QDLoader 9008 Driver Installation. To verify the same... go to Device Manager in Win 7 / Win 10 and Under Ports (Com & LPT)... you should see Qualcomm HS-USB QDLoader 9008 (COMXX).. The XX corresponds to a particular COM Port. Remember this port.
5. Once the Le Max 2 is in Qualcomm QDLoader 9008 EDL Mode... Start the FlashOne Software.
6. Choose “Qualcomm – flash dead phone” from the drop down menu next to “Flash type”.
7. Click “Refresh button” next to “Select Device”. Here your Le Max 2 will show up but in COM Number (ComXX)
8. Browse for our Qfil/service ROM by clicking “Select File”.... You can technically select the Latest EUI ROM... But it is safer with Service ROM. DO NOT Unzip the ROM File.
9. After everything is set up under “Settings”, Press “Flash” button.
10. Installation can take anywhere between 10 to 20 minutes. Have Patience.
There are chances that the Flashing might fail. In case it does... Simply put the phone in EDL Mode again... and restart the procedure.
11. After the FlashOne confirms successful flash... Wait for 15 - 20 seconds. Then Power On the phone by pressing the Power Button for at least 60 seconds. Do Not Panic due to the long press.. Press it until the phone vibrates.
12. The Le Max 2 should be in Developer Version of EUI with an unlocked Bootloader and STOCK recovery.
13. The Developer ROM has the “Format Virtual SD card” setting in Settings Menu--> Backup/Reset--> Factory Reset.. Use the setting to get back the 50+GB
[You can also use the option Format Data in TWRP Recovery instead and the partition will 64GB correctly instead of 10 GB initially. Read ahead for the procedure]
14. Once you have a working Le Max 2... there are two directions:
Install Latest Stable EUI ROM... with Update Option
OR Install TWRP Recovery / ROOT / Custom ROM
15. a. For those who wish to install Stock ROM... Simply rename it to "update" (DO NOT Add .zip... Else the file will look like update.zip.zip) and place the update.zip file in ROOT of the phone. Thereafter Switch Off the Phone... Enter Recovery by pressing Volume + and Power Button... Choose Update System AND the other setting to Clear All Data. Your Le Max 2 should update without any error.
15. b. For those who want TWRP and ROOT:
* Download the latest TWRP (For Le Max 2) and SuperSU from their respective websites. Download and Install ADB and Fastboot From HERE.
* Copy the SuperSU Zip File to the ROOT of the Phone.
* Unzip and Rename the TWRP recovery to Recovery (The file should be Recovery.img.... NOT Recovery.img.img)
* Put the Le Max 2 into Fastboot Mode By Pressing Volume - and Power Button
* Go to the ADB Install Folder and Press Shift & Right Click to get & select “Open command window here“. Confirm Fastboot is working by Entering Command: Fastboot Devices.. You should see a random string of letters followed by the word Fastboot. If you do not see the same..... the installation didn't complete successfully.
* In the Command Window.. Type: fastboot flash recovery recovery.img
* Enter the following Command: fastboot boot recovery.img
* Once the Phone has entered the Recovery... Flash the SuperSU Zip file and you will have ROOT capabilities.
* Take FULL Backup of your device and then install ANY Custom ROM.
Do let me know your results.
[Update]: There's a simple method you could try to get the Update Option Back in Le Max 2 Phone that arrived with Vendor ROM... Using the default File Manager Tap on the Update.zip file and select Upgrade Option. This will force the phone to Update using the ROM file. This method is for people who could not update through the Stock Recovery and received Errors.
After QFil/flashone my lemax2 still bootloops. I've tried flashing other roms via recovery but it reboots mid installation.
Any advice?
Try Another QFil / Service ROM
Yisheng said:
After QFil/flashone my lemax2 still bootloops. I've tried flashing other roms via recovery but it reboots mid installation.
Any advice?
Click to expand...
Click to collapse
My advice is try another Qfil. These files are quite large and hence the one you downloaded might have some corruption.
Try THIS File
Hi, the link to the Leeco website is down...is there any alternative for downloading the latest stable EUI?
I downloaded the 23s from another website, renamed "update" but when I try to update via recovery it fails, cause: corrupted.
Any suggestion on this?
Thanks a lot in advance
ermonnezza said:
Hi, the link to the Leeco website is down...is there any alternative for downloading the latest stable EUI?
I downloaded the 23s from another website, renamed "update" but when I try to update via recovery it fails, cause: corrupted.
Any suggestion on this?
Thanks a lot in advance
Click to expand...
Click to collapse
You may try to use twrp to flash it, you downloaded version is a twrp backup version...
Thanks for the suggestion but I'm trying to get back to stock for other phone issues... So I wanted to avoid to install twrp, if possible.
Any link to a stock rom that can be updated via stock recovery?
You know I just going to blame Android 7.0 Nougat any chance we can have a CyanogenMod 13 6.01 based foxfi friendly ROM ?
ermonnezza said:
Thanks for the suggestion but I'm trying to get back to stock for other phone issues... So I wanted to avoid to install twrp, if possible.
Any link to a stock rom that can be updated via stock recovery?
Click to expand...
Click to collapse
I used the 23s from this link: https://bbs.le.com/zt/eui/le_max2.html
I flashed it from an indian rom. It will change your bootloader to chinese, though (not really an issue). And your recovery too, I guess (don't panic, it's bilingual). It will also update /firmware, and that should help with many issues.
However, there's no need to flash TWRP in order to use it: you can just boot it ( fastboot boot TWRPname.img).
At the last step, my indian rom is not getting flashed. Saying corrupted!!. Yesterday I updated with the same (rom) file from the system updater when I did not root the device.
"[Update]: There's a simple method you could try to get the Update Option Back in Le Max 2 Phone that arrived with Vendor ROM... Using the default File Manager Tap on the Update.zip file and select Upgrade Option. This will force the phone to Update using the ROM file. This method is for people who could not update through the Stock Recovery and received Errors."
Following these steps got the same error.
Edit: I am pretty much sure the developer chinese rom has the issue. It does not let you update with the Indian rom. Pretty bad.
Did anyone succeed to flash the indian rom the phone came with, or any indian rom from these chinese developer rom?
---------- Post added at 03:52 AM ---------- Previous post was at 03:15 AM ----------
BTW, the indian latest stock rom 5.8.019s can not be download from anywhere now. Can you give me a link that works now?
deltasata said:
At the last step, my indian rom is not getting flashed. Saying corrupted!!. Yesterday I updated with the same (rom) file from the system updater when I did not root the device.
"[Update]: There's a simple method you could try to get the Update Option Back in Le Max 2 Phone that arrived with Vendor ROM... Using the default File Manager Tap on the Update.zip file and select Upgrade Option. This will force the phone to Update using the ROM file. This method is for people who could not update through the Stock Recovery and received Errors."
Following these steps got the same error.
Edit: I am pretty much sure the developer chinese rom has the issue. It does not let you update with the Indian rom. Pretty bad.
Did anyone succeed to flash the indian rom the phone came with, or any indian rom from these chinese developer rom?
---------- Post added at 03:52 AM ---------- Previous post was at 03:15 AM ----------
BTW, the indian latest stock rom 5.8.019s can not be download from anywhere now. Can you give me a link that works now?
Click to expand...
Click to collapse
It is the link of stock Indian eui 5.8.019s
https://drive.google.com/file/d/0BymbvUDXUaNlTjN6X0g1ME1helk/view?usp=drivesdk
Akashsundar said:
It is the link of stock Indian eui 5.8.019s
https://drive.google.com/file/d/0BymbvUDXUaNlTjN6X0g1ME1helk/view?usp=drivesdk
Click to expand...
Click to collapse
Yes
Akashsundar said:
It is the link of stock Indian eui 5.8.019s
https://drive.google.com/file/d/0BymbvUDXUaNlTjN6X0g1ME1helk/view?usp=drivesdk
Click to expand...
Click to collapse
Thanks a lot
Have any one flash this ROM
If there is any bugs reply here I will prepare fix for it
Hello...
Where can I find the original rom for le max 2 x820 with no system update please
thanks .
http://g3.letv.cn/218/24/9/letv-hdt...1S-5.9.020S.zip?b=123456&platid=5&splatid=500
Is 23S whit recovery stock.
Ok so I did as said in your post, but big problem for me : My screen is not split in two and both side are reversed.... I tried install roms goind thought twrp the problem is the same, and doing the manipulation all over again trough flashone doesn't solve my problem either. I really need someone's help on this one please.
x820 64g 6g
---------- Post added at 04:23 PM ---------- Previous post was at 04:22 PM ----------
Akashsundar said:
Have any one flash this ROM
If there is any bugs reply here I will prepare fix for it
Click to expand...
Click to collapse
I do have problem (see the post right above). Any Ideas?
Ok so, I did as shown in the topic : https://forum.xda-developers.com/le-max-2/help/flash-eui-rom-fastboot-t3525831
download twrp (The one I know didn't had the touchscreen issue)
boot from twrp (wish I had know about it before!)
upload zip file to /sdcard ( here's the catch, while in TWRP in don't have access to adb, the phone doesn't connect to pc or I don't know even I mount it, could be me. So i just put the archive at the root of the phone before booting to twrp from adb)
install rom
reboot
And ... it's ****ING WORKING!*
Really big thanks to ThE_MarD for his help!
HI, i hv the same problem likes yours with split screen.
Possible to share the steps how you manage to solved it.
Update:
Hi, I just managed to resolved it.
Download the given recovery 19S and save it on a USB drive.
Run twrp and press button wipe as our screen is reversed.
Then look for the file at external drive USB.
Just install it and once it is done..... the screen will return to normal
deltasata said:
At the last step, my indian rom is not getting flashed. Saying corrupted!!. Yesterday I updated with the same (rom) file from the system updater when I did not root the device.
"[Update]: There's a simple method you could try to get the Update Option Back in Le Max 2 Phone that arrived with Vendor ROM... Using the default File Manager Tap on the Update.zip file and select Upgrade Option. This will force the phone to Update using the ROM file. This method is for people who could not update through the Stock Recovery and received Errors."
Following these steps got the same error.
Edit: I am pretty much sure the developer chinese rom has the issue. It does not let you update with the Indian rom. Pretty bad.
Did anyone succeed to flash the indian rom the phone came with, or any indian rom from these chinese developer rom?
Click to expand...
Click to collapse
Hi.
Yes. After "QFIL", i also didn't update my device from DEV ROM with any Stock ROM (Indian or Chinese versions) by "upgrade.zip" without get the "corrupted file" error. So by TWRP, i installed 16S Indian Stock ROM -- TWRP informed that i have "no OS installed" but i proceeded and restarted from TRWP. It initialized the new ROM, and after the first setup, i restarted the device to complete any system operations after the first boot, and i updated the device with the Indian 19S with the EUI updater ( tapped "upgrade.zip" file). The device now have the stock recovery and boot in english (not chinese), and the EUI in all languages available on "India 19S Stock ROM".
Stock ROMS:
Le Max 2 All Official Stock Firmware links
Best regards.
NextGear said:
Hi.
Yes. After "QFIL", i also didn't update my device from DEV ROM with any Stock ROM (Indian or Chinese versions) by "upgrade.zip" without get the "corrupted file" error. So by TWRP, i installed 16S Indian Stock ROM -- TWRP informed that i have "no OS installed" but i proceeded and restarted from TRWP. It initialized the new ROM, and after the first setup, i restarted the device to complete any system operations after the first boot, and i updated the device with the Indian 19S with the EUI updater ( tapped "upgrade.zip" file). The device now have the stock recovery and boot in english (not chinese), and the EUI in all languages available on "India 19S Stock ROM".
Stock ROMS:
Le Max 2 All Official Stock Firmware links
Best regards.
Click to expand...
Click to collapse
Hey bro, I have the same problem. What twrp you used? When I try to install 16s indian twrp gives an error "Patching system image..." for too much long time, so it stop to install it.
I tried to flash twrp in my Redmi Note 4 and it successfuly flashed. But when i turned on the phone it says"your system has been distroyed" What can i do?..please help me!!:crying::crying:
try formatting data in twrp before booting back into system.
(and yes, this will delete EVERYTHING you have except your ROM)
edit: OR flash lazyflasher as recommended here in this official twrp thread: https://forum.xda-developers.com/re...er-development/recovery-twrp-3-0-2-0-t3550061
Robiul1727 said:
I tried to flash twrp in my Redmi Note 4 and it successfuly flashed. But when i turned on the phone it says"your system has been distroyed" What can i do?..please help me!!:crying::crying:
Click to expand...
Click to collapse
Did the exact same to my phone this is how I fixed
Vid link helps to explain what saying below
Download the old first version of mi flash 1st one preferred and any of the stable miui ROMs.
https://xiaomiflashtool.com
Stable global ROM
ROM
http://en.miui.com/thread-2312573-1-1.html
Boot into fastboot by holding volume down and power till the little guy shows up connect to pc
Unzip ROM copy name of folder (important)
Go into flash tool older version
Click refresh your device will show
Put name of the mi software you copied in the tab above your device
Go to browse on top left and advanced open the miui file you unzipped
Now find flash all file its the second file in my one
Go back and flash takes 3 mins than 10 to boot your at least back to stock working phone worked 100% for me I have messed up flashing few times can reflash to stock now in about 5 mins as long as you can fastboot :good:
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- Decryption works
- Otg works
- Flash Rom works
- F2FS support
- Fastboot boot command support
Not working:
- Fastbootd
- Adb sideload
- Backup restore and image flash (system-vendor-product)
- Android 11 fully support
Download:
TWRP 3.4.0-14 Unofficial by mauronofrio
TWRP 3.4.0-13 Unofficial by mauronofrio
To Flash the TWRP:
Code:
fastboot flash recovery twrp-3.3.1-xx-xxxxxx-mauronofrio.img
Then reboot in TWRP manually or using a fastboot command.
Code:
fastboot boot twrp-3.3.1-xx-xxxxxx-mauronofrio.img
or
Code:
fastboot oem reboot-recovery
REMEMBER: is important that from fastboot you directly go in TWRP mode or the TWRP will be overwritten.
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Source code:
https://github.com/Teamwin/android_bootable_recovery
https://github.com/mauronofrio/android_device_xiaomi_toco
My Telegram TWRP Support Group:
https://t.me/twrp_Mauronofrio
Donations:
Credits:
- Thanks to @bigbiff and @Captain_Throwback for the hard work on this android 10 TWRP
Thanks to all testers on the Telegram Group
Created 2020-05-29
Oooo finally... Gonna test this out when I get home later.
Just to check, what happens if i flash and i get bootloop? How do I recover? By flashing the entire MIUI rom from official site?
Okay Im sure im being a noob... But err...
I wasnt able to mount data...
I tried to mount and install MAGISK via USB-OTG mounting and i get permission denied for system and vendor (and also Data unable to mount)
EDIT2: Oh cool... despite the errors Magisk got installed! Nice!
Hello, will there be more development for this terminal? and the note 10 lite thread? Thank you
Did anyone boot it?
hello, work boot it?
fastboot boot twrp.XXXX.img
StanGumn said:
hello, work boot it?
fastboot boot twrp.XXXX.img
Click to expand...
Click to collapse
Yes
iron maiden said:
Hello, will there be more development for this terminal? and the note 10 lite thread? Thank you
Click to expand...
Click to collapse
Let us hope so.
I would like to apologize in advance as I am a noob when it comes to the recent changes made by Google to android. So on a lot of the recent devices launched with android 10, an essential step before flashing Magisk is to disable the vbmeta partition by flashing the "vbmeta.img" using a fastboot command with the --disable-verify and --disable-verification argument. My question is that is the "vbmeta.img" modified by developers or is this the same identical file found in the stock firmware files?
I do apologize if this is the wrong thread but there's not many resources online or even on xda for this device.
Why its in mi note 10 general section? Isnt right to do separately section for mi note 10 lite since there is nothing in common just name.
Reanimax said:
Why its in mi note 10 general section? Isnt right to do separately section for mi note 10 lite since there is nothing in common just name.
Click to expand...
Click to collapse
ask to xda to make a dedicated section and i will ask to move this thread
mauronofrio said:
ask to xda to make a dedicated section and i will ask to move this thread
Click to expand...
Click to collapse
Yes. You right about it.
Kediraksith said:
Oooo finally... Gonna test this out when I get home later.
Just to check, what happens if i flash and i get bootloop? How do I recover? By flashing the entire MIUI rom from official site?
Okay Im sure im being a noob... But err...
I wasnt able to mount data...
I tried to mount and install MAGISK via USB-OTG mounting and i get permission denied for system and vendor (and also Data unable to mount)
EDIT2: Oh cool... despite the errors Magisk got installed! Nice!
Click to expand...
Click to collapse
Nowadays you have to unmount Data and mount vendor (just in case for Vendor) before flashing Magisk. Mounting data does not let Magisk install via TWRP. Follow the this process, same install process with the Mi Note 10, and assuming the Mi note 10 Lite. The reason why is because of encryption.
Update: 5/16/2020
1) Flash lastest TWRP unofficial 3.31-4 mauronofrio using Command prompt using the - fastboot flash recovery [XXXX].img. Note: it's easier to just rename the recover image to "twrp"
2) Then - fastboot boot [XXXX].img to reboot into TWRP recovery.
3) In my experience for thr Mi Note 10 that is, the reboot to RECOVERY did not happened, so instead i pressed - volume up and power button at the same time for thr phone to reboot until you see the boot splash screen, hold the two buttons for another 3 seconds ... and then let go of power button and then TWRP recovery will show up.
4) Ok...so first things first... flash the VBMETA PATCHER like the OP says on first page --> that way you don't lose TWRP after flashing the Rom and MAGISK. After install, reboot to RECOVERY. ***This is only if OP asks to flash VBMETA PATCHER, otherwise skip to Step 5***
5) Now....go to FORMAT DATA (Warning: DON'T use advanced wipe)... Instead, go to the FORMAT DATA, type in yes and press ok. Then go back to main menu, and reboot to RECOVERY again.
6) Now you can access your internel memory when connecting to USB... You can import the two neccesary files --> Xiaomi.EU and MAGISK 20.4. Now Flash the Rom and when flash MAGISK, make sure you unmount DATA and mount VENDOR to avoid flash error. After unticking DATA, you can now install Magisk.
7) Now you can go to REBOOT, and press SYSTEM, and the phone will boot to Xiaomi EU 11 or 12, etc. just follow this process and enjoy your ROM. ?
Note: When updating, flash EU rom and Magisk, dont forget to unmount Data when flashing Magisk. You can probably disable decryption because that is why you can't mount Data when flashing Magisk. **Just don't ask me about it because I normally don't flash Disable Decyption often.
Wmateria said:
Nowadays you have to unmount Data and mount vendor (just in case for Vendor) before flashing Magisk. Mounting data does not let Magisk install via TWRP. Follow the this process, same install process with the Mi Note 10, and assuming the Mi note 10 Lite. The reason why is because of encryption.
1) Flash lastest TWRP unofficial 3.31-4 mauronofrio using Command prompt using the - fastboot flash recovery [XXXX].img. Note: it's easier to just rename the recover image to "twrp"
2) Then - fastboot boot [XXXX].img to reboot into TWRP recovery.
3) In my experience for thr Mi Note 10 that is, the reboot to RECOVERY did not happened, so instead i pressed - volume up and power button at the same time for thr phone to reboot until you see the boot splash screen, hold the two buttons for another 3 seconds ... and then let go of power button and then TWRP recovery will show up.
4) Ok...so first things first... flash the VBMETA PATCHER like the OP says on first page --> that way you don't lose TWRP after flashing the Rom and MAGISK. After install, reboot to RECOVERY.
5) Now....go to FORMAT DATA (Warning: DON'T use advanced wipe)... Instead, go to the FORMAT DATA, type in yes and press ok. Then go back to main menu, and reboot to RECOVERY again.
6) Now you can access your internel memory when connecting to USB... You can import the two neccesary files --> Xiaomi.EU and MAGISK 20.4. Now Flash the Rom and when flash MAGISK, make sure you unmount DATA and mount VENDOR to avoid flash error. After unticking DATA, you can now install Magisk.
7) Now you can go to REBOOT, and press SYSTEM, and the phone will boot to Xiaomi EU 11 or 12, etc. just follow this process and enjoy your ROM.
Note: When updating, flash EU rom and Magisk, dont forget to unmount Data when flashing Magisk. You can probably disable decryption because that is why you can't mount Data when flashing Magisk. **Just don't ask me about it because I normally don't flash Disable Decyption often.
Click to expand...
Click to collapse
this post is gold! Coming back to xiaomi and twrp after 2 years with a huawei, hope to go smooth again with root magisk etc!
cerme said:
this post is gold! Coming back to xiaomi and twrp after 2 years with a huawei, hope to go smooth again with root magisk etc!
Click to expand...
Click to collapse
The root and flash process is basically the same process as the Mi 9T/K20, Mi Max 3, Mi Note 10 since decryption is now a common thing with Android 10... except for the VBmeta.zip, which is new and necessary to flash, as long as you follow the directions..you'll be fine.
Wmateria said:
The root and flash process is basically basically the same process as the Mi 9T/K20, Mi Max 3, Mi Note 10 since decryption is now a common thing with Android 10... except for the VBmeta.zip, which is new and necessary to flash, as long as you follow the directions..you'll be fine.
Click to expand...
Click to collapse
I understand. Last experience ti flash etc was on a mi5, so I have a little bit of rust with that. I do think that following instructions i shouldn't face major difficulties
cerme said:
I understand. Last experience ti flash etc was on a mi5, so I have a little bit of rust with that. I do think that following instructions i shouldn't face major difficulties
Click to expand...
Click to collapse
Same here, i was on the Mi 9T before, I didnt understood the whole new flashing process and carefully updating from EU Rom to AOSP Roms and back, I think i was messing with with thwe wipe and change partition feature (f2fs to ext 4 with an EU Rom) - then the Mi 9T bricked big time. Never recovered after that, luckily got it refunded for it but not many may have that second chance. After learning how to flash propeely and root, ect. I try to help out here when needed and ask too. I just got my Mi Note 10 2 weeks ago and rooted a week ago. So if anything, am willing to help out and repeat the following flash process or any changes in the future and feedback on future Roms.
Was thinking about which rom to use... does xiaomi.eu is stille faster with providing updates? what about the situation with OTA with that.
Now I have the phone with global rom, I want at least flash the EEA rom. But I also know that at some point i want to root, install magisk and get nice features. Still don't want to update manually everytime for an update...
will be watching this thread with much interest..
I recently bought this device (Global version) for use here in Australia.
my first time owning a Xiaomi - quite happy with it so far.
would be nice to have the themeing stuff work properly - I have used MIUI based ROMs back a LOoonggg time ago, in the days of the Nexus S and Galaxy Nexus etc.
used to have a new ROM flashed every couple of days lol, back then. But recent years I've stopped all that, no cool ROMs no snazzy kernels TWRP no nothing not even root lol, very boring!
anyway thanks for posting I hope to try this sometime soon
Hello is there any Eu rom for Mi note 10 lite?
Alisiddiqui75 said:
Hello is there any Eu rom for Mi note 10 lite?
Click to expand...
Click to collapse
yes, there is the EEA ROM you can find on miui website. You can flash it after unlocking bootloader with miFlash
Alisiddiqui75 said:
Hello is there any Eu rom for Mi note 10 lite?
Click to expand...
Click to collapse
I'm not sure if you mean the official ROM or xiaomi.eu.
The link to the official EEA(EU) ROM:
Recovery: https://bigota.d.miui.com/V11.0.7.0.QFNEUXM/miui_TOCOEEAGlobal_V11.0.7.0.QFNEUXM_7926bf9c02_10.0.zip
Fastboot: https://bigota.d.miui.com/V11.0.7.0...EUXM_20200508.0000.00_10.0_eea_4eb1c694c9.tgz
I have yesterday seen a xiaomi.eu Stable build for toco which is based on Global Stable ROM:
https://sourceforge.net/projects/xi...e10LITE_V11.0.4.0.QFNMIXM_v11-10.zip/download
I can not promise that it's working.