Related
***************SOLVED*******************
Hey, hoping some android gurus can help me out here.
I had the latest version of Obsydian on my phone and have not had any issues. Yesterday, my battery on the phone died, and when it started up again I was getting forcecloses all over the place. Tried reinstalling the rom and go errors, tried a different rom and got errors. So I ODINed the Voodoo RFS fix, followed by stock+Voodoo-Froyo-T959-UVJL5.tar , and didn't get anywhere.
I thought there might have been something wrong with the data on the phone so i tried clearing and formatting everything through Clockwork recovery. Then I tried the partition SD Card through clockwork recovery. I assumed it was the EXT-SD it was formatting so i chose 128mb ext, 32 swap, and left the rest for fat32. However, I'm starting to think it might have been the internal SD card.
I tried ODINing back to stock stock using this guide: http://androidspin.com/2010/08/09/h...droidSPIN+|+Your+No.1+source+for+Android+news.)
I get the phone in ODIN and it flashes, no errors in ODIN, but when the phone leaves download mode and goes to installation it gives a few errors:
Code:
MBR Checksum Error
Movinand Checksum Confirmation Fail
Then it continues installing, and I get another error:
Code:
Wiping data
Formatting Data
[B]Data Wipe Fail[/B]
Formatting Cache
It still acts like it completely finishes the installation, reboots, I get the Tmobile boot and then Galaxy S, and then I get a black screen with all 4 of the lights/buttons on the bottom of the screen on. It can sit like this for 30 minutes, it doesn't do anything.
I still have access to download mode, and I still have access to recovery, however it's no longer ClockworkMod recovery, it's the stock recovery, and it seems to only work for a few moments before going to a triangle with an exclamation point and the android logo.
Any ideas on what I can do to make this phone functional again, or acceptable for a warranty return?
I appreciate any help.
Welcome to the club
Check out my post http://http://forum.xda-developers.com/showthread.php?t=887837
Post #3 it might help if it does let me know so we know for sure if it works
Yes welcome to the club!!! glad you could join us!
Anyways here is what I have learned/done, my only working rom currently is the eugene froyo, can use the phone and data BUT cant download anything or install anything. You can adb push apks into the rom though. Heres the link for it
Use Odin, pit=512, pda=eugene..tar Run this to get semi working rom
http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=3
Once here I have access to my Sd card, this is where I placed the clockwork recovery on as an "update.zip" Link to this is posted below
http://forum.xda-developers.com/showthread.php?t=734164
Boot into recovery, note this will take you to stock recovery. REINSTALL update, may have to do this twice but itll get you to the Clockwork recovery....
After this I tried to install two different roms and both times I get some sort of data error, and installation aborted....hopefully this will help a few people
Yeah a bit more google searching for "vibrant mbr checksum" brought me to the same conclusion, that I needed to ODIN the eugene's froyo - it's flashing right now. Will see where that gets me.
It's my belief that using the SD partition in CWM is what caused the MBR issues and the Data Wipe Fail, as others said they messed with a partition in either CWM or something else prior to this happening
And that's a no go. It just reboots back into the stock recovery every time after odining it, with some new errors.
update media. please wait.
E:Can't mount /dev/block/mmcblk0p1
(Invalid argument)
E:copu_dbdata_meda:Can't mount SDCARD:
your storage not prepared yet. please use UI menu for format and reboot actions.
copy default media content failed.
Click to expand...
Click to collapse
I take it back - i did the wrong one apparently.
Had to use the files located on the link you sent, inside of the Eugene_2E_JK2_Froyo.zip file. Apparently there are a few different download files on the first post of that link. This one took longer than all the others I'd tried ODINing, about 5-6 minutes, compared to 2-3 for the others. I had also updated my Odin3 to v1.7, from the v1.3 I was using before.
When it booted up, it gave me an issue with my external SD card, said it was formatted incorrectly, so i formatted it from the phone - it says I have 13gb memory and 1.86 on the ext-SD.
Was able to download and install ROM manager from the market. Attempting to install Nero v3 now.
*** SOLVED ***
I've succesfully installed a rom other than Eugene's froyo, and did not receive any installation errors! Got Nero V3 up and running, very happy.
Note that the MBR checksum error still appeared but did not affect installation at all. Thanks everyone for their help - hopefully this helps the others.
I just got a tablet from the outlet, but it can't boot up. It shows the android logo in small yellow text, then a <!> pops up. Reboots in viewsonic logo, and gets stuck at gtablet logo. I tried holding startup and vol + but that doesn't work. Help please!
EDIT: Thank this guy rcgabriel
rcgabriel said:
The solution is simple -
1) Download clockwork mod recovery (cwmod_internal.zip) from the sticky thread in the Dev forum (http://forum.xda-developers.com/showthread.php?t=865245). Unzip it, and get the file called recovery.img and put it in the directory you ran nvflash from before.
2) Now go to your nvflash directory. Find the gtablet.cfg file. Edit it - under partition 9 where it says filename, change that to say recovery.img.
Now re-run nvflash - your G Tablet will get flashed with Clockwork Mod now instead of stock recovery. Once it's finished, reboot, and hold down the Vol + key while booting. You should get into Clockwork Mod Recovery now.
From here, I recommend repartitioning (use 2048 and 0 as the two options). Now try booting normally and everything should work fine.
Let me know how it goes!
Click to expand...
Click to collapse
Gajun said:
I just got a tablet from the outlet, but it can't boot up. It shows the android logo in small yellow text, then a <!> pops up. Reboots in viewsonic logo, and gets stuck at gtablet logo. I tried holding startup and vol + but that doesn't work. Help please!
Click to expand...
Click to collapse
it's not broken - just flash the latest firmware
Try an nvFlash. Mine was stuck at the Viewsonic logo this pas weekend with the recovery (Vol+ and power) not working either. The nvFlash was very easy to do and fixed my Tab.
http://forum.xda-developers.com/showthread.php?t=861950
g1no23 said:
Try an nvFlash. Mine was stuck at the Viewsonic logo this pas weekend with the recovery (Vol+ and power) not working either. The nvFlash was very easy to do and fixed my Tab.
http://forum.xda-developers.com/showthread.php?t=861950
Click to expand...
Click to collapse
thanks for the reply. I tried this, but it didn't help at all. I was able to do all everything but it is still stuck on the gtablet logo. I can go to apx mode fine but I can't go to recovery mode, it reboots back to and gets stuck ;/.
Gajun said:
thanks for the reply. I tried this, but it didn't help at all. I was able to do all everything but it is still stuck on the gtablet logo. I can go to apx mode fine but I can't go to recovery mode, it reboots back to and gets stuck ;/.
Click to expand...
Click to collapse
Okay, the reason recovery mode is doing that is that's what stock recovery mode does - retarded, but that's it - it just tries to install a file called update.zip in your SD card main area.
As for why the ROM itself won't boot in regular mode - I've had the same problem after nvflashing from bekit's image when my data/sdcard partitions were screwed up.
The solution is simple -
1) Download clockwork mod recovery (cwmod_internal.zip) from the sticky thread in the Dev forum (http://forum.xda-developers.com/showthread.php?t=865245). Unzip it, and get the file called recovery.img and put it in the directory you ran nvflash from before.
2) Now go to your nvflash directory. Find the gtablet.cfg file. Edit it - under partition 9 where it says filename, change that to say recovery.img.
Now re-run nvflash - your G Tablet will get flashed with Clockwork Mod now instead of stock recovery. Once it's finished, reboot, and hold down the Vol + key while booting. You should get into Clockwork Mod Recovery now.
From here, I recommend repartitioning (use 2048 and 0 as the two options). Now try booting normally and everything should work fine.
Let me know how it goes!
Dude! You are the best!!! You are a life saver!! It worked! I got into cwm! Thank you!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
EDIT: Just after few minutes of finally getting into CWM, I was able to install VEGAN on it easily. Seriously, I don't know how to thank you enough!
gtab won't boot on its own
ok so i followed the instructions and it worked i was able to boot into the tablet but when i reboot it won't do it i have to use nvflash again to get it to it and once i do and the tablet goes to sleep it wont come back up and once again i have to use nvflash. please help!!
rcgabriel said:
Okay, the reason recovery mode is doing that is that's what stock recovery mode does - retarded, but that's it - it just tries to install a file called update.zip in your SD card main area.
As for why the ROM itself won't boot in regular mode - I've had the same problem after nvflashing from bekit's image when my data/sdcard partitions were screwed up.
The solution is simple -
1) Download clockwork mod recovery (cwmod_internal.zip) from the sticky thread in the Dev forum (http://forum.xda-developers.com/showthread.php?t=865245). Unzip it, and get the file called recovery.img and put it in the directory you ran nvflash from before.
2) Now go to your nvflash directory. Find the gtablet.cfg file. Edit it - under partition 9 where it says filename, change that to say recovery.img.
Now re-run nvflash - your G Tablet will get flashed with Clockwork Mod now instead of stock recovery. Once it's finished, reboot, and hold down the Vol + key while booting. You should get into Clockwork Mod Recovery now.
From here, I recommend repartitioning (use 2048 and 0 as the two options). Now try booting normally and everything should work fine.
Let me know how it goes!
Click to expand...
Click to collapse
I'm stuck in bootloop and I tried you solution and being I'm a noob at this I dont know how to rename the dile under partition 9. I just simply rename the file to recovery.img and i get an error when running the nvflash when it gets to partition 9. Can you please help me .... All help is appreciated.
rcgabriel said:
Okay, the reason recovery mode is doing that is that's what stock recovery mode does - retarded, but that's it - it just tries to install a file called update.zip in your SD card main area.
As for why the ROM itself won't boot in regular mode - I've had the same problem after nvflashing from bekit's image when my data/sdcard partitions were screwed up.
The solution is simple -
1) Download clockwork mod recovery (cwmod_internal.zip) from the sticky thread in the Dev forum (http://forum.xda-developers.com/showthread.php?t=865245). Unzip it, and get the file called recovery.img and put it in the directory you ran nvflash from before.
2) Now go to your nvflash directory. Find the gtablet.cfg file. Edit it - under partition 9 where it says filename, change that to say recovery.img.
Now re-run nvflash - your G Tablet will get flashed with Clockwork Mod now instead of stock recovery. Once it's finished, reboot, and hold down the Vol + key while booting. You should get into Clockwork Mod Recovery now.
From here, I recommend repartitioning (use 2048 and 0 as the two options). Now try booting normally and everything should work fine.
Let me know how it goes!
Click to expand...
Click to collapse
How do you EDIT the gtablet.cfg file in Windows 7? Thanks
Thanks! And a potential pitfall:
Thanks! I was having the same problem all night last night, and repartitioning fixed it.
I'd like to highlight something I had a problem with: I wasted a couple of hours with the WRONG clockworkmod recovery image. I found a similar response from another user who didn't include a link, and I found the clockwork image for g-tablet pointed to by someone else. If you're still having boot loop problems, use the clockworkmod linked to from this thread (v2.5.1.1-bekit-0.8).
Thanks everyone!
Is there a way that a mod can make a Sticky of the "Bricked Solution" fix.
There is no such thing as a bricked Gtablet that I've ever seen. Ive messed mine up a few times now and still works fine no matter how bad it gets.
Same for me, this fixed worked. I was not able to mount /data prior to repartitioning, was able to after. Thus the GTab was able to boot again, I now have a stock GTab, formatted clean, running 3588. Always nice to have a path forward.
emanzi said:
How do you EDIT the gtablet.cfg file in Windows 7? Thanks
Click to expand...
Click to collapse
Use Notepad
Hey i've done as you suggested however I'm stuck at the entering nvflash recovery node / nv3p server print out on my viewsonic gtab.... I still have the device plugged into my computer and it is registered with the usb bus but it won't reboot into the recovery img. I tried to power it down and reboot with "power and volume up" but I get no response. Any suggestions?
One thing I noticed, when people say they try to use nvflash they are using volume +, that is incorrect. You have to do "volume - (the minus sign) with the power button at the same to get the point to be able to use nvflash. See this a lot places in the forums, no wonder there is problems with people trying to use nvflash.
Thank you so much for this. I started getting an error when trying to mount /data so I did an nvflash without reading into it...turned out to be a huge mistake because that caused bootloops and left me without CWM. Turns out I should have just repartitioned but I couldn't get CWM to install from an SD card even though I knew I need to get it back on. Tried dozens of other things - including the full format with no luck but this finally got me into CWM so I could repartition.
Thanks again.
may as well be a brick - in my gut...
Every attempt at customization seems to be a step backwards.
Late nights have been spent over the last week trying to get things back to "normal" and I've had little success. Actually, make that "no success"...
At current, I've been looking ALL DAY (at work) and the last 4 hours at the NVFlash process.
I've got:
USB drivers installed for Windows
Bekit's 1105 files in place (gtablet + windows files)
I can boot to apx with volume.minus and power
PC sees tablet
I can run NVFlash w/o issue
gtablet boots immediately to stock ROM
I power off the gtablet and all I get is APX MODE again.
And again.
I have tried re-running NVFLASH with Roebeet's updated (4/17) files - same thing
I have tried renaming recovery.img from clockwork as "part9.img" and re-running, no success.
I have tweaked the gtablet.cfg and actually adjusted the SIZE for partition 9 to match the clockwork version of what I've named "part9.img" and no luck.
I ran the Format.zip version of nvflash, then ran regular nvflash, no luck.
Every time I run bekit's NVFlash, it loads stock ROM a-ok. Power cycle brings APX mode... I can't get Clockwork to install via the "nvflash switcheroo" nor by dropping "update.zip" and the recovery folder + command file in the root directory.
I feel foolish for spending about $300 on a device like this, and I feel foolish for spending SO MANY LATE NIGHT HOURS trying to fix it, and now I'm essentially going to only be able to use it unless - unless! - someone can come up with something else for me to try.... or if I "boot with NVFlash and hope it doesn't fall asleep on me..."
Any ideas?
Trust me, I've read every thread, seen the same "oh this worked...!" over and over on steps I've tried 3x or more. I think I'm depressed as this is ALL I DID TODAY - research on how to fix my gadget. sigh.
EDIT:
Just thinking here... (scary!) Has anyone ever sideloaded ROM Manager into the stock 3588 ROM? What I'm thinking is that if I can get ROM Manager to install, it loads CWM simultaneously, correct? And from ROM Manager I can reboot into recovery, yes? I would have tried this last night but I didn't come up w/ the idea until past 1:30am.
Also, let me take a step back and explain how I got here:
Installed Cyanogen 7 stable
installed a different keyboard
next day I got keyboard force-closes incessantly
tried to reflash CM7 - boot looped.
I could flash to the stock 3588 ROM w/o issues, and could use Clockwork w/o issues
tried to flash CM7 again, no dice
I suppose what i should have done at this point is re-partition and THEN try to reinstall CM7 - but I was having an issue w/ clockwork not completing the Factory Wipe / Reset - it would get stuck...
so I decided to bring the hammer w/ NVFlash - and I've certainly accomplished that
I can't get clockwork to install despite all I've tried:
paste recovery.img into my NVFLASH folder
change part9.img to recovery.img in the gtablet.cfg file
put clockwork's update.zip in the root folder
put clockwork's update.zip (and change "command" file to SDCARD2
I guess - how do I know if I'm still rooted? When I (nvflash and boot into) the stock ROM, I can connect via usb and navigate the folder structure. I see .android-secure and "data" and other typical folders that I've seen for weeks now...
so tired...
What happens if you do a factory reset immediately after it boots?
@K J Rad - you mean after it boots to the stock ROM, going to settings/security/factory reset (or clear all user data, whatever it says?) - I've tried that twice, and each time it comes back to apx-mode only, and when I nvflash again all my wifi settings are still in place.
if you mean factory wipe / reset from w/in Clockwork - I can't get CW to install.
EDIT - I added more explanation in my earlier post - a "how did I get here" of sorts...
Ok... if you hold down the Volume Up key during the reboot after nvflash does it drop back to APX or enter Recovery? If it goes to recovery... try method I from this: http://forum.xda-developers.com/showthread.php?t=1030915
It doesn't seem real common, but I seem to have permabricked my nook. I can't connect to it via adb, can't boot to recovery from sd or the emmc, and can't seem to get it to recover via sdcard. I've tried Adam's Unbuntu Unbrick, copying the recovery to the sdcard, and trying to recover to 1.4.2 via the sdcard.
How I broke it:
I installed Goomanager and installed TWRP, and then flashed to CM9 with the 3.0 kernel. The recovery and CM9 were working as well as could be expected, but CM9 had too many Sleep of Death issues so I decided I wanted to roll back to a nandroid backup of CM7. TWRP couldn't see my backups, so I decided I'd flash the recovery back to CWM via indirect's nookrecoveryflasher.apk. This was the end.
The symptoms:
I rebooted after using the nookrecoveryflasher flashing back to CWM, and now it just displays the n with the copyright info. It then flashes white briefly, then a slightly bigger n is displayed, it gets brighter, then dimmer, then a black screen (still backlit). The charger goes from red-orange to green after the screen goes black, and charging appears to be halted. If I hold down the power button for 8 secs, the backlight goes off and the charger light turns back to red-orange and it seems to charge. ADB lists no devices.
Are there any suggestions for things I should try that I haven't already? I thought this was pretty much unbrickable but something went really badly, and this should have been a relatively "safe" operation.
Update:
I'm now able to boot to CWM from the SD card, not sure why I couldn't previously. From here I did a nandroid restore of CM7, but after restore/reboot, it gives me the exact same symptoms. I also tried to flashing the CM7, CM9 roms, but still doesn't seem to actually boot into them. Is there a way to complete unroot/reset from recovery?
Did you try removing and inserting the sdcard back in while in twrp?
I stayed with cwm and I was able to flash both kernel versions of cm9 just fine. Since u already tried the 1.4.2 revert to stock, your situation seems quite troublesome indeed
Sent from my Nook Tablet using xda premium
I can't get into either TWRP or CWM now.
Hm sounds like your recovery is screwed up...
Sent from my Nook Tablet using xda premium
Do you know what kind of bootloader you are using? Is it cyanoboot?
Sent from my Nook Tablet using xda premium
Cyanoboot was installed when I installed CM9, but after trying to flash back to TWRP, it doesn't seem to be coming up any more.
Wow that's unfortunate. I was thinking if u were using cyanoboot you would be able to hold the n button to choose where to boot from...
Sent from my Nook Tablet using xda premium
Have you tried burning a clockworkmod recovery image to an sdcard and booting into cwm via said sdcard? If you can get this to work, you can flash the internal cwm recovery zip to overwrite the internal recovery partition.
Also try the 8 failed boots method. Each time you see the gray n logo dissapear when powering on, pressand hold both the n button and the power button until your nook tablet shuts off. Repeat this 8 times and your tablet should be forced to boot into recovery mode. Good luck!
Sent from my Nook Tablet using xda premium
I don't think that will work, as it sounds as though the recovery partition was broken with indirect's app (it happens and I think there is a thread he made with 1 method of fixing broken partitions but it requires you to have drivers set up properly for it).
I had this same thing happen to me when indirect pushed his new app that supports the 8GB and 16gb models out. I got the big N and I ended up flashing cwm via sdcard cwm and then flashing cm9 again via the newly flashed internal cwm.
Yes I've tried putting CWM on the sdcard but the same thing happens. I've also tried 3 different sdcards 2,8,16Gb. I've tried meghd00t's repart.img and it all behaves the same. It's as if the code that gets called to read the sdcard is broken now.
It sounds like after that white flash is when CMW should load but instead I get a bit bigger n, and then it goes black.
I'm now able to boot to CWM from the SD card, not sure why I couldn't previously. From here I did a nandroid restore of CM7, but after restore/reboot, it gives me the exact same symptoms. I also tried to flashing the CM7, CM9 roms, but still doesn't seem to actually boot into them. Is there a way to complete unroot/reset from recovery?
comat0se said:
I'm now able to boot to CWM from the SD card, not sure why I couldn't previously. From here I did a nandroid restore of CM7, but after restore/reboot, it gives me the exact same symptoms. I also tried to flashing the CM7, CM9 roms, but still doesn't seem to actually boot into them. Is there a way to complete unroot/reset from recovery?
Click to expand...
Click to collapse
try locating the stock 1.4.2 rom in the development section and flash that. see if it works.
In general if you are in CWM you have adb access at that time. The world is at your wish when adb works. Push stock recovery, etc., etc. Instead of trying to flash (which continues to fail) use adb to recover by of the many methods available. I would begin with pushing stock recovery and boot recovery (by command or power + N).
Good Luck.
Lars for tobdaryl
Did you flash TWRP using the .zip from the 1st-2nd page? That TWRP .zip is bugged so as not to recognize an external sd. I had a problem like this until I used a recovery sd (ill put a link in here in a sec)
I had a terrible 13 hour run of trying to fix it before I finally got it to boot, then I opened up my gmail inbox and found out that I had won a Transformer Pad 300 from Phandroid.com, needless to say after 13 hours I was nearly hysteric when I found this out, hope your issue gets resolved.
I also couldnt mount sd, couldnt adb, couldnt fastboot, couldnt get sd to show up in TWRP so maybe this method will work:
http://forum.xda-developers.com/showthread.php?t=1640958
Sent from my Transformer Prime TF300T using XDA Premium HD app
Hello wonderful people of the S. Vibrant community. I come to you in order to diagnose and hopefully fix a problem with a friends samsung vibrant.
Basically here's the backstory... He wanted to root his Vibrant (2.2 i believe) to ICS so i sent him the AIO Vibrant toolbox and told him explicitly to read the instructions of the tool and any potentials roms he wants to put on his phone. Lo and behold! I proceed to take a 2 hour map and my phone is bombarded with text messages saying that he 'messed up' and the phone is 'looping' upon boot.
I absolutely do not know what the hell he did and he was intentionally vague on what steps he took and what roms he downloaded etc. He mentioned something about reformatting and downloading a new kernal ...
Anyways. As I'm an owner of a Sprint SGS2; i know that sammys are literally the hardest devices to hard brick so i proceeded to search up these forums and odin a stock tar so i can get this thing booted up.
I followed this guide
http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/ and proceeded to odin back the pit and tar and it was a success.
Then it rebooted and bam still a boot loop. I tried a KA6 tar and still the same results. So I'm stuck here on how to get this phone out of the boot loop and am wondering if you guys can direct me to where I can hopefully fix this problem.
Side note. AIO Vibrant toolbox says the phone has USB Debugging mode off... (SMFH!!!!).
Thanks guys!
Download the bionix V fish man ROM. Its froyo, its good and it has an Odin flashable file. It comes with Bali kernel.
May help you on your way.
http://forum.xda-developers.com/showthread.php?p=21324042
Even though its boot looping, if you can get into recovery, you may be able to flash about any ROM you want. Wipe data/factory reset, clear cache and dalvik, and flash a good solid ROM. I've gotten out of the situation using both of the options I've listed.
May the force be with you.
I'll try and see if this will work and report back.
Well i odin'd the rom according to instructions and it's on the bali screen now for 5 mins... How long does the first boot take
lilotimz said:
Well i odin'd the rom according to instructions and it's on the bali screen now for 5 mins... How long does the first boot take
Click to expand...
Click to collapse
It does take a while. I'd let it go at least another few minutes. Then update me.
---------- Post added at 11:51 PM ---------- Previous post was at 11:46 PM ----------
If your still stuck, pull battery and boot into CWM recovery. Find Voodoo lagfix in the options. Disable it and reboot the phone. That's most likely why its hanging on the first start.
After you get it booted the first time you can go later and reenable voodoo lagfix.
tried using adb reboot recovery cmd and still no dice...
I assume froyo bootloader, hold both volume buttons and power until you see Samsung text and let go. May take a couple tries.
there is no samsung text. It goes white screen then Bali screen and repeat... (boot loop i guess.. again)
Update : Flashed the second odin tar and it seems to be somewhat working now... got into recovery mode and wiped data / cache... rebooting now
Excellent. If that doesn't boot all the way go back to recovery and disable voodoo lagfix.
Well i got into samsung recovery and deleted user data & cache data.
It does indeed go white screen then Bali screen for some reason... same.
Boot loop. No option to disable voodoo lagfix. Recovery is not CWM but samsung recovery... ?!!
lilotimz said:
Well i got into samsung recovery and deleted user data & cache data.
It does indeed go white screen then Bali screen for some reason... same.
Boot loop. No option to disable voodoo lagfix. Recovery is not CWM but samsung recovery... ?!!
Click to expand...
Click to collapse
Hmm. If you have the update.zip on your phone you can click reinstall packages and it will be CWM recovery.
here's what it says...
Update media:
E: Can't mount /dev/block/mmcklk0p1
(no such file or directory)
E: copy_dbdata_media; Can't mount SD card:
your storage not prepared yet.Please use UI menu for format and reboot actions
E:Copy_dbdata_media:format SDCARD:
formatting Sd card:...
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 to format and reboot actions
copy default media content failed
Your internal sd has been destroyed. Your only option is running the entire os off of an external microsd card. http://forum.xda-developers.com/showthread.php?t=1580902
At least it seems like this is the case. I also had this happen to my phone, but eventually it fixed itself after odining about 20times and installing other roms. Good luck. Heres what I did http://forum.xda-developers.com/showthread.php?t=1665123)
Didn't work for some people, so the fact that mine came back might have just been luck.
le sigh...
I guess i'll try some more tomorrow. Guess he did the unthinkable and 99.9% killed a sammy. Poor galaxy s...
I finally managed to follow your instructiosn and i installed CM9 for the first time and it's now boot looping. Your instructions state to reboot into recovery mod and install it again but I for my life cannot discover how to reboot this thing into recovery mod. What are the steps and buttons again if I may ask?
lilotimz said:
I finally managed to follow your instructiosn and i installed CM9 for the first time and it's now boot looping. Your instructions state to reboot into recovery mod and install it again but I for my life cannot discover how to reboot this thing into recovery mod. What are the steps and buttons again if I may ask?
Click to expand...
Click to collapse
Pull the battery and replace it, hold vol up, vol down and power until you see screen come on then release. That should take you to recovery.
sent from the depths of helly bean
Samsung Vibrant, unlocked, was rooted on SlimBean 4.2.1 beta2 OC'd to 1.2ghz. Anyways...
I was using my phone this morning and it suddenly just failed. Rebooted to initial "Vibrant SAMSUNG" screen with no warning, an then stuck at that screen. Pull battery, reboot. Pull battery, vol+ vol- pwr. Same results. Could get to Download though.
Got home in the afternoon. Tried to Odin to stock. After Odin kludging up and failing a few times, I manage to get it to succeed with the PIT and TAR that come with the AIO toolbox. Reboot... No dice. Now just loops the same initial screen, with a half-second blackscreen between. Reboot to recovery... Stock recovery, so can't flash anything. Use an external microSD adapter to put another SLimbean rom on there, name it 'update.zip." Flash zip. Fails at "Slim Bean v.whatever, formatting /system and /data..." More screwing around with Odin. Find stock bootloader in a .tar.md5, flash it with the same PDA (no PIT this time as it caused Odin to fail and I believe my partitions are correct), failure. Repeating this odin now, will update with results.
Any help would be greatly appreciated. You guys have helped me in the past, I know you can do it!
EDIT: More odining, got a quite scary message of "KERNEL PANIC UPLOAD MODE" with some red writing superimposed on it. Looks pretty damn dead. Might go to the last resort and try the UnBrickable Mod...
EDIT 2: Reboot recovery, wipe user data, try to install SLimbean zip again, fails. Reboot, stuck at same "vibrant" screen. Recovery again and Semaphore Recovery comes up! Try to flash zip, the file list thing is of my _external_ sd. Fails at same place, with generic error. Can't mount anything else, only external SD is visible. Weird...
Try booting after removing external Sd. Stuck at Vibrant screen.
Put in sdcard again, reboot to recovery. Trying things, hit "reboot recovery" from recovery. Similar error message to the kernel panic screen before: "POWER RESET or UNKNOWN UPLOAD MODE" with similar red text.
Okay, will work on this tomorrow. Again, any help would be very, well, helpful. Thanks!
Another EDIT: Few more details about recovery:
Installing slimbean fails with "status 0"
Mounting or wiping anything except USB storage results in a black "flicker" and recovery restarts
USB storage shows two drives on the PC: One that used to be internal SD that is now the external, and another that gives the "empty drive" message
I think the phone somehow swapped the SD cards.
When you flash to stock was it JFD? Did you hsave reparition checked?
Also - Pull the external sdcard out. I have found it causes boot loops when going from JFD to JB. That said pulling the sim card wont hurt either.
Moped_Ryder said:
When you flash to stock was it JFD? Did you hsave reparition checked?
Also - Pull the external sdcard out. I have found it causes boot loops when going from JFD to JB. That said pulling the sim card wont hurt either.
Click to expand...
Click to collapse
Sorry for the noob question- What is JFD? No, I did not have repartition checked as Odin would lock up and eventually fail if I did.
It doesn't seem to boot without the external SD. I could try Odin without it, (If I can get Odin to work) would that help?
EDIT: Just found http://forum.xda-developers.com/showthread.php?t=1665123 , looks right. Will try once I get a spare flash drive to GParted-ize.
yet another EDIT: Partitioned SD, still no download mode, still can't install from zip. I may be in the market for a new cell phone soon...
Finally SUCCESS!
After parting SD, held both vols, plugged in, download mode! Got odin to work, am now running absolute stock. Not sure if internal memory is OK though...