Hi guys,
I can't work out why but when I go to wipe all settings then install custom rom from zip file in cmw recovery, it completes normally but after the reboot it just stays on the android bot. I went back into recovery and managed the phone through usb to my PC & saw that in the phone storage there was nothing where there is obviously supposed to be boot files. I have installed this custom rom before & it has been no problem. I also have tried a few other roms (all that i've tried before & they all work) and the same thing happens. I have found one rom that worked strangley and when I manged the phone on my PC i saw that it has placed the boot files on the sd card (not the phone storage).
how can i fix this.
i am very new to rooting so please no complicated talk
can someone not help? this is a big issue.
ill try and explain the problem in more detail below...
i have been messing with my phone lately using CMW TOUCH to wipe my data then install rom from zip. everything was going great until now.
i want to install a rom (that i have installed before.so i know its compatible with my phone), i go through tge same procedure of wiping data then installing from zip.all goes the way it should with it telling me its installing from zip, after a while it tells me to reboot the phone. when i do all that happens is it stay on the green android bot for 1 min then reboots. i went into CMW TOUCH to connect phone to pc & found out that it installed nothing, nothing on the phone storage and on the sd card except the custom rom.
i have tried this with few other roms all with the same results.
NOW...
ive managed to find a rom that will install so it is functional all except recently after a reboot it has stopped detecting the sim，weird.
i connected the phone to my pc to find that all boot files are stored on the sd card not phone storage like it used to.
i had an idea that i will try later today and that is to move the custom rom over to the phone storage from the sd card. remove the sd card during install. maybe that will force the install to use the phone storage for the boot files
will let you know the outcome
jamos
i have just tried to install the rom with the sdcard removed from phone & the same thing happened. even though during the installation it tells me that it is formatting system then installing it installs nothing to the phone storage.
Related
I had problems with my galaxy S, which was running on official 2.3.6
I decided to wipe everything clean and install a custom rom
But during the process, I've come across a weird weird problem
I started to get UIDs system error and was asking me to wipe data partition to use the phone
so I tried to wipe all the partitions
I have tried wiping int sd card via phone -> didn't work
I have tried wiping via cwm -> didn't work
I have tried wiping & re-partition via odin + reinstall -> didn't work
I have physically deleted contents from int sd while connected via USB -> didn't work
I have formatted the removable disk (int sd) while connected via USB -> didn't work
what I mean by didn't work is, the next time I reboot, I find that all the contents in my phone comes back alive...
I don't know what I can do to fix this problem
I can install new mods fine, but due to the fact that old system files and apps are present together, which didn't get wiped, and causes clashes and my phone won't work as it starts up... I really don't know how I can fix this problem and wipe my phone clean to "resurrect" it..
please help me if you know solution to this problem
This really sounds weired.....
You should download sd maid for root users (search for the paid version)
There you have many options for finding odd data on your sdcard and internal phone storage
you can delete files
sd maid makes you find some dead apps wich make your problems
give me a feedback if it works..or not
stay well
jiffer1991 said:
This really sounds weired.....
You should download sd maid for root users (search for the paid version)
There you have many options for finding odd data on your sdcard and internal phone storage
you can delete files
sd maid makes you find some dead apps wich make your problems
give me a feedback if it works..or not
stay well
Click to expand...
Click to collapse
hey thanks for the suggestion, but at the moment, I can't use the phone at all because all my basics apps and system apps clashes on boot up, no matter what I flash on to my phone, hence basically it won't start up.. so I can't use any apps infact the phone itself
Only thing I can do is via CWM recovery mode, or via odin
If you know how to deal with this problem via that way, it will be great~
jdarkj said:
hey thanks for the suggestion, but at the moment, I can't use the phone at all because all my basics apps and system apps clashes on boot up, no matter what I flash on to my phone, hence basically it won't start up.. so I can't use any apps infact the phone itself
Only thing I can do is via CWM recovery mode, or via odin
If you know how to deal with this problem via that way, it will be great~
Click to expand...
Click to collapse
Ok it seems if something went wrong during ur installation
To bring ur phone back to life
1. http://www.sammobile.com/firmware/ go here type in I9000 and search for the stock rom that belongs to ur country
2.search for the *.ops file for ur I9000
3. look out for a flashing guid for ur phone ( you will find it here in the xda)
4. reflash the stock rom and test if ur problems still there
Reply to me if it worked or not
Hi
http://forum.xda-developers.com/showthread.php?t=1679563
I tried to install the above ROM and kernel and followed the guide 100% and the video. After i installed the JELLYBLASTV3.signed.zip
via CWM everything went ok. When i did the reboot in CWM it displayed about 4 error messages and
on reboot the phone got stuck on the first logo screen and that is it. Nothing else will work and recovery mode also not working.
Got the phone exchanged and can you tell me what want wrong as i dont want it to happen to the new phone..
Also how do i remove the a2sd or data2sd feature as in the guide, there was no 2nd partition and 1 have formated the memory card.
also the phone is showing "Move to SD card" put it is grayed out on all the apps, do i need to remove this ?
Thanks for the help in advance.
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
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.
I flashed the TWRP recovery compatible with treble from the Screwd ROM thread because I was having a problem with the normal TWRP (that is it didn't show the date or hour correctly even if I changed them).
I flashed it using flashify, I went to recovery to see if everything was ok, it was so I rebooted. But after the reboot I noticed that my SD (exFAT) was shown as "corrupted" even though it was working perfectly fine before I flashed the recovery. I tried flashing the normal TWRP again from both, the app and the recovery itself but it didn't solve the problem.
I even clean flashed the ROM I was using but no luck. What it's weird is that both recoveries recognized my SD card. Also, the ROM recognizes other SD card (exFAT) but not the original I was using.
Does anyone know how to fix this? Please help.
You really shouldn't use apps to flash stuff. Only use TWRP. Recovery apps cause more problems than anything.
Take the card out, format it on your PC, boot into system and set it up again. Hopefully it's not completely dead, but I've heard plenty of stories of Android phones corrupting SD cards randomly. That's probably why no Google phones come with SD card slots--SD cards are unreliable even as portable media storage.