Related
I've been stuck in a weird place for some time with my phone. After I installed clockwork mod, backed up, installed some flavour of FroYo, and made the mistake of trying to flash back my old back up without properly wiping things have been getting weird. I can use ODIN to flash fresh ROMs, but I always get a bunch of FCs at startup, and most apps don't work. I tried to do all kinds of tricks to completely wipe the internal SD, but there is always some remnants of old fun hanging about causing cascading errors and FCs. No matter what I try to do, MyBackupPro and Rommanager is always present, but not working.
How I can completely rid myself of anything not stock ROM?
I've finally gotten back to root ADB, after a long and hard battle. I believe this may hold the key to salvation for my Vibrant.
Any and all suggestions are much appreciated!
Things I've already tried:
EUGENE373_SamsungS_Froyo_PDA -> Stock 2.1 T959UVJFD
EUGENE373_SamsungS_Froyo_PDA -> battery pull -> Stock 2.1 T959UVJFD
Stock 2.1 T959UVJFD -> EUGENE373_SamsungS_Froyo_PDA
Bionix1.9.zip - would not install due to some error I can't recall right now. Will update.
Factory wipe - from Settings menu
Wipe in Clockworkmod menu
Wipe all in adb shell
The weird *2767*3855#* factory wipe
UPDATE:
Strangest thing happened: I flashed an old ROM back onto the phone with Odin 1.52, then the Updated Stock 2.1 also via Odin the usual FC-ing was still there. Then I rebooted into recovery, reinstalled the Clockworkmod recovery menu, installed the root-update.zip in order to have root shell access. Then I pushed VibrantDeodexed1_2.zip and Vibrantfroyo_R3.zip on to the sd card. I tried to apply the VibrantDeodexed1_2.zip, but it aborted due to some catalog not present. However, I did notice that the installation erased /system and deleted some files, and I had the notion to try and install the VibrantFroyo_R3.zip. The installation succeeded, and Lo and Behold!
the phone has returned to the land of the living! Wohoo!!
I do not fully understand how this can be, but there is no Force Closing of programs any longer. What a relief!
Thanks to everybody who contributed ideas!
If you're having problems, back up whatever data you want to keep to your computer. Go download eugenes 2.2 that doesn't brick. Flash that, do a battery pull once it's done (don't reboot). Then go get a stock eclair file, flash that with odin and check repartition. This solved every problem I had from flashing way too many roms.
Yea, when in doubt I thank the deities for Eugene and flash his "Froyo that doesn't brick" followed by the stock JFD firmware.
Sent from my SGH-T959 using XDA App
brnagndan said:
If you're having problems, back up whatever data you want to keep to your computer. Go download eugenes 2.2 that doesn't brick. Flash that, do a battery pull once it's done (don't reboot). Then go get a stock eclair file, flash that with odin and check repartition. This solved every problem I had from flashing way too many roms.
Click to expand...
Click to collapse
Sorry to say, that trying this solved nothing. Just the same as before.
ullrotta said:
Sorry to say, that trying this solved nothing. Just the same as before.
Click to expand...
Click to collapse
You clicked the "repartition" option? That should format your internal sd...
I7oobie said:
You clicked the "repartition" option? That should format your internal sd...
Click to expand...
Click to collapse
Yeah, that's the weird part.. It doesn't really delete anything. Files are still there, and so are the un-wanted system files, too.
Does anyone know if I can manually partition the sdcard?
Had a similar issue, and couldn't fully erase my files. Figured out how to completely erase everything, before you proceed, backup your files and be ready to Odin. In rom manager, enable advanced mode in settings, then use the flash alternate recovery option. That set my current cwm version to 2.5.1.2, now when I reboot to cwm i have a menu that says something similar to "sd and storage" and within that menu are options to completely format all of the internal storage. Be careful in there, you can delete everything, incl the sd ext, but I think this is what you are looking for.
Edited - I rebooted and checked the menus, mounts and storage in cwm is what you are looking for after flashing the alternate recovery, I can confirm this removes remnants that an Odin repartition or factory format still leaves behind, let me reiterate, backup your personal files, cause this does remove everything
After formatting, Odin away
Sent from my T959 running Bionix1.91 with Jacs OC/UV and Voodoo
same thing happened to me >.> I just formatted the SD card on the phone. then flashed whatever rom I wanted.
Br1cK'd said:
Had a similar issue, and couldn't fully erase my files. Figured out how to completely erase everything, before you proceed, backup your files and be ready to Odin. In rom manager, enable advanced mode in settings, then use the flash alternate recovery option. That set my current cwm version to 2.5.1.2, now when I reboot to cwm i have a menu that says something similar to "sd and storage" and within that menu are options to completely format all of the internal storage. Be careful in there, you can delete everything, incl the sd ext, but I think this is what you are looking for.
Edited - I rebooted and checked the menus, mounts and storage in cwm is what you are looking for after flashing the alternate recovery, I can confirm this removes remnants that an Odin repartition or factory format still leaves behind, let me reiterate, backup your personal files, cause this does remove everything
After formatting, Odin away
Sent from my T959 running Bionix1.91 with Jacs OC/UV and Voodoo
Click to expand...
Click to collapse
When I boot into recovery, I always have to reinstall packages to get to the CWM recovery menu. I tried to clear everything from the mounts and storage submenu; I cleared system, cache and data, then flashed stock eclair. STILL the same applications and files sit on the internal SD.
When performing the wiping, all looks normal. It does take a little time, and the system reports that all is going according to plan, yet no files are deleted.
What can possibly make the phone act this way? Are there no super secret samsung-technician codes that allow me to completely wipe clean the face of the sdcard?
When you get into the storage and mounts menu, I would format everything given what you're experiencing. Format boot, data, system, cache, and sdcard. Dont format the sd ext, thats the physical card. After formatting all of those your phone should be an odin ready blank slate, mine was. Hope this helps.
Sent from my T959 running Bionix1.9 with Jacs OC/UV and Voodoo
this has to be one of the most useful threads. just last night i was messing with rom manager and enabled advanced settings, BEEFORE reading this thread. I've done so much monkeying, but didn't keep a journal or log, so ive got **** from so many hacks and tweaks (mods and themes)...
thanks, im gonna wipe this ****er clean.
Good Info..but moved to Q&A
Br1cK'd said:
When you get into the storage and mounts menu, I would format everything given what you're experiencing. Format boot, data, system, cache, and sdcard. Dont format the sd ext, thats the physical card. After formatting all of those your phone should be an odin ready blank slate, mine was. Hope this helps.
Sent from my T959 running Bionix1.9 with Jacs OC/UV and Voodoo
Click to expand...
Click to collapse
This is exactly what I tried yesterday. I'll try it again a few times to see if I can find a way.
ullrotta said:
This is exactly what I tried yesterday. I'll try it again a few times to see if I can find a way.
Click to expand...
Click to collapse
I was hoping that would help you friend, that process wiped mine clean of all remnants. Good luck in getting her back into a functional state.
After reading som more, contacting Samsung Service, I've decided to send the phone in for service. [sigh]
I've learnt a lot about ADB, pushing and pulling files, rooting, unrooting, swapping ROMS and whatnot. Still, the phone is stuck in that weird place where I cannot delete files.
Hopefully the service team can fix this poor, misguided phone
Hello XDA,
I am a noob to the forum, but not to rooting my peripherals. I just came from an HTC Inc 2 that I previously had just DevUnlocked via HTC, then went full root with S-off via tacoroot method. I since have retired the phone and now have a DInc 4G LTE verizon. I have just used the FakeCID script method to gain bootloader unlock. I now have superuser installed and TWRP as the recovery. The question I have is relating to ROM installation. I have tried to install both ViperLTE and PizzutoClaws ROM's with no luck. I erase every thing 3x as stated in various posts as well as factory reset and system erase. When installing the ROM's, the aroma installer boots up and does the usual walk through, but at the end of the selections to install right after the selection for 'dirty wipe or full wipe' the aroma installer shows it's wiping the cache and such for a few seconds then immediately goes right to the 'Installation complete' screen. There should be some wait time and a loading bar showing the rom is loading. Both ROM's are doing this and thus the ROM is not installed. Is it possible I have an issue with the bootloader unlock? I have since reverted back to the stock ROM still at ****TAMPERED**** ****UNLOCKED**** with super user. I really would like to install a new ROM and could use some guidance. Thanks.
rudyo78427 said:
Hello XDA,
I am a noob to the forum, but not to rooting my peripherals. I just came from an HTC Inc 2 that I previously had just DevUnlocked via HTC, then went full root with S-off via tacoroot method. I since have retired the phone and now have a DInc 4G LTE verizon. I have just used the FakeCID script method to gain bootloader unlock. I now have superuser installed and TWRP as the recovery. The question I have is relating to ROM installation. I have tried to install both ViperLTE and PizzutoClaws ROM's with no luck. I erase every thing 3x as stated in various posts as well as factory reset and system erase. When installing the ROM's, the aroma installer boots up and does the usual walk through, but at the end of the selections to install right after the selection for 'dirty wipe or full wipe' the aroma installer shows it's wiping the cache and such for a few seconds then immediately goes right to the 'Installation complete' screen. There should be some wait time and a loading bar showing the rom is loading. Both ROM's are doing this and thus the ROM is not installed. Is it possible I have an issue with the bootloader unlock? I have since reverted back to the stock ROM still at ****TAMPERED**** ****UNLOCKED**** with super user. I really would like to install a new ROM and could use some guidance. Thanks.
Click to expand...
Click to collapse
are you flashing the boot.img via adb this is required if you are not s-off.
also check the zip on the sdcard and make sure you don't have (2)zips on it, make sure the rom zip is not in any other folder on card, must be at the root of the sdcard
also, you need to be on software 2.17.605.2-which I assume you are to be unlocked
Aldo101t said:
are you flashing the boot.img via adb this is required if you are not s-off.
also check the zip on the sdcard and make sure you don't have (2)zips on it, make sure the rom zip is not in any other folder on card, must be at the root of the sdcard
Click to expand...
Click to collapse
Thanks for the response. I have verified both ROM files are just .zip files. I even did MD5 check sum and the files are matching. I have placed them on the root of the SD card. I did notice however that when I am in ES file explorer the directory shows /sdcard/ with files that look similar to the root of the SD card, but then there is also ext_sd and when I select that, it lists the files I loaded on the SD card. I load the files via SD reader and not through the phone. Is it possible I could move the ROM over to the sdcard/ directory or should it be on the ext_sd. This Inc4g storage allocation is different than the DInc2....confusing.
rudyo78427 said:
Thanks for the response. I have verified both ROM files are just .zip files. I even did MD5 check sum and the files are matching. I have placed them on the root of the SD card. I did notice however that when I am in ES file explorer the directory shows /sdcard/ with files that look similar to the root of the SD card, but then there is also ext_sd and when I select that, it lists the files I loaded on the SD card. I load the files via SD reader and not through the phone. Is it possible I could move the ROM over to the sdcard/ directory or should it be on the ext_sd. This Inc4g storage allocation is different than the DInc2....confusing.
Click to expand...
Click to collapse
yes the zip needs to be on ext-sdcard not the internal card.
rudyo78427 said:
Thanks for the response. I have verified both ROM files are just .zip files. I even did MD5 check sum and the files are matching. I have placed them on the root of the SD card. I did notice however that when I am in ES file explorer the directory shows /sdcard/ with files that look similar to the root of the SD card, but then there is also ext_sd and when I select that, it lists the files I loaded on the SD card. I load the files via SD reader and not through the phone. Is it possible I could move the ROM over to the sdcard/ directory or should it be on the ext_sd. This Inc4g storage allocation is different than the DInc2....confusing.
Click to expand...
Click to collapse
Forgot to mention that I have also tried to flash the boot.img files via fastboot. this is normal practice for HTC phone with unlocked bootloader only if I am not mistaken. I pull the boot.img file from the ROM zip. a quick note though, I noticed when doing the flash for the recovery or boot image, in the bootloader screen, the right side load bar show's up green as it's loading, but right after the bar is highlighted red and will show a quarter of red bar for a brief second. I noticed too that the twrp recovery will not load all the time. sometimes I have to pull the battery and retry.
rudyo78427 said:
Forgot to mention that I have also tried to flash the boot.img files via fastboot. this is normal practice for HTC phone with unlocked bootloader only if I am not mistaken. I pull the boot.img file from the ROM zip. a quick note though, I noticed when doing the flash for the recovery or boot image, in the bootloader screen, the right side load bar show's up green as it's loading, but right after the bar is highlighted red and will show a quarter of red bar for a brief second. I noticed too that the twrp recovery will not load all the time. sometimes I have to pull the battery and retry.
Click to expand...
Click to collapse
what version of twrp are you using-the is an official twrp 2.4.3 now
http://techerrata.com/file/twrp2/fireball/openrecovery-twrp-2.4.3.0-fireball.img
Aldo101t said:
what version of twrp are you using-the is an official twrp 2.4.3 now
I initially used the 2.4.3.0 version. after the initial issues, I went to twrp site and downloaded the latest 2.4.4 and still having the same issues. Another note, I noticed on the ROM installation instructions on either rom, there is no mention of the System-erase button use. This is the one that erases the current ROM. I tried just factory reset 3x, cache erase 3x and delvik cache 3x with out doing the system erase. flash the rom going through the aroma installer, then flashing the boot img. the phone will boot back into the stock ROM. I'm still wondering why the aroma installer says the rom loaded so quickly after doing the full wipe 4xt format with out showing any load progress. On the Inc2 I had, I switched rom's regularly with no issues and the ones that used aroma installer, has some wait time to load the rom files. I guess I will try a full format on the SD card and just load the rom zips to see if that does anything. Thanks again for the replies. Much appreciated.:good:
Click to expand...
Click to collapse
rudyo78427 said:
Aldo101t said:
what version of twrp are you using-the is an official twrp 2.4.3 now
I initially used the 2.4.3.0 version. after the initial issues, I went to twrp site and downloaded the latest 2.4.4 and still having the same issues. Another note, I noticed on the ROM installation instructions on either rom, there is no mention of the System-erase button use. This is the one that erases the current ROM. I tried just factory reset 3x, cache erase 3x and delvik cache 3x with out doing the system erase. flash the rom going through the aroma installer, then flashing the boot img. the phone will boot back into the stock ROM. I'm still wondering why the aroma installer says the rom loaded so quickly after doing the full wipe 4xt format with out showing any load progress. On the Inc2 I had, I switched rom's regularly with no issues and the ones that used aroma installer, has some wait time to load the rom files. I guess I will try a full format on the SD card and just load the rom zips to see if that does anything. Thanks again for the replies. Much appreciated.:good:
Click to expand...
Click to collapse
there is an option under wipe for system.
---------- Post added at 01:16 PM ---------- Previous post was at 01:10 PM ----------
Aldo101t said:
rudyo78427 said:
there is an option under wipe for system.
Click to expand...
Click to collapse
you should wipe data/factory reset--wipe cache--wipe dalvic--wipe system then install rom
Click to expand...
Click to collapse
Click to expand...
Click to collapse
rudyo78427 said:
...I have tried to install both ViperLTE and PizzutoClaws ROM's with no luck. I erase every thing 3x as stated in various posts as well as factory reset and system erase. When installing the ROM's, the aroma installer boots up and does the usual walk through, but at the end of the selections to install right after the selection for 'dirty wipe or full wipe' the aroma installer shows it's wiping the cache and such for a few seconds then immediately goes right to the 'Installation complete' screen...
Click to expand...
Click to collapse
I had this exact same problem when using TWRP 2.4.3.0. I re-flashed my phone with TWRP 2.3.3.0 and my ROMS installed without any issues.
Atomic83 said:
I had this exact same problem when using TWRP 2.4.3.0. I re-flashed my phone with TWRP 2.3.3.0 and my ROMS installed without any issues.
Click to expand...
Click to collapse
Thanks for the suggestion. That was my other consideration, to go with a lower rev recovery. I will try that and see if it works. :good:
Success!!!
rudyo78427 said:
Thanks for the suggestion. That was my other consideration, to go with a lower rev recovery. I will try that and see if it works. :good:
Click to expand...
Click to collapse
Success!!!!! Thanks for the last tip to try a lower recovery version. Seems TWRP 2.4 on up didn't work allowing the Aroma Installer to complete installation. I have downgraded to twrp version 2.3.3.0 and the ROM's flash now. Thank you XDA community!!! :laugh:
rudyo78427 said:
... I erase every thing 3x as stated in various posts ....
Click to expand...
Click to collapse
A discussion about this starts here and continues for a couple pages.
The 2.4.x series TWRP recoveries have been working fine to install Sense based ROMs with Aroma installers for numerous individuals. You should only need to: Wipe > Factory Reset (this takes care of all types of cache as well) and Wipe > System. As mentioned before, ensure the zip file you're installing is on the external storage. In TWRP, at the install screen, toggle the radio button back and forth between Internal Storage and External Storage to make sure you are reading the zip from the external storage (I've seen the file list show the wrong contents before until it is toggled).
Edit: TWRP 2.4.3.0 and newer seem to have trouble with Aroma
mdmower said:
A discussion about this starts here and continues for a couple pages.
The 2.4.x series TWRP recoveries have been working fine to install Sense based ROMs with Aroma installers for numerous individuals. You should only need to: Wipe > Factory Reset (this takes care of all types of cache as well) and Wipe > System. As mentioned before, ensure the zip file you're installing is on the external storage. In TWRP, at the install screen, toggle the radio button back and forth between Internal Storage and External Storage to make sure you are reading the zip from the external storage (I've seen the file list show the wrong contents before until it is toggled).
Click to expand...
Click to collapse
Thanks for the feedback, mdmower. I had done a complete format of my sd card on the comp and loaded only the zip file on the card. I also had done 3x factory wipe/reset, 3x cache delete and 3x delvik cache wipe. All of my attempts at getting the ROMS to load failed. The aroma installer would go through the setup, but when it executed the actual writing/flashing of the files, it wouldn't finish. The program stated that the zip file was 'Installed successfully, but no OS was actually loaded(stuck at white HTC boot screen). I tried this with different twrp recoveries. It wasn't until I used twrp version 2.3.3.0 that the ROM's load successfully. I have since flashed Pizzuto claw's and now running ViperLTE. I am thinking of going with CM10.1 now, but not sure of the latest nightly release. Waiting for a stable release. Question, noticed your device list shows your using CM10.1. How is it working for you? any real bugs? I need sim card support as i travel overseas and have different sim cards for the various regions I visit. :good:
rudyo78427 said:
I also had done 3x factory wipe/reset, 3x cache delete and 3x delvik cache wipe.
Click to expand...
Click to collapse
First thing, drop this habit. A single factory reset will suffice.
rudyo78427 said:
All of my attempts at getting the ROMS to load failed. The aroma installer would go through the setup, but when it executed the actual writing/flashing of the files, it wouldn't finish. The program stated that the zip file was 'Installed successfully, but no OS was actually loaded(stuck at white HTC boot screen). I tried this with different twrp recoveries. It wasn't until I used twrp version 2.3.3.0 that the ROM's load successfully.
Click to expand...
Click to collapse
Issues with aroma and TWRP versions 2.4.3.0 and greater have been confirmed (possibly other 2.4.x releases). The folks behind TWRP suspect a problem with make_ext4fs, but it is unclear whether the blame lies within TWRP, the update_binary, or the particular make_ext4fs called by Aroma.
rudyo78427 said:
I am thinking of going with CM10.1 now, but not sure of the latest nightly release. Waiting for a stable release. Question, noticed your device list shows your using CM10.1. How is it working for you? any real bugs? I need sim card support as i travel overseas and have different sim cards for the various regions I visit. :good:
Click to expand...
Click to collapse
Read the first post in the CM thread. Others have successfully used CM outside the U.S.
Hi, i'm new at the forums, but this have been my first option for android related solutions and info for a long time ago, but i finally decided to join it.
Well, this is embarrasing, but my first post it's about a problem in my pretty new SGS3 GT-i9300 i got a couple of weeks ago.
The problem is..., well, i've been testing some roms as 2nd roms with the help of the Siyah kernel. I've done the basics things..., root my phone, install my first kernel (siyah...), killed the stock rom so i learned how to flash a new stock rom for my country without all the operator's junk, then i overclocked (just a bit only), then i started with the 2nd roms....
My first try was UltimaROM, pretty good but i wanted to test MIUI, no problem, i worked but i didn't like it completely since it deleted all the samsung goodies, so i tried to flash ihackers, no luck..., it wouldn't just boot. So i tried with FoxHound, the same thing. So just dissapointed, i came back to UltimaROM and installed it again as 2nd rom (all in just 2 days). Well, it worked ok but then i noticed a serious problem...
Since the last time, when i flashed UltimaROM with the 2nd Rom Utils from Siyah, i came back to the stock rom (1st rom) because i wanted to record the fireworks outside my home (because of new year ), but, the camera said "Error al grabar" and just closed..., then i remember a couple of random massages saying that i was running out of space in the internal memory, so i dicided to temporarily delete the 2nd rom (i've been so gross these two days...), and..., according to the 2nd rom utils from siyah, the 2nd rom was succesfely removed, but just to be sure, i fixed permissions (i did this everytime i tried to flash a new 2nd rom).
Now back to the stock rom, the camera problem not being able to record to the internal memory still there, but now, i looked into the internal memory with root explorer and there is a big folder named "ADM" with a...¡¿copy?! of the UltimaROM zip, which weights 1.5Gb, and i can't delete it, EVEN WORSE!, now a lot of random files and folders in the internal memory are "locked", i can't delete any of these, or even change permissions (my DCIM folder for example). I then tried the CWM option to "fix permissions", on the main CWM recovery as well as in the siyah 2nd rom utils recovery..., but all the same
Thinking that the internal memory file system got corrupted, i though that my best option was to flash the stock rom from samsung again, but this time with the option "Re-partition" checked. I tried it in Odin but...damn it..., it won't make it!, however, i can soft-flash the stock rom without "re-partition" check..., but this doesn't fix the internal memory...
In short, i CAN boot into my main stock rom, i can FLASH the stock rom trough Odin but i can't if i check the Re-partition option, and until i get i fix for the internal memory, i'll have to use my 2Gb External SD Card.....
So..., what can i do? Is there anything i can do to safely format the internal emmc completely and then flash the stock rom again? Or maybe do i have to...assume...that the locked internal memory problem...is a hardware problem? That's what i'm afraid of...
Anyway, i'll leave the details here.
OS: Stock Rom Samsung JB 4.1.2 (I9300UBEMH2_I9300UVOEMH1_ARO)
Kernel: Siyah Kernel 1.9.1
Recovery: CWM-based Recovery v5.5.0.4 CF-v1.5
I would leave a dump file of the failing Odin process now, but i don't know if that is possible and neither how to do it. But he most i can give is a screenshot attached.
Thanks in advance!
P.D.: let me know if this post is on the wrong place inside the forum
alpha-ro said:
Hi, i'm new at the forums, but this have been my first option for android related solutions and info for a long time ago, but i finally decided to join it.
Well, this is embarrasing, but my first post it's about a problem in my pretty new SGS3 GT-i9300 i got a couple of weeks ago.
The problem is..., well, i've been testing some roms as 2nd roms with the help of the Siyah kernel. I've done the basics things..., root my phone, install my first kernel (siyah...), killed the stock rom so i learned how to flash a new stock rom for my country without all the operator's junk, then i overclocked (just a bit only), then i started with the 2nd roms....
My first try was UltimaROM, pretty good but i wanted to test MIUI, no problem, i worked but i didn't like it completely since it deleted all the samsung goodies, so i tried to flash ihackers, no luck..., it wouldn't just boot. So i tried with FoxHound, the same thing. So just dissapointed, i came back to UltimaROM and installed it again as 2nd rom (all in just 2 days). Well, it worked ok but then i noticed a serious problem...
Since the last time, when i flashed UltimaROM with the 2nd Rom Utils from Siyah, i came back to the stock rom (1st rom) because i wanted to record the fireworks outside my home (because of new year ), but, the camera said "Error al grabar" and just closed..., then i remember a couple of random massages saying that i was running out of space in the internal memory, so i dicided to temporarily delete the 2nd rom (i've been so gross these two days...), and..., according to the 2nd rom utils from siyah, the 2nd rom was succesfely removed, but just to be sure, i fixed permissions (i did this everytime i tried to flash a new 2nd rom).
Now back to the stock rom, the camera problem not being able to record to the internal memory still there, but now, i looked into the internal memory with root explorer and there is a big folder named "ADM" with a...¡¿copy?! of the UltimaROM zip, which weights 1.5Gb, and i can't delete it, EVEN WORSE!, now a lot of random files and folders in the internal memory are "locked", i can't delete any of these, or even change permissions (my DCIM folder for example). I then tried the CWM option to "fix permissions", on the main CWM recovery as well as in the siyah 2nd rom utils recovery..., but all the same
Thinking that the internal memory file system got corrupted, i though that my best option was to flash the stock rom from samsung again, but this time with the option "Re-partition" checked. I tried it in Odin but...damn it..., it won't make it!, however, i can soft-flash the stock rom without "re-partition" check..., but this doesn't fix the internal memory...
In short, i CAN boot into my main stock rom, i can FLASH the stock rom trough Odin but i can't if i check the Re-partition option, and until i get i fix for the internal memory, i'll have to use my 2Gb External SD Card.....
So..., what can i do? Is there anything i can do to safely format the internal emmc completely and then flash the stock rom again? Or maybe do i have to...assume...that the locked internal memory problem...is a hardware problem? That's what i'm afraid of...
Anyway, i'll leave the details here.
OS: Stock Rom Samsung JB 4.1.2 (I9300UBEMH2_I9300UVOEMH1_ARO)
Kernel: Siyah Kernel 1.9.1
Recovery: CWM-based Recovery v5.5.0.4 CF-v1.5
I would leave a dump file of the failing Odin process now, but i don't know if that is possible and neither how to do it. But he most i can give is a screenshot attached.
Thanks in advance!
P.D.: let me know if this post is on the wrong place inside the forum
Click to expand...
Click to collapse
Use es file explorer and click on root manager. And click mount r/w. Make sure both is rw.
Sent from my GT-I9300 using xda app-developers app
Give a thank if I helped you
JellyYogurt said:
Use es file explorer and click on root manager. And click mount r/w. Make sure both is rw.
Sent from my GT-I9300 using xda app-developers app
Give a thank if I helped you
Click to expand...
Click to collapse
Thanks JellyYogurt, Yeah, i tried it as one of my first options, even with root permissions
Now, i'm really REALLY consufed...maybe, can Android get stuck for periods and lock access to some files? because after a while, i came back to take a screenshot in windows showing me a "Read-Only" mode error when trying to delete those damn files, at least, that's what said to me before, because now i connected in MTP as usual and the things i tried to delete with error earlier are...gone? I don't get it yet, and i'm hope it won't happen again, maybe tomorrow i'll try reflashing again
If the problem happens to vanish, i'll let you know so u can delete this post, just give a couple of days, i want to make sure i can make a full reflash with repartitioning in case of future emergencies
Thanks again! Really
Well, it looks like the MTP lied to me, i checked inside /sdcard/ again and the locked files still there and locked :/, i tried again mounting as R/W with no luck. When i try to take a screenshot with power + home, it says that the usb storage could be ON...this is weird, i double check my usb mass storage app and swtich to usb mass storage mode and then back to mtp (i know it's only for the extSdCard...but i don't know what else can i do)
Any ideas plz? Thanks again
Sent from my GT-I9300 using xda app-developers app
alpha-ro said:
Well, it looks like the MTP lied to me, i checked inside /sdcard/ again and the locked files still there and locked :/, i tried again mounting as R/W with no luck. When i try to take a screenshot with power + home, it says that the usb storage could be ON...this is weird, i double check my usb mass storage app and swtich to usb mass storage mode and then back to mtp (i know it's only for the extSdCard...but i don't know what else can i do)
Any ideas plz? Thanks again
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Have u tried a factory reset? Copy paste all ur pics and data to the computer first as u seem to be able to do so.
Well, i tried and tried and let me say this an awful way to begin the year :crying:
I tried using doing the factory reset from within CWM and apparently all was succesful, but again in android, the internal /sdcard/ still the same, it didn't delete anything that my settings!
Now i can't avoid being a bit desperate, is there any way to format the internal /sdcard/ (or /sdcard0/, whatever) so i can start from scratch again? In fact i don't have anything useful in there, 'cause i made a full backup 4 days ago before this problem even appeared. Now i would just be fine if i could format the internal /sdcard/, just that..., i tried the "format /sdcard" option from within CWM...but it formatted the external sdcard, what a mess
I'll be waiting, thanks again!
Use philz recovery instead, format internal sd card, wipe for new rom.
Sent from my GT-I9300 using Tapatalk
You are just a master! I tried flashing a Philz recovery via Odin and, like you told me, i formatted the internal /sdcard/, then without exitting the recovery, i check inside the sdcard with the "install zip" option, and it says "No files found", i would never have imagined how beautiful would those words look .
Now, just to make sure, i would like to repartition with odin, and (at least for now) come back to my stock rom, but the problem i mentioned earlier about "can't open file" when i tried to repartition, was because i missed the .pit file hehe
So i searched for the .pit file for the S3 16GB edition and i found it, in the corresponding forum, they said that the .pit file ending in 329 worked good for all of them.
Now with all in hand, i powered on in Download mode, opened Odin v3 once more, selected Re-partition, choosed the .pit file (ending in 329) and the stock rom .md5, flashed, waited 10min and..., no errors, until i saw the "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" problem, so i flashed again the Philz Touch recovery over the stock one (because when i tried to access the stock recovery the error always appeared), so fine! I booted into Philz and wiped cache, data and...it's so beautiful...:crying:, Android finally started! As if it were just when i bought the S3
So, i fixed it finally! I think the only thing that remains is to reset the counter with TriangleAway and get back my last backup
Thank you so much friend! At the end, i'll stay with Philz Recovery, i didn't know it before but is far better than CWM. Thanks again!
P.D.: now that i know how to unbrick completely, i'll tell my journey to my friend Dany
I have an S3 (i9300), and in recovery (TWRP 2.8.6.1) It will give me errors that it can't open folders in the data partition, so Aroma installer roms cannot format data, and I get a long error every time i data reset.
Data/misc/audit is unopenable (can't see it in file explorer in system, but i can see the folder in recovery)
Data/data/com.samsung.dcm - a folder in there is unopenable, is named as a tilted square with a "?"in ES.
Ashab7013 said:
I have an S3 (i9300), and in recovery (TWRP 2.8.6.1) It will give me errors that it can't open folders in the data partition, so Aroma installer roms cannot format data, and I get a long error every time i data reset.
Data/misc/audit is unopenable (can't see it in file explorer in system, but i can see the folder in recovery)
Data/data/com.samsung.dcm - a folder in there is unopenable, is named as a tilted square with a "?"in ES.
Click to expand...
Click to collapse
For anyone still with this problem, the solution is to reformat and repair any faulty partitions in the advanced wipe menu in TWRP.
I am having this problem with an S3 that I'm trying to restore to stock. I can get TWRP on the phone but no image will install nor saved backups will restore. The reason is the data partition is corrupt. When I try using the Advanced Wipe option to repair the partition it reports:
/sbin/e2fsck -fp /dev/block/mmcblk0p15 process ended with ERROR: 4
Unable to repair Data.
Click to expand...
Click to collapse
Any other thoughts on how to repair the data partition? It was just working before trying to restore to stock, so I doubt it is a hardware problem.
For those facing the same problem. I did fix this but I can't tell you exactly what did it. I used the Terminal in TWRP to repair the partition manually. I think I used "e2fsck -cvf /dev/block/mmcblk0p15" and accepted all repairs. Be sure to say "no" to the first question that recommends you to stop. Then I used TWRP to format the partition and then it mounted just fine. I did many repairs on the partition using e2fsck and not all of them worked so I'm not 100% positive I know which options did it. I think it was "-cvf" but maybe "-B" also played a role. Either way, you gotta get that partition repaired before it will format and then mount.
Maybe flashing a stock ROM, with or without a pit file, would also work?
audit13 said:
Maybe flashing a stock ROM, with or without a pit file, would also work?
Click to expand...
Click to collapse
I tried that. That's what led to my /data partition being corrupted. I tried Kies 2.0 and stock ROMs with Odin. I couldn't get beyond the corrupt file system. I even got to the point where download mode was complaining to me about things being jacked. I thought I bricked the thing for a while.
Did you try flashing a stock ROM with Odin? Kies can't be used to flash a stock ROM unless you use the emergency recovery option.
scottlindner said:
For those facing the same problem. I did fix this but I can't tell you exactly what did it. I used the Terminal in TWRP to repair the partition manually. I think I used "e2fsck -cvf /dev/block/mmcblk0p15" and accepted all repairs. Be sure to say "no" to the first question that recommends you to stop. Then I used TWRP to format the partition and then it mounted just fine. I did many repairs on the partition using e2fsck and not all of them worked so I'm not 100% positive I know which options did it. I think it was "-cvf" but maybe "-B" also played a role. Either way, you gotta get that partition repaired before it will format and then mount.
Click to expand...
Click to collapse
thanx scottlindner actually "-cvf" is work.
thank you allot:good:
Little bit of history. Stumbled into CM13 and android 6 via a "Nightly" download. So hadn't read up on it beforehand!
So chickened out and went back to CM12.1 and android 5.1.1.
I got so fed up running out of memory when reinstalling all my Apps so looked into increasing the partion size .
The thread I followed , by gsstudios, indicated I needed to have the pit file and the recovery file in at the same time.
That bit worked for me.
I could not get Iso Rec or TWRP to load up on my phone via Odin so I am stuck with CWM 6.0.5.1.
I am able to get into Recovery with CWM, clear all the caches, select a 12.1 zip file and confirm install. Next the android comes up briefly with some text, a couple of lines that disappear too quickly for me to see and it drops back into the CWM menu.
I have installed the files "emmc" , on my SD card, to check for "bricks" in the memory, again they take me straight back into the CWM menu so I have no idea if they have run correctly?
I have an identical phone, Samsung GTi9100 intl, running CM12.1 and android 5.1.1, just trhe sd card a different size,
so if anyone has an idea how to clone this onto my sick phone and get it working, "I'm yer friend for life"!!
Just referring back to when I briefly had Cyanogen Recovery on my phone when it failed to do something in recovery I could not read the writing that came with it so no use to me!
Volume Two
During one of my tries to flash a zip file from my SD01 card whilst using CWM, the error I was able to read said "something" like unable to load this file " you need TWRP Recovery".
So first lesson learnt, do as you are told!
So after a lot of searching and reading through the threads I found this one worked for me Via Odin.
AOSP.LP-Kernel+_25-08-2015.TWRP-2.8.7.0 tar. Sorry to the "Author" can't remember where I got it from but you know who you are and thanks. It may have not been an exact "Fit" but it got me TWRP on my phone!
An observation whilst using "Odin", a few of the posts seem to indicate it can be a bit "Flakey". I was using version 3.10.7 in the end and adopted the method of removing the battery and the USB lead after any error, bringing up "Odin Mode" on the phone again, starting the program in supervisor mode on the PC and reloading the files again.
I suspect if I had followed this method in the first place a few more "ideal" kernels would have worked for me!
So that's a second lesson.
Now I have a working TWRP. So I go into TWRP, (don't see many People using it on Youtube?), and the"Wipe" button gives me the basic wipe of the caches but I see some errors occuring, so I run it again and it shows just one error. So I go for broke a try and install a Zip file, it fails. So I look at the "in depth" wipe that shows up a heap of registers you can select so I select the lot and eventually I get a clean result but i've managed to wipe my SD card 01 with all my Zips on it.
I enabled USB storage in TWRP and was able to view my SD card 01 on my PC .So I tried to reload a Zip file to it "not enough storage"! Only 36 MB of a 15 GB SD card available?? Tried a Format of the SD card 01 from the PC that didn't help, although through the PC "Disk Manager" I could see the full 15GB.
So I formatted it in TWRP and that solved it I was able to reload my Zip files. After a "Careful" "Wipe" I was able to load a CM13.0-20160209-NIGHTLY-i9100 and BaNkS-Dynamic-GApps-6.x.x-10-20-15.
pa-gapps mod pico 5.0.1-20150221 came up with an error when I tried to load it.
I have read in one of the threads that later "Nightly's" have some problems?? I am having problems with MD5 failures indicated after the download finishes so perhaps I've been lucky?
If I look I'm sure there's and better GApps recommended out there.
When the Cyanogenmod loads it gives an option to use "Google Settings" to download your apps and settings, so as I had an identical phone I thought this was a quick way to get my apps loaded up. According to the write up on Android 6 that feature has been "Dropped/Discontinued",Shame!!
I should point out that I used a i91001GB_6GB.pit when I loaded my Kernel that all indicated a "Pass".
I reinstalled all my Apps from my PC and did not get a "not enough memory" error but will wait until I get a few updates OTA before I call that a success.
Hope this helps some one out there that there is another "Div" out here trying to make sense of it all.
Reminds me of IBM "Maps". Who does that ring a bell with??