Related
Greets, I am a long time XDA reader with deep rooting and flashing experience (phones dude, phones) from Samsung Galaxy S I9000 and Sony Xperia Z (yuga).
I have here a LG G2 D802T that I have no experience on, and the touch screen don't work due to dropping and screen cracking.
The phone powers on and off OK, boots fine. The screen works fine, but no response when touched.
I need to:-
- find out how to boot to recovery
- enable developer access
- enable adb access
- enable k.janku1's awesome tool http://forum.xda-developers.com/showthread.php?t=2786395
So I need to install a recovery and/or the correct stock compatible kernel (4.4.2) i think. adb access in recovery would be great for a start.
I already have LGUnitedMobileDriver_S4981MAN38AP22_ML_WHQL_Ver_3.8.1.exe installed on my Windows, but no response from phone when I plug in USB cable. I also speak Linux.
I am just starting to read the G2 forums, but id appreciate any tips and pointers from you fine folks.
Hello, I've tried posting my problem elsewhere on xda without response so I'll give it a try in here. My phone shows the sony logo then reboots infinitely after rooting it and I searched everywhere for a solution but all I could do is get this message on flashtool:
06/056/2015 17:56:00 - INFO - Loader : S1_Root_2f8b - Version : MT6582_15 / Boot version : S1_Boot_MT6582_TC9SP_11 / Bootloader status : ROOTED
06/056/2015 17:56:00 - INFO - Transfer buffer size : 262144
06/056/2015 17:56:01 - INFO - You must have the according fsc script to flash this device.
06/056/2015 17:56:01 - INFO - Flashing finished.
06/056/2015 17:56:01 - INFO - Please unplug and start your phone
06/056/2015 17:56:01 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
It should be a driver problem but I have already installed adb drivers, specific drivers for e4 from sony website and flashtool, fastboot and jdm drivers from flashtool. I also tried switching usb ports and trying on other computers with the same results, and I'm 100% sure unknown sources and debug mode were checked last time the phone was in working condition.
I tried installing all drivers from flashtool's driver folder as well, still nothing. I dunno if it's relevant but the device is recognized as somc flash device in device manager. I'm using flashtool 0.9.19.0 as I read somewhere it works better for the e4 dual (even if it doesn't for me) and the latest version gives an IO exception error.
Any expert who can help me with the problem?
Edit: Bootloader is unlocked but the problem was the same before unlocking
Is there really no way of fixing my phone? Please help. . .
Anyone?
Can someone enlighten me? Now the battery is dead too... phone won't charge anymore.
ZeroJoe said:
Can someone enlighten me? Now the battery is dead too... phone won't charge anymore.
Click to expand...
Click to collapse
too bad i didn't see this thread previously.
hello friend,
I too have the same problem now.
i tried to change the build .prop and ended in bootloop today.
i have a similar message
"16/028/2015 15:28:57 - INFO - Please connect your device into flashmode.
16/029/2015 15:29:08 - INFO - Device disconnected
16/029/2015 15:29:13 - INFO - Bootloader unlock canceled
16/029/2015 15:29:50 - INFO - Device connected with USB debugging off
16/029/2015 15:29:50 - INFO - For 2011 devices line, be sure you are not in MTP mode"
I tried to change the usb debugging settings through adb ,it is not working.
the internal storage and sdcard are not mounting. :crying::crying:
I think we will have to get help from sony support and the thread Xperia E4 Development by LeonXperiaXC
Did you try out the sony pc companion ? it is supposed to work as my device has a locked boot loader . but it is not working either.
dushandiaz said:
Did you try out the sony pc companion? it is supposed to work as my device has a locked boot loader . but it is not working either.
Click to expand...
Click to collapse
Yes I did that, device not supported, and that was even before I unlocked the bootloader.
I gave up fixing it some days ago, seeing that neither sony nor xda helped, and I can't afford a new one for now. Please let me know if you do manage to fix it, as I will check here from time to time, good luck to you.
ZeroJoe said:
Yes I did that, device not supported, and that was even before I unlocked the bootloader.
I gave up fixing it some days ago, seeing that neither sony nor xda helped, and I can't afford a new one for now. Please let me know if you do manage to fix it, as I will check here from time to time, good luck to you.
Click to expand...
Click to collapse
As i couldn't fix the device,I gave the phone to the service center.they had fixed it .I will be getting the device on moday. :fingers-crossed:
By the way,i found some interesting fact why unbricking didn't work for our E4.
sony pc companion unbricked my previous device xperia E1,it is a snapdragon device.
I think mediatek devices can't be unbricked by sony pc companion and also flashtool by androxyde.
Xperia C cannot be unbricked by the both as well.it is a mtk 6589 device.
Xperia C has an unbrick method using a tool/software called WMshua perfect flash.
https://www.informationlord.com/ultimate-guide-to-fix-bricked-xperia-c/
I didn't try it because i was scared of hard bricking the device.
I think it might work.
plus for chinease mediatek devices there is another tool called spflashtool.
also learn to use the spflashtool .there is a begineers guide at mtkroms.com
http://www.mtkroms.com/2015/02/how-...howComment=1447795342637#c6494565355265496004
give it a try.
If you have warranty definitely get it repaired by the service center.
or try the above methods if you have no choice.
I hope you will get your device working as soon as possible. :good::good::good::fingers-crossed::fingers-crossed::fingers-crossed:
Good luck.
ZeroJoe said:
Is there really no way of fixing my phone? Please help. . .
Click to expand...
Click to collapse
Did you try to restore with pc companion
1.Open back case and found OFF lockup using pen shutdown the bootloop
2.Open pc companion then support zone
3.click update my phone
4.click restore phone/tablet
5.then choose Sony Xperia E4 dual (E2115) because i connected
or if you not connected preess other phone/tablet then Choose E2115
6.after downloading firmware and getting ready
7.Make sure you have 80 % of charge
8.Start you phone in Flashmode PWR+VOL-
9.Wait
10.prrrrooooffffiiiiiitttt!!!!!!
AND NOTE SP FLASH TOOL NEVER FLASH SONY XPERIA WITH MTK EXPECT FAKES
Hi! I have sony xperia e4 E2105 and yesterday it went into bootloop. I tried to flash stock firmware but the version I have doesn't see the tft file so I downloaded older version of flashtool and it recogniznes tft file but when I try to flash it says that it can't open bundle . I dont have custom recovery .Please help me!
Thank you
Recently I have owned lenovo zuk 1
Then I try to unlock bootloader and root my device and get successful in this process and try some custom ROM's to make my handset with more interesting features ( thanx for the those developers who develop such ROM's , hat's to you guys) but after some weeks I try CM 14.1 , I messup with that process and got bricked device then I try to reflash that ROM , I have completed all processes very patiently , again and again I was ported to recovery ,not able to access my device. I became fed up with this then I leave my phone on customer care , after some days I get my zuk 1 with stock firmware
Now the main problem arises
Again I try to unlock my device
I have already install the adb and fastboot drivers and that working fine
I tried , adb devices
Its working
Then I try ,adb reboot bootloader
Its also working
But when I try , the script for unlocking bootloader
I get , { waiting for device }
Idk what's this happening
Lenovo USB drivers are property installed on my PC
Adb and fastboot drivers are also installed properly but I don't know ,what i am doing wrong
I think customer care ppls forcefully locked my bootloader that I can't able to root my handset in future
If anyone here to solve this issue ,ASAP
racker16 said:
Click to expand...
Click to collapse
Which commands you using for bootloader unlock?
strongst said:
Which commands you using for bootloader unlock?
Click to expand...
Click to collapse
fastboot -i 0x2b4c oem unlock- go
I was using right command
racker16 said:
fastboot -i 0x2b4c oem unlock- go
I was using right command
Click to expand...
Click to collapse
Without the space between oem and go?
fastboot -i 0x2b4c oem unlock-go
strongst said:
Without the space between oem and go?
fastboot -i 0x2b4c oem unlock-go
Click to expand...
Click to collapse
Yeah I have used this also but same ,
Waiting for device
racker16 said:
Recently I have owned lenovo zuk 1
Then I try to unlock bootloader and root my device and get successful in this process and try some custom ROM's to make my handset with more interesting features ( thanx for the those developers who develop such ROM's , hat's to you guys) but after some weeks I try CM 14.1 , I messup with that process and got bricked device then I try to reflash that ROM , I have completed all processes very patiently , again and again I was ported to recovery ,not able to access my device. I became fed up with this then I leave my phone on customer care , after some days I get my zuk 1 with stock firmware
Now the main problem arises
Again I try to unlock my device
I have already install the adb and fastboot drivers and that working fine
I tried , adb devices
Its working
Then I try ,adb reboot bootloader
Its also working
But when I try , the script for unlocking bootloader
I get , { waiting for device }
Idk what's this happening
Lenovo USB drivers are property installed on my PC
Adb and fastboot drivers are also installed properly but I don't know ,what i am doing wrong
I think customer care ppls forcefully locked my bootloader that I can't able to root my handset in future
If anyone here to solve this issue ,ASAP
Click to expand...
Click to collapse
in developer options (in settings) make sure both oem and usb debug are ON
CoreKido said:
in developer options (in settings) make sure both oem and usb debug are ON
Click to expand...
Click to collapse
Its already on that time
racker16 said:
Recently I have owned lenovo zuk 1
Then I try to unlock bootloader and root my device and get successful in this process and try some custom ROM's to make my handset with more interesting features ( thanx for the those developers who develop such ROM's , hat's to you guys) but after some weeks I try CM 14.1 , I messup with that process and got bricked device then I try to reflash that ROM , I have completed all processes very patiently , again and again I was ported to recovery ,not able to access my device. I became fed up with this then I leave my phone on customer care , after some days I get my zuk 1 with stock firmware
Now the main problem arises
Again I try to unlock my device
I have already install the adb and fastboot drivers and that working fine
I tried , adb devices
Its working
Then I try ,adb reboot bootloader
Its also working
But when I try , the script for unlocking bootloader
I get , { waiting for device }
Idk what's this happening
Lenovo USB drivers are property installed on my PC
Adb and fastboot drivers are also installed properly but I don't know ,what i am doing wrong
I think customer care ppls forcefully locked my bootloader that I can't able to root my handset in future
If anyone here to solve this issue ,ASAP
Click to expand...
Click to collapse
Buddy try this tool
http://forum.xda-developers.com/zuk-z1/orig-development/tool-toolzukz1eng0-0-3-mauronofrio-t3332563
[HELP] [URGENT]
//this is the story, skip if you prefer
so i was updating my cm 12.1 rom to rr 7.1 rom
everything was fine, no real mess just bad flash so i decided to reflash the rom (dunno why i did that actually, its just my tradition). Aaaaand the ROM went flawlessly
next step is install supersu, i checked that the rom is pre-rooted so i think its easier to get supersu via playstore. Installing supersu went flawlessly (again) and i rebooted ma phone.
//then everything starts to f***ed up
my phone bootlooped (not a big deal actually, done with this sh** all the time)
like a casual day, reflash my phone. but i cant go to recovery mode its stuck at logo i think that supersu binary damaged ma recovery.img (again not a big deal but i started to worry) i connect my phone to my pc, summon my adb, and hope the best, but my devices not listed there. then i remembered i forgot to turn on usb debugging on setting oh crap!
so here is my question:
is it possible to turn on usb debugging via pc or something else? if so how.
is it possible to use adb feature without my phone being turned on its usb debugging?
is it possible to repair my recovery <== i mean reflash beside using adb. if so how :crying:
and the last one, beside my phone not listed on adb device list. it wont showed or recognized in my pc (do i need something else beside usb and adb driver?)
any help will be appreciated :good:
this is my only phone so i put my hands on you guys, you're the superhero here
if i dont have any solution, my only way is send this phone to service centre :crying:
some info:
devices : lenovo a6k plus
old rom : cm 12.1 by ED300
new rom: rr nougat v5.8.0 (i dont remember who made this rom, sorry. by the way i found the rom somewhere in xda)
supersu ver: newest per 21 Feb 2k17 (playstore)
my pc: win 8 64x <== dunno if this info useful though
old recovey: twrp (forget the version, but im pretty sure the recovery made by russian developer and it has chicken logo during startup)
battery level when i discovered i cant go to recovery mode: somewhat near 16% <== maybe helpful
if you really care to help me just tell me what do you know, i would appreciate that really, i meant that because this phone is the only way i can contact all of my super important buddy for my business.
Thanks anyway, regards Tom
Well take out the battery and return it hold volum down + power button now you should be able to use fastboot commands go to the folder where you have your adb and fastboot there paste a recovery img file you want to use.Open cmd and type fastboot flash recovery nameofyourimg.img
And now you should be able to use recovery.If not try qfil debricking method that you can find on forum.Best of luck if somthing isnt clear enough feel free to PM me.Also download new recoveries that are now officialy developed
Thanks for replying JovanSijacki
unfortunate enough, i have done that and still dope and nope.
usually i can find my device in windows device manager named android with yellow triangle, but this one is different, my computer wont recognize my phone.
will try debricking method instead, thank you dude :smile:
Thank you for those who care to reply, friend of mine who are expert developer told me how to fix this. AS LONG AS YOU ABLE TO GET INTO FASTBOOT MODE YOU ARE SAFE. Im going to make separate thread to share the tutorial *insert smiley emoji*
Hi to all.
I landed on XDA because I am not able to hack my Asus Zenfone Laser 2 dual-sim (ZE550KL, which seems to be also called as Z00L or Z00LD... I don't know why... ?!? ). Actually I'm very new on smartphone hacking, so I did my best recently to understand what "rooting", "recovery", "brick" etc mean.
I tried to enter this world because my phone gets gradually very slow as I use it and so I supposed that erasing the pre-installed applications and overclocking it would help, possibly installing a lighter and more performing custom rom. In order to do this I read that in short I have to unlock the boot loader, root the phone and then eventually install a custom rom. In fact I suppose that getting root privileges should already do the job by keeping the original rom, unistall all unwanted apps and eventually overclocking it. Is that correct?
However, the problems I found on my way are the following two:
I've not been able to follow those procedures on Linux. In detail, I'm not able to use "fastboot boot" instruction because it gets stuck on "waiting for any device". The device is listed and allowed when running "adb devices", the boot had been unlocked previously, the phone is in debug mode etc... but the problem is still there despite I've been trying with both the adb package included in the repositries and the one downloaded from the related google page. I've been told it may be a matter of USB drivers, so I also installed the android studio package thinking it would help, but I was wrong. I'm quite confused on this, despite I do hope I can hack my phone using my favourite operating system (I'm a Linux user since 2006). If you do not feel like helping on this then I will try on Windows.
After trying the same procedures on Windows 10, I realised that the Android Usb drivers released by Google did not work. I had to install the proprietary ASUS USB Drivers from the official website and only then I was able to overcome on Windows the same "waiting for any device" I had experienced on Linux. However, the phone "bricks". I suppose this should be the technical term used in this field to tell that the phone gets stuck for hours on the boot animation. I tried several times to reboot it, but each time the same story.
Maybe the problem on Linux is that I do not have the proper Android Device Usb drivers installed. In this case, how to solve the problem taking into account that ASUS only released the drivers for Windows?
RECAP: I have my phone bricked now (Android is unable to reboot, but I can do access both to the Power+VolumeUP menu (by the way, what's the name of this menu? Fast boot?) and the Power+VolumeDOWN menu (by the way, what's the name of this menu? Recovery boot?)
So sorry for the long story.
Hope you can help.
Thanks for your attention and best regards.
Uhm... no replies till now?
i dont know how you get this kind of trouble, maybe try other computer? , im using wondows 10, download small package of of fastboot driver and adb driver, flash twrp using fastboot command. all done. then i make full backup using twrp, next flash magisk .now i have root access, any problem or bootloop i just restore the full backup that work.
---------- Post added at 04:53 PM ---------- Previous post was at 04:22 PM ----------
i see a lot of this zen2 laser got bricked on this general forum , you should read some more if that could help
When I had this device, I remember booting a temporary recovery TWRP and rooted it in that recovery. Then once I got rooted, I installed TWRP app and installed a permanent recovery from within the TWRP app, which needed root of course. Then I got everything working.
You can try booting on a temporary TWRP using fastboot then flash supersu or magisk or whatever rooting client you want. Though, I think you need an unlocked bootloader. I'm sure there's a guide around here somewhere
I'm using a Z00T and just installed LineageOS yesterday using Windows 10, following a guide by Android Authority and LineageOS.
Volume Up + Power = Fastboot
Volume Down + Power = Recovery
Sounds like you can get into Fastboot, so I'm wondering if maybe you can use it to flash the recovery image??? (I'm not a dev in any form; try this at own risk)
I'm assuming you unlocked the bootloader already...
In the directory where all your images are, perhaps try flashing the recovery with the following, where RECOVERY.img is whatever you may have renamed the TWRP image to be:
Code:
fastboot flash recovery RECOVERY.img
After it's finished flashing, turn off the phone, then reboot into recovery mode with Volume Down + Power.
Something Similar happened with my phone and looking for answer
Hi All,
I'm new to this but do some hands on reading these forums. Recently i don't know how but my phone continuously boot into Fast-Boot mode. If I try to push some zip file as mentioned i'm getting error related to partition. "failed to write partition."
Can someone help me out with this.
Thank in advance.
CerealKiIIel said:
Hi to all.
I landed on XDA because I am not able to hack my Asus Zenfone Laser 2 dual-sim (ZE550KL, which seems to be also called as Z00L or Z00LD... I don't know why... ?!? ). Actually I'm very new on smartphone hacking, so I did my best recently to understand what "rooting", "recovery", "brick" etc mean.
I tried to enter this world because my phone gets gradually very slow as I use it and so I supposed that erasing the pre-installed applications and overclocking it would help, possibly installing a lighter and more performing custom rom. In order to do this I read that in short I have to unlock the boot loader, root the phone and then eventually install a custom rom. In fact I suppose that getting root privileges should already do the job by keeping the original rom, unistall all unwanted apps and eventually overclocking it. Is that correct?
However, the problems I found on my way are the following two:
I've not been able to follow those procedures on Linux. In detail, I'm not able to use "fastboot boot" instruction because it gets stuck on "waiting for any device". The device is listed and allowed when running "adb devices", the boot had been unlocked previously, the phone is in debug mode etc... but the problem is still there despite I've been trying with both the adb package included in the repositries and the one downloaded from the related google page. I've been told it may be a matter of USB drivers, so I also installed the android studio package thinking it would help, but I was wrong. I'm quite confused on this, despite I do hope I can hack my phone using my favourite operating system (I'm a Linux user since 2006). If you do not feel like helping on this then I will try on Windows.
After trying the same procedures on Windows 10, I realised that the Android Usb drivers released by Google did not work. I had to install the proprietary ASUS USB Drivers from the official website and only then I was able to overcome on Windows the same "waiting for any device" I had experienced on Linux. However, the phone "bricks". I suppose this should be the technical term used in this field to tell that the phone gets stuck for hours on the boot animation. I tried several times to reboot it, but each time the same story.
Maybe the problem on Linux is that I do not have the proper Android Device Usb drivers installed. In this case, how to solve the problem taking into account that ASUS only released the drivers for Windows?
RECAP: I have my phone bricked now (Android is unable to reboot, but I can do access both to the Power+VolumeUP menu (by the way, what's the name of this menu? Fast boot?) and the Power+VolumeDOWN menu (by the way, what's the name of this menu? Recovery boot?)
So sorry for the long story.
Hope you can help.
Thanks for your attention and best regards.
Click to expand...
Click to collapse
hey I have the same issue im on windows 10 and asus hasn't realeased drivers for asus zenfone laser connectivity so It wont show up no matter what I do, and the windows 7 drivers cant be used.
BlondebigboobsIRL said:
hey I have the same issue im on windows 10 and asus hasn't realeased drivers for asus zenfone laser connectivity so It wont show up no matter what I do, and the windows 7 drivers cant be used.
Click to expand...
Click to collapse
I'm using Z00T and Windows 10. Had no issues using the Android Authority and LineageOS guides.
These guides are great but I don't want to lose my data by formatting my bootlooping device, and the drivers asus gives do not work with windows 10, the adb drivers work fine but the asus drivers do not.