Related
Long story short: When restoring via Nandroid it hangs, when using advanced restore the data portion says
E:Can't mount /dev/block/mmcblk0p2
(file exists)
Error mounting DATA:!
Click to expand...
Click to collapse
This afternoon I tried running the Voodoo zip, but the one I downloaded from their site isn't for the Captivate. I ended up with a phone that was constantly displaying 90 degrees off from what it should have been (holding it straight up had the phone thinking I had it on its side).
I decided to uninstall voodoo by creating the "disable lagfix" folder on my card. I rebooted and the phone hung and remained hung at the spinning progress wheel for an hour. I pulled the battery since I couldn't get out of that screen. Rebooting after that had me in what appeared to be the stock version and showed a few of my non-stock apps as "com.etc..." apps.
More reading on here and I found the Captivate-specific version of Voodoo. I figured I'd try to install that before restoring from the Nandroid backup I ran before installing the Voodoo. However, when in recovery mode I couldn't "click" anything with the power button. I tried using adb reboot recovery which didn't fix the problem and instead put me into a non-stop cycle of non-functioning recovery modes after boots.
So I used Odin to get back to stock. Now I'm trying to restore back to where I was before Voodoo. I tried to just run a simple Restore but it hung and after 90 minutes it hadn't completed. So I tried to run an advanced restore and all sections restored except for Data. When I try to restore Data i get the error at the top of this post. I've googled for an answer and everything I've read so far is Cyanogen specific and appears to require Cyanogen to fully fix it. Anyone know how to fix this on a Captivate? Anyone have a link that I'm missing?
Thanks!
If you can boot the phone, then go into android terminal emulator (you may have to download it from the market first) and type mount in the terminal. See what type of partition /data is. If it's ext 4, the disable lagfix was not finished before you pulled the battery. Your best bet then is to download the Captivate voodoo beta 4 kernel version 1.6, which is sticky post in the Captivate development forum here, remove the disable lagfix folder/file from /sdcard/Voodoo/ and let it boot. It will then get you to the point where you should have been at first without having rotation issues and with a kernel that understand ext4. After that, restore your phone to the way it needs to be with Titanium, or by manually downloading and reinstalling any apps that got deleted by your premature battery pull. When ready to do a nandroid backup, do a disable lagfix and let it fully reboot to convert the ext4 to RFS. Then you can do a nandroid backup of restore, as clockwork recovery does not understand ext4 (yet).
Thanks Rajendra! I'll try that and follow up with the results.
I used Odin again to bring it back to stock, which appears to have given it back RFS formatting on data which means I'm able to restore to it now.
However, my restore is hung on one file and has been for a good 25 minutes now. Is it normal for it to sit on a file? Anything I can do to skip/bypass the problem file or find out what it is? All it says is '-274738110' for the file.
Duplicate post (no way to delete I guess?)
RobertDeBord said:
I used Odin again to bring it back to stock, which appears to have given it back RFS formatting on data which means I'm able to restore to it now.
However, my restore is hung on one file and has been for a good 25 minutes now. Is it normal for it to sit on a file? Anything I can do to skip/bypass the problem file or find out what it is? All it says is '-274738110' for the file.
Click to expand...
Click to collapse
Try this - once the phone boots - then go to internal sd card and see if there is a Voodoo folder (which there still should be) inside the Voodoo folder make a folder called disable-lagfix - reboot and it should go through the reverse process of creating the lagfix (robot voice). After it finishes reboot go to rom manager and restore.
Hope This Helps....
I can tell you, I've never had a successful restore from rom manager/clockwork recovery. Not once! The only thing that program is good for is as a replacement recovery reboot, it lets you select which zip you want to install from, rather than having to manually name everything to "update.zip". I can't honestly think of anything else its good for. I've tried literally dozens of restores on my captivate and everyone of them has crashed or frozen at some point during the restore. Worthless!!
Hello,
Like many other users on this forum, I am having trouble with my i9000M sdcard after doing some ROM flashing.
Although there is some extensive threads collecting the different situations people are experiencing, I was hoping I could get some help for a specific circumstance relating to the sdcard issue.
I'll start by..
- Detailing the firmwares I have flashed, and what happened
- What is working / not working now, and how I got to get to the current situation
- And finally, I'll detail what I'm trying to do and where I'm getting stuck.
I would really appreciate some help with this, and thank anyone who takes the time to read it. I am trying to be very thorough to give you as much information as possible.
-----------------------------------------------------------------------------
1. Started with stock firmware. I am not sure what it was.. I believe the phone is equivalent to the Bell i9000M, but I am on the SaskTel carrier.
2. Flashed firmware I9000XXJP2: This worked, and I was using Froyo 2.2 fine.
3. Tried to root Froyo 2.2 firmware: This FAILED and the trouble began. I was using the update.zip method, and the source claimed it was compatible with 2.2. I had to hard reboot the phone, but it would stall on the white text intro screen (not the animated one).
4. Went into Download mode. Tried to flash firmware I9000UGJH2 (apparently the most current bell firmware), using Odin v1.1. This FAILED, and I had to hard reboot, which resulted in the PHONE - ! - PC error. I am aware the i9000M can still be recovered from this state.
NOTE: I could do nothing at this point: all firmware flashes failed, UNTIL I CHANGED TO ODIN V 1.3!
Using Odin v.1.3:
5. Flashed a series of firmwares.. (I9000UGJG8, I9000XXJM1, I9000XWJG5), ALL resulted in the phone either being in a shutdown-boot loop to the white Glaxaxy text screen, or the battery charging screen.
I could enter Download mode to reflash, but NOT recovery mode.
6. The ONLY semi working firmware is I9000XXJP2, Samsung Froyo 2.2. This is what the phone is now.
- I CAN enter Download mode, Recovery mode, and the phone stalls on the white Galaxy boot screen, but goes no further, and does not restart.
- I CAN run abd commands
Here is the output I get from each of the options in the Recovery mode:
Code:
I9000XXJP2
Odin 1.3
512.pit
Flashes fine
Goes into recovery mode
Displays error:
(No such file or directory)
E:copy_dbdata_media: Can't mount SDCARD
your storage not prepared yet. please use UI me nu for format and reboot actions.
copy default media content failed.
Try to format sdcard:
Formatting SDCARD:...
ensure_root_path_unmounted**
ensure_root_path_unmounted (/mnt/internal_sd)
ensure_root_path_unmounted ret 0
ensure_root_path_unmounted It's not mounted
update media, please wait
E:Can't mount /dev/block/mmcb1k0p1
(No such file or directory)
E:copy_dbdata_media: Can't mount SDCARD
your storage not prepared yet. please use UI me nu for format and reboot actions.
Try to wipe cache partition:
-- Wiping cache...
Formatting CACHE:...
ensure_root_path_unmounted**
ensure_root_path_unmounted (/cache)
ensure_root_path_unmounted ret 0
unmount (/cache) attempt 1 (Unknown error: 0)Cache wipe complete.
Try to apply sdcard:update.zip
Same errors as 1) can't mount sdcard therefor installation fails.
Reboot system:
- Will accept adb download reboot
note: I can reach download mode using the button combination
- recovery mode: can access with button combination or 'adb reboot recovery'
- power off: battery charging indicator shows
note: it does not loop the battery indicator
- power on: stalls at Galaxy S GT-19000 white lettering screen.
note: i recieve an indication on windows desktop that a device has been connected which is capable of USB high speed point
ADB COMMANDS WORKS: device is detected
Things I have tried:
I tried booting into a Ubuntu Live cd to see if I could format the sdcard, as suggested in this thread: (sorry, forum won't allow me to hyperlink, thread id=759910)
The disk utility picked up the Samsung drives (One was labeled something like Samsung_Galaxy, and the other Samsung_Galaxy sdcard, but I'm not 100%) but could not format them. There was also no info being listed about the size.
Things I would like to try / have hunches on:
Before all this happened, I made a Nandroid backup of the orriginal firmware, and copied it from the i9000's sdcard to my computer. I made the backup using Rom Manager's Clockworkmod.
Is there a way to use Odin to flash Clockworkmod, so I can restore this backup?
-everything out there says to use Rom Manager, which I can't access because the phone is pseudo dead.
Will the backup even still be on my sdcard?
Wait, my sdcard isn't mounted.. can we try mounting it with abd? (I tried, but am not sure of the command / path of how to do this..
Can abd be used to restore my backup stored on my computer? Is this dependent on the sdcard being mounted?
I fully appreaciate those you take the time to read through this as it is rather lengthy. I just want to ensure I have tried every means to revive the device, and hopefully some more skilled users can help with the mounting and adb syntax.
All comments and ideas are welcome and appreciated! Thank-you
Sorry to be the bearer of bad news. But time and time again this error has proven to be a hardware error. Mine did the same thing and samsung/bell had to replace the mainboard in my phone. Good luck, but unfortunately, anything you do further is a waste of time short of sending it back for repair.
Hi there
I've unfortunately gotten a faulty devices and I'm suppose to get it switched with a new device. (another story about not being able to make calls, scrathing sound etc)
I've rooted my phone and it worked flawlessly, but today I wanted to un-root and would install the apps i've removed with root explorer. Therefore I downloaded a system/ dump and tried restoring the "app" directory in system/ with root explorer. This resulted in random force closes
Then I used "adb" su to copy all the app files from sdcard (where I copied the files from the dump) to the system/app directory. After a while it was done and I type reboot... [Bricked?]
Now the phone keeps rebooting. Getting the LG logo with sound and afterwards the LG logo with progress bar... then rebooting...
I need help
djkoch said:
Hi there
I've unfortunately gotten a faulty devices and I'm suppose to get it switched with a new device. (another story about not being able to make calls, scrathing sound etc)
I've rooted my phone and it worked flawlessly, but today I wanted to un-root and would install the apps i've removed with root explorer. Therefore I downloaded a system/ dump and tried restoring the "app" directory in system/ with root explorer. This resulted in random force closes
Then I used "adb" su to copy all the app files from sdcard (where I copied the files from the dump) to the system/app directory. After a while it was done and I type reboot...
Now the phone keeps rebooting. Getting the LG logo with sound and afterwards the LG logo with progress bar... then rebooting...
I need help
Click to expand...
Click to collapse
Try to hard reset, turn off your phone press volume - and power.
Thanks for the response... When I press power+volume down, the "unpacking box with android person" appears for a 20 seconds or so... the reboots and I'm back to rebooting constantly
When I try pressing volume down and home key/returnkey I can get in to S/W update mode, but I cant get the ADB to work?
Other suggestions?
That's why its a bad idea to delete stock apps in the first place when we don't have custom recovery yet.
gensplejs said:
That's why its a bad idea to delete stock apps in the first place when we don't have custom recovery yet.
Click to expand...
Click to collapse
It wasnt a problem when deleting them, and the phone was alright... it was when restoring through ADB it went wrong... I need a suggestion to get it fixed not an "I-told-you-so"
Yeah... sorry... i was kinda an ass.
But sadly I'm all out of ideas.
Maybe if we had a service manual (not user manual)
Sent from my LG-P990 using XDA Premium App
Can you connect to phone by adb?
You need to clear dalvik cache.
Hi Doc
No... unfortunately I cant get ADB to work....
I can get into S/W update mode, but ADB doesnt work. I can get the Factory reset to begin too, but it just gets into the reboot circle again.
If there was just a way to get into ADB mode I could push every single file again
Damn... I hope it isn't bricked for good
If HR doesn't work. Just return for warrenty.
Cause if it reboots that a corrupted boot.img
Try to see if you can get alist of apps installed on phone.
If superuser.apk is not in there, return it for warrenty.
In one of the reboots I think I had a glimse of a connection thru ADB acouple of times. I had approx. 10 seconds before rebooting again.
Did a list... and guess I saw a dir called "root" but didnt have time to get into the system/app directory...
If we can't find a solution I think I'll try to return the phone and hope for a new one without any question asked
Have you tried putting it in sw update mode and running the LG update tool?
http://www.lg.com/dk/support/mc-support/mobile-phone-support.jsp?countryCd=dk
Might do the trick
Yes I've tried the LG update tool. It says it has a new update, but the current firmware version doesn't show, and when I'm trying to do the update It aborts and says that the phone cannot be updated...
I just tried the Factory Reset and you can abort the reset when the "unpacking box" is showing by pressing the home key. Then you get into the 3e recovery menu... But there no way to select an option. Would have tried to wipe cache partition and data/factory reset. In the text it only says "formatting DATA:..., Formatting CACHE:..., Formatting MISC:..."
djkoch said:
Yes I've tried the LG update tool. It says it has a new update, but the current firmware version doesn't show, and when I'm trying to do the update It aborts and says that the phone cannot be updated...
I just tried the Factory Reset and you can abort the reset when the "unpacking box" is showing by pressing the home key. Then you get into the 3e recovery menu... But there no way to select an option. Would have tried to wipe cache partition and data/factory reset. In the text it only says "formatting DATA:..., Formatting CACHE:..., Formatting MISC:..."
Click to expand...
Click to collapse
There in no way to restore you phone now because we don't have any tools that's work with optimus 2x.
Bring it back to retailer and say that phone is just not booting and you want a replacement.
Edit: Well... discount the advice below for the time being... I've found myself in the same position and the commands below don't work.
My phone is also now useless...
I replied to your thread over at MoDoCo, and although the thread has gone off track it does have Paul's attention.
djkoch said:
Yes I've tried the LG update tool. It says it has a new update, but the current firmware version doesn't show, and when I'm trying to do the update It aborts and says that the phone cannot be updated...
I just tried the Factory Reset and you can abort the reset when the "unpacking box" is showing by pressing the home key. Then you get into the 3e recovery menu... But there no way to select an option. Would have tried to wipe cache partition and data/factory reset. In the text it only says "formatting DATA:..., Formatting CACHE:..., Formatting MISC:..."
Click to expand...
Click to collapse
Oh dear.
I tend to agree, whilst it will be recoverable it could be very time consuming.
A factory reset will wipe cache and dalvik cache, so that's not your problem.
Neither is boot.img your problem, that will be intact.
However, if you can't get a console (via adb or terminal) you're in a difficult position.
Try issuing the 'stop' command in your brief adb window to see if you can preserve the shell.
Code:
$ su
# stop
If you can then try and mount /system rw
If you can do that then you can possibly self recover... by carefully and selectively adding files to /system/app/, rebooting and trying, again and again.
Hi All:
My Sprint Tab P100 got some strange problems.
It's a second hand P100, Once i turn on the tab, it will warning with 3 Beebee, and nook & Amaza Mp3 & Market will report error.
Below warning will show up:
Amazon MP3_nook
“The application XXX has stopped unexpectedly, pls try again”
Market
"Attention:
An Error has occured, Please try again later."
After check, i found the original usr information still there.
(Gmail/Facebook account will try to sync with previous owner's ID. and i can not remove the account.)
What i have tried:
1) I have tried to WIPE using system recovery, after WIPE both data & Cache partition, issue still exist.
2) Perform the Samsung factory reset by enter *2767*3855# in the Memo, problem still there.
3)Format the SD card with Phone & Windows, still got problem
4) Flashed with the stock EA24 Rom from XDA(with Modem,using Odin), the problem still remain the same.
5)Flashed with DJ30, the problem still exist(Base/Fireware EA24).
6)Tried to install CWM, failed to boot up(Rooted before install CWM, after flash the Zimage to Kernal or recovery, some strings flush in the screen, then the tab hung at Samsung logo and reboot.)
I guess those problem was caused by some program information still remain in the internal storage, even after factory reset or flash with other ROM.
Can somebody help on this? Also prefer someone can help on how to install CWM
I am interesting that the OVERcome 2.01 Rom got a version to WIPE the internal storage, but the OVERcome rom are designed for GSMer. Can i tried to use it to clear my internal storage?
just installed Astro, the program will crashed when launch it
Can some one help on this topic?
I am suspecting my internal storage was locked to Non-Writable.
This might result CWM can not access the internal memory caused the failure of the installation.
Is it related to the Flash lock option in the Odin?
Check this thread..
http://forum.xda-developers.com/showthread.php?t=1133053
That has the stock files, and instructions to get root and CWM installed with the stock software. Using Odin to put the stock firmware (EA24) should wipe anything and everything off the tab and restore it to as if it were new out of the box. You also might want to wipe your sd card as it can cause issues with the CWM ext4 conversion.
Hi pvtjoker42 & All:
During the process of Kernel with CWM Recovery, i has been stopped @ step7
1) Download the zip file here
2) Unzip the file. You will need the file named zimage only.
3) Open Heimdall Frontend
4) Select Browse under Kernel and navigate to the file you downloaded in step 1 and select it
5) Press Start
6) The Tab will reboot, but will freeze on the Samsung logo. Turn it off and boot into recovery (Vol Up + Power)
~~~~~~~~~~~~~~~~~~~~
my tab failed here, no matter what you pressed, it doesn't go to CWM. Do u have any idea?
~~~~~~~~~~~~~~~~~~~~
7) CWM Recovery will attempt to back your tab up, but will fail. Don't fret.
8) Do a factory reset in CWM Recovery and reboot
9) You'll freeze on the Samsung logo again Turn it off and boot into recovery.
10) CWM Recovery will back your Tab up successfully.
11) You now have a CWM backup. Reboot.
12) Your auto rotate is broken.
13) Download the rotation file
14) Put it in /system/lib/hw and change the permissions to match the other items.
Can someone helps?
Today i tried 1 more things, Use a update.zip to update the tab from EA24 to EB28,before try this, i have tried OTA to EB28, it never success.
i download the update.zip from <forum.sdx-developers.com/index.php?PHPSESSID=99sdnmh5pm4rtuv39hk80f7du6&topic=13104.0;nowap> it seems to be official one, and the recovery is the stock version, but it failed again.
I start to believe that my internal storage has been locked, and data can not write in.
Is it possible to due to Fstab issue?
Pls helps to save my tab....
There is only one thing to do : return to stock. Carefully follow the guide. Don't do anything else to your tab, until you go through the restock steps :
http://forum.xda-developers.com/showthread.php?t=1133053
[SPRINT] Sprint Tablet Owners Thread (Root, ROM, Flash to stock, CWM Recovery)
The process reformats/repartitions your internal sd card, and sets the correct permissions. If this process fails, there is probably something wrong with the tab.
you might also try to select the option to repartition in Odin when going back to EA24. Then try the steps to get EB28 OTA update, and once you've got that up and running, you can try the update.zip to get to EF17 (gingerbread, as long as you don't need root)
I wouldn't. Try a different sd card
Sent from my Nexus S 4G using Tapatalk
Hi All:
Thanks for the advice.
I have tried to back to stock EA24 using odin, but the situation still ramain the same.
And it fail to OTA to EB28, the EB28 upgrade program will reboot the machine, and enter recovery model. but it will complete the program. also i have tried to put EB28 update.zip in the SD card, but also fail to upgrade to EB28.
I have repartition the phone by P100 serveral time using odin, also tried update Pit file. All failed.
I have format the SD card in Windows & then in Android, useless.
Now i have some clues:
In P1000 rom Roto-JME, there is Movinand.bin, this one got same name as the internal storage IC from samsung. i am thinking that file could be a file similar to partition table.
Can someone help to dump a "movinand.bin" for me from P100?
steps:
1)Get back to stock EA 24
2)Wipe Cache & factory data
3) Root it (Using superone click , you can find it here http://forum.xda-developers.com/showthread.php?t=803682)
4)Install terminal (i use better terminal) or using a ADB to connect to shell.
5)Type "su", check whether "$" change to "#" in the shell
6) Type “dd if=/dev/block/mmcblk0p2 of=/sdcard/movinand.bin bs=4096”
7) Find the Movinand.bin in the SD card
You can sent it to me by drop a email to [email protected]
If there is anything wrong, pls help to correct me
Thanks in advance
as some people is asking how did i fix the issue, just publish the information here.
I fixed the issue by replaced the internal storage (the chip), cost about US$ 30(RMB 200)
If anyone have better solution, just post here to share
**I've searched, asked, tried many different files--still boot loops**
tl;dr What files do I use in Odin to return to stock from a phone that boot loops? (i have no idea what software was on there before it started)
The phone came from Canada (Bell). Previous owner tried to unlock it for use in the US. Phone worked for a few days then turned off & wouldn't get past boot (it would show animation & sound then go into a black screen with menu/back key lit up). It was also missing volume up/down keys. Phone was given to me as I was moving back to Canada. Now here I am in Canada...
I've ordered & replaced the volume keys, got into download mode, and using Odin I've flashed "I9000XXJVU_I9000OXAJVU_OXA". I've no idea what software version was on the phone at the time. I used pit 512. The phone reboots and...
Code:
-- Copying media files...
[COLOR="Red"]E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet. please use UI men
u for format and reboot actions.[/COLOR]
Meida files copy failed.
-- Wiping data...
Formatting /data...
Formatting /dbdata...
Formatting /cache...
Deleting Meta Data
[COLOR="Red"]Data wipe failed.[/COLOR]
-- Appling Multi-CSC...
Installing Multi-CSC
Applied the CSC-code 'KOR'
Successfully applied multi-CSC
The failed actions are due to me not having an SD card correct? And at the bottom there it says it applied the CSC-code 'KOR' for Korea? I'm in Canada.
Now the phone goes into a loop, flashing the "Galaxy S GT-I9000 Samsung" logo on and off for ever (no animation or sound this time). I also tried flashing the latest from sammobile (under GT-I9000M). It's a single file and that put me in a boot loop as well.
Any advice greatly appreciated!!!
Try this:
[HOWTO] Flashing CWRecovery to i9000m & upgrade to ICS AOSP 4.x ROM from any version