Related
My tf101 cannot enter recovery anymore
when i try to enter recovery ,
there is a " ! " on the robot , then tf101 reboot automatically
then freeze on the ASUS logo page
I cannot boot up the machine in normal mode too !
my tf101 is B70 version, someone help..thanks
! with the Android guy is recovry, stock recovery.
instead of Vol up to get into revovery, wait till you get options to cold boot or wipe device.
try booting that way.
also what were uou doing when it gotvstuck at that screen?
baseballfanz said:
! with the Android guy is recovry, stock recovery.
instead of Vol up to get into revovery, wait till you get options to cold boot or wipe device.
try booting that way.
also what were uou doing when it gotvstuck at that screen?
Click to expand...
Click to collapse
i tried cold boot , but it said cold booting up linux .. but no response
i tried wipe device , but it still freeze on ASUA screen too
yesterday, i try to root and install CWM via Prime V4.5
then the device comes this .....
Thanks ...
Never heard of that root utility before. You may not have used the right rooting utility for your device which can cause a brick situation. Also, are u sure u dont have the tf 101 and not thr tf prime? The vipermod utility found in the tf prime forum will root ics for both the 101 and prime. My suggestion is that u make sure u have the right device and search the right forum for brick recovery, unroot, or return to stock threads. They are usually found in the development sections.
Sent from my SGH-I777 using XDA
viperMod PrimeTime 4.5 will only root the TF101 and shouldn't be used to install CWM. That's why it bricked.
cholywell said:
viperMod PrimeTime 4.5 will only root the TF101 and shouldn't be used to install CWM. That's why it bricked.
Click to expand...
Click to collapse
i had an issue that was caused by lack of sleep last night that i might be able to help this guy out.he never used it to flash CWM.. he rooted it and never flashed from within the CWM app. The stock recovery doesn't have options for choosing files ect..
victor1144 said:
My tf101 cannot enter recovery anymore
when i try to enter recovery ,
there is a " ! " on the robot , then tf101 reboot automatically
then freeze on the ASUS logo page
I cannot boot up the machine in normal mode too !
my tf101 is B70 version, someone help..thanks
Click to expand...
Click to collapse
I might be able to help you... I saw your post around 4am. I had the same problem kinda. Was asleep most the day (got done at 6am).
I rooted with viperMod PrimeTime and it worked !
BUT i forgot to FLASH CWM RECOVERY from inside the app and proceeded to install the new ROM after root was made USING the CWM app. What happened in my case , the CWM app restarted trying to flash the new ROM, WITHOUT CWM being my recovery instead rebooted to STOCK recovery and something glitched up. I had the same thing as you stuck on Eee pad never re-starting. Cold boot wouldn't work or full wipe..In my case something conflicted.
Below is the NVFlash of the 3.2 Build of 8.6.5.13 (Latest Build). You need to re-flash again using APX threw your USB connected to a PC (it self installs) :
http://www.tabletroms.com/forums/tr...stock-3-2-recovery-roms-unbricking-tools.html
the links are in Grey btw and says US version, ect ..read everything but its very straight forward... ill explain what i did toward the end of the post to simplify it since it took awhile to figure it out. Ill add side comments threw the process that explains better than the link.
Attention: These tools are designed to bring your device back to working condition. They are great for getting back to stock if you need to send your device in for repair or you need to downgrade to stock in order to root your device, etc.
Instructions for Windows users:
1. download the file from the original link i gave above. NVFlash of the 3.2 Build of 8.6.5.13 (Latest Build) USWindows
2. unpack zip to desktop.
3. Press Volume up and Power at the same time on your Transformer to enter APX mode, connect to pc (hold for about 7 seconds). Basically, Power off.. THAN, power and Volume up at the same time to enter APX mode. IMPORTANT!! the screen remains BLACK like its frozen ,with no writing or indication something is happening. that's normal and the original poster in the link never mentioned it. That is APX mode..
4. drivers for APX are in there if you need them..inside the windows downloaded file its called NVFLASH towards the bottom
On your PC go Device manager.. if APX is working correctly and the Transformer is in APX mode it will appear as an exclamation on the device manager named APX.. you cant miss it.. it stands out. On my Windows 7 PC it changed and said Asus USB (or something like that)
5. double click Run Download.bat file and let run! everything is prepackaged so no copying files, etc. In the same file you downloaded that you unzipped named Windows its the 4th file that says "download" with a gear looking icons.
Your Transformer (based on what happened with mine) will go threw a self install like its pushing files and flashing it..the black screen looks like its being pushed the files and reflashing without a recovery. Your going back to stock. if you dont see anything on your Transformer screen after running/double clicking the Download.bat file ....Right click on APX in the device manager , properties, Drivers, update Firmware, choose manual install and find the Downloaded.bat file and click it. That should do the trick..I did both and only noticed the Transformer lighting up after manually pushing it threw APX.
6. After the device reboots power it off. Then hold vol- and power until you get the option to erase your data.... Select the option to wipe data.
7. Download the latest update from the Asus website if applicable and follow the manual instructions. This step may not be necessary if your OTA update worked or my nvflash is the latest version. US update on there site is 9.2.1.17.Its the only one...
What i did was go back to stock since i didn't see any interesting ROMS..Point is THAT unbricked my device by flashing it in APX mode when it was connected to the PC.
I did use ViperMod again to Root, but used the Clockwork mod app in my Transformer to FLASH CWM RECOVERY to try a few ROMS out.
After trying a few of them out i choose to revert everything to stock, unrooted and reflashed STOCK recovery.
Hopefully that helps you out.. it did work for me...
Thank you so much it worked great
Lantek23 said:
Thank you so much it worked great
Click to expand...
Click to collapse
Glad i could help
Sorry to dig up slightly old threads, but I have a question for you. I have a TF101 that I was trying to update to ICS. It is currently running 3.2 courtesy of the unbricking tool listed in this thread. I had to unstore it as it was bricked from a bad install. That was many moons ago. It won't show an updaate listed, so I decided to go with the manual route. I downloaded the appropriate update (my device lists WW version) loaded it on an SD card had the install prompt come up and rebooted to install... For a split second it shows the android with the gears like it is installing the update and then shows the android with a triangle and exclamation mark. After that, nothing. I have to reboot to get it off that screen. Upon booting, I get a message saying system update failed (2) unknown error. Any ideas?
If Im not mistaken, the zip file you download (I guess from asus?) contains another zip.
Thats the zip you should place on your SD card, did you do that?
Also try renaming that zip to EP101_SDUPDATE.zip (the one extracted)
I already had the zip extracted, and renaming didn't do anything.
Killa357 said:
I already had the zip extracted, and renaming didn't do anything.
Click to expand...
Click to collapse
Are you rooted? Did you remove any system apps?
Another thing to try is on your micro sd card, make a folder name ASUS and inside that folder another folder call Update, inside the Update folder put the extracted zip file (don't rename). Turn off TF and turn it back on, see if it will detect the update file.
If that fail, you did mentioned you use the unbricking tool, use that NVFlash to flash a compatible ICS ROM
It isn't rooted anymore since I ran the unbricking tool, and no system files were modified. Placing it in Asus>Update folder didn't work. I may end up having to really do things manually...
Killa357 said:
It isn't rooted anymore since I ran the unbricking tool, and no system files were modified. Placing it in Asus>Update folder didn't work. I may end up having to really do things manually...
Click to expand...
Click to collapse
You don't need to be root to use NVFlash.
Just when with a slightly older version of the update and it worked. There may be something wrong with the file Asus has hosted.
Hi
I have a slightly different problem. I have rooted my B60 serial number, it has the ICS from ASUS on it and it boots fine, its rooted and it works. Now the problem is I thought lets try a clockwork mod and play with custom roms.
So I set my win 7 up to adb etc, and pressed power button volume button - and off to recovery I went...
but all I got was a little green android on its back chest open and an exclamtion mark. No adb fastboot devices command.
I seem not to have a recovery nor a way of forcing a custom recovery.
Should I NV flash or just be happy the tab works and leave well alone?
Any other answers since a lack of recovery may come back to haunt me sooner or later.
I also tried the power button vol uyp for 7 secs and nothing happens I can get to the cold boot erase data option on power down, don't want to do that yet since Im not sure what data gets erased and I may have a totally non working tab.
Use RecoveryInstaller to install cwm recovery
Use RecoveryInstaller to install cwm recovery
This is my problem I can't get recovery - nor can I get adb to see the device. It shows as a hard drive/storage device but not in adb.
I have an a500 with a thor 3.2 rom. I recently used CWM to reset to factory to install the Thor ICS v170 rom. I got an error when restarting into recovery to install it so I restarted again. There it hung up on the logo. So I restarted into recovery holding the power and volume down, but here is where it goes nuts. Once into recovery, the tablet vibrates nonstop and a Team Rogue logo comes up in the background and gives me errors for reading system data and cache. It gives me menu items listen but doesnt let me do anything and I have to Hold power to power down. Still even restarting doesnt get past the Acer boot logo. Please help me out!
Staples01 said:
I have an a500 with a thor 3.2 rom. I recently used CWM to reset to factory to install the Thor ICS v170 rom. I got an error when restarting into recovery to install it so I restarted again. There it hung up on the logo. So I restarted into recovery holding the power and volume down, but here is where it goes nuts. Once into recovery, the tablet vibrates nonstop and a Team Rogue logo comes up in the background and gives me errors for reading system data and cache. It gives me menu items listen but doesnt let me do anything and I have to Hold power to power down. Still even restarting doesnt get past the Acer boot logo. Please help me out!
Click to expand...
Click to collapse
That's what happens when you run stuff from Dev's that don't adhere to GPL. Undoubtedly some leftover code from whomever it was taken from and "somebody" didn't bother to clean it out all the way. FYI, Team Rogue did ICS development for the Xoom tablet, and also some early CWM work. Guess we know where "somebody" got some code from
Ok, back to your current issue at hand. For starters, you're probably still on an HC Bootloader and probably running a really old version of CWM recovery. If you are going to run ICS or JB roms, I highly suggest you upgrade your bootloader to the patched ICS Unlocked bootloader. Also, I would update to the latest version of CWM. You can get it at his site.
I believe your next rom may be able to run on an HC bootloader, or so I've heard, but your CWM needs to be updated, and that's what probably threw out the errors.
You can find a guide for the unlocked bootloader installation in the Dev Forum. It's stickied.
Hope this fixes your issue. If not, post back.
MD
Staples01 said:
I have an a500 with a thor 3.2 rom. I recently used CWM to reset to factory to install the Thor ICS v170 rom. I got an error when restarting into recovery to install it so I restarted again. There it hung up on the logo. So I restarted into recovery holding the power and volume down, but here is where it goes nuts. Once into recovery, the tablet vibrates nonstop and a Team Rogue logo comes up in the background and gives me errors for reading system data and cache. It gives me menu items listen but doesnt let me do anything and I have to Hold power to power down. Still even restarting doesnt get past the Acer boot logo. Please help me out!
Click to expand...
Click to collapse
All I can say is WOW!!
linuxsociety said:
All I can say is WOW!!
Click to expand...
Click to collapse
Yeah, its strange but doesn't surprise me.
OP, your partitions are also undoubtedly messed up as well. I suppose you didn't by chance write down your UID number did you? You may be able to get by with installing an ICS full update zip. Maybe.
MD
Soo...nothing. is it just a piece of junk now?
Staples01 said:
Soo...nothing. is it just a piece of junk now?
Click to expand...
Click to collapse
I wouldn't think it is 100% bricked, but I'd definitely ask on tegraowners.com since it is from one of their recovery/roms. Guess you may have already asked Thor about the issue though?
I have my cpuid but when i run the dotnetdetector to update the usb doesnt stay connected long at all.
Staples01 said:
I have my cpuid but when i run the dotnetdetector to update the usb doesnt stay connected long at all.
Click to expand...
Click to collapse
Are you trying to manipulate the A500 from a Windows PC or Linux? Notice you said Dotnetdetector, sounds like windows, but not familiar with it exactly. Maybe you could try using a live linux distribution (such as Ubuntu or Fedora) to try to get fastboot/adb and reflash the recovery partition with a known working recovery for A500. The teamrogue thing still puzzles me and I'm just curious if bits of Team Rogue's code has been pieced in with the A500 recovery you are trying to use, or if you may have got a hold of a recovery that was for a different device ? I'm not trying to say that you are a nub and flashed a recovery for the wrong device, but there is a possibility depending on where you obtained the rom from, that it could have been mis-labeled for your device ( but been for a different one) If it was for a diff device it would make sense why you can't do anything with it.
Let me get it straight how this happened.
1. You had CWM installed for A500 and recovery was working fine
2. You used CWM to try to flash a Thor ROM, in which the installation failed.
3. After reboot you have nothing but the Acer logo
4. When you boot back into recovery, it is no longer CWM, but a Team Rogue logo is displayed, and that is all you see?
That's the way I interpret the issue you are having anyway. Can you please send me a link to the ROM that you tried to install that triggered all of this. That way I can see exactly what the installer script attempted to do (because it very well could have tried to flash a diff recovery to your device and failed on something else)
Hope we can get things straightened up for you. Good luck again bud
My phone might be bricked. After many failed attempts to flash a custom rom (I really believe there is a hardware problem since I am a flashaholic since 2009), I managed to flash stock recovery (using cwm 6) so that I could go back to bootloader and flash original ZTE rom.
Now, I can boot to stock recovery, but not to the bootloader.
When pressing Vol+ with Power, instead of going to FTM mode, it shows a white screen with ZTE logo and then reboots back to recovery.
Unfortunately, /system is corrupt with no working rom.
Any ideas?
jastonas said:
My phone might be bricked. After many failed attempts to flash a custom rom (I really believe there is a hardware problem since I am a flashaholic since 2009), I managed to flash stock recovery (using cwm 6) so that I could go back to bootloader and flash original ZTE rom.
Now, I can boot to stock recovery, but not to the bootloader.
When pressing Vol+ with Power, instead of going to FTM mode, it shows a white screen with ZTE logo and then reboots back to recovery.
Unfortunately, /system is corrupt with no working rom.
Any ideas?
Click to expand...
Click to collapse
Seriously... I FIXED IT.
But seriously... I was "Fighting" to solve this for 24 hours. The moment I make this post, I do some magic and phone works....
I really did some magic here I think
: o
jastonas said:
Seriously... I FIXED IT.
But seriously... I was "Fighting" to solve this for 24 hours. The moment I make this post, I do some magic and phone works....
I really did some magic here I think
Click to expand...
Click to collapse
What did you do ?
Blazed2 said:
What did you do ?
Click to expand...
Click to collapse
It's a while back to remember exactly but I think my Blade had a hardware problem with it's internal storage. It just worked after doing the steps correctly after a while and then it went back to be replaced....!
What problems are you having?
jastonas said:
It's a while back to remember exactly but I think my Blade had a hardware problem with it's internal storage. It just worked after doing the steps correctly after a while and then it went back to be replaced....!
What problems are you having?
Click to expand...
Click to collapse
Same as you, can't launch into FTM mode, just to stock CMW mode and can't install any ROM.
Blazed2 said:
Same as you, can't launch into FTM mode, just to stock CMW mode and can't install any ROM.
Click to expand...
Click to collapse
What happens when you try to install a ROM?
jastonas said:
What happens when you try to install a ROM?
Click to expand...
Click to collapse
Just can't! It starts unpacking and then aborts with normally error 0 or 7.
Edit: Check thread [Q] ZTE Blade 2 - Bricked ? Or something You are subscribed to this thread if you can, I state there everything.
Thanks for your time
My Nexus 10 has been acting up recently...the battery seemed to be draining A LOT quicker then it normally would.....the tablet would just shutdown in the middle of doing something. Fast forward a week or two, now when I turn it on it vibrates for a second, shows the "GOOGLE" logo and starts the boot animation for 4.4, vibrates and repeats the same. I manually formatted and flashed 4.4 (fastboot flash boot ...etc...) and still am getting the same issues...Any suggestions on what to try next?
Flash the newest factory image automatically via fastboot.
Sent from my Galaxy Nexus using XDA Free mobile app
Just did that to no avail....same issue as before...Anything else to try?
It almost seems like it is not charging but I would assume I could still get it to boot up while connected to the charger....correct?
Update....I flashed CWM and sideloaded gapps and a ROM...and tried that...still the result..."GOOGLE" logo comes up and then a vibration...then it goes back to "charging" (the white battery with the lightning bolt through it)
Nobody has anything? Damn...lol
cirenj said:
Nobody has anything? Damn...lol
Click to expand...
Click to collapse
Sounds like it may be a hardware issue, since flashing the factory image didn't even help. I would say trying flashing the factory image using the flash-all method, and wiping data/factory reset right after. Couldn't hurt.
cirenj said:
Nobody has anything? Damn...lol
Click to expand...
Click to collapse
You said you installed cwm -- I assume you mean the recovery rom... If I'm wrong ignore the rest.
I too have had this issue and it was not hardware. To fix this I booted into cwm (the recovery rom I use on my N10) and reinstalled a stock factory boot rom. Just for those that don't know to boot into the recovery rom, power off the tablet, then press and hold the power, volume up AND volume down simultaneously --- finally, use the volume button to scroll to the recovery menu.
uDude
texascwby1836 said:
You said you installed cwm -- I assume you mean the recovery rom... If I'm wrong ignore the rest.
I too have had this issue and it was not hardware. To fix this I booted into cwm (the recovery rom I use on my N10) and reinstalled a stock factory boot rom. Just for those that don't know to boot into the recovery rom, power off the tablet, then press and hold the power, volume up AND volume down simultaneously --- finally, use the volume button to scroll to the recovery menu.
uDude
Click to expand...
Click to collapse
I have tried that as well...I am thinking it is a hardware issue as previously stated....amazing...spend $500 for a piece of hardware only to have it die a little over 12 months later....talk about pissed off....
cirenj said:
I have tried that as well...I am thinking it is a hardware issue as previously stated....amazing...spend $500 for a piece of hardware only to have it die a little over 12 months later....talk about pissed off....
Click to expand...
Click to collapse
No shoot me a PM ..
Lets see if we can get you up and running again ..
If we do we can post what we did back here from all XDA users ..
Thx Josh
I am having the same exact issues. I too force flashed stock 4.4.4 and it still does not boot up. Any ideas on how to remedy this would be greatly appreciated.
Thank you!
Hoping to hear something as well...but doesn't look good...
Can you access adb? To check logcat while it's booting (and possibly find out why it's bootlooping)?
What did you use to format the partitions?
Sent from my Nexus 10 using Tapatalk
I can access adb on my laptop...and I used the "fastboot format" and "fastboot flash"
How would I check the logcat file?
http://forum.xda-developers.com/showthread.php?t=2274119
beekay201 said:
Can you access adb? To check logcat while it's booting (and possibly find out why it's bootlooping)?
What did you use to format the partitions?
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
I am unable to get my Nexus to show up in command prompt when I run "adb devices". Not sure what to do.
Any ideas? I've tried reflashing stock images and still have the same problems..
michaelearth said:
Any ideas? I've tried reflashing stock images and still have the same problems..
Click to expand...
Click to collapse
Can you give more details about your issue? If its still about not connecting PC and tablet see this guide for help
http://forum.xda-developers.com/showthread.php?t=2277112
demkantor said:
Can you give more details about your issue? If its still about not connecting PC and tablet see this guide for help
http://forum.xda-developers.com/showthread.php?t=2277112
Click to expand...
Click to collapse
The problem is that my tablet will reboot constantly and it shows my battery being fully drained even after charging it overnight. I'm able to force flash stock images to my tablet and this has not fixed the issue. So at the moment my nexus 10 is an expensive paperweight.
What happens when booted to bootloader or recovery? Does it act normal or loop?
demkantor said:
What happens when booted to bootloader or recovery? Does it act normal or loop?
Click to expand...
Click to collapse
When I boot into the bootloader it acts normal.
Hi guys, I have a problem with my LG G2 16gb. Today I have upgraded CM 13 with the last nightly. After having flashed Rom and Gapps I rebooted the system. The system runs but with some bugs (dialer crashes, screen doesn't wake up anymore when it goes in standby mode). So I decided to come back to the previous nightly, but I suddenly appreciated that I can't go in recovery mode.
I can go in download mode but both Flashtool and SRKtool don't work. I really don't know how to do.
I admit that I'm not able to resolve 2% problem with the fix.
I read that if I try to flash a firmware 10A then Flashtool should work, but I didn't manage to find a mirror of it.
Someone could help me? I Would be grateful
Same problem here. Flashed from cm-13.0-20160427 to cm-13.0-20160430 and now have the same problems. Using d802 with twrp-3.0.2-0
CM is booting, but has the same bugs as written above - no dialer, once in standby screen doesnt wake up any more.
I tried to reboot in Recovery from booted CM, the Phone is hanging with the "Reboot" on Screen. Same with normal reboot or shutdown. It just hangs. The Combination with the Volume Key Down & Power wont let me in Recovery as usual.
CM13 ist really awesome and nightly to nightly it was getting better, but the nightly today just went that wrong.
Would be nice if there is some solution to get the phone back working.
Thanks a lot for any advice or help!!!
Greetings,
Feldinos
fedu89 said:
Hi guys, I have a problem with my LG G2 16gb. Today I have upgraded CM 13 with the last nightly. After having flashed Rom and Gapps I rebooted the system. The system runs but with some bugs (dialer crashes, screen doesn't wake up anymore when it goes in standby mode). So I decided to come back to the previous nightly, but I suddenly appreciated that I can't go in recovery mode.
I can go in download mode but both Flashtool and SRKtool don't work. I really don't know how to do.
I admit that I'm not able to resolve 2% problem with the fix.
I read that if I try to flash a firmware 10A then Flashtool should work, but I didn't manage to find a mirror of it.
Someone could help me? I Would be grateful
Click to expand...
Click to collapse
if the phone boots into system use flashify to install twrp..
if not maybe using srk tools. will help..
why it doesnt work flashtools?
raptorddd said:
if the phone boots into system use flashify to install twrp..
if not maybe using srk tools. will help..
why it doesnt work flashtools?
Click to expand...
Click to collapse
flashtool stops at 2%, I don't know why.
srktool doesnt know my lg g2..
fedu89 said:
Hi guys, I have a problem with my LG G2 16gb. Today I have upgraded CM 13 with the last nightly. After having flashed Rom and Gapps I rebooted the system. The system runs but with some bugs (dialer crashes, screen doesn't wake up anymore when it goes in standby mode). So I decided to come back to the previous nightly, but I suddenly appreciated that I can't go in recovery mode.
I can go in download mode but both Flashtool and SRKtool don't work. I really don't know how to do.
I admit that I'm not able to resolve 2% problem with the fix.
I read that if I try to flash a firmware 10A then Flashtool should work, but I didn't manage to find a mirror of it.
Someone could help me? I Would be grateful
Click to expand...
Click to collapse
I had some problems with booting into recovery as wel. CM13's latest nightly kept freezing my phone and I wanted to go back to my previous backup, but I couldn't boot into recovery from anywhere. Luckily I remembered that the button combination has changed with the latest bootstack I installed. It'sn now like this:
Force a shutdown by holding the power button. As soon as it goes black, press power + vol down, release as soon as the logo appears and then hold vol down + vol up. Then you should be able to get into recovery.
Thoms92 said:
Force a shutdown by holding the power button. As soon as it goes black, press power + vol down, release as soon as the logo appears and then hold vol down + vol up. Then you should be able to get into recovery.
Click to expand...
Click to collapse
Thanks a lot for that information! Almost forgotten that i had installed an new boostack as i flashed the first CM13 nightly that was released.
I was now able to get in recovery and flash 04-27 nightly. Now my phone works normal like it does before i flashed 04-30.
Greetings,
Feldinos
fedu89 said:
flashtool stops at 2%, I don't know why.
srktool doesnt know my lg g2..
Click to expand...
Click to collapse
i think that d802 stuck at 2% but wait and itll be flashed.. i think ive read that somewhere...
are you using windows 7/ usb por 2.0/
here take a look here
http://forum.xda-developers.com/lg-g2/development-d802/fix-lg-flash-tool-stuck-2-t3031112
Thoms92 said:
I had some problems with booting into recovery as wel. CM13's latest nightly kept freezing my phone and I wanted to go back to my previous backup, but I couldn't boot into recovery from anywhere. Luckily I remembered that the button combination has changed with the latest bootstack I installed. It'sn now like this:
Force a shutdown by holding the power button. As soon as it goes black, press power + vol down, release as soon as the logo appears and then hold vol down + vol up. Then you should be able to get into recovery.
Click to expand...
Click to collapse
Thank you so much for the advice! it had been so useful that I managed to get into recovery!
You saved my money, because I was starting thinking about a phone's forced change
I came back to cloudy because I wouldn't find myself in this situation once another!
raptorddd said:
i think that d802 stuck at 2% but wait and itll be flashed.. i think ive read that somewhere...
are you using windows 7/ usb por 2.0/
here take a look here
http://forum.xda-developers.com/lg-g2/development-d802/fix-lg-flash-tool-stuck-2-t3031112
Click to expand...
Click to collapse
When it reaches 2%, it suddenly appears a message telling me that my g2 is disconnected.
Unfortunately for modding, I installed w10. My pc has gotten better, but almost all the programs for modding don't work anymore. In addition to this, I didn't found drivers working well.
I'm thinking about restore w8.1.
There's a way to fix the problem of 2%, but I am not so prepared to use adb.. I'm aware about my limits
fedu89 said:
Thank you so much for the advice! it had been so useful that I managed to get into recovery!
You saved my money, because I was starting thinking about a phone's forced change
I came back to cloudy because I wouldn't find myself in this situation once another!
Click to expand...
Click to collapse
You're welcome As long as you can remember the different button combinations to get into recovery, you shouldn't be afraid to flash roms. Just never forget to make a nandroid backup before upgrading any rom!
If you start to flash roms, you WILL mess up at least once And this time, it wasn't actually your fault, CM13 messed up.
fedu89 said:
When it reaches 2%, it suddenly appears a message telling me that my g2 is disconnected.
Unfortunately for modding, I installed w10. My pc has gotten better, but almost all the programs for modding don't work anymore. In addition to this, I didn't found drivers working well.
I'm thinking about restore w8.1.
There's a way to fix the problem of 2%, but I am not so prepared to use adb.. I'm aware about my limits
Click to expand...
Click to collapse
if there is read the go back to stock in the general section.. read and if cant find answer then ,ask in the thread..
and be especific everything pc and phone..