Related
So I've never rooted my phone, but one day my phone just stopped responding.. it entered into an endless loop of that white screen.
I believe its due to water damage from steam/heat or something because when I took it in, they said the water damage sticker was activated... anyways, I'm able to get into reboot mode by hitting the power button + volume.
However, there are some errors that pop up:
E: Can't mount /dev/block/mmcblk0p1 (No such file or directory)
E: Can't mount SDCARD:update.zip
Installation aborted.
I tried plugging it into the PC to see if it is recognized but it is not...
Any leads on what I should do? My phone is completely stock with default software.
Thanks in advance!
If you can get it into 'reboot mode', you should be able to get it to download mode too.
First of all, if you look underneath where your battery is (so on the phone itself), you should see a bunch of numbers. One of them will be something like 1006,1007,1008,1009,1010,etc.
This is important, if the numbers are from 1006-1009 then follow these steps, but remember... nobody here is responsible for what you do to your own phone:
0. Make sure your USB isn't connected.
1. Download this: http://www.mediafire.com/?fr8bkogcu923wdu
2. Install the correct version for your computer (32-bit or 64-bit).
3. Download this: http://www.megaupload.com/?d=SBSMALFJ
4. Turn off your phone and pull the battery out.
5. Open the I897UCJF6-final-OCD-REV0.exe
6. Press the Volume + and - both at the same time and keep holding them
7. Put your battery in, and plug the USB in (never press the power button).
8. You should see a screen that says "Downloading now..." Or something like that.
9. Your Odin should show that your phone is connected (you can let go of the volume keys at this point), and just press on the 'Start' button.
10. Wait until it all finishes, NEVER pull the USB cable out.
If you're on a number that's 1010 or bigger, then tell me.
It says 1007. Trying now. Will keep you updated in the next 10 minutes
At the end of it all... It says device driver software was not successfully installed...
The Odin3 One-Click Downloader seemed to be successful though.
<ID:0/003> Firmware update start..
<ID:0/003> Sbl.bin
<ID:0/003> boot.bin
<ID:0/003> cache.rfs
<ID:0/003> dbdata.rfs
<ID:0/003> factoryfs.rfs
<ID:0/003> param.lfs
<ID:0/003> zImage
<ID:0/003> modem.bin
<ID:0/003> cache.rfs
<ID:0/003> Removed!!
I tried going into reboot mode after, and it says:
#Manual Mode#
-- Appling Muti-CSC...
Installing Muti-CSC
And it stalls there..
However, it's acting the same as before. Any other solutions?
Not really I'm afraid... I think it'll be best for you to try one more time, and if it still doesn't work try using this version of ODIN next: http://www.megaupload.com/?d=QL6NX702
venomio said:
Not really I'm afraid... I think it'll be best for you to try one more time, and if it still doesn't work try using this version of ODIN next: http://www.megaupload.com/?d=QL6NX702
Click to expand...
Click to collapse
I think your first post is the most recent version of Odin
How long ago did it get moisture in it?
one of the things to try(if it was fairly recent) take the SIM/Micro SD, if you have one/and battery out. Put the phone IN a small bag of rice for 24 hours. If there is any moisture left in the device the rice will absorb it. When you take it out, use a can of compressed air to blow out any residue
kangi26 said:
Try this version of Odin. I think it's the "latest"
http://www.mediafire.com/?0w2y31maz8mdom4
How long ago did it get moisture in it?
Click to expand...
Click to collapse
The same version as in my first reply... But it's the thought that counts
venomio said:
The same version as in my first reply... But it's the thought that counts
Click to expand...
Click to collapse
I just saw that and edited my post
it got moisture in a few days ago... 4? 5?
method still doesnt work with alternate odin version...
looks like im screwed...
it says movinand read fail
movinand checksum confirmation fail
-- movi_checking done!
edit: actually. I feel like there's hope. Now it shows the galaxy s screen after the att screen.... but still no luck.
Anyone know what the next step should be?
did you flash with your sd card in? no promises but i forget what or when but once, flashing with sd card in caused me to stall, now i just always do it, give it a shot.
How do I flash with my sd-card in? I'm sort of unfamiliar with the terminology...
xpiamchris said:
How do I flash with my sd-card in? I'm sort of unfamiliar with the terminology...
Click to expand...
Click to collapse
If you have a micro SD card, make sure you take it out before you start the Odin process
Sent from a autonomous device
Just to give an update, I've tried flashing with sd card both in and out.. and its the same..
Updated list:
When rebooting phone:
ATT World Phone Screen comes up
Galaxy S Screen Comes up
Screen goes black after.
Booting phone under reboot mode:
ATT World Phone Screen comes up
--Movi_check Start..!!
movinand read fail
Movinand Checksum Confirmation Fail
--movi_checking done!!...
update media, please wait
E: Can't mount /dev/block/mmcblk0p1 (No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet. please use UI menu for format and reboot actions.
copy default media content failed.
So after this pops up, I try to format internal sd-card, and this pops up:
update media, please wait
E: Can't mount /dev/block/mmcblk0p1 (No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet. please use UI menu for format and reboot actions.
When I try to reinstall packages:
Install from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.
(Still hoping there is a solution!)
Okay... this is the final step you can try.
This is the manual (or "full") Odin, it's taken from a post by icezar1 in the Development Forum:
Do not use this if you want to send your phone back to ATT or Samsung for warranty!
Do not use this if you know you flashed a -LOW- ODIN package (when opening the PDA***.tar or CODE***.tar you will find inside boot.bin or sbl.bin)
Use this if you want to go back to stock before flashing a custom ROM.
Use this without worries if you changed your boot screen image or if you flashed the secondary boot loader which allows you to enter download/recovery with key combos.
Download the package from here
Download the phone drivers from DG's thread if you dont have them already. [Note: You should already have this xpiamchris, it will be the same one I asked you to download and install]
How to:
Remove sdcard and SIM card from the phone
Extract JF6_secure.zip somewhere.
Boot your phone in Download Mode
Run Odin3 v1.3.exe
Plug in your phone via USB
Click on the button PDA
Choose JF6_secure.tar.md5
Click start
Wait and do not unplug cable until it is finished
I noticed on the reboot, the phone said "data wipe failed"
But phone is acting the same as before..
Hi,
I was attempting to update my P7310 to ICS and have flashed CWM 5.0.2.6 I then attempted to flash the alpha2 ICS release but it started flashing and then the device rebooted. I was able to boot back into recovery but it seems that the whole device fileystem is empty / screwed.
I have tried adb push of a file to /sdcard/ but it fails:
$ ./adb.exe push p5wifi_galaxian-soup-a2.zip /sdcard/wifi.zip
failed to copy 'p5wifi_galaxian-soup-a2.zip' to '/sdcard/wifi.zip': Not a directory
Is there any way of getting a new rom zip onto the device so that I can then update again through CWM "apply update from sdcard". Can I apply update from any other way?
I can push the file to the device root:
$ ./adb.exe push p5wifi_galaxian-soup-a2.zip /wifi.zip
1307 KB/s (96366459 bytes in 71.999s)
I can't run adb shell to do stuff either:
$ ./adb.exe shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Can I flash something that works through ODIN which still talks to the device..?
Im stuck and have ran out of ideas..any help appreciated
mj_blue said:
Hi,
I was attempting to update my P7310 to ICS and have flashed CWM 5.0.2.6 I then attempted to flash the alpha2 ICS release but it started flashing and then the device rebooted. I was able to boot back into recovery but it seems that the whole device fileystem is empty / screwed.
I have tried adb push of a file to /sdcard/ but it fails:
$ ./adb.exe push p5wifi_galaxian-soup-a2.zip /sdcard/wifi.zip
failed to copy 'p5wifi_galaxian-soup-a2.zip' to '/sdcard/wifi.zip': Not a directory
Is there any way of getting a new rom zip onto the device so that I can then update again through CWM "apply update from sdcard". Can I apply update from any other way?
I can push the file to the device root:
$ ./adb.exe push p5wifi_galaxian-soup-a2.zip /wifi.zip
1307 KB/s (96366459 bytes in 71.999s)
I can't run adb shell to do stuff either:
$ ./adb.exe shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Can I flash something that works through ODIN which still talks to the device..?
Im stuck and have ran out of ideas..any help appreciated
Click to expand...
Click to collapse
You're telling adb to push the file into a zip? Anyways, ADB sadly does not work in our CWM (nor USB mounting as you might have noticed), so the only way you can restore functionality and start again (no erasure of your SDcard contents so don't worry) is to use ODIN back to stock. From there, start again. It could be your download was corrupted (download again), because I could flash it fine, but eventually went back to KJ5 for functionality.
Edit: Check my guide below for ODIN FAQ and how-to if necessary.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
The clockwork I posted in the CM9 thread supports adb.
A bit late for that now though...
kallt_kaffe said:
The clockwork I posted in the CM9 thread supports adb.
A bit late for that now though...
Click to expand...
Click to collapse
Edit: Sent you a PM.
was there a resolution to this issue? i have the same exact problem as the OP.
However, I cannot restore back to stock with ODIN. when writing my system.img.md5 my restore fails.
I know my devices can be fixed! i just have not found my answer yet.
you need to copy the CWM flashable rom into the sdcard:
1st: Install CWM using Odin
2nd: enter CWM and go to "Mount" and mount /system (this will enable the shell)
3rd: now you can use "adb shell" and "adb push" to push your rom into the sdcard.
I remember this thing happened to me once, that the /sdcard directory was not found, but I don't remember how I solved it.
How about this.?
adb push files\your_files /data/media/.
Before that, please mount your /data partition..
Why? Because /data/media/... have the same content with /sdcard/...
Just check it, and tell me if it works...
ellokomen said:
you need to copy the CWM flashable rom into the sdcard:
1st: Install CWM using Odin
2nd: enter CWM and go to "Mount" and mount /system (this will enable the shell)
3rd: now you can use "adb shell" and "adb push" to push your rom into the sdcard.
I remember this thing happened to me once, that the /sdcard directory was not found, but I don't remember how I solved it.
Click to expand...
Click to collapse
suwandiapr said:
How about this.?
adb push files\your_files /data/media/.
Before that, please mount your /data partition..
Why? Because /data/media/... have the same content with /sdcard/...
Just check it, and tell me if it works...
Click to expand...
Click to collapse
Ok, so i'll let you know what my whole problem is. I am not starting a thread yet, because i believe the problem is the same.
I wanted to install overcome's rom on a United States, Galaxy Tab 8.9 WiFi Only. I rooted my devices just fine. The instructions with pictures told me to use ODIN to flash the modified version of CWM. now, in the picture i saw a pit file being used. it was called "android_fastboot_emmc_full_p4_16G_32G.pit". I found the file and I left 'Re-Partition' checked per the picture.
After this, I had no CWM, only downloading mode. I used ODIN to reflash the P7310XXKJ4. I put that in PDA. unchecked re-partition. it failed at writing system.img.md5
stock normal recovery was back, but i had no access to the sdcard, data, or anything else.
I then used ODIN (no more pit files anymore and no more re-partition) to flash the overcome CWM. WORKED.
So now i have access to CWM, but it cannot mount sdcard, data, nothing.
I purchased the sdcard kit so i could see if i could load up a ROM on an external SDcard and flash from there. NO DICE.
I refuse to believe this is over! but I am begging for someone's help.
Tonight, I am going to uninstall the drivers i have on win7. reinstall a fresh copy of KJ4. and see if that works.
I am open to ANY suggestions. I see that others are experiencing this problem, but there is no readily available solution.
wyatt23 said:
Ok, so i'll let you know what my whole problem is. I am not starting a thread yet, because i believe the problem is the same.
I wanted to install overcome's rom on a United States, Galaxy Tab 8.9 WiFi Only. I rooted my devices just fine. The instructions with pictures told me to use ODIN to flash the modified version of CWM. now, in the picture i saw a pit file being used. it was called "android_fastboot_emmc_full_p4_16G_32G.pit". I found the file and I left 'Re-Partition' checked per the picture.
After this, I had no CWM, only downloading mode. I used ODIN to reflash the P7310XXKJ4. I put that in PDA. unchecked re-partition. it failed at writing system.img.md5
stock normal recovery was back, but i had no access to the sdcard, data, or anything else.
I then used ODIN (no more pit files anymore and no more re-partition) to flash the overcome CWM. WORKED.
So now i have access to CWM, but it cannot mount sdcard, data, nothing.
I purchased the sdcard kit so i could see if i could load up a ROM on an external SDcard and flash from there. NO DICE.
I refuse to believe this is over! but I am begging for someone's help.
Tonight, I am going to uninstall the drivers i have on win7. reinstall a fresh copy of KJ4. and see if that works.
I am open to ANY suggestions. I see that others are experiencing this problem, but there is no readily available solution.
Click to expand...
Click to collapse
The thing is, none of the ODIN images (at least the 7310 ones I've seen) have this .pit file since it is not needed at all. The CWM available is just for wiping and flashing. I'm afraid adb does not work. I heard of a Recovery in the CM9 kang thread over at the Development section in which adb works if that's what you want. There are some ODIN links in my guide and all you need to do with the downloaded file is putting the biggest (and only) file in PDA, make sure "F. Reset Time" is clicked and forget about Repartitioning (it is NOT needed in this tab).
nirogu325 said:
The thing is, none of the ODIN images (at least the 7310 ones I've seen) have this .pit file since it is not needed at all. The CWM available is just for wiping and flashing. I'm afraid adb does not work. I heard of a Recovery in the CM9 kang thread over at the Development section in which adb works if that's what you want. There are some ODIN links in my guide and all you need to do with the downloaded file is putting the biggest (and only) file in PDA, make sure "F. Reset Time" is clicked and forget about Repartitioning (it is NOT needed in this tab).
Click to expand...
Click to collapse
I have done this. when i re-flash the odin stock image, i get stuck at the restoration of system.img.md5.
I uninstalled and reinstalled the samsung usb drivers and installed the latest. i've tried different usb ports. i am truly at a loss.
i installed an odin flashable version of CWM 5.0.2.6 (? i think thats the version), but adb was not available on that.
Does adb work on the stock recovery? Do you know where i can find this CM9 Kang thread? do you know if their version of CWM in flashable via Odin? that's the only way i can push anything onto the tablet as of right now.
btw... if i restart the tab unconnected to any USB cables, I get a message saying to reconnect to Kies and perform a recovery. IMHO kies is useless.
I am still stuck. I am open to literally anything not physically harmful to my tab.
Is nvflash an option for fixing this? I've never used it before, but if it can help I would be down.
---------- Post added at 09:49 AM ---------- Previous post was at 09:41 AM ----------
suwandiapr said:
How about this.?
adb push files\your_files /data/media/.
Before that, please mount your /data partition..
Why? Because /data/media/... have the same content with /sdcard/...
Just check it, and tell me if it works...
Click to expand...
Click to collapse
$ ./adb.exe shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
If i push files, they look as tho they are transferring, but i think they are not really making their way their on to the device.
After doing a little prying today at work, I found a .pit file. I read that this contains the partition information for drive.
I downloaded the stock 3.1 image, extracted it, and i found a P5.pit. Perhaps, I can use that PIT file, while keeping Re-Partition checked, and reflash the overcome CWM?
I know others have run into my exact problem and fixed it. there's gottttta be a way.
i will keep posting my progress and/or reading for others' suggestions.
When trying to flash KJ4 , i get the following:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P7310XEUKJ4_P7310XXKJ4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img.md5
<ID:0/006> NAND Write Start!!
<ID:0/006> bootloader.bin.md5
<ID:0/006> cache.img.md5
<ID:0/006> hidden.img.md5
<ID:0/006> recovery.img.md5
<ID:0/006> system.img.md5
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Then when looking at my galaxy tab screen i see the following:
Code:
Partition size is small! [Bin:173568 > Part:147968] (4KB unit)
WriteExt4Partition: Error to OpenCompExt4![err:0xa]
DownloadPartition_odin: Error to WriteExt4Partition![err:0xa]
Tegra_Nand_Write: Error to DownloadPartition_odin![err:0xa]
I have to believe my partition table is all botched.
wyatt23 said:
I have to believe my partition table is all botched.
Click to expand...
Click to collapse
I believe the PIT file you flashed earlier did something to the partition table. I really don't know where did you find that PIT file . I think I saw a PIT file from an Asian ROM for our tabs months ago, but it's not on XDA. Gonna look for it.
EDIT: Found it here. Attached is the PIT file so you don't have to download the whole package (just unzip the file and there it is). I know it is for the 7300 but I don't think partitions are so different between the two models. Try it with your preferred ODIN image and see if it solves the issue.
nirogu325 said:
I believe the PIT file you flashed earlier did something to the partition table. I really don't know where did you find that PIT file . I think I saw a PIT file from an Asian ROM for our tabs months ago, but it's not on XDA. Gonna look for it.
EDIT: Found it here. Attached is the PIT file so you don't have to download the whole package (just unzip the file and there it is). I know it is for the 7300 but I don't think partitions are so different between the two models. Try it with your preferred ODIN image and see if it solves the issue.
Click to expand...
Click to collapse
and should i keep 'Re-Partition' Checked?
---------- Post added at 02:21 PM ---------- Previous post was at 02:12 PM ----------
wyatt23 said:
and should i keep 'Re-Partition' Checked?
Click to expand...
Click to collapse
ehh, so i tried it without re-partition. didn't work. still cannot mount /sdcard.
tried it with repartition checked with clockwork 5.0.2.6 and I'm stuck at the "choose download mode or recovery mode" screen. if i select recovery, the screen blinks.
TO FIX THIS: I can use odin 1.85 to flash KJ4. however, this will fail at system.img.md5. However, stock recovery will be bootable. stock recovery will give me errors saying most of my partitions cannot mount.
I then can use odin to flash clockwork 5.0.2.6 and enter recovery.
the partitions are still botched if i go that route.
OK. so... i don't know what fixed it, but here's how things went down.
i stumbled across this website: http://www.tsar3000.com/Joomla/inde...14:samsung-flashes&catid=55:samsung&Itemid=82
i downloaded the stock odin flashable version of 3.1. i was able to use the stock 3.1 (even tho it said 32G) to get a working copy of android back on.
3.2 just would not work. however, 3.1 seemed to fix the problem of the partitions. then i flashed 3.2 right on top of it right away.
after that, i used odin to flash overcome's recovery and NANDROID!
now, i'm about to run overcome 3.2.
nirogu325, do you develop at all? I think you're up for a donation. thank you for all your help.
Glad to hear you fixed your issue, thought I'd add a few side notes as I had the same problem as you pretty much but fixed it at 3am and went straight to bed and was gonna post this morning.
For my situation I was doing it all on a lenovo T500 so for any1 using one flash with the usb port closest to you, in win 7 there seems to be a difference in this port possibly being the only port with always on charge feature, the drivers handle this port differently.
Install or reinstall drivers with the tab unplugged and only plug it in once your already in download mode.
I used the same pit file posted on the previous page and used the stock 3.1 pda, no csc or modem or bootloader files, would still hang wen other files were included. Re-partition checked. Only use pit file once, later flashes shouldn't require it as you've just rectified you partition table.
Once you got 3.1 on there then continue the 3.2 flashes as you wish and hopefully no more problems.
All done trough odin and please people take your time with these steps, the rom should only take 2-3 mins and if it pauses for more than 1:30, its hung, just press and hold power button leaving everything plugged in and odin open and go straight back into download mode and try again.
I've done this several more times with 8 more roms and havent had an issue with any (all morning). I've broken it on purpose then gone through these steps so that the information is as functional as I can make it.
I know its querky but hopefully this saves someone the anguish we went through.
Sent from my GT-P7300 using Xparent Blue Tapatalk
wyatt23 said:
OK. so... i don't know what fixed it, but here's how things went down.
i stumbled across this website: http://www.tsar3000.com/Joomla/inde...14:samsung-flashes&catid=55:samsung&Itemid=82
i downloaded the stock odin flashable version of 3.1. i was able to use the stock 3.1 (even tho it said 32G) to get a working copy of android back on.
3.2 just would not work. however, 3.1 seemed to fix the problem of the partitions. then i flashed 3.2 right on top of it right away.
after that, i used odin to flash overcome's recovery and NANDROID!
now, i'm about to run overcome 3.2.
nirogu325, do you develop at all? I think you're up for a donation. thank you for all your help.
Click to expand...
Click to collapse
Lol no I don't develop. But I am glad you found the way! That was the objective!
Sent from my SGH-T959.
Hello my honorable SGT colleagues, I managed to roll back from Overcome P7300 v2.3.0 to the Russian v3.1 stock ROM (PDA/CSC/PHONE) flashing it by Odin 1.85 together with p5_0614 PIT mapping table file kindly provided above by Nirogy325, however in my case in attempt to fix modem firmware. All operations including ROM re-partitioning went absolutely smoothly! However to my regret, this has not fix my problem – every ROM (either stock and custom) I used to try do not flash PHONE firmware properly, with basedband version always indicated as “unknown” in the system properties and GSM/CDMA modem not operable… this malfunction happened after Google map app inadvertently hanged up and I tried to shut down the tablet.. does anybody have a clue what happened with the damned tablet and what might be possible cure? Will be extremely grateful for any advice
Thank you!
Thanks wyatt23 & nirogu325. I had this exact problem and downloaded 7-8 pit files that weren't working until I found this. I was about to get a baseball bat and go Office Space on the tablet. It's working fine now and will get a custom mod as soon as it charges.
hi , i have problem with samsung galaxy s i9000 , when i start phone appears first samsung logo and goes in black screen , then over again non stop . Phone go into download mode and root menu , I start odin 1,85 and i set a new flash and everything else he wrote at the end " finish ok" , restarted phone and again nothing , please help me
ivojima1970 said:
hi , i have problem with samsung galaxy s i9000 , when i start phone appears first samsung logo and goes in black screen , then over again non stop . Phone go into download mode and root menu , I start odin 1,85 and i set a new flash and everything else he wrote at the end " finish ok" , restarted phone and again nothing , please help me
Click to expand...
Click to collapse
Would be great if you tried to explain what you tried to do with odin anyway.
what rom you tried to install?
ivojima1970 said:
hi , i have problem with samsung galaxy s i9000 , when i start phone appears first samsung logo and goes in black screen , then over again non stop . Phone go into download mode and root menu , I start odin 1,85 and i set a new flash and everything else he wrote at the end " finish ok" , restarted phone and again nothing , please help me
Click to expand...
Click to collapse
Who says?
Which Rom are you trying to use and what are you coming from?
If flashing ODIN for JVU Rom :
Use ODIN with PIT File
PIT File Incase you need it : LINK
Open Odin and select 512 .PIT, and put in your files for : CSC, PDA, MODEM.
Check Re-partition and don't touch any other settings.
Turn off your phone and put it in download mode by holding VOL DOWN+MENU+POWER.
Attach Phone
When you have all the files needed in ODIN, say JVU Rom for example as thats what we are using here
Click Start let it Run
Once complete you will see S logo on phone
Unplug Phone > Let it power up then Power Off > Again into Download mode
Then plug in Phone
Click Reset on ODIN then in PDA put in CF-Root Kernel File for JVU to be Rooted *File is included in ODIN Files*
Same again when you see S Logo on Phone unplug Phone Cable
Close ODIN
Let phone boot up ....
What I do now is go into
Settings > SD Card and Storage > Unmount SD and Wipe that and then at the bottom Wipe Format USB Storage
Before doing this make sure you have what you need from the phone as it will ERASE everything!
Enable USB Debugging by going to Settings > Applications > Development > Check USB Debugging
Plug in Phone and copy over your chosen Custom ROM that you want
Reboot into Recovery : VOL UP + MENU + POWER
Wipe the 4 things (probably know these... you should do)
If not you choose these by using the left side keys on the phone and to apply changes click Menu key
WIPE : data/factory reset > cache partition
Scroll down and go to advanced
Dalvik Cache > Battery stats
Go Back
Install ZIP (ROM) from Zip Card
Reboot Phone when complete... DONE!
Hope this helps a lot of people if not just ask here if you are still having issues to save peole posting same questions again and again
I made up the first part, but after the phone went into recovery mode
The screen shows the following:
installin update ...
successfully installed package.
- Copying media files ...
e: failed to mount / sdcard (file exists)
e: copy_dbdata_media: cant mount / sdcard your storage not prepared yet. please use meny VI for format and reboot actions.
meida files copy failed.
- Wiping data ...
Formatting / data ...
e: format_volume: rfs format failed on / dev/block-mmcblkqp2
Formatting / dbdata ...
Formatting / cache ...
deleting meta data
Data wipe failed.
- Appling Multi-CSC ...
installing multi-csc
Cant access to / system / csc / eng / system /.
successfuly applied multi-csc.
Flash dbdata.rfs as PDA in Odin 1.85. Reboot. Congratulate yourself.
Sent from my GT-I9000 using Tapatalk 2
Helpppp
I have exactly the same problem. I had froyo 2.2 im new to this odin all these settings. Yesterday i was tried rooting my phone and I did. but after I mounted a courrupted rom from the recovery. and my android doesn't want to load. I followed the same instructions you just gave him. on these posts but now when i turn on the phone its the logo comes and nothing loads. Only Downloading VOL DWN + MENU + PW is working.
Are you talking to me devildrake? No, your problem is different and you need to flash the rom again too, not just dbdata lol. Do this.
Flash Gingerbread, in Odin (I always used JW4 but JVU will be fine) with 512 pit file and repartition checked. Untick reboot. Once its finished, unplug the USB cable and take the battery out. Put the battery back in and boot into download mode. Reset Odin. USB cable back in. Tick reboot again. Put dbdata.rfs in PDA. Flash.
Should boot into gingerbread. I've done this a LOT of times... Then you can go back to Odin and root.
If that doesn't work then I'd download a different version of GB, download new 512 pit, and download a new dbdata.rfs. Must be one of those corrupt.
Sent from my GT-I9000 using Tapatalk 2
This may be the last chance to get back the needed important data (please don't ask the awkward question: why not back up the data first) .....
Tried the official SAMSUNG repair office, they said no way!!! Tried search the net and not much available either!
Any expert here can help?
Problem:
Galaxy Note 1 GT-N7000, possibly still in unrooted Ginger Bread, suddenly stuck at boot logo. Press+hold Power/Vol Up/Home brings the machine into recovery mode showing:
1. the green Android robot and yellow arrow out from a file box logo,
2. messages displayed:
<in red>
E: failed to mount /sdcard (I/O error)
E:copy_cache_media:Can’t mount /sdcard
Your storage not prepared yet, please use UI menu for format and rebootactions.
<in Red>
<in yellow>
Media files copy failed.
# MANUAL MODE #
-- Updating application …
<in yellow>
..<in red>
E: failed to mount /sdcard (I/O error)
E:copy_cache_media:Can’t mount /sdcard
Your storage not prepared yet, please use UI menu for format and rebootactions.
Copy application failed.
<in Red>
..<in yellow>
-- Applying Multi-CSC…
Installing Multi-CSC
Can’t access to ‘/system/csc/TGY/system/’.
Successfully applied Multi-CSC
<in yellow>
Then, the usual Android system recovery message <in blue> for reboot, apply update, wipe data/factory reset, wipe cache, test redbend fota displayed at the top part of the screen.
3. Tried wiping cache partition and reboot, no luck with the same situation after reboot.
4. The SAMSUNG repair office said it’s not the battery problem. All data will be gone for rebooting the machine.
The data are more important than the machine, ie, saving the data is more important than saving the machine.
Any suggestions and directions for a workable solution will be highly appreciated.
there is a possible way ... do at your on risk..
1. boot into dwonload mode and connect the phone to PC.. open odin and check if connecting fine
2. download philz kernel for for ICS/JB (tar version) and flash it using the PDA tab in odin. (This will not boot the GB rom but should give you access to CWM)
3.Once flash is completed, remove the cabe and battery.. put the battery back in and boot into recovery mode, (vol up+home+power) .. You should see CWM recovery
4. Contacts can be backuped up by doing a nandroid backup of your rom. for the data in InternalSD, go to mounts and storage and choose mount USB storage.
conect phone to pc and wait for the drivers to appear.
5. copy what ever data you need.
It is possible.
Flash CF Root Gingerbread kernel using PC Odin.
Drop into recovery and connect your phone to PC.
From ADB you'll be able to copy (backup) ANY file you need.
DO NOT perform factory reset / wipe data or you'll lose the data.
---------- Post added at 05:56 PM ---------- Previous post was at 05:54 PM ----------
Ohh yes nandroid backup too will work.
Easier way. Do a nandroid backup on recovery. Flash the same rom you were using. Advanced restore of data partition of the nandroid.
Thank you very much guys for all of your quick and valuable replies.:good::good:
Please excuse my ignorance as I’m only a dummy, actually the worst, an old dummy!!
In order not to make the suitation worse, I’d like to know/clarify the following details before proceeding to the suggested ways:
@nokiamodeln91:
1. Connected to PC with the N7000 in SAMSUNG logo display, opened Odin3 v1.85, ID:COM column shows <in yellow>0:[COM4] and Message column shows<ID:0/004>Added!!
Is download mode=press&hold [power+vol up+home] keys?
2. In the thread: http://forum.xda-developers.com/showthread.php?t=1901191
Trying to download philz-cwm6-n7000, found the following 5 tar files:
PhilZ-cwm6-XXLT5-OXX-5.03.0.tar.md5
PhilZ-cwm6-ZSLO2-OZS-5.03.0.tar.md5
PhilZ-cwm6-DDLSC-ODD-5.03.0.tar.md5
PhilZ-cwm6-DXLSE-OLB-5.03.0.tar.md5
PhilZ-cwm6-JPLSB-UAE-5.03.0.tar.md5
Which one is suitable for an UNROOTED GingerBread N7000 with csc/TGY/system?
Will try to follow the other steps after clarifying the suitable tar file.
@Boy124:
1. What is CF Root Gingerbread kernel? Where can I download a copy for an UNROOTED N7000?
2. Please elaborate on or direct me to detailed ADB procedures, preferably a step-by-step guide if not asking too much. I’ve downloaded adt-bundle-windows-x86-20130219. How to copy (backup) the contacts data?
3. Thanks for reminding not to wipe data and perform factory reset.
@projeto56 and Boy124:
Search a bit on nandroid. But how to add nandroid in the machine as it is (stuck in boot logo)?
The machine has not been flashed with any ROM since purchase. No modifications, flashing or anything, no rooting, just add apps (as said, I’m an old dummy!). When booting in recovery mode, cannot see any backup or restoring options
Hope you guys have enough patience to bear with me and answer the questions.
Thanks again.
@liway
CF Root is not necessary.
As nokiamodeln91 said flash PhilZ kernel with PC Odin - any version will do the job.
After flashing with PC Odin, drop into recovery. (home key + volume up + power)
Then back up your current ROM.
Flash Gingerbread firmware with PC Odin again.
Root it. If you have Titanium Backup Pro, you can directly restore data from a nand backup. Or restore data only after rooting your ROM.
Lemme know if you need further assistance.
liway said:
Search a bit on nandroid. But how to add nandroid in the machine as it is (stuck in boot logo)?
The machine has not been flashed with any ROM since purchase. No modifications, flashing or anything, no rooting, just add apps (as said, I’m an old dummy!). When booting in recovery mode, cannot see any backup or restoring options
Click to expand...
Click to collapse
Do this:
Boy124 said:
As nokiamodeln91 said flash PhilZ kernel with PC Odin - any version will do the job.
After flashing with PC Odin, drop into recovery. (home key + volume up + power)
Then back up your current ROM.
Click to expand...
Click to collapse
But afterwards, i recommend you to flash a JB stock ROM directly from your new recovery. And after you've set it up, you either restore your data from your nandroid, or you use titanium backup pro to restore only what you need (recommended).
Anyway, if you've set up your google account previously, probably your contacts are already saved in the cloud.
You need to connect the phone in download mode (vol down + home + power). Then volume up to continue. The screen should show downloading.
Now connect the phone to pc and use odin to flash any tar version of the kernel. (like ddlsc). Select on pda tab.
None of these kernels are suitable as it will not boot on GB. This is just for you to get into an advanced recovery to backup your data before you wipe and get your phone working.
Following the suggested procedures, set the machine in downloading mode to download PhilZ-cwm6-DDLSC-ODD-5.03.0.tar, the bar below KERNEL square in Odin becomes completely green with the Message displayed:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-DDLSC-ODD-5.03.0.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
It stayed at this stage for hours and seems stopped there.
Tried to boot it in recovery mode [vol up+home+power], this time only the boot logo with an exclamation mark (!) in yellow triangle. Odin message:
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Put back in downloading mode again, and the machine now is exactly at the same stage with the above message displayed and apparently halted at "NAND Write Start!!". The machine's screen remains in the downloading mode.
What should I do next?
Make sure kies process is not running in task manager. Use the main usb ports. Use samsung usb cable only. Reboot the phone in download mode and try again. The tar file should be in pda.
kies process is not running in task manager.
using one of the main usb ports.
Cannot locate the original samsung usb cable, using ordinary USB 2.0 cable. Will try to find the original samsung usb cable and try again later.
The tar file is in pda.
Thanks.
maybe a pciture of where file should be added in odin will help him/her. flashing kernel takes only seconds. as i can see drivers were properly installed from the descriptions above.
In Odin, I've ticked the box for PDA, then put the file with the whole path name for the folder in the column after PDA.
Tried again with
1. sure that all kies process is not running in task manager.
2. using one of the main usb ports at the back plate of a desktop PC.
3. Using an original samsung usb cable from Note 2 (should be the same as for this Note 1?),
4. The tar file is in pda, and path/location stated in the box after ticked PDA in Odin.
....
Still halted at the stage of NAND Write Start!!:crying:
did you reboot into download mode? you should not continue from a failed flash. reboot
restart the pc and run odin as admin.
disable any AV and Firewall softwares.
if still a no go then try on a different pc
Disconnected the machine. Taken away and put back the battery. Rebooted in download mode [vol dn+home+power].
Restarted the pc and run under a user with administrator right.
Disabled all norton internet security protections. Turned off modem/router connection.
Connect to Odin, still no go. Same situation, halted at NAND Write Start.
Will try to arrange another pc next day or so.
In the meantime, any other alternatives worth trying?
Even a bricked phone in download mode should be able to flash a kernel.
What you could try is unintall kies and usb drivers. And then download samsung usb drivers from developer. Samsung.com and install it again. Then try.
- deleted Kie and SAMSUNG USB driver. Restart the PC.
- reinstall samsung usb driver.
- restart in download mode and connect PC.
still no go!
to recap: using Odin3-v1.85 and PhilZ-cwm6-DDLSC-ODD-5.03.0.tar
diff PC seems to be the last option
though you could try this. download http://d-h.st/FVh. its the PIT file. Select the PIT file in PIT Tab.. and kernel in PDA tab..
make sure repartition is checked.. then flash again and see..
flash wit PIT and kernel.
In Odin, Set Partition shows up in the 1st square and message:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PhilZ-cwm6-DDLSC-ODD-5.03.0.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
seems halted there!
How long will I have to wait?
Good afternoon. I need help, URGENT!
I can say that I have some experience with S2, S3 and S4 currently with sufficient skills to perform upgrades, installations, restorations.
What happens, that recently got an S I9070 Advantage and how it was decided to perform the ROM 2.3.6 update to the ROM with CSC DBT latest 4.1.2.
Update fallhou to restart the first time (when you enter the recovery mode to format the cell) appeared the following error message:
E: failed to mount / efs (invalid argument)
E: failed to mount / efs (invalid argument)
# MANUAL MODE #
- Appling Multi-CSC ...
Applied the CSC-code: unknow
Successfully applied multi-CSC.
E: failed to mount / efs (invalid argument)
E: Can not mount / efs / log / boot_cause
E: Can not open / dft / log / boot_cause
Restarted manually and when you perform the initial settings of the Samsung, I get an alert with the following error:
The process com.google.process.gapps has stopped
Clicking Ok and proceed with the setup, but once you get to the last step I get the following error:
The SecSetupWizard stopped.
I click OK again, but this time returns the option to choose the language, making it impossible to access the cell.
Performed the downgrade to 2.3.6 it starts, it works normally, have the IMEI BACKUP, but I can not restore, need a form, a script to format the phone completely, even if you delete the IMEI.
Nor is it possible to install any CUSTOM ROM. Only this version that comes with the file. PIT, CSC and CODE.
Does anyone have a light, guidance?!
I look back.
Which firmwares were they exactly?
Sent from whatever the hell you want to think it is. I ain't yo mama.
I do not know the exact version 2.3.6 had, considering I got this phone yesterday. And knowledge to update other models, such as S2, S3, S4've downloaded the FW-Updates.com-Samsung GT-I9070-DBT-I9070XXLQE-1365486223 and gave this error when installing.
I found a complete FW Forum here to perform the downgrade, did, went back to GB, the phone works as usual, however, when you first start the errors appears to start in recovery mode:
E:failed to mount /efs (No such file or directory)
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
E:check_selective_file:Can't moun /efs
-- Copyng media files...
E:failed to mount /efs (invalid argument)
Sucessfully copied media files.
# MANUAL MODE #
-- Updating application...
Copying Contents.
Successfully updated application.
-- Appling Multi-CSC...
E:failed to mount /efs (Invalid argument)
E:multi_csc:Can't mount /efs
Multi-csc applied failed.
The following report from ODIN - Downgrade 2.3.6.
Added <ID:0/005>!
<OSM> Enter CS for MD5 ..
<OSM> Check MD5 .. Do not unplug the cable ..
<OSM> Please wait ..
<OSM> CODE_GT-I9070_I9070DXLD1_CL1068093_REV00_user_SEC_KEY_LD1_8G.tar.md5 is valid.
<OSM> CSC_GT-I9070-MULTI-CSC-OLBLD1_SEC_KEY_8G.tar.md5 is valid.
<OSM> Checking MD5 finished sucessfully ..
<OSM> Leave CS ..
<ID:0/005> Odin v.3 engine (ID: 5) ..
<ID:0/005> File analysis ..
<ID:0/005> SetupConnection ..
<ID:0/005> Initialzation ..
<ID:0/005> Set PIT file ..
<ID:0/005> DO NOT TURN OFF TARGET!
<ID:0/005> Get PIT for mapping ..
<ID:0/005> Firmware update start ..
<ID:0/005> GT-I9070_EUR_XX_8G.pit.md5
<ID:0/005> NAND Write Start!
<ID:0/005> EFS.img.md5
<ID:0/005> STE_boot.bin.md5
<ID:0/005> Cspsa.img.md5
<ID:0/005> Ipl.bin.md5
<ID:0/005> Kernel.bin.md5
<ID:0/005> Kernel2.bin.md5
<ID:0/005> Mem_init.bin.md5
<ID:0/005> Modem.bin.md5
<ID:0/005> Modemfs.img.md5
<ID:0/005> Normal.bin.md5
<ID:0/005> Normal2.bin.md5
<ID:0/005> Param.lfs.md5
<ID:0/005> Power_management.bin.md5
<ID:0/005> Ssgtest.img.md5
<ID:0/005> System.img.md5
<ID:0/005> Ums.rfs.md5
<ID:0/005> Userdata.img.md5
<ID:0/005> GT-I9070_EUR_XX_8G.pit.md5
<ID:0/005> Cache.img.md5
<ID:0/005> Hidden.img.md5
<ID:0/005> RQT_CLOSE!
<ID:0/005> RES OK!
<ID:0/005> Completed ..
<OSM> All threads completed. (Succeed 1 / failed 0)
Added <ID:0/003>!
The ODIN steps were right....but why do you have so much efs errors? Is your phone network locked?
Sent from whatever the hell you want to think it is. I ain't yo mama.
Cell functioning normally to return to GB, JB but it does not start. Dandos the errors mentioned in the first post (The process com.google.process.gapps has stopped and The SecSetupWizard stopped.) Getting a constant loop. I need a solution to completely erase (the S2 / S3 / S4 - there is a script that does all this procedure, but this model did not find anything.
I have the backup of the IMEI (if it is corrupted) and the program EFS_Pro_1.9.12_Release even in the most current version EFS_Professional_2.0.40_Release gives error when trying to restore.
The EFS errors are because the S Advance has a special way of storing the EFS, much different from the SII.
But EFS errors are not my forte, hopefully someone will be able to help you out.
Sent from my GT-I9070P
Installing the JB by ODIN:
<OSM> Enter CS for MD5 ..
<OSM> Check MD5 .. Do not unplug the cable ..
<OSM> Please wait ..
<OSM> I9070VJLPD_I9070ZTMLPD_I9070VJLPD_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished sucessfully ..
<OSM> Leave CS ..
Added <ID:0/005>!
<ID:0/005> Odin v.3 engine (ID: 5) ..
<ID:0/005> File analysis ..
<ID:0/005> SetupConnection ..
<ID:0/005> Initialzation ..
<ID:0/005> Get PIT for mapping ..
<ID:0/005> Firmware update start ..
<ID:0/005> cache.img.md5
<ID:0/005> NAND Write Start!
<ID:0/005> hidden.img.md5
<ID:0/005> kernel2.bin.md5
<ID:0/005> kernel.bin.md5
<ID:0/005> modem.bin.md5
<ID:0/005> normal.bin.md5
<ID:0/005> param.lfs.md5
<ID:0/005> power_management.bin.md5
<ID:0/005> system.img.md5
<ID:0/005> RQT_CLOSE!
<ID:0/005> RES OK!
I don't see any problem.....weird....
Sent from my GT-I9070P
SOLVED!! (Y)
SOLVED!
Procedure:
1) If you are with a Gingerbread rom, first have to migrate to a Jelly Bean
2) Now that you're with Jelly Bean, download the CWM Temporary, extract the files to a folder of your choice and move to your memory card.
3) Unplug the device and plug it into recovery mode
volume p / up + home + power
4) Select using the volume button the option "Apply update from external storage" and press the power
5) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
6) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
7) Select "Wipe Cache"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take out the battery and restart the device in recovery mode
10) The error message should no longer appear, now just install the Stock ROM Jelly Bean desired.
Likely that when you have finished installing the ROM it goes straight to the home screen, without showing that the initial setup screen.
In this case, only those who have backup EFS folder do the following:
1) To make the procedure you need to have installed on the device Es File Explorer and access to ROOT
2) Copy the contents of folder EFS backup that you did and put inside the folder / efs of your device. If asked if you want sobscrever content, press OK.
3) Made the above procedures, unplug the unit and plug into recovery mode
4) Do Wipe Data / Wipe Cache and Factoy
5) Now elecione using the volume button the option "Apply update from external storage" and press the power
6) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
7) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take off the battery switch on the phone normally.
10) You should open on the screen of your initial system configuration.
Download CWM: http://j.mp/cwm-temporario
Source: http://migre.me/flwBA
tiirabello said:
SOLVED!
Procedure:
1) If you are with a Gingerbread rom, first have to migrate to a Jelly Bean
2) Now that you're with Jelly Bean, download the CWM Temporary, extract the files to a folder of your choice and move to your memory card.
3) Unplug the device and plug it into recovery mode
volume p / up + home + power
4) Select using the volume button the option "Apply update from external storage" and press the power
5) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
6) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
7) Select "Wipe Cache"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take out the battery and restart the device in recovery mode
10) The error message should no longer appear, now just install the Stock ROM Jelly Bean desired.
Likely that when you have finished installing the ROM it goes straight to the home screen, without showing that the initial setup screen.
In this case, only those who have backup EFS folder do the following:
1) To make the procedure you need to have installed on the device Es File Explorer and access to ROOT
2) Copy the contents of folder EFS backup that you did and put inside the folder / efs of your device. If asked if you want sobscrever content, press OK.
3) Made the above procedures, unplug the unit and plug into recovery mode
4) Do Wipe Data / Wipe Cache and Factoy
5) Now elecione using the volume button the option "Apply update from external storage" and press the power
6) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
7) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take off the battery switch on the phone normally.
10) You should open on the screen of your initial system configuration.
Download CWM: http://j.mp/cwm-temporario
Source: http://migre.me/flwBA
Click to expand...
Click to collapse
this really can be solved?
Efs.img help
This procedure actually works if done with the files available in the posting. In my case solved this problem, but now face a bigger problem. My backup IMEI is corrupted, and you can not restore it.
I need a file EFS.img to perform some tests. Someone with courage and willingness to send me that file?!
HELP
Didn't work for me :crying:
PLS HELP
I did every step till 10 but after i can't continue cause secsetup wizard had stopped!!!
Sorry if im n00b
Help
I get my imei with *#06# (the correct).And i can phone others,so guess there is no problem with the efs folder :S
2.3.6 runs gr8 but 4.1.2 still doesn't.Help me!!!!!!
God....Tussi great hooo....
It worked perfectly......saved my phone....:good:
tgabor7 said:
I get my imei with *#06# (the correct).And i can phone others,so guess there is no problem with the efs folder :S
2.3.6 runs gr8 but 4.1.2 still doesn't.Help me!!!!!!
Click to expand...
Click to collapse
Hi, tgabor , I had exactly same problem, I have tried everything, finally I have come to the conclusion that it can be solved by service centre or some tools like octopus box. Buying those tools are costly option. I have taken my phone to service centre after flashing jb(my phone was in warranty) and they repair it within one day for free . before going to service centre you should wipe your custom rom count using triangle away. You can see your count in download mode.
Sent from my GT-I9070 using XDA Free mobile app
tiirabello said:
SOLVED!
Procedure:
1) If you are with a Gingerbread rom, first have to migrate to a Jelly Bean
2) Now that you're with Jelly Bean, download the CWM Temporary, extract the files to a folder of your choice and move to your memory card.
3) Unplug the device and plug it into recovery mode
volume p / up + home + power
4) Select using the volume button the option "Apply update from external storage" and press the power
5) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
6) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
7) Select "Wipe Cache"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take out the battery and restart the device in recovery mode
10) The error message should no longer appear, now just install the Stock ROM Jelly Bean desired.
Likely that when you have finished installing the ROM it goes straight to the home screen, without showing that the initial setup screen.
In this case, only those who have backup EFS folder do the following:
1) To make the procedure you need to have installed on the device Es File Explorer and access to ROOT
2) Copy the contents of folder EFS backup that you did and put inside the folder / efs of your device. If asked if you want sobscrever content, press OK.
3) Made the above procedures, unplug the unit and plug into recovery mode
4) Do Wipe Data / Wipe Cache and Factoy
5) Now elecione using the volume button the option "Apply update from external storage" and press the power
6) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
7) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take off the battery switch on the phone normally.
10) You should open on the screen of your initial system configuration.
Download CWM: http://j.mp/cwm-temporario
Source: http://migre.me/flwBA
Click to expand...
Click to collapse
what if i dont have the efs backup? can i still get the phone working?
tiirabello said:
SOLVED!
Procedure:
1) If you are with a Gingerbread rom, first have to migrate to a Jelly Bean
2) Now that you're with Jelly Bean, download the CWM Temporary, extract the files to a folder of your choice and move to your memory card.
3) Unplug the device and plug it into recovery mode
volume p / up + home + power
4) Select using the volume button the option "Apply update from external storage" and press the power
5) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
6) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
7) Select "Wipe Cache"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take out the battery and restart the device in recovery mode
10) The error message should no longer appear, now just install the Stock ROM Jelly Bean desired.
Likely that when you have finished installing the ROM it goes straight to the home screen, without showing that the initial setup screen.
In this case, only those who have backup EFS folder do the following:
1) To make the procedure you need to have installed on the device Es File Explorer and access to ROOT
2) Copy the contents of folder EFS backup that you did and put inside the folder / efs of your device. If asked if you want sobscrever content, press OK.
3) Made the above procedures, unplug the unit and plug into recovery mode
4) Do Wipe Data / Wipe Cache and Factoy
5) Now elecione using the volume button the option "Apply update from external storage" and press the power
6) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
7) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take off the battery switch on the phone normally.
10) You should open on the screen of your initial system configuration.
Click to expand...
Click to collapse
hi
my problem in step 6
my screen phone is off and phone will be restart and cwm can't be install : (
Aminhitman said:
hi
my problem in step 6
my screen phone is off and phone will be restart and cwm can't be install : (
Click to expand...
Click to collapse
I think there are 2 versions of CWM, one maybe not working on JB. Use right one.