yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] bmckenna:
Resized pictures are basically worthless as any manipulation done to a picture has the potential to alter the header/footer info during the decompression/recompression process for the JPEGs (as I understand it). I need freshly taken with stock camera app on a Gnex full size picture headers/footers just to make sure I'm not missing anything.

od -bc <imagename> | head

That command can be run in android terminal to give the header. Really I'm just interested in the first 10 octals. For my phone it is the following:

377/330/377/341/047/253/105/170/151/146

377/330/377/341/105/253/105/170/151/146

(two different files with slightly different headers, but that's easy to compensate for)

The footer can be obtained by running the same command without the piped portion...it will take longer to run as it is doing an octal dump of the entire file. Here I would need the last 3 rows (45 octal groups) as I'm trying to figure out if there is in fact some sort of pattern to the footer (so far I haven't been able to identify one that works).

My footers (from three files) -

013/105/013/074/000/000/000/053/020/120/004/253/017/214/017/053

020/120/004/253/017/214/017/074/000/000/000/001/120/001/000/074

000/000/000/000/000/000/000/000/000/000/000/000/000/000/000/000

172/035/377/044/132/046/166/016/172/035/377/044/074/000/000/000

001/120/001/000/074/000/000/000/000/000/000/000/000/000/000/000

000/000/000/000/000/000/000/000/000/000/000/000/000/000/000/000

024/030/030/032/026/031/031/034/030/033/033/036/032/035/035/040

033/036/036/042/034/040/040/043/034/042/042/044/034/042/042/044

034/042/042/044/034/042/042/044/034/042/042/044/034/042/042/044

The last one differs greatly from the first two (which have been taken post-flash)...the last one is from April and was copied from the phone to Windows as a backup from that timeframe then copied back onto the phone.

However, I'm running AOKP at this point and was not earlier (when some of the pictures were taken), and the phone has been flashed since (the headers/footers here are from post-flash, not sure if flashing would affect headers/footers or the camera app somehow) so if I can get a bit more data to see if the ROM being used/the version of Android on the Gnex has any effect on the header/footer, and whether or not the 074/000/000/001/120/001/000/074/000 pattern is a footer of sorts for other people, it might help me figure out what's going on and to figure out why the footer pattern changed from April to today.
[Samsung Galaxy Nexus] efrant:
Great work so far! I'm interested in your progress. Keep us up to date.
[Samsung Galaxy Nexus] bmckenna:
friend of mine running unrooted stock ROM gave me these -

$ od -b IMG_20110719_093821.jpg |head

0000000 377 330 377 341 210 036 105 170 151 146 000 000 115 115 000 052

0000020 000 000 000 010 000 007 001 017 000 002 000 000 000 004 110 124

0000040 103 000 001 020 000 002 000 000 000 012 000 000 000 142 001 032

0000060 000 005 000 000 000 001 000 000 000 154 001 033 000 005 000 000

0000100 000 001 000 000 000 164 001 050 000 003 000 000 000 001 000 002

0000120 000 000 002 023 000 003 000 000 000 001 000 001 000 000 207 151

0000140 000 004 000 000 000 001 000 000 000 174 000 000 001 124 116 145

0000160 170 165 163 040 117 156 145 000 000 000 000 110 000 000 000 001

0000200 000 000 000 110 000 000 000 001 000 013 210 047 000 003 000 000

0000220 000 001 000 351 000 000 220 000 000 007 000 000 000 004 060 062

$ od -b IMG_20110719_093821.jpg |tail

3377260 103 161 370 125 211 143 076 110 363 076 120 060 163 305 117 065

3377300 237 263 173 235 022 152 311 330 252 144 135 305 243 301 214 162

3377320 015 106 367 161 335 260 164 166 332 111 014 304 167 366 253 155

3377340 062 222 361 111 003 060 043 052 123 220 175 276 265 132 073 074

3377360 076 365 212 110 002 375 326 162 061 370 142 211 070 245 175 231

3377400 122 273 121 121 104 006 325 325 320 156 037 067 166 156 152 164

3377420 177 050 341 230 053 172 016 151 056 135 363 030 165 312 307 302

3377440 340 165 036 346 234 261 014 215 270 003 030 033 316 171 367 254

3377460 145 053 044 344 312 346 345 155 133 325 237 377 331

3377475

What's interesting is that I thought 337/331 was the standard footer for JPG files (at least according to scalpel's base configuration, it seemed to be)....but none of my files have this tail :/.
[Samsung Galaxy Nexus] cmstlist:
You are certainly braver than I.

I don't really know the details of how flash memory is laid out, but I seem to recall that some sort of wear levelling is typically used to prevent the same sectors from being repeatedly written and erased and wearing out with others left untouched. The structural layout of sectors may not actually match the logical layout of the file system. E.g. if you have a 20 MB Angry Birds apk file and then you upgrade it from Play Store, it might write the upgraded 25 MB apk on a less worn sector rather than rewrite it at the same spot. And the sectors containing app data aren't necessarily going to be the same all the time... they could "wander" from one region to another as a result of dynamic wear levelling.

So it's conceivable that if you had a bunch of photos sitting around for a long time, those sectors were the "least worn", and the moment the files were wiped, they became prime territory for writing new data. If the phone has booted a few times since the wipe, your photos may have been overwritten by app data, the dalvik cache, anything really.

Could the dynamic levelling lead to some scrambled files, where sectors containing deleted files are no longer interpreted as contiguous post-wipe?

And next time... use ADB over USB from CWM recovery to pull all your files before any drastic restore attempts :)
[Samsung Galaxy Nexus] bmckenna:
Your wear-leveling theory has been my fear. Most of photos were sitting on my phone since I got it (copied over from my Droid X), though some were taken 48 hours before I had my major screw-up. If it wasn't flashing the phone, it was probably the recovery process that hexamob pro did where it dumped like 20gb of jpg files onto my SD card. :/

I wasn't as savvy to adb as I am now (nor to many aspects of my phone...this whole thing, at worst, has forced me to learn a lot about the inner workings of it), and will certainly do that going forward...MTP is just utter shiat when it comes to copying files. I used to use SwiFTP and FTP into my phone to get the files to be backed up...but now that I know adb commands, I will go that route.

I've tried a few different recovery methods, but I think the next two I will try when I get some time are 377 330 377 ? ? ? 105 170 151 146 as the header (to eliminate the seemingly variable fourth through sixth octets but only pull files with EXIF data) and do a forward read with the standard jpg footer and a reverse read from 2.5, 2, 1.5, and 1 MB with the standard jpg footer. The forward read in scalpel takes the file from the header start to the first instance of the footer...the reverse read goes out the number of bytes specified and reads backward toward the header until it finds the footer...

I'm just really confused why there is what appears to be "pad data", or at least some kind of data, at the end of my JPG files. I'm wondering if some aspect of AOKP puts it there, as the head and tail of the file given to me by my buddy are from a stock ROMed phone.
[Samsung Galaxy Nexus] QuattroCS:
i have made a similar issue with my sister-in-law nexus. i have been unsuccessful at getting dd image to otg usb because the battery doesnt last long enough.i did make a my backup backup file, but that was deleted during wipe and it didnt even cross my mind to copy before such. also because i was not used to non sdcard devices, my current phone is a thunderbolt.

is there a way to get it thru adb?

i formatted my otg udb to ext3 because it didnt work on fat due to file size limitations

is mmcbl0p12 all that is needed or should the dump be the whole mmcblk0?

have you tried any of the diskinternals apps? the reader or the recovery. (the link restriction prevents me from posting links. google is your friend for this)

i also have access to other tools and i am willing to to try them, but i still need to get may hands on that dump file.

any suggestions are welcome.
[Samsung Galaxy Nexus] bmckenna:
as far as i know, no way to get the dd image through adb because there's no way to get the phone to recognize your computer as a mount point...when you run adb shell you are running the entire command on your phone so something like "adb shell dd if=/dev/block/mmcblk0p12 of=C:\temp\sdbackup.img" or even replacing C with a mount point wouldn't work since you can't mount the computer as a mount point on the phone :/.

you could also format the usb drive to ntfs and load an ntfs capable kernel (i used samurai akira's) so you can work on the .img file in windows or linux. mmcblk0p12 is i think all that is needed as it is mapped to /device/ which should contain all of the pertinent data. i haven't tried diskinternals but am coming to the realization that hexamob probably screwed me by dumping 20GB worth of 1-50mb jpg files onto the SD card (because it couldn't dump them anywhere else) and i attempted recovery that way in a panic after it first deleted :/.

if you want that dd image you're gonna have to wire your phone up for external power the way i did it, as far as i know...no other way to go about it. instructions i found were here - http://www.droidforums.net/forum/galaxy-nexus-development/209149-backup-sd-partition-using-dd.html
[Samsung Galaxy Nexus] QuattroCS:
how were you able to mount the dd image to use photorec. this is the point at which i am stuck at the moment.
[Samsung Galaxy Nexus] bmckenna:
I never mounted the dd image, just ran recovery tools on the .img file itself. There are quite a few tools you can use...I had Ubuntu installed on a second partition so I used Linux tools for the most part (since the OS natively supports ext*). Scalpel and foremost were the two I had the most success with (in terms of number of files recovered...unfortunately I didn't actually get any picture files from my DCIM folder).

Unfortunately it looks like Hexamob probably killed any recovery efforts I had by writing 20gb of junk/repeated JPG files to the partition. I'm thinking it does something along the lines of a scalpel file carve but goes 50mb out from the header and reads backward (this is an option within scalpel) as I had a ton of small (64x64 pixel size, for example) JPG files that were close to 50mb in size.

EVERYONE STAY AWAY FROM HEXAMOB! If you lose files and really want them back, immediately turn off your phone and make a dd image as described earlier in this thread...then say a prayer to any deities you've heard of that the files might still be there in the file structure.

Live and learn! :)
[Samsung Galaxy Nexus] alexonfire:
Hi, having the same problem...

accidentally flashed with fastboot -w and stopped it when I saw it that it wants to wipe userdata, but the damage was already done.

Now everything on the sdcard is gone. I created a image using dd of /dev/block/mmcblk0p12

So far I couldn't restore any images using scalpel. I also tried looking for strings that should be in the image, like ID3 tags of mp3s and also can't find any. ( strings image; cat image | grep -i bandname ).

I saw that the sdcard folder is mounted using fuse. Maybe that's the problem, we first have to use fuse to get to the file?

Have you been restored your pictures in the end?

Thanks, Alex
[Samsung Galaxy Nexus] bmckenna:
I restored some pictures but none from the camera itself, just jpg files that had been downloaded (even after modifying the header/footers that were being carved). I have a very strong suspicion that the lack of recovered images is due to hexamob recovery and the way it restored files (it looks like it did a reverse from 50mb out which created a lot of 50mb jpg files that quickly filled up the sdcard, overwriting any pictures that may have been left on there).

You shouldn't need fuse to mount the image of the file to perform recovery provided the image is a full image file.
[Galaxy S II Q&A, Help & Troubleshooting] singharun18:
I want to buy spare battery or rather a battery to replace my existing battery as it gives me max 6-7 hours backup

Plz suggest me from where should i buy battery..

M from pune,maharastra,INDIA

thanks in advance
[Galaxy S II Q&A, Help & Troubleshooting] boki9999:
You can get Samsung official 2000 Mah battery from Amazon or eBay. But you'll get a new back cover because the battery is bigger than the normal one.

Sent from my Galaxy S2 GT i9100
[Galaxy S II Q&A, Help & Troubleshooting] singharun18:
Do they ship to india?
[Galaxy S II Q&A, Help & Troubleshooting] kilometers4:
I would suggest an anker 1900mah battery. That with the stock battery would get you more than your required battery life and not need the extended back cover
[Galaxy S II Q&A, Help & Troubleshooting] dnanielsmith311:
i suggest you get the original samsung 2000 mAh battery, it comes with their custom back cover already
[Galaxy S II Q&A, Help & Troubleshooting] singharun18:
How can i get it in india?
[Galaxy S II Q&A, Help & Troubleshooting] boki9999:
Simply by ordering it online.

Sent from my Galaxy S2 GT i9100
[Galaxy S II Q&A, Help & Troubleshooting] singharun18:
Can i buy from in.mobilefun.comm???is it reputed enough
[Galaxy Tab 10.1 General] GazaIan:
I want to know what you guys think of the new Jellybean ROMs that we've all been blessed with. Are you happy with it? Any comments, anything? Just wanted to hear what you all think about the new OS on our tablets.

Personally I love it more than anything. Honeycomb and ICS have been nothing but pure lag, from stock ROMs to custom ROMs. I never thought I'd see the day this tablet actually performed smoothly, so when Jellybean first arrived (and pretty damn fast, as well), I was excited. Tried the ROM and loved it, it's just ridiculously smooth, and it works. Now I still get lag playing MC3 or Monster Life, but those are heavy games and Gameloft is pretty ****ty when it comes to properly making an Android game so that's excused. But other games like Dead Trigger work without a hitch, and emulators no longer suffer either. And just for being Android, it gets even better since I can use a wireless mouse over USB OTG, a BT keyboard, and a PS3 controller for games and emulators. All thanks to Jellybean, my tablet is awesome now :)

And also a thanks to MapleSyrup and pershoot, for the two that gave us Jellybean ROMs at all :)
[Galaxy Tab 10.1 General] vladtdr:
Yes, i like cyanogenmod 10, it's smooth and I haven't really noticed any over the top bugs...Battery life could be better but i prefer to sacrifice battery for that smoothness... And now that leads me to Samsung and their ****ty update plan...I mean come on i have waited 8 months to get ICS that lags like hell and doesn't play youtube videos correctly?...They should have just skipped ICS and focus on jelly bean...Other tablets are getting jellybean and we just got ICS, wonder how much will it take them to provide the stock jellybean...another 8 months?(i'm a fan of touchwiz that's why i *****...and i don't want a 7 inch tablet(nexus 7)).
[Galaxy Tab 10.1 General] Nacho Zits:
I Skype lots so need a working camera. Can't wait till CM10 has the camera driver. Any word on wheh this can be expected ?
[Galaxy Tab 10.1 General] arashtarafar:
I have cm10 and it seems so fast but a Quadrant test must tell it's value...the previous tests show that ICS is faster but JB's graphics are better...

Now that the rear camera is working the ROM is worth flashing(I never use the camera but couldn't bear it's loss...).

What do you TouchWiz fans think about putting it on the JB?it seems possible,doesn't it?let me know... ...
[Galaxy Tab 10.1 General] GazaIan:
The reason Quadrant scores are lower in JB is because JB puts the UI at a higher priority, basically to keep the whole thing smooth. Antutu's latest update takes that into account and as far as I know, it's the only benchmark app that has been updated for Jellybean.
[Galaxy Tab 10.1 General] spitzaf:
I keep installing ROMs on here to find the smoothest reliable ICS or JB, and CM10 is working beautifully for me. I especially like the subtle mods, like weather on the lock screen, email count in status bar, ability to enter settings without the app you were in being closed by the system, three action lockscren... the list goes on.

Definitely gets my vote unless you can't live without camera.
[Galaxy Tab 10.1 General] StevenBX:
Same here. I won't flash until we have a working front camera either. Hopefully it's done soon...
[Galaxy Tab 10.1 General] cashiro:
I would like to know why data package is not supported on gsm I try to pay data for my tab and once I received confirmation of the debit my tab keeps displaying no internet connection it only allows to navigate through the WiFi does any one knows how to fix it...
[Galaxy Tab 10.1 General] djmatt604:
I'm very happy with CMX. I'm glad I like it because I'm having a lot of trouble trying to go to other ROMs right now for the sake of checking them out - but I'll tell ya, there are probably way worse ROMs to be stuck on! I also have CMX on my S2 and am so in love with JB I don't know if I want to go back from a daily driver perspective. :)
[Galaxy Tab 10.1 General] jayceebee23:
I actually used CM10 Preview by pershoot and was highly impressed by the performance and smoothness. However, I recently started to require skyping for work related meetings so had to switch back to ICS 4.0.4. When JB works with front camera, expect me to be the first in line. :)
[Galaxy Tab 10.1 General] jazzespresso:
Android 4.1.1? which one? confused like hell!?

Maybe it is only me confused here. and this is my first post, so be gentle

:D

so I got excited when Samsung finally release Android 4.0.4!, could not wait so I downloaded UK Galaxy Tab 10.1 wifi (I have US one).

all good, but still not smooth, slow, then realize we need Android 4.1.1 (I have Google Nexus 7)...so jumped here, checking JB ROMs. that's when I start get confused. which one should I download that has less bug? Android 4.1.1 - CyanogenMod 10? or Toldo's JellyBeanRom ICS v5? or MapleSyrup's JellyBeanRom ICS? when you read each post (usually hundreds of replies), you even got more confused...

don't take me wrong, I love what our developer is giving us! even if this my first post, I already donated. however, it would be so helpful if there's new thread that lists all JB ROMs, and clearly outlines what works and what does not works, of any additional fixes. Now my galaxy tab 10.1 sitting there, staring at me, and dying to get on JB :)

Cheers to all:good:

J.
[Galaxy Tab 10.1 General] Caede:
I've been using CM10 builds from Pershoot and I've been really pleased. Fast, responsive, and all the apps I use day-to-day work beautifully. Battery life is trouble-free. I do occasionally get lockups, but I'm too lazy to try to identify how -- a lot of the time, it's opening large PDFs. Otherwise, most tasks are trouble-free. Rear cam works beautifully.

Unfortunately, I'm cursed with an SCH-i905 -- and no 4G LTE until Samsung gets off their ass and releases source that pershoot can merge. When that day comes, I will wet my pants in excitement.

I have a 4G LTE phone as well, so I just tether the tablet, and life is grand... but I sure would love to have it natively working on my tab. For a few months I had to revert back to stock HC on it because I needed the 4G... now that I've switched back to CM, I've been very happy.
[Galaxy Tab 10.1 General] jazzespresso:
-----------------------

so CM10 build that you use is from : http://xdaforums.com/showthread.php?t=1787399

it is safe to say that I can flash my galaxy tab 10.1 wifi (which is now on stock android 4.0.4) with CM10 build, and all works perfect no issue other than front camera?
[Galaxy Tab 10.1 General] bkress:
It is CM10, even the developers hate to hear it called CMX... This is Android, not Crapple!

For me, it is running great on both my tablet and my phone minus the occasional scrambled boot on my tablet (never happened on cm9 or any other roms) which I still get after updating to the official ICS boot loaders. But, it seems way more polished and complete then the early versions of CM9. I have made it my daily driver on both devices. Battery life is better than 4.0.4 also as long as you turn off Google now and so e of the location services. It will only get better with time...
[Galaxy Tab 10.1 General] djmatt604:
BAHA - Crapple. :)

Yeah sorry about that - it does say CM10 in my sig, I just got lazy typing last night. My bad.
[Galaxy Tab 10.1 General] GazaIan:
So Crappie owns the letter X? I use it as a roman numeral when abbreviating CM.

Also, I'm curious, what difference do the ICS bootloader provide? Is it a noticeable improvement?
[Galaxy Tab 10.1 General] bkress:
Haha, of course they don't own it... I just heard entropy tell someone in another thread not to call it cmx Since the boot animation that coined the cmx name is in no way official and they (cm10 dev team) have never called it that. If people are searching for answers about cm10 and people are calling it cmx, it may confuse users and make them think cmx is something different. We all know it is not, but we should all be using the real name for consistency purposes, right? I didn't mean to be an a**, just stating the facts.
[Galaxy Tab 10.1 General] marciozh:
Whereas CM10 is still in alpha stage, I can say that it works very well! This promises to be the best ROM.:laugh:
[Galaxy Tab 10.1 General] rpoitras:
I was running MapleSyrup's AOSP JellyBean build for about a week and then switched over to pershoot's CM10. While I found they were very similar I stuck with CM10 because it feels a bit smoother. I had a little issue with a scrambled screen when booting where only for a second or two the screen was rolling but cleared up afterwards. I did not have a rolling recovery screen. I updated the bootloader to the ICS version and it's been great since. I also haven't had any SOD's either when charging overnight or just sitting there.

The only issue which I still have is Youtube HD videos get very choppy and this happened on both JB builds.

But another good news tidbit is that HBO GO was updated to support JB and that was the only thing I was missing since running an ICS rom. And it seems to work perfectly!

So, thanks go out to Maple and pershoot and all the other devs out there that contribute to getting us up to speed. I was just over my dad's house and updated his GTab to ICS for him and all the while I was chuckling because I've been running JellyBean for a while before he even got ICS!
[Galaxy Tab 10.1 General] jazzespresso:
I am on MapleSyrup's AOSP JellyBean, and you said "updated the bootloader to the ICS version"? I am a little confused. .how do you do that? what the benefit? I am assuming when you said bootloader to ICS version, you meant latest ICS stock?
[Galaxy Tab 10.1 General] sueder:
CM10 by pershoot is now my daily use rom. i don't miss the front camera and haven't noticed any annoying bug.
[Galaxy Tab 10.1 General] rpoitras:
See here: http://xdaforums.com/showpost.php?p=30667324&postcount=4017

Instead of having to install an ICS build (to get the ICS bootloader) before going to Jellybean you can just install the bootloader directly.
[Galaxy Tab 10.1 General] usafbamafan:
I like the rom, but I keep getting SOD after charging at night. Thought it was fixed with pershoot last patch, and it definitely happens less often than it did with some of the other ICS roms. however, it still SOD's once every couple of days.

Cant wait for him to finish the new kernel cm9.
[Galaxy Tab 10.1 General] jazzespresso:
rpoitras, you are going to be mad at me, but I am still confused :rolleyes:
[Nexus 7 Q&A, Help & Troubleshooting] gogol:
Hi,

Nexus 7 charger ouputs 2A.

Is it safe and ok to use it to charge Galaxy Nexus, Nexus S, and HTC Desire?

I am thinking more in the long run, if it does not brake the phones.

Thanks
[Nexus 7 Q&A, Help & Troubleshooting] James-NC:
It should not hurt anything.My daughter charges her Droid 4 with my charger every day.