Sup guys, im really desesperate, today i rooted mi motorola xt316 spice key, so i deleted some apps for a better performance, but now the screen is black, i can view the notificaction bar and the lock screen but its all, what can i do? i searched for one rom and i found nothing, do u guys have a rom or something? ohh and i already do a hard reset.. still the same, please help
What apps had you deleted?
Sent from my Nexus S using xda premium
well i dont remember exactly, but i deleted ones of motorola, u know the widget time, and others. i dont remeber exacly, damn:s
Black screen.. I think you have deleted the launcher
Sent from my Nexus S using xda premium
any suggestion?:S
Is your phone set up with an android market account? I've actually had this problem before and what you do is just install a launcher from the android market and it automatically installs on your phone and it should work perfectly. I still recommend you should reinstall the apps you lost because if you factory reset your phone it will be just as you described. hope it helps!
No , i cant login in with my account, i reset the phone with the factory reset, and when i turn it on, i cant connect with the google servers.
Have someone text you a link to the apk of a launcher, when you get the notification click the download link and when it finished downloading select the download from the notification bar. It'll prompt you to install. If you don't have unknown sources checked then it'll ask you to turn that option on. Once you have a launcher installed then your phone will function properly (depending on what you removed) until you can get the stock rom flashed.
Our you can go straight to the flashing part. Find a rom - stock if you'd like - and flash it. There should be some kind of stock flasher available if there aren't any roms, like an RUU or something... I think RUUs are only for HTC devices, but there should be something similar for your device.
If your phone has a subforum here on XDA, check there for stock or custom roms.
Supersonic Evo 4G | MIUI | Tapatalk
thanks for the response, i have a question; the launcher can be installed via adb?, im gonna try your solution first.
Well I tried the message metod and I apparently delete the default browser, so I tried to install pro launcher via adb but the cmd command says offline device, i think is because the usb debugging is off?, i cant activate it because the screen is black:S
Just flash your rom via Odin. It safer and easy
Odin? what is that? its compatible with the motolola spice key xt316? thanks for the response.
The problem is i cant put my phone in usb debugging because the screen is black, is there another method?
boot ur phone in recovery mode,
this does not need usb-debugging to be On,
and u can use adb...
worth to try
thanks dude im gonna try now.
I put my phone in recovery mode, and i plug the phone to my pc,but when i type adb devices, it doesnt appear.
in the recovery mode there is this options:
reboot system now
apply update from sd card
wipe data/factory reset
wipe cache
download nb0 from sd card
when i tried to install using the adb install comand it says error: device not found
henry225 said:
I put my phone in recovery mode, and i plug the phone to my pc,but when i type adb devices, it doesnt appear.
in the recovery mode there is this options:
reboot system now
apply update from sd card
wipe data/factory reset
wipe cache
download nb0 from sd card
when i tried to install using the adb install comand it says error: device not found
Click to expand...
Click to collapse
ya i think i know why
its the USB drivers for hboot
u need to install drivers for the phone (hboot drivers)
so the machine recognize the phone when plugged
--- or ---
u can get the apk and pack it as an update.zip file (google this to find out how)
then use the option (apply update from sd card)
i think this will install the apk
stinger1 said:
ya i think i know why
its the USB drivers for hboot
u need to install drivers for the phone (hboot drivers)
so the machine recognize the phone when plugged
--- or ---
u can get the apk and pack it as an update.zip file (google this to find out how)
then use the option (apply update from sd card)
i think this will install the apk
Click to expand...
Click to collapse
When i plug my phone on normal mode the comand adb devices recognize the phone but it say offline, but when i plug the phone on recovery mode dont. There is drivers for the recovery mode?, sorrty ima huge noob.
Ok i gogole it and i found a video,http://www.youtube.com/watch?v=FXDszE0Ytn8, but my question is the hboot drivers are the same for all androids? or i need find for my spce xt316.
henry225 said:
Ok i gogole it and i found a video,http://www.youtube.com/watch?v=FXDszE0Ytn8, but my question is the hboot drivers are the same for all androids? or i need find for my spce xt316.
Click to expand...
Click to collapse
i think there is some kind of types/drivers
not 100% related to manufacturer
i mean a driver may work even if its for another manufacturer
anyways try the drivers in ur hand (if u have any)
or try to find "google usb drivers" online somewhere
if failed...
check this list and try to get the proper drivers
http://developer.android.com/sdk/oem-usb.html
Hello,
I have a Allview Speed City tablet, and after i installed root on it, i changed the dpi using an app..
(root thanks to mad_ady, root availible at http://forum.xda-developers.com/showthread.php?p=40740061#post40740061 )
After this, the tablet is stuck in a boot loop.
I tried to do a factory reset from recovery mode, but this didn't solved the problem.
(the tablet has only 2 buttons, power and home. The recovery can be accessed pressing and holding both buttons until the recovery boot).
I located the file where the dpi is changing, /system/build.prop , and tried to flash another file from Onda 701 ROM (a very similar tablet). I didn't managed to find the original file. Anyway, the flashing didn't succeeded, "instalation aborted" appeared on the screen.
I found on some forum a flashable zip with build.prop from another device, and i replaced the build.prop file with the one from Onda ROM, signed it with a tiny program and still fails.
What options do i have to replace/edit the build.prop file? Before bricking, the ADB was not turned on on the tablet, and i read that i cannot use the SDK (anyway don't know how to use it). I contacted Allview and they don't want to give me the ROM from the tablet. And so, i call anybody that can give me a backed up rom from the tablet, anyone who have the knowledge about AD ROMS and are willing to help me..
Thanks folks!
I installed ADB on my pc and tried to pull the build.system file from /system on tablet, but i get error:closed.. I tried to run this command with tablet in recovery/ apply update from ADB.. Why do i get this error? the device cannot recieve other commands than adb sideload?
Thanks..
this worked for me for full reset
crististan said:
I installed ADB on my pc and tried to pull the build.system file from /system on tablet, but i get error:closed.. I tried to run this command with tablet in recovery/ apply update from ADB.. Why do i get this error? the device cannot recieve other commands than adb sideload?
Thanks..
Click to expand...
Click to collapse
this has been done with the allview speed city
I had a simular problem...
here my solution, hold on and home button at the same time until the screen gets back
wait until you get the boot screen...
use both, 1. erase card and 2. media options...
then to be save I choosed the other option say something like for factory reset.
the I used the apply update from ADB...
the tablet shows the same screen for 5 or 6 minutes
after it booted normaly, but I still had some problems
and I used a needle for a reset...
after that the tablet worked fine
the only thing what I dont understand is why its still root
Thank you for this tutorial, but i solved my problem with warranty. Even so, i erased all cache, factory reset from recovery but still i had no access to system files, and factory reset didn't changed the build.prop (system settings) to defaults.
It's normal. build.prop is part of /system (and the su binary is installed under /system as well), and any changes you make to /system files are permanent until you flash a different firmware.
Hi,
I'm trying to take control of my galaxy s3 which has a broken screen. I saw a windows tool for it, but I need ADB enabled, which was not enabled on this one. So I'm trying to go in recovery mode and follow some instructions I've seen to enable adb. Sadly, it looks like my home button is also broken (I can't go in recovery mode, or the problem maybe that adb.exe does not list it at all). So few questions :
1) When a pure new stock galaxy s3, when the first screen appears after booting up, does the home button triggers some vibrations? (If no, I'll be sure it's broken)
2) Is there any way to directly flash my S3 with a custom firmware that have adb enabled by default in its properties, without going through recovery mode?
Thanks in advance!
noxew said:
Hi,
I'm trying to take control of my galaxy s3 which has a broken screen. I saw a windows tool for it, but I need ADB enabled, which was not enabled on this one. So I'm trying to go in recovery mode and follow some instructions I've seen to enable adb. Sadly, it looks like my home button is also broken (I can't go in recovery mode, or the problem maybe that adb.exe does not list it at all). So few questions :
1) When a pure new stock galaxy s3, when the first screen appears after booting up, does the home button triggers some vibrations? (If no, I'll be sure it's broken)
2) Is there any way to directly flash my S3 with a custom firmware that have adb enabled by default in its properties, without going through recovery mode?
Thanks in advance!
Click to expand...
Click to collapse
Yes. Theoretically You can flash a custom firmware with odin or heimdall in download mode. Make sure your new rom has enabled adb and debugging and then you can use "adb reboot recovery" and add or remove packages.
BUT, unless you can cook you own room with that enabled, i dont think you will find a room adb and debug enabled by default.
Alternative:
Flash the param zone. After it flashes it will boot into recovery mode. Or try flashing CSC file (just the cache is enough) which does the same.
Edit:
I assumed u know how to go into download (fastboot) mode even though u cant boot into recovery mode. For fastboot is easier, u can google for many tricks. From there u use odin to use Alternative above.
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