yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Q&A, Help & Troubleshooting] darkgandhi05:
That worked. Nice and simple. Thanks.
[Nexus 7 Q&A, Help & Troubleshooting] Kralik:
Wondering if I can get some help here -- I read the whole thread and searched around Google for some answers but have had no luck.

I'm trying to return my Nexus 7 to stock. So far everything seems to be working fine... I flashed the 4.1.2 stock rom and relocked the device. However, recovery doesn't seem to work properly. When I boot into recovery from fastboot, I get the standard android with exclamation mark. But, when I press Power+VolUp or Power+VolUp+VolDown or press and hold or whatever... I get no recovery menu. What am I doing wrong? I tried unlocking the bootloader and reflashing recovery, but no dice.

I hope I'm missing something simple?
[Nexus 7 Q&A, Help & Troubleshooting] El Daddy:
Hmmm volume up + power should do it. Sometimes it can be a bit tricky.
[Nexus 7 Q&A, Help & Troubleshooting] Kralik:
Trust me, I've tried that combo and its variations a dozen times. I'm having the same problem as others from this thread:

http://xdaforums.com/showthread.php?t=1929379

But I'm not finding a good solution there either.
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
Since you've already rest your device, would you mind flashing 4.2.1 and trying again? Make sure to flash everything in flash-all. I'm wondering if the newer recovery will behave the same.
[Nexus 7 Q&A, Help & Troubleshooting] Kralik:
Thanks for the suggestion -- I have actually tried both 4.1.2 and 4.2.1 now and they both have the same behavior. Different bootloaders, different recoveries each. Ran flash-all both times. When I try to get to recovery from fastbook, the Google screen pops up for a few seconds and then I get the exclamation android screen which will not respond to any keypresses. Eventually I have to hard-power off (hold power for 10-20 seconds).

Note that the Nexus does work... boots to welcome screen, fastboot works of course, but I want it completely back to its original settings. Hmm... :confused:
[Nexus 7 Q&A, Help & Troubleshooting] ajacks7553:
Problem accessing internal storage?

Hey guys,

Hoping you can help because I’m have some serious issues bringing my nexus 7 back to life.

Followed the instructions step by step, however I’m getting the following errors once I get to flashing the bootloader (see screenshot). When I boot into recovery I get the following errors (see photo). It looks like I don't have access or the computer can't connect to the Nexus' internal storage.

Any ideas? I'd love to get it back up and running again

Let me know if you need any other info

Cheers
[Nexus 7 Q&A, Help & Troubleshooting] ajacks7553:
Update

I've tried the same instructions with the 4.2.1 stock image and it seems to write boot, recovery and system fine but is then unable to write system. I've also extracted system.img into \platform-tools\ and tried to flash it separately (fastboot flash system system.img) and it keeps saying 'command write failed - see screenshot.

Any help would be amazing
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
Try changing the drivers to the Universal Naked Driver. I've seen a few people with errors like that in the past and the issues were related to drivers.
[Nexus 7 Q&A, Help & Troubleshooting] ajacks7553:
No luck

I uninstalled the drivers for the adb interface in device manager and then installed the universal naked driver and keep getting the same error. Am I doing something wrong here, i.e. not uninstalling the drivers completely?

Any other ideas?
[Nexus 7 Q&A, Help & Troubleshooting] El Daddy:
Try plugging it with a different cable and/or a USB port that's connected directly to the motherboard.

Sent from my Nexus 4
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
If what El Daddy suggested works please come back and let us know.

Sent from my Nexus 4
[Nexus 7 Q&A, Help & Troubleshooting] ajacks7553:
THANKYOU!

Seriously, I can't thank you guys enough!! THANK YOU THANK YOU THANK YOU!!!!!!!!!!!!!!

This guide and the help here has got him back up and running. When I used a different plug and my USB 2.0 port (instead of 3.0) it worked. It's probably taken me 10 hours+ of trying and lots of searching the net but my nexus is back!

Very happy right now haha
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
Glad to hear it, thanks for coming back and letting us know!
[Nexus 7 Q&A, Help & Troubleshooting] sgkvra:
Full Backup

See to How-To Geek "How To Create a Full Android Phone or Tablet Backup Without Rooting or Unlocking Your Device"

I don't know it's bit-by-bit coping of all partitions and permissions on root level for all system files or only copying selected files on user level.
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
I'm looking at updating/redoing the guide in the next couple weeks and it will include links to backup guides if not the actual instructions.

Sent from my Nexus 4
[Nexus 7 Q&A, Help & Troubleshooting] Skyfall007:
works well.Thanks dude!
[Nexus 7 Q&A, Help & Troubleshooting] B3rt0:
worked like a charme :)

Now all the flashing routine again :\
[Nexus 7 Q&A, Help & Troubleshooting] jt2173:
Thank you all for the great write up and tips!
[Nexus 7 Q&A, Help & Troubleshooting] UlysisAM:
Just wondering how long does installing the factory ROM on the tablet take.

Only because for 10 minutes so far, it is hanging on "sending 'boot' (4942 KB)..."

Thank you for your time and help.
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
It shouldn't take anywhere near that long. Try again with a different USB port.

Sent from my Nexus 4
[Nexus 7 Q&A, Help & Troubleshooting] UlysisAM:
Well I certainly feel like an idiot.

Thank you for your help. Much appreciated.
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
No worries. Glad to hear it worked out.

Sent from my Nexus 4
[Nexus 7 Q&A, Help & Troubleshooting] puacham:
so, can you tell me about cm 10.1 offical?is this﻿ good for my n7? aboout﻿ battery life how long this can take ? will wifi better or anything? hope you rep soon
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
You'll be able to find the answers to your questions in the cm10.1 thread.

Sent from my Nexus 4
[Nexus 7 Q&A, Help & Troubleshooting] jask05:
Great work :) It is so useful !! And you explained it very well

Thanks U
[Nexus 7 Q&A, Help & Troubleshooting] ashwin123:
Ive had the drivers installed, fastboot devices showed the n7 fine, everything happened as you said it would, finished locked bootloader and then hit reboot and stuck on google screen.

Tried doing it with 4.1.2 and 4.2.1 both and same results.

Have also tried other versions with various toolkits and the same, n7 sits with the "google" screen...

Please any help would be appreciated!

Ash (www.cursed4eva.com)
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
Would you be able to run through the procedure again and paste the output in paste in or similar?

Sent from my Nexus 4
[Nexus 7 Q&A, Help & Troubleshooting] ilpolpi65:
I had your same problem ....at the end only with Linux(ubuntu) i've been able to put back in life my nexus 7

---------- Post added at 10:51 AM ---------- Previous post was at 10:14 AM ----------

anyway here there is an error:

C:\adt-bundle-windows-x86_64\sdk\platform-tools>fastboot flash bootloader-groupe

r-4.13.img

the right command is:

C:\adt-bundle-windows-x86_64\sdk\platform-tools>fastboot flash bootloader bootloader-groupe

r-4.13.img

bye
[Nexus 7 Q&A, Help & Troubleshooting] farmerned:
Thanks!

I dialed back from 4.2.1 to 4.1.2 on my Nexus 7 (WiFi). Piece of cake. Thanks, mate!
[Nexus 7 Q&A, Help & Troubleshooting] ashwin123:
Fixed that error in the next line bro,

btw can you give me a link on how to do it with linux?

Ash
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
Unlocking the bootloader should be the first thing you do. I'm wondering if your is being caused by running unlock after the erase commands. Also, try letting the device completely boot before locking the bootloader again.

Try again and run the commands in the order outlined in the guide and skip locking the bootloader. There is a link to the Linux Android platform tools in my signature, the commands are the same.
[Nexus 7 Q&A, Help & Troubleshooting] ilpolpi65:
With linux u must run the flash-all script ...

Inviato dal mio Nexus 7 con Tapatalk 2
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
The shell scripts have always been there but at no point has it been required to run the script explicitly. You can still run the commands as outlined in the guide.

Sent from my Nexus 4
[Nexus 7 Q&A, Help & Troubleshooting] ilpolpi65:
http://www.modaco.com/topic/355944-...a-what-to-do-when-it-all-goes-horribly-wrong/

Inviato dal mio Nexus 7 con Tapatalk 2
[Nexus 7 Q&A, Help & Troubleshooting] ashwin123:
its late tonight, will try and post back tomorrow (in 12 hours)

Thanks for the help :)

Ash
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
Yep, that is what is outlined here in detail. :silly:

Running the batch file in Windows or the shell script in Linux will work fine provided all the files from the factory image are available in the directory the batch file or shell script is run from. I have intentionally avoided this in the guide for the sake of verbosity and education. I'm not saying nobody should run the scripts, by all means if you know what you're doing, go right ahead! I merely stated that it is not a requirement.

If someone is doing this for the first time, it is more important they follow the steps manually to aid in their learning and will also allow them to provide more useful information in the event they run in to a problem.
[Nexus 7 Q&A, Help & Troubleshooting] michalurban:
Whats the content of "userdata.img"? Or yet better, how can I alter the batch file so it wont erase userdata? Im trying to remove the userdata.img from the original zip and removing the "erase userdata" command from the original flash batch - but wont it screw something?

EDIT: Ok, I dont know why but it didnt work ... I hoped that my files would remain intact but they are gone ...
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
When you ran the "fastboot -w update ..." command, userdata and cache partitions were wiped - this is the

function of the -w parameter.

If you wanted to flash the device without losing the contents of /sdcard or custom recovery you could run the commands outlined below. Please note the commands assume a Wi-Fi Nexus 7[/code]

fastboot erase boot
fastboot format cache
fastboot erase system
fastboot flash bootloader bootloader-grouper-4.13.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img

The dalvik cache will need to be wiped before normal boot, so do this from custom recovery and boot normally.
[Nexus 7 Q&A, Help & Troubleshooting] michalurban:
Thanks, I realized what the -w means in the end. :good: But what surprised me is that not only my files remained, but also an installed app (file manager). Or is that caused by the not-erased dalvik? And wont it mess with a newliy installed rom? (say I had smoothrom with apps before and I would install a stock rom this way).

BTW isnt dalvik cache erased when cache gets erased?

EDIT: Is there no way to wipe dalvik using fastboot? I like things automatised ... :)
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
By not erasing/formatting userdata or flashing userdata.img the /data partition remains intact which is where user installed applications and their data live. User's files also live in the /data partition under /data/media/.

Yes, if you are switching between ROMs this may cause problems. I typically use this method when I'm updating a stock device to a newer minor version (ie. 4.1.2 -> 4.2) where the device has had very minor changes - custom recovery, root, etc. If you go from stock to any other ROM or back, you need to be aware that there *may* be issues. My opinion, is that you can try it anyway - worst case scenario is that you'll need to wipe the device, which you would have done anyway, but you may be able to just wipe application data if there is a specific app giving you problems. Either way it's the experimentation that is fun, IMHO.

Typically, dalvik cache lives at /data/dalvik-cache; the /cache partition is separate. Right now the simplest way I can think to wipe the dalvik cache is from custom recovery.
[Nexus 7 Q&A, Help & Troubleshooting] michalurban:
Okey, thanks for the reply, its been much helpful! :) I dont understand why did google make it this way. I love the way this is done in my Nexus S phone -ie. it has Mass storage && I can reflash stock rom without losing my files. Sick!
[Nexus 7 Q&A, Help & Troubleshooting] ashwin123:
unlocked bootloader

ran all commands in sequence

did not relock

now stuck on "google" again but with an unlock icon below...

Please HELP!!! :(

When it reboots the MTP USB Device driver installation fails on win 7... does that make a difference?

Ash
[Nexus 7 Q&A, Help & Troubleshooting] kakukreja:
PLZ HELP

Hi everyone,

Im new and i have a big problem. I tried to flash cyanogen mod 10 on my nexus 7 and it flashed it. I had made a backup, but when i wanted to go back to stock rom 4.2.1 rooted, i couldnt find my backup. I tried this and everything goes welll until the sending system part. it usually takes 2 mins according to others. but ive been on it for an hour and it still says sending system. PLZ help, i have no idea what to do. I can boot up into bootloader but not into recovery. PLZ help
[Nexus 7 Q&A, Help & Troubleshooting] trandithao:
thanks you

i bought my tablet 3 days ago ! i really tired with re-stock use toolkit only one big error :

Tilapia does not match but all tool duno show this error . when i use Manual flash with command i can back to stock :d. Thanks your command again

fastboot flash radio radio-tilapia-1231_0.10.0_1021.img
[Nexus 7 Q&A, Help & Troubleshooting] padremayi:
Glad to help you :)
[Nexus 7 Q&A, Help & Troubleshooting] 0145ethan:
Thanks for this man!
[Nexus 7 Q&A, Help & Troubleshooting] blenchh:
I guess i'm in driver hell....

So i believe i followed all the directions but unfortunately this god forsaken computer chose this moment to do a restart against my will to update windows and at that very moment my nexus was on the screen where it said start and pointed towards the power button and now its all black and looks like its really messed up T____T i see flickering lines like a broken tv display, but when i restart the nexus it goes back to the android with its chest part open and it says start, but after some time it goes back to "driver hell" what should i do now??? and before my nexus was recognized and now its not x_x

**EDIT**

I also realized that i downloaded the wrong factory image, i had downloaded 4.1.2 nakasi, but i dont even think i used it right to cause any effect, all i did was use 7 zip to extract the file and when that finished the window would just disappear, and another thing is that i dont think i can debug on my nexus because i would get a prompt to allow debugging and i never knew you had to press the build # a number of times to get it...so how does this affect me?
[Nexus 7 Q&A, Help & Troubleshooting] michalurban:
Sorry, quick question: whats "radio-tilapia-1231_0.10.0_1021.img" and where did it come from? I didnt find anything on google ...
[Nexus 7 Q&A, Help & Troubleshooting] mariocaraujo:
Great guide, thanks.

A question: can I use Titanium Backup to restore data(only apps, not system) after the wipe?
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
It's the radio firmware included in the JOP40D factory image for the 3G Nexus 7.
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
I can't see a reason this would be a problem. Worst case scenario you might run in to a force close... give it a shot.
[Nexus 7 Q&A, Help & Troubleshooting] comminus:
Sorry, I'm having a really hard time understanding what you've written so I'm going to ask some questions.

You mentioned you downloaded the wrong factory image... please let us know exactly which device you have.

Are you able to get the device in fastboot mode? If yes, can your computer detect the Nexus 7? Either way, can you provide an image of the device in whatever state(s) you're stuck at.

ADB debugging is not required at this point, we only need to worry about fastboot. Lets focus on trying to get your device running and go from there.
[Nexus 7 Q&A, Help & Troubleshooting] blenchh:
1. I have the nexus 7 (I had downloaded nakasi-jzo54k the first time from asus website, when i realized that was the wrong one i downloaded nakasi-jop40d which is the right factory image)

2. I can get it into fast boot mode, my computer can recognize my nexus 7 (attachment is current state)

**EDIT**

about 2 minutes after being idle my nexus disconnects from my computer and the screen starts to look like this. it may be hard to see but its basically a bunch of white lines and dots
[HTC One X] Slaytanic:
Great job, you're really fast! ;)

EDIT: installation fails on my HOX.. it asks me if I want to replace this system app and when I say OK it fails installation.
[HTC One X] j4n87:
you need to push it to system/app with adb. You cant install it.

I will create a flashable zip in a few...

EDIT: flashabel zip attached.
[HTC One X] samarain:
When try to install this apk he decline, shoul substitute in the system directly?

---------- Post added at 08:07 AM ---------- Previous post was at 08:05 AM ----------

Already answer :)
[HTC One X] Slaytanic:
You're too fast :good: Thanks! I'll donate for your marriage :)
[HTC One X] HebeGuess:
Great, I done testing by myself yesterday..

My HOX prompt out my IMEI, OMG..

Thanks for the FIX..

You're even faster than Samsumg..

HTC should voices out and fix it ASAP too..
[HTC One X] twics:
Thanks

This is a little over my head:o but did the test and my IMEI showed up so I guess im vulnerable, thanks for the fix.
[HTC One X] TAGTRAUM:
I did the test...Nothing happened, no dialer run, no showing #06, no IMEI appeared, loaded like plain link....Do i need install this fix??

ROM - ViperX 2.7.1, Browser - Opera :cyclops:
[HTC One X] robocik:
read somewhere that only stock browsers are vulnerable. Opera, Chrome, Firefox etc. should be fine...
[HTC One X] j4n87:
All HTC Sense devices are affected...this browser thing seems to work just on stock browser though. But keep in mind that those codes ca be sent via sms as well.

Please read my article carefully again, then you can decide on your own if you want to flash this patch or not.
[HTC One X] j4n87:
correct, but as mentioned above those codes could be sent via sms as well.

btw...you are alive! =P

Imo theres really no danger concerning this codes.

I didnt tested it myself, but through my code analysis this code should never execute on our sense One X devices.

Please check the updated OP at the bottom.
[HTC One X] pandata000:
Just made a quick fix app for those that don't want to alter their dialers - http://xdaforums.com/showthread.php?t=1908170
[HTC One X] geenyous:
Nope, it works on chrome too.

I am using an AOSP contacts/dialer hybrid and I see the IMEI when visiting the page linked in OP (through chrome).

Now, I tried to fix the code part in the dialer I use but I get FCs after installing, no matter if I sign the apk or not.

But I trust you fully if you say that there should be no effect on our One X as there is no Facotry Reset code to be run through the dialer.

Also, I have a nandroid around which is never really older than 2 weeks and my apps backup and sync to Drive every other day.

Btw, I attached the apk if you want to have a look.
[HTC One X] j4n87:
planned that as well, but dont have ecplise at work =D.

Good work m8, linked it in the first post above the attachments.
[HTC One X] samarain:
I update the dial but lose the red venon dial, if i run the redvenon zip this invulnerability comes again, right?
[HTC One X] j4n87:
Yepp
[HTC One X] ShyamSasi:
Great work Jan! I knew someone in XDA will fix the problem :)
[HTC One X] ViTAMiNCHEG:
Flashed .zip file via CWM, after rebooting my phone I went to this http://dylanreeve.com/phone.php page to check if this working, the IMEI thing poped up anyway. Does this thing works? How can I check that?
[HTC One X] j4n87:
please reread the OP.
[HTC One X] Alex-V:
Samsung have the same problem :)

Anyway thx for the fix
[HTC One X] :
tested myself with the zip.

I already removed the imei method call as well, so it should work.

You guys really dont need to worry about that security issue.

I just reacted to the speadded info, where some blogs claim the issue could affect also current HTC sense devices...after my findings this is not the case. The explanation is in the first post.

Make a nandroid, backup your sd-card and try to run the codes I posted at the bottom. YOu will notice, that none of them will whipe anything.

For people that are still frightend I posted an explanation how to kill the method that executes those USSD commands..to be 100000% sure.
[HTC One X] pandata000:
Thanks man ! Your fix is better, but I made this one for lazy users :)
[HTC One X] inzaghi75:
Jan could you please make it for venom theme dialer.?
[HTC One X] diamant-x:
It should be said at the beginning in big bold letters that this is not needed as the "harmful codes" don't work in our HTC Devices...

Proof:http://xdaforums.com/showthread.php?p=32082049#post32082049
[HTC One X] Alex-V:
I listen to radio and they said Samsung..now I'm ?!?
[HTC One X] Vorbeth:
Few thing's I would like to point out:

First; The wipe code's only effect Samsung devices.

Second; They are NOT USSD Codes! They are MMI codes. (Source: http://berlin.ccc.de/~tobias/mmi-ussd-ss-codes-explained.html) Thanks to Amon_RA

As for patching the IMEI MMI code, it's not really a security issue, that is a mandatory MMI code enabled on all mobile phones, be they Android, iPhone, Nokia or even old 'dumb' phones.
[HTC One X] :
I already know that...I pointed out as well, that those codes doesnt affect htc devices. And the showing of the IMEI dialog has no connection to the vulnerability of our phones. The info that is spread over the internet that HTCS devices may affected is wrong and not prooven.

It's possible though that HTC got other codes that may erase the user data. So preventing the calls to execute those "secret codes", what no one needs actually, at least on a rooted device, isnt that wrong.
[HTC One X] -fluffy-:
i have now try all off thoose codes the only one there is working on my phone is this one here

*#06#=imie
[HTC One X] fisha21:
Jan, thanks for taking the time to look into this, and explaining exactly why this isn't an issue on our phones. That said, thanks for the quick fix too ... peace of mind never a bad thing!
[HTC One X] lonewolf083:
visual voice mail

hey j4n

i flash your fix for ussd on viperx 2.7.0

the fix totaly broke my orange visual voice mail

when i select a message to listen it the app FC ,
[HTC One X] pandata000:
What about the MMI for SIM card PIN code change that can block the card on 10+ wrong tries?
[Atrix 4G Themes and Apps] Zombienaut:
I'm not taking credit for this, but I found this over on the Atrix 2 forums. It's a lot like the Atrix HD launcher with the exception of the quick settings Page left of the homepage and a favorites app tab. Unfortunately, just like the Atrix HD launcher, the circle clock widget force closes. However, the favorite contact widget works along with the Motocamera app(preview doesn't work but still captures pictures perfectly.) Simply unzip the file and push apps to system and change permissions. Reboot and enjoy. If this is old news, feel free to let me know. https://m.box.com/view_shared/r2p1xjem3wlc9wnl9ja9
[Atrix 4G Themes and Apps] Zombienaut:
Some photos.
[Atrix 4G Themes and Apps] mrtausif2004:
For ics or gb?
[Atrix 4G Themes and Apps] Zombienaut:
As far as I'm concerned it won't work on Gingerbread.
[Atrix 4G Themes and Apps] zimplemeh:
Would this work on aokp JB?
[Atrix 4G Themes and Apps] Zombienaut:
I personally haven't tried it on any JB roms, but considering the Atrix HD launcher ran on JB, I can't see why this wouldn't.
[Atrix 4G Themes and Apps] grim_ripper:
Is it possible to get the widget on other launchers?
[Atrix 4G Themes and Apps] Zombienaut:
Unfortunately no. The widgets will only work with a Motorola supported launcher. Such as the Atrix HD launcher and this one.