Related
Guys, need some help here
I'm generally ok at fixing these sorts of problems but this one has got me well and truly stumped.
Been trying without much luck to flash a working fw onto i9000 since updating to rom with voodoo and forgetting to disable lage fix before flashing non voodoo rom. Even flashing back with voodoo rom doesnt help.
I think I've finally managed to ascertain the root cause of the issue seems to be that either the internal sd card is somehow write protected or the current journalling on the ext4 partition is undoing and changes to that partition (where does journal reside?). I seem to be in a viscious circle as well. I cant mkfs a new ext2 partition as it complains that it wasnt unmounted cleanly, If I ignore I get a segmentation fault. If I e2fsck the partition it complains it cant write to the superblock, If I use alternate superblock it complains there is data in the journal, trys to replay the journal and complains it cant write the superblock. If I tunefs to disable the journal it complains that the needs_recovery flag is set so need to e2fsck the filesystem first :-S.
I've flashed kernel that has recovery option to disable lagfix. If I choose this and reboot it just sits at Galaxy S boot screen indefinite (over an hour waited). If I mount USB using same recovery mode, I can see the files in the partition, I can (through windows) delete the files so folder shows no files however disk still shows a percentage used. If I eject and remount all the files are back. I have formatted the partition as fat32 and re-labeled the drive. Format completes succesfully (done this both using cmd line and right click format). on eject and remount, label change has remained but files are back again. Partition still shows up as ext4 when looking via adb shell.
Have tried to use parted, but despite all parted functions giving success indicator, no changes are ever made.
I'm now at a loss on how to proceed?
Anyone any ideas on what next steps could yield any further results?
I had a similar issue... what solved it was to flash Darky's ressurection rom. Had to flash it 3 times in a row.. Flashed with Odin 1.7.
Hope it helps, i know how frustrating it is.
Sent from my GT-I9000 using Tapatalk
I have tried Darkys res rom, It wouldnt boot, just stuck at Galaxy S boot screen so didnt persue it. I'll try doing it multiple times as you suggest and let you know. Ta
EDIT: Nope tried it 4 times, same result, boots to Galaxy S screen, I get the voice prompt saying its coverting system, will take approx 2 mins, then another voice prompt about restore, then it sits there indefinetly (waited about 20 mins each time). Whilst its in this state adb devices shows device in recovery, and I can get an adb shell, however there seems to be no commands accesible, cd, ls, mount etc
nivenj said:
I have tried Darkys res rom, It wouldnt boot, just stuck at Galaxy S boot screen so didnt persue it. I'll try doing it multiple times as you suggest and let you know. Ta
Click to expand...
Click to collapse
I have a way that may fix your bricked phone. If it gets to the SGS logo boot animation, I would try flashing CM7. Try it out and then try reverting back to a stock rom.
Here are the instructions:
http://forum.cyanogenmod.com/topic/15275-gt-i9000-cyanogenmod-7-we-love-bugs-version-20110211/
You MUST follow the instructions to the letter though. Do not deviate from them!
How do I know this may work? Because it happened to me. My phone was bricked, then I flashed CM7 and now it works again. I've tested going back to stock rom and it works. Give it a try. It may be tough reverting back to stock since CM7 gingerbread is awesome! lol
If that doesn't work try flashing one of the earlier Froyo ROMs, I used XXJP2, and then moving on from there. The key is to ensure that whatever ROM you use has all three files (PDA, Modem, & CSC) and tick Re-Partitioning on Odin.
Again this is what worked for me and my device was restored to great working order.
robbiev80 said:
I have a way that may fix your bricked phone. If it gets to the SGS logo boot animation, I would try flashing CM7. Try it out and then try reverting back to a stock rom.
Here are the instructions:
http://forum.cyanogenmod.com/topic/15275-gt-i9000-cyanogenmod-7-we-love-bugs-version-20110211/
You MUST follow the instructions to the letter though. Do not deviate from them!
How do I know this may work? Because it happened to me. My phone was bricked, then I flashed CM7 and now it works again. I've tested going back to stock rom and it works. Give it a try. It may be tough reverting back to stock since CM7 gingerbread is awesome! lol
Click to expand...
Click to collapse
Thanks for the suggestion but this wont work, as I said above, the root of my problem is that the internal SD card wont keep any changes I make to it. Once I upload the zip file and the phone reboots into download mode in order to flash with Odin, the files I would have put on the internal SD card will no longer be there. It seems to me that the FS cant set the recovery_flag to clean and therefore keeps replaying the journal and overwriting any changes on reboot.
I sort of proved this earlier, by managing to flash JP4 with speedmod kernel. This allows the phone to boot, but it has major force close issues. I can take a photo, see it in images, I can even mount it via USB and see it on my laptop. When I reboot, the photo is gone and anything I've deleted is back again.
Fundamentally I need someone who maybe has some experience fixing the filesystem, I cant see any Roms working until this manages to get resolved
thecrucible said:
If that doesn't work try flashing one of the earlier Froyo ROMs, I used XXJP2, and then moving on from there. The key is to ensure that whatever ROM you use has all three files (PDA, Modem, & CSC) and tick Re-Partitioning on Odin.
Again this is what worked for me and my device was restored to great working order.
Click to expand...
Click to collapse
Ive tried JP2, but no joy. Also tried
JFF,JS5,DDJG4,Darkys Res,JP4,JM8,JS3,EUGENE373,JPC,JP3,JM5 & Finally JPU, All with a mixture of partitioning and not.
got an ext-sd card? if so remove it, format sd, then try factory reseting,
edit : flash an old rom, like jm2, ascertain its function then yell again (missed a line *doh*)
azuresystem said:
got an ext-sd card? if so remove it, format sd, then try factory reseting,
edit : flash an old rom, like jm2, ascertain its function then yell again (missed a line *doh*)
Click to expand...
Click to collapse
Yep tried all that, tried formating via recovery mode, says successful, but all data still exists on reboot. Have tried formating using windows, via command line, via adb shell, they all say they are succesfull but on reboot, same problem exists and all data is still there :-S
nivenj said:
Ive tried JP2, but no joy. Also tried
JFF,JS5,DDJG4,Darkys Res,JP4,JM8,JS3,EUGENE373,JPC,JP3,JM5 & Finally JPU, All with a mixture of partitioning and not.
Click to expand...
Click to collapse
I am sorry, not sure where to go from there. Keep Googling and maybe you'll come across something helpful.
Sent from my Galaxy S using Tapatalk
Hi. Has anyone come across a solution to this problem. Any changes to the data on my internal SD card are lost on reboot, and many of my apps are not working.
jm_928 said:
Hi. Has anyone come across a solution to this problem. Any changes to the data on my internal SD card are lost on reboot, and many of my apps are not working.
Click to expand...
Click to collapse
Try editing the void.fstab to swap the internal sd card and external sd card. --- it won't address issues with internal card, but it may get you up and going again..
fooman123 said:
Try editing the void.fstab to swap the internal sd card and external sd card. --- it won't address issues with internal card, but it may get you up and going again..
Click to expand...
Click to collapse
Thanks fooman123. Can you tell me where I can find the void.fstab file?
jm_928 said:
Thanks fooman123. Can you tell me where I can find the void.fstab file?
Click to expand...
Click to collapse
see this tread:
http://forum.xda-developers.com/showthread.php?t=1088474&page=14
use the correct void.fstab for your phone (i9000 and i9003 are different)
backup the original and compare the new and old void.fstab file..
Hi,
I was happily using my blue-dot NC with CM7 Nightly-177, as suddenly it started to boot ONLY to recovery (CWM 3.2.0.1).
I had used the NC, then put into a neoprene type cover, and put all in a soft bag, and carried it in the car and when I wanted to power the NC on, I was in recovery..
SDCard was intact, could read and copy the contents in my PC.
Tried everything including trying to install CM7 from the sdcard anew multiple times.
It boots from the sdcard, I wipe data, I wipe cache, I wipe dalvik cache, I find and install zip, I install gapps, everything goes OK.. I power down, take the sdcard out. I powerup.. I have the green logo, then the recovery...
What could I be doing wrong?
I'm really pissed off, and thanks for any help.
I wouldn't have wiped data. (I hope you have a backup.) Since it will boot into recovery off the eMMC, put a nightly on a non booting SD card and try again and only wipe Davlik. Normally when updating with ROM Manager that is all you need to wipe. You also might want to flash the gaaps .zip again if you find the market missing after you get back into CM7.
Seemed like you flashed ROM manager into eMMC.
patruns said:
I wouldn't have wiped data. (I hope you have a backup.) Since it will boot into recovery off the eMMC, put a nightly on a non booting SD card and try again and only wipe Davlik. Normally when updating with ROM Manager that is all you need to wipe. You also might want to flash the gaaps .zip again if you find the market missing after you get back into CM7.
Click to expand...
Click to collapse
Well, I had asked the same question at androidtablets.net, few days ago, and I was told do take this route, wiping the data and all.
BTW, I have a backup yes..
votinh said:
Seemed like you flashed ROM manager into eMMC.
Click to expand...
Click to collapse
So? How do I use this comment to help my problem?
velizet said:
So? How do I use this comment to help my problem?
Click to expand...
Click to collapse
Did you try what I suggested in the 2nd post?
patruns said:
Did you try what I suggested in the 2nd post?
Click to expand...
Click to collapse
Yes, multiple times with different zips..
It is always, the green Cyanogen logo, says loading, a little flicker, and the amber menu..
That is very odd. Possibly you have a corrupted image on your card. Have you tried creating the bootable image all over again?
Dumb question..... is it fully charged?
patruns said:
That is very odd. Possibly you have a corrupted image on your card. Have you tried creating the bootable image all over again?
Dumb question..... is it fully charged?
Click to expand...
Click to collapse
It is even on the mains.
I have tried creating the bootable drive more than once. The image is the one that I have used for the first time..(1gb_clockwork-3.2.0.1-eyeballer)
I will try reverting to stock, and then install once more. If not, I will try to boot from the sdcrad (double boot).
Either I am missing some very basic step, or it is really odd..
velizet said:
It is even on the mains.
I have tried creating the bootable drive more than once. The image is the one that I have used for the first time..(1gb_clockwork-3.2.0.1-eyeballer)
I will try reverting to stock, and then install once more. If not, I will try to boot from the sdcrad (double boot).
Either I am missing some very basic step, or it is really odd..
Click to expand...
Click to collapse
Patruns, now I have a nook color e-reader ver 1.2..
Before trying once more I want to check with you which image, which nightly, and which gapps should I use, and maybe from where to download..
I have a 4 GB Sandisk sdcard.
Do you want to install CM7 to the internal memory (eMMC) or just running it off the uSD?
You have to know what you want to do first.
velizet said:
It is even on the mains.
I have tried creating the bootable drive more than once. The image is the one that I have used for the first time..(1gb_clockwork-3.2.0.1-eyeballer)
I will try reverting to stock, and then install once more. If not, I will try to boot from the sdcrad (double boot).
Either I am missing some very basic step, or it is really odd..
Click to expand...
Click to collapse
votinh said:
Do you want to install CM7 to the internal memory (eMMC) or just running it off the uSD?
You have to know what you want to do first.
Click to expand...
Click to collapse
Of course I would like to install to emmc..
I assume you have a brand-new (or like brand-new) v.1.2 NC and you don't want to deal with its partitions.
1. I never try that 3.2.0.1 from eyeballer, but it should be good. Just make sure you not get the corrupted one during download
2. Get the Win32DiskImager old version, r0.15 or something
3. Create flashable uSD (i'm sure you know how to)
Make sure it's good (there should be 4 files in the boot uSD)
4. Get the stable CM7 7.1 and the latest Gapps (0811 or 0821)
5. Drop both in the uSD
6. Fire the NC up.
7. It should get into the CwM R, from there
a. format /system
b. format /data
c. format /cache
Note: I didn't format /boot when doing mine.
d. install CM7 first
e. then install Gapp
8. perform wipe data/factory reset
9. after done, remove the uSD before reboot system.
Give it some times during the first boot.
If after 10' and still not up, then force reboot.
Keep fingers crossed.
I really hope someone can help..
I'd previously installed CWM and rooted my one, but was still using the stock ROM (.13)
I wanted to wipe my One and have a fresh start after having tried out a load of apps and trying to get the menu/logo mods going..
I chose to wipe everything through the android settings, but my SDCard was still full of my stuff afterwards, when I'd chosen to remove it all..
I then made my mistake. I booted into CWM and chose to format a few of the different options it allows under Mounts and Storage. tbh, I exactly forget which now.
Now, it'll still boot into CWM but wont get past the HTC splash screen when booted normally.
I have nandroid backup I originally took while rooting available on my PC, as well as a image.zip I made at the same time.
Would anyone be kind enough to help me resurrect it pleeeease?
panic over..
just in case it helps out anyone who does something similarly dumb:
I copied my backup.zip onto a USB drive, connected it using a USB OTG cable and CWM let me restore it from that = booting HTC one.
However, you can push the rom into the sd when you're on recovery and with a pc type:
Code:
adb push name_of_recovery /sdcard
Guich said:
However, you can push the rom into the sd when you're on recovery and with a pc type:
Code:
adb push name_of_recovery /sdcard
Click to expand...
Click to collapse
Thanks.. I'll keep that for the next time I stuff it up!
This from a real noob, but I thought I would solict some additional input if there is some trick I have missed on my problem.
Since installing CM 10 on my Vivid, everything has worked well except the fact my internal SD has gone away. Based on stuff I have read here I have tried the following:
1. Factory Reset - no help
2. Mount drive using installed recovery, CWM - No Help
3. Install TWRP recover and try that, no help
4, Try various apps from Play Store, No Help
At this point it seems best to me to return the phone to factory state and see if the internal card is there, if it is, unlock the boat loader, install TWRP recover, then flash the rom, then boot imate (s on) and hope it works.
Any app that requires root and access to all the drives errors out.
A large group thanks to all of you who post so much info on the phone, and how to do things.
I assume you've tried mounting Internal SD in the Settings/Storage menu?
Sent from my Vivid 4G using Tapatalk
Internal Mounting
Thanks for reminding me about this, but yes, I have tried it numerous times but it doesn't work. A bit frustrating since it keeps me from storing certain stuff or using some rooted apps. Unless I find some other way, I will give the restore option a try in a few days when I get home.
Appreciate the reply.
pwebber09 said:
This from a real noob, but I thought I would solict some additional input if there is some trick I have missed on my problem.
Since installing CM 10 on my Vivid, everything has worked well except the fact my internal SD has gone away. Based on stuff I have read here I have tried the following:
1. Factory Reset - no help
2. Mount drive using installed recovery, CWM - No Help
3. Install TWRP recover and try that, no help
4, Try various apps from Play Store, No Help
At this point it seems best to me to return the phone to factory state and see if the internal card is there, if it is, unlock the boat loader, install TWRP recover, then flash the rom, then boot imate (s on) and hope it works.
Any app that requires root and access to all the drives errors out.
A large group thanks to all of you who post so much info on the phone, and how to do things.
Click to expand...
Click to collapse
My guess... Is you did a reset from fastboot...
If that is the case... I recommend getting twrp... Installing that... Mounting both storages in recovery... Then hook to your windows PC... And let windows format your internal SD...
After a reboot... Your phone will either mount your internal... Or offer to format it again... At which point it will work...
Unless we are talking about apps2sd in CM11...
Sent from my Vivid 4G using Tapatalk
More Info
rignfool said:
My guess... Is you did a reset from fastboot...
If that is the case... I recommend getting twrp... Installing that... Mounting both storages in recovery... Then hook to your windows PC... And let windows format your internal SD...
After a reboot... Your phone will either mount your internal... Or offer to format it again... At which point it will work...
Unless we are talking about apps2sd in CM11...
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
____________________
As far as I know I did not reset from fastboot, but I have been in that mode a good number of times, so it is very possible.
I replaced CWM recover with TWRP and it would not allow me to mount the internal card, but the phone booted up OK, just no internal card. So I tried another factory reset and while in TWRP I noticed I was also getting a "can't mount /emmc/" message. Phone still boots up ok and works except for apps requiring access to the internal card.
I ran across some reference to a recovery called aroma something that is supposed to help with this problem, but am not sure it will work with my phone, still researching that.
So maybe this is pretty good evidence I did screw up and reset from fastboot?
I figure I am going to have to restore the phone to factory status, and start over, but I will wait to see if there any other suggestions.
Thanks again for the feedback.
pwebber09 said:
____________________
As far as I know I did not reset from fastboot, but I have been in that mode a good number of times, so it is very possible.
I replaced CWM recover with TWRP and it would not allow me to mount the internal card, but the phone booted up OK, just no internal card. So I tried another factory reset and while in TWRP I noticed I was also getting a "can't mount /emmc/" message. Phone still boots up ok and works except for apps requiring access to the internal card.
I ran across some reference to a recovery called aroma something that is supposed to help with this problem, but am not sure it will work with my phone, still researching that.
So maybe this is pretty good evidence I did screw up and reset from fastboot?
I figure I am going to have to restore the phone to factory status, and start over, but I will wait to see if there any other suggestions.
Thanks again for the feedback.
Click to expand...
Click to collapse
Ok...
You were close...
Don't mount internal for twrp...
Mount as USB mass storage in the same menu...
Then connect to windows...
Sent from my Vivid 4G using Tapatalk
I will give it a try
rignfool said:
Ok...
You were close...
Don't mount internal for twrp...
Mount as USB mass storage in the same menu...
Then connect to windows...
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
Thanks very much, I will probably do this a bit later today and will let you know how it goes. Thanks for taking the time to help me out.
It Works!
Thanks againk, that solution did the trick.
First of all, sorry for the bit of a text wall below, but if you could bare with me, I really need help and would greatly appreciate any comments that could be of help. Thank you.
So I was looking at a thread on how to do something so I changed two lines on build.prop. I made a back up of the original build.prop file. So my phone was able to start up but everything was invisible and couldn't do anything other than use my notification shade and respond to messages. I ended up turning on emergency mode then I turned it off right after and that fixed it. I guess I messed up when I copy and pasted the original build.prop and replaced it with the one that made my phone mess up in the first place. This messed it up my phone even more and now it's in a bootloop. I can only go into ODIN download mode and recovery. I tried clearing system cache but that didn't help at all. The first time my phone messed up it showed up as a drive on a few different computers that I used, but once the bootloop started it won't be recognized as a drive on any of the three computers I tried. It shows up as "Gadget Serial" when in download mode and when it's powered off it shows as SAMSUNG_Android. I have installed the Samsung phone drivers on two of the computers but that didn't help either.
When it shows up as SAMSUNG_Android it shows that MTP USB Device didn't install properly. I was thinking maybe that's what is causing the problem? I am using the original usb cable that came with the phone. Odin recognizes it so I could always restore it with a ROM, but I need to backup my photos (to my fault, I haven't done a backup in awhile) before I restore it to a fresh ROM. No android file explorers show it either, or a root explorer like Droid Explorer. I've also tried to connect it to a mac (third computer) but that doesn't show up either.
Some person suggested to me to restore with a ROM that saves data, but to no avail, I couldn't find one (anybody know of any?)
I was also reading about using the wipe data/factory reset, but I couldn't get a straight answer if it deletes or keeps the data in the SD Card section on the internal storage (does anybody know?)
So I feel like I might be screwed and may lose my photos and other data. If I could connect my phone to my computer properly, I might be able to edit build.prop again to fix the problem. If I can't connect it to my computer ever, is there any other way I could back up my photos or other data? I have a OTG cable if that helps at all.
Some additional info: I'm on a stock ROM, stock kernal, and rooted. And yes I had R/W on when editing build.prop.
So any ideas guys, I really need to get my phone up and running again.
Thanks in advanced.
Just reflash the stock ROM through ODIN.
EncryptedCurse said:
Just reflash the stock ROM through ODIN.
Click to expand...
Click to collapse
That won't delete my data (i.e. my photos and and other files on sd card portion)?
FrostyChill said:
That won't delete my data (i.e. my photos and and other files on sd card portion)?
Click to expand...
Click to collapse
i dont have an answer to that question, but whats more important - fixing ur phone or keeping ur now-unaccessable-anyway files?
i THINK replacing a rom does not delete ur data, but i highly recommend waiting for someone else to chime in as I am completely unsure and just going off what i think i've read before.
take this as a lesson, any time you are going to play with system files (be it in a phone or computer), backup anything you care about, and be prepared to lose what you dont.
Flashing rom doest wipe the data in the external sd card but it do wipe the internal storage i recommend flashing a rom after taking out your sd card
jassi150 said:
Flashing rom doest wipe the data in the external sd card but it do wipe the internal storage i recommend flashing a rom after taking out your sd card
Click to expand...
Click to collapse
considering this is the S6 forum, its safe to assume hes talking about an S6, which means its safe to assume he cant do that.