Ask : About Oppo A57 - Android Q&A, Help & Troubleshooting

How to make oppo a57 be fastboot mode.
I want to install twrp and will be in root.
I've tried to hold volume + power button but become booting to window screen again..
what is oppo a57 no feature fastboot mode?
And what version twrp for oppo a57?
Please help me
thanks

"volume+" and "power" mostly running recovery/twrp mode.
Try "volume-" and "power" for fastboot mode.
Developer option is running? OEM unlock?
Load TWRP please. I wanna try too. Thanks.

volume - and power to recovery mode default oppo..
volume + and power oppo loggo appears and than booted to start again..
i have done it all before..
butstill can not get into fastboot mode..
i have not instaled twrp..
i want to fastboot mode to install twrp..
the problem is oppo a57 can not get into fastboot mode..
unlike oppo f1 i already successfully install twrp and root..
please help me
thanx for the answer

How about ADB?
USB-debagging, OEM unlock on phone, then use terminal.
"ADB reboot bootloader" - isn't work?
I'll try some things too, then return to home after work.

i have done and nothing happened,when running adb command "adb reboot bootloader" phone restart and returne to home screen not to fastboot mode.
i try to do this repeatedly until finally i ask to this forum..
help me
thanx for the answer

can someone help me?

Hello Dear, I have been trying the same with My Oppo A57, but still nothing works, I hope, we find out a way to enter fasboot mode. Thanks

Oppo A57 makes me dizzy:crying:

Fastboot access has been disabled on Oppo A57
Hey guys,
I've been looking into this situation and as far as I can tell, fastboot is disabled/unavailable on new Oppo devices unless we can find a workaround.
Fastboot was disabled by Oppo to help secure ColorOS but was previously available by flashing 'project spectrum'. Based on this report by Ausdroid it appears that they have either cancelled or temporarily suspended development of project spectrum now as well: http://ausdroid.net/2017/03/16/oppo-project-spectrum-killed-off-hiatus-notice/
A potential option I have found was a flashable zip file (magictricks.zip) that was created to enable fastboot on the Oppo F1 but I have not yet attempted to flash it as it wasn't made specifically for the A57 so it could possibly brick it.
https://forum.xda-developers.com/oppo-f1/development/boot-loader-unlock-twrp-related-t3397013/page1
I have emailed the creator of magictricks.zip asking if there's potential that it could work but I have yet to receive a response.
If someone has an A57 and is feeling brave, flashing it might possibly work as the F1 had fastboot disabled for the same reason. I am not responsible for your bricked device if you attempt this though.
Here's hoping some senior devs start helping us out with this because this phone has the potential to be an awesome well spec'd budget device with a custom rom installed.
Here's hoping.

I am waiting for news from the maker of magictrick.zip..:good:
thank

I tried .
Magictricks get rejected by A57 recovery.
As any other not genuine oppo firmware.
I tried adb reboot edl command and it works.
Blank screen phone is recognized as COM port in Windows.
That could be way to upload custom boot image.

martinr1 said:
I tried .
Magictricks get rejected by A57 recovery.
As any other not genuine oppo firmware.
I tried adb reboot edl command and it works.
Blank screen phone is recognized as COM port in Windows.
That could be way to upload custom boot image.
Click to expand...
Click to collapse
Interestingly I only found this out the other day as well.
Turns out if you put: *#801# in the dialer it gives you access to a diagnostics menu which let's you activate a bunch of Qualcomm diag ports.
Problem is I'm a rookie when it comes to QPST. I was able to use one of the included programs to backup a copy of my non-volatile memory but I'm not sure if I did it correctly or if that information is even useful? It's only 917KB.
Now would be a great time for an experienced developer to chime in. If you know ways to use QPST to back up I can do it and send you the files you need.

You need to modify emmc_appsboot.mbn to enable fastboot, then flash to phone with built in recovery or harder way with QPST tool.
Magictrics contains also emmc_appsboot.mbn but for different phone.
Original firmware is available on oppo website. It is 1.7GB size, quite a bloat. It contains emmc_appsboot.mbn
If you look inside that file with text editor you can see fastboot commands etc.
It is implemented but disabled.

martinr1 said:
You need to modify emmc_appsboot.mbn to enable fastboot, then flash to phone with built in recovery or harder way with QPST tool.
Magictrics contains also emmc_appsboot.mbn but for different phone.
Original firmware is available on oppo website. It is 1.7GB size, quite a bloat. It contains emmc_appsboot.mbn
If you look inside that file with text editor you can see fastboot commands etc.
It is implemented but disabled.
Click to expand...
Click to collapse
Thanks for the info, now I'm headed in the right direction. You sound like you know your stuff a lot more than me tbh.
See the potential problem I could see with the stock recovery is that I'm assuming it would have some kind of signature verification to ensure that the update.zip is legitimate.
I'm in the process of fixing my computer atm so I can't use it to look at the file right now.
When I open emmc_appsboot.mbn with a generic editor it's gibberish. Do I need to use notepad++ or is it just encrypted or a compressed format?
I reckon I could work out how to decrypt the emmc_appsboot.mbn but repackaging it into a working flashable file makes me nervous..
I hate this phone in its current state though so I guess I've got nothing to lose if I brick it haha. Wish me luck.

So I've done some digging and realised it's a binary file. Looks like I've got a steep learning curve ahead of me trying to wrap my head around editing these binary files. ?
This should be fun.

Good continue waiting then

Yes, it is binary file, but with text editor you can find understandable text inside gibberish.
Better results can be seen with dissassembler.
More info:
newandroidbook.
com
/Articles/aboot.html

So what next?
is there a solution?
I hope to find the best solution ..
thanks

It seems there might be a solution in China.
bbs.7to.cn/thread-315780-1-1.html

I got my A57 to custom recovery and root.
http://bbs.7to.cn/thread-315939-1-1.html

Related

[Q] Huawei U8520 Dual Sim problem with bootloop and no recovery menu

Hi all
first of all I apologize if this is not the right place to put my inquiry in, but I could not find the specific forum for this device.
I have serious problem with this android mobile phone. it is pretty good phone very useful with dual sim function one of them is 3G with WiFi Hotspot but the problem that I have rooted the phone with superoneclick and I have installed a lot of apps in it modifying some language files then when I restart the phone to let the changes take effect then the mobile keep restarting for infinite. Tried to get in to the recovery mode by using Call Button+Volume up+Power but the screen became blank. I spent the whole day searching the the internet to find the solution but with no clue. the problem the device is new and not supported that much in the public forums. could not find Stock Rom. Huawei website and bulletin was not useful.
is there any way to do it through USB or sdcard and How?
thanks in Advance
I am still trying to find a solution...
if you need it, I attached the original recovery dump to this post.
then you just need to get "fastboot" and then (after preparing your device for fastboot):
"fastboot flash recovery recovery.img" (on a command line opened on the same folder where "fastboot" is)
or you can probably do it too on Linux if you prefer. if it is possible, you'll find the way for it on Google.
also, to access fastboot mode is POWER+VOL_DOWN (not volume up or a 3 key combination) and recovery is POWER+HOME (which you probably already know).
the system dump I can't send because I never made a dump.img of it and I am currently having a bootloop problem (I'll probably have to flash the original rom from a friend).
bl88drg said:
if you need it, I attached the original recovery dump to this post.
then you just need to get "fastboot" and then (after preparing your device for fastboot):
"fastboot flash recovery recovery.img" (on a command line opened on the same folder where "fastboot" is)
or you can probably do it too on Linux if you prefer. if it is possible, you'll find the way for it on Google.
also, to access fastboot mode is POWER+VOL_DOWN (not volume up or a 3 key combination) and recovery is POWER+HOME (which you probably already know).
the system dump I can't send because I never made a dump.img of it and I am currently having a bootloop problem (I'll probably have to flash the original rom from a friend).
Click to expand...
Click to collapse
Hi, Can you help me and upload the boot img. I accidentally erase the boot partition.
Many Thanks.

Huawei Y6, how to remove FRP?

Hi guys, i got the Huawei Y6 SCL-L01 phone and i wanted to install a custom rom, so i tried to install TWRP first, but since there wasn't a Y6 version (there isn't a Y6 version for anything pf ) i used the P8 version and it installed but when it rebooted the phone was stuck at a screen that say FASTBOOT & RESCUE MODE. The phone seems to be unlocked according to that screen but the FRP is loocked.
Things i've tried so far
Installed ADB latest version, extracted Recovery Cust System and Boot images from an official stock ROM.
Tried all available drivers from Google TP_Link and Intel for my phone.
The screen i am stuck does not work with ADB commands, the device is not recognized.
Fastboot commands work and it sees the device correctly, the problem is every time i try to flash the images from the stock rom i get FAILED message due to FRP Lock.
Format userdata and cache doesn't work either.
Vol + / - and Power button combinations also have no effect, it only shows that screen regardless of what i press.
I've searched the web and the XDA forums extensively since this happened and tried every possible solution i could find even if it was meant for another device.. no luck.
And here's my question, how can i possibly remove the FRP lock by only using fastboot?
Please somebody help, i am like half a day away from decorating the wall with this piece of ****
PS: I am not able to upload screenshots, sorry about that.
Asdforcer said:
Hi guys, i got the Huawei Y6 SCL-L01 phone and i wanted to install a custom rom, so i tried to install TWRP first, but since there wasn't a Y6 version (there isn't a Y6 version for anything pf ) i used the P8 version and it installed but when it rebooted the phone was stuck at a screen that say FASTBOOT & RESCUE MODE. The phone seems to be unlocked according to that screen but the FRP is loocked.
Things i've tried so far
Installed ADB latest version, extracted Recovery Cust System and Boot images from an official stock ROM.
Tried all available drivers from Google TP_Link and Intel for my phone.
The screen i am stuck does not work with ADB commands, the device is not recognized.
Fastboot commands work and it sees the device correctly, the problem is every time i try to flash the images from the stock rom i get FAILED message due to FRP Lock.
Format userdata and cache doesn't work either.
Vol + / - and Power button combinations also have no effect, it only shows that screen regardless of what i press.
I've searched the web and the XDA forums extensively since this happened and tried every possible solution i could find even if it was meant for another device.. no luck.
And here's my question, how can i possibly remove the FRP lock by only using fastboot?
Please somebody help, i am like half a day away from decorating the wall with this piece of ****
PS: I am not able to upload screenshots, sorry about that.
Click to expand...
Click to collapse
I'm stuck with this problem too. The exact problem. Have you found a way to fix it?
I have exactly the same problem with my Huawei Tablet.
If I boot with the original ROM and look in the "/log" - directory with adb shell, there is a cust.log. The contents say, that the specific ROM is not original or factory.
I think even the bootloader is unlocked, there is a kind of signature checking.
EDIT: @Asdforcer: Have you tried to boot the original boot.rom with "fastboot boot" - command?
How to remove FRP on Huawei Y6 TIT U02
Hi,
Since I try to update firmware from HUAWEI website, my phone comes non stop booting (bootloop). Any one can help me how to fix my phone?
Asdforcer said:
Hi guys, i got the Huawei Y6 SCL-L01 phone and i wanted to install a custom rom, so i tried to install TWRP first, but since there wasn't a Y6 version (there isn't a Y6 version for anything pf ) i used the P8 version and it installed but when it rebooted the phone was stuck at a screen that say FASTBOOT & RESCUE MODE. The phone seems to be unlocked according to that screen but the FRP is loocked.
Things i've tried so far
Installed ADB latest version, extracted Recovery Cust System and Boot images from an official stock ROM.
Tried all available drivers from Google TP_Link and Intel for my phone.
The screen i am stuck does not work with ADB commands, the device is not recognized.
Fastboot commands work and it sees the device correctly, the problem is every time i try to flash the images from the stock rom i get FAILED message due to FRP Lock.
Format userdata and cache doesn't work either.
Vol + / - and Power button combinations also have no effect, it only shows that screen regardless of what i press.
I've searched the web and the XDA forums extensively since this happened and tried every possible solution i could find even if it was meant for another device.. no luck.
And here's my question, how can i possibly remove the FRP lock by only using fastboot?
Please somebody help, i am like half a day away from decorating the wall with this piece of ****
PS: I am not able to upload screenshots, sorry about that.
Click to expand...
Click to collapse
Try to unlock your bootloader

Qilive(smartphone) how to root Q8 series tutorial(q8s5in4gp-q8s55in4g2)

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

Here are for all the rom oficial zte 820 metropc and t-mobile.

hello everyone here I bring the rom zte z820 to metropc and t-mobile files are recognized by the spflash tool but I only work with the Multiport_download_Z820_V1.0 (Service) (with the computer without battery and pressing the volume button less until the end the installation without further I pass the link to a drive folder with 3 files on
Multiport_download_Z820_V1.0 (Service) .zip
322150B3090Z820V1.0.0B30.zip (rom for t-mobile)
316100B1178MPCS_Z820V1.0.0B11.zip (rom for metropc)
I hope that with this contribution you can create new rom mod that improves the z820 ...
link: https://drive.google.com/drive/folders/1Pk-Duhdt0svif8YYLY8NYk6tOG-bRL2k
please download and upload it to another server so that the contribution is not lost ...
Thanks a lot, your post help me so much, I repair my Z820 with the files but with the up volumen button. Thanks man.
Thanks you!! i fixed boot loop in logo screen MPCS
Could someone help me use this? It doesnt like the scatter file Nevermind, I just had to extract the entire folder. So I run the service program, load the scatter file, select scan and then plug my phone in with no battery and press volume up. It does it's thing and now what?
I wish people would be clear about things when it concerns processes that could brick your device...anybody reading this i followed this video to get a basic idea of what to do:
youtube.com/watch?v=yslH3ito2lQ
Thank you for the files, Diego
Thanks a lot
was able to flash the stock rom from metropcs with the sp flash tool even though it would not work without the agent.bin found in this folder:
ZTE_Obsidian_Z820_MT6735M_MetroPCS_V1.0_(by_ztefirmware.com)
with sp flash tool version 5.1720
anyways are all the other people having problems loading the bootloader to get to fastboot mode?
i cant access fastboot mode it says waiting for device. adb recognizes the phone and so does fastboot even though once i reboot to bootloader from adb and from manual option in recovery all it does it restart the phone never gets to fastboot mode on both ways. i want to unlock the bootloader so i can flash twrp and set a custom firmware.
anybody with help please post a reply and a link that will support this model. i tried the tool all in one and adb same problem for fastboot

Question ONEPLUS Ace 2 BLACKDEATH AFTER FLASHING 11R OCDT.IMG

Hi everyone into this post thread.
We all know that converting chines ace 2 to oxygen os has some issues. We are trying our best to fix such issues, therefore trying different techniques. I had the same issue too, i read one post that flashing ocdt.img of 11R ll fix the issue, therefore, i took step to do it. After flashing 2487 ocdt.img, i restarted bootloader to normal. Phone booted, but still gets black, flicking and then goes black. I tried to restart it with keys, and phone wont detected by pc, even the bootloader was unlocked and usb debugging was enabled too. I tried enough to start in fastboot mode. But nothing, then i forcely start into EDL mode, and it deteceted. I purchased official authentication key to flash it back to coloros 13. The official tool failed to flash with error that image and product code mismatched and i loss money. Now dont know if i purchase a other authentication or wait for the developers to figure out issue.i have a complete flash tool logs, which is very useful for the developer.
Because in the stock image, they have made tachtis to keep users afftected and pay them to bring the devices back.
Pro opinion and fix is needed for everyone affected by this.
you need to flash china version (Ace2) ocdt.img again in your phone
make sure you have unlocked bootloader ( i know you have black screen). then go to fastboot and flash this file.
download file
power off ...
power on +( vol - )
connect cable
then in cmd write
fastboot flash ocdt ocdt.img
you have not orher way .. only this way can work 100%.
in OFP we have not OCDT image . so do not waste your time and money
I had tried enough to boot into fastboot, but phone dont boot, and dont know even this is booting or not due to black screen, i only know theat attaching cable vibrate the phone but it wont detected. Tried combination keys to boot i to bootloader, but no luck. I keep phone as it is to see if battery get drain and ensure that its power off and will try afternoon.
Thanks forsharing stock ocdt for this model.i would request you to kindly rename the file to this specific model, so people know about it. The flashing way is a same.
you need to keep all 3keys togather...
after 15sec it will go to EDL mode.. connect cable
after that ..
keep power + (vol- ).. after 15 sec it will go to fastboot
I face the same issue, I did wrong that FLASHING 11 (not 11 R) OCDT.IMG, The after-sales staff were unable to restore my phone, so they directly gave me a new one.

Categories

Resources