After updating to latest update, now the phone only shows background with either the "LOCKED" or "UNLOCKED" icon on the top and is constantly flickers on/off every second.
No response on the touchscreen either.
Attached video
Am currently downloading a stock rom (https://www.mediafire.com/file/bu4s...21062302340000_%28Mobileguru4.com%29.zip/file).
In the meantime, I installed the drivers for realme and the Realme Flashtool. Plugged in the phone to the PC using the cable however, the device is not recognized by the Realme Flashtool software, or is not "detecting" the phone.
(The driver I installed was this: https://www.mediafire.com/file/d3xf...river_Setup_V2.0.1.1_MobileGuru4.com.zip/file)
I have a guess on what it might be that's causing it (inside the developer settings option, sensors option). Not sure how to turn that **** off without being able to access the phone.
Scorpionish said:
Am currently downloading a stock rom (https://www.mediafire.com/file/bu4sjesfikq74dg/RMX2085_RMX2086export_11_C.07_2021062302340000_%28Mobileguru4.com%29.zip/file).
In the meantime, I installed the drivers for realme and the Realme Flashtool. Plugged in the phone to the PC using the cable however, the device is not recognized by the Realme Flashtool software, or is not "detecting" the phone.
(The driver I installed was this: https://www.mediafire.com/file/d3xf...river_Setup_V2.0.1.1_MobileGuru4.com.zip/file)
Click to expand...
Click to collapse
Download Driver Booster app (free version), run in and find Android drivers option and install. It will clear most of the driver issues.
Realme Flashing tool is not working and no other flashing tool worked forme, only fastboot method is worked good
Llatest stock images not having partitions of System and Vendor, they may be userdata and others.
Install "Minimal ADB Fastboot" and then download latest Stock OFP file.
Erase Data, if possible flash OrngeFox / custom recovery and format the phone.
Download this OFP to Scatter format (Link: https://softwarerom.blogspot.com/2021/03/ofp-file-cmd-converter-ofp-file-extract.html) and unzip it
Copy Latest Stock OFP to this folder and Just push the OFP to Qualcomm... Exe file, it will open a command prompt and create a folder contains some files & folder including Images,
Copy all the image files to Minimal ADB Fastboot folder, open Minimal ADB fastboot command prompt and copy all the images like, recovery, boot, vbmeta, userdata and so on using "Fastboot Flash Name Name.img" commands and reboot.
It worked for me.
The problem has reoccurred, exact same problem issue (browsing playstore, exited, closed phone, a moment later after opening up the phone) same thing happened, screen just flickering on&off.
I dont get how such problem could occur, now am certain its not the (sensor thing) cus this time (after PHONE WIPE) I did not play with any of those settings or (dev settings).
Honestly, if any1 experienced this, or might have a clue whats causing it.
[email protected] said:
Download Driver Booster app (free version), run in and find Android drivers option and install. It will clear most of the driver issues.
Click to expand...
Click to collapse
Its not a drivers issue, was able to plug in phone after having wiped the phone data (a complete reset), but did reinstall just incase, thx.
Also, I dont see how that fixes the issue (its a stock firmware)
Phone was working just fine after hard reset/wipe.. for a few months that is.
Related
Seems this device has no support anywhere. I spent the last 28 hours trying to fix my problem with no luck it went as follows:
-The device rom had a lot of adware related to something called: com.android.ser
-To get rid of it I rooted it successfully using FrameRoot
-I used some malware cleaners and deleted some sytem apps reported by them including com.android.ser
-My big mistake: I felt I need to clean more, and thought Mediatek apps are another source of adwares and deleted them, the device crashed and when rebooted stuck in bootloop.
-I went into recovery and deleted cache + data , didn't work
-installed ADB and tried sideload (which is an available option in the stock recovery) a ROM which I found here. It pushed the rom up to 100% but immediately failed after that.
-used fastboot app. It connected successfully, could restart the device from there but when I try to flash system.img it fails.
-USB debugging in developer options were most probably not enabled as I remember. Unknown sources was enabled.
Help is appreciated.
Update: Resolved. I'm posting the solution below, which is generic for Mediatek Devices, just ensure you use your own device's ROM, recovery,boot,...etc
(please note we are working on Windows)
(This Video has most of the below notes)
1- From device manager manually install Mediatek USB VCOM drivers and ADB, , installing PDANet (free PC application)helps a lot for some of driver installation, which was true in my case. Installation of PDA Net should be while device is connected and in normal mode (The boot loop in my case).
2-Download Smart Phone Flash Tool
3- You need what is called the "scatter file" for your device. In my case it was included in the ROM zip. There is also a tool to create one called "MTK Droid Tools".
4- open the scatter file, and make sure each image type is assigned to the corresponding image file. In my case the assignment was done automatically as the scatter was included with the ROM zip.
5- Shut down the device (use a needle or pin to reset in case of Ainol Numy 3G AX10)
6-Keep the device disconnected
7-click download on SP Flash tool
8- connect the device. The counters of download start counting and when done (about 5min), a small window with green sign pops up.
9- if download does not start try to fix your drivers. Sometimes you need to uninstall-reinstall drivers. Sometime you need to try from different sources.
10- tell me if this post was helpful
Hi all,
I need your help. Given what I already (unsuccessfully) tried, I'm not sure if there will be a solution, at all...worst case, my Huawei Smartwatch isn't usable anymore,,,
Given that there is a preview version of WEAR Version 2.0 available, I thought it might be good idea to install and test. In fact, given that I manually/successfully installed the WEAR Version 1.4, some months ago, I was sure that I can manage to do it, with the preview version, as well.
I followed the steps, which you can find here developer.android.com/wear/preview/downloads
The point is, after the update has been done (given the message in ADB) the Smartwatch didn't automatically start to reboot. I was waiting about 30- 40 minutes, but nothing happened. So, I rebooted the watch by my own, via the fastboot menu.
But, the watch was only booting up to the Huawei Logo and nothing more did happen. I was also waiting for 30 - 40 minuntes.
After that, I googled and found a way how to access the fastboot mode (long and shore pressing of the power button of the watch) Here I tried the possible options. But, I would say, the only option which worked was "shutdown". All the other option, except fastboot recovery, brought me to the same result, as described above. Finally, I tried fastboot recovery, which might have made the situation even worse...means, after the Huawei Logo I can see a fallen over "android" with a open flap / a sign with a bang plus some text lines. But, it's so fast disappearing, nobody can read...even this is coming up again and again.
Next what I wanted to try is, to flash the WEAR version 1.4 again. But, it seems to be that ADB doesn't find the Huawei device anymore. (command ADB Devices doesn't show me any device)
Meanwhile, even it is somehow not logical (as it was working before with my "Standard Win 10 PC and the drivers installed) I tried 3 different PC with different combinations of Windows Version (7,8, 10), USB Ports (2.0 and 3.0) and probably almost all Android USB Drivers you can find.on the WEB. I even followed a procedure how to modify the INF file with some HUAWEI specific entries. I also let the watch run, overnight, in the loop mode, so the battery got empty..which really didn't help, as once loaded again, the watch started with the "loop procedure" again. However, I tried all the steps I did before, once again.
Regarding ADB/Fastboot, I'm not using the full Android SDK package, but the minimal version, at first version 1.1.3 and the later 1.4.3. I also followed the hints to open a command line with shift and right click "in" the respective ADB folder.
So, as you can read, I already tried a lot of thinks with no luck. in fact, I wasn't able to find anything more when I googled.
Hope you / some Android "guru's" can help me, now.
Here some of my current thoughts to which you have answers/comments.
1. Could it be, that the watch is totally broken and can't be "repaired" anymore?
2. Could it be, even the watch is in the fastboot mode, that the watch really isn't in a "full" one (...because the upgrade procedure of WAER 2.0 somehow failed) and this might be the reason, why ADB can't find the device anymore?
3. If 2. is really the case, is there any way to force a "full" fastboot mode?
4. Do you have any other idea, what can be done to make ADB aware of the device?
5. Is there meanwhile a specific ADB driver for the HUAWEI watch available? / Can somebody send me a link to a driver which is definitely working with that watch.
6.Whatever you can think of.
I really would appreciate any help to get my problem fixed.
Thanks in advance
Claus
TL;DR
When you used flash-all.bat it wipes your userdata partition. That means all settings are back to default. So no developer options, no adb debugging.
You can only use fastboot.
Code:
fastboot devices -l
needs to show your device.
- Then untargz the factory image.
- unzip the *.zip
- print out the flash-all.bat (or open in an editor)
use these commands:
Code:
fastboot flash bootloader bootloader-sturgeon-nvd36i.img
fastboot reboot-bootloader
sleep 5
and now flash each image in sequence (boot, cache, recovery, system, userdata.img
fastboot's 2nd param is like the basename of the corresponding .img file
Hi ranf,
first of all, THANKS A LOT, my watch is alive, again.
FYI, what I did...both ways are working, but as I saw, that you updated the procedure, I did the flash the watch two times. To add, I flashed the WEAR 2.0 Preview version.
1. The normal flash process by using one IMG and the one ZIP file, following the steps in the flash-all.bat.
2. Your updated "version", means the IMG file, plus all IMGs (extract from the ZIP file) plus the steps you have written, above.
I just finnished number 2 and the watch is synchronizing..looks good so far.
Thanks
Claus
Nice.
I have the suspicion that this "sleep 5" (seconds) sometimes is not enough.
I did All the steps, but my watch is stucked in moving circles screen
Acer Predator 8 GT-810 system\etc backup please!
Make a backup folder etc
Do you still need it? I can send it you tomorrow or something like that.
p8tgames said:
Do you still need it? I can send it you tomorrow or something like that.
Click to expand...
Click to collapse
hey man if u able to send me a back up. Will that solve my problem ?
I made mistake to wipe everything in my phone and now i dont have OS ( i cant start my phone) i can only enter TWRP and thats all. i can use pc to transfer files to my phone and then install the files from there , so i wonder if any1 send me back up will that save me ???
i cand find anywhere OS for acer predator gt 810
there is official avolo zip on acers' page. flash that zip and you're safe
Flash archive corrupted
Hi, I downloaded this archive and I want to flash my tablet, but Intel Phone Flash Tool Lite(flasher for x86 devices) say, that archive corrupted. I downloaded firmware 3 time, but its not working.I used TWRP to install firmware, it installed, but i have BootLoop.Please, someone, do Backup of firmware.
dvijetrecine said:
there is official avolo zip on acers' page. flash that zip and you're safe
Click to expand...
Click to collapse
Hi, I downloaded this archive and I want to flash my tablet, but Intel Phone Flash Tool Lite(flasher for x86 devices) say, that archive corrupted. I downloaded firmware 3 time, but its not working.I used TWRP to install firmware, it installed, but i have BootLoop.Please, someone, do Backup of firmware
Alex_merser54 said:
Hi, I downloaded this archive and I want to flash my tablet, but Intel Phone Flash Tool Lite(flasher for x86 devices) say, that archive corrupted. I downloaded firmware 3 time, but its not working.I used TWRP to install firmware, it installed, but i have BootLoop.Please, someone, do Backup of firmware
Click to expand...
Click to collapse
Use fastboot to flash the stock ROM instead of Intel flash tool. (If you know what you're doing, just read the part in blue below.)
fastboot is for Android devices, whether they have Qualcomm or Intel processors. Using Intel Flash tool is more akin to using Qualcomm's QPST for flashing, which is also something that should only be attempted
after trying fastboot. The Intel flash tool expects the .zip file to be in a format such as a Chuwi ROM with Windows is. Intel Flash tool unfortunately doesn't expect the .zip to be in the Android format like Acer's stock
ROM "AV0L0-something.zip" is.
With the tablet off, and plugged into your computer, hold both volume buttons and power it on. (You probably already knew this step, but here just in case )
It will vibrate longer than it usually does when turning on.
The screen should indicate that the device is in download, or "dnx" mode.
Open a command prompt in administrator mode,(the title of the window should say "Administrator: Windows Command Prompt" or "Administrator: <current directory>")
Type:
Code:
fastboot
If command not found, then either copy fastboot.exe into System32, or add the path it is in to your PATH variable, or simply navigate to its directory within the command prompt.
If you're not familiar with the PATH variable, you can just shift+right-click on fastboot.exe, click "Copy Path" and then paste it into the command prompt to use it's full path in place of simply "fastboot".
Once you're able to type "fastboot" or paste the full path and press enter and it returns the fastboot help message, type:
Code:
fastboot devices
this will either return a single line containing your device's serial number, or it will return nothing at all
If you see a serial number, you're in business.
(make sure the tablet is not low on battery before you continue):
Type:
fastboot update <path to ROM .zip>
Click to expand...
Click to collapse
This should initiate a full reflashing of the stock ROM. The tablet will reboot a couple times, you should hear/feel an even longer vibration during the process, do not touch it or unplug it from the computer until it is at the initial Google device setup screen waiting for your input.
Note that this full reflashing will also overwrite TWRP with the stock recovery.
if "fastboot devices" returns nothing at all, and also doesn't say "command not found" then do the following:
open device manager on computer, find the tablet's driver (may be under portable devices, or COM ports. sometimes under USB.)
if you can't find it, look for an "unknown device" with a yellow exclamation mark on it. If you see that, then you may not have had the driver installed in the first place. To verify, unplug the tablet from the computer
and see if the unknown device disappears from device manager.
If you were able to find the tablet in device manager, then right click and "Uninstall Device" and be sure to check the box to uninstall the driver software as well before clicking OK.
Then, unplug the tablet from your computer if you haven't already.
Download the latest driver from the same place on Acer's website that you downloaded the stock ROM from. Install the driver and restart your computer if it says it needs to.
Afterward, ensure the tablet is off and try the steps above again.
biorpg said:
Use fastboot to flash the stock ROM instead of Intel flash tool. (If you know what you're doing, just read the part in blue below.)
fastboot is for Android devices, whether they have Qualcomm or Intel processors. Using Intel Flash tool is more akin to using Qualcomm's QPST for flashing, which is also something that should only be attempted
after trying fastboot. The Intel flash tool expects the .zip file to be in a format such as a Chuwi ROM with Windows is. Intel Flash tool unfortunately doesn't expect the .zip to be in the Android format like Acer's stock
ROM "AV0L0-something.zip" is.
With the tablet off, and plugged into your computer, hold both volume buttons and power it on. (You probably already knew this step, but here just in case )
It will vibrate longer than it usually does when turning on.
The screen should indicate that the device is in download, or "dnx" mode.
Open a command prompt in administrator mode,(the title of the window should say "Administrator: Windows Command Prompt" or "Administrator: <current directory>")
Type:
If command not found, then either copy fastboot.exe into System32, or add the path it is in to your PATH variable, or simply navigate to its directory within the command prompt.
If you're not familiar with the PATH variable, you can just shift+right-click on fastboot.exe, click "Copy Path" and then paste it into the command prompt to use it's full path in place of simply "fastboot".
Once you're able to type "fastboot" or paste the full path and press enter and it returns the fastboot help message, type:
this will either return a single line containing your device's serial number, or it will return nothing at all
If you see a serial number, you're in business.
(make sure the tablet is not low on battery before you continue):
Type:
This should initiate a full reflashing of the stock ROM. The tablet will reboot a couple times, you should hear/feel an even longer vibration during the process, do not touch it or unplug it from the computer until it is at the initial Google device setup screen waiting for your input.
Note that this full reflashing will also overwrite TWRP with the stock recovery.
if "fastboot devices" returns nothing at all, and also doesn't say "command not found" then do the following:
open device manager on computer, find the tablet's driver (may be under portable devices, or COM ports. sometimes under USB.)
if you can't find it, look for an "unknown device" with a yellow exclamation mark on it. If you see that, then you may not have had the driver installed in the first place. To verify, unplug the tablet from the computer
and see if the unknown device disappears from device manager.
If you were able to find the tablet in device manager, then right click and "Uninstall Device" and be sure to check the box to uninstall the driver software as well before clicking OK.
Then, unplug the tablet from your computer if you haven't already.
Download the latest driver from the same place on Acer's website that you downloaded the stock ROM from. Install the driver and restart your computer if it says it needs to.
Afterward, ensure the tablet is off and try the steps above again.
Click to expand...
Click to collapse
Thank you, but I just entered EFI and load android.efi file, also I autorun it and reflash via recovery
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
Hi People,
I hope I am putting this question in the proper location.
I have had several attempts ate flashing a new ROM to my device as it was the Chinese version & kinda useless to me not having Play store or several other APPs I want. I also wanted to try ROOT a phone for the first time.
I managed to get as far as getting ADB & fastboot working & TWRP installed on the device. The first ROM I had put in my file storage was corrupt so I tried the Lineage 17 version which "seemed"to install with a success message, but the phone would only boot into TWRP. so I tried the Havoc ROM from the thread in this site area. Same thing, would only boot into TWRP. Then I thought I would start over & install the factory ROM from: https://xiaomifirmwareupdater.com/miui/olivelite/stable/V12.0.2.0.QCPMIXM/ with ADB & fastboot. I got a success message from the MiFlash tool but the device is now saying the "MIUI verson cannot be installed on this device" in one screen from the Redmi-Recovery 3.0 menu that's now on it.
From here I can Reboot, wipe data or connect with MiAssistant. When I try MiAssistant (PC Suite) the phone does not connect to my PC but I can see the ADB device from device manager and ./adb fastboot devices shows a serial number -but connected as sideload if that makes a difference?
I hope I explained well enough to be understood. Is there anything I can do from here to get it working or is it fully stuffed?
Ur device's bootloader still unlocked?
T0B3R said:
Hi People,
I hope I am putting this question in the proper location.
I have had several attempts ate flashing a new ROM to my device as it was the Chinese version & kinda useless to me not having Play store or several other APPs I want. I also wanted to try ROOT a phone for the first time.
I managed to get as far as getting ADB & fastboot working & TWRP installed on the device. The first ROM I had put in my file storage was corrupt so I tried the Lineage 17 version which "seemed"to install with a success message, but the phone would only boot into TWRP. so I tried the Havoc ROM from the thread in this site area. Same thing, would only boot into TWRP. Then I thought I would start over & install the factory ROM from: https://xiaomifirmwareupdater.com/miui/olivelite/stable/V12.0.2.0.QCPMIXM/ with ADB & fastboot. I got a success message from the MiFlash tool but the device is now saying the "MIUI verson cannot be installed on this device" in one screen from the Redmi-Recovery 3.0 menu that's now on it.
From here I can Reboot, wipe data or connect with MiAssistant. When I try MiAssistant (PC Suite) the phone does not connect to my PC but I can see the ADB device from device manager and ./adb fastboot devices shows a serial number -but connected as sideload if that makes a difference?
I hope I explained well enough to be understood. Is there anything I can do from here to get it working or is it fully stuffed?
Click to expand...
Click to collapse
You should flash China factory rom, if you can.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com