Related
TOTALLY EXPERIMENTAL ONLY FOR TEST
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.
Click to expand...
Click to collapse
Working :
- graphics, sound, touch screen
- sim card, mobile data, voice calls
- internal memory, sdcard
- wifi, bluetooth
- flashlight/torch
- camera
- fingerprint
- nfc
- battery percentage (fast charging, confirmed)
Not working :
- notification leds
- wrong battery percentage
- auto brightness
- tethering
- earphone not detected
- other not tested functionalities
How to install :
- Unlock your phone
- Download the CyanogenMod zip(s). (cm-13.0-20160916-UNOFFICIAL-passion_row.zip) Updated link
- Copy the CyanogenMod zip to internal or external sdcard.
- Install a compatible Recovery. (TWRP 3.0.2.0, CM) MUST INSTALL!!
- Boot into Recovery.
- Do a Factory Reset. (Wipe data & cache), SAVE YOUR DATA
- Flash CyanogenMod.
Optional:
- Install the Google Apps addon package (chose ARM64).
Device : https://github.com/kyotr/android_device_lenovo_passion_row
Kernel : https://github.com/kyotr/android_kernel_lenovo_passion_row
Vendor :https://github.com/kyotr/android_vendor_lenovo_passion_row
Hey anyone tried this rom?
While installing I am getting error like "This rom is for passion_row. Your device name is idol347." Can anyone tell me what is wrong?
daniyalhasan said:
Hey anyone tried this rom?
While installing I am getting error like "This rom is for passion_row. Your device name is idol347." Can anyone tell me what is wrong?
Click to expand...
Click to collapse
first you need to install new a recovery file, use fastboot to install one of these recoveries (TWRP, CM)
Command: fastboot flash recovery filename
Click to expand...
Click to collapse
Can you confirm whether this ROM contains VOLTE feature or not? Is there anything else you got not working? Share your experience please.
I also got the same error. Used twrp. Do I have to use yet another recovery?
mifiik said:
I also got the same error. Used twrp. Do I have to use yet another recovery?
Click to expand...
Click to collapse
Will only work with recoveries provided here . other recoveries ARE NOT COMPATIBLE
Ok, I'm going to try. I'll report. Thanks
After using suggested recovery I'm up and running. Besides bugs from the first post I found brightness not working (neither automatic nor manual) and some apps from the Play Store not able to install due incompatible.. (Chrome and some others). Wifi hotspot also not working. Everything else seems to be OK. Good job done!
Thanks for starting your work on this. Keep up the good work
Sent from my Lenovo P1a42 using XDA-Developers mobile app
My observations:
Wifi tethering and usb tethering not working.
Built in root not working(though triggered under developer options)
Automatic brightness not working(though brightness slider working flawlessly)
Notification LED not working
Great work @_kyo_ ....... kudos[emoji106] [emoji106]
Super su works.
Battery charging is slow . It would be nice if this issue is resolved . Thank you.
awesome work,
glad to see developments, 1st custom rom fr vibe p1
though few bugs i observed over previously notified by others,
-Coudn't unlock using fingerprint
i could register my my FP but when i try to unloack, it vibrate fr one time with error following no responce
-call volume cannot be adujusted
both in normal speaker n loud speaker mode
-headphone or earphones r not detected
Fingerprint unlock forks for me. I noticed volume adjustment problem too.
all bugs list till now
1-notification leds
2-wrong battery percentage
3-brightness not working >>>> automatic only
4-some apps from the Play Store not able to install due incompatible
5-Wifi hotspot also not working
6-Wifi tethering and usb tethering not working
7-Built in root not working >>>>> fixed by super su
8-Battery charging is slow
9-Coudn't unlock using fingerprint worked well
10-call volume cannot be adujusted
11-headphone or earphones are not detected
Click to expand...
Click to collapse
mohamed abd elmoaety said:
all bugs list till now
1-notification leds
2-wrong battery percentage fixed using gravity box
3-brightness not working >>>> automatic only
4-some apps from the Play Store not able to install due incompatible
5-Wifi hotspot also not working
6-Wifi tethering and usb tethering not working
7-Built in root not working >>>>> fixed by super su
8-Battery charging is slow
9-Coudn't unlock using fingerprint worked well
10-call volume cannot be adujusted
11-headphone or earphones are not detected
Click to expand...
Click to collapse
Please how did you fix the battery percentage bug with gravitybox? Thanks
Hello, this ROM is compatibile which version of Lenovo P1?
Vibe P1 P1a42
Vibe P1 P1c58
Vibe P1 Pro P1c72
or... Vibe P1 Turbo ?!? Thank you very much for the support
pickmod said:
Hello, this ROM is compatibile which version of Lenovo P1?
Vibe P1 P1a42
Vibe P1 P1c58
Vibe P1 Pro P1c72
or... Vibe P1 Turbo ?!? Thank you very much for the support
Click to expand...
Click to collapse
Vibe P1 P1a42
@_kyo_ is this ROM built from source or ported using copy paste methods? And was it really necessary to force a random name as the device name to make people use your custom recoveries? If you have source built any of the recovery or ROM can you please release your sources?
Ambient display also not working.
Hello,
I recently acquired the HomTom HT10 and I am really liking it so far. Trying to get more out of this device I started looking for viable methods to root it. So far, none of them has worked.
Specifications:
Software:
- Android Version: 6.0
- API Level: 23
- Android Security Patch Level: 2016-08-05
- Kernel Architecture: armv8l
- Kernel Version (in device info): "[email protected] 2016/06/03"
- Kernel Version (in CPU-Z): 3.18.22 (1473842401)
- Build Number: HOMTOM-HT10-Android 6.0-V01-20160914
- Custom Build Version: alps-mp-m0.mp9-V1.33_aeon6797.6c.m_P11
- Firmware download at the bottom of this page: http://homtom.cc/
- Bootloader is unlocked
- I can access the device using ADB and Fastboot
- The only bootmenu is accessible by holding down the Volume Up button while booting the phone. In this menu there are 3 options:
1. Recovery Mode: This shows a blank screen with a picture of a droid with an open chest and a red triangle floating over it, as well as the text "No Command" written above it.
2. Fastboot Mode: This shows a blank screen with the typical "Fastboot mode" text.
3. Normal Boot: Does what you would expect.
Hardware:
- mt6797
- MediaTek Helio X20
- Mali-T880
- Resolution: 1080 x 1920
- Ram: 3 GB
- Memory: 32 GB
Rooting methods I tried (for each method, the mobile and PC version was tried, if one was available):
- Framaroot: 2 Exploits choosable, both of them return Error #6 immediately
- Kingoroot: Error around 85%, can't read Chinese error message
- Kingroot: Root Failed
- iRoot (formerly vRoot): Root Failed
- Towelroot: after pressing the "make it ra1n"-button, the application gets stuck
- Root Genius: phone reboots twice, the PC tool gets to ~56 % and says "Root Failed"
- The Ultimate Guide to Rooting any Android Device Manually: Method 1 works, until I have to reboot into the recovery mode, Ubuntu just won't mount it. Method 2 relies on "psneuter", which gives the error "mmap() failed. Invalid argument". I presume it just doesn't work for my android version, maybe someone knows of an alternative?
http://forum.xda-developers.com/showthread.php?t=2684210
Does anyone have an idea how I could get root on this thing? Can someone maybe point me in the right direction how I would go about decompiling the manufacturer firmware and building a rooted image, or at least build a custom recovery? AFAIK there isn't even a custom recovery available yet.
On another note, I also found MOD Edit:- Links Removed. Could this be useful?
If I forgot to mention anything, let me know!
Thank you for reading this,
Greetings, Nukeer
Edit:
I have managed to root my device, though I had to deal with quite a few real-life issues, so I totally forgot about this thread. I apologize for this late reply, but I guess better now than never. Note: the following two paragraphs are also copied from a reply I wrote in another thread about this phone. If anyone can answer my questions, I'd really appreciate it.
I have the Homtom HT10 running the firmware Android-6.0-V01-20161202 and I was able to root the device using Kingo Root. It's been a while, but I think there were some additional steps to go through before this root worked. My question is if anyone here has had success in rooting one of the newer firmwares, since I'm not sure if this root would survive the firmware update and I wouldn't want to lose root access.
Also, does anyone know how to replace the Kingo Superuser app with Chainfire's version?
[Source for my reply: https://forum.xda-developers.com/an...omtom-ht10-t3564957/post72876549#post72876549 ]
Me too.
I also can not be.
ttp://hirachon.blogspot.jp/2016/10/root.html
also looking for a tutorial to root because i'm not satisfied with the current OS :
- losing connectivity: cannot receive calls (need to reboot or turn off/on SIM cards in settings)
- no 5Ghz Wi-Fi networks compatibility
- losing user preferences (language or default apps)
- froze and reboot if you set a password to lock your device (pattern or PIN)
- battery saving mode is too aggressive and not easy to manage
...
Hi guys!
Same specs here:
Software:
- Android Version: 6.0
- API Level: 23
- Android Security Patch Level: 2016-08-05
- Kernel Architecture: armv8l
- Kernel Version (in device info): "[email protected] 2016/06/03"
- Kernel Version (in CPU-Z): 3.18.22 (1473842401)
- Build Number: HOMTOM-HT10-Android 6.0-V01-20160914
- Custom Build Version: alps-mp-m0.mp9-V1.33_aeon6797.6c.m_P11
- Firmware download at the bottom of this page: http://homtom.cc/
- Bootloader is unlocked
- I can access the device using ADB and Fastboot
- The only bootmenu is accessible by holding down the Volume Up button while booting the phone. In this menu there are 3 options:
1. Recovery Mode: This shows a blank screen with a picture of a droid with an open chest and a red triangle floating over it, as well as the text "No Command" written above it.
2. Fastboot Mode: This shows a blank screen with the typical "Fastboot mode" text.
3. Normal Boot: Does what you would expect.
Hardware:
- mt6797
- MediaTek Helio X20
- Mali-T880
- Resolution: 1080 x 1920
- Ram: 3 GB
- Memory: 32 GB
Solution FIND ! ! !
KingRoot apk finally works !!! :victory:
I tried this version: V4.9.7
by this file: NewKingrootV4.9.7_C152_B341_xda_release_2016_11_14_20161115194410_105243.apk
IMPORTANT NOTE:
1) I find some bloatware that doesnt wipe out neither with a factory reset
2) the root is factoryreset resistant.
3) Some issue with Wathsapp only when sending stored images.
Best regards!
If you are happy with this please tnx me! :highfive:
If you have trouble, please share!
did not work
Westboy82 said:
NewKingrootV4.9.7_C152_B341_xda_release_2016_11_14_20161115194410_105243.apk
Click to expand...
Click to collapse
This NewKingroot apk did not work for me, no root available, same for version 5 from kingroot page.
I hope someone can figure this out soon.
ht20 / ht10 / root homtom
hello Nukeer,
have you found a way yet? i bought the ht20 a few weeks back, and would also like to root it, and if it works, plan to probably use replicant... already contacted them.. waiting.
any ideas? something we could share, work together?
there is a new firmware available:
https://forum.xda-developers.com/android/general/homtom-ht10-firmware-homtom-ht10-t3564957
This video describes the installation of TWRP and after the installation of SUPERSU within the TWRP Recovery in HomTom HT10
The same recovery and scatter file to flash it with SP_Flash_Tool i found it at the needrom.
Does anyone tried this method;
I don't have the phone yet so i cannot try if work.
Because i cannot post outside links search at the youtube for the video "HOMTOM HT10 TWRP и ROOT" from "vova snake" channel.
See the edit in my original post. I've done it, I managed to root my device.
Root did well
Hi guys, i could root using kingroot, it was an easy task. Greetings.
root HT10 with twrp and su
damaskos said:
This video describes the installation of TWRP and after the installation of SUPERSU within the TWRP Recovery in HomTom HT10
The same recovery and scatter file to flash it with SP_Flash_Tool i found it at the needrom.
Does anyone tried this method;
I don't have the phone yet so i cannot try if work.
Because i cannot post outside links search at the youtube for the video "HOMTOM HT10 TWRP и ROOT" from "vova snake" channel.
Click to expand...
Click to collapse
It's in Russian ?
here is one in english on youtube youtu.be/btdllA1vlqI
How to Root the HTC 10 and Install TWRP Recovery by RootJunky
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.
This is the simplest ATV, it starts without an initial Google account request, therefore it is suitable for pensioners and barig.
For revision P1
HTML:
https://mega.nz/#!Q19EmCzB!bGb9-KWiz2Tl8V8f8YEsnxgepq9ToW86tlF7S1BQjZ0
For revision P2
HTML:
https://mega.nz/file/QoljlQ6T#f6aVjQtz1sLJw1X-0EHz67aVyl51MoSn3a-UTdCfWW4
For revision P3
HTML:
https://mega.nz/file/Bw92VQjL#0PikKxROBJ1ekcvxolbHiV9fZVZZ3b8Yt5j8X2E5HBo
For revision V2
HTML:
https://mega.nz/file/dw9S2SbQ#8Rue9KZRi8s6EygVZfW_aEmiYb-10qMcHVkMW7mrKM4
UPD_20191214_V1.1: links are updated, noise canceling is disabled, support for gaming devices is expanded, after installation you can restore your DATA from TWRP if before were on the same firmware.
UPD_20191215_V1.2: the links have been updated, the sleep mode (USB power) has been fixed for turning on air mice, after installation you can restore your DATA from TWRP if you were using the same firmware before.
UPD_20191219_V1.3: links updated, stock recovery replaced with TWRP 3.3.1 by Sasvlad, Tweaks of the interface (a bit smooth), after installation, you can restore your DATA from TWRP if you were on the same firmware before. I hope this completes the refinement of this firmware
UPD_20200112_V1.4: the picture is without plasticine, OTAUPDATE is removed, AppDrawer is immediately in the application bar + in the band a set of applications, it added smoothness to the interface
UPD_20200221_v1.5 fixed sudden increase in volume when on CEC
Installation: standard via UBT.
The update files suggest that the builds are from 2019 but your comments are pointing to 2020, i am confused.
Thank you so much.
I can use .
Hi, thanks very much but how to flash it ? With Amlogic Burning Tools ? If yes, which version ?
Because I try 2 version, 3 cable, 2 computer, all usb port, and nothing is detect ( on recovery mode ) :'(
If anyone have TWRP Backup, it will be nice
Thanks
hi, i use x96 air V2, after up your V2 version it doesn't work but also not brick
[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