I try to root my phone, it was frozen on 3% and i unplug the usb cable.
Now, when i try to turn it on i had this message:" error boot certification verify" then goes to black screen.
I can´t enter in download mode or recovery mode.
What can i do to fix it?
Everything is frozen?
What have you done, flashed an img or something else?
I flash a .kdz file with lg flash tool. I was trying to update to lollipop. But the installation stop and then i remove the usb cable.
Now i have the black screen after "error boot certification verify".
What can i do?
not exactly for your problem but still try this
forum.xda-developers.com/g2-mini/general/guide-unbrick-bricked-wrong-aboot-img-t3128896
luismiranda22 said:
I flash a .kdz file with lg flash tool. I was trying to update to lollipop. But the installation stop and then i remove the usb cable.
Now i have the black screen after "error boot certification verify".
What can i do?
Click to expand...
Click to collapse
Same for me...
Now I have only fastboot mode, but no respond any fastboot command (Failed: no respond command).
I tryed many, but no success: no download mode, only fastboot :crying:
papzi57 said:
Same for me...
Now I have only fastboot mode, but no respond any fastboot command (Failed: no respond command).
I tryed many, but no success: no download mode, only fastboot :crying:
Click to expand...
Click to collapse
Weird... When i had this problem I could go into download mode and it was fixed
My lesson:
Don't **** with your phone again i did it too, I NEVER do it again
i have all this problems: http://forum.xda-developers.com/showthread.php?t=2582142
but i can find this files for my phone:
1- sbl1.img
2- aboot.img
3- rpm.img
4- tz.img
5- openrecovery-twrp-2.6.3.2-g2d802
Anyone knows where i can donwload this files?
luismiranda22 said:
i have all this problems: http://forum.xda-developers.com/showthread.php?t=2582142
but i can find this files for my phone:
1- sbl1.img
2- aboot.img
3- rpm.img
4- tz.img
5- openrecovery-twrp-2.6.3.2-g2d802
Anyone knows where i can donwload this files?
Click to expand...
Click to collapse
you can extract those files from kdz
sergioslk said:
you can extract those files from kdz
Click to expand...
Click to collapse
did i loose the warranty by canceled the instalation of lollipop?
It was the official version of lollipop.
Yes,you've lost warranty.
Every bloody page on the net says,that root and custom roms cancel your warranty.
Better have thought before messing up.
I'm a phone tech,but before I was qualified for that,I used to read many pages over XDA and the Israeli site for Android phones.
There's a saying here,you better shave on some else's beard.
So,no offence,but now you're shaved,but butt naked.......
Try the help of the guys here.
Just for your knowledge:
You DO NOT study how to root and jailbreak phones on your phone tech studies,because on 90% of the cases,you do not need to do so.
We are past the days of Cydia,black market and custom features that require root.
I basically raped my Galaxy S2 with root and rom changes,never bricked it,but got normal results only when working with the official Stock Rom.
On my G2 mini,I don't even bother to root,and have flashed a stock rom manually through LG Flash Tool 2014.
Even if the flash went wrong,I could have tried flashing another rom,or send it for maintenance,because it was an official flash,and could have claimed it happened with PC Suite,which happnes to do so on many occasions .
I think I've made my point.
Happy post digging,my frined.
Peace!
Related
Hi all!!
Yesterday i tried to install android 4.4 but the procces didnt succeed, it stuck at. LG boot logo. So i decided to restore my backup in ckockworkmod,it started the process then stopped at the phase "restoring /system" . I waited about a half hour, and because it didnt take the much time before, i took out the battery. I read somewhere that formatting the system partition in cwm could help, so i did that. Then i retried restoring my backup. It stuck at the same phase. Later i downloaded the official kdz, and decided to flash it. I could bring the phone in update mode, but the process stopped at 15% at lg update manager.
At the moment i can get into clockworkmod, but cant restore /system . The update mode is also okay. I dont know that fastboot works or not. I havent tried it yet. Please help me thanks in advance
@trapistasajt
You will need to get fastboot working and use lelus's fastboot script to flash the "u" and "x" loaders for the device and then perform the offline or online flash
http://forum.xda-developers.com/showthread.php?t=2292828
Also as you found out you cannot flash custom roms without ulocking the bootloader first and you cannot use the L9 CWM bootstrap recovery for Locked Bootloaders, too flash custom roms.
try this online flash methode with B2CAppSetup
http://forum.xda-developers.com/showthread.php?t=2085344
i had the same probleme and i fixed it .
My bootloader is unlocked. I tried the fast boot method, but it doesnt go further than "Waiting for omap...." . So, i couldnt go into fastboot (probably my fault). Yesterday i sent it to the service. If they notice that my varranty is void (because of the unlocked bl) and send it back, i will try it once more. I would be very thankful if someone could write a noob friendly-fastboot guide. As i read, lots of people are struggling with the same problem. Thanks in advance!!!
You have to use LGMobile Support Tool (Install drivers from it first) Then enter in download mode conecting the phone to pc pressing vol+ and the rest its automatic.
jufece said:
You have to use LGMobile Support Tool (Install drivers from it first) Then enter in download mode conecting the phone to pc pressing vol+ and the rest its automatic.
Click to expand...
Click to collapse
I installed the drivers but it didnt work
trapistasajt said:
I installed the drivers but it didnt work
Click to expand...
Click to collapse
what happened??
jufece said:
what happened??
Click to expand...
Click to collapse
It didnt go further than searching for "omap device", so i couldnt load fast boot, as i said. my phone is still in the service
If they 'll send it back to me, because of unlocked bootloader, i wil try it once more. Any suggestions?
trapistasajt said:
It didnt go further than searching for "omap device", so i couldnt load fast boot, as i said. my phone is still in the service
If they 'll send it back to me, because of unlocked bootloader, i wil try it once more. Any suggestions?
Click to expand...
Click to collapse
I dont know about fastboot.
LG Mobile support tool let you download the correct drivers. Then connect your phone while u keep pressing vol+ and it enters in SW Upgrade mode. Then just click "additional features" and "upgrade error recovery"
jufece said:
I dont know about fastboot.
LG Mobile support tool let you download the correct drivers. Then connect your phone while u keep pressing vol+ and it enters in SW Upgrade mode. Then just click "additional features" and "upgrade error recovery"
Click to expand...
Click to collapse
Thanks! What should i do after that? Or it will automatically flash v20h on my phone?
trapistasajt said:
Thanks! What should i do after that? Or it will automatically flash v20h on my phone?
Click to expand...
Click to collapse
It shows something about firmware ir will restore. Ir will flash the latestbfirmware from original carrier release.
For example i actuallybhave v20L but my original carrier only released v10a. It will restore to v10a
None of them works, other ideas?
This fastboot method worked for me in 5 min, pay close attention to the instructions and it works!
http://androidforums.com/optimus-l9-all-things-root/807569-guide-security-error-fix.html
Spent days with LG update tool which if you read the log has no url for files to download.
Good luck!
I got my phone back from the service. They didnt repair it, because my varranty is void. I tried the methods mentioned above.
First, I tried flashing kdz, (with the solution for post-jb problem), but i couldn't get into S/W mode, which was available before the service.
Second, since i couldn't load S/W mode, the LG upgrader wasn't successfull, too
Third, fastboot still not work.
I am sure, that im not the only person with this problem, since it happened during installing @artas182x 's JB 4.4 rom. Please @artas182x or somebody write a noob-friendly guide/suggestion which may help to unbrick my beloved phone. Thanks!!!!!
Hello,
today i tried to root my phone who runs on kitkat 44.2 and i v'e made a big mistake
i wanted to make my phone look like the g3
now its rooted but while it got in recovery i didnt know how to select the options so what i did was
i took my battery out and now i tried to get it on again and it won't
it doensn't want to get in recovery nothing
when i connect it with my phone it shows that its connected
i don't know what to do can someone help me pleasss i want it back like the beginning without the root pleas (((((
Sorry @Teamsvg,
but with this description no one can help you.
Please explain what you did.
How did you root?
What did you do to make it G3 like?
Did you flash anything?
I can not believe it bricked because of pulling the battery while in recovery, because I did the same when my phone was all stock and nothing wrong happened.
You may try: http://forum.xda-developers.com/showthread.php?p=54325341
Regards,
Zaaap
hi
Zaaap72 said:
Sorry @Teamsvg,
but with this description no one can help you.
Please explain what you did.
How did you root?
What did you do to make it G3 like?
Did you flash anything?
I can not believe it bricked because of pulling the battery while in recovery, because I did the same when my phone was all stock and nothing wrong happened.
You may try: http://forum.xda-developers.com/showthread.php?p=54325341
Regards,
Zaaap
Click to expand...
Click to collapse
hi, thnks for replying
this is what i tried
https://www.youtube.com/watch?v=KINp9v_GN3o
i didn't enable usb debugging ...
zaap
Zaaap72 said:
Sorry @Teamsvg,
but with this description no one can help you.
Please explain what you did.
How did you root?
What did you do to make it G3 like?
Did you flash anything?
I can not believe it bricked because of pulling the battery while in recovery, because I did the same when my phone was all stock and nothing wrong happened.
You may try: http://forum.xda-developers.com/showthread.php?p=54325341
Regards,
Zaaap
Click to expand...
Click to collapse
My phone is like this: you the screen is black, i forgot to enable usb debugging because i tried to root it in my phone so i ddin't need my computer, i can't get in download mode or recovery nothing ! i tried the buttns( and no my buttons works fine) how can i fix this? the link you've send me ask me to put my phone in download mode : "if your device is bricked and can't boot you'll have to enter the Download Mode, to do that just keep holding the Vol. Up button while inserting the USB cable in the phone( The USB cable must be already plugged into the PC while doing that), and you keep it until you go into the Download Mode."
but it can't ...
Teamsvg said:
My phone is like this: you the screen is black, i forgot to enable usb debugging because i tried to root it in my phone so i ddin't need my computer, i can't get in download mode or recovery nothing ! i tried the buttns( and no my buttons works fine) how can i fix this? the link you've send me ask me to put my phone in download mode : "if your device is bricked and can't boot you'll have to enter the Download Mode, to do that just keep holding the Vol. Up button while inserting the USB cable in the phone( The USB cable must be already plugged into the PC while doing that), and you keep it until you go into the Download Mode."
but it can't ...
Click to expand...
Click to collapse
autoirec is onyl for g2.. not mini. becouse we have locked bootloaders custom recoverys doesnt work. something similiar happened to my phone. i can tell you by confedens that first of all it doesnt sound that you are familiar with custom recoverys and stuff and that you have hard bricked your phone. i had to send mine in after 2 days of trying to make it start again. it is broken. and if you take it to service i wouldnt tell them what you did or that you rooted it.
Try this. If you phone is detected under sdb or sdc you have a chance to unbrick your phone.
I attached the files needed to unbrick G2 mini:
sbl1.img
aboot.img
rpm.img
tz.img
recovery.img - download from here.
Be very careful. The order of partitions for our phone is different from the LG G2. So then you use "gdisk -l /dev/sdb" command, find the partitions numbers of each file attached, and use that number in dd command.
I do not know why on tutorial for G2 there is a warning not to flash original recovery.img on recovery partition. So my advice is to flash all partition except recovery.img and see if your phone enter download mode. If not, flash recovery.img, you have nothing to lose.
If the phone enter download mode flash kdz.
powermetza said:
Try this. If you phone is detected under sdb or sdc you have a chance to unbrick your phone.
I attached the files needed to unbrick G2 mini:
sbl1.img
aboot.img
rpm.img
tz.img
recovery.img - download from here.
Be very careful. The order of partitions for our phone is different from the LG G2. So then you use "gdisk -l /dev/sdb" command, find the partitions numbers of each file attached, and use that number in dd command.
I do not know why on tutorial for G2 there is a warning not to flash original recovery.img on recovery partition. So my advice is to flash all partition except recovery.img and see if your phone enter download mode. If not, flash recovery.img, you have nothing to lose.
If the phone enter download mode flash kdz.
Click to expand...
Click to collapse
Can i use this files on G2 Mini D618?
Thanks!
No you can´t.
Sent from my LG-D620 using XDA Free mobile app
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,
I have a lg G5 H850 stuck into "fastboot for bootloader unlock" mode and recovery or download mode are not working, I tried to recover it by unlocking the bootloader but the OEM unlock option is disabled so I cannot flash anything.(device locked error error message)
I saw a YouTube video yout ube.com/watch?v=ImJ1xXXzV6s with my exact issue but he is not responding to my messages.
Is there any option to unbrick this device?
Thanks a lot in advance to all!
yoanc244 said:
Hi,
I have a lg G5 H850 stuck into "fastboot for bootloader unlock" mode and recovery or download mode are not working, I tried to recover it by unlocking the bootloader but the OEM unlock option is disabled so I cannot flash anything.(device locked error error message)
I saw a YouTube video yout ube.com/watch?v=ImJ1xXXzV6s with my exact issue but he is not responding to my messages.
Is there any option to unbrick this device?
Thanks a lot in advance to all!
Click to expand...
Click to collapse
Same here
happened after using the wrong dd command to get rid of the boot loop
boot loop still there, but phone bricked lol
https://forum.xda-developers.com/showpost.php?p=77833566&postcount=21
Hi guys,
it's been more than two hours that I seek the solution to this same problem with next to me the LG G5 bootllop.
All other solutions give nothing:
- unlook via fastboot makes a mistake because the debugging option is not enabled
- the download mode does not remain more than 15 seconds
Guys, have you found a way out of this problem?
MathFR34 said:
Hi guys,
it's been more than two hours that I seek the solution to this same problem with next to me the LG G5 bootllop.
All other solutions give nothing:
- unlook via fastboot makes a mistake because the debugging option is not enabled
- the download mode does not remain more than 15 seconds
Guys, have you found a way out of this problem?
Click to expand...
Click to collapse
You can try getting the .kdz for your phone (e.g. off lg-firmwares.com), use the WindowsLGFirmwareExtract tool to extract the .dz out of the .kdz, then use the tool to extract the laf_6.bin out of the .dz. You can then flash this in fastboot mode using a command like
Code:
fastboot flash laf laf_6.bin
Make sure to use the same .kdz as your running firmware.
I had the same problem with Download Mode as you (restarted after 15 seconds). I extracted laf_6.bin from the H85030e KDZ firmware (whose boot stack was in use), and flashed its LAF (i.e. Download Mode) volume over the laf partition. After this Download Mode stopped restarting after 15 seconds, and I was able to use LGUP (and you would be able to use UPPERCUT) to flash the full KDZ.
(I proceeded to start the phone in bootloader/fastboot mode and flash TWRP recovery as well, with my unlocked bootloader.)
obs3rv said:
You can try getting the .kdz for your phone (e.g. off lg-firmwares.com), use the WindowsLGFirmwareExtract tool to extract the .dz out of the .kdz, then use the tool to extract the laf_6.bin out of the .dz. You can then flash this in fastboot mode using a command like
Code:
fastboot flash laf laf_6.bin
Make sure to use the same .kdz as your running firmware.
I had the same problem with Download Mode as you (restarted after 15 seconds). I extracted laf_6.bin from the H85030e KDZ firmware (whose boot stack was in use), and flashed its LAF (i.e. Download Mode) volume over the laf partition. After this Download Mode stopped restarting after 15 seconds, and I was able to use LGUP (and you would be able to use UPPERCUT) to flash the full KDZ.
(I proceeded to start the phone in bootloader/fastboot mode and flash TWRP recovery as well, with my unlocked bootloader.)
Click to expand...
Click to collapse
interesting. I am in Bootloop from two weeks. Tried to much time lineage 17.1 and then leave the phone so many hours in order to boot in lineage that at some point it won't enter system anymore.
So I passed to LGUP that works only with UPPERCUT and only with UPGRADE functions even if I installed all the drivers.
Maybe I need a "megalock.dll" file?
But the way one week trying to boot in system after flashing KDZ files with UPPERCUT and after many and many bootloop I finally enter the system with H85020a_00_OPEN_EU_OP_1030.kdz
But after one reboot it returns the problem.
I am desperate.
Have you got a phone name to buy that is unbrickable?
Hello guys!
I've been looking for a solution to this problem, I have a Moto One XT1941-5 that was never rooted nor bootloader unlocked. I left it charging and after about one hour it was at Fastboot Mode, it says that it failed booting from normal mode. Even if I try to restart or start normally, it gets back to Fastboot.
What have I done until now?
- Tried to flash the whole latest STOCK ROM again (manually with fastboot tools)
- Tried with a ROM from another region (mine is OPENMX and tried with RETLA) and I get the same
- Tried with Repair Assistant from Motorola, nothing happens.
- Tried to unlock bootloader, it asks me to enable OEM unlock on Developer settings (I can't, phone doesn't power up)
* Something that gets me confused is about the slots, $fastboot getvar all reports that none of the slots are bootable, every time I flash the ROM it says that slot A is bootable and B not, or that A is not bootable and B yes, or none of the slots are bootable.
Here are some screenshots about the info I have.
You can follow these steps from https://forum.xda-developers.com/motorola-one/how-to/unroot-ota-wipe-data-tested-t3905745 and then fastboot erase userdata and try to boot again.
lucasdeeiroz said:
You can follow these steps from https://forum.xda-developers.com/motorola-one/how-to/unroot-ota-wipe-data-tested-t3905745 and then fastboot erase userdata and try to boot again.
Click to expand...
Click to collapse
Just unzipped the bat, and opened with a text editor... those are exactly the commands I manually used, nothing has worked until now.
adri_sefp said:
Just unzipped the bat, and opened with a text editor... those are exactly the commands I manually used, nothing has worked until now.
Click to expand...
Click to collapse
When did you buy this phone?
borksek said:
When did you buy this phone?
Click to expand...
Click to collapse
On June 2018, warranty is not valid any longer. Carrier just give us 1 year here in Mexico.
I never had a problem like this, I was looking forward to find the blankflash for this model but it doesn't exist yet, maybe all I can do is wait for it or hard brick it. :crying:
adri_sefp said:
On June 2018, warranty is not valid any longer. Carrier just give us 1 year here in Mexico.
I never had a problem like this, I was looking forward to find the blankflash for this model but it doesn't exist yet, maybe all I can do is wait for it or hard brick it. :crying:
Click to expand...
Click to collapse
did you manage to solve this problem?
claudiusuflea said:
did you manage to solve this problem?
Click to expand...
Click to collapse
No, I think this problem has to do with the EMMC memory.
Yesterday I was trying again with the Android 10 stock rom using fastboot, nothing changes.
adri_sefp said:
No, I think this problem has to do with the EMMC memory.
Yesterday I was trying again with the Android 10 stock rom using fastboot, nothing changes.
Click to expand...
Click to collapse
that means there's no work-arround
adri_sefp said:
No, I think this problem has to do with the EMMC memory.
Yesterday I was trying again with the Android 10 stock rom using fastboot, nothing changes.
Click to expand...
Click to collapse
also, anyone having an ideea how to hard brick it to qualcomm 908/906 if it's fastboot bricked to blank flash it?
claudiusuflea said:
also, anyone having an ideea how to hard brick it to qualcomm 908/906 if it's fastboot bricked to blank flash it?
Click to expand...
Click to collapse
Even if you do that, there's no blankflash for this model... as long as I know, I was looking forward to find it somewhere but there is none available.
claudiusuflea said:
that means there's no work-arround
Click to expand...
Click to collapse
That's correct, now my device shows nothing on screen, it is just black but when I plug the usb cable, fastboot detects it as fastboot mode, all commands are working but nothing else works.
I'm giving up now.
claudiusuflea said:
also, anyone having an ideea how to hard brick it to qualcomm 908/906 if it's fastboot bricked to blank flash it?
Click to expand...
Click to collapse
UPDATE:
- I finally found a blankflash (my phone still the same) but you can give it a try.
LINK (copy and paste om your browser) drive.google.com/file/d/1-Dgj4WlbitUUHgcZmuBVR_bSendXLdAx/edit
1. To make your phone go to Qualcomm 9008 all you have to do is download an Android 8.1 stock rom from any region, flash it all using fastboot. You may get an error trying to flash boot.img but keep flashing the files.
2. Once you finish flashing and type: "fastboot reboot", your phone will boot into Qualcomm mode, it should be listed in Device Manager.
3. DISABLE any antivirus and download this blankflash, just unzip it and execute the blankflash.bat file.
4. Your phone should boot up in fastboot mode and you can start flashing the latest stock rom.
adri_sefp said:
UPDATE:
- I finally found a blankflash (my phone still the same) but you can give it a try.
LINK (copy and paste om your browser) drive.google.com/file/d/1-Dgj4WlbitUUHgcZmuBVR_bSendXLdAx/edit
1. To make your phone go to Qualcomm 9008 all you have to do is download an Android 8.1 stock rom from any region, flash it all using fastboot. You may get an error trying to flash boot.img but keep flashing the files.
2. Once you finish flashing and type: "fastboot reboot", your phone will boot into Qualcomm mode, it should be listed in Device Manager.
3. DISABLE any antivirus and download this blankflash, just unzip it and execute the blankflash.bat file.
4. Your phone should boot up in fastboot mode and you can start flashing the latest stock rom.
Click to expand...
Click to collapse
works if I have the bootloader still locked?
adri_sefp said:
UPDATE:
- I finally found a blankflash (my phone still the same) but you can give it a try.
LINK (copy and paste om your browser) drive.google.com/file/d/1-Dgj4WlbitUUHgcZmuBVR_bSendXLdAx/edit
1. To make your phone go to Qualcomm 9008 all you have to do is download an Android 8.1 stock rom from any region, flash it all using fastboot. You may get an error trying to flash boot.img but keep flashing the files.
2. Once you finish flashing and type: "fastboot reboot", your phone will boot into Qualcomm mode, it should be listed in Device Manager.
3. DISABLE any antivirus and download this blankflash, just unzip it and execute the blankflash.bat file.
4. Your phone should boot up in fastboot mode and you can start flashing the latest stock rom.
Click to expand...
Click to collapse
followed all the steps, bricking worked, but after flashing the latest software had the same problem
it would be nice if motorola would give us qfil software so we could flash it from the scratch
also, anyone any other option in this case? also found a dump of deen android 10 but I don't know what to do with it
claudiusuflea said:
followed all the steps, bricking worked, but after flashing the latest software had the same problem
it would be nice if motorola would give us qfil software so we could flash it from the scratch
also, anyone any other option in this case? also found a dump of deen android 10 but I don't know what to do with it
Click to expand...
Click to collapse
Was your device detected as Qualcomm? Did you use the blankflash file? Did yor phone boot to fastboot?
adri_sefp said:
Was your device detected as Qualcomm? Did you use the blankflash file? Did yor phone boot to fastboot?
Click to expand...
Click to collapse
Indeed, after flashing an Android 8 firmware my phone went into Qualcomm 908 EDL mode. After blankflashing and flashing the latest firmware had the same issue with "No bootable A/B slot". The same state before hardbricking the phone (AP Fastboot flash mode secure).
adri_sefp said:
Hello guys!
I've been looking for a solution to this problem, I have a Moto One XT1941-5 that was never rooted nor bootloader unlocked. I left it charging and after about one hour it was at Fastboot Mode, it says that it failed booting from normal mode. Even if I try to restart or start normally, it gets back to Fastboot.
What have I done until now?
- Tried to flash the whole latest STOCK ROM again (manually with fastboot tools)
- Tried with a ROM from another region (mine is OPENMX and tried with RETLA) and I get the same
- Tried with Repair Assistant from Motorola, nothing happens.
- Tried to unlock bootloader, it asks me to enable OEM unlock on Developer settings (I can't, phone doesn't power up)
* Something that gets me confused is about the slots, $fastboot getvar all reports that none of the slots are bootable, every time I flash the ROM it says that slot A is bootable and B not, or that A is not bootable and B yes, or none of the slots are bootable.
Here are some screenshots about the info I have.
Click to expand...
Click to collapse
maybe works "lenovo rescue and smart assistant"
Marc.os said:
maybe works "lenovo rescue and smart assistant"
Click to expand...
Click to collapse
No, lmsa would recognise the phones after A10 update, but the problem persists. Someone who has repaired this or someone who has managed to take it to the service or managed to revive the phone from this state? With locked bootloader
Marc.os said:
maybe works "lenovo rescue and smart assistant"
Click to expand...
Click to collapse
That didn't help either, there's nothing else we can do than replacing the main board.
Hello.
I have a similar problem. I have tried all of the methods listed, unfortunately nothing works. I ended up replacing the motherboard. The old PCB is waiting, maybe someday it can be repaired.