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 folks,
Today it's a great day for me : I have successfully patched the kernel to have a 100% working TWRP 3.2.1 for our Maze Alpha 4G.
I have port a Jemmini build for Bluboo S1 and I have patch the kernel to have a working touch panel
I have followed this Thead
For the Maze Alpha 6G version, you can test it and tell me please.
How to flash:
I Fastboot method (must unlock device) :
1- Reboot your phone in bootloader mode : adb reboot bootloader or phone off, press and hold at the same time POWER and Vol+ buttons
2- Connect your phone to your computer with adb/fastboot already installed
3- Unlock your bootloader : fastboot oem unlock (it will erase you data, only data)
4- Flash the recovery : fastboot flash recovery recovery_maze_alpha_4G_twrp-321.img
II SPFlashTool method (no need to unlock device) :
1- Download latest version of SPFlashTools.
2- Execute it and load the provided scatter (the recovery image must be in the same folder as the scatter and must be renamed to recovery.img) then press "Dowbload" button
3a- windows SPFlashTools users : phone off, press VOL+ and connect it to your PC (running SPFlashTool and waiting for phone connetion)
3b- linux SPFlashTools users : phone off and connected to PC , press VOL+ and POWER while your PC is running SPFlashTool (with sudo) and waiting for phone connetion.
Update : you can found here the latest version: TWRP 3.3.0 for MAze Alpha 4Ghttps://github.com/dreambo/android_device_maze_alpha/releases/tag/3.3.0
have a nice day.
Works great on Maze alpha 4G. Thanks.
But I forgot to save original recovery...
super_sonic said:
Works great on Maze alpha 4G. Thanks.
But I forgot to save original recovery...
Click to expand...
Click to collapse
You can get the original recovery from the stock rom designed for SPFlashTool, provided here
dreambo said:
You can get the original recovery from the stock rom designed for SPFlashTool, provided here
Click to expand...
Click to collapse
Thanks. Can you share stock recovery.img, if you have it? I have recovery-verified.img from V05 but I don't know if there is a new update and if size is correct: 11,54MB. Your TWRP recovery has got a size of 14.24MB...
Can you make a small procedure on how to install it? Will help many nOOb's out.
And people need to report back issues and successes !!!! Again I see many questions and people with issues that we seniors try to help out with that end up in no more response which to me is not done and not helping others.
I have a 6GB version that I could test on but at the moment I am using it for other stuff and I can't risk bricking it this week.
Would finally love to start some stuff happening on this phone.
Ok in the process of doing so on my 6GB/64GB version.
edit : congratz I now have a 'phone' that can only go into TWRP . Should have never ever done this!
Says no OS installed ... really nice
Edit 2: after hours wasted was able to get your zipped rom on the Maze but I got no boot with that TWRP, so flashed recovery-verified.img from the 6GB rom from Alpha I had downloaded ... It would then start up but show 4GB out of 6GB. No good but at least all the rest seemed to work. All other effort to get it going back with the proper kernel etc resulted in frustration.
So now to flash the official rom back via their tool... that one got me really frustrated and was completely my fault that I couldn't figure it out. But you know angry, frustrated, must get it back to work, can do this ... After all these years of toying with phones we are so used to pressing 'power and vol+ or vol-' together to make something work. Now in the end I re-read the manual again and saw that you only have to push vol+ and NOT vol+ and power together or it wont go in the mode it should go to make it flash!!
In case this happens : The best advice I can give to people is to download the proper MTK drivers. Search for vcom drivers for MTK and you will find.
Print out the instructions and mark every step you do to the letter. The flashing itself only takes like 3 or 4 minutes
lukesan said:
Ok in the process of doing so on my 6GB/64GB version.
edit : congratz I now have a 'phone' that can only go into TWRP . Should have never ever done this!
Says no OS installed ... really nice
Edit 2: after hours wasted was able to get your zipped rom on the Maze but I got no boot with that TWRP, so flashed recovery-verified.img from the 6GB rom from Alpha I had downloaded ... It would then start up but show 4GB out of 6GB. No good but at least all the rest seemed to work. All other effort to get it going back with the proper kernel etc resulted in frustration.
So now to flash the official rom back via their tool... that one got me really frustrated and was completely my fault that I couldn't figure it out. But you know angry, frustrated, must get it back to work, can do this ... After all these years of toying with phones we are so used to pressing 'power and vol+ or vol-' together to make something work. Now in the end I re-read the manual again and saw that you only have to push vol+ and NOT vol+ and power together or it wont go in the mode it should go to make it flash!!
In case this happens : The best advice I can give to people is to download the proper MTK drivers. Search for vcom drivers for MTK and you will find.
Print out the instructions and mark every step you do to the letter. The flashing itself only takes like 3 or 4 minutes
Click to expand...
Click to collapse
Haha I did the same exact thing..and managed to get it working after flashing it with the spflash tool but the trick is if you have Windows 10 latest version you won't be able to do this..at least I couldn't because of driver incompatibility so in my case:
1 I installed Windows 7 and installed mtk drivers for spflash tool
2.booted into twrp
2.1 if you can't boot into twrp or it doesn't turn on you can still try this
3.Start sp flash tool and download the zip the one(in case of trouble)that the moderator published
4. Load the scatter file and make sure that all of the files and the scatter are in the same folder.
5.click download and leave it like that
6.plug in your phone in fastboot if you can't try one of the following
6.1 just plug it in turned off and monitor spflash tool status
6.2 plug it in holding volume up key (just volume not power)
6.3 in twrp go to boot and boot into bootloader
And the tool should do the rest
If all else fails check the drivers one more time
After all that if you are feeling adventurous flash twrp one more time and do not factory reset through twrp ! Because that was the problem in my case and after you unlock bootloader boot your phone and go through the setup without setting the password because twrp will be locked.
Good luck.
frumac96 said:
Haha I did the same exact thing..and managed to get it working after flashing it with the spflash tool but the trick is if you have Windows 10 latest version you won't be able to do this..at least I couldn't because of driver incompatibility so in my case:
1 I installed Windows 7 and installed mtk drivers for spflash tool
2.booted into twrp
2.1 if you can't boot into twrp or it doesn't turn on you can still try this
3.Start sp flash tool and download the zip the one(in case of trouble)that the moderator published
4. Load the scatter file and make sure that all of the files and the scatter are in the same folder.
5.click download and leave it like that
6.plug in your phone in fastboot if you can't try one of the following
6.1 just plug it in turned off and monitor spflash tool status
6.2 plug it in holding volume up key (just volume not power)
6.3 in twrp go to boot and boot into bootloader
And the tool should do the rest
If all else fails check the drivers one more time
After all that if you are feeling adventurous flash twrp one more time and do not factory reset through twrp ! Because that was the problem in my case and after you unlock bootloader boot your phone and go through the setup without setting the password because twrp will be locked.
Good luck.
Click to expand...
Click to collapse
Wait a sec., missing a couple of things here.
1) Do you have a 6GB ?
2) In case you have a 6GB did you manage to get it working, rooted and all?
Your point 6) well I flashed mine on the latest 64bit win10 ... but.... if the phone is off and you connect the usb cable my phone tried to boot up either in twrp with no com port. Also booting it in bootloader doesn't make the comport visible so you can't flash.
The only way to make mine visible for the flashtool was to press vol+ and then connect the usb cable.
Btw I am glad someone finally responds and spreads information. A very good post! Your first 'thanks' well deserved!
I wonder where the guys are that I was trying to help. Did they throw their phones away or something? Sharing is caring I thought.
I want to root mine to alter the camera settings and the media xml file. I find it strange that our sensor, which is the same as in my wife's Xiaomi's, takes seriously bad pictures.
lukesan said:
Wait a sec., missing a couple of things here.
1) Do you have a 6GB ?
2) In case you have a 6GB did you manage to get it working, rooted and all?
Your point 6) well I flashed mine on the latest 64bit win10 ... but.... if the phone is off and you connect the usb cable my phone tried to boot up either in twrp with no com port. Also booting it in bootloader doesn't make the comport visible so you can't flash.
The only way to make mine visible for the flashtool was to press vol+ and then connect the usb cable.
Btw I am glad someone finally responds and spreads information. A very good post! Your first 'thanks' well deserved!
I wonder where the guys are that I was trying to help. Did they throw their phones away or something? Sharing is caring I thought.
I want to root mine to alter the camera settings and the media xml file. I find it strange that our sensor, which is the same as in my wife's Xiaomi's, takes seriously bad pictures.
Click to expand...
Click to collapse
Sorry forgot to mention I have a 4 GB version but since maze is not providing the roms on their website any further development will be limited..thank God for dreambo he is the only guy doing any work here and like you said nobody is responding to any questions asked..shame really because maze is a great phone with a terrible camera..which drivers did you use on Windows 10? because I tried a hundred of them and non of them recognize my phone..and in adb I can run the command fastboot reboot bootloader but after reboot none of the commands are working .
And yes I did manage to install twrp and root using magisk and I to hope that all those other guys didn't brick their phones
frumac96 said:
Sorry forgot to mention I have a 4 GB version but since maze is not providing the roms on their website any further development will be limited..thank God for dreambo he is the only guy doing any work here and like you said nobody is responding to any questions asked..shame really because maze is a great phone with a terrible camera..which drivers did you use on Windows 10? because I tried a hundred of them and non of them recognize my phone..and in adb I can run the command fastboot reboot bootloader but after reboot none of the commands are working .
And yes I did manage to install twrp and root using magisk and I to hope that all those other guys didn't brick their phones
Click to expand...
Click to collapse
This is the filename I used on Windows 10 VCOM Drivers (All MTK Devices & All Windows OS version).zip I think I downloaded it from XDA somewhere.
Also something you must know https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Another thing I experienced is that one USB connector is not the other one on a pc. Always connect it to the ones directly on the main board next to the other device outputs like audio etc. and preferably not go through ones that have been extended via a cable like the ones on top of the casing or so. Also a must have application is usbdeview.
Well should be easy to get it going if you can boot it into 'fastboot' then you can try as much as you want to. But djeeeeezzzz the letters are very small when you boot it with a power+volume up . Also check that volume up will toggle between 'fastboot', 'recovery' and 'normal start' and volume minus will select it, not the power button which would be more logical to me.
I might have another go at trying to get it working on my 6GB but it involves having a lot of time and knowing that I will get frustrated. Installing all apps and settings is also a time consuming thing. Once you have TWRP on it it all becomes easy to backup. So many things to test or try.
Maybe dreambo has an idea on how to get mine up to a 6GB one as it is probably only indicated in the kernel.
Anyway I will continue to write down my progress.
Ok more frustration. Done multiple things to try to get this running. It's good to know that the original rom is easy to install again after practice.
Take 1: Try to install clean 6GB rom and immediately install TWRP.
Results: Dreambo forgot 1 step and that is to allow OEM unlock in the developer options. If you do the adb command to unlock press volume up and it will unlock (very hard to see, very small letters on the display in bootloader mode)
Well TWRP starts but immediately I get a message 'mount decrypt data password' which I tried a couple of things but no go. Also googled... different solutions but always ending in a bootloop to TWRP
A possible solution that I read was to create a startup pin .... no go 'pin not valid'
Take 2: Take all the rom files and change the scatter file with the one dreambo provided.... Thought it was successful but ended up with the same Chinese recovery. Trying to figure out why since the filename was correct like indicated in the scatter file. Came to the conclusion that the original file was/is called recovery-verified.img and not recovery.img. Really really strange this one as in the original scatter file it also points to recovery.img. So this one I will have to investigate. Renaming the TWRP file to recovery-verified.img lead to a error during the initial scan of the flashtool.
So moral of the story is that I am back on square 1 and lost 2 hours today (plus putting all apps and settings back) today.
I get a bit lost, is this TWRP method only working with the 6GB or also with the 4GB version?
CYberdog11 said:
I get a bit lost, is this TWRP method only working with the 6GB or also with the 4GB version?
Click to expand...
Click to collapse
There is no fundamental difference between 6G and 4G version.
It must works in boat versions.
If you have issues with SPFlashTool try this (no need to install any drivers on Windows 10) :
Put the preloader.bin (found in the rom package designed for SPFlashTool) in the same folder as the recovery.img without checking it the list of partitions (only recovery must be checked) and click on Download to flash the recovery, as usual.
Perhaps SPFlashTool cannot read by himself the preloader in the EMMC, and we must provide it.
The linux version of SPFlashTool not works at this moment, I do not know why
With the SPflashtool I always get the error:
ERROR:STATUS_DA_HASH_MISMATCH (0xC0070004)
HINT
CYberdog11 said:
With the SPflashtool I always get the error:
ERROR:STATUS_DA_HASH_MISMATCH (0xC0070004)
HINT
Click to expand...
Click to collapse
From another thread:
mmakdz said:
google translate
Hello
I had the same problem, (error BROM ERROR: STATUS_DA_HASH_MISMATCH)
what I did: I use Windows 7 System
1- clear all drivers for smartphones with "usbdeview-2-17"
2- install Drivers "Drivers_Auto_Installer_v1.1236.00"
3- install "PdaNetA4170"
4- use "SP_Flash_Tool_v5.1708_Win" to flash the rom. first flash the preloader alone and then flash the others.
the problem was the bad installation of the drivers, after that everything went well for me.
try it can work for you too.
the mentioned software is easy to find on google
Click to expand...
Click to collapse
dreambo said:
There is no fundamental difference between 6G and 4G version.
It must works in boat versions.
If you have issues with SPFlashTool try this (no need to install any drivers on Windows 10) :
Put the preloader.bin (found in the rom package designed for SPFlashTool) in the same folder as the recovery.img without checking it the list of partitions (only recovery must be checked) and click on Download to flash the recovery, as usual.
Perhaps SPFlashTool cannot read by himself the preloader in the EMMC, and we must provide it.
The linux version of SPFlashTool not works at this moment, I do not know why
Click to expand...
Click to collapse
If there is no difference between the 4GB and 6GB then why did I literally spend days on trying this and documenting what happened?
lukesan said:
If there is no difference between the 4GB and 6GB then why did I literally spend days on trying this and documenting what happened?
Click to expand...
Click to collapse
Do you have the 2 versions of the phone and do you have notice any difference of the flashing procedure ?
dreambo said:
Do you have the 2 versions of the phone and do you have notice any difference of the flashing procedure ?
Click to expand...
Click to collapse
I only have the 6GB version of the Maze Alpha. But you wrote that the procedure should work for both versions. I think I wrote down what happened with mine if I installed TWRP.
I tried both the 'regular' flashing and then the full rom install with the trick to put the files in the directory and rename but both ended up as I've written in my previous post.
lukesan said:
I only have the 6GB version of the Maze Alpha. But you wrote that the procedure should work for both versions. I think I wrote down what happened with mine if I installed TWRP.
I tried both the 'regular' flashing and then the full rom install with the trick to put the files in the directory and rename but both ended up as I've written in my previous post.
Click to expand...
Click to collapse
From times to times, I notice trouble with flashing using SPFlashTools.
First (when I post my first post relating of the root) I use the linux version : no issues it works perfect, no need of any drivers!
Actually, no way to have it working on linux, why I do not know!
I have tried Windows 10 and I notice that we have to provide the preloader to have it working, as I write in my post.
In theory, and only in theory, the SPFlashTool must works the same manner in any phone with a Mediatek SOC.
But in reality, we have notice that with exactly the same phone the flashing procedure works for some users and not for others!
SPFlashTool is a very capricious software, there is no warranty to have it 100% working in any platform, even with the same OS.
dreambo said:
From times to times, I notice trouble with flashing using SPFlashTools.
First (when I post my first post relating of the root) I use the linux version : no issues it works perfect, no need of any drivers!
Actually, no way to have it working on linux, why I do not know!
I have tried Windows 10 and I notice that we have to provide the preloader to have it working, as I write in my post.
In theory, and only in theory, the SPFlashTool must works the same manner in any phone with a Mediatek SOC.
But in reality, we have notice that with exactly the same phone the flashing procedure works for some users and not for others!
SPFlashTool is a very capricious software, there is no warranty to have it 100% working in any platform, even with the same OS.
Click to expand...
Click to collapse
The thing is that I have no issue with flashing the software as I can perfectly flash the original rom. The problem is that when flashing the TWRP file, in both options by the way, so also via method 1, I get a boot loop.
The Developer Preview has ended. The official release has been released and can be found here https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265
The current (unofficial) Developer Preview is developed by @erfanoabdi This thread serves as a means to help folks from further discussing LOS16 within the Official Lineage 15.1 thread (to help prevent that thread from being both further hijacked and to prevent confusion from the two in conversation).
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Code:
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
Please remember this is NOT a final release. There WILL be bugs. It is also very possible that you could end up bricking your phone by attempting to install, use, or upgrade LOS16 and you do so at your own risk.
How to install Lineage 16.0 Developer Preview
!! Please read in full before proceeding !!
Remember to submit logs when reporting any errors.
Remember to be as detailed and as clear as possible on what actions you took which resulted in any errors.
Download the latest Official TWRP https://dl.twrp.me/payton/. - You want the .img file.
Restart your phone to your bootloader. - You do this by pressing and holding both your phone's power button and the lower volume key at the same time.
Once at your phone's bootloader, from your Windows Command Prompt (as administrator) or from your Linux Terminal (as root) run the following command to load TWRP:
Code:
fastboot boot '/your_path_here/twrp-X.X.X-X-payton.img'
Note: Be sure to use your path on where you have the file on your computer. Be sure to replace and use the correct file name for your file (Do not just copy and paste example posted here).
!! You will be wiping everything because this is a developer preview and bug reports are most helpful on a clean, fresh install !!
Regardless of what ROM you are coming from (stock or not), format your DATA.
Reboot your device to bootloader and reuse the previous fastboot command to load TWRP listed above.
Regardless of what ROM you are coming from (stock or not), wipe your device (all partitions).
Reboot your device to bootloader and reuse the previous fastboot command to load TWRP listed above.
Download "Copy Partitions Zip" - courtesy of @filipepferraz https://drive.google.com/file/d/1oiry9UfP2tf-5A6nQBF7pn2t2eSGKt0F/view
Upload "Copy Partitions Zip" to your phone using the "ADB Push" command to /sdcard/ (run as admin if on windows or as root if on Linux).
Code:
adb push copy-partitions-payton.zip /sdcard/
Now INSTALL "Copy Partitions Zip"
Reboot to your bootloader. - Stay at the bootloader screen (do not load TWRP)
Download the firmware for your phone
XT1900-1 Android 8.0
firmware_27.251.12_payton_retail_xt1900-1.zip
Only tested on
XT1900-1
XT1900-2
XT1900-5 (https://forum.xda-developers.com/showpost.php?p=76934354&postcount=173)
XT1900-7 (https://forum.xda-developers.com/showpost.php?p=76779696&postcount=14)
feel free to test on other Moto X4 models running 8.0.
XT1900-6 Android 8.0 - courtesy @filipepferraz
https://www.androidfilehost.com/?fid=674106145207492371
XT1900-1 Android 8.1 - courtesy @ptn107
https://www.androidfilehost.com/?fid=890278863836292604
tested on XT1900-7 as well (https://forum.xda-developers.com/showpost.php?p=76816113&postcount=92)
Latest firmware for payton_fi android 9 from PPW29.69-26 - courtesy @ptn107
firmware-29.69-26_payton-fi_xt1900-1.zip
Unzip on your computer.
User flash_all.bat if on windows as administrator OR ./flash_all.sh if on Linux as root.
Reboot your phone to bootloader
Reboot your device to bootloader and reuse the previous fastboot command to load TWRP listed above.
Download and locate the latest developer preview: https://androidfilehost.com/?w=files&flid=281597
You will upload these files to your phone using the "ADB PUSH" command to your /sdcard/ directory (as admin in windows or root in Linux). For example:
Code:
adb push lineage-16.0-20180921-UNOFFICIAL-payton.zip /sdcard/
Install your ROM.
Congratulations! You're done!
NOTE: The point of using a developer preview is to test the ROM itself. You can attempt to install TWRP after installing your ROM, just as you can reboot back to recovery after, and install OpenGapps, followed by Magisk, but that is NOT the true point of testing this ROM. While it may be useful to know of issues with those commonly used tools, the primary concern is the ROM itself at this time.
Remember to submit logs when reporting any errors.
Remember to be as detailed and as clear as possible on what actions you took which resulted in any errors.
MotoX4 said:
Remember to submit logs when reporting any errors.
Remember to be as detailed and as clear as possible on what actions you took which resulted in any errors.
Click to expand...
Click to collapse
Excelent Rom very good accuracy of battery, but usb adb is not working
Hi @erfanoabdi, I am really enjoying this ROM.
Question: Is there any way to replicate the Retail X4's One Button Nav? It seems to have implemented a press/long-press/longer-press for the fingerprint scanner. Not sure if something like this is in the AOSP code or not. It is really awesome for locking screen AND keeping Google Assistant.
---------- Post added at 08:05 PM ---------- Previous post was at 07:18 PM ----------
I have played around a it with flashing Generic System Images (GSI) over this ROM, and it seems to be quit compatible most of the Android 9 ones that I have tried.
It is awesome that this phone suddenly has many options to toy with (yes, I said it, it is a toy) due to the hard work of the devs Trebelizing (or is it Treble-izing?) our Moto X4!
---------- Post added at 08:09 PM ---------- Previous post was at 08:05 PM ----------
vmmiguel said:
Excelent Rom very good accuracy of battery, but usb adb is not working
Click to expand...
Click to collapse
USB ADB seems to be working fine for me. I am on the 9/29 version.
jhedfors said:
Hi @erfanoabdi, I am really enjoying this ROM.
Question: Is there any way to replicate the Retail X4's One Button Nav? It seems to have implemented a press/long-press/longer-press for the fingerprint scanner. Not sure if something like this is in the AOSP code or not. It is really awesome for locking screen AND keeping Google Assistant.
---------- Post added at 08:05 PM ---------- Previous post was at 07:18 PM ----------
I have played around a it with flashing Generic System Images (GSI) over this ROM, and it seems to be quit compatible most of the Android 9 ones that I have tried.
It is awesome that this phone suddenly has many options to toy with (yes, I said it, it is a toy) due to the hard work of the devs Trebelizing (or is it Treble-izing?) our Moto X4!
---------- Post added at 08:09 PM ---------- Previous post was at 08:05 PM ----------
USB ADB seems to be working fine for me. I am on the 9/29 version.
Click to expand...
Click to collapse
For me doesn't work, nothing appears in notificacions bars or even in fastboot can´t recognize my device...
Actually i have running this rom, but i don´t have GAPPS installed, and the adb is not working so i cant flash via fastboot the twrp for install my gapps, any suggerency to do?:good::crying:
jhedfors said:
Hi @erfanoabdi, I am really enjoying this ROM.
Question: Is there any way to replicate the Retail X4's One Button Nav? It seems to have implemented a press/long-press/longer-press for the fingerprint scanner. Not sure if something like this is in the AOSP code or not. It is really awesome for locking screen AND keeping Google Assistant.
Click to expand...
Click to collapse
Thanks for using this rom but you can enable it from
Setting system buttons and disable on screen nav bar
I couldn't get long hold and longer hold to detect in custom roms but still it's usable for home recent and back buttons
You can set hold home button to action something else then assist (lockscreen)
erfanoabdi said:
Thanks for using this rom but you can enable it from
Setting system buttons and disable on screen nav bar
I couldn't get long hold and longer hold to detect in custom roms but still it's usable for home recent and back buttons
You can set hold home button to action something else then assist (lockscreen)
Click to expand...
Click to collapse
Thanks. I am using the fingerprint navigation as you describe. I am using an app that detects a double-tap, which I am using to lock the screen.
Sorry for OT:
Is there any way to take the long-press away from Google Assist (and be able to re-assign it) short of UN-installng Google? When I "disable" it in the Google App, or even change the default assist app, long press fingerprint only prompts to re-enable Google Assist. It seems those settings only apply to long-press Home, but not long-press fingerprint. Google Assist has hijacked my fingerprint button!
Thanks again.
jhedfors said:
Thanks. I am using the fingerprint navigation as you describe. I am using an app that detects a double-tap, which I am using to lock the screen.
Sorry for OT:
Is there any way to take the long-press away from Google Assist (and be able to re-assign it) short of UN-installng Google? When I "disable" it in the Google App, or even change the default assist app, long press fingerprint only prompts to re-enable Google Assist. It seems those settings only apply to long-press Home, but not long-press fingerprint. Google Assist has hijacked my fingerprint button!
Thanks again.
Click to expand...
Click to collapse
I disabled the "google" application and stopped bothering with activating it again, it was the only way I found, because if you deactivate the assistant only when you keep it pressed the sensor sends the message to activate it xD
vmmiguel said:
Excelent Rom very good accuracy of battery, but usb adb is not working
Click to expand...
Click to collapse
I hope somebody to help me, last night i tried to update mi Lineage OS 16 (from erfanoabdi).
My device is unlocked bootloader, and i used the rom from nightly build (2018-21-09), it works fine and everything, the issue becomes when i look what was avaible a new update, so downloaded and install the new rom.
I do full wipe, after that i install the new rom, at this point everything its working fine, but after that when i changed the partition slot from A to B.
When i started to install the gapps they closed because it says what i am running Android 8.0, but its a mistake so i think that reboot the phone without install the gapps. So the phone starts well, so i decide again to boot into recovery (TWRP) to install the missing gapps.
When the device reboot in fastboot and i chosee the recovery option, the surprise was that TWRP was reemplaced by the stock recovery, and when i tried to flash the TWRP.img my device wont appear in fastboot mode, stays finding device and Windows wont recognized my phone.
I think the rom still no have usb adb support, so i cant flash TWRP
My device its unlocked and i was running the rom (but another nightly) .. without issues for a week ago... until i flashed this one
Now i have Lineage OS without GAPPS, without USB mode... Like the update from OPW 27 or 28 idk remember.
Thanks for read this i hope somebody can help me.
My device its a XT1900-4 in Android 9.0 without google apps, only have the essencial apps like phone dialer , sms, the very very essencials app. Like an phone from 2008 jhaha
I attach some information photos from the Rom that im running:
(System Running) fine thanks
https://ibb.co/bXC7ye
(ADB is switched on, but no appears nothing)
https://ibb.co/exGpBz
(I tried with everyone of the opcions
https://ibb.co/ekv5jK
and this is my currently fastboot:
AP Fastboot Flash Mode (Secure)
BL: MBM-3.0-uefi-641a15b-180224
Baseband: M660_7042.27.01.74R PAYTON_LATAM_CUST
Product/Variant: payton xt1900-4 32GB P4
CPU: SDM630 1.0 (6)
Console [NULL]: null
Tools Mode Config: DISABLED
POWER OK
flashing_unlocked
Software status: Official
Transfer Mode: USB Connected
At this point my windows so says to my device is Error in a request for the USB device descriptor.
i tried last_usb_google driver.
Motorola Device manager 2.5.4
Minimal adb fastboot 1.4.2
and nothing works fine.
In my recovery appears this:
Android Recovery
motorola/payton/payton
8.0.0/OPW27.57.25-6-10/12
user/release-keys
Use volume to...etc and then i used the (Apply update from adb)
says:
Supported API: 3
Stopping adbd. . .
Now send the package you want to apply to the device with "adb sideload <filename>"
I tried to navigate in the device with the terminal app, so i put this command in terminal to make ADB run
command adbd, and this appears on terminal:
adbd E 10-04 23:01:31 3819 3819 adbd_auth.cpp183] Failed to get adbd socket: success
adbd E 10-04 23:01:31 3819 3819 adbd_auth.cpp183] Failed to get adbd socket: success
i try to run command logcat.txt, but terminal cant move to sdcard.
i try to adb over network and that connect but can´t do anything because stuck on <waiting device>, i look the blankflash but
didn´t works to me, and in the configurations usb settings looks greyed so cant switch between then.
when i run the command ls i saw this files:
init.usb.configfs.rc
init.usb.rc
init.recovery.qcom.usb.rc
maybe there is my problem? Thanks for read, thanks to @erfanoabdi he works very hard to make this possible, i hope somebody can
help me.
vmmiguel said:
I hope somebody to help me, last night i tried to update mi Lineage OS 16 (from erfanoabdi).
...
When the device reboot in fastboot and i chosee the recovery option, the surprise was that TWRP was reemplaced by the stock recovery, and when i tried to flash the TWRP.img my device wont appear in fastboot mode, stays finding device and Windows wont recognized my phone.
...
Click to expand...
Click to collapse
Not sure if I understood all of your post.
On the MotoX4 there is no separate partition for the recovery, it is build into the system boot image / ramdisk. If you flash a new LineageOS or a new kernel youre TWRP is gone. So before you boot, you have to reflash TWRP. If you forgot to do this, you have to bring your device to fastboot mode (Volume down + Power 'till it boots to fastboot mode). Then boot it by "fastboot boot twrp-3.2.3-1-payton.img" to TWRP. If it has booted to TWRP recovery only then you can "adb push twrp-install-xxxx-payton.zip /sdcard" and install it from recovery. After that you should be able to directly reboot to recovery and flash what you need.
I always have all required "xxx.zip" on my microSDcard, so that I can flash them from TWRP without sideload or adb push. Remember to reboot to recovery after every "xxx.zip" flashed because of the A/B design of the MotoX4.
---------- Post added at 09:46 PM ---------- Previous post was at 09:41 PM ----------
Anybody else?
WLAN for me does not connect on lineage-16.0-20180929-UNOFFICIAL-payton.zip, if you have a hidden network (SSID). It will be shown as "saved" but does not try to connect.
Worked on lineage-16.0-20180921-UNOFFICIAL-payton.zip.
vmmiguel said:
Excelent Rom very good accuracy of battery, but usb adb is not working
Click to expand...
Click to collapse
USB is working for me (09/29)
For testing I changed my wlan SSID to visible on my wlan router and a second later, wlan is connected. Setting it back to unvisible drops the connection. So I think its's a bug in 09/29 LOS preview.
Gesendet von meinem Moto X4 mit Tapatalk
Just got around to trying the FM Radio app, and it is not working for me - working for anyone else? I did not check if it worked on 15.1...
jhedfors said:
Just got around to trying the FM Radio app, and it is not working for me - working for anyone else? I did not check if it worked on 15.1...
Click to expand...
Click to collapse
I'm trying too, does not work
FM not working here also... build from 21.09. 2018. - Don't want to upgrade to 2909, waiting for October build, September builds look obsolete now
Demoniackers said:
Rom Pixel Experience unofficial TREBLE Android 9 ARM 64 A/AB (GSI) Working (TRY IT)
...
Running almost everything, in Moto x4
-Magisk, modules, Volte, bluetooth.
I have not tried, NFC, Hotspot
Bugs: Headphone Jack, Second camera, One Button (fingerprint gestures) It is not deactivated
Could you solve the errors?
Click to expand...
Click to collapse
Wrong thread/forum.
Edit: it is VERY bad form to spam all the different threads that you have posted to. If you annoy people, they are less likely to want to help you.
PLEASE HELP!
Unfortunately I do not know how to report error logs but I will describe my issue the best I can.
I am on a moto x4. XT1900-1, Android One edition. Bootloader Unlocked.
I followed the steps to a "T". Everything went smooth with rom install but I noticed a couple things. When running the flash_all.bat file, everything but flashing the modem completes successfully. It gives a failed message.
Code:
PS C:\platform-tools\firmware> .\fastboot flash modem_a modem.img
Sending 'modem_a' (112640 KB) OKAY [ 2.806s]
Writing 'modem_a' (bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 2.830s
It does this for modem_a and modem_b.
When I boot to bootloader(fastboot), it shows Baseband: <not found>
I haven't finished setup to see if I get cellular service. My guess is NO. Can you please help? Why would it be failing to flash the modem. I am trying the 8.1 firmware for Project Fi.
Thank you.
reedc83 said:
PLEASE HELP!
Unfortunately I do not know how to report error logs but I will describe my issue the best I can.
I am on a moto x4. XT1900-1, Android One edition. Bootloader Unlocked.
I followed the steps to a "T". Everything went smooth with rom install but I noticed a couple things. When running the flash_all.bat file, everything but flashing the modem completes successfully. It gives a failed message.
Code:
PS C:\platform-tools\firmware> .\fastboot flash modem_a modem.img
Sending 'modem_a' (112640 KB) OKAY [ 2.806s]
Writing 'modem_a' (bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 2.830s
It does this for modem_a and modem_b.
When I boot to bootloader(fastboot), it shows Baseband: <not found>
I haven't finished setup to see if I get cellular service. My guess is NO. Can you please help? Why would it be failing to flash the modem. I am trying the 8.1 firmware for Project Fi.
Thank you.
Click to expand...
Click to collapse
I once did a quick Google search on this issue as I too faced this problem. It is safe to ignore. Allow me to explain:
This is safe to ignore. All it means is that your device already has a new firmware at that particular base. I, personally, originally used, for my device, XT1900-1 Android 8.1 - courtesy @ptn107 https://www.androidfilehost.com/?fid=890278863836292604 and the first time I used it (coming from STOCK) everything flashed without any issues. A few updates later and if I attempt to use it again, it proceeds to flash everything and it skips (soft fails) on 1 point while proceeding to do everything else. This is because, on that particular point, I likely have a newer firmware.
You should be able to proceed as normal and safely ignore that small error.
MotoX4 said:
I once did a quick Google search on this issue as I too faced this problem. It is safe to ignore. Allow me to explain:
This is safe to ignore. All it means is that your device already has a new firmware at that particular base. I, personally, originally used, for my device, XT1900-1 Android 8.1 - courtesy @ptn107 https://www.androidfilehost.com/?fid=890278863836292604 and the first time I used it (coming from STOCK) everything flashed without any issues. A few updates later and if I attempt to use it again, it proceeds to flash everything and it skips (soft fails) on 1 point while proceeding to do everything else. This is because, on that particular point, I likely have a newer firmware.
You should be able to proceed as normal and safely ignore that small error.
Click to expand...
Click to collapse
Thank you for the information! I was able to proceed and most things seem to work fine.
I noticed a couple bugs to report so far.
- External SD not available.
- Project Fi will not get LTE on US Cellular or Sprint.
- Messages app will not allow dark mode. Option is there but it does nothing. (I noticed this in the latest official build of LOS 15.1 as well. 20181002 build of 15.1 worked fine.)(I did install OGAPPS so this may be my fault.)
- Settings > Display > Color? does nothing. On LOS 15.1, I could switch it to be more saturated. I put a question mark because I am back on stock at the moment and don't remember exactly what the color option was called.
Other than that I was loving the smoothness of the ROM. I want to go back but have a hard time living without my project fi working as I live in a remote location and drive back-roads and need for my service to work across carriers.
Question, do we need to install any of the stuff found on the GSI version like the FBE_Disable etc? I don't know what GSI stands for or how that differs from this. Sorry for the noob question.
Thank you so much for the OP and sharing this. Really hope to see an October build soon that address some of the bugs.
reedc83 said:
Thank you for the information! I was able to proceed and most things seem to work fine.
I noticed a couple bugs to report so far.
- External SD not available.
- Project Fi will not get LTE on US Cellular or Sprint.
- Messages app will not allow dark mode. Option is there but it does nothing. (I noticed this in the latest official build of LOS 15.1 as well. 20181002 build of 15.1 worked fine.)(I did install OGAPPS so this may be my fault.)
- Settings > Display > Color? does nothing. On LOS 15.1, I could switch it to be more saturated. I put a question mark because I am back on stock at the moment and don't remember exactly what the color option was called.
Other than that I was loving the smoothness of the ROM. I want to go back but have a hard time living without my project fi working as I live in a remote location and drive back-roads and need for my service to work across carriers.
Question, do we need to install any of the stuff found on the GSI version like the FBE_Disable etc? I don't know what GSI stands for or how that differs from this. Sorry for the noob question.
Thank you so much for the OP and sharing this. Really hope to see an October build soon that address some of the bugs.
Click to expand...
Click to collapse
Here the external SD works as portable storage with ou a problem.
The LTE is a known problem.
I don't know about the dark mode from message app.
In the stock rom you need to deactivate night mode to change the color, in Los 16 you change it at Live Display.
Hello, I'm having the exact same issues as another use on here about the Oneplus 5, but on my older OnePlus. I have tried all the suggesting in the original thread 5 I'll paste the original post below:
https://forum.xda-developers.com/oneplus-5t/help/please-help-hardbricked-oneplus-5t-t3716057
Dear Community,
I just searched the past 2 days for a solution but I've not been lucky
Therefore I'd like to ask for help in this forum and hope there is some additional hint or hack I could try...:
So here's the situation:
OnePlus 5T (8/128) with a non booting or not "useful" OS (see last point what I've tried)
No TWRP or CWM
Stock Recovery present
Bootloader Locked
Allow Bootloader to be unlocked = FALSE
What I've already tried yet:
Flashing TWRP --> Not possible Bootloader Locked
Flashing regarding any other kinds like "update" or "flash all" as provided with TOOL_ALL_IN_ONE
ADB Sideload any available ROMS (Original "full" OP5T / FreedomOS / Omni8) --> ADB stops at 47% in Stock Recovery regardless of size of the ZIP file
Tried different versions of ADB (32 & 64 Bit / older & new / also with the LargeAddressAware approach / and on multiple PC's) --> Always same error (47%)
Stumbled upon the possibility to EmergencyDownload a factory flash due to Qualcomm chipset using the MSM-Download-Tool --> Only OnePlus 5 ROM available (no "T")
Mentioned EDL procedure works and OS is booting BUT neither Touchscreen nor USB OTG (for external mouse support) is working --> So I can't navigate and allow Bootloader to be unlocked again
Unfortunately I'm now stuck and have no more idea how to unbrick my phone again
What would help:
Any source to MSM-Download-Tool packed with a correct ROM for the OnePlus 5T
A Workaround to just flash TWRP via MSM-Download-Tool or Qualcomm's QFIL application in EDL mode
Some "hack" to bypass the locked Bootloader situation
Every appreciated Input you might have that I'm currently not aware of...
So PLEASE let me know of any approach that I could try or if you might have found a link or something else to a solution that might help me out of this disaster...
Many thanks in advance!
Tryouts due to your feedback:
@dreinulldrei - "fastboot boot recovery.img" tried with the original 5T Recovery.img also with blu_spark TWRP --> no luck...
I think I need a remote fix for this.
Thanks in advance!
Try this :
https://www.themefoxx.com/2018/01/unbrick-oneplus-5t.html
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..