I bought a CN version, but now try to change to WW version.
But when I try to change the firmware to WW, then I have a error .
status 7 assert failed: write_raw_image (" /tmp/blob" , "staging" )
the TF101 is already rooted.
Any idea how to fix that.
thanks
Are you trying to flash it from the CWM?
Use at your own peril! You have been warned!
You'll need adb on your computer and your TF in CWM recovery. Type in your PC terminal:
adb shell
that will put you in a shell. type the following:
mkdir /staging
mount /dev/block/mmcblk0p4 /staging
exit
flash your zip in recovery
after it finishes flashing, reboot and the blob should flash
In the mount command, the last three characters are zero p 4.
The blob flashing command looks for /staging partition or ...0p4. It copies the blob there and the TF is set up to flash whatever is in 0p4 when it starts up. /staging is not mounted in CWM, so we are just helping it along.
I have problem for the MTD device install, when connect to win7.
it said the device cannot start . so, when run the adb shell command, it said no device connect
If you are using my CWM recovery 3.2.0.1 you should be able to mount /staging from the mounts and storage menu. Just do this before flashing the update.
allen03 said:
I have problem for the MTD device install, when connect to win7.
it said the device cannot start . so, when run the adb shell command, it said no device connect
Click to expand...
Click to collapse
Did you turn on USB debugging in the settings/applications/development menu?
Related
You need a rooted device
1.Step
Patitioning your sd-Card
forum .xda-developers.com/wiki/index.php?title=SD_card_partitioning
here is a great Howto for this
2. Step
plug on your device via usb to the computer
if you don't have it enable usb debugging
now extract the zip from the Attachment into the root of your sdcard
3. Step
open and adb shell with
Code:
adb shell
now instert the folloing command
Code:
sh /sdcard/app2sd.sh
4. Step
to install app2sd youst press enter
after some time your phone should be reboot
info : on the x10 they will the led lights show you if there is an error
with the sdcard
but my script creates a failsafe it's on /data/appbak
it will be used if you had an sdcard malfunktion
please say me all errors you have
wolfilein
I may need to edit something because I get this error on my M003 (Via8505) :
mount: mounting /dev/block/mtdblock3 on /system failed: Invalid argument
mount: mounting /dev/block//vold/179:2 on /system/sd failed: Invalid argument
busybox is /busybox/bin/busybox
tet
rm: can't remove '/etc/mount_sd.sh': No such file or directory
Partitioned SDcad with three partitions 1. 7gig Fat32 2. 96MB Swap 3. (1GB-96MB) as ext2
System will not complete boot now. Sits at initial boot screen then goes dark. Never get to animated logos.
Time to reflash ROM
Wanted swapfile. If it's the issue I'll remove it and try again
wolfilein said:
You need a rooted device
1.Step
Patitioning your sd-Card
forum .xda-developers.com/wiki/index.php?title=SD_card_partitioning
here is a great Howto for this
2. Step
plug on your device via usb to the computer
if you don't have it enable usb debugging
now extract the zip from the Attachment into the root of your sdcard
3. Step
open and adb shell with
Code:
adb shell
now instert the folloing command
Code:
sh /sdcard/app2sd.sh
4. Step
to install app2sd youst press enter
after some time your phone should be reboot
info : on the x10 they will the led lights show you if there is an error
with the sdcard
but my script creates a failsafe it's on /data/appbak
it will be used if you had an sdcard malfunktion
please say me all errors you have
wolfilein
Click to expand...
Click to collapse
so there is a chance that I can brick my phone (kyocera zio 1.6) and since phone doesnt have a recovery i would be screwed? correct?
i would like to know as well...
jcaf77 said:
so there is a chance that I can brick my phone (kyocera zio 1.6) and since phone doesnt have a recovery i would be screwed? correct?
Click to expand...
Click to collapse
i've been looking into this as well and was wondering the same thing as jcaf.. i have 0 space on this phone and would love to be able to install stuff onto sd card, thanks in advance
please help me..I got on Xperia X8..
busybox: not found
mkdir failed for /system/xbin, file exists
[2]
rm failed for /etc/mount_sd.sh, No such file or directory
sed: cannot create temp file /init.rccfoXyj: Read only file system
:::finished going reboot now:::
and he keeps restarting after SE logo..
Does it work on i5800 with ROOT?
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
I have a Thinkpad 1838 25U tablet that is stuck at the boot screen after attempting to flash it with closckworkmod. I cannot access the internal storage files to restore the operating system and when I contacted Lenovo they suggested that I reinstall the operating system. When I try to do that in recovery mode all I get is an error that states "file_getprop: failed to stat "/system/build.prop" No such directory E:Error in /tmp/sideload/pack.zip (status 7) Installation aborted. Is there a way to access the internal storage files or a way to re-install the system when the tablet is soft bricked?
What happen was I rooted my tablet with RootDebugfs.bat and then I followed the directions to How to Install ClockworkMod Recovery on the Lenovo Thinkpad Tablet on the UnLocker site. Where I messed up was changing the command that was given in the directions. I opened the command prompt and entered each command:
adb push A2109_CWMrecovery-6.0.1.9c.img /mnt/sdcard/
adb shell
su
mount -o rw,remount /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.backup
dd if=/mnt/sdcard/A2109_CWMrecovery-6.0.1.9c.img of=/dev/block/mmcblk0p1
After trying that several time with no luck I changed the last command and file or directory to mmcblk0p5 instead of mmcblk0p1
dd if=/mnt/sdcard/recovery.img of=/dev/block/mmcblk0p5
After doing that my screen went blank and when I restarted it, it will not go past the boot screen.
I did back up my system as a backup.ab file. My OS is ICS 4.03 but when I try to re-install the updates on the Lenovo site I get the error message "file_getprop: failed to stat "/system/build.prop" No such directory E:Error in /tmp/sideload/pack.zip (status 7) Installation aborted."
Can anything be done to fix it. I am presently getting ready to start my 2nd semester of college in computer programming and I let my inexperience of commands get the best of me. And caused a big mess.
Is my tablet ruined. Lenovo service dept. said that since my warranty has expired I will have to pay $575 up front to have it repaired.
Any suggestions will be of great 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
Hey.
I got a Samsung Galaxy S4 Mini (I9190 3G version) and the device is rooted. Unfortunately, I wiped all my roms from the SDcard and no:crying:w I cant access my device.
I trıed to connect my device to the PC, but the PC detects the device; but not the storage. Therefore, I cannot transfer files from the computer to the device. I tried mounting the /system, /data and /cache. I got CWM recorvery v6.0.3.5.
I searched a bıt on the internet and I found out that I were needed to use ADB. I downloaded and placed my ROM ın the MODDED_FILE folder. I open the CMD and change the ADB to recorvery. When I have changed it, I choose the file and I push the file from MODDED_FILE to the /sdcard section. When I push it, it give me this message:
" daemon not runningç starting ıt now on port 5037 "
" deaemon started successfully "
su
mount -o rw,remount -t ext4 /dev/block/mmcblk0p8 /data
mkdir /data/media/rr
exit
exit
" # su
/sbin/sh: su: not found
" # mkdir /data/media/rr
" # exit
C:/Users/XXXX/Desktop/ff/tools/tmp1
----------------------------------------------------
pushing cm-10.2.1.3-serrano3gxx.zip to /data/media/rr ....
------------------------------------------------------
The ADB tool is stuck here. I have waited many hours and tried again and again.
The PC wont detect my storage.
I tried to set the external sdcard onto my computers SDCard slot, and placed the ROM in the external sdcard. I tried to install the zip, but it gives me the error;
(bad)
İnstallation aborted.
Thank you for fast answers.
needs
can921 said:
Hey.
I got a Samsung Galaxy S4 Mini (I9190 3G version) and the device is rooted. Unfortunately, I wiped all my roms from the SDcard and no:crying:w I cant access my device.
I trıed to connect my device to the PC, but the PC detects the device; but not the storage. Therefore, I cannot transfer files from the computer to the device. I tried mounting the /system, /data and /cache. I got CWM recorvery v6.0.3.5.
I searched a bıt on the internet and I found out that I were needed to use ADB. I downloaded and placed my ROM ın the MODDED_FILE folder. I open the CMD and change the ADB to recorvery. When I have changed it, I choose the file and I push the file from MODDED_FILE to the /sdcard section. When I push it, it give me this message:
" daemon not runningç starting ıt now on port 5037 "
" deaemon started successfully "
su
mount -o rw,remount -t ext4 /dev/block/mmcblk0p8 /data
mkdir /data/media/rr
exit
exit
" # su
/sbin/sh: su: not found
" # mkdir /data/media/rr
" # exit
C:/Users/XXXX/Desktop/ff/tools/tmp1
----------------------------------------------------
pushing cm-10.2.1.3-serrano3gxx.zip to /data/media/rr ....
------------------------------------------------------
The ADB tool is stuck here. I have waited many hours and tried again and again.
The PC wont detect my storage.
I tried to set the external sdcard onto my computers SDCard slot, and placed the ROM in the external sdcard. I tried to install the zip, but it gives me the error;
(bad)
İnstallation aborted.
Thank you for fast answers.
Click to expand...
Click to collapse
have to installed cwm?
is odin able to detect your device?
[email protected] D€\/¡! said:
have to installed cwm?
is odin able to detect your device?
Click to expand...
Click to collapse
Hey.
Thank you for fast answer.
No, I do not get any message in Odin saying "Added" when plugging in my device. I have installed Samsung USB drivers too.
get it into download mode then try as odin work in download mode only