Database Users

[Q] Can "see" device in ADB, not in fastboot....

Hey guys,
Bare with me please as I am fairly new-ish to Android but have some experience with Samsungs, HTCs and the beloved LG GT540.....
I appreciate if anyone can help me on my plight.....
My girlfriend was running Cyanogen Mod for the last year or so on her device and decided that she wanted to try out a different ROM on her phone....
I wanted to install the Oxegen ROM....
Originally I was thinking it would be easy and I could put it on through Clockwork Recovery and flash the zip no problem, for some reason when I rebooted to recovery clockwork would not load up on the device.... just blank screen....
Not content with this, bored on a Sunday afternoon I gave it a couple of hours of my time and in the process messed my girlfriends phone up....
What I did was I tried flashing back to stock using the LG KDZ updater, that was fine and the phone rebooted and has since stuck on the Android logo....
According to this thread : http://forum.xda-developers.com/showthread.php?t=1078745&highlight=stuck+on+android+screen I gave all this a go and I can not get the device showing up in Fastboot, I can not enable USB debugging on it either as I can not get into the phone to tick the box....
In my cmd prompt I am seeing 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"
}
In my device manager when my device is connected and powered on I am seeing this :
When I am connected and the device is in "download mode" my devices are like this :
I understand the steps provided in the link above and I am fairly confident I could do them if I can get the device "seen" in Fastboot....
I have installed and re-installed all the USB drivers in hope that it may be a driver issue, now I am wondering is it maybe my OS? Win7 64Bit Ultimate?
I can try it on XP netbook if thats all thats causing my issues....
I am kinda lost now and wondering have I bricked it? It will be the first phone I have if thats the case....
Any help would be appreciated, thanks a lot guys....
Mods if this is in the wrong area, please feel free to move my post.....

did u go to fastboot (power+camera pressed when booting up).
well, from my experience, if i flash incorrectly (via fastboot or recovery), it will go bootloops or go to clockwork, or if i flash incorrectly via kdz, i've got stuck in LG logo or got linux kernel panic.
it seems to me u've flash kdz incorrectly. flash kdz with fastboot mode via download (or emergency mode).
try this:
http://forum.xda-developers.com/showpost.php?p=13184840&postcount=42
and make sure u already install all LG drivers (u can Google those).
gud luck. if else fails, put a very sad and stupid face, act as u dont know anything, bring the phone to the LG representative in ur town.
idk for 64 bit version as i use 32 bit. u can try find pdanet driver, there is 64 bit driver there and it install fastboot well in PC.

m1st3r1 said:
did u go to fastboot (power+camera pressed when booting up).
well, from my experience, if i flash incorrectly (via fastboot or recovery), it will go bootloops or go to clockwork, or if i flash incorrectly via kdz, i've got stuck in LG logo or got linux kernel panic.
it seems to me u've flash kdz incorrectly. flash kdz with fastboot mode via download (or emergency mode).
try this:
http://forum.xda-developers.com/showpost.php?p=13184840&postcount=42
and make sure u already install all LG drivers (u can Google those).
gud luck. if else fails, put a very sad and stupid face, act as u dont know anything, bring the phone to the LG representative in ur town.
idk for 64 bit version as i use 32 bit. u can try find pdanet driver, there is 64 bit driver there and it install fastboot well in PC.
Click to expand...
Click to collapse
Fastboot and ADB works on Windows 7 Home Premium 64bit. I installed LG Drivers then Google USB Driver. It worked then. But I know I did struggle to finally get it working.

Thanks a lot for the advice and replies guys....
As I said, I think my problem lies in not being able to tick the USB debugging option on the phone as I can not boot into the phone to do so....
Is there a way to enable USB debugging over ADB?
As I said, I can "see" the phone responding to ADB, just not fastboot!
I am in the process of installing everything and starting fresh on the Xp netbook, if this fails I would say its new phone time for my g/f, Sony X8 is 80 euro on our network so if the worst comes to the worst I will get her a new one....
Much appreciated guys and if anyone has anything to the thread I will be all ears...
Cheers!

Ko_Ka said:
Thanks a lot for the advice and replies guys....
As I said, I think my problem lies in not being able to tick the USB debugging option on the phone as I can not boot into the phone to do so....
Is there a way to enable USB debugging over ADB?
As I said, I can "see" the phone responding to ADB, just not fastboot!
I am in the process of installing everything and starting fresh on the Xp netbook, if this fails I would say its new phone time for my g/f, Sony X8 is 80 euro on our network so if the worst comes to the worst I will get her a new one....
Much appreciated guys and if anyone has anything to the thread I will be all ears...
Cheers!
Click to expand...
Click to collapse
i think u got it wrong.
read here: http://android-dls.com/wiki/index.php?title=Fastboot and here: http://wiki.cyanogenmod.com/wiki/Fastboot
first of all, i need to ask u the question (again), can u boot to fastboot (or bootloader) when u pressed power (the reject/red phone button) and camera button altogether? the fastboot screen in the phone will be like black screen, but with a little amount of backlight (u'll notice the difference) or blue screen with texts if u flash a kdz-modified-fastboot. if u cant go to bootloader/fastboot, then u need to flash a kdz with fastboot.
u can try this: when u type adb devices, type: adb reboot bootloader
though im not sure if ur gf's phone has fastboot/bootloader (might be missing during the kdz flashing that u've done).
when u type adb devices

m1st3r1 - if you ever come to Dublin, I will buy you a beer!
After nearly 3 days of pulling what hair I have left on my head out, my problem was I was mistaking Fastboot for Download mode.....
I was connecting the phone holding the volume down so it came up "download mode" now all I did was hold the camera + red button and off it went with the command from the post above....
I feel like an idiot, but im a happy idiot right now.....
Thanks a lot, means a lot to me.... (and my girlfriend!)

LOL welcome to the hackers club

[Q] Nexus 7 hard brick ?

My nexus has been rooted. I up rom 4.3 by nexus 7 toolkit failed. When it change to fastboot mode, recovery failed, start failed so i choose power off. Now it won't boot just black screen forever (. Somebody help me please !

minhpro9xhp said:
My nexus has been rooted. I up rom 4.3 by nexus 7 toolkit failed. When it change to fastboot mode, recovery failed, start failed so i choose power off. Now it won't boot just black screen forever (. Somebody help me please !
Click to expand...
Click to collapse
Just manually try flashing recovery through fastboot .
Code:
fastboot flash recovery recovery.IMG
There are tons of similar threads like this . please try to search before posting.

Red Devil said:
Just manually try flashing recovery through fastboot .
Code:
fastboot flash recovery recovery.IMG
There are tons of similar threads like this . please try to search before posting.
Click to expand...
Click to collapse
Thank for your help but i tried and it just show "waiting for devices". My nexus still not display

minhpro9xhp said:
Thank for your help but i tried and it just show "waiting for devices". My nexus still not display
Click to expand...
Click to collapse
Oh did you install the drivers that are required on Windows from Asus ? Make sure you install them.
Code:
fastboot devices
will let you know if your device is connected well.

Red Devil said:
Oh did you install the drivers that are required on Windows from Asus ? Make sure you install them.
Code:
fastboot devices
will let you know if your device is connected well.
Click to expand...
Click to collapse
yes, i insalled driver from asus and i tried to press POWER ON and VOLUME DOWN so it change to APX mode. So, i update driver, pick driver from my computer>C:user/minh/download/usb_driver and nexus 7 still on APX mode with "ASUS Transformer prime APX interface" driver.
fastboot devices--->nothing
adb devices-->nothing

hi same thing happened to me
can you post the link of where to get the asus drivers from
any luck with your nexus yet??

Driver from Asus? Pretty sure you just use the one from the Android SDK.

GldRush98 said:
Driver from Asus? Pretty sure you just use the one from the Android SDK.
Click to expand...
Click to collapse
thanks for that
and do you have any idea on how to get the nexus back up and running
or anyone else

Can you get in to fastboot? If so, you can flash a recovery or system imaged or anything from there. Fastboot should always work (volume up + volume down + power all at the same time)

GldRush98 said:
Can you get in to fastboot? If so, you can flash a recovery or system imaged or anything from there. Fastboot should always work (volume up + volume down + power all at the same time)
Click to expand...
Click to collapse
yes i was, when in fastboot mode i choosed start and recovery mode but all failed so i choosed power off (very stupid thing). Now my device is brick.

minhpro9xhp said:
yes i was, when in fastboot mode i choosed start and recovery mode but all failed so i choosed power off (very stupid thing). Now my device is brick.
Click to expand...
Click to collapse
Tried plugging it in to the a/c adapter and charging for a few hours?

minhpro9xhp said:
fastboot devices--->nothing
adb devices-->nothing
Click to expand...
Click to collapse
^ This sounds like a driver issue if you are not getting anything to show up. You could try the zip I have attached its the google drivers I use and they work fine.
{
"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"
}
View attachment google-usb_driver.zip

GldRush98 said:
Tried plugging it in to the a/c adapter and charging for a few hours?
Click to expand...
Click to collapse
i tried
dpdurst said:
^ This sounds like a driver issue if you are not getting anything to show up. You could try the zip I have attached its the google drivers I use and they work fine.
Click to expand...
Click to collapse
i don't thing the driver issue, i tried many driver but it not working.
google nexus 7 ADB interface
google nexus ADB interface
google nexus 7 BootLoader interface
google nexus bootloader interface
asus fastboot interface
...

thanks for replying
i tried many times to do various combinations o fholding down the power and up,down volume...nothing
i will try later when i am on my desktop to look at fastboot...and update the drivers
right now when i plug the nexus into the pc it comes up as not recognised...
if the nexus were completely dead would it still even come up in the device manager??
i also tried to pull the battery for a few minutes and then try again....nothing
i charge it into the mains with cable and nothing...
i will need to check it when i get home on my main pc in a few hours
please wirte any further siggestions or any web video/links which may help in this situation
THIS is the point where i turned the power off in the FIRST SCREEN
http://loewald.com/blog/?p=5198

i am on my main pc right now
i have downloaded the SDK manager and installed the Android SDK platform tools and Google USB driver
nothing happens when i plug the nexus into the PC
do i need to actually manually install these drivers or they are already installed when i ran the SDK manager...
the nexus shows as unknown device right now

Try to install WugFresh's toolkit. http://www.wugfresh.com/
Follow the driver installation guide and make sure thet the previous drivers is removed.
Choose the recomended driver.
If you can start your device in fastboot mode (bootloader) it should be salvageable.
If you use Windows 8, getting a working driver can be quite a struggle.

it was wugfresh toolkit that i was using
so i uninstalled all drivers and installed the drivers from his toolkit
sadly the usb device is still not recognised

well, i searched google and they said there was one way to fix hard brick nexus 7. It is using "JIG usb". If somebody used "JIG usb" please reply me.

I think I'm having the same problem as you, but I am still able to get into bootloader mode. It may take up to around 20 seconds holding the volume down and power button to get back into bootloader mode. In fastboot bootloader, going into recovery freezes (freezes on the "Teamwin" screen), "start" freezes on the "Google" screen with padlock unlocked. Used Wug's to try to go back to factory setting (but to 4.3 instead of 4.2.2), failed to write 'bootloader' and device never boots back up when it says "waiting for device". Then tried using Nexus 7 toolkit (not Wug's) to lock it back up and now I can't unlock again...same thing..."waiting for device" and device never boots back up.

any update for this problem?
any update for this problem?
i try alot of solution but nothing change
i saw N7 can connect to APX with correct Driver however we can do anything
i try connect power about 8 h but nothing change
what the F *K with OTA update ........

[Solved]D800 Bricked after using wrong AutoRec,No download mode

hi everyone, i accidentaly used the AutoRecLs980 app to flash the recovery to a D800 and now the device is bricked and wont boot on recovery nor on android,,, just keep showing those lines:
[850] Fastboot mode started
[900]udc_start()
i tried the command "fastboot devices" on sdk and i got 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"
}
like is partially recognizing the device..
>>can i try flashing a TWRP.img? or what i did has broken other than recovery partitIon on the devices and that wont solve my problem..
i also founded this: http://forum.xda-developers.com/showthread.php?t=2582142 but dont know if will help me..
thanks so much for triying to help me.

elmy2424 said:
hi everyone, i accidentaly used the AutoRecLs980 app to flash the recovery to a D800 and now the device is bricked and wont boot on recovery nor on android,,, just keep showing those lines:
[850] Fastboot mode started
[900]udc_start()
i tried the command "fastboot devices" on sdk and i got this:
like is partially recognizing the device..
>>can i try flashing a TWRP.img? or what i did has broken other than recovery partitIon on the devices and that wont solve my problem..
i also founded this: http://forum.xda-developers.com/showthread.php?t=2582142 but dont know if will help me..
thanks so much for triying to help me.
Click to expand...
Click to collapse
jump on irc, freenode, lg-g2 channel. Tell them you used the wrong auto-rec and u are able to get into fastboot. They will give you/direct you to partitions for your phone. You will then need to flash these partitions. Probably the correct aboot and laf(downloadmode), and recovery(maybe not). You will then be able to get into download mode, where you can flash a stock rom. Or possibly give you old aboot and directly flash a custom recovery. Not sure. Go and ask.

elmy2424 said:
hi everyone, i accidentaly used the AutoRecLs980 app to flash the recovery to a D800 and now the device is bricked and wont boot on recovery nor on android,,, just keep showing those lines:
[850] Fastboot mode started
[900]udc_start()
i tried the command "fastboot devices" on sdk and i got this:
like is partially recognizing the device..
>>can i try flashing a TWRP.img? or what i did has broken other than recovery partitIon on the devices and that wont solve my problem..
i also founded this: http://forum.xda-developers.com/showthread.php?t=2582142 but dont know if will help me..
thanks so much for triying to help me.
Click to expand...
Click to collapse
Damn please report back if you resolve your issue. I'm sure you'll help anyone else who might themselves in a similar situation

You can install the Stock ROM For KDZ file, the G2 will be restored...
Search in Google/Youtube: Back To Stock ROM LG G2
PS. You can only enter the Download Mode with the G2 connected with PC by USB

he can't enter dld mode.
1. download autorec for your version
2. extract aboot - boot - laf
3.
fastboot flash aboot aboot.img
fastboot flash boot boot.img
fastboot flash laf laf.img

I did the same thing. Recovered by flashing the correct laf.img with fastboot, which repaired download mode. Then use download mode with a .kdz file and the (un)official LG rescue tool.
Sent from my LG-D801 using XDA Free mobile app

did you readed the title of mi post???
NO DOWNLOAD MODE...

@bender_007 @jug6ernaut@ahilliard
really thanks:laugh: ill do it as soon as i get in my house.
i was thinking to flash all the partitions since i didn´t know which one had the DOWNLOAD MODE xD, thanks again

elmy2424 said:
@bender_007 @jug6ernaut@ahilliard
really thanks:laugh: ill do it as soon as i get in my house.
i was thinking to flash all the partitions since i didn´t know which one had the DOWNLOAD MODE xD, thanks again
Click to expand...
Click to collapse
Just the ones I wrote. Don't touch others.

Solved

elmy2424 said:
Solved
Click to expand...
Click to collapse
I'm sorry that I write here but if I do not want to create a new topic. Maybe someone is able to help?
Hello my problems started up in the morning as I came up with a kernel update.
Mistakenly threw versions of the D800 and the phone went into fastboot.
I tried the method with a live CD of Ubuntu but it does not fit me these many partitions so I can not write it these paintings partition.
I tried to unpack the correct kernel to a file boot.img fastboot flash I uploaded by write and quite like to be spoiled because I wrote that there is no certificate or something - so as to completely fell boot.
But after some time did enter into download mode I uploaded versions V220D and went.
Now phone can enter to download mode but charges only to the logo and the LED flashes blue and green.
The computer sees the phone software from LG emergency phone does not play because he writes with is the newest version but see the battery level and what I currently versions.
What else to do to restore phone?
I would be very grateful.

will find some time for you later

bender_007 said:
will find some time for you later
Click to expand...
Click to collapse
thank you very much

sarzyk said:
thank you very much
Click to expand...
Click to collapse
hm..I see you managed to flash the rom ?
so the problem is you didn't wipe.
turn the device OFF
hold power + volume down until you see the LG logo, release the buttons for a moment and then hold volume down + volume up. On the white screen confirm 2-3 times with power button. After the factory reset (the thing you just did) it will boot.

bender_007 said:
hm..I see you managed to flash the rom ?
so the problem is you didn't wipe.
turn the device OFF
hold power + volume down until you see the LG logo, release the buttons for a moment and then hold volume down + volume up. On the white screen confirm 2-3 times with power button. After the factory reset (the thing you just did) it will boot.
Click to expand...
Click to collapse
you are a god.
Cleans all day interencie but nowhere have written about this to keep the volume + and - raze ..
For now operates proof, and write exactly what and how.
We would like to thank my friend.
Please write more as I'll official* Rom from LG is the site can check if a ROOT or another Rom if it was uploaded?
Where can I check whether they were any signs of interference?
Is it only in Download Mode it says?

Can't boot into recovery or system

I flashed the latest chinese 7.1.1 and it bootloops. So I tried going into recovery to wipe/reinstall and found that it wasn't working. The led blinks 3 times and the phone turns off.
I can boot into bootloader, but Windows is not recognizing my device, it just says "Android" under device manager.
Any ideas how to fix this?

have you tried EDL method to restore your original firmware?

otaconremo said:
have you tried EDL method to restore your original firmware?
Click to expand...
Click to collapse
i dont know how to boot to EDL
power+vol up gives me 3 led blinks and then turns off
power + vol down does nothing, just tries to boot the rom
EDIT: what a moron... vol down + vol up + power boots into EDL just fine, but the same, windows cant recognize the device and install the proper driver
I tried with these drivers:
Qualcomm QUSB_BULK Drivers
Version: 2.1.1.0 (2014-01-25)
WHQL signed.
but nothing

bornlivedie said:
i dont know how to boot to EDL
power+vol up gives me 3 led blinks and then turns off
power + vol down does nothing, just tries to boot the rom
EDIT: what a moron... vol down + vol up + power boots into EDL just fine, but the same, windows cant recognize the device and install the proper driver
I tried with these drivers:
Qualcomm QUSB_BULK Drivers
Version: 2.1.1.0 (2014-01-25)
WHQL signed.
but nothing
Click to expand...
Click to collapse
try to remove the previous drivers on windows or reinstall another qcom driver. or maybe try from another computer. unless it gets 9008 mode in windows, you can't do anything on it.

otaconremo said:
try to remove the previous drivers on windows or reinstall another qcom driver. or maybe try from another computer. unless it gets 9008 mode in windows, you can't do anything on it.
Click to expand...
Click to collapse
Already did all those things
tried multiple installations of windows, multiple drivers
QUSB_BULK is installed but MiFlash or axon7root won't detect it

Dumb question but did you try booting normally? Power button only, no vol buttons.
Should take you to the ZTE logo followed by the bootloader unlocked screen.

You said you can boot into bootloader, right? Did you try fastboot commands? If fastboot works, try flashing stock boot and recovery from yoir previous rom and reboot to recovery.

t2jbird said:
Dumb question but did you try booting normally? Power button only, no vol buttons.
Should take you to the ZTE logo followed by the bootloader unlocked screen.
Click to expand...
Click to collapse
Yes, i can see the bootloader screen and go into fastboot.
otaconremo said:
You said you can boot into bootloader, right? Did you try fastboot commands? If fastboot works, try flashing stock boot and recovery from yoir previous rom and reboot to recovery.
Click to expand...
Click to collapse
Windows is not recoginizing the phone while in fastboot. It just says "Android" under device manager. Can't make it work with google usb drivers.
I need the correct drivers to flash the firmware while in EDL mode.

bornlivedie said:
Yes, i can see the bootloader screen and go into fastboot.
Windows is not recoginizing the phone while in fastboot. It just says "Android" under device manager. Can't make it work with google usb drivers.
I need the correct drivers to flash the firmware while in EDL mode.
Click to expand...
Click to collapse
Possibly it is a driver issue. Maybe try disabling driver signature in windows? Just google it.

otaconremo said:
Possibly it is a driver issue. Maybe try disabling driver signature in windows? Just google it.
Click to expand...
Click to collapse
It's off...
I just reinstalled windows 10 and now this is happenning:
Windows 10 recognizes my device as Handset Diagnostic Interface(DFU) (COM3) after installing the QUSB_BULK driver
forcing the QUSB_BULK drivers is not working, as it says that windows couldn't verify the compatibility of the drivers, installs them anyway, and shows the device as COM10 and no tool detects the phone....

Try reading this thread. They're discussing about drivers here as well.
https://forum.xda-developers.com/axon-7/help/a2017g-totally-bricked-t3537990
And here's another one i came across with.
https://forum.xda-developers.com/axon-7/help/fastboot-recognizing-phone-bootloader-t3492201

I also had trouble with the drivers when trying to unlock the bootloader. It wasn't easy.
I had to put the phone in CD mode to install the supplied drivers. It's a must.
Then I followed the guide and some guys' extra comments on the post to unlock the G variant. It was tricky... I suggest you read that guide and "choose an user name" comment here: https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379/page32

I have terrible experience between Windows 10 and axon's driver - it's not work with any reason.
Try with again with Windows 7 (or at least Windows 8.1) , it may work for you.

bornlivedie said:
i dont know how to boot to EDL
power+vol up gives me 3 led blinks and then turns off
power + vol down does nothing, just tries to boot the rom
EDIT: what a moron... vol down + vol up + power boots into EDL just fine, but the same, windows cant recognize the device and install the proper driver
I tried with these drivers:
Qualcomm QUSB_BULK Drivers
Version: 2.1.1.0 (2014-01-25)
WHQL signed.
but nothing
Click to expand...
Click to collapse
If you're able to connect to EDL then is driver is the issue... Try connecting from your friend pc...
I always go using the below method to get in EDL mode.. If you haven't tried... Check this as well
{
"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 tried flashing the chinese firmware as well without b15 bootdtack... But able to boot to recovery.. But the version of twrp shows as 3.0N 1...i thought it's a glitch and flashed the recovery 3.04.1 and it showed correctly... Don't know it helps at this level
Sent from my ZTE A2017U using Tapatalk

`SBR` said:
If you're able to connect to EDL then is driver is the issue... Try connecting from your friend pc...
I always go using the below method to get in EDL mode.. If you haven't tried... Check this as well
I tried flashing the chinese firmware as well without b15 bootdtack... But able to boot to recovery.. But the version of twrp shows as 3.0N 1...i thought it's a glitch and flashed the recovery 3.04.1 and it showed correctly... Don't know it helps at this level
Click to expand...
Click to collapse
3.0.N1 came from the bootstack. If I remember correctly, it's one that unjustified_dev compiled to go with it.

lumia 520 bricked after flash of android and now showing android in drivers

my lumia 520 is bricked after flash of android but is vibrating and and connecting to pc but showing android in device managment. any solutions?
not detected by cmd or windows device recovery tool.

janjuaalpha said:
my lumia 520 is bricked after flash of android but is vibrating and and connecting to pc but showing android in device managment. any solutions?
not detected by cmd or windows device recovery tool.
Click to expand...
Click to collapse
Try to get into recovery by press the power button and volume + at the same time
If you can get to recovery , you can try it again , or comeback Windows Phone

Ryonic said:
Try to get into recovery by press the power button and volume + at the same time
If you can get to recovery , you can try it again , or comeback Windows Phone
Click to expand...
Click to collapse
it vibrates but shows only android i have tried every key combination.

janjuaalpha said:
it vibrates but shows only android i have tried every key combination.
Click to expand...
Click to collapse
Do you flash the rom yet?, or just install bootloader and recovery?
If your device get bricked after run the uefi2lk.cmd , tell me and i will show you the way to fix it
P/s : Sorry about my bad english skill

i flashed bootloader and recovery and my nokia bricked after that

Ryonic said:
Do you flash the rom yet?, or just install bootloader and recovery?
If your device get bricked after run the uefi2lk.cmd , tell me and i will show you the way to fix it
P/s : Sorry about my bad english skill[
hello plzzz i went restore my nokia lumai 520 andrio TO windows i have backup flash plzzzz send me tuto or video plzzzzzzz
Click to expand...
Click to collapse

janjuaalpha said:
my lumia 520 is bricked after flash of android but is vibrating and and connecting to pc but showing android in device managment. any solutions?
not detected by cmd or windows device recovery tool.
Click to expand...
Click to collapse
You phong is working,just need flash recovery

Ryonic said:
Do you flash the rom yet?, or just install bootloader and recovery?
If your device get bricked after run the uefi2lk.cmd , tell me and i will show you the way to fix it
P/s : Sorry about my bad english skill
Click to expand...
Click to collapse
no i just flashed recovery but tried to flash rom but not sucessful

I'm having a really similar issue that I've had for nearly a whole year after flashing Android. I myself am trying to roll back to WP 8.1 however I cannot flash the hex file (emergency) back.
{
"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"
}
Also I want to point this out, Lumia 520/521 devices have issues with reading and writing as explained here

So you install the recovery of android already? , if that so , you can't used this way to roll back to WP 8.1
P/s: I've met a lot of error when try to install android on my lumia 520 , and finally , i can't touch or do anything in TWRP because my digitizer is not original . So I rollback to windows 8.1 and sell it
Use should used this tutorial : https://forum.xda-developers.com/no...nt/restore-windows-phone-8-installed-t3608223
You need to have a backup , if you don't , you have to stick with android.
I think all the error when install android on lumia 520/521/525 could all be fixed , except when you have a samsung emmc :fingers-crossed:

Try to enter recovery with fastboot. Connect the Phone to the PC, and open fastboot in cmd and type this:
fastboot oem reboot-recovery
If you installed successfully the recovery, it will appear in the phone. (It may take 30 seconds or less in appear)

Seems people aren't getting the message
Issue Identification:
Although our investigation is not complete, we’d like to share some initial insight into what we’ve uncovered:
Data writing size & speed: It was discovered that some devices are having trouble accepting the recovery image data being flashed. The blocks of data were too large for some devices to handle, and the memory on the device was having trouble with the speed at which the data was being written. In short, devices were getting too much data, too quickly. This would cause the failure as the new software is corrupted.
Small portion of 520/521 devices affected: As we reviewed logs and worked through issue reproduction, we identified the subset of affected 520/521 devices that may encounter this issue. There is no direct way for an end-user to check their device unfortunately, however it is positive news that not all units would experience this issue.
Click to expand...
Click to collapse

janjuaalpha said:
my lumia 520 is bricked after flash of android but is vibrating and and connecting to pc but showing android in device managment. any solutions?
not detected by cmd or windows device recovery tool.
Click to expand...
Click to collapse
Hi I solve it by installing the Compositive ADB interface driver manually, after this the uefi2lk.cmd detects it and completes the installation of twrp .... the bad thing is that there is still no solution for the micro sd, the chip reading , and the camera and the installation of google play services would be excellent if this could be solved at the moment the only thing I have for solution is to return the movila windows thanks to the help :crying::crying::good:

kristiano646 said:
Hi I solve it by installing the Compositive ADB interface driver manually, after this the uefi2lk.cmd detects it and completes the installation of twrp .... the bad thing is that there is still no solution for the micro sd, the chip reading , and the camera and the installation of google play services would be excellent if this could be solved at the moment the only thing I have for solution is to return the movila windows thanks to the help :crying::crying::good:
Click to expand...
Click to collapse
could you please provide me with the drivers? i cant make uefi2lk ro recognize my phone

Ryonic said:
Do you flash the rom yet?, or just install bootloader and recovery?
If your device get bricked after run the uefi2lk.cmd , tell me and i will show you the way to fix it
P/s : Sorry about my bad english skill
Click to expand...
Click to collapse
Hello. My device bricked after run uefi2lk.cmd and don't detecting with any key combinations. I have backup. Please,help me.

thinhx2 said:
You phong is working,just need flash recovery
Click to expand...
Click to collapse
How to do it?
---------- Post added at 02:43 AM ---------- Previous post was at 02:36 AM ----------
Ryonic said:
Do you flash the rom yet?, or just install bootloader and recovery?
If your device get bricked after run the uefi2lk.cmd , tell me and i will show you the way to fix it
P/s : Sorry about my bad english skill
Click to expand...
Click to collapse
What to do?

thinhx2 said:
You phong is working,just need flash recovery
Click to expand...
Click to collapse
hi, i also having similar issue but in my case i have run uefi2lk.cmd command and after that my phone was bricked......
it only shows android in device manager but can not be detected by windows devide recovery tool or cmd......
will you please let me know the solution in detail as i am a beginner in that kind of works....

adityachoudhary368 said:
hi, i also having similar issue but in my case i have run uefi2lk.cmd command and after that my phone was bricked......
it only shows android in device manager but can not be detected by windows devide recovery tool or cmd......
will you please let me know the solution in detail as i am a beginner in that kind of works....
Click to expand...
Click to collapse
Use fastboot,flash twrp for it,install android

My device is stuck in a boot loop on the first load of Lineage OS 13, nothing on my computer can pick up the phone so I can't fastboot or anything like that. I'm a bit stumped, does anyone have any insight?