I recently recovered my phone through ODIN and then upgraded to JI6 through Kies.....I wanted to re-root the phone and get it back to where it was before, but I'm having problems. I loaded the root file and put the update.zip in the root (not the avatar folder) and tried to update packages through recovery. I get an error message that says e:can't open /sdcard/update.zip no such file or directory. I checked the file type in both drives (avatar is on e: and everything else on g, the avatar folder shows a FAT file type, but the g: drive shows an unknown file type. I had received information to try a different update.zip file, but it won't change the error message I get when select update packages in recovery. What can I do? I've searched a lot of posts (and I risk a flaming on this one, I know), but I can't seem to find one that seems to follow my trail of getting to where I am at today. One last thing, when I was recovering through ODIN, i did not select repartition because i could not get the 512 pit file to populate in ODIN. Thanks to anybody who can help me (again).....
gtiryan said:
I recently recovered my phone through ODIN and then upgraded to JI6 through Kies.....I wanted to re-root the phone and get it back to where it was before, but I'm having problems. I loaded the root file and put the update.zip in the root (not the avatar folder) and tried to update packages through recovery. I get an error message that says e:can't open /sdcard/update.zip no such file or directory. I checked the file type in both drives (avatar is on e: and everything else on g, the avatar folder shows a FAT file type, but the g: drive shows an unknown file type. I had received information to try a different update.zip file, but it won't change the error message I get when select update packages in recovery. What can I do? I've searched a lot of posts (and I risk a flaming on this one, I know), but I can't seem to find one that seems to follow my trail of getting to where I am at today. One last thing, when I was recovering through ODIN, i did not select repartition because i could not get the 512 pit file to populate in ODIN. Thanks to anybody who can help me (again).....
Click to expand...
Click to collapse
ok....
are you SURE you are putting update.zip on the right sd card....it goes on the INTERNAL CARD ( the 16gb one )...
I'm pretty sure I am, this is the one where all of the apps and apk were stored previously?
ok then start over...
odin back to stock and re-root
ok, ODIN back to stock. No change for the update.zip. This time when I flashed I added the pit file, and also checked repartition. No change in anything regarding the message or anything from before. I have tried tyhe update before and after I went from JFD to JI6. I really have no basis to speak from, but it seems that the path from my e drive (avatar) to g drive (everything else), is where the problem is, or else I got a bad flash. They all look the same though. I assume I would need root to get anywhere other than JI6 anyway. Thanks again for your help with this. I do appreciate it.....
gtiryan said:
ok, ODIN back to stock. No change for the update.zip. This time when I flashed I added the pit file, and also checked repartition. No change in anything regarding the message or anything from before. I have tried tyhe update before and after I went from JFD to JI6. I really have no basis to speak from, but it seems that the path from my e drive (avatar) to g drive (everything else), is where the problem is, or else I got a bad flash. They all look the same though. I assume I would need root to get anywhere other than JI6 anyway. Thanks again for your help with this. I do appreciate it.....
Click to expand...
Click to collapse
ok....
1. when you Odin you are supposed to load both pit and tar files and not check repartition...
2.read that...http://forum.xda-developers.com/showthread.php?t=849028
3. are you trying to go to a stock JI6 ROM?? If so...why??
My suggestion:
Click on the Noob Guide (signature)
Download files
Load ODIN
Get phone in download mode
follow my instructions in the guide
You will then have a stock froyo leak + root
at that point I would backup, then flash something, maybe NeroV3 and then enable voodoo (if you like).
I don't see how the alt method could lead you wrong.
I apologize, I sincerely didn't notice anything that mentioned not to partition. Going forward, if I reflash through odin with the right pit and tar files WITHOUT checking partition, do you think I should be ok? As a note (if it even matters), all of my files and things were still in the internal sd card, although the new market is there from my old 2.1 rom. Not sure if it matters, just more information.
gtiryan said:
I apologize, I sincerely didn't notice anything that mentioned not to partition. Going forward, if I reflash through odin with the right pit and tar files WITHOUT checking partition, do you think I should be ok? As a note (if it even matters), all of my files and things were still in the internal sd card, although the new market is there from my old 2.1 rom. Not sure if it matters, just more information.
Click to expand...
Click to collapse
just follow s15274n's guide...he wrote a nice guide for noobs (no offense)...it'll walk u through going back to stock and you'll be ok...
Excellent information, but one question since I'm still learning. Not in the way I had hoped, but trial-by-fire.....If I download the leaked froyo with root, don't I need root access first. Also if I can flash this through ODIN, where does the update file go in the ODIN screen, do I need the 512 pit file, what about the pda, phone csc windows, what do i poopulate in those options, if any. I do bow to your experience and knowledge. I promise once I get back to where I was before I may never do this again! All this from trying to flash a new kernal that was supposed to be compatible with all bionix platforms (I was running 1.9 w/jac's ocuv). Thanks again....
gtiryan said:
Excellent information, but one question since I'm still learning. Not in the way I had hoped, but trial-by-fire.....If I download the leaked froyo with root, don't I need root access first. Also if I can flash this through ODIN, where does the update file go in the ODIN screen, do I need the 512 pit file, what about the pda, phone csc windows, what do i poopulate in those options, if any. I do bow to your experience and knowledge. I promise once I get back to where I was before I may never do this again! All this from trying to flash a new kernal that was supposed to be compatible with all bionix platforms (I was running 1.9 w/jac's ocuv). Thanks again....
Click to expand...
Click to collapse
(sigh)....
ok in Odin....as long as the phone is in Download mode...Odin has root access to the phone(technically) so just make sure you're in download mode...
Odin needs 2 files to flash a VIBRANT to stock...the pit and tar files...load the pit file in the PIT field and the tar goes in the PDA field..( i know its tricky) dont mess with any other settings...click start and WAIT
Odin is a flasher's best friend....learn to use it and you'll love it
In process now. I do like ODIN although yesterday afternoon, I would have rather taken a sharp instrument to the neck rather than use it. I preferred to use ROM manager or other methods. I know it means nothing to you guys that have experience, but this is a learning experience and one I am grateful for with all of the experience on these forums. I know you devs don't like these dumb questions, but sometimes kids just want to be professional football players but end up working in a supermarket instead....get back to you soon.
it said updating firmware then it's sitting on cache.rfs for about 5 minutes. no green loading symbol like when I flashed before. Not sure if I should unplug and retry....
waited about 20 minutes with it stuck at the cache.rfs line. Unplugged and retried. Same thing. I need to get a working phone at least for tonight. I tried one more time, but check repartition and it started loading completely. Maybe there's something wrong with one of the files? Not sure. Will update when I get home to my laptop.....
Use this version of ODIN (older versions are known to hang)
http://forum.xda-developers.com/showpost.php?p=8863820&postcount=138
The files you need to get the leaked froyo + root: CLICK HERE TO DOWNLOAD
(IGNORE THE OLD OLDN VERSION IN THIS .ZIP - USE THE ONE I POSTED ABOVE)
1 - download the files to your pc
2 - open ODIN on your pc
3 - connect USB to pc (not to the phone)
4 - power off phone
5 - go into download mode (hold both volume keys... then insert usb to the phone)
6 - ODIN should be connected, and you should be in download mode
7 - load pit file
8 - load tar file
9 - click start
10 - it will run it's course, once done the phone will reboot
11 - once rebooted, go to stock recovery and wipe data/cache (I made this bold below for emphasis since not in the video)
I gotta hand it you guys, you really bailed me out and for that I am eternally grateful. I will have to scrape the funds together for whomever needs a donation, but it is well worth it. I have one last remaining question. Now that I have Eugene's Rom, am I safe to flash another ROM by update.zip, or is ODIN the only reliable way for me to get one on the phone. I like the phone better now, but it seems like it is an out of the box ROM, which is fine. I didn't mind bionix 1.9 on 2.1 either. I just made a big mistake. Anyways, thanks again, and whomever can answer my last question I will extend my thanks in advance!!
Download rom manager
Flash cwr
Make backup in cwr
D nownload nero v3
Flash it in cwr
Enable voodoo if you desires
Enjoy your much improved phone that has a stable backup for an emergency.
I you need detailedsteps for this, read my sticky threads.
I dowloaded ROM manager last night and flashed recovery. I went to recovery and applied packages. I'm still getting this error that says the update.zip file is invalid through my e: drive (avatar folder). I just looked on both e and f. I can't seem to find any update.zip file on either card and I can't seem to flash any other ROM or even enter CW recovery. I looked at another post from someone and noticed that I never pulled my external sd card when I used ODIN to go back to stock or flash Eugene's ROM that I was suggested to use. Any formats I could try or tricks to suggest. I've looked around, but I'm not sure if this is a partition issue, an sd card (internal or external), or otherwise. Thanks again....
i noticed that there were a lot of additional file in places i didn't notice originally. I found in the CW file a recover-update and I thought that might be confusing things, I put it in a seperate folder and retried cw recovery, but that didn't work.
Hi,
I bought my 10.1v in July and I was very happy with it. Soon, I realised that HC 3.0.1 was a bit unstable and very basic...
I started looking for an update to 3.1 or above and found nothing (ad still there is no update).
So, 2 weeks ago I was looking for good guides for rooting my tablet and installing a Custom ROM.
And found many different and many good ones.
It's been a week since I last touched my tab, so I can't exactly remember what I did or who's guide I followed (a couple different ones actually).
The problem is: I'm kinda a noob at this. Well, a total noob actually...
But I got the bootloader unlocked and the I got root access, or the other way around...
Anyway I got it unlocked and rooted, erased all the user data and went back to factory settings.
Started the tab and got the setup and etc etc... (Last time it booted)
I activated USB Debugging and Unknown Sources as I was going to install HDBlogGalaxy ICS v2.2.
I (kinda) followed the guide with the ADB.exe in the cmd window.
Then CWM Recovery, install from SD Card, choose HDBlogGalaxy ICS v2.2 and it seemed to have it installed it okay.
Then it got stuck at the boot and I started playing in the CWM Recovery... (stupid of me...)
I might have changed the partition SD Card, wiped everything and more.
So now I'm left with a non booting tab with:
Access to fastboot
Access to Odin3
Apparantly no access to ADB
Unable to mount USB (in CWM) ->error: Unable to open ums lunfile (No such file or directory)
Unable to mount /efs (in CWM)
maybe more things, as I'm not very familiar with flashing android stuff
I tried flashing over a stock rom with Odin3 but it gets stuck at boot.
I can boot CWM Recovery with fastboot, but can't get access to internal memory to copy over a Custom Rom.
I tried nvflash but I keep getting the error: Nvflash started, rcm version 0X4, command send failed (usb write failed).
I'll accept any advice and I will be immensely grateful if someone could help me my fix my tablet.
Grtz, Aythamie
Bricked Galaxy Tab 10.1v
I'm in exactly the same situation and I'm looking for a hopeful Fix
Hopefully some genius developers on here can help us out.
I see you posted this a while ago did you get it solved? If so could you let me know how you fixed it?
Cheers
(CM9 Build 20120502 dated 2012-05-03 06:19:39)
I'll start off acknowledging my idiocy...I started tinkering with things I knew too little about. I messed up my phone fairly severely today, but managed to get it up and running again...with one issue. I no longer have a cellular connection (voice or data). I was having trouble the last couple of days, as I couldn't access the "More..." settings under "Wireless & Networks", but I figured it was a bug in whatever release I was running at the time and would be resolved eventually. I semi-borked my phone early in the afternoon (I repartitioned the internal storage incorrectly), but it was still able to connect. I then really borked it by tinkering with the partition tables. I was able to get that restored via parted restoring the GPT and doing some magic I didn't quite catch. I had previously attempted to flash back to stock via heimdall at one point, so I had an unrooted kernel and whatnot. I managed to flash a kernel with CWM, which allowed me to restore my last nandroid image. I've tried flashing a new modem. I've tried a complete wipe (data, cache, dalvik cache), but I get no connection. I have wireless, so that's something...but definitely not optimal.
Is this fixable? Should I try re-restoring to stock (from a workable state this time) and starting over from scratch? I have a rooted stock nandroid that I'll probably try restoring tomorrow. Could this actually be a hardware issue that just happened to show up at the same time I borked the rest of the phone? Any help/advice you have is appreciated!
EDIT: I've flashed back to stock, including flashing the bootloaders and param file. On first boot after flashing, I get the following error:
Code:
-- Appling Multi-CSC...
E:failed to mount /efs (Invalid argument)
E:multi_csc:Can't mount /efs
Multi-csc applied failed.
If I click "reboot system now" the system will boot, but without service. I can still hop on wifi if available, but I have no phone, and no data away from wifi.
EDIT 2: I fixed it, and I'm putting the info up here in case someone comes across this post. I downloaded [urlhttps://play.google.com/store/apps/details?id=com.helroz.GSII_Repair&feature=also_installed]GSII_Repair[/url] from the market, and stepped through the first two steps of the repair process. After step 2, it tells you to reboot. Once I rebooted, I was up and running. I will be making a complete backup of efs.img and the rest of my system just in case I do some stupid tinkering again, and if you're here, I'd advise you do the same. It appears this can spontaneously happen based on a couple of other, less stupid methods (at least according to the comments on the app).
I would flash back to stock using odin or heimdall. Give yourself a clean slate to start over. I don't think that it is hardware related as it was working before you started tinkering.
So I flashed my original stock (rooted) image, which didn't help. I then heimdall-flashed back to pure stock. Still no go...however, it then booted directly to stock recovery with an error: "failed to mount /efs". After another couple of searches, it appears that normal flashing doesn't touch this. Given my phone is already pretty messed up, is there a good way to try fixing this?
The entire text in the stock recovery is:
Code:
-- Appling Multi-CSC...
E:failed to mount /efs (Invalid argument)
E:multi_csc:Can't mount /efs
Multi-csc applied failed.
SUCCESS!!! I downloaded GSII_Repair from the market, and started stepping through the "repair" steps. After step 2, it said to reboot. I rebooted. I now have signal, and can make calls.
I was really starting to think I was screwed there for a minute.
Let me just start out by saying I'm a nube with limited skills. I have a Samsung Showcase SCH-S950C for Straightalk. I was sitting around on saturday and decided I would figure out how to root my phone because I had nothing better to do. I followed the instructions in a forum on this site and was able to root with no issues. After that I of course then decided to try my hand in flashing a custom rom to the phone (cyanogenmod) and this is where i went wrong. After flashing the rom I booted the phone and now the rom won't load and is stuck saying, "Unfortunately, setup wizard had stopped" and "Unfortunately, the process android.process.acore has stopped." The only menu I can get into is the sound menue via the volume key.
The next step I took was to reboot the phone back into CWM to see what I could do. Upon loading I was faced with the below errors.
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Tried wiping the cache, factory reset and wiping dalvik and am unable to do so. It won't mount the cache, data or datadata. I then tried to put it back to stock via instructions for flashing a recovery mod for the phone and that did not take because I cant wipe it. From what I read i need to repartition the phone to fix this issue but I do not know how and honestly not even sure exactly what that means. As I said to start Im a nube. I also noticed in USB mode it says i now have 4 custom binarys on the phone and Im sure that is not helping things.
This is the point I stopped so as not to completely FUBAR the phone, if I have not already done so. If anyone can point me in the write direction on how to proceed I would greatly appreciate the help.
Look for odin and some related rom of your phone. Flash again. Normally problem would be fixed.
Sent from my XT901 using xda app-developers app
Probably non-useful information
I know nothing about the Showcase, so please accept this information for instructional purposes only.
I had zero experience with anything Android related until September. I successfully used old flip style or otherwise non-smart phones, so never had any experience with any version of Android (or any iOS either for that matter). My brother-in-law had given my parents a Fascinate that he replaced with a Note. It sat around their house until I picked it up and decided to see what I could do with it. I found this guide to be exceptionally helpful:
http://forum.xda-developers.com/showthread.php?t=1238070
Whereas I don't know if any of this information is relevant to your Showcase, the operational theory may relate. The phone that I was given was already rooted so I used the instructions in the guide to use Odin to return the phone to stock, then update to a Jellybean ROM. I learned a great deal working through the process a couple times, and have since been given a first gen Kindle Fire, an LG Ally, and a Droid Charge that I had enough confidence to work with, and successfully rooted and flashed each.
Hey folks,
a friend of mine owns this GT-I9300. After leaving it on overnight, it wouldn't boot the following morning.
He asked me, if I could somehow fix his phone but now after hours and hours of browsing through forums and flashing at least a million different PITs and firmwares, I'm desperate enough to write an own thread for this issue.
He has never flashed or rooted that thing in any way.
I first tried to get into the stock recovery, but it immediately told me that it couldn't mount /efs (This file or directory doesn't exist), nor could it mount /system, /cache, or anything else for the same reason.
I hoped to get some order into this chaos by flashing an original firmware, but this didn't solve the problem either.
After my last attempt (flashing a 4.0.4 Stock Firmware [since I read in a thread that this solved the problem]), the phone would now not even get to the boot logo nor the recovery but is just a criss-cross, snowy frozen screen when turned on.
The only thing that worked (and still works) is the download mode.
So I tried to flash another version, but then Odin told me that there was no partition!
I accordingly browsed the web and found a firmware consisting of three parts + a PIT partition.
But that still does not work.
Can anyone somehow help? Or can the phone not be resurrected?
Thanks in advance.
Your emmc chip is toast, new motherboard required. Have a read of the dead boot resurrection thread in general forum.