Related
12/08/2010 Updated with fix permission
TO ALL PEOPLE:
PLEASE STOP POSTING IN THIS TOPIC ABOUT "THIS PART DOESN'T WORK ECC ECC" WRITE IN THE TOPIC OF THE RELEASE (KERNEL OR SYSTEM), PLEASE LOOK IN THIS THREAD FOR WORKING SETUPS AND TRICKS, AND SEARCH ON THE FORUM BEFORE POSTING!
This method erase all data on your system and you can brick you phone so do it carefully.
Main problem: screen
For polaris there are 3 type of screen. Usually pola100 (the old one) use panel 1, and pola 200 (09 edition) has panel 3 but ... not always works...
The best mode to test is try to install and after double reboot you have black screen change panel type.
What you need:
phone (with hardspl installed)
sd card (1 Gb or more)
time
python
Update guide: http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsNand
important said:
if you have black screen:
reset the device and edit the pannel (E)
with onother type (1,2,3) and retry.
Click to expand...
Click to collapse
For androidinstall.tar e nbh look in this thread for working setups. (Choose Eclair or Froyo, Donut as problems with new kernel)
You can flash back windows (using your preferred method), if you need, but it's a shame!
Reserved by me
good
nice going l1q1d.
Make this also sticky.
can you add how to change panel 1 to 3 or vice versa?
There are som nbh file that only come out as panel 3
can you add how to change panel 1 to 3 or vice versa?
There are som nbh file that only come out as panel 3
Click to expand...
Click to collapse
You just Download NBH Editor and select the NBH with panel 3.
Then you will see that you can choose from whatever panel you would like, save and copy on SD
sorry for my english.
good guide.
I installed everything ok android
now if I wanted to update the radio?
ho installato android tutto ok
ora se volessi aggiornare la RADIO ?
Download radio update.
rename it to POLAIMG.nbh and put in sd
start with camera button pressed
push power button when asked
restart
you have successfully update the radio
ok. perfect.
tanks : )
HTC Polaris 100 - doesn't flash
I followed you instructions exactly as you wrote them. BUt it doesn't work.
When I power on the device with camera button pressed I see the 3 color boot screen- but that is it. At this point the screen says "Loading" and nothing else happens.
What am I doing wrong?
I have been using the Haret version of Froyo and think it is great, but wanted to go the NAND route. I am hoping it will perform better.
Thanks for your help
Re-download the nbh and retry, maybe is corrupted..
A little help
Hi,
It's been a while since i posted but I'm trying to flash to the NAND but must be a little out of touch as I get blocked at an Error
on the micro SD card I put
\POLAIMG.NBH (renamed from POLAIMG-PANEL1-320-FROYO.NBH
in the \andboot
install-seq.sh
androidinstall.tar (which is not easy to find but I managed
I followed your guide http://forum.xda-developers.com/showthread.php?t=725604
but the bootlog.txt stops at these errors;
...
....
Script finished
sh: 0: unknown operand
mount: mounting /dev/block/mtdblock2 on /system failed: Invalid argument
mount: mounting /dev/block/mtdblock3 on /data failed: Invalid argument
mount: mounting /data/tmpcache on /cache failed: Invalid argument
mount: mounting /data/shared_prefs on /shared_prefs failed: Invalid argument
mount: mounting /data/tmpcache on /tmp failed: Invalid argument
mount: mounting /data/sysfiles/su on /system/bin/su failed: No such file or directory
mount: mounting /data/sysfiles/su on /system/xbin/su failed: No such file or directory
mount: mounting /data/sysfiles/su on /bin/su failed: Invalid argument
mount: mounting /data/sysfiles on /system/etc/ppp failed: No such file or directory
mount: mounting /data/sysfiles on /smodem failed: Invalid argument
I am doing something wrong ???
Thanks for any help
Richard
It's very strange, try another time..
(remember that install-seq disable automatically if install procedure works without problems)
there only these errors? are there any "Failed to format"?
Indeed the install-seq did get renamed ti install-seq-disable and the data.img & system.img was on the sd card....
Tried three times already...humpf..
Maybe I'll try a manual install.
I can post the dmesg if you think it helps??
If you use nand install you don't need anymore data.img and system.img ...
the install-seq install all on nand.
Post your dmesg (with a link) and i'll take a look...
Hi, at first I want to thank you for this tut and all your work It walked me through the proces of getting android on my pola100.
Just wanted to ask what I can delete from my sd card after succesful flashing. Can I delete complete folder andboot? Thx for your help
All the files, but it would be a better choice to keep all file on sd...
l1q1d said:
If you use nand install you don't need anymore data.img and system.img ...
the install-seq install all on nand.
Post your dmesg (with a link) and i'll take a look...
Click to expand...
Click to collapse
When I used your install script for the first time it tries to install system.img and data.img on the EXT2 partition.
After restart I entered the menu and selected the NAND option.
When I re-install the nbh and using your install script (for the second time) it is working.
I have the same problem as zeeos, I have "loading..." on my screen but nothing happens. I tryed many nbh...
Try to change sd card or flash from windows application...
Hey guys,
I've followed the guide exactly, performed task 29 first and ran from a clean, formatted SD card.
I'm using the latest Froyo build and have changed it to panel 1 as I have a POLA100.
The install procedure runs smoothly until it it gets to the point where I see the Warm Donut boot screen with animation, but then it stops and just shows a black screen with white cursor in the top left hand corner, doesn't go any further. Is this normal? Do I have to wait longer? I've left it for half an hour...?
Which files did you use?
I heve edited the system.img.ext4 on samsung galaxy mini 2
and after i have flashed the phone i receive this error :
failed to mount system invalid argument
Flashing the system back with original phone works
What is causing this error?
grigoreee said:
I heve edited the system.img.ext4 on samsung galaxy mini 2
and after i have flashed the phone i receive this error :
failed to mount system invalid argument
Flashing the system back with original phone works
What is causing this error?
Click to expand...
Click to collapse
Well, it really depends on your edit.
I have mounted system.img.ext4 and removed some files from it then i have recreated the image and flashed to phone but i receive this error when the phone starts.
re install the firmware or install a new one....that should serve the purpose
the phone is working when i flash the original fw but i want my modded system.img.ext4
with the modified system i receive this:
Not need checksum confirmation already executed!!... (this is normal )
then:
E:failed to mount /system (invalid argument)
@grigoreee - I have the same problem like You with system...
Do You found any solution?
I think that replace boot.img from this thread:
Code:
http://forum.xda-developers.com/showthread.php?t=1719699
end's in the same way
How did u guys extract the system.img.ext4?
using dd?
I use this method:
Code:
http://forum.xda-developers.com/archive/index.php/t-1588461.html
(in mini2 system is mount with the same parameters as described above)
No solution for this error?
I still receive the same error......
grigoreee said:
No solution for this error?
I still receive the same error......
Click to expand...
Click to collapse
try to format /system partion from cwm in mount and storage
Hi,
Hope someone can figure this as its wrecking my brain.
I got an 8010 (wifi only version) a few days ago.
Did the clockwork and rooting and it was all working fine, until..
Booted it up this morning and it flashed a message 'Unfortunately, Factory Test has stopped. Factory Mode is ON!!' and gave me the 'calculator' program for putting in service codes.
I've checked the efs folder and its blank, no files. (I do not have a backup, yes I know I'm an idiot)
I've since tried flashing a number of roms, including stock. None of which have resolved the issue.
When using the stock recovery it gives me an error about being unable to mount /efs
From google it appears that the efs folder is to do with the imei and other areas. As mine is wifi only version should I even have this folder?
The note appears to work fine with the exception of having a lock screen, power off options etc.
thanks
BB
Have you tried to flash it over the PC with Odin and the Files from sammobile.com ??
Have you tried to repair the EFS with this Tool: http://forum.xda-developers.com/showthread.php?t=1308546 ?
update
Darkman_RS said:
Have you tried to flash it over the PC with Odin and the Files from sammobile.com ??
Have you tried to repair the EFS with this Tool: http://forum.xda-developers.com/showthread.php?t=1308546 ?
Click to expand...
Click to collapse
Hi,
I have tried with the N8010XWALG4_N8010XSAALG3_XSA from sammobile but am currently running the N8010-XXALH2-XAALH2-DBT-deodexed
Strangely enough I have just tried to connect with Kies, and it wont connect gives an error of 'No Sim Card inserted unable to continue communication'
I'm wondering if I've somehow confused my device into think its a 8000, when it is in fact an 8010.
I've tried the EFS Repair, it states that Locate /efs partition failed and can't locate any backups ;-((
I've just tried reflashing a stock rom via odin, selecting the re-partition and format efs section (got nothing to lose at this stage I guess)
I've also removed clockwork mod and gone back to stock recovery, which reads E:failed to mount /efs (Invalid arument)
would anyone have the .pit file / bootloader files? or are they built into the the pda rom?
thanks
BB
Pit file
Further testing has shown that the /efs partition does not exist or has become corrupt.
Would anyone have / or could make a pit file for a 32gb gt-8010?
Failing that would anyone know the terminal commands and dev location for making the /efs partition (make2fs ??)
Did you fixed the issue?
blue_bear said:
Further testing has shown that the /efs partition does not exist or has become corrupt.
Would anyone have / or could make a pit file for a 32gb gt-8010?
Failing that would anyone know the terminal commands and dev location for making the /efs partition (make2fs ??)
Click to expand...
Click to collapse
I have the same problem please advise?
Dont want to start another thread, i ran into this problem today and my solution
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
you can do this with terminal also but i dont type well so this works best for me...tested only on 8013
Hello
I am getting the same problem.
Odin can not find partition. But I cant go to CWM, only download mode is possible. Any other way to start, it goes to a white screen...
BaDaB!ng505 said:
Dont want to start another thread, i ran into this problem today and my solution
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
you can do this with terminal also but i dont type well so this works best for me...tested only on 8013
Click to expand...
Click to collapse
You made my day bro a lot of thanks its works for me thank u
ques
BaDaB!ng505 said:
Dont want to start another thread, i ran into this problem today and my solution
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
you can do this with terminal also but i dont type well so this works best for me...tested only on 8013
Click to expand...
Click to collapse
hi, I sent u a msg, if u dont read msgs on private, qoute me her so i can ask ya her.
bless
BaDaB!ng505 said:
Dont want to start another thread, i ran into this problem today and my solution
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
you can do this with terminal also but i dont type well so this works best for me...tested only on 8013
Click to expand...
Click to collapse
perfect
thx a lot
thank you sir, good job.
BaDaB!ng505 said:
Dont want to start another thread, i ran into this problem today and my solution
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
you can do this with terminal also but i dont type well so this works best for me...tested only on 8013
Click to expand...
Click to collapse
Hi,
how is the zip to be used?
YOSEFE said:
Hi,
how is the zip to be used?
Click to expand...
Click to collapse
it is just factorymode file set to on
use root enabled file manager and copy to /efs over writing current one. but it's just as easy or easer to just edit current file and change OFF to ON
BaDaB!ng505 said:
Dont want to start another thread, i ran into this problem today and my solution
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
you can do this with terminal also but i dont type well so this works best for me...tested only on 8013
Click to expand...
Click to collapse
@YOSEFE and @carl1961
hello
where I find this CWM and ANDROIDSDK ,,,??? ...she said " Assuming you have CWM installed on device and have androidsdk store on computer C: drive "
CWM what exactly is and where to find it ?
same for androidsdk where I find it ??
can you give me the real or good link plz ?? thanks
Hello,
CWM Recovery is found on www.clockworkmod.com
You need the one for your device.
You can Google search this and other file too. Be sure to read about CWM Recovery. It will trip knox on Samsung phones.
Sent from my SM-N910F using XDA Free mobile app
YOSEFE said:
Hello,
CWM Recovery is found on www.clockworkmod.com
You need the one for your device.
You can Google search this and other file too. Be sure to read about CWM Recovery. It will trip knox on Samsung phones.
Sent from my SM-N910F using XDA Free mobile app
Click to expand...
Click to collapse
@YOSEFE
I'm sorry but what this i don't understand where is the link plz direct links for download ?? thanks
I can not go and install apps because the tablet does not open
my device is GT-8010 WIFI ONL
edits
i have downloaded this "recovery-clockwork-6.0.4.6-n8000 ' and "recovery-clockwork-6.0.4.6-n8013" it's ok or no ?? here http://www.clockworkmod.com/rommanager
if yes how to install ??
joan62 said:
@YOSEFE
I'm sorry but what this i don't understand where is the link plz direct links for download ?? thanks
I can not go and install apps because the tablet does not open
my device is GT-8010 WIFI ONL
edits
i have downloaded this "recovery-clockwork-6.0.4.6-n8000 ' and "recovery-clockwork-6.0.4.6-n8013" it's ok or no ?? here http://www.clockworkmod.com/rommanager
if yes how to install ??
Click to expand...
Click to collapse
your best using one for 8013
https://goo.im/devs/Darkman/Recoverys/N8013-CWM-noTouch-6.0.3.6-ODIN.zip/
carl1961 said:
your best using one for 8013
https://goo.im/devs/Darkman/Recoverys/N8013-CWM-noTouch-6.0.3.6-ODIN.zip/
Click to expand...
Click to collapse
+1...
Sent from my SM-N910F using XDA Free mobile app
@YOSEFE @carl1961
please help with the screnns is possible I'm sorry but i don't understand
I enter the ligne but the command not working
he said not find
the ANROIDSDK IN c : drive /android /android-sdk.... it's ok the intallation ?
Install on C:\. Use ODIN to install Recovery. Make sure your device is in download mode.
Sent from my SM-N910F using XDA Free mobile app
Since most of the high-end devices are using now EXT4 partitions i decided to make a guide.
I am doing this because this is the easiest way to create an EXT4 image.
This is not my guide I am just adapting and make it clear to everybody; someone showed me how to do this (I will mention him at the end of the guide).
Let's assume that you dumped the system.img from your own device and you want to add something to it.
We will create a new system.img and we will name it system_new.img, the size will be 240 Mb.
Step 1
Linux Machine (I used Ubuntu)
We prepare the directories and copy the system.img in the folder in which we will work.
mkdir system (here we will mount the old system.img
mkdir system_new (here we will mount the system_new.img)
Step 2 – Creation of the actual EXT4.img
dd if=/dev/zero of=system_new.img bs=4k count=60000
Translation of the terms,
bs =blocksize, 4k= the size of the block`s which in this case is 4kb
count=60000, the number of block`s, in our case will result an image of 240 Mb.
The blocksize can be 1k/2k/4k/16k
To get the exact size of the image that you create use simple maths.
60000 * 4 = 240000
Step 3 Formating the system_new.img with EXT4
mkfs.ext4 system_new.img
It will be a question where you will select yes (Y)
We override the file system check (If you don`t do this, the image will not work)
tune2fs -c0 -i0 system_new.img
Step 4 We mount the directories that we previous created.
mount -o loop system_new.img system_new/
mount -o loop system_new.img system/
Step 5 We copy the content from the old system.img in the system_new.img
cp -v -r -p system/* system_new/
We sync the files
sync
Step 6 Unmounting the partitons.
umount system_new/
umount system/
Step 7 Enjoy your new ext4 system.img
Tips:
If you are using Ubuntu just type
sudo su
And you will be root and no more sudo at each command.
You can add new files in the new created system.img but you need to set the permissions and ownership properly, otherwise it will not work.
Credits: arctablet.com administrator.
work perfect!
I managed to create a new system img for huawei phone.
Errors in Step 3 and 4: Unable to proceed
Hi There,
I am getting errors in step 3 and 4.
Step 3 Formating the system_new.img with EXT4
mkfs.ext4 system_new.img
It will be a question where you will select yes (Y) -- after this below error comes
Device size reported to be zero. Invalid partition specified, or partition table wasn't reread after running fdisk, due to a modified partition being busy and in use. You may need to reboot to re-read your partition table.
We override the file system check (If you don`t do this, the image will not work)
tune2fs -c0 -i0 system_new.img -- after this below error comes
Attempt to read block from filesystm resulted in short read while trying to open system.img
Step 4 We mount the directories that we previous created.
mount -o loop system_new.img system_new/ -- after this below error comes
unknown filesystem type 'ext4'
Could you please help.
i whant to create and system.img.ext4 for my android ! ! But i saw that image which is created is just system.img ! I`m using ubuntu and i whant to know what is need it to create that system.img.ext4 ! I don`t see that img to be ext4 file ! Thanks
jabarel said:
i whant to create and system.img.ext4 for my android ! ! But i saw that image which is created is just system.img ! I`m using ubuntu and i whant to know what is need it to create that system.img.ext4 ! I don`t see that img to be ext4 file ! Thanks
Click to expand...
Click to collapse
I'm not sure but it's probably just a matter of file extenstion.
By the way, great tuto. May be someting to add :
Android ext4 don't seem to be the exact standart of linux ext4 file systems.
To make it fully compatible and usable with fastboot, the use of "ext2simg" can be useful.
So it will be something like this :
ext2simg fs2convert.img fsconverted.img
ext2simg can be found in android-tools in debian repository.
I am porting a rom ,i extracted "system.new.dat" into "sytem" folder , applied changes according to this guide to port a ROM -->> http://forum.xda-developers.com/showthread.php?p=65933478#post65933478
can you tell me how to reconstruct the "system.new.dat" from "sytem" folder ?
is mkfs.ext4 applet available to arm devices..??
you can do it faster...
Great if you create a new image, but to edit no need to create all these steps ...
Just copy the system.img to system_new.img and mount that one and edit..
There's no clear instruction!
Hours of researching many places and no good instruction about how to create or edit an EXT4 with or without Linux!
I know this is an old post but I just wanted to try, might get a reply!
Frank2406 said:
Hours of researching many places and no good instruction about how to create or edit an EXT4 with or without Linux!
I know this is an old post but I just wanted to try, might get a reply!
Click to expand...
Click to collapse
what is not clear?
this has been tested by me and it works.
there are more refined ways in doing it, it just depends on what you need to to with the ext4 image.
globula_neagra said:
what is not clear?
this has been tested by me and it works.
there are more refined ways in doing it, it just depends on what you need to to with the ext4 image.
Click to expand...
Click to collapse
Step 1: "We prepare the directories" you said. What directories?
"mkdir system"
"mkdir system_new" which, what or where are they?
Step 2: The whole step 2 for a newbie in Linux like me is bla bla bla except the title "Creation of the actual EXT4.img"!
And the rest of your guide is as the same as step 2 which I mentioned.
And if this guide is for Ubuntu experts then maybe in the beginning you could mention so people don't get their hopes up dear globula_neagra!!
Long story short, I just wanted to try a custom Rom on my Zenwatch 1, but I've forgot to make backup, so the official Rom was gone. Asus itself didn't help to get a copy of the official one, so I tried Anthias custom Rom instead, but that made the watch even worse.
Then I started to research how to fix it, so I found this article.
It s not a step by step guide on how to use ubuntu.
I assume that wheen you want to learn something you do use google too. For this instance i would google in this way "what does mkdir command in ubuntu"
After i understood the purpose of the command and how to use it i would try to apply it using the guide and after that you will see that things will start to make sense.
My guide was written with the idea that if you use android you have an idea of linux too and in this case ubuntu.
The command line in linux is somewhat similar to the one in windows commander there are some extra things that you need to learn but those can t be put in a guide like this.
In regards to your watch. My advice is to find another one and take a system dump from that one and flash it to yours if you have an unlocked bootloader.
Here you cand find some good reads on how to dump the files from the watch. And a bit more details on what is the business with the ext4 creation. Topic is5 years old but still relevant.
http://www.arctablet.com/blog/forum/arnova-7c-g3/arnova-7c-g3-dev-topic/
Hi
My N8000 not start. ODIN flash well (no errors) but Rom not start from logo.
I flash a Custom Recovery on Odin I made full wipes and install or restore Roms, but they not start.
After Odin if I go to Stock Recovery I have:
E: Failed to mount /efs (Invalid argument)
Applied the csc-code : unknown
Can't open /efs/log/boot_cause.
On Custom Recovery can't mount /efs also.
May be I must flash a Pit File? But where is it?
Thank You
ValenteL said:
Hi
My N8000 not start. ODIN flash well (no errors) but Rom not start from logo.
I flash a Custom Recovery on Odin I made full wipes and install or restore Roms, but they not start.
After Odin if I go to Stock Recovery I have:
E: Failed to mount /efs (Invalid argument)
Applied the csc-code : unknown
Can't open /efs/log/boot_cause.
On Custom Recovery can't mount /efs also.
May be I must flash a Pit File? But where is it?
Thank You
Click to expand...
Click to collapse
did you backup EFS if so restore .
PIT are on sammobile but wrong PIT - brick ,
jje
JJEgan said:
did you backup EFS if so restore .
PIT are on sammobile but wrong PIT - brick ,
jje
Click to expand...
Click to collapse
Thanks
I have a backup but the Note not start. How can I restore it by Odin/Pc?
EDIT: I have efs backups format .tar.gz Can I flash this on Odin?
Must odin back to original ICS rom to work
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
device must be rooted
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3 ( skip to next step if fail)
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
factorymode
Now you can back up your efs.tar(for 8000 user only)
Reboot and everthing should be back to normal
ValenteL said:
Thanks
I have a backup but the Note not start. How can I restore it by Odin/Pc?
EDIT: I have efs backups format .tar.gz Can I flash this on Odin?
Click to expand...
Click to collapse
You need Help?
Sent from my GT-N8000 using XDA Premium HD app
Thanks by Your Help:
BaDaB!ng505 said:
Must odin back to original ICS rom to work
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
Click to expand...
Click to collapse
I have CWM and all on PC. I can flash on Odin and on Recovery. But I don't understood, I must flash the original ICS XWALG9 from SamMobile by Odin? You mean this?
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
Odin back to ICS to work....
Click to expand...
Click to collapse
After ...mount system I dont understood "Odin back to ICS"
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3 ( skip to next step if fail)
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
factorymode
Now you can back up your efs.tar
Reboot and everthing should be back to normal
Click to expand...
Click to collapse
This attach "factorymode" is the ON to replace the OFF?
Thank You
Good, it started, I have the Yellow text... now I continue...
Thank You
EDIT: Solved. Thank You BaDaB!ng505, from Your great help.
Not necessary to go to ICS.
mke2fs works well.
Edited factorymode whit Root Explorer and changed inside to ON.
Restored my /efs. All normal now.
Thank You
for the poeple who need the stock ICS 4.0.4
http://www.hotfile.com/dl/165813833/f958ae4/N8000XXALGA_N8000OXXALG5_PHN.zip.html
P.S. if all Poeple who recover his System, Will post Some Useful links here, he had used .
So I Can I make a good guide for the users with the same problems .
i fill tonight more links,mk now Go to my work .
Rongogo
Sent from my GT-N8000 using XDA Premium HD app
Rongogo said:
for the poeple who need the stock ICS 4.0.4
http://www.hotfile.com/dl/165813833/f958ae4/N8000XXALGA_N8000OXXALG5_PHN.zip.html
Click to expand...
Click to collapse
I have already a ICS 4.0.4 whit csc TPH from Portugal.
Thank You
How i made my 8000 work again...
Hello everyone,
i hope i canhelp. I also installed 5.0 Collective and everything worked....until the first reboot. It did not start again so i installed ICS from samfirmware and had that efs-problem and yellow text. (using TWRP 2.4.4)
I first rooted the device installed busybox (make sure to open and let install busybox)
i also installed Android Terminal (both, busybox and android from google play)
i had an efs-backup ((efs-18Marxxx.tar.gz) wich i extracted once on device then copied it to pc and extracted it again with 7zip.
So finally i had the folder again, i copied backto device extSdCard.
i opened android terminal and followed BaDas Steps (in collective thread...dont remember the post number just search pls.)
I started es file explorer gave it root in settings and copied the efs folder to / (root)
i set the rights for efs same as folder factory and renamed the file 000000000.something inside efs folder to Aaa000000000.something.
i am not sure if the last step is needed, but lately my device worksjust fine.
pls excuse any mistakes in text, if u have questions just shoot, good luck and dont worry as long as u can get into flashmode ur device can be fixed. peace
Robert
BaDaB!ng505 said:
Must odin back to original ICS rom to work
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
Odin back to ICS to work....
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3 ( skip to next step if fail)
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
factorymode
Now you can back up your efs.tar
Reboot and everthing should be back to normal
Click to expand...
Click to collapse
Will this method work to restore a Galaxy S3's efs files with the proper 4.0.4 image? Stuck in Factory mode and the efs folder is empty.
n8000 getting ready for v6 to flash...
hello,
will flash the collective v6 by badab!ng now, will report hopefully within the next hour.
Robert
...it works just fine with me, even after reboot..
I can confirm Collective Edition v6 Dark Side works on N8000, no more efs issus
BaDaB!ng505 said:
Must odin back to original ICS rom to work
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
device must be rooted
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3 ( skip to next step if fail)
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
factorymode
Now you can back up your efs.tar
Reboot and everthing should be back to normal
Click to expand...
Click to collapse
Dear Sir,
I think my EFS is corrupted cuz when i go to service mode, i get something which reads SPEECHver: FR FR FR when I bought my phone in the usa from tomobile. Cannot read sim card. Its a note2, i don't even know how to view or where to view my efs but i am assuming it is efs corruption, imei shows up everything looks ok except not recognizing the sim. Restored and everything, will this bring me back to original efs if i install the original factory rom?
Actually how do i view my efs details cuz right now i cannot use my phone everything else looks fine except cannot read sim. Will your method work with on a tmobile t889?
Thanks.
I am having the same efs issue
HI,
I am having the same efs issue when doing a factory wipe. My Tmobile Galaxy Note 2 is stuck in a bootloop and I have flashed the current Samsung firmware from their firmware site and it changed nothing. After I flashed it and the bootloop started I booted into the stock recovery and did a factory reset. That is when I got "E: Failed to mount /efs (invalid argument). I think one problem is I am a noob, the other is I didn't get CWM installed on my phone prior to all this. I do believe it all stimmed from me downloading and running Swapper on my phone. Everything seemed fine with it until I ran that and rebooted. To make matters worse, I failed (again noob here) to back up anything. Is there any hope for my Note 2?
You do know that this is the Note 10.1 forum don't you?
What did you flash?
thanks god I see your solution but...if I didn't install CWM...and android sdk...is there any other way to save my phone? THANKS!!
BaDaB!ng505 said:
Must odin back to original ICS rom to work
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
device must be rooted
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3 ( skip to next step if fail)
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
factorymode
Now you can back up your efs.tar(for 8000 user only)
Reboot and everthing should be back to normal
Click to expand...
Click to collapse
Fix it finally
THANK YOU ><!
BaDaB!ng505 said:
Must odin back to original ICS rom to work
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
device must be rooted
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3 ( skip to next step if fail)
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
factorymode
Now you can back up your efs.tar(for 8000 user only)
Reboot and everthing should be back to normal
Click to expand...
Click to collapse
BaDaB!ng505 said:
Must odin back to original ICS rom to work
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
device must be rooted
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system
2 on computer Shift+Ctrl +right click to open command window
command window type
cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3 ( skip to next step if fail)
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it
root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done
factorymode
Now you can back up your efs.tar(for 8000 user only)
Reboot and everthing should be back to normal
Click to expand...
Click to collapse
thank you sooooooo much!!
my s4 kept getting stuck on the samsung boot logo, i tried everything..flashing stock rom,pit files you name it. I was about to give up, untill i found this after hours upon hours of searching. Took me a couple of tries, but in the end my s4 was back up and running.
thanks so much!
aRbMama said:
thanks god I see your solution but...if I didn't install CWM...and android sdk...is there any other way to save my phone? THANKS!!
Click to expand...
Click to collapse
Dunno if CWM is necessary, but Android SDK is. Besides, It is going to help you to diagnose and repair many other problems.
Sent from my GT-N8000