yashsingh1/xdaforums huggingface dataset:
[One (M7) General] Lidodido:
The S4 has better quality, but none of them are any good. Audio quality is a lot worse on the S4 though, as we already know.

From what I've seen and read, HTC One has a camera with worse image quality in terms of best possible image quality, but the camera is more useful since it can be used in any conditions (dark and noisy environments and better wide angle). I love it because no matter what situation I know the camera is usable. Right now mine is on repair due to a cracked glass and I'm using an Xperia P which has a good camera, but unless I turn all the lights on and back away all across the room I know I won't be able to get usable pictures. It's not even near the HTC One. And where any phone I've tried has produced inaudible sound the HTC One has been absolutely clear.

To be honest, that's just what I want from a mobile phone. The whole point with a mobile camera is that I always carry it so it's available in ANY situation. If it can't handle dim light or loud noise or narrow rooms it's completely useless. The quality is good enough for facebook and instagram and stuff so I don't care about that, as long as it's usable whenever I feel the need to use it.
[One (M7) General] cpufrost:
Sound quality: The S4 is rather atrocious. Its AGC is way too heavy, some users may find this better for "getting in" the details but this is not how our hearing works naturally. For music and faithful reproduction it's quite bad. Actually it's awful. For recording a crowd where you want to hear everyone's comments, etc, it would actually be desirable. Again different tools for the job. The HTC easily wins on audio here.

Video it's a tossup. There are color artifacts present in the One's video and color itself is difficult to reproduce. The flames almost appear "electrical" in nature. There is less apparent camera shake with the HTC One. The S4's video looks better with its reproduction of the flames, less blooming and glares. The fire is very hot and has copious amounts infrared radiation. Most sensors will show a pinkish color to longer IR energy and this must be effectively filtered to reduce its affect on sensor output processing and clipping. It's a delicate balance here but the S4 seems to do a better job. Its smaller pixels probably help as well.

As far as SQ goes the processing appears to be globally applied as the similar use of AGC and frequency response is realized in voice recording applications on both devices as well. The recorded volume appears much lower on the HTC because little compression is used. This would be preferred for recording live events where dynamic range needs to be preferred. With voice users may desire to use post processing on a PC to add gain (RMS normalize, etc.).

Personally I prefer the sound of the HTC.

And as far as stills go the HTC is the better *shooter*. I put emphasis on shooting as you can capture good shots of things that happen in real life. There is little shutter lag and pictures turn out decent. The S4 is a very good camera but using both I find it easier to catch the action of life as it happens with the HTC. Too often pictures turn out blurry or out of frame on the S4, it's too slow. When taking pictures of scenery during the day, however, the S4 camera is spectacular!

Remember the best camera is the one you have within your reach!

The best of both worlds would be a higher MP camera in the S4 with the responsiveness of the One. Surely it will happen in the not so distant future. Look how P&S cameras have evolved.
[One (M7) General] dvsk69:
LoL isnt this thread closed yet??
[Galaxy Tab 2 Themes and Apps] Deleted member 5266660:
6. Do not post warez.

If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit any member to request, promote or describe ways in which Warez, cracks, serial codes or other means of avoiding payment, can be obtained. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community
[Galaxy Tab 2 Themes and Apps] dynospectrum:
You need to buy it...
[Galaxy Tab 2 Themes and Apps] InFiD3ViL:
Well since you already have the link, click where it says "Purchase"

Easy Peasy! Now you own the Game of Life legally.

*hint* XDA does not condone, endorse, or tolerate theft of paid apps. Please support your devs and acquire paid apps the right way....just a tip so you don't get banned from XDA.
[Galaxy Tab 2 Themes and Apps] Clark Joseph Kent:
OP see my edits on your post....Thread Closed.
[RAZR i Q&A, Help & Troubleshooting] AyanamiRei:
I'am with Pi-llama 1.3, and i need to know who is more better, if is Pi-llama or Moto JB...And what more better AOSP or MOD? Can give me the links for they ?
[RAZR i Q&A, Help & Troubleshooting] metalmoot:
What do you want ? Tweaked ROM, performance, battery smooth ?

Sent From My Beaned Razr I
[RAZR i Q&A, Help & Troubleshooting] adddaamo:
Pilama is fastest for me. On Omar my battery last longer (but performance degradation is very visible for me). Stock is in the middle.
[Nexus 7 (2013) General] jporter396:
Hopefully this helps people in my situation.

So on the first day of having my nexus 7 i found a way to have no OS and 0MB internal storage showing in TWRP. Yah i suck.

I tried tons of things but knew a system image was needed.

HOW: I was about to flash the superuser root for 4.3 newly released and forgot to put it on nexus so i then proceeded to exit TWRP, however upon exiting TWRP the recovery detected i havent installed supersu and asked do i want to install superuser? I though why the hell not!

I confirmed to install superuser and then tried to reboot but for 20 minutes device could not boot. TWRP showed 0MB internal storage and pushing adb files in this state yielded nothing as there was no directory

This is how i managed to have a working tablet again

1. FORMAT DATA in TWRP - after doing this your internal storage should be back and not show 0MB

2. reboot to the bootloader

3. On your computer download this file kindly given to us by phuduong and uploaded by Nburnes

https://mega.co.nz/#!PBIiEbBJ!bKpdHxegOVlde12nsu_ulEyRq7UsANLLQab1IZjLIGc

Credit to Nburnes http://xdaforums.com/member.php?u=2918596[/QUOTE]

4. Once downloaded move that system.img file to your adb directory

5. With you nexus 7 in the bootloader, adb open, and file downloaded copy and paste this command into adb terminal

fastboot flash system system.img

6. Now you have an OS but it still would loop and wouldnt start

7. Boot into recovery and Format Data again, because for me 0MB interal storage was back again

8. Then Factory Reset

FINALLY YOUR DEVICE SHOULD BE BACK TO ITS ORIGINAL STATE!!!!!
[Nexus 7 (2013) General] plbelanger:
Is that the factory image? Have you tried going from unlocked bootloader & rooted back to factory using that image?
[Nexus 7 (2013) General] phonic:
Google has yet to release the official factory image for the new N7. However, a kind user was gracious enough to make their own. It is likely to be almost identical to what Google will eventually release and should work the same way.
[Nexus 7 (2013) General] Admiralcurtis:
Thank you! Thank you!
[Nexus 7 (2013) General] dadoc04:
good stuff OP. glad you got it working again
[Nexus 7 (2013) General] erikjonpeterson:
You all are life savers! 1000X Thanks!
[Nexus 7 (2013) General] petersellers:
I tried running through this, but it didn't work for me. I think my situation is different though because I tried to install a factory image for the 2012 nexus, and during part of that process I ran the "flash-all" script which starts by deleting boot, cache, recovery, userdata, and system.

I think deleting boot screwed me up, because even though I can go into recovery now after reinstalling twrp and I can restore my system using system.img, I still can't boot (get stuck on the google logo). Any way to fix that?
[Nexus 7 (2013) General] jporter396:
So you first tried to restore from the OLD Nexus 7 Image?????
[Nexus 7 (2013) General] jporter396:
So you first tried to restore the OLD nexus 7 factory image? Probably gonna have to wait for factory image or exchange yours
[Nexus 7 (2013) General] petersellers:
Yes, I tried to restore from the old image. Obviously fastboot wont let you install the old image, but I didn't realize that until boot, system, cache, etc. were deleted :(
[Nexus 7 (2013) General] BoomBucks:
THANK YOU!!!

This worked perfectly! I had a wiped system folder (no ROM), and obviously no USB debugging enabled. And with the lack of a factory image, I've been counting seconds to seeing somebody post this!

Just follow the instructions carefully. Thank you guys! :)
[Nexus 7 (2013) General] phuduong:
You can flash old and new image through fastboot. I did 2 times ^_^

This is boot.img for who need

BOOT.IMG HERE
[Nexus 7 (2013) General] jarjar124:
It gives me a fail when I try to wipe data.

Edit: never mind
[Nexus 7 (2013) General] Balsta:
How did you fix it? I still cant wipe data.
[Nexus 7 (2013) General] jporter396:
Have you formatted first?
[Nexus 7 (2013) General] Balsta:
I can't, get an error with that too
[Nexus 7 (2013) General] dynamicpda:
OP and nburnes saved my butt!
[Nexus 7 (2013) General] dexgen:
I did this and now it seems my device is booting and it shows up as N7 when I attach it to my PC. But the display shows nothing at all. It just goes blank after the Google screen. Any ideas?

After flashing everything I could think of and banging my head and the device against the wall for two hours, I finally got it to work. Not sure how exactly but the last thing I did was reflashing bootloader. So if anyone has the same problem, try that.
[Nexus 7 (2013) General] kdkinc:
Thank you.

Note:

Give step 6 a little time be patient.:p
[Nexus 7 (2013) General] Nburnes:
All main JSS15J .IMGS here: http://xdaforums.com/showthread.php?t=2381438

Glad this helped some of you guys!
[Nexus 7 (2013) General] varpness:
Yes!!! This worked for me as well! Thank you so much, man!
[Nexus 7 (2013) General] mattspfld:
Thanks so much. Worked perfectly.
[Nexus 7 (2013) General] dexgen:
Question to people who followed this technique:

Do you notice something funny about the file system?

More specifically, I installed dropbox and noticed that when I try to download files from it, I get the no storage available error. I'm pretty sure this is a permissions issue. If anyone can install dropbox and tell me if they have the same problem I'd be thankful.

I'm also rooted, I should add.
[Nexus 7 (2013) General] Krunk83:
I just formatted data and after that rebooted the system. It booted up fine. Didn't have to follow any of these steps except the format data first step. Just an FYI for those of you that may want to try it.
[Nexus 7 (2013) General] Mikey503:
Worked perfectly! Thanks OP and nburnes! I was freaking out for a few hours while troubleshooting haha
[Nexus 7 (2013) General] Patsfan123:
That worked for me as well.
[Nexus 7 (2013) General] wolffie:
Thank you so much. After hours of googleing to find a fix I used the right keywords to find your post. It worked great, and now my new N7 is up and running again.

Thanks!
[Nexus 7 (2013) General] rene130313:
Similar to nexus 4

Hi samting similar happen to me in my nexus 4 I was flashing 4.3 version ota using now cry tool kit version 3.6.6 and I get stuck in a bootloop terrible so take me about 7 houres making the same procedure and finally pass the signing image step what I discovered was that the bootloader cat stuck so I have to manually reseret many times until it work so I recommend using this program to fix your nexus 7 issues this program works for all nexus devices don't stress your self there's hope.
[Nexus 7 (2013) General] roustabout:
I made the OPs mistake as well. Also, I was trying to use a 1.43 version of chainfire's kit, not the 1.45.

When I first booted twrp, it couldn't mount data and so couldn't flash, but did offer to root.

On reboot, I could either

- look at the boot logo indefinitely

- force boot to fastboot via power and vol down

- force boot to twrp via power s vol up

In recovery, I had adb and system but not data, and I was prompted to enter password by twrp.

I was able to fix by doing:

- fastboot oem lock

- reboot

- fastboot oem unlock

- reboot

- power off

- power on to twrp

- install root via adb sideload
[Nexus 7 (2013) General] hodags:
Count me in for this as well.. in fact, I had flashed TWRP, went DIRECTLY into it (oops!) and on exit of TWRP accepted the install of SuperSU. From there, I was stuck at the bootloop...

After reading this, I went back into TWRP and formatted Data only (as this poster said) and then did a factory reset. Rebooted and everything came up fine - SuperSu was even already there from TRWP! Less steps and no downloading of the system.img :good: :cool:

Looks like TWRP might want to put a warning in or not suggest SuperSu when cache is messed up/password check wasn't passed :p
[Nexus 7 (2013) General] jwebb1111:
should we go ahead and flash the UPDATE SuperSU 1.43 after it does successfully boot? i know you said it already had SuperSU but didn't know if it would benefit from the newer zip

EDIT: it told me after boot and an attempted SuperSU update that i would have to go to TWRP and manually update SuperSU
[Nexus 7 (2013) General] coaustinm:
I also accepted twrp to flash SU and caused a bootloop.

I just reformatted data and did a factory reset and everything works fine.
[Nexus 7 (2013) General] jwebb1111:
no update message regarding SuperSU?
[Nexus 7 (2013) General] coaustinm:
I did get a message saying I needed to update it but after I did, I didn't get root access. So I rebooted into twrp and flashed the SU 1.43 zip file. I now have root with no problems
[Nexus 7 (2013) General] jwebb1111:
after i updated it said i didn't have the binary and asked me to install it via the app or TWRP. i selected the app first and it froze so i rebooted to recovery>cleared caches>rebooted to system>opened app>selected binaries via TWRP and it did it's thing. rebooted now with root access and all is well.

as far as the OPs first post, i too found that only a format data and factory reset were necessary. the device then rebooted and i went through the situation above ^
[Nexus 7 (2013) General] Landara:
Exactly the same thing happened to me,and the same results, went to TWRP then as I exited TWRP says "Hey brotha why you ain't rooted up in this mofo?" to which I said "..." then it said "Want me to root a mutha?" and I said yes, softbrick. This thread saved my device, thanks much!
[Nexus 7 (2013) General] FormeriPhoney:
Where exactly is factory reset in Bootloader mode or TWRP?
[Nexus 7 (2013) General] corythug:
Twrp
[Nexus 7 (2013) General] iutri:
Same story for me as others. I followed OP's instructions to the t and they worked. The only weird thing is now the Amazon Mobile app is now incompatible with my device from the google play store. This certainly was not the case originally. Anyone run into this?
[Nexus 7 (2013) General] TheAltruistic:
+1 to this. I'm a fool. Dang it. DANG YOU TWRP! The cake is a lie.
[Nexus 7 (2013) General] drpfenderson:
I have the worst issue out of this. Booted up to TWRP, asked for password, wouldn't work with my password, forced reboot...now dead. Nothing. Won't reboot, startup, nothing. Totally black screen, no button response. What. The. Hell. I've done this a million times, how could it be this messed up? Any ideas to jumpstart me back into fastboot?

EDIT: I'm a dingus. I just waited a couple more minutes and tried again. DING. Works.
[Nexus 7 (2013) General] jab1472:
Okay I need help please. After following the root instructions and semi- bricking it my fault. Then following this post instructions I have my system image back but when I reboot system Google screen appears then the screen goes blank no boot logo nothing few seconds go by it goes completely black then light blank again. I can still boot into recovery and boot loader. I followed all the instructions to the T installing system image data format and factory reset and this is where it landed me. Any help will be greatly appreciated.
[Nexus 7 (2013) General] phazerorg:
This happened to me as well, and although it was easily fixed I'm still wondering what the actual cause of this is. I've read this thread and some others on the topic, but they talk about fixing it and not what caused it.

I've owned two other Nexus devices (Nexus One and Galaxy Nexus), and the procedure is always the same... unlock bootloader, flash (or at least boot) custom recovery with fastboot, flash Superuser/SuperSU using the custom recovery. That's all I did this time... I used TWRP and didn't let it flash SuperSU, I did it myself... and I used no toolkits or anything else. Same way I've been rooting and flashing Nexus devices for years... except this time I ended up with an unbootable system.

So besides having some help available to people who get into this situation, do we know what actually caused it so people can avoid it in the first place? Was it an issue with TWRP? (maybe it doesn't happen with CWM?) Is it SuperSU? (I tried two different versions) Something to do with booting up once after unlocking? (if so, what and why?) Why hasn't this been a problem with other Nexus devices (at least for me)?

I've seen several threads on the topic and couldn't see a clear answer, but feel free to tell me to search better and point me to an appropriate thread if I missed something.
[Nexus 7 (2013) General] brandogg:
I had the same issue (adb did not see my Nexus 7 after flashing TWRP, so I chose to reboot and it asked me to install SU, so I said yes, then it goot stuck at X logo)...anyway, I'm with the crowd that only had to format data. At first that didn't work (still stuck at the X), but it did show 26600 available storage for /system/, so I just swiped to wipe data/factory reset again and it worked, no need to flash anything with fastboot...back to rooting now.

But thank for you this, and thank you for the users that only formatted and had success, add me to the list.
[Nexus 7 (2013) General] bailyc:
I too am curious to know why this happened. For what it's worth, I flashed CWM recovery and not TWRP, and used SuperSU for root. I then was unable to boot past the Google X logo. Using the instructions on this thread to a T with TWRP, I finally got it fixed. (Thanks OP, by the way!)

Interestingly, I have two new Nexus 7's. The first one had no issue, but I used it stock for several days, then flashed CWM recovery, then rooted a few days later. Shouldn't make a difference, but the second device is the one I had issues with and I did everything at once, before I even booted into the OS for the first time.
[Nexus 7 (2013) General] FoulOwl:
TWRP to OUDHS

Good day,

I also started having the 0mb problem today. What I am interested in is swapping the TWRP to OUDHS (http://xdaforums.com/showthread.php?t=2386112).

My question is - do I just simply

fastboot flash recovery oudhs.img

in fastboot over the TWRP?

Thanks to everyone!
[Nexus 7 (2013) General] mattlgroff:
Yup :thumbup:
[Nexus 7 (2013) General] Jashafi:
Didn't have to flash system image

Thanks for help. Was ready to flash sys image until I read a post saying you don't need to flash just format. Well that is exactly what I just did and it worked, back in android and rooted.:D

If it doesn't work for you just flash sys image its pretty easy.
[Nexus 7 (2013) General] rackerhacker:
This post just saved my rear. Many thanks.
[Nexus 7 (2013) General] garytako:
i got exactly the same problem as you, everything goes find, flash rom and reboot, but only google screen come up and then show nothing.

is it you flash the boot.img to the device to get it done?
[Nexus 7 (2013) General] tryest:
0MB Internal Storage

tried it all still 0MB Internal Storage so I called Goggle; they are send me a new one. I see the /data partition (using df) but acts like its not mounting. I am limited because its not rooted and busybox not installed. :eek::cyclops:

if anyone cant figure this one out let me know. thanks
[Nexus 7 (2013) General] drms12:
Try this fastboot command

fastboot -w

It should erase all of the user data partitions and creates new ones instead. It should fix your problem.
[Nexus 7 (2013) General] NienorGT:
It worked!

I don't know how the hell I soft-bricked my Nexus but dawn I was happy to get that so easy solution!
[Nexus 7 (2013) General] synplex:
Thx

OP Thank you! :highfive:

This has saved my ass twice! with 2 different nexus 7s :laugh::victory:

Again thx! :good:
[Nexus 7 (2013) General] WeRSpecialPeople:
Hopefully won't have to do this again. Thank you very much though for sharing. :good:
[Nexus 7 (2013) General] FormeriPhoney:
Me 2.
[Nexus 7 (2013) General] paulrileysullivan:
I'm experiencing the same issue, were you able to find a fix?
[Nexus 7 (2013) General] liam.lah:
Thanks. I was having this issue, then wiped data as you recommended. I didn't do the factory image however, as I intended to install CM10.2 So heads up to anyone with that intention, wiping data should be all you need before attempting to flash CM.
[Nexus 7 (2013) General] slatesekx:
I think my situation is different though because I tried to install a factory image for the 2012 nexu
[Nexus 7 (2013) General] mick_soul:
It worked :good:

Thank you!! :D
[Nexus 7 (2013) General] crypticc:
just first two steps worked for me:

"fastboot -w" in fastboot bootloader; which recreated /data

then "wipe", "data" in TWRP which recreated /sdcard /cache etc

thanks OP
[Nexus 7 (2013) General] MadMic:
Tried the OP - no joy - read about this and gave it a try - all good and you're a legend!

What a dumb-ass issue this is - way to easy to soft-brick :(
[Nexus 7 (2013) General] mtfrimp:
system.img for mobile model ?!

I got a big problem, I have the nexus 7 (mobile) and flashed the system.img for the wifi model! Now cellular doesn't work and my nexus doesn't even ask for sim card! Could someone give me a link for the mobile model? I only found stock rom for wifi model and not mobile model...
[Nexus 7 (2013) General] Gertlily:
Sorry mate,

The software for the LTE (Wireless) version of the Nexus 7 (2013) hasn't been released yet by Google. And as I thought it was also not for sale already..?

Bye,
[Nexus 7 (2013) General] mtfrimp:
Of course it's released how should I otherwise got it? It's available in Germany since 28th of august. I hope Google will release the system.img soon!
[Nexus 7 (2013) General] Gertlily:
Oh yes it was released by Mediamarkt Germany. But not in US itself.. So Mediamarkt was bit to early with release. Haha. I think it will max take a week before release of the system.img..

Bye,
[Nexus 7 (2013) General] jchubbs:
1st Step

I probably sound like an idiot :confused: but I'm confused about step 1, when it says format data in twrp. Can you tell me exactly how I'm supposed to do that? Currently my nexus 7 is on the booting screen with the nexus logo. Thanks!
[Nexus 7 (2013) General] silvan g:
you will need to have TWRP Custom recovery installed ;)
[Nexus 7 (2013) General] afremont:
Try fastboot -w when the bootloader is on the screen. Of course this will wipe any user data you have.
[Nexus 7 (2013) General] mm@rks:
I did the same thing.. how do you do a factory reset when you can't start the system? I can't find it in twrp.

EDIT: never mind I didn't realize that there where more than 3 pages in this thread.. factory reset from twrp did the trick for me! I love the OP!
[Nexus 7 (2013) General] LoVeRice:
You can fix all these with nexus toolkit, it even downloads all the necesary file
[Nexus 7 (2013) General] Ivan93tm:
will this work on LTE version ? i think no, but is better ask and don't make mistakes XD thanks in advance =)