Related
All credit for this goes to Razor950
Coby Kyros MID-7015
Download recovery.img from Sendspace.com - send big files the easy way
use flash_image and flash recovery to tablet. (ex flash_image recovery /sdcard/recovery.img)
Navigating:
Home is down
Menu is select
Back is back
Everything works and I'll post stock nandroid dumps on here soon.
Update some are reporting that they are unable to Flash to the recent firmware update that was posted
on the coby website do to the clockworkmod being installed.
Thanks to Kasten for coding this then thanks to adamdietrick for creating a new zip
That can be flashed with the clockworkmod installed.
Clockworkmod Coby Firmware update
Donate if you like Razor950's work!
thanks for posting
any issues that anyone gets with this recovery, please pm me.
enjoy
havic said:
Everything works and I'll post stock nandroid dumps on here soon.
Donate if you like Razor950's work!
Click to expand...
Click to collapse
Here's my backup
http://www.megaupload.com/?d=5ALHYN80
You must be rooted (I assume z4root or universal android root works)
then either using terminal (grab terminal app from market) or using adb.
Grab the recovery.img and drop it into sdcard via usb or adb push.
Open terminal and type su and then flash_image recovery /sdcard/recovery.img
or if using adb, its adb shell and then su and then flash_image recovery /sdcard/recovery.img
Note: I am not the best at writing noobie guides but hopefully it helps
Thanks for this. I do not have mine yet( lol, just ordered it) but I donated for your work!
Thanks!
Anyone have a idea on how to get back into recovery? I have it installed but have tried holding every button to get me back and nothing kinda sucks since I have been testing new mods for this and cant get to my backup because the first shot at the mod was a fail.
I was able to get clockwork installed thanks to you. Do you know of any images that are out for the 7015?
Lawful123 said:
I was able to get clockwork installed thanks to you. Do you know of any images that are out for the 7015?
Click to expand...
Click to collapse
Aside from stock(rooted) dump, there is nothing, I'll work with havic to get a rooted dump with google apps(market mostly) working correctly.
Besides that there is nothing else from my end for now. I personally don't like telechip tablets, bad experience from a gentouch :X
Also telechip company are retards and don't release kernel source, it'd help developers optimize a 2.1 rom and also be able to port kernel to a newer one for 2.2
I can see that this model gained popularity this black Friday. We are just now starting to see android tablets hit " Joe User ". I think that the telechip tabs will become popular so long as the price is on point. Thanks for all you do.
what exactly is this recovery for?
does installing this offer me additional features, or is it merely what we would restore to in case of disaster?
Deenybird said:
what exactly is this recovery for?
does installing this offer me additional features, or is it merely what we would restore to in case of disaster?
Click to expand...
Click to collapse
For now it is a good way to backup your unit so that if you screw it up you can go back. In the future people will make images for it. Hopefully someday android 2.2
Which version of flash_image tool is needed to flash this recovery or is the tool stock on the tablet?
EDIT: figured it out. stock. Looking through the dump now =)
adamdietrick said:
Here's my backup
http://www.megaupload.com/?d=5ALHYN80
Click to expand...
Click to collapse
If you try and recover from the backup that is in the link you may or may not get a error.The error is md5 mismatch. So the recovery fails to install.
What needs to be done is need to have busybox installed then shell in and run the following commands.
This has to be ran from the dir. that contains the backup files.
Which will more than likely be similar to this
/sdcard/clockworkmod/backup/2010-12-01.20.41.18
#busybox md5sum -c nandroid.md5
boot.img: OK
cache.img: OK
data.img: OK
recovery.img: OK
system.img: OK
# reboot recovery
reboot recovery
Once in clockwork then run a recovery.
If you have a Issue let me know I will try my best to get you some answers.
razor950 said:
You must be rooted (I assume z4root or universal android root works)
then either using terminal (grab terminal app from market) or using adb.
Grab the recovery.img and drop it into sdcard via usb or adb push.
Open terminal and type su and then flash_image recovery /sdcard/recovery.img
or if using adb, its adb shell and then su and then flash_image recovery /sdcard/recovery.img
Note: I am not the best at writing noobie guides but hopefully it helps
Click to expand...
Click to collapse
When I type this it it says its file not found.
I double checked and in astro I see
sdcard/recovery.img
any ideas?
beccaannabell said:
When I type this it it says its file not found.
I double checked and in astro I see
sdcard/recovery.img
any ideas?
Click to expand...
Click to collapse
where are you when you type that? does it not find the flash_image binary or the .img?
Worked for me
I got it working by doing the following.
1. Download and installed "Android Terminal Emulator" on to the device.
2. Download and installed Z4Root 1.3.0.apk from here http://forum.xda-developers.com/showthread.php?t=833953
3. Run it and pressed the "Permanent Root" button. It took a bit and it auto rebooted.
4. Place the recovery.img on the root of my sd card. (Razor950's recovery.img is from post#1 on this thread.)
5. Opened "Android Terminal Emulator".
6. Entered the following.
su
flash_image recovery /sdcard/recovery.img
7. Locked everything up for about 5 min and it went back to # prompt when it was done.
8. I powered off the device.
9. After it turned off I pressed and held the back button then pressed the power button. Kept holding it until you see clockworkMod v2.5.1.3. (If it says Android it's too late.)
I have a question myself what is sd-ext on clockwork? Also is there a way to do a selective backup? Just system with no data?
Thanks.
Thanks for your procedure, will try it when I receive my tablet.
Regarding your question about sd-ext, it's a partition of your sdcard. One will be in fat32 and the other in ext2 or ext3. Usually ext2 is used when you have app2sd or 12sd+. The purpose of this is to have more apps in install by installing them on your ext partition instead of internal memory. I use it for my HTC desire (smartphone)
Regarding your second question, I don't know anyway of doing a backup without data but pretty sure it's possible, for example, if you go in your Android do a factory reset. reboot in recovery then do your backup. Not sure if there's another way to do it
Yezir!
Kasten said:
I got it working by downing the following.
1. Download and installed "Android Terminal Emulator" on to the device.
2. Download and installed Z4Root 1.3.0.apk from here http://forum.xda-developers.com/showthread.php?t=833953
3. Ran it and pressed the "permit root" button. It look a bit and it auto rebooted.
4. Place the recovery.img on the root of my sd card.
5. Opened "Android Terminal Emulator.
6. Entered the following.
su
flash_image recovery /sdcard/recovery.img
7. Locked everything up for about 5 min and went back to # prompt when done.
8. Powered off device.
9. Press and held the back button then pressed the power button. Kept holding it until I saw clockworkMod v2.5.1.3. (If it says Android its too late)
I have a question myself what is sd-ext on clockwork? Also is there a way to do a selective backup? Just system with no data?
Thanks.
Click to expand...
Click to collapse
this is perfect!!!!! thanks for thinking of us dummies
Daali said:
where are you when you type that? does it not find the flash_image binary or the .img?
Click to expand...
Click to collapse
same thing for me
"error opening /sdcard/recovery.img:No such file or directory"
Help
noonerealy said:
same thing for me
"error opening /sdcard/recovery.img:No such file or directory"
Help
Click to expand...
Click to collapse
Can you see the recovery.img on your sd card from a file manger app like Astro? If so when your in the terminal can you cd to /sdcard? If so can you enter ls -l recovery.img? Check the size to make sure it is all there.
I have anther question myself.
At cobyusa.com/?p=prod&prod_num_id=10498&pcat_id=1013 there is a firmware update. in the update.zip in system in the build.prop file i see a line that says "ro.build.version.incremental=eng.enzo.20101125.200217". I notice that the build number on the device says "MID7015 1.6a_20101105-2". Looks like they may have changed somethings but not sure what. What would be bet best way to figure out what they changed?
I tried to run it from clockwork and i get
assert failed: getprop("ro.product.device") == "tcc8900" || getprop("ro.build.product") == "tcc8900"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
To install this update would I just have to unroot my device? Not sure how to look what the current ro.build.product is now.
Thanks.
Hi,
i hope anybody can help me to make a Galaxy 3 Rom Backup Tool.
I made a little script for the German Forum, and it works fine but i can not flash the backupped Rom files.
Can somebody help me how i can push the backupped /data partition in datafs.rfs to the Phone without getting a Bootloop?
Here is a link to the Script http://www.multiupload.com/TAIJ9Z53J7
Sry for my english ^^
Nice work!
Will try ASAP...
And btw your english is good enough!
Ok, translated for you :
Code:
Install Total Commander and connect your Galaxy 3 to your PC in USB debugging mode
Next run Backup.bat
Your backup is finished when the window closes by itself. You can find the data in the folder backup on your SD
Copy the whole folder to your PC
Open the ROM Image.tar in total commander
Now you can flash your backup as One Package in Odin.
WARNING: please mention my name when you upload or translate the tool
Thanks for the code, I was just thinking along the same lines. You can skip the Total commander thing if you'd include something like 7zip commandline which is free. You can then call it from your batch file. Or tar it in the phone itself or is this too slow/bad for SD ?
You pull the files over with adb pull, but instruct to copy them from the SD as well.
As for why it bootloops : need to test it, but will probably wait for a fresh rom.
You can also put it back with dd ?
hmm
with which adb command i can put all 5 files in a flashable .tar file?
and how i can put the whole /data partition from the datafs.rfs in the /data folder and overwrite the files in the data folder?
Hmm, I see it's Busybox responding on my Galaxy, maybe it's not installed by default, but it was included in a custom ROM ?
Code:
BusyBox v1.18.4 (2011-03-20 15:16:04 CDT) multi-call binary.
Usage: tar -[cxtzjamvO] [-X FILE] [-f TARFILE] [-C DIR] [FILE]...
Create, extract, or list files from a tar file
Operation:
c Create
x Extract
t List
Options:
f Name of TARFILE ('-' for stdin/out)
C Change to DIR before operation
v Verbose
z (De)compress using gzip
j (De)compress using bzip2
a (De)compress using lzma
O Extract to stdout
h Follow symlinks
m Don't restore mtime
exclude File to exclude
X File with names to exclude
T File with names to include
You'd have to remount /data r/w to make any changes to it. But if you're dd-ing, it'll talk to the block device directly. Not sure how to clear it though, maybe dd does it by itself. Have a google for linux commands.
hmm ok,
and why i get a bootloop when i want to flash the files with odin?
one more question ^^
how i can pull the complete /data partition to SD card?
And Creating a .tar file with 7zip commandline works, but the File is not flashable.
you can find the info in i9000 forum
http://forum.xda-developers.com/showthread.php?t=943588
http://forum.xda-developers.com/showthread.php?t=960946
http://forum.xda-developers.com/showthread.php?t=965190
Okay i have a 1 click Rom backup now ^^
But its still the problem that i get a bootloop after flashing...
Ok, I tested it and /data was wiped, phone can't mount sd card etc. etc.
tgm28 said:
Ok, I tested it and /data was wiped, phone can't mount sd card etc. etc.
Click to expand...
Click to collapse
Use THIS from HERE.
Quoting deskjeti.
deskjeti said:
Hi,
I made a Backup & Recovery Script in the German Android Hilfe Forum for the Galaxy 3.
The Tool make a flashable Rom with 3 Clicks and Restore the Backup with one Flash and one Click.
The Script restores all Apps, app Data Google Account and Wifi key´s.
How To:
Unzip the zip file wherever you want and plug in your Phone with USB Debugging Mode.
Run the Step1 and wait, after Step1 is finished run Step2 and if Step2 finished Run Step3
In the "Alexgalaxys G3 Recovery v2 Final" Folder now is a CustomRom.tar.
Flash it as One Package.
If the Phone is started plug the Phone in Usb debugging mode and Run the Recovery.bat after it is complete you have to reboot you Phone.
Link: http://www.multiupload.com/NV0CFVYV2I
Click to expand...
Click to collapse
Although I edited the files to just be one click.
Hi guys!
I suppose the thread was close so I hope it isn't wrong posting here.
after carefully reading the 12 pages of http://forum.xda-developers.com/showthread.php?t=884093&page=12
I'm still getting the "mismatch md5" error, it's really frustrating...
These are my procedures:
(right now I'm using MIUI 1.4.29 + EN Pack1_2.3) and CWM 3.0.1.4, and of course the SNS is unlocked.
-Download the stock rom "twice" from the two links from mediafile posted in the first thread. just to be sure they are the same files. First open the zip file with 7zip and run the "test" no error. Second test, compare md5 hashes from the 2 zip files downloaded --> matched. Third, extracted them (PC) and open the nandroid.md5 files with notepad++ and verify every files hashes -> matched
-Booted to recovery --> CWM 3.0.1.4 --> mounted usb storage
-extracted directly from the zip file to maintain the "clockwork\backup\2010-12-22.21.06.07" directory structure.
-unmount. restore --> mismatch md5
-open the zip file manually drag the clockwork to sdcard (extract and copy) --> unmount --> restore from 2010-12-22.21.06.07 --> mismatche md5
-deleted the previous folders, and create folder one by one manually the drag each file inside --> mistmach md5
Those are the steps I tried, I'm running out of ideas.
googled the issue and couldn't a single concrete answer to this problem... My guts is telling me is a directory bad naming, but I'm keeping it just as it is.
any help is appreciated!
Thx in advance
be sure you've got busybox
Code:
adb shell
cd /sdcard/clockworkmod/backup/[COLOR="Blue"]YourDate[/COLOR]
busybox md5sum *.img > nandroid.md5
then reboot to recovery to do a nandroid restore,does it do your job?
jonirrings said:
be sure you've got busybox
Code:
adb shell
cd /sdcard/clockworkmod/backup/[COLOR="Blue"]YourDate[/COLOR]
busybox md5sum *.img > nandroid.md5
then reboot to recovery to do a nandroid restore,does it do your job?
Click to expand...
Click to collapse
This will definitely do the job except in case the backup actually is corrupted.
I'm guessing that the backup is corrupted. It happened to me once when I backed up to try a new rom and decided to restore. Like what you had I got an error on md5 also.
Sent from my infin1ty powered Nexus S c",) using XDA Premium App
hello all,
this recovery is not ported by me, xda's senior member fun_ have ported this to many devices, and we using the one which is compatible with paladin, many many thanks to him, a link to original thread is here
requirements:-
1. a rooted phone, you can root your tab here
2. cwm recovery image which you can get here
steps:-
1. open file manager which can have root access
2. go to system and rename recovery.cpio.img to recovery.cpio.img.bak
3. put downloaded recovery in /sdcard
4. open terminal emulator
5. type su
6. type "inand_flash_image recovery /mnt/sdcard/recovery.cpio.img" (if you have put it in flash then replace sdcard with flash)
7. then boot into recovery by holding menu and power button together or by typing "reboot recovery" in terminal emulator
how to control recovery:-
# power button is used to select options
# menu button will take you up
# home button will get you down when pressed
some notes you should keep in mind:-
1. back button do not work in recovery
2. never try the key test option else you will get stuck
3. backup do not work for boot, xboot, mbr areas
4. do not flash any rom available for paladin, basic etc. devices (or you will have a hard bricked tablet)
a simple step to enable on-screen back button
as soon as you booted into recovery, press menu then home then again menu, a message will appear saying enabled ( can be done in every screen)
Cwm
Nt able to rename recovery.cpio.img to recovery.cpio.img from andro zip, es file explorer,terminal . . ? Any solution?
in terminal type
Code:
su
mv /system/recovery.cpio.img /system/recovery.cpio.img.bak
dheeraj (dhlalit11) said:
in terminal type
Code:
su
mv /system/recovery.cpio.img /system/recovery.cpio.img.bak
Click to expand...
Click to collapse
failed - read only file system . . . ? . . Any other way to rename this file
pbhasin21 said:
failed - read only file system . . . ? . . Any other way to rename this file
Click to expand...
Click to collapse
tab is not rooted root it first
http://forum.xda-developers.com/showthread.php?p=29100664
dude i followed ur steps, used root explorer to rename to bak, and then tried, i get kcrc32 file size not same. and then when i boot to recovery the whole screen goes berzerk with curtain falls and doesn't do anything. i renamed the bak file into normal and flashed it and got the old recovery.. could you tell me what im doing wrong? used your recovery.cpio.img 3.5mb file in my sdcard... doesnt work..
rooted karbonn smart tab
kcrc32 not same is normal
did the terminal flash the recovery 2 times
like:-
kcrc32 not same
then a hex address
flashing from /mnt/sdcard
kcrc32 not same
then a hex address
flashing from /mnt/sdcard
if you get something like above then it is flashed properly
dheeraj (dhlalit11) said:
kcrc32 not same is normal
did the terminal flash the recovery 2 times
like:-
kcrc32 not same
then a hex address
flashing from /mnt/sdcard
kcrc32 not same
then a hex address
flashing from /mnt/sdcard
if you get something like above then it is flashed properly
Click to expand...
Click to collapse
yup i got it twice, kcrc32 not same.
then i entered reboot recovery. thats when the screen goes all curtainfall like a crash, and recovery doesn't load. i had to use the reset pin and power button to turn on the tab again.. perhaps the img is not compatible with my tab?
btw mine is Karbonn Smart Tablet 2.
http://ncarry.nimbuzz.com/karbonn/product.php?product_id=2212
but when i purchased, it came with android 4.0 ics. everything else is same as in that page..
it is different
and I think that's why recovery is not booting
any suggestions mate? perhaps another ainol tab is similar to karbonn st2?
What if there is no "recovery.cpio.img" file in the system folder? This is after having root permissions...nothing has been done otherwise. I do not have a recovery file to rename and am unsure if it should still go in the system folder or not. It doesn't even have a file extension (I had to transfer it to my laptop just to check, and there's no .img or .zip...nothing.)
Also I keep getting the following message in terminal emulator when attempting to run the command:
sh: inand_flash_image: not found. The image file is in the /mnt/sdcard/Download folder. The full instance is:
[email protected]:/ $ su
[email protected]:/ # inand_flash_image recovery /mnt/sdcard/Download/recovery.cpio.img
sh: inand_flash_image: not found
127|[email protected]:/ # inand_flash_image
sh: inand_flash_image: not found
Any help?
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