yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Hi, Ricey_uk...

Mmm... not sure, but I think you're trying to flash the wrong factory image for your device...

Reason being, is because (QUOTE: fastboot flash bootloader bootloader-tilapia-4.13.img) 'tilapia' refers to the 3G/GSM variant of the Nexus 7.

But you appear to have a (QUOTE: (bootloader) product: grouper) 'grouper' device. Which is WiFi only... this seems to be supported by the two lines in your output...

(bootloader) version-baseband: N/A

(bootloader) version-cdma: N/A

... which suggests your N7 has no 'radio' capability.

You need the factory stock image for "nakasi" for Nexus 7 Wi-Fi only (device board "grouper").... NOT "nakasig" for Wi-Fi & Mobile (device board "tilapia").

(See my sig for download links).

-----------

In short, there is an incongruity/contradiction in your reported outputs.... the device is either 'grouper' or it's 'tilapia'

It can't be both.

If it has a SIM card (like a mobile phone), or a space for a SIM card, then it's 'tilapia'... if it doesn't, then it's 'grouper'.

Ensure you are flashing the correct factory stock for your device.

-----------

But having said all of that... (and if there is confusion, it needs to be cleared up)... it doesn't explain why something as straightforward and innocuous as...

fastboot oem unlock

...isn't working.

Two possibilities occur to me...

1) A bad USB connection. Try a different USB port on your PC... Or, maybe, a different USB cable.

Once the fastboot oem unlock command is issued at the PC end, it will need to be confirmed at the Nexus 7 end (see attached thumbnail). Use either of the two VOL buttons to choose YES and confirm by pressing the POWER button.

2) It's possible there could be a hardware failure... some problem with the EMMC flash memory chip. As alluded to by a previous poster...

Whilst I don't discount the possibility that it COULD be EMMC chip failure, I'm not inclined to think that this is a likely possbility. More prosaic explanations need to be explored first.

First... check the integrity of of your USB connections - at both ends; change to different USB ports on your PC; if you can, try a different PC; try a different USB cable. And confirm at the Nexus 7 end, once the unlock command has been issued. (again, see attached thumbnail).

Second... if you are going to try to fastboot flash back to Android factory stock... make sure you do so with correct version for your device. If you're device is Wi-Fi only, you need the 'grouper' version... if not, the 'tilapia' version.

Hope this helps.... and good luck.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] Ricey_uk:
Hi Ged,

thanks for the info, I was wondering about the .img versions - but I can't seem to find the 'grouper' version of 4.13 anywhere. It's not on the factory downloads page (google)

As for the unlock, it does indeed come up with the screen as you showed, and pressing the power button for 'yes' says that it is unlocking. When it then reboots itself it just stays blank. A hard power cycle back to recovery states that it is still locked.

thought?

cheers
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Hi, Ricey_uk...

Yeah... that, unfortunately, does not sound good at all:(. Unlocking the bootloader just sets some 'flag state' on the internal EMMC flash chip. Specifically, somewhere in the mmcblk0boot0 partition, where the bootloader lives.

There's some technical info here...

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

If fastboot oem unlock is performing as you describe, then it strongly suggests some sort of hardware failure. It just shouldn't behave that way... once you have confirmed the oem unlock request on the Nexus 7, the PC should display (if I remember correctly), the following...

Unlocking....

The device is unlocked now...

The whole procedure should take no more than a few seconds. Blank screens and forced reboots have happened many times on my Nexus 7... but never whilst unlocking the bootloader (and yes, I have locked and relocked several times, when I was experimenting with the

'motochopper' root exploit

).

----------------------------------

Incidentally, you won't find 4.13 on the

factory downloads page

, as that number refers to the bootloader version for JellyBean 4.2 and 4.2.1. (It's not always the case that with each new version of JellyBean the bootloader is updated).

Anyway... looking through my collection of system images on my laptop, I find the following...

JellyBean 4.1.2 -> bootloader-grouper-3.41.img

JellyBean 4.2.0 -> bootloader-grouper-4.13.img

JellyBean 4.2.1 -> bootloader-grouper-4.13.img

JellyBean 4.2.2 -> bootloader-grouper-4.18.img

JellyBean 4.3.0 -> bootloader-grouper-4.23.img

With JellyBean 4.3 being the latest, and it updating the bootloader to 4.23.

If you're still stuck on bootloader version 4.13, then that means it was last updated with the rollout of JellyBean 4.2, sometime around November 2012.

----------------------------------

All of which is technically interesting... but probably doesn't help you.

I think there is a hardware problem on your Nexus 7, that is preventing the bootloader-lock-state flag from being correctly set.

Wish I could be of more assistance.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] Ricey_uk:
Thanks Ged,

great info - I was looking for the factory image for JB 4.2.0 to get the bootloader image out of, but that version of JB isn't on the factory page :(

my theory being if I re-flash the same version it might fix the bootloader?? But it being locked it would need the exact same version?

perhaps if you could mail me the .img file I could try it? I can pm you my address??

cheers!
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Give me half an hour or so, and I'll upload it to my dropbox and I'll post a link. Gotta get it of my laptop first:).

Although I'm not convinced it will solve your problem... but I suppose you have nothing to loose by trying.

Rgrds,

Ged.

---------- Post added at 12:53 PM ---------- Previous post was at 12:21 PM ----------

OK... here is the bootloader .img file - v4.13... extracted from nakasi-jp40d-factory-6ac58a1a.tar... or in English, Jellybean 4.2.1.

https://dl.dropboxusercontent.com/u/37483979/bootloader-grouper-4.13.img

File size: 2.05 MiB (2,146,892 bytes)
MD5: a119629c89ad06c7e49bebd260df9cf3
SHA-1: fd60a0d9da5c814e2c1ee049f537700cbbe2c3cc

Flash as follows....

fastboot flash bootloader bootloader-grouper-4.13.img

---------------

Be careful with this.

Flashing a bootloader is the riskiest single operation you can undertake on the Nexus 7.

All it takes is one false step, and you have a hardbrick.

The device will never boot again.

Make sure you have good USB connections at both ends... and before flashing... type...

fastboot devices

If you don't see a serial number, you have either a driver problem OR a possible dodgy USB connection.

Do not proceed with this flash until you see a serial number.

Normally, I would suggest test flashing something innocuous first, like a recovery, for example.... but since your bootloader is locked, that's not possible.

I'm not even sure flashing a bootloader is possible with a locked bootloader... but then, I've never directly flashed a bootloader before.

Very best of luck - really hope this fixes your problem.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] Ricey_uk:
Many thanks Ged,

tried it to no avail - still getting the 'Bootloader is locked'

It won't even re-flash the existing :(

I checked all the cables and used a different USB port.

thanks for your help :)

Ricey
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Damn... thought that might happen... but wasn't 100% sure.

You can't use fastboot with a locked bootloader, even to flash a bootloader... and you can't unlock it because - well, who the hell knows why (but I suspect a problem with the internal EMMC).

What is the precise current status of your Nexus 7?

Android version?

Rooted?

Stock or Custom ROM/kernel?

Custom recovery (CWM/TWRP) installed?

Did you receive any OTA notifications regarding the recent release of Android 4.3? and if so did you allow the OTA update to proceed? What happened?

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] Ricey_uk:
I know! I'm stuck in a loop!

I don't know the exact Android version, but it's fairly new and the owner hasn't updated it as far as I know.

Apart from that, completely stock and unrooted!

The last thing to happen was that it was left for a while to go flat (battery) then when re-started it got stuck at the Google logo and no further.

All I can get apart from the Google logo is the recovery with the andoid on his back with his tummy open ;)

cheers
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
You can get the Android version info by going to SETTINGS>>ABOUT TABLET.

Without further details, what is odd about your predicament is this...

If your bootloader is v4.13, then that means the device hasn't been updated since November of last year. Since then, there have been, I think, 3 official updates from Google... the most recent being JellyBean 4.3 about a couple of weeks ago

Normally, when an OTA update is pending, you get pestered endlessly with an endless stream of notifications:(.

Upon the user accepting the lastest update (whatever that might be - but is currently JellyBean 4.3)... the device downloads the OTA, runs a checksum test on the current files in /system... and then'patches' them, meaning it brings them up to date.

The very last thing the OTA does is update the bootloader, by dropping BOOTLOADER.RAW into the USP(staging) partition. Upon automatic reboot, the new bootloader is then copied (from the USP/staging partition) into the bootloader partition proper... thus obviating the risks associated with flashing the bootloader partition directly.

Since November, the bootloader has been updated by this means twice... 4.13->4.18 (in, I think February, when JellyBean 4.22 was rolled out) and just recently 4.18->4.23 when JellyBean 4.3 was rolled out.

It's odd you haven't received any notifications of any OTA updates.

----------------------------------

Anyway....

A possible workaround...

A slightly rhetorical question... why do you want to unlock the bootloader anyway?

I assume it's because you want to root... or maybe flash a custom ROM...

That 'might' still be possible...if you're running a version of Android THAT ISN'T JellyBean 4.3, you can root via 'exploit'.

Details here -

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

This requires no fastboot commands and thus, no need for an unlocked bootloader.

It's really simple to implement. Indeed, I ran my Nexus 7 for several month BOOTLOADER locked, but rooted.

(But with the advent of JellyBean 4.3, root exploits no longer work.... so I've had to root the old fashioned way).

But it might be useful to you...

Anyway... once you are rooted, you can then flash a Custom Recovery... like CWM or TWRP.

Normally this would be done via fastboot. But there are two great apps available that will 'write' a recovery partition... directly from the Nexus 7.

These are

Flash Image GUI

and

Flashify

.

Both will request root access.

It doesn't matter which one you use, as they essentially do the same job... but IMHO, Flashify is the better of the two.

Once you have a Custom Recovery installed, the metaphorical gateway is open to whatever Custom ROMs or Custom Kernels you like.

----------------------------------

It's possible none of the above will work... maybe for the same reason why you can't unlock the bootloader. A suspected fault with the internal EMMC chip.

But it just might... and it's gotta be worth a shot:):):).

To summarize

Root via 'exploit'

Use Flashify or Flash Image GUI to install a Custom Recovery

Good luck.

Rgrds,

Ged.
[Android Q&A, Help & Troubleshooting] TheMrcool212:
Hi guys, i'm new to Android development. I built Paranoid Android from source for TF101. The ROM was nice and i'm happy with my ROM. So now i'm so curious about what developers do regarding building a ROM and updating it.

1. If the ROM had bugs/problems, how can i analyze it and find the root cause of the bug?

2. How can i fix the bug? Do i need to edit a file in the ROM?

3. Every ROM that had updated build from source has an changelog, how can i know what is the changelog?

I'm sorry if the questions are quite noobish. I'm new with it. Thanks
[MDA, XDA, 1010 Software Upgrading] Lowlife:
I have an XDA1 with 3.17.03 ENG

1.) I have downloaded the latest XDA Tools.

2.) I have run OSImage Tool and copied the 'current rom' to my PC hard disk.(Backup)

3.) I have visited Lumpistefans ROMkitchen and prepared a WM2003 ROM based on 4.01.16 ENG and downloaded the nb1 zip file.

What do I do now?

Do I simply used OSImage to copy the downloaded WM2003 rom to the 'current rom' location on my XDA. Have I missed anything out.

Help really appreciated.
[MDA, XDA, 1010 Software Upgrading] CDTV:
...wierd, I guess it's changed to only the 2 together...
[MDA, XDA, 1010 Software Upgrading] Lowlife:
Hmm cryptic! -

Like I said "help" would be appreciated

Thanks
[MDA, XDA, 1010 Software Upgrading] Seraphic:
If you download the EXE version when you build the rom in the kitchen, all you have to do is make sure your XDA is connected to your PC and simply run the installer and everything is done automatically.
[MDA, XDA, 1010 Software Upgrading] Biso007:
the answer is yes ... it might give you a communication error ... in that case you will have to use the SD card method.
[MDA, XDA, 1010 Software Upgrading] Lowlife:
Got it working!

Thanks XDA developers - Fantastic work.
[Android Q&A, Help & Troubleshooting] shady2137:
As i can't afford a class 4 or 6 sd card and my phone have

system memory

Internel memory

externel sd

So if i use the swap in internel sd will it effect anything ?

2.what if i use a swap partition in ext sd (class 2) am i good or still not ?

Thanx
[HTC Desire X] NigelDX:
Hey guys,

Is there a full sense rom coming ?? Just for ics or jb because i really like full sense way better then aokp aosp or sense lite or ubuntu.. so does anyone knows if there is a full sense rom comin to desire x ? And i really like to see when the base is htc one s or one x.

Thnx
[HTC Desire X] Matyt:
There's mySENSE by ckpv5, you can find it in the android developement section.

It's still ICS based though, but I think that there will be a new release, JB based, soon.
[HTC Desire X] GXInfinity:
No JB full sense as of now!
[One (M7) Q&A, Help & Troubleshooting] BLOOD_ANGEL:
Hello devs

Is it possibly to Port Sense 4.1 to the HTC One ?

Sense 5 is Not my... Older Sense versions better ....
[One (M7) Q&A, Help & Troubleshooting] jonny68:
Can't understand why you think a previous version of sense is better, sense 5 is very good and HTC have finally gotten it right.
[One (M7) Q&A, Help & Troubleshooting] Zheiko:
Thats a matter of opinions dude... not everyone likes it
[One (M7) Q&A, Help & Troubleshooting] Riyal:
It's about personal preferences. And

+1 for the OP for this :D I like sense 4.5 too.
[One (M7) Q&A, Help & Troubleshooting] BLOOD_ANGEL:
Yeah or Sense 4.1 ...

Blinkfeed is not so mine ^^

i wait for cyanogenmod which works complete^^

or a sense 4.1 JB 4.2.2^^

I like sene ^^ i miss my ring lockscreen^^
[Networking] HIGKILLER:
Hey i have http://xdaforums.com/show...250691&page=16 this rom For Arc s, but i have a lille problem, the wi-fi aint working, and i have lockedbootloader, can anyone help? :s
[Android Q&A, Help & Troubleshooting] arjiegodz:
Im running jellybean 4.2.2 and i used stock calendar and google calendar and they wont alarm when i make any appointment.. and there is no notification of the event. i also tried to use many calendar app from playstore but they also wont alarm... can any1 help me about this?

ps: i tried to use calendar snooze and it alarm any event i used but i want to use only my calendar and no 3rd party app.
[Android Q&A, Help & Troubleshooting] akshay.mehta9:
Try to check alarm volume in setting>sound/profile

Or download a audio manager app
[Sprint Samsung Galaxy S III] bulkierbear:
[Q] Is it possible to get Crt animation with a custom TW rom (M.O.A.R) on the gs3
[Sprint Samsung Galaxy S III] LuigiBull23:
Here you go. It may npt work perfectly though.

http://xdaforums.com/showthread.php?t=1725361
[Sprint Samsung Galaxy S III] jazz995756:
Its in an upcoming update of M.O.A.R check the thread
[Sprint Samsung Galaxy S III] CNexus:
Crt animation?
[Sprint Samsung Galaxy S III] bulkierbear:
Thanks I'll try it out
[Sprint Samsung Galaxy S III] CNexus:
Lol, I was asking a question

What's a CRT animation?

EDIT: Nvm, found it. For anyone else that doesnt know (or knew what it was but didnt know what it was called like me), theres a video in this thread:

http://xdaforums.com/showthread.php?t=1834637
[Sprint Samsung Galaxy S III] bulkierbear:
Lol sorry been working all day misunderstood I love the Crt animation I can't wait till m.o.a.r updates
[Sony Xperia P, U, Sola, Go] Levered:
this mod i have shared from [MENTION=4803788]gagan.u20[/MENTION] and [MENTION=4388232]ZeroInfinity[/MENTION]

this mod from xperia tablet z...

HOW TO INSTALL:

1) FIRST OF ALL ADD THIS LINE AT THE BOTTOM OF YOUR BUILD.PROP!!

2) Download and put it on your SD card.

3) Reboot in recovery

4) Flash this mod.

5) Wipe cache and dalvik cache and reboot your device.

STEPS TO COMPLETELY ENABLE xLOUD and ClearPhase:

A. IF YOU WANT TO LISTEN MUSIC IN PHONE'S EXTERNAL SPEAKER:

1. Stop playing music on Walkman (or any other player that is using SoundEnhancement as default equalizer).

2. Goto settings->Music effects->Select Music FX.

3. Now open walkman and play any song and you can hear sound difference with xLoud and ClearPhase.

B. IF YOU WANT TO LISTEN MUSIC IN HEADPHONES:

1. Stop playing music on Walkman (or any other player that is using SoundEnhancement as default equalizer).

2. Goto settings->Music effects->Select SoundEnhancement.

3. Now open walkman and play any song and you can hear sound difference in headphones.

Screenshot

Take screenshot from Unofficial JB Xperia Sola

REQUIREMENT

Credit

gagan.u20

ZeroInfinity
[Sony Xperia P, U, Sola, Go] Mtakween:
Are u sure no bugs
[Sony Xperia P, U, Sola, Go] Levered:
Maybe have some..can you test?
[Sony Xperia P, U, Sola, Go] Mtakween:
yes and this may fix my walkman port xloud problem;)
[Sony Xperia P, U, Sola, Go] Xperia_Fans:
Hopefully this is no bug and I'll test it tomorrow cause since many sound mod got some bug...
[Sony Xperia P, U, Sola, Go] Mtakween:
yes no bugs:D:D:D:victory::victory:
[Sony Xperia P, U, Sola, Go] LilBlinx:
It works, but it doesn't produce the same volume level and clarity as the stock
[Sony Xperia P, U, Sola, Go] Mtakween:
untick sforce and u will get a loud sound
[Sony Xperia P, U, Sola, Go] sadiq23:
There isn't SForce! I mean we get

Sound Enhancements

Nd

Music FX
[Sony Xperia P, U, Sola, Go] Mtakween:
oh first u should be in jb or installed v/z walkman with sound mods(my port) then install this

u will get s-force when go to sound enhancement in walkman

hope i helped if yes plz press thnx :D:p:good::fingers-crossed:
[Sony Xperia P, U, Sola, Go] Kanzhelier:
not work for my xu, it doesnt show anything.
[Sony Xperia P, U, Sola, Go] aybykut3:
not work on xperia sola ics

On my X sola( ICS) it not work.

Music FX-- FC

SoundEnhancement.---FC

S-Force Front 3D Surround Sound--- have not in setting!
[Sony Xperia P, U, Sola, Go] andhikafajarms:
Same things happen to me too, but I'm using XU with stock ICS .89
[Sony Xperia P, U, Sola, Go] Mtakween:
First install my xperia z walkman then this for all stock ics users:cowboy:
[Sony Xperia P, U, Sola, Go] aybykut3:
Ready?
[Sony Xperia P, U, Sola, Go] StinkyToilet:
What do u mean "it doesn't show anything"? Just open settings > music effects > select sound enhancements
[Sony Xperia P, U, Sola, Go] Mtakween:
after that u will find option called S-force sound bla bla bla
[Galaxy 3 Q&A, Help & Troubleshooting] Mohit12:
My phone is spoilt, and it fails to detect the sim card sometimes because of which I have to re insert a few times a day. The problem is that the phone reboots every time I re insert the sim card, so I was wondering if there's any way to disable that.
[Galaxy 3 Q&A, Help & Troubleshooting] sad96:
Wrong section. Go to Q&A
[Galaxy 3 Q&A, Help & Troubleshooting] amarendar94:
This trick only works in cm7.

1. Long press power key.

2. Choose turn aeroplane mode on.

3. Remove simcard, insert it again.

4. Turn aeroplane mode off.

5. Wait for few seconds.

6.if ur carrier does not get detected, go to mobile operators in wireless an network settings and search for available network and choose yours.

7. Done
[Galaxy 3 Q&A, Help & Troubleshooting] Mohit12:
Can't use cm7 unfortunately.

Can't be done some other way?
[Galaxy S III Mini Q&A, Help & Troubleshooting] Knux14:
Hello guys,

I installed the maclaw's unofficial Cyanogen 10.1 to my S3 mini and it works fine, but i tried to flash the GApps and it failed. It cancelled the flash before installing and nothing happened. Then, i went into Rom Manager and i found "Google Apps" in the rom avaliable, i installed the first for CM 10.1.X and now, i have everything but i cant use Playstore (It keeps crashing) and i cant do anything because the message "Unfortunately, Google Play Store has stopped." is flooding. It's really annoying and nothing it's working

Hopefully someone will help me :/

PS: When i am on a sms (Using GO Sms) the error "Unfortunately, Android keyboard (AOSP) has stopped" but i'm using Swiftkey ...
[Galaxy S III Mini Q&A, Help & Troubleshooting] tys0n:
Whatever it is you're running it must be anything but CM10.1. You might have flashed the wrong gapps package.
[Galaxy S III Mini Q&A, Help & Troubleshooting] Knux14:
Here's what i've got under "About phone"

http: //image.noelshack .com/fichiers/2013/20/1368980256-screenshot-2013-05-19-18-09-02.png

And the rom that i've installed is the first one on this screen:

http: //image.noelshack .com/fichiers/2013/20/1368980310-screenshot-2013-05-19-18-11-06.png
[Galaxy S III Mini Q&A, Help & Troubleshooting] tys0n:
Yeah, thats CM10
[Galaxy S III Mini Q&A, Help & Troubleshooting] Knux14:
So i need to wipe everything and then flash the second Gapps ?

ll

==> That's what i'm doing right now.
[Galaxy S III Mini Q&A, Help & Troubleshooting] bihslk:
Download gapps for 4.1.2 cm 10 reflash and wipe cache/dalvik
[Galaxy S III Mini Q&A, Help & Troubleshooting] Knux14:
That worked ! Thanks man but i reinstalled my backup because Youtube is not compatible yet :/
[Xperia Arc Q&A, Help & Troubleshooting] HIGKILLER:
Hey i have http://xdaforums.com/show...250691&page=16 this rom For Arc s, but i have a lille problem, the wi-fi aint working, and i have lockedbootloader, can anyone help? :s
[Xperia Arc Q&A, Help & Troubleshooting] HIGKILLER:
simple, i needed 10 posts to post on the FORUM i need help, so i started posting, after 5 posts i posted on games, so yeah
[Xperia Arc Q&A, Help & Troubleshooting] mike_disturbed:
Wow..just..wow..

Should i even report this..

Or bump this thread so that the mod read this?

-----------------------------------

(҂`☐´)︻╦̵̵̿╤── .:System:.

-----------------------------------
[Xperia Arc Q&A, Help & Troubleshooting] HIGKILLER:
i asked for help on the good places and some games i took i just commented dafuq, i really needed to solve my phone problem, god -.-
[Xperia Arc Q&A, Help & Troubleshooting] mike_disturbed:
So you just spam everywhere...

So that you could post a useless post in dev section?

-----------------------------------

(҂`☐´)︻╦̵̵̿╤── .:System:.

-----------------------------------
[Xperia Arc Q&A, Help & Troubleshooting] Sahaab:
U cud hv pm'd the dev of the rom
[Xperia Arc Q&A, Help & Troubleshooting] tangosierra_:
Page not found
[Windows Mobile Development and Hacking General] pena_leve:
If someone can help me out, great.

I'm looking for the app above Guess the newest version is 2.26 ou 2.25.... The XDA sellers at portugal have a small app, an old one, marked as shareware. Well, i went to V2R home page, and nothing. Have search trough software houses, nothing again.

So, can someone help me out? Was interested on this cause, want to use their newst app Sync4Outlook, and they say :? we do need it.

Thx
[Windows Mobile Development and Hacking General] CDTV:
...try handango.com for Caller2Picture...