First off, I am no expert so please be gentle! I previously rooted my old Samsung Galaxy S i9000 and installed ICS, which went OK, but the phone became quite slow and unstable. I was advised to install RemICS and downloaded all the zip files from this forum, and put them on the external SD card. I followed the developer's instructions to the letter, as well as reading everything I could find on the subject. The reset and data wiping went fine, but the installation of the ROM didn't. It halted with an error message -`ROM incompatible, trying to use an invalid partition'. I repeat that this is supposed to be the specific ROM for the i9000. The phone now won't boot into recovery. It stops with an orange Android logo and the text `Powered by Mackay Kernel'. It won't boot into download mode either. The Mackay screen stays there however long I leave it. I really need help from the ROM developer but I can't post to that forum. How can I either boot into recovery or into download mode? Is this ROM reliable? What could I have done wrong?
More info:
Presumably everyone is on holiday! But just in case anyone is reading, there is further news. The reason I could not start recovery mode was that the button sequence was different from what I had been told. It now boots reliably into Mackay (which of course is TWRP). I have found that the phone is unable to mount the partitions DATA and SYSTEM - they seem to be corrupted. Hence it has not wiped DATA, although TWRP wrongly reports success. I have tried updating the partitions to ext3 or ext4 but this fails every time. I could format the thing from Windows but that will wipe everything including recovery of course. I need a tool to repair these partitions, but have not found anything so far. This may well have been the reason the phone was getting creaky in the first place.
I have copied a new ROM to the external SD card, using a card reader, and inserted this into the phone. Strangely the TWRP file manager reports that EXTERNAL SD is a sub-folder of SD CARD, and that is empty. The file manager does not show the real external SD card. But the real external SD shows up on the Windows USB connection. What is going on?
When I try to mount the partitions, DATA and SYSTEM can't be checked - the other partitions (Cache, sdcard, and emmc are all checked).
kingGrn Copeland
Well for the benefit of anyone else with the same problem, I have managed to re-flash the ROM back to stock. It just took 3 days of intensive web browsing until I understood how to do it, and found software that worked - a lot of stuff out there has errors.
To summarise, the problem was:
1. Data and System partitions became damaged, so phone became unstable.
2. Attempt to upgrade ROM failed because of damaged partitions.
3. Could not boot phone into recovery or download because button combination was different from what I was told.
The solution was:
4. Boot into download mode using correct button combination.
5. Re-flash back to stock ROM and re-partition using Odin.
Yes, someone did tell me that, and I would have done that straight away if I could have gotten into download mode. We live and learn
The solution was:
4. Boot into download mode using correct button combination.
5. Re-flash back to stock ROM and re-partition using Odin.
Click to expand...
Click to collapse
Thanks this wa useful for me too.
Related
I wanted to clear out my SD card so I used the setting in clockworkmod to repartition the SD card, but that apparently wiped out the system partition and after doing that my phone would not boot up. It would just get stuck at the Vibrant screen. After MANY attempts with ODIN, I finally was able to use Odin3 V1.7 along with Eugene_2E_JK2_Froyo to get a ROM on it and get my phone to boot back up, however now I can't update any apps or download new apps. When I look at the settings, it shows available app space as 0. There is plenty of system space and plenty of space on the SD card.
When I used Odin, the V1.7 version automatically checked the option to re-partition, but that doesn't seem to have changed the partition size. How can I get my Vibrant back to good working order? I can't install ClockworkMod again to try and flash a different ROM. Is there any way to change the available application storage space?
I'm pretty desperate at this point.
Thanks,
pamulli said:
I wanted to clear out my SD card so I used the setting in clockworkmod to repartition the SD card, but that apparently wiped out the system partition and after doing that my phone would not boot up. It would just get stuck at the Vibrant screen. After MANY attempts with ODIN, I finally was able to use Odin3 V1.7 along with Eugene_2E_JK2_Froyo to get a ROM on it and get my phone to boot back up, however now I can't update any apps or download new apps. When I look at the settings, it shows available app space as 0. There is plenty of system space and plenty of space on the SD card.
When I used Odin, the V1.7 version automatically checked the option to re-partition, but that doesn't seem to have changed the partition size. How can I get my Vibrant back to good working order? I can't install ClockworkMod again to try and flash a different ROM. Is there any way to change the available application storage space?
I'm pretty desperate at this point.
Thanks,
Click to expand...
Click to collapse
Can you Go into recovery & then into mount options & format data... worse case is to odin to stock then flash this over...
use the toolbox
http://forum.xda-developers.com/showthread.php?t=954509
No luck. If I use the toolbox and flash to stock Rom the phone doesn't fully boot. I get an error immediately after it reboots that says checksum error and then failed to wipe. I then see the Vibrant screen and the T-Mobile boot animation but then the phone goes completely black and does nothing. It seems that none of these processes are correcting the partition size problem that was created when I did the partition command in ClockworkMod. I'm just guessing, but if all of these are doing a format and not actually resizing the reserved application space partition then I'm never going to get a ROM to work.
I'm thinking that I may have to see if I can get it replaced under warranty since in it's current state T-Mobile shouldn't be able to tell that it was rooted. I hate to have to go through all of that though.
pamulli said:
No luck. If I use the toolbox and flash to stock Rom the phone doesn't fully boot. I get an error immediately after it reboots that says checksum error and then failed to wipe. I then see the Vibrant screen and the T-Mobile boot animation but then the phone goes completely black and does nothing. It seems that none of these processes are correcting the partition size problem that was created when I did the partition command in ClockworkMod. I'm just guessing, but if all of these are doing a format and not actually resizing the reserved application space partition then I'm never going to get a ROM to work.
I'm thinking that I may have to see if I can get it replaced under warranty since in it's current state T-Mobile shouldn't be able to tell that it was rooted. I hate to have to go through all of that though.
Click to expand...
Click to collapse
Do you have repartition in Odin checked?
I found several other posts regarding this exact same issue and everyone concluded there is no fix and it has to be replaced. Luckily I'm still under warranty and T-Mobile is sending me out a new one. Oh well...
Long story short I find myself in a boot loop and am a little hesitant to try what I believe to be the 'next step' to recovery in case I am mistaken and totally fubar my new toy. (this is my first android device and I'd prefer not to brick it in the first 24hrs!)
As to how I got myself into this situation here's a play by play.
1) Researched internet for best value tablet with awesome dev community. Found my gtablet and xda! (buy, buy, buy!)
2) I spend the week leading up to taking delivery of my new tablet reading everything I can get my hands on.
3) Unpacked new tablet and played with stock rom briefly before saying farwell.
4) Installed clockworkmod .08 and then TNT Lite 4.4 and everything worked wonderfully
(youtube.com/watch?v=mY_FvJnWNEw&feature=related) used this method
5) when I turned my gtab on for round 2 I find myself in a boot loop, I figured there's an issue with something I changed so since clockwork seems to be working brilliantly and the update.zip file in root is the same I wipe data/factory reset and wipe cache partition and then rerun the update. This still leaves me in a boot loop...
6) In further reading the recommended fix seems to be repartition sdcard and then reinstall rom with clockworkmod off of sdcard2. I put the update.zip file with \Recovery\command (edited to point to sdcard2) onto the microsd popped the micro sd into the tablet and restarted... the tablet did not read the microsd when i started up clockworkmod. And so I am left with questions at this point and a semi-bricked device.
am I correct in trying to repartition the sdcard as my next step?
does the mircosd need to be of a certain format?
have I done something ridiculously obviously wrong??
Thanks in advance for your any help or guidance you can provide...
I'm experiencing the same thing man. However, i have another g-tablet that i haven[t cracked open yet and i'm wondering if i can just partition and copy/paste the folders from the g-tablet that hasn't been opened to get the device back to stock.
Hello!
I have just recently (last night) successfully recovered from your *exact* same problem. Short answer...Yes, Install CWM on your micro card, partition the sd card (2048 and 0). I have my microsd card formatted to FAT32.
Here is my thread:
http://forum.xda-developers.com/showthread.php?t=1028118
I specifically used "butchconner"'s first post although all of the responses were friendly and helpful!
Best of luck!
Pat
Wait a minute everyone!!!! (Talking about gilpin)
He said when he tried to boot the microSD card, he couldn't find it in CWM.
If CWM is up, that's the main thing he needs??!!!
If you can get into CWM, go to the Advanced Menu and run the Partition, Fix Permissions and Wipe Dalvik Cache options. Then go to the Main Menu and run
the Wipe Cache and Wipe/Reset Factory Settings.
Then re-boot and see if your tablet is okay.
If it's not (and CWM is still working), you can put the appropriate ROM update.zip
in /sdcard and then select and load it through CWM.
Hope this helps.
Rev
geedup,
If you are boot looping also, you need to re-partition and the nvflash back to
stock.
The following thread pretty well covers nvflashing:
http://forum.xda-developers.com/showthread.php?t=861950
After you nvflash, check to see if you still are getting boot loops.
If so, you need to load CWM and do the same thing as gilpin. When
you finish the CWM routine either it will be working -- or you can
nvflash again and it should be good to go.
Let me know......
Rev
working again...
Thanks for the fast replies all! I repartitioned my sdcard (2048, 0) reset permissions, cleared data and then rebooted. This seems to have fixed my problem as I booted cleanly and everything is working again!
Hi everyone,
In my overzealous attempts to reformat an old 4gb external SD card through CW Recovery, I managed to reformat my internal SD card (I was using the Clockwork Recovery version 2.5). I thought that "format sd card" would reformat my external memory card and not leave me without a usable phone, but I guess I misunderstood.
I spent at least five hours going through all of the ODIN tutorials and trying them out, and found that using Eugene's 2.2 with 2E recovery ROM actually allows me to boot up (hooray! ), while the stock rom from this thread simply forces a bootloop on my poor phone, with occasional freezes. Even using AIO's "Flash to Stock" from Eugene's 2.2 doesn't work.
Further searching has lead to the thread about partitioning using parted, which has been hard for me to use effectively (I made a new partition, but I couldn't get it to mount properly).
I was really excited to come across this tutorial, but it didn't solve my problem. After getting through all of the steps, at step 5, ODIN3 versions 1.0, 1.7, and 1.81 (I tried all 3 on 3 different walk-throughs of the tutorial) never were actually capable of repartitioning the sdcard properly. Every time after the first time of using "parted" to reduce the card to a single partition, I found that that lone partition was always the only one there (15.5 gb /SYSTEM Fat32). No changes had been made to the sd card's partitions.
I don't know if it helps any, but the ROM I was running before I reformatted the card was Bi-Winning 3.0, and Voodoo had not been disabled at the time of the reformat, which may be why I can't flash new ROMs through the recovery as well.
As near as I can tell, ODIN can't actually return my vibrant's partitions to factory settings, so is there a way for me to do that manually? I think that would solve my problem.
Thanks,
-NewbieCube
My guide (you linked to) clearly states its not for this intent... if you read it, you would also see I linked to Eugenes froyo that does not brick. If you did it, THEN you did my guide ODIN to JFD, you are on a fully functional stock 2.1 JFD build.
If your intent was to just format the external sd, go to menu settings, sd card/phone storage, unmount the external and format it.
Right, I know that. In fact I read all through your thread and tried to flash to Eugene's first, and then to JFD, but JFD does not boot properly. It just gives me a black, unresponsive screen. I'll definitely go back through once more and try that again, though, as you clearly know what you're talking about.
I basically formatted the wrong storage (internal sd vs external sd), and would like to get that internal back to stock, so you are right that Eugenes -> JFD should work. I'll report back with results.
^ yeah, exactly... that should work with no issues. let me know if it does not.
Oddly enough, that didn't work for me either. Since my phone still can boot into Eugene's (albeit with 0.00B available to apps), I know this should work, just from reading through your guide. So once more, here's what I did:
1. Download mode -> ODIN 1.70: Flash Eugene_2E_JK2_Froyo.tar.md5, and s1_odin_20100512.pit (from Eugene) Re-Partition NOT checked (Eugene's thread says not to)
2. Boot up into Unbrickable Froyo, with no application space remaining Mount sdcard and move Update.zip (s15274n's) into the root folder without issue.
3. Download mode -> ODIN 1.70: Flash s1_odin_20100512.pit, and T959UVJFD.tar (s15274n's) with Re-Partition checked
4. Boots once automatically into recovery, saying something about a failed MBR checksum and failure to clear userdata
5. Bootloops that never get past the VIBRANT logo screen
6. Boot into recovery and try deleting user data and cache data manually and to reinstall packages, but bootloops continue.
I really don't know what I'm doing wrong here...
UPDATE:
I even used Heimdall on another computer and got the same result, so it isn't ODIN. Why is reformatting the internal SD card to stock so difficult to do?
delete my post
I FIGURED IT OUT!!! ...by random chance
For my problem, it was indeed the voodoo lagfix that was messing things up, and this post:
http://forum.xda-developers.com/showthread.php?t=888084
helped me out tremendously.
Hi guys i have problem with a phone thats friends gives me to repair and this is the problem.
Phone was dead so i put in download mode and flashed with "T959UVJFD" , and the phone stucks on GALAXY S logo and then the 4 lights of the down of the phone on and the screen was black so i tried differents combinations of roms, pits files , etc.
The phone finaly booted propely when i flashed a kernel "Bali_1.8.8UV-zImage" with heimdall .
After the phone booted i was happy but i checked and internal 16gb was not recognized and also when i inserted sd card also no detected.
Finaly i was searching solution also when tried to flash with RIFF BOX BY jtag and still same , phone only boots when i flash with kernel "Bali_1.8.8UV-zImage" but still no internal or external storage .
Also in recovery mode messages like
"can't mount /dev/block/mmcblk0 (or /dev/block/mmcblk0p1)"
Anybody can help me?
I need to work one of them storages
Did you ever find a solution to this? I have an old Vibrant laying around that has this same problem....both the external and internal memories are unavailable no matter what I do.
rikimaer said:
... Also in recovery mode messages like
"can't mount /dev/block/mmcblk0 (or /dev/block/mmcblk0p1)"
Click to expand...
Click to collapse
a) When you see this message in recovery, what happens if you simply select "Reboot phone" and hit the Power button? Does it then boot up?
b) mmcblk0 = Internal sdcard. I hate to say it, but it sounds very likely your friend's phone could have been hit by the Encyption Unsuccessful bug (refer to Merio90's thread).
As a test, you could follow Merio90's OP steps and use the updated CWM recovery (via update.zip) to re-partition your external sdcard. Note: all data will get wiped (so backup first). When you "reinstall packages" in recovery, you may get that "can't mount ... emmcblk0" error again. Just "reinstall packages" again. Then see if you get int / ext sdcard detection at that point.
If still not detected, proceed to flash a CM7 v7.2.0-vibrantmtd rom. Flash it twice (1st flash updates recovery; 2nd flash converts to mtd partitioning and flashes rom). Merio90's thead is geared towards ending up at an ICS rom, but keep in mind essentially all of the Vibrant EU occurences have been on ICS rom's. This is why I suggest using that stable CM7 build as a test. For kicks, see if you get sdcard detection (probably not). If not, do the vold.fstab emmc/sdcard swap, which works the same and uses the same syntax on GB & ICS (ie. refer to Merio90's OP for vold.fstab syntax). Flash CM7, edit your vold.fstab, & reboot (for swap to take place).
If you're good to go ... you can always proceed onto a JB rom from there. Read through the last discussions re. JB rom flashing issues and kernel compabitibility - ie. to save you the trial & error.
If you still don't get sdcard detection at this point, maybe this is something different altogether. But, my hunch is that you'll get detection on CM7 (after the vold.fstab swap).
Okay, this is quite a long story, so I apologise in advance.
I decided to update my Galaxy S2 today to a newer ROM (SuperNexus 2) with the latest version of Android. I was coming from a CM9 build. I went through the usual process of backing up data and performing a full NANDROID backup via CWM Recovery, booted the phone again and transferred the backups to my PC via USB. These files transferred fine.
I then downloaded the zip files for the new ROM and proceeded to copy them to the internal storage of my phone. The copy dialog in Windows said that it was "discovering items" and stayed like this until I turned off USB transfer mode on the phone and removed it (ie. the files failed to copy) This happened a number of times and I didn't get anywhere. I have plenty of space free on the SD card, but just to make sure I started the phone in CWM again and formatted the SD card, and since I was going to do it anyway, the data and cache partitions too. When I booted the phone again, the files still wouldn't copy. I managed to copy a text file to the phone which was about 32kb but anything larger just seemed to fail.
I then went back into CWM and decided to partition the SD card, as I thought that it may have been corrupted somehow and needed to rebuild the filesystem. This however, caused even more problems as trying to format the SD card (In CWM) now just reported "Error, can not mount E:/sdcard".
Feeling fairly frustrated, I decided to download the Stock ICS ROM for the Galaxy S2 and install it via Odin, thinking that the problem was probably with CWM. The install went fine, but upon reboot the phone just stayed on the boot animation, no matter how long I left it. To make sure the install went smoothly I decided to try and reinstall the Stock ROM via Odin again, but now Odin didnt seem to get past the "Initializing.." stage.
So all in all, I now have a phone which wont boot into Android, cant copy anything to internal storage, and Odin wont seem to connect to.
I am convinced this is a software issue and therefore fixable. But maybe the internal storage was not working correctly in the first place. I have installed many ROMs before and never had such issues.
Anyone know anything about this or how I could potentially fix it? Thanks so much in advance!
Benji1992 said:
Okay, this is quite a long story, so I apologise in advance.
I decided to update my Galaxy S2 today to a newer ROM (SuperNexus 2) with the latest version of Android. I was coming from a CM9 build. I went through the usual process of backing up data and performing a full NANDROID backup via CWM Recovery, booted the phone again and transferred the backups to my PC via USB. These files transferred fine.
I then downloaded the zip files for the new ROM and proceeded to copy them to the internal storage of my phone. The copy dialog in Windows said that it was "discovering items" and stayed like this until I turned off USB transfer mode on the phone and removed it (ie. the files failed to copy) This happened a number of times and I didn't get anywhere. I have plenty of space free on the SD card, but just to make sure I started the phone in CWM again and formatted the SD card, and since I was going to do it anyway, the data and cache partitions too. When I booted the phone again, the files still wouldn't copy. I managed to copy a text file to the phone which was about 32kb but anything larger just seemed to fail.
I then went back into CWM and decided to partition the SD card, as I thought that it may have been corrupted somehow and needed to rebuild the filesystem. This however, caused even more problems as trying to format the SD card (In CWM) now just reported "Error, can not mount E:/sdcard".
Feeling fairly frustrated, I decided to download the Stock ICS ROM for the Galaxy S2 and install it via Odin, thinking that the problem was probably with CWM. The install went fine, but upon reboot the phone just stayed on the boot animation, no matter how long I left it. To make sure the install went smoothly I decided to try and reinstall the Stock ROM via Odin again, but now Odin didnt seem to get past the "Initializing.." stage.
So all in all, I now have a phone which wont boot into Android, cant copy anything to internal storage, and Odin wont seem to connect to.
I am convinced this is a software issue and therefore fixable. But maybe the internal storage was not working correctly in the first place. I have installed many ROMs before and never had such issues.
Anyone know anything about this or how I could potentially fix it? Thanks so much in advance!
Click to expand...
Click to collapse
I9100?
Can get to DL mode?
Can get to recovery?
Get an older Odin version and flash siyah just to see if it can be flashed again.
If you can get to recovery, Nuke Script is the way to go.
It sounds to me that maybe your memory is corrupt...
Not just yet, smells like soft brick.
Sent from the little guy