Database Users

My g2 stuck at fastboot mode

Hi all,
I'm really desperate because my LG stuck in a boot loop and it can only get in the download mode.
I've read the thread about using fastboot command to restore to stock but my condition seems to be a little bit difference
First
i've got these command while plug my phone in
[860]fastboot mode started
[1070]-reset-
[1080]-portchange-
[1150] fastbootrocessing commands
Normally there would be a [910]udc_start() in the second line but i don't have it
Second
my command such as fastboot reboot or fastboot erase all stuck. When i unplug the usb cable it appear the too many link line like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is there any other way for me to return to stock or i can't use my phone anymore?
Note: i've tried to change the usb cable, usb port and even another computer and all of them stuck at the command line.

lordgon said:
Hi all,
I'm really desperate because my LG stuck in a boot loop and it can only get in the download mode.
I've read the thread about using fastboot command to restore to stock but my condition seems to be a little bit difference
First
i've got these command while plug my phone in
[860]fastboot mode started
[1070]-reset-
[1080]-portchange-
[1150] fastbootrocessing commands
Normally there would be a [910]udc_start() in the second line but i don't have it
Second
my command such as fastboot reboot or fastboot erase all stuck. When i unplug the usb cable it appear the too many link line like this
Is there any other way for me to return to stock or i can't use my phone anymore?
Note: i've tried to change the usb cable, usb port and even another computer and all of them stuck at the command line.
Click to expand...
Click to collapse
Try Skt tool and fix fastboot.

xmayhemreturnsx said:
Try Skt tool and fix fastboot.
Click to expand...
Click to collapse
can you be more specific about what i have to do , i really don't understand.
Guys, please help me :crying:. I feel so hopeless

lordgon said:
can you be more specific about what i have to do , i really don't understand.
Guys, please help me :crying:. I feel so hopeless
Click to expand...
Click to collapse
I'm sorry but I meant to say Srk Tool. you can find it here http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 . Once you download the tool open it up and go to fixed utility (4) and then press fix fastboot.

xmayhemreturnsx said:
I'm sorry but I meant to say Srk Tool. you can find it here http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 . Once you download the tool open it up and go to fixed utility (4) and then press fix fastboot.
Click to expand...
Click to collapse
Thank you so much. May i asked if its worked for an lg without usb debugging ( i stuck in the bootloop so i can not enable it) and i havent rooted my device yet?

lordgon said:
Thank you so much. May i asked if its worked for an lg without usb debugging ( i stuck in the bootloop so i can not enable it) and i havent rooted my device yet?
Click to expand...
Click to collapse
It should work just fine.

N7 (3G, 2012) bricked? Boot mode, no recovery. N Toolkit doesn't flash.

Hello there.
I am writing because I need your help on unbricking my Nexus 7 3G (2012). Yesterday night I was trying to upgrade it from 5.1.0 to 5.1.1 (from the OTA) and I couldn't because I had an error produced by Stickmount. It changed a file on system/bin which I tried to push manually (following some thread's intructions on XDA) and it didn't work, showing error Status 7 (unexpected content on file debuggerd).
Because of that, I decided to flash the 5.1.1 system image using Nexus Toolkit. I set it up so it'd download and install it automatically (using the "Flash stock + Unroot" option). Everything went okay and started the flashing process until the command prop window force closed mid flash, thing that never happened to me before (as I had tried many times flashing from zero my N7 before).
I tried to start the Toolkit again and the command prop window says it flashes bootloader and radio img's successfully, but then a line of code appears and the cmd window force closes again (it says "No se esperaba ( en este momento" or roughly translated as "The ( was not expected at this moment" into English) and my N7 turns off.
Next, I try to turn it on and it shows the Google logo and a green arrow saying "start". I press it and the N7 reboots to the same screen, saying "booting failed" at the top of the screen. If I choose recovery, the same thing happens.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I just can make it to boot to bootloader mode but I cannot flash the firmw (even when this mode must be selected in order to the Toolkit to start flashing). It shows the same line of unexpected code as above.
I tried pushing the files manually using ADB and I cannot may it work either.
What can I do to solve this? I've read that as long as you can get to bootloader mode you can unbrick a device.
I hope you could help me out. Thanks in advance.

Anyone?

Im not a expert, but so if you in bootloader, fastboot (android sdk) dont see your nexus? For check type - 'fastboot devices', if that return something, you can use it to flash recovery/or whole system.
Im linux user, so I dont know how to check how visible is device in windows - and whether drivers are working properly.
I'm sorry if I say the obvious, I just would like to help as much I can. Good luck!

wombat3 said:
Im not a expert, but so if you in bootloader, fastboot (android sdk) dont see your nexus? For check type - 'fastboot devices', if that return something, you can use it to flash recovery/or whole system.
Im linux user, so I dont know how to check how visible is device in windows - and whether drivers are working properly.
I'm sorry if I say the obvious, I just would like to help as much I can. Good luck!
Click to expand...
Click to collapse
Thanks wombat. Actually, the N7 is listed under adb devices. It starts the flashing process but ends automatically without finishing the installation.

[SOLVED] Can't boot, can't boot recovery, oem locked, usb debugging disabled

Happened when I was updating twrp:
I downloaded the .img from their website, booted into my older version of twrp, went to flashing pressed the butting in the bottom right corner, selected the file and selected 'recovery'
Said it was successful, so I rebooted, then it wouldn't do anything anymore except for fastboot.
1. Can't boot into recovery
2. Can't boot normally
3. USB debugging disabled
4. oem locked
Only thing I can enter is fastboot.
I followed this guide, but no luck on my end.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/

Have you tried this?
http://forum.xda-developers.com/oneplus-2/general/guide-return-op2-to-100-stock-unbrick-t3229606
and
All in one toolbox by mauronofrio.
I my self had lost recovery myself and flashed stock image in toolbox and then flashed image from above link to restore to stock and started custom rom process again.
Should not erase twrp once recovered if it has reflash your previous version of twrp or hybrid version.
Hope this helps.

passion8059 said:
Have you tried this?
http://forum.xda-developers.com/oneplus-2/general/guide-return-op2-to-100-stock-unbrick-t3229606
and
All in one toolbox by mauronofrio.
I my self had lost recovery myself and flashed stock image in toolbox and then flashed image from above link to restore to stock and started custom rom process again.
Should not erase twrp once recovered if it has reflash your previous version of twrp or hybrid version.
Hope this helps.
Click to expand...
Click to collapse
It's no use because oem is locked. That means I can't flash anything.

toolbox should still help you unlock bootloader again

Just use the Qualcomm factory restore image to return the phone to original shape of things.

passion8059 said:
toolbox should still help you unlock bootloader again
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pitrus- said:
Just use the Qualcomm factory restore image to return the phone to original shape of things.
Click to expand...
Click to collapse
I have no idea how I would do this without being able to flash anything.

Do you mean that the Qualcomm download program also crashes like fastboot? Sounds like you either have some problems with your windows installation or perhaps you haven't searched for and downloaded the Qualcomm restore if your still trying to flash the ordinary way instead of the emergency way.

Was able to fix it when I was messing around. Not sure what I did but it worked.
Thank you for all your help guys

Theevilsocks said:
Was able to fix it when I was messing around. Not sure what I did but it worked.
Thank you for all your help guys
Click to expand...
Click to collapse
I'm having this problem too, and this isn't helpful. What were the last steps, or at least some of them, that you took to get it working? Which toolkit/script/program were you using? etc

Redjax said:
I'm having this problem too, and this isn't helpful. What were the last steps, or at least some of them, that you took to get it working? Which toolkit/script/program were you using? etc
Click to expand...
Click to collapse
I used this tool: http://forum.xda-developers.com/oneplus-2/general/guide-official-op2-stock-reset-to-oos-3-t3402020
I fiddled around a bit with it, but I'm not sure what I did, and I already deleted the files.

Theevilsocks said:
I used this tool: http://forum.xda-developers.com/oneplus-2/general/guide-official-op2-stock-reset-to-oos-3-t3402020
I fiddled around a bit with it, but I'm not sure what I did, and I already deleted the files.
Click to expand...
Click to collapse
Literally JUST finished with this guide, and my OP2 is alive again! I was going to come back and post. Thanks for the link.
Anyone trying to use this guide without success:
There's one very important step I somehow missed. You MUST disconnect your phone, hold the power button for ~15-20 seconds until it's off, and hold the Volume+ button, THEN plug it back in. Your computer will make the "device connected" sound, but the screen will stay black. THIS IS OK! That means you're in a special recovery, which is where you need to be for the tool.
I also installed the certificate file in the folder I downloaded, then rebooted (it did not work before a reboot, but did work after).
So, the steps:
1. Download the files, make sure your signature signing for drivers is off.
2. Install the trusted certificate, then the driver.
3. Reboot PC
4. Power off phone (hold power for 15-20 secs), hold volume+, then connect through USB (wait for device connected sound, screen on phone will still be black)
5. Run the tool (I ran as admin, not sure if that's required)
6. Weep with joy that you finally found a solution that works.

TWRP Not Opening And adb Showing Unauthorized.

Help Me Anyone Guys, I'm In Extreme Problem.
Unfortunately, I Did Something With TWRP Backups, And Then TWRP Is Not Opening, It Just Restarts, And When Connected To PC, adb Shows Device Unauthorized And Doesn't Show Any Authorisation Pop UP On Mobile. What Should I Do?
I Can't Even Factory Reset From Settings As It Makes A Reboot And Does Nothing.
Help Would Be Extremely Appreciated.
Thanks In Advance.

Reinstall drivers properly, mostly don't try in win 10, 10 is **** causes bugs, use win 7 or 8 or 8.1 also enable oem unlocking from settings and enable USB debugging
Sent from my Moto G4 Plus using Tapatalk

Krsambhav16 said:
Help Me Anyone Guys, I'm In Extreme Problem.
Unfortunately, I Did Something With TWRP Backups, And Then TWRP Is Not Opening, It Just Restarts, And When Connected To PC, adb Shows Device Unauthorized And Doesn't Show Any Authorisation Pop UP On Mobile. What Should I Do?
I Can't Even Factory Reset From Settings As It Makes A Reboot And Does Nothing.
Help Would Be Extremely Appreciated.
Thanks In Advance.
Click to expand...
Click to collapse
Need a little more details to help (Which ROM, what exactly did you do, which version of TWRP, etc)
Have you tried the 'Revoke USB Debugging Authorisation' option? It worked for me when my phone wasn't recognised.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm not sure if it's a W10 issue as I've been doing everything with W10 since then beginning with no issues.
⌲ from my Moto G⁴ Plus / Tapatalk

1chrome said:
Need a little more details to help (Which ROM, what exactly did you do, which version of TWRP, etc)
Have you tried the 'Revoke USB Debugging Authorisation' option? It worked for me when my phone wasn't recognised.
I'm not sure if it's a W10 issue as I've been doing everything with W10 since then beginning with no issues.
⌲ from my Moto G⁴ Plus / Tapatalk
Click to expand...
Click to collapse
Hello Brother, Meeting U After Many Days.
First, I Have Moto Stock ROM, And That **** Doesn't Has Revoke Option.
Last, Yes I Was Using Windows 10 And It Detects The Device But Doesn't Gets Authorized By Phone Due To No Pop Up.
Thanks
EDIT : TWRP 3.0.2-2 r2 I Think.
EDIT 2 : I Restored My Old Backup And Unfortunately I Forgot To Wipe Partitions And Then Got This Problem.

I am not what exactly went wrong. Boot into fastboot mode and If you're PC is detecting fastboot, try booting into TWRP using an image and see if you can restore a backup.
Or if you have your personal files backed up, just flash the Stock Nougat ROM via fastboot.
That will clear up everything. Or if you want a more flexible ROM, just go for a custom one
⌲ from my Moto G⁴ Plus / Tapatalk

1chrome said:
I am not what exactly went wrong. Boot into fastboot mode and If you're PC is detecting fastboot, try booting into TWRP using an image and see if you can restore a backup.
Or if you have your personal files backed up, just flash the Stock Nougat ROM via fastboot.
That will clear up everything. Or if you want a more flexible ROM, just go for a custom one
⌲ from my Moto G⁴ Plus / Tapatalk
Click to expand...
Click to collapse
But adb Is Showing Unauthorized So How Do I Use Fastboot?

Krsambhav16 said:
But adb Is Showing Unauthorized So How Do I Use Fastboot?
Click to expand...
Click to collapse
Did you tried other computer/laptop, or change the port you are using, try to change the data cable as these are the basic steps we do in these cases.
If problem continue persist try to use the Windows 7 for flashing via abd, also try to boot into safe mode and then try the adb may help you.

avirk said:
Did you tried other computer/laptop, or change the port you are using, try to change the data cable as these are the basic steps we do in these cases.
If problem continue persist try to use the Windows 7 for flashing via abd, also try to boot into safe mode and then try the adb may help you.
Click to expand...
Click to collapse
OK I Will Try On Friends pc. Thanks

Stuck at ASUS IN SEARCH OF INCREDIBLE screen

I've seen this kind of problem alot here but here's my problem and why nothing helps.
Basically I wasn't updating my device I was just texting or something like that when my phone went black except the system outline(you know time, signal, wifi/net conection etc. on upper part of phone) so I forced it to shoot down and after that when I try to turn it on it's stuck at ASUS logo(I can't take picture of my phone but it's same as on the picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now I tried factory reseting it and entering the recovery mode, none of it seems to help and the problem is that my PC can't detect my zefone when I connect it(and I'm pretty sure it wasn't detectable before this problem either so I don't think those are connected issues).
Any suggestions?

nc96 said:
I've seen this kind of problem alot here but here's my problem and why nothing helps.
Basically I wasn't updating my device I was just texting or something like that when my phone went black except the system outline(you know time, signal, wifi/net conection etc. on upper part of phone) so I forced it to shoot down and after that when I try to turn it on it's stuck at ASUS logo(I can't take picture of my phone but it's same as on the picture:
Now I tried factory reseting it and entering the recovery mode, none of it seems to help and the problem is that my PC can't detect my zefone when I connect it(and I'm pretty sure it wasn't detectable before this problem either so I don't think those are connected issues).
Any suggestions?
Click to expand...
Click to collapse
are you tried flashing system via ''apply update from adb'' command of recovery

Yes, as grady_8 said, Flash update using ADB from your recovery, but you need ADB and Fastboot drivers first, then your PC will able to detect your ZF.

https://forum.xda-developers.com/zenfone-5/help/bootlooped-bricked-returning-to-stock-t3358662
try this guide

You must be downgrade first, because the lolipop firmware not support adb flash. Download firmware save at same folder with file extracted. (Version . UL_WW.2.22.40.54-user.zip. )extract it to new folder, then click shift+right mouse, open command here. Then type fastboot flash boot boot.img then' fastboot flash recovery recovery.img , then ' fastboot flash fastboot fastboot.img. after that reboot to recovery manualy, then aply update from adb . Then In CMD type ' adb sideload <the name of firmware>.zip (example = adb sideload UL_WW.2.22.40.54-user.zip ) Wait the progress. Then finish.