This is a guide how I flashed Android 10 to my Cubot Power.
Preparation:
HINT:
Make a Backup! You will definitely loose all your data on the phone due to several factory resets!
First make sure your Device can use treble and also which one you need with this app:
https://play.google.com/store/apps/details?id=tk.hack5.treblecheck
(according to this post https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559)
note down:
Architecture: (Cubot Power: arm64)
System as Root: (Cubot Power: A-only)
then you will need fastboot and adb:
Windows:
https://forum.xda-developers.com/showthread.php?t=2588979
Linux:
Code:
sudo apt-get install android-tools-adb
Code:
sudo apt-get install android-tools-fastboot
Then you need twrp Recovery or something similar. Cubot Power is not supported by the official twrp project, but there is this unofficial version:
https://unofficialtwrp.com/twrp-3-2-3-recovery-cubot-power/
And you will probably need gapps:
https://opengapps.org/
For cubot power you will need "arm64" and "anrdoid 10" of course.
For the variant version I went with "nano" but you can probably choose what you like.
If you have a external sd card you want to copy the gapps, supersu and no-verty-opt-encrypt ZIP onto it.
Now download the android 10 treble image from:
https://github.com/phhusson/treble_experimentations/releases?after=v211
For the Cubot Power i went for the system-quack-arm64-aonly-vanilla.img.xz. But you should select the right one according to the treble app.
I went for vanilla because with gapps it did not seem to work.
Optional:
From this site:
https://romprovider.com/cubot-power-root-twrp/
Download SuperSu (https://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip)
and no-verty-op-encrypt (https://romprovider.com/download-no-verity-opt-encrypt-version/)
this prevents bootloops.
In case something goes wrong have your stock rom and sp flash tool ready:
Cubot Power: http://forum.cubot.net/viewtopic.php?f=21&t=2419
Flashing
Make sure your phone is charged probably. Booting might take up to an hour. At least 70% is recommended.
Go to developer settings and enable usb -debugging and disable oem.
now type:
Code:
adb reboot bootloader
the device should now restart and boot into fastboot
now disable oem in fastboot and unlock flashing: (WARNING: this will factory reset your phone)
Code:
fastboot oem unlock
Code:
fastboot flashing unlock
now we want to "install" twrp:
Code:
fastboot flash recovery TWRP_cubot_power-030918.img
--(Optional) check if twrp is working:
Code:
fastboot reboot
and restart with the volume up button
in twrp go to mount and check if you can mount data. If not: https://appuals . com/how-to-fix-twrp-unable-to-mount-storage-internal-storage-0mb/.
Make a Backup. Then wipe "dalvik cache", "cache" and "data"
Then go to install and install no-verty-op-encrypt.
then got to reboot and select bootloader.
--
continue with flashing android 10:
unzip the xz file
Code:
fastboot flash system system-quack-arm64-aonly-vanilla.img
this might take a while.
Then reboot
Code:
fastboot reboot
now your phone should boot into android 10. This can take very long for me it took about 30 minutes. If it takes longer then one hour you can probably start troubleshooting.
Install google apps(playstore)
once it has booted you either can start the login process and enable usb debugging again and reboot into recovery:
Code:
adb reboot recovery
or turn it off and restart into twrp (power button and volume up).
In twrp again check if you can mount data (see the optional step).
Make a Backup. Then wipe "dalvik cache", "cache" and "data"
Install super su and gapps.
Now reboot to system.
Now again the phone will boot a very long time (up to a hour).
Conclusion:
For me it is pretty stable but sometimes the fingerprint sensor does not work or the sim card is not recognized. But a reboot fixes it (sometimes).
But rebooting always takes time. At least 5 minutes sometimes up to 30 minutes. Once the system is booted there are no feel-able performance issues.
Hy there !
My Treble Info says:
Trable & VNDK supports old Version with VNDK version 27.0
System as Root:
Not supported, use A-only-OS
Will this flash to Android 10 work on this Cubot Power ?
The Phone is currently rooted.
regards
Al
Virtu-Al said:
Hy there !
My Treble Info says:
Trable & VNDK supports old Version with VNDK version 27.0
System as Root:
Not supported, use A-only-OS
Will this flash to Android 10 work on this Cubot Power ?
The Phone is currently rooted.
regards
Al
Click to expand...
Click to collapse
Probably it will work, but I can give you no guarantee for that.
Thank you!
Hi Johanno,
Thank you for this great tutorial! I think I already downloaded the treble check tool in March and I also found the github page, but I didn't find any experience on the net related to Cubot Power, so I didn't dare to upgrade.
Did you try later releases?
Should I go with latest release v222 or do you know about any change in v211 that prevents us from upgrading to a later version? ( your link in the tutorial shows only older versions: https://github.com/phhusson/treble_experimentations/releases?after=v211 )
Did you use windows or linux?
Did you experiment with V25 ROM?
https://www.cubot.net/platform/Support/detail/id/192/cid/23.html
Br,
taarzaan
I'm trying the latest release v222. I'm after the last reboot. It's not fast, but I would say it's less than 30 minutes. It should boot in 5 or 10 minutes.
Br,
taarzaan
Results of my experiments
Fingerprint sensor has similar issues like other Cubot devices:
https://github.com/phhusson/treble_experimentations/issues/1273
https://github.com/phhusson/treble_experimentations/issues/1319
I failed to install MS Outlook, Office, Company Intune app and things like that. I tried to unroot the phone, but it didn't help.
Maybe this Magisk thing worse a try next time:
https://github.com/phhusson/treble_experimentations/issues/31
https://github.com/phhusson/treble_experimentations/issues/909
Br,
taarzaan
Virtu-Al said:
Hy there !
My Treble Info says:
Trable & VNDK supports legacy Version with VNDK version 27.0
System as Root:
Not supported, use A-only-OS
regards
Al
Click to expand...
Click to collapse
hi
i just want to understand what is legacy version? and vndk27 ? i googled but few info
my phone say same info here
i ll post the results but if one could explain those 2 things
thank u in advance
taarzaan said:
Fingerprint sensor has similar issues like other Cubot devices:
https://github.com/phhusson/treble_experimentations/issues/1273
https://github.com/phhusson/treble_experimentations/issues/1319
I failed to install MS Outlook, Office, Company Intune app and things like that. I tried to unroot the phone, but it didn't help.
Maybe this Magisk thing worse a try next time:
https://github.com/phhusson/treble_experimentations/issues/31
https://github.com/phhusson/treble_experimentations/issues/909
Br,
taarzaan
Click to expand...
Click to collapse
notes for the next experiment (we should open a proper ticket for phhusson):
"What does "can't be used" mean? Does the pone vibrate? Does screen lights on? If you go in Fingerprint settings, do you see the enrolled fingerprint? Can you enroll a second one? If you press your fingerprint sensor when you're on that screen, what happens?"
I've tried with both v211 and v222 - but I don't seem to get past boot screen.
After using fastboot flash (and I've also tried SP flash tool flash) the phone shows cubot boot screen (with a warning about "orange mode" not being trusted) and can boot into TWRP but when booting system it shows a black screen with white slowly flashing "android" for a long time. More than one hour. I lose faith and re-install stock each time.
Any ideas how to debug and see what's happening?
Any improvements to this? I am having a P20/cubot and had same problems. AOSP v222 does not boot but I tried lineage-17.1-20201215-UNOFFICIAL-treble_arm64_avS.img.xz from https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/
Surprise. it works but a bit slowly. Due to large battery I am thinking of cubot power?
I have 2 questions:
1. Can you please try the lineage-17.1 rom?
2. BTW, did AOSP8 work OK in cubot power? (i like oreo more than android 10)
Thanks for your replies.
htorsten2020 said:
1. Can you please try the lineage-17.1 rom?
Click to expand...
Click to collapse
Thanks, sorry, I'll check it only next month. Any other issues besides slowness?
htorsten2020 said:
2. BTW, did AOSP8 work OK in cubot power?
Click to expand...
Click to collapse
I don't know what you mean. Do you mean treble roms? I haven't tried any yet.
taarzaan said:
Thanks, sorry, I'll check it only next month. Any other issues besides slowness?
Click to expand...
Click to collapse
Call/SMS/data stability. A lot of devices that came with oreo (vendor) have lots of issues with signal (mobile SIM) dropping after some hours. Thanks
taarzaan said:
I don't know what you mean. Do you mean treble roms? I haven't tried any yet.
Click to expand...
Click to collapse
Cubot Power ships with Android 8.1 (oreo). So I asked if you tried the old AOSP from phhusson (v32 - this is AOSP8 equivalent treble ROM). I found the AOSP from the same version (oreo as the device) is faster than installing newer ROM.
Hi guys, as you may have noticed I am not very active here ;-)
I actually went back to stock firmware after a few weeks because I couldn't get the phone working again. And since I want to use my smart phone and not tinker on it every few days I gave up. But now I am thinking about using Lineage os.
But first I need to back up everything and that's probably the thing that will hinder me the most.
Hi. I provide you my story with CUBOT power. It took me 2 days. I worked with a device that was never before modified. Guide on this page is very helpful. Johanno thank you very much!
By TWRP install an Orange mode has been triggered (you see small black text on the white screen with CUBOT POWER logo during boot. First I went step-by-step from this guide and I installed AOSP 11.0 v313. But it didnt want to boot because of boot loops. The no-verty-op-encrypt (last version) solved. I did not installed before because I did not want any root (I dont need). The boot time itself is really very long (I did not measure but guess 30 minutes) and after boot 3 buttons at bottom of screen (back/home/change task) were missing. As it was first run of fresh installed Android maybe restarting could help maybe not. I did not try because the boot time is really unacceptable...
Then I downloaded LineageOS 18.1 (lineage-18.1-20220120-UNOFFICIAL-treble_arm64_avS) and tried this one (before install I wiped cache, data, dalvik cache). After install phone started booting - there was some screen about encrypting partitions or so, then animation and there it frozen (I let it run full night without progress). At morning I turned phone off and on and it surpriesd me by just normal boot of working LineageOS 18.1.
Boot time is completely normal (lets say up to 3 minutes) each time I restart.
I tried fingerprint sensor - it works but maybe daily usage is not 100% reliable (Few times during phone unlock it completely ignored fingers). But honestly this sensor is not reliable (from past experiences)
Original LineageOS camera app cannot change some camera settings (I think ISO) because you see only very dark image. But after install F-droid and Simple camera app then it just works without issues.
Another issue i found was the night mode - you will find out that the "low temperature white" color is not stable - it flickers little bit. After some time it started bothering me. I completely solved it by activating developer mode and there I turned on some graphics hardware acceleration (I dont understand why is it turned off by default). Videos playback is working with this with no issues.
This lineageOS has 2 "Music" apps. I did not study the difference but one works and other one crashes.
I did not find any other issue. Gapps works (I installed nano), our local bank apps work (no issues cased by "Orange mode").
kezyr said:
Hi. I provide you my story with CUBOT power. It took me 2 days. I worked with a device that was never before modified. Guide on this page is very helpful. Johanno thank you very much!
By TWRP install an Orange mode has been triggered (you see small black text on the white screen with CUBOT POWER logo during boot. First I went step-by-step from this guide and I installed AOSP 11.0 v313. But it didnt want to boot because of boot loops. The no-verty-op-encrypt (last version) solved. I did not installed before because I did not want any root (I dont need). The boot time itself is really very long (I did not measure but guess 30 minutes) and after boot 3 buttons at bottom of screen (back/home/change task) were missing. As it was first run of fresh installed Android maybe restarting could help maybe not. I did not try because the boot time is really unacceptable...
Then I downloaded LineageOS 18.1 (lineage-18.1-20220120-UNOFFICIAL-treble_arm64_avS) and tried this one (before install I wiped cache, data, dalvik cache). After install phone started booting - there was some screen about encrypting partitions or so, then animation and there it frozen (I let it run full night without progress). At morning I turned phone off and on and it surpriesd me by just normal boot of working LineageOS 18.1.
Boot time is completely normal (lets say up to 3 minutes) each time I restart.
I tried fingerprint sensor - it works but maybe daily usage is not 100% reliable (Few times during phone unlock it completely ignored fingers). But honestly this sensor is not reliable (from past experiences)
Original LineageOS camera app cannot change some camera settings (I think ISO) because you see only very dark image. But after install F-droid and Simple camera app then it just works without issues.
Another issue i found was the night mode - you will find out that the "low temperature white" color is not stable - it flickers little bit. After some time it started bothering me. I completely solved it by activating developer mode and there I turned on some graphics hardware acceleration (I dont understand why is it turned off by default). Videos playback is working with this with no issues.
This lineageOS has 2 "Music" apps. I did not study the difference but one works and other one crashes.
I did not find any other issue. Gapps works (I installed nano), our local bank apps work (no issues cased by "Orange mode").
Click to expand...
Click to collapse
hi, how exactly did you install the lineageos 18.1 with the twrp 3.2.3? thank you in advance for your help
i just get boot loop on every rom i try on cubot power
I had the same problem and gave up
Related
Thread moved to https://forum.xda-developers.com/galaxy-s9/samsung-galaxy-s9--s9-cross-device-development/twrp-exynos-t3763464.
Changelog:
Note that this page only includes device-specific changes. For global TWRP changes, go to twrp.me.
Mar 16, 2018 (twrp-3.2.1-1):
Add system_image, vendor_image
Rename display name of /odm to "Carrier Configs"
Mar 15, 2018:
Initial version
Guides:
Be aware that Android Verified Boot requires data (including those in internal storage) to be cleared after you unlocked bootloader and flash custom binaries. ("to protect user data, all state transitions wipe the data partitions and ask the user for confirmation before data is deleted." - https://source.android.com/security/verifiedboot/verified-boot)
It is normal to get prompts like "Integrity verification failed. You have to reset the device to factory settings."
However, this will only happen when there is "state transition" so only when you switch from locked to unlocked or vice versa.
Part 1 - HOW-TO FLASH TWRP:
1. In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
2. Go to Settings -> Developer options and enable OEM Unlock option.
Notice: This is "state transition" mentioned eailier.
3. Download and Install Samsung Mobile Phones Drivers.
- Option 1: Download and Install Smart Switch for PC.
- Option 2: Download and Install standalone driver package.
4. Download and extract Odin (Samsung's Flash Tool) to your computer.
5. Download a .tar image of TWRP.
6. Reboot your device to download mode.
- Hold [VOLUME DOWN] + [BIXBY] + [POWER] for approx. 15 seconds.
- Read the warning carefully.
- If you agree, press [VOLUME UP] to get into Download mode. If you don't agree, STOP.
7. Open Odin and place that TWRP tar file in the [AP] slot.
8. Connect your phone.
9. Hold [VOLUME UP] + [BIXBY] + [POWER] on your phone and then press start on Odin.
10. Wait for the phone to reboot. DO NOT release [VOLUME UP] + [BIXBY] + [POWER] or you may not reboot into TWRP.
Part 2 - HOW-TO INITIALIZE TWRP: (for new phones)
1. If you completed Part 1 successfully, you should be in TWRP now. At this point, you will reach the screen asking you if you want to allow system modifications.
2. Select "Keep /system RO". (Don't swipe right or you may not be able to boot into system if you failed to complete next steps. However, you can swipe right to allow modifications if you are confident that you can complete next steps.)
3. Go to "Wipe" menu of TWRP and you will find "Format Data". Press "Format Data" and type "yes" to continue.
4. Go to "Reboot" menu and Press "Recovery" to reboot TWRP.
5. Download the special dm-verity and force encryption disabler zip on your computer.
6. Transfer the zip to your phone.
- Option 1: MTP: Connect your phone with computer and just copy the zip to internal storage. (similar to how you transfer files when in system.)
- Option 2: ADB: Connect your phone with computer and run command "adb push /path/to/zip /sdcard/".
- Option 3: External SD: Copy the zip to an external SD and then insert the card to your phone.
7. Go to "Install" menu of TWRP and flash the zip.
TWRP is initialized and fully functional at this stage.
jesec said:
Now you can either reboot into system or root, flash custom ROMs via TWRP.
Click to expand...
Click to collapse
In theory you can, but so far no one including myself has been able to root from this.
See this thread https://forum.xda-developers.com/galaxy-s9/development/twrp-samsung-s9-t3763548/
I wiped my data for nothing!
Wow that was fast twrp already.
Nice work Jesec and thank you:thumbup:
Now lets see how long till some dummy asks if it works on the snapdragon lol
sent from my Pixel 2 XL or Note FE
@jesec if this twrp is becoming the official one I suggest you to include some of my features/fixes as for example img flash to specific partitions, OTG fix and more (also people on the s9+ thread reported that usb wasn't working), check my device tree here.
Have a nice day!
Can we flash SuperSU/Magisk instead of the dm-verity disabler? To root as well as for disabling dm-verity at the same time?
Tkkg1994 said:
@jesec if this twrp is becoming the official one I suggest you to include some of my features/fixes as for example img flash to specific partitions, OTG fix and more (also people on the s9+ thread reported that usb wasn't working), check my device tree here.
Have a nice day!
Click to expand...
Click to collapse
Please follow the contribution and code review process of TWRP if you want to contribute.
I will review the changes.
After following the instructions exactly in the OP, I flashed SuperSU v2.82-SR5-20171001224502. My S9 is rooted and everything is working great!
Thanks
(NOTE to North Americans: Don't get your hopes up, although I am in Canada, I have the Exynos version SM-G960F)
flar2 said:
After following the instructions exactly in the OP, I flashed SuperSU v2.82-SR5-20171001224502. My S9 is rooted and everything is working great!
Thanks
(NOTE to North Americans: Don't get your hopes up, although I am in Canada, I have the Exynos version SM-G960F)
Click to expand...
Click to collapse
Will we see a kernel of yours ?
I mean after the news that AOSP GSI images are booting, one of the greatest kernel developer coming to S9 would be like the cherry on the top.
Paradoxxx said:
Will we see a kernel of yours ?
I mean after the news that AOSP GSI images are booting, one of the greatest kernel developer coming to S9 would be like the cherry on the top.
Click to expand...
Click to collapse
Maybe. I got this phone mostly for testing Button Mapper and High Brightness Mode. I couldn't resist trying to build a kernel this morning. It booted after a couple tries, but there was no wifi.
flar2 said:
Maybe. I got this phone mostly for testing Button Mapper and High Brightness Mode. I couldn't resist trying to build a kernel this morning. It booted after a couple tries, but there was no wifi.
Click to expand...
Click to collapse
Sounds like a good start to me
I'm sure Samsung people, and myself would love some kernel magic.
For both Samsung and AOSP flavors
https://www.xda-developers.com/samsung-galaxy-s9-aosp-android-oreo-project-treble/
flar2 said:
Maybe. I got this phone mostly for testing Button Mapper and High Brightness Mode. I couldn't resist trying to build a kernel this morning. It booted after a couple tries, but there was no wifi.
Click to expand...
Click to collapse
It is regarding an unpatched fimc , we had this issue on s8
Fennec_1 said:
It is regarding an unpatched fimc , we had this issue on s8
Click to expand...
Click to collapse
I'm guessing this involves editing a firmware binary?
(Sorry for OT, though it is development related)
flar2 said:
I'm guessing this involves editing a firmware binary?
(Sorry for OT, though it is development related)
Click to expand...
Click to collapse
Yup, im not sure about which fimc-<name>.bin needed to be patched on s9
Although this wont be a problem if you running gsi
Fennec_1 said:
It is regarding an unpatched fimc , we had this issue on s8
Click to expand...
Click to collapse
flar2 said:
I'm guessing this involves editing a firmware binary?
(Sorry for OT, though it is development related)
Click to expand...
Click to collapse
Fennec_1 said:
Yup, im not sure about which fimc-<name>.bin needed to be patched on s9
Although this wont be a problem if you running gsi
Click to expand...
Click to collapse
That was for camera issues, the wifi issue is secure storage related.
mwilky said:
That was for camera issues, the wifi issue is secure storage related.
Click to expand...
Click to collapse
Ah, thanks for correcting me
I've had a few issues with FRP randomly being triggered and not allowing TWRP to boot at all. Still not sure what causes it (might be because I changed my google account password) but I've successfully been able to reflash stock without losing the data partition, so you can re-root without losing anything. Had to remove the USERDATA image from the stock AP tar file to not wipe USERDATA tho.
flar2 said:
Maybe. I got this phone mostly for testing Button Mapper and High Brightness Mode. I couldn't resist trying to build a kernel this morning. It booted after a couple tries, but there was no wifi.
Click to expand...
Click to collapse
Change wifi paths in config
Hello everyone, after struggling for a few hours I managed to finally disable force encryption in my phone (so that TWRP could backup the data partition).
I'd like to write a quick list of what I did in the form of a guide to unlocking the bootloader, installing TWRP and getting root with Magisk. I'm just a user, not a developer and this guide is brief, it's not a detailed tutorial and does not include trivial steps (like how to install drivers for your OS).
Warnings: Although small, there is always the chance this bricks your phone. I take no responsibilities.
This will factory reset your phone so back up everything before you start.
My phone is Lenovo S5 (K520) Global version (see screenshot) I don't know if this will work for other firmwares.
Prerequisites:
Install Phone, ADB and Fastboot drives. You can get ADB and Fastboot binaries from here:
https://forum.xda-developers.com/showthread.php?t=2588979
Download this archive:
http://www.mediafire.com/?4dcvzw1hdmzfn10
It contains all the files used in this guide.
Alternatively, download all the files used from their sources.
You will need an SD card or a USB flash drive with an OTG adapter.
Copy the following files to it:
A. "Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip"
(Downloaded from http://forum.xda-developers.com/showthread.php?t=3817389 )
B. "Magisk-v18.0.zip"
(Downloaded from http://forum.xda-developers.com/showthread.php?t=3473445 )
C. (optional) "\stock\boot.img"
(Downloaded from the global firmware @ 4pda)
If you chose to use Micro SD card, you can insert it now.
Note: I know there is a way to push these files directly to TWRP from PC through USB instead of using SD Card/Flash drive but I've never tried it.
Lets start:
1. Go to 'Settings>About phone' and tap on "Lenovo version" several times until developer options are enabled.
2. Go to 'Settings>System>Developer options' and enable "OEM unlocking" (Note: for me this option was greyed out and I had to connect to wifi and wait for a minute or two).
Optional: Enable "USB debugging" if you wish to enter fastboot via ADB.
3. Turn off the phone and press and hold 'Volume down'+'Power' buttons until you see "fastboot mode" on the phone screen (alternatively, don't turn off the phone and instead enter fastboot mode via ADB (adb.exe reboot bootloader)).
4. Connect the phone to the PC via USB and open a command prompt in the location that you installed fastboot binary to.
Type (after each command press enter):
Code:
fastboot devices
To verify that the phone is recognized. And if it is type:
Code:
fastboot oem unlock
Now on the phone LCD navigate to "Yes" with volume buttons and press power to select it.
Your phone will factory reset, this will take a few minutes. Let it finish.
5. Put the TWRP image in your fastboot path. I used "recovery-twrp-3.2.3-crn-seoul(v3.2.3-1).img" downloaded from this URL:
https://forum.xda-developers.com/android/development/lenovo-s5-k520-twrps-t3863860
But I included 2 more files that I found (I did not try them).
6. Enter fasboot mode again and type:
Code:
fastboot flash recovery recovery-twrp-3.2.3-crn-seoul(v3.2.3-1).img
(Substitute "recovery-twrp-3.2.3-crn-seoul(v3.2.3-1).img" with the recovery filename of you choice)
7. If successful, disconnect the USB cable and enter Recovery mode, do not turn off or reboot the phone because upon restart the phone will revert to stock recovery (I.E. delete TWRP).
To enter Recovery mode press and hold 'Volume down'+'Power' buttons until you see "fastboot mode" and from there choose "Recovery mode" with the volume buttons and confirm with the power button.
(Alternatively, you can try holding 'Volume up'+'Power' to directly enter Recovery mode but I found it a little finicky)
8. In TWRP, swipe to allow changes. Press cancel when asked for a password to decrypt data.
If you chose to use a USB flash drive with an OTG adapter, connect it and mount it (Mount>usb-otg).
9. Go to Wipe>format data, type "yes" and confirm (if you have any data like installed apps, contacts etc., it will be deleted).
10. Go to Install and install "Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip".
The files will be in (/external_sd/ or /usb-otg/).
11. Install "Magisk-v18.0.zip"
Important note: If you want to keep encryption (if you don't care if TWRP can't access /data/) and just obtain root, skip steps 9 and 10.
12. Reboot to system and wait for a few minutes for the initial setup.
If for some reason boot fails (nothing happens after 10 minutes) and you can still enter TWRP (hold 'Volume up'+'Power'), then you can revert the changes by restoring the stock boot image (TWRP>Install>Install image>boot.img - put a checkmark on "boot").
If this worked for you, please tell us by replying to this thread.
Thanks a lot man. This phone is a beast in quality/price when talking about hardware. Costs a bit more than 100€ and has the same hard than others at 180-200€ at least. Bad thing is software but with TWRP and root everything is possible . Just found what project treble is, amazing possibilities. Can't beliebe nobody replied yet to yor post. Its a great guide and you show all the sources from where your downloads come. As you said in another thread its better this way so people can trust your content more:
C4lculated said:
I also wanted to root but I didn't want to run a bunch of unknown programs (from XN Logos), so I managed to install TWRP and root with magisk. I wrote a guide on how to do it:
https://forum.xda-developers.com/ge...ide-lenovo-s5-k520-twrp-root-decrypt-t3882402
Click to expand...
Click to collapse
I am yet waiting for my Lenovo S5 to arrive but I will give this guide a try. I was about to follow XN logos (stupdroid) guide/software but I prefer yours. Just one question... have you checked whether the TWRP v3.2.3 (latest) from dmilz make proper working backups? Can I trust that a full backup will be loaded correctly after installing any unofficial ROM, to go back to stock if necessary? I made once the mistake of relying a TWRP and later I found out that one was ok for flashing but didn't create working backups. I asked him also the same question, but I guess you also tried yourself to make a backup and restore from it using TWRP.
Next step will be to flash an Android 8.1 or 9 GSI rom (did I already say I'm amazed by GSI/project treble roms? just found about them last days). I will update you about my luck following your guide
does anyone enable lte bands, 4 and 28?
just bought this phone, currently on shipping..
I'll first try with twrp + aosp 9 GSI
Hi man, have you upgrade to gsi
acost91 said:
Thanks a lot man. This phone is a beast in quality/price when talking about hardware. Costs a bit more than 100€ and has the same hard than others at 180-200€ at least. Bad thing is software but with TWRP and root everything is possible . Just found what project treble is, amazing possibilities. Can't beliebe nobody replied yet to yor post. Its a great guide and you show all the sources from where your downloads come. As you said in another thread its better this way so people can trust your content more:
I am yet waiting for my Lenovo S5 to arrive but I will give this guide a try. I was about to follow XN logos (stupdroid) guide/software but I prefer yours. Just one question... have you checked whether the TWRP v3.2.3 (latest) from dmilz make proper working backups? Can I trust that a full backup will be loaded correctly after installing any unofficial ROM, to go back to stock if necessary? I made once the mistake of relying a TWRP and later I found out that one was ok for flashing but didn't create working backups. I asked him also the same question, but I guess you also tried yourself to make a backup and restore from it using TWRP.
Next step will be to flash an Android 8.1 or 9 GSI rom (did I already say I'm amazed by GSI/project treble roms? just found about them last days). I will update you about my luck following your guide
Click to expand...
Click to collapse
Kindly drop the procedure am hitting brick with all the method i used .????????
Stock firmware lenovo k520
I have tried your method on ROM that is based on China and also globally, and TWRP was successfully installed, and I have also tried several Rom GSI, and only AOSP Extended is successful, but with Bluetooth bugs it cannot be turned on, if others want flash files and stock firmware for k520, just let me know, thanks.
Working on S5 Pro too?
Hi! Can it work on S5 Pro too? I really want to root this device and I don't find out a way to get this happening. Thanks!
Does this work for s5 pro l58041?
Thanks
B4ph0 said:
I have tried your method on ROM that is based on China and also globally, and TWRP was successfully installed, and I have also tried several Rom GSI, and only AOSP Extended is successful, but with Bluetooth bugs it cannot be turned on, if others want flash files and stock firmware for k520, just let me know, thanks.
Click to expand...
Click to collapse
Hi! Sorry for offtopic!
Could you please PM me the link on AOSP extended image which you installed. Thank you!
Hello! Did somebody managed to install GCAM to Lenovo S5? I'm trying and I can;t do this, magisk modules are not loading...
so far I've used 2 alternative rom and works fine, aosp & octopus os, especially octopus os
I need some help..
Did anyone had lenovo s5 persist.img..
I lost my persist afer flashing global rom.208st via qfil..
I check the rom has no persist.img
Please visit to https://youtu.be/wbpV59kutJM for tutorial flash and upgrade Lenovo S5 in YouTube
hello guys, i always get into download mode,after press reboot system (twrp), any solution for my problem ?
has anyone achieved unlocking bands in this phone?
Please port miui 11 9.10.30 mi-room pie 9.0 redmi note 4x SD625 to lenovo S5.
https://megaroms.net/miui-11-9-10-30-stable-port-for-redmi-note-4-4x/
https://sourceforge.net/projects/miui-ports.whats-new.p/files/mido/miroom/
After unlocking bootloader, is there anyway to remove the hideous "software can't check for corruption" warning? Thanks.
---------- Post added at 01:44 AM ---------- Previous post was at 01:39 AM ----------
Suryo75 said:
hello guys, i always get into download mode,after press reboot system (twrp), any solution for my problem ?
Click to expand...
Click to collapse
This means no rom is installed in your phone. Either you accidentally wipe system in twrp, or the rom is corrupted.
Download the deodexed stock rom below and flash with twrp. Should fix your problem.
https://drive.google.com/open?id=13tRqo5eSpRiVJwKiA-iSj2GyIF353ATQ
jychung93 said:
After unlocking bootloader, is there anyway to remove the hideous "software can't check for corruption" warning? Thanks.
---------- Post added at 01:44 AM ---------- Previous post was at 01:39 AM ----------
This means no rom is installed in your phone. Either you accidentally wipe system in twrp, or the rom is corrupted.
Download the deodexed stock rom below and flash with twrp. Should fix your problem.
https://drive.google.com/open?id=13tRqo5eSpRiVJwKiA-iSj2GyIF353ATQ
Click to expand...
Click to collapse
thank you i'll try
Could you plz make tutorial about getting back to stock unroot...thx
Twrp gone
Hello sir thank you for this wonderful tutorial,
But I have a problem , after booting to TWRP , then boot to system after that when I try to go back to recovery mode TWRP , twrp is gone , stock recovery back
Hello Team,
Well, I wish that there was a special special section for the Honor 8X MAX, as there was so many things we can add to it, but well, let's post in this section
Most devices that came with Android 8.1 are likely to be Treble GSI compatible, so, the thng is that you just gotta find what Partition it uses.
For this device, it was kinda tricky as it was supposed to be A partition but I found out that it on EMUI 8 neither or AB worked, so after several tests, I found out that using any EMUI 9, we gotta use AB and not A, so I tried LOS 17.1 and worked like a charm but as TWRP is not the best for this device and I did not want to bother decrypt it, then root and install GAPPS, I preferred to install AOSP 10 from phhusson now and it works like a charm. The pros of this rom are that it is already "Rooted" and "Gapped", so I would highly recommend it :good:
Requirements::
* Unlocked Bootloader (Not explained here, so you need to use HCU Unlock and purchase a credit for that);
* Your Recovery has to be stock, so if you have TWRP, I recommend to reflash the stock one;
* Choose an ARM64 AB GSI Rom from here;
BUGS:
1. The device might show as not certified, so you won't be able to use any Google services until you register your device. Guide from Androidsage to help doing that;
2. Brightness seems to be at 50% when set at a maximum. This issue might be due to the Vendor Overlays (not a 100% sure though), I am investigating this, but I am using the device as it is and it is fine for me, until we find a solution for it.
Quick Guide:
1. Turn off your phone and then start it with Power and VOL+, until you see the message of the unlocked phone;
2. Wait until you see the Stock recovery not eRecovery;
3. Wipe and reset, Type "YES" and wait for wiping;
4. Plug the USB Cable to PC, reboot the phone while pressing VOL - ;
5. You should see the Android Fastboot now;
6. On Windows download ADB tools and Linux or Mac they can be added using terminal (You can find it easily by doing a simple search);
7. To make sure the phone is correctly connected, type in the CMD Line or Terminal: fastboot devices ;
8. You should see a series of numbers, so now you can flash by typing: fastboot flash system WHATEVERGSIIMAGEYOUCHOOSE.IMG ;
9. Wait about 2-3 minutes and then when the flash is finished, type: fastboot reboot ;
10. That's it! Your phone should now boot to your preferred GSI ROM with more or less everyhing working
riadtaihi said:
Hello Team,
Well, I wish that there was a special special section for the Honor 8X MAX, as there was so many things we can add to it, but well, let's post in this section
Most devices that came with Android 8.1 are likely to be Treble GSI compatible, so, the thng is that you just gotta find what Partition it uses.
For this device, it was kinda tricky as it was supposed to be A partition but I found out that it on EMUI 8 neither or AB worked, so after several tests, I found out that using any EMUI 9, we gotta use AB and not A, so I tried LOS 17.1 and worked like a charm but as TWRP is not the best for this device and I did not want to bother decrypt it, then root and install GAPPS, I preferred to install AOSP 10 from phhusson now and it works like a charm. The pros of this rom are that it is already "Rooted" and "Gapped", so I would highly recommend it :good:
Requirements::
* Unlocked Bootloader (Not explained here, so you need to use HCU Unlock and purchase a credit for that);
* Your Recovery has to be stock, so if you have TWRP, I recommend to reflash the stock one;
* Choose an ARM64 AB GSI Rom from here;
BUGS:
1. The device might show as not certified, so you won't be able to use any Google services until you register your device. Guide from Androidsage to help doing that;
2. Brightness seems to be at 50% when set at a maximum. This issue might be due to the Vendor Overlays (not a 100% sure though), I am investigating this, but I am using the device as it is and it is fine for me, until we find a solution for it.
Quick Guide:
1. Turn off your phone and then start it with Power and VOL+, until you see the message of the unlocked phone;
2. Wait until you see the Stock recovery not eRecovery;
3. Wipe and reset, Type "YES" and wait for wiping;
4. Plug the USB Cable to PC, reboot the phone while pressing VOL - ;
5. You should see the Android Fastboot now;
6. On Windows download ADB tools and Linux or Mac they can be added using terminal (You can find it easily by doing a simple search);
7. To make sure the phone is correctly connected, type in the CMD Line or Terminal: fastboot devices ;
8. You should see a series of numbers, so now you can flash by typing: fastboot flash system WHATEVERGSIIMAGEYOUCHOOSE.IMG ;
9. Wait about 2-3 minutes and then when the flash is finished, type: fastboot reboot ;
10. That's it! Your phone should now boot to your preferred GSI ROM with more or less everyhing working
Click to expand...
Click to collapse
Hi,
Great job, very detailed.
I've faced a situation when trying to flash many GSI img's (Lineage 18, Pixel Exp+, AOSP). The recovery (stock then TWRP) returned "image is too large for the partition". I've ARE-AL00C (4/128) with unlocked BL. Is there any workaround ?
hatemelectr said:
Hi,
Great job, very detailed.
I've faced a situation when trying to flash many GSI img's (Lineage 18, Pixel Exp+, AOSP). The recovery (stock then TWRP) returned "image is too large for the partition". I've ARE-AL00C (4/128) with unlocked BL. Is there any workaround ?
Click to expand...
Click to collapse
Some images simply do not work, so you will need to check for other images simply.
Just install this one : https://github.com/phhusson/treble_...nload/v222/system-quack-arm64-ab-gapps.img.xz
root&gapps&backlight working
of course you'll need Device+ID.apk and register ID with Google but that's easy and simple
Device: Huawei 8x Max AR00
The Quack version works but sadly it is Android 10. I have found many Android 12L GSI roms that I would like to use but the brightness is an issue on all of them. Anyone know how to copy the Quack backlight vendor display and patch it to the newer GSI roms? Tried buildprop GSI wont boot (Crdroid, Lineage 19) Tried Dirty flashing, obviously didn't work. Can't seem to find the file containing the slider brightness limitations. Phherson gives rom backlight options and tried several combinations, and yes rebooted everytime none of them work. Any ideas?
riadtaihi said:
Hello Team,
Well, I wish that there was a special special section for the Honor 8X MAX, as there was so many things we can add to it, but well, let's post in this section
Most devices that came with Android 8.1 are likely to be Treble GSI compatible, so, the thng is that you just gotta find what Partition it uses.
For this device, it was kinda tricky as it was supposed to be A partition but I found out that it on EMUI 8 neither or AB worked, so after several tests, I found out that using any EMUI 9, we gotta use AB and not A, so I tried LOS 17.1 and worked like a charm but as TWRP is not the best for this device and I did not want to bother decrypt it, then root and install GAPPS, I preferred to install AOSP 10 from phhusson now and it works like a charm. The pros of this rom are that it is already "Rooted" and "Gapped", so I would highly recommend it :good:
Requirements::
* Unlocked Bootloader (Not explained here, so you need to use HCU Unlock and purchase a credit for that);
* Your Recovery has to be stock, so if you have TWRP, I recommend to reflash the stock one;
* Choose an ARM64 AB GSI Rom from here;
BUGS:
1. The device might show as not certified, so you won't be able to use any Google services until you register your device. Guide from Androidsage to help doing that;
2. Brightness seems to be at 50% when set at a maximum. This issue might be due to the Vendor Overlays (not a 100% sure though), I am investigating this, but I am using the device as it is and it is fine for me, until we find a solution for it.
Quick Guide:
1. Turn off your phone and then start it with Power and VOL+, until you see the message of the unlocked phone;
2. Wait until you see the Stock recovery not eRecovery;
3. Wipe and reset, Type "YES" and wait for wiping;
4. Plug the USB Cable to PC, reboot the phone while pressing VOL - ;
5. You should see the Android Fastboot now;
6. On Windows download ADB tools and Linux or Mac they can be added using terminal (You can find it easily by doing a simple search);
7. To make sure the phone is correctly connected, type in the CMD Line or Terminal: fastboot devices ;
8. You should see a series of numbers, so now you can flash by typing: fastboot flash system WHATEVERGSIIMAGEYOUCHOOSE.IMG ;
9. Wait about 2-3 minutes and then when the flash is finished, type: fastboot reboot ;
10. That's it! Your phone should now boot to your preferred GSI ROM with more or less everyhing working
Click to expand...
Click to collapse
After trying many different gai variants and versions I found they all have an issue with browsers. Both chrome and edge freeze after scrolling a bit. I'm wondering if this because the GSI uses too much storage space and cannot buffer? Tried to port GSI onto other partitions such as cust, prod didn't work. Even Magisk flashes successfully but does not appear in the rom. The a and b is confusing like EMUI uses both and the TWRP does not decrypt and no Verity commands don't work either. The havoc rom seems to work the best with gapps pico flashed.
~ Android 12 backlight issues had to revert to android 10
~ All GSI have the common browsers freezing. Have to use VIA browser (basic)
~ Magisk won't install have to port to ramdisk, but isn't that the TWRP recovery?
Hello, which one is the Qualcomm driver to be installed for sdm660?
EDIT:SOLVED -- READ BELOW:
I finally got it flashed by following a few guides here which I will link, and try to break it down easier for someone else to come across and follow. I thought I bricked my phone (flashed LineageOS then rebooted, phone did not show anything on screen, full black screen) but after following a few guides I got it solved.
If you get bricked, or just want to follow a clean perfect install, please start below (Skip to step 2 if you are starting fresh, if you have soft-bricked your device start from step 1)
1. Bricked it and had to execute QDLoader 9008 fix again.
Tutorial is easier than it looks, do not fear, if you have soft-bricked your device and see a black screen, go ahead and go through the qdloader brick solution.
2. From factory recovery updated to Version WW-16.1220.1909.193.
If you have started fresh, I would highly recommend updating to the more updated firmware first. For me this worked, and I suggest updating to get a more current kernel, which may play better with Lineage OS install. To install a newer stock firmware linked above, download the ~2GB Firmware above, and save it to your Minimal ADB / Fastboot folder. Power off your device, after it has been successfully restored (if you bricked it) or you want to start off fresh and get the install right the first time. With your device powered off, Hold Volume UP and then Hold Power Button until the Fastboot menu appears. Use your volume keys to select Recovery, then press Power button to enter the STOCK Recovery (we are still on stock firmware with stock recovery). When in stock recovery select install from ADB. We are going to push the install via ADB (I tried dragging the firmware to the internal and selecting install ZIP and that didnt work).
Go into your Minimal ADB / Fastboot folder on your computer and open command prompt by holding Shift+Control and Right clicking and then selecting open command prompt here.
Now, enter the following command in the command prompt and hit enter:
adb devices
This command will show if any fastboot device is connected. If it doesn’t show, then please check the drivers are installed properly and try again.
If your device is listed, then type the command given below and press enter:
adb sideload File_name.zip
^^This will be the ~2GB Firmware file downloaded above
Wait until the installation process completes.
Once the installation process is complete, restart your device.
Done. You have successfully upgraded the Asus ZenFone 6 to the newer firmware, please continue.
3. Downloaded OTA 16.1220.1909.193 to 16.1220.1909.194, renamed it to UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user.zip and placed into root of internal memory.
When I disconnected USB cable (or rebooted, not sure), I was prompted with update notification. I have updated it. Either way, reboot your device if you don't see the notification, and look in your notifications to see something saying: System Update Detected Proceed with Update - and select it and update.
4. Now that your phone is 100% Updated with the newest firmware, let's follow another guide I found here:
I assume you're on a fresh Android 9 stock ROM, or just finished restoring your phone with the Flashall_AFT.cmd from this tutorial.
You should at least boot once on the system, and disable any PIN or password to unlock your phone (hence putting a default password for the FBE).
Download the latest OFFICIAL TWRP.x.x.img (which we'll use to boot on it), and it's installer to install it later (TWRP.x.x.zip) if you want to use it.
LineageOS installation steps :
Reboot to bootloader (=fastboot mode), connect to your PC and boot on TWRP :
Command:
fastboot boot TWRP.x.x.img
Once on TWRP, you can see that we're on slot A (Menu > Reboot). Now go to wipe > factory reset and then wipe system (technically I suspect this only wipes slot A, but do it anyway, don't worry about the errors!)
Now go to Install > flash the newest official LOS_latest.zip. What happens here is that the LOS installer will flash LOS on the inactive slot (slot B in our case). And will also install the LOS recovery (on both slots it seems).
Reboot to recovery : your phone automatically switches slots and will boot the LineageOS recovery (Don't fear, we don't need TWRP right now, just go along with this step) on slot B.
On the LineageOS recovery, do factory reset (which seems to be a full /data format in fact, thus removing any previous encryption AND all your data on internal storage). If you want to use Magisk, go to the recovery's install menu and sideload it now
Use code:
adb sideload Magisk-v20.3.zip
Now reboot to system. It might take a while (one or 2 loops in my case), but your phone should boot, or in some cases will end up on LOS recovery asking for a 'factory data reset' (then do it and reboot again).
Once booted on your LOS rom, you can define a pin or password to lock your phone (that'll be the FBE decryption password).
Now if you want to use TWRP, reboot to bootloader and boot again on TWRP.img (step 1)
From TWRP > Install > flash TWRP.x.x.zip (that is, the TWRP installer). It installs on both slots by default. If you had installed Magisk, you have to flash it again (because anything modifying the boot.img - like the TWRP installer in our case - will erase it).
You can now reboot to system and enjoy LOS
Thanks for the nice documentation. I've recently also struggling with installing a custom ROM and this clears some things up.
Wanted to ask, if you also have the audio issue that 1) callers hear an echo of themselves, and 2) the bottom speaker is active when receiving a call?
Thanks.
abprie said:
Thanks for the nice documentation. I've recently also struggling with installing a custom ROM and this clears some things up.
Wanted to ask, if you also have the audio issue that 1) callers hear an echo of themselves, and 2) the bottom speaker is active when receiving a call?
Thanks.
Click to expand...
Click to collapse
Haven't actually put my sim in yet to make calls, will let you know later today, sorry about the delay!
I had previously attempted this a number of months ago, and managed to soft brick my Zenfone 6 several times, eventually kind of giving up and just using the stock firmware.
I tried again back on Memorial Day in the US. This time around, I bricked it hard. Could not get device to power on in any fashion. PC would not "see" USB connection at all.
I returned it to ASUS for service, and they've charged me a little over $200 to repair it. The only problem they noted was, "Device is rooted/unlock". So I have no way of knowing if their diagnosis is based on actual inspection of the device, or if they're just replacing the SOC on the basis that I used their official bootloader unlock tool, thus registering my phone's S/N.
Just a little caveat emptor for anyone attempting to use this guide. I was able to get TWRP to load, and succesfully updated the stock firmware, but any and all attempts to load the Lineage image failed.
Eventually one of them soft bricked my phone as before, and I think my mistake was interrupting the soft brick rewrite procedure by prematurely unplugging my phone from the PC.
I had a similar issue: Bricked and totally unresponsive phone (or so I thought until I realised the screen was flashing very faintly when I switched off the lights - I could only tell in the dark due to how dim the flashing on the display was) where de "Powered by Android" logo kept flashing for a millisecond and in a loop. None of the button combinations worked so I couldn't switch completely off, access recovery/fastboot, and my computer wouldn't recognise the phone when I connected it via USB. I ended up buying an EDL cable for deep flashing Qualcomm phones (€9) and within minutes I was back up and running. All solved.
~SilverLad~ said:
I had a similar issue: Bricked and totally unresponsive phone (or so I thought until I realized the screen was flashing very faintly when I switched off the lights - I could only tell in the dark due to how dim the flashing on the display was) where de "Powered by Android" logo kept flashing for a millisecond and in a loop. None of the button combinations worked so I could switch completely off, access recovery/fastboot, and my computer wouldn't recognize the phone when I connected it via USB. I ended up buying an EDL cable for deep flashing Qualcomm phones (€9) and within minutes I was back up and running. All solved.
Click to expand...
Click to collapse
Can you post a link to where you purchased the cable?
abprie said:
Can you post a link to where you purchased the cable?
Click to expand...
Click to collapse
I bought it from Amazon. The one I bought is out of stock now, but there are a lot of them available (from other brands/sellers). This one for example - is the one that most resembles the one I actually bought: https://www.amazon.es/ASHATA-tel%C3%A9fono-reparaci%C3%B3n-Adaptador-Engineering/dp/B086WZMFKW/ref=sr_1_18?__mk_es_ES=%C3%85M%C3%85%C5%BD%C3%95%C3%91&dchild=1&keywords=cable+edl&qid=1597417614&sr=8-18
Since the thread is already on topic, could I flash lineage os while being on a custom rom? I have Bliss ROM on partition A and stock on B. Is it possible to have both Bliss and Lineage in dual boot?
Also, maybe a little off topic, the partition A/B scheme was intended to be used as a dual OS boot like normal PCs? Because right now I can select A and boot Bliss, select B and boot stock, I don't get why the procedure for flashing Lineage OS is so convoluted(requires having stock both on B and A?!) since both partition seems to be standalone and separated from each other.
~SilverLad~ said:
I bought it from Amazon. The one I bought is out of stock now, but there are a lot of them available (from other brands/sellers). This one for example - is the one that most resembles the one I actually bought: https://www.amazon.es/ASHATA-tel%C3%A9fono-reparaci%C3%B3n-Adaptador-Engineering/dp/B086WZMFKW/ref=sr_1_18?__mk_es_ES=%C3%85M%C3%85%C5%BD%C3%95%C3%91&dchild=1&keywords=cable+edl&qid=1597417614&sr=8-18
Click to expand...
Click to collapse
Hey there, what's the process around using this cable?
vikashhero said:
Hey there, what's the process around using this cable?
Click to expand...
Click to collapse
The cable itself (on its own), doesn't seem to "do" anything, but is paramount in reaching the right area, in order to fix the problem by means of the appropriate instructions and files. I can't recall where I ended up getting the right instructions from - as I researched quite a bit, and did a lot of "trial an error" before getting it right - so I'm sorry but I can't refer you directly to them via link (so that whoever posted them originally gets the credit they deserve), but this is what I ended up doing (on a WINDOWS machine) based on said instructions:
DOWNLOADS:
- Qualcomm drivers: https://androidfilehost.com/?fid=11410963190603857508
- Firmware with scripts: https://androidfilehost.com/?fid=1395089523397969054
- Latest official ASUS firmware from the ASUS webpage (download and place it in a memory card)
- (If you don't already have it on your WINDOWS machine): download and install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package
PROCEDURE:
1- Install the Qualcomm drivers
2- Unpack the downloaded firmware containing the scripts
3- Place the memory card in the phone's slot (with the latest official ASUS firmware already in it)
4- Power off the phone by VolumeDown + Power buttons (keep them pressed for about <25 seconds)
5- Connect the phone to the computer via the EDL cable and press the button on the EDL cable (there was an extra bit on what to do with a archive from the drivers file if your computer doesn't recognise the port straight away, but it wasn't necessary in my case so I didn't keep that step/archive name in my notes... I'm afraid you will have to search for it like I did if you come across that issue).
6- Start update_image_EDL.bat script from the unpacked firmware
7- After the script in step 6 finishes, start script flashall_AFT.cmd
8- Start bootloader
9- Go to stock recovery mode and install the ASUS firmware from the memory card
X- (Instructions also suggested to repeat steps 8 & 9 again at this point - for a second time - but in my case it wasn't needed)
I hope this helps.
~SilverLad~ said:
The cable itself (on its own), doesn't seem to "do" anything, but is paramount in reaching the right area, in order to fix the problem by means of the appropriate instructions and files. I can't recall where I ended up getting the right instructions from - as I researched quite a bit, and did a lot of "trial an error" before getting it right - so I'm sorry but I can't refer you directly to them via link (so that whoever posted them originally gets the credit they deserve), but this is what I ended up doing (on a WINDOWS machine) based on said instructions:
DOWNLOADS:
- Qualcomm drivers: https://androidfilehost.com/?fid=11410963190603857508
- Firmware with scripts: https://androidfilehost.com/?fid=1395089523397969054
- Latest official ASUS firmware from the ASUS webpage (download and place it in a memory card)
- (If you don't already have it on your WINDOWS machine): download and install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package
PROCEDURE:
1- Install the Qualcomm drivers
2- Unpack the downloaded firmware containing the scripts
3- Place the memory card in the phone's slot (with the latest official ASUS firmware already in it)
4- Power off the phone by VolumeDown + Power buttons (keep them pressed for about <25 seconds)
5- Connect the phone to the computer via the EDL cable and press the button on the EDL cable (there was an extra bit on what to do with a archive from the drivers file if your computer doesn't recognise the port straight away, but it wasn't necessary in my case so I didn't keep that step/archive name in my notes... I'm afraid you will have to search for it like I did if you come across that issue).
6- Start update_image_EDL.bat script from the unpacked firmware
7- After the script in step 6 finishes, start script flashall_AFT.cmd
8- Start bootloader
9- Go to stock recovery mode and install the ASUS firmware from the memory card
X- (Instructions also suggested to repeat steps 8 & 9 again at this point - for a second time - but in my case it wasn't needed)
I hope this helps.
Click to expand...
Click to collapse
Hey buddy, I appreciate your reply. The cable is on its way but I got a bit fiesty and opened up the phone to short the two contacts. This did the trick for me, got me back into EDL mode, and I was able to flash the latest firmware. On that topic, I'm trying to find the most suitable firmware version to run LineageOS 17 on the phone. I grabbed Mauro's TWRP to temporarily boot into which allowed me to flash the latest Asus image from their site. I guell I'll just carry on from there.
vikashhero said:
Hey buddy, I appreciate your reply. The cable is on its way but I got a bit fiesty and opened up the phone to short the two contacts. This did the trick for me, got me back into EDL mode, and I was able to flash the latest firmware. On that topic, I'm trying to find the most suitable firmware version to run LineageOS 17 on the phone. I grabbed Mauro's TWRP to temporarily boot into which allowed me to flash the latest Asus image from their site. I guell I'll just carry on from there.
Click to expand...
Click to collapse
As far as I understand, that's pretty much what the cable does actually... I also came across that method along my research, but I didn't want to risk opening the phone up. Since you are in the "flashing state": be careful with some of the instructions out there - I flashed through TWRP as I have been doing all these years with other phones, following specific instructions for each ROM I've tried, and I had nothing but issues until I flashed through ADB. I still don't know why I was getting the "No OS" warning all the time despite flashing correctly from TWRP (contemplating the A/B partitions matter), but none worked...
~SilverLad~ said:
As far as I understand, that's pretty much what the cable does actually... I also came across that method along my research, but I didn't want to risk opening the phone up. Since you are in the "flashing state": be careful with some of the instructions out there - I flashed through TWRP as I have been doing all these years with other phones, following specific instructions for each ROM I've tried, and I had nothing but issues until I flashed through ADB. I still don't know why I was getting the "No OS" warning all the time despite flashing correctly from TWRP (contemplating the A/B partitions matter), but none worked...
Click to expand...
Click to collapse
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
vikashhero said:
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
Click to expand...
Click to collapse
Happy to hear that Indeed be careful - this is a tricky phone...
vikashhero said:
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
Click to expand...
Click to collapse
Same here. It was so easy to do the Samsungs "back in the day", and you always had ODIN as a fallback if things went south. But this "A/B" partition nonsense (as well as other useless changes they introduce every time they "upgrade" Android, or certain structure modifications every so often when a new phone comes out) are a pain in the butt! Changes clearly aimed at making things more annoying/difficult for us people who don't want standard/corporate/unnecessarily bloated phones... Actually (as a former Blackberry user) I was tempted to get one of these Android based Blackberrys (the KEY2), but I didn't in the end precisely due to the fact that the bootloader can't be touched, and it can be rooted...
vikashhero said:
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
Click to expand...
Click to collapse
I want to switch to because the latest security update (August 2020) by Asus is soft bricking the phone for many users,
but I am seeing a few reports about some bugs (like the phone is stuck in the lineage boot symbol and cellular errors) in lineage os and also seeing few post with a lot of installation errors (like soft and total bricking) etc. and for me in developers options I'm not seeing the OEM and advanced boot options.(in my asus stock os) I just found out that I have to download the Unlock Boot loader apk separately from asus and install it using command prompt so I don't know how to proceed.
Can you please elaborate on how you actually did it with your Asus Zenfone 6(2019), I am a total noob in this and I also couldn't understand the partition a and b parts too.
Hey Guys,
Before you dive in, irrespective of your reading speed read this carefully and slowly for better understanding but if you cannot focus and read it slowly then you better give up music for a few weeks.
About the Device
Before you jump in and get your hands dirty.. you should know that what you will be installing is Generic System Image, It is not specifically made for your device so if you are going to install some other GSI other than this, you might face some issues.
If you are a beginner, you should Go Through Project Treble, just for the sake of knowledge.
Also Galaxy A51 has A/B partition and Supports Project Treble though remember that Treble Devices are not same as A/B devices and Vice Versa.
Things You’ll Need
A Computer (not an iPad)
Internet [requirement around 6 gigs (4.8 gigs optional, for downloading stock Firmware, Highly Recommended)]
Samsung Galaxy A51 (will not work on A50)
Patience and a madcap attitude.
Resources
Download Odin from the link given below and extract it in a folder.
https://odindownload.com/download/Odin3_v3.13.3.zip
Adb and Fastboot Drivers
https://gsmusbdrivers.com/download/adb-fastboot-drivers/#
Samsung Drivers
https://developer.samsung.com/mobile/file/68b2dc40-3833-4a8b-b58e-32f7aca25c00
Havoc OS GSI
Havoc-OS - Browse /arm64-ab at SourceForge.net
Don’t forget to check that there is “arm64” and “ab” written on the name of the file
Other option is with Gapps (it means the rom will come with Google Play services built in
otherwise it is Vanilla Android.
GSI Flasher
(It is used for converting your img file into flashable Zip)
https://drive.google.com/file/d/1J8OlI2CCXpvAJ5FhFlR2b_y58eHQERGs/view?usp=sharing
Extract it you’ll find three folders gsi, META-INF, scripts, keep all of them inside the GSI
Flasher extracted folder.
Twerp Recovery
twrp-a51-3.5.0_10-1_ianmacd.tar | by androidhowto for Utilities (androidfilehost.com)
Do not use any other in this case you might get mounting errors.
Encryption Disabler
Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip | by androidhowto for Utilities (androidfilehost.com)
Its Show time
1. Go to settings and go to about phone, tap build number 7 times and a dialog will appear, you are now a developer.
2. Go to additional setting or search developer options in the settings search bar
3. Once in the developer settings find OEM unlock and turn in on, scroll down and also turn on USB debugging, your phone will ask the permission for accessing the data by your computer.
4. Turn off your device. Get a usb cable and connect it to your computer.
5. While phone is off first press Volume UP and Volume Down together, and then then insert the usb cable into the phone while holding the buttons wait for two seconds. a blue screen will come up telling you about consequences and life choices.
6. Long press the Volume Up Button and a new blue screen will show up asking you for unlocking the bootloader. Press Volume Up to confirm. You device will erase everything and reset itself ( Don’t forget to take backup of your Data).
7. After the setup screen appears skip everything in the setup and enable developers option and enable USB debugging in the developer options.
8. Turn off your device again and Repeat step 5.
9. Press Volume up for entering the download mode
10. Now in your computer, Install Odin and open Odin.exe you’ll find your device as comm: xx
Now click on the AP button and select the twerp you downloaded.
Press start and twerp will be installed in your device. Your device will reboot don’t let it boot to one ui, press all three buttons together and hold, as soon as the screen goes black release only the volume down button. Keep holding the Volume UP and power buttons for 3 seconds and then release, you find yourself in twerp. If you miss it repeat the process again but don’t let it boot to One Ui.
In twerp press wipe => format data =>type yes. Press home button and again go to wipe advanced select Data, Cache and Dalvik and swipe to clear.
Press home again. Go to reboot and select recovery, twerp wil reboot. Once it reboots transfer the encryption disabler to your phone and in twerp press install select the storage, sdcard or internal storage, where you have stored the file, select it and swipe to install.
Now in your computer extract the Havoc os image and rename it as “system.img”.
Extract the GSI flasher, copy system.img and paste it in the gsi folder of the GSI Flasher.
Select gsi, Meta-inf, scripts and compress them into a zip and transfer into the phone.
Now in twerp Press install, select the zip file and swipe to install. Also install Gapps or Magisk if you want (though normal magisk will have problem try install phh_magisk, discussed later).
Reboot and KABLAMO You have installed Havoc OS.
Bugs
A small random issue in Auto Brightness
If you root with magisk and install modules, after you reboot your phone will get into a bootloop. Use Phh_Magisk but I aint sure if it’ll work or not Your call madcap.
NONE OF THE FILES IN THIS TUTORIAL HAVE ANYTHING TO DO WITH ME. If SOMETIHING HAPPENS I AM NOT RESPONSIBLE. ONLY DO IT AT YOUR OWN RISK.
Troubleshooting.
If you find errors in twerp, such as unable to mount vendor or system_root, or data. Then you got to install the stock One Ui Back again, therefore it is highly recommended to keep with yourself the stock firmware. You will need It. And it is 4.78 gigs. You can download it from
Model : SM-A515F - Galaxy A51 — Samfrew.com
To reinstall the stock firmware first extract it and the open odin and repeat steps 8 and 9, once your device is detected in Odin press the respective buttons and select the respective files such as for BL button select the file With BL in the name. Do it for buttons, BL, AP(once you select the file it will take long for it load into odin so do not panic and let it load, it might become unresponsive but use patience and wait.)CP , CSC. Click on start and you’ll have ONE Ui back on your device.
To Lock the bootloader repeat steps 5 and 6.
If you still want more stability and Control You can install a different Kernel NDataX from (@Hendamanu) https://forum.xda-developers.com/m/hendramanu.11224917/
I'd like you to please correct the title and write GSI instead of custom rom as both are different things and the title can be considered misleading.
Yillié said:
I'd like you to please correct the title and write GSI instead of custom rom as both are different things and the title can be considered misleading.
Click to expand...
Click to collapse
Oh, my bad.. changed it.
GrandmaGotGuns said:
Oh, my bad.. changed it.
Click to expand...
Click to collapse
Thanks a lot
Is stable? Does the fingerprint on the screen work?
LichtEstarossx said:
Is stable? Does the fingerprint on the screen work?
Click to expand...
Click to collapse
Its Stable and yes fingerprint works as well. Battery life is also good almost 9 hours of screen on time for my device.
GrandmaGotGuns said:
Its Stable and yes fingerprint works as well. Battery life is also good almost 9 hours of screen on time for my device.
Click to expand...
Click to collapse
I will try to test it although another question arose, the encryption works in the twrp or is it to disable the dm verity?
LichtEstarossx said:
I will try to test it although another question arose, the encryption works in the twrp or is it to disable the dm verity?
Click to expand...
Click to collapse
You need to flash disable dm verity before flashing the gsi.. one ui encrypts the data.
I'll soon update this for Android 11 (R)
I did all the steps correctly (started oneui before), but now it won't start the system, is there any way to fix it?
LichtEstarossx said:
I did all the steps correctly (started oneui before), but now it won't start the system, is there any way to fix it?
Click to expand...
Click to collapse
What android version are you at?
GrandmaGotGuns said:
What android version are you at?
Click to expand...
Click to collapse
I had android 10
one ui 2.5
although it is rare that the gsi does not work
LichtEstarossx said:
I had android 10
one ui 2.5
although it is rare that the gsi does not work
Click to expand...
Click to collapse
If you are using the same gsi mentioned above then it should work. Not all GSIs will run on your device. Did you successfully install twerp?
GrandmaGotGuns said:
If you are using the same gsi mentioned above then it should work. Not all GSIs will run on your device. Did you successfully install twerp?
Click to expand...
Click to collapse
use havoc 3.8 vanilla arm64 ab
and I tried phh aosp but it didn't work
LichtEstarossx said:
use havoc 3.8 vanilla arm64 ab
and I tried phh aosp but it didn't work
Click to expand...
Click to collapse
Model : SM-A515F - Galaxy A51 — Samfrew.com
Model : SM-A515F | Samsung Firmware Database
samfrew.com
Upgrade to android 11, first install one ui 3 from the site above. I'll update it for Android 11 [R].
GrandmaGotGuns said:
Model : SM-A515F - Galaxy A51 — Samfrew.com
Model : SM-A515F | Samsung Firmware Database
samfrew.com
Upgrade to android 11, first install one ui 3 from the site above. I'll update it for Android 11 [R].
Click to expand...
Click to collapse
for now reinstall oneui 2.5, I will try to compile orangefox for android 10, and about the brightness bug in the gsi I know how to correct it, if there is any way to contact you to talk about it, say so
LichtEstarossx said:
for now reinstall oneui 2.5, I will try to compile orangefox for android 10, and about the brightness bug in the gsi I know how to correct it, if there is any way to contact you to talk about it, say so
Click to expand...
Click to collapse
If you are talking about gsi fix then im not sure that it'll work. I tried patching other gsi's for specifically efor xynos but the success rate is 50%. Sure let's talk here
GrandmaGotGuns said:
If you are talking about gsi fix then im not sure that it'll work. I tried patching other gsi's for specifically efor xynos but the success rate is 50%. Sure let's talk here
Click to expand...
Click to collapse
What I say is not a patch, it is one of the phh oberlays for aosp gsi, after I have time I will try to make one, but that overlay would only be for the a51, not for another Samsung
If it is about gsi I am relatively knowledgeable about that, although as far as I know it was not necessary to use this zip to enter gsi, I think the super partition must be modified to install gsi
LichtEstarossx said:
What I say is not a patch, it is one of the phh oberlays for aosp gsi, after I have time I will try to make one, but that overlay would only be for the a51, not for another Samsung
If it is about gsi I am relatively knowledgeable about that, although as far as I know it was not necessary to use this zip to enter gsi, I think the super partition must be modified to install gsi
Click to expand...
Click to collapse
I attach my telegram username in case you need something more specific.
(nicopizza) Add the @
Can someone plz assist........I got the rom installed on issues
Root chkr says I'm rooted but substratum says I'm not Magisk I don't think I have the patch img. for it..... plz can someone hlp