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: ***
Dropped my Nexus 4 last night and the screen cracked, leaving only the top and left side of the touch screen functioning - as such, I can't do anything on it, or even unlock it (only two dots on the left of the lock can be touched).
I am getting an upgrade shortly, so I would like to avoid repairing it, but I need to extract a bunch of data from it first (photos, amongst other things).
So my question is, are there any command line tools or anything which would allow me to access my phone? At the moment when I plug it into my mac, it just goes into charge mode, so can I initiate disk mode any how, or control it using my computer in any way?
Thanks a lot for reading! Hopefully one of you can help me.
Did you try connecting while in recovery? (Assuming the hard keys do still work)
I tend to forget which recovery does what, but I am sure that at least one of CWM or TWRP (or both even) allows USB debugging while in recovery so you can also get to your files, if needed. Via adb of course.
Thanks for the reply! Recovery mode was a good shout, because as you say my hard keys do still work. The only trouble I'm having is getting it to communicate with my computer now, as I'm on the stock recovery which doesn't seem to have a USB option. I suppose I'm going to have trouble installing CWM through stock recovery?
HikerMan said:
Thanks for the reply! Recovery mode was a good shout, because as you say my hard keys do still work. The only trouble I'm having is getting it to communicate with my computer now, as I'm on the stock recovery which doesn't seem to have a USB option. I suppose I'm going to have trouble installing CWM through stock recovery?
Click to expand...
Click to collapse
You can try installing CWM or TWRP via fastboot. Should also work as you wouldn't need to use your touchscreen.
---------- Post added at 12:11 PM ---------- Previous post was at 12:05 PM ----------
HikerMan said:
Thanks for the reply! Recovery mode was a good shout, because as you say my hard keys do still work. The only trouble I'm having is getting it to communicate with my computer now, as I'm on the stock recovery which doesn't seem to have a USB option. I suppose I'm going to have trouble installing CWM through stock recovery?
Click to expand...
Click to collapse
You can try installing CWM or TWRP via fastboot. Should also work as you wouldn't need to use your touchscreen. I am not allowed to posts link yet, but a simple search should do the trick. Good luck!
You should be able to access the SD card as long as the phone is booted, plugged into the computer and the driver is working properly. Whenever I have plug mine in I'm not required to toggle anything on the device in order for the computer to recognize it.
Unless you have MTP disabled.. then you'll have to find an alternative option.
Hello, I am completely new to this rooting thing and definitely a noob at this. I have tried to search for solutions, but most solutions I have seen use terminology that I have, for the most part, no idea what they are talking about. I was able to successfully unlock the bootloader. I then tried to root the phone but ended up getting stuck on "Your device software can't be checked for corruption. Please lock the bootloader." It said it would boot in 5 seconds but it does nothing. To make matters worse, I made the mistake of locking the bootloader and now that I turn on the phone it is stuck on the ZTE logo. Assistance would be greatly appreciated .
My phone is the ZTE Axon 7 version 7.1 and A2017U.
radmike12 said:
Hello, I am completely new to this rooting thing and definitely a noob at this. I have tried to search for solutions, but most solutions I have seen use terminology that I have, for the most part, no idea what they are talking about. I was able to successfully unlock the bootloader. I then tried to root the phone but ended up getting stuck on "Your device software can't be checked for corruption. Please lock the bootloader." It said it would boot in 5 seconds but it does nothing. To make matters worse, I made the mistake of locking the bootloader and now that I turn on the phone it is stuck on the ZTE logo. Assistance would be greatly appreciated .
My phone is the ZTE Axon 7 version 7.1 and A2017U.
Click to expand...
Click to collapse
Okay, this is getting pretty serious... At least 5 people locked their bootloader after getting bricked this month. This is the least helpful thing. @bkores Is there a warning on your toolkit? Maybe some testing for the stock recovery would be nice, but I don't believe that's possible
Okay, on to the debricking. You have one of the 3 models, A2017, A2017G or A2017U. The model is specified on the back of the phone; do not guide yourself by the software that you have installed. You need a Win10 x64 PC (or at least a windows PC on an x64 CPU, but Win10 usually works best); MiFlash, which is a program you can get from anywhere, and a FULL_EDL package for your phone, which you can find somewhere here. The name is usually A2017x_NOUGAT_FULL_EDL (the X stands for G for int'l, U for US, or nothing for Chinese). This package is pretty heavy (2.3 gb).
After you have all of that, unpack the package until you have a folder, connect your the USB cable to the PC on one of the rear USBs if you have a desktop PC (but leave the phone disconnected), and hold the two volume buttons but not the power button. Then plug the USB-C in and use MiFlash to flash the system. I guess I'll make a tutorial or something if this isn't clear enough, but for now, i'd say you ready the stuff
Choose an username... said:
Okay, this is getting pretty serious... At least 5 people who locked their bootloader after getting bricked. This is the least helpful thing. @bkores Is there a warning on your toolkit? Maybe some testing for the stock recovery would be nice, but I don't believe that's possible
Okay, on to the debricking. You have one of the 3 models, A2017, A2017G or A2017U. The model is specified on the back of the phone; do not guide yourself by the software that you have installed. You need a Win10 x64 PC (or at least a windows PC on an x64 CPU, but Win10 usually works best); MiFlash, which is a program you can get from anywhere, and a FULL_EDL package for your phone, which you can find somewhere here. The name is usually A2017x_NOUGAT_FULL_EDL (the X stands for G for int'l, U for US, or nothing for Chinese). This package is pretty heavy (2.3 gb).
After you have all of that, unpack the package until you have a folder, connect your the USB cable to the PC on one of the rear USBs if you have a desktop PC (but leave the phone disconnected), and hold the two volume buttons but not the power button. Then plug the USB-C in and use MiFlash to flash the system. I guess I'll make a tutorial or something if this isn't clear enough, but for now, i'd say you ready the stuff
Click to expand...
Click to collapse
Thank you very much for the reply! When it comes to theA2017x_NOUGAT_FULL_EDL file, is this what you are referring to? https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
radmike12 said:
Thank you very much for the reply! When it comes to theA2017x_NOUGAT_FULL_EDL file, is this what you are referring to? https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Click to expand...
Click to collapse
I don't know, because you haven't told me your phone model. Just look at the back, it should say the model there. But I think it's that. There's a thread with A2017G and A2017 files on the Guides section, made by WesTD. If you have one of those you can use one of the files. If you have an A2017U, you'll have to search. if you find the file, could you send me the link? I want to do a guide but can't find the U file
Choose an username... said:
Okay, this is getting pretty serious... At least 5 people locked their bootloader after getting bricked this month. This is the least helpful thing. @bkores Is there a warning on your toolkit? Maybe some testing for the stock recovery would be nice, but I don't believe that's possible
Click to expand...
Click to collapse
Yes my toolkit makes it perfectly clear
Choose an username... said:
Okay, this is getting pretty serious... At least 5 people locked their bootloader after getting bricked this month. This is the least helpful thing. @bkores Is there a warning on your toolkit? Maybe some testing for the stock recovery would be nice, but I don't believe that's possible
Okay, on to the debricking. You have one of the 3 models, A2017, A2017G or A2017U. The model is specified on the back of the phone; do not guide yourself by the software that you have installed. You need a Win10 x64 PC (or at least a windows PC on an x64 CPU, but Win10 usually works best); MiFlash, which is a program you can get from anywhere, and a FULL_EDL package for your phone, which you can find somewhere here. The name is usually A2017x_NOUGAT_FULL_EDL (the X stands for G for int'l, U for US, or nothing for Chinese). This package is pretty heavy (2.3 gb).
After you have all of that, unpack the package until you have a folder, connect your the USB cable to the PC on one of the rear USBs if you have a desktop PC (but leave the phone disconnected), and hold the two volume buttons but not the power button. Then plug the USB-C in and use MiFlash to flash the system. I guess I'll make a tutorial or something if this isn't clear enough, but for now, i'd say you ready the stuff
Click to expand...
Click to collapse
When I hold the two volume buttons the phone does nothing .
Choose an username... said:
Okay, this is getting pretty serious... At least 5 people locked their bootloader after getting bricked this month. This is the least helpful thing. @bkores Is there a warning on your toolkit? Maybe some testing for the stock recovery would be nice, but I don't believe that's possible
Okay, on to the debricking. You have one of the 3 models, A2017, A2017G or A2017U. The model is specified on the back of the phone; do not guide yourself by the software that you have installed. You need a Win10 x64 PC (or at least a windows PC on an x64 CPU, but Win10 usually works best); MiFlash, which is a program you can get from anywhere, and a FULL_EDL package for your phone, which you can find somewhere here. The name is usually A2017x_NOUGAT_FULL_EDL (the X stands for G for int'l, U for US, or nothing for Chinese). This package is pretty heavy (2.3 gb).
After you have all of that, unpack the package until you have a folder, connect your the USB cable to the PC on one of the rear USBs if you have a desktop PC (but leave the phone disconnected), and hold the two volume buttons but not the power button. Then plug the USB-C in and use MiFlash to flash the system. I guess I'll make a tutorial or something if this isn't clear enough, but for now, i'd say you ready the stuff
Click to expand...
Click to collapse
Nevermind I got it to work! but now it is saying that i am putting in the wrong pin even when I know my own pin.
radmike12 said:
Nevermind I got it to work! but now it is saying that i am putting in the wrong pin even when I know my own pin.
Click to expand...
Click to collapse
That's normal, just unlock the phone and do whatever you were hoping to do before. But use axon7toolkit now instead
A factory reset would also unlock the phone, but you might as well want to unlock and all that stuff since you'll lose your data anyways.
Choose an username... said:
That's normal, just unlock the phone and do whatever you were hoping to do before. But use axon7toolkit now instead
A factory reset would also unlock the phone, but you might as well want to unlock and all that stuff since you'll lose your data anyways.
Click to expand...
Click to collapse
i once again unlocked the bootloader using the toolkit. How to root the phone with the axon7toolkit? When TWRP opens while trying root on my phone I get the message that my device is not conneted anymore. When TWRP opens what do I do after that?
radmike12 said:
i once again unlocked the bootloader using the toolkit. How to root the phone with the axon7toolkit? When TWRP opens while trying root on my phone I get the message that my device is not conneted anymore. When TWRP opens what do I do after that?
Click to expand...
Click to collapse
No, forget about the toolkit. Put the latest Magisk on your internal storage or SD card (or SuperSU if you don't care about SafetyNet), enter TWRP with the key combination (I think it's vol up + power), make a full backup, and flash the zip.
Choose an username... said:
No, forget about the toolkit. Put the latest Magisk on your internal storage or SD card (or SuperSU if you don't care about SafetyNet), enter TWRP with the key combination (I think it's vol up + power), make a full backup, and flash the zip.
Click to expand...
Click to collapse
ok I put Magisk on my sd card. How do i enter TWRP without the toolkit?
radmike12 said:
ok I put Magisk on my sd card. How do i enter TWRP without the toolkit?
Click to expand...
Click to collapse
turn it off, vol up + power
You said you roooted other phones?
Choose an username... said:
turn it off, vol up + power
You said you roooted other phones?
Click to expand...
Click to collapse
I never said I rooted other phones. That's why I called myself a noob on the original post. I now successfully rooted the phone and all that now I want to get Xposed on it. I found o post about it but it says that If I have a systemless root it will break it. https://forum.xda-developers.com/showpost.php?p=68206045&postcount=2
hi; rank amateur here. i unlocked my 6p which went with no problems and then installed trwp, now it just boots to the google logo. i can get to fastboot and twrp but my linux pc no longer sees the phone. i suspect the phone is in charge mode. can i use recovery, > terminal to turn on data transfer so i can load and flash a new os? i was looking at loading a zip to a sd card but i had to order an adapter from c to type a usb. thanks
@dr1445 Have you tried a factory reset? I'm not how Linux works but if I'm remembering correctly I think Windows installed additional drivers after I unlocked the bootloader. This is a bit old but looks like people are still using might find something useful.
yes i did try a factory reset but the same result. as for the the linux pc i used it to unlock the 6p and other phones, i just need to toggle off the the charge function and click on transfer. i have a widows machine, i will give it a try, never know.
fastboot says connect cable but it also reports download mode disabled, is there away to turn it on in fastboot?
dr1445 said:
fastboot says connect cable but it also reports download mode disabled, is there away to turn it on in fastboot?
Click to expand...
Click to collapse
Make sure your fastboot is the latest and maybe try a different cable if you can.
---------- Post added at 01:39 PM ---------- Previous post was at 12:54 PM ----------
dr1445 said:
fastboot says connect cable but it also reports download mode disabled, is there away to turn it on in fastboot?
Click to expand...
Click to collapse
Mine also says download mode disabled and I can still use fastboot. So I don't think its the problem.
dr1445 said:
hi; rank amateur here. i unlocked my 6p which went with no problems and then installed trwp, now it just boots to the google logo. i can get to fastboot and twrp but my linux pc no longer sees the phone. i suspect the phone is in charge mode. can i use recovery, > terminal to turn on data transfer so i can load and flash a new os? i was looking at loading a zip to a sd card but i had to order an adapter from c to type a usb. thanks
Click to expand...
Click to collapse
You're best bet is to just flash a factory image from Google and start over, link
let's see my pc still doesn't have commo with fastboot. i found that "sideloader" works between the pc and fastboot. i was able to install lineageos 15.1 but with out the gapps at the moment. odd thing is i can not get the "developer option" with 7 taps of the build #. working on new post now. thanks all.
dr1445 said:
let's see my pc still doesn't have commo with fastboot. i found that "sideloader" works between the pc and fastboot. i was able to install lineageos 15.1 but with out the gapps at the moment. odd thing is i can not get the "developer option" with 7 taps of the build #. working on new post now. thanks all.
Click to expand...
Click to collapse
Make sure your on the latest bootloader (3.79) I know that was a must after March update for most ROMs. Also make sure fastboot is the latest here.I think your best option is written above with reflashing latest stock image from March and starting over.
happy to check the bootloader version. i get bl: angler-03.79, baseband: angler-03.85. should be good?
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