Related
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
[ZE620KL/Android 9][TREBLE] COMPLETE GUIDE: Unlocking, Rooting & Flash GSI + Fixes
Unlocking bootloader to Flashing GSI (Asus Zenfone 5 [ZE620KL] / Android 9.0)
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.
*/
About :
The last guide could leads to soft brick, as the instructions were not clear nor the files not supported for Android 9.0.
Here is a complete guide with TWRP 3.3.0 for Android 9.0, clear instructions and multiple fixes for GSI.
It has been tested on stock version v16.0615.1903.92.
Requirements :
- A stock version V16.0610.XXXX.XX or higher
- A phone on Android 9.0 (not 8.0!)
- A fully working USB cable
- Latest ADB / Fastboot drivers
- Bootloader unlocker (download latest from Asus website or from here)
- TWRP 3.3.0 image
- Android9EncryptionDisablerZE620KL.zip
- Magisk v19.3
Instructions :
Unlocking Bootloader
1. Backup all your important data.
2. Install the bootloader unlocker APK, and follow the steps. You will loss your warranty here, and it will factory reset your data
3. If there is any issue here, go into your stock recovery (volume down + power button) and factory reset.
Installing TWRP
4. Shutdown your device & boot in fastboot mode using volume up + power button.
5. Check that the connection between your device and your computer by typing this in your command line :
Code:
fastboot devices
6. Flash TWRP recovery using :
Code:
fastboot flash recovery <twrp_name>.img
7. Now reboot in recovery mode using :
Code:
fastboot oem reboot-recovery
8. In TWRP, select Wipe > Format Data > enter "yes" and confirm
9. Return to the main menu, select Reboot > Recovery
10. Do 8. & 9. and again
11. Using TWRP or ADB, install Android9EncryptionDisablerZE620KL.zip (on TWRP, go into Install > find Android9EncryptionDisablerZE620KL.zip > Install zip)
If everything has gone successfully, you now have a custom recovery.
As for some GSIs, a patched boot partition may cause bootloop, you should try installing Magisk after installing the GSI. If you want to keep your stock ROM, go directly to "Magisk Installation" section.Installing a GSI
This step may vary depending on the different GSIs distribution. I assume you install Havoc OS v2.7 GSI which actually works on this device.
1. Backup all your important data using TWRP backup.
2. Select the arm64-aonly GSI image you want, and move it on your external SD.
3. Wipe Data, Dalvik, and Cache.
4. Go back in the main menu of TWRP, and reboot to recovery.
5. Remove Magisk if it was previously installed, by using its uninstaller script.
6. Flash the GSI to system partition.
7. Boot and perform a factory reset.
Installing Magisk
1. Add the Magisk zip archive to your external storage.
2. Boot into TWRP recovery, and install the zip.
3. Enjoy!
Bug fixes:
Insufficient storage in the system partition to flash GApps : Download your OpenGApps archive on your external SD, and use MagicGApps 2018.9.23 to install GApps.
Auto-Brightness doesn't work: Download framework-res__auto_generated_rro.apk from here.
Using a root explorer or command-line, push the APK to /vendor/overlay.
Then run the following command in a rooted terminal or ADB shell:
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/framework-res__auto_generated_rro.apk
My camera doesn't work well (green tint on face camera) and/or the app doesn't boot: If Asus Camera doesn't launch on your GSI, you should probably edit your /system/build.prob file.
You need to edit ro.product.model, ro.product.brand, ro.product.name, ro.product.device, ro.product.manufacturer & ro.build.product properties to be:
Code:
ro.product.model=ASUS_X00QD
ro.product.brand=asus
ro.product.name=WW_Phone
ro.product.device=ASUS_X00QD
ro.product.manufacturer=asus
ro.build.product=ZE620KL
You can instead use Google Camera mod (port from Arnova8G2 & modded by 5Z community, thanks to them!), which works well (edit: there is a bug on HavocOS, we can't access settings).Bonus:
- You can reinstall DTS Headphone:X here.
- For booting your kernel in Permissive mode, check here
Sources:
TWRP 3.3.0 : On GitHub
If you need help or if you want to help on ZE620KL development go here:
https://t.me/Zenfone5Dev
(We will continue to update & help here though.)
Many thanks to all of the Zenfone 5 community (particularly Emincan, Pandolfi and Lmajkej),
Phhusson & Erfan for their works on GSI, and Shakalaca for its work on TWRP 3.3.0!
On HavocOS v2.8 GSI (13-08-2019):
It works:
- Almost anything
- Adaptive Brightness (after manual fix)
- Notch overlay
- DTS Headphone X (after manual installation)
- NFC
- Face unlock
- Stock camera (after manual fix)
- Magisk
- SDcard access
It doesn't works:
- VoLTE / VoWifi
- Google Camera settings
- External speaker amplifier (NXP amp)
- APT-X / APT-X HD bluetooth
- Low microphone in normal use
- No microphone in calls (only headphone microphone works)
GCam settings
But my google camera keep crashing when I want to go into camera settings
Hi thanks for this tutorial, this is my first time rooting my phone. I'm encountering a problem with my sd card after installing havoc os, everytime i try to move, save or any write functionality i do to my sd card, it always says the android version isn't compatible. I could still see my files from my sd, but everytime it asks permission it always say this
bentley0928 said:
But my google camera keep crashing when I want to go into camera settings
Click to expand...
Click to collapse
Same issue here. I will update the thread when I will find a more working GCam port (perhaps, this GCam port works well on ZenUI)
Jolo110 said:
Hi thanks for this tutorial, this is my first time rooting my phone. I'm encountering a problem with my sd card after installing havoc os, everytime i try to move, save or any write functionality i do to my sd card, it always says the android version isn't compatible. I could still see my files from my sd, but every time it asks permission it always say this
Click to expand...
Click to collapse
It's a known issue, the GSI maintainer @vince31fr is working on it. I don't have it, but I can advice you to use Solid File Manager, which works like a charm on my device.
"- No microphone in calls (only headphone microphone works)"
Funny... I'm on stock latest firmware and I have this issue, so I thought I try something new, and this has that issue. It can't be a coincidence. Something is ****ed up with this device.
Wonder if this will work for the Zenfone 5 Lite (or 5Q)? I wanna root my 5Q so bad haha
Thanks for the great instructions! Steps 1 through 11 worked perfectly for me, then I installed LineageOS (lineage-17.0-20191231-UNOFFICIAL-treble_arm64_avN.img) and it works properly. Then when I go back to TWRP and install Magisk v20.1 it reboots into an endless Lineage bootup logo animation (not boot loop). I can get an adb shell, but now also the external SD card has become invisible. Any suggestions?
UPDATE: I switched over to the patched Magisk version from PHH (https://forum.xda-developers.com/zenfone-5/general/ze620kl-add-support-to-evey-android-9-t3966918) and everything works perfectly now!
Hi!! I thanks for these instructions you gave. I know this post is a bit older. But is the only one I think could help me.
I got an ZE620KL and I'm trying to root this device. I have some experience in unlocking bootloader and rooting devices. But this one... Is giving me a lot of work. Researching in a lot of forums and websites I tried a lot of things with no success. In theory, is just install the official apk provided by ASUS and run the application. But the app doesn't work for a long time as I researched (error accusing network problem). I tried unlock via fastboot commands but I always got stucked by "remote: permission denied" even with latest drivers and ADB Fastboot installed. And yes... I let my device with no one security feature enabled and didn't worked. I tried everything even after wiped data / cache and factory reset and no progress.
In my researches, I realized something about 'oem unlock'. It appears to be the key to solve this. And I guess the tool to work with this is the damn unlock tool from ASUS which don't work! Also, I've heard about workaround with Magisk by flashing a custom recovery to achieve the root. Magisk no longer supports zip files to flash. Only '.img' and '.tar' files. I'd like to find some light here... I don't know what to do. I appreciate any help!
Hello do I need to flash Android9EncryptionDisablerZE620KL.zip if Im gonna flash a non-GSI custom ROM? Or its only for GSI Treble ROM?
[email protected] said:
Hi!! I thanks for these instructions you gave. I know this post is a bit older. But is the only one I think could help me.
I got an ZE620KL and I'm trying to root this device. I have some experience in unlocking bootloader and rooting devices. But this one... Is giving me a lot of work. Researching in a lot of forums and websites I tried a lot of things with no success. In theory, is just install the official apk provided by ASUS and run the application. But the app doesn't work for a long time as I researched (error accusing network problem). I tried unlock via fastboot commands but I always got stucked by "remote: permission denied" even with latest drivers and ADB Fastboot installed. And yes... I let my device with no one security feature enabled and didn't worked. I tried everything even after wiped data / cache and factory reset and no progress.
In my researches, I realized something about 'oem unlock'. It appears to be the key to solve this. And I guess the tool to work with this is the damn unlock tool from ASUS which don't work! Also, I've heard about workaround with Magisk by flashing a custom recovery to achieve the root. Magisk no longer supports zip files to flash. Only '.img' and '.tar' files. I'd like to find some light here... I don't know what to do. I appreciate any help!
Click to expand...
Click to collapse
Im not sure if you still have your phone or you have successfully unlocked bl. but I found an updated version of their tool which works.
*tried unlocking from android 10 not working, it says device model not supported*
Zenfone 5 Unlock BL
cf100clunk said:
Thanks for the great instructions! Steps 1 through 11 worked perfectly for me, then I installed LineageOS (lineage-17.0-20191231-UNOFFICIAL-treble_arm64_avN.img) and it works properly. Then when I go back to TWRP and install Magisk v20.1 it reboots into an endless Lineage bootup logo animation (not boot loop). I can get an adb shell, but now also the external SD card has become invisible. Any suggestions?
UPDATE: I switched over to the patched Magisk version from PHH (https://forum.xda-developers.com/zenfone-5/general/ze620kl-add-support-to-evey-android-9-t3966918) and everything works perfectly now!
Click to expand...
Click to collapse
Do you still have the patched Magisk zip file, the original link in the post seems not working
Realme 5 Pro global ROM for Realme Q
Code:
* We are 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 us for messing up your device, we will laugh at you.
{Mod edit}
If you know exactly what you're doing then jump go step 5)
1) Introduction:
Oh sheet. Here we go again. Hope you guys will make use of this little guide for at least 20 RMQ users PMed me here on xda, on Messenger and on Telegram to help them install RM5P ROM on their RMQ device and had to dump them for I had no idea. Now that I have tried it myself I'll try to do. I've an RMQ device 4+64GB variant which I ordered from AliExpress for 161$/148€ ( in September of 2019 ) and tried loads of tweakings on stock ROM to make it more fitting to a person like me for daily usage but I don't think I have to say... without much success. In this guide I'll try to show/tell you how to make with COS without weeks of testing and debugging I've been through on stock RMQ ROM since October of 2019.
2) Personal reasoning:
I heard there are people who like Color OS as it is existed but still I wouldn't want to believe you even after I talked with some of you. Since the very first day I held my device in my hands I started seriously despising Color OS for I've been a purist, minimalist and stock Android fan for 10 years now and always tried to stick to "clean" ROMs such as LOS, PE, Aosp Extended, AOSIP because of reasons. This is mainly because (Chinese) Android skins modify system/vendor so heavily that they prohibit or interfere (with) basic Android functions that work well on stock-like ROMs. {Mod edit}
3) Features:
Mostly same as on RMQ ROM but...
More languages are supported by the system.
Most of Oppo's restrictions are removed {Mod edit}
3.5) Known bugs:
None. You tell me!
4) Basic terms:
RMQ: Realme Q
RM5P: Realme 5 Pro
RMX1971CN: Realme Q device codename.
RMX1971EX: Realme 5 Pro device codename. Both are used to distinguish China and Global/India ROMs.
COS: Color OS
ROM: Read Only Memory (means for us the OS we use to flash with TWRP/Fastboot)
OS: Operating System
TWRP: TeamWin Recovery Project (the one recovery we use widespread to flash custom ROMs and fixes on our mobile device)
FASTBOOT: A mode of your device and a script on PC that you can use to flash stuff via USB cable onto your device. This is necessary if you are on stock recovery.
FLASHING: The process of writing onto our mobile device's ROM that wouldn't necessarily be possible without using external tools if TWRP wasn't there for us. Mobile device companies don't really support or encourage users to do this.
BOOTLOADER: Default state is locked on our and on most devices. Without unlocking it, it would be extremely hard if not impossible for us to flash custom ROMs on our mobile phones. You can unlock your bootloader by following this guide if you haven't already done that because without unlocking it, flashing global ROM on your device which comes with Chinese one preinstalled will likely be impossible at least not known to the RM5P/RMQ community so far.
MAGISK: Systemless solution which grants root access (admin-like) to the user without really tampering the ROM system, this way granting higher stability than it's predecessors.
5) Precautions:
If you aren't an advanced user and don't really know what you're doing follow the steps closely and it's highly advised to read the basic expressions to understand better what's happening just in case something goes wrong so you can fix it.
External SD card is highly recommended to use because to make this work formatting data is quite likely needed.
If you want to bring your data with you from your current ROM make sure to do either Titanium or Migrate backup and save it to your external SD card.
TWRP for RMQ (this one I highly recommend to use for it has a wide range of features and options that come in handy, unlike normal TWRP)
Magisk if you want root or/and want to pass Google's Safetynet completely.
Magisk COS beta FIX from here (step 6)
Modified vbmeta.img from here. (step 6)
Magisk modules: Busybox and MagiskHide Safety Props Config. (from inside Magisk Manager after successfully rooting with Magisk flashable zip file)
6) Prerequisites:
{Mod edit}
Probably formatting your data.
This means all your stuff, apps, data will be gone after you do this so be prepared and save your stuff to your external SD card.
7) Installing:
A) If you're coming from custom ROM then:
1) Wipe everything (except internal and external storage) including /data/system/dalvik/cache/ but not vendor and vendor shouldn't even appear in the list when wiping anyway.
2) Flash the ROM.zip
3) Flash TWRP.IMG as recovery and again flash it as boot.
4) Flash vbmeta.img as vbmeta.
5) Reboot even if you get notification "no OS is installed".
6) If you're stuck on boot logo for 15+ minutes or bootloop then turn off your device volume up+power then right after shutdown vibration and black screen enter fastboot mode by holding volume down+power, from there select recovery and you should be back to TWRP recovery
7) Select wipe and format data by typing "yes". This will delete all data on internal storage so take care.
8) Reboot to system
9) The device should boot up to COS. Do the initial setup and after that reboot to TWRP recovery again.
10) Flash Magisk.zip
11) Reboot to system
12) Enter Magisk Manager and disable core only mode
13) Reboot to TWRP recovery... again.
14) Flash Magisk COS Fix beta.zip
15) Reboot to system.
16) Check Magisk Manager. Core only mode should be turned off. Check SafetyNet Status. BasicIntegrity should be true now.
17) Download and install MagiskHide SafetyProps and Busybox from Magisk downloads.
18) Reboot to system (normal reboot)
19) Enter Magisk Manager and see if the two installed modules are active. (If yes you probably done everything well. If not, something is fishy.)
20) Download any terminal emulator app, I recommend Termux. Open it and by typing "su" without quotation marks and pressing enter you should grant root access to the terminal app you use. Now type: "props" and press enter.
Type 1) and press enter as edit device fingerprint.
Type f) and press enter as pick from certified fingerprint.
Type 6) and press enter as Google (you can use others too but I used this one so it should be tested).
Type 21) and press enter as Google Pixel 3a XL.
Type 1) and press enter as Android version 9.
Type y) and press enter as yes.
21) Reboot to system and open Magisk Manager. Check SafetyNet Status. Now both cts profile and basicintegrity should be true.
22) Enjoy your better Color OS.
B) If you're coming from stock rom:
If you haven't unlocked your device's bootloader it's time to do it.
After unlocking install TWRP for Realme Q. Then follow the steps above for they're the same.
Don't report issues. I can't help for I'm no developer and I've dyscalculia which means I should be bad at every Informatics stuff that requires math/logic thus I can't compile/rebuild/update ROMs. As for the developer he lost his phone so it's not his interest anymore to make fixes and updates for the ROM/device. Probably pointless to bug him.
Click to expand...
Click to collapse
ROM modified/made by: Birman34
ROM data/turorial written by: greenys'
ROM brought to you by: Realme 5 Pro/Realme Q global Telegram group
{Mod edit}
ROM information:
Security patch date: 2020.01.05.
Kernel version: 4.9.112
Build number: RMX1971EX_11.A.16
Android version: 9.0
It good way to flash global rom for realme Q. But your method is very completed. Thank you anyway!
bahuy2003 said:
It good way to flash global rom for realme Q. But your method is very completed. Thank you anyway!
Click to expand...
Click to collapse
Well, yes. I wish I had found a simpler method but I didn't and I wanted to make sure everything is going to work fine without letting issues happen during or after installation. Perhaps it seems complicated because of that and that I didn't want to take chances. Better be safe than sorry, I presume. For me, who has been flashing ROMs since 2010 it didn't take more than 5 minutes to complete all the steps. Evidently there are lots of users who just gotten into bootloader unlocking and don't know much about the details of flashing. That's why I tried to make this guide quite well detailed. Anyway, if I find a simpler way or I get know of an easier method or Realme itself will approve the change between regional ROMs I'll add those steps to my post of course. Don't thank me yet. Thank me if it worked btw!
Thank you for your tutorial, Excellent!
Should this convert Realme Q to Global version or just ported rom? Developers saying it's impossible for now because of different partitions sizes..
I have flashed the ported R5P rom in the Russian forum on my realme Q few weeks ago..
What about ota update in your method?, would it work and I can update regularly or not? I have to wait update fixes to fit the realme Q?
And can I lock the bootloader or mobile will getting bricked?
Many apps don't work because of root and unlocked bootloader..
Appreciating your effort ??
nagar.xda said:
Thank you for your tutorial, Excellent!
Should this convert Realme Q to Global version or just ported rom? Developers saying it's impossible for now because of different partitions sizes..
I have flashed the ported R5P rom in the Russian forum on my realme Q few weeks ago..
What about ota update in your method?, would it work and I can update regularly or not? I have to wait update fixes to fit the realme Q?
And can I lock the bootloader or mobile will getting bricked?
Many apps don't work because of root and unlocked bootloader..
Appreciating your effort ?
Click to expand...
Click to collapse
According to my knowledge official ROM change from global to China or vice versa is not possible. I don't know about OTA updates. I presume you can't update that way if you flash this ROM for as you said different partition sizes. This ROM while it's still made from global, several stuff from system were removed so it'd still fit onto an RMQ device's smaller partition. The ota updates are not modified this way so I think you couldn't update that way because the ota would be too big to fit onto the RMQ device's partition. I believe you shouldn't worry about root and bootloader unlock. Without rooting and using safetyprops Google notices your unlocked bootloader thus both cts and basicintegrity will fail. In my tutorial I go through that bothersome Magisk method to trick Google's security system. After doing that both SafetyNet checks pass, meaning Google shouldn't see your device as rooted. Root is dangerous for some apps because it can trick them. Unlocked bootloader is dangerous for the device and its owner. At least according to Google. Meaning with Magisk SafetyProps applied only DRM Widevine stuff shouldn't work completely like Netflix full HD and above. Every other app that requires certified device fingerprint should work. Banking apps and online purchases work just fine for me. I think you shouldn't worry, only if you're the type of guy who wants ota updates badly and watches DRM protected content all the time. Else this is completely safe ROM.
greenys' said:
...
Click to expand...
Click to collapse
THREAD CLOSED due to the distribution of warez.
XDA Forum Rules (excerpt).
...
6. Do not post or request warez.
If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit members to request, post, promote or describe ways in which warez, cracks, serial codes or other means of avoiding payment, can be obtained or used. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community.
...
Click to expand...
Click to collapse
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.
hi guys
I have a problem :
I tried to do this manipulation to get freemobile ISP using the following one, on a oneplus 5T
howerver, I tried several manipulation,such as :
[Guide]Activate VoLTE/VoWiFi OOS 11(OB1&OB2)
Hi everyone. /* * Your warranty is void. Or vaild, probably? * * I am not responsible for bricked devices, dead SD cards, Ebolation X, * thermonuclear war, or the current economic crisis caused by you following * these directions. YOU are...
forum.xda-developers.com
until at reboot :
blackscreen + fixed blue led.
I understood it wrote on the modem partition, probably the wrong .mbn files.
I tried to do a wipe cache firstly, then to totally factory reset the device.
Then, it started to bootup android to almost end of user session.
wifi and cell modules are not working right now.
Well, it looks like modem drivers are not the right ones.
problem #1: without internet connection, the oxygen oneplus android stock rom, is stuck on installation wizard.
problem #2: phone is not bootloader-unlocked, which means that I cant install lineageos/twrp.
I tried to do an adb sideload with OEM stock rom zip file several times. It finishes the operation well, but again : at startup of android session, wizard is blocked and doesnt go ahead, sim not detected nor wifi networks detected
how could I fix it?
I thank you vm
Your best bet would probably be MSM, see the guide here and grab the tool from the OP community server in case AFH doesn't work.
Nimueh said:
Your best bet would probably be MSM, see the guide here and grab the tool from the OP community server in case AFH doesn't work.
Click to expand...
Click to collapse
thank you for your answer
unfortunately the corrupted modem drivers block cell+wifi at google startup wizard. everything looks like stuck
bootloader is not unlocked, so I can only adb sideload.
adb sideload worked only with OnePlus5TOxygen_43_OTA_069_all_2010292144_76910d123e3940e5.zip
even into that file it seems that there is the image file for right modem configuration and bin bloobs I guess
even with that, after the end/reboot, android keeps blocked at google installation
I tried the different android images of the link you gave me : none is about to be adb sideloaded (I guess that oneplus made a whitelist of md5 or other kind of file signature to avoid it)
each time Im trying a new android zip file, adb sideload says :
[email protected]:/home/user/$ adb sideload OnePlus_5T_OxygenOS_4.7.6.zip
Total xfer: 0.00x
how could I get this solved?
is it possible to bypass google assistant and cutitoff before starting?
Not sure why you're talking about cell or wifi - MSM tool doesn't need either of those, you simply need to install the drivers and use your PC with the cable. Locked bootloader doesn't matter either and MSM is EDL mode, nothing to do with sideload.
Read + follow the guide I linked
Nimueh said:
Not sure why you're talking about cell or wifi - MSM tool doesn't need either of those, you simply need to install the drivers and use your PC with the cable. Locked bootloader doesn't matter either and MSM is EDL mode, nothing to do with sideload.
Read + follow the guide I linked
Click to expand...
Click to collapse
hey
thank you for your reply
I tried and this putted back the oneplus original firmware
BUT
as I said previously I tried on to upgrade with the xda link above, to get volte enabled on oneplus 5T, using that efstools software command
after few attemps and lot of phone reboots without success of volte, I tried a last one
after rebooting, phone was just black screen+ blue fixed led
but since that moment, I had absolutely no way to get back my modem files
even doing adb sideload with the official oneplus recovery zip, it refreshed the phone from factory reset ; but without any connection
thanks to your new "how to" given in link, Im able now to start an android whom doesnt requires internet connection to use it.
BUT
there is still no qualcomm backup restored.. means that it doesnt see wifi nor cellular connection
Im wondering about how to solve it :
fastboot flash modem NON-HLOS.bin
but, even with oem bootloader unlocked in the developper options :
fastboot flash modem NON-HLOS.bin
Sending 'modem' (108724 KB) OKAY [ 3.267s]
Writing 'modem' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
how could I fix it?
thank you vm
Just use MSM and stop messing with whatever it is you're messing with. You can NOT fastboot one of those MSM roms from the links, you HAVE to use the MSM tool.
MSM will restore your device to a stock OOS version and if VoLTE doesn't work on stock then just leave that alone, try a custom rom or switch to a provider that offers it.
I was able to unlock bootloader finally
but anyway, I flashed twice with the links/tutos you gave me, it doesnt brings back working files for modem
lm8lm8 said:
I was able to unlock bootloader finally
but anyway, I flashed twice with the links/tutos you gave me, it doesnt brings back working files for modem
Click to expand...
Click to collapse
I don't know what exactly you are doing, but you're not supposed to "flash" anything - you're supposed to use the MSM tool to restore the device to it's original state. I'm pretty sure it's not even possible for the modem files to not get restored, but maybe I'm wrong. In which case I don't know how else to help you, sorry
Nimueh said:
I don't know what exactly you are doing, but you're not supposed to "flash" anything - you're supposed to use the MSM tool to restore the device to it's original state. I'm pretty sure it's not even possible for the modem files to not get restored, but maybe I'm wrong. In which case I don't know how else to help you, sorry
Click to expand...
Click to collapse
okay guys, here is a little message to explain what happened
well, in a way I wanted, on OnePlus 5T, to enable volte or/and vowifi, for my ISP Free Mobile...
as several messages reported it (1), it was not an impossible operation. Mainly from xda howto, here is what happened.
1. with last andro running on 5T, I downloaded both apk to answer the original prcoess, with PDC software (whom is not maintained anymore)
while stuck on PDC detecting my device but blocking on an error message : dunno if the software is bugged or just new OT software doesnt allow it.
2. get back on the latest howto, running EFS command line howto (2). It was supposed to work. After several injection plus different reboots without volte working, a last one has been made but.. at reboot, the screen was totally black, with blue fixed led.
I factory reset it, wiping out everything (already saved before), then android was starting back but.. without any wifi/bt/cellular! It was stuck at the end of installation wizard : google doesnt allow usage of this phone, with last update, without connecting to google account, it forbidd it unfortunately.
3. I had so to find back a way to get back android+wifi/bt/cell : I spent hours and days looking for a solution to restore it ; I had no unlocked bootloader, and I finally discovered a way with Oneplus after sales tools (3), that made me able to get a new refreshed old android booting well, but still no wifi/cell/bt. Was however able, so, to unlock the bootloader.. with hope another android image from oneplus could work and bring back my cell working !
4. I was wrong.. so I opened a thread on XDA. Then I remind that on frenchy lafibre forum (dedicated to telecommunications), someone attempted to do so weeks ago... and was also stuck while, after (2) first operation, at reboot wifi/bt/cell were not working anymore too, with others feedbacks showing it! (4). Unfortunately, the link shown in the forums of onplus brings to "internal server error". After that, I did a little investigation to understand that the modem files has to be flashed again. Modem, wifi, BT. I did it several times, thinking fastboot was able to apply directly .img on the destinated partition of phone. Was wrong : erase the partition was necessary! (5)
fastboot erase modemst1
fastboot erase modemst2
fastboot erase modem
fastboot flash modem NON-HLOS.bin
fastboot erase oem_stanvbk
fastboot flash oem_stanvbk static_nvbk.bin
fastboot erase bluetooth
fastboot flash bluetooth BTFM.bin
Was then about to get back cell/wifi/BT ! but the tools of OnePlus doesnt do that.. EFS restoration is really something you have to backup before, and most brand doesnt restore it..
1:
Tutoriel - Activer la VoLTE et VoWifi sur OnePlus 6/7/8
Tutoriel - Activer la VoLTE et VoWifi sur OnePlus 6/7/8
lafibre.info
[Guide] VoLTE + VoWiFi working for German carriers
[UPDATE] Updated QPST version + new how to Exciting news, jamal2367 from https://jamal2367.com has developed a way to get VoLTE + VoWifi working for many countries + carriers. If you are on Vodafone and you are having problems with...
forum.xda-developers.com
2:
[Guide]Activate VoLTE/VoWiFi OOS 11(OB1&OB2)
Hi everyone. /* * Your warranty is void. Or vaild, probably? * * I am not responsible for bricked devices, dead SD cards, Ebolation X, * thermonuclear war, or the current economic crisis caused by you following * these directions. YOU are...
forum.xda-developers.com
3:
[OP5T][LATEST 9.0.11] Collection of unbrick tools
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
OnePlus 5T Unbricking Tool
OnePlus 5T Unbrick tool Here is the Oneplus 5T Unbricking Tool files provided by OnePlus during a Remote Session Download No Password Needed OxygenOS 4.7.4 (Nougat 7.1.1) OxygenOS 5.1.3 Thanks to Titokhan OxygenOS 5.1.7 (Oreo 8.0.1) Drivers...
forum.xda-developers.com
OnePlusCommunityServer
This webserver contains various resources that may be useful to the OnePlus community.
onepluscommunityserver.com
4: https://lafibre.info/4g/tutoriel-activer-la-volte-et-vowifi-sur-oneplus-7/msg782650/#msg782650
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
5. https://droidwin.com/how-to-fix-corrupt-efs-no-imei-network-issues/