yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] jrfullar:
Hi all,

Haven't posted much(or any) but been rooting and such for a while now. I'd like to take my One back to stock and this could be a stupid question but here goes. I've read all the the instruction about going back to stock with RUU, but since there isn't one for Bell mobility I have an OTA but none of the instruction mention using an OTA to revert back to stock so really I don't know what to do with it. Any help be greatly appreciated. Thanks
[One (M7) Q&A, Help & Troubleshooting] jrfullar:
Anyone?
[Nexus 7 (2013) Q&A] sfhub:
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.
[Nexus 7 (2013) Q&A] Johmama:
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.
[Nexus 7 (2013) Q&A] Stealth22:
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?
[Nexus 7 (2013) Q&A] Stealth22:
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? :confused:
[Nexus 7 (2013) Q&A] Johmama:
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.
[Nexus 7 (2013) Q&A] Stealth22:
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.
[Nexus 7 (2013) Q&A] sfhub:
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 ----------

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.
[Nexus 7 (2013) Q&A] Stealth22:
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.
[Nexus 7 (2013) Q&A] reubendevries:
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.
[Nexus 7 (2013) Q&A] Johmama:
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)

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:

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

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.
[Nexus 7 (2013) Q&A] Stealth22:
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.
[Nexus 7 (2013) Q&A] Johmama:
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:

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.
[Nexus 7 (2013) Q&A] Stealth22:
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+. :(
[Nexus 7 (2013) Q&A] joecap5:
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.
[Nexus 7 (2013) Q&A] Stealth22:
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.
[Nexus 7 (2013) Q&A] Hannah Stern:
Try this:

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:

[IMG="89% Battery charge"]http://xdaforums.com/images/icons/advanced/battery_full.png[/IMG] ►Turned into►►→→ [IMG="OMG 3%"]http://xdaforums.com/images/icons/advanced/battery_low.png[/IMG]‼‼

I hope, that i could help.

All the best for you and your Nexus. ;) [IMG="undefined - no Image Description."]http://xdaforums.com/images/icons/icon14.gif[/IMG]
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Sathub4u:
Hi Android frnds..i have installed a new rom in my sony LWW,the rom is super smooth but after installation of rom i cudnt download apps from google play:( i tried lear data in google play and singed in with different user,but no use:(:crying: plzzzzzzzzzzzzzz helppppppppppppp.when trying to download it keeps on loading..
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] gaga0101:
try settings/apps/all. find google play and clear data,maybe you have to reboot.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] bejunk:
simply download playstore apk from internet ond replace in system it mostly solves this problems (iv u have newest version use some older..)
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Sathub4u:
Thanks,Frnd
[MDA II, XDA II, 2060 General] varma_in_ap:
Hi,

does any one know where can i get Windows Mobile 5.0 upgrade for XDA 2i?

Is it possible to upgrade if ROM is not available right now in future?

tia for comments
[MDA II, XDA II, 2060 General] Rudegar:
there is not any 2005 for IIi

that i know off

the official word from the people who sell the alpine / andes which the IIi a part of is that there will never be an 2005 update for it

so unless it's leaked like the himalaya version

or if somebody manage to move the rom from himalaya to other htc devices

then it will never be possible
[MDA II, XDA II, 2060 General] varma_in_ap:
Hi There,

thanks for reply.

so sofar only Windows Mobile 5.0 ROM is available for only XDA II ?

no other O2/HTC Models ( Pocket PC Phone) has Windows Mobile 5.0 ROM ?
[MDA II, XDA II, 2060 General] Rudegar:
well the himalaya is leaked as in it was never supposed to have gotten out from htc

and the official words from imate who also oem these devices along with o2, tmobile....

then there will be no 2005 for any of the current devices

the first 2005 device will be the utms phone called universal which will be prob be released this fall

there is also an 2005 smartphone rom leaked for the thyphone smartphone
[MDA II, XDA II, 2060 General] varma_in_ap:
hmm.. :x

seems like its good to buy a second hand XDA II and upgrade ROM to windows mobile.. :-( compared to buying new XDA IIi. :?

i wonder why HTC/O2/ is doing this.. :?:
[MDA II, XDA II, 2060 General] Rudegar:
why do you think 2005 is that important ?

it's more about having the latest and greatst

much software still run on ppc 2000 and even earlier

your device will continue to work for a long time if you just stick with your current 2003 or 2003SE
[MDA II, XDA II, 2060 General] AlanJC:
Maybe because WM2005 is:

More stable

Looks nicer

Easier to use

Better UI as a phone

Better Office support

And now Buzz has finally merged the Disk on Chip partitions to get 32mb persistant storage, it's even better as you will never lose your data if the batteries run down :D
[MDA II, XDA II, 2060 General] varma_in_ap:
yeah.. future safe :-) better battery life( or same battery life, but longer usage to be precise.) and new UI..
[Samsung Galaxy Nexus] Deejayadhd:
have a sprint galaxy nexus, had the original replaced because the usb port crapped out, and the replacement had seriously weak wifi strenght so i have another one coming. was just wondering the difference in these model numbers, cant really find anything... have a look at the screen shot.
[Nexus 7 Q&A, Help & Troubleshooting] santan007:
My nexus 7 recently started to behave weirdly, it doesnt charge while turned on, neither with USB or AC. It does charge perfectly well when turned off.

I am unable to use the USB either no device is detected, nor in normal mode, USB debugging, fastboot or adb.

Please help me to get this USB brick fixed on my Nexus 7 asap.

Please help developers!
[Nexus 7 Q&A, Help & Troubleshooting] Cappurnikus:
I've had this problem for a few weeks now and have yet to find a solution.
[Nexus 7 Q&A, Help & Troubleshooting] cmonsterf50:
I'm quite astonished I haven't found a fix for this either. I have yet to open mine up ... I'm try to get the bootloader relocked, so I can warranty the dumb thing. But since it's not recognized by USB when powered on, I can't.
[Nexus 7 Q&A, Help & Troubleshooting] SlowCobra96:
Have you tried putting pressure on the cable when it's plugged in? Also are you using the factory cable?

Sent from my Nexus 7(2012) that has zero issues.
[Nexus 7 Q&A, Help & Troubleshooting] cmonsterf50:
Yep ... Tried pushing. Pulling. Etc. Factory cable. Non factory. Doesn't seem to matter. Anything I use charges fine off. Once on ... No juice
[Nexus 7 Q&A, Help & Troubleshooting] SlowCobra96:
Unfortunately it is a hardware failure. Most likely the USB port assembly. It is possible there is a loose ribbon cable connection.
[Nexus 7 Q&A, Help & Troubleshooting] mswin341:
Nexus 7 not charging

I have the same problem. My Nexus 7 will not charge when turned on. It will not now connect to my pc. I have checked the drivers and all are ok.

It happened a few days ago Its rooted. I can restore backups that are on my Nexus through rom manager, but still the same problem. I thought of doing a factory reset, but if it will still not connect to my pc. I will loose the data. If it is a hardware usb port failure, what is the next stop
[Nexus 7 Q&A, Help & Troubleshooting] krazierokz:
I know this is going to sound strange but open up the back of the Nexus and you will find your battery... And you will notice that it's loose you have to plug or wedge it back on to the battery clip it comes loose overtime use a credit card or similar to open the case :thumbup:;) success

sent from my t mobile S4
[Nexus 7 Q&A, Help & Troubleshooting] mswin341:
Thanks for reply, already checked battery and connections. It charges perfect when not switched on, that's what I find strange. It also charges when connected to my pc
[Nexus 7 Q&A, Help & Troubleshooting] krazierokz:
sorry man good luck was hoping i could shed some light LOL
[Nexus 7 Q&A, Help & Troubleshooting] mswin341:
Did you find an answer, I also have the same problem
[Nexus 7 Q&A, Help & Troubleshooting] mswin341:
Nexus 7 not charging/USB not detected while turned on

Has anybody else had the same problem, if so, how did you overcome it.
[Nexus 7 Q&A, Help & Troubleshooting] raylgo:
Similar thing happened to me... No amount of pressure or angling of the charging port would work. Batteries ran dead as a result. Sent it to the service center and they would assess it for 2-3 days and try to repair since it is under warranty. I'm gonna get an official dock to try and save the charging port from the stress of always being in use although I know that's not the only factor at play.
[Nexus 7 Q&A, Help & Troubleshooting] mswin341:
Nexus 7 not charging/USB not detected while turned on

That's sounds a good idea with the official dock for charging, but you should not have to do that.

To much usage of the micro usb port is going to give problems. I'm always connected to my pc, downloading roms ect. but as I said before, my N7 charges perfectly when not turned on.
[Nexus 7 Q&A, Help & Troubleshooting] mswin341:
Nexus 7 not charging/USB not detected while turned on

As I can't connect my N7 to my pc. Is there anyway to revert to stock. Need to return for repair. USB port not working as it should.

N7 is rooted