How do I restore a system? - Sony Tablet S

Hello,
My Tablet S is in deep need of expert help to see the light of day...:crying:
History:
I've rooted it about one day after the working exploit was found, ran Condi's AiO tool to update, and everything went fine.
At once, I used the "reinstall to factory settings" in the Settings app, which gave me a happy - if somewhat unstable at times - tablet.
It suddenly stopped working and remained stucked at the Sony logo.
Having no other option, I restarted in Recovery (Power-Volume+), and tried to update the system from SD card :
- with latest Condi's R5a zip : signature error
- with stock encrypted Sony zip : update blocked (yes, I left the tablet running about 8 hours without a move from the progress bar)
In the Android Recovery, I then selected "Reset to factory settings". Which seemed to do its thing, except that...the tablet still was stucked at the Sony logo at boot.
Going to Recovery again...
Code:
E:Fail to read boot logo flad
E:Can't open /dev/block/mmcblk0p5
(No such file or directory)
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/command
E:failed to mount /cache (No such file or directory)
E:failed to mount /cache (No such file or directory)
E:failed to mount /sdcard (No such file or directory)
E:failed to mount /cache (No such file or directory)
E:failed to mount /sdcard (No such file or directory)
E:failed to mount /cache (No such file or directory)
I can see the following device with ADB :
Code:
./adb devices
List of devices attached
0123456789ABCDEF recovery
and that's about all I can do with the tablet now.
Code:
./adb shell "ls /"
- exec '/system/bin/sh' failed: No such file or directory (2) -
One word remains: PLEASE HELP !
Is there any way I can dump a working system on the tablet in this state?
Note: I'm not afraid of running anything arcane command/script/setup.

Strange because the shell binary cannot be found but it can be wiped.
It is possible that the System partition is gone.
Sent from my Sony Tablet S using xda premium

andyabc said:
It is possible that the System partition is gone.
Click to expand...
Click to collapse
Yes indeed, I'm pretty sure that the Recovery option "Restore to factory settings" did wipe partitions...and failed to write anything sensible to them afterwards, or to recreate them at all (if that makes sense : I am far from sure of what the whole process really does and whether this is an Android standard or Sony-proprietary).
So, I'm there with my half-baked tablet ... any kind soul with the know-how how to revive it?

sorry to be the bearer of bad news, but I have had the expect same thing happened to my tablet s, all of sudden it stopped working, stuck on sony logo during booting, can't mount sd card in recovery mode, etc etc. Chances are your mother board is damaged. Might be a good time to send it to sony for repair. Good luck

since you have root,look here
how to use adb shell in recovery mode
http://forum.xda-developers.com/showthread.php?t=2081196
once you get shell,check you mmc device,and it's partitions
http://forum.xda-developers.com/showthread.php?t=2102704
any way,send your tablet to sony is a good chiose.

Palijn said:
Yes indeed, I'm pretty sure that the Recovery option "Restore to factory settings" did wipe partitions...and failed to write anything sensible to them afterwards, or to recreate them at all (if that makes sense : I am far from sure of what the whole process really does and whether this is an Android standard or Sony-proprietary).
So, I'm there with my half-baked tablet ... any kind soul with the know-how how to revive it?
Click to expand...
Click to collapse
Data partition is still there though.
The recovery has its own shell for sure since you are rooted.
The recovery has its own binary and adb support.
Here is the boot order:
Bootloader>Kernel>Boot Animation>System
When the Sony logo flashes thats when it switches to the Kernel but since it did not do anything it is possible that there is missing files in the data partition.
Bootloader = On a component on the motherboard somewhere
Kernel = Data Partition
Boot Animation = System Partition
System = System Partition (Obviously)
Sent from my Sony Tablet S using xda premium

maybe kernel is not on data patition.
kermel is in rootfs.which is split with inner mmc dev(or in a hidden partition)

robin said:
maybe kernel is not on data patition.
kermel is in rootfs.which is split with inner mmc dev(or in a hidden partition)
Click to expand...
Click to collapse
Yeah true but the question is did the Sony logo flash for a moment, if it did then it switched to the kernel successfully.
I cannot view your username in the quote above due to it using part of the tags used in programming languages.
Sent from my Sony Tablet S using xda premium

andyabc said:
Yeah true but the question is did the Sony logo flash for a moment, if it did then it switched to the kernel successfully.
Click to expand...
Click to collapse
Yes indeed, the Sony logo flashes (and that's a fairly nice indication for the right time to press Power again and enter Recovery afterwards!).
Anyway, the tablet froze from time to time just entering Recovery (screen with the green/white dots), then I was able once or twice to start restoring a system image from the original Sony encrypted-signed ZIP so gracefully provided by condi in his Google Drive , but the process froze at different places!
I guess there is definitely a hardware issue (such as a faulty memory chip, if not a grilled processor), so right away it went to repair.
If it comes ever back as "repairable and repaired" I'll inform here!
Thanks to all for the attempts at helping!:highfive:

Palijn said:
Yes indeed, the Sony logo flashes (and that's a fairly nice indication for the right time to press Power again and enter Recovery afterwards!).
Anyway, the tablet froze from time to time just entering Recovery (screen with the green/white dots), then I was able once or twice to start restoring a system image from the original Sony encrypted-signed ZIP so gracefully provided by condi in his Google Drive , but the process froze at different places!
I guess there is definitely a hardware issue (such as a faulty memory chip, if not a grilled processor), so right away it went to repair.
If it comes ever back as "repairable and repaired" I'll inform here!
Thanks to all for the attempts at helping!:highfive:
Click to expand...
Click to collapse
Every chip and processor has its own firmware so maybe somehow it became corrupted.
Sent from my Sony Tablet S using xda premium

Related

[Q] semi-Bricked?? fix?

hi, i recieved a eris from a friend of mine with the intentions on fixing it and using it. when i power it on there's just a black backlit screen.. no splash, nothing. if i plug usb in it goes to a htc screen with 4 triangles in the corners. i've tried the ruu update and it gives an 110 error at the end saying something about files not found, i unhooked the usb and it went to a white screen with hboot 1.49 , n s-on n all that stuff.. and it showed info from the ruu, and it showed that the system and boot(or recovery, i cant remember exactly) failed and they were red. i can connect with fastboot but not with adb.. is there anything i can do to atleast get the phone working.. fastboot oem boot doesnt work for me, it just gives a long list of errors
fastboot will do nothing useful for you if you have the 1.49.0000 S-ON bootloader.
The basic definition of a brick for the Eris is this:
1.49.0000 S-ON bootloader + no recovery + non-booting OS = brick
So, let's review.
1) You have 1.49.0000 S-ON. There is no PB00IMG.zip available to you that can change that using Hboot (without performing some magic with a custom recovery first), and fastboot is worthless with S-ON. So, no go there.
2) You didn't mention (or your description was lacking detail) what happens when you try to go into the Hboot menu (cold start with Vol-Down+End). From there you might be able use the menu to try to launch the recovery boot, to see whether (a) it is the stock recovery, (b) it is a custom recovery, or (c) it fails to start. You should try that next.
If that doesn't work, try a cold start with Vol-Up + End. (You need to keep holding both the buttons down until the screen lights up). That is an alternate way to get to the recovery (when a 1.49.xxxx bootloader is on the phone).
If you have a "stock" recovery, you will see a splash screen with an image of the phone and a triangle with an exclamation point in it. (Pressing Vol-Up+End after you see that splash screen will show a blue menu). If you have Amon_RA's custom recovery, you will see a green menu.
3) If your kernel boots, but the OS is "hanging", there is a remote possibility that you can initiate a factory reset from the "hung" OS. This is a long shot, but you power up the phone normally and then press together Vol-Up+Send+End after waiting a couple of minutes. This might make it bootable. (As I said, "long shot". The fact that you have 1.49.0000 on the phone suggests that the prior owner tried some things - and apparently failed at it.)
bftb0
thanks for the response
i tried all of that just now and all i get is a black backlit screen unless i connect usb which gives me a black screen with HTC n four exclamation point triangles in the corners. and there isnt anything i can do from that screen and its bricked huh?
SoSicWiTiT said:
thanks for the response
i tried all of that just now and all i get is a black backlit screen unless i connect usb which gives me a black screen with HTC n four exclamation point triangles in the corners. and there isnt anything i can do from that screen and its bricked huh?
Click to expand...
Click to collapse
That's not a very good sign. I will say, however, that it is very strange that you can get the phone into RUU mode but not have a working bootloader - those two observations are mutually exclusive.
For grins, you could check to see if perhaps your Vol-Up/Vol-Down keys are broken by doing the following:
- Cold start the phone by pressing Send + End simultaneously (make sure to press Send first so that you are not initiating a normal boot; hold both keys down until the screen lights up). Make sure you pull the battery and have the USB cable disconnected when you pull the battery before you try this (to insure that the phone is "really" off).
If that works, the phone will be in Fastboot mode. You might be able to get into Hboot (but not recovery if your Vol-Up/Vol-down keys are broken) at that point with the command
Code:
fastboot reboot-bootloader
from a USB-connected PC.
Under normal circumstances, you can navigate from Fastboot Mode to Hboot and then from there to the Recovery boot - but this requires working Vol-Up or Vol-Down keys.
There is a very, very slim chance that if you can get Hboot launched this way (that is "fastboot reboot-bootloader")... and try to apply the Leak-V3 "PB00IMG.zip" file. If I recall correctly, you don't need Vol-Up/Vol-Down to apply an HTC PB00IMG.zip file - just the trackball press.
I'm not optimistic though - I think that the Leak-V3 (and all other Leak PB00IMG.zip) files probably will just fail with "Main Version is Older Messages".
As for other avenues of approach, there are no publicly known exploits of the RUU mode (= oem-78 mode).
Good luck
well
actually after staying up n working at it for 48 hours, i'm halfway done with a solution...and maybe the first ruu exploit.
i decided to run the 2.1 RUU and after it does its install wizard thing, i navigated to the temp folder where it installed all the files. i took the root rom (pb00img.zip) n renamed it to "rom.zip" then over wrote the version in the temp folder and started the ruu (clicked next and what not).. it failed as usual with error 110.. but afterward i noticed my phone says
pb00100 xc ENG S-OFF
HBOOT-1.49.2000
and before i did the file swap and ruu it said
pb00100 XC ENG S-ON
HBOOT-1.49.0000
so now i might be able to flash a custom recovery thru fastboot since i have s-off now
if not.. still.. its progress
Hmmm, interesting.
Whether or not that qualifies as new behavior sort of depends on what your "friend" did to the phone prior to getting it into the nearly bricked state. If they had previously run the jcase "Flash any RUU" method, then the Root ROM would have "taken" with the Hboot method... although in your case, since you "couldn't get there from here", my hat's off to you for a clever way of making the best of what you have!
Since you have the S-off bootloader, you might be tempted to direct-boot Amon_Ra without even bothering to flash it:
Code:
fastboot boot recovery-RA-Eris-v1.6.2.img
to see if your phone springs to life... congrats if you see a menu!
bftb0 said:
Since you have the S-off bootloader, you might be tempted to direct-boot Amon_Ra without even bothering to flash it:
Code:
fastboot boot recovery-RA-Eris-v1.6.2.img
to see if your phone springs to life... congrats if you see a menu!
Click to expand...
Click to collapse
i did that right after i seen it say "S-OFF". i get to the menu but when i try to flash a rom it gives me an error after formatting system.
Code:
E:Can't symlink /system/xbin/arp
E:Failure at line 65:
symlink /system/xbin/busybox SYS
TEM:xbin/arp
and after hours or more reading, everything is pointing to the boot and system partitions being corrupted by a bad flash of some sort.
i think i might have hit the end of the road..
EDIT
i managed to somehow get all the regular hboot, fastboot, n recovery to work and flashed amon_ra and can get to it from volup+power.. even got the 3 skateboarding droids on normal power on..
but cant flash any roms , from amon's ( gives the error above )or pb00img from hboot (at the end has "failed-PU" next to system..)
any idea's?
I have a couple ideas (still typing them up) ... in the meantime, if you boot Amon_RA and then open up a shell from the PC ("adb shell") and then
- check the output of "dmesg" to insure that the MTD partition table is still intact; you should see something like this towards the beginning of the boot log:
Code:
NAND_EBI2_ECC_BUF_CFG: 1ff
flash_id: 5501bcec size 20000000
Creating 6 MTD partitions on "msm_nand":
0x00001ff60000-0x000020000000 : "misc"
0x000002c60000-0x000003160000 : "recovery"
0x000003160000-0x0000033e0000 : "boot"
0x0000033e0000-0x00000dde0000 : "system"
0x00000dde0000-0x000015fe0000 : "cache"
0x000015fe0000-0x00001ff60000 : "userdata"
- try mounting (in turn) each of /system, /data, /sdcard, e.g.:
Code:
mount /sdcard
mount /data
mount /system
/cache should already be mounted.
Which mounts fail?
bftb0
The scenario you describe has come up before - or at least very similar symptoms.
Note that Nandroid restore will fail because it uses standard Unix tools such as "rm" to clear filesystems, so if a partition will not mount because of a corruption issue, nandroid will fail. I suppose that the same thing is true of the /sbin/recovery utility running underneath the booted recovery kernel (but I have not read the source code to verify that it is attempting to "mount" the filesystems first - if it didn't do that, it would need to understand the raw format details of yaffs2, and I think that is a stretch).
Unfortunately the filesystem formatting tools provided by Amon_RA do not include tools for repairing the mtd (NAND flash) - they are for the SD card/ extN filesystems. It is my impression, however, that the "yaffs2" filesystem is "format free" - meaning that a clean (Flash memory) "yaffs2" filesystem is simply a bunch of zero'ed pages - no superblocks, or Inode lists, - none of that. This suggests that the equivalent of "dd if=/dev/zero of=/dev/mtd/mtdNNN bs=..." could "repair" a yaffs2 file system by simply wiping it... but let's try something a little less crude than that (see below).
I had one of the file systems in my phone in this state at one time and I was able to repair the problem by reflashing the Root ROM - otoh, XDA user "stick" tried this and it seemed to produce a permanent brick in his case, so I am reluctant to recommend you do that. (You might, however, want to perform the jcase "Flash any RUU" hack to the "misc" partition so that you have flexibility to apply any PB00IMG.zip file)
Because the "flash_image" tool (in /sbin/flash_image in Amon_RA) writes both boot images and yaffs2 image files to arbitrary mtd partitions (and raw binary files to "misc"!), there is a chance that it is merely the equivalent of "dd for the MTD device" - so that you could "repair" a corrupted yaffs2 filesystem by simply overwriting it with a valid yaffs2 image file. The repair strategy here would be to:
- Unpack any PB00IMG.zip file and move the contents to a folder on the SD card. (Verify the md5sums of the files on the SD card before you use them - use this reference)
- Use "flash_image" from Amon_RA to flash the corresponding image file for the offending ("won't mount") partition, e.g.
Code:
flash_image system /sdcard/unpacked-PB00IMG/system.img
If this succeeds, see if you can "mount /system".
bftb0
PS Don't try flashing "system.img" using fastboot. However it is engineered (by the HTC bootloader) it will fail due to space issues. It is possible that the HTC bootloader uses the /cache partition to temporarily stage the file, which is only 130 MB compared to 159.5 MB for the /system partition - but whatever the explanation, the experimental result is that that on the Eris, you can not flash /system from fastboot. All the other partitions, no problem - but not the /system partition.
thanks,
i tried what you suggested and it let me mount all 3 of those partitions, and i tried using flash_image to flash the system.img i extracted and in return got a million and one errors..
starting with mtd: ECC error soft 0 hard 1 (continuing until about a hundred something)
then
mtd: not writing bad block at (basically the entire /system hex range)
then finally
error writing system: no space left on device
SoSicWiTiT said:
thanks,
i tried what you suggested and it let me mount all 3 of those partitions, and i tried using flash_image to flash the system.img i extracted and in return got a million and one errors..
starting with mtd: ECC error soft 0 hard 1 (continuing until about a hundred something)
then
mtd: not writing bad block at (basically the entire /system hex range)
then finally
error writing system: no space left on device
Click to expand...
Click to collapse
Was the partition table information correct? (I have seen innocuous "write error" messages on my phone, but they only occurred on regular block boundaries - not for every page; but in that case I don't think I ever saw an "out of space" message. Assuming everything was performed correctly, your phone is behaving as if large blocks of flash memory are being skipped due to "bad blocks")
Did you unmount the filesystems prior to doing the writes?
That is very mystifying.
If you can mount /system, or /data, what happens when you go in and do a
Code:
mount /system
cd /system
rm -rf /system/*
mount /data
cd /data
rm -rf /data/*
cd /
If those succeed, unmount everything
Code:
cd /
for x in /system /data /sdcard ; do
umount $x
done
Run an Amon_RA "wipe data/factory reset", and try and flash a ROM.
???
bftb0
One other thing you could try - I have never used it, so I don't know what effect it will have - is to use fastboot mode to erase the "system" and "data" partitions, and see if that has any effect on your ability to flash a ROM.
In fastboot (boot w/ Send+End) mode:
Code:
fastboot erase system
fastboot erase data
And then afterward boot into Amon_RA and try flashing a ROM.
I suppose you could also erase the boot partition this way, but you probably ought to do them one at a time just to minimize erase operations - and then if an operation fails in Amon_RA, examine the log file at
Code:
adb shell cat /cache/recovery/log
to see if it provides further elaboration on the nature of the error(s).
bftb0
Something else to try:
The symptoms you have (esp. since it appears that /system and /data will mount correctly) appear as if you "run out of space" when flashing ROMs to NAND. I suppose that could occur if somehow a bunch of pages in flash memory got (erroneously) marked invalid. Unless there is some means to clear flash memory so that bad page indicators are cleared, there is no way to reclaim those pages. (It is my impression that brand new NAND flash chips are already programmed with bad pages pre-marked)
It would be nice if the partition erase function of fastboot actually performed the page reclaim/retesting/re-marking operation - but there is no way to know whether that happens, as the HTC bootloader acts as the interpreter of "fastboot commands" passed over the wire (USB). It is free to implement whatever bad page management strategy that HTC desires - and frankly, a "never reclaim bad pages" policy is fairly reasonable when you consider that most consumer phones are flashed perhaps only 3 or 4 times in their lifetime - if that.
Something to try: if you perform a manual wipe of either /system or /data (after mounting them), do a "df" to see how much free space the kernel thinks they have - for a normal phone, that should be pretty darn close to the partition size. E.G.
Code:
> adb shell
# mount /system
# df /system
# mount /data
# df /data
# umount /system
# umount /data
# exit
>
If it seems "short" by a substantial amount, try installing a "small footprint" ROM, such as CELBFroyo 3.2 - it only uses about 100216 KB (97.9 MB).
Just a thought; I realize this is grasping at straws, but there is little for you to lose (which you knew right from the get-go).
bftb0
wow seriously i appreciate all the help you've provided , you need a donate button lol.
the system partition is 66% used (bad blocks im guessing) after a format leaving 59,648 useable
but the data partition is fine with 1% used. and 162,176 usable
but i havent lost all hope yet and this is entertaining me.
custom mtd maybe..swap /data to mtdblock3 (the bad one, system) and and /system to mtdblock5 (where data currently is).. or use a memory card idk?
here's where i got the idea
http://forum.xda-developers.com/showthread.php?t=717874
SoSicWiTiT said:
the system partition is 66% used (bad blocks im guessing) after a format leaving 59,648 useable
Click to expand...
Click to collapse
Holy crap!
For grins, could you do a "cat /proc/yaffs" and post up the section for the "system" partition? (You need /system to be mounted when you run that command).
Here's what mine looks like after performing an erase with fastboot, booting into Amon_RA, and then mounting it:
Code:
Device 1 "system"
startBlock......... 0
endBlock........... 1359
totalBytesPerChunk. 2048
nDataBytesPerChunk. 2048
chunkGroupBits..... 0
chunkGroupSize..... 1
nErasedBlocks...... 1359
nReservedBlocks.... 5
blocksInCheckpoint. 0
nTnodesCreated..... 0
nFreeTnodes........ 0
nObjectsCreated.... 200
nFreeObjects....... 96
nFreeChunks........ 86976
nPageWrites........ 0
nPageReads......... 0
nBlockErasures..... 0
nGCCopies.......... 0
garbageCollections. 0
passiveGCs......... 0
nRetriedWrites..... 0
nShortOpCaches..... 10
nRetireBlocks...... 0
eccFixed........... 0
eccUnfixed......... 0
tagsEccFixed....... 0
tagsEccUnfixed..... 0
cacheHits.......... 0
nDeletedFiles...... 0
nUnlinkedFiles..... 0
nBackgroudDeletions 0
useNANDECC......... 1
isYaffs2........... 1
inbandTags......... 0
I wonder what your "nRetireBlocks" count is.
I only poked around in the HTC "msm_7k" kernel code a little while ago for some clues, so I'm no expert. There does not seem to be any useful knobs to turn by using mount options.
Because Flash filesystems have to deal with new bad pages as they develop, I'll bet the phone could be completely fixed if there was a way to clear the bad pages - ( if they were actually bad, then on the first write use the write would fail, the pages would be marked bad, and the FS driver would recover gracefully - just as normally happens).
But as you say, that would probably require a custom kernel at the minimum with patches to the mtd driver. I do wonder if the kernel driver for the MTD device exposes any hooks (ioctls, etc) that would let you write a (privileged) userspace app which could wipe the raw pages status info.
This YAFFs doc suggests that certain tuning operations can be performed by writing options to /proc/yaffs, including control of tracing. One of the things that seems possible to control is the number of write attempts per page.
I'll have a look at your URL; no promises, though.
bftb0
[ Edit ] PS - do you have any idea what your friend did to get the phone in this state? Maybe flashing a ROM with really, really low battery? It seems hard to believe that an actual hardware problem occurred - moreover, this is not the first phone where very similar symptoms were exhibited.
I'm wondering if a busybox with mtd-utils compiled in might be of some assistance; in particular the "flash_eraseall" tool. (Perhaps use it with the "-N" option?)
lookit recent versions of the "flash_erase.c" code (excerpted from above Git link):
Code:
static void display_help (void)
{
printf("Usage: %s [options] MTD_DEVICE <start block> <block count>\n"
"Erase blocks of the specified MTD device.\n"
"Specify a count of 0 to erase to end of device.\n"
"\n"
" -j, --jffs2 format the device for jffs2\n"
[COLOR=green][B] " -N, --noskipbad don't skip bad blocks\n"[/B][/COLOR]
" -u, --unlock unlock sectors before erasing\n"
" -q, --quiet display progress messages\n"
" --silent same as --quiet\n"
" --help display this help and exit\n"
" --version output version information and exit\n",
PROGRAM_NAME);
}
(I don't have that version of busybox - I see references made to it in a few posts here on XDA, but I don't know it's origin or where to get it)
bftb0
[ Edit ] looked around for a bit and couldn't find anything pre-built; looks like you might have to build mtd-utils using the NDK for Android. Time for bed for me; here's the link to the mtd-utils project.
i found out that my friend installed rom manager n clockwork recovery and did a flash that failed then ran the 2.1 ruu thinking it would fix it. and that's how the phone got to the state i started with.
i actually got a rom to flash (kinda) with some info from that link i posted. i patched my recovery with files from that link which gave it a custom mtd (table) , i shrunk cache and used the extra space to make up for the bad blocks in system and bind mounted cache to and ext partition on my sd card... and all would be great BUT i realized that the boot partition is corrupt too.. ( which makes sense, since clockwork is known to corrupt both)
so my solution was to flash boot.img to recovery and just boot normally with volup+powerand use amon ra by "fastboot boot " if i need to.
but i cant flash the zip file that patches the kernel to boot using the custom mtd because it's script copies,unpacks,patches then repacks boot.img from /boot but my boot.img is on recovery so im either going to have to edit the .sh in the zip or have someone do the whole custom mtd thing and use the same mtdpartmap.txt and have them nandbackup then give me the boot.img from the backup folder so i can flash it to recovery.
OR have someone manually patch my boot.img file... but i highly doubt i'm going to be able to figure that out or find anyone todo it.
and i'll post the system section of that command in a second.
SoSicWiTiT said:
i found out that my friend installed rom manager n clockwork recovery and did a flash that failed then ran the 2.1 ruu thinking it would fix it. and that's how the phone got to the state i started with.
i actually got a rom to flash (kinda) with some info from that link i posted. i patched my recovery with files from that link which gave it a custom mtd (table) , i shrunk cache and used the extra space to make up for the bad blocks in system and bind mounted cache to and ext partition on my sd card... and all would be great BUT i realized that the boot partition is corrupt too.. ( which makes sense, since clockwork is known to corrupt both)
so my solution was to flash boot.img to recovery and just boot normally with volup+powerand use amon ra by "fastboot boot " if i need to.
but i cant flash the zip file that patches the kernel to boot using the custom mtd because it's script copies,unpacks,patches then repacks boot.img from /boot but my boot.img is on recovery so im either going to have to edit the .sh in the zip or have someone do the whole custom mtd thing and use the same mtdpartmap.txt and have them nandbackup then give me the boot.img from the backup folder so i can flash it to recovery.
OR have someone manually patch my boot.img file... but i highly doubt i'm going to be able to figure that out or find anyone todo it.
and i'll post the system section of that command in a second.
Click to expand...
Click to collapse
I was going to say, holy crap that's a lot of work - but then I've been struggling for a couple hours trying to build mtd-utils (or at least "flash_erase"). I've got all the Makefiles happy (by dropping non-essential parts of the build that require "libuuid"), but now I'm struggling with the linker/toolchain issues to try to avoid the hassles of dynamic link libraries for Amon_RA.
I still think that whatever it is that Clockwork does to get all those flash pages marked as if they are bad is a software error or some sort - so that if you can get
flash_eraseall -N
to do its thing on mtd3, you will recover all those "bad" pages in the system partition. (It is hard to believe that massive physical damage to eeprom would only show up in one or two logical partitions).
Cheers.
bftb0
FWIW,
SoSicWiTiT said:
OR have someone manually patch my boot.img file... but i highly doubt i'm going to be able to figure that out or find anyone todo it.
Click to expand...
Click to collapse
Have a look at this android-dls.com tutorial if you haven't already seen it. Use "split_bootimg.pl" to split apart the boot image into the kernel and compressed ramdisk, and then the ramdisk is just a gzipp'ed "cpio" archive.
The hardest bit about this is finding a verstion of "mkbootimg" - there are some floating around on XDA, or you can build it from the github sources.
It's not too bad, the only secret sauce is the load address for the Eris, which is 0x11200000
This is an excerpt from a shell script I use for repacking boot images - it's the essential part (everything else in the script is just glue).
Code:
mkbootimg --kernel ${_KFIL} --ramdisk new-${_RAMDGZ} --cmdline 'no_console_suspend=1 console=null' --base 0x11200000 --output new-${_BNAM}
i edited the shell script thats supposed to patch it to the best of my abilities (changed all boot.img txt to recovery.img) and it has mkbootimg and everything it needs in the zip, so im going to replace the script in the zip and try flashing it...
and something weird just happened.. i forgot i put boot.img for my rom on /recovery . so in shell just now, i typed reboot recovery expecting amon RA and the phone booted into the os???
even though i patched amon ra with custom mtd to install the rom ( system :300,000 - enough to skip bad blocks, cache: 30,000 ) my boot.img is mtd is set to see 176,000 right?
EDIT
i think i flashed that zip with my version of the script earlier to see what happened and i guess it worked..
Code:
C:\droid\tools>adb shell
sh-3.2# df /system
df /system
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mtdblock3 307200 229296 77904 75% /system
sh-3.2# df /cache
df /cache
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mtdblock4 61440 36500 24940 59% /cache
sh-3.2# df /data
df /data
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mtdblock5 101888 2608 99280 3% /data
sh-3.2#

[Q] YP-G1CWY/XAA stuck at system recovery after failed backup[FIXED]

After unboxing my SGP 4.0(USA) I applied Steve's kernel which I cannot recommend enough. Anyway, I was so happy with it that I decided to try Klin's Klassic ROM. In Klin's instructions he stresses to make a backup via CWM prior to flashing so I booted into CWM, had my device create a backup, then rebooted. I ended up in bootloops like others have experienced.
Before anyone flips out on me, yes I was fully aware that Steve said, "NOTE: Don't use ROM Manager". I did not use the Rom Manager app. I booted into CWM and felt I was safe in doing so. No experimentation took place. I made a backup to the internal storage and rebooted.
Anyway, I was getting bootloops so I tried the fix in Hyperrunner's thread. I followed the instructions. The first portion of his recommended fix did not work so I proceeded to step two where I included the pit file and followed the instructions verbatim. I was stoked when I saw that his steps meshed with what I was seeing on my screen to include the booting into Recovery Mode. I Wiped Data and Wipe Cache. The data wipe got rid of a bunch of errors. The cache wipe did not.
I am now stuck in Android system recovery <3e> with the following errors:
-- Copying media files...
E:failed to mount /dbdata (Invalid argument)
E:copy_dbdata_media:Can't mount /dbdata
your storage not prepared yet, please use UI menu for format and reboot actions
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Successfully applied multi-CSC.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
So I'm stuck in system recovery with the options to:
reboot system now(Done several times)
apply update from sdcard(Have not seen that discussed)
wipe data/factory reset(Did that. It cleared some errors.)
wipe cache partition(Cache errors persist)
I cannot get the device to Download Mode, into the mode with the PC and phone), or connect via Odin. I saw this thread about getting back to download mode but it is for the 5.0 and I'm looking for help as to what my next step should be.
Thanks for your time.
[UPDATE]
1. I purchased a jig(link further down) and the jig got me into "Downloading..." mode
2. Once in download mode I flashed a ROM and pit file as from Hyperrunner's thread(again, link further down)
3. Using Yaph's experience on AnythingButIpod I flashed Steve's kernel again and gained access to CWM
4. I tried using the restore I was making before the bootlooping started and it went through but I am still stuck in CWM
[UPDATE 2]
All fixed. Big thanks to everyone, especially Zaclimon!
SGP4isokay said:
After unboxing my SGP 4.0(USA) I applied Steve's kernel which I cannot recommend enough. Anyway, I was so happy with it that I decided to try Klin's Klassic ROM. In Klin's instructions he stresses to make a backup via CWM prior to flashing so I booted into CWM, had my device create a backup, then rebooted. I ended up in bootloops like others have experienced.
Before anyone flips out on me, yes I was fully aware that Steve said, "NOTE: Don't use ROM Manager". I did not use the Rom Manager app. I booted into CWM and felt I was safe in doing so. No experimentation took place. I made a backup to the internal storage and rebooted.
Anyway, I was getting bootloops so I tried the fix in Hyperrunner's thread. I followed the instructions. The first portion of his recommended fix did not work so I proceeded to step two where I included the pit file and followed the instructions verbatim. I was stoked when I saw that his steps meshed with what I was seeing on my screen to include the booting into Recovery Mode. I Wiped Data and Wipe Cache. The data wipe got rid of a bunch of errors. The cache wipe did not.
I am now stuck in Android system recovery with the following errors:
-- Copying media files...
E:failed to mount /dbdata (Invalid argument)
E:copy_dbdata_media:Can't mount /dbdata
your storage not prepared yet, please use UI menu for format and reboot actions
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Successfully applied multi-CSC.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
So I'm stuck in system recovery with the options to:
reboot system now(Done several times)
apply update from sdcard(Have not seen that discussed)
wipe data/factory reset(Did that. It cleared some errors.)
wipe cache partition(Cache errors persist)
I cannot get the device to Download Mode, into the mode with the PC and phone), or connect via Odin. I saw this thread about getting back to download mode but it is for the 5.0 and I'm looking for help as to what my next step should be.
Thanks for your time.
Click to expand...
Click to collapse
Adb should work in recovery; type Adb reboot download and you should be in download mode. In download mode you have to flash zaclimon's full recovery rom for the 4.0.
Link: http://forum.xda-developers.com/showthread.php?p=23290249
Sent using Tapatalk
klin1344 said:
Adb should work in recovery; type Adb reboot download and you should be in download mode. In download mode you have to flash zaclimon's full recovery rom for the 4.0.
Link: http://forum.xda-developers.com/showthread.php?p=23290249
Sent using Tapatalk
Click to expand...
Click to collapse
Thank you. I've never worked with Android Debug Bridge but it looks drop dead simple from Androidsamurai's guide, so I'll give it a go along with Zaclimon's work. Much appreciated.
have you flashed the stock recovery for the 4.0? or did you already fix it?
minimeofctown said:
have you flashed the stock recovery for the 4.0? or did you already fix it?
Click to expand...
Click to collapse
I haven't flashed anything yet. I just downloaded the guide, the All In One tool, and the Google USB drivers. I'm trying to load the drivers now.
SGP4isokay said:
I haven't flashed anything yet. I just downloaded the guide, the All In One tool, and the Google USB drivers. I'm trying to load the drivers now.
Click to expand...
Click to collapse
For ADB you need samsung drivers not google's
Link to samsung drivers: http://forum.xda-developers.com/showthread.php?t=961956
zaclimon said:
For ADB you need samsung drivers not google's
Link to samsung drivers: http://forum.xda-developers.com/showthread.php?t=961956
Click to expand...
Click to collapse
Thank you. Unfortunately my Windows XP machine is not recognizing my Galaxy Player as anything other than a two drive mass storage device(with the "Safely Remove Hardware" icon in the system tray). The command adb devices returns
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Click to expand...
Click to collapse
With nothing following.
SGP4isokay said:
Thank you. Unfortunately my Windows XP machine is not recognizing my Galaxy Player as anything other than a two drive mass storage device(with the "Safely Remove Hardware" icon in the system tray). The command adb devices returns
With nothing following.
Click to expand...
Click to collapse
Ensure that Usb debugging is enabled: settings-->applications-->developpment-->enable USB debugging.
also ensure that you don't turn on USB mass storage (which means the little android remains green.) Then try again. (Before trying again do this command: adb kill-server.
SGP4isokay said:
Thank you. Unfortunately my Windows XP machine is not recognizing my Galaxy Player as anything other than a two drive mass storage device(with the "Safely Remove Hardware" icon in the system tray). The command adb devices returns
With nothing following.
Click to expand...
Click to collapse
youll have to have usb debugging on. it might give you that at first. just input the command again.
zaclimon said:
Ensure that Usb debugging is enabled: settings-->applications-->developpment-->enable USB debugging.
also ensure that you don't turn on USB mass storage (which means the little android remains green.) Then try again. (Before trying again do this command: adb kill-server.
Click to expand...
Click to collapse
Yeah, I saw that I needed debugging on when I started going through Androidsamurai's guide. I neglected to enable that before I tried making a backup and now there appears to be no way to enable it since I am stuck in "Android system recovery". A little Googling leads me to believe that any effort to recover at my device hinged on that being enabled.
SGP4isokay said:
Yeah, I saw that I needed debugging on when I started going through Androidsamurai's guide. I neglected to enable that before I tried making a backup and now there appears to be no way to enable it since I am stuck in "Android system recovery". A little Googling leads me to believe that any effort to recover at my device hinged on that being enabled.
Click to expand...
Click to collapse
might wanna invest in one of these(; http://www.ebay.com/itm/Micro-USB-J...ccessories&hash=item3372a56243#ht_1175wt_1141
mine came in. im getting it tomorrow hopefully. so if you wanna wait until i test if it works then ill let you know if its safe to buy
minimeofctown said:
might wanna invest in one of these(; http://www.ebay.com/itm/Micro-USB-J...ccessories&hash=item3372a56243#ht_1175wt_1141
mine came in. im getting it tomorrow hopefully. so if you wanna wait until i test if it works then ill let you know if its safe to buy
Click to expand...
Click to collapse
Thanks! I'll wait for news from you. I'm in no rush and this experience has been a pretty decent learning opportunity.
SGP4isokay said:
After unboxing my SGP 4.0(USA) I applied Steve's kernel which I cannot recommend enough. Anyway, I was so happy with it that I decided to try Klin's Klassic ROM. In Klin's instructions he stresses to make a backup via CWM prior to flashing so I booted into CWM, had my device create a backup, then rebooted. I ended up in bootloops like others have experienced.
Before anyone flips out on me, yes I was fully aware that Steve said, "NOTE: Don't use ROM Manager". I did not use the Rom Manager app. I booted into CWM and felt I was safe in doing so. No experimentation took place. I made a backup to the internal storage and rebooted.
Anyway, I was getting bootloops so I tried the fix in Hyperrunner's thread. I followed the instructions. The first portion of his recommended fix did not work so I proceeded to step two where I included the pit file and followed the instructions verbatim. I was stoked when I saw that his steps meshed with what I was seeing on my screen to include the booting into Recovery Mode. I Wiped Data and Wipe Cache. The data wipe got rid of a bunch of errors. The cache wipe did not.
I am now stuck in Android system recovery <3e> with the following errors:
-- Copying media files...
E:failed to mount /dbdata (Invalid argument)
E:copy_dbdata_media:Can't mount /dbdata
your storage not prepared yet, please use UI menu for format and reboot actions
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Successfully applied multi-CSC.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
So I'm stuck in system recovery with the options to:
reboot system now(Done several times)
apply update from sdcard(Have not seen that discussed)
wipe data/factory reset(Did that. It cleared some errors.)
wipe cache partition(Cache errors persist)
I cannot get the device to Download Mode, into the mode with the PC and phone), or connect via Odin. I saw this thread about getting back to download mode but it is for the 5.0 and I'm looking for help as to what my next step should be.
Thanks for your time.
Click to expand...
Click to collapse
so i have the exact same problem BUT i can access download mode and it is recognized by odin, the next post says to use the zaclimon's recovery rom but it is closed for US. also use ADB but idk if that would apply to my case and if so what do i do exactly because for someone like me its very confusing.
Thank you for any help.
minimeofctown said:
might wanna invest in one of these(; http://www.ebay.com/itm/Micro-USB-J...ccessories&hash=item3372a56243#ht_1175wt_1141
mine came in. im getting it tomorrow hopefully. so if you wanna wait until i test if it works then ill let you know if its safe to buy
Click to expand...
Click to collapse
I purchased a Jig from here(USBJig). With it I was able to get back to the "Downloading..." screen(Android with shovel). I plugged the USB cable in and Windows XP recognized my device. So...hooray!
Vilai said:
so i have the exact same problem BUT i can access download mode and it is recognized by odin, the next post says to use the zaclimon's recovery rom but it is closed for US. also use ADB but idk if that would apply to my case and if so what do i do exactly because for someone like me its very confusing.
Thank you for any help.
Click to expand...
Click to collapse
Indeed, Zaclimon's rom is a No-Go. I have been following Kwipper's "[STOCK ROM]" but it says that, "Your phone should be rooted prior to doing this." I did root my device but I'm so hesitant to do anything at this point that I wanted to check with XDA before I do anything.
I'm going to drop a note in Kwipper's thread and ask for guidance. Vilai, I will update you as I progress. Any other input from XDA posters is obviously welcome.
i actually did that one too a no go for me just gonna wait out what i see here in the coming days.
Vilai said:
i actually did that one too a no go for me just gonna wait out what i see here in the coming days.
Click to expand...
Click to collapse
I found someone who has recovered from these errors but I don't know how to replicate his fix being that this is my first experience with Android/Odin. I will try to contact him and see if I can get a step-by-step repair process.
Here is his last post on the thread I linked just above:
So this is solved!
If anyone gets this kind of error (I think it appears after flashing something with a pit file, even if it is the same you just used), I fixed it by flashing a rom with those inside:
SBL
BOOT (IBL + PBL)
CACHE
DBDATAFS
PARAM
I have the 4.0 US but I took those from a 4.0 international.
PLEASE BE CAREFUL NOT TO USE A ROM WITH zimage & factoryfs INSIDE if you own the us version... if you do a usb jig will still do the trick.
Good to know: the unbrickable resurector does work on the 4.0, check that out if you have a hard brick (no screen response).
Click to expand...
Click to collapse
He mentions at the top of his post that he successfully applied Steve's Kernel to regain Clockwork Mod recovery access so I tried that and now I have CWM working.
[EDIT]
I tried to restore my device from the backup. It seemed to go through successfully(the restore process) but then it just keeps booting into CWM regardless of what I do.
Meh, progress. =- D
SGP4isokay said:
I found someone who has recovered from these errors but I don't know how to replicate his fix being that this is my first experience with Android/Odin. I will try to contact him and see if I can get a step-by-step repair process.
Here is his last post on the thread I linked just above:
He mentions at the top of his post that he successfully applied Steve's Kernel to regain Clockwork Mod recovery access so I tried that and now I have CWM working.
[EDIT]
I tried to restore my device from the backup. It seemed to go through successfully(the restore process) but then it just keeps booting into CWM regardless of what I do.
Meh, progress. =- D
Click to expand...
Click to collapse
I've decided to remake the rom for the US (I will not include bootloaders this time) just /cache /system /dbdata and zImage only. I will post it later today. (your error is the recovery can't mount /cache so reinstall it would work.) I will send you a PM for testing if you want before sending it to the recovery thread.
zaclimon said:
I've decided to remake the rom for the US (I will not include bootloaders this time) just /cache /system /dbdata and zImage only. I will post it later today. (your error is the recovery can't mount /cache so reinstall it would work.) I will send you a PM for testing if you want before sending it to the recovery thread.
Click to expand...
Click to collapse
For Vilai and anyone else wanting a progress report, I tried the ROM supplied by Zaclimon and it cleared all errors in Samsung Recovery but I am still stuck there. Apparently the next step was to try flashing the bootloader but that failed in Odin. I still have access to Samsung Recovery and "Downloading..." mode.
SGP4isokay said:
For Vilai and anyone else wanting a progress report, I tried the ROM supplied by Zaclimon and it cleared all errors in Samsung Recovery but I am still stuck there. Apparently the next step was to try flashing the bootloader but that failed in Odin. I still have access to Samsung Recovery and "Downloading..." mode.
Click to expand...
Click to collapse
I am having the same problem. I get no errors but keep booting into recovery. Tried flashing Steves kernel and it loaded into CWM with no errors. Still no system though.
Hmm, sorry for being late into the game, but I had these exact same errors, back before we really knew what we were doing, lol! I couldn't ever get rid of the errors, but I think that was because I was flashing the wrong partitions, so glad you got rid of them! I'm not sure why it still boots to recovery, I'll stay tuned to see what happens! Let me know if you need anything...
Sent using the XDA app.

[Q] replacing a file in /system/ after phone won't boot

alright i have this problem and i am quite panicking now.
i will set everything straight , i hope someone reading the forums can help me asap !
- have a sgs2 unbranded (hk)
- has ICS 4.0.3 stock rom, rooted.
- i don't remember if usb debug mode was enabled
- i messed up in some way with the file /system/build.prop but there is a backup in /system/ called build.prop.bak
- phone doesn't boot anymore as it's stuck at the logo
- recovery and download modes work however
#need a way to delete the build.prop and replace the bloody file with the one backupped. I would like to avoid having to format the phone as i do not remember when was my last kies backup...
what i tried:
-adb shell: it doesn't work. for some stupid reasons the drivers won't be recognized (i have download android sdk and usb drivers), but when i plug the phone in recovery windows just says Device Unknown and even if i update drivers manually it would say that current ones are functioning so no need to update.
if i connect the phone to usb while it's stuck at boot logo, it would recognize the device through samsung drivers (except MTP of course, that would give error).
in both cases adb shell doesn't list any connected device: even if i kill-server and start-server it still doesn't list anything.
-tried using droid explorer in both frozenboot mode and recovery mode, doesn't see anything.
-tried using that other program called SuperOneClick or something like that, that has a "check drivers" button in advanced: if the phone is in recovery pressing the button doesn't do anyhing; if the phone is in frozenboot it asks to download and install some drivers but when i press yes a message appears with " no more data is available " !
i tried this procedure on both win7x64 and winXPx86: same results. reading around , someone says that adb shell will never work if usb debug is de-actived, like i said i cannot remember if that's the case.
-zip package: i created a package to try and overwrite the file with a custom working one i got. i put the package in the root of the micro sd , put the sd in the phone and booted in recovery.
but when i am in recovery the bloody CWM 5.0.2.7 says error to mount /sdcard, or E: could not mount /sdcard , same if i try to mount/unmount /sdcard. if i go to mount external usb card or whatever it says that a file or a lib (cant remember the exact message) was not found.
i have no more ideas of how to solve this, please be patient :<
edit: is there a way to soft format the system folder so that i don't have to properly wipe all my user data and it only affects the system without other contents?
If adb doesn't work hen you are in trouble, better download some non wipe rom and flash it over the existing rom so that your user data will still be there.
Sent from my GT-I9100 using xda premium
bala_gamer said:
If adb doesn't work hen you are in trouble, better download some non wipe rom and flash it over the existing rom so that your user data will still be there.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
can you expand on this?
give any suggestion/example?
isn't there a soft temp rom for emergencies like this that you can just start, make modifies to fix and reboot (similar to the process to boot ubuntu on windows, fix issues and then restart normal windows? )
i would so like to make adb work.. but how.!!!
probebly will not work but try backing up of your ROM from CWM working or not..then just back up current one...
you can restore apps & data lateron from nandroid backup with some application like titanium backup donated version.
i made a backup . but since the external sd card isn't found by the recovery, now the backup is sitting on the internal memory.
the problem is that, if i flash something with odin now, won't odin wipe everything in the internal memory killing my backup as well?
-marco- said:
i made a backup . but since the external sd card isn't found by the recovery, now the backup is sitting on the internal memory.
the problem is that, if i flash something with odin now, won't odin wipe everything in the internal memory killing my backup as well?
Click to expand...
Click to collapse
nope....it will be there dont worry,
just check one more option, go to storage and mount, there is one option mount usb storage, after connecting your phone to PC just mout that and check, are you able to access the SDcard from the computor ot not, if yes, just copy paste your backup to the computor.
then flash a firmware from ODIN
Did the very same thing myself yesterday.. Most ICS-roms from Samsung is non-wipe, so you can just flash it over again with Odin.. Then you just need to root and make customizations (if any) again
zaheedahmed said:
nope....it will be there dont worry,
just check one more option, go to storage and mount, there is one option mount usb storage, after connecting your phone to PC just mout that and check, are you able to access the SDcard from the computor ot not, if yes, just copy paste your backup to the computor.
then flash a firmware from ODIN
Click to expand...
Click to collapse
nope. i just tried this , and when i "mount /sdcard" it says " Error mounting /sdcard! "
when i try mount USB storage , it says " E: unable to open ums lunfile (no such file or directory) "
mljjlm said:
Did the very same thing myself yesterday.. Most ICS-roms from Samsung is non-wipe, so you can just flash it over again with Odin.. Then you just need to root and make customizations (if any) again
Click to expand...
Click to collapse
could you be more specific on the process ? can you suggest me one to flash with odin ? i need to enter the OS , transfer my backup on my hard disk and then restore the whole thing.
currently my kernel is CF-Root-SGS2_XX_XEO_LPQ-PROPER-v5.4-CWM5.tar
and my firmware is GT-I9100_BRI_I9100ZSLPE_I9100OZSLPE_I9100ZSLPE.tar
-marco- said:
nope. i just tried this , and when i "mount /sdcard" it says " Error mounting /sdcard! "
when i try mount USB storage , it says " E: unable to open ums lunfile (no such file or directory) "
could you be more specific on the process ? can you suggest me one to flash with odin ? i need to enter the OS , transfer my backup on my hard disk and then restore the whole thing.
currently my kernel is CF-Root-SGS2_XX_XEO_LPQ-PROPER-v5.4-CWM5.tar
and my firmware is GT-I9100_BRI_I9100ZSLPE_I9100OZSLPE_I9100ZSLPE.tar
Click to expand...
Click to collapse
you try to reflash once more CF-Root (.TAR)only from odin
then check "E: cant mout...error" is rectified or not.... also check booting or not,
still no hope...you flash the same firmware again and Cf-root, your SD card data will be there for sure as far as our expereicne till now..
first part of your comment: i tried reflashing the kernel; no changes. same errors
second part: shall i try using the same firmware from my previous post then?? not other roms? after that i will put the root and check if internal memory is still there. if it is i will copy it on my hd and restore.
if it is not there anymore..............
so the end of the story.
thanks to anyone who helped.
the resolution was much easier than everything else.
opened odin, pda loaded my same firmware which was the HK stock update to ICS and reflashed.
what it did was apparently and overhaul of the system folder, that's it.
any data was still there, as well as the backup that i did and all my apps etc etc etc.
however especially at first it looked a bit unstable, with processes failing randomly. now it seems it has stabilized a bit, but still when i try to run a Kies backup, the phone kies process dies and the backup gets stopped.
i still don't know how to fix this, but i'll be looking into it.
so, the morale out of this was at least for me: if there is some **** up within the system folder just reflash the same rom installed. i feel so stupid now for having made such a fuss when the solution was so easy and straightforward
NICE that you finaly came across and able to boot , now you make the Titanium back of your all apps and data transfer to PC....forget the system data.
and move to a nice stable ROM
"Unfortunately, wssyncmlnps has stopped"
anybody knows about this?

[SOLVED] Springboard problem, VERY STRANGE, please help

T-Mobile Springboard S7-303u
Was on S7-301u stock, works perfectly
Tried to update SuperSU from CWM
I might messed up and mis-flashed the CM10.1 Sep.10 by after_silence
http://forum.xda-developers.com/showthread.php?t=2045808
Rebooted, stuck at the Huawei logo screen (logo, instead of boot animation)
dload folder stock recovery, still stuck at the Huawei logo
Fastboot fine, free to flash recoveries
Formatted everything in TWRP, flashed CM10.1
Booted into system perfectly, IMEI/MAC all gone
Reflashed several times, still only CM10.1 works, with IMEI CHANGED!!!!!!
IMEI SV: 00
SIM lock also relocked (previously unl*cked might be related to changed IMEI)
Even with the T-Mobile SIM, can call/text/HSPA+
Correctly reads SIM operator, blank Net operator
Additional observations:
Only cm10.1 kernel will boot system
With stock kernel + cwm/twrp, cannot manipulate internal storage (system/data/cache...)
A white screen right before booting into recovery
TWRP keeps saying "Unknown File System: datamedia" "Updating partition details..."
It looks to me:
1) internal storage is either collapsed or changed into some different format (only accessible by cm10.1 kernel)
2) to the hell of it I cannot understand where does the different IMEI come from
3) collapsed radio files? (ADB pushed Tmobile stock before flashing cm10.1)
Please kindly input. I do not care about stock ROM, I just want my original IMEI back, want correct Net Operator, want SIM lock gone. Ideally the storage is restored, so that it is back to normal...
Many thanks to all!
Similar stories:
http://forum.xda-developers.com/showthread.php?p=38363578
441Excelsior said:
hi all, my friend got mediapad and he wanted custom rom so I flashed twrp recovery and his tablet became bricked, it shows huawei logo, then white screen and then after few seconds it shuts down, I tried to restore my backup to his tablet (CM10.1) via twrp and then it booted without problems but when I do wipe data/actory reset, the white screen and bootloop appears again, where is the problem? in twrp recovery? should I choose cwm for his device? twrp shows error "E: unknown filesystem datamedia" (also on my device but mine works without problems)
thanks for any help
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=37663928&postcount=48
netfortius said:
Just a follow-up to my earlier "used twrp to wipe everything": re-applied (i.e.
$ fastboot flash recovery twrp.img
with the trwp.img from auto_recovery, but booting the system still goes through the same process:
teamwin logo, then:
E:Unable to mount '/data'
E:Unable to recreate /data/media folder
E: Unknown File System: 'datamedia'
Updating partition details...
E:Unable to mount '/data'
E:Unable to mount internal storage
E:Unable to mount /data/media during GUI startup
E:Unable to locate page (main2)
Formatting Cache using make_ext4fs...
Done
E:Unable to mount /data when trying to read settings file
E:Unable to mount '/data'
After the above, if I power down and back up, I go back to log screen, then immediately "Encryption unsuccessful", with the two options:
"Reset tablet"
and
"Encrypt tablet" ... choosing the latter asks for a key which I do not have. Choosing the former goes to ... you guessed:
teamwin logo, then
E:Unable to mount '/data'
E:Unable to recreate /data/media folder...
Any ideas how to recover from this?
Click to expand...
Click to collapse
maybe there are 2 different hardware versions of mediapad
441Excelsior said:
maybe there are 2 different hardware versions of mediapad
Click to expand...
Click to collapse
This might not be the case because the stock firmware was once working...
but if there are 2 versions of mediapad, CM could have support for only one....it can be something like on my HTC Desire S (first models have sony displays and second made in 2012 have hitachi mddi displays) - I have version with MDDI display and therefore CM does not boot on my device but stock firmware works on both versions...so maybe SU-303u is a bit different than SU-301u
441Excelsior said:
but if there are 2 versions of mediapad, CM could have support for only one....it can be something like on my HTC Desire S (first models have sony displays and second made in 2012 have hitachi mddi displays) - I have version with MDDI display and therefore CM does not boot on my device but stock firmware works on both versions...so maybe SU-303u is a bit different than SU-301u
Click to expand...
Click to collapse
This might not be my situation:
Before crash:
Stock works / cm works
After crash:
Stock not working / cm works with wrong IMEI
you said that you got message about unsuccessfull encryption, why did you wanted to encrypt your device? maybe it failed and now partitions are unaccessible or corrupted
441Excelsior said:
you said that you got message about unsuccessfull encryption, why did you wanted to encrypt your device? maybe it failed and now partitions are unaccessible or corrupted
Click to expand...
Click to collapse
That's not what I said, but some quotes from others...
I never tried to encrypt, but I will try to encrypt and decrypt and see if it helps.
you can try flash stock rom via fastboot manually every partition
441Excelsior said:
you can try flash stock rom via fastboot manually every partition
Click to expand...
Click to collapse
Is there any detailed instruction of how to do this? I tried fastboot push of a bunch of files from T-Mobile stock rom, but it did not help.
Not sure if it is the same thing as flashing partitions...
unzip the stock rom somewhere, boot tablet into fastboot mode, connect usb, then open cmd, change working dir to dir with unpacked zip and via command 'fastboot flash <partition> <filename>' flash every file, partition names are the same as files names (but without extension)
441Excelsior said:
unzip the stock rom somewhere, boot tablet into fastboot mode, connect usb, then open cmd, change working dir to dir with unpacked zip and via command 'fastboot flash <partition> <filename>' flash every file, partition names are the same as files names (but without extension)
Click to expand...
Click to collapse
Tried and did not help. This is actually what dload folder is exactly doing...
Now it is not the contents in those partitions are corrupted, but the partitions themselves are corrupted. Pushing recovery files in whatever way won't fix partitions...
Problem solved by luck.
Flashed TMO stock
then S7-302u stock
booted into system
said "last encryption failed, encrypt again or reset?"
chose reset
then everything back to normal
never tried to encrypt the tablet
not sure what happened.
might be some bug in the stock S7-301u ROM
which told the tablet to do crazy things.
Congrats :good:
Can you share your both files which makes you happy

[Q] SGPT111us/S stuck on boot... ?

I apologize in advance for posting this kind of thread for the 100th time (as I've read similar ones around). I still couldn't find one that may have a solution. I'm not an Android user, so this is all new to me. I got this Sony Tablet S stuck on a bootloop. I can't do anything but enter the hard reset/recovery screen I think it's called... ? I figured maybe re-installing its firmware from the SD Card would do, but I don't know which one it had before (it's a friends tablet that I'm attempting to fix). I think it may be one called Ice Cream Sandwich since I read it on some other thread. Where can I find it and how can I do this? Is there a go-to for-dummies kind of guide? haha. Sorry. I'm really lost when it comes to rom talk and whatnot, so be gentle, lol.
Thank you for reading. Don't mean to waste anyone's time.
Attached a picture, just in case.
Don't judge me for this being my first post. I probably created this account, left it laying around and never came back. I just tried it cause it's my usually my username and it was taken. Found out it really was mine. :/
Click to expand...
Click to collapse
lindapr said:
I apologize in advance for posting this kind of thread for the 100th time (as I've read similar ones around). I still couldn't find one that may have a solution. I'm not an Android user, so this is all new to me. I got this Sony Tablet S stuck on a bootloop. I can't do anything but enter the hard reset/recovery screen I think it's called... ? I figured maybe re-installing its firmware from the SD Card would do, but I don't know which one it had before (it's a friends tablet that I'm attempting to fix). I think it may be one called Ice Cream Sandwich since I read it on some other thread. Where can I find it and how can I do this? Is there a go-to for-dummies kind of guide? haha. Sorry. I'm really lost when it comes to rom talk and whatnot, so be gentle, lol.
Thank you for reading. Don't mean to waste anyone's time.
Attached a picture, just in case.
Click to expand...
Click to collapse
My signature faq thread and its links
Sent from my HTC One using xda app-developers app
stifilz said:
My signature faq thread and its links
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
When I try to install from SD Card, it says "E:failed to mount /sdcard (no such file or directory)"
It's the only thing on your FAQ that I tried, since it's the "brick" thing that I think is where I'm at.
Also, (don't know if this would help) tried using the ADB Driver Installer but the drivers are not installing either... I went to the device manager and tried to do it manually, didn't work either. Android Composite ADB Interface "The hash file for the file is not present for the specified catalog file. The file is likely corrupt or the victim of tampering".
Unfortunetly i have the same issue! :/ and now i dont know to do..
Generaly my tablet s stuck's on bootloop (sony logo)
I can enter recovery mode (with some errors.. cant find, cant mount etc.)
When im picking flash from SDCard tablet says E:/ cant mount /sdcard
and then shows empty card :/
PLS help!
lindapr said:
When I try to install from SD Card, it says "E:failed to mount /sdcard (no such file or directory)"
It's the only thing on your FAQ that I tried, since it's the "brick" thing that I think is where I'm at.
Also, (don't know if this would help) tried using the ADB Driver Installer but the drivers are not installing either... I went to the device manager and tried to do it manually, didn't work either. Android Composite ADB Interface "The hash file for the file is not present for the specified catalog file. The file is likely corrupt or the victim of tampering".
Click to expand...
Click to collapse
The sd card must be fat32 for the device to see it
Use blue chips auto installer for adb
xperia m c1905 stock rooted lb
and sony XTS rooted stock j.b thanks djrbliss
dex9mm said:
The sd card must be fat32 for the device to see it
Use blue chips auto installer for adb
xperia m c1905 stock rooted lb
and sony XTS rooted stock j.b thanks djrbliss
Click to expand...
Click to collapse
SD CARD is formated in FAT32 but still no luck:
E:fail to read boot logo flag
E: can'T OPEN /DEV/block/mmblk0p5
(no such file or directory)
E: failed to mount /cache
E: cant mount /cache/recovery/command
E: failed to mount /cache
E: failed to mount /cache
E: failed to mount /sdcard
its in Android system recovery REV 29 (3e)
Ok. I have installed ADB drivers and now i can see device but adb shell its not working - no sh
generaly its seams that kernel and recovery partition stay on this tablet :/
Anyone know how to recover?

Categories

Resources