Related
About
Hi there,
I created this guide not so much as a substitute for the other guides or because this would be the best way to do it.
When I looked into rooting my new Axon 7 (international) I studied all the other guides first, but then did it very differently, mainly
because
- I am on Win 7 32-bit and some of the tools used in the other guides don't work for that
- since the other guides were created the Axon7Toolkit came along - that simplified a lot of steps.
The guide is actually very similar to this one for the 2017U:
https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128
Only now with the toolkit it pretty much works for the 2017G as well without the need for tenfar's TWRP (see comments). In case I left out anything, this guide will be of help, too.
So this guide is for you if
- You want to root or flash a custom rom and don't mind unlocking the bootloader OR
- You are on Win32 and cannot use the axon7tool command line tool OR
- You want to use the Axon 7 Toolkit for the job to keep things simple
Please read all the notes below before attempting anything...
Disclaimer
- This worked well for me - no claims it does for anyone else. For the record: I was on Stock 6.0 MM B08 A2017G, no fingerprint/lock etc and went straight to RR.
- Use at your own risk, if you are unsure what you are doing stay stock - I'm not responsible for bricked devices, dead SD cards, Donald Trump, or you getting fired because the alarm app failed...
Regarding Drivers
- Qualcomm ones for MiFlash (link below)
- QUSB_BULK if going with eg the axon7tool commandline version (edl mode)
- You can use the Toolkit to install (some of) the needed drivers
- ZTE drivers - phone is set up to install them upon connect to the PC. Don't.
- Uninstall incorrect drivers, just installing the correct ones won't necessarily do the trick.
MiFlash
- right click & 'run as admin' (flashing didn't work for me without this)
- Correct driver: Qualcomm HS-USB QDLoader 9008 when in edl (check with device manager open)
Boot modes
- power phone down and boot into
- EDL by holding Volume UP/DOWN & POWER simultaneously
- recovery/TWRP (once installed) by holding Volume UP & POWER simultaneously
- fastboot: Not enabled in A2017G Stock
Windows
- 32-bit: MiFlash needed, commandline axon7tool not working
- The toolkit seems to run on Mac/Linux using a Windows emulator/virtual machine (not tested, Wine helps I guess)
TWRP
- versions: Signed tenfar TWRP 3.0.2 that is used in a lot of other guides is buggy and can do a lot of harm - not needed if you unlock
the bootloader first. You can (and should) use the latest official TWRP version.
- dm-verity: https://twrp.me/devices/zteaxon7.html
- USB OTG: Axon 7 supports this, so does TWRP - no need for SD cards. Simply use a thumbdrive with a OTG cable (with included Adapter if needed), boot into TWRP (thumbdrive needs to be connected beforehand) and click 'Mount' in TWRP, then select USB storage
Bootloader
- Afaik DO NOT lock again with custom rom installed or rooted (brick)
Root/Unlock
- Can create problems with Android Pay, playstore etc - see https://www.xda-developers.com/tag/safetynet/
- Root disabled by default in Lineage, needs flashing Magisk or SU - see other guides
- Some features root provides on Android 6.0 MM won't work in Nougat (so far anyway, eg xposed)
Links
- Axon7Toolkit: https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
- TWRP: https://twrp.me/devices/zteaxon7.html
- Zadig (if needed): http://zadig.akeo.ie/
- Qualcomm driver: https://build.nethunter.com/misc/axon7/Qualcomm_QUSB_BULK_Drivers.zip (link from https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514)
- Lineage Os thread: https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-14-1-zte-axon-7-t3545679
- Modem & bootloader from Lineage Os thread: https://www.androidfilehost.com/?w=files&flid=148464
- OpenGApps: http://opengapps.org/?arch=arm64&api=7.1 (arm64 version for OS version to flash, e.g. 7.1 Nougat)
Thanks
bkores (for the tool), dnlilas (help in the forum), DrakenFX, Unjustified Dev, Controllerboy & all the guide/rom creators etc in this forum. (And the poor souls who came first and discovered all the ways not to do it, preventing my fall)
1) Prep
- Note down IMEI(s) from your settings/about phone/status/... just in case
- Unlock developer options (Phone settings > "About Phone" > Click "Build Number" 7 times...)
- Check "Allow OEM unlock" and "USB Debugging" there
- Connect your Axon 7 to your PC with the original USB cable - do not disconnect with MiFlash/Toolkit running.
- Open device manager to check your drivers (will show up differently depending on the boot mode)
- Run Axon7Toolkit
- Select Option 1 - Install/Test Drivers
2) Unlock
- This will RESET your device, did you save your data? (using Toolkit etc)
- Select option 6-unlock on toolkit main screen -
- MiFlash launches and one has to select the folder with the files to flash, following the instructions of the toolkit
- Check Device Manager lists your Axon 7 as Qualcomm HS-USB QDLoader 9008, if not uninstall wrong drivers and install Qualcomm ones
- The unlock files the Axon7Toolkit offers are in a folder 'A2017U_FASTBOOT_UNLOCK_EDL' - works for A2017G
(- Axon7Toolkit preview version offers different folder content to flash - have not checked that)
- One can restart MiFlash (e.g. to 'run as Admin') anytime and try again, but after the flash was succesful, do not disconnect the phone but
- Finish off with the Toolkit 'press a key to continue' (or one will have only fastboot enabled)
- A message will appear on the phone: Confirm that you want to unlock the bootloader (using volume & power buttons to navigate)
- Done. From now on you will get an annoying message on booting the phone about your device being unlocked. Just ignore and wait for a re-boot...
3) TWRP
- Unlock developer options - AGAIN etc as device was reset. And - again - enable debugging...
- In the toolkit (main screen) go to '11 Advanced Options', select <Flash boot/bootloader/modem/recovery<choose recovery partition
- In 'Open' dialog select C:\Axon7Development\Axon7Toolkit\twrp\twrp-3.1.0-ailsa_ii.img (or newer version)
- Flash as 'recovery'
- Reboot, check system boots up fine
4) Flash Custom Rom etc.
- Generally: Follow instructions provided with the custom rom you are going to flash (as they might differ)
- Boot into recovery/TWRP (Volume UP + Power after shutdown)
- No need to swipe to 'Allow system modification' - this can actually brick things...see https://forum.xda-developers.com/axon-7/help/a2017u-stuck-zte-screen-boot-factory-t3584062
- Mount/Select storage (for OTG USB)
- Backup boot, recovery, data(if needed), HLOS, System image or System (image was recommended but that did not work in my case, so I backed up system)
- Wipe/Format
- ***If you like to avoid your data partition to be encrypted, follow that thread: ( format your data partition to ext4 instead of f2fs (wipe -> advanced)????)
- Install Bootloader & then modem (or Nougat won't install if coming from MM) - A2017X_B15_Universal_Bootloader.zip & A2017G_N_Modem.zip
- Rom & Magisk/SuperSU
- GAPPS (version)
- Re-boot: Unlocked message, long first time boot - After RR, my phone show up as 2017U... well, who cares...
Any comments to correct errors in this guide or fill out any blanks are highly appreciated...
I dunno why now one has thanked this yet, it is a well written guide imo and useful for those not yet unlocked.
THANKS SOO MUCH FOR THIS!! The timing could not have been any better. I literally just bought this phone from a guy on craigslist for $270 (Couldn't pass that up coming from an LG G4) less than a hour ago. Quick question. It's a 2017u with build B25. Will the toolkit work with it. I don't see an option for this build
Hi Senny,
thanks a lot - I hope the guide is helpful, as mentioned it worked for me. Hopefully I included at least most of the pitfalls one could encounter...
Hi raphi809,
The toolkit should work fine with the 2017U (it should detect your version).
To be sure, also have a look at the toolkit thread (https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108) and the thread linked above (https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128), as it is more specific for the 2017U.
The main thing I am not 100% sure with the 2017U is (as I am on a 2017G and started from Android 6.0 MM), if you have to downgrade from Nougat/certain versions before unlocking etc.
If someone could shed some light on this, that would be great!
Whoooo? said:
About
- Select option 6-unlock on toolkit main screen -
- MiFlash launches and one has to select the folder with the files to flash, following the instructions of the toolkit
- Check Device Manager lists your Axon 7 as Qualcomm HS-USB QDLoader 9008, if not uninstall wrong drivers and install Qualcomm ones
Click to expand...
Click to collapse
Hi Whoooo?, first thank your for your time to write this guide.
I tested your procedure and I remain stuck at the same point than the others guides. After Axon7Tool / 6-Bootloader Unlock, MiFlash.exe doesn't launch because I am not under 64bits system. So, after a successful Xiao MiFlash package, I launch it manually (admin rights): my device (in edl mode) is not seen, whatever the driver used (Qualcomm, QUSB...).
If I understand correctly the right procedure to install LineageOS 14.1 & TWRP, Axon 7 must be unlocked in its bootloader by flashing A2017U_FASTBOOT_UNLOCK_EDL?
Volumetrik said:
Hi Whoooo?, first thank your for your time to write this guide.
I tested your procedure and I remain stuck at the same point than the others guides. After Axon7Tool / 6-Bootloader Unlock, MiFlash.exe doesn't launch because I am not under 64bits system. So, after a successful Xiao MiFlash package, I launch it manually (admin rights): my device (in edl mode) is not seen, whatever the driver used (Qualcomm, QUSB...).
If I understand correctly the right procedure to install LineageOS 14.1 & TWRP, Axon 7 must be unlocked in its bootloader by flashing A2017U_FASTBOOT_UNLOCK_EDL?
Click to expand...
Click to collapse
Hi Volumetrik,
For me the MiFlash version that came with the Toolkit originally didn't work either (as Win32, too).
Instead I used the installer that came with the beta version of the toolkit (v1.2 - there was an installer in the MiFlash folder).
The installer created two applications (MiPhone and MiFlash or similar) - one of them worked for me if run as admin.
Also make sure the right driver is actually used by windows (by checking what is used in the device manager when the phone is connected in edl mode) - Windows is sometimes funny if more than one driver is installed...
Hope that helps
Whoooo? said:
Hi Volumetrik,
For me the MiFlash version that came with the Toolkit originally didn't work either (as Win32, too).
Instead I used the installer that came with the beta version of the toolkit (v1.2 - there was an installer in the MiFlash folder).
The installer created two applications (MiPhone and MiFlash or similar) - one of them worked for me if run as admin.
Also make sure the right driver is actually used by windows (by checking what is used in the device manager when the phone is connected in edl mode) - Windows is sometimes funny if more than one driver is installed...
Hope that helps
Click to expand...
Click to collapse
Hi Whoooo?
Thank you for swift reply. In fact, I decided to work under x64 environment, so I made a fresh install. Then, I combined your guide with the others in this part in the forum.
I must say I thank you so much, for your work. For a N00b, it's difficult to sort the main steps to complete the process... even if I already did this on different devices before.
I'll explain in the LineageOS thread how I completed this conversion from a full stock A2017G B03 (MM). It's slightly similar with yours.
Once again, Thank you. :good:
It's now a few days ago since this guide has been published and I wonder why nobody seems to share any experiences. Has nobody tried to follow these steps so far? I am interested whether it is possible to start from Nougat or is MM recommended?
marcus.linkenbach said:
It's now a few days ago since this guide has been published and I wonder why nobody seems to share any experiences. Has nobody tried to follow these steps so far? I am interested whether it is possible to start from Nougat or is MM recommended?
Click to expand...
Click to collapse
Hi there,
Obviously I have not tried this myself, so I only can refer to these two posts from the Toolkit thread:
https://forum.xda-developers.com/ax...on7toolkit-t3573108/post71673370#post71673370
https://forum.xda-developers.com/ax...on7toolkit-t3573108/post71861250#post71861250
...stating that 'Bootloader mode is disabled in G variant with Nougat update' and one has to either
- revert to MM or
- flash a different Unlock package with MiFlash (linked in the second post)
(There is also a note in the instructions saying that the toolkit's Bootloader unlock with MiFlashdoes not work on A2017U B25)
marcus.linkenbach said:
It's now a few days ago since this guide has been published and I wonder why nobody seems to share any experiences. Has nobody tried to follow these steps so far? I am interested whether it is possible to start from Nougat or is MM recommended?
Click to expand...
Click to collapse
Hi Marcus,
I tried to find some time to reply and explain how I used this guide and two others to get my device unlocked, twrp'ed and LineageOS. It's running like a charm.
I started with a A2017G device basis with MM B03. My device was updated to the latest official update available via MyFavor network. I didn't try to update OTA.
I Used Axon7ToolKit v1.1.1 + Update_Install.bat / Qualcomm Drivers / A2017U_Bootloader_EDL. I worked under windows x64, because I experienced too many troubles to get Axon7toolkit working properly under 32bits. The only one differences I experienced and not written in the threads:
- I saw a FTM mode (Factory Test Mode) displayed in a white square centered on the device screen after unlocking bootloader. In my memory, it disappeared after TWRP flash.
- I got a problem with Flashlight, didn't work, associated with a problem to call (sms working). I flashed the modem firmware once again, it solved the problem after reboot.
- At the end, LineageOS installed, LineageOS updater strangely saw the same update version installed on the device. The only difference was the"signed" at the end of the update name I launched the update and installed it succesfully, without issue. No more update after that (until a new one of course)
Hope this will help someones
Volumetrik said:
Hi Whoooo?
Thank you for swift reply. In fact, I decided to work under x64 environment, so I made a fresh install. Then, I combined your guide with the others in this part in the forum.
I must say I thank you so much, for your work. For a N00b, it's difficult to sort the main steps to complete the process... even if I already did this on different devices before.
I'll explain in the LineageOS thread how I completed this conversion from a full stock A2017G B03 (MM). It's slightly similar with yours.
Once again, Thank you. :good:
Click to expand...
Click to collapse
Hi, when are you planning to release your complete guide? This would really help me.
I am trying unlocking the bootloader on B11
When I try flashing bootloader unlock in MiFlash it says:
Lenght cannot be less than zero.
Parameter name: lenght
Tried restarting MiFlash, installing it again and restarting PC. Does anyone know what am I doing wrong?
EDIT: Managed to unlock using Controllerboy guide that didn't work for me at first (why I used toolkit). But I am still curious why that error in MiFlash happened...
Bootloader is unlocked. Drivers are okay, toolkit recognises the phone connected. But every time I try to flash twrp or root it says 'FAIL'.
Can someone please help?
still_living said:
Bootloader is unlocked. Drivers are okay, toolkit recognises the phone connected. But every time I try to flash twrp or root it says 'FAIL'.
Can someone please help?
Click to expand...
Click to collapse
Hi,
Sorry for the late reply -
just to clarify, are you stuck after point 2 of the guide (as root is the last step of the guide/only mentioned there)?
Personally I did root not via the toolkit but via TWRP when I flashed the custom rom (as described eg in the lineage os thread).
Problems with flashing TWRP I could think of:
- bootloader unlock not successful
- debugging/developer option not enabled
- TWRP not flashed as recovery
At what point does the toolkit report fail (maybe your problem is also worth posting in the toolkit thread)?
Alternatively TWRP could also be flashed with MiFlash (did NOT try myself - but there should be guides around somewhere).
Apocalypse12345 said:
I am trying unlocking the bootloader on B11
When I try flashing bootloader unlock in MiFlash it says:
Lenght cannot be less than zero.
Parameter name: lenght
Tried restarting MiFlash, installing it again and restarting PC. Does anyone know what am I doing wrong?
EDIT: Managed to unlock using Controllerboy guide that didn't work for me at first (why I used toolkit). But I am still curious why that error in MiFlash happened...
Click to expand...
Click to collapse
Hi there,
I think (memory blanks setting in) that's the error I got when MiFlash was not running as admin.
Whoooo? said:
Hi,
Sorry for the late reply -
just to clarify, are you stuck after point 2 of the guide (as root is the last step of the guide/only mentioned there)?
Personally I did root not via the toolkit but via TWRP when I flashed the custom rom (as described eg in the lineage os thread).
Problems with flashing TWRP I could think of:
- bootloader unlock not successful
- debugging/developer option not enabled
- TWRP not flashed as recovery
At what point does the toolkit report fail (maybe your problem is also worth posting in the toolkit thread)?
Alternatively TWRP could also be flashed with MiFlash (did NOT try myself - but there should be guides around somewhere).
Click to expand...
Click to collapse
Hello. Yes I have posted it there and the questions and answers section to which bkores (the one who made the axon7toolkit) replied and asked me to do a command in which I followed and replied to him with the results and he didn't reply after that. Also, bootloader is unlocked. This is what happens:
Checking ADB/fastboot connectivity...
ADB device connected!
Rebooting to bootloader...
Checking fastboot connectivity...
Fastboot device connected...
Flashing twrp...
And within a second an error message pops up with a red cross 'Flash failed!'
Sorry, I forgot to say that I couldn't follow your guide entirely because I think we are on different versions of the toolkit. I am on the latest version 1.2.0 (stable), so I don't have the option 11 to go to advance settings to install the twrp. I have just the option 6 to install directly(you can see in the thumbnail of axon7toolkit post).
Thank you so much for this guide ! Had the phone back in october and i unlocked it using tenfar tool but since it was stolen in march, i bought a new one last week and this is so much simpler and safer !
still_living said:
Hello. Yes I have posted it there and the questions and answers section to which bkores (the one who made the axon7toolkit) replied and asked me to do a command in which I followed and replied to him with the results and he didn't reply after that. Also, bootloader is unlocked. This is what happens:
Checking ADB/fastboot connectivity...
ADB device connected!
Rebooting to bootloader...
Checking fastboot connectivity...
Fastboot device connected...
Flashing twrp...
And within a second an error message pops up with a red cross 'Flash failed!'
Sorry, I forgot to say that I couldn't follow your guide entirely because I think we are on different versions of the toolkit. I am on the latest version 1.2.0 (stable), so I don't have the option 11 to go to advance settings to install the twrp. I have just the option 6 to install directly(you can see in the thumbnail of axon7toolkit post).
Click to expand...
Click to collapse
Did you try booting to recovery after the failed flash attempt ? I had the same issue with the fail message (toolkit 1.2.0) but twrp was running fine.
djona12 said:
Thank you so much for this guide ! Had the phone back in october and i unlocked it using tenfar tool but since it was stolen in march, i bought a new one last week and this is so much simpler and safer !
Did you try booting to recovery after the failed flash attempt ? I had the same issue with the fail message (toolkit 1.2.0) but twrp was running fine.
Click to expand...
Click to collapse
Only stock recovery for me. No twrp unfortunately. Really want to change from miflavour
djona12 said:
Thank you so much for this guide ! Had the phone back in october and i unlocked it using tenfar tool but since it was stolen in march, i bought a new one last week and this is so much simpler and safer !
Did you try booting to recovery after the failed flash attempt ? I had the same issue with the fail message (toolkit 1.2.0) but twrp was running fine.
Click to expand...
Click to collapse
HURRAY! ! !
Well no it didn't work until today I tried the option to restore from bricked device to b10. Out took me to miflash and asked me to unlock bootloader? Dunno why, it's already unlocked, anyway , after that was successful I went back to the option page of the toolkit and selected 'install twrp', and this time it flashed! It didn't stop on the 'failed to flash twrp' message but still gave me a 'flash to boot into twrp' then I followed your advise to go to twrp directly from there and it had installed. I'm so happy thanks loads dude. :laugh:
Worked like a charm! Thanks for posting the guide
Edit: Went from locked Nougat to Unlocked Lineage.
Whole process took me about 2 hours, but if you are better at following the steps than me you'll probably be able to do it in 1 hour.
Hi there,
I recently got in my hands an Asus (Mediatek according to system properties) zenfone 4A Max X00KD. It comes with android 7 nougat installed, and fully bloated with usefulness apps.
I've tried to root it (I did it before with other devices with older android os) but this thing comes with a Chinese recovery boot mode which is very limited.
Steps I've already done:
-Usb debugging enabled.
-adb & fastboot tools working.
-Unlocked bootloader.
I've been reading about the SP_Flash_tool and the MTK_droid_tool as well as the ZenFone_Rootkit, but none of them work with android 7. The same happens with apks like kingroot (tried and without success).
Too many people talks about TWRP in order to inject Magisk tools' zip, but there's no version for this phone, and in order to complie I need the source (I think from the zenfone kernel, correct me if I'm wrong) but I'm unable to find it trough the web.
Am I missing something? Is there any way to root an android 7 with a chinese bootloader?
Thanks in advance.
Dear , did you find any solution ? I m facing same. thanks
i am facing the same too
Summary:
After attempting to unlock bootloader using unofficial method, it is flashing red and doing a bootloop.
Any suggestions? Worried!
Specs:
Redm Note 3 Pro
qualcomm snapdragon 650 model msm8956
Kenzo
DETAILS:
1. I followed the instructions in this video precisely to unlock the bootloader (forum wont let me post link, but this is exact name of Youtube video):
Root Redmi Note 3 Without unlocking bootloader | Unlock bootloader without MI permission.
Poster is Tech unlock
Video length is 11 mins exactly
2. Shortcut info - files used:
Fastboot ROM
MI flash tool:
Fastboot_EDL:
Unlocked Bootloader:
TWRP Recovery:
Android image Kitchen:
ADB&Fastboot setup:-
Notepad++
3. I was a little low on power but MI Flash said 'success'
4. But when I turned on:
- the red light continually flashes while charging (but is not flashing while it is not charging)
- it went into bootloop:
5. This is the only thing it will do:
Press power down for 7 seconds (lately it always seems to take a long time to turn on any way)
Phone buzzes and MI logo comes up, then disappears
Let go
Again: Phone buzzes and MI logo comes up, then disappears
Nothing
6. If you hold the power button down, the same thing happens over and over, with shorter wait-times between each double appearance of the MI logo
7. It can boot into fastboot
8. I'm assuming it COULD just be low on power, or that issue is a separate issue to the bootloop?
Please help ! It's freaking me out...
Found the answer and a better method
Summary:
There is a better method to unlock bootloader and root, but I also fixed the looping problem above.
Fixing looping problem:
1. Go into fastboot mode (google it)
2. Run 'Minimal Adb and Fastboot' app installed earlier
3. Type:
fastboot oem unlock-go
4. It should start
I found this on the following page of this site, though I used it as part of trial and error:
Fix bootloop in redmi note 3 (no recovery ,no edl mode) by adithyan25
Better method to root with later version of MIUI OS (version 8.0.6.0)
I discovered that the method I used from the youtube video installed an older version of the OS, so I sought an unlocking-and-rooting method that installed the OS I was already on (8.0.6.0).
I found one and it worked:
I can't do links because I've just joined but look up this article on codeshuffle[dot]blogspot[dot]com for the unlocking process:
Unlock Bootloader+Flash MIUI 8.0.6.0 Global Stable fastboot ROM Redmi Note 3 Snapdragon Variant [KENZO][RN3]
It also has links to the following related topics, but you will have to use Waybackmachine to find them, because they are no longer online:
* The rooting process:
'Flash TWRP recovery and Root your Redmi note 3 [KENZO][RN3]'
* Preparing a custom boot image as part of the rooting process (highly advisable I would think):
'[Fix] Custom recovery getting replaced by Stock recovery : Cooking custom boot.img using Android Kitchen for Redmi note 3 Snapdragon variant [KENZO][RN3]'
* What to do if you can't get your PC to recognise your adb drivers:
'[Fix] Fastboot/ADB device connection "waiting for device" error fix for android phones [General]'
BONUS: Making the SD card writable
The whole reason I rooted was to make my SD card writable by any app, after the (i think) lunatic decision by Android devs to restrict it from lollipop onwards.
I found an easy way to do this**, on this here site.
You use TWRP recovery (put on the phone during root) and install a zip file called:
tmo_n900t_extsd_fix_tekhd.zip
You can download it from the page called:
androidhost[dot]org[backslash]VPxGt
I later found a copy of that zip file on this site somewhere but I can't find that again.
But that file above is definitely the same file (I checked the hash)
___________________________
FOOTNOTE
** This way is much safer I think than editing platform.xml. I tried that and ended up with an unbootable phone, requiring me to reflash the stock rom using the info in the pages above.
[Just a bit of feedback for this site: It adds quite a lot of work for me and for anyone trying to use this information, to provide it as headings of pages rather than URLs.
I don't think I'll be doing it again so I doubt I will get up to the max number of posts to be allowed to link, which means posting will continue to be a bit of an effort. So this is likely my last post.
Be good if the admins could work out a better way to prevent spam?]
First clean flash fastboot rom to latest 10.2 miui rom.
Then try to unlock using official method.
If u cant bind account in developr option and getting 20091 error.
Then use unofficial method.
---------- Post added at 03:54 PM ---------- Previous post was at 03:50 PM ----------
Use this below method to install twrp
https://forum.xda-developers.com/redmi-note-3/how-to/unlock-unofficially-install-zcx-twrp-t3586778
---------- Post added at 03:56 PM ---------- Previous post was at 03:54 PM ----------
Once twrp is installed update to latest twrp 3.3.1 official .
format data
Factory reset
Flash rom 9.0
Flash gapps 9.0
Reboot
[original comment with links to ROMs is there: https://forum.xda-developers.com/t/root-possibility.4130739/post-83915657]
Hello
This is way to install AOSP rom with root (not Magisk, Superuser). All thanks to Wer99, he found this method
You need:
ROM:
http://www.mediafire.com/file/mdavroo9edpwveg/AP_AOSP_Android_10_A21s.tar/file > AOSP Android 10 ( only bug i found is not working auto-brightness [which is normal for GSI without overlay, but there is not working light sensor probably, i dont see values in CPU-Z or AIDA64 either])
http://www.mediafire.com/file/r6m7s99hs9d031e/AOSP_super.tar/file > AOSP Android 10
https://www.mediafire.com/file/wjhwnh3pags62fa/super.tar/file > HavocOS Android 10 (i use this rom on my daily phone, bug is the same as on AOSP)
Others:
Odin, you can found it on XDA
Samsung Mobile USB Drivers, or other drivers for Samsung Download Mode
Installation is easy.
Unlock your bootloader [it trips Knox and voids warranty!]
Power-off your phone, boot it in Download Mode with pushing volume down and up, and connect USB cable to PC simultaneously.
In Odin, push file with ROM to AP section, and click flash. Done!
After reboot, do factory reset of phone.
After installation, enable support of all cameras in phh-treble settings.
Didn't work for me, I tried with the AOSP_super.tar, which succeeded, but got a boot loop.
I tried with the AP_AOSP_.., but it fails, I got "Only official released binaries are allowed to be flashed (SUPER)". The same occurs with Havoc tar.
When I tried the AOSP_super.tar again, I got the same message, instead of a boot loop.
Steps:
Unlock bootloader (OEM unlock is also permanently triggered in developer settings)
Power off phone
Download mode (volume up + power on) and connect USB
Load tar file in AP slot (other slots are empty)
Factory reset and clear cache
Flashing back the stock rom still works. Stock rom: A217FXXU5BUB4
Any ideas?
KaroloBC said:
[original comment with links to ROMs is there: https://forum.xda-developers.com/t/root-possibility.4130739/post-83915657]
Hello
This is way to install AOSP rom with root (not Magisk, Superuser). All thanks to Wer99, he found this method
You need:
ROM:
http://www.mediafire.com/file/mdavroo9edpwveg/AP_AOSP_Android_10_A21s.tar/file > AOSP Android 10 ( only bug i found is not working auto-brightness [which is normal for GSI without overlay, but there is not working light sensor probably, i dont see values in CPU-Z or AIDA64 either])
http://www.mediafire.com/file/r6m7s99hs9d031e/AOSP_super.tar/file > AOSP Android 10
https://www.mediafire.com/file/wjhwnh3pags62fa/super.tar/file > HavocOS Android 10 (i use this rom on my daily phone, bug is the same as on AOSP)
Others:
Odin, you can found it on XDA
Samsung Mobile USB Drivers, or other drivers for Samsung Download Mode
Installation is easy.
Unlock your bootloader [it trips Knox and voids warranty!]
Power-off your phone, boot it in Download Mode with pushing volume down and up, and connect USB cable to PC simultaneously.
In Odin, push file with ROM to AP section, and click flash. Done!
After reboot, do factory reset of phone.
After installation, enable support of all cameras in phh-treble settings.
Click to expand...
Click to collapse
Is there a way to install Havoc OS prerooted?
To David112+ :
I've Been Looking Forward On How To Make A GSI For Samsung A217F,
But I'm Only Able To Create A Non Rooted GSI With "CherishOS"
I'm Looking For Every Help Possible On This Forum.
Although I Don't Even Have Any Android Knowledge,
But You Know I Tried To Make A Non Rooted GSI With "HavocOS".
The Result Was Bad...
Booting - Passed
Access First Start Pages - Passed
Access Settings - Passed
But...
There's A Problem With The GSI.
Problem :
Random Restart Within 10 Second
My Device Variant = International
LonelyCracker said:
To David112+ :
I've Been Looking Forward On How To Make A GSI For Samsung A217F,
But I'm Only Able To Create A Non Rooted GSI With "CherishOS"
I'm Looking For Every Help Possible On This Forum.
Although I Don't Even Have Any Android Knowledge,
But You Know I Tried To Make A Non Rooted GSI With "HavocOS".
The Result Was Bad...
Booting - Passed
Access First Start Pages - Passed
Access Settings - Passed
But...
There's A Problem With The GSI.
Problem :
Random Restart Within 10 Second
My Device Variant = International
Click to expand...
Click to collapse
Yeah I think I know why, There's a filesystem problem, the UUID and filesystem has to be the same as the system.img of OneUI
The UUID depends in the device binary that you have (in the firmware)
I'd help you but, all my steps just led to a dead end sadly
KaroloBC said:
[original comment with links to ROMs is there: https://forum.xda-developers.com/t/root-possibility.4130739/post-83915657]
Hello
This is way to install AOSP rom with root (not Magisk, Superuser). All thanks to Wer99, he found this method
You need:
ROM:
http://www.mediafire.com/file/mdavroo9edpwveg/AP_AOSP_Android_10_A21s.tar/file > AOSP Android 10 ( only bug i found is not working auto-brightness [which is normal for GSI without overlay, but there is not working light sensor probably, i dont see values in CPU-Z or AIDA64 either])
http://www.mediafire.com/file/r6m7s99hs9d031e/AOSP_super.tar/file > AOSP Android 10
https://www.mediafire.com/file/wjhwnh3pags62fa/super.tar/file > HavocOS Android 10 (i use this rom on my daily phone, bug is the same as on AOSP)
Others:
Odin, you can found it on XDA
Samsung Mobile USB Drivers, or other drivers for Samsung Download Mode
Installation is easy.
Unlock your bootloader [it trips Knox and voids warranty!]
Power-off your phone, boot it in Download Mode with pushing volume down and up, and connect USB cable to PC simultaneously.
In Odin, push file with ROM to AP section, and click flash. Done!
After reboot, do factory reset of phone.
After installation, enable support of all cameras in phh-treble settings.
Click to expand...
Click to collapse
Hi i flash havocos but not reboot in rom reboot in download mode help please
LonelyCracker said:
To David112+ :
I've Been Looking Forward On How To Make A GSI For Samsung A217F,
But I'm Only Able To Create A Non Rooted GSI With "CherishOS"
I'm Looking For Every Help Possible On This Forum.
Although I Don't Even Have Any Android Knowledge,
But You Know I Tried To Make A Non Rooted GSI With "HavocOS".
The Result Was Bad...
Booting - Passed
Access First Start Pages - Passed
Access Settings - Passed
But...
There's A Problem With The GSI.
Problem :
Random Restart Within 10 Second
My Device Variant = International
Click to expand...
Click to collapse
Can you make a unrooted gsi? If you could please use dot os 5.2 it would mean world for me. The community also i think.
Don't use this. The Method Doesn't work. You'll be stuck in Bootloop Even if it Shows it Succeeded.
EatABRick said:
Don't use this. The Method Doesn't work. You'll be stuck in Bootloop Even if it Shows it Succeeded.
Click to expand...
Click to collapse
It worked, but with older version of OneUI installed. I don't have this phone anymore but maybe i can help
Update 2021.01.24: I consider the problem mentioned here as solved, since it can be resolved with MTK Bypass explained in the Guides Section. BE CAREFUL however to ONLY choose "Download Only" from the dropdown box in SP Flashtool! DO NOT select anything with "Format" in it, else you will lose S/N, MACs and IMEIs!
--- Original post ---
Hi, I have hard-bricked my new Realme 6 while trying to root it with Magisk. At the moment I am stuck in a bootloop at the power-on logo (realme in white letters). The boot animation (yellow realme letters) does not appear, instead the phone reboots after ~35 seconds. The bootloader says "Orange State".
I can NOT enter fastboot nor recovery mode by any key combination. Holding Power and Vol- makes the string RECOVERY MODE appear for a split second in the lower left part of the screen, however nothing happens afterwards.
I can power down by holding Power and Vol+ an releasing them immediately after the screen goes blank.
Holding Vol- and Vol+ while the phone is off and connecting USB makes a USB serial device appear on a windows machine for about 1-2 seconds before it disappears again.
I am very thankful for any hints on how to unbrick the device.
Here's what I have done in detail to mess up the phone:
1. OTA-Update to the latest OS in my region (EU11.A.48)
2. Unlocked the bootloader with the realme In-depth Test app (everything fine so far)
3. Download stock firmware RMX2001EU_11.A.48 ozip from realmeupdater.com
4. Unzipped with gnu unzip (content was readable, no extra decrytion tool for the ozip needed?) and extracted boot.img
5. Installed Magisk Manager and uploaded boot.img to the phone
6. Patched boot.img with Magisk Manager (and if I remeber correctly DIDN'T UNCHECK Preserve AVB 2.0/dm-verity)
7. Certainly FORGOT to do anything with vbmeta.img
8. Did NOT erase cache and userdata
9. Flashed patched boot.img directly and WITHOUT --disable-verity or --disable-verification
10. Rebooted the phone.
Am I correct that my problem is the AVB/dm-verity part?
Why does the modified boot.img affect the recovery (I thought they were seperate)
Can I try something with SP Flashtool?
I do have a second intact device that I didn't dare to touch yet, if that helps resolving the issue (e.g. for SP Flashtool readbacks).
As said any advice is highly welcome. Please ask I you need any more information to help.
I did that too... Magisk patched boot .img process of rooting is the risky process , I bricked my device, got it into red state.. tried thick and thin to revive using various flash tools, unable to do it, finally went to a shop , got it fixed, go-to a good repair shop, if you go to the service center, they will say replace motherboard for 5 k , I hope it helps, do traditional unlock bootloader TWRP recovery then flashing Magisk zip method for rooting process.
Thank you for sharing! But doesn't red state mean locked BL plus non-stock firmware? I wish I could find any repair shop during this Corona lockdown... May I ask how much they charged you for having the phone reflashed?
cmfan said:
Thank you for sharing! But doesn't red state mean locked BL plus non-stock firmware? I wish I could find any repair shop during this Corona lockdown... May I ask how much they charged you for having the phone reflashed?
Click to expand...
Click to collapse
Yes, you are right , red state means that, I guess bcoz, I may have formatted it and ran again unlocked bootloader but it showed unlocking failed, but I thought that I had previously unlocked it so it should be unlocked but I forgot to do that app thing process of deep test again, and I was on Android 10 latest and patched boot img of previous version using magisk, now I understand what mistake I made, I should have used boot IMG of current version of a 10 , but still I am afraid of doing this magisk method of rooting by patching boot IMG bcoz repair cost me 800/- , and I found out on YT that the latest version of a 10 of my device doesn't readily allows twrp and flashing zip of magisk.... Plus there are half baked info on important things, this is new device for me, I have had rooted Samsung and Lenovo, but rooting this is kind of tricky, bcoz it's still new, I think.... Want to try .... But I m afraid.... Tried fastboot method of TWRP flashing but can't replace stock room, so I guess I can't root .....
Well, there is a tutorial on how to root here on XDA, and seems to be confirmed working. I just didn't know about the vbmeta part from earlier Android versions. Haven't you tried that?
cmfan said:
Well, there is a tutorial on how to root here on XDA, and seems to be confirmed working. I just didn't know about the vbmeta part from earlier Android versions. Haven't you tried that?
Click to expand...
Click to collapse
Thnx man, I have rmx 1825 , but the process would be same for my device, I would have to search for it...
cmfan said:
Thank you for sharing! But doesn't red state mean locked BL plus non-stock firmware? I wish I could find any repair shop during this Corona lockdown... May I ask how much they charged you for having the phone reflashed?
Click to expand...
Click to collapse
Hello, please check my reply to your reply on my thread. BROM mode is as known as "Emergency Mode" and should not be inaccessible. I will once again request you to try different key combinations and also if it's detecting as fastboot, ADB or Fastboot commands should be available. Please try typing adb reboot or fastboot reboot with minimal ADB and fastboot tools and let me know. If you want to personally message me, message my telegram. I will try helping you there.
Why is this thread showing solved !!! It's nothing solved here... Pls check and confirm
daeSundae said:
Hello, please check my reply to your reply on my thread. BROM mode is as known as "Emergency Mode" and should not be inaccessible. I will once again request you to try different key combinations and also if it's detecting as fastboot, ADB or Fastboot commands should be available. Please try typing adb reboot or fastboot reboot with minimal ADB and fastboot tools and let me know. If you want to personally message me, message my telegram. I will try helping you there.
Click to expand...
Click to collapse
I think there is no Emergency Download Mode in Realme devices.. pls guide ...
Ank Sak said:
Why is this thread showing solved !!! It's nothing solved here... Pls check and confirm
Click to expand...
Click to collapse
Hello. Please follow this guide.
Repair DEAD(HARD BRICKED) Realme 3 | 3i Tutorial
In this tutorial we are going to Repair Realme 3 (RMX1821) MT6771 Chipset. from being hard bricked (no charge, no recovery, no fastboot) using SP Flashtool. with the help of Bypass Utility "MTK-bypass" to disable bootrom protection(sla and daa)...
forum.xda-developers.com
daeSundae said:
Hello. Please follow this guide.
Repair DEAD(HARD BRICKED) Realme 3 | 3i Tutorial
In this tutorial we are going to Repair Realme 3 (RMX1821) MT6771 Chipset. from being hard bricked (no charge, no recovery, no fastboot) using SP Flashtool. with the help of Bypass Utility "MTK-bypass" to disable bootrom protection(sla and daa)...
forum.xda-developers.com
Click to expand...
Click to collapse
Thnx that's a life saver, I am afraid to go forward with the device, this is promising, I will try, I found out that the new version c17 os Android 10 I am unable to root by twrp magisk zip flashing method, twrp isn't installing, there's an .ofp extracter, but it gives virus with software, unable to do, even talked on WhatsApp and gave him Gmail id, will try this method , I wanted the SP flash tool method, it's simple and can readily restore the stock rom... Thnx Sundae.. daesundae ... What kind of name is that...?? .. chuckles...
Ank Sak said:
Why is this thread showing solved !!! It's nothing solved here... Pls check and confirm
Click to expand...
Click to collapse
This thread is about a Realme 6 (RMX2001 in my case). I've edited the very first post to immediately show the solution. Please check there or follow daeSundae's guide if you have a different device.
cmfan said:
This thread is about a Realme 6 (RMX2001 in my case). I've edited the very first post to immediately show the solution. Please check there or follow daeSundae's guide if you have a different device.
Click to expand...
Click to collapse
I saw everything that You posted, incidentally the YouTube video on this is on rmx1825 , thnx, whatever you posted it helped..