Database Info

[Q] Rooted XOOM No SD

Hi all,
I am a noob, first post. I purchased my XOOM (WiFi version) one week ago. I was led to believe it was stock (it is 2 mo. old) and have discovered that it has been rooted and modded. Here is the Device Info:
Android Version 3.2
Kernel Version 2.6.36.4-Tiamat_Xoom-v2.1.0-Tachi-StockGPU-gcef3887
It did not come with an SD card. I purchased one today (16gb). Are there critical files missing that were on the original sd card?! Thanx in advance.

To further clarify; if I wish to factory reset the device, are there files that I will need on the sd card other than a current backup?

the stock xoom didnt come with an sd card. it didnt even support it initally. hitting the restore to default button will not remove your root.

patass said:
the stock xoom didnt come with an sd card. it didnt even support it initally. hitting the restore to default button will not remove your root.
Click to expand...
Click to collapse
What exactly do you want to do with your Xoom? It is great to already be rooted and that Tachi kernel is a big improvement over stock. Do you just want to clean out the previous owners stuff and make it more yours? Or do you want to go back to a pure stock state?

That is a good question. I guess my main concern is that I am able to mod my device without any problems that the previous owner may have caused by removing critical files on the SD card. I'm a little paranoid as I am just beginning to learn.
I discovered a clockworkmod recovery file "recovery-clockwork-4.0.0.4-stingray.img" in the internal memory. I don't understand what that file is. Is this a stock recovery file?

Janoska said:
That is a good question. I guess my main concern is that I am able to mod my device without any problems that the previous owner may have caused by removing critical files on the SD card. I'm a little paranoid as I am just beginning to learn.
I discovered a clockworkmod recovery file "recovery-clockwork-4.0.0.4-stingray.img" in the internal memory. I don't understand what that file is. Is this a stock recovery file?
Click to expand...
Click to collapse
ClockworkMod recovery is a custom recovery. It is installed when rooting and is a great improvement over the stock recovery because it allows you to make a complete system image so you can experiment with new rom or kernel and always be able to restore to a previous state if you're dissatisfied or if something goes wrong. Also, with the right version you can save files to your external micro sdcard [you purchase it.it does not come with the Xoom] and flash them through your CWM recovery menu. However, version 4.0.0.4, the one you have installed, doesn't recognize the external sdcard. You will need to install version 3.2.0.0 R4c.

Thanks for the info, I will install version 3.2.0.0 R4c. Looks like the previous owner saved me some work.

[Q] Cannot use samsung recovery to install CWM

Hi,
I have a problem with my P6210. I am trying to install CWM on it (it has root access) but whenever I go into the recovery, it cannot find the sdcard with the cwm zip file. I have put it in multiple places in the system to see if the recovery software can find it but fails.
The photo shows the screen I get every time I try -
https://www.dropbox.com/s/gau2erxviegyqwc/2012-06-22 05.26.54.jpg

Anyone please?

It means you either didn't put the zip in the right place (on the root of the SD) or you have a wonky MicroSD card. Happened to me with an off-brand 8gb. Used another 2gb card I had lying around and works fine.

Thanks a million!
I remember this is how i rooted my tab too. I swapped the sd card from my optimus black to my tab and was able to root it like that. Must have forgotten.
Again thanks a lot.

My pleasure. Just got my GT+ (trying to decide if it can replace my GT10.1) and had fun figuring this one out myself. It's a bummer there's no working ICS for this tab (yet); on the GT10 it was night and day from the best custom 3.2 ROM to the first ICS ROM.

[Q] S3 Locked in Boot Following CRT Down zip

This is one heck of a way to introduce myself. I am embarrassed and frantic about what has happened. I've been using the guidance in these forums for years, never had any problems, but I usually made a backup. Because of the size of the S3 backups, I didn't have one this time.
I have a Verizon S3 on stock ROM, rooted, CWM Touch Recovery installed, bootloader locked. I flashed the CRT Down - ODEX.zip (attached) from the thread below. Everything seemed to go well, but on reboot the phone gets stuck in the boot animation. I have also contacted Scott over Scott's ROMS since this was where the file came from, but have not heard back. My first preference is to undo the changes to the modded files. Second choice is to flash the latest stock ROM (Stock Root - VRALHE - ODEX.zip) that I have downloaded, BUT I cannot get it on the phone since the phone won't boot, and for some reason CWM does not see any files on the external SD card. My last choice is to do a wipe/restore from stock, and I think I know how to do this, but it will be very painful.
Anyone in a helping mood? I don't know where to go from here. This is just terrible.
http://forum.xda-developers.com/showthread.php?t=1841802&highlight=crt

CWM won't read your SD card because it's not formatted to the correct file system. You could take your card and backup the data, format it to Fat32 then transfer the ROM over to your phone that way. I've long since lost the link to the simple format tool that I used to format my card but if you search for it you should find it in I think the General Forum...

SD card already FAT32, formatted by PC and then reformatted in phone. Thanks anyway.

undrgnd1 said:
SD card already FAT32, formatted by PC and then reformatted in phone. Thanks anyway.
Click to expand...
Click to collapse
If you reformated in phone you formatted it back to extFAT.

You are absolutely correct sir. Your assessment was dead on. Thank you very much. I can now make a backup to the external card. Unfortunately, I had to restore the phone (-#*@"*). I found that two other 64GB cards I was having problems with had the same issue. Wow! Twenty five years around computers and I just figured out how to format volumes larger than 32GB in FAT32. Thanks again. This thread is done.

[Q] Phone broken or still hope?

Hello everydody, I am experiencing some difficulties with my Samsung, model GT-I9003-phone which "dropped off a lorry" somewhere next to my relatives somewhere in Asia. When I goth the device, it was in a non-working condition, except a boot-loop and the download-mode. Back then, I had the package of the phone where the exact version ( I don't know if this is what is called "Baseband" or at least is called baseband at my wife's GT-I5003) was specified. So, back then, I was able to find the exact ROM for the device. Unfortunately, the box with the version number now is - somewhere.
After flashing a stock-rom, I managed to enter recovery-mode where I read something about the internal memory being corrupt. As far as I can recall, I then mounted the external SD-Card and somehow managed to reboot the system back to almost normal operation. Even reboots appeared to work normal, besides the fact I had no memory access, neither to internal nor to external sd. In addition, GPS malfunctioned, too.
Unfortunately, even this state didn't last for long time. After several weeks of now-and-then-use, the system just broke down again into a boot-loop. After some time of flashing a variety of stock roms, I managed to flash clockworkmod recovery which works perfectly well. Unfortunately, I didn't manage to root the phone before it "collapsed" again. Besides the possibility, I'd guess this could be a resaon for CWM being unable to flash a custom rom? Otherwise, I'd just test my way through the varieties of versions .
Basically, I do have two questions: 1. is there a possibility to find out if internal memory has failed - and if yes: How?
2. Is it possible to install any version of CM on that phone in the condition it is in?
Thanks a lot in advance for any answers

Hello everybody, I finally found the box . It reads GT-I9003MKDTHL. Is my assumption right that there are no such things as basebands in the GT-I9003 any more and I should be able to flash pretty much any firmware? Furthermore, today I tried to format what is specified as "sd-card ext" in CWM fir GT-I9003 and it gives me an error-message. When I flash "sd-card", my external sd-card gets formatted. So, I'd presume the internal sd is just fried. I read about a workaround for GT-I 9000, where someone installed Androd on a partitioned external SD. Is there somebody who knows someboy having heard about somthing similar working with the GT-I9903?

One step forward...
Hello everybody, I finally managed to get some light into my issues as I once again figured out how to get a software installed and running . It's this one:
http://forum.xda-developers.com/showthread.php?t=2329200
Thanks a lot to the guy who just posted it somewhere where id could do good...
By the way, I figured out that this software actually includes the Baseband.
As in this version, the original recovery system is running and giving me an error message when I start it without external SD-card, I am now quite sure that the internal memory has just failed as this error message was specified in another posting of someone who had a similar issue with a GT-I9000.
The biiiig "Outch" is, that I am unable to install any CWM Recovery System with that Baseband..This results in me not being able to upgrade the software to ICS, where - as far as I read some troubleshoot-information - will enable me to mount an additional partition on my SD-Card as Data-Partition which isn't possible yet (i.e.: I can't access my SD for storing data or whatever - it's just specified as "not there").
I tried to install the XXKPE-Baseband to be able to go for KPQ which would enable me to install CWM Recovery. I also installed Bagarias CWM-normalboot-image via Heimdall - but I was unable both to boot the OS and to find any trace of a zip-file on the SD-card.
Edit: I managed to install the right CWM - it's mentioned in the post where I've got the firmware from... now, I only have to figure out how to deal with the fact that "officially" there is no SD-card inserted - or, better, that this SD-card is now flagged as "internal SD" - and how that machine can find the zip-file on it
Thanks for every bit of help with that issue

Try Aroma File Manager with Terminal
For SDCard issue you could probably switch them in vold.fstab in /system/etc
Good Luck !!!

try this- http://forum.xda-developers.com/showthread.php?t=2329200

SD cards: exFAT Fat32 file sizes

Just wanted to check peoples thoughts on this. Had a 32GB Sandisk card corrupt (i think) on me the other day. Woke the phone and seen the SD card icon in the task bar as if it had just mounted the SD but it had unmounted it and said that there wasn't one inserted. Have yet to try it in a PC to see what (if any) files I can recover.
The previous night I had made a nandroid backup (Philz touch), there was something not quite right with the file sizes not showing on screen but it seemed to work the second time around. Can't recall if the card was formatted as FAT32 or exFAT, but if FAT32 could one of the nandroid files caused issues if it was over 4GB? Anyway going to see what I can possibly recover and if it can be reformatted again before possibly purchasing a 16GB Samsung card here: (http://www.7dayshop.com/samsung-plus-microsdhc-uhs-1-16gb-memory-card-class-10). Dont mind the smaller size if its more reliable.

gsmyth said:
Just wanted to check peoples thoughts on this. Had a 32GB Sandisk card corrupt (i think) on me the other day. Woke the phone and seen the SD card icon in the task bar as if it had just mounted the SD but it had unmounted it and said that there wasn't one inserted. Have yet to try it in a PC to see what (if any) files I can recover.
The previous night I had made a nandroid backup (Philz touch), there was something not quite right with the file sizes not showing on screen but it seemed to work the second time around. Can't recall if the card was formatted as FAT32 or exFAT, but if FAT32 could one of the nandroid files caused issues if it was over 4GB? Anyway going to see what I can possibly recover and if it can be reformatted again before possibly purchasing a 16GB Samsung card here: (http://www.7dayshop.com/samsung-plus-microsdhc-uhs-1-16gb-memory-card-class-10). Dont mind the smaller size if its more reliable.
Click to expand...
Click to collapse
I quite highly doubt a Samsung SD card will be more reliable. Don't know what's the fuss about SanDisk corrupted but I myself or anyone in my friend/colleague circle have yet to face a problem with SanDisk!
And the first thing you should do is format your card to exFAT, I really don't know how and why people uses FAT32

jujuburi said:
I quite highly doubt a Samsung SD card will be more reliable. Don't know what's the fuss about SanDisk corrupted but I myself or anyone in my friend/colleague circle have yet to face a problem with SanDisk!
And the first thing you should do is format your card to exFAT, I really don't know how and why people uses FAT32
Click to expand...
Click to collapse
This is the first problem I've had with it to be honest, had it or over a year and was using it in my HTC Sensation previously. I'm trying to remember if it was exFAT or FAT32, I remember a ROM (Google Edition S4 ROM) not being compatible with exFAT and checking mine out of curiosity, but just can't recall what it was and never flashed the ROM. I didn't reformat it coming from my Sensation so it hadn't changed in anyway.
Luckily all my photos were backed up to dropbox so nothing lost of too much importance. Need to get a microSD card reader to see if its completely borked or if files can be retrieved.

Someone will correct me if I'm wrong but I'm pretty sure that Nandriod breaks the files down smaller than 4GB if you're running on Fat32 so I doubt that'll be your problem. Mostly because the FAT32 architecture just won't accept a file that big unless the Linux kernel of Android ignores the limitations. I would HIGHLY recommend NOT restoring a nandroid backup if you think the sizes are off or if you're attempting to recover the data without and MD5 checksum. That's all sorts of bad juju.
As for Sandisk vs Samsung, I have both, I've never had a problem with either. My sammy card is in my TF201 and my Sandisk is in my I337 as it's a faster card from my benchmarks. But like I said, no problems with either.
As for data recovery, go check out Recuva, it's supposed to be pretty good especially for being free. Since I'm IT I have professional grade software for data recovery and don't have tons experience with Recuva. A couple tips about data recovery. Once you determine you want to recover data, DO NOT WRITE TO OR FORMAT THE CARD, that'll prove to make the entire process more difficult. it's going to take a good long time, at least an hour for the initial scan. Do all the work on the card from a computer and not through a connection to your phone. Anyway if you have any questions or possibly want some help shoot me a PM, I'm happy to impart my knowledge.

Theoriginalgiga said:
Someone will correct me if I'm wrong but I'm pretty sure that Nandriod breaks the files down smaller than 4GB if you're running on Fat32 so I doubt that'll be your problem. Mostly because the FAT32 architecture just won't accept a file that big unless the Linux kernel of Android ignores the limitations. I would HIGHLY recommend NOT restoring a nandroid backup if you think the sizes are off or if you're attempting to recover the data without and MD5 checksum. That's all sorts of bad juju.
As for Sandisk vs Samsung, I have both, I've never had a problem with either. My sammy card is in my TF201 and my Sandisk is in my I337 as it's a faster card from my benchmarks. But like I said, no problems with either.
As for data recovery, go check out Recuva, it's supposed to be pretty good especially for being free. Since I'm IT I have professional grade software for data recovery and don't have tons experience with Recuva. A couple tips about data recovery. Once you determine you want to recover data, DO NOT WRITE TO OR FORMAT THE CARD, that'll prove to make the entire process more difficult. it's going to take a good long time, at least an hour for the initial scan. Do all the work on the card from a computer and not through a connection to your phone. Anyway if you have any questions or possibly want some help shoot me a PM, I'm happy to impart my knowledge.
Click to expand...
Click to collapse
I thought it should break them down, it was just the /data partition that includes the apps and app cache, if it could be over 4GB stored as a .tar file would that still be broken down as such? Won't be attempting to restore the nandroid (if its even still recoverable) as I have flashed a pre-rooted stock odin firmware and its actually really smooth (maybe thats due to the sd card not being inserted). Although I seem to be having an issue flashing a custom ROM, as even after flashing the firmware via odin then trying to flash a ROM via Philz touch its still bootlooping (even with a wipe/factory reset and clean install format). Haven't attempted a different custom ROM but just havent had the time to test that out. Thinking I would have to download the original firmware files and start from scratch with rooting and adding a recovery to see if that solves it, but think I'm going to sit tight for the moment.
Thanks for the recommendation and the support, much appreciated.

gsmyth said:
I thought it should break them down, it was just the /data partition that includes the apps and app cache, if it could be over 4GB stored as a .tar file would that still be broken down as such? Won't be attempting to restore the nandroid (if its even still recoverable) as I have flashed a pre-rooted stock odin firmware and its actually really smooth (maybe thats due to the sd card not being inserted). Although I seem to be having an issue flashing a custom ROM, as even after flashing the firmware via odin then trying to flash a ROM via Philz touch its still bootlooping (even with a wipe/factory reset and clean install format). Haven't attempted a different custom ROM but just havent had the time to test that out. Thinking I would have to download the original firmware files and start from scratch with rooting and adding a recovery to see if that solves it, but think I'm going to sit tight for the moment.
Thanks for the recommendation and the support, much appreciated.
Click to expand...
Click to collapse
Well in general in windows when a FAT32 structure is asked to write a file larger than 4GB it'll flat out deny it (usually saying something like disk is full). If you're writing to a FAT32 structure using something that increments the file as it writes it, when it hits the 4GB file size limit, it'll usually say again disk is full and the file will go corrupt (which can lead to the file being undetectable). I do believe that Nandriod is smart enough to realize when it gets to that 4GB limit it'll break the tar into multiple files or else the linux OS would probably kick back an error. As for your ROM bootloops and things like that, I'd see about another ROM, maaaaybe it could just be that the ROM you flashed doesn't like your phone (I have an i717 that does that with a ROM). If that still doesn't solve it, like you said. Start at the beginning completely clean and just work through the entire process.

Theoriginalgiga said:
Well in general in windows when a FAT32 structure is asked to write a file larger than 4GB it'll flat out deny it (usually saying something like disk is full). If you're writing to a FAT32 structure using something that increments the file as it writes it, when it hits the 4GB file size limit, it'll usually say again disk is full and the file will go corrupt (which can lead to the file being undetectable). I do believe that Nandriod is smart enough to realize when it gets to that 4GB limit it'll break the tar into multiple files or else the linux OS would probably kick back an error. As for your ROM bootloops and things like that, I'd see about another ROM, maaaaybe it could just be that the ROM you flashed doesn't like your phone (I have an i717 that does that with a ROM). If that still doesn't solve it, like you said. Start at the beginning completely clean and just work through the entire process.
Click to expand...
Click to collapse
Cheers, I had re-downloaded the previous version of the ROM which I was on before hand and made sure to check the md5s but it still wouldn't boot which was annoying, but a full install from scratch may be the way to go. Never had bootloops before and was just worried after I had wiped and started a fresh and it still happened. I think the real lesson is to make sure to backup ANYTHING that is of value to you!
Luckily I had just happened to use the auto backup for photos to dropbox so got off lightly this time!

I have had the EXACT same issue 2 weeks ago.
I bought 2 x 32gig microSD cards (Sandisk)
1 for my phone and 1 for my digital camera.
Recently the 32gig one in my phone just DIED for no reason at all. Lost all my files, music, everything.
I contacted Sandisk, had it repalced. In the meanwhile i purchased a 64gig Samsung one.
I am yet to have an issue with the Samsung 64gig, but only time will tell.
On a plus note, Sandisk sent me a replacement 32gig card very quickly (infact too quick, i purchased the 64gig Samsung one on the idea that the Sandisk replacement was going to take months... in fact it only took 6 days...)
Cheers

How did you contact Sandisk, did you need to give a serial number or provide proof of purchase?
Sent from my Nexus 7 using xda app-developers app

jujuburi said:
And the first thing you should do is format your card to exFAT, I really don't know how and why people uses FAT32
Click to expand...
Click to collapse
I always use Fat32 on SD-cards. Why? It works on every Rom, with every kernel, every recovery, on every device, every camera, every computer, all the time.
When not in need of files greater than 4GB Fat32 simply is the way to go, compatibilty-wise.

gsmyth said:
How did you contact Sandisk, did you need to give a serial number or provide proof of purchase?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Tried the card in a reader connected to my laptop but nothing. I've emailed Sandisk support so will see what they say.
Sent from my GT-I9505 using xda app-developers app