TLDR: Phone was bricked revived it now stuck with generic IMEI
Ok so basically my GS3 got bricked dont know exactly why but in recovery it said e: failed to mount /efs (Invalid argument) i was able however to revive it with this thread post #4 ( http://forum.xda-developers.com/showthread.php?t=2204960 ) but now my IMEI is "generic" 004999010640000 and now i cant connect to the network. Im on a mac and the only tutorials ive seen are for windows. my question is is there anyway to change it from the phone itself or on a mac? Sorry if this has been asked before but if anyone can point me in the right direction that would be great.
PS i know changing your IMEI is HIGHLY illegal but i just want to change it back to the original one on the back of the phone.
You're #2 today and #1073453 in total, asking for help with 00499... issue! Not nice...
Use the flipping search bar! :/
Im on a mac...
oh im sorry but if you read the whole thing IM ON A MAC so anyway to fix this would be great...
djembey said:
You're #2 today and #1073453 in total, asking for help with 00499... issue! Not nice...
Use the flipping search bar! :/
Click to expand...
Click to collapse
Restore your backed up EFS folder through whatever method you used .
No backup then a Samsung service centre .
jje
Ok so i have a backup but its the coorrupted one... anyway to open up the .img and copy the files manually on a mac? sidenote when i restore the corrupted one im in a boot loop
JJEgan said:
Restore your backed up EFS folder through whatever method you used .
No backup then a Samsung service centre .
jje
Click to expand...
Click to collapse
Sorry not a clue don't even know how to switch a Mac on .
jje
If your EFS dump is a full partition dump (it being .img suggests that), you can simply write it back in recovery with:
Code:
umount /efs
dd if=/sdcard/yourefs.iso of=/dev/block/mmcblk0p3
reboot
If that fails or throws errors, repeat the steps in the tutorial you linked to re-create an empty EFS partition.
By the way /efs is an EXT4 partition so neither Windows nor Mac (or any other BSD-derivate) are natively capable of reading it, only Linux computers (read: Ubuntu, ...) or specialized tools that simulate filesystem drivers are able to do so.
so i tried that and wasnt able to boot past the i9300 screen. any other suggestions?
d4fseeker said:
If your EFS dump is a full partition dump (it being .img suggests that), you can simply write it back in recovery with:
Code:
umount /efs
dd if=/sdcard/yourefs.iso of=/dev/block/mmcblk0p3
reboot
If that fails or throws errors, repeat the steps in the tutorial you linked to re-create an empty EFS partition.
By the way /efs is an EXT4 partition so neither Windows nor Mac (or any other BSD-derivate) are natively capable of reading it, only Linux computers (read: Ubuntu, ...) or specialized tools that simulate filesystem drivers are able to do so.
Click to expand...
Click to collapse
ugh
Ok so i havent updated this in awhile but here it goes...
First i installed ubuntu on my mac and converted my corrupted EFS partition to .iso and opened it in linux. Anyway no files in there.
Second the samsung service center here in alaska is only for TVs...
Third ill call samsung on monday but dunno what i can do besides save up for another phone or a octopus box or what you call it.
Related
Hi
I've done a bit of searching but can't find anything too specific to what I'm trying to do. Basically we have 10 Android tablets, and I want to make them all standardised e.g. have the same Apps on, configured in the same way (e.g. enterprise wireless network added).
Now the thing is if anyone messes around with them I want a really easy way to restore them to the original config which I've done.
One way I thought was to configure one fully, install Titanium Backup on it, do a full backup of apps/system data etc, and put the backup onto an SD card. Then I already have the base ROM on an SD card so if theres any problems, I can just flash the ROM over it again, install TB, and restore all the data. Would this be suitable to do to duplicate the data onto 10 tablets, and also restore the data if required?
The other thing I looked into was customising a ROM myself, don't want to do anything too tricky it'll just be a case of removing all the preinstalled crap I don't want, preloading the Apps we do want, and if possible preloading the wireless key and getting rid of the first boot initial set up wizard.
PS I've looked at installing CWM and doing whole image backups, but supposedly the tablet isnt supported (its an Ainol Novo 7 Elf 2)
Any advice would be great, hopefully theres some fairly straight forward way of managing this
Thanks
One of the reasons I integrated a full blown GNU/Linux on my devices, was the need to run full and automated backups. If you are looking into the possibility making a custom ROM, this might be a solution for you as well. I'm using BackuPC to run backups nightly, backing them up as any other GNU/Linux machine (using tar over ssh).
See the link in my signature for more information about this.
kuisma said:
One of the reasons I integrated a full blown GNU/Linux on my devices, was the need to run full and automated backups. If you are looking into the possibility making a custom ROM, this might be a solution for you as well. I'm using BackuPC to run backups nightly, backing them up as any other GNU/Linux machine (using tar over ssh).
See the link in my signature for more information about this.
Click to expand...
Click to collapse
Hi
Thanks for the reply, not too sure this would be the right option for us. I don't really need to take nightly backups, I just need to make a backup of a preconfigured image, and then put that image onto 10 other devices. Then I want to keep the original backup and have an easy way to restore it onto any devices which have been messed up. Sort of like image cloning for PCs, I want to prepare a base image, and then flash it over all the devices.
fro5tie said:
Hi
Thanks for the reply, not too sure this would be the right option for us. I don't really need to take nightly backups, I just need to make a backup of a preconfigured image, and then put that image onto 10 other devices. Then I want to keep the original backup and have an easy way to restore it onto any devices which have been messed up. Sort of like image cloning for PCs, I want to prepare a base image, and then flash it over all the devices.
Click to expand...
Click to collapse
Ok, I see. Compile the image to you likings (boot image and system partition), and then flash it using fastboot onto you devices.
Hi
Does anyone have any more thoughts on this?
I have experimented with Titanium Backup and this seems to work quite well. I have installed a ROM, and customised it e.g. installed the apps I need and configured the apps, wireless settings and home screens etc. Then I do a full apps + system backup in TB to my SD card.
Then the plan is, I can reflash the ROM onto the other device, install TB and then restore this backup. This saves my user state and wireless settings etc.
Only problems is when I flash the ROM, I have to go through all the initial set up again and also remove some preinstalled apps which I dont want. Any ways around this?
There must be something I'm missing. Why don't you install the device, walk through the setup, remove the bloatware you don't want and then dumps the disk partitions into images you flash the other devices with using fastboot? This way you'll get'em cloned, isn't it this you want..?
Of course there's still some tinkering needed once restored/cloned, such as giving them individual Google accounts etc, but you can easily fix this without re-running the setup wizard.
kuisma said:
There must be something I'm missing. Why don't you install the device, walk through the setup, remove the bloatware you don't want and then dumps the disk partitions into images you flash the other devices with using fastboot? This way you'll get'em cloned, isn't it this you want..?
Of course there's still some tinkering needed once restored/cloned, such as giving them individual Google accounts etc, but you can easily fix this without re-running the setup wizard.
Click to expand...
Click to collapse
Hi
Yes that's what I want to do! How would I go about dumping the disk into an image and then flashing?
fro5tie said:
Hi
Yes that's what I want to do! How would I go about dumping the disk into an image and then flashing?
Click to expand...
Click to collapse
There are several methods. Some boot loaders (such as nvflash for tegra based devices) can actually read back the disk partitions to a computer via the USB port. You can also on the tablet read the raw mtd device with busybox/dd. I assume you've unlocked the bootloader and gain root access to the device, since this is a requirement for flashing them as well. A third alternative is using busybox/tar, and then recreate the filesystem image using mkyaffs (or if ext3/ext4 even easier, just loopback mount an image on you linux maching to unpack the tar archive to). Once you got the images (system and userdata partitions), you flash the devices with "fastboot flash system system.img" and "fastboot flash userdata data.img". I don't believe you'll need to tamper with the other partitions.
kuisma said:
There are several methods. Some boot loaders (such as nvflash for tegra based devices) can actually read back the disk partitions to a computer via the USB port. You can also on the tablet read the raw mtd device with busybox/dd. I assume you've unlocked the bootloader and gain root access to the device, since this is a requirement for flashing them as well. A third alternative is using busybox/tar, and then recreate the filesystem image using mkyaffs (or if ext3/ext4 even easier, just loopback mount an image on you linux maching to unpack the tar archive to). Once you got the images (system and userdata partitions), you flash the devices with "fastboot flash system system.img" and "fastboot flash userdata data.img". I don't believe you'll need to tamper with the other partitions.
Click to expand...
Click to collapse
Hi
Thanks for the quick reply, much appreciated.
Unfortunately you've lost me a bit here!
Yes the device is rooted, I dont have a linux machine though.
Any chance you'd be able to provide some more specific instructions? The device is a chinese tablet from manufacturer Ainol, the model is a Novo 7 Elf 2. Unfortunately there isn't much discussion on these online so specific help is hard to find!
fro5tie said:
Any chance you'd be able to provide some more specific instructions? The device is a chinese tablet from manufacturer Ainol, the model is a Novo 7 Elf 2. Unfortunately there isn't much discussion on these online so specific help is hard to find!
Click to expand...
Click to collapse
I can provide you specific answers to specific questions, but I have no experience of the tablet in question, so you'll have to do some digging yourself first. Make sure it supports fastboot, investigate what the proprietary bootloader is capable of, see how/if you can obtain an original image etc.
One maybe easier solution, especially if you plan to restore the tablets on a regular basis, is to only make a new boot image to reflash the devices with. The only modification done is that you change the /init.rc script to mount /data and /system from the SDcard instead of from the internal nand disk device.
Once this is done, you'll power up and run the installation wizard and everything on your master tablet. Then power it down, and clone the SDcard. This SDcard now contains everything, so you'll simply restore a device by replacing its SDcard with a copy of this master card. I guess it's easier to clone a SDcard than reflashing several internal partitions. Easier to make the master as well - you don't need to dd or tar them, they are already in "image" format. If you can get hold of the original firmware, this should be quite easy without the need to preserving data from the device itself.
fro5tie said:
Any chance you'd be able to provide some more specific instructions?
Click to expand...
Click to collapse
Issue the commands "cat /proc/mtd" and "mount" on your device at command prompt (e.g. via "adb shell" or the "ConnectBot" terminal app). This shows you if the device allows you to copy the boot image from it. Paste in the output into this thread. If you believe the "clone the tablet via the SDcard" is a good solution for you, the process is in short terms something as below;
Copy the boot image to the sdcard:
# dd if=/dev/mtd/mtd2ro of=/mnt/sdcard/boot.img bs=2048 (device dependent of contents of /proc/mtd)
Remove the sdcard, insert into a computer, split the boot image info kernel + initramfs. Read http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images for instructions about how to work with the boot.img file. I really recommend a GNU/Linux environment for this.
Then edit /init.rc replacing the "mount yaffs2 [email protected] /system" with "mount ext3 /dev/block/mmcblk0p2 /system" for system and data (use p3 for data partition, the device name may be different on your tablet, see mount output).
Create an SDcard with three partitions: #1 vfat (standard), #2 and #3 ext3. Insert into you device and boot it up again.
# mount -t ext3 /dev/block/mmcblk0p2 /root
# cd /system
# tar cf - . | (cd /root ; tar xf - )
# umount /root
# mount -t ext3 /dev/block/mmcblk0p3 /root
# cd /data
# tar cf - . | (cd /root ; tar xf - )
# umount /root
This copies your partitions to the SDcard. Shutdown the tablet again.
Make a new boot.img using the instructions in the link above, using the edited init.rc script.
Now you can non-destrutive give this a try.
Place you tablet in fastboot mode (often vol-up (or vol-down) during power on).
$ fastboot devices
This vill verify the tablet is in fastboot mode. It should be listed. Then:
$ fastboot boot boot.img
Note here, only BOOT the tablet, do NOT use the "flash" keyword. This in case of the image isn't working, you'll just have to restart you tablet, and no harm's done.
Look around. Do a "mount" command. Everything works? Mount shows /data and /system from sdcard? Perfect. Now you can reflash it. Shutdown and flash:
$ fastboot flash boot boot.img
Now the device will use /data and /system from the SDcard every time. Customize your device, and then clone your SDcard and try it in tablet #2 you'll booting with your new boot.img and the cloned SDcard. Verify that #tablet #2 is a perfect clone of tablet #1. It is? Now you can flash the boot,img into all your tablets.
--------------------
But don't forget, there may be other solutions as well, maybe more suitable. This you'll have to investigate yourself.
And the usual disclaimer - you can probably not follow above by the letter. There sure is some obstacle you'll have to overcome, something non-standard, etc.
Also keep the original boot.img file for safekeeping in the case you want to restore the device's boot image some day.
Wow! Thanks for the info! This is really helpful, I need to set aside a bit of time to work through this and have a look. Thanks again its really appreciated, I'll be back with info once I've had chance to give it a go!
I certainly can't offer more detailed info than the fellow from Sweden who seems to really know his stuff...but what about making a nandroid backup of your fully configured reference tablet (I'm assuming all tablets are rooted). Ensure all your tabs have CWM recovery and copy your nandroid file to each one.
If any of your fleet get 'corrupted' you can simply restore the original, fully configured ROM.
In fact that sounds too obvious..likely I missed something about your scenario which precludes this option from consideration!
Good luck mate.
tweeny80 said:
I certainly can't offer more detailed info than the fellow from Sweden who seems to really know his stuff...but what about making a nandroid backup of your fully configured reference tablet (I'm assuming all tablets are rooted). Ensure all your tabs have CWM recovery and copy your nandroid file to each one.
If any of your fleet get 'corrupted' you can simply restore the original, fully configured ROM.
In fact that sounds too obvious..likely I missed something about your scenario which precludes this option from consideration!
Good luck mate.
Click to expand...
Click to collapse
Hi
Yes that was my first thought as well, tablets are rooted yes but there is no CWM for the tablet. Its an obscure Chinese branded tablet.
Unless there is another way to do nandroid backups?
hmm tricky situation. Catch 22 ! From what I know, your best bet is to backup all possible things through Titanium Backup given that you don't have the use of Nandroid backups. You can include wifi settings, messages etc but it's modular & not systemic.
I did a quick google search with no luck - time to upgrade your fleet dude :-0
Best of luck.
Please could somebody tell me if there is any known method for backing up efs/IMEI data that works for the S5830i and if anybody has ever actually successfully restored their IMEI number for this model of phone?
I've read alot of information about differrent methods, although most of them are in the Galaxy S forums and I've seen one post in the Galaxy Ace S5830 forum stating there is currently no known working restore method for the S5830 (but not the S5830i).
Also, apparently (see http://forum.xda-developers.com/showpost.php?p=25718433&postcount=8) you can actually corrupt the /efs partition when backing it up if you are not carefull as it is a hidden partition that is not mounted by default when the phone boots. Apparently, if you don't unmount it after you've backed it up, goodbye /efs partition.
Even if there is no current working restore technique, I would rather backup now to be on the safe side and hope a restore method becomes apparrent in the future as I've already lost my IMEI information once (and managed to get a phone replacement under warranty luckily). I would however prefer to know how I can safely do so first.
Ok, so I've been looking into how to do this for a couple of weeks now and still nothing. Surely somebody must know some information regarding /efs or IMEI data on the s5830i?
I'm in an ADB shell at the moment and I've got an /efs folder in my root directory, but I've looked in this directory and it's currently completely empty (including hidden files). The only thing I can presume is that on my phone /efs is merely a directory that has been created for the specific purpose of acting as a mount point for the actual 'efs partition', which is not actually mounted at the moment for whatever reason.
Issuing the mount command confirms nothing along the lines of an efs partition is mounted. I've had a look in /dev and from searching this forum a bit more, I understand, efs is likely to be /dev/stl# (where # is a digit). So does anybody know which one it is?
I'm not going to do anything silly and start dd'ing it straight off but there must be some way of backing it up safely seeing as it has been done on many other phones. Also any information on when and how it is mounted (by Android OS) and how to mount it safely would be much appreciated even if this is more Android general than my specific model of phone.
I may be speaking to myself in this thread but in case anybody else needs an answer, it looks like Galaxy Toolbox can do an /efs backup and is compatible with the S5830i. See:
http://forum.xda-developers.com/showthread.php?p=25949902
https://play.google.com/store/apps/details?id=com.doky.sgtoolbox
Incidentally, that information seems to imply that the /efs device file is at /dev/bml15, which does exist on my phone, not that I plan on manually interacting with it!
I know this is an old topic and no one showed up here.
But I wanted to come to say to you THANKS! because you really helped me
kitsune0 said:
I know this is an old topic and no one showed up here.
But I wanted to come to say to you THANKS! because you really helped me
Click to expand...
Click to collapse
galaxy toolbox is the solution :good: i already try it ... work fine in restore and backup
terminal emulator
su press enter
busybox dd if=/dev/bml15 of=/sdcard/bml15.img press enter
angel.sea said:
terminal emulator
su press enter
busybox dd if=/dev/bml15 of=/sdcard/bml15.img press enter
Click to expand...
Click to collapse
1. Use SGY Toolbox
2. Use this .
http://forum.xda-developers.com/showthread.php?p=38823212
3. Then at last resort
Use the command given by above person
AW: Is efs/IMEI Backup Possible for S5830i
Yeah thats work for me too :thumbup:
Gesendet von meinem GT-S5830i
Hi,I ended up deleting alot of my pictures off my phone by accident and was wondering if there is a tutorial in linux to recover them?I found this tutorial but i dont have a windows machine on hand to try it out:
http://forum.xda-developers.com/showthread.php?t=1994705
I have searched but havent came up with anything as far as how to do it in linux.I apprecitate the help.thanks
cadogan32 said:
Hi,I ended up deleting alot of my pictures off my phone by accident and was wondering if there is a tutorial in linux to recover them?I found this tutorial but i dont have a windows machine on hand to try it out:
http://forum.xda-developers.com/showthread.php?t=1994705
I have searched but havent came up with anything as far as how to do it in linux.I apprecitate the help.thanks
Click to expand...
Click to collapse
Quite frankly data recovery in linux = major pain in the butt, desperation to recover from a ext4 partition once led me to an app called "photorec" don't be fooled by the name it's a data recovery app, oh I was on Ubuntu and I don't know whether other Linux distro's have this or use it, after going through settings, synaptic, terminal commands *shudder*(it still gives me the creeps) I recovered a corrupted piece of my important data, turns out even a minor use in the partition in question will corrupt most deleted data, so I suggest you use a Windows PC for recovering, it will give same results without taking you through a ride in Hell.
Edit :that windows tutorial is another Hell there is an easier way for you, mount the device in UMS mode in your windows PC run data recovery software like Recuva for the mounted partition.
Sent from my GT-P6200 using xda app-developers app
Yeah sounds like ill stick with the windows method when i get a chance.Thanks for the help!
I was doing a factory reset to clean install one of the CM10.1 release candidates and I went into Mounts and Storage and I accidentally formatted ROM instead of System. Now Cyanoboot keeps going into CWM and won't boot my rom. I flashed a different rom and I also restored from backup but neither did the trick. Any tricks that can get my dear old Nook booted? Any help would be greatly appreciated. (My last resort is one of those lengthy unbrick posts if there's no way to fix it. I've done these before but if there is an easier solution I'd like to try that first.)
I am familiar with adb (and ubuntu if need be).
Do you know the serial number? Like when you use adb, and you type adb devices, it shows a serial number. Did you write it down? I have a backup of the ROM partition and it includes a few files in there containing serial and mac address, etc. The serial number is important for it to boot AFAIK, so I hope you have that somewhere.
sagirfahmid3 said:
Do you know the serial number? Like when you use adb, and you type adb devices, it shows a serial number. Did you write it down? I have a backup of the ROM partition and it includes a few files in there containing serial and mac address, etc. The serial number is important for it to boot AFAIK, so I hope you have that somewhere.
Click to expand...
Click to collapse
I have the serial number (behind the microsd card slot)..but not the mac address
Also, I only wiped the ROM and system partitions. The factory partition is still there untouched and I've read somewhere that it contains a backup of the information in the ROM partition.
adb devices shows a serial number of abcdef123456789.
Not exactly a good sign...Should I try so****e's serial number recovery thing through ubuntu?
If what you had re-formatted by mistake is /rom but your /factory is still intact then not all was lost, as /factory holds romdata.zip which is a backup archive of data files in /rom (see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more elaboration).
What you can try is to flash stock recovery (e.g., flash_stock_recovery.zip from Succulent's repo https://github.com/succulent/acclaim_recovery_sdcard), then do the "8 failed reboots" to trigger a "factory reset to stock".
Can you try to use adb from CWM? Try "adb pull /factory" and see if it copies over the factory folder to your computer.
digixmax said:
If what you had re-formatted by mistake is /rom but your /factory is still intact then not all was lost, as /factory holds romdata.zip which is a backup archive of data files in /rom (see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more elaboration).
What you can try is to flash stock recovery (e.g., flash_stock_recovery.zip from Succulent's repo https://github.com/succulent/acclaim_recovery_sdcard), then do the "8 failed reboots" to trigger a "factory reset to stock".
Click to expand...
Click to collapse
Factory is definitely in tact; only rom was formatted (I figured factory was important so I didn't want to format it.) I'll try this after and let you know. I'm going to manually flash partition 5 onto my nook through adb and see if that can get me up and running.
sagirfahmid3 said:
Can you try to use adb from CWM? Try "adb pull /factory" and see if it copies over the factory folder to your computer.
Click to expand...
Click to collapse
pull: building file list...
0 files pulled. 0 files skipped.
This was through command prompt/adb in Windows 7. Should I try Ubuntu?
topdawg7793 said:
pull: building file list...
0 files pulled. 0 files skipped.
This was through command prompt/adb in Windows 7. Should I try Ubuntu?
Click to expand...
Click to collapse
You need to mount the /factory partition before you can access it.
Why not do it the easy way: just flash stock recovery and let it restore the missing data as part of the "8 failed boots" factory reset process?
digixmax said:
You need to mount the /factory partition before you can access it.
Why not do it the easy way: just flash stock recovery and let it restore the missing data as part of the "8 failed boots" factory reset process?
Click to expand...
Click to collapse
I had no clue it fixed the missing data! Just did it and I'm back to a working nook. Appreciate the help everybody!
So what did you do to finally get it fixed? Flash stock recovery and do the 8 failed reboots method?
sagirfahmid3 said:
So what did you do to finally get it fixed? Flash stock recovery and do the 8 failed reboots method?
Click to expand...
Click to collapse
I know I'm slightly late on this, but I figure I should at least respond so any poor soul who gets into the same situation and sees this thread can have some go-to solution. I never got to do the partition thing through adb (use somebody's ROM partition and change the serial number and mac address to that of my Nook) so I booted an SDcard version of some CM10 nightly and then used the touchscreen firmware flasher to restore to the factory firmware. Then I took out the SDcard and did the 8 reboots thing and that finally fixed it.
NOTE: NEVER GO BACK TO STOCK WHILE ON THE 10-TOUCH FIRMWARE. YOUR TOUCHSCREEN WILL NOT WORK AND YOU WILL EFFECTIVELY BE STUCK UNTIL YOU BOOT OFF AN SDCARD AND RESTORE THE FACTORY TOUCHSCREEN FIRMWARE.
topdawg7793 said:
I had no clue it fixed the missing data! Just did it and I'm back to a working nook. Appreciate the help everybody!
Click to expand...
Click to collapse
lol well now i know wut to do if i accidentally format rom. cheers every1 who helped topdawg :highfive:
So I am stuck in a bootloop and no obvious way out.
US Galaxy Player 4.0
Rooted and been on custom roms for a year now. Problem started after upgraded to latest CM. Tried going back to stock but no luck in resolution. I am able to get into recovery and download mode and flash with odin. I can run adb shell. Just won't boot. The error message I get is as follows:
"E:format_volume: rfs format failed on /dev/block/mmcblk0p2"
In my adb shell I can see that there is no "mmcblk0..." files at all.
I have tried to go through the full stock recovery and used the PIT files and the stock rom through odin. I get the same boot loop and cant get the data to wipe due to the same error. I can flash anything through Odin easily without fail but everything is stuck in boot loop. I just don't seem to have /data to wipe.
There are some other posts around which indicate the Partition may be screwed but I am not sure what it is supposed to look like or the command line syntax to use to correct.
http://forum.xda-developers.com/showthread.php?t=1468213&highlight=wipe+data+shell
I have several nandroid backups on an external location but now I can't get the external card to recognize in CWM so haven't been able to try to revert backwards that way. I have backup of efs and all other stuff just can't seem to get to it.
Anybody with Ideas or direct help are greatly appreciated
map1122 said:
So I am stuck in a bootloop and no obvious way out.
US Galaxy Player 4.0
Rooted and been on custom roms for a year now. Problem started after upgraded to latest CM. Tried going back to stock but no luck in resolution. I am able to get into recovery and download mode and flash with odin. I can run adb shell. Just won't boot. The error message I get is as follows:
"E:format_volume: rfs format failed on /dev/block/mmcblk0p2"
In my adb shell I can see that there is no "mmcblk0..." files at all.
I have tried to go through the full stock recovery and used the PIT files and the stock rom through odin. I get the same boot loop and cant get the data to wipe due to the same error. I can flash anything through Odin easily without fail but everything is stuck in boot loop. I just don't seem to have /data to wipe.
There are some other posts around which indicate the Partition may be screwed but I am not sure what it is supposed to look like or the command line syntax to use to correct.
http://forum.xda-developers.com/showthread.php?t=1468213&highlight=wipe+data+shell
I have several nandroid backups on an external location but now I can't get the external card to recognize in CWM so haven't been able to try to revert backwards that way. I have backup of efs and all other stuff just can't seem to get to it.
Anybody with Ideas or direct help are greatly appreciated
Click to expand...
Click to collapse
This is how we fix that with the Player 5 : http://forum.xda-developers.com/showthread.php?t=2398120&page=4 (read the whole thread from page 4 on)
You'll need to do pretty much the same thing but you need an image from the Player 4.:good:
recrtora above
Thank you Meticulus. I see that you were involved in the thread I referenced too and this is where I figured I needed to go. However this is where I get tripped up. The main issue being that I don't have an image from a 4.0 US player. The thread I linked to had the Intl Player shown... There were even a few requests for the US version later on in the thread.
So- Anyone want to share their US player working partition table?
Is this information contained in the .PIT files somehow?
anyway to retrieve this?
map1122 said:
Thank you Meticulus. I see that you were involved in the thread I referenced too and this is where I figured I needed to go. However this is where I get tripped up. The main issue being that I don't have an image from a 4.0 US player. The thread I linked to had the Intl Player shown... There were even a few requests for the US version later on in the thread.
So- Anyone want to share their US player working partition table?
Is this information contained in the .PIT files somehow?
anyway to retrieve this?
Click to expand...
Click to collapse
As far as I know that's the only way to do it is with the picture.... Be patient, I'm sure someone will post an image...
@zaclimon ???
Needed: out put of fdisk on mmcblk0
Code:
adb root
adb shell
fdisk -l /dev/block/mmcblk0
Then post a screenshot, or just the output.:highfive:
Meticulus said:
As far as I know that's the only way to do it is with the picture.... Be patient, I'm sure someone will post an image...
@zaclimon ???
Needed: out put of fdisk on mmcblk0
Code:
adb root
adb shell
fdisk -l /dev/block/mmcblk0
Then post a screenshot, or just the output.:highfive:
Click to expand...
Click to collapse
Here it is, do note that it's a intl device though too.
zaclimon said:
Here it is, do note that it's a intl device though too.
Click to expand...
Click to collapse
That's definately not what I expected... to see from the 4.0's partition table...
Meticulus said:
That's definately not what I expected... to see from the 4.0's partition table...
Click to expand...
Click to collapse
We only have mmc blocks for the actual storage of the device. The system partition and others are pure raw nand (which is why we use mtd and yaffs2)
Envoyé depuis mon Nexus 7 avec Tapatalk 4
zaclimon said:
We only have mmc blocks for the actual storage of the device. The system partition and others are pure raw nand (which is why we use mtd and yaffs2)
Envoyé depuis mon Nexus 7 avec Tapatalk 4
Click to expand...
Click to collapse
So then, will recreating these partitions solve the OP problem?
Meticulus said:
So then, will recreating these partitions solve the OP problem?
Click to expand...
Click to collapse
Most probably because it will only touch /data and internal storage. Actually this is the first time I see a problem like this for the 4.0.
Envoyé depuis mon Nexus 7 avec Tapatalk 4
So any confidence in the international vs the US version being the same?
Now the next thing is I used the command fdisk to start trying to recreate the partitions using the post instructions you recommended. I did not get an option for "new". I attached the output from the shell command. Tried looking up shell command references on fdisk but is not helping me here. Is it because there is not mmcblk0 at all? I don't seem to be getting into the command mode of the fdisk command.
If I use fdisk -l /dev/block/mmcblk0 I get "no such file or directory"
map1122 said:
So any confidence in the international vs the US version being the same?
Now the next thing is I used the command fdisk to start trying to recreate the partitions using the post instructions you recommended. I did not get an option for "new". I attached the output from the shell command. Tried looking up shell command references on fdisk but is not helping me here. Is it because there is not mmcblk0 at all? I don't seem to be getting into the command mode of the fdisk command.
If I use fdisk -l /dev/block/mmcblk0 I get "no such file or directory"
Click to expand...
Click to collapse
Hmm... Can post a list of /dev/block ?
Code:
adb shell
ls /dev/block
Here you go.
map1122 said:
Here you go.
Click to expand...
Click to collapse
Hmmmmm .... see if you can get here: /sys/bus/platform/devices/s3c-sdhci.0 and post the output
Like so?
map1122 said:
Like so?
Click to expand...
Click to collapse
yes.... I'm not sure what's wrong but id recommend installing a full odin flashable rom...
Not sure what that would be for the 4.0..
Here is another place you can check /sys/bus/platform/devices/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0
Here is the output of that. No further.
I am already on fresh Odin flash. Several attempts actually. I have been able to flash back to Stock (and use PIT) files, access stock recovery. I did this first to think I could restore to OEM. Then flash the Terra-Silent kernel to obtain CWM and the IcyFusion Rom (did this again this morning so I could get adb to link). These are the only Odin flashable that I am aware of for the 4.0. Obviously nothing boots because the issues discussed here.
Thank you.
what does "partition SD Card" in the Advanced and Debugging menu in CWM do?
map1122 said:
Here is the output of that. No further.
I am already on fresh Odin flash. Several attempts actually. I have been able to flash back to Stock (and use PIT) files, access stock recovery. I did this first to think I could restore to OEM. Then flash the Terra-Silent kernel to obtain CWM and the IcyFusion Rom (did this again this morning so I could get adb to link). These are the only Odin flashable that I am aware of for the 4.0. Obviously nothing boots because the issues discussed here.
Thank you.
Click to expand...
Click to collapse
I don't know if those are "full" odin flashable roms.
Try here: http://forum.xda-developers.com/showthread.php?t=1531850
Yes, that is the one I am using to revert to stock and additional PIT. I checked MD5 sums too.
Would this kind of thing be backed up in a nandroid?
map1122 said:
Yes, that is the one I am using to revert to stock and additional PIT. I checked MD5 sums too.
Would this kind of thing be backed up in a nandroid?
Click to expand...
Click to collapse
No, It wouldn't be backed up in android...
I'm betting that the U.S. Odin ROM on that page is not a "full" recovery rom either... I'm downloading right now to check. If it isn't, we need to find out how safe it is to flash an INT version first then flash a USA over it.
On the 5.0, we can do that... and everything is OK but don't know about 4.0...
EDIT: Seem like the only difference is that INT has bootloaders and USA does not. That doesn't help us...