Related
Okay, so i am using a xperia z2, cant rmb the version of the firmware, but i successfully rooted my device so i went on to try and flash cm11 onto my device. However, upon flashing cm11 and gapps into my phone through dual recovery i was no longer able to boot up my phone. Holding the power switch causes the device to vibrate, like perhaps every two seconds, but does nothing meaningful. Holding the powerswitch and the volume up key boots into fast boot, which is just a blank screen, but with the blue led that i read on the internet meant fastboot. Problem is, I am unable to get windows to install the relevant drivers for S1 Fastboot as it is displayed on my device manager window, and nothing i try will help. Ive downloaded usb drivers from numerous sources, including but not limited to flashtool, and nothing can get the fastboot to be recognised by the computer. Kindly advise on what i could do to restore my phone please! any help is greatly appreciated!!!!
I live in Singapore and i understand that bootloaders are by default unlocked? I'm not sure if i have to install any form of kernel , but i have a feeling this may be the cause of the problem? Please be kind, I am new to this entire rooting business. Once again any assistance is greatly appreciated!
http://forum.xda-developers.com/showthread.php?p=53220435
Folow this to unbrick your device
You need an unlocked bootloader to flash cm11, no bootloader comes unlocked
There is unlockable and non unlockable
Hey guys,
I am sorry if I am in the wrong place or am asking something wrong. This is my first time using these forums (and forums in general). If I need to be somewhere else kindly redirect me.
Anyway, I was with Verizon for a while but after some shady stuff I decided to break up with them. Beforehand I had bought outright a Sony Xperia Z2 Tablet. Because I did not want anything Verizon on it I decided to root it, and flash a good ROM onto it (Cyanogenmod was my idea, but at the time I don't think they supported it? I'm not good with ROMS). Anyway, the rooting was completely successful and I had a custom recovery (TWRP) installed. I was ready to flash the ROM. Unfortunately, I wasn't paying attention and grabbed the wrong ROM. What ended up happening is when I attempted to reboot after "flashing", the device didn't show anything on the screen and just kept vibrating. After some digging around I found it might be "soft-bricked". I had at one time found a guide that told me how to undo this by using SDK Tools and Fastboot Mode (blue LED), but cannot find the guide anymore.
I was wondering if ANYONE could help me undo this mistake, and get the tablet back to it's original state or with a nice compatible ROM. I am currently in Fastboot mode and it is plugged into my ASUS Laptop running Windows 7. Any and all help would be GREATLY appreciated. Thank you so much for taking time to read this.
EDIT: So a breakdown is I cannot interact with the tablet directly. There is absolutely no interface. Just a screen that won't turn on. Meaning if there is a method it can't be done on the tablet. The old guide I found was explaining how to do it through Windows while the tablet was plugged into it via USB.
Also the bootloader was never unlocked so I think that was also an issue.
First of all, if your bootloader is locked, you cannot install CM because you cannot change the Kernel. You can only use Sony-certified Kernels which won't work with CM. So Sony-based ROMs are your only options
But what you can do is:
- Go into fastboot mode (turn off your tablet, connect it to your PC and press volume up. If the blue LED shows up, you are in fastboot)
- With fastboot, you should be able to flash a ROM (preferably Android 4.4, so you can root again)
- Then root, install dual recovery
- Flash the correct ZIP
Alternative:
- Unlock Bootloader
- Flash recovery
- Flash CM
BabelHuber said:
First of all, if your bootloader is locked, you cannot install CM because you cannot change the Kernel. You can only use Sony-certified Kernels which won't work with CM. So Sony-based ROMs are your only options
But what you can do is:
- Go into fastboot mode (turn off your tablet, connect it to your PC and press volume up. If the blue LED shows up, you are in fastboot)
- With fastboot, you should be able to flash a ROM (preferably Android 4.4, so you can root again)
- Then root, install dual recovery
- Flash the correct ZIP
Alternative:
- Unlock Bootloader
- Flash recovery
- Flash CM
Click to expand...
Click to collapse
Can you simplify this? Where do I find the ROM (again, this was a tablet from Verizon so I assume on top of the Sony ROM I need the Verizon version of it?) And I understand I cannot install CM unless the bootloader is unlocked; do you know how to do this?
I'm confused by the first set of instructions as I cannot use the tablet directly. How will I flash the ROM (and which is the right ROM and where can I find it?) through the computer since the tablet can't be interacted with. There is absolutely no interface to interact with whatsoever. Which ROM do I download for the Verizon Sony Xperia Z2 Tablet and how do I flash it using Fastboot? I assume I do it thru my computer?
Sorry, but you'll have to Google a little bit - I haven't had your exact problem.
But as long as you can get into fastboot mode, nothing is lost.
There also is the Sony ftf tool or so, the Windows program name is Emma. This should be easier than using fastboot.
Also there is a sony site for bootloader unlocking. You can check whether your bootloader can be unlocked at all.
hi folks,
tomorow should be getting my hands on the Ulephone power 2.
its the 5.5 screen 4gb ram 64gb rom.
all looks good until i have seen that the normal duel sim is one is hybrid for sdcard which is the norm right,
ant
but............
usually its sim 1 is for 4g cards and the hybrid is for 2g/3g/sdcard. yeah?
well the power 2 looks like its sim slot 1 is a 2g/3g slot and the hybrid is 4g or sdcard??????????
so will have to choose 4g or sdcard??? that cant be right?
I don't try this device with sim.
I know you can use the older power (1) have a sim 4g and SD card
So i believe the power 2 have the same method.
My first steps: How to root this device? i don't find a twrp.
I try to root with kingroot kingoroot, no results
Please?
The power 2 is the same as the power wrt the sim/memory card tray; both sim slots support 4g, but only one at a time. So if you put two 4g sims in, only one of them will have 4g (you choose which one), with a sim and a memory card the 4g should default to the inserted sim, but you might have to check this in settings.
Received my power 2 a couple of weeks ago after having it on pre-order for a month and I love it (sold the original power towards the cost).
I haven't tried rooting it yet, but was thinking of trying to flash twrp for the original power and seeing if that works. The great thing about these phones is that they're very hard to brick as you can always flash them as long as they still switch on.
Slàinte
mmidders
Hello my friends. I just bought the ulefone power 2 and i try to root it. Can anyone help me pls ???
mmidders said:
The power 2 is the same as the power wrt the sim/memory card tray; both sim slots support 4g, but only one at a time. So if you put two 4g sims in, only one of them will have 4g (you choose which one), with a sim and a memory card the 4g should default to the inserted sim, but you might have to check this in settings.
Received my power 2 a couple of weeks ago after having it on pre-order for a month and I love it (sold the original power towards the cost).
I haven't tried rooting it yet, but was thinking of trying to flash twrp for the original power and seeing if that works. The great thing about these phones is that they're very hard to brick as you can always flash them as long as they still switch on.
Slàinte
mmidders
Click to expand...
Click to collapse
I'm sure it's not working the twrp from the power (1).
If you have troubles with bootloops you can flash again the facatory rom and SP flash tools.
Press the power volume + and - and SP flash tools gonna flash.
The only way is to made a twrp from the k6000 http://fvknl.pro/k6000-plus-root-guide/
I don't know how, that device is almost the same...
There has been 2 ulefone Updates since launch
Android 8.0 is scheduled for end of the year.
Updates are fine, who can create a TWRP? So we can finally root the device
geheimke said:
Updates are fine, who can create a TWRP? So we can finally root the device
Click to expand...
Click to collapse
up
TWRP please!
Not so easy to do it. It will take very long time to port or build twrp
It sucks that power 2 still doesn't have root or twrp. I refuse to touch unrooted phones. I just received it as gift. I will keep it in a drawer and check next month or so.
I find that it lacks optimisation, kinda laggy in 3D/games ..
On Antutu, scores is 44000. I tested a galaxy S5 of a friend, it was 72000. For a phone that is several years older than Power 2.
I understand that it comes not with high end cpu/gpu but still..
I will copy my post from needrom website.
I have successfully rooted my two Power 2 phones. I had to port the TWRP recovery from Oukitel k6000 plus using Carliv Image Kitchen and following some online tutorials.
The only issue is, TWRP is semi functional, that is, touch doesn't work. I had to connect a mouse to my phone via OTG usb port and using some dongle to make USB smaller to fit the port. Also it comes with Russian language as default, but can be changed to English or any other as the original TWRP from Oukitel k6000+ (3rd button from second column, then click on Globe tab at the top right then choose English and the only button at the bottom to accept the change).
I am trying to fix this with no luck so far. But at least I am rooted and I was able to flash "SR1-SuperSU-v2.82-SR1-20170608224931.zip" which is the latest as of writing this. SuperSu functions properly and I am able to use AdAway.
If anyone is interested in the recovery image, I will post it. I flashed it using fastboot though after unlocking the bootloader using "fastboot oem unlock"
Click to expand...
Click to collapse
Rebel_X said:
I will copy my post from needrom website.
Click to expand...
Click to collapse
I would very much like to give this a go with my ulefone power 2!
Here you go, TWRP for Ulefone Power 2
What you need to do before you start flashing:
0) You need to have ADB installed on your computer, if you have Windows, the easiest way is by using 15 Seconds ADB Installer v1.4.3.
1) Your bootloader must be unlocked, otherwise flashing recovery will fail using fastboot command. PLEASE NOTE: When unlocking the bootloader, your phone will do a factory reset automatically, so backup all your important files beforehand.
To unlock the bootloader:
a) Go to Settings -> About Phone -> Build number (tap on it 7 times to unlock Developer Options) -> Tap on back to Settings menu then Developer Options.
b) Now move the slider for "OEM Unlocking" to enable it, say yes to the warning message.
c) Enable "USB Debugging"
d) Connect your phone to your computer via USB cable, say Yes for the dialog on your phone to trust your computer for debugging using USB.
e) Run command prompt and type
Code:
adb reboot bootloader
Then press enter
f) Once in bootloader, type
Code:
fastboot oem unlock
Then press Volume UP on your phone to allow OEM Unlock. It shouldn't take long, just few seconds and a message will appear on command prompt saying success or OK.
g) Type
Code:
fastboot reboot
To reboot your phone, it might reboot twice, it will do a factory reset and you will have to "Enable Developer Options and USB Debugging" again. As a side note, you will also notice that OEM Unlocking is grayed out. It will remain like that unless you do "fastboot oem lock" or erase the entire phone (might erase imei, but can be restored using SN Writer Tool) and/or flash bootloader using SP_FLASH_TOOL, but I digress.
2) Before you flash TWRP recovery, you must have SuperSu zip file on your phone beforehand, otherwise, your phone will not boot to Android. It has to do with something about the original TWRP for Oukitel k6000+, since the author of that TWRP port said so in the instructions about how to flash the recovery.
So download SR1-SuperSU-v2.82-SR1-20170608224931.zip from this link or the original SuperSu thread on XDA, and copy the file into your phone, say inside the Download folder in the internal memory of your phone.
3) Open command prompt again if it is not already open, type
Code:
adb reboot bootloader
4) Once in bootloader, type
Code:
fastboot flash recovery C:\TWRP-recovery-20170618-1340.img
Note: You replace the path for the TWRP recovery to where you have the file, to make it easier, just put it in the root of C drive.
Also, if you don't already know, while in command prompt, you can type C:\TWRP then press TAB to auto-complete the file name for you, so you don't have to type lengthy file names. Keep pressing TAB to cycle between similar occurrences, that is, if you have more than one file that their names start with TWRP
5) Press power button until phone shuts down. Then press Volume UP + Power and keep holding until you see super tiny text with 3 options to cycle between. Release your fingers from Volume Up + Power, then cycle between the options using Volume Up only, choose "RECOVERY" which is the first in the menu, then press Volume DOWN to select.
6) Wait a few seconds, you will be inside TWRP, connect your phone with a mouse since touch doesn't work here. Once you do, you will see a mouse pointer appear. I used a wireless mouse with bluetooth dongle, with an adapter to change USB port size.
7) Slide the slider to the right, to enable modifications to System partition. Don't press anything else, unless you know Russian, I don't .
8) To change the language to English or your own language, click on the third button of the second column. Then click on the Globe tab on the top right corner, change language, then press the only button at the bottom to accept. Language of the UI is changed.
9) Click "Install", browse for the SuperSu zip file you have downloaded to your phone, for example inside the Download folder. And then select it.
10) Slide to the right to flash SuperSu.
11) From the TWRP menus, you can reboot your phone.
12) Enjoy your rooted Power 2 phone. :good:
---------- Post added at 04:47 AM ---------- Previous post was at 04:47 AM ----------
alpsayin said:
I would very much like to give this a go with my ulefone power 2!
Click to expand...
Click to collapse
Check the post above :good:
hello , i got a ulefone power 2 but unfortunately its not powering on. As i am from india and returning or replacing is costly and timetaking process, i need you guys to help me. I tried to flash it with software available on the website but stuck. I need some checksum.ini file which is not there in the firmware file provided. So anyone please help me. the phone doesnt even show the ulefone logo. i can just see the charging percentage when the charger is connected, then keeping it connected i tried to turn on but didnt work. keeping the charger connected ,after some time the display goes off and no mater how long you press the power button , the display doesnt show up. I can only see the notification bulb.
Soft bricked :laugh: trying to recover the phone, official ulefone guide is useless. Getting some error about a missing checksum.ini file. Will keep this thread updated
All went well until step 9, where I realised factory reset deleted the supersu zip. So I tried to reboot into system to download it again. It never booted. Doesnt even go into adb mode.
Fastboot mode and TWRP intact (TWRP needs a mouse). I was able to flash original recovery via fastboot, getting "cannot load system.img" error when I try to flash system (it appears I might need to update my adb/fastboot version).
UPDATE: was able to flash the stock rom. And tried to follow the guide again, and faced the same symptoms. If i have working TWRP, then the system doesnt boot. And vice-versa. Will keep updated, i'm a persistent mf
Rebel_X said:
Here you go, TWRP for Ulefone Power 2
What you need to do before you start flashing:
0) You need to have ADB installed on your computer, if you have Windows, the easiest way is by using 15 Seconds ADB Installer v1.4.3.
1) Your bootloader must be unlocked, otherwise flashing recovery will fail using fastboot command. PLEASE NOTE: When unlocking the bootloader, your phone will do a factory reset automatically, so backup all your important files beforehand.
To unlock the bootloader:
a) Go to Settings -> About Phone -> Build number (tap on it 7 times to unlock Developer Options) -> Tap on back to Settings menu then Developer Options.
b) Now move the slider for "OEM Unlocking" to enable it, say yes to the warning message.
c) Enable "USB Debugging"
d) Connect your phone to your computer via USB cable, say Yes for the dialog on your phone to trust your computer for debugging using USB.
e) Run command prompt and type
Code:
adb reboot bootloader
Then press enter
f) Once in bootloader, type
Code:
fastboot oem unlock
Then press Volume UP on your phone to allow OEM Unlock. It shouldn't take long, just few seconds and a message will appear on command prompt saying success or OK.
g) Type
Code:
fastboot reboot
To reboot your phone, it might reboot twice, it will do a factory reset and you will have to "Enable Developer Options and USB Debugging" again. As a side note, you will also notice that OEM Unlocking is grayed out. It will remain like that unless you do "fastboot oem lock" or erase the entire phone (might erase imei, but can be restored using SN Writer Tool) and/or flash bootloader using SP_FLASH_TOOL, but I digress.
2) Before you flash TWRP recovery, you must have SuperSu zip file on your phone beforehand, otherwise, your phone will not boot to Android. It has to do with something about the original TWRP for Oukitel k6000+, since the author of that TWRP port said so in the instructions about how to flash the recovery.
So download SR1-SuperSU-v2.82-SR1-20170608224931.zip from this link or the original SuperSu thread on XDA, and copy the file into your phone, say inside the Download folder in the internal memory of your phone.
3) Open command prompt again if it is not already open, type
Code:
adb reboot bootloader
4) Once in bootloader, type
Code:
fastboot flash recovery C:\TWRP-recovery-20170618-1340.img
Note: You replace the path for the TWRP recovery to where you have the file, to make it easier, just put it in the root of C drive.
Also, if you don't already know, while in command prompt, you can type C:\TWRP then press TAB to auto-complete the file name for you, so you don't have to type lengthy file names. Keep pressing TAB to cycle between similar occurrences, that is, if you have more than one file that their names start with TWRP
5) Press power button until phone shuts down. Then press Volume UP + Power and keep holding until you see super tiny text with 3 options to cycle between. Release your fingers from Volume Up + Power, then cycle between the options using Volume Up only, choose "RECOVERY" which is the first in the menu, then press Volume DOWN to select.
6) Wait a few seconds, you will be inside TWRP, connect your phone with a mouse since touch doesn't work here. Once you do, you will see a mouse pointer appear. I used a wireless mouse with bluetooth dongle, with an adapter to change USB port size.
7) Slide the slider to the right, to enable modifications to System partition. Don't press anything else, unless you know Russian, I don't .
8) To change the language to English or your own language, click on the third button of the second column. Then click on the Globe tab on the top right corner, change language, then press the only button at the bottom to accept. Language of the UI is changed.
9) Click "Install", browse for the SuperSu zip file you have downloaded to your phone, for example inside the Download folder. And then select it.
10) Slide to the right to flash SuperSu.
11) From the TWRP menus, you can reboot your phone.
12) Enjoy your rooted Power 2 phone. :good:
---------- Post added at 04:47 AM ---------- Previous post was at 04:47 AM ----------
Check the post above :good:
Click to expand...
Click to collapse
mbs.yaswanth said:
hello , i got a ulefone power 2 but unfortunately its not powering on. As i am from india and returning or replacing is costly and timetaking process, i need you guys to help me. I tried to flash it with software available on the website but stuck. I need some checksum.ini file which is not there in the firmware file provided. So anyone please help me. the phone doesnt even show the ulefone logo. i can just see the charging percentage when the charger is connected, then keeping it connected i tried to turn on but didnt work. keeping the charger connected ,after some time the display goes off and no mater how long you press the power button , the display doesnt show up. I can only see the notification bulb.
Click to expand...
Click to collapse
Yeah, I had the same issue with the software that comes from Ulefone, it was asking for Checksum Generator that I have to download separately, it was like 150kb stand alone executable, you put it in the same folder of your stock ROM and wait forever for it to build the Checksum, which unfortunately didn't work since it complains about multiple RECOVRY images. So scratch that.
What you need to do, is as I did, download SP FLASH TOOL, it works great, no shinanigans or bullsh!t. It flashed the stock ROM in less than 2 minutes (around 1:30 seconds, to be exact) and revived my phone. There are plenty of youtube tutorials on how to use it. It is easy, just load the scatter file, for the other file, you can use the same all in one mtk file that comes with SP FLash Tool (I did this) or use the one from your STOCK ROM.
I hope that helps :good:
---------- Post added at 02:33 PM ---------- Previous post was at 02:27 PM ----------
alpsayin said:
Soft bricked :laugh: trying to recover the phone, official ulefone guide is useless. Getting some error about a missing checksum.ini file. Will keep this thread updated
All went well until step 9, where I realised factory reset deleted the supersu zip. So I tried to reboot into system to download it again. It never booted. Doesnt even go into adb mode.
Fastboot mode and TWRP intact (TWRP needs a mouse). I was able to flash original recovery via fastboot, getting "cannot load system.img" error when I try to flash system (it appears I might need to update my adb/fastboot version).
UPDATE: was able to flash the stock rom. And tried to follow the guide again, and faced the same symptoms. If i have working TWRP, then the system doesnt boot. And vice-versa. Will keep updated, i'm a persistent mf
Click to expand...
Click to collapse
All I can think of, you did something wrong. Initially, while I was trying to port TWRP, I had the same issue, I was trying to save some steps by flashing the recovery after I unlocked the bootloader without rebooting, the result was TWRP was not able to see any partitions.
Flash Stock-ROM and redo the steps. If you flash the preloader you might have to OEM Unlock your phone again.
I mentioned that if you "do not flash SuperSu, the system will NOT boot to Android". Also mentioned that after you unlock the bootloader, you have to RE-ENABLE USB Debugging, and while you are at it, check to see if your bootloader is unlocked inside Developer Options.
Edit: BTW, try not to unlock the bootloader if it is already unlocked. If it is unlocked, then skip the steps for unlocking the bootloader. It might cause an issue.
These are the steps I used to flash TWRP and I was able to flash SuperSu, all rooted apps are working fine, AdAway, Lucky Patcher...etc!
This:
Rebel_X said:
Here you go, TWRP for Ulefone Power 2
2) Before you flash TWRP recovery, you must have SuperSu zip file on your phone beforehand, otherwise, your phone will not boot to Android. It has to do with something about the original TWRP for Oukitel k6000+, since the author of that TWRP port said so in the instructions about how to flash the recovery.
Click to expand...
Click to collapse
And this combined:
Rebel_X said:
Here you go, TWRP for Ulefone Power 2
9) Click "Install", browse for the SuperSu zip file you have downloaded to your phone, for example inside the Download folder. And then select it.
Click to expand...
Click to collapse
Apparently if you dont flash the supersu first time you go into TWRP then it gets messy. Got the root working now. Thank you for the help and of course for the TWRP build!
Also if anyone's wondering it's possible to restore the system via fastboot. Extract the rom zip (can be downloaded from http:/ulefone.com/download/power2.html ) and flash boot, recovery and system;
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
link for sp flash tool u used.
Rebel_X said:
Yeah, I had the same issue with the software that comes from Ulefone, it was asking for Checksum Generator that I have to download separately, it was like 150kb stand alone executable, you put it in the same folder of your stock ROM and wait forever for it to build the Checksum, which unfortunately didn't work since it complains about multiple RECOVRY images. So scratch that.
What you need to do, is as I did, download SP FLASH TOOL, it works great, no shinanigans or bullsh!t. It flashed the stock ROM in less than 2 minutes (around 1:30 seconds, to be exact) and revived my phone. There are plenty of youtube tutorials on how to use it. It is easy, just load the scatter file, for the other file, you can use the same all in one mtk file that comes with SP FLash Tool (I did this) or use the one from your STOCK ROM.
I hope that helps :good:
---------- Post added at 02:33 PM ---------- Previous post was at 02:27 PM ----------
All I can think of, you did something wrong. Initially, while I was trying to port TWRP, I had the same issue, I was trying to save some steps by flashing the recovery after I unlocked the bootloader without rebooting, the result was TWRP was not able to see any partitions.
Flash Stock-ROM and redo the steps. If you flash the preloader you might have to OEM Unlock your phone again.
I mentioned that if you "do not flash SuperSu, the system will NOT boot to Android". Also mentioned that after you unlock the bootloader, you have to RE-ENABLE USB Debugging, and while you are at it, check to see if your bootloader is unlocked inside Developer Options.
Edit: BTW, try not to unlock the bootloader if it is already unlocked. If it is unlocked, then skip the steps for unlocking the bootloader. It might cause an issue.
These are the steps I used to flash TWRP and I was able to flash SuperSu, all rooted apps are working fine, AdAway, Lucky Patcher...etc!
Click to expand...
Click to collapse
ok what should i select there? formal all+download or download only or firmware upgarade???
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
My first thread and my only device, please help.
My device was rooted 3 years ago downgrading to 23.0.A.2.93 then flashing a prerooted stock ROM.
Right now I was using 23.5.A.1.291 SLiMM 3.8 with SuperSU 2.82 and Xposed 89, but I think at some point I tried to update BusyBox and lost access to the recovery.
So my idea was to instal XZDualRecovery (2.8.26) then unlock bootloader and jump into some newer version of Resurrection Remix (my fav ROM) cause I felt I was quite behind and I don't really like any new device.
How I broke it:
I connected it to my computer (Win10), enabled USB debugging, clicked on the install.bat from XZDR and allowed debugging and root access, the script went as I thought it should, threw some "couldn't write" errors but I think the script figured out as I saw some mounting system partition and whatnot underneath, when it finished it tried to reboot and there I am, I cannot go past the Sony logo and it constantly reboots.
What I tried:
Using Xperia Companion's "Software repair", I shut the device down, I press volume - and connect USB, my computer finds a USB device but the software doesn't recognize it as my device, so it doesn't continue.
I also tried doing the same but this time with volume +, it recognizes my device but it says that is locked and to please unlock it (as in drawing the unlock pattern) but the screen is black and doesn't react.
Flashtool also cannot find the device.
My last attempt was to unlock the bootloader to see if that changed anything, fastboot doesn't do anything and shows < waiting for any device >.
The best of this all is that I didn't even have a backup of almost anything, as this process doesn't wipe anything I thought I was in the clear, the more you know...
Come on guys, I need some help, somewhere from where to start, either to recover my files or to revive my Z3.