Related
Hello there
My name is Kareem and I'm using a Sony Xperia U 4.0.4 and build number 6.1.1.B.1.10.
So the thing is that I want to update my phone to 4.4 Kitkat and I'm following this thread.
I rooted my device, and I'm now trying to unlock bootloader. My devices says that I'm able to bootload but I still need to unlock it. So I googled around and came across this video which shows me how to unlock bootloader. First I had problems with installing the drivers because I am using windows 8.1 64-bit, but after I disabled “Driver Signature Enforcement” I managed to install the drivers.
And here the problem starts... I have to press the up volume button while plugging in so I can start fastboot. As what I was told, I did and the blue led on the left side turned on. But when I look on my desktop I get a notification that my usb device is not recognized.
Can anyone tell what causes this issue? Otherwise, is there another and maybe an easier way to unlock bootloader?
Kind regards
Kareem
P.s. I'm using that flashtool software to unlock bootloader. It's called "Sony Mobile Flasher by Androxyde".
I prefer to use this.
Is the official method for unlocking the bootloader, includes the drivers and stuff, just follow that tutorial and you're good to go.
Also you have to make sure that your phone can have unlocked bootloader first, if not, then, you have to stick to locked bootloader ROM's.
Now, sorry for saying like this but Windows 8.1 is such a pain in the a**, it always gives error because the drivers isn't signed, if you get problems with that again use this.
USB not recognized, well the solutions for that problem can be:
Use other USB port, if still doesn't work on any of the ports, then can be the slots or bad placement of pins in the motherboard, almost never is a problem of internal dust in the computer but you can try these.
Try other USB cable, may be the cable is failing, try other from another Android phone to complete the process.
Try using other computer with WIndows 7 or Ubuntu.
If you were not able to get working, then tell me.
Thanks for your reply. Both links are the ones I came across too, I used the first one but not the second one. So I'm trying the 2nd link, but I'm troubling with
browse from disk and select "android_winusb.inf" from "...\android-sdk\extras\google\usb_driver" and select "android bootloader interface.
Click to expand...
Click to collapse
There is no android bootloader interface in my usb_driver folder. Do I need to get it from somewhere like the SDK manager or a website?
Kareem
Kareem_XperiaU said:
Thanks for your reply. Both links are the ones I came across too, I used the first one but not the second one. So I'm trying the 2nd link, but I'm troubling with There is no android bootloader interface in my usb_driver folder. Do I need to get it from somewhere like the SDK manager or a website?
Kareem
Click to expand...
Click to collapse
Windows key + R, write devmgmt.msc, enter.
Plug your phone and look if some device is recognized in the list, it may appear as Android or something like that, if you got it, then follow me.
Right click to it, Update driver, select from computer, use a list from the PC, and "Use disk", see if there's something that says like that because I got Windows 7 in spanish so it's different.
In that browse for the folder that has the .inf file and open it, it returns a list that you have to select the interface, next and your driver may be installed.
Understand? I can explain more but I have Windows in spanish so I don't know how is in english.
Okay.
So I got to Device Manager and when I plug my phone when going in fastboot mode it first appeared as Android but then later on it appeared as Other Device(s) and after a split seconds it goes away. That's because the fastboot doesn't last long since fastbood isn't unlocked yet (and yest bootunlocker:yes is stated on my phone when dialing a code).
Secondly to your explanation. So when I still try to update the driver I can choose to let windows find a driver a use my own software to update it. So I clicked on use my own software, chose the path where the usb_driver is located. But only the folders appear, I can't see the ini or inf. files.
Edit: I'm actually going to downgrade back to windows 7. Since I went to 8.1 it gave a lot of troubles like unsupported screen resolutions and this.
Update: I managed to borrow my sister's laptop for one time, her laptop contains windows 7. So I got on her laptop and took my usb with flash-tool on it and a kernel. I connected my phone with cable while holding the buttons to get in fastboot mode, voila it got recognized by flashtool. I'm one step closer to unlocking bootloader with only one trouble a head. So when I try to unlock my bootloader with a kernel I get an error that my phone needs to be rooted first. The thing is that my phone has been rooted already, plus I just test if it is rooted and the test said that it's rooted. What can be the problem? Not having the right kernel? Not having pc companion on that pc?
Kareem_XperiaU said:
Okay.
So I got to Device Manager and when I plug my phone when going in fastboot mode it first appeared as Android but then later on it appeared as Other Device(s) and after a split seconds it goes away. That's because the fastboot doesn't last long since fastbood isn't unlocked yet (and yest bootunlocker:yes is stated on my phone when dialing a code).
Secondly to your explanation. So when I still try to update the driver I can choose to let windows find a driver a use my own software to update it. So I clicked on use my own software, chose the path where the usb_driver is located. But only the folders appear, I can't see the ini or inf. files.
Edit: I'm actually going to downgrade back to windows 7. Since I went to 8.1 it gave a lot of troubles like unsupported screen resolutions and this.
Update: I managed to borrow my sister's laptop for one time, her laptop contains windows 7. So I got on her laptop and took my usb with flash-tool on it and a kernel. I connected my phone with cable while holding the buttons to get in fastboot mode, voila it got recognized by flashtool. I'm one step closer to unlocking bootloader with only one trouble a head. So when I try to unlock my bootloader with a kernel I get an error that my phone needs to be rooted first. The thing is that my phone has been rooted already, plus I just test if it is rooted and the test said that it's rooted. What can be the problem? Not having the right kernel? Not having pc companion on that pc?
Click to expand...
Click to collapse
Tried to unlock the bootloader with the Sony method?
manudo said:
Tried to unlock the bootloader with the Sony method?
Click to expand...
Click to collapse
Okay I'm going to try it right now, at least I want to but there are some steps very confusing for me.
Sony website said:
9. Download and unzip this file. This is the standard android_winusb.inf-file, with a few lines of code added to enable Fastboot to support Sony and Sony Ericsson devices. Make sure you are running Google USB Driver package revision 4 or higher in your Android SDK. You can see current Google USB Driver package revision in the SDK Manager.
10. Place the unzipped file in the usb_driver folder, located in the Android SDK > extras > google folder on your computer. Accept to replace the old android_winusb.inf-file with the new file. If you can't find the usb_driver folder, please install the Google USB Driver Packager using the Android SDK manager.
11. Turn off your device.
12. On your device, push and hold the Fastboot button at the same time as you connect the device to the computer with a USB-cable. The Fastboot button may differ between different device models. See the Fastboot buttons page for more information on what button use on your device.
13. On your computer, you will be asked for drivers. Point to the usb_driver folder where you placed the android_winusb.inf-file, and select the Android Boot loader Interface-file.
14. Open a command window and go to the tools folder within the Android SDK folder.
15. Enter fastboot.exe -i 0x0fce getvar version, and verify that you get a response back (for example "0.3"). This means your device is connected properly.
Click to expand...
Click to collapse
13. Well when I connect my phone in fastboot mode it doesn't ask for driver installation, it happens automatic i guess. No problem, right?
14. Do I have to do it like the screenshot?
i1362.photobucket. com/albums/r682/klaskareem/Untitled_zps296a1291.jpg (website protocol needs to be placed in front + remove space between . &com
Kind regards
Kareem_XperiaU said:
Okay I'm going to try it right now, at least I want to but there are some steps very confusing for me.
13. Well when I connect my phone in fastboot mode it doesn't ask for driver installation, it happens automatic i guess. No problem, right?
14. Do I have to do it like the screenshot?
i1362.photobucket. com/albums/r682/klaskareem/Untitled_zps296a1291.jpg (website protocol needs to be placed in front + remove space between . &com
Kind regards
Click to expand...
Click to collapse
13. If your phone is recognized in fastboot mode then continue, if not, update the driver.
14. Know the command "cd"? Is for accesing directories, you can use "dir" to see whats in the folder. Example, you downloaded the Android SDK bundle in the Desktop, then "cd" to the "tools" directory, that contains the binary to unlock the bootloader. That's in cmd.
Like:
Code:
cd /SDK/adt-bundle-blah-blah/sdk/tools
And, you're using Windows 8, again, your device is recognized in fastboot mode?
Thank you for the clear explanation, makes sense now ( already knew that cd thing, wasn't sure though).
Uhm don't mind me using windows 8 atm. I'm downloading 32-bit sdk so I can use it on my sisters laptop.
Kareem_XperiaU said:
Thank you for the clear explanation, makes sense now ( already knew that cd thing, wasn't sure though).
Uhm don't mind me using windows 8 atm. I'm downloading 32-bit sdk so I can use it on my sisters laptop.
Click to expand...
Click to collapse
Right, if anything goes wrong, feel free to ask!
By the way. Do I need to make a copy my ROM I already have? Like when something goes wrong I can still go back to my original android 4.0.4
Kareem_XperiaU said:
By the way. Do I need to make a copy my ROM I already have? Like when something goes wrong I can still go back to my original android 4.0.4
Click to expand...
Click to collapse
It's recommended to keep the stock ROM or any other ROM if anything goes wrong.
Sent from my Xperia Sola using XDA Premium 4 mobile app
manudo said:
It's recommended to keep the stock ROM or any other ROM if anything goes wrong.
Sent from my Xperia Sola using XDA Premium 4 mobile app
Click to expand...
Click to collapse
And how can I do that to be honest?
Kareem_XperiaU said:
And how can I do that to be honest?
Click to expand...
Click to collapse
In this post, there are a list with all stock and custom ROM's available in XDA forum, you should download stock and if anything goes wrong then flash the stock ROM with flashtool. You know, flashmode, select kernel, connect to green led, let it boot, and you have stock.
By now, try to unlock the bootloader, if you need help with the flashing then you can ask by here or create another thread.
http://forum.xda-developers.com/m4-aqua
I have just successfully completed all 3 steps in the title and would like to compile the information so that more people can report more success. Many thanks and all credit to the threadstarter of this guide, the devs of the amazing Flashtool, and the dev of this newly created TOUCH version of the TWRP recovery (finally!)
Code:
DISCLAIMER:
[B]Your warranty is now void. [/B][U]DO THIS AT YOUR OWN RISK.[/U]
I am not responsible for bricked devices, bootloops, dead SD cards, thermonuclear war,
or you getting fired because the alarm app failed.
Please do some research if you have any concerns about any of the steps in this guide before performing them!
YOU are choosing to make these modifications,
please own your actions and don't be a baby about it.
Bootloader Unlock (instructions taken from this guide)
0. First check if your phone allows unlocking by dialing *#*#7378423#*#* , when Service Menu opens, go to Service Info, then Configuration; scroll down to read Rooting Status.
If "Bootloader unlocked" says yes, skip to the next section on Root.
If it says no (unlocked allowed), great, proceed on to next step.
If it says no (unlocked disallowed) or something like that, I'm sorry, unlocking won't work on your phone. Lodge a complaint with your mobile provider for locking it.
Getting the unlock code (skip to Step 5 if you already have it)
1. Go to Sony's official bootloader unlocking website.
2. Select Xperia M or M2 in the dropdown.
3. Follow all the steps (including *#06# to note your phone's IMEI number)
4. COPY the unlock code and paste and save it in a text file on your desktop.
Ensuring Flashtool recognises phone
5. Download Flashtool here and install it.
(To apply the 0.9.19.10 patch, install 0.9.19.8 and replace x10flasher.jar with the one from the patch. Default install folder is C:\Flashtool , don't change it)
6. Open Flashtool, connect your phone via USB. (Make sure USB Debugging is enabled in Developer Options). If Flashtool warns that ADB driver is not installed, go to the Sony website to download them. If Flashtool recognises phone, skip to Step 11.
7. Unzip the Sony drivers into a folder.
8. Boot into Advanced Startup on Windows and disable signed driver enforcement (I'm sorry, you have to Google this for your specific Windows installation)
9. When Windows has restarted, go to Device Manager, click on the ADB Interface item with the yellow questionmark, click Update Drivers, Search Manually, Have Disk, and then open the folder where the Sony driver inf is. select the ADB inf and install it. Warnings will pop up but install the drivers anyway. When done, the yellow questionmark will be replaced by something normal.
10. Verify that Flashtool recognises phone by connecting the USB cable when phone is on. You should see information about phone kernel and ROM version.
<Congratulations for making it this far>
Setting up Flashtool for use
11. With Flashtool open and phone connected, click on Devices in Flashtool menu > Check Drivers.
12. More information will pop up. Under ADB Devices, your phone's serial number will be stated (something like 10 digits and letters). Copy that serial number.
13. Go to %USERPROFILE%\.flashTool\mydevices .
14. Create a new folder in here and rename it to the serial number.
15. Open the serial number folder, create a new text file and rename it "ulcode.txt" (without the quotes).
16. Open the text file, paste your bootloader unlock code, save and close the file.
For step 16, as a precaution, copy and paste the serial number folder inside registeredDevices too. I didn't test which folder was being used by Flashtool for the unlock.
Actual unlocking of bootloader
17. With Flashtool open and phone connected, click on the BLU button. Follow all instructions. One involves VOL UP, the other involves VOL DOWN (for fastboot), please take note to do both, it's not deja vu.
18. When you have done so correctly, Flashtool will pop a small dialog with your IMEI and unlock code already pasted inside.
19. Take a deep breath and click unlock.
20. Check in main window that bootloader has indeed been unlocked.
21. Unplug the USB cable and boot your phone to check that everything should be normal.
CONGRATULATIONS, YOUR WARRANTY IS NOW VOID. :laugh:
Installing TWRP recovery (with touch capability but NO external SD card mount yet as of 13 Nov 2015)
0. Make sure your bootloader is unlocked before proceeding.
1. The download link is from the M4 Aqua Marshmallow Site, scroll to the bottom. (XDA thread is here)
2. Download and save the recovery.img file anywhere you like.
3. Copy and paste recovery.img to C:\Flashtool\x10flasher_lib .
4. Install the recovery using fastboot using the instructions based on this website (thanks and credits to Shyam Karnani):
Flashtool comes with its own ADB interface so we don't need to install any new ones or the bloated Android SDK.
a) Open a command window inside the folder C:\Flashtool\x10flasher_lib (shift-rightclick and select "open command window here")
b) Connect phone to the computer using the USB cable.
c) type "adb reboot bootloader" (without quotes) in the command window and press enter (if asked to allow USB debugging in the phone screen, touch ok)
d) when the phone has entered fastboot, type "fastboot flash recovery recovery.img" (without quotes) and enter. Check that there are no errors produced by the flashing.
e) type "fastboot reboot" and enter.
The phone now has TWRP recovery but NO ROOT.
To boot into recovery
1. Simultaneously press the Power button and Volume down until your device vibrates.
2. Quickly release the Power button, but keep pressing Volume down.
3. When you see the TWRP screen, release Volume down. You have now successfully entered recovery mode.
(Instructions from Sony Developer website)
Rooting using SuperSU
0. Check that you have flashed a custom recovery. If not, please refer to steps right above.
1. Download SuperSU from the official website.
2. Connect your phone and transfer the zip file to the INTERNAL storage (because no recovery can mount external SD card yet as of 13 Nov 2015).
3. Power off phone and boot into TWRP recovery.
(An info dialog will popup asking if you want to keep read-only for /system. I chose NOT to keep, but need someone with knowledge to explain if read-only will block rooting procedure. It will, right?)
4. Touch the Install button and scroll to find the supersu zip.
5. Install the supersu zip. When done, clearing cache/Dalvik is optional (can be done using Titanium Backup anyway once you have root).
6. Reboot system.
Enjoy your root! :good:
Good work, but is it for the M4 Aqua E2353 only?
adejager1 said:
Good work, but is it for the M4 Aqua E2353 only?
Click to expand...
Click to collapse
Of course, that's what the title says lol. I cannot vouch for the other models.
I think the instructions can be modified, like for example different serial number for different model.
I'm having problem after clicking the BLU button, I'm doing what it said "Unplug USB cable, power off, hold vol down, connect USB cable" but will have an error USB not recognized, check flashtool screen it said usb debugging is off, make sure your not in MTP, I already turn usb debugging on. I'm stuck here.
btw I disable signed driver enforcement already and installed the ADB, but still no luck
Running OS windows 10
help please, :crying: if you can make a video it may help. thanks!
Everything went well for me thanks a lot.
i'm on windows 8 64bits
---------- Post added at 05:20 PM ---------- Previous post was at 05:16 PM ----------
jmikaii said:
I'm having problem after clicking the BLU button, I'm doing what it said "Unplug USB cable, power off, hold vol down, connect USB cable" but will have an error USB not recognized, check flashtool screen it said usb debugging is off, make sure your not in MTP, I already turn usb debugging on. I'm stuck here.
btw I disable signed driver enforcement already and installed the ADB, but still no luck
Running OS windows 10
help please, :crying: if you can make a video it may help. thanks!
Click to expand...
Click to collapse
Have you installed the drivers in -> C:\Flashtool\drivers
select :
Flashmode Drivers (1st line)
Fastboot Drivers (2nd line - this one will be used)
Common drivers Nicky (11th line)
Yes i install it all, guys do you think because the os im using? "windows 10"?
Thanks a ton, bro successfully rooted my Sony Xperia M4 Aqua Dual (E2363).
jmikaii said:
I'm having problem after clicking the BLU button, I'm doing what it said "Unplug USB cable, power off, hold vol down, connect USB cable" but will have an error USB not recognized, check flashtool screen it said usb debugging is off, make sure your not in MTP, I already turn usb debugging on. I'm stuck here.
btw I disable signed driver enforcement already and installed the ADB, but still no luck
Running OS windows 10
help please, :crying: if you can make a video it may help. thanks!
Click to expand...
Click to collapse
I also find a problem of unable to unbrick my bricked my old sony device on windows 10 with flashtool.
I also get the same error.
Try on windows 8.1.
failed unlock
i have problem when trying to unlock the bootloader. it says "failed <remote: commend not allowed>" in flashtool
can someone help me?
thanks
alvind27 said:
i have problem when trying to unlock the bootloader. it says "failed <remote: commend not allowed>" in flashtool
can someone help me?
thanks
Click to expand...
Click to collapse
IS bootloader unlock allowed : yes ?
Go to calls,enter *#*#7378423#*#* and go to service info-configuration
angelus-95 said:
IS bootloader unlock allowed : yes ?
Go to calls,enter *#*#7378423#*#* and go to service info-configuration
Click to expand...
Click to collapse
yes, I already check it at first and it say "yes"
i search in google there's no answer too for this. i really really need to root my phone because i'm running out of internal memory
Same issue with alvind27
Same issue as alvind27 has there been a fix yet.
my model is the same as yours
Works fine with my 2303
Great tutorial. Thank you so much. I forgot many things since someone has stolen my Xperia S. Root revived this phone. Android 6 + root is great future but now I am happy with that, too.
Working on my E2303. If someone has problem then he/ she has to learn more about it. Just follow steps slowly and everything is gonna be fine.
I had the same problem but also on windows 10, flashed in a windows 8 computer without any major issues.
I have a problem. Me appears seen, how can I fix?
C:\Flashtool\x10flasher_lib>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device unauthorized. Please check the confirmation dialog on your device.
C:\Flashtool\x10flasher_lib>adb reboot bootloader
C:\Flashtool\x10flasher_lib>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (32650 KB)...
OKAY [ 1.032s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.032s
Click to expand...
Click to collapse
Stuck at Bootloader Unlocking...
Hi, I have a problem here. I have the E2353 Xperia M4 Aqua and use the mac version of Flashtool
I've followed every step from checking whether or not the phone's BL can be unlocked (it is allowed) to putting all the necessary text files in the "mydevices" and "registeredDevices" folder. Problem is when I press and hold the VOL Down key and plug the USB in...nothing happens, it's just stuck there at the instructions screen while I keep holding the down volume key. I expected to see the Bootloader Unlock Wizard but it doesn't appear
Is there something I missed? What should I do?
Worked on e2363!
I managed to work on my E2363, though at the beginning I had problems and errors (when using fasboot to record TWRP.img got the error "unable to record the image").
In step 0, i got YES, but the error I mentioned persisted.
So did all the steps again (assuming in step 0 I would have gotten "no") and worked, the TWRP was recorded.
mikaaa6 said:
I have a problem. Me appears seen, how can I fix?
Click to expand...
Click to collapse
are you already unlock the bootloader first before flash recovery?
alvind27 said:
yes, I already check it at first and it say "yes"
i search in google there's no answer too for this. i really really need to root my phone because i'm running out of internal memory
Click to expand...
Click to collapse
what mean your bootloader say "yes"
check your bootloader again and maybe this can your answer
silencar said:
are u sure that it is unlocked? there are 3 kinds of status:
Bootloader unlock allowed: No - u can't unlock BL
Bootloader unlock allowed: Yes - u can unlock BL, BUT its not unlocked yet
Bootloader unlocked: Yes - BL is unlocked
Click to expand...
Click to collapse
sent from E2353 using bootloader
mufhm said:
are you already unlock the bootloader first before flash recovery?
I did every step to unlock the bootloader without any error, however Rooting Status spent UNAVAILABLE
Click to expand...
Click to collapse
1-step
in order to root these qilive devices you will need...
magisk manager apk v5.6.4
stock boot.img file
working ADB to unlock oem and flash
2-step
lets get to it
place the magisk.apk and the stock boot.img
in the internal memory of your phone (downloads)
if you like to keep stuff organized :good:
3-step
follow the vídeo tutorial and use magisk manager
to patch your stock boot.img it will output a new
boot.img that includes magisk Root (patched_boot.img)
https://www.youtube.com/watch?v=BF4_hnKgjFA
ps: major ty to hovatek team for this great tutorial
step-4 use Google drive or usb OTG to get the patched_
boot.img to your PC and place it in the ADB folder
once you have oem(bootloader) unlocked just
rename the patched_boot.img to boot.img
step-5
unlock oem, these qilive devices wont unlock
the bootloader even if you enable it in DEV options
enable USB debug in dev options
you will need to use ADB commands
command- adb devices
serial appears
command- adb reboot bootloader
phone reboots to fastboot mode
command- fastboot devices
serial appears
command- fastboot oem unlock
(MAJOR WARNING the fastboot
oem unlock will wipe/reset/factoryreset/delete your data)
after you give the command small letters will appear
on the phone screen(yes or no) hard to read dont be hasty plz
use VOLUME+ to select and VOLUME - to confirm
note: when my phone ended the unlock it whent back to
that black screen where you choose fastboot-recovery-restart
and was stuck there, side keys did nothing if this happens
just long press the power key for 10 sec it will shutdown
then press power again to turn on
first boot after unlock will take longer then normal dont freakout
after you unlock small letters will appear during boot up saying the device
is not safe unlocked ,you can later use ( fastboot oem lock )
step-6
flash the patched boot.img with ADB
command- adb devices
serial appears
command- adb reboot bootloader
phone reboots to fastboot mode
command- fastboot devices
serial appears
command- fastboot flash boot boot.img
finished/ok
command- fastboot reboot
and voila you should now have magisk
installed in the app drawer, open it!!
step-7 run the install one final time from the
magisk manager and install magisk V16 using
recomended option it will verify/patch the boot image
Do NOT select the AVB 2.0 BOX it will bootloop the phone
and your done, enjoy your qilive rooted phone.
from this point on you can use the fastboot
command- fastboot oem lock
to remove the letters in boot up about the
device not safe unlocked
WARNING oem lock
will WIPE/FACTORY RESET again (god damn it!!)
ps: i had to install twice in a row,major pain in the ....
Repeat step 7 after Wipe/Reset
here is the stock boot for 2 qilive models
you can get the stock firmware for any qilive
at this site www.doc-doapi.com/EM/qilive/smartph...te_3m-fdd-cs_mul_20170818-110645_songlixin_PC
and get the recovery or boot from the unpacked firmware file
ps:my phone is the Q8SIN4GP AND ITS WORKING FINE
A VERY SPECIAL TY to topjohnwu (magisk creator), this man is nothing
short of a God damn genius!! , and if you can donate to him.
hope this helps other qilive users to root:highfive:
quick note on the qilive models, they have two model names
the cliente name in my case Q8SIN4GP
and the factory name in my model its 882912
in order to download the right firmware for your model
you need the factory model witch is what appears in the qilive
site above, it will be in the back of the phone or the original
box on a sticker just bellow the bar code, full model exempl
:Q8SIN4GP/882912 my firmware serves several models,
these Q8 models all start with 88xxxx WARNING
dont try this using the wrong firmware/boot file or you will DAMAGE your phone
Help with BOOTLOOP problems, if you find your self stuck in a bootloop
the phone wont go past the qilive logo and just stays there, dont freak out
you will loose your data but there is a way out
just keep pressing power + Volume up until a black screen with 3 options appears
when it does let go, use Volume + to select option and Volume - to confirm
select Fastboot or alternative select recovery and then select reboot to bootloader
both option will place your phone in Fastboot mode, once in fastboot mode
connect your phone to PC and use ADB commands to fix/bootloop
command- fastboot devices
serial appears
command- fastboot oem unlock (skip this if you use phone unlocked)
a confirm action option appears on the phones screen
use Volume up to say YES / or Volume Down to say NO
Warning oem unlock will WIPE/Factory reset your phone
once it finishes the phone will be stuck on the
Recovery/fastboot/restart screen just long press the power key
until the phone shuts down
start the phone again using Power + Volume up when the black
screen with the 3 options come up, let go and use Volume up to
select Fastboot mode and confirm using Volume Down
Once in fastboot connect your phone to PC and use ADB commands
command- fastboot devices
serial apears
Here you will flash the magisk patched_boot.img
the same image you used to root your phone
command- fastboot flash boot boot.img
it will say finished-ok (or similar)
command- fastboot reboot
the boot up time will be longer than normal
but the phone should now complete the boot
and present the inicial setup screen, select language
enter your mail, the usual bla bla...
any way at this point just repeat step 7
to get root running again
sp flash tools v5.1716.
phonedriller said:
1-step
in order to root these qilive devices you will need...
magisk manager apk v5.6.4
stock boot.img file
working ADB to unlock oem and flash
2-step....
Click to expand...
Click to collapse
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
xdacktheresianum said:
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
Click to expand...
Click to collapse
Awsome work congrats, as for the recovery so far no luck so try not to go 2 crazy until a working recovery is up and working , install stericsons busy box this is always the first root app i install
If possible buy sterics busybox pro and titaniumbackup pro if you want to install apps to sd card apps2sd pro all of these can be tested in free
Version,again nice work congrats enjoy you rooted phone :highfive:
xdacktheresianum said:
Hi phonedriller,
phew, I did it! (Q8S55IN4G2), thanks.
Next step: Have you found a compatible custom recovery? (especially for nandroid backups and for xposed installation)
Would be very thankful for your help!
thanks
xdatheresianum
Click to expand...
Click to collapse
give a hungry man fish and you solve his problem for a day or two
teach him how to fish and you solve his problem for life
phonedriller said:
give a hungry man fish and you solve his problem for a day or two
teach him how to fish and you solve his problem for life
Click to expand...
Click to collapse
hi phonedriller,
...well, i must have been an unlucky fisherman
an app i installed ended up giving me a soft brick (bootloop between qilive icon opening screen - btw still with the "warning" of "device is unsafe etc", i.e. oem still open - and black screen, qilive opening screen etcetcetc)
have cleaned cache; went for factory reset; etc
BUT: am presently stuck when trying to go via ADB (which used to work perfectly before) that somehow the usb drivers don't want to get installed properly. as a consequence, desktop cannot see devices.
and i cannot, for the sake of me, remember how i had succeeded before installing usb drivers.
could you please help?
thx
cktheresianum
xdacktheresianum said:
hi phonedriller,
...well, i must have been an unlucky fisherman
an app i installed ended up giving me a soft brick (bootloop between qilive icon opening screen - btw still with the "warning" of "device is unsafe etc", i.e. oem still open - and black screen, qilive opening screen etcetcetc)
have cleaned cache; went for factory reset; etc
BUT: am presently stuck when trying to go via ADB (which used to work perfectly before) that somehow the usb drivers don't want to get installed properly. as a consequence, desktop cannot see devices.
and i cannot, for the sake of me, remember how i had succeeded before installing usb drivers.
could you please help?
thx
cktheresianum
Click to expand...
Click to collapse
PS: adb will not work if the phone is not booting to the OS
it will work if you manualy place the phone in fastboot AKA bootloader
MODE ,you see if it does not boot to OS then usb service is not working
use power + Volume up to enter the black menu
use the Volume up to select fastboot(bootloader) volume - to confirm
connect the phone to your PC
flash the boot.img, the same boot.img used to root (patched by magisk)
to see is adb is ok just run - fastboot devices
if a serial is presented then all other stuff should work
step 1 - reflash the boot img
step 2 - after the flash finishes - fastboot oem lock
message on the phone screen, confirm yes to lock
OEM
step 3- press power until it turns off
it should now complete the start up (boot)
if not working this method let me now
you can still flash the full factory firmware
using SP Flash Tool v5.17xx
phonedriller said:
PS: adb will not work if the phone is not booting to the OS
it will work if you manualy place the phone in fastboot AKA bootloader
MODE ,you see if it does not boot to OS then usb service is not working
use power + Volume up to enter the black menu
use the Volume up to select fastboot(bootloader) volume - to confirm
connect the phone to your PC
flash the boot.img, the same boot.img used to root (patched by magisk)
to see is adb is ok just run - fastboot devices
if a serial is presented then all other stuff should work
step 1 - reflash the boot img
step 2 - after the flash finishes - fastboot oem lock
message on the phone screen, confirm yes to lock
OEM
step 3- press power until it turns off
it should now complete the start up (boot)
if not working this method let me now
you can still flash the full factory firmware
using SP Flash Tool v5.17xx
Click to expand...
Click to collapse
dearphonedriller,
thank you so much for your speedy help.
followed the steps given by you. all is well, as you predicted, until step 3.
however:
phone (now without the "orange state" message, i.e. oem locked) still bootloops and short of ADB "fastboot devices" the desktop doesn't see the phone (and driver installation continues to fail), as per your PS (thanks!) i guess flashing the full factory firmware ("RC-mt6737...zip" quoted by you in your very first post) is next.
would you please point me to a basic-for-noobs tutorial or instruct me on the step-by-step commands/procedures using this zip file?!
HUGE thanks
ckth
xdacktheresianum said:
dearphonedriller,
thank you so much for your speedy help.
followed the steps given by you. all is well, as you predicted, until step 3.
however:
phone (now without the "orange state" message, i.e. oem locked) still bootloops and short of ADB "fastboot devices" the desktop doesn't see the phone (and driver installation continues to fail), as per your PS (thanks!) i guess flashing the full factory firmware ("RC-mt6737...zip" quoted by you in your very first post) is next.
would you please point me to a basic-for-noobs tutorial or instruct me on the step-by-step commands/procedures using this zip file?!
HUGE thanks
ckth
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=-zaEmj3-prU
turn the phone off, follow the video
flashing the full firmware is actualy easy
https://forum.hovatek.com/thread-13970.html
or searh sp flash tool here on xda
https://www.youtube.com/watch?v=LzyYXAflmOk&t=125s
phonedriller said:
https://www.youtube.com/watch?v=-zaEmj3-prU
turn the phone off, follow the video
flashing the full firmware is actualy easy
https://forum.hovatek.com/thread-13970.html
or searh sp flash tool here on xda
https://www.youtube.com/watch?v=LzyYXAflmOk&t=125s
Click to expand...
Click to collapse
thank you, phonedriller
everything worked perfectly via SPFlash Tool.
and, referring back to our above questions re the possibility of getting TWRP onto the phones, a developer friend of mine writes me this:
>try to flash TWRP:
>Download following files from this link:
>https://mega.nz/#F!qZIgnJRK!5apBfYo1je0ytg-wmA6JMQ
>- Odin3 v3.12.3 (Complete folder)
>- twrp-3.2.1-0-Q8S55IN4G2-20180318.tar
>1. Start your Phone into download mode
>2. Start Odin (Odin3 v3.12.3\Odin3.exe)
>3. Click on Options and unmark Auto Reboot
>4. Click AP and select twrp-3.2.1-0-Q8S55IN4G2-20180318.tar
>5. Press Start and wait until finished (Reset or OK!)
>6. Restart your phone immediatly to recovery mode
>7. In TWRP Recovery click on mount
>8. Set the checkbox checked at system (that system is mounted)
>9. go back and click on advanced
>10. Open file manager
>11. navigate to system/build.prop and click on build.prop
>12. Click on chmod
>13. type: 0644 and hit the accept button on screen or at the virtual
>keyboard on your phone
>14. restart your phone
i haven't tried this, but am wondering whether it might seem "reasonably possible" when reading through it.
thanks
ckth
Do you perhaps have link to Q8S5IN4GP stock rorm? Mine came with malware installed on it. I want to see if those were chinese who preinstalled or or was it decided by Auchan.
tommo1982 said:
Do you perhaps have link to Q8S5IN4GP stock rorm? Mine came with malware installed on it. I want to see if those were chinese who preinstalled or or was it decided by Auchan.
Click to expand...
Click to collapse
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
phonedriller said:
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
Click to expand...
Click to collapse
I had issues with adds being displayed at home screen and I was not able to close them. I had to use NetGuard to find that FOTA talks to 'adsup' and it is a known malware provider. I learned that some of the system apps try to talk with Alibaba servers and AdOppo (whatever it's called). Kaspersky might not be wrong, actually.
I'm trying to download stock firmware, but I don't know the file name. The website with it is locked, so unless I know exactly what I need, I cannot download it.
phonedriller said:
On my phone it came from factory and on the firmware file on 2 models , however only kasperky complains about malware on an system app called Helper bla bla bla i think its a false positive(i think) as no other antivirus or playstore ever found anything,but hey better investigate and be safe then sry right :good: maybe a ported cyanogen rom, ive look at a few rom port tutorials but my knowhow is limited + dont even have a working twrp yet, avg/avast/malwarebytes and a few others ,only kaspersky detects malware.
Click to expand...
Click to collapse
Yes i noticed the site now asks for a login that i dont have,but it was open to all until recently i have the firmware file in my pc,a few days ago i went to check for firware updates and the site was diferent and closed , in the site the download link was 882912/****** this firmware services at least 3 similar models
phonedriller said:
Yes i noticed the site now asks for a login that i dont have,but it was open to all until recently i have the firmware file in my pc,a few days ago i went to check for firware updates and the site was diferent and closed , in the site the download link was 882912/****** this firmware services at least 3 similar models
Click to expand...
Click to collapse
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
phonedriller said:
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
Click to expand...
Click to collapse
Ps use root + apps2sd or titaniumbackup to stop/disable the bad apps and replace them with playS app,not possible on all apps of course
phonedriller said:
I guess the best thing would be a lineage or cyanogen ported rom(clean),ps i flashed the phone 2 times because of popups/adds and battery drain,however im aware that having root and installing tones of crasy stuff can fu.. Up any phone cheap or flagship,thus the firmware flashes,i discovered that having malwarebytes(premium)free for 30days keeps the phone clean and working fine,it seems that one is forced to buy from a main stream brand or risk this kind of thing,little to no support,no updates at all,bad security,the problem is certain apps if removed resoult in boot loop like this Helper app
Click to expand...
Click to collapse
I'm thinking about Android 8.1 with it's Treble project. I might not be knowledgable enought to compile and flash it, though.
tommo1982 said:
I'm thinking about Android 8.1 with it's Treble project. I might not be knowledgable enought to compile and flash it, though.
Click to expand...
Click to collapse
Flashing is super easy use spflashtools or. Odin compiling a Rom is not , were you able to get the original firmware? You will need the original firware to get the boot and partition info from what i read so far
Unfortunately not. I will ask at the shop where I bought it how to contact tech. It should be freely available. I don't understand why Qilive restricted access to firmware.
I'll post when I learn anything.
Well, you can download the firmware if you know the file name. The bad news is, it seems the stock firmware has malware preinstalled. If there is anyone who could help confirm it. I have the ROM, and I can upload it to Google Drive if needed.
Hi all,
I'm coming back to a question lingering since the very first post here and mentioned again in post #9:
Is there a successful way to install TWRP on this Qilive model?
Re this topic:
- has anybody tried/has anybody been successful with the procedure described in post #9?
and
- has anybody seen the following TWRP builders' version (do an in-page search on Q8S55IN4G2)
https://twrpbuilder.github.io/fr/downloads/twrp/
with the download belonging to it
https://androidfilehost.com/?fid=890129502657591798
???
any successful installations to report???
Wouldn't THAT be great!!??
thanks
xdack
Hi,
I'm quite new to the world of custom roms and I would appreciate some help to get my z3 tablet working again. I wanted to install this ROM as my Z3 was still running on Lollipop with no update in sight.
I managed to unlock the bootloader following the instructions from Sony's homepage and I was able to flash TWRP using the version provided in the thread linked above. Unfortunately now I can neither boot into recovery nor do anything else with the tablet except start the fastboot mode (solid blue light after holding power up and connecting the power cable).
Is there any whay to start TWRP? Did I use the wrong image? I'm on Windows 7 64-bit. Thank you for your help!
I used this solution to get out of the very same situation on my SGP611.
If your tablet is soft bricked, stuck at boot, restart display SONY and keep restarting you can do the bellow steps, but after that you will need to root and install TWRP again.
To turn off your tablet which is keep restarting, press and hold POWER and VOLUME UP until the tablet vibrates 3 times and turns off.
On your PC open Sony Xperia Companion, click Software repair, check My device cannot be detected or started, Next, chose Xperia phone or tablet, Next, check I know my Google credentials, wait until instruction are displayed how to connect to your PC.
Make sure your tablet is turned off, press and VOLUME DOWN while connecting the USB cable to PC, when the program starts the next step you can release the VOLUME DOWN.
Now wait and do not disconnect the tablet from PC.
Hi, I used Lightheadeds link and I managed to install the stock rom that way. I also tried luk71s solution but Xperia Companion did not work because my tablet has an unlocked bootloader.
Many thanks, I now have a working tablet again!!!
Hello everyone. I have the same problem. I just changed from my Z2 tablet to a Z3 Tablet compact. Unlocked boot loader but I can not install twrp using ADB or Flash to update to oreo.
I don't even have the oem unlock under developper status.
I will be gratefull for any help
Thanks
dsman said:
Hello everyone. I have the same problem. I just changed from my Z2 tablet to a Z3 Tablet compact. Unlocked boot loader but I can not install twrp using ADB or Flash to update to oreo.
I don't even have the oem unlock under developper status.
I will be gratefull for any help
Thanks
Click to expand...
Click to collapse
Since you already unlocked your bootloader it makes sense that you do not have an OEM unlock option. In developer settings you must enable USB debugging and reboot in bootloader mode to flash twrp. What happens if you send the command 'fastboot devices'?
Thanks for replying my Sos.I did not have the unlock oem optoon before unlocking the bootloader. When I write adb devices the computer sees it in normal mode but does see the tablet in fastboot mode.
dsman said:
Thanks for replying my Sos.I did not have the unlock oem optoon before unlocking the bootloader. When I write adb devices the computer sees it in normal mode but does see the tablet in fastboot mode.
Click to expand...
Click to collapse
I checked my tablet and it has no OEM unlock option either, so maybe it is simply not implemented. This means you should be able to unlock.
To see your tablet in fastboot mode you must install the correct drivers on your PC. For me the easiest way was to install Flashtool from www.flashtool.net. It has an option to install drivers and it is also useful if you want to go back to stock. You may also want to backup your TA partition if you consider returning back to a pristine state.
Suite
M1chiel said:
I checked my tablet and it has no OEM unlock option either, so maybe it is simply not implemented. This means you should be able to unlock.
To see your tablet in fastboot mode you must install the correct drivers on your PC. For me the easiest way was to install Flashtool from www.flashtool.net. It has an option to install drivers and it is also useful if you want to go back to stock. You may also want to backup your TA partition if you consider returning back to a pristine state.
Click to expand...
Click to collapse
I have wiped off everything from the Tablet it's mega clean but i really want to remove all bloatware and instal a better rom. have already installed fashtool but once I am in fastboot mode ( Blue light) there is no communication with computer.
I have installed the correct driver
Checked in the devices settings it there is no Triangle
Checked the s1 driver , the Z3 tablet compact driver No triangle.
Sony companion regognises the Tablet
But when in Fatsboot mode, there is no communication.
Heeeeeeelp and thanks to all the developpers and other testers
dsman said:
I have wiped off everything from the Tablet it's mega clean but i really want to remove all bloatware and instal a better rom. have already installed fashtool but once I am in fastboot mode ( Blue light) there is no communication with computer.
I have installed the correct driver
Checked in the devices settings it there is no Triangle
Checked the s1 driver , the Z3 tablet compact driver No triangle.
Sony companion regognises the Tablet
But when in Fatsboot mode, there is no communication.
Heeeeeeelp and thanks to all the developpers and other testers
Click to expand...
Click to collapse
You may have to disable driver signature verification: https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Also close Sony Companion and Flashtool if you run the fastboot commands.
Z3 Tablet Root
M1chiel said:
You may have to disable driver signature verification: https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Also close Sony Companion and Flashtool if you run the fastboot commands.
Click to expand...
Click to collapse
Ok i'll do that and will keep you posted
Z3 tablet Root 2018
So I finally managed to root my lovely and Tiny Tablet. Info those interested.
Step by Step. My machine Windows 10 Pro 1803 : Did not work with this computer and changed on a second one Same windows Pro 1803
that does not mean it will not work on yours)
Phone is Z3 Tablet Compact with Marshmallow.
A On Computer
1 Installed Flashtool 64
2 Installed ADB FlashTool 5contains drivers also)
3 Installed Phones Driver (it may be included with Flash tool)
4 Installed Sony Flashtool
5 Unlocked Bootloader with Flashtool or Go to Sony's Site to obtain Unlockboot loader Code. Sorry Too long to explain ( I used Flashtool)
6 Downloaded SGP621_23.0.1.A.0.167_CE.ftf or other Firmware that fits you xperia device with Sony Flashtool :: ATTENTION This downgraded my phone to Android 5 Lollipop.
ON Phone
If you are here, you already know that you have to unlock your Developper mode, Allow Debbuging mode, Allow mock locations, Go to de security option and allow Unkown sources.
1 Installed Kingroot 4.50 (Install it even if Google says it may be dangerous)
2 Ran Kingroot 4.50 IT IS NOT the latest but it worked for me on Android Lollipop. (I had tried the lastests versions of Kingroot, Kingoroot, and other it did not work on Marshmallow and it did not work for me)
It did not work the first time. SO i tried a second time as proposed and it then worked.
2 bis I rebooted verified with a root checker afterwards: Rooted Yeeeeeeeeeeeeeeeeees
3 Then downloaded Root checker, Titanium Backup, Rom Manager, Official TWRP,SuperSU,Busy Box
4 Once rooted, I removed purify that came with Kingroot and other bloatwares and Installed the above apps. You don't have to do it but that is what I did.
As from here, you choose what you want to do. You are FREE to debloat and install what you want.
I will like to thank all the developpers on this site and thoses who a have showed my ways to find a solution. It is not always clear. But atleast they have tried.
So I am transmitting my experience for others.
Second stage finding the best Nougat or Oreo setup for me in a week or two.
Have a nice day
I was trying to flash lg-k350n with LineageOs and make a whole bunch of idiotic deeds, so currently I'm felling like dying is the best option for me.
1. I've used this tutorial: .getdroidtips.com/install-custom-rom-using-twrp-recovery. It clearly says that this ROM is for Android 8.0 Oreo, while mine is Android 6.0 Marshmallow. Nevertheless I've downloaded ROM lineage-15.0-20170913-Unofficial-MT6735-64-bit.zip. For some reason TWRP mentioned here getdroidtips.com/lineage-os-15-lg-k8-8-0-oreo/ did not wok for me but I've googled a bit and found something called TWRP-recovery-for-LG-K8.img which worked (not by fastboot flash TWRP-recovery-for-LG-K8.img since this TWRP appeared to be to big but simply by fastboot boot TWRP-recovery-for-LG-K8.img).
So I just did:i
turn on debugger
turn off oem lock
adb boot bootloader
fastboot boot TWRP-recovery-for-LG-K8.img
Feeling happy that TWRP loaded nicely I had not done any backjup and just wiped system as suggested here: lineageos.org/devices/h990/install. Then I've tried to installl the Android 8..0. ROM with obviously did not work. And I've got left with a TWRP working and then I've put the last needle in my coffin - I've rebooted hoping that some hard reset or recovery will fix things for me.
So now I have a phone which I'm able to put to recovery, but it does not recover anything. The phone just go dead after such a recovery.
I cannot put it into fastboot mode, if I could, I would just run 'fastboot boot TWRP-recovery-for-LG-K8.img' and at least had a chance to google a bit for maybe a vanilla ROM or anything working, which I could've later installer.
I've seen that there is a way to put the phone into download mode when it will download stuff from S/W "LG Bridge", bu I don't have Windows and haven't yet tried in virtualbox.
Is there any way to unbrick the device? Please help an idiot!
Sorry, you have to find a Windows box I'm afraid, LG is only offering Windows software for flashing. But chances are quite good that you are able to revive the telephone that way. I have bricked my phone as well but was able to unbrick it this way:
Go to www.lg.com, choose your language, select download, software and firmware.
Select smartphone, Android smartphones, K-series and your model number. This is only to come to the download site of LG Bridge, I guess it's not really important to choose the precise model!
Download LG Bridge, install and start it.
Let it update itself and the USB drivers and keep the software running.
Switch off the phone, press Volume up and keep holding that button.
Connect the phone with via USB with the PC while still pressing Volume Up. The phone should be recognized by the PC (install USB driver) and by LG Bridge (watch the status line to the left, it should show the phone type and USB)
The phone should automatically switch on and show a download screen (yippee!)
Select the second tab "software update" and then click on "correct update error" in the lower right. It should automatically download the correct firmware from the internet, so this is rather fool proof!
Click through it and this should start the flashing process, at the end the phone will automatically reboot, ask for the PIN, etc.
Unbricked!!!
Above instruction worked for me on a completely demolished phone. Lineage OS, changed FS, root attempted, I almost though that's it, but no, it recovered, thumbs up.
I haven't tried in Virtual Box, so I cannot tell if this is working. But you've got nothing to loose, right, so why not try it?
xor512 said:
I was trying to flash lg-k350n with LineageOs and make a whole bunch of idiotic deeds, so currently I'm felling like dying is the best option for me.
1. I've used this tutorial: .getdroidtips.com/install-custom-rom-using-twrp-recovery. It clearly says that this ROM is for Android 8.0 Oreo, while mine is Android 6.0 Marshmallow. Nevertheless I've downloaded ROM lineage-15.0-20170913-Unofficial-MT6735-64-bit.zip. For some reason TWRP mentioned here getdroidtips.com/lineage-os-15-lg-k8-8-0-oreo/ did not wok for me but I've googled a bit and found something called TWRP-recovery-for-LG-K8.img which worked (not by fastboot flash TWRP-recovery-for-LG-K8.img since this TWRP appeared to be to big but simply by fastboot boot TWRP-recovery-for-LG-K8.img).
So I just did:i
turn on debugger
turn off oem lock
adb boot bootloader
fastboot boot TWRP-recovery-for-LG-K8.img
Feeling happy that TWRP loaded nicely I had not done any backjup and just wiped system as suggested here: lineageos.org/devices/h990/install. Then I've tried to installl the Android 8..0. ROM with obviously did not work. And I've got left with a TWRP working and then I've put the last needle in my coffin - I've rebooted hoping that some hard reset or recovery will fix things for me.
So now I have a phone which I'm able to put to recovery, but it does not recover anything. The phone just go dead after such a recovery.
I cannot put it into fastboot mode, if I could, I would just run 'fastboot boot TWRP-recovery-for-LG-K8.img' and at least had a chance to google a bit for maybe a vanilla ROM or anything working, which I could've later installer.
I've seen that there is a way to put the phone into download mode when it will download stuff from S/W "LG Bridge", bu I don't have Windows and haven't yet tried in virtualbox.
Is there any way to unbrick the device? Please help an idiot!
Click to expand...
Click to collapse
same here, we are two now.
Don Pedro! said:
Sorry, you have to find a Windows box I'm afraid, LG is only offering Windows software for flashing. But chances are quite good that you are able to revive the telephone that way. I have bricked my phone as well but was able to unbrick it this way:
Go to www.lg.com, choose your language, select download, software and firmware.
Select smartphone, Android smartphones, K-series and your model number. This is only to come to the download site of LG Bridge, I guess it's not really important to choose the precise model!
Download LG Bridge, install and start it.
Let it update itself and the USB drivers and keep the software running.
Switch off the phone, press Volume up and keep holding that button.
Connect the phone with via USB with the PC while still pressing Volume Up. The phone should be recognized by the PC (install USB driver) and by LG Bridge (watch the status line to the left, it should show the phone type and USB)
The phone should automatically switch on and show a download screen (yippee!)
Select the second tab "software update" and then click on "correct update error" in the lower right. It should automatically download the correct firmware from the internet, so this is rather fool proof!
Click through it and this should start the flashing process, at the end the phone will automatically reboot, ask for the PIN, etc.
Unbricked!!!
Above instruction worked for me on a completely demolished phone. Lineage OS, changed FS, root attempted, I almost though that's it, but no, it recovered, thumbs up.
I haven't tried in Virtual Box, so I cannot tell if this is working. But you've got nothing to loose, right, so why not try it?
Click to expand...
Click to collapse
your phone cannot be trusted loooooop, cannot goto download and fastboot mode...
If you don't manage to enter download mode you have probably indeed bricked the phone. If what I've written above doesn't work for you I know of no other way to resurrect it, sorry.
This is because you cannot burn TWRP to the Flash plus there's no tool available to bootstrap an LG phone with a completely naked or corrupted Flash. There must be something like that, because a freshly manufactured phone has by definition a naked Flash.
With Samsung phones you have Odin and with it it is possible to burn a software to a completely dead phone. So it is almost impossible to hard brick it. With LG unfortunately it is different. Plus this phone is somehow crippled, it has only a very, very limited amount of Flash. So I would recommend to not care for this phone anymore, it's not worth it, and instead get a current one with a decent amount of memory.