i have a new nexus 7 2013 and i messed up big time im no good with all this adb stuff i unlocked it rooted. wouldnt boot. went in team win recovery project and somehow ended up deleting the os i cant get the computer to recognize the device to install the os if thats even possible or if i even could find out how. the computer just calls it flo and says i need to update the driver which it is or i culdnt of rooted(failed)... thanks any help is much appreciated. some on recommended to mount but cant get it to connect to computer.
UTubeMeBeach said:
i have a new nexus 7 2013 and i messed up big time im no good with all this adb stuff i unlocked it rooted. wouldnt boot. went in team win recovery project and somehow ended up deleting the os i cant get the computer to recognize the device to install the os if thats even possible or if i even could find out how. the computer just calls it flo and says i need to update the driver which it is or i culdnt of rooted(failed)... thanks any help is much appreciated. some on recommended to mount but cant get it to connect to computer.
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?t=2381582
http://goo.gl/lF0HEC
This is the driver you need to install to use ADB while in recovery which is different to the one for Fastboot and ADB while booted.
Perhaps this is what you are facing?: http://forum.xda-developers.com/showthread.php?t=2380913 The fact that you lost the OS leads me to believe so. Match the thread to your problem, however. If the information in the thread I linked to doesn't match your issue, then your best bet would be the one-click factory recovery mentioned earlier in the thread. Best of luck, from one novice, shaky rooter to another!
thetechaddict10 said:
Perhaps this is what you are facing?: http://forum.xda-developers.com/showthread.php?t=2380913 The fact that you lost the OS leads me to believe so. Match the thread to your problem, however. If the information in the thread I linked to doesn't match your issue, then your best bet would be the one-click factory recovery mentioned earlier in the thread. Best of luck, from one novice, shaky rooter to another!
Click to expand...
Click to collapse
OMG if this works ill pm you and tell you
thetechaddict10 said:
Perhaps this is what you are facing?: http://forum.xda-developers.com/showthread.php?t=2380913 The fact that you lost the OS leads me to believe so. Match the thread to your problem, however. If the information in the thread I linked to doesn't match your issue, then your best bet would be the one-click factory recovery mentioned earlier in the thread. Best of luck, from one novice, shaky rooter to another!
Click to expand...
Click to collapse
omg gimme your paypal email?? you saved my ass dude that worked perfect id be glad to pay you a couple dollars and thanks for everyone else who helped
UTubeMeBeach said:
omg gimme your paypal email?? you saved my ass dude that worked perfect id be glad to pay you a couple dollars and thanks for everyone else who helped
Click to expand...
Click to collapse
If you insist, there should be a "Donate to Me" box next to my information on the left.
I had the same problem. Got stuck with no OS installed, USB debugging disabled, and no ROM I could flash. I was scared ****less but I ended up fixing it with a restore program.
Glad you got it fixed.
I learned how to unlock, root, flash custom kernels with my old nexus 7 before I attempted on my new nexus 7. Didn't want to make an expensive mistake. I looked at things here last year when I got my first n7, got confused and didn't attempt it. Now, I definitely won't go back to just stock. Hope you get it all sorted out! It was definitely scary for me the first time.
Sent from my Nexus 7 using Tapatalk 4
I don't think I've ever heard of a case where someone permanently soft-bricked their device.
This irrational fear of "bricking" your device if you do something wrong needs to stop.
If your device gets soft-bricked, just flash the stock images - fixes it every time.
Geodude074 said:
I don't think I've ever heard of a case where someone permanently soft-bricked their device.
This irrational fear of "bricking" your device if you do something wrong needs to stop.
If your device gets soft-bricked, just flash the stock images - fixes it every time.
Click to expand...
Click to collapse
It's mainly the word "brick" that gets on my nerves.
Most of these are really just bootloops or boot hangs. My last one was the latter (and a little unsettling, I'll admit). Turns out that trying to flash a root zip before you've signed into the tablet at least somewhere to create the sdcard directories just leads to a headache for me.
Hi guys! this is my first post, or thread, whatever you wanna call it.
So here i am facing problems with my 2013 nexus 7 device, im currently on JB 4.3, the update for 4.4.2 is downloaded and verified, but when i try to install it the countdown of 10 seconds starts, when it reach to "rebooting" it stucks in there and nothing, i waited like 10 minutes once,( the tablet wont stuck).
Any help of suggerstions? i hope anyone can help me since i dont want to do a manually update for now. :silly:
thanks.
It isn't seldom thing that OTA updates fail, or even soft-brick the device for they have not been completely flashed. Updsting manually is much safer option IMHO.
.....of course, it is only then safe, if the fastboot commands get executed flawlessly well... read: if stupid Windows has installed the USB driver properly. Read around how guys fall into troubles if it isn't the case.
tetakpatalked from P5110
I recently picked up a D851 (TMobile). I rooted it, but did not replace the ROM or install a custom bootloader.
Last weekend, the phone started randomly rebooting. Watching logcat via adb showed me several random apps throwing sig11s, after which the phone would give up and reboot. Cycle repeats.
This looks like a hardware issue, as the apps that crash change on each boot cycle.
I arranged with TMobile to swap the device, but they cautioned me that the phone must be returned to an unrooted state.
I've had a hell of a time with it from here. My first try was to install the LG drivers and the PC Suite under a Windows VM, as I do not run Windows at home. Enabling USB passthrough for the phone to the VM let Windows see the phone, but the LG drivers would invariably fail with 'Device cannot start. Code 10.'. Likewise, the PC Suite couldn't find the phone.
Next step was to throw together some spare hw and install Windows 7 on that (a desparate move, to be certain. ). The LG drivers can now recognize the phone, so that's a definite plus. The LG PC Suite, though, claimed that my phone could not be upgraded. Wonderful.
Next step was to try this tutorial: http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html . I was able to get further with this method, but as it begins to flash SYSTEM, it pauses, and then dies with 'We can't communicate with Phone'. End result - I now have a soft bricked phone. On the phone, I see the port - COM41 - appear, and the usb animation starts to spin ... and after a few seconds, stops. It's at this point that Flashtool throws the Can't Connect error.
I next tried following this tutorial: http://forum.xda-developers.com/showthread.php?t=2785089 to flash a KDZ. The newer LG Flash tool used here can't create a connection to my phone for flashing.
I've run into a wall here. Any ideas on where to go next? I need to reset this phone back to a working stock state so that I can send it back.
http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4
BACARDILIMON said:
http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4
Click to expand...
Click to collapse
Also - as silly as it sounds, make certain you're using the USB cable that came with the phone. This has solved problems for a lot of people when trying to revert to stock.
etawful said:
Also - as silly as it sounds, make certain you're using the USB cable that came with the phone. This has solved problems for a lot of people when trying to revert to stock.
Click to expand...
Click to collapse
I wasn't initially, but I did switch to it last night. Still no go.
I suspect it's either the phone itself (see above: re suspected hw failure), or the PC in question (nVidia chipset on this old motherboard, and I've had more than a few problems with adb talking to phones on nVidia motherboards). I'm going to try Bacardilimon's suggestion tonight, on a PC that has *nothing* nVidia-related in it, before I throw in the towel. As it is, the failing phone needs to be back to TMO by the middle of next week, so I'm all but out of time to resolve this.
Drake Maijstral said:
I recently picked up a D851 (TMobile). I rooted it, but did not replace the ROM or install a custom bootloader.
Last weekend, the phone started randomly rebooting. Watching logcat via adb showed me several random apps throwing sig11s, after which the phone would give up and reboot. Cycle repeats.
This looks like a hardware issue, as the apps that crash change on each boot cycle.
I arranged with TMobile to swap the device, but they cautioned me that the phone must be returned to an unrooted state.
I've had a hell of a time with it from here. My first try was to install the LG drivers and the PC Suite under a Windows VM, as I do not run Windows at home. Enabling USB passthrough for the phone to the VM let Windows see the phone, but the LG drivers would invariably fail with 'Device cannot start. Code 10.'. Likewise, the PC Suite couldn't find the phone.
Next step was to throw together some spare hw and install Windows 7 on that (a desparate move, to be certain. ). The LG drivers can now recognize the phone, so that's a definite plus. The LG PC Suite, though, claimed that my phone could not be upgraded. Wonderful.
Next step was to try this tutorial: http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html . I was able to get further with this method, but as it begins to flash SYSTEM, it pauses, and then dies with 'We can't communicate with Phone'. End result - I now have a soft bricked phone. On the phone, I see the port - COM41 - appear, and the usb animation starts to spin ... and after a few seconds, stops. It's at this point that Flashtool throws the Can't Connect error.
I next tried following this tutorial: http://forum.xda-developers.com/showthread.php?t=2785089 to flash a KDZ. The newer LG Flash tool used here can't create a connection to my phone for flashing.
I've run into a wall here. Any ideas on where to go next? I need to reset this phone back to a working stock state so that I can send it back.
Click to expand...
Click to collapse
There is a link in the general thread on how to return to stock including a method using twrp. It's a sticky thread at the top I've never done the twrp method myself but it can more than likely be done without a computer. Twrp can be installed via Playstore if you don't already have it
BACARDILIMON said:
httx://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
Use this and follow video carefully. Has worked many times. Use all his links not what you have downloaded.
NOTE 4
Click to expand...
Click to collapse
Holy hell. That site's links are absolutely infuriating. Anyone who puts each and every download link for software referenced by a howto behind separate timed appearance links that you have to ALSO enter an annoying captcha to enable should be shot out of a cannon - or, at the very least, have their howto ignored by the rest of the world.
Suffice it to say, the quality of that page doesn't give me much confidence that this will work any better than what I've tried already. Since I've already wasted a crapload of time on this project, and more on following those damned links, I'll give it a try tonight, but I'm not going to hold my breath.
Is the author of that page an XDA member? If so, please let me know who he is, so I can berate him personally. Thanks.
Toneman07 said:
There is a link in the general thread on how to return to stock including a method using twrp. It's a sticky thread at the top I've never done the twrp method myself but it can more than likely be done without a computer. Twrp can be installed via Playstore if you don't already have it
Click to expand...
Click to collapse
I'd consider doing that, except as I mentioned, the G3 in question disconnected during a run of Flashtool, rendering it without a working OS to boot to. The phone now boots straight to download mode. The good news is, it's now officially unrooted. The bad news is, it's also officially bricked until I can get an OS flash to work.
Drake Maijstral said:
Holy hell. That site's links are absolutely infuriating. Anyone who puts each and every download link for software referenced by a howto behind separate timed appearance links that you have to ALSO enter an annoying captcha to enable should be shot out of a cannon - or, at the very least, have their howto ignored by the rest of the world.
Suffice it to say, the quality of that page doesn't give me much confidence that this will work any better than what I've tried already. Since I've already wasted a crapload of time on this project, and more on following those damned links, I'll give it a try tonight, but I'm not going to hold my breath.
Is the author of that page an XDA member? If so, please let me know who he is, so I can berate him personally. Thanks.
Click to expand...
Click to collapse
OK I gonna keep it real with you. You can either enter the captcha and fix the issue or throw the phone away. Yes he is a member and for every phone that is out their he has its own page doing this for us. If you can't fix your phone with his method then it not the method but you. I have used this for many bricks. It works and it works great. Sorry if he making you do a little typing but like I said u can use his method or keep trying the other methods. Good luck
NOTE 4
BACARDILIMON said:
OK I gonna keep it real with you. You can either enter the captcha and fix the issue or throw the phone away. Yes he is a member and for every phone that is out their he has its own page doing this for us. If you can't fix your phone with his method then it not the method but you. I have used this for many bricks. It works and it works great. Sorry if he making you do a little typing but like I said u can use his method or keep trying the other methods. Good luck
NOTE 4
Click to expand...
Click to collapse
After going through the painful process of clicking his links, I found that everything I downloaded is the same thing I already had, except for Flashtool - lgg3root's is actually older. Even the TMO firmware for my phone and the dll are both exactly the same, and I checked by running md5sum on them.
But hey, it must be me. There's clearly no other technology-related cause for this issue. I obviously don't know how to follow a howto, right?
Thanks for 'keeping it real'.
Drake Maijstral said:
After going through the painful process of clicking his links, I found that everything I downloaded is the same thing I already had, except for Flashtool - lgg3root's is actually older. Even the TMO firmware for my phone and the dll are both exactly the same, and I checked by running md5sum on them.
But hey, it must be me. There's clearly no other technology-related cause for this issue. I obviously don't know how to follow a howto, right?
Thanks for 'keeping it real'.
Click to expand...
Click to collapse
See we agree.
NOTE 4
BACARDILIMON said:
See we agree.
NOTE 4
Click to expand...
Click to collapse
Not likely.
In any case, it failed again. The video he did gave me the exact same steps I followed elsewhere, and unsurprisingly, it failed with 'We can't communicate with Phone', after beginning the flash process. There is something else wrong here, though I'm not certain if the failing phone is at fault or the PC in question is causing the issue. To be crystal clear, the flash process starts, and then, at a random point during the flash, it completely stops, and Flashtool eventually gives up and throws the aforementioned error.
Any other ideas? If not, I'm going to have to try another PC to rule that out as the culprit. Sigh.
Mine gave the same error as well as couldn't communicate with server but the flash process continued running and the phone rebooted took about 3 minutes u learned not to touch any of the popups on the screen during flash and sorry I missed the part about no OS I thought you were booting to recovery... Driving while reading not the best idea
Toneman07 said:
Mine gave the same error as well as couldn't communicate with server but the flash process continued running and the phone rebooted took about 3 minutes u learned not to touch any of the popups on the screen during flash and sorry I missed the part about no OS I thought you were booting to recovery... Driving while reading not the best idea
Click to expand...
Click to collapse
Nope, the phone is definitely not doing anything - the usb animation on the G3 completely stops before Flashtool throws the error.
And damnit, quit reading while driving. You can do that later.
Moved the hdd Windows is installed on to another PC with a different chipset. After it updated drivers, I tried again. Flash proceeded partway, then died. Reset phone, Flashtool reststarted flash from scratch, flash died at 15%.
15% is interesting. While I've seen the flash die at various points, 15% is the one that was most often repeated. This tells me the failure follows the phone, not the PC - which makes sense, as the phone has a suspected RAM failure.
At this point, it appears that flashing this phone is impossible due to faulty hw. Hopefully TMO (and eventually, LG) will accept the faulty phone back with no OS, because there's no way an OS is being written to this device ever again.
Thank you for answering
yanowman said:
Thank you for answering
Click to expand...
Click to collapse
No problem. There's nothing I hate more than stumbling across a thread where the OP has the same problem I have, only to find it was never updated with the solution.
Good luck man let us know what tmobile says
This is my first post, so please forgive any mistakes I make with a post.
My wife's Galaxy Note 8.0 tablet was being stupid, it would refuse to properly use the internet from our Asus router, would connect but apps would insist there was no connection. Was getting tired of that crap so I decided to install a custom ROM, since samsung can be kind of jackasses abandoning most their devices after one major update, was only running Kitkat for crying out loud. I had done so before, but issues arouse. For one, I had great difficulty finding a proper TWRP for some stupid reason, NO ONE seamed to know where to get a well working version. I found one, but it messed everything up, it seems to work just fine but any ROM I install has massive issues with the Google apps, they crash eternally and continuously so I can do literally nothing, can't even get past first setup. I came across talk that it was old TWRP to blame, that it has issues with newer OS's like the lollipop I was trying to install, and FINALLY managed to find a newer version of TWRP, but freaking Odin keeps hanging on it's install, gets to "Nand write start" then stops doing anything. I have tried different cables as well as different computers, does jack crap so far to help. My backup I made in TWRP doesn't even work, when I restore the result is nothing but a boot loop. I am trying to find a stock os to restore it to (mostly) original condition, but it is absurdly difficult for some stupid reason to find, found one all in one exe that didn't work for a damn. I was hoping there might even be a way to install the newer TWRP from with TWRP itself. Can anyone help me with any part of this?
First things first. Calm down.
Do you have Samsung Smart Switch installed on your pc? If not, do so.
Connect your note 8.0 to your pc, select the 'more' button and then Emergency software recovery and initialization. Let that run is course. It can take a while.
See if that helps.
kge420 said:
First things first. Calm down.
Do you have Samsung Smart Switch installed on your pc? If not, do so.
Connect your note 8.0 to your pc, select the 'more' button and then Emergency software recovery and initialization. Let that run is course. It can take a while.
See if that helps.
Click to expand...
Click to collapse
Sorry, but you are going to have to be a little more specific. I installed Switch, but connecting an off device obviously does nothing, should I install and let it boot into a broken ROM again, where gapps crashes, and connect it then?
If your main isues are with GApps try clearing the cache in the play store app, check the date and time on your device.
I literally just got my Note 8 up and running after suffering these same issues you describe. My thread on this:
http://forum.xda-developers.com/galaxy-note-8-0/help/note-8-0-stuck-screen-t3218608
I'll try my best to help you. I received some good advice and I 'd like to help someone as a show of appreciation.
We'll get this straight!
Thanks, pretty much.
kge420 said:
If your main isues are with GApps try clearing the cache in the play store app, check the date and time on your device.
I literally just got my Note 8 up and running after suffering these same issues you describe. My thread on this:
http://forum.xda-developers.com/galaxy-note-8-0/help/note-8-0-stuck-screen-t3218608
I'll try my best to help you. I received some good advice and I 'd like to help someone as a show of appreciation.
We'll get this straight!
Click to expand...
Click to collapse
None of what you said really made sense, I could not get to ANYTHING AT ALL that was not Odin or TWRP. But that link you had gave me the name for the stock os, I searched that and flashed it and now everything is great. So thanks, sort of. You even mentioned that method not working for you I think in that thread, but it did for me, so yeah.
All good then.
I've done many dumb things to this phone but I've finally found something I have not been able to recover from. Let's start with the list of things you guys will have me try that I've already done.
- FlashAll to the latest as well as the "Return to Stock" thread here on XDA
- Lenovo's Recovery Tool (I thought someone on XDA might be wrong about something and went with the Mfg's software, sorry I doubted you guys.)
I'm using linux so I convert your Flash bat to an sh but I've never had issues doing so before. I've rooted this and three other phones and I'd like to think I know what I'm doing I've spent about two weeks on here and other Android forums but this time I need to actually ask for your help.
Now on to my issue.
I installed Lineage OS using their lovely guide and everything was great until I found out my WiFi isn't working. Well can't have that, return to stock! Oh my WiFi is still dead. Wait now I can't even enable dev options because I cannot get past the initial setup without WiFI. OK full reset wipe and restore. Nope nothing doing.
It shows MAC unavailable in the initial setup. adb shell over via recovery shows no wlan0 then I tried TWRP and also OrangeFox because I saw a similar fix with it. I try ip link show but ip isn't there tried to su but it's not going. I think I have eveything mounted right but I'm more Arch than Android :\
And in 5 seconds someone is going to link a thread on here I couldn't find in the search with a easy 3 step procedure. But just in case that doesn't happen feel free to ask for any logs.
I'm a dumb. Be sure you do the Pre-install instructions as these are what fixed my issues.
Hi, is your phone ATT version? Thanks.