Related
1-step
in order to root these qilive devices you will need...
magisk manager apk v5.6.4
stock boot.img file
working ADB to unlock oem and flash
2-step
lets get to it
place the magisk.apk and the stock boot.img
in the internal memory of your phone (downloads)
if you like to keep stuff organized :good:
3-step
follow the vídeo tutorial and use magisk manager
to patch your stock boot.img it will output a new
boot.img that includes magisk Root (patched_boot.img)
https://www.youtube.com/watch?v=BF4_hnKgjFA
ps: major ty to hovatek team for this great tutorial
step-4 use Google drive or usb OTG to get the patched_
boot.img to your PC and place it in the ADB folder
once you have oem(bootloader) unlocked just
rename the patched_boot.img to boot.img
step-5
unlock oem, these qilive devices wont unlock
the bootloader even if you enable it in DEV options
enable USB debug in dev options
you will need to use ADB commands
command- adb devices
serial appears
command- adb reboot bootloader
phone reboots to fastboot mode
command- fastboot devices
serial appears
command- fastboot oem unlock
(MAJOR WARNING the fastboot
oem unlock will wipe/reset/factoryreset/delete your data)
after you give the command small letters will appear
on the phone screen(yes or no) hard to read dont be hasty plz
use VOLUME+ to select and VOLUME - to confirm
note: when my phone ended the unlock it whent back to
that black screen where you choose fastboot-recovery-restart
and was stuck there, side keys did nothing if this happens
just long press the power key for 10 sec it will shutdown
then press power again to turn on
first boot after unlock will take longer then normal dont freakout
after you unlock small letters will appear during boot up saying the device
is not safe unlocked ,you can later use ( fastboot oem lock )
step-6
flash the patched boot.img with ADB
command- adb devices
serial appears
command- adb reboot bootloader
phone reboots to fastboot mode
command- fastboot devices
serial appears
command- fastboot flash boot boot.img
finished/ok
command- fastboot reboot
and voila you should now have magisk
installed in the app drawer, open it!!
step-7 run the install one final time from the
magisk manager and install magisk V16 using
recomended option it will verify/patch the boot image
Do NOT select the AVB 2.0 BOX it will bootloop the phone
and your done, enjoy your qilive rooted phone.
from this point on you can use the fastboot
command- fastboot oem lock
to remove the letters in boot up about the
device not safe unlocked
WARNING oem lock
will WIPE/FACTORY RESET again (god damn it!!)
ps: i had to install twice in a row,major pain in the ....
Repeat step 7 after Wipe/Reset
here is the stock boot for 2 qilive models
you can get the stock firmware for any qilive
at this site www.doc-doapi.com/EM/qilive/smartph...te_3m-fdd-cs_mul_20170818-110645_songlixin_PC
and get the recovery or boot from the unpacked firmware file
ps:my phone is the Q8SIN4GP AND ITS WORKING FINE
A VERY SPECIAL TY to topjohnwu (magisk creator), this man is nothing
short of a God damn genius!! , and if you can donate to him.
hope this helps other qilive users to root:highfive:
quick note on the qilive models, they have two model names
the cliente name in my case Q8SIN4GP
and the factory name in my model its 882912
in order to download the right firmware for your model
you need the factory model witch is what appears in the qilive
site above, it will be in the back of the phone or the original
box on a sticker just bellow the bar code, full model exempl
:Q8SIN4GP/882912 my firmware serves several models,
these Q8 models all start with 88xxxx WARNING
dont try this using the wrong firmware/boot file or you will DAMAGE your phone
Help with BOOTLOOP problems, if you find your self stuck in a bootloop
the phone wont go past the qilive logo and just stays there, dont freak out
you will loose your data but there is a way out
just keep pressing power + Volume up until a black screen with 3 options appears
when it does let go, use Volume + to select option and Volume - to confirm
select Fastboot or alternative select recovery and then select reboot to bootloader
both option will place your phone in Fastboot mode, once in fastboot mode
connect your phone to PC and use ADB commands to fix/bootloop
command- fastboot devices
serial appears
command- fastboot oem unlock (skip this if you use phone unlocked)
a confirm action option appears on the phones screen
use Volume up to say YES / or Volume Down to say NO
Warning oem unlock will WIPE/Factory reset your phone
once it finishes the phone will be stuck on the
Recovery/fastboot/restart screen just long press the power key
until the phone shuts down
start the phone again using Power + Volume up when the black
screen with the 3 options come up, let go and use Volume up to
select Fastboot mode and confirm using Volume Down
Once in fastboot connect your phone to PC and use ADB commands
command- fastboot devices
serial apears
Here you will flash the magisk patched_boot.img
the same image you used to root your phone
command- fastboot flash boot boot.img
it will say finished-ok (or similar)
command- fastboot reboot
the boot up time will be longer than normal
but the phone should now complete the boot
and present the inicial setup screen, select language
enter your mail, the usual bla bla...
any way at this point just repeat step 7
to get root running again
sp flash tools v5.1716.
phonedriller said:
1-step
in order to root these qilive devices you will need...
magisk manager apk v5.6.4
stock boot.img file
working ADB to unlock oem and flash
2-step....
Click to expand...
Click to collapse
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
xdacktheresianum said:
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
Click to expand...
Click to collapse
Awsome work congrats, as for the recovery so far no luck so try not to go 2 crazy until a working recovery is up and working , install stericsons busy box this is always the first root app i install
If possible buy sterics busybox pro and titaniumbackup pro if you want to install apps to sd card apps2sd pro all of these can be tested in free
Version,again nice work congrats enjoy you rooted phone :highfive:
xdacktheresianum said:
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
Click to expand...
Click to collapse
give a hungry man fish and you solve his problem for a day or two
teach him how to fish and you solve his problem for life
phonedriller said:
give a hungry man fish and you solve his problem for a day or two
teach him how to fish and you solve his problem for life
Click to expand...
Click to collapse
hi phonedriller,
...well, i must have been an unlucky fisherman
an app i installed ended up giving me a soft brick (bootloop between qilive icon opening screen - btw still with the "warning" of "device is unsafe etc", i.e. oem still open - and black screen, qilive opening screen etcetcetc)
have cleaned cache; went for factory reset; etc
BUT: am presently stuck when trying to go via ADB (which used to work perfectly before) that somehow the usb drivers don't want to get installed properly. as a consequence, desktop cannot see devices.
and i cannot, for the sake of me, remember how i had succeeded before installing usb drivers.
could you please help?
thx
cktheresianum
xdacktheresianum said:
hi phonedriller,
...well, i must have been an unlucky fisherman
an app i installed ended up giving me a soft brick (bootloop between qilive icon opening screen - btw still with the "warning" of "device is unsafe etc", i.e. oem still open - and black screen, qilive opening screen etcetcetc)
have cleaned cache; went for factory reset; etc
BUT: am presently stuck when trying to go via ADB (which used to work perfectly before) that somehow the usb drivers don't want to get installed properly. as a consequence, desktop cannot see devices.
and i cannot, for the sake of me, remember how i had succeeded before installing usb drivers.
could you please help?
thx
cktheresianum
Click to expand...
Click to collapse
PS: adb will not work if the phone is not booting to the OS
it will work if you manualy place the phone in fastboot AKA bootloader
MODE ,you see if it does not boot to OS then usb service is not working
use power + Volume up to enter the black menu
use the Volume up to select fastboot(bootloader) volume - to confirm
connect the phone to your PC
flash the boot.img, the same boot.img used to root (patched by magisk)
to see is adb is ok just run - fastboot devices
if a serial is presented then all other stuff should work
step 1 - reflash the boot img
step 2 - after the flash finishes - fastboot oem lock
message on the phone screen, confirm yes to lock
OEM
step 3- press power until it turns off
it should now complete the start up (boot)
if not working this method let me now
you can still flash the full factory firmware
using SP Flash Tool v5.17xx
phonedriller said:
PS: adb will not work if the phone is not booting to the OS
it will work if you manualy place the phone in fastboot AKA bootloader
MODE ,you see if it does not boot to OS then usb service is not working
use power + Volume up to enter the black menu
use the Volume up to select fastboot(bootloader) volume - to confirm
connect the phone to your PC
flash the boot.img, the same boot.img used to root (patched by magisk)
to see is adb is ok just run - fastboot devices
if a serial is presented then all other stuff should work
step 1 - reflash the boot img
step 2 - after the flash finishes - fastboot oem lock
message on the phone screen, confirm yes to lock
OEM
step 3- press power until it turns off
it should now complete the start up (boot)
if not working this method let me now
you can still flash the full factory firmware
using SP Flash Tool v5.17xx
Click to expand...
Click to collapse
dearphonedriller,
thank you so much for your speedy help.
followed the steps given by you. all is well, as you predicted, until step 3.
however:
phone (now without the "orange state" message, i.e. oem locked) still bootloops and short of ADB "fastboot devices" the desktop doesn't see the phone (and driver installation continues to fail), as per your PS (thanks!) i guess flashing the full factory firmware ("RC-mt6737...zip" quoted by you in your very first post) is next.
would you please point me to a basic-for-noobs tutorial or instruct me on the step-by-step commands/procedures using this zip file?!
HUGE thanks
ckth
xdacktheresianum said:
dearphonedriller,
thank you so much for your speedy help.
followed the steps given by you. all is well, as you predicted, until step 3.
however:
phone (now without the "orange state" message, i.e. oem locked) still bootloops and short of ADB "fastboot devices" the desktop doesn't see the phone (and driver installation continues to fail), as per your PS (thanks!) i guess flashing the full factory firmware ("RC-mt6737...zip" quoted by you in your very first post) is next.
would you please point me to a basic-for-noobs tutorial or instruct me on the step-by-step commands/procedures using this zip file?!
HUGE thanks
ckth
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=-zaEmj3-prU
turn the phone off, follow the video
flashing the full firmware is actualy easy
https://forum.hovatek.com/thread-13970.html
or searh sp flash tool here on xda
https://www.youtube.com/watch?v=LzyYXAflmOk&t=125s
phonedriller said:
https://www.youtube.com/watch?v=-zaEmj3-prU
turn the phone off, follow the video
flashing the full firmware is actualy easy
https://forum.hovatek.com/thread-13970.html
or searh sp flash tool here on xda
https://www.youtube.com/watch?v=LzyYXAflmOk&t=125s
Click to expand...
Click to collapse
thank you, phonedriller
everything worked perfectly via SPFlash Tool.
and, referring back to our above questions re the possibility of getting TWRP onto the phones, a developer friend of mine writes me this:
>try to flash TWRP:
>Download following files from this link:
>https://mega.nz/#F!qZIgnJRK!5apBfYo1je0ytg-wmA6JMQ
>- Odin3 v3.12.3 (Complete folder)
>- twrp-3.2.1-0-Q8S55IN4G2-20180318.tar
>1. Start your Phone into download mode
>2. Start Odin (Odin3 v3.12.3\Odin3.exe)
>3. Click on Options and unmark Auto Reboot
>4. Click AP and select twrp-3.2.1-0-Q8S55IN4G2-20180318.tar
>5. Press Start and wait until finished (Reset or OK!)
>6. Restart your phone immediatly to recovery mode
>7. In TWRP Recovery click on mount
>8. Set the checkbox checked at system (that system is mounted)
>9. go back and click on advanced
>10. Open file manager
>11. navigate to system/build.prop and click on build.prop
>12. Click on chmod
>13. type: 0644 and hit the accept button on screen or at the virtual
>keyboard on your phone
>14. restart your phone
i haven't tried this, but am wondering whether it might seem "reasonably possible" when reading through it.
thanks
ckth
Do you perhaps have link to Q8S5IN4GP stock rorm? Mine came with malware installed on it. I want to see if those were chinese who preinstalled or or was it decided by Auchan.
tommo1982 said:
Do you perhaps have link to Q8S5IN4GP stock rorm? Mine came with malware installed on it. I want to see if those were chinese who preinstalled or or was it decided by Auchan.
Click to expand...
Click to collapse
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
phonedriller said:
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
Click to expand...
Click to collapse
I had issues with adds being displayed at home screen and I was not able to close them. I had to use NetGuard to find that FOTA talks to 'adsup' and it is a known malware provider. I learned that some of the system apps try to talk with Alibaba servers and AdOppo (whatever it's called). Kaspersky might not be wrong, actually.
I'm trying to download stock firmware, but I don't know the file name. The website with it is locked, so unless I know exactly what I need, I cannot download it.
phonedriller said:
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
Click to expand...
Click to collapse
Yes i noticed the site now asks for a login that i dont have,but it was open to all until recently i have the firmware file in my pc,a few days ago i went to check for firware updates and the site was diferent and closed , in the site the download link was 882912/****** this firmware services at least 3 similar models
phonedriller said:
Yes i noticed the site now asks for a login that i dont have,but it was open to all until recently i have the firmware file in my pc,a few days ago i went to check for firware updates and the site was diferent and closed , in the site the download link was 882912/****** this firmware services at least 3 similar models
Click to expand...
Click to collapse
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
phonedriller said:
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
Click to expand...
Click to collapse
Ps use root + apps2sd or titaniumbackup to stop/disable the bad apps and replace them with playS app,not possible on all apps of course
phonedriller said:
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
Click to expand...
Click to collapse
I'm thinking about Android 8.1 with it's Treble project. I might not be knowledgable enought to compile and flash it, though.
tommo1982 said:
I'm thinking about Android 8.1 with it's Treble project. I might not be knowledgable enought to compile and flash it, though.
Click to expand...
Click to collapse
Flashing is super easy use spflashtools or. Odin compiling a Rom is not , were you able to get the original firmware? You will need the original firware to get the boot and partition info from what i read so far
Unfortunately not. I will ask at the shop where I bought it how to contact tech. It should be freely available. I don't understand why Qilive restricted access to firmware.
I'll post when I learn anything.
Well, you can download the firmware if you know the file name. The bad news is, it seems the stock firmware has malware preinstalled. If there is anyone who could help confirm it. I have the ROM, and I can upload it to Google Drive if needed.
Hi all,
I'm coming back to a question lingering since the very first post here and mentioned again in post #9:
Is there a successful way to install TWRP on this Qilive model?
Re this topic:
- has anybody tried/has anybody been successful with the procedure described in post #9?
and
- has anybody seen the following TWRP builders' version (do an in-page search on Q8S55IN4G2)
https://twrpbuilder.github.io/fr/downloads/twrp/
with the download belonging to it
https://androidfilehost.com/?fid=890129502657591798
???
any successful installations to report???
Wouldn't THAT be great!!??
thanks
xdack
Hey everyone,
My questions are at the end below, but they need a bit of history which might be useful to someone in similar position.
I have SGP321 and used it stock for a number of years without much issues. Lately though it seems the age of the device shows itself and I wanted to try a custom LineageOS ROM on it - I 've done this before with several other devices.
I tried to follow this guide - [Guide/tutorial] Sony Xperia Tablet Z LTE or Wifi Any version to Android 8 - however the service menu of the tablet showed that the bootloader cannot be unlocked. Attempts to unlock the device using fastboot oem unlock 0xYOURUNLOCKKEY using and unlock code from https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/ showed that the bootloader of the tablet is indeed locked and the lock cannot be removed. I also tried to use the Flashtool to unlock the bootloader - again unsuccessfully.
Being stubborn as I am, I rooted the tablet using this guide - [Guide][Easiest Way]How to Root Xperia Z Android 5.1.1 Without PC and Get SuperSu - which works for Tablet Z as well. Having root access gives possibility to work around the bootloader lock to some extend since access to the tablet storage happens from the OS. I proceeded to copy twrp-3.3.1-0-pollux.img to the external sdcard of the device and executed from a root terminal on the device:
dd if=/sdcard1/twrp-3.3.1-0-pollux.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernelwhich completed without complaint, then I rebooted and tried to enter recovery by using repeated presses of volume-up and volume-down buttons as well as other combinations like holding them pressed simultaneously, combining the volume buttons with the power button - no positive result (most probably as I read later because the stock BL doesn't support recovery). Then I decided to install the official TWRP app and the used it to install the image to the recovery partition - again no result booting into recovery. Then (foolishly) I used the app to try to install the TWRP image in the boot partition - no problems there, however on the next reboot the tablet was bricked
In this state when trying to power-on the tablet the indicator LED starts flashing in red and the screen remains black. Power-off was possible through pressing volume-up and power buttons for more than 10 seconds. It was also possible to enter fastboot mode by powering-off the tablet and holding volume-up while inserting a USB cable that was plugged to a PC - success was indicated by a continuous blue indicator LED. Attempts to use fastboot flash or fastboot boot with TWRP image didn't give any positive result - the first failed with "Operation not allowed", the second failed with "Too many links". I also tried the same with kernel.sin and fotakernel.sin files from the stock ROM FTF file downloaded using the Flashtool - again unsuccessfully.
Using the Flashtool itself to restore the stock ROM failed initially because the on-screen instructions for getting into flash/download mode - powering off and then holding the volume-down button while inserting a USB cable that was plugged to a PC - didn't work in my case. Then I decided to use this sequence:
powering off
first pressing and holding the volume-down button
second pressing and holding the power button
finally - inserting a USB cable that was plugged to a PC
I was awarded with short green flash of the indicator LED and the Flashtool recognized the device as being in flash/download mode. I then proceeded to flash the downloaded stock ROM using the default settings. The flash was successful, and I was back to square one. I also rooted the device again as described above.
My questions:
Does anyone know of a method that allows to use the root shell of the device itself to remove the bootloader lock? For example, custom copy/flash using the dd command from a root shell and partition images extracted form TWRP/Custom non-stock ROMs.
Is it possible in the situation of my device to install/flash custom recovery/kernel/ROM if we assume that the bootloader cannot be changed?
Thanks in advance for your time and thoughts...
iiontihy said:
Hey everyone,
My questions are at the end below, but they need a bit of history which might be useful to someone in similar position.
I have SGP321 and used it stock for a number of years without much issues. Lately though it seems the age of the device shows itself and I wanted to try a custom LineageOS ROM on it - I 've done this before with several other devices.
My questions:
Does anyone know of a method that allows to use the root shell of the device itself to remove the bootloader lock? For example, custom copy/flash using the dd command from a root shell and partition images extracted form TWRP/Custom non-stock ROMs.
Is it possible in the situation of my device to install/flash custom recovery/kernel/ROM if we assume that the bootloader cannot be changed?
Thanks in advance for your time and thoughts...
Click to expand...
Click to collapse
Hello!
1. If you have operator carrier device like DOCOMO or Orange, then you're out of luck. Carrier branded devices cannot be unlocked, so no TWRP and custom ROMs like LOS, RR, CR, etc.
2. If you have ordinary device, you can unlock the bootloader and install whatever ROM you like, no limitations here.
Root access nor recovery are needed for bootloader unlock.
Thanks Rootk1t, the device was purchased and is locked to a local carrier - so I guess I'm out of luck.
Still, a valuable experience while trying to flash it and having it rooted might allow to squeeze a bit more life out of it
iiontihy said:
Thanks Rootk1t, the device was purchased and is locked to a local carrier - so I guess I'm out of luck.
Still, a valuable experience while trying to flash it and having it rooted might allow to squeeze a bit more life out of it
Click to expand...
Click to collapse
Stock 5.1.1 + root + XZDR + Xposed + some mods (like SDFix for Lollipop; XReality+SuperVivid; xLOUD) is not bad at all.
Realme devices are nice because bootloader unlocks are officially allowed by the company. Unfortunately, they usually also have to be explicitly released, in the form of a DeepTesting/In-Depth Test app from OPPO/Realme. You usually can't take the DeepTesting APK from another device and install it, and if you do, Realme still has to whitelist the device model on the server backend. It turns out that at least the X3 SuperZoom is actually whitelisted for bootloader unlocking by Realme. Now all we need is a DeepTesting APK that'll install, which we do. The Realme 6 Pro's version installs just fine on the X3 SuperZoom.
Since this isn't official yet, I figured I'd share a "guide" (my process) for unlocking the bootloader on the Realme X3 SuperZoom (it should also work on the normal X3, but I don't have one to confirm). Let's get started.
NOTE: I think this goes without saying, but unlocking the bootloader WILL wipe your data, and it WILL void any warranty you may have. While you can relock the bootloader, you shouldn't do this in the first place if you aren't sure.
First up, enable Developer Options. Go to Settings >> About Phone >> Baseband & Kernel and tap the Build Number field 7 times.
Next, go to Settings >> Additional Settings >> Developer Options and enable OEM Unlocking.
Now, download the Realme 6 Pro DeepTesting APK (in the attachments here).
Open it up (launcher shortcut is called In-Depth Test) and start the application process. Agree to the disclaimers and whatnot, and send in the application. (NOTE: If you get an error about your device being carrier-customized, you can work around this. I'll write up another guide for that later.)
After a few minutes, check your application status (the tiny green link at the top right of the home page of the app). It should say "Approved" with another tiny green link to "Start In-Depth Test."
Tapping that link will cause your phone to reboot into fastboot mode. If you don't have fastboot installed on your computer, follow these instructions.
Plug your phone into your computer and execute "fastboot flashing unlock". (NOTE: I had to unplug and replug my phone for every command. Otherwise, fastboot would sit there with "< waiting for any device >".)
Your phone should now show a bootloader unlock prompt. Use the volume buttons to choose the option to continue with the unlock, and use the power button to confirm.
The phone will wipe all data and restart into the setup wizard.
That's it! If you want to root with Magisk, follow this guide: https://forum.xda-developers.com/x3-superzoom/how-to/guide-root-realme-x3-superzoom-magisk-t4136333.
This is great info, thanks @Zacharee1!
Will be unlocking as soon as there is a good recovery software that I can use, which will make rooting process easier.
How long point 5 "After a few minutes, check your application status (the tiny green link at the top right of the home page of the app). It should say "Approved" with another tiny green link to "Start In-Depth Test."
should take, is more than one hour that stay on status "application submitted"
Anyone tried GSI images after unlocking bootloader?
ch3mn3y said:
Anyone tried GSI images after unlocking bootloader?
Click to expand...
Click to collapse
I wouldn't recommend it. My unit is hardware defective and I'm returning it to Realme soon anyway, so I tried an LOS 17.1 GSI. So far, I've only managed to get it stuck at the bootloader splash screen. It just doesn't get past that state. And it's a pain to restore to a functional system. I had to use a leaked OFP and the fastboot that comes with the Realme Flash Tool to reflash the super.img. Stock fastboot breaks things further when flashing it. I have one more combination of weirdness to try, but it doesn't seem like GSIs really work.
I'm not a ROM or bootloader expert, so it's possible I'm just doing something wrong, but if I am, it's certainly not easy to flash a GSI right now. I think the best thing to do is wait for the official bootloader unlock and kernel source, and then someone should be able to build TWRP.
How long can it take for an application to be approved? I'm waiting for 15-20 minutes already
EDIT: OK, I'm just to lazy to check it.
Thanks for the guide, at least I have root now.
Just bumping this thread - any recoveries available for X3 Super Zoom yet?
Though root is possible now, I am waiting for a bit more easy process of flashing through a recovery.
phonedroid said:
Just bumping this thread - any recoveries available for X3 Super Zoom yet?
Though root is possible now, I am waiting for a bit more easy process of flashing through a recovery.
Click to expand...
Click to collapse
PBRP RECOVERY IS Available on Telegram Channel
What telegram channel?
SolankiDS064 said:
PBRP RECOVERY IS Available on Telegram Channel
Click to expand...
Click to collapse
When I checked the PBRP website, there are recoveries available only for Realme X, X2, XT etc, but not for X3 Super Zoom. Can you please give the details about the telegram channel?
EDIT: I got the Telegram channel info from their website. Thanks. (Still to check for X3 SS recovery availability)
phonedroid said:
When I checked the PBRP website, there are recoveries available only for Realme X, X2, XT etc, but not for X3 Super Zoom. Can you please give the details about the telegram channel?
EDIT: I got the Telegram channel info from their website. Thanks. (Still to check for X3 SS recovery availability)
Click to expand...
Click to collapse
https://t.me/RealmeX3Updates join this Group
And Development has been Stopped for Realme X3& SuperZoom because of Developers have No Realme X3 Device
---------- Post added at 08:04 AM ---------- Previous post was at 07:08 AM ----------
phonedroid said:
When I checked the PBRP website, there are recoveries available only for Realme X, X2, XT etc, but not for X3 Super Zoom. Can you please give the details about the telegram channel?
EDIT: I got the Telegram channel info from their website. Thanks. (Still to check for X3 SS recovery availability)
Click to expand...
Click to collapse
https://t.me/RealmeX3Updates
Is there any information after unlocking the bootloader, that it is unlocked when the phone boots up?
For example, in Nexus 7/4 there is an unlocked padlock icon after each reset.
@Zacharee1
Official tutorial for Android 10 is released at https://c.realme.com/in/post-details/1365223130418737152
Thanks
After running a dedicated unlock "in-depth test" app, phone reboots, enters fastboot mode for a second (screen with fastboot and some chinese chars), then reboots to system. When my phone is plugged to PC I try to type "fastboot devices" in platform tools and my phone is not visible there, however it is visible when I type "adb devices" I can not boot into fastboot mode manually either - after pressing VOL UP + POWER for a few seconds, it boots up to fastboot and then immediately restarts to system. How can I possibly unlock the bootloader?
I'm gonna note that the same thing happens when I try to execute "adb reboot bootloader" - boot to fastboot mode for few seconds, then restart to system immediately
Any idea what to do?
M1ch0k0 said:
After running a dedicated unlock "in-depth test" app, phone reboots, enters fastboot mode for a second (screen with fastboot and some chinese chars), then reboots to system. When my phone is plugged to PC I try to type "fastboot devices" in platform tools and my phone is not visible there, however it is visible when I type "adb devices" I can not boot into fastboot mode manually either - after pressing VOL UP + POWER for a few seconds, it boots up to fastboot and then immediately restarts to system. How can I possibly unlock the bootloader?
I'm gonna note that the same thing happens when I try to execute "adb reboot bootloader" - boot to fastboot mode for few seconds, then restart to system immediately
Any idea what to do?
Click to expand...
Click to collapse
Are you sure the unlock application succeeded? This means bootloader unlocking isn't allowed.
Not quite sure it succeeded, I was able to start in-depth test, phone rebooted to fastboot mode (white fastboot logo with chinese chars) for a second and immediately went to system after, I don't know if it was a proper behaviour.
M1ch0k0 said:
Not quite sure it succeeded, I was able to start in-depth test, phone rebooted to fastboot mode (white fastboot logo with chinese chars) for a second and immediately went to system after, I don't know if it was a proper behaviour.
Click to expand...
Click to collapse
Did you enable the OEM Unlocking switch in Developer Options?
Yes, I enabled it.
Zacharee1 said:
Are you sure the unlock application succeeded? This means bootloader unlocking isn't allowed.
Click to expand...
Click to collapse
Is there any way to get around this? it's weird because I bought the phone online and not in any telecommunication services provider. why would they block it?
M1ch0k0 said:
Is there any way to get around this? it's weird because I bought the phone online and not in any telecommunication services provider. why would they block it?
Click to expand...
Click to collapse
I don't know why it's happening, sorry.
Hey everyone. Today I've finally unbricked my Zenfone 7 after my dumbass locked the oem with fastboot since I've already rooted my phone and didn't want to use adb anymore (I was getting tired of the warranty voided message at boot too). Right after locking the oem, the phone booted and displayed a message that says: " Your device is corrupted. It cannot be trusted and won't boot". You already could tell I was scared as hell, so all I did the past hours was to look around until I found this solution!
Have in mind I'm not an expert or a developer, I'm only hoping you find this thread if you ever find yourself locked in fastboot with no access to recovery, oem, adb or usb debugging, just fastboot commands.
Having said that, you need to flash the raw firmware for your device. For the Zenfone 7 the one you need is "WW__ZS670KS_29.14.53.5_MR1.3_20201111_release-user.raw".
You also need:
- Android sdk and platform tools (minimal adb works too but I recommend original google software)
- Usb asus drivers
- Usb google drivers (installable from android studio just like sdk and platform tools)
Turn on your device on fastboot and connect it to your pc, then open cmd or powershell on your platform-tools folder and execute
Code:
fastboot devices
to check if your zenfone is detected. Close the command prompt.
Now, on the raw rom folder open flashall_AFT.cmd as administrator, then it should start flashing all of the stock firmware files. Once the prompt closes itself, reboot your phone using volume keys and power button to select.
In my case, right after booting, the phone displayed a message that said "your phone is corrupted" but with a wipe data option this time around. Choose wipe data/factory reset (all your data will be gone).
There you go! The phone should reboot into stock clean rom now.
I get Flashing is not allowed in Lock State
RickJF said:
I get Flashing is not allowed in Lock State
Click to expand...
Click to collapse
did you unlock bootloader?
IronSingh said:
did you unlock bootloader?
Click to expand...
Click to collapse
No, to do so I need go get into developer tools,
wich I can't because android won't boot
[ROM][OFFICIAL] Omnirom for zenfone7/7pro [Android-13.0]
What is Omnirom ? Selinux Status: Enforcing Instructions : Follow this Steps by steps You need to be lastest firmware on both slots Please. How to have lastest FW on both slots: Reboot twrp Flash stock + twrp on opposite reboot recovery do...
forum.xda-developers.com
RickJF said:
No, to do so I need go get into developer tools,
wich I can't because android won't boot
Click to expand...
Click to collapse
RickJF said:
I get Flashing is not allowed in Lock State
Click to expand...
Click to collapse
How strange, you shouldn't need OEM unlock to flash the raw rom. Hope you get through it... meanwhile I'll let you know if I find a possible solution
tommydotwav said:
How strange, you shouldn't need OEM unlock to flash the raw rom. Hope you get through it... meanwhile I'll let you know if I find a possible solution
Click to expand...
Click to collapse
What is the problem?
tommydotwav said:
How strange, you shouldn't need OEM unlock to flash the raw rom. Hope you get through it... meanwhile I'll let you know if I find a possible solution
Click to expand...
Click to collapse
thanks, I've searched enough and tried it all, sent ticket to Asus support,
they say considering all that it's probably physically corrupted,
nothing much I can do at home
RickJF said:
thanks, I've searched enough and tried it all, sent ticket to Asus support,
they say considering all that it's probably physically corrupted,
nothing much I can do at home
Click to expand...
Click to collapse
DM me, make sure you are able to do test Point, we can fix it via EDL
the idea is to simply deggogle my a10. i found a few videos on how to do it. however i took the liberty of making a note of the base build number and after searching the internet, i found a firmware farchive that contained several md5 files. i figured i may need this in case anything went wrong.
so i went into settings and developer mode, turned on unlocking oem and usb debugging and attempted to flash the phone by booting into rescue mode (power off phone then power on while holding the volume up button) then selecting boot into bootlader from the menu before using a toll called odin on my pc, which given the threads i've seen on here, most of you are aware odin. i tried to flash the tar file reccomended on the site. odin reported failure. so without rebooting i flashed the firmware that matched my phone my selcting the respective md5 files and telling odin to do it. it reported neither success nor failure but gave a message of something like cs select. i have no idea what that means. however on rebooting the phone it booted fine. no errors or anything, just a completely reset phone. I like to add that this is not may main phone as i am a newbie on this area and wouldn't be so reckless as to experiment on my main phone. hower there is an app on there now called lazade which i beleiv is a shopping app based in the asian continent which isn't where i'm from. i unlocked developer mode once again as it had reset and found that the unlock oem option is missing. is it becasuse of the firmware i burned on it and to i need to reburn another? or is ther another way to get it back?
the baseband version is a105gdxu8cvg2
android 11
one ui 3.1
Your post isn't very clear....have you been able to unlock your bootloader?
The OEM Unlock toggle often disappears if 1) the bootloader is already unlocked, or 2) the system has not yet verified whether OEM unlocking is allowed. This is most likely not a firmware issue.
V0latyle said:
Your post isn't very clear....have you been able to unlock your bootloader?
The OEM Unlock toggle often disappears if 1) the bootloader is already unlocked, or 2) the system has not yet verified whether OEM unlocking is allowed. This is most likely not a firmware issue.
Click to expand...
Click to collapse
it's an old phone. i've had it for a number of years, but i got a new phone recently so i took the oppounity to attempt to degoogle my old one. apparently there's more than one way to do this One is to replace android with other operating system. if youtube is to be beleived. i doubt the phone needs veryfying as it's an old phone although the firmware is fresh. perhaps it is unlocked. in tairness i don't know how to determine that.
fjb59 said:
it's an old phone. i've had it for a number of years, but i got a new phone recently so i took the oppounity to attempt to degoogle my old one. apparently there's more than one way to do this One is to replace android with other operating system. if youtube is to be beleived. i doubt the phone needs veryfying as it's an old phone although the firmware is fresh. perhaps it is unlocked. in tairness i don't know how to determine that.
Click to expand...
Click to collapse
The best I can suggest is to flash a LineageOS GSI without Gapps. There are other custom ROMs available that are sanitized of all Google services.
V0latyle said:
The best I can suggest is to flash a LineageOS GSI without Gapps. There are other custom ROMs available that are sanitized of all Google services.
Click to expand...
Click to collapse
are they available here?
fjb59 said:
are they available here?
Click to expand...
Click to collapse
Just Google LineageOS, they have a website. You should be able to flash a GSI image via TWRP.
V0latyle said:
Just Google LineageOS, they have a website. You should be able to flash a GSI image via TWRP.
Click to expand...
Click to collapse
that's my next goal. i haven't got twirp on there. none of the methods i saw on youtube worked.
fjb59 said:
that's my next goal. i haven't got twirp on there. none of the methods i saw on youtube worked.
Click to expand...
Click to collapse
i found the site for it but the a10 is not listed on thier choice of phones
Assuming your bootloader is already unlocked, here is the TWRP thread for your device., which you probably could have found by searching. Instructions for flashing are in that thread. And here is the LineageOS 19.x GSI thread.
If you haven't unlocked your bootloader yet, that's your first step. Some devices are not bootloader unlockable.
V0latyle said:
Assuming your bootloader is already unlocked, here is the TWRP thread for your device., which you probably could have found by searching. Instructions for flashing are in that thread. And here is the LineageOS 19.x GSI thread.
If you haven't unlocked your bootloader yet, that's your first step. Some devices are not bootloader unlockable.
Click to expand...
Click to collapse
i don't know if i have yet. i went though a process and now the oem unlocking option disappeared ffrom the developer menu. i can boot into the bootload from the rescue menu. I assume that's what you mean.
fjb59 said:
i don't know if i have yet. i went though a process and now the oem unlocking option disappeared ffrom the developer menu. i can boot into the bootload from the rescue menu. I assume that's what you mean.
Click to expand...
Click to collapse
When you're in download mode, you should see OEM LOCK among the text in the upper right of the screen. If this says ON, your bootloader is locked.
V0latyle said:
When you're in download mode, you should see OEM LOCK among the text in the upper right of the screen. If this says ON, your bootloader is locked.
Click to expand...
Click to collapse
oem lock onu1)
looks like it's on. how do i disable it for this phone?
Turn the phone completely off, and leave it off for a few minutes. Then, while holding both Volume buttons together, plug in the USB cable. The device should start in Download mode. Hold Volume + until the bootloader unlock screen appears, then follow the prompt to unlock your bootloader. This will wipe data.
V0latyle said:
Turn the phone completely off, and leave it off for a few minutes. Then, while holding both Volume buttons together, plug in the USB cable. The device should start in Download mode. Hold Volume + until the bootloader unlock screen appears, then follow the prompt to unlock your bootloader. This will wipe data.
Click to expand...
Click to collapse
never shows up. i get to the download screen but pressing the vol up keys doesn't do anything. not even adb can see the device. use debugging is turned on. and usb mode is set to file transfer mode. it weorked finde before i reflashed it. perhaps i need another version of the firmware
development, i noticed the wifi wasn't turned on. i turned it on the went into the development mode. unlock oem was there and ticked
so i did what you said again, this time the option for unlocking oem in download was present. i followed the instructions. it booted and came telling me the oem is unlocked and won't be able to verify the intergrty of the os. now it's doing a reset. i think we got here. what next? you you said twrp?
fjb59 said:
never shows up. i get to the download screen but pressing the vol up keys doesn't do anything. not even adb can see the device. use debugging is turned on. and usb mode is set to file transfer mode. it weorked finde before i reflashed it. perhaps i need another version of the firmware
Click to expand...
Click to collapse
ADB only works in Android or in recovery mode. Samsung devices don't have a fastboot mode.
fjb59 said:
development, i noticed the wifi wasn't turned on. i turned it on the went into the development mode. unlock oem was there and ticked
so i did what you said again, this time the option for unlocking oem in download was present. i followed the instructions. it booted and came telling me the oem is unlocked and won't be able to verify the intergrty of the os. now it's doing a reset. i think we got here. what next? you you said twrp?
Click to expand...
Click to collapse
Yep. Since you don't already have TWRP installed, follow "Method 2" in the thread I linked.
V0latyle said:
ADB only works in Android or in recovery mode. Samsung devices don't have a fastboot mode.
Yep. Since you don't already have TWRP installed, follow "Method 2" in the thread I linked.
Click to expand...
Click to collapse
yep it does. i had a little bit of trouble between installing the first and second file. it kept reporting a corrupt operating system but i noteiced it cycled a reboot wo i held hte power and volume up buttons together when it cycled. this allowed me into rescue mode. from there i was able to power down the phone so i could reboot it back into download mode then upload the rescue file contained in the zip file mentioned. after that it booted ok but keeps claiming that the operating system isn''t offician but then boots into android ok. i expect installing the disable_drm_very app wil fix that. then i can try installign a new os.
but that's for tomorrow
Jjflick said:
I noticed this thread and would like to keep looking
Click to expand...
Click to collapse
i hope it helps you. i've detailed the steps i took as best as i could.