Related
Installing ROMS & Such on the A700/701
For Extreme A700/Android Neophytes
Read It All BEFORE Beginning!
Important Links:
http://forum.xda-developers.com/showthread.php?t=1710755 ← Unlock Bootloader
http://forum.xda-developers.com/showthread.php?t=1791165 ← CWM
http://forum.xda-developers.com/showthread.php?t=1806980 ← CM10 Official Thread
http://forum.xda-developers.com/showthread.php?t=2056964 ← CM10.1 Official Thread
http://forum.xda-developers.com/showthread.php?t=2489708 ← CM10.2 Official Thread
-----http://get.cm/?device=a700 ← CM10 Download
-----http://goo.im/gapps ← Google Apps 4.1.2
http://forum.xda-developers.com/showthread.php?t=1995981 ← AOSP 4.2
http://forum.xda-developers.com/showthread.php?t=1952124 ← iconiaN
http://forum.xda-developers.com/showthread.php?t=1953917 ← Vorbeth’s EasyRoot ← Do This to Root!
http://forum.xda-developers.com/showthread.php?t=2004441 ← Vorbeth’s OC GPU Kernel
http://forum.xda-developers.com/showthread.php?t=1994294 ← CoolOne700
http://forum.xda-developers.com/showthread.php?t=2196266 ← IcOdiv for A701 & A700 based on CyanogenMod 10.1
http://forum.xda-developers.com/showthread.php?t=2219575 ← Evil Alex Purgatory A701
http://forum.xda-developers.com/showthread.php?t=2232411 ← 7comp based on RootBox
http://forum.xda-developers.com/showthread.php?t=2510004 ← Official PAC-man 4.3
Software You Will Use/Need (depending on your root method):
http://support.acer.com/us/en/product/default.aspx?tab=1&modelId=4318 ← Acer USB Drivers
http://developer.android.com/sdk/index.html ← Android SDK
General Information:
First off, this was never made adequately clear for new users (without going through a hundred different posts with hundreds of replies): You will be using the Android SDK and the Windows Command Prompt. When installing the Android SDK, change the directory to something easy like C:\SDK because you will be typing it a lot. The directory in that folder you will be using exclusively for this process is the “platform-tools” directory. This is where adb and fastboot are found.
In addition, you will need to activate ADB Debugging on your tablet. This is found by going to Settings -> Developer Options -> USB Debugging. If this isn’t done, you will get nothing accomplished. Yes, you will need to have your tablet connected through USB to your PC for this to work. I know there are other ways, but I’m writing this with brand new users in mind.
After you’ve got that set, you should go ahead and install the Acer USB Drivers. None of my computers could properly identify the tablet without the drivers. Speaking of quirks, 64GB microsd cards are not generally very friendly with CM10 or CWM even when formatted as Fat32. There are lots of issues I can’t find a workaround to. Consider using a 32GB until the kinks are worked out.
I’m also assuming you are currently running the JB OTA that was pushed worldwide in October 2012. If you are not, then there are a few extra steps when installing IconiaN. Although I compiled the instructions you’re reading, I had nothing to do with anything else. In fact, I didn’t write the codes used to install things through the command prompt….I just compiled all the information into one easy-ish to follow paper.
As usual, if anything in this causes a brick to your tablet, it was your decision. I’m just providing the information that has worked for me (repeatedly). Also, as I’m not a developer, nor am I very handy with editing files or trouble shooting things without actually handling them…….Ask your specific questions directly to those people in charge of the files (pawitp, Vorbeth, Moscow Desire, meier2009, odiv81 and alx5962). They’re the gurus at this..I am a plebe in their shadow.
TL;DR:
Install Android SDK to an easy directory.
Install Acer USB Drivers.
Unlock Your Bootloader: (codes from alx5962)
1. Open a command prompt in windows and navigate to the directory where adb is stored. For the sake of conversation, I’m going to call it “C:\SDK\platform-tools”
2. Plug your tablet into your computer through USB. It should automatically mount because you’ve installed the Acer USB Drivers and didn’t skip that step above. J
3. At the command prompt, enter the following:
Code:
adb reboot-bootloader
-- Allow the device to reboot.
4. Type Code:
Code:
fastboot oem unlock
5. Press the + Volume button to select Unlock then - Volume button to confirm.
6. Restart :
Code:
fastboot reboot-bootloader
----- I had issues on step 6. I tried that, and it rebooted to the bootloader screen. To be on the safe side without hard rebooting (not knowing what was going on), I used the command from Step 3. to reboot. This works for ICS and for JB bootloaders, I confirm I used the above steps on both.-----7. Confirmation of your unlocked status will be seen in the upper left hand corner of the screen.
Install Clockwork Mod Recovery: (all work & codes from pawitp)
Somehow I wasn’t able to install this properly (permanently) until last night (11/09/12). I’m still not entirely sure what I did differently, but I’ll try to document it here. The safest version of CWM is 6.0.1.5. Don’t attempt anything without that version or better. I’ve heard that at this time the touch version isn’t working properly, so be sure to download the original style CWM.
To navigate CWM, the following bit of information will come in handy (especially if you’ve never used it before.) Use the ‘Vol-‘ and ‘Vol+’ buttons to navigate up and down and the ‘Power’ button to select your choice. When you have made a choice it will sometimes give a screen with a ton of “NO” options with only one “YES” option (usually near the bottom). Like any good video game, if you scroll upwards, you can get to the bottom of the screen faster.
1. Place the CWM file you downloaded into your “platform-tools” directory. For the sake of being easy to install, I changed the file name to ‘recovery.img.’
2. Open a command prompt in windows and navigate to the directory where adb is stored. For the sake of conversation, I’m going to call it “C:\SDK\platform-tools”
3. Plug your tablet into your computer through USB.
4. At the command prompt, enter the following:
Code:
fastboot flash recovery recovery.img
5. At this point, you have flashed CWM to the system, BUT you will now need to boot into CWM using :
Code:
fastboot boot recovery.img
The caveat here is that you will need to install either a custom ROM or unencumbered boot.img (kernel) NOW. If you do not install one, flashing CWM was pointless because stock recovery will overwrite it at next reboot. When prompted at reboot (leaving CWM after flashing a ROM) you should choose to keep CWM. This was sort of a miscommunication between the devs and myself, but meier2009 and Moscow Desire cleared it up.
-----Step 5. does NOT install recovery, but forces your system to boot into CWM by pushing the file to your A700 from your ‘platform-tools’ directory.-----
For Future Reference: Enter recovery…(JB):
a. With system powered off, press and hold ‘Power’ and ‘Vol -‘
b. When the system vibrates, release the ‘Power’ button.
c. When the system vibrates a second time, slide your finger from ‘Vol-‘ to ‘Vol+.”
d. When the system vibrates a third time, release that button.
Install pawitp’s CM10.1 OR IcOdiv (A701): (all work & codes from pawitp)
Download the CM10 nightly from the official Cyanogen page and grab the Google Apps file (optional, but you won’t have market without it) listed in the links section. Despite what people say, I have always been unable to install from my external SD card. Instead, I save the zip files to the root/main directory of the internal SD. Save BOTH FILES to internal SD at this time. This has always worked for me, but your mileage may vary. You do this at your own risk, blah, blah, blah.
1. Boot your A700 into CWM using the steps outlined in Step 5. (or 6) from “Install Clockwork Recovery Mod.”
2. Backup your system by navigating to “backup and restore” by using the ‘Vol-‘ and ‘Vol+’ buttons to navigate up and down and the ‘Power’ button to select your choice.
3. At this point, there are two options for you. “backup” and “backup to external_sdcard”…. I have never been able to mount my 64GB Fat32 external_sd in CWM. Try a smaller card if you have one available (I don’t). If you can backup to external, that is probably necessary when coming from stock. I would only backup to internal if you are just updating from an older nightly or previous rom.
4. On the main screen, assuming you’re coming from stock JB or ICS, you will need to do a couple of wipes. I’m positive the first is necessary, and have read in other parts of threads and other forums that the other two wipes are needed, but as they’re both called “cache,” I went ahead and did both (with no ill effects).
Select “wipe data/factory reset”
Select “wipe cache partition”
Select “advanced” and navigate to “wipe dalvik cache”
Go back to the main menu.
5. From the main menu, select “install zip from sdcard”.
6. Select “choose zip from sdcard” and scroll down to the CM10 zip file. Press the ‘Power’ button to select and confirm.
After this has successfully installed, you can choose to install Google Apps or not. I’m assuming you will want to install them because…well…who doesn’t?
7. To install Google Apps, follow Steps 3 and 4 from above, but this time you will choose the gapps zip file instead of the CM10 zip.
8. Reboot Device & Enjoy well sorted Jelly Beans.
Install iconiaN: (all work & codes from Vorbeth)
At the moment this is my favorite. It is one version number (4.1.1) behind CM10 (4.1.2), BUT it is compatible with my SD card, and is similar to the stock experience …. only faster and without the bloatware. The only reason it is second in this guide is because of the alphabet (C before I & P before V).
The latest updates to the ROM bring the latest GAPPS and firmware. meier2009’s 4Way Reboot Mod is also included (and rocks).
1. Boot your A700 into CWM.
2. Follow Steps 2-6 from above if coming from stock JB (or CM10, or CoolOne700) with the exception that you’re installing the iconiaN zip (not CM10, duh). Also, iconiaN comes with v4.2 Google Apps pre-installed, so no need for Step 7.
-----2.a. If coming from stock ICS, you will need to install the Jelly Bean Firmware (Found in the Aroma Setup of the ROM)
3. If coming from an older version of iconiaN, you shouldn’t need to do the wipes, but go ahead and do the backup just to be safe.
4. Reboot Device & Enjoy well sorted Jelly Beans.
-----On a side note, I went ahead and installed BusyBox (https://play.google.com/store/apps/details?id=stericson.busybox) not sure if this was necessary, but I am suffering no ill effects from having it running on my tablet. -----
Install Vorbeth's OC GPU Kernel: (all work & codes from Vorbeth)
This is a custom kernel (as of this writing available only for the A700) that overclocks the Tegra 3 from 1.3Ghz to 1.5Ghz. There has been a noted improvement in gaming performance using this kernel.
1. Boot your A700 into CWM.
2. From the main menu, select “install zip from sdcard”.
3. Select “choose zip from sdcard” and scroll down to the iconiaN Kernel zip file. Press the ‘Power’ button to select and confirm.
4. Reboot Device PLAY SOME GAMES! WEE!
Install Vorbeth’s EasyRoot: (all work & codes from Vorbeth)
If for some reason you’re happy with stock and just want a very simple way to ROOT, then this is for you. Using this kernel will cause OTA to stop working (or you will have to edit the updater-script) and remove all the file checks. The latest update has made all previous instructions null, and it is now exceedingly easy to install ROOT on your A700. Awesome! Still, this does require an unlocked bootloader.
1. Download and extract the EasyRoot ZIP on your computer.
2. Locate and double click the file 'easyroot.bat'.
3. Follow all onscreen instructions.
4. Profit.
CoolOne700: (all work & codes from meier2009)
This is the new kid on the block. meier2009 has included three different install options in this ROM including Full (rooted stock), Small (all the Acer bloatware removed), and Custom (Choose what you want.) It’s definitely one to keep an eye on. Custom install is very handy. He’s also got his 4Way Reboot Mod which adds all our favorite reboot/recovery features. Sweet! Also, BusyBox and SuperSU are included on install, so you don’t need to worry about that.
1. Boot your A700 into CWM.
2. Follow Steps 2-6 from CM10 Install if coming from stock JB (or CM10, or iconiaN) with the exception that you’re installing the CoolOne700 zip (not CM10, duh). Also, CoolOne700 comes with Google Apps pre-installed, so no need for Step 7.
-----2. a. If coming from stock ICS, you will need to install the Jelly Bean Firmware (Found in the Aroma Setup of the ROM)
3. If updating from an older version of CoolOne700, you won’t need to do any of the wipes, but it is always a great idea to do the backup.
4. Reboot Device & Enjoy well sorted Jelly Beans.
Code:
6. If upon reboot, you hit the old system recovery, you will need to reflash the recovery.img OR just work around it by doing:
Code:
fastboot boot recovery.img
-----Step 6. does NOT install recovery, but forces your system to boot into CWM by pushing the file to your A700 from your ‘platform-tools’ directory. I had to use this method to install CM10 because I was never able to get CWM to install. Your luck may be different.-----
THAT´s the Trick my Friend !
Install recovery with
Code:
fastboot flash recovery recovery.img
AND THEN
Code:
fastboot boot recovery.img
Install any ROM and if you´re rebooting and asked to FIX Recovery, answer YES, then it will be leaved there !!!
With this way your also able to start CWM Recovery temporary
only use
Code:
fastboot boot recovery.img
then CWM will start, you can flash anything and after that CWM is gone, because the Stock Recovery is always inside the Recovery Partition
Makes sense then how I finally ended up with CWM actually installed on my tablet. Were the original instructions from pawitp mistaken, or just incomplete?
ExtremeRyno said:
Makes sense then how I finally ended up with CWM actually installed on my tablet. Were the original instructions from pawitp mistaken, or just incomplete?
Click to expand...
Click to collapse
Lost in translation...
ROFLMAO
Added more info last night and have now included the AOSP 4.2 to the links. Keepin' this bumped & updated.
Thanks for posting this excellent How To! I used it to install CM10.
I can confirm the backup to external backup functionality does work with a 8 GB MicroSDHC card. One thing you could do to bypass the external vs internal SD card discussion is to use sideloading. I used it to both install CM10 and the Google Apps and it works nicely. Just select Update through sideload in CWM and then enter 'adb sideload <filename>' on the command line and everything works nicely.
Also for the real beginner you could may be suggest backing up all user applications using Titanium Backup in order to easily restore them after flashing a mod.
Bumping thread back near the top. Lots of people got an A700 for the holiday and it seems many of them are bricking or at least screwing things up using outdated methods or strange new forms of CWM from other forums.
Also, thanks for the info, SanjuroE. Appreciated, and I can honestly say I never knew how to do the sideloading thing. I didn't actually realize that was what it was as on my old tablet (three years ago) sideloading was always in reference to installing from the external SD.
This guide was awesome. Many thanks for this.
I flashed CWM 6.0.3.1 via fastboot.
After that I tried fastboot boot recovery.img but it doesn't work.
On the display:
Booting downloaded image.
But nothing happens ??
Can anyone help me ??
schlex2010 said:
I flashed CWM 6.0.3.1 via fastboot.
After that I tried fastboot boot recovery.img but it doesn't work.
On the display:
Booting downloaded image.
But nothing happens ??
Can anyone help me ??
Click to expand...
Click to collapse
Loot at
http://forum.xda-developers.com/showthread.php?t=1791165
Post #166 to end of thread.
cfgh said:
Loot at
http://forum.xda-developers.com/showthread.php?t=1791165
Post #166 to end of thread.
Click to expand...
Click to collapse
Thanks mate!
I tried another recovery.img and than everything went fine!! :good:
USB driver link is not working.
papars said:
USB driver link is not working.
Click to expand...
Click to collapse
Check this : http://forum.xda-developers.com/showpost.php?p=58172023
Many files available, including Drivers
I can't connect my iconia a700 to PC (Windows 10) is say: device not found. Any help?
I install USB Driver, but in Device managers shows Acer Iconia Tab a700 with yellow worming sign.
Driver Issues WIN10
goralpm said:
I can't connect my iconia a700 to PC (Windows 10) is say: device not found. Any help?
I install USB Driver, but in Device managers shows Acer Iconia Tab a700 with yellow worming sign.
Click to expand...
Click to collapse
Hi,
I have the same issue and it took me hours to even find a driver from ACER. But even after the installation I cannot get the tablet to work stable. I installed general MTP drivers which gave me access to the "adb reboot-bootloader" command but during the reboot the tablet gets stuck on the Acer logo screen and does not boot into the bootloader. I have to unplug the tablet and only then I get the white text in the top left corner of the screen saying "starting Fastboot USB download protocol". But that is it. I assume that fastboot would use the Acer drivers to access the tablet but I don't have any for windows 10.
My question: Could somebody post drivers for Windows 10 for the A700/A701?
Thanks
realshadow
realShadow said:
Hi,
... ...
My question: Could somebody post drivers for Windows 10 for the A700/A701?
Thanks
realshadow
Click to expand...
Click to collapse
I had exactly the same problem. The solution was give here: https://forum.xda-developers.com/showthread.php?p=48915118
You don not need Acer driver.
- Wayne
Dear NS forum - my colleague has crespo work phone.Last year I rooted and installed custom ROM for all my co-workers. The Nexus S user came to me with a problem; lately has many force closures and is very slow. I booted it into recovery & got the Android on its back with red triangle --> this is Stock recovery, right?
Not sure how CWM disappeared and got replaced by stock recovery.. but that seems the case. Am I correct that -
1. I need to load my PC with Samsung USB drivers to communicate with phone while in fastboot/download mode?
2. I need to install ADB SDK on my pc too?
3. I need to enter fastboot/download mode and flash a custom recovery?
Kindly help confirm the steps required, am I missing a vital step? Which recovery is best suited ... I have no preference over TWRP / CWM.
Lastly, I am very much out of touch with latest ROMs, appreciate any advice on a simple ROM, maybe 4.2 is best...
appreciate any help, I used to know all this stuff but I moved to Note 2 a year ago. Cheers.
Hey, I just read about Wug toolkit, is this a suitable tool for my issue ?....seems I could use it to flash a recovery for this phone which magically reverted to stock recovery .
http://www.wugfresh.com/nrt/
Hey folks, here I look forward to guide the Google Nexus S users of the XDA Community to go custom with their Samsung Nexus S. I shall try to put forth the most prevailing steps to make my way to your minds. Also I will use the fastboot method to accomplish custom during this entire guide. Before we put our hands on the device and begin with the instructions, I would like to state some general terms, for your ease. :good:
Terms & Understanding
* What is Bootloader and Why do we need to Unlock?
A bootloader is a boot initializing component which is generally locked by the device manufacturer to avoid any messing around with the OS. We need to unlock it for the same reason. Once unlocked it will allow us to change the boot sequence and modify the OS in accordance of our needs.
* What is Rooting?
It is a process of gaining root privileges over an Android subsystem. Rooting an Android device is easy in most cases. If you will to Install custom ROMs, kernels, other patches or addons to your Android device, rooting is what you will need. It can be achieved in two ways; either by manual method (using fastboot) or by automatic method (using toolkit or software) . Here, I am going to follow the manual method by using fastboot commands.
* ClockworkMod, what is it?
In short, CWM; It is a secondary recovery system created by Koush (Koushik Dutta), which adds enormous features like wiping partitions, flashing flash able .zip files like ROMs, kernels, patches etc to the stock AOSP recovery. Visit ClockworkMod website for more.
* What does Custom ROM means?
These are the aftermarket Android firmware which are not official supported by the OEM (Original Equipment Manufacturer). They are made available to the Android public by Android developers and contributors all around the world. Custom ROMs are either built from Google’s source code i.e AOSP (Android Open Source Project) or are modified versions of the device manufacturer’s ROM (Stock ROMs or Factory ROMs) with additional tweaks and extend functions which are not delivered with the Stock ROMs. Some of the popular Custom ROMs include CyanogenMod (CM), Android Open Kang Project (AOKP), MIUI, Codename Android (CNA), Oxygen, ParanoidAndroid and many more.
* What is Custom Kernel?
A Kernel is a bridge between the applications and the actual data processing done at the hardware level, In simple words, it is the communication between the hardware and software of an Operating System. In Android world, Custom Kernels play a vital role since they provide the users with several features including changing CPU frequencies, modifying the boot sequence and boot scripts and other features too.
* What are Google Apps (Gapps)? The name speaks for itself. Gapps are Google apps for Android available in flash-able zip format. Most of these applications can now be found and updated via the Google Play Store.Some of the apps include the Google Play Store itself, Google Talk, Google Sync (for adding and synchronizing Google accounts), Google Backup Transport, Car Home, Gmail, Google Maps, YouTube, Google Search, Google Voice Search, Google Music, and Google Docs. In some Custom ROMs, the Google Apps are included. These are usually stock ROMs, smaller or less-common ROMs, or those from areas where intellectual property laws are less commonly obeyed. But many AOSP ROMs, most famously CyanogenMod and AOKP, do not include the Google Apps due to licensing issues. They are after all proprietary code owned by Google and not included in the Android Open Source Project.
Disclaimer
Early necessary requirements
* At least 60% of battery to ensure no random shutdowns due to low battery.
* Backup your storage manually. Also your text messages and contacts using some backup app.
* Install Google and Samsung USB drivers from here
* A compatible USB data cable for undisturbed connection between PC and device.
* Enable USB Debugging in your device’s settings [Settings > Developer Settings > USB Debugging].
* A PC with Windows OS.
* Download Required files
* Extract the downloaded NexusS_files.zip to the desktop. So now you will have a folder named "NSFiles" on your desktop which beholds all the needed files during the process.
Please make sure to follow every single instruction mentioned during the guidelines. This will resist you from any mishaps during the process. Lets begin!
Unlock Bootloader
NOTE: Unlocking the bootloader will erase all the data on the phone as well as SD storage. So be sure to back everything up.
1. Reboot your Nexus S into bootloader mode by pressing volume up + power buttons simultaneously until you see the bootloader screen.
2. Connect your device to the PC via the USB data cable.
3. Open the extracted folder "NSFiles" that we have have on the desktop. On an empty space inside the folder, press shift and right click and then select "Open command prompt here". This will execute a new CMD window which is already cd'ed to the folder's location.
4. Type in CMD:
5.
6. You will now receive a message on the screen. Use the volume keys to highlight "Yes" and select it using the power button.
7. Your bootloader is now unlocked.
8. Highlight and select "Reboot" to reboot your device.
9. You have successfully unlocked your Nexus S bootloader.
Installing Custom Recovery
1. Reboot your phone into bootloader mode by pressing volume up + power buttons altogether.
2. Connect it to the PC via USB data cable.
3. While in the "NSFiles" folder on your desktop, press shift + right click on an empty space and go to "Open command promopt here". This will execute a command window which is already cd'ed to your current location.
4. To Install ClockworkMod touch 6.0.1.0
Type in CMD:
5. To Install ClockworkMod non-touch 6.0.1.0
Type in CMD:
6. To Install TWRP 2.3.1.0
Type in CMD:
7. The CMD prompt will indicate when the flashing is complete, it barely takes a few seconds.
8. Do not exit the bootloader mode, since this is the way to boot into recovery.
9. Now to boot into your new custom recovery, highlight "RECOVERY" and select it using the power button.
Rooting the Nexus S
If you plan to use the stock (factory) ROM, it is preferable to root. Otherwise, all the Custom ROMs out there already have root access.
The mentioned process is recommended to carry out using ClockworkMod Recovery.
1. Download the latest SuperSU flash-able root package. [Chainfire's SuperSU Thread]
2. Power off your device and boot into the bootloader mode by pressing volume up + power buttons simultaneously until you see the bootloader screen. Highlight"RECOVERY" using the volume buttons and select it using the power button.
3. Now, your Nexus S is in recovery mode.
4. Go to "mounts and storage" > scroll to the very last and select "mount USB storage".
5. This will mount your device's storage to the PC.
6. Drag the downloaded "CWM-SuperSU-v0.98.zip" to the root of your storage.
7. Select "unmount" to exit the USB storage mode.
8. Go to "install zip from sdcard" > "choose zip from sdcard" > select the "CWM-SuperSU-v0.99.zip" you placed in the storage and flash it.
9. Once flashed, select "reboot system now"
.
You now have your device rooted. You can officially declare yourself as the true master of your device.
Install Custom ROMs
Installing a ROM is quiet a simple process, you can say that it is the easiest of all.
1. First, you need to choose a suitable ROM that meets your requirements.
2. Once you have chosen, download the ROM's .zip (flash able zip file) as provided by the Author/ Developer .
3. Also make sure to download specific Gapps and other add-on if provided by the developer himself. [If not, download generic Gapps from here]
4. Put the downloaded files to your SD storage either by using USB mass storage directly or by mounting USB storage in recovery mode.
5. Reboot your Nexus S into Recovery mode. Power off your device and boot into the bootloader mode by pressing volume up + power buttons simultaneously until you see the bootloader screen. Highlight"RECOVERY" using the volume buttons and select it using the power button.
* Using CWM:
wipe data/factory reset.
Go to "mounts and storage" > "format /system".
Go to "install zip from sdcard" > "choose zip from sdcard" > select your ROM .zip file that you placed in step #6. Flash it.
Gapps are the next to be flashed just after flashing the ROM. So, flash Gapps following the same way as the ROM. further if your are provided any add-on in a flash able zip format you can flash it the same way after flashing the ROM and Gapps successfully.
Once everything has flashed successfully, select "reboot system now".
* Using TWRP:
Go to "Wipe" > "System" and "Factory Reset".
Go to "Install" > choose the ROM .zip file and flash it.
Gapps are the next to be flashed just after flashing the ROM. So, flash Gapps following the same way as the ROM. further if your are provided any add-on in a flash able zip format you can flash it the same way after flashing the ROM and Gapps successfully.
When flashed, go to "Reboot" > "System".
Your phone will now boot into the custom ROM.
Install Custom Kernels
1. Download the flashable zip package of your desired Custom Kernel.
2. Connect your device to PC via USB cable in USB Storage Mode.
3. Drag the downloaded kernel zip package to the root of your device's storage.
4. Disconnect the device from PC.
5. Power off, now press the volume up button and the power button altogether until you see the bootloader screen. Use the volume keys to highlight "Recovery" and select it using the power button.
6. Your device shall now be in recovery mode.
* Flash using CWM:
"advanced" > "Wipe Dalvik Cache"
"install zip from sdcard" > choose zip from sdcard" > now browse and select the kernel zip package that you placed in your storage root during step #3.
Select "Yes".
Your Kernel will now flash to your OS and replace your current kernel.
When it has successfully flashed, select "reboot system now".
* Flash using TWRP:
"Wipe" > "Dalvik Cache"
"Install" > now browse and select the kernel zip package that you placed in your storage root during step #3.
Your Kernel will now flash to your OS and replace your current kernel.
When it has successfully flashed, go to "Reboot" and select "System".
You now have Custom Kernel installed on your Nexus S.
NOTE: Before choosing any Custom Kernel, do verify that the Kernel is meant to be flashed on your present Android OS version.
Congratulations! You shall now enjoy the full packed potential of your wonderful Nexus S.
If you have got any questions/ queries or you're stuck anywhere in the mid process, comment here. I will try my best and provide you an helping hand. 
Sent from my Nexus S using XDA Premium 4 mobile app
In order to keep this thread clean, please use this one to discuss about Development, Support or Software Updates.
ROMs:
To avoid any possible issue, do not forget to backup your NVRAM so that you won't risk to lose your IMEI. How-to: http://www.anythingultimate.in/2015/11/how-to-backup-your-nvram-partition.html
Custom ROM
- CyanogenMod 13 Beta 2 by "smurad-05": https://mega.nz/#!kMcRwTDb!1yrNzrP_XvqGyPcXzNF9eSRKfj1DpFixkUaNz_3OPAY
Stock (Android 6.0)
- 20161202: https://yadi.sk/d/rYoOTrUT32xDuL or http://www.leagoo.com.my/support/firmware/
DO NOT USE THE "Format All & Download" OPTION IF YOU CARE ABOUT YOUR IMEI! Choose "Download Only" instead.
Previous Releases:
- 20160909: http://leagooftp.com.my/M series/M5..._WF562G.LEAGOO.M0.HB.H.SSA.B18.0909.V3.03.zip
- 20160808 by "smurad-05": https://mega.nz/#!8V93SYaI!E4FOHWBxCFU6TKFmjguu7x3A3590Zt2W-c9KgNLgOLU
Flash Tool
- SP Flash Tool v5.1628 for Windows & Linux: https://mega.nz/#F!dYUm0TbB!SWeMLb5Wu1NbRzTPQ8-s_A
Recovery:
- TWRP (Universal), use the Scatter that comes with the latest Stock ROM linked above: https://github.com/VRNWALLE/Android/raw/master/MT6580/Leagoo m5/TWRP/recovery.img
Root:
Rooting Methods (if you are on Stock ROM)
- SuperSU (flashable using TWRP): http://forum.xda-developers.com/apps/supersu
Extras (Root-Only):
Customization
- Xposed Framework: http://forum.xda-developers.com/showthread.php?t=3034811
Useful Third-Party Apps:
Battery Life
- Amplify: https://play.google.com/store/apps/details?id=com.ryansteckler.nlpunbounce&hl=en
- Greenify: https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en
CM13 & TWRP added to first post.
dear my freind, how to install twrp?
thanks
@yamani_25 - Haven't done it myself, but first root your phone (see bottom of http://giveawaytricks.in/install-cyanogenmod-13-leagoo-m5/) then install TWRP the same way but using the recovery.img that's in the TWRP.3.0.2 zip file.
vladhed said:
@yamani_25 - Haven't done it myself, but first root your phone (see bottom of http://giveawaytricks.in/install-cyanogenmod-13-leagoo-m5/) then install TWRP the same way but using the recovery.img that's in the TWRP.3.0.2 zip file.
Click to expand...
Click to collapse
I think install TWRP first than the device can be root. CMIIW
Sent from my M5 using XDA Premium 4 mobile app
yup, first you need TWRP for root the phone with SuperSu..
waiting for tutorial too..
from my x500 on TT
tutorial for installing custom recovery (twrp) and how to root
Hi guys! Here's a tutorial for installing custom recovery (twrp) and how to root Leagoo M5 cellphone.
First turn on the cellphone, go to "Settings>About phone" and enable "Developer options" by tapping on the "Build number" multiple times. Then go one step back, enter the "Developer options" and turn it on, and also enable the "OEM unlocking" and "USB debugging" options
Now you need to install custom recovery by following these steps:
1. plug the cellphone into pc, unzip and manually install drivers by going to "control panel>device manager" (select the device which needs drivers).
drivers are located here
https://drive.google.com/file/d/0B4PwJKhC6foZZnBzY0RPQnhHX2s/view?usp=sharing
2. download to pc and unzip the twrp custom recovery zip file
https://drive.google.com/open?id=0B4PwJKhC6foZc1czcnZtRXQ4eUU
3. download to pc and unzip the Sp Flash tool zip file
https://drive.google.com/open?id=0B4PwJKhC6foZcWJQVThGTGhzaTQ
4. download to pc, but do not unzip the "super su" file needed for root
https://drive.google.com/open?id=0B4PwJKhC6foZQzA0OGtYRTVRWnc
Now copy this "supersu" zip file to cellphone (e.x. into "Download" folder). Once you're done, disconnect the cellphone from pc and turn it off.
5. go into "Sp Flash tool" folder and run "flash_tool.exe" application. Click on the "Download tab" at the top and then on the "Scatter-loading" button to select a path to Scatter file which is needed to flash custom recovery. The file is located in the "TWRP_3.0.2" folder and it is named "MT6580_Android_scatter.txt". The mode for flashing should be "Download only". When you're sure that everything is setup correctly click on the "Download" button located in the top left part of the screen.
6. Now take out a battery from cellphone, wait 5 seconds, put it back in, and just connect the cellphone. Do not turn it on.
Windows (PC) should recognize the device, and the flashing process should start.
Note: if it says that there is no driver, then manually install it by following procedure on step 1.
When the flashing is done you'll see a green checkmark. It's ok now to close the app and to disconnect the cellphone from the pc.
7. Cellphone will boot to startup menu, you should choose "Recovery" to enter TWRP custom recovery.
When you're in recovery go to "Mount" and mount (select) following partitions: protect_f, protect_s, nvdata, System, Cache and Data.
Now it's time to perform root. Go back from "Mount" screen, tap on "Install", find and select "SuperSU_PRO_v2.76_patched_Cobra1111.zip" file and flash it.
When the flashing is done click on "delete cache and dalvik cache", and then reboot cellphone.
8. Let the cellphone boot, it should take a few minutes. When it's booted you'll see the "SuperSU" app installed on your cellphone homescreen.
You're done! Enjoy!
Note:
I've collected these files on the internet. All of credits should go to their authors, so please thank to them!
One more thing. I would advise you to perform nandroid backup of your cellphone. Go into twrp recovery and perform backup (all partitions), save it to sd card and also copy that backup to pc, just in case something goes wrong.
Bye,
cuks
@cuks [emoji482]
from my x500 on TT
tutorial - how to update youtube app
as you all know, youtube app on the Leagoo m5 is an very old version. in order to update it you need to do the following:
note: you have to have a rooted phone
1. install file manager app which can access system partition (es file explorer, root explorer, etc.)
2. start file manager, go to /system/priv-app and move the folder named "Youtube" to another directory outside /system, e.g. to /sdcard/Download
3. restart the phone
4. install the youtube app from the google play
enjoy!
cuks said:
as you all know, youtube app on the Leagoo m5 is an very old version. in order to update it you need to do the following:
Click to expand...
Click to collapse
ARGH, didn't noticed this, but really, the youtube app got frozen every time on the stock rom. That's why i changed to this Cyanogen.
That's the reason why I wrote this tutorial
What are your experiences with cm rom? Are you satisfied? Is there any bugs? What's about battety life?
cuks said:
That's the reason why I wrote this tutorial
What are your experiences with cm rom? Are you satisfied? Is there any bugs? What's about battety life?
Click to expand...
Click to collapse
Not sure about battery life sorry, i'm trying to keep it charged
But i still have problems with youtube (however i'm not an experienced user): sometimes it halts, mostly in 720p/HD videos. The picture freezes, audio is working. Sometimes the video gets zoomed to the left upper corner with a black banner in the left. This could be an app-problem though.
cuks said:
That's the reason why I wrote this tutorial
What are your experiences with cm rom? Are you satisfied? Is there any bugs? What's about battety life?
Click to expand...
Click to collapse
Oops, fingerprint sensor doesn't work with CM.
Well, that's bad.
I have thought that the cm rom has the all functionality.
Better to stay on stock rom then. Only problem with it is sending images from within whatsapp, because it works on only one awkward way.
i wrote this before, without kernel source fingerprint cant work, same problem on my Leeco Le 1s..
from my x500 on TT
I cant scan the whatsapp web QR code with stock rom... (Whith third apps i can)
Today Leagoo launched a new patch LEAGOO_M5_FreemeOS_20160728_TEST with some bug fixed.
Is there a way to un-root after fixing YouTube? MobileIron refuses to work on a rooted phone, probably because it's a security hole.
Thanks!
you can unroot directly from SuperSu apk.. try it..
from my x500 on TT
Hello guys,
i have a problem with my battery ( drain out too fast - 25% in 30 min - and charge really slow - full charge in 6h+ !!! )
I suspect that this is caused due to the official update i made but the strange thing is that my mother's m5 with the same update is ok.
Is there any " official " way to go back to the original version to check it without doing all this process you analyzed ?
Ps. I checked my apps / settings, cleared chase, made factory reset, changed charger, checked my battery with apps and is in a good condition,
so i concluded that problem has to be there. Any ideas ?
divinitygr said:
Hello guys,
i have a problem with my battery ( drain out too fast - 25% in 30 min - and charge really slow - full charge in 6h+ !!! )
I suspect that this is caused due to the official update i made but the strange thing is that my mother's m5 with the same update is ok.
Is there any " official " way to go back to the original version to check it without doing all this process you analyzed ?
Ps. I checked my apps / settings, cleared chase, made factory reset, changed charger, checked my battery with apps and is in a good condition,
so i concluded that problem has to be there. Any ideas ?
Click to expand...
Click to collapse
GPS on maybe?
from my Leagoo M5 on TT
Hello everyone, lets root your ulefone power 5 and if you want: flash another rom. I'm kinda new here so don't mind if I'm telling things in a stupid way.
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.
*/
Ok, first of all, massive shout out to @gamr13 and @Dukino and @CarelMinnaar for providing some of the files.
Original threat: https://forum.xda-developers.com/android/help/ulefone-power-5-twrp-root-t3848501/
Link to the website I copied and translated the guide from: https://www.chinahandys.net/android-9-auf-dem-ulefone-power-5-anleitung/
Code:
If you are using any custom rom on your phone, I strongly
recommend reflashing your whole phone with the original
firmware provided by ulefone. I'll add the link.
I assume you know how to flash, otherwise search on youtube or
request it and I'll add a guide.
Most files you may need and worked in my case:
MediaFire
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
More files in the spoiler below.
Let's begin!
First of all, make sure your phone is recognized by your pc and use a good cable. (the original one broke pretty quickly in my case)
Next, go to system and search for 'build number'.
Tap it untill it says: you are now developer.
Go to developer options and enable: OEM unlocking. Then power your phone off.
Next, download the fastboot and adb zip file I provided. If you already use adb and fastboot, download the recovery zip and you know how it works.
Extract the 'android' folder and put it on the root of your system disk (mostly /C).
Next, go to your command prompt and type: cd \android
Now you start your phone in bootloader. Press and hold volume up and power and let your phone cycle untill you enter bootloader.
Select 'fastboot'.
Plug your phone into your pc and type in the command prompt: fastboot devices
Now you should see the serial number of one device (in my case it was something like ABCD1234567890). If not, install some fastboot drivers and use device manager to select the fastboot driver for your phone.
Then, type: fastboot oem-unlock
Select Yes on your phone and let it reboot.
Re-enter fastboot on your phone.
To be sure: fastboot devices
Flash your recovery using: fastboot flash recovery TWRP_3.2.3_Ulefone_Power_5_AND_5S.img
Then, you need (maybe not but just do it) to reboot straight into bootloader. So press volume up and power untill it shows the bootloader, and then select recovery.
Now your phone may be encrypted or something like that. Select 'Wipe' and accept.
Next, put your gsi (A only, arm64), gapps and/or your decrypt file on your sdcard and flash it!
Known bugs:
- VoLTE - I needed to use a simcard from a different provider to get calling working.
- Hotspot
- Seems sticky to 2.4G?
- MTP not working in recovery
- When waking up your device you may encounter some weird behaviour. Just wait a second and it's gone.
Spoiler: The old guide
Files:
https://mega.nz/#!N2hijYAB!0LLshTYgW...SUfOKpV5BELo4A (seems to be down and dated)
or
http://www.mediafire.com/folder/55lxwzgdd938t/ulefone_power_5
or
https://drive.google.com/drive/folders/1totRbNzS1RBeSO66WW2O0hG2kPGbGERl?usp=sharing
So, the method.
1.) In the files above you will find a file ulefone power 5 twrp root. Extract it and find the map called SP_Flash_Tool. Open this and run the flash_tool.exe. Please download the firmware.zip and the flashtool.zip and extract them. Put the decrypt.zip on your sdcard. (in some cases you need also the 'MT65xx_USB_VCOM_DRIVERS.zip' to install properly)
2.) Once opened the flashtool.exe, go into the options menu, click the connection tag and make sure USB is selected. make sure its set to Full speed and auto detect.
3.) Browse through the map sp flashtool and use the MTK_AllInOne_DA.bin file as the DA file (may be selected by default).
4.) Select the scatter file found in the firmware folder with all the .img files. Its called: MT6763_Android_scatter.txt
5.) While unplugged, hold the volume up and power button to load the phone into it's bootloader mode.
(if your phone is bricked in any screen skip this step) Turn your phone totally off.
6.) Set the SP flash tool to download only and press the download button to start the download.
7.) Plug your phone in and as expected, nothing will happen.
8.) Now, hold the volume up and power button continuously. Keep holding it until the SP Flash tool starts start downloading and the bottom bar loads things. Be sure you immediately loose the buttons, otherwise it soft-bricks itself so you have to start the download again.
9.) Be patient and wait until you get the green check mark, then unplug your phone.
10.) Boot directly back into bootloader. (vol. up and power, hold it untill you get the fastboot screen. Sometimes it takes up to 4 reboots), select and boot recovery.
11.) Now it's all for you! Put something on your sdcard and flash it. Mine seems to be broken so I used an usb stick, wich is working fine. MTP is not working in the recovery.
12.) CarelMinnaar published the new decrypt file, wich I thrust more than the previous russian one. Put it on your sdcard, do a full wipe and install. This should ban the forced encryption.
12.)
A.) For root: flash the magisk .zip file from the files above or search on the internet for the right one.
Thanks to @gamr13
1. Reboot to TWRP
2. MAKE A FULL BACKUP (every partition checked)
3. Mount System and Vendor
4. Go back to the main screen
5. Advanced > File Manager
6. Go to Vendor
7. Go to the "lib" folder
8. tap libdirect-coredump.so and Copy File
9. Go to /system/lib
10. paste the file in here
11. Go to /vendor/lib64
12. Copy libdirect-coredump.so
13. Paste in /system/lib64
14. Install Magisk
15. Reboot
16. Go to Magisk > Download > Search for "SafetyPatch" by hackintosh5
17. Reboot and enjoy
Click to expand...
Click to collapse
B.) 1. For another rom: search overhere for a system.img Download the A only variant. I'll keep you updated below. I am not using this phone frequently anymore, so updates may come later. @gamr13 will keep you updated
2. Wipe cache, dalvik cache, data and System.
3. Select flash .img and flash the .img at your System.
4. Flash magisk or other mods.
5. There may be some bugs. Sms was not working on the phh treble for me. The launcher crashed also.
13.) Boot up
14.) Enjoy! Feel free to ask anything.
Got some pm's asking what to do if stuck on boot/recovery, this video explains the return to stock process. In short: start spflashtool, select the scatter file in the stock firmware, select download only, firmware upgrade or download and format. Plug your cable in. Then click start, and press vol. up and power until you hear the 'new device found' sound on your pc and let it go. Then just reboot.
Feel free to use his files or mine. Doesn't really matter.
Working gsi images
These gsi images are tested on this phone:
Android 8.1
https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
bugs: sometimes the screen flickers when powering on. (once or twice per month)
Android 9
https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
bugs: a bit laggy. It takes up to 30 seconds to wake up from just screen off. Maybe a bug with the sleep state. When you use your phone frequently you don't suffer from this.
Thanks to @gamr13 :
Alright boys, yet another stride made today.
I've done some extensive testing on some Generic System Images for the Ulefone Power 5. This GSI seems to be the most stable I've used so far and best of all, it has root built-in (of course, it's LineageOS).
This is the only one I've gotten to work with ViPER4Android and root. Quick note that this still does have the screen flicker on the lock screen, but it's not as bad in this ROM compared to others I've tried.
Android Q GSIs currently do not work on the Ulefone Power 5, I've tried and fought hard with 'em but nothing. So, Pie it is for now.
Note: Magisk DOES NOT work. Please do not flash it on this ROM or you will break root access and need to reflash the system image.
First things first:
https://sourceforge.net/projects/andyyan-gsi/files/
1) Download the A-ONLY ROM.(avN): https://sourceforge.net/projects/an...309-UNOFFICIAL-treble_arm_avN.img.xz/download
2) Make a backup of your stock ROM as it is, just in case in TWRP.
3) WIPE System, Data, Cache and Dalvic in the Advanced Wipe section of TWRP.
4) Flash the image as a System Image in TWRP.
5) Flash Open Gapps
7) Reboot into ROM
8) Enable Developer Options and enable root for apps and adb
9) Download ViPER4Android 2.5.0.4 (This is critical as the newest release will not work)
10) Install the driver
11) On every reboot you will have to go into V4A and go to Settings > Turn on developer mode > Disable SELinux
12) Enjoy Android Pie with ViPER4Android on your Ulefone Power 5.
Click to expand...
Click to collapse
Android 11
Havoc os
[11][OFFICIAL] Havoc-OS 4.1 [ARM64/ARM/A64][A/AB/AB-VNDKLITE][GApps/Vanilla]
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel. Has a refined Material Design 2 UI crafted by @SKULSHADY. Many useful features that will blow your mind. All you can dream of and all you'll ever need. Just flash and enjoy... General...
forum.xda-developers.com
Not the quickest, but looks nice with the pixel inspired interface. No extra bugs found.
Handy thread!
I can’t get Magisk working though on any GSIs. I don’t ever get a prompt to allow root access to an app or even with it set to automatically grant, nothing happens and apps don’t detect it, yet, Magisk is installed and Magisk Modules install and work no problem.
Weird issue.
oes20 said:
These gsi images are tested on this phone:
Android 8.1
https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
bugs: sometimes the screen flickers when powering on. (once or twice per month)
Android 9
https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
bugs: a bit laggy. It takes up to 30 seconds to wake up from just screen off. Maybe a bug with the sleep state. When you use your phone frequently you don't suffer from this.
Click to expand...
Click to collapse
Does Magisk work for you on these GSIs?
gamr13 said:
Does Magisk work for you on these GSIs?
Click to expand...
Click to collapse
It works on (i guess) the android 8 gsi. I do not recommend magisk, as it messes with your /vendor partition. That partition can not be factory reset other than re-flashing the whole recovery/system/vendor/radio etc. Magisk is also not optimized for this device. Tweaks like viper4androidfx won't work. I don't use my phone anymore at this moment, so any tips, tricks or new information is always welcome to ensure that everybody can get the same good experience
oes20 said:
It works on (i guess) the android 8 gsi. I do not recommend magisk, as it messes with your /vendor partition. That partition can not be factory reset other than re-flashing the whole recovery/system/vendor/radio etc. Magisk is also not optimized for this device. Tweaks like viper4androidfx won't work. I don't use my phone anymore at this moment, so any tips, tricks or new information is always welcome to ensure that everybody can get the same good experience
Click to expand...
Click to collapse
That reply gave me serious doubt that you know a single thing about what you're doing. If it touches /vendor, you flash stock vendor.img in fastboot mode, ez pz. Not that it matters at all since nothing will get messed up at all. Magisk works perfectly fine on stock ROM. V4A works on stock, but when I use any GSI then no apps that require root work at all.
gamr13 said:
Handy thread!
I can’t get Magisk working though on any GSIs. I don’t ever get a prompt to allow root access to an app or even with it set to automatically grant, nothing happens and apps don’t detect it, yet, Magisk is installed and Magisk Modules install and work no problem.
Weird issue.
Click to expand...
Click to collapse
It is a problem, I know. We can't do anything than reporting these problems to the Magisk team and hope for help. In my case, Magisk worked for root, but not for the modules. I got also knocked out of Snapchat because of Magisk. Just one of those little things that are part of our development hobby
gamr13 said:
That reply gave me serious doubt that you know a single thing about what you're doing. If it touches /vendor, you flash stock vendor.img in fastboot mode, ez pz. Not that it matters at all since nothing will get messed up at all. Magisk works perfectly fine on stock ROM. V4A works on stock, but when I use any GSI then no apps that require root work at all.
Click to expand...
Click to collapse
In my case I got root acces working in Magisk. I apologize for that part about the vendor. You are right about that. I am trying my best to share my experience. I am no expert in anything.
Alright boys, yet another stride made today.
I've done some extensive testing on some Generic System Images for the Ulefone Power 5. This GSI seems to be the most stable I've used so far and best of all, it has root built-in (of course, it's LineageOS).
This is the only one I've gotten to work with ViPER4Android and root. Quick note that this still does have the screen flicker on the lock screen, but it's not as bad in this ROM compared to others I've tried.
Android Q GSIs currently do not work on the Ulefone Power 5, I've tried and fought hard with 'em but nothing. So, Pie it is for now.
Note: Magisk DOES NOT work. Please do not flash it on this ROM or you will break root access and need to reflash the system image.
First things first:
https://sourceforge.net/projects/andyyan-gsi/files/
1) Download the A-ONLY ROM.(avN): https://sourceforge.net/projects/an...7-UNOFFICIAL-treble_arm64_avN.img.xz/download
2) Make a backup of your stock ROM as it is, just in case in TWRP.
3) WIPE System, Data, Cache and Dalvic in the Advanced Wipe section of TWRP.
4) Flash the image as a System Image in TWRP.
5) Flash Open Gapps
7) Reboot into ROM
8) Enable Developer Options and enable root for apps and adb
9) Download ViPER4Android 2.5.0.4 (This is critical as the newest release will not work)
10) Install the driver
11) On every reboot you will have to go into V4A and go to Settings > Turn on developer mode > Disable SELinux
12) Enjoy Android Pie with ViPER4Android on your Ulefone Power 5.
Android 10 and TWRP...
Me. I tested 10 different roms of Android 10 and none works correctly .. I always stay on the Android logo that lights up in a loop. if you find information and manipulations or roms that work and are stable, send me the link or download. Thank you. And if you also find a new TWRP custom 3.3.0 or 3.3.1, put the download here. Thanks ?
gamr13 said:
Alright boys, yet another stride made today.
I've done some extensive testing on some Generic System Images for the Ulefone Power 5. This GSI seems to be the most stable I've used so far and best of all, it has root built-in (of course, it's LineageOS).
This is the only one I've gotten to work with ViPER4Android and root. Quick note that this still does have the screen flicker on the lock screen, but it's not as bad in this ROM compared to others I've tried.
Android Q GSIs currently do not work on the Ulefone Power 5, I've tried and fought hard with 'em but nothing. So, Pie it is for now.
Note: Magisk DOES NOT work. Please do not flash it on this ROM or you will break root access and need to reflash the system image.
First things first:
https://sourceforge.net/projects/andyyan-gsi/files/
1) Download the A-ONLY ROM.(avN): https://sourceforge.net/projects/an...7-UNOFFICIAL-treble_arm64_avN.img.xz/download
2) Make a backup of your stock ROM as it is, just in case in TWRP.
3) WIPE System, Data, Cache and Dalvic in the Advanced Wipe section of TWRP.
4) Flash the image as a System Image in TWRP.
5) Flash Open Gapps
7) Reboot into ROM
8) Enable Developer Options and enable root for apps and adb
9) Download ViPER4Android 2.5.0.4 (This is critical as the newest release will not work)
10) Install the driver
11) On every reboot you will have to go into V4A and go to Settings > Turn on developer mode > Disable SELinux
12) Enjoy Android Pie with ViPER4Android on your Ulefone Power 5.
Click to expand...
Click to collapse
8 Days later and I can confirm the ROM has been really stable with no issues other than the lock screen flicker which rarely happens, especially compared to other ROMs. Battery life has had a significant increase even when putting the phone under heavy usage (Call of Duty: Mobile and other games). Performance has shown a decent increase compared to the stock ROM. All in all, very impressed with the substantial improvements the GSI has brought over the stock Oreo firmware that came with this phone.
Can not install ANDROID 10 AOSP v201 !
Hello, I tested all versions of Android 10 phhusson and none works ..
phhusson offers to do this manually but I do not understand where to put it and how to run it!
phhusson: "need to manually setprop ro.skia.ignore_swizzle true"
If you have a solution to my problem, tell me here because I'm tired of Android 9 .. I'd like to upgrade to the latest version and not bother with this Android 9 .. Thanks
Android 10 GSIs currently do not work with the Ulefone Power 5.
gamr13 said:
8 Days later and I can confirm the ROM has been really stable with no issues other than the lock screen flicker which rarely happens, especially compared to other ROMs. Battery life has had a significant increase even when putting the phone under heavy usage (Call of Duty: Mobile and other games). Performance has shown a decent increase compared to the stock ROM. All in all, very impressed with the substantial improvements the GSI has brought over the stock Oreo firmware that came with this phone.
Click to expand...
Click to collapse
Tried to install the .xz gsi-image in TWRP but that doesn't work. Can anybody tell me how to install this image, because in TWRP you can only choose between .zip and .img install. Thanks in advance!
fernseher said:
Tried to install the .xz gsi-image in TWRP but that doesn't work. Can anybody tell me how to install this image, because in TWRP you can only choose between .zip and .img install. Thanks in advance!
Click to expand...
Click to collapse
You have to extract the file and then you will have an .img
Extract it with Winrar or 7ZIP
PetroChina said:
You have to extract the file and then you will have an .img
Extract it with Winrar or 7ZIP
Click to expand...
Click to collapse
This!
A guy was able to install Android 10 with another TWRP
I will soon receive the recovery on Facebook,
I am impatient for me and for all of you who tries to
install Android 10 without success, I hope to have it this week!
I'll let you know about Ulefone Power_5's friends <3
https://1drv.ms/u/s!AidaoCKFpLudgeJAwtAZTJlaLIV2EQ?e=6N3RaD
PetroChina said:
I will soon receive the recovery on Facebook,
I am impatient for me and for all of you who tries to
install Android 10 without success, I hope to have it this week!
I'll let you know about Ulefone Power_5's friends <3
https://1drv.ms/u/s!AidaoCKFpLudgeJAwtAZTJlaLIV2EQ?e=6N3RaD
Click to expand...
Click to collapse
Great! Let us know what bugs it has (if any) and especially for TWRP if it has the screen flicker!
gamr13 said:
Great! Let us know what bugs it has (if any) and especially for TWRP if it has the screen flicker!
Click to expand...
Click to collapse
I will tell you everything, I must first test it personally and after the upload on Mediafire.
In my opinion, I hope that the scienceillements of the TWRP will not be there
I have the files but I can not install it because it did not explain very well the steps ..
http://www.mediafire.com/file/eqzhwznxxr9qlsf/TWRP_3.3.1_UlefoneP5.img/file
http://www.mediafire.com/file/1sf9mi9qlcv5ari/no_encryption_mod.zip/file
He told me this and I do not understand much and it is not clear enough... : no encryption mod first before install latest twrp if your phone doesnt boot from old twrp to twrp 3.3.1
Heya,
This is a guide aimed on helping you to switch to a custom rom from the stock firmware.
For any questions, feel free to join our Telegram groups.
PREREQUISITES
1) Stock rom recommended by the maintainer of the rom that you want to flash. Typically for Q roms, 10.0.13.0, 10.0.18.0, 11.0.4.0 work well. (Link here).
2) The custom rom you want (Custom Rom list here).
3) Platform-Tools by Google for adb and fastboot (Link here).
4) TWRP Recovery Image and installer zip (Link here and here).
5) Force Encryption Disabler (Link here).
6) MiFlash by Xiaomi (Download the latest version from here).
7) An unlocked Bootloader
INTRODUCTION
Installing a custom ROM on an Android phone used to be a walk in the park. However, some newer phones, like Xiaomi Mi A2 Lite, have what's called an A/B partition layout. This facilitates an update process on stock ROMs, however it makes it harder to install and develop custom ROMs. You can read more about A/B partitions here.
The upshot is that Mi A2 Lite doesn't have a recovery partition. Instead, when you install TWRP, it gets installed to the boot partition. Which means that every time you install or update a ROM, you will need to re-flash the recovery ZIP. One more thing to keep in mind is that the ROM always gets installed to another slot. Meaning, if you're currently in the slot B, the ROM will be installed to slot A and vice versa.
INSTALLATION PROCESS
A) Installing Stock Rom as a Base
1) Extract the platform tools zip file and open the new extracted folder.
2) Open a command line / PowerShell window in that folder by holding the shift key and right clicking into the empty space of the folder. Press the "open PowerShell / Command line window here" option.
3) Plug the device into your PC with a Micro USB cable.
4) Hold down the power button and the volume down button for ~10-15 seconds. You should see the fastboot screen.
5) In the Command Line / PowerShell window type: "cmd" and hit Enter. Then, type "fastboot oem edl" and hit Enter again. If your device can't get detected (Stuck on "Waiting for any device") and nothing happens on your phone's screen, check the notes section of the guide below.
This will reboot your device into edl mode (Emergency Download Mode). The screen should turn off and the led indicator should be blinking indefinitely
5) Extract the MiFlash zip file and open the extracted folder
6) Launch the Mi Flash application by double clicking the XiaoMiFlash.exe file
7) Install the necessary drivers for MiFlash (Click ok in the dialogues).
8) Extract the downloaded stock rom.
9) Press the "select" button and point into the previously extracted folder. (There should be an images folder and some other sh and bat files in the same directory).
10) Click "Clean All" all in the bottom left.
11) Press "Refresh".
12) Your device should appear (COM port). (If not, check the notes section of the guide below)
13) Click "Flash". The process will take around 200-350 seconds.
14) After it is done, hold down the power button for ~10 seconds and verify that the stock rom boots.
DO NOT UPDATE OR MAKE ANY MODIFICATIONS IN THE BOOTED STOCK ROM IN ANY WAY.
B) Install the Custom Rom
(If you want to flash PixelExperience Official, continue with this guide by the PE team. If you face any issues, check the NOTES section of this guide)
1) Paste the downloaded custom rom (zip file) into your sd card and insert it into your phone.
2) Hold down the power button alongside with the volume down button. You should see the fastboot screen shortly.
3) Copy the TWRP IMG file to the platform-tools folder
4) Copy the TWRP Installer Zip file to your SD Card.
5) Open a cmd / PowerShell window in the platform-tools folder (like Step 2 of Section A)
6) Type: "fastboot boot twrp-3.4.0-3-unofficial-daisy.img".
7) You will see the recovery on your phone, prompting you to enter the password. Choose "Cancel"
8) Go into the main menu of TWRP. Press Wipe, then "Format Data". Type "yes" and press enter. (Keep in mind that all of your data will be wiped and there is no going-back).
9) Go back and press "Advanced Wipe". and select everything except "SD Card". Swipe to confirm the action.
10) Go into the main menu. Press "Install", "Select Storage" and select "Micro SD Card".
11) Flash the zips in this order (Click on them and swipe to confirm the action)
- Custom ROM
- TWRP Installer ZIP
- Force Encryption Disabler
DO NOT install Magisk, GApps or anything else yet, we will do that later!
(Some ROMs do not require Force Encryption Disabler as Force Encryption is disabled by default, although flashing that zip won't hurt anything)
After everything is done, DON'T TAP REBOOT YET. Instead, go back to the main menu, choose "Reboot", change the slot (e.g. if it says "Current Slot: A", tap "Slot B", vice versa.
12) Tap "Recovery" in the reboot menu.
13) Copy anything you would like to install on your phone (Magisk, Gapps, etc.) and flash it the usual way (optional)
(Some roms like EvolutionX and Pixel Experience have Gapps built-in so do not flash any gapps package in such roms.)
(Flashing Magisk isn't necessary but some roms may need it for CTS / SafetyNet to pass.)
14) Reboot to System and enjoy your Rom.
DIRTY FLASHING / MANUALLY INSTALLING A NEW BUILD
Manually Installing a new ROM build a.k.a Dirty Flashing is also somewhat complicated on A/B phones like Xiaomi Mi A2 Lite. However, if you follow these steps, you should be good to go:
1) Download the new build and copy it to your phone.
2) Reboot into the recovery mode (hold power + volume up) and flash the ROM ZIP.
3) Here's where the fun part begins: since we've just overwritten the boot partition, we don't have TWRP anymore, so we need to flash it again.
4) Once again, after you're done, don't tap on "Reboot" yet, instead, go back to the main menu, change the slot, and tap "Recovery".
5) Once the phone boots into recovery again, flash Magisk (optional) and Gapps if you had flashed them before.
6) Reboot the phone to system.
PSA: Dirty Flashing rom builds may cause unexpected problems and for this reason, it is recommended to perform a clean flash (Format Data) every time you want to flash a new build of your rom or switch to a different one.
SEAMLESS UPDATES
LOS Updater (which is used in Lineage OS and many other roms) downloads the ROM ZIP automatically and installs it to the inactive slot, which spares us the need to reboot into recovery. Thus, these updates look like OTA updates from the stock rom. However, there are a few gotchas here too:
After the OTA is installed, DON'T TAP ON "REBOOT". Instead, go to Magisk Manager and install a module called "TWRP A/B Retention Script" (you should be able to find it in the "Downloads" section)
Then, go to the Manager's main menu, tap on "Install" and choose "Install to inactive slot (After OTA)"
After the installation process is completed, you can reboot. You have to repeat the process every time you get an OTA if you want to keep Magisk and TWRP on your newly updated system.
- - - - NOTES - - - -
- Windows is the only supported operating system by this guide.
- If when you type a fastboot command (like fastboot oem edl) it just shows "Waiting for any device", it is probably due to missing drivers. See this page on how to install the Google USB driver that is required for fastboot to detect your phone.
- If you have an older version of Windows like 8, 8.1, 7 etc, your device might not get detected by MiFlash due to missing drivers. In this case, you will have to install the Qualcomm EDL driver on your own (Link here). Windows 10 finds and installs the driver automatically.
- If SafetyNet doesn't pass, ensure you have not modified anything in the system partition and that you have enabled Magisk Hide in Magisk Manager. If it still does not pass, try using the "MagiskHide Props Config" Magisk Module (More Info here). If it still doesn't work, try reinstalling your rom. If there are still issues regarding safetynet, it may be the rom's problem or google's new server-side changes might have affected your device (Learn more here)
- If some apps detect root and do not function properly (like banking apps), make sure SafetyNet passes. Also, you can try selecting the app in the MagiskHide section of Magisk Manager. The "Hide Magisk Manager" option in the Settings of Magisk Manager can be useful too.
- MIUI Roms / Ports have a special installation procedure (different from the one presented here) and thus, it is recommended that you take a look at their respective xda thread(s) and / or in the appropriate telegram group.
- If your download speed is slow when downloading the stock rom base, try using a download manager like IDM. If the speed is still slow, it is an issue with xiaomi's servers and there is nothing that can be done about it.
- 3.18 kernels such as butterfly, dragonheart etc, do NOT work and / or cause unexpected issues in updated custom roms because these roms use newer 4.9 kernels. The recommended custom 4.9 kernel is Sleepy and it can be found on Telegram (https://t.me/Laciakerneltg). Therefore, there will be no support offered if you are using a 3.18 kernel in a ROM that uses 4.9 kernels (all new UPDATED roms do)
- If your fingerprint doesn't work / partially works, flash this fix in twrp (This issue exists in the official version of pixel experience)
- Android 11 ROMs might require extra steps that are not mentioned here, please follow the respective maintainer's installation guide for now.
CREDITS
tkchn for some parts of the guide
@Offain for FED
@FDoop for some links and guides
Amazing ?
Detailed Guide
LinkBoi said:
Heya,
This is a guide aimed on helping you to switch to a custom rom from the stock firmware.
For any questions, feel free to join our Telegram groups.
PREREQUISITES
1) Stock rom recommended by the maintainer of the rom that you want to flash. Typically for Q roms, 10.0.13.0, 10.0.18.0, 11.0.4.0 work well. (Link here).
2) The custom rom you want (Custom Rom list here).
3) Platform-Tools by Google for adb and fastboot (Link here).
4) TWRP Recovery Image and installer zip (Link here and here).
5) Force Encryption Disabler (Link here).
6) MiFlash by Xiaomi (Download the latest version from here).
INTRODUCTION
Installing a custom ROM on an Android phone used to be a walk in the park. However, some newer phones, like Xiaomi Mi A2 Lite, have what's called an A/B partition layout. This facilitates an update process on stock ROMs, however it makes it harder to install and develop custom ROMs. You can read more about A/B partitions here.
The upshot is that Mi A2 Lite doesn't have a recovery partition. Instead, when you install TWRP, it gets installed to the boot partition. Which means that every time you install or update a ROM, you will need to re-flash the recovery ZIP. One more thing to keep in mind is that the ROM always gets installed to another slot. Meaning, if you're currently in the slot B, the ROM will be installed to slot A and vice versa.
INSTALLATION PROCESS
A) Installing Stock Rom as a Base
1) Extract the platform tools zip file and open the new extracted folder.
2) Open a command line / PowerShell window in that folder by holding the shift key and right clicking into the empty space of the folder. Press the "open PowerShell / Command line window here" option.
3) Plug the device into your PC with a Micro USB cable.
4) Hold down the power button and the volume down button for ~10-15 seconds. You should see the fastboot screen.
5) In the Command Line / PowerShell window type: "cmd" and hit Enter. Then, type "fastboot oem edl" and hit Enter again. If your device can't get detected (Stuck on "Waiting for any device") and nothing happens on your phone's screen, check the notes section of the guide below.
This will reboot your device into edl mode (Emergency Download Mode). The screen should turn off and the led indicator should be blinking indefinitely
5) Extract the MiFlash zip file and open the extracted folder
6) Launch the Mi Flash application by double clicking the XiaoMiFlash.exe file
7) Install the necessary drivers for MiFlash (Click ok in the dialogues).
8) Extract the downloaded stock rom.
9) Press the "select" button and point into the previously extracted folder. (There should be an images folder and some other sh and bat files in the same directory).
10) Click "Clean All" all in the bottom left.
11) Press "Refresh".
12) Your device should appear (COM port). (If not, check the notes section of the guide below)
13) Click "Flash". The process will take around 200-350 seconds.
14) After it is done, hold down the power button for ~10 seconds and verify that the stock rom boots.
DO NOT UPDATE OR MAKE ANY MODIFICATIONS IN THE BOOTED STOCK ROM IN ANY WAY.
B) Install the Custom Rom
1) Paste the downloaded custom rom (zip file) into your sd card and insert it into your phone.
2) Hold down the power button alongside with the volume down button. You should see the fastboot screen shortly.
3) Copy the TWRP IMG file to the platform-tools folder
4) Copy the TWRP Installer Zip file to your SD Card.
5) Open a cmd / PowerShell window in the platform-tools folder (like Step 2 of Section A)
6) Type: "fastboot boot twrp-daisy-3.3.1.0-offain.img".
7) You will see the recovery on your phone, prompting you to enter the password. Choose "Cancel"
8) Go into the main menu of TWRP. Press Wipe, then Advanced Wipe and select everything except "SD Card".
9) Go back and press "Format Data".
10) Go into the main menu. Press "Install", "Select Storage" and select "Micro SD Card".
11) Flash the zips in this order (Click on them and confirm the action) :
- Custom ROM
- TWRP Installer ZIP
- Force Encryption Disabler
DO NOT install Magisk, GApps or anything else yet, we will do that later!
PSA: Some ROMs do not require Force Encryption Disabler as Force Encryption is disabled by default.
After everything is done, DON'T TAP REBOOT YET. Instead, go back to the main menu, choose "Reboot", change the slot (e.g. if it says "Current Slot: A", tap "Slot B", vice versa.
12) Tap "Recovery" in the reboot menu.
13) Copy anything you would like to install on your phone (Magisk, Gapps, etc.) and flash it the usual way (optional)
PSA: Some roms like EvolutionX and Pixel Experience have Gapps built-in so do not flash any gapps package in such roms.
PSA2: Flashing Magisk isn't necessary but some roms may need it for CTS / SafetyNet to pass.
14) Reboot to System and enjoy your Rom.
DIRTY FLASHING / MANUALLY INSTALLING A NEW BUILD
Manually Installing a new ROM build a.k.a Dirty Flashing is also somewhat complicated on A/B phones like Xiaomi Mi A2 Lite. However, if you follow these steps, you should be good to go:
1) Download the new build and copy it to your phone.
2) Reboot into the recovery mode (hold power + volume up) and flash the ROM ZIP.
3) Here's where the fun part begins: since we've just overwritten the boot partition, we don't have TWRP anymore, so we need to flash it again.
4) Once again, after you're done, don't tap on "Reboot" yet, instead, go back to the main menu, change the slot, and tap "Recovery".
5) Once the phone boots into recovery again, flash Magisk (optional) and Gapps if you had flashed them before.
6) Reboot the phone to system.
PSA: Dirty Flashing rom builds may cause unexpected problems and for this reason, it is recommended to perform a clean flash (Format Data) every time you want to flash a new build of your rom or switch to a different one.
SEAMLESS UPDATES
LOS Updater (which is used in Lineage OS and many other roms) downloads the ROM ZIP automatically and installs it to the inactive slot, which spares us the need to reboot into recovery. Thus, these updates look like OTA updates from the stock rom. However, there are a few gotchas here too:
After the OTA is installed, DON'T TAP ON "REBOOT". Instead, go to Magisk Manager and install a module called "TWRP A/B Retention Script" (you should be able to find it in the "Downloads" section)
Then, go to the Manager's main menu, tap on "Install" and choose "Install to inactive slot (After OTA)"
After the installation process is completed, you can reboot. You have to repeat the process every time you get an OTA if you want to keep Magisk and TWRP on your newly updated system.
- - - - NOTES - - - -
- Windows is the only supported operating system by this guide.
- If when you type a fastboot command (like fastboot oem edl) it just shows "Waiting for any device", it is probably due to missing drivers. See this page on how to install the Google USB driver that is required for fastboot to detect your phone.
- If you have an older version of Windows like 8, 8.1, 7 etc, your device might not get detected by MiFlash due to missing drivers. In this case, you will have to install the Qualcomm EDL driver on your own (Link here). Windows 10 finds and installs the driver automatically.
- If SafetyNet doesn't pass, ensure you have not modified anything in the system partition and that you have enabled Magisk Hide in Magisk Manager. If it still does not pass, try using the "MagiskHide Props Config" Magisk Module (More Info here). If it still doesn't work, try reinstalling your rom. If there are still issues regarding safetynet, it may be the rom's problem or google's new server-side changes might have "hit" your device (Learn more here)
- If some apps detect root and do not function properly (like banking apps), make sure SafetyNet passes. Also, you can try selecting the app in the MagiskHide section of Magisk Manager. The "Hide Magisk Manager" option in the Settings of Magisk Manager can be useful too.
- MIUI Roms / Ports have a special installation procedure (different from the one presented here) and thus, it is recommended that you take a look at their respective xda thread(s) and / or in the appropriate telegram group.
- If your download speed is slow when downloading the stock rom base, try using a download manager like IDM. If the speed is still slow, it is an issue with xiaomi's servers and there is nothing that can be done about it.
- 3.18 kernels such as butterfly, dragonheart etc, do NOT work and / or cause unexpected issues in updated custom roms because these roms use newer 4.9 kernels. The recommended custom 4.9 kernels are: Sleepy (can be found in Telegram) and Loki (Link here). Therefore, there will be no support offered if you are using a 3.18 kernel in a rom that uses 4.9 kernels (all new UPDATED roms do)
CREDITS
tkchn for some parts of the guide
@offain for TWRP IMG and FED
@FDoop for some links and guides
@ScaryMen1325 for fixing MTP in @offain's twrp for 4.9 kernels
Everyone who builds Custom Roms
Click to expand...
Click to collapse
Hi LinkBoi,
Hope You're Doing Great.
Detailed Guide...
Really Appreciated For Your Hardwork.
Thanks,
MUHAMMAD Asif Qasim
Wow, so much information in one place. Thanks for spending your time on this.
Pat750 said:
Wow, so much information in one place. Thanks for spending your time on this.
Click to expand...
Click to collapse
Thanks for the positive feedback
Thanks for the great and detailed work..
I don't have windows, someone knows how can I do the steps that use the MI software? I just thinking on install Oreo again
mancarv said:
I don't have windows, someone knows how can I do the steps that use the MI software? I just thinking on install Oreo again
Click to expand...
Click to collapse
Not quite the same... But the stock rom .tgz can be flashed using fastboot. That's what I do, since my main system is a Mac.
I think EDL/miflash can fix some things fastboot can't (eg. partition table).
For "flash stock and erase data" it should be fine.
mancarv said:
I don't have windows, someone knows how can I do the steps that use the MI software? I just thinking on install Oreo again
Click to expand...
Click to collapse
Are you on mac or linux? For, mac, I know little about the process. Edl flashing is certainly not possible in mac os. Regarding linux, there is qdl if you wanna try it, but i do not recommend it. For fastboot flashing, you can try the .sh scripts in the stock rom's folder but no support will be given.
Guys thanks for your answers, sorry for being late I have been occupied. I'm on Linux, Ubuntu 18.04. I didn't remember that stock roms come with sh script. Has been a long time since I did this kind stuff and it was with a ZTE Open with Firefox OS :laugh: Maybe I'm gonna try downgrade, I'm testing the last stock version and it is working good so far .
Hi. Question about: "A) Installing Stock Rom as a Base". Can I skip this step if I'm already on a stock rom?
93starletgt said:
Hi. Question about: "A) Installing Stock Rom as a Base". Can I skip this step if I'm already on a stock rom?
Click to expand...
Click to collapse
Yes
93starletgt said:
Hi. Question about: "A) Installing Stock Rom as a Base". Can I skip this step if I'm already on a stock rom?
Click to expand...
Click to collapse
depends one which stock version you're on. The ones I have recommended have been tested and work well. Users have reported that latest stock q works well too. From my experience, anything over 10.0.13.0 is good but if you have weird bugs, try to flash any of the recommended stock roms first and see if those bugs persist.
TWRP Recovery Update
TWRP Recovery v3.4.0-0 - UNOFFICIAL
Updated: 4/9/2020
TWRP Bootable image
TWRP Installer ZIP
Changelog:
• Merged all TWRP 3.4.0-0 Changes
• Based on @TogoFire's OFRP device tree:
- Enabled System-as-Root
- Updated recovery.fstab
- Updated Rootdir & Blobs
- Added bootctrl from Stock Q
- Updated kernel, in the bootable image, to 4.9.233
- Fixed stability issues
- Fixed mounting issues
Note:
- The Tap-to-wake gesture was removed
- Decryption doesn't work (it never did)
Credits:
- @TogoFire for the device tree (Massive kudos to him for making a fully stable tree)
- @lslx_22S99176LF, @LmAo_device for testing
- @ScaryMen1325 for the MTP fix
LinkBoi said:
TWRP Recovery v3.4.0-0 - UNOFFICIAL
Updated: 4/9/2020
TWRP Bootable image
TWRP Installer ZIP
Changelog:
• Merged all TWRP 3.4.0-0 Changes
• Based on @TogoFire's OFRP device tree:
- Enabled System-as-Root
- Updated recovery.fstab
- Updated Rootdir & Blobs
- Added bootctrl from Stock Q
- Updated kernel, in the bootable image, to 4.9.233
- Fixed stability issues
- Fixed mounting issues
Note:
- The Tap-to-wake gesture was removed
- Decryption doesn't work (it never did)
Credits:
- @TogoFire for the device tree (Massive kudos to him for making a fully stable tree)
- @lslx_22S99176LF, @LmAo_device for testing
- @ScaryMen1325 for the MTP fix
Click to expand...
Click to collapse
Original post has been updated aswell
Twrp update 2
If you have the recovery loop issue (the device is always booting to recovery), go to advanced > fix recovery loop, confirm the action and it should be fixed )
Twrp update 2
TWRP Recovery v3.4.0-0 - UNOFFICIAL
Updated: 5/9/2020
TWRP Bootable image
TWRP Installer ZIP
Changelog:
• Based on @TogoFire's TWRP device tree:
- Updated kernel image in the bootable image to 4.9.234.
- Fixed USB, to be recognised better.
- Added the double-tap-to-wake (dt2w) gesture. (When the screen is off, you can press it twice to open it)
- Remove the reboot to EDL option as it didn't work
Note:
- Decryption doesn't work
- If you have any issues regarding double tap to wake, try to delete the .twrps file in the TWRP folder (can be found in the Internal Storage).
Credits:
- @TogoFire for the device tree (all of the work is his)
- @lslx_22S99176LF, @proxer05 for testing
Awesome guide, thanks a lot!
I have a question, if i want to install some patches and fixes throgth TWRP, is necessary to change the slot before reboot?
LinkBoi said:
TWRP Recovery v3.4.0-0 - UNOFFICIAL
Updated: 5/9/2020
Click to expand...
Click to collapse
Is this using some kind of Magisk based stuff to install or something because between this and the Force-enc disabler zip linked in this thread, something is causing my banking app to think my phone is rooted even though it isn't. I'd rather avoid having to install magisk purely for the sake of making my bank app work properly, so what's with this?
EDIT: well, I installed magisk anyway and got safetynet passing + magiskhide set up but the bank app still thinks im rooted so rip me i guess
EDIT 2: "Back in March of 2020, Google made some changes to SafetyNet that permanently trips when your bootloader is unlocked no matter what you do." welp,
Wher can I find "TWRP A/B Retention Script" in Magisk?
There is a new Design with no Download Selection.