So basically i got the ICS Encryption unsuccessful error and now my phone wont get past the vibrant splash screen. I tried odining back to stock but it just goes to splash screen and then turns off. i cant get into recovery mode. please please pleaseeee help!
jig or get to download mode
odin EUGENE373_SamsungS_Froyo_PDA (read directions)
then flash back to stock then try not too "brick" the unbrickable vibrant again.
this does not fix the problem. the /data partition is the cause of the problem and i dont know how to fix it. repartitioning in odin doesn't fix it either. :/
I had the same thing happen to me.. ive tried everything i could think of
enter download mode
dvryu said:
enter download mode
Click to expand...
Click to collapse
and then what? anything i flash gets me bootloader screen. eugene's unbrickable rom gets me to stock recovery but buttons dont work in that rom to let me select anything.
Unfortunetly there is no fix as of now. The problem seems to be the internal flash memory 16gb is unable to mount. SD card (External) mounts perfectly fine as i was able to pull some files using adb commands. Hope you have a spare phone cuz there is no way to fix your phone as of today.
A warning to ICS rom users. You phone could potentially become paperweight so be extremely careful. You might want to consider using Gingerbread or some other rom other than ICS until someone finds a solution to this problem.
---------- Post added at 04:35 PM ---------- Previous post was at 04:33 PM ----------
Nirmalspeed said:
and then what? anything i flash gets me bootloader screen. eugene's unbrickable rom gets me to stock recovery but buttons dont work in that rom to let me select anything.
Click to expand...
Click to collapse
The buttons in recovery don't work after flashing Eugene's rom.
You can only reboot your phone through the adb command:
adb reboot
Of course you must also have the android debugging bridge installed on your computer to issue these commands. Including the SDK. Good luck.
i have two other vibrants in my family right now. what do you think i could do with those to fix mine?
http://forum.xda-developers.com/showthread.php?t=1447303
OP, what ROM were you running when this happened intially? Also what kernel?
I have been reading most of the morning and am looking into some things. Alex's thread does show how to workaround the problem but it seems that the internal sd is lost (for now).
Since you are not the only one this happened to, I would like to know the above and see if it correlates to the others that this happened to in the Vibrant section. I'll post the same in their threads too.
Woodrube said:
OP, what ROM were you running when this happened intially? Also what kernel?
I have been reading most of the morning and am looking into some things. Alex's thread does show how to workaround the problem but it seems that the internal sd is lost (for now).
Since you are not the only one this happened to, I would like to know the above and see if it correlates to the others that this happened to in the Vibrant section. I'll post the same in their threads too.
Click to expand...
Click to collapse
i was running ICS Passion 13 with the Kiss kernel that came with it. and i've looked around and many people with ics have gotten this problem both on our device and on the AT&T's captivate.
If you loaded Eugene's rom, and are stuck at the recovery, don't wait so long to type that adb reboot command and don't unplug the usb just type the command. let the rom load then get the phone back in download mode and flash the stock rom.
Eugene's rom properly set up will fix your issue. try again!
cotbu said:
If you loaded Eugene's rom, and are stuck at the recovery, don't wait so long to type that adb reboot command and don't unplug the usb just type the command. let the rom load then get the phone back in download mode and flash the stock rom.
Eugene's rom properly set up will fix your issue. try again!
Click to expand...
Click to collapse
that wouldn't work as the /data partition isn't being red by the phone. Nothing happens when i try that command.
These are the instructions, Eugene's rom write like a lowlevel format, either you are not following directions or you actually bricked the vibrant.
But....you say you've made it to Eugene's recovery if you did you should be good to go.
Okay, Now with the Caution Posted, Lets Begin with the Froyo that Don't Brick
I have Tested this 5 Time's to Make Sure! Only install What I Post!
First,
You must already Have Odin installed & Know how to boot into Down-loader Mode!!
Do Not Select Repartition In ODIN Flasher
Quote:
Installing...
Extract the .zip file
Open ODIN Flasher, Select the Pit File.
Select Eugene373_GalaxyS_Froyo_PDA.tar
Select start..
Second,
Once Odin had Done Flashed, & you are in Recovery Mode you will not be able to Access anything & need to be at a Computer with Samsung Driver's installed & a working SDK pre-installed..
Side note: you will get an error in recovery, Don't be worried!!!! Ignore this!
Third,
Open a CMD Prompt & type:
Quote:
adb reboot
Froyo with Downgrading back to Stock Possible:
Download here > EUGENE373_SamsungS_Froyo_PDA.zip
*Stock Froyo with*
~ Root
~ SuperUser.apk
~ Build.prop now Correct
~ Defualt.prop Also Correct
****
*Issue's
Volume Key are Reversed
****
*Not working*
~ Rom Manager via reboot to Recovery!
~ Selectable Menu in Recovery
~ 3.5 Head-jack
~ Hot Spot Tethering
sorry for stressing but, I have a 4yr old that loves playing with the vibrant and I think I've brought it back from every brick situation possible. As long as the vibrant has power, it will not stop! xd!
Related
so I have a vibrant and was running 1.6 bionix mod on it, and i figured i would download 1.7 and flash it over. But before I did I wanted to flash back to stock via odin to download the OTA but when I did that I get a black screen after the galaxy s logo..I have looked and searched these forums and
I have tried this
http://forum.xda-developers.com/showthread.php?t=741027&highlight=brick
did not work
and I am currently trying to use eugenes froyo flash method, however I need to use adb reboot and adb cannot detect my phone because I assume it's not rooted anymore since I reverted back to stock..
any ideas?? on how to root my phone while it's in this soft brick or any ideas what to flash in odin to fix this ?? If this thread was unclear I will clarify any questions.
PS. ever since i used odin to flash Euguenes froyo rom whenever I start up the phone it goes straight to android system recovery and I do not have the option to do anything else. HELPPP
ok...reading up a bit more and it looks like I didn't disable voodoo lag fix before i flashed over the stock rom ?
now i am trying to run the fixes that this thread lists,
http://forum.xda-developers.com/showthread.php?t=782027
but i can not do any adb commands because my phone isn't rooted now, any way to root through odin?
Wykedx said:
ok...reading up a bit more and it looks like I didn't disable voodoo lag fix before i flashed over the stock rom ?
now i am trying to run the fixes that this thread lists,
http://forum.xda-developers.com/showthread.php?t=782027
but i can not do any adb commands because my phone isn't rooted now, any way to root through odin?
Click to expand...
Click to collapse
your phone doesn't have to be rooted to use adb ...
When your phone throws you into recovery with that media error, unplug your phone for 5 seconds, and plug it back in. Eugene put that in the instructions, and i didn't read that part either lol. If adb still doesn't work, you need to dl the right drivers again
dav3wash said:
your phone doesn't have to be rooted to use adb ...
When your phone throws you into recovery with that media error, unplug your phone for 5 seconds, and plug it back in. Eugene put that in the instructions, and i didn't read that part either lol. If adb still doesn't work, you need to dl the right drivers again
Click to expand...
Click to collapse
when you unplug the phone and re plug in what should the phone do?
is it just so the computer recognizes the phone or does it boot something up?
Wykedx said:
when you unplug the phone and re plug in what should the phone do?
is it just so the computer recognizes the phone or does it boot something up?
Click to expand...
Click to collapse
nothing will happen on the phone, but your computer and adb will recognize the phone
omg i was just about to lose hope and go into tmobile and make a bs excuse about how the ota update f'ed up my phone LOL,
thank you so much!! now i can flash the stock rom correct? or can voodoo still mess my phone up?
Wykedx said:
omg i was just about to lose hope and go into tmobile and make a bs excuse about how the ota update f'ed up my phone LOL,
thank you so much!! now i can flash the stock rom correct? or can voodoo still mess my phone up?
Click to expand...
Click to collapse
Haha no problem. As for Voodoo ... i never ventured there. I usually stick with JAC's or King Kilikkk's, but here's the uninstall/verification for Voodoo. Try it b4 you flash anything else just to be safe.
How-to Disable the Voodoo Lagfix:
1. Once again, you MUST disable the Voodoo lag fix in order to flash any other rom, kernel, or perform a nandroid backup. If you don't...well....lets just say I warned you.
2. Its simple. Create a folder on the root of your sdcard called 'Voodoo'.
3. Now, open notepad or something similar and save the blank file. Name it 'disable-lagfix'. This file cannot have any file extension, so remove it if it does.
4. Place your blank file into the 'Voodoo' folder you made on your sdcard.
5. In order to disable, simply power down your phone and power it back up.
6. FINISHED! You can now flash anything you'd like!
How-to Confirm Voodoo Lagfix is Disabled:
1. In adb shell or terminal type 'mount'
2. If it is disabled is should read '/dev/block/mmcblk0p2'.
3. If it is not disabled, it will read '/dev/block/mmcblk0p4'.
done and done, thanks again!!
Sooo.... I flashed JK6 + voodoo over my stock froyo. now i can't get back to clockwork recovery, i have tried everything and i cant get even into download mode, but my phone turns on perfectly fine... idk what it is or how to fix it can someone help? my phone's fine right now but if i try to go into recovery it gives me and error: code-7 , which i have never had or even seen before and i tried to flash clockwork recovery again and it said it flashed just fine, but it won't work.... help me someone. thanks
it sound's like you have a 3e recovery now and CWM doesn't work with stock 3e recovery. you need to modify it using the information from this
post.
also if you have adb setup on your computer, and you want to go back to stock and start over but can't access download mode from buttons, just use
adb reboot download
another way is right on the phone, download terminal emulator and use
su
reboot download
also works for getting to stock recovery(not sure why you would need to other than to flash CWM from SD card..)
hope this helped.
I suggest you disable voodoo then retry it... Voodoo is real tricky when it come to certain things.. if you go to Team Wiskeys website, the have a tutorial on how to do it.. then try to redo OCLF. i myself use Eugenes kernal B_Stock_1120_100 Kernel #20..... and the Lagfix... letme know how it goes... but ALWAYS disable voodoo before you do any flashing!! or system changes.
Just my 2cents... thats how i overcame the CWR... besides flashing a stock Kernal and starting from scratch..
Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
c-brit323 said:
Sooo.... I flashed JK6 + voodoo over my stock froyo. now i can't get back to clockwork recovery, i have tried everything and i cant get even into download mode, but my phone turns on perfectly fine... idk what it is or how to fix it can someone help? my phone's fine right now but if i try to go into recovery it gives me and error: code-7 , which i have never had or even seen before and i tried to flash clockwork recovery again and it said it flashed just fine, but it won't work.... help me someone. thanks
Click to expand...
Click to collapse
With the Voodoo kernel recently released you DO NOT use clockwork as you're used to seeing it, ie, green text version, and going through rom manager and rebooting into recovery from there will not get you where you want to go. Reason being, the voodoo kernel you flashed has a new version of clockwork to work with. When you see the red text clockwork, you know you are there.
Now how to get there. If you are familiar with adb, use "reboot recovery" command and you'll be there. If adb is not your bag, dowload android terminal emulator from the market. Open it, type "su" and press enter. Accept the superuser prompt. You may have to hit your menu button and toggle keyboard button to bring your kb back after the su command. Then type "reboot recovery" and press enter, your phone will now reboot into the red text voodoo version of clockwork. All command listed are of course typed without the quotations. Good luck, its really easy, and mentioned in the voodoo thread, along with other tips for your reference.
Ginger Clone's of the world unite! via the XDA App
Yeah I can get there but how do I disable voodoo and flash another rom/kernel without odin? And how do I get my recovery back?
You have recovery, just a different version now. To disable voodoo, you can use the good old fasioned method of creating a folder inside the voodoo folder, named "disable lagfix", no quotes, reboot your phone and listen to linda do her work, or use the voodoo lagfix menu in the red recovery to disable it. Note you will still have red clockwork until you flash a different kernel, after disabling voodoo of course.
Ginger Clone's of the world unite! via the XDA App
Yeah but it says "cant derterminate" or something like that, and it stays on.... Finding update package, and I cant scroll or anything
Sounds like you are odin bound, friend.
Ginger Clone's of the world unite! via the XDA App
Which is cool, except. My drivers are messed up and I have parental controls on and yada yada... So I cant install the drivers unless I use a friends computer or something. But its cool. Thanks man
One more thing that might help. Last week zimphishmonger started a thread and found a fix for the new voodoo not disabling correctly. Find it and there is a flashable that replaces the format.fat file on the phone and on some phones lets voodoo didable. Search it and try it. I'll try to post a link when I get around a pc.
Edited: http://forum.xda-developers.com/showthread.php?t=875498&highlight=zimphishmonger
its worth a shot to try, and he created a flashable to install the file in the first post there, good luck.
Ginger Clone's of the World Unite! Via the XDA App
i have a fascinate that ive had for a while. ive managed to root it(took 4ever to find out how) but im rooted with everything else stock. no custom rom kernel or anything(i know im rooted cuz i can use wireless tether with superuser) HOWEVER, ive been reading on this cyanogen mod 7 and would really like to put this on my phone and get rid of touchwiz once and for all, and don't suggest adw it lags my phone down. can somebody plz give me a tutorial on how to download and flash whatever that is. i can't handle the sluggishness of tw anymore. btw i have odin but really don't know what to do with it. oh and sorry if this is already posted but ive searched and don't really feel like going through every thread in existence. please help me!!
Well before I would go and post a tutorial about this we need to address one thing.
You said
and don't suggest adw it lags my phone down.
Click to expand...
Click to collapse
You understand that the default launcher in Cyanogenmod7 (CM7) is ADW correct? I just would hate for you to go through the touch n go process of flashing CM7 and end up hating it because of this
Well... you can switch away from ADW. For instance, I switched to the GO launcher, and it ran like a dream.
Alright, here's a n00b guide.
0)Download these files to you SD card: http://www.mediafire.com/?dfjjclddzq6fl5q, http://goo-inside.me/gapps/gapps-gb-20110613-signed.zip
1) Flash this in Odin: http://forum.xda-developers.com/attachment.php?attachmentid=657960&d=1310959789
2) Boot into recovery by turning off the phone/pulling battery and holding volume up, volume down and power at the same time
3) Select wipe cache, then select wipe data
4) Select install zip from sd card or something like that and flash CM7 (The file you downloaded from mediafire above)
5)Once phone finishes installing, hit reboot phone or if your phone is off turn it back on
6) Hold down power button, select reboot, select recovery
7) From here, select install zip from sd card again, and install the gapps from the second link.
8) Reboot, and enjoy. If you don't like adw, install GO launcher from the market
more noob please! how do i flash a file on odin? and what the hell is gapps and what do i do with it?
beefsmith said:
more noob please! how do i flash a file on odin? and what the hell is gapps and what do i do with it?
Click to expand...
Click to collapse
Install this on your computer: http://www.mediafire.com/download.php?7946i8tdbe0yv50
Open Odin, remove your phone's battery, hold the "volume down" button on your phone while plugging it into your computer and a little android with a shovel should come up.
On your computer, download the file from step 1. In odin, click the PDA button (NOT THE PHONE BUTTON) and select that downloaded file. Hit start or flash or whatever the button like that says. It will take a while. Once done, you will have cwm, so do step 2.
Once in CWN, use the volume buttons to go up and down and use the power button as the "enter button". Follow the rest of the steps from there.
Also, GAPPS is just the technical name for that second file you downloaded. Install it through CWM exactly as the steps say.
beefsmith said:
more noob please! how do i flash a file on odin? and what the hell is gapps and what do i do with it?
Click to expand...
Click to collapse
Gapps...is abbreviated for google apps. Ie. Google talk, gmail, google voice, google chrome to phone, ect...this is a zip file package that contains a lot of googles apps that are not pre packaged into the rom
Odin is a software program for pc to push a modified recovery program or complete stock rom files, or patches and some other goodies and this recovery abbreviated cwm(clock work mod ) is the program you use to install custom roms and kernels. All odin file formats will end in .tar while files for flashing via recovery end in .zip
Sent from my SCH-I500 using XDA App
ok so i tried to flash that file using odin, but it just told me succeded0 failed1 and now my phone has the phone to ! to pc logo, and appears bricked
beefsmith said:
ok so i tried to flash that file using odin, but it just told me succeded0 failed1 and now my phone has the phone to ! to pc logo, and appears bricked
Click to expand...
Click to collapse
Follow this to fix your phone: http://forum.xda-developers.com/showthread.php?t=1124391
Just to let you know, you should probably read up on some more of the threads in the general and development section after you fix your phone before trying this again. You really need to know what you're doing or you'll break your phone for real next time.
skafan2 said:
Follow this to fix your phone: http://forum.xda-developers.com/showthread.php?t=1124391
Just to let you know, you should probably read up on some more of the threads in the general and development section after you fix your phone before trying this again. You really need to know what you're doing or you'll break your phone for real next time.
Click to expand...
Click to collapse
While skafan is right, you probably won't completely bork your device but you can get in deep real quick if you screw up anything major...like flashing a rom not for the fascinate. Go to the link he posted and do it exactly to return to complete stock and then read read read before flashing again, but it is very hard to completely destroy our phones besides physically smashing it. His warning is of just cause....that said..everything I learned(and I'm sure some will agree with me) for the most part is out of necessity..meaning I started tinkering with my phone and learned what I had to as I made mistakes and needed to know how to get out of a boot loop or force closes. There were even a few times where I thought I just turned my fassy into an expensive paper weight! You'll get there and, if nothing else borking builds character!
Sent from my SCH-I500 using XDA App
i followed those instructions to the letter, same result, success(0) failed (1)
this sucks
borking does not build character for me
it engenders a sense of helplessless and makes me cry
Here's the situation.
I had bionix 1.3 on my phone > tried to install stock froyo 2.2 > bricked phone > did a factory reset using odin> re rooted phone and installed rom manager > rom manager gives me the error message "an error occurred while downloading your recovery" when I try to install bionix-v
After you Odin to stock, are you rooting with the update.zip from here at XDA?
You'll put it on your internal storage (not Micro SD) and not in a folder. Just drop it on the base level of the internal storage. Then go to stock recovery, click reinstall packages. You'll probably have to click reinstall packages a 2nd time.
Then it should boot into Clockwork Mod Recovery.
You really don't need ROM Manager. I guess some people like it, though.
Toast6977 said:
After you Odin to stock, are you rooting with the update.zip from here at XDA?
You'll put it on your internal storage (not Micro SD) and not in a folder. Just drop it on the base level of the internal storage. Then go to stock recovery, click reinstall packages. You'll probably have to click reinstall packages a 2nd time.
Then it should boot into Clockwork Mod Recovery.
You really don't need ROM Manager. I guess some people like it, though.
Click to expand...
Click to collapse
Where can I get the xda update zip? My version of the vibrant doesn't allow you to physically get into recovery up with the buttons. What else can I use to install roms? I tried using rom toolbox lite ( i think that's the name) but it still didn't work.
refer to my post here: http://forum.xda-developers.com/showpost.php?p=32180600&postcount=3
rocketrocketrocket said:
Where can I get the xda update zip? My version of the vibrant doesn't allow you to physically get into recovery up with the buttons. What else can I use to install roms? I tried using rom toolbox lite ( i think that's the name) but it still didn't work.
Click to expand...
Click to collapse
What do you mean "your version of the vibrant"???
Because I am hard, you will not like me. But the more you hate me, the more you will learn.
samsgun357 said:
What do you mean "your version of the vibrant"???
Because I am hard, you will not like me. But the more you hate me, the more you will learn.
Click to expand...
Click to collapse
As I understand it you could get into recovery mode on the original vibrants by holding down the buttons in a specific way but they removed the feature on later vibrants. I have one of the vibrants where the feature was removed. I can only get to recovery mode through software I think.
rocketrocketrocket said:
As I understand it you could get into recovery mode on the original vibrants by holding down the buttons in a specific way but they removed the feature on later vibrants. I have one of the vibrants where the feature was removed. I can only get to recovery mode through software I think.
Click to expand...
Click to collapse
They didn't remove that feature from vibrants. Go to settings> about phone>model and type that in here letter for letter please.
Try this, turn phone off. Hold volume up/down and power until you see screen come on then release.
Because I am hard, you will not like me. But the more you hate me, the more you will learn.
Shut your phone off. Hold volume up + volume down and power all at the same time. As soon as you see the Vibrant black/white text let go.
You may have to try this multiple times to get it to work. This will be stock recovery.
The later ones were getting shipped with updated Android version and installing signed packages bug was fixed.
Nowadays, you get around that by entering Download mode and using Odin to revert back to stock, which allows flashing of custom recovery and rooting, and then voila... you're on your way.
I guess I've been wrong before, but I've never heard anything about them disabling the button combos altogether.
---------- Post added at 11:52 PM ---------- Previous post was at 11:48 PM ----------
tacosbuenos said:
Here's the situation.
I had bionix 1.3 on my phone > tried to install stock froyo 2.2 > bricked phone > did a factory reset using odin> re rooted phone and installed rom manager > rom manager gives me the error message "an error occurred while downloading your recovery" when I try to install bionix-v
Click to expand...
Click to collapse
Do you have an SGH-T959? Not to be confused with a T959v, that's different. Do you have a front facing camera? The errors you describe typically take place when you erroneously flash a ROM that isn't for your device.
Have a looksy in Settings>About phone and make sure it says SGH-T959.
Good luck!
At this point I'm just trying to re install bionix 1.3 with a non working rom manager on my rooted, stock vibrant.
rocketrocketrocket said:
At this point I'm just trying to re install bionix 1.3 with a non working rom manager on my rooted, stock vibrant.
Click to expand...
Click to collapse
Good luck.
Because I am hard, you will not like me. But the more you hate me, the more you will learn.
rocketrocketrocket said:
At this point I'm just trying to re install bionix 1.3 with a non working rom manager on my rooted, stock vibrant.
Click to expand...
Click to collapse
In my opinion, forget about ROM Manager and get Clockwork Mod Recovery installed. Search the forums, find the update.zip file. You'll need to be on stock Eclair to flash it in recovery.
Check the stickies for guides on how to get back to stock, how to flash Update.zip and the ROM threads have instructions in the 1st post how to install the ROM via Clockwork Mod Recovery.
Good Luck!
Hint: look in stickies for Woodrubes Repository. He put together a great collection of files. Don't forget to hit his thanks button.
Toast6977 said:
Search the forums, find the update.zip file. You'll need to be on stock Eclair to flash it in recovery.
Click to expand...
Click to collapse
I've posted the instruction and link from my previous post on first page.
Here's what happened:
-Had Eryigit GB-Installed PA w/ mevordel's kernel 4.0Rebooted recoveryStarted weird bootloop=would go back into recovery and act like its installing something, then reboot, ad infinitum
I tried reflashing Eryigits rom from odin,
then repartitioning. Somehow it was able to boot into Eryigit's ROM once, but the capacitative buttons didnt work and I couldnt reboot into anything except for download mode or a normal samsung logo bootloop.
I tried a few more things in Odin (not blindly, mind you) and still no go.. I can get it into recovery only if I flash a bootloader in Odin and auto-reboot it, otherwise it just goes back to the bootloop.
I believe I have the same problem as in this thread
I'm trying to adb into my device, but am having trouble detecting it. It'll connect in Odin fine, but not in adb, whether in download mode or just hanging at the samsung logo.
What can I do to fix this without adb working? I'm hoping for an odin fix for it, but through the mountains of threads I've been reading I don't believe there to be.
According to the thread above ^ it needs to be repartitioned manually... I read all the threads linked to and tried adb & heimdall but no luck after like 3+ weeks ):
Can anybody give me a better explanation of whats going on or throw me some troubleshooting advice?
<3 <3 <3
bmxer4130 said:
Here's what happened:
-Had Eryigit GB-Installed PA w/ mevordel's kernel 4.0Rebooted recoveryStarted weird bootloop=would go back into recovery and act like its installing something, then reboot, ad infinitum
I tried reflashing Eryigits rom from odin,
then repartitioning. Somehow it was able to boot into Eryigit's ROM once, but the capacitative buttons didnt work and I couldnt reboot into anything except for download mode or a normal samsung logo bootloop.
I tried a few more things in Odin (not blindly, mind you) and still no go.. I can get it into recovery only if I flash a bootloader in Odin and auto-reboot it, otherwise it just goes back to the bootloop.
I believe I have the same problem as in this thread
I'm trying to adb into my device, but am having trouble detecting it. It'll connect in Odin fine, but not in adb, whether in download mode or just hanging at the samsung logo.
What can I do to fix this without adb working? I'm hoping for an odin fix for it, but through the mountains of threads I've been reading I don't believe there to be.
According to the thread above ^ it needs to be repartitioned manually... I read all the threads linked to and tried adb & heimdall but no luck after like 3+ weeks ):
Can anybody give me a better explanation of whats going on or throw me some troubleshooting advice?
<3 <3 <3
Click to expand...
Click to collapse
If you are sure of what you state, solution is from post 39 at the following adress
http://forum.xda-developers.com/showthread.php?t=1676606&page=4
But check if you have a true "memory partitioning issue" best is said when wiping cache you get many advices about what is wrong (normaly in red letters!)
good luck and welcome to our club!
lolo9393 said:
If you are sure of what you state, solution is from post 39 at the following adress
http://forum.xda-developers.com/showthread.php?t=1676606&page=4
But check if you have a true "memory partitioning issue" best is said when wiping cache you get many advices about what is wrong (normaly in red letters!)
good luck and welcome to our club!
Click to expand...
Click to collapse
Hey thanks. I already read through all that stuff ^ and am not having much luck. Is there some way I can IM you or something? PM me if so. You seem very knowledgeable about this matter
bmxer4130 said:
Hey thanks. I already read through all that stuff ^ and am not having much luck. Is there some way I can IM you or something? PM me if so. You seem very knowledgeable about this matter
Click to expand...
Click to collapse
Normally we can solve this within a thread that can help any other getting the same issue.
i am still very involved because end 2011 I got in trouble (I was expecting to have much better performance by flashing a Gnote kernel !!!!) and stayed for months reading at XDA for a save. (also good english training then)
your Pb:
did you check by wiping if you are in this situation? You should get advice that (partition from n 14 and upper can't be read) if so follow the tracks from the relevant post and tell me what goes wrong with you.
I fixed it! you will do it the same!
PS:To enter Adb you should flash FIRST a kernel (with ODIN) rj14 for int'll version or entropy for US model
lolo9393 said:
Normally we can solve this within a thread that can help any other getting the same issue.
i am still very involved because end 2011 I got in trouble (I was expecting to have much better performance by flashing a Gnote kernel !!!!) and stayed for months reading at XDA for a save. (also good english training then)
your Pb:
did you check by wiping if you are in this situation? You should get advice that (partition from n 14 and upper can't be read) if so follow the tracks from the relevant post and tell me what goes wrong with you.
I fixed it! you will do it the same!
PS:To enter Adb you should flash FIRST a kernel (with ODIN) rj14 for int'll version or entropy for US model
Click to expand...
Click to collapse
Ok so I got into recovery with entropy's kernel and wiped everything,
When I try to mount usb storage it says:
E: Unable to write to ums lunfile (No such file or directory)
Click to expand...
Click to collapse
So yeah, its the internal memory.. now if i could just get adb shell to work right
okay now I'm just trying to adb shell into it from win7 x64 and fedora 18 linux with no luck. in win7 it shows up in adb devices, but i cant connect to it, right now im thinking its because of the java sdk and problems with the fact that its a 64 bit comp. in fedora adb devices says ???????????? offline usb:2-2...
bmxer4130 said:
okay now I'm just trying to adb shell into it from win7 x64 and fedora 18 linux with no luck. in win7 it shows up in adb devices, but i cant connect to it, right now im thinking its because of the java sdk and problems with the fact that its a 64 bit comp. in fedora adb devices says ???????????? offline usb:2-2...
Click to expand...
Click to collapse
So, you were able to flash entropy's kernel (said you have a US device?) Now you can go to recovery mode and enter adb call for;" adb devices" and your will and must show up. No need to mount anything. I 've never, under win7, tryied this. so no comment.
Would you mind to give me what is said after you do a single wipe because we have to be sure your problem is really a memory partition wreck.
lolo9393 said:
So, you were able to flash entropy's kernel (said you have a US device?) Now you can go to recovery mode and enter adb call for;" adb devices" and your will and must show up. No need to mount anything. I 've never, under win7, tryied this. so no comment.
Would you mind to give me what is said after you do a single wipe because we have to be sure your problem is really a memory partition wreck.
Click to expand...
Click to collapse
Ok, I was able to adb shell and rebuild the partition table, and it was indeed messed up, and I can mount usb storage, but I still can't get it to boot into any rom, and it refuses to boot into cwm recovery unless its just rebooted from odin. in recovery in the log it has an error about libc.so, idk if that has anything to do with it though. I'm beginning to think the problem may have to do with my usb cable. I accidentally switched the stock one with a Galaxy SII one, which should be fine, but maybe not.
bmxer4130 said:
Ok so I got into recovery with entropy's kernel and wiped everything,
When I try to mount usb storage it says:
So yeah, its the internal memory.. now if i could just get adb shell to work right
Click to expand...
Click to collapse
The "mount USB storage" option is for mounting the SD card on your computer. That error is because you don't have an external SD card inserted.
Mevordel said:
The "mount USB storage" option is for mounting the SD card on your computer. That error is because you don't have an external SD card inserted.
Click to expand...
Click to collapse
hehehe, I kinda realized that after posting. Derp.
But I think it may have to do with /data & maybe other folders/files being R/O (read only..) instead of R/W, as per this thread so I am now convinced I need the bootchain for the galaxy player, but this is just a sneaking suspicion, I need to do some more digging before making a fool of myself again
bmxer4130 said:
hehehe, I kinda realized that after posting. Derp.
But I think it may have to do with /data & maybe other folders/files being R/O (read only..) instead of R/W, as per this thread so I am now convinced I need the bootchain for the galaxy player, but this is just a sneaking suspicion, I need to do some more digging before making a fool of myself again
Click to expand...
Click to collapse
Ok you have all the needed stuff and now you are trained and skilled enough. You will succeed.
Why not you to try flashing Mevordel's GB Chip 1.5 rom that is in my view the best for your device, it is light simple and fast and no need for more for what we expect from this excellent but outdated product.
lolo9393 said:
Ok you have all the needed stuff and now you are trained and skilled enough. You will succeed.
Why not you to try flashing Mevordel's GB Chip 1.5 rom that is in my view the best for your device, it is light simple and fast and no need for more for what we expect from this excellent but outdated product.
Click to expand...
Click to collapse
Yes, I tried flashing it in cwm, along with eryigit (both with entropys kernel flashed over them) and PA venturi, but it refuses to boot properly. If it is the bootchain, how can I get a dump of a working one?
And I was able to dump a lot of stuff from [adb pull */*] and can access logs and dmesg, but havent inspected them fully. Is there an easy way to read the boot log and/or setup a custom log to run preboot? I figure that wouldnt be necessary since the linux kernel does a fine job of logging itself.
And yes I think I am skilled enough now, just was confused how to get to the adb shell, but I'm fairly well versed in linux, so the shell is relatively comfortable for me.
But if I'm able to figure it out I'm going to make a How To thread including what I've found and what you've found and posted to make it easier for nooblets in the future, maybe even make a simple shell script to repartition the US 8gb model.
I fixed it
how?
Jistropy said:
how?
Click to expand...
Click to collapse
Mainly luck hehe. But actually from the mentioned threads ^^^^^ and this nifty trick, but use caution as I have no clue how well this works for other devices, if it all. And a large part of the problem was that my battery was dead because it wasn't charging correctly when plugged into my computer; and it kept dying in Odin.
Do you have a similar problem?? I can probably help..