Anyone know of a way to get into recovery mode (botton combo, one-click, etc.) on the 10.1 tab without having android sdk and adb installed on my PC? I am not new at flashing files in recovery mode, but going through help files/instructions on adk is a bit overwhelming.
I have the root zip file on my tab, I just need to get into recovery mode to flash it.
Thanks in advance...
It isn't possible without adb on a non-rooted device. You can attempt to boot into recovery mode by holding power and volume down on start up and selecting the android guy with "downloading" but it will say: "waiting for usb" and hang there. I was attempting to do this the other night.
Getting into recovery is dead simple though once you have adb going. Go to the android development section and go to rooting your tablet. Download the drivers > connect to the computer > run adb in command prompt once you have your sdk installed > then if you have your drivers fully installed and usb debugging mode is on just type in command prompt "adb reboot recovery" and it will send you directly to recovery mode to flash any zip file you please.
Thx, Really wish someone had a one-click option, I guess i'll just have to jump in
I've been trying to boot into recovery for a while now, but with no luck. I installed the full SDK platform, and the Manager app downloaded and installed all the available packages (took forever). The 'push' command seemed to work fine, and when I do "adb reboot recovery" the tablet reboots, but just goes into the battery charging screen. Any idea why this might be happening, and what I can do to get into recovery?
kentoe said:
It isn't possible without adb on a non-rooted device. You can attempt to boot into recovery mode by holding power and volume down on start up and selecting the android guy with "downloading" but it will say: "waiting for usb" and hang there. I was attempting to do this the other night.
Getting into recovery is dead simple though once you have adb going. Go to the android development section and go to rooting your tablet. Download the drivers > connect to the computer > run adb in command prompt once you have your sdk installed > then if you have your drivers fully installed and usb debugging mode is on just type in command prompt "adb reboot recovery" and it will send you directly to recovery mode to flash any zip file you please.
Click to expand...
Click to collapse
The mode that says "downloading" is not recovery mode. Just select the one on the left and you will get into stock recovery mode (unless you already have Clockwork installed).
Itaintrite said:
The mode that says "downloading" is not recovery mode. Just select the one on the left and you will get into stock recovery mode (unless you already have Clockwork installed).
Click to expand...
Click to collapse
I managed to do that, but it wouldn't show anything on my '/sdcard' directory, even when I renamed the root package to "update.zip"
In red, it says "E:unknown volume for path [/sdcard]" Not sure if I'm getting into real, stock recovery, or what - seems crazy that stock wouldn't be able to access its own sdcard directory.
Battery not recovery mode
I am in a similar situation, when I use adb to run recovery mode it sends me to teh battery charging screen. With the exception of that they only other things I can do are to hold power and vol to get option of using Fastboot or ODIN. I do not have any options ever to chose to go into recovery mode. Anyone know why this may be? I am running 3.1 IO version.
Thanks
You will need fastboot and recovery.img to boot into recovery in order to perform a factory reset.
Installing the sdk works best, as drivers needed are acquired from the process! ELse there are extracted contents available on net including just the drivers, adb (and fastboot!)
Check my thread #9
http://forum.xda-developers.com/show....php?t=1136958
bakobitz said:
I managed to do that, but it wouldn't show anything on my '/sdcard' directory, even when I renamed the root package to "update.zip"
In red, it says "E:unknown volume for path [/sdcard]" Not sure if I'm getting into real, stock recovery, or what - seems crazy that stock wouldn't be able to access its own sdcard directory.
Click to expand...
Click to collapse
I don't think the stock retail recovery is capable of flashing off SD storage. That's why the current rooting methods have you first flash either I/O recovery or a custom recovery.
Berner said:
I don't think the stock retail recovery is capable of flashing off SD storage. That's why the current rooting methods have you first flash either I/O recovery or a custom recovery.
Click to expand...
Click to collapse
The manual says to press the power and UP VOL button to get into recovery mode for update flash or wipe data ..
Pressing power and DOWN VOL enters fastboot mode
gunzo71 said:
The manual says to press the power and UP VOL button to get into recovery mode for update flash or wipe data ..
Pressing power and DOWN VOL enters fastboot mode
Click to expand...
Click to collapse
Go ahead and let know if you are able to enter recovery with the keys combination and wipe or factory reset the device, according to manual. Did not work for me, am on 3.1 honeycomb i/o galaxy tab 10.1 and many others.
engljeff said:
Anyone know of a way to get into recovery mode (botton combo, one-click, etc.) on the 10.1 tab without having android sdk and adb installed on my PC? I am not new at flashing files in recovery mode, but going through help files/instructions on adk is a bit overwhelming.
I have the root zip file on my tab, I just need to get into recovery mode to flash it.
Thanks in advance...
Click to expand...
Click to collapse
Use the quick boot app. Works well for me. Supports power off, recovery, and normal reboot for the free version. Oh yeah but that requires root.
Sent from my GT-P7510 using Tapatalk
mughalgxt said:
Go ahead and let know if you are able to enter recovery with the keys combination and wipe or factory reset the device, according to manual. Did not work for me, am on 3.1 honeycomb i/o galaxy tab 10.1 and many others.
Click to expand...
Click to collapse
yes it did.. thats why I said try that ..
On 3.1 IO too .. though I broke it within 3 weeks
gunzo71 said:
The manual says to press the power and UP VOL button to get into recovery mode for update flash or wipe data ..
Pressing power and DOWN VOL enters fastboot mode
Click to expand...
Click to collapse
This worked for me on Rogers 4G version
I rooted my Galaxy Pocket lately and installed LCD modder just to try changing the dpi settings. i changed the stock 120 dpi to 160 and clicked save. the phone froze and i had to pull of the battery. after i restart all i get is a boot loop. i get 3 things (1) s5300 logo (2) animated samsung logo (3) flashing samsung logo which appears just before the lock screen appears ( 1 and 2 vibrations during this) and then it loops all over again. as i understand the change i dpi is not supported for my device and it is not loading into the home screen. the solution seems to be editing the build.prop file to reassign the stock dpi value. but to access the file i have to get into adb mode and have the device available in the list. but since debugging mode was not selected before i essentially soft bricked my phone i am not able to access my device in adb mode. i am able to get into recovery mode tho.any way to edit the build.prop file from this situation?? help is much appreciated.....i am travelling now and my phone is unusable......thanks a ton..
If you can get to download mode, than you can reflash to stock rom again..
Sent from my GT-S5300 using Tapatalk 2
thanks for the idea..i am able to get into download mode....im sure i can reflash my phone with a new firmware to get it up and going....but i would loose all my contacts and data on the phone, which unfortunately i hadnt backed up since i wasnt expecting this situation to arise. (my badd!!!!). as far as i know the only thing that prevents my phone from booting up properly is the "LCD density property line" in build.prop. Is there anyway i can just edit it back to my stock setting (dpi 120). ????
I had come across the term CWM which is said to be an alternative recovery option. does it mean i can get into CWM recovery mode from switched off state with button combos just like i get into android stock recovery menu??? and if dats possible, can i apply an update.zip from my memory card that would change this dpi setting in the build.prop some how?? how can i get clockworkmod into my system without flashing the firmware and erasing the data (without flashing)??? thanks......
or can i just change/flash the bootloader (which i understand contains all the system files necessary to bootup the phone) using ODIN flash. if so...can i get the stock bootloader from an s5300 user like u?? I know flashing would be the easiest option now..but i just want to go to all extremes to just keep my data if possible in anyway. if there is anyway to have ADB working without debugging mode on or any way to activate debugging mode from the recovery menu or download menu?
help much appreciated
Well, in s5300 we use cwm that had aroma file manager that can run in recovery mode.like file explorer.that might solve you problem to edit build prop.
Sent from my GT-S5300 using Tapatalk 2
bayustev said:
Well, in s5300 we use cwm that had aroma file manager that can run in recovery mode.like file explorer.that might solve you problem to edit build prop.
Sent from my GT-S5300 using Tapatalk 2
Click to expand...
Click to collapse
thanks for the insight...Could you just give me a small"how-to" on this idea???
how do i install cwm with aroma file manager?? all the videos i saw on youtube shows the installation after its being copied into internal storage when the phone is on and then getting into recovery mode to install it, so hw do i get it into phone memory or may be into SD card if there is a way to mount it in recovery mode
appreciate your speedy reply man...
Cwm vM00v3f. Flash with odin (if you don't had custom recovery mode). Than v00kernelv1.10. Then get into recovery mode. In there you see aroma manager inside recovery mode. Click it .there you can explore file folder on your device.search the file you want to edit..for cf root link you type in search box ..
send from p1010 kmicic rom tapatalk 2
galaxy pocket lcd density problem
I have the same problem but I have open usb debug
jkanth7 said:
thanks for the idea..i am able to get into download mode....im sure i can reflash my phone with a new firmware to get it up and going....but i would loose all my contacts and data on the phone, which unfortunately i hadnt backed up since i wasnt expecting this situation to arise. (my badd!!!!). as far as i know the only thing that prevents my phone from booting up properly is the "LCD density property line" in build.prop. Is there anyway i can just edit it back to my stock setting (dpi 120). ????
I had come across the term CWM which is said to be an alternative recovery option. does it mean i can get into CWM recovery mode from switched off state with button combos just like i get into android stock recovery menu??? and if dats possible, can i apply an update.zip from my memory card that would change this dpi setting in the build.prop some how?? how can i get clockworkmod into my system without flashing the firmware and erasing the data (without flashing)??? thanks......
or can i just change/flash the bootloader (which i understand contains all the system files necessary to bootup the phone) using ODIN flash. if so...can i get the stock bootloader from an s5300 user like u?? I know flashing would be the easiest option now..but i just want to go to all extremes to just keep my data if possible in anyway. if there is anyway to have ADB working without debugging mode on or any way to activate debugging mode from the recovery menu or download menu?
help much appreciated
Click to expand...
Click to collapse
flash Phil touch or Cwm through download mode and then you can use adb tools. Open up cmd cd /d C:\where you saved your SDK (mini-sdk is quick to download just search mini-sdk on Google and click the first one) now adb pull /system/build.prop it should be where your sdk is, then edit with notepad ++. Once you've done this do adb push build.prop /system. You can flash recovery without wiping any data.
As the title says i have broken my phones screen and i am unable to see anything on the screen, though it still works. i have downloaded a program called "Ultimate Touchscreen Control for Android" that allows me to make an emulator of the phone and i can access setting etc. i wish to use the htc transfer tool on my phone to get the data off of it, but the program needs adb debugging to have been enabled but it wasn't, i have heard there is a kernel to change this but i am unable to access my phone via usb due to the fact it was set on internet pass through when i plug it in my usb port. Is there some way i am able to turn on adb debugging?
Icomic said:
As the title says i have broken my phones screen and i am unable to see anything on the screen, though it still works. i have downloaded a program called "Ultimate Touchscreen Control for Android" that allows me to make an emulator of the phone and i can access setting etc. i wish to use the htc transfer tool on my phone to get the data off of it, but the program needs adb debugging to have been enabled but it wasn't, i have heard there is a kernel to change this but i am unable to access my phone via usb due to the fact it was set on internet pass through when i plug it in my usb port. Is there some way i am able to turn on adb debugging?
Click to expand...
Click to collapse
You can enable debugging from developer options.
Hit thanks if I helped.
Vineet Upadhyaya said:
You can enable debugging from developer options.
Hit thanks if I helped.
Click to expand...
Click to collapse
He said he couldn't see anything on the screen... Can't you read a bit instead of spamming all the threads on this forum?
Oh, I forgot... "Hit thanks if helped"
Delta-flasher said:
He said he couldn't see anything on the screen... Can't you read a bit instead of spamming all the threads on this forum?
Oh, I forgot... "Hit thanks if helped"
Click to expand...
Click to collapse
My bad
@Icomic there are many ways to enable adb without touchscreen, though the simplest way is to flash a modded kernel with adb debugging enabled by default.
To flash a custom kernel you need to download one from Original Dev section, go into fastboot mode and type:
fastboot flash boot kernel_downloaded.img
All custom kernels for desire x should have adb enabled so flash one you like.
If you don't want to replace your stock kernel with a custom one you can just boot it with:
fastboot boot kernel_downloaded.img
..and it will boot your phone with the custom kernel, you can do whatever you want until you reboot normally and then you will have back your stock kernel.
xpirt
xpirt said:
@Icomic there are many ways to enable adb without touchscreen, though the simplest way is to flash a modded kernel with adb debugging enabled by default.
To flash a custom kernel you need to download one from Original Dev section, go into fastboot mode and type:
fastboot flash boot kernel_downloaded.img
All custom kernels for desire x should have adb enabled so flash one you like.
If you don't want to replace your stock kernel with a custom one you can just boot it with:
fastboot boot kernel_downloaded.img
..and it will boot your phone with the custom kernel, you can do whatever you want until you reboot normally and then you will have back your stock kernel.
xpirt
Click to expand...
Click to collapse
Thanks for that it worked great
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