[Q] Build.prop edit fail -- Completely dead? - G Pad 8.3 Q&A, Help & Troubleshooting

Yep, I became that idiot that started messing around with stuff he didn't about well enough. It's been a while since I've really messed around with rooting and editing system files, and this is where it got me.
In an attempt to install CyanogenMod on the G Pad 8.3 (this was a while ago), I attempted to switch out the build.prop file with something else, for whatever reason. Now the tablet will only boot up to the LG logo and hang until it dies.
Yesterday, I attempted to see if I could do absolutely anything for it, and I've found a little out but I'm not sure if it's enough to possibly do some tablet necromancy.
I downloaded the LG Flash Tool, but have only used the USBView file that comes with it. With the tablet plugged in, the tablet looks like it turns off and on every five minutes or so. When the screen turns on and shows the LG logo, I hear the device 'disconnect' from the computer. When the screen turns off, i hear the 'connect' sound on the computer. During the time the tablet is "off" I see the device show up as a USB Input Device on USB View, and managed to track it down on Device Manager as a HID-compliant device.
At this point, I'm not sure what the next step would be in the attempt to saving the tablet if I can. Any and all attempts at installing a new driver for the tablet have failed, and I can't seem to boot into anything else but this boot loop of nothing.
Serves me right if I can't get this thing fixed, but it would be rad if someone knew where to go next from here.
Thanks

are you using Windows or Linux? Which Gpad do you have assumed it is the LG LGE and not the Google Play edition? Do you have adb installed? if you have a Google Play Edition I will be more than happy to upload a copy of the build.prop.
If you saved a copy, use adb to push it back onto your device.
Code:
Adb push file_you_want_to push where_you_want_to_push_it
Example:
Code:
Adb push /home/desktop/build.prop /system
note the space between prop and /system.
this might be a problem because /system is a read only file, but there are ways around this you will have to look them up. If you could get into your device for instance you can mount /system as read / write and simply copy and paste your build.prop file over. I am unsure whether you could do this from recovery or not,and I suppose it would only work if you had already allowed your computer to get into your device. I guess without more information as to what you did there isn't a whole lot to say.
for me, sometimes receiving a small amount of information about how to solve a problem will lead to something better or bigger.

He needs to mount system fisrt
U will need root
And he needed to had usb debugging on
Enviado do meu GT-I9300 através de Tapatalk

I was rooted and more than likely had USB debugging on. I still can't seem to update the driver in anyway for adb to recognize it. The LG drivers are all installed through exe files so it's harder to just go to device manager and point it to the right driver. ADB devices shows nothing.
Also, this is the korean version. Not sure how much that changes anything, but I'd love to get either the US or Google Play software on this puppy if it's able to be saved.

if you have twrp recovery you can make a flashable zip with the right build.prop and push it using the sideload command

Related

[Q] Waiting for Device

So, Ive been searching for over 6 hours now and I really cant seem to root my kindle fire. I tried basically everything, and when things went wrong, I just deleted the files and started again. On my last try, I was able to fastboot it (at least I think so). When I ran KFU, ADB was online and Boot: 4002.
When I tried to root it always got stuck trying to find twrd.img. Then I tried option number 4, Installing Clockwork Recovery (because option number 3 was a dead end) and twrd.img was installed. But everytime something seemed to go right, the process wouldnt finish, it would just be <waiting for device>. I thought my problems would be over, so I tried to root it again. Now whenever I turn on the device, KFU is unable to locate my kindle, and it doenst appear on the device managing tab either. Even using the kindleunbrick.bat that worked for me the last times, it just gets stuck at <waiting for device>. ADB is offline and Boot: Unknown for now.
I really need to root my kindle because I dont live in America, so I dont have access to most stuff. I already changed the language when installing the driver, however, everytime I hooked my kindle up, a windows message would pop out saying that there was a problem with the driver, but when I went to device managing tab and tried to uptade the driver to "user\.android" it always came back as updated.
I am really noob at this, but I have read all the guides I found and something always went wrong. I hope someone can help me with this, please.
Thanks
Is your kindle turning on? If I could suggest you should put off anymore attempts to root your device till you know precisely what your doing and why. My biggest guess right now is your drivers are the greatest pitfall. You seriously don't want anything going wrong with them in the process of sending recoveries boot loaders or rooting you will end up with a really fancy paperweight. Privy to to attempting anymore you need to know that your drivers are functioning 100%.The fact that you pushed cwmr to your device after twrp should hurt a thing hopefully one should overwrite the other if all goes well . Since rooting is the primary goal go with that until you have verified root then recovery and bootloader can be done easily later with safer methods. Hold off awhile as long as your device will boot until you have found the knowledge and support to make it happen right. Start here http://forum.xda-developers.com/showthread.php?t=1552547 then go here http://forum.xda-developers.com/showthread.php?t=1638452 plan to use this method to root http://forum.xda-developers.com/showthread.php?t=1568340 ask a lot of questions don't be hasty or you will spend a lot of time trying to fix it instead of enjoying it.
As I said, I read all those guides already. I can use my kindle normally, but when I connect it to my computer, it is unrecognized. I tried every method I found to root, even though I just wanted to watch stuff and download a few games for my spare time(my intention was to watch stuff from premium features, but Im not really sure if root will allow me to do that from a foreign country*, so Im a little hesitant to extend premium).
I guess I wont try anything else for now because my main goal was reading, and this I can still do, but I am puzzled with the fact that I was unable to root it. Ill try to understand a bit more (hopefully with some tips). Thanks
*Geographical restrictions
OK well youve read the guides but in what you say it appears you are doing some of the wrong things why would you unbrick if your not bricked? Your drivers are your only issue as of this point but your methods are pushing you close to bricking your kindle. I would like to see you succeed in rooting your device and avoid bricking it.
---------- Post added at 11:59 PM ---------- Previous post was at 11:36 PM ----------
When your around we can try to get your drivers working
It would be nice to know what os your running on your computer. If you are on windows 7 use system restore to roll your computer back to a date before you started messing with the drivers or anything. Once it completes plug your kindle into your computer check to see if you can access the SD card contents and if it appears as a kindle in your device manager. Important now if all is good unplug your kindle and run the .bat file that comes with kfu. Then plug your kindle in let windows install the driver. Open up kfu find the tools folder shift plus right click select open command window here. Then type adb devices if its followed by a string of numbers this shows your kindle connected via adb . At this point you should obtain some help from some of the pros here at xda at fastboot and adb commands to safely root your kindle. If you decline and still wish to use kfu then only select install permenant root. If at any point in this process it fails and you loose adb connection do not unplug your kindle run the driver file again then recheck device status with kfu I believe its option 0 to see if your back online again. Pay attention to the dialogue that takes place in the kfu window you see verbatim that says failed or permission denied then quit after that. One important thing is you need to allow installation from unknown sources in the kindle settings on the kindle under device or it won't push the required files anyway.Wait to install twrp and fff until later there are easier safer methods. If your kindle hangs for a long time at the kindle fire logo select boot mode normal in kfu before unplugging. If at anytime kfu states waiting for device do not unplug it rather power it completely off then power it back on while connected .
---------- Post added at 01:53 AM ---------- Previous post was at 01:32 AM ----------
Just a side note I have rooted 4 different times with kfu without a single failure or mishap including the ones you are experiencing. I'm inclined to feel that relates mostly to your computer and drivers which makes kfu an unsafe approach for you I'm not responsible If you brick it!!!
I unbricked my device before I even came here, I tried an youtube tutorial and then it got stuck on the kindle fire logo, but after I unbricked it, it was fine. I know that something is going wrong, but Im following step-by-step the guides (at least I think so). As I said, everything was going correctly, ADB was online, Boot:4002, but when I tried to root it would be on an endless search for the file twrp.img, and after I succesfully downloaded it (I guess), my computer is unable to find my Kindle.
I run Windows 7, but it isnt properly activated (my room mate threw out the serial code), I dont know if this would interfeer in any way. When I conect the kindle, it appears to be in USB mode and says that I can transfer files, but my computer wont even find it. Ill try to restore my computer now and then Ill come back.
I know that doing this is my responsibility, but not being able to download apps is pretty annoying, so I have to keep trying.
If you can get adb status online then, why don't you install TWRP manually? Or use the "smirkit"?
Once you get recovery installed, you're set.
Also, be sure to "disconnect" from USB storage mode before trying to use adb commands or they won't work.
I dont even know how to use ADB comands. Is there anyway to make my computer recognize my kindle other then doing a system recovery? I dont know how to do that, and after searching, they say I need the CD (which I dont have).
Shift+right click your KFU "tools" folder and select "Open command window here"
From there, enter:
Code:
adb devices
If the output is something like:
Code:
List of devices connected
123456789ABCDEF
then you can install TWRP
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
If the output is:
Code:
List of devices connected
(null)
then you need to reinstall your drivers
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Thank everyone that helped me, I managed it!
Actually I was doing everything right, but I guess the problem was my computer, because when my girlfriend came over I tried connecting it to her netbook and it recognized my kindle. I just downloaded the kfu, installed drivers, reconected kindle and let it update, ran KFU and selected option 2. All done now
I have no idea why this didnt work before, but at least now I can really enjoy my kindle.
Thanks again!
saybhausd said:
I dont even know how to use ADB comands. Is there anyway to make my computer recognize my kindle other then doing a system recovery? I dont know how to do that, and after searching, they say I need the CD (which I dont have).
Click to expand...
Click to collapse
Not system recovery bud system restore two different things go to accessories system tools system restore choose a date chose to restore to that point. System recovery is way way different. Glad you got it going

[Q] Wondering if the device is unfixable (That is it) (Provided specifics)

I just bought a used Kindle Fire (Model D01400). The guy had android on it but reinstalled the original software before selling it to me apparently. The original software worked when he gave it to me perfectly but i decided to restore the device to factory settings. When I did that it brought up the blue kindle fire startup screen with v 1.4 in the top corner and then loaded TWRP. There was an Install, backup, restore, wipe, mount, settings, advanced and reboot option. It says Team win recovery project (TWRP) V 2.2.2.1 at the top. I proceeded to choose the wipe option and wiped the cache, dalvid cache, factory reset, system and external storage. Then i rebooted it and it gave me that blue kindle fire screen and then nothing. If i press the power button I get one of three boot options. 2 of them bring me to the regular white and orange kindle fire screen that just sits there and does nothing. The other one brings me back to the TWRP screen.
The other pertinent piece of information is that when i try to connect it to the computer, I cannot access the device drive and see the contents. (I watched a video on how to fix the device to get it back to the original device software but I need to access the contents of the device) I followed the instructions provided in one of the beginners threads and installed the google sdk that allowed me to see the kindle on my device manager as an android phone but that it is. I cant do anything with the device in My Computer. It does not even show up in there as kindle.
I have been all over this website and read the beginners guide and short of installing linux to try soupkit and trying all the other fixes:
I just want to ask: Is this device bricked forever and unfixable or if I follow the guides that are on this forum can I get it to work like it did when it first came out of the box. (Just asking yes or no if this is fixable)
I just want to get this Kindle back to its normal state with its normal software. I just want to read books on this thing. Not use android.
Bonus Question: Knowing that I just want to get this back to how it works out of the box, is there a faster process than sifting through the beginner threads? (Just Yes or No) (If there is I will search harder to find it)
I am not asking for someone to hold my hand and do this for me. Just making an enquiry because there is tons of stuff to learn and do to try and fix this and I wonder if I am wasting my time.
(More specifics: I am using 64 bit version of windows vista, and have ubuntu installed as well, I have USB 2.0 ports, I have a factory Kindle USB cable from my older Kindle 3G)
I hope I covered everything.
And yes I realize now that I should have never done that factory reset when i first got it. It was working exactly how I wanted it to when i first got it. I am apparently not a smart man.
The smartest thing you can do is install the MoDaCo ROM. Use adb to push it to your sdcard and install it in recovery.
Sent from my Amazon Kindle Fire using Tapatalk 2
soupmagnet said:
The smartest thing you can do is install the MoDaCo ROM. Use adb to push it to your sdcard and install it in recovery.
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
Any advice on getting around the "connecting it to my pc thing" or is it alright if it shows up as an android phone in my device manager.
soupmagnet said:
The smartest thing you can do is install the MoDaCo ROM. Use adb to push it to your sdcard and install it in recovery.
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
Alright I have been learning about this and trying for hours and hours now. I have device manager reading the kindle fire as an android phone ADB interface but when i try to use KFU it does not show the kindle as being connected and when i even try to do anything, like installing TWRP again or something it does not read the device and says waiting for device. I have done everything in the beginners guide.
I think i am having so many issues because I inherited this device in the middle of its functionality and i never had to do the previous steps. I curse the guy who rooted this damnable device in the first place..
Alright i have made some progress and I got my hopes up way too much because i may not ever get a response to this but I am hoping. I followed thesee instructions because I already have all the prerequisites for this process done:
"Reverting to stock software
Required software:
Amazon Kindle Fire Software Update
Warning: Installing the Amazon Kindle Fire Software Update will not only replace the system software, but also overwrite the bootloader and recovery with the stock versions. Any custom bootloader and recovery like FFF and TWRP will be overwritten in the process.
This section assumes the device is already booted into TWRP recovery.
1) Copy the update bin file to the /sdcard as update.zip
Code:
adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip"
I found this on http://forum.xda-developers.com/showthread.php?t=1638452
have the kfu and the software folder and the update put in that folder. I get the device into fastboot but when i type in
adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip
It returns back "error: device not found"
And that is when I cried for an hour. I have everything installed. TWRP i can now reasonably navigate everything. I have ADP thing in my device thing. Why wont this work!
adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip <------ that there is about the worst thing you could do go ahead wipe out your recovery your bootloader and brick your device. I think Soupmagnet recommended modaco that`s about the best place to start. The reason you cant push it might be drivers read up a little it won`t hurt ya. At any rate flashing stock is a mistake here is a nice big list of goodies to flash on that thing http://forum.xda-developers.com/showthread.php?t=1859851 . If your running Ubuntu? run this script on it and reboot http://forum.xda-developers.com/showthread.php?t=1850038 great little feature there that will help you adb push anything you want to that kindle not to mention return to stock safely which really isn`t needed if you flash modaco.
Ijustwanttoreadonthis said:
Any advice on getting around the "connecting it to my pc thing" or is it alright if it shows up as an android phone in my device manager.
Click to expand...
Click to collapse
In TWRP, you can use the Mount function to mount your sdcard as a USB device and transfer your ROM that way. I would highly suggest you install MoDaCo and try it out before you try to revert your device back to stock. In the meantime, you can educate yourself a little more about the device and how it works before you get yourself into trouble by not reverting properly.
I should have reported that I tried to put modaco on the device with the same process as thhis -> adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip
And it still gave me an error saying it could not find the device. And i have been reading threads and trying stuff for hours now. The only problem is that because my device already has all this stuff set up the guides and threads all presuppose that the person knows what they are doing. If i would have just had a stock kindle and done all the steps to get to this point I would have already had all the practice and hands on training. I am going to try to get modaco onto my SD card trying every possible avenue before I post again. Again, my device manager is reading the kindle as Android phone -> Android ADP Interface and it does not show up in My computer as anything. That is what one of the tutorials said it had to do. I really hope this is correct and I am not trying in vain.
Ijustwanttoreadonthis said:
I should have reported that I tried to put modaco on the device with the same process as thhis -> adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip
And it still gave me an error saying it could not find the device. And i have been reading threads and trying stuff for hours now. The only problem is that because my device already has all this stuff set up the guides and threads all presuppose that the person knows what they are doing. If i would have just had a stock kindle and done all the steps to get to this point I would have already had all the practice and hands on training. I am going to try to get modaco onto my SD card trying every possible avenue before I post again. Again, my device manager is reading the kindle as Android phone -> Android ADP Interface and it does not show up in My computer as anything. That is what one of the tutorials said it had to do. I really hope this is correct and I am not trying in vain.
Click to expand...
Click to collapse
Don't worry about using ADB at the moment. Boot into TWRP using the FireFireFire1.4a boot menu you described before, and select "Mount". Make sure there is an [X] on the last option and press the button at the top that says "Mount USB storage". Then check under "My Computer" in Windows to see if the sdcard was mounted. Then transfer your ROM as you would with a USB flash drive.
soupmagnet said:
Don't worry about using ADB at the moment. Boot into TWRP using the FireFireFire1.4a boot menu you described before, and select "Mount". Make sure there is an [X] on the last option and press the button at the top that says "Mount USB storage". Then check under "My Computer" in Windows to see if the sdcard was mounted. Then transfer your ROM as you would with a USB flash drive.
Click to expand...
Click to collapse
Short answer: Nothing appeared in My Computer
---------------------------
Long Answer: I tried every combination of processes that I found through the various troubleshooting methods.
I have 2 chords: A white Kindle chord I used for my old Kindle 3G and a blackberry USB chord that fits the same. I also tried every function with every chord with both Windows and Ubuntu just in case because I saw that in other threads where people were having issues that they were just not doing the proper process based upon the circumstances. I also tried all of these functions while the plugged in Kindle was reading as:
Other devices -> Kindle (Big K)
&
Android Composite ADB Interface
In my device manager. In all the cases I tried the best case scenario was a "removable disk" appeared in My Computer but it read "please insert a disk into Removable Drive" if i tried clicking on it. I also tried all of these functions with each of my 4 USB ports (all 2.0 ports) (which all work for any other device)
So I tried every port with every chord I have using every combination of processes I found in other threads to do what you advised and it did not show up. It took a while but I wanted to be concise because other people do not give enough background or try everything before coming back to the forum.
(Just for reference I tried the process outlined in "How can I verify the drivers are loading?" section in http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2 among other threads for troubleshooting advice and guides.
-------------
I will learn more about this ADB pushing process thing using CMD because the only glimmer of hope I have had in the past 2 days has been getting my computer to read the device when I used KFU. It worked one time and it was magical. Unless there is anything else I can try or if someone can confirm that this thing is completely broken beyond repair.
It's not broken it's just a little unhappy with you right now you may have a combination of things going on. Your drivers my be mistreating you and either you have an sdcard mounting issue or the drivers are affecting it. How ever it is I would be happy to help you sort through it. The only thing I ask is that you complete your thread afterward with a detailed description of what it took to fix it for the benefit of others in your situation. So pm me when your online and if I can I will assist you through it.
Just to let you know it may have been simulating mount in recovery as well funny thing those setting are useless when you want to get something done
Thepooch said:
It's not broken it's just a little unhappy with you right now you may have a combination of things going on. Your drivers my be mistreating you and either you have an sdcard mounting issue or the drivers are affecting it. How ever it is I would be happy to help you sort through it. The only thing I ask is that you complete your thread afterward with a detailed description of what it took to fix it for the benefit of others in your situation. So pm me when your online and if I can I will assist you through it.
Click to expand...
Click to collapse
There was a fairly simple solution that should be universal for most issues if you require pushing a file to your device.
Here is some background stuff that you should have before attempting to fix the problem I had and starting from scratch.
You will want this installed: http://developer.android.com/sdk/index.html
And the Kindle Fire Utility: http://forum.xda-developers.com/showthread.php?t=1399889
And in my case the Modaco ROM: http://www.modaco.com/topic/350682-14-jun-gr9-631-modaco-custom-rom-for-the-kindle-fire/
Unzip the Kindle Fire Utility into c:\kfu
Install the Android program
Create a folder titled Software in your c:\kfu and put the ZIP file that you downloaded from Modaco in the software folder
Make sure to go through the "How can I verify the drivers are loading?" section in http://forum.xda-developers.com/show...71&postcount=2
Plug your USB chord into the kindle first (while it is off) and then plug the chord into the USB port
It will bring up TWRP
Go into the options and make sure that you push Restore Defaults and ensure that any options with "simulate" in them are unchecked.
Open up cmd.exe and type in "cd c:\kfu\tools"
Go to the mount option in TWRP and mount the USB
type in ADB push and then drag the modaco file from the software folder onto the cmd window and it will show you and then type in \sdcard\
ADB push (the modaco file) \SDCARD\
It should take a few moments to transfer and it will say that it is done
Unmount and then unplug from the computer. Go to wipe and wipe everything other than external memory, then go to install and find the file you pushed onto the kindle in the file folders. Push on the file and it will ask you if you want to flash it, select yes.
After that is complete select reboot and it should automatically reboot and then go to the proper startup screen.
Special credit to Thepooch for providing all this information to me. I believe that should be everything.
Working in the directory that adb is in is important and this
Code:
adb push <exact file path> <exact file name> /sdcard/

[Q] Nexus 7 won't boot, need to recover data...HELP!!!!

Ok, so, this is a two part question.
I've got a 32GB Nexus 7, and I'm having some issues with it. This tablet is completely stock. I haven't rooted it, I haven't unlocked the bootloader, installed a custom ROM or anything. All I've done with it was install OTA updates from Google, download some apps/games, and take some pictures.
About two days after I bought the thing and set it up, I got an error that said "System UIDs inconsistent" or something to that effect. I'd never seen it before, but a Google search revealed that the easiest way to fix it was to do a wipe/factory reset, so I did.
Fast forward to a couple of days ago...I'm from Canada, and while driving down to the States, I was bored, so I took out my shiny new Nexus 7, and turned it on. It was stuck at the 'X' screen, and wouldn't boot. I was frustrated, but because I was still in Canada, I was able to run a search on my phone. Factory reset. Ugh. So I did...once it finished, I used my data plan to download a few essential apps, and it was good to go.
Fast forward to today. I'm going to be returning home later today, but yesterday I decided to try out the GPS functions, because the TomTom GPS I've got isn't the greatest, and I much prefer Google Maps Navigation. A friend with a Nexus 4 was able to use the wifi where we were staying to get directions to various places, and then he'd shut off the wifi, and his N4 would still maintain the GPS signal and navigate him for the whole trip, even with no data, and for a lot of the time, no cell signal at all. I wanted to try the same with my N7, not knowing that many users are experiencing issues with the GPS.
So yesterday I was trying to use the Sygic GPS app, which apparently does offline navigation. And I guess because the N7 location capabilities are iffy right now, it wasn't working. So I, in my infinite wisdom, decided to reboot the tablet, thinking that would fix the GPS. This was after I had taken LOTS and LOTS of photos during the trip.
The tablet reboots, and gets stuck on the 'X' screen again. I was ready to bash my head through the car window at that point.
Long story short, the tablet doesn't boot. I'm a software developer for a living, so I had (keyword.. HAD) USB debugging turned on, but since I had to wipe the thing at the start of the trip, I never re-enabled USB debugging, but I don't recall if you actually have to or not...I'm assuming that it loses that setting when you wipe it.
So USB debugging, I can only assume, is not enabled. I can boot into recovery mode, but all I get is the Android icon with a red exclamation mark, and a message that says "No command". I know that you can press the power and volume up buttons to get the menu in recovery mode.
But what I was hoping to be able to do was use ADB to pull a full backup of the device, to at least salvage all the photos I took. I don't care about the apps, I can always reinstall those. I did not have a chance to set up an auto-sync (either Dropbox or Google+) of the photos, unfortunately.
I downloaded the Google USB drivers, and the Android Platform Tools (the wifi at this hotel sucks, so I didn't get the full SDK), and I'm using my brother's laptop, which is running Windows 8. I can get the tablet into recovery mode, and the laptop recognizes the tablet when I try to power it up, or when its in the fastboot menu.
But I can't get ADB to recognize the Nexus at all, it doesn't appear in adb devices whatsoever. And right now, the laptop doesn't seem to react when I plug the tablet in after booting into recovery mode. I also tried plugging in the USB cord, then booting into recovery mode, same thing.
I can only get ADB to recognize the tablet if I hit the "Apply update from ADB" option in the recovery menu. It shows up in adb devices, but it says "sideload" next to it, and if I try any other adb command (shell, backup, pull, etc) it just says "error: closed". I tried adb kill-server and adb start-server, then adb backup again, no dice.
I stayed up till 1AM last night fiddling with this thing, and I have a feeling that I might need to wait till I get home, or maybe when I get to work, as I believe I've got the full Android SDK installed there.
So, my two questions on this are...
1) What the hell am I doing wrong? Is there any way for me to recover the photos from the device? I'm sure that adb backup will work, if I could just get this damn laptop to recognize the device.
I've done quite a few Google searches already, and found a few results. I can't post links apparently, but there's a certain thread posted on StackExchange about how to perform a full backup of non-rooted Android devices. While it was helpful, I can't do that backup because this laptop won't recognize the tablet.
But I'm just spinning my wheels here, and could really use some help. Are there different drivers I should be using? Is there a way to run ADB from the bootloader rather than recovery mode? How do I get Device Manager (Windows) to even recognize the tablet when its in recovery mode?
2) So this will be the third time (after I get these photos recovered, hopefully) that I'll be doing a wipe on this tablet. I've got a two year replacement warranty on it. Should I be taking it back for a new one? Would it be a bad app thats causing these issues? Most of the apps I have are "official" ones anyway, aside from a couple of games, but they're all popular ones. After the wipe, should I re-flash it with Google's latest stock ROM?
Thanks in advance!!
Woops, I just realized you haven't unlocked the tablet. Sorry, everything I wrote below won't work because the bootloader won't let you boot into an unsigned recovery image and if you try to unlock now the process will force a wipe. The only thing I can suggest is try booting into safe mode. Sometimes you can get the MTP device to show up even if the system isn't totally started. There is a link in the stuff below for that. I guess you could also try the adb backup again, now knowing what is going on with adb and recovery.
[Info] Guide to entering safe mode, bootloader, stock recovery
[GUIDE] Full Phone Backup without Unlock or Root
====
Almost TLDR.
Anyway, I don't know why you get the System UIDs inconsistent. Probably some corruption somewhere, but who knows the cause. There are sporadic reports of it on this tablet and actually other brand tablets as well, but it doesn't seem like the more widespread issues. Personally I think it would be worth it to exchange it to see if that helps.
Regarding your ADB issues, there are multiple:
First, in stock recovery, adb isn't running until you select sideload, that is why you don't see it under adb devices.
Second, the adb in stock recovery (ie adb sideload option) is restricted in its functions. It basically only supports sideloading.
You don't seem to have this issue, but the regular Google USB drivers won't work for adb under recovery because the USB IDs change and the device usually shows up as an unknown device "Flo". If you are afflicted by that issue, see this post for drivers that will work under both android and recovery:
[FIX] MTP with USB debugging / ADB within Recovery (windows/nexus7)
Hope is not lost though, you can boot into TWRP recovery, which does support a full adb and you should be able to "adb pull" all your files off the sdcard. Just don't do any wipes or formats by accident until you get the files off.
Download TWRP from here: http://techerrata.com/browse/twrp2/flo
Place the file in the same directory as your adb/fastboot executables
Boot into bootloader using Power+VolDown, see this post if you have trouble
[Info] Guide to entering safe mode, bootloader, stock recovery
connect the USB cable to a USB2.0 port on your computer
you should see some indication that the android bootloader device got recognized
in your adb directory enter (I renamed the downloaded TWRP image for convenience)
fastboot boot twrp.img​after maybe 5 seconds of seemingly nothing going on, TWRP will start up
your PC may ask you for drivers, if so, see the link above where I provided drivers
after that you should have full adb available to pull your files
After you are sure you have everything pulled off, try the factory image restore from google.
1. This may or may not help you but have you manually installed the adb drivers on the laptop? If not, check here. It also includes instructions on how to disable driver signature enforcement on your brother's Window 8 laptop. Now, I'm not sure if he updated that driver for flo, or if he even has to, but if that driver doesn't work, download the sdk. A driver comes in it that'll work. I know it'll be painful to wait for the whole thing to download, but it might be your best option. It's in ...\sdk\extras\google\usb_driver\
2. It's up to you whether to return it or not. I, personally, hate dealing with the return process, even if it's in-store, so I usually make-do until a fix is found, or in this situation with a Nexus device, I would try to troubleshoot it. I, too am a software developer by profession (mainly .NET; I develop on Android as kind of a hobby) and I enjoy working out issues myself. But that's just my opinion, it's completely up to you. I doubt it's any apps, I doubt it's any games. I would probably try installing factory images back onto the device and see if that helps.
Thanks for the replies, guys.
I just got home late last night, and while I was too exhausted yesterday to do anything with it, I brought the Nexus 7 with me to work today, so I'll see what I can do with it here. I thought I had the Android SDK installed on my work computer, but I don't. Fortunately, now that I'm back from holidays, I have access to fast internet connections.
My regular desktop at home and my work computer are both running Windows 7, so I shouldn't run into the driver enforcement issues that people experience with Windows 8.
I tried booting it into safe mode once, but I didn't have the USB connected. Even with safe mode, it was just frozen at the 'X' screen, but I'll try it again with the USB connected.
I'm a bit confused though. The tablet hasn't been unlocked, sfhub, so like you said, I won't be able to boot into TWRP. So aside from booting into safe mode, there's nothing I can do to get the adb pull or adb backup commands to work?
If someone can clear that up for me, that'd be appreciated. I'm going to try safe mode now, but as far as I'm aware, all I can do is boot the tablet into recovery mode. So is there a driver that would allow me to use the shell, pull, or backup commands from either stock recovery or the bootloader menu?
Update...
So, safe mode doesn't work as far as booting the device goes; it just hangs at the 'X' screen.
However, something named "Nexus 7" shows up in Device Manager, and when I told it to look for a driver in the folder containing the USB drivers from Google, it installed a driver, and called it "MTP USB Device".
Unfortunately, the device doesn't show up under My Computer (damn it, wishful thinking!!), and then after about 15 seconds, a yellow exclamation mark shows up on the device icon in Device Manager, and it generates an error saying "This device cannot start. (Code 10)".
Does this at least seem like progress?
Stealth22 said:
Update...
So, safe mode doesn't work as far as booting the device goes; it just hangs at the 'X' screen.
However, something named "Nexus 7" shows up in Device Manager, and when I told it to look for a driver in the folder containing the USB drivers from Google, it installed a driver, and called it "MTP USB Device".
Unfortunately, the device doesn't show up under My Computer (damn it, wishful thinking!!), and then after about 15 seconds, a yellow exclamation mark shows up on the device icon in Device Manager, and it generates an error saying "This device cannot start. (Code 10)".
Does this at least seem like progress?
Click to expand...
Click to collapse
It does look like progress. Try booting your phone up into recovery mode, connecting it to the computer, then installing those drivers for the phone again. Mine comes up as "Google Galaxy Nexus ADB Interface" in recovery after installing the drivers, but I think if you can get it to come up as "MTP USB Device", you might be able to use adb commands. I'm not 100% sure, but if you can get it back to recognized as an MTP device again, try quickly switching over to the command prompt and trying the "adb devices" command and see if it shows up. Of course, if you install the drivers and it comes up as an ADB interface device, you should just be able to run adb commands and not need to see if MTP will work.
The computer doesn't recognize the device at all when I start Recovery Mode. On the tablet, all I see is an Android laying down with a red exclamation mark saying "No command."
The only way I can get it to even pop up in Device Manager is if I hit "Apply update from ADB", which enables the adb sideload command, but NOTHING ELSE. If I try to run ANY other ADB command, I get "error: closed".
Remember, the device is COMPLETELY stock, not rooted, and the bootloader is locked. I had to do a wipe the last time this happened, driving down to the States at the beginning of my vacation. So even though I had USB debugging enabled before, I never re-enabled it after doing the wipe. Then I took a bunch of photos, and after rebooting the device for the first time after that one wipe, it again no longer boots up.
I would love to fix the damn thing by just doing another factory reset. But I don't want to do that, because I need to recover the photos that I've taken this past weekend.
I might call Google support and see if they know of any solution.
Stealth22 said:
I'm a bit confused though. The tablet hasn't been unlocked, sfhub, so like you said, I won't be able to boot into TWRP. So aside from booting into safe mode, there's nothing I can do to get the adb pull or adb backup commands to work?
If someone can clear that up for me, that'd be appreciated. I'm going to try safe mode now, but as far as I'm aware, all I can do is boot the tablet into recovery mode. So is there a driver that would allow me to use the shell, pull, or backup commands from either stock recovery or the bootloader menu?
Click to expand...
Click to collapse
With stock recovery and locked bootloader with Android that won't boot, and not being to factory reset because you want to save your data, you won't be able to do any normal adb commands.
The only thing you might want to try is the adb backup command, which I've never tried from stock recovery, so there is a remote possibilty it might work, but probably not.
---------- Post added at 09:56 AM ---------- Previous post was at 09:54 AM ----------
Stealth22 said:
Update...
So, safe mode doesn't work as far as booting the device goes; it just hangs at the 'X' screen.
However, something named "Nexus 7" shows up in Device Manager, and when I told it to look for a driver in the folder containing the USB drivers from Google, it installed a driver, and called it "MTP USB Device".
Unfortunately, the device doesn't show up under My Computer (damn it, wishful thinking!!), and then after about 15 seconds, a yellow exclamation mark shows up on the device icon in Device Manager, and it generates an error saying "This device cannot start. (Code 10)".
Does this at least seem like progress?
Click to expand...
Click to collapse
It would have been huge progress if you got the MTP device recognized as you could drag and drop files.
You can try spending some time figuring out whether it is a driver issue or the unit hasn't booted up far enough to response to MTP requests by removing drivers and let it reinstall with known good ones.
The ADB backup command was the first thing that I tried, it didn't work. I can't do ANYTHING with ADB in recovery mode because the computer doesn't even recognize that the tablet is connected until I select "Apply update from ADB", at which point I can only run the sideload command. Any other ADB command (backup included) brings up "error: closed".
I guess my last hope will be the MTP option, if I can get the driver working. I think I'm going to have to call Google on this one.
Stealth22 said:
Ok, so, this is a two part question.
I've got a 32GB Nexus 7, and I'm having some issues with it. This tablet is completely stock. I haven't rooted it, I haven't unlocked the bootloader, installed a custom ROM or anything. All I've done with it was install OTA updates from Google, download some apps/games, and take some pictures.
About two days after I bought the thing and set it up, I got an error that said "System UIDs inconsistent" or something to that effect. I'd never seen it before, but a Google search revealed that the easiest way to fix it was to do a wipe/factory reset, so I did.
Fast forward to a couple of days ago...I'm from Canada, and while driving down to the States, I was bored, so I took out my shiny new Nexus 7, and turned it on. It was stuck at the 'X' screen, and wouldn't boot. I was frustrated, but because I was still in Canada, I was able to run a search on my phone. Factory reset. Ugh. So I did...once it finished, I used my data plan to download a few essential apps, and it was good to go.
Fast forward to today. I'm going to be returning home later today, but yesterday I decided to try out the GPS functions, because the TomTom GPS I've got isn't the greatest, and I much prefer Google Maps Navigation. A friend with a Nexus 4 was able to use the wifi where we were staying to get directions to various places, and then he'd shut off the wifi, and his N4 would still maintain the GPS signal and navigate him for the whole trip, even with no data, and for a lot of the time, no cell signal at all. I wanted to try the same with my N7, not knowing that many users are experiencing issues with the GPS.
So yesterday I was trying to use the Sygic GPS app, which apparently does offline navigation. And I guess because the N7 location capabilities are iffy right now, it wasn't working. So I, in my infinite wisdom, decided to reboot the tablet, thinking that would fix the GPS. This was after I had taken LOTS and LOTS of photos during the trip.
The tablet reboots, and gets stuck on the 'X' screen again. I was ready to bash my head through the car window at that point.
Long story short, the tablet doesn't boot. I'm a software developer for a living, so I had (keyword.. HAD) USB debugging turned on, but since I had to wipe the thing at the start of the trip, I never re-enabled USB debugging, but I don't recall if you actually have to or not...I'm assuming that it loses that setting when you wipe it.
So USB debugging, I can only assume, is not enabled. I can boot into recovery mode, but all I get is the Android icon with a red exclamation mark, and a message that says "No command". I know that you can press the power and volume up buttons to get the menu in recovery mode.
But what I was hoping to be able to do was use ADB to pull a full backup of the device, to at least salvage all the photos I took. I don't care about the apps, I can always reinstall those. I did not have a chance to set up an auto-sync (either Dropbox or Google+) of the photos, unfortunately.
I downloaded the Google USB drivers, and the Android Platform Tools (the wifi at this hotel sucks, so I didn't get the full SDK), and I'm using my brother's laptop, which is running Windows 8. I can get the tablet into recovery mode, and the laptop recognizes the tablet when I try to power it up, or when its in the fastboot menu.
But I can't get ADB to recognize the Nexus at all, it doesn't appear in adb devices whatsoever. And right now, the laptop doesn't seem to react when I plug the tablet in after booting into recovery mode. I also tried plugging in the USB cord, then booting into recovery mode, same thing.
I can only get ADB to recognize the tablet if I hit the "Apply update from ADB" option in the recovery menu. It shows up in adb devices, but it says "sideload" next to it, and if I try any other adb command (shell, backup, pull, etc) it just says "error: closed". I tried adb kill-server and adb start-server, then adb backup again, no dice.
I stayed up till 1AM last night fiddling with this thing, and I have a feeling that I might need to wait till I get home, or maybe when I get to work, as I believe I've got the full Android SDK installed there.
So, my two questions on this are...
1) What the hell am I doing wrong? Is there any way for me to recover the photos from the device? I'm sure that adb backup will work, if I could just get this damn laptop to recognize the device.
I've done quite a few Google searches already, and found a few results. I can't post links apparently, but there's a certain thread posted on StackExchange about how to perform a full backup of non-rooted Android devices. While it was helpful, I can't do that backup because this laptop won't recognize the tablet.
But I'm just spinning my wheels here, and could really use some help. Are there different drivers I should be using? Is there a way to run ADB from the bootloader rather than recovery mode? How do I get Device Manager (Windows) to even recognize the tablet when its in recovery mode?
2) So this will be the third time (after I get these photos recovered, hopefully) that I'll be doing a wipe on this tablet. I've got a two year replacement warranty on it. Should I be taking it back for a new one? Would it be a bad app thats causing these issues? Most of the apps I have are "official" ones anyway, aside from a couple of games, but they're all popular ones. After the wipe, should I re-flash it with Google's latest stock ROM?
Thanks in advance!!
Click to expand...
Click to collapse
I would take it back, if you haven't rooted it, unlocked the bootloader then you probably got a lemon. Just return it, not worth the hassle. Even if you fix it yourself you shouldn't have too. My recommendation is to return it.
sfhub said:
With stock recovery and locked bootloader with Android that won't boot, and not being to factory reset because you want to save your data, you won't be able to do any normal adb commands.
Click to expand...
Click to collapse
Ah, I stand corrected. I don't have much experience with the stock recovery; one of the first things I did when I got this phone was install CWM, and I haven't flashed a stock recovery image since.
So, back to OP:
Try getting MTP to work in recovery, then you can manually bring the files over through Explorer.
Wait, why not install a custom recovery? go here, download the fastboot file, and put it in your platform-tools folder. Might want to rename it to "recovery.img" if it isn't already named that. Now:
1. Boot into the bootloader (power off, hold Power and Volume down until it vibrates and goes to a screen with an Android on his back and his chest open)
2. Once there, see if adb will recognize your device. If not, try installing the drivers again.
3. If adb sees your device, issue this command (assuming the CWM recovery.img file is in your platform-tools folder)
Code:
fastboot flash recovery recovery.img
Once that's done, boot up into your new custom recovery. From there, make a nandroid (optional, that nandroid will contain your pictures if you want to do a factory reset or accidentally hit something). Now if you can get adb to recognize your phone while in this recovery, you can issue adb commands such as adb pull. I would do:
Code:
adb pull /sdcard/ \sdcard\
That will pull the entire contents of your sdcard to a folder called \sdcard\ under platform-tools.
EDIT:
Slight revision to the command I gave you to pull your pictures. If you just want the pictures taken by your camera, run
Code:
adb pull /sdcard/DCIM/Camera/ camera\
That will pull the pictures and place it into a folder called 'camera' inside of your platform-tools folder. The previous code I gave you would put the entire contents of you sdcard in a folder called 'sdcard' on the root of the C:\ drive because I put a back-slash ahead of the folder name. My mistake.
I'll give it a try, but I'm 99.9% sure that I can't flash a recovery image unless the bootloader is unlocked, which wipes all of the data.
I'm just downloading a factory image now...I've pretty much accepted the fact that the photos are gone.
Stealth22 said:
I'll give it a try, but I'm 99.9% sure that I can't flash a recovery image unless the bootloader is unlocked, which wipes all of the data.
I'm just downloading a factory image now...I've pretty much accepted the fact that the photos are gone.
Click to expand...
Click to collapse
Oh yeah, I'm sorry. I keep forgetting you have your bootloader locked, whoops.
Hey, I just thought of something else. Are you planning on flashing those images one by one, following a guide similar to this one? If so, if you don't flash userdata.img, it should preserve your data, including contents of /sdcard/. He touches on it a bit in the guide:
10) Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 2 below.
Click to expand...
Click to collapse
2) This note is NOT for n00bs. There has been a lot of uncertainty and questions around stock ROMs and losing/wiping data. You CAN flash a stock ROM WITHOUT losing the data stored in /sdcard (and possibly even all apps and app data, although this depends on which apps you have installed). This can be done by skipping step 10 in part D. However, if your device goes into a boot loop, you will need to boot CWM, and wipe data <-- this will wipe your apps and app data, but not /sdcard.
Click to expand...
Click to collapse
Might want to note that the guide I posted was for the Nexus 4, but the process should be the same. Try not flashing userdata.img when flashing the stock image.
If the bootloader was unlocked to begin with, yeah, that would work. The guide for the N7 has a similar note about preserving user data.
I've gone ahead with the factory reset. Next time, I'll be sure to have automatic backups to Dropbox or Google+.
I'm going through the same thing right now.
Photos from vacation in Italy. I did back up half of the trip but wifi was so slow at the hotels that I couldn't get everything.
Now Stuck on X at boot.
Boot loader locked.
USB debugging off.
I installed the Nexus 7 Toolkit.
I too was only able to get my computer to recognize the nexus only in sideload mode.
I was able to load an update to the nexus through sideload and it did install.
I was hopeful that the update would have fix it but it did not.
I poked around in the update zip file and say a script called install-recovery.sh.
I was wondering if this script or another one that runs during the update process could be edited to run something like and adb pull or backup.
Does anyone know if this is possible?
I don't know much about adb or messing around with ROMs, etc. I don't even know what language this sh file is written in. Could someone tell me?
Thanks.
joecap5 said:
I'm going through the same thing right now.
Photos from vacation in Italy. I did back up half of the trip but wifi was so slow at the hotels that I couldn't get everything.
Now Stuck on X at boot.
Boot loader locked.
USB debugging off.
I installed the Nexus 7 Toolkit.
I too was only able to get my computer to recognize the nexus only in sideload mode.
I was able to load an update to the nexus through sideload and it did install.
I was hopeful that the update would have fix it but it did not.
I poked around in the update zip file and say a script called install-recovery.sh.
I was wondering if this script or another one that runs during the update process could be edited to run something like and adb pull or backup.
Does anyone know if this is possible?
I don't know much about adb or messing around with ROMs, etc. I don't even know what language this sh file is written in. Could someone tell me?
Thanks.
Click to expand...
Click to collapse
I don't know if you can edit that script to pull a backup, I'm not really an expert on that subject. But from the amount of time and effort I spent, my guess would be that you (like I was) are unfortunately SOL.
I know it's been 3 weeks since you posted, but I thought I'd reply anyway, in case this ever happens to anyone else. Long story short, I was never able to recover anything, and was forced to do a reset.
I had called Google and tried to see if they could work out a solution. I was willing to ship the tablet to them, have them pull the data off, do a reset, and ship it back, but obviously, they said they couldn't do that.
In the end, I accepted that the photos were gone, and did a factory reset. Then I downloaded the stock image from Google, and reinstalled the stock OS from scratch, because of the issues I was having. I just figured that because this was the third time I was doing a factory reset, that something was screwed up with the factory image that was on the device, and that it wouldn't hurt to do a fresh install.
The very first thing I did was install Dropbox and set up the automatic sync function for photos.
I haven't rebooted my N7 very much since then (for fear of this happening again!), but whenever I've had to, it's started up with no issues. Now, I'm careful about what apps I install from Google Play, and any time I have to do a reboot or if Google sends out an update, I do a full backup first. In fact, I hadn't done a backup in a while, so I just pulled a backup, and restarted the tablet because my BT keyboard wouldn't connect. No issues this time either.
From now on though, any time I go on vacation, I don't care if I'm using a real camera or if I forget the camera and have to use my phone or N7. The laptop comes with me on the trip, and photos/videos taken get backed up at the end of each day. Copied to the laptop, to my USB passport drive, Dropbox, the whole 9 yards. I learned that lesson the hard way, and I'm a programmer for a living, so I definitely should have known better.
Moral of the story...if it's important to you, don't be lazy like I was. BACK IT UP.
Try this:
Stealth22 said:
Ok, so, this is a two part question.
I've got a 32GB Nexus 7, and I'm having some issues with it. This tablet is completely stock. I haven't rooted it, I haven't unlocked the bootloader, installed a custom ROM or anything. All I've done with it was install OTA updates from Google, download some apps/games, and take some pictures.
About two days after I bought the thing and set it up, I got an error that said "System UIDs inconsistent" or something to that effect. I'd never seen it before, but a Google search revealed that the easiest way to fix it was to do a wipe/factory reset, so I did.
Fast forward to a couple of days ago...I'm from Canada, and while driving down to the States, I was bored, so I took out my shiny new Nexus 7, and turned it on. It was stuck at the 'X' screen, and wouldn't boot. I was frustrated, but because I was still in Canada, I was able to run a search on my phone. Factory reset. Ugh. So I did...once it finished, I used my data plan to download a few essential apps, and it was good to go.
Fast forward to today. I'm going to be returning home later today, but yesterday I decided to try out the GPS functions, because the TomTom GPS I've got isn't the greatest, and I much prefer Google Maps Navigation. A friend with a Nexus 4 was able to use the wifi where we were staying to get directions to various places, and then he'd shut off the wifi, and his N4 would still maintain the GPS signal and navigate him for the whole trip, even with no data, and for a lot of the time, no cell signal at all. I wanted to try the same with my N7, not knowing that many users are experiencing issues with the GPS.
So yesterday I was trying to use the Sygic GPS app, which apparently does offline navigation. And I guess because the N7 location capabilities are iffy right now, it wasn't working. So I, in my infinite wisdom, decided to reboot the tablet, thinking that would fix the GPS. This was after I had taken LOTS and LOTS of photos during the trip.
The tablet reboots, and gets stuck on the 'X' screen again. I was ready to bash my head through the car window at that point.
Long story short, the tablet doesn't boot. I'm a software developer for a living, so I had (keyword.. HAD) USB debugging turned on, but since I had to wipe the thing at the start of the trip, I never re-enabled USB debugging, but I don't recall if you actually have to or not...I'm assuming that it loses that setting when you wipe it.
So USB debugging, I can only assume, is not enabled. I can boot into recovery mode, but all I get is the Android icon with a red exclamation mark, and a message that says "No command". I know that you can press the power and volume up buttons to get the menu in recovery mode.
But what I was hoping to be able to do was use ADB to pull a full backup of the device, to at least salvage all the photos I took. I don't care about the apps, I can always reinstall those. I did not have a chance to set up an auto-sync (either Dropbox or Google+) of the photos, unfortunately.
I downloaded the Google USB drivers, and the Android Platform Tools (the wifi at this hotel sucks, so I didn't get the full SDK), and I'm using my brother's laptop, which is running Windows 8. I can get the tablet into recovery mode, and the laptop recognizes the tablet when I try to power it up, or when its in the fastboot menu.
But I can't get ADB to recognize the Nexus at all, it doesn't appear in adb devices whatsoever. And right now, the laptop doesn't seem to react when I plug the tablet in after booting into recovery mode. I also tried plugging in the USB cord, then booting into recovery mode, same thing.
I can only get ADB to recognize the tablet if I hit the "Apply update from ADB" option in the recovery menu. It shows up in adb devices, but it says "sideload" next to it, and if I try any other adb command (shell, backup, pull, etc) it just says "error: closed". I tried adb kill-server and adb start-server, then adb backup again, no dice.
I stayed up till 1AM last night fiddling with this thing, and I have a feeling that I might need to wait till I get home, or maybe when I get to work, as I believe I've got the full Android SDK installed there.
So, my two questions on this are...
1) What the hell am I doing wrong? Is there any way for me to recover the photos from the device? I'm sure that adb backup will work, if I could just get this damn laptop to recognize the device.
I've done quite a few Google searches already, and found a few results. I can't post links apparently, but there's a certain thread posted on StackExchange about how to perform a full backup of non-rooted Android devices. While it was helpful, I can't do that backup because this laptop won't recognize the tablet.
But I'm just spinning my wheels here, and could really use some help. Are there different drivers I should be using? Is there a way to run ADB from the bootloader rather than recovery mode? How do I get Device Manager (Windows) to even recognize the tablet when its in recovery mode?
2) So this will be the third time (after I get these photos recovered, hopefully) that I'll be doing a wipe on this tablet. I've got a two year replacement warranty on it. Should I be taking it back for a new one? Would it be a bad app thats causing these issues? Most of the apps I have are "official" ones anyway, aside from a couple of games, but they're all popular ones. After the wipe, should I re-flash it with Google's latest stock ROM?
Thanks in advance‼
Click to expand...
Click to collapse
Ok, first of all, have you tried to - simply let it on the Charger!??
Then press and hold the power button
If it doesn't work: Has the device ever taken a kind of damage because of heat/water/drop/whatever?
Try to replace the battery.
Try to hold the so►called „KEÝ4" inside of the device- for exactly 16.0 to 16.2 seconds. Then you smoehow can manage and check the hardware health+status+whatever. Efficient application. Also works with 0,1% battery charge.☺☻☺
I'm so sorry for you.
Which Nexus is it? (2012/2013? How many GB? Which Android Version? Because KitKat is bogus.))
I know a Galaxy S3 Mini, fell into water for 3 Seconds.
Then everything worked perfectly fine but... even if the device was turned off and connected to the charger: the device actually did recogniƶe the Charger but then:
{
"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"
}
►Turned into►►→→
‼‼
I hope, that i could help.
All the best for you and your Nexus.

Bricked? Thanks LineageOS

So I tried to migrate from CM to Lineage (which ive already done on my N5) and while formating my data due to encryption, my tablet is completely F'd in the A.
If I had it connected to my PC i could see it power on and would show 30 or so unknown partitions, but my screen would be blank.
I ended up deleting all of the partitions but now i cant even see the device at all.
Since i cant get anyhting on the display and since i cant even get to fastboot, i have a feeling in screwed and need to go get a new board for it now... or just a new tablet i guess, but i rly liked my & and id hate to be w/o it over something stupid like this...
Can anybody else at least confirm or possibly have another idea?
I dont even get the charging animation with it off either...
carnagex420x said:
So I tried to migrate from CM to Lineage (which ive already done on my N5) and while formating my data due to encryption, my tablet is completely F'd in the A.
If I had it connected to my PC i could see it power on and would show 30 or so unknown partitions, but my screen would be blank.
I ended up deleting all of the partitions but now i cant even see the device at all.
Since i cant get anyhting on the display and since i cant even get to fastboot, i have a feeling in screwed and need to go get a new board for it now... or just a new tablet i guess, but i rly liked my & and id hate to be w/o it over something stupid like this...
Can anybody else at least confirm or possibly have another idea?
I dont even get the charging animation with it off either...
Click to expand...
Click to collapse
Do you have ADB set up? if not, now may be a good time and through ADB try download a factory image.
carnagex420x said:
If I had it connected to my PC i could see it power on and would show 30 or so unknown partitions, but my screen would be blank. I ended up deleting all of the partitions but now i cant even see the device at all.
Click to expand...
Click to collapse
Connect it to a PC again and check the USB mode your N7 is in.
If it is, or if you can make it work in, USB mode 9006 then follow this post. The linked N7 image is from my 32GB Hynix but you can use it to restore boot on any eMMC and adjust it later. While you do not see the partitions anymore, you may be able to access the device to restore the image.
If it is USB mode 9008 then your only recovery option is JTAG or hardware programming of the eMMC chip.
Good luck, it is still fixable :good:
the device still appears completly lifeless however i am able to get the device to show up as
Code:
Bus 002 Device 064: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
but im not sure how to go about getting fastboot yet, i get that i can dd an image to it i guess but im pretty sure i only have the 16GB not the 32, wjich i cant seem to find.
After playing with it for a couple hours and reading the entire Unbricking thread, the spot im stuck at now is the 9008-9006 mode switch. I have the QPST software and drivers working right and i get the NAK error but i follow the directions and cant get it into 9006 mode...
LineageOS update of May 24 2017 bricked my Nexus 7 2013 also.
Can't even use the Nexus Root Toolkit to recover. Always get stuck in the Google symbol.
Can enter into recovery, but it takes 15 minutes. And the directory structure showed is all empty.
Rebooting it show some errors saying that the partition table is empty.
"OEM Device Info" of NRT shows that the equipment is now locked also.
Have no idea of what to do. Can't even install the SO again.
There is a thread on "general" that seems to deal with related problems:
https://forum.xda-developers.com/nexus-7-2013/general/rd-thread-trying-to-solve-ota-brick-t3117495
ramon.hugo said:
LineageOS update of May 24 2017 bricked my Nexus 7 2013 also.
Can't even use the Nexus Root Toolkit to recover. Always get stuck in the Google symbol.
Can enter into recovery, but it takes 15 minutes. And the directory structure showed is all empty.
Rebooting it show some errors saying that the partition table is empty.
"OEM Device Info" of NRT shows that the equipment is now locked also.
Have no idea of what to do. Can't even install the SO again.
There is a thread on "general" that seems to deal with related problems:
https://forum.xda-developers.com/nexus-7-2013/general/rd-thread-trying-to-solve-ota-brick-t3117495
Click to expand...
Click to collapse
When you can boot into recovery you are good to go. Use a pendrive and an otg cable and flashthe rom from pendrive.
Already tried that ... Also impossible.
Try this way,
Connect to Computer
Use NRT then pess root, your Device will restart in TWRT then you can put the file in and reinstall.
You may be running into flash wear issues. This device is about 4 years old at this point, a similar thing started happening to the 2012 models. Don't blame the ROM, blame the NAND chip in your tablet.
I have a busted USB port so prefer to recharge via wireless. Sometimes wireless charging keeps disconnect and reconnecting if it's on so I need to shut it off.
I did that and now it just hangs at the Google screen as well.
If I hold Vol down I dont get twrp but the general bootloader. Any choice seems to just reboot it.
I think I'm screwed as well.
Prior to this my pc doesnt detect via USB at all, just charges it.

LG G4 How to find correct version & model

Hello guys,
I am an unlocked LG G4 user running on Android 5.1 Lollipop.
I cant recieve updates through OTA as it always says "You have latest version of current OS". So I tried updating manually.
Since I am not very good with LG flash tools I was looking at unlocking bootloader and twrp.
The problem is :
My hardware info shows "LG H815"
Adb recognizes it as "LGF500L204da3d4 unauthorized"
A google search told me that F500L is Korean variant and now I am totally confused. Am I missing something here.
I have attached screenshots of device info.
Please guide.
The unauthorized thing comes from enabling ADB in the Developer Options. Once you do that, the very next time you connect the G4 to a computer and then run the "adb devices" command it starts the adb daemon and then tries to connect to the device, upon a connection the phone not the computer will pop up a box asking for permission to allow the connection based on an RSA fingerprint (aka the security aspect) and you have to allow that.
Without allowing that you'll never get ADB to work properly. You can try this process to get things working properly:
- Disconnect the G4 from the computer entirely
- Disconnect it from any charger too just so you're good to go
- Go into the Developer Options, revoke all using the "Revoke USB debugging permissions" and reboot the G4 right then and right there as soon as those permissions are revoked, do NOT do anything else, reboot immediately after you make that change
- Upon the reboot let the G4 boot completely and wait 2 minutes before swiping/unlocking the device back to the Home screen
- Plug in the USB cable and make sure you choose the MTP/file option, not charging
- Fire up the adb devices command on the computer and watch the phone carefully for that popup asking for permission to connect
- Choose OK to enable the connection and check the box to make it permanent for that specific computer
After that it should show you the device serial number and say "authorized." If not then you're missing something or there's some other problem, but that's how I've done this on a few hundred devices over the years and never had an issue. The other thing that could be affecting this are making sure you have the proper ADB drivers, sometimes that can be a complete pooch-screw to get working and I can't help on that front.
Pic below is what you're looking for and without granting this permission ADB will never see the device as authorized.
Good luck...
br0adband said:
The unauthorized thing comes from enabling ADB in the Developer Options. Once you do that, the very next time you connect the G4 to a computer and then run the "adb devices" command it starts the adb daemon and then tries to connect to the device, upon a connection the phone not the computer will pop up a box asking for permission to allow the connection based on an RSA fingerprint (aka the security aspect) and you have to allow that.
Without allowing that you'll never get ADB to work properly. You can try this process to get things working properly:
- Disconnect the G4 from the computer entirely
- Disconnect it from any charger too just so you're good to go
- Go into the Developer Options, revoke all using the "Revoke USB debugging permissions" and reboot the G4 right then and right there as soon as those permissions are revoked, do NOT do anything else, reboot immediately after you make that change
- Upon the reboot let the G4 boot completely and wait 2 minutes before swiping/unlocking the device back to the Home screen
- Plug in the USB cable and make sure you choose the MTP/file option, not charging
- Fire up the adb devices command on the computer and watch the phone carefully for that popup asking for permission to connect
- Choose OK to enable the connection and check the box to make it permanent for that specific computer
After that it should show you the device serial number and say "authorized." If not then you're missing something or there's some other problem, but that's how I've done this on a few hundred devices over the years and never had an issue. The other thing that could be affecting this are making sure you have the proper ADB drivers, sometimes that can be a complete pooch-screw to get working and I can't help on that front.
Pic below is what you're looking for and without granting this permission ADB will never see the device as authorized.
Good luck...
Click to expand...
Click to collapse
Ok..So I tried as per above instructions.
The only change is it's written as "device" in place of "unauthorized". The serial number is the same.
I thought it would be written as LGH815...etc etc for the H815 model. But here it's F500L...
Is this normal?
[email protected] said:
Ok..So I tried as per above instructions.
The only change is it's written as "device" in place of "unauthorized". The serial number is the same.
I thought it would be written as LGH815...etc etc for the H815 model. But here it's F500L...
Is this normal?
Click to expand...
Click to collapse
Update:
Found something interesting as well.
The phone doesn't boot into recovery using hardware keys.
I tried with adb and got into a screen showing "No command" with red exclamation.
It means you don't have a working recovery partition now so something got borked. Best case scenario: do a full factory reinstall of the stock ROM and go from there, maybe, using Odin or whatever tool you prefer, these days I have no idea what software there is to be honest.
I don't own a G4 anymore either, but if I find one in good shape for a good price, like $50 or less, I'll more than likely grab it.
br0adband said:
It means you don't have a working recovery partition now so something got borked. Best case scenario: do a full factory reinstall of the stock ROM and go from there, maybe, using Odin or whatever tool you prefer, these days I have no idea what software there is to be honest.
I don't own a G4 anymore either, but if I find one in good shape for a good price, like $50 or less, I'll more than likely grab it.
Click to expand...
Click to collapse
Maybe I should just keep it as it is coz I don't even know what rom to use and actually which model it is.
[email protected] said:
Maybe I should just keep it as it is coz I don't even know what rom to use and actually which model it is.
Click to expand...
Click to collapse
Used to believe HTC devices are tough nuts to crack but LG just blowed me away.

Categories

Resources