Related
Rooted my LG G2 (ATT) recently. Yesterday i got an error on bootup stating that system UI has crashed.. After that all hell broke loose. Phone when powered on only boots into the TWRP, friend thought he could "fix" the issue by doing a format on the device.. FML. SO now when trying to get into download mode to perform the Stock Rom/Unbrick process it just won't allow me to do anything. It just keeps booting into TWRP.
My laptop has all drivers needed, but phone won't be detected by my laptop..
Anyway how i can get my LG back to stock & working? Didn't have a custom rom or anything, only the Camera Mod which never gave issues..
The system UI came on before i did the Camera Mod by the way..
JelloSS said:
Rooted my LG G2 (ATT) recently. Yesterday i got an error on bootup stating that system UI has crashed.. After that all hell broke loose. Phone when powered on only boots into the TWRP, friend thought he could "fix" the issue by doing a format on the device.. FML. SO now when trying to get into download mode to perform the Stock Rom/Unbrick process it just won't allow me to do anything. It just keeps booting into TWRP.
My laptop has all drivers needed, but phone won't be detected by my laptop..
Anyway how i can get my LG back to stock & working? Didn't have a custom rom or anything, only the Camera Mod which never gave issues..
The system UI came on before i did the Camera Mod by the way..
Click to expand...
Click to collapse
try one of the methods below:
http://forum.xda-developers.com/showthread.php?t=2451696
or
http://forum.xda-developers.com/showthread.php?t=2432476
and good luck.
bean373 said:
try one of the methods below:
http://forum.xda-developers.com/showthread.php?t=2451696
or
http://forum.xda-developers.com/showthread.php?t=2432476
and good luck.
Click to expand...
Click to collapse
Id try those, but seeing this POS won't boot into download mode or anything im F***ked
Holding volume up & plugging in usb cable boots into TWRP.. Holding both vol down & up, while plugging in USB makes device stick on LG logo screen..
Hehe i have same Problem
Flash a Rom
start at the recovery, go to Advanced, then Terminal Command, press Select,use this code,
dd if=/dev/Zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Then reboot,this works.
letschky said:
Hehe i have same Problem
Flash a Rom
start at the recovery, go to Advanced, then Terminal Command, press Select,use this code,
dd if=/dev/Zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Then reboot,this works.
Click to expand...
Click to collapse
No rom on phone.. :/ how would i be able to get a rom at this stage? seeing there is no SD card slot & that i can't get into download mode...
JelloSS said:
No rom on phone.. :/ how would i be able to get a rom at this stage? seeing there is no SD card slot & that i can't get into download mode...
Click to expand...
Click to collapse
ya I got can't open '/dev/Zero : No such file or directory.
Looks like we did the same thing , I installed the OTA two days ago and it went to TWRP so I try to wipe phone and just use my back up and I wiped the whole phone now now there is nothing on the phone but TWRP. This suck
edivens said:
ya I got can't open '/dev/Zero : No such file or directory.
Looks like we did the same thing , I installed the OTA two days ago and it went to TWRP so I try to wipe phone and just use my back up and I wiped the whole phone now now there is nothing on the phone but TWRP. This suck
Click to expand...
Click to collapse
Yea same... Sux man :/
Have u got into download mode??
Trwp is set on default on Boot,you cannot in Downloadmode!Have you a Otg Cable?
letschky said:
Trwp is set on default on Boot,you cannot in Downloadmode!Have you a Otg Cable?
Click to expand...
Click to collapse
How do i get it off default? & yes i have a mico usb cable.
Copy a Rom on a USB stick and install it in TWRP via OTG, run back into TWRP and enter this line
start at the recovery, go to Advanced, then Terminal Command, press Select,use this code,
dd if=/dev/Zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
That should solve your problem, for me it just works
Only in this way can be turned off Trwp as default and the phone boots normally
Good Luck!
---------- Post added at 07:26 PM ---------- Previous post was at 07:17 PM ----------
You just have to be careful that you type it correctly,
[Space]
stands for space bar/Space on the keyboard
dd[space]if=/dev/zero[space]of=/dev/block/platform/msm_sdcc.1/by-name/fota
letschky said:
Copy a Rom on a USB stick and install it in TWRP via OTG, run back into TWRP and enter this line
start at the recovery, go to Advanced, then Terminal Command, press Select,use this code,
dd if=/dev/Zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
That should solve your problem, for me it just works
Only in this way can be turned off Trwp as default and the phone boots normally
Good Luck!
---------- Post added at 07:26 PM ---------- Previous post was at 07:17 PM ----------
You just have to be careful that you type it correctly,
[Space]
stands for space bar/Space on the keyboard
dd[space]if=/dev/zero[space]of=/dev/block/platform/msm_sdcc.1/by-name/fota
Click to expand...
Click to collapse
How am i going to get the ROM from a USB onto my LG G2? Cause my pc can't pick it up.........
& yes i have LG Drivers installed.
JelloSS said:
Id try those, but seeing this POS won't boot into download mode or anything im F***ked
Holding volume up & plugging in usb cable boots into TWRP.. Holding both vol down & up, while plugging in USB makes device stick on LG logo screen..
Click to expand...
Click to collapse
Have you tried to use the "sideload" option to see if you can load a rom onto it yet? This requires that your computer sees your phone with the correct drivers and adb working too.
Did you try to do a complete wipe/reboot and see if you can get into download mode?
If none of those methods work then I'm not sure what to tell you. I ran into two problems only so far.
First one was when I accidently wiped everything and had to sideload a rom onto my phone.
Second, I took the OTA update and had the bootloop TWRP problem which was solved by using the LG Flash tool to flash the stock Sprint rom onto my phone by following the directions for the Verizon Method but used a Sprint rom and dll file.
If you can't sideload a rom or get into download mode then you have a major problem there but it could be just that you've overlooked something.
JelloSS said:
How am i going to get the ROM from a USB onto my LG G2? Cause my pc can't pick it up.........
& yes i have LG Drivers installed.
Click to expand...
Click to collapse
Copy a Rom to Usb and install the Rom via Usb/Otg Cable,it is self to install from internal Storage.You can Select OTG or internal Storage in Recovery to install the Rom.Its easy,I can Backup or install Roms on Otg.
Sorry for my Bad English,i hope you understand me!
bean373 said:
Have you tried to use the "sideload" option to see if you can load a rom onto it yet? This requires that your computer sees your phone with the correct drivers and adb working too.
Did you try to do a complete wipe/reboot and see if you can get into download mode?
If none of those methods work then I'm not sure what to tell you. I ran into two problems only so far.
First one was when I accidently wiped everything and had to sideload a rom onto my phone.
Second, I took the OTA update and had the bootloop TWRP problem which was solved by using the LG Flash tool to flash the stock Sprint rom onto my phone by following the directions for the Verizon Method but used a Sprint rom and dll file.
If you can't sideload a rom or get into download mode then you have a major problem there but it could be just that you've overlooked something.
Click to expand...
Click to collapse
nope doesn't work.. Won't connect to PC... It did before fine.. Sideload is stuck at loading screen or something. I'll try loading rom onto USB & from usb to phone once i get an adapter for USB Female to Micro USB.
He got out.
I was stuck in the bootloop for about 6 hours before I realized I had the correct dll, and tot file, the correct utility from LGE, and I turned the noodle of a brick into a "unbranded" phone temporarily, until sprint came to the rescue, and branded everything back from the production image I loaded just earlier. I just wanna say this... DO NOT PLAY WITH PHONE DIALER CODES MEANT FOR THE KOREANS WHO TEST YOUR PHONE!!!
You can brick that **** fast as hell. TWRP kept coming in, and I didn't know how to deal with adb sideload, or the basic dd command to get things back to download mode. Now I have a real working knowledge of recovering from an otherwise hopeless state. Take your time, and explore slowly.
Your mileage may vary, just sayin'
letschky said:
Copy a Rom on a USB stick and install it in TWRP via OTG, run back into TWRP and enter this line
start at the recovery, go to Advanced, then Terminal Command, press Select,use this code,
dd if=/dev/Zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
That should solve your problem, for me it just works
Only in this way can be turned off Trwp as default and the phone boots normally
Good Luck!
---------- Post added at 07:26 PM ---------- Previous post was at 07:17 PM ----------
You just have to be careful that you type it correctly,
[Space]
stands for space bar/Space on the keyboard
dd[space]if=/dev/zero[space]of=/dev/block/platform/msm_sdcc.1/by-name/fota
Click to expand...
Click to collapse
This is not working for me I still get redirected right back to the recovery screen , none of my backups will work either, they say successful at the end but when I reboot I am right back to TWRP recovery once again.
jcal321 said:
This is no?t working for me I still get redirected right back to the recovery screen , none of my backups will work either, they say successful at the end but when I reboot I am right back to TWRP recovery once again.
Click to expand...
Click to collapse
I experienced this situation for a while.
The solution is doing a normal procedure to install custom rom from USB.
Just copy custom rom to USB, choose advanced wipe, then wipe dalvik, cache, data, and system. Then install custom rom in USB, and, reboot phone after installation finished.
Phone should be back to normal again.
htcm7 said:
I experienced this situation for a while.
The solution is doing a normal procedure to install custom rom from USB.
Just copy custom rom to USB, choose advanced wipe, then wipe dalvik, cache, data, and system. Then install custom rom in USB, and, reboot phone after installation finished.
Phone should be back to normal again.
Click to expand...
Click to collapse
Actually I was able to fix it through the terminal emulator thankfully. Thanks for the info though I appreciate it.
jcal321 said:
Actually I was able to fix it through the terminal emulator thankfully. Thanks for the info though I appreciate it.
Click to expand...
Click to collapse
hi, i am having the exact same problem, i formated it and everything. please, how did you fix it?? its my only connected phone so i dearly need it to work
bean373 said:
try one of the methods below:
http://forum.xda-developers.com/showthread.php?t=2451696
or
http://forum.xda-developers.com/showthread.php?t=2432476
and good luck.
Click to expand...
Click to collapse
***i try second one but i jusy says:dd: can't open '/dev/block/platform/msm_sdcc.1/by-name/fota': No such file or directory. :crying: ***
Pretty sure I know the answer to this, but before I finally through in the towel or rather my Nexus 4 against the wall... I will defer to the resident experts. So, I attempt to install Liquid Smooth 4.0 and after going into TWRP I did a wipe and installed it. I was running the previous official build of Liquid Smooth. I also install gapps for Lollipop. Everything began to boot and then the phone said something to the like apps are starting and it stayed on that screen for a full 8 hours. I went back into recovery and tried to restore from my previous Liquid Smooth. Exact same thing happened. After several attempts I did the unmentionable. I did a full wipe. I know it was a dumb*ss move now. My phone does NOT connect to ANY PC. Every time the PC says device not recognized. Now I have now OS. Only TWRP. I tried sideload, but computer does not recognize device. I bought usb-otg adapter, but found out that usb-otg does not work with Nexus 4. So.... should I throw in the towel? My phone now a fancy paperweight?
Many thanks!
kjtay said:
Pretty sure I know the answer to this, but before I finally through in the towel or rather my Nexus 4 against the wall... I will defer to the resident experts. So, I attempt to install Liquid Smooth 4.0 and after going into TWRP I did a wipe and installed it. I was running the previous official build of Liquid Smooth. I also install gapps for Lollipop. Everything began to boot and then the phone said something to the like apps are starting and it stayed on that screen for a full 8 hours. I went back into recovery and tried to restore from my previous Liquid Smooth. Exact same thing happened. After several attempts I did the unmentionable. I did a full wipe. I know it was a dumb*ss move now. My phone does NOT connect to ANY PC. Every time the PC says device not recognized. Now I have now OS. Only TWRP. I tried sideload, but computer does not recognize device. I bought usb-otg adapter, but found out that usb-otg does not work with Nexus 4. So.... should I throw in the towel? My phone now a fancy paperweight?
Many thanks!
Click to expand...
Click to collapse
Under device manager, what is listed as your phone?
Ajxx16 said:
Under device manager, what is listed as your phone?
Click to expand...
Click to collapse
Unknown Device... It is worth noting that I have used Wugs Toolkit and followed every set of directions to a T. This includes a PC that that has never had my phone in it before. Followed all the steps before I even tried to connect. Also, both PC machine indicate that I have installed the most update driver.
I have zero experience with that toolkit, but have you tired every usb port on your computer and possibly another computer? Your phone is far from gone, this just sounds like a driver issue to me. Is your phone recognizable in bootloader?
I don't actually have this phone but my wife does, as well as my brother. Just the other night my wife's was showing up unrecognized, all I had to do was swap usb ports on the computer.
Ajxx16 said:
I have zero experience with that toolkit, but have you tired every usb port on your computer and possibly another computer? Your phone is far from gone, this just sounds like a driver issue to me. Is your phone recognizable in bootloader?
I don't actually have this phone but my wife does, as well as my brother. Just the other night my wife's was showing up unrecognized, all I had to do was swap usb ports on the computer.
Click to expand...
Click to collapse
I have tried all usb ports and a different usb cord. My OS is gone, so I was hoping to find some way to install a rom or stock. I am at a loss!
How about the bootloader? If you have that feature you can flash stock image
---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------
Volume down + power incase you didn't know.
Ajxx16 said:
How about the bootloader? If you have that feature you can flash stock image
---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------
Volume down + power incase you didn't know.
Click to expand...
Click to collapse
I do if I understand the term correctly. I am at the android "start" screen and underneath the android it says
Fastboot Mode
Product_Name - mako
lock state - unlocked
Now what?
Connect it to your computer, and I assume you have fastboot and adb set up correctly. In command prompt type fastboot devices and see if your phone is listed, should give the serial and say fastboot next to that
Not sure if I know how to set up adb correctly... as far as fastboot goes.. I assume that is set up correctly. Would adb work if the PC doesn't recognize my phone?
Well adb is of no use here so I wouldn't worry about it. Is fastboot recognized?
Ajxx16 said:
Well adb is of no use here so I wouldn't worry about it. Is fastboot recognized?
Click to expand...
Click to collapse
Don't mean to sound like an idiot (may be too late for that), but do you mean fastboot recognized on my PC when I plug in my phone? Or does is say fastboot on my phone? PC does not recognize my phone, but it does say fastboot enabled on my phone.
Alright so follow these instructions.
http://forum.xda-developers.com/showthread.php?t=2317790
Get that set up and in the mean time download either the 4.4.4 or 5.0 image here.
https://developers.google.com/android/nexus/images
Once you finish the adb fastboot setup, while your phone is in the boot loader screen you should be able to type into a command prompt "fastboot devices" and your device should be listed.
Ajxx16 said:
Alright so follow these instructions.
http://forum.xda-developers.com/showthread.php?t=2317790
Get that set up and in the mean time download either the 4.4.4 or 5.0 image here.
https://developers.google.com/android/nexus/images
Once you finish the adb fastboot setup, while your phone is in the boot loader screen you should be able to type into a command prompt "fastboot devices" and your device should be listed.
Click to expand...
Click to collapse
I can't get the PC to recognize the phone. The phone is in fastboot mode. It is looking mighty grim!
I'm fairly certain this is just a simple fix on the drivers on your computer, you have access to recovery and boot loader, your phone is far from gone. I'm out atm so I'll check in with ya a little later.
Ajxx16 said:
I'm fairly certain this is just a simple fix on the drivers on your computer, you have access to recovery and boot loader, your phone is far from gone. I'm out atm so I'll check in with ya a little later.
Click to expand...
Click to collapse
An easy fix, do you have a nandroid backup? Just restore it in twrp. As mentioned, you're far from bricked and sol. If you can get into the bootloader it's recoverable.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
An easy fix, do you have a nandroid backup? Just restore it in twrp. As mentioned, you're far from bricked and sol. If you can get into the bootloader it's recoverable.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Would you happen to have a link for an ADB driver he could install? Not sure of the n4 requires something specific.
Ajxx16 said:
Would you happen to have a link for an ADB driver he could install? Not sure of the n4 requires something specific.
Click to expand...
Click to collapse
I'd Google 15 second adb install xda. That'll set yo adb and fastboot on the pc and includes drivers
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I'd Google 15 second adb install xda. That'll set yo adb and fastboot on the pc and includes drivers
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Installed 15 second adb and still nothing recognized on my PC. Still have "fastboot mode" in red on my phone???
kjtay said:
Installed 15 second adb and still nothing recognized on my PC. Still have "fastboot mode" in red on my phone???
Click to expand...
Click to collapse
Open up device manager, look for the phone, right click and hit update driver, then hit let !e choose driver, then select from list, you shpuld see something along the lines of ADB interface. Select that and install and try fastboot devices in command prompt again.
Ajxx16 said:
Open up device manager, look for the phone, right click and hit update driver, then hit let !e choose driver, then select from list, you shpuld see something along the lines of ADB interface. Select that and install and try fastboot devices in command prompt again.
Click to expand...
Click to collapse
I am pretty certain I have the proper drivers installed on 3 computers. Not a single one recognizes the device. I suppose it is possible that it is a hardware issue? If I can figure a way to the computer to recognize the phone I am certain I can save it. Right NOTHING has worked.
Okay, this is must be my first thread since I join this lovely forum.
So here is the deal, this is my previous phone that I gave to my sister not so long ago, she has this not-so-bright wise *ss who try to fix her G2.
Sadly, he flashed the wrong rom, this is LG F320L and I think he flashed with F320K (based on error message that I got from the LG Flash Tool when I try to fix it)
This is the story so far :
1. the first time i got it on my hand (after get wrong-flashed that is ) :
- the phone is cannot boot, it stucked on black screen with fastboot command, try to go to recovery but not working, keep going to fastboot screen
- but i can still go to download mode (if I press vol UP while connect it to my PC) but somehow my PC will not recognize it
2. So I browse so many tutorial here and I end up erase and then reflash the stock recovery via cmd fastboot command, I'm 100% sure that I flashed the correct stock recovery file
- the process kinda work, the phone is able to go to recovery screen now although still cannot boot to system
- i still can go to download mode but the PC still didn't recognize it
- however, now the phone is being recognize by my PC if i plug the phone (without pressing anything on the phone), but gave me error code on the MTP driver
3. So next step I try to flash it via kdz method, didn't work of course, since my download mode won't be recognize, and then i also try to flash it via TOT method, also fail (again)
Note : on TOT method I try to flash it while NOT on download mode, since it will not recognized, it gave me error message that i try to cross flash or something. It says that I try to flash F320K to F320L (hence I assume that my sister's boyfriend flashed the wrong rom and got bricked)
also please note that while i'm did this i already make sure that i change the port setting to port 41
So now i stucked here, without the working download mode that can be recognized by my PC i think i'm start to running out of option to fix this phone
Please point me to the right direction good people of xda, please, thank you in advance
ecko no yaro said:
Okay, this is must be my first thread since I join this lovely forum.
So here is the deal, this is my previous phone that I gave to my sister not so long ago, she has this not-so-bright wise *ss who try to fix her G2.
Sadly, he flashed the wrong rom, this is LG F320L and I think he flashed with F320K (based on error message that I got from the LG Flash Tool when I try to fix it)
This is the story so far :
1. the first time i got it on my hand (after get wrong-flashed that is ) :
- the phone is cannot boot, it stucked on black screen with fastboot command, try to go to recovery but not working, keep going to fastboot screen
- but i can still go to download mode (if I press vol UP while connect it to my PC) but somehow my PC will not recognize it
2. So I browse so many tutorial here and I end up erase and then reflash the stock recovery via cmd fastboot command, I'm 100% sure that I flashed the correct stock recovery file
- the process kinda work, the phone is able to go to recovery screen now although still cannot boot to system
- i still can go to download mode but the PC still didn't recognize it
- however, now the phone is being recognize by my PC if i plug the phone (without pressing anything on the phone), but gave me error code on the MTP driver
3. So next step I try to flash it via kdz method, didn't work of course, since my download mode won't be recognize, and then i also try to flash it via TOT method, also fail (again)
Note : on TOT method I try to flash it while NOT on download mode, since it will not recognized, it gave me error message that i try to cross flash or something. It says that I try to flash F320K to F320L (hence I assume that my sister's boyfriend flashed the wrong rom and got bricked)
also please note that while i'm did this i already make sure that i change the port setting to port 41
So now i stucked here, without the working download mode that can be recognized by my PC i think i'm start to running out of option to fix this phone
Please point me to the right direction good people of xda, please, thank you in advance
Click to expand...
Click to collapse
Okay, so at this moment does the device try to mount quite a lot of partitions? Also does it give any errors on the screen if you power on without trying to boot to download mode or recovery? Ideally we want to see something along the lines of security error.
Sent from my LG-D802 using Tapatalk
I too have problem with my lg..
i flashed kdz file, but i have error. Now my lg >> dont have fastboot mode, download mode. but when i connect to the computer (USB) i have a lot of partitions.
what i must to do to bring my lg to life?
Sorry for my english
Mati0807 said:
I too have problem with my lg..
i flashed kdz file, but i have error. Now my lg >> dont have fastboot mode, download mode. but when i connect to the computer (USB) i have a lot of partitions.
what i must to do to bring my lg to life?
Sorry for my english
Click to expand...
Click to collapse
did you try to go from lollipop to kitkat?
heavy_metal_man said:
Okay, so at this moment does the device try to mount quite a lot of partitions? Also does it give any errors on the screen if you power on without trying to boot to download mode or recovery? Ideally we want to see something along the lines of security error.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
thanks for your reply, i really appreciate it
well, you're right, it does give me errors when i power on (without trying to go to download mode or recovery mode)
so when i power it on, it shows LG logo then the image goes like corrupt, at first it kinda like shaking then it went blur and last it disappearing, leave the screen into just blank screen.
but my PC recognize it on this moment, just the MTP driver that wasn't
about your first question i'm afraid i can't catch what that means
Code:
I too have problem with my lg..
i flashed kdz file, but i have error. Now my lg >> dont have fastboot mode, download mode. but when i connect to the computer (USB) i have a lot of partitions.
what i must to do to bring my lg to life?
Sorry for my english
did you try to go from lollipop to kitkat?
yep :/ i dont have any idea what i must to do :/
ecko no yaro said:
thanks for your reply, i really appreciate it
well, you're right, it does give me errors when i power on (without trying to go to download mode or recovery mode)
so when i power it on, it shows LG logo then the image goes like corrupt, at first it kinda like shaking then it went blur and last it disappearing, leave the screen into just blank screen.
but my PC recognize it on this moment, just the MTP driver that wasn't
about your first question i'm afraid i can't catch what that means
Click to expand...
Click to collapse
Hmmm. okay, so what does the pc recognize it as exactly in device manager? Also if you connect the device do you get several pop ups stating that the mounted device needs to be fixed? It's just that if the partitions are being mounted we can reflash them manually using DD commands with ubuntu.
---------- Post added at 06:20 PM ---------- Previous post was at 06:05 PM ----------
Mati0807 said:
Code:
I too have problem with my lg..
i flashed kdz file, but i have error. Now my lg >> dont have fastboot mode, download mode. but when i connect to the computer (USB) i have a lot of partitions.
what i must to do to bring my lg to life?
Sorry for my english
did you try to go from lollipop to kitkat?
yep :/ i dont have any idea what i must to do :/
Click to expand...
Click to collapse
Right, you need to follow this guide i think. Ensure your read it fully before you attempt anything. Now, the lollipop update apparently changed some partitions so I would flash the bumped twrp from the development section instead of the 2.6.3.2 version recommended. Then once you can boot into recovery flash the rom recommended in this post
heavy_metal_man said:
Hmmm. okay, so what does the pc recognize it as exactly in device manager? Also if you connect the device do you get several pop ups stating that the mounted device needs to be fixed? It's just that if the partitions are being mounted we can reflash them manually using DD commands with ubuntu.
Click to expand...
Click to collapse
it's just like the pict that i attached
about the pop ups, no.. i don't think i got those, the only pop ups that appear was the small notification on the bottom right panel that the drivers is being installed, and keep failing on the MTP driver, maybe that's why my PC can't recognizes it under the download mode
ecko no yaro said:
it's just like the pict that i attached
about the pop ups, no.. i don't think i got those, the only pop ups that appear was the small notification on the bottom right panel that the drivers is being installed, and keep failing on the MTP driver, maybe that's why my PC can't recognizes it under the download mode
Click to expand...
Click to collapse
if you open disk management what does it say about the g2? also did you install the universal adb driver at any point? http://forum.xda-developers.com/showpost.php?p=51265001&postcount=30 here it states that installing the universial driver will show your device as a samsung.
---------- Post added at 06:55 PM ---------- Previous post was at 06:42 PM ----------
Mati0807 said:
Code:
I too have problem with my lg..
i flashed kdz file, but i have error. Now my lg >> dont have fastboot mode, download mode. but when i connect to the computer (USB) i have a lot of partitions.
what i must to do to bring my lg to life?
Sorry for my english
did you try to go from lollipop to kitkat?
yep :/ i dont have any idea what i must to do :/
Click to expand...
Click to collapse
Additional! this rom flash assumes you are on a d802 so if your not on a d802 the dont flash it!
heavy_metal_man said:
if you open disk management what does it say about the g2? also did you install the universal adb driver at any point? http://forum.xda-developers.com/showpost.php?p=51265001&postcount=30 here it states that installing the universial driver will show your device as a samsung.
---------- Post added at 06:55 PM ---------- Previous post was at 06:42 PM ----------
Additional! this rom flash assumes you are on a d802 so if your not on a d802 the dont flash it!
Click to expand...
Click to collapse
okay, i just checked on disk management and it appear that my PC doesn't recognized the G2, what makes it weird, at the same time it recognizes the G2 on device manager on ports (COM & LPT) on port 41, about the adb yes, i do believe i did that long time ago, though i forgot what was my intention of doing so
ecko no yaro said:
okay, i just checked on disk management and it appear that my PC doesn't recognized the G2, what makes it weird, at the same time it recognizes the G2 on device manager on ports (COM & LPT) on port 41, about the adb yes, i do believe i did that long time ago, though i forgot what was my intention of doing so
Click to expand...
Click to collapse
Hmmm. im stumped. I think its a bit of a catch 22 here. What i think has happened is that the rom flash that was done has changed some of the partition layout, but the methods of fixing that issue is either with DD commands from a custom recovery (which you dont have and cannot flash) or with DD commands using ubuntu when the device is auto-mounting all of your partitions. Its worth a look if you have an ubuntu disk around, if not download here, burn to disk or mount it to a bootable usb and see if ubuntu has any luck with it. Either that or try installing any drivers you can on the pc to get download mode working.
there is also this as a last resort but i've never had to do this so i cannot vouch for it :-/ Good luck pal.
Yeah, i do these.
I used these tool >> https://doc-04-5c-docs.googleuserco...27034/0B_Hol5T47S-benVFYWIxcGlQU0k?e=download
and install bumped recovery 2.8.5.1, then next with otg cabble flash these http://forum.xda-developers.com/showpost.php?p=59079665&postcount=536.
and now i install cloudyg2 and i feel great xD thank you!
Mati0807 said:
Yeah, i do these.
I used these tool >> https://doc-04-5c-docs.googleuserco...27034/0B_Hol5T47S-benVFYWIxcGlQU0k?e=download
dear do you have above mentioned tool bcoz i can not download , this page do not open
Click to expand...
Click to collapse
new link http://www39.zippyshare.com/v/UphAeXOO/file.html
With all files for d802. i used these for my phone!
Only run these tool, and smile
Hello I have a "a2017u" model, without a working touchscreen. I need to sent it in for a warranty repair. can anyone explain to me how to restore the device, currently it has twrp+lineage os. I CAN'T use the touchscreen, however you can see everything, only touch doesn't work. I really need help since this is my only phone and I'm borrowing one.
So where are you getting stuck?
I don't think you need to use the screen for anything.
lafester said:
So where are you getting stuck?
I don't think you need to use the screen for anything.
Click to expand...
Click to collapse
I tried to use axon 7 toolkit, I run the check under option one and get this message.
So I don't know what's happening
cato1986 said:
I tried to use axon 7 toolkit, I run the check under option one and get this message.
So I don't know what's happening
Click to expand...
Click to collapse
EDIT: Some guy gave me an awesome idea: Use an OTG adapter and a USB mouse on TWRP. From there you can install some zips, I don't know anything about A2017s but you can look for guides on how to get to stock (not mine though)
Right. If you have an SD card I think you can:
- find a stock recovery.img, use fastboot to install it to recovery (fastboot flash recovery yourfile.img)
- then wipe data/factory reset with the stock recovery
- install an official system zip with your sdcard
You have a Chinese version phone so I don't have any recovery zips for that, sorry. If you can, look for the recovery img and send the link of where you got it here.
Axon7toolkit is a little bit too hardcoded, it needs adb first, then from ADB it boots to fastboot, then from there it boots a twrp img...
Well that's a no go. Besides the fact it refuses to show the mouse. It just doesn't work. I did manage to get to the desktop. But parts of the digitizer work and then it goes crazy clicking things on its own.
Chinese version? Mines the American. Zte a2017u
cato1986 said:
Chinese version? Mines the American. Zte a2017u
Click to expand...
Click to collapse
Then why did you write A2017 in the title and the OP?? Change that
---------- Post added at 05:16 AM ---------- Previous post was at 05:13 AM ----------
Okay there may be an easier way. Try putting your phone in FTM mode (while off, hold Vol down + power) and a message that says FTM mode should appear. Now try axon7toolkit.
Or, if you have an USB mouse and an OTG adapter, enable USB debugging and connect your phone to the PC. Then use axon7toolkit
Hey guys, need some help here. I have M1 pro European version and just kind of bricked it:
-The screen stays black, I think system is booting because I can hear unlock click if I press the power button. Also notification led indicates charging when connected.
-in fastboot mode the screen is black too, but fastboot sees the device, though the name is different than before the brick.
-In recovery all I can see is black screen.
Now, here's how this happened:
-I got the phone, updated firmware to 323
-Unlocked successfuly with unofficial unlock
-Tried installing TWRP to no avail - The process seemed to go through fine, but no TWRP, just stock Asus recovery. Tried multiple times, tried rebooting straight to recovery from fastboot, tried on different computers. Weird thing I noticed was that write time in fastboot during the process was like 0.001s, which led me to believe it thought it was writing TWRP, but really wasn't for some reason.
-Then I decided to flash fastboot firmware using this guide: https://forum.xda-developers.com/as...ow-to/guide-revert-to-stock-rom-lock-t3798420
-It started flashing, but during the process I noticed again that all the write times
were super low like 0.001s, which made me expect the worst, and well, here I am now.
It's the first time I have so many problems with rooting a phone. Any help is greatly appreciated, I hope I can fix this considering it kinda works in fastboot mode.
Thanks in advance and have a great day.
Not really an expert but there are problems flashing this phone via usb 3.0 port. If you are using one try a usb 2.0 one.
gr8guzzler said:
Not really an expert but there are problems flashing this phone via usb 3.0 port. If you are using one try a usb 2.0 one.
Click to expand...
Click to collapse
Thanks, but I tried both usb 2 and 3 and both yield same results for me.
gr8guzzler said:
Not really an expert but there are problems flashing this phone via usb 3.0 port. If you are using one try a usb 2.0 one.
Click to expand...
Click to collapse
Thanks, but I tried both usb 2 and 3 and both yield same results for me.
Not sure whether this will work (it does in some cases), try full ADB instead of minimal ADB + ASUS drivers installed from the website.
By what name does the fastboot see the device?
Hye, did you solve the problem?
Don't worry, it’s only soft bricked. All you need to do is to flash a stock service rom. Something like: WW_ZB602KL_15.2016.1805.318_20180712 or WW_ZB601KL(ZB602KL)-15.2016.1805.311-20180623. The reason it is "bricked" is because you flashed the incorrect rom for your device, actual model is important, M1 has many variants.
Try flash stock recovery through fastboot, relock ur device, then place whatever version of stock rom into microsd,
And last flash it via stock recovery
Hi sorry but how can i flash it through fastboot? I have same problem...
kothy said:
Hi sorry but how can i flash it through fastboot? I have same problem...
Click to expand...
Click to collapse
Flash stock recovery? Enter fastboot, connect Ur device to PC
Open cmd command in folder where U place the recovery.img file. Then, type "fastboot devices" to make sure Ur device detected
Then type "fastboot flash recovery (filename)"
Done
If you can see your device name when typing 'fastboot devices' you can do as said above. Could it be dead screen?
RAMBO29 said:
If you can see your device name when typing 'fastboot devices' you can do as said above. Could it be dead screen?
Click to expand...
Click to collapse
Yep, if it shows 'blablabla device' It could be dead screen
Then you can go to next step
Its not a dead screen. You just have a wrong rom/kernal/drives/firmware etc. Its a software issue.
Vico100 said:
Its not a dead screen. You just have a wrong rom/kernal/drives/firmware etc. Its a software issue.
Click to expand...
Click to collapse
i am facing the same issue but cant gent into stock recovery and cant enable usb debugging as well
any solutions.
Get into fastboot. Hold volume up and power. Even if you don't see the screen it should still go into fastboot. Check device manager on windows to see if any devices appear. The phone should vibrate when you turn it on and go into fastboot.
Vico100 said:
Get into fastboot. Hold volume up and power. Even if you don't see the screen it should still go into fastboot. Check device manager on windows to see if any devices appear. The phone should vibrate when you turn it on and go into fastboot.
Click to expand...
Click to collapse
i did that works but screen is blank or dead after flashing fastboot rom
What is your phone model and what rom did you flash?
tried this it did not work
https://forum.xda-developers.com/as...ow-to/guide-revert-to-stock-rom-lock-t3798420
---------- Post added at 10:36 PM ---------- Previous post was at 10:20 PM ----------
can you please help me... i have ZB601KL model... can do fast boot i do not know what to do next.... im stuck on the black screen... i can hear the phone booting up and starting up but its just black screen blinking... please help
---------- Post added at 10:39 PM ---------- Previous post was at 10:36 PM ----------
ASUS_X00TDB is the name of the phone when it boots up
same problem with my device. share if you find any solution.
------------------------------------------------------------------------------
fixed my device following this