Related
I tried to install a new rom(cynogenmod 11 from xda forums) in my lenovo a6000 which i god a day before on my birthday. it had lollipop os and i installed TWRP recovery in it. but the instructions for installing rom said to clear data. dalvik, cache before installing and the twrp cleared cache and delvik cache but then it had been over 5 min and it still stated -"formatting data by mounting(bla... bla...) method". so i just reboot the phone by removing the battery and booted in the recovery again. i tried to clear them again but this time all of those three stated mounting problems while clearing. i went on installing the rom but it stuck too stating only these lines:-
1>no md5 checksum found.
2>skipping md5 checksum(bla.. bla...).
so i did the same mistake again and removed the battery to reboot but now it just shows the lenovo logo on bootup and nothing happens thereafter except frequent restarts. i tried to connect it to pc to load recovery via minimal adb and fastboot but the phone is just charging itself via usb cable and not connecting to the pc no matter i reinsert the battery.
i dont want to reach the service center or my dad will kill me for damaging a new phone. please if anyone can help then reply soon or i am gonna screwed.
Just press volume - & power key same time , now your phone is in boot loader mode now connect USB & flash twrp recovery through minimal adb method & restore your backup
Sent from my Lenovo A6000 using XDA Free mobile app
To be continued
Oh I somehow figures it out, I pressed all the keys I.e. volumeup + volumedown + power key even after the Lenovo powered by android logo and it suddenly booted into recovery. This method worked in my bq s37 I didnt expected it in this case. BTW thanks for your support and can u please help in in a new case related to same. The twrp recovery for a6000 lollipop is not installing cm11 properly. Every time I install using the same method as mentioned in a post of XDA. After installation it stops on the same screen:- Lenovo (powered by android) and after that no reboot just that screen forever till the battery dies. I even tried cleaning /system before installing cm11 ROM but still no progress. Please help!
You cannot install cm11 on top of stock Lollipop rom
Revert it back to kitkat flash recovery Then install cm11
Get it of one problem and the other awaits. Now when installing KitKat rom (the official one from techotally) it said unable to mount /data. I followed some tutorial which asked to write some codes from adb shell menu. One of the codes said something like -kill recovery, after what my recovery frooze. I restarted the phone by removing the battery but nothing is happening after that. I am trying to restart it in recovery or in bootloader or even normal restart. Everything in vain and nothing is shown on screen and not even boot logo or the lenovo powered by Android screen. But in my pc some drivers started installing out of which two were installed and two weren't please help.
Ahmad Tawfik said:
Follow this guide
QUOTE]
There is said that ensure the devise is connected as Qualcomm his 9008 drivers but for me windows iinstalls 9006 drivers and States failed to verify signature. I manually installed the 9008 drivers . the installed properly without error but in not cases m getting sahara error. Failed to download. Also my phone doesn't display anything, no display, no sound and no vibrating while powering on but the PC connats it as as Qualcomm hs..............
Click to expand...
Click to collapse
*in both the cases*
Ok I will help you
1- Download stock Lollipop firmware and place it in your sd and insert it in your phone
http://phonedl.ota.lenovomm.com/dls/v6/Kraft-A6000_S054_150915_WCAA.zip
2-hold volume down and power key and you will see fastboot under powered by Android
3- use fastboot to flash and boot into stock Lollipop recovery
Fastboot flash recovery recovery.img
Fastboot boot recovery.img
http://www.mediafire.com/download/gcg2klu8fwam2sk/Recovery.img
4- in Stock recovery factory rest and wipe cache partition
5- apply update from Sd and select the stock Lollipop firmware the you placed on SDCard
6- Done your phone will boot to system successfully
If you want to install cm11 after fixing your phone
1-revert to kitkat stock firmware follow the guide (like the phone is bricked)
2- Install twrp recovery by fastboot
http://lenovo-forums.ru/index.php?app=core&module=attach§ion=attach&attach_id=36985
3- Install cm11 and enjoy
Note:
place the files you want to fastboot in the fastboot folder
Sent from my GT-I9300I using Tapatalk
You are not correctly getting it my friend. i said the phone doesnt boot at all no matter what key combinations are tried. it simply doesnt start. no display no vibration no sound nothing just the pc detects it as qualcomm hsusb.........
BTW in the mean time my father got to know about this condition. he scolded me but asked to fix it if i can before going to service center. i was just thinking what if they got to know that i rooted the phone? or installed custom recovery in it? anyway if i am to go to the service center the statement given by me will be that:- while updating via ota from kitkat to lollipop the battery died and this all happened. an yes i live in INDIA time zone=+5:30 GMT so tell me when i can find you online(time?) my friend so we can try fixing my phone also it will be help full if we become friends on facebook? so that we can chat live clearly and for as long as we want. so that i can ask you about any problem occouring in future directly without creating a forum in xda. so please buddy please....... .... .. .
The Boy Who Cried Wolf said:
You are not correctly getting it my friend. i said the phone doesnt boot at all no matter what key combinations are tried. it simply doesnt start. no display no vibration no sound nothing just the pc detects it as qualcomm hsusb.........
BTW in the mean time my father got to know about this condition. he scolded me but asked to fix it if i can before going to service center. i was just thinking what if they got to know that i rooted the phone? or installed custom recovery in it? anyway if i am to go to the service center the statement given by me will be that:- while updating via ota from kitkat to lollipop the battery died and this all happened. an yes i live in INDIA time zone=+5:30 GMT so tell me when i can find you online(time?) my friend so we can try fixing my phone also it will be help full if we become friends on facebook? so that we can chat live clearly and for as long as we want. so that i can ask you about any problem occouring in future directly without creating a forum in xda. so please buddy please....... .... .. .
Click to expand...
Click to collapse
My Facebook is [email protected]
I prefer hangout
[email protected]
Contact me any time and I will try to reply directly
Sent from my GT-I9300I using Tapatalk
After flashing the firmware link given by u , Ota will work or not ?
Sent from my Lenovo A6000 using XDA Free mobile app
amit1009000 said:
After flashing the firmware link given by u , Ota will work or not ?
Sent from my Lenovo A6000 using XDA Free mobile app
Click to expand...
Click to collapse
It will work and also this is the latest update
Sent from my GT-I9300I using Tapatalk
I know but only this update is not installing in my device 138mb , so i thinking to flash the full lolipop with this update by ur given link . can i do it ?
Sent from my Lenovo A6000 using XDA Free mobile app
amit1009000 said:
I know but only this update is not installing in my device 138mb , so i thinking to flash the full lolipop with this update by ur given link . can i do it ?
Sent from my Lenovo A6000 using XDA Free mobile app
Click to expand...
Click to collapse
Yes
Sent from my GT-I9300I using Tapatalk
Ahmad Tawfik said:
Ok I will help you
1- Download stock Lollipop firmware and place it in your sd and insert it in your phone
2-hold volume down and power key and you will see fastboot under powered by Android
3- use fastboot to flash and boot into stock Lollipop recovery
Fastboot flash recovery recovery.img
Fastboot boot recovery.img
-- in Stock recovery factory rest and wipe cache partition
5- apply update from Sd and select the stock Lollipop firmware the you placed on SDCard
6- Done your phone will boot to system successfully
If you want to install cm11 after fixing your phone
1-revert to kitkat stock firmware follow the guide (like the phone is bricked)
2- Install twrp recovery by fastboot
http://lenovo-forums.ru/index.php?app=core&module=attach§ion=attach&attach_id=36985
3- Install cm11 and enjoy
Note:
place the files you want to fastboot in the fastboot folder
Sent from my GT-I9300I using Tapatalk
Click to expand...
Click to collapse
But why don't u understand that I can not boot in any mode the danm phone simply doesn't display anything no sound or vibrations and no change of mode too.just connected as quallcomm hsusb and nothing else and even with that and following the ways in the link provided before(boycracked unbrick a6000) I'm getting sahara download error.
Not Install
Dear
Ahmed
When I am try to install the zip its give an erro
phone does not switch to carrier can not install
status (101)
installation abbroat
Please help to install it.
amit1009000 said:
Dear
Ahmed
When I am try to install the zip its give an erro
phone does not switch to carrier can not install
status (101)
installation abbroat
Please help to install it.
Click to expand...
Click to collapse
You have to install it from stock recovery and to factory reset and wipe cache partition before installing the zip
Lenovo updates are very bad and may soft brick you phone
Sent from my GT-I9300I using Tapatalk
install
i tried with stock recovery but same problem.
So it seems I'm being ignored
Hey ahmed
I did everything that was stated in the how to's but to no avail. additionally i cant get TWRP installed via fatboot, i have checked and crosschecked usb debugging and unlock OEM , but i cant get it to work , with SP Flash my phone pops up and vanishes in the hardware manager withing fractions of a second so it doesnt work with the sp Flash , in fastboot it wont let me download to recovery even if i use the command line oem unlock , because the volume up button that you have to use to accept[yes] doesnt work , only the vol down[no ] button has an effect, anyone any ideas anyone?
?
Kylekassar said:
I did everything that was stated in the how to's but to no avail. additionally i cant get TWRP installed via fatboot, i have checked and crosschecked usb debugging and unlock OEM , but i cant get it to work , with SP Flash my phone pops up and vanishes in the hardware manager withing fractions of a second so it doesnt work with the sp Flash , in fastboot it wont let me download to recovery even if i use the command line oem unlock , because the volume up button that you have to use to accept[yes] doesnt work , only the vol down[no ] button has an effect, anyone any ideas anyone?
?
Click to expand...
Click to collapse
To use SP Flash tools, turn the phone off, press download on the software then plug the phone in. The preloader is only meant to show for a short time (a fraction of a second to a few seconds) so SPFT needs to be sending the signal to download in that time window.
What I've also found works is to press download on SPFT then press and hold power and volume up until the device starts downloading.
thx for the quick answer i will try a.s.a.p.
Kylekassar said:
thx for the quick answer i will try a.s.a.p.
Click to expand...
Click to collapse
Tried but it doesnt work , i starts the dload but then i end up on brom error : STATUS_PRELOADER_INVALID(0xC0030004) no recovery flashed
Kylekassar said:
Tried but it doesnt work , i starts the dload but then i end up on brom error : STATUS_PRELOADER_INVALID(0xC0030004) no recovery flashed
Click to expand...
Click to collapse
That could be a couple of things:
Which SPFT version are you using? If its an older version try using a newer one.
Or
The scatter file you loaded is not good, download a stock firmware and use the scatter file from that.
Try this:
fastboot flash recovery "filename".img
or
fastboot flash boot "filename".img
Do you have the MTK drivers installed? What does your phone appear as in the Device Manager? Like others have said, once you've chosen your scatter file and recovery to flash, hit download and then plug in the phone.
Managed to fix this? I have the exact same problem and not able to fix it till now....
I'm in a similar situation. I CAN get my phone to flash recovery in SPFT and get a lovely big green tick but when I power off and boot into recovery using power and volume up it boots into the stock android recovery rather than TWRP.
Going another way via ADB, I can get the phone detected but when I send the OEM unlock bootloader command I am unable to use volume up to confirm. Only the volume down key works to cancel.
All I want is to put viper4android on. Never had any issues until this phone.
chandlerp said:
I'm in a similar situation. I CAN get my phone to flash recovery in SPFT and get a lovely big green tick but when I power off and boot into recovery using power and volume up it boots into the stock android recovery rather than TWRP.
Going another way via ADB, I can get the phone detected but when I send the OEM unlock bootloader command I am unable to use volume up to confirm. Only the volume down key works to cancel.
All I want is to put viper4android on. Never had any issues until this phone.
Click to expand...
Click to collapse
Are you 100% sure the recovery.img you flashed was TWRP?
Absolutely. Downloaded from this very site. It was this one: recovery_TWRP_3021_P9000.img
---------- Post added at 02:23 PM ---------- Previous post was at 02:17 PM ----------
Did an OTA update this morning and am showing as on build number Elephone_P9000_20160608 now. Haven't tried flashing since the update as I'm at work with locked down computers. Was going to try again over the weekend. Which recovery and version of flash tools would you recommend trying this time?
thanks for any advice.
Actually I have the same problem.
I tried to reinstall the drivers because it seems to be not the correct one. Here is a pic: i.imgur.com/FoUnVyz.png
After I read somewhere that i can try and hold down Volume+ while connecting my phone to the pc where i started the download in sp tools prior.
I got this error code: STATUS_PRELOADER_INVALID(0xC0030004)
And here I am with a not-up-to-date elephone p9000.
Anybody care to help me?
I'm in the same situation, tried everything - flashtool recovery.img separate in download mode, flashtool in update mode full 7.0 with replaced original recovery.img with TWRP one, played with fastboot with no luck as did not find the way to OEM UNLOCK it - vol + not reacting. Bought the phone on Gearbest, looks like it's locked very hard.
Can't install TWRP
Me too! I've updated my p9000 to latest stock v7 rom with spft. I can't install twrp recovery despite getting a geen tick from spft. Tried four times but it won't overwrite the stock rom recovery. A locked bootloader seems to be the popular diagnosis but spft doesn't use the bootloader. What else could it be? Ideas very welcome.
Did you boot into recovery immediately after flashing? A normal system boot will overwrite TWRP with the stock recovery. Once you start TWRP there is an option to prevent this from happening.
Can't install TWRP
Thanks for the suggestion. I flashed twrp again but it won't boot into recovery afterwards without a restart, just hangs. Stiĺl on stock recovery.
Hello guys, I am new here to XDA Developers, so here's my take on my phone's problem..
Long story short, I wanted to root my phone so I could enable the OTG option for my phone cuz I tend to get my storage filled up and use a USB to transfer files. So, I did root my phone, got its bootloader unlocked and successfully done the operation. I used the kiwi_twrp_3-21_recovery.img via ADB and Fastboot tool for this.
But when I used ADB and Fastboot to flash the boot-kiwi-marshmallow-otg,img file and restart it afterwards, the phone will go straight to eRecovery mode. Here I cannot download the recovery it wants because it always show download info fail of some sort and that I cannot debug the phone either. I do can get it to Fastboot mode but my computer won't detect it.. So my phone is basically a stone now. What should I do now? It is my first time so I don't wanna get busted, any help will be appreciated! Thanks!
For reference: I was using this this thread for OTG enabling feature:
https://forum.xda-developers.com/honor-5x/how-to/tutorial-enable-otg-honor-5x-t3322274
And for rooting process, I just watched this video:
https://www.youtube.com/watch?v=Y-2SWbInT6U
Kingofiron257 said:
Hello guys, I am new here to XDA Developers, so here's my take on my phone's problem..
Long story short, I wanted to root my phone so I could enable the OTG option for my phone cuz I tend to get my storage filled up and use a USB to transfer files. So, I did root my phone, got its bootloader unlocked and successfully done the operation. I used the kiwi_twrp_3-21_recovery.img via ADB and Fastboot tool for this.
But when I used ADB and Fastboot to flash the boot-kiwi-marshmallow-otg,img file and restart it afterwards, the phone will go straight to eRecovery mode. Here I cannot download the recovery it wants because it always show download info fail of some sort and that I cannot debug the phone either. I do can get it to Fastboot mode but my computer won't detect it.. So my phone is basically a stone now. What should I do now? It is my first time so I don't wanna get busted, any help will be appreciated! Thanks!
For reference: I was using this this thread for OTG enabling feature:
https://forum.xda-developers.com/honor-5x/how-to/tutorial-enable-otg-honor-5x-t3322274
And for rooting process, I just watched this video:
https://www.youtube.com/watch?v=Y-2SWbInT6U
Click to expand...
Click to collapse
Solutions:
1. Boot into recovery (Power + VolUp) and restore last backup (I really do hope you have a backup). It should be enough to restore just boot image. Mine ended in eRecovery few days ago after messing with Magisk and I've successfully recovered my device from there
2. Download original firmware, extract it, boot into fastboot (obv., try fixing it first, but you've flashed TWRP so it must work for other stuff, too) and just reflash original boot image
3. Download original firmware, extract it, boot into fastboot and reflash original recovery, then try eRecovery (this will probably wipe all your data, though)
There are tons of manuals how to extract Huawei/Honor firmware images (even a nice little program to do it for you), so I'd suggest searching around for that SW instead of asking how.
Kingofiron257 said:
Hello guys, I am new here to XDA Developers, so here's my take on my phone's problem..
Long story short, I wanted to root my phone so I could enable the OTG option for my phone cuz I tend to get my storage filled up and use a USB to transfer files. So, I did root my phone, got its bootloader unlocked and successfully done the operation. I used the kiwi_twrp_3-21_recovery.img via ADB and Fastboot tool for this.
But when I used ADB and Fastboot to flash the boot-kiwi-marshmallow-otg,img file and restart it afterwards, the phone will go straight to eRecovery mode. Here I cannot download the recovery it wants because it always show download info fail of some sort and that I cannot debug the phone either. I do can get it to Fastboot mode but my computer won't detect it.. So my phone is basically a stone now. What should I do now? It is my first time so I don't wanna get busted, any help will be appreciated! Thanks!
For reference: I was using this this thread for OTG enabling feature:
https://forum.xda-developers.com/honor-5x/how-to/tutorial-enable-otg-honor-5x-t3322274
And for rooting process, I just watched this video:
https://www.youtube.com/watch?v=Y-2SWbInT6U
Click to expand...
Click to collapse
what recovery do you have now?? can you access twrp? or you are left with emui recovery??
if you have emui recovery, just perform a dload flash
Looks like he solved it.
adriansticoid said:
Looks like he solved it.
Click to expand...
Click to collapse
We need his solution , the one he tried
gopinaidu77 said:
We need his solution , the one he tried
Click to expand...
Click to collapse
Let's wait for his post.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
Let's wait for his post.
Click to expand...
Click to collapse
Its been long he replied. Omg ,what is going ?
Stop. Spamming. The. Thread. For. Points.
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
PHH aosp gsi confirmed to boot on BOLD-N1.
Need to be fully stock
--boot
--vendor
--recovery
Restoring device to factory condition , see this thread
Download PHH-AOSP 10
Download will be a compressed file *.gz , ectract the *.img file from inside
.
Code:
fastboot flash system **extracted-GSI.IMG**
fastboot oem reboot recovery
Perform factory reset inside stock recovery.
my tests trying to complete these steps with twrp all end with unknown imei.
V203 boots with only found issue is the fingerprint sensor Not working. For me i feel mtk devices are not secure anyway, the fingerprint sensor is more of a gimmick, so if it is not working, i do not care.
Current version v215 tested by and boots fine.
https://github.com/phhusson/treble_experimentations/releases
Things to consider
WHAT WORKS:
audio -music and speaker phone
camera-front and back (yes pop-up camera works)
video-camera front and back
video playback --(tested youtube in browser) - recorded video playback
Phone calls
messages
auto rotate
brightness
wifi tethering
mtp
flashlight
lift to wake (needed to turn off then on to activate it)
adaptive brightness
dark theme
gps
WHAT DOESN'T:
--Fingerprint
--phone works/ but dialer app has message that device is unsupported
--off-mode charging -- when charging with phone off, bootloader logo screen stays on, instead of battery icon
--screen recording-- after enable dev option // feature flag // settings_screenrecord_long_press .. you can access
screen record from long press power menu, long press screenshot menu, but recording will not save or stop
recording.-- setting option to on does not survive reboot
-- screen shot -- taking screen shot forces a bug report creation. (maybe this is not an issue, only a setting)
.
So I actually have to go back to stock since I'm running magisk? Is that why when I try flashboot flash vbmeta vbmeta.img it comes back as unknown file/directory?
Sergeantslaughter said:
So I actually have to go back to stock since I'm running magisk? Is that why when I try flashboot flash vbmeta vbmeta.img it comes back as unknown file/directory?
Click to expand...
Click to collapse
our device does not have VBmeta
the directions that say flash VBMETA, say use the stock meta file from stock firmware. so because that file is not used here, this is why you get the error message, ......
actually from your command you did not tell fastboot the location of the file you are trying to flash Unless you have a file called "vbmeta.img" in the current command terminal location. But again back to my original statement, our device does not have this file, so IF you do have the file, it is from other device anyway.
I guess I see how to flash the gsi but how do I get twrp installed?
mrmazak said:
PHH aosp gsi confirmed to boot on BOLD-N1.
only one permission file needed to be added. This is also expected to be included in the next release anyway.
Need to be fully stock
--boot
--vendor
--recovery
fastboot flash system **GSI.IMG**
fastboot oem reboot recovery
perform factory reset inside stock recovery.
my tests trying to complete these steps with twrp all end with unknown imei.
tested version was AOSP 10.0 v201
V203 boots without having to add the extra permission XML file.
Current version v204 not tested yet.
https://github.com/phhusson/treble_experimentations/releases
additional step to get version lower than v203 to boot
Download the additional permission file from
https://github.com/phhusson/device_...0.0/privapp-permissions-me.phh.treble.app.xml
While system is on boot animation screen. (this is as far as it will go on its own)
After the adb push, for me at least, the phone starts to continue its boot operation. Still do the reboot anyway.
Click to expand...
Click to collapse
So I haven't been able to find a twrp.img file for bold n1. Sorry if I sound stupid but this is my first time doing this. I had root with magisk and something screwed it up, and my phone was reading SIM cards. I uninstalled magisk and am back stock with an unlocked bootloader ...can you possibly walk me through installing twrp and flashing the Android 10 files? I would be so appreciative!
Sergeantslaughter said:
I guess I see how to flash the gsi but how do I get twrp installed?
So I haven't been able to find a twrp.img file for bold n1. Sorry if I sound stupid but this is my first time doing this. I had root with magisk and something screwed it up, and my phone was reading SIM cards. I uninstalled magisk and am back stock with an unlocked bootloader ...can you possibly walk me through installing twrp and flashing the Android 10 files? I would be so appreciative!
Click to expand...
Click to collapse
I have not been using twrp with GSI, but if you want to try goto twrp thread. Note that the twrp is currently only working with adb command line interface. No touch screen activity.
start by looking at the threads here. You will find twrp thread there.
So I've got Android 10 up and running...so can I just go ahead and root with magisk? Or will that mess up what I just did?
Sergeantslaughter said:
So I've got Android 10 up and running...so can I just go ahead and root with magisk? Or will that mess up what I just did?
Click to expand...
Click to collapse
aosp has root built in. If you prefer majisk, you need to first remove the included -su, and then need to use PHH-Majisk, not standard version.
Information on that should be found in gsi thread. It is not device specific.
ok so i had 10 working without twrp.....went to flash twrp...flash success....reboot to recovery...screen went black and CAN NOT get the device to power back on.....no vibrate no power no nada......wtf do i do?!?!?!
Sergeantslaughter said:
ok so i had 10 working without twrp.....went to flash twrp...flash success....reboot to recovery...screen went black and CAN NOT get the device to power back on.....no vibrate no power no nada......wtf do i do?!?!?!
Click to expand...
Click to collapse
you do know the screen in twrp has long delay before turns on. Do you have adb access to device?
if twrp is dead to adb, then
not sure why it would do that. but , i would first flash stock recovery with spflash tool
mrmazak said:
not sure why it would do that. but , i would first flash stock recovery with spflash tool
Click to expand...
Click to collapse
will that work? i cant get my phone to power on at all and adb is not recognizing it...
mrmazak said:
you do know the screen in twrp has long delay before turns on. Do you have adb access to device?
if twrp is dead to adb, then
not sure why it would do that. but , i would first flash stock recovery with spflash tool
Click to expand...
Click to collapse
everything is dead....phone no power or vibration while pushing buttons...no reaction when charging....adb says no device....fastboot the same
ive tried spflash tool but since computer isnt even detecting device, no luck.......im so upset. i just bought this phone.....the only kind of life i get is when plugging into windows laptop the connected "doop" sound for connected and then about 5 seconds later the same sound for disconnect.....repetitively and its driving me crazy
when trying to install the vcon drivers for spflash as the log is running says finish because its not detecting, but then says detected and drivers are newer what is trying to be installed...then not detected again
any advice? any chance at saving my phone??
Sergeantslaughter said:
everything is dead....phone no power or vibration while pushing buttons...no reaction when charging....adb says no device....fastboot the same
ive tried spflash tool but since computer isnt even detecting device, no luck.......im so upset. i just bought this phone.....the only kind of life i get is when plugging into windows laptop the connected "doop" sound for connected and then about 5 seconds later the same sound for disconnect.....repetitively and its driving me crazy
when trying to install the vcon drivers for spflash as the log is running says finish because its not detecting, but then says detected and drivers are newer what is trying to be installed...then not detected again
any advice? any chance at saving my phone??
Click to expand...
Click to collapse
That repeating sound is sign of bootloop.
Spflash tool is the recommended repair tool.
Download the factory restore package,
Extract the downloaded file.
Open flashtool, select scatter file from the extracted download. Ensure tool is on "download only" mode
Clear all select boxes in the tool window. Put check only in the recovery line.
Press download button, plug USB into phone. The bootloop in the phone is enough to make connection start.
What twrp did you use, where did it come from. Did you verify md5 of the downloaded file.
The only twrp I found was the one I shared, and it did not cause that kind of issue for me. So maybe you did something that you didn't mention?
I think I found the culprit... I download a file called "twrp" that actually turned out to be orangefoxrecovery... So I'm pretty positive that that's what caused it... Also, I've got a green check mark that says download OK.... Yellow bar at bottom of screen says recovery download flash 100%... What is my next step sir...?
---------- Post added at 05:11 AM ---------- Previous post was at 05:06 AM ----------
By the way I just wanna say you're awesome and thank you so much for your help!, this is my first time trying to do all this and I'm grateful to have someone so knowledgeable to save my a$$! Thanks man!
Sergeantslaughter said:
I think I found the culprit... I download a file called "twrp" that actually turned out to be orangefoxrecovery... So I'm pretty positive that that's what caused it... Also, I've got a green check mark that says download OK.... Yellow bar at bottom of screen says recovery download flash 100%... What is my next step sir...?
---------- Post added at 05:11 AM ---------- Previous post was at 05:06 AM ----------
By the way I just wanna say you're awesome and thank you so much for your help!, this is my first time trying to do all this and I'm grateful to have someone so knowledgeable to save my a$$! Thanks man!
Click to expand...
Click to collapse
Oh, last step is unplug USB. Then long press power button.
10 second should do. But maybe 20
Sergeantslaughter said:
everything is dead....phone no power or vibration while pushing buttons...no reaction when charging....adb says no device....fastboot the same
ive tried spflash tool but since computer isnt even detecting device, no luck.......im so upset. i just bought this phone.....the only kind of life i get is when plugging into windows laptop the connected "doop" sound for connected and then about 5 seconds later the same sound for disconnect.....repetitively and its driving me crazy
when trying to install the vcon drivers for spflash as the log is running says finish because its not detecting, but then says detected and drivers are newer what is trying to be installed...then not detected again
any advice? any chance at saving my phone??
Click to expand...
Click to collapse
Same happened to me, ended up fixing issue by using spflah tool (latest) and updated stock rom (mrmazak posted it) ?
I haven't bought the N1 yet but just might thanks to @mrmazak testing! Anyone tried Q v204 yet? Also curious if PHH regular Pie is bug free.
mrmazak said:
PHH aosp gsi confirmed to boot on BOLD-N1.
Need to be fully stock
--boot
--vendor
--recovery
Restoring device to factory condition , see this thread
Download PHH-AOSP 10
Download will be a compressed file *.gz , ectract the *.img file from inside
.
Code:
fastboot flash system **extracted-GSI.IMG**
fastboot oem reboot recovery
Perform factory reset inside stock recovery.
my tests trying to complete these steps with twrp all end with unknown imei.
V203 boots with only found issue is the fingerprint sensor Not working. For me i feel mtk devices are not secure anyway, the fingerprint sensor is more of a gimmick, so if it is not working, i do not care.
Current version v204 not tested by me yet.
https://github.com/phhusson/treble_experimentations/releases
Click to expand...
Click to collapse
Do not tell me in v 203 which version to download? I tried several but all to no avail
elephone p8000
any insight as to why every computer i plug my bold n1 into it shows up as a elephone p8000?
and on that note, say i found a working twrp for the elephone p8000 would that be possible?
i lost my root and android 10 due to bootloop. i used spflash to restore stock pie firmware. but now no matter what method or gsi or rom i try to flash my phone just will not accept it. The flashing is always successful, but upon reboot, i get a yellow/green screen flash followed by boot anim boot loop? any idea what would be causing this? i cant for the life of me figure out why my phone wont accept any system imgs i try to flash..
Sergeantslaughter said:
any insight as to why every computer i plug my bold n1 into it shows up as a elephone p8000?
and on that note, say i found a working twrp for the elephone p8000 would that be possible?
i lost my root and android 10 due to bootloop. i used spflash to restore stock pie firmware. but now no matter what method or gsi or rom i try to flash my phone just will not accept it. The flashing is always successful, but upon reboot, i get a yellow/green screen flash followed by boot anim boot loop? any idea what would be causing this? i cant for the life of me figure out why my phone wont accept any system imgs i try to flash..
Click to expand...
Click to collapse
Elephone p8000 is at least 3 years old. And would not think twrp from it will work on your bold n1.
As for why your PC shows your bold n1 as different phone, I can only guess that your PC drivers are somehow modified.
Or your phone is maybe not stock?