Related
Guys,
First of all, hello to all! So, I followed a tutorial to install Froyo on my Defy. Now I'm stuck with my phone trying to boot as soon as i put the battery on, but it never makes it past the "M". I can get into recovery. I wiped data, cache and tried to install the "update.zip" but it aborts saying "signature verification failed." I have the boot file (that was the next step) to install using RSDlite 4.9 but the phone is not even recognized any of my USB ports. Any ideas? Thanks to all in advanced.
press volumn up buton and power button on boot , once you saw the backlit is on , release the button , you will see the rsd litle showing your usb .
dont worry . i think it is your first time to use RSD only
yea i been through that ( doesnt work on vista )
you need to install rsd lite and 2.51 UK Firmware ( no usa )
google it and you will find it or on this forum
install usb driver from motorola webiste
install rsd lite
put uk firmware in ... C drive/ program files / motorola / rsd lite
install driver
If your phone is stuck on " M " then pull battery out
turn on and quicky press power + vol up ( i think ) before M even appear
wait till it say your boot loader and your battery
plug phone in
start rsd lite
on ... look up your uk firmware that you you recently put in rsd lite folder
then you should see your phone connected on the 1 slot
then hit start or something and wait it out .
Thanks guys! But I've been messing around with this thing for so long, I drained the battery. I had to run it up to the local phone store to get it charged. I'll pick it up in a couple of hours and give your advice a try.
Hey guys! it worked! I'm up and running. Now, anyone has a link to bypass this Welcome to Motoblur screen. Is there a Custom Froyo or Gingerbread Rom out there without Motoblur?
Alright... I'm up and running, but no camera!!! Heck, it was a learning experience. I guess I'll go back to 2.1 now. LOL
So the Chinese ROM was rooted. I installed Clockworkmod and restored from the backup i had made of the original 2.1 OS. I'm back to a rebooting phone not making it past the "M" I went back to RSDlite and realized the boot file said 2.2 only. Can anyone assist me finding the right one to go back to original. I haven't been able to find a thread about reverting back to original.
The more I read, the smarter I get seems like the only thing I'm missing here is the SBF file for my original T-Mobile OS. I'm looking at the motorola website, but I can't find it. Can anyone point me to it? Thanks all! Oh yeah, this is the first android phone i mess with so my apologies.
There is no us sbf file. You have to flash a uk version and restore 3g with the posted fix. You can find the links to available sbf files on this forum. They are not available thru moto's site.
Sent from my ME525 using Tapatalk
Just to make sure I got it right. After using clockworkmod to restore to my factory backup, I need to use the UK sbf to be able to boot to it. Correct?
I found the sbf for Central Europe with no Motoblur. Does anyone know of any issues with it?
well the only way to fix this if you previously backed up your rom/files with recovery ( good thing i did this ). If not then you have to live with what you got.
I backed up my original firmware using clockworkmod. I flashed to the Chinese 2.2 but my camera didn't work. Since the camera is important to me, the Chinese Froyo was a deal breaker. I installed clockworkmod again and "recovered" from my original backup but now my defy won't boot. Did I miss a step?
Your data from the backup may cause issues when rolling backwards. Install an eclair sbf, then restore. That worked for me.
On another note there is a fix for the camera. Check the forums.
Sent from my ME525 using Tapatalk
Bricked Defy and not recognized by my USB
I also bricked my phone when going back to stock from cm7. My phone is able to go into boot loader. But it is not recognized by my desktop PC/RSDlite. I tried in linux with SBF_Flash. I tried with my laptop also. no luck . anyone please help me!
arulshoponline said:
I also bricked my phone when going back to stock from cm7. My phone is able to go into boot loader. But it is not recognized by my desktop PC/RSDlite. I tried in linux with SBF_Flash. I tried with my laptop also. no luck . anyone please help me!
Click to expand...
Click to collapse
Just try and install the Motorola Drivers in your desktop and open RSDLite and press 'show devices' button. It will surely show the details of your phone.
Then point RSDLite to the stock SBF and flash away.
kvigneshkrish said:
Just try and install the Motorola Drivers in your desktop and open RSDLite and press 'show devices' button. It will surely show the details of your phone.
Then point RSDLite to the stock SBF and flash away.
Click to expand...
Click to collapse
Thanks! Vignesh. But i have drivers installed. Tried uninstalling and reinstalling drivers. But did not help
Edit:
I missed to mention. My defy did not connect to desktop even before bricking.
arulshoponline said:
Thanks! Vignesh. But i have drivers installed. Tried uninstalling and reinstalling drivers. But did not help
Edit:
I missed to mention. My defy did not connect to desktop even before bricking.
Click to expand...
Click to collapse
If you hear the USB plugged in sound in your Pc, it's a messed up driver installation. If you don't hear the sound, it can be a bad cable, or a faulty microusb port (assuming that your pc usb works fine). Try once in a different pc and with a different microusb cable.
nsm1234 said:
If you hear the USB plugged in sound in your Pc, it's a messed up driver installation. If you don't hear the sound, it can be a bad cable, or a faulty microusb port (assuming that your pc usb works fine). Try once in a different pc and with a different microusb cable.
Click to expand...
Click to collapse
I do not hear any sound from desktop/laptop.
I think I stuck in boot loop. When I try to power on the phone, it just shows CM7 boot logo for few seconds then restarts again shows the boot logo... this happens continually. When I try to enter into recovery, it does not go to CWM recovery instead it goes to stock recovery. I am still able to enter into boot loader. In boot loader, it says battery OK connect USB to program. When I connect USB, it is recognized by phone and says transfer mode: USB. But my PC does not shows up the phone.
I tried re-installing drivers and RSDlite many times but no luck. But I have nandroid backup of CM7. Is there any possibilities to enter into CWM recovery?
Any help is appreciated.
Edit:
I tried even different USB cables and PCs also.
Alrighty then. I have Zte Blade 3. Lovely phone. I rooted it and I really loved it. Everything worked perfectly. I even connected my phone to my ADSL 2+ modem. I loved it! And then and ugly motherfu***r like me had to do this. BRICK IT. I tried installing a new mod unsuccesfully. Installation process gave me error so I clicked reboot now in recovery mode.So it turned off. And then it showed me android logo as it always shows when its booting up. And I thought Imma give a rest to the mods I will enjoy my phone as it is. But the problem appeared. My phone DID NOT PASS the green android logo.Just sitting there.Can't enter recovery mode via key combination(never could I actually used RootBlade3 program to enter recovery mode). But now I cant boot,enter recovery mode or get recognized by my pc. Cuz the phone wont boot up. Before you asked I did update all my drivers. This phone cost me some good money and since Im 15 Im dead if I dont get this right. Imma make you a rich man If you fix it(lying cuz Im broke) Thanks in advance.:laugh:
I Love The Register Video said:
Alrighty then. I have Zte Blade 3. Lovely phone. I rooted it and I really loved it. Everything worked perfectly. I even connected my phone to my ADSL 2+ modem. I loved it! And then and ugly motherfu***r like me had to do this. BRICK IT. I tried installing a new mod unsuccesfully. Installation process gave me error so I clicked reboot now in recovery mode.So it turned off. And then it showed me android logo as it always shows when its booting up. And I thought Imma give a rest to the mods I will enjoy my phone as it is. But the problem appeared. My phone DID NOT PASS the green android logo.Just sitting there.Can't enter recovery mode via key combination(never could I actually used RootBlade3 program to enter recovery mode). But now I cant boot,enter recovery mode or get recognized by my pc. Cuz the phone wont boot up. Before you asked I did update all my drivers. This phone cost me some good money and since Im 15 Im dead if I dont get this right. Imma make you a rich man If you fix it(lying cuz Im broke) Thanks in advance.:laugh:
Click to expand...
Click to collapse
Download the official update.zip from official ZTE website for your phone!
It contains a recovery.img .
First copy the whole update.zip to your sdcard.
Then fastboot the stock recovery.img ..
Now it wont boot full , you are only able to get in recovery.
So go in recovery , apply update ; choose the update.zip and let the update.zip install.
Your phone should work fully normally now.
Thanks need more help
kevinrus123 said:
Download the official update.zip from official ZTE website for your phone!
It contains a recovery.img .
First copy the whole update.zip to your sdcard.
Then fastboot the stock recovery.img ..
Now it wont boot full , you are only able to get in recovery.
So go in recovery , apply update ; choose the update.zip and let the update.zip install.
Your phone should work fully normally now.
Click to expand...
Click to collapse
Im so happy you replied. Now here comes the deal-all the flashing and struff not good at it. If you could explain step by step I would be grateful. Slap a link of drivers and I thought you cant flash when your phone cant be recognized. Cuz when I enter fastboot it says waiting for device and then it says device not found. I tried almost every solution via modaco-tpt and many others...please help me bro
I Love The Register Video said:
Im so happy you replied. Now here comes the deal-all the flashing and struff not good at it. If you could explain step by step I would be grateful. Slap a link of drivers and I thought you cant flash when your phone cant be recognized. Cuz when I enter fastboot it says waiting for device and then it says device not found. I tried almost every solution via modaco-tpt and many others...please help me bro
Click to expand...
Click to collapse
You said you tried the recovery.img to fastboot , so : do you got the fastboot drivers for Blade III installed?
When you ain't installed them , it is normal that devices won't be found.
Click here to get to drivers
I believe I've hard-bricked my Nexus 7. I'm not stranger to flashing, etc., but something must have messed up this time. I was previously running stock Android 4.3 with TWRP recovery and my tablet took the OTA update. The update of course failed because of the root and recovery, but instead of going back to Android 4.3, it wouldn't boot past the fastboot screen (bootloader screen? with the green android).
So, planning to return to all stock, I downloaded the official Android 4.4 .tgz file and extracted it to my platform-tools folder for the Android SDK. I ran "flash-all.bat" as explained in this tutorial: http://www.androidpolice.com/2013/0...stock-using-a-full-factory-image-and-root-it/
Something must have went wrong because the screen went black and will not turn back on. When plugged into the PC, it is recognized as only an "APK" device. Sources online indicate that this is hard-bricked, as there is no "nvflash" openly available for the Nexus 7 to restore the bootloader.
1. What happened and how can others prevent this?
I think I should have flashed each partition individually (i.e. boot, recovery, system, etc) instead of "flash-all." Any idea what happened to the bootloader? Any other ideas on how to restore the bootloader?
2. What to do now?
EDIT: Apparently my device is out of warranty. Crap.
EDIT 2: Apparently I accidentally downloaded Android 4.4 (KRT16S) for the Nexus 7 Mobile (nakasig) and not for the Nexus 7 Wifi (nakasi)... Opps!
There are several Nexus 7s on ebay with cracked screens, etc. If I purchased one of these, what would I need to pull from them to fix this?
Thanks for your assistance in advance! This forum is great.
What about pressing and holding power button for more than 30 seconds?
Once it could boot and you could enter into fastboot mode, then I think you would get a chance to save it.
BTW, I did mess up when I was flashing KRT16O factory images, which was the earlier release for Kitkat.
At that time, I just used the flash-all.bat like you did. And in the second round, I still failed when following and typing the listed commands in flash-all.sh.
So I chose to use nexus toolkit after that.
Thanks for your reply.
I keep trying that, along with the various other combinations of power button and volume down and volume up. Nothing. The most that happens is when it's plugged into the PC, the PC makes the sound of something being connected and disconnected. I just tried unplugging the battery too. I'll let it charge over night and try again tomorrow.
When yours failed the first 2 times, you were still able to get into fastboot? You're right, if I can just get there then I'll be alright.
Thanks again.
I was just backtracking my steps and realized the mistake I made. I accidentally downloaded Android 4.4 (KRT16S) for the Nexus 7 Mobile (nakasig) and not for the Nexus 7 Wifi (nakasi). Major opps!!
1. Any way to recover from this brick? My gf also has a Nexus 7 (2012). Anything I can copy from that to restore mine? (if she even lets me touch it after she hears about this!)
2. There are several Nexus 7s on ebay with cracked screens, etc. If I purchased one of these, what would I need to pull from them to fix this?
No problem,bro. I think you can always get responses here at XDA though I didn't help you out.
And yes, I could still enter into Fastboot at that time.
However, I was not able to reboot my N7 using the aforementioned methods since it got stuck in Google logo.
Hence I removed the batterysilly, booted it and used the key combination to get into Fastboot. And you know the rest, used the toolkit....
My friend if u can enter fastboot then u can definately revive ur device, it is soft brick not hard brick (soft brick = software is dead) (hard brick = hardware is dead)
I do this all the time just for fun
Let me give u step by step instructions.
1. Download this tool kit
http://forum.xda-developers.com/showthread.php?t=1766475
2. Download the proper stock image for ur device (make sure u pay attention when u download the file, u definately dont want to download wrong file and then redownload the file again)
https://developers.google.com/android/nexus/images
3. Install toolkit, Select your device and don't worry about android version because u have non rit now and install the proper drivers for fastboot to work.
4. From toolkit main screen, select (softbrick/bootloop) and accept the warning.
5. Now select (Other/Browuse option) and then select (I Downlaoded a factory image myself) option then it will ask for the image that u downloaded from google website (Step 2).
6. If u have done exactly as i said then ur phone should be detected in Fastboot mode and the flashing would start and after some time phone should show loading screen (os is booting) wait for it to boot and enjoy ur stock android.
7. Enjoy.
FYI u should have enough battery (around 50%) and to enter fastboot mode u just have to boot to bootloader (restart/ power on the device while pressing volume down button) u should see the screen with bunch of numbers e.g bootloader version etc.
zamboniman87 said:
I was just backtracking my steps and realized the mistake I made. I accidentally downloaded Android 4.4 (KRT16S) for the Nexus 7 Mobile (nakasig) and not for the Nexus 7 Wifi (nakasi). Major opps!!
1. Any way to recover from this brick? My gf also has a Nexus 7 (2012). Anything I can copy from that to restore mine? (if she even lets me touch it after she hears about this!)
2. There are several Nexus 7s on ebay with cracked screens, etc. If I purchased one of these, what would I need to pull from them to fix this?
Click to expand...
Click to collapse
Hmm... there is a thread on making it unbrickable, but you have to do that ahead of time. If you were to buy a broken tablet, you'd probably need to replace the motherboard.
Sent from my Nexus 4 using XDA Premium 4 mobile app
xateeq said:
My friend if u can enter fastboot then u can definately revive ur device, it is soft brick not hard brick (soft brick = software is dead) (hard brick = hardware is dead)
Click to expand...
Click to collapse
Thanks for your help, but unfortunately I can't even enter fastboot. I can only enter APX mode, which apparently is pre-fastboot.
korockinout13 said:
Hmm... there is a thread on making it unbrickable, but you have to do that ahead of time. If you were to buy a broken tablet, you'd probably need to replace the motherboard.
Click to expand...
Click to collapse
Thanks. I saw that thread, but of course it was too late at that point. Perhaps I'll look into buying one with a cracked screen, or sell mine for parts on ebay.
Plz dont tell me u flashed wrong bootloader, plz plz plz.
zamboniman87 said:
I was just backtracking my steps and realized the mistake I made. I accidentally downloaded Android 4.4 (KRT16S) for the Nexus 7 Mobile (nakasig) and not for the Nexus 7 Wifi (nakasi). Major opps!!
Click to expand...
Click to collapse
Dammit, I just made this exact same mistake. Came here to XDA looking for help, and it seems that this may be one of those things that you simply can't recover from... sad day!
---------- Post added at 11:40 AM ---------- Previous post was at 11:09 AM ----------
SteveRiley said:
Dammit, I just made this exact same mistake. Came here to XDA looking for help, and it seems that this may be one of those things that you simply can't recover from... sad day!
Click to expand...
Click to collapse
Well, now isn't this weird... I unplugged the USB cable from my PC and then plugged it into the wall charger. After waiting a while, I was able to boot the Nexus into the "wrong" bootloader. I immediately flashed the correct one, and now am running the latest factory image.
@zamboniman87 -- I did find a thread on Android Central describing a situation in which someone erased their bootloader. The thread contains a tool that a couple folks claimed to help fix the problem. You might give that a try.
Lucky you! This gives me hope though. I'll check it out. Thanks!
xateeq said:
Plz dont tell me u flashed wrong bootloader, plz plz plz.
Click to expand...
Click to collapse
yep.... I feel dumb. haha.
xateeq said:
My friend if u can enter fastboot then u can definately revive ur device, it is soft brick not hard brick (soft brick = software is dead) (hard brick = hardware is dead)
I do this all the time just for fun
Let me give u step by step instructions.
1. Download this tool kit
http://forum.xda-developers.com/showthread.php?t=1766475
2. Download the proper stock image for ur device (make sure u pay attention when u download the file, u definately dont want to download wrong file and then redownload the file again)
https://developers.google.com/android/nexus/images
3. Install toolkit, Select your device and don't worry about android version because u have non rit now and install the proper drivers for fastboot to work.
4. From toolkit main screen, select (softbrick/bootloop) and accept the warning.
5. Now select (Other/Browuse option) and then select (I Downlaoded a factory image myself) option then it will ask for the image that u downloaded from google website (Step 2).
6. If u have done exactly as i said then ur phone should be detected in Fastboot mode and the flashing would start and after some time phone should show loading screen (os is booting) wait for it to boot and enjoy ur stock android.
7. Enjoy.
FYI u should have enough battery (around 50%) and to enter fastboot mode u just have to boot to bootloader (restart/ power on the device while pressing volume down button) u should see the screen with bunch of numbers e.g bootloader version etc.
Click to expand...
Click to collapse
I soft bricked my nexus 7 (2012), I was in Team Win Recovery and I selected Dalvik Cache, System, Cache, Data, Internal Storage and formated/deleted it , now I don't have system or recovery
img > https://www.dropbox.com/s/a7ojrr16lt8n27s/nexus bricked (3).JPG?dl=0
all I can load is fastboot mode
img> https://www.dropbox.com/s/jzmr7811w02r525/nexus bricked (2).JPG?dl=0
I will try to do all this steps that "xateeq" wroted and let you now how it went thanks!
psykg said:
I soft bricked my nexus 7 (2012), I was in Team Win Recovery and I selected Dalvik Cache, System, Cache, Data, Internal Storage and formated/deleted it , now I don't have system or recovery
img > https://www.dropbox.com/s/a7ojrr16lt8n27s/nexus bricked (3).JPG?dl=0
all I can load is fastboot mode
img> https://www.dropbox.com/s/jzmr7811w02r525/nexus bricked (2).JPG?dl=0
I will try to do all this steps that "xateeq" wroted and let you now how it went thanks!
Click to expand...
Click to collapse
hey it worked thanks!
at first there were problems with fastboot and drivers somehow usb 2.0 was a bit problematic but usb 1.0 was able to see device
after downloading many drivers (some from nexus tollkit some from web) , and after few restarts of device and bootloader, pc was able to recognize device and than I had to go 2 times with nexus tololkit >softbrick/bootloop
1st time failed
2nd time worked!
thank all!
Alright, so I'm stuck in boot loop, the only recovery I can boot into is stock, which doesn't help obviously. I can't get into download mode, and my computer doesn't detect it. Just tell me the bad news.
Have you removed the LG drivers completely and reinstalled them? How did you get into the bootloop in the first place?
Sent from my LG-D800 using XDA Premium 4 mobile app
whynottry said:
Alright, so I'm stuck in boot loop, the only recovery I can boot into is stock, which doesn't help obviously. I can't get into download mode, and my computer doesn't detect it. Just tell me the bad news.
Click to expand...
Click to collapse
Let me see.. If by download mode you mean the blue dots(circles) then - no, you're not in download mode. But if you can enter teh real download mode (it should go past the circles) then you can flash it ( you should be able to flash it).
More info please.
bender_007 said:
Let me see.. If by download mode you mean the blue dots(circles) then - no, you're not in download mode. But if you can enter teh real download mode (it should go past the circles) then you can flash it ( you should be able to flash it).
More info please.
Click to expand...
Click to collapse
There's a lot of info in his previous posts. We went through hell and back trying to fix it. Hopefully you can give some better guidance.
Art Vanderlay said:
There's a lot of info in his previous posts. We went through hell and back trying to fix it. Hopefully you can give some better guidance.
Click to expand...
Click to collapse
Damn. I've read "I CAN get into download mode and ...." :/
will look into it to help out
one question : how did you brick it ?
Let me copy paste my previous three posts.
"When I originally tried to install TWRP, I was rooted in a stock rom, or whatever you call it when you're rooted and haven't installed a rom yet. When I tried originally, I went through CWM and installed it through that, but whenever I rebooted into recovery, I got the android with the caution sign in its chest. I kept trying to install it, and eventually I believe I used the flashify app to install it(the version I believe was 2.6.3.3) and I tried to boot again and it went into a boot loop, and began making a bunch of drives. I used this http://forum.xda-developers.com/show....php?t=2582142to get me into TWRP, and it worked. Problem is, I have no roms, no backups, no download mode, and my computer only recognizes my phone as 'g2'. I tried to install adb drivers manually so that the computer would recognize it as an adb device, but it gave me error:closed, and that's where we are right now. Quite a hole I have dug myself into, huh?"
"Ok, so I went back into linux -- I have dual boot for windows 7 and ubuntu -- and for some reason adb worked there, so I was able to adb sideload a cwm .img. But of course, I got excited because I thought it would just fix it but now I'm stuck in fastboot mode, and still can't get into download mode."
"I tried it, and now it is stuck in a bootloop and isn't detected by my computer. Only thing I can boot into is stock recovery. Looks like this is the end of my G2.."
I truly do think there's nothing that can be done, just from a logical standpoint. It isn't detected by anything on the computer and can only boot stock recovery which doesn't help at all. I do appreciate the help, though.
bender_007 said:
Damn. I've read "I CAN get into download mode and ...." :/
will look into it to help out
one question : how did you brick it ?
Click to expand...
Click to collapse
Ugh..so no fastboot either :/
fastboot was good.
Hello everyone,
So ive been lurking on these forums for some time now looking for a solution for the mess I just created, but its been so long now that I want to ask if anyone can help me out now.
The situation is I bought a LG G2 AT&T, and then proceeded to root, recovery and everything was flawless, but I tried to install another ROM and this is went everything went to hell (Im from Mexico). It went all black and with the "Fastboot mode activated" and stuff so I went an put it on download mode and tried by all possible ways, the LG Flash Tool and the LG Flash tool 2014, both ways do not seem to bring back my phone to life.
Whenever I try to install it like this, I get this error with the D800AT FW. I get this error.
And whenever I try to install with D802 FW. I get this one as well.
When I try with the Lg Flash Tool 2014 method. I cant get it to 100%, I always get stuck on 99% And then it crashes.
I am really running out of options here, the phone is recognized by the PC, but I cant get to install a normal working stock ROM.
Any pointers, or help, would be greatly appreciated.
Thank you.
EDIT:
Apparently, I cant post images just yet to show you the exact error. But for the first 2 errors, I get something like this.
"DOWNLOAD FAIL! Check phone or DLL" both for D800 and D802
If you have twrp as your recovery you can adb sideload a rom onto your device from your computer. Google how to sideload adb with trwp installed and follow the instructions. If your phone is recognized it should be fine.
Sent from my LG-VS980 using XDA Free mobile app
TexasRules777 said:
If you have twrp as your recovery you can adb sideload a rom onto your device from your computer. Google how to sideload adb with trwp installed and follow the instructions. If your phone is recognized it should be fine.
Sent from my LG-VS980 using XDA Free mobile app
Click to expand...
Click to collapse
First of all, thank you for your response.
Now, it is still recognized, but I tried to flash it with some DLL a guy provided on this one thread (http://forum.xda-developers.com/showthread.php?t=2663369) and it didnt complete, it just froze on 94% and now I cant get to Download mode.
I saw about the adb sideload, but I cant seem to access to Recovery now. Tried to, but all I get is some kind of bootloop just showing the LG and android with the open belly and then back to LG.
Yoso14 said:
First of all, thank you for your response.
Now, it is still recognized, but I tried to flash it with some DLL a guy provided on this one thread (http://forum.xda-developers.com/showthread.php?t=2663369) and it didnt complete, it just froze on 94% and now I cant get to Download mode.
I saw about the adb sideload, but I cant seem to access to Recovery now. Tried to, but all I get is some kind of bootloop just showing the LG and android with the open belly and then back to LG.
Click to expand...
Click to collapse
So the three finger method only gets you the android with the belly up? Is your phone still recognized? I'm on Verizon but i think with other phones it's the same process. If you have no recovery you need to tot back to stock. I've only done it once but it did work. This is what i used to fix my problem when adb didn't work. Lots to read but it does work and people will answer if you have a problem http://forum.xda-developers.com/showthread.php?t=2797190.. Good luck man.
Sent from my LG-VS980 using XDA Free mobile app
TexasRules777 said:
So the three finger method only gets you the android with the belly up? Is your phone still recognized? I'm on Verizon but i think with other phones it's the same process. If you have no recovery you need to tot back to stock. I've only done it once but it did work.
Sent from my LG-VS980 using XDA Free mobile app
Click to expand...
Click to collapse
If I try to enter Recovery I enter the stock one and just asks for a Factory Reset... I can not enter download mode now, I get fastboot mode only when I try download mode. Phone is recognized by computer when I connect it, but when I try to enter Download, it does show the device on device manager, but it sounds weird and I cant do anything.
Im really starting to lose it.
Yoso14 said:
If I try to enter Recovery I enter the stock one and just asks for a Factory Reset... I can not enter download mode now, I get fastboot mode only when I try download mode. Phone is recognized by computer when I connect it, but when I try to enter Download, it does show the device on device manager, but it sounds weird and I cant do anything.
Im really starting to lose it.
Click to expand...
Click to collapse
If you see hit enter for factory reset (white screen) hit yes. It will enter the recovery. Twrp in this case. If the above program doesn't work but you can get into twrp download a full stock att rom... Download koush's universal drivers (google it) and watch this video at 4:20 he explains in english perfectly how to side load a rom. ADB Sideload - Flashing Zips with TWRP & PC (Expl…: http://youtu.be/YP1LVOKgwQM.. Fingers crossed man.
Sent from my LG-VS980 using XDA Free mobile app