Hello,
I formatted the "pink drive" and choose the FAT32 file system.
This is the type of the original system files??
Thanks
GeoRCZ said:
Hello,
I formatted the "pink drive" and choose the FAT32 file system.
This is the type of the original system files??
Thanks
Click to expand...
Click to collapse
Yes, the Bootloader (pink screen) default file system is FAT32.
In case you lost the bootloader contents, just create a folder called "image" and copy the following files to that:
EMMCBOOT - http://www.mediafire.com/?lb6ifvgk72iru4a
AMSS.MBN - http://www.mediafire.com/?d6r45q6p5gew59v
Recovery.img - http://www.mediafire.com/?57njygc8oianjac
Boot.img - http://www.mediafire.com/?6d5i0714a7o9z97
Hello Katu!
Thanks for the answer yesterday!
Formatted in FAT32, but I'm not sure what the size of the allocation unit.
Can you help me ... again??
Thanks
GeoRCZ said:
Hello Katu!
Thanks for the answer yesterday!
Formatted in FAT32, but I'm not sure what the size of the allocation unit.
Can you help me ... again??
Thanks
Click to expand...
Click to collapse
Sure, leave that to default (i think it's 4096.)
GeoRCZ said:
Hello,
I formatted the "pink drive" and choose the FAT32 file system.
This is the type of the original system files??
Thanks
Click to expand...
Click to collapse
wow...you're extreme DD
katu2006 said:
Yes, the Bootloader (pink screen) default file system is FAT32.
In case you lost the bootloader contents, just create a folder called "image" and copy the following files to that:
EMMCBOOT - http://www.mediafire.com/?lb6ifvgk72iru4a
AMSS.MBN - http://www.mediafire.com/?d6r45q6p5gew59v
Recovery.img - http://www.mediafire.com/?57njygc8oianjac
Boot.img - http://www.mediafire.com/?6d5i0714a7o9z97
Click to expand...
Click to collapse
Helo
Pink drive, Data storage, internal storage, rom, ram... I worked in PC hardware... who can I study the hardware organization of a smartphone like the U8800?
I'm curious
Thanks
katu2006 said:
Yes, the Bootloader (pink screen) default file system is FAT32.
In case you lost the bootloader contents, just create a folder called "image" and copy the following files to that:
EMMCBOOT - http://www.mediafire.com/?lb6ifvgk72iru4a
AMSS.MBN - http://www.mediafire.com/?d6r45q6p5gew59v
Recovery.img - http://www.mediafire.com/?57njygc8oianjac
Boot.img - http://www.mediafire.com/?6d5i0714a7o9z97
Click to expand...
Click to collapse
Helo
My U8800 has also a /image/cust. This /cust has the data and parameters of net operator TMN. Is not necessary?
Thanks
ValenteL said:
Helo
My U8800 has also a /image/cust. This /cust has the data and parameters of net operator TMN. Is not necessary?
Thanks
Click to expand...
Click to collapse
It is required, but in that folder the stock Rom usually backs-up critical stuff... don't delete it or anything!
If you don't have that folder, it's not a tragedy, because a fresh install of a stock Rom will create that folder for you.
katu2006 said:
It is required, but in that folder the stock Rom usually backs-up critical stuff... don't delete it or anything!
If you don't have that folder, it's not a tragedy, because a fresh install of a stock Rom will create that folder for you.
Click to expand...
Click to collapse
Thanks
My error ---> is the /image/cust_data, not /image/cust.
Are the same data there is on phone folder /cust
ValenteL said:
Thanks
My error ---> is the /image/cust_data, not /image/cust.
Are the same data there is on phone folder /cust
Click to expand...
Click to collapse
Yeah, cust_data is the one I was referring at. You'll notice that inside that folder there is another folder with the initial letters from each Stock Rom (for example my is "ee", which stands for Estonia Elisa).
katu2006 said:
Yeah, cust_data is the one I was referring at. You'll notice that inside that folder there is another folder with the initial letters from each Stock Rom (for example my is "ee", which stands for Estonia Elisa).
Click to expand...
Click to collapse
Oh Yes
And in the mine is /cust_data/tmn/pt/ here 9 data folders. (TMN of Portugal)
katu2006 said:
............................
because a fresh install of a stock Rom will create that folder for you.
Click to expand...
Click to collapse
I think the stock Rom will create that if I have de /cust phone folder. It's this folder I must'nt delete.
But now I'm not a stock Rom, I have 3 Oxygen versions, a MIUI and a CM7 backups. I restore one of them wen I want . If I want I can delete /cust and no problems is'n it?
ValenteL said:
I think the stock Rom will create that if I have de /cust phone folder. It's this folder I must'nt delete.
But now I'm not a stock Rom, I have 3 Oxygen versions, a MIUI and a CM7 backups. I restore one of them wen I want . If I want I can delete /cust and no problems is'n it?
Click to expand...
Click to collapse
Do not delete that folder! I wouldn't touch that just for fun...Leave it there, it won't affect your Roms in anyway.
The fact that you can restore Oxygen doesn't have anything with that folder. Your backups for Oxygen etc are on the SD card.
I personally think that some relevant info used by all Roms is actually located there, so I wouldn't delete that folder just for fun.
katu2006 said:
Do not delete that folder! I wouldn't touch that just for fun...Leave it there, it won't affect your Roms in anyway.
The fact that you can restore Oxygen doesn't have anything with that folder. Your backups for Oxygen etc are on the SD card.
I personally think that some relevant info used by all Roms is actually located there, so I wouldn't delete that folder just for fun.
Click to expand...
Click to collapse
Oh yes yes
Now I remember, when I made a backup or restore there are the files /data /system etc. and also /cust. It's important.
Thanks
Related
why when i try to restore this roms it said "MD5 mismatch!"..?
how can i fix this so i can install this roms..?
HAKA posted unwillingly a corrupted zip at first. Make sure you are flashing the new one.
maliceomalice said:
why when i try to restore this roms it said "MD5 mismatch!"..?
how can i fix this so i can install this roms..?
Click to expand...
Click to collapse
When you extracted the file.. He created a folder name [GingerFroyo.1.4.16]
Just open this Folder and inside you will see another folder in the same name..
This is one that you should copy in xrecovery/backup/ folder.. this file contains 4 files..
Chris95X8 said:
HAKA posted unwillingly a corrupted zip at first. Make sure you are flashing the new one.
Click to expand...
Click to collapse
i dont quite understand what u mean by flashing the new one. i download the newest (i think) v1.4.16_2...rite?
malungkot said:
When you extracted the file.. He created a folder name [GingerFroyo.1.4.16]
Just open this Folder and inside you will see another folder in the same name..
This is one that you should copy in xrecovery/backup/ folder.. this file contains 4 files..
Click to expand...
Click to collapse
when i open gingerfroyo folder, i do not see another folder. all i see is 4 files...
maliceomalice said:
i dont quite understand what u mean by flashing the new one. i download the newest (i think) v1.4.16_2...rite?
Click to expand...
Click to collapse
Just make sure you have downloaded the new one. Extract it on your PC and you will have a folder named GingerFroyo 1.4.16
Put that folder in SD > xrecovery > backup
Restore and make full wipe
maybe my download was the problem..i'll try to download it again...thank you for helping
better try to redownload, and see what will happen
maliceomalice said:
when i open gingerfroyo folder, i do not see another folder. all i see is 4 files...
Click to expand...
Click to collapse
I just downloaded the file just now, and when I extracted the file it came with the folder [GingerFroyo.1.4.16].. and inside that folder I saw a folder again in the same name..
this is the folder as just copy in xrecover/backup
yep, there is 4 file..drag the folder again to sd->xrecovery->backup. and put the folder there. reboot with xrecovery, choose back up and restore, select restore->GingerFroyo.1.4.16. after finish installation, make sure u make factory reset (full wipe). then reboot.
maliceomalice said:
when i open gingerfroyo folder, i do not see another folder. all i see is 4 files...
Click to expand...
Click to collapse
maybe you should have a look on the thread with help in flash on http://forum.xda-developers.com/showthread.php?t=921652
hi guys..
im unable to install any video player... nothing works...
pls help....
did you try rock player ?
rtzuiop said:
did you try rock player ?
Click to expand...
Click to collapse
tried every player available on market.. rockplayer, vplayer, moboplayer etc,..
i tried wiping cache also, i think problem is with this rom..
For those of you that don't think you need to read this - you are wrong! I have flashed 100's of ROM's with no issue until the end of last week.
MODERATORS PLEASE STICKY THIS IN A PLACE WHERE EVERYDAY USERS THAT FLASH ROMS WILL SEE IT
I uneventfully flashed a ROM (not important which one because I don't think it has anything to do with particular ROM) and all went well. I went to bed with a working phone and the somehow a reboot happened and awoke with a phone with no signal. The error was saying that there was no SIM card and / or No Network Available.
I finally used HC-kTool app on the Market (used latest version) to Restore an efs.tar file and my phone started working but I had a generic / fake IMEI number -- 004999010640000
If you have backed up your /EFS folder on the root of your phone then all is well. The easiest way is to use Hellcat's HC-kTool to back up your EFS and save a copy on your sdcard and your PC and that way you will not have to go through my misery.
However if you have not BACKED UP your EFS files then you will have issues like I did
Ok so here is what I can tell based on my experience:
Look for any files or folders on your sdcard that have EFS in the name. You might get lucky and look in the /EFS folder on your phone. If the nv_data.bin file has been corrupted the .nv_data.bin.bak might still be OK. If that is the case you may be able to follow this guide: http://forum.gsmhosting.com/vbb/f606/samsung-android-repair-efs-imei-repair-without-box-1348192/
What won't work is any sort of simple copying nv_data.bin from the sdcard to the /EFS folder using Root Explorer - I spent almost an entire weekend trying this.
If your /EFS folder .bak file has been corrupted then in my case I found a folder on my sdcard named EFS_BACKUP that I assume that Clockworkmod has created during some of my ROM flashes (somebody correct me if I'm wrong because otherwise I have no idea how it got there).
In the EFS_BACKUP folder I have a number of files form different dates (I assume of flashes) labelled efs_xxdate.tar.gz
btw you can use these or any .gz file when using HC_kTool tool simply by renaming the file (long press with Root Explorer) to just a .tar file (delete the .gz). HC_kTool uses a file named efs.tar on the root of the sdcard to restore.
In my case I had to extract one of these files by long pressing in Root Explorer and choicing extract. I then went to the extracted folder on the sdcard (using Root Explorer) and found a folder named efs_xxdate and within that a folder named EFS
... again don't get mislead -- simply copying and pasting that file or any other to the root /EFS folder will not work!!
I noticed that there were multiple files in the extracted/efs_xxdate/efs folder but the dates were different. The nv_data.bin and the nv_dat.bin.md5 files were dated the same as the date of the folder BUT the .nv_data.bak file was dated Dec31, 2010
Here's how I restored that file:
1) I extracted the .tar.gz file as above
2) Went to sdcard\extracted\efsxxdate\efs folder and copied the older dated .nv_data.bak to the root of the sdcard using Root Explorer (long press, copy, then paste)
3) Then renamed the .nv_data.bak file to nv_data.bin on the root of the sdcard
3) Then followed these instructions from line 14 on in this post .. http://forum.gsmhosting.com/vbb/f606/samsung-android-repair-efs-imei-repair-without-box-1348192/
14 = at command prompt [ C:\adbtools\ ], type adb shell
15 = type su
16 = type cp /sdcard/nv_data.bin
17 = type rm -rf /efs/nv_data.bin.md5
18 = type exit & exit
19 = REBOOT YOUR PHONE
I'm not sure why this works but EVERY combination of copying and pasting nv_data.bin , .bak, or entire EFS folders suing Root Explorer does NOT work but this above technique did work for me ! Somehow having the .md5 file recreated is the key ??
I hope this helps someone.
BACKUP YOUR EFS -- Hellcat's HC_kTool seems to work great
Thank the DEVELOPERS
Already been highlighted a few times
http://forum.xda-developers.com/showthread.php?t=1068193&highlight=efs
Can you please clarify....I always keep a weekly copy of clock work mod backed up. Is this not enough? A lille confused about the need for efs backup...
Sent from my SGS2
Thx for this post. Anyway, i got stuck at 17, it says "-rf: not found". What does that mean? Am i unable to mount efs?
Nice post. Not happened to me *yet* but you never know.
Here is the direct link to Hellcats K-tool
Backing mine up now
jcrompton said:
However if you have not BACKED UP your EFS files then you will have issues like I did
Click to expand...
Click to collapse
You had the EFS image file already, all you had to do was rename the file then use ktool and you were done within seconds..
You probably could've done it via pm as I don't think it was a good idea to try any suggestion that was thrown at you in public forum...
btw, this is original development section.. someone move it to general please..
s2d4 said:
You had the EFS image file already, all you had to do was rename the file then use ktool and you were done within seconds..
You probably could've done it via pm as I don't think it was a good idea to try any suggestion that was thrown at you in public forum...
btw, this is original development section.. someone move it to general please..
Click to expand...
Click to collapse
Actually i don't understand how he made it: ktool doesn't use a tar file like posted, but an img file, and you can only find tar.gz files in the backup folder. How do you get an img file out of those?
s2d4 said:
someone move it to general please..
Click to expand...
Click to collapse
Sorted
Used K-Tool since the method mentioned via terminal never worked..
stylez said:
Sorted
Used K-Tool since the method mentioned via terminal never worked..
Click to expand...
Click to collapse
Good for you
But what did you do exactly? How did you obtain the img file for ktool to flash it? I only have the tar backups from the Efs_ backup folder...
s2d4 said:
You had the EFS image file already, all you had to do was rename the file then use ktool and you were done within seconds..
You probably could've done it via pm as I don't think it was a good idea to try any suggestion that was thrown at you in public forum...
btw, this is original development section.. someone move it to general please..
Click to expand...
Click to collapse
I did not have a new efs image file
All the files I had had been corrupted
I spent four days PMing all the big wigs re this. It's not as simple as you think unless you familiarize yourself with EFS backup BEFORE you need it!
Clockwork mod and nandroid backups do not alter the efs folder when a backup is restored! It must be backed up separately
Sent from my GT-I9100 using xda premium
vnvman said:
Good for you
But what did you do exactly? How did you obtain the img file for ktool to flash it? I only have the tar backups from the Efs_ backup folder...
Click to expand...
Click to collapse
I did not have an image file either. Look above at my post where I describe how to do it from step number 1 forward
I didn't use the tool to fix it
I just suggested getting the tool and learning how to use it
Sent from my GT-I9100 using xda premium
jcrompton said:
I didn't use the tool to fix it
Click to expand...
Click to collapse
Just to make the whole thread clear, is your IMEI now the original IMEI or the default U1 IMEI of 0049...?
Hmm..in the end i fixed this by flashing the efs from the official kh3 firmware through odin (clear efs checked). Now my imei changed to a generic one but i don't really care: i have my baseband back and the phone works. I just hope the FBI or something isn't after me now.
vnvman said:
Hmm..in the end i fixed this by flashing the efs from the official kh3 firmware through odin (clear efs checked). Now my imei changed to a generic one but i don't really care: i have my baseband back and the phone works. I just hope the FBI or something isn't after me now.
Click to expand...
Click to collapse
Do you have an EFS_BACKUP folder on your sdcard? And if so do you have any compressed files with older (mine was dated Dec31 2010) .nv_data.bak files?
If you do then that's what I ultimately used to restore my IMEI (not the generic one)
jcrompton said:
Do you have an EFS_BACKUP folder on your sdcard? And if so do you have any compressed files with older (mine was dated Dec31 2010) .nv_data.bak files?
If you do then that's what I ultimately used to restore my IMEI (not the generic one)
Click to expand...
Click to collapse
Thanks, i'll try that right away.
vnvman said:
Actually i don't understand how he made it: ktool doesn't use a tar file like posted, but an img file, and you can only find tar.gz files in the backup folder. How do you get an img file out of those?
Click to expand...
Click to collapse
kTool does both, raw .IMG dump and filebased .tar.gz backup.
Does K-Tool work with CF-Root kernel?
HellcatDroid said:
kTool does both, raw .IMG dump and filebased .tar.gz backup.
Click to expand...
Click to collapse
Wtf, i got answered by Hellcat himself!
Thanks, i didn't notice that option, i would have gone much less nuts if i knew it, stupid me
nfribeiro said:
Does K-Tool work with CF-Root kernel?
Click to expand...
Click to collapse
Yes, should work fine.
Should you find any missbehavings or issues though, please let me know and they shall be fixed
vnvman said:
Wtf, i got answered by Hellcat himself!
Thanks, i didn't notice that option, i would have gone much less nuts if i knew it, stupid me
Click to expand...
Click to collapse
lol xD
Well, but not necessarily stupid, the first few versions indeed only made the raw .IMG dump and the button still only says "backup to /sdcard/efs.img" (yeah, I should really change that text )
But since some 1.2x build it makes the .tar as well and when you hit the restore button it asks if you want to restore the .IMG or the .tar
Haha yeah right, i never hit restore because i didn't have an img dumped to the sd so i thought i had nothing to restore there
Hi all,
i installed this but while booting from SD, MAGLDR is just saying "initrd open failed" in red font color. Then 123456... The Display looks crazy
Whats the problem?
First unzip the downloaded initrd.gz and after that replace the file.
Have fun!
Ahhhh... Shame on me!!!
Thanks
Intrid open failed
Petricanu said:
First unzip the downloaded initrd.gz and after that replace the file.
Have fun!
Click to expand...
Click to collapse
Hi, I must e one of the last one still liking the HTC HD2. Can you be please more precise which file and where (what directory on SD) should be replaced with the unzipped one.
Cheers
Marek
[email protected] said:
Hi, I must e one of the last one still liking the HTC HD2. Can you be please more precise which file and where (what directory on SD) should be replaced with the unzipped one.
Cheers
Marek
Click to expand...
Click to collapse
Hi Marek, can you be a bit more precise with your question?
MAGLDR is looking for two files to boot android, initrd.gz and zImage. You can tell it where to look for these files on your sd card by using 10. services / 1. bootsettings / 3. ad sd dir/ and selecting the folder where these files are located from the list.
Hope this helps
Hello,
I am a bit anxious about my phone. It works well under omega 3.1 but I was checking my saves and I foud that:
1) My EFS folder is empty
2) I have two efs backup files but they seem rather small (35k each) ans they are dated 1970 I am pretty sure they are empty
3) my IMEI is correct when I go into about phone (But does not appear when I dial *#06#
Is there something wrong ?
The Imei seems good but as the efs folder is empty it should not...
Any idea ?
dronarg said:
Hello,
I am a bit anxious about my phone. It works well under omega 3.1 but I was checking my saves and I foud that:
1) My EFS folder is empty
2) I have two efs backup files but they seem rather small (35k each) ans they are dated 1970 I am pretty sure they are empty
3) my IMEI is correct when I go into about phone (But does not appear when I dial *#06#
Is there something wrong ?
The Imei seems good but as the efs folder is empty it should not...
Any idea ?
Click to expand...
Click to collapse
see it with a root explorer. or file manager with root access (enable root explorer in its setting).
how did you backup your efs??
Yes I looked a t it with a root explorer and it is empty.
The backup was donne while flashing rom but I have not the original efs backup (I forgot to back it up)
dronarg said:
Yes I looked a t it with a root explorer and it is empty.
The backup was donne while flashing rom but I have not the original efs backup (I forgot to back it up)
Click to expand...
Click to collapse
try to backup it now with terminal emulator and see the size
I9505 http://forum.xda-developers.com/showpost.php?p=41536475&postcount=8
I9500 http://forum.xda-developers.com/showpost.php?p=41559366&postcount=2
samersh72 said:
try to backup it now with terminal emulator and see the size
I9505 http://forum.xda-developers.com/showpost.php?p=41536475&postcount=8
I9500 http://forum.xda-developers.com/showpost.php?p=41559366&postcount=2
Click to expand...
Click to collapse
I am not sure how to do it with terminal emulator.
After flashing TWRP recovery and while the phone was brand new I made a full backup of the phone and inside there is a efs backup wich is 35k
Also I made another backup made with twrp recovery and it is 35 k again for the efs.ext4.win
Is that a normal size ?
dronarg said:
I am not sure how to do it with terminal emulator.
After flashing TWRP recovery and while the phone was brand new I made a full backup of the phone and inside there is a efs backup wich is 35k
Also I made another backup made with twrp recovery and it is 35 k again for the efs.ext4.win
Is that a normal size ?
Click to expand...
Click to collapse
i dont think so.
download terminal emulator from play store and just do the command in link. it is very easy.
samersh72 said:
i dont think so.
download terminal emulator from play store and just do the command in link. it is very easy.
Click to expand...
Click to collapse
I did it and it created a 13.62 mb file.
However I dont know if there is something inside as there is no file in efs folder. It may have copied blank data ?
dronarg said:
I did it and it created a 13.62 mb file.
However I dont know if there is something inside as there is no file in efs folder. It may have copied blank data ?
Click to expand...
Click to collapse
very good. right size for I9505 !
nothing wrong with your phone :good:
copy it to your pc for emergency
i advise also to backup m9kefs partitions also http://forum.xda-developers.com/showpost.php?p=41537402&postcount=10 arround 780 kb each one
it doesnt matter if you dont see it. the efs partition is fine
samersh72 said:
very good. right size for I9505 !
nothing wrong with your phone :good:
copy it to your pc for emergency
i advise also to backup m9kefs partitions also http://forum.xda-developers.com/showpost.php?p=41537402&postcount=10 arround 780 kb each one
it doesnt matter if you dont see it. the efs partition is fine
Click to expand...
Click to collapse
Yes I did it also for the m9kefs partitions and everything is stored in safe place.
Many thanks to you !
My efs (files and folders inside) is 3.xx kb and is correct.
The whole partition of efs is about 13.xx mb.
Even the efs folder has no files in it or have,
the size of the partition remain the same.
Thanks.
ausdim said:
My efs (files and folders inside) is 3.xx kb and is correct.
The whole partition of efs is about 13.xx mb.
Even the efs folder has no files in it or have,
the size of the partition remain the same.
Thanks.
Click to expand...
Click to collapse
Thank you. Yes :thumbup: i was pointing to the whole partition. it seems that his efs partition is not corrupted. I suggest always to backup the whole partition.
Sent from my Galaxy using xda premium
samersh72 said:
Thank you. Yes :thumbup: i was pointing to the whole partition. it seems that his efs partition is not corrupted. I suggest always to backup the whole partition.
Sent from my Galaxy using xda premium
Click to expand...
Click to collapse
And any idea why the efs folder is empty ? Is the efs a hidden partition and the folder just a dumb file or symbolic link ?
dronarg said:
And any idea why the efs folder is empty ? Is the efs a hidden partition and the folder just a dumb file or symbolic link ?
Click to expand...
Click to collapse
what explorer are you using?
download attached file manager, install it. open it, go to the settings of file manager, check "root explorer" (grant permission) and check "mount system folder". now see efs folder.
So my favorite boot animation by far is the one that comes with NucleaRom, but I need to use a different rom. Could someone point me in a direction to extract the bootanimation from a certain rom and flash it on my current system? Was surprised to not find a guide to help me already.
A2017U
Lots of ba threads in theme forum.
lafester said:
Lots of ba threads in theme forum.
Click to expand...
Click to collapse
Read through them. Not what I'm looking for
Amer532 said:
extract the bootanimation from a certain rom and flash it on my current system?
Click to expand...
Click to collapse
@Amer532 ... Use a root empowered File Manager to go to /system/media and there you will find the current "bootanimation.zip" file. Copy it to a folder on your external sdcard then when you load your new rom, again go to /system/media and replace the existing file "bootanimation.zip" with the one you previously saved to your ext sdcard. That should do the trick. I should stress that the A2017U is a finiky device so I don't take any responsibility for anything that goes wrong. :fingers-crossed:
metpolds said:
@Amer532 ... Use a root empowered File Manager to go to /system/media and there you will find the current "bootanimation.zip" file. Copy it to a folder on your external sdcard then when you load your new rom, again go to /system/media and replace the existing file "bootanimation.zip" with the one you previously saved to your ext sdcard. That should do the trick. I should stress that the A2017U is a finiky device so I don't take any responsibility for anything that goes wrong. :fingers-crossed:
Click to expand...
Click to collapse
Ok thank you now I understand that the rom has to be installed to get to that "bootanimation.zip". Thanks for clearing that up for me XD