Cache Partiton - Galaxy Tab Q&A, Help & Troubleshooting

If someone has any suggestions that would be great. I have flashed multiple roms but never had a desire to create one so I know my way around linux/andriod. Anyways my cache partition is screwed, it wont let me format it convert it anything. The only rom I can get to run on the tab is spacemooses gingerbread which clears everything on reboot. Sprint tab btw.

Have you tried going back to original stock? Do an Odin or Heimdall flash for EA24, and it should wipe everything out and get you back to normal.

yeap tried that and DJ30 both boot loop before even getting to the first sprint screen.

if you've tried the full EA24 flash with pit file to repartition the Tab, then you probably have a hardware issue if it's still boot looping. Are you able to get into stock recovery and try to do a factory wipe, and or cache wipe?

yea i have tried that also, i haven't tried with the pit file on EA24, it was on DJ30 that i used it. Anything Gingerbread based will boot to the second samsung screen and then just hang, anything Froyo based just boot loops at the first samsung screen, Spacemooses honeycomb will boot but take about a hour. When i try to wipe data/factory reset it says cannot format cache partition in factory recovery and clockwork. Ill post here in a bit the actually message it gives me.

Related

[Q] Galaxy S Boot Screen hang meaning?

Hi all,
So after I flash a new ROM (MIUI MGv2/RC8vC/MGv1) I always hang at the Galaxy S GT-I9000 screen - the first boot screen.
I am wondering what this means? is it a corrupt file, something wrong with my internal sdcard, ROM not installed properly?
Please help,
Thanks.
some times a wipe from recovery will help and goes back to normal boot
many issues may cause this problem for instance if framework.jar or android.policy.jar or... have some bugs , will happen like that
Hi,
By wipe you mean clearing the formatting system, data, cache, dalvik cache and a factory reset? I ask this because the MIUI roms are not are non-wipe and the instructions recommend you to format those places before install (which I did).
I mean wipe cache partition from recovery. just try it and ley us know if it works
Well I just tried again but it doesn't work because I can't access recovery mode. It hangs at the Galaxy S screen and doesn't move from there so I'm wondering why because if I can't fix the bad install then I can't access the recovery mode and can only flash.
if recovery dont work BUT download mode does,
start the whole process again, flash back to stock froyo with froyo bootloader.
did you come to MIUI from Gingerbread ??
Well i've done the process like 10 times, nearly every single time from froyo (JPU,JS5,Ezbase 2.0) and I also went from 2.1 to 2.2 and then to MIUI. The other times I have tried coming from CM7 as CM7 works.
well i have a similar issue but in my case i just wiped my data thru cwm on darky v8 xxjpy..
now i get boot loops,any idea what should i do??
i know this is not exactly the thread but if i get my answer it'll save me from starting a new one..
When I got bootloops i normally reflashed. If you don't have data it will probably work?
I assume you have data as your on Dark v8 when V9 is out?
i dont understand by have data??
i flashed v9.5 but went back to v 8 few months ago..
today i just wiped/factory reset my phone using cwm and it was succesful but now its bootloops and vibrations..
i never wiped my phone before and only have flashed using cwm,never used odin for flashing roms!!
OH I see, by data i meant personal data that you might want to back up...I'm not to most knowledgeable but I know how to flash roms. I reckon you should try to flash V8 it again if you can enter recovery.

[Q] Boot loops after working/flashing normally

I keep getting the same problem with various ROM's I flash.
When a flash a ROM I first wipe everything by fastboot, superwipe or a combination of the 2, then I use the wipes in recovery, wipe my ext, and repair ext. Then I proceed to flash the ROM and applicable kernels.
First boot goes fine, and so does consecutive reboots/power offs. After about a week, at a seemingly random time, I reboot, then I get a boot loop.
The last time I got a boot loop, was after a week of using froyo by laszlo and I wiped cache, and dalvik-cache, then rebooted, and boot looped overnight.
Other times it would bootloop just after rebooting the phone (and not wiping anything).
Any tips to prevent this from happening?
Thanks (and sorry if I missed some info)
did you flash any custom mtd files? or have you tried a manual wipe of everything? i usually do the superwipe, than manual wipe in recovery.. wipe everything there is!! data, cache, dalvik cache, sd partition, battery stats and rotate... maybe even re format your sd card... not sure what it could be.. but i did have a slightly similar issue in the past but im always sooo paranoid about bricking so i just un-rooted than started again from scratch lol if you choose to do so this guide may be able to help you! http://forum.xda-developers.com/showthread.php?t=1098899
I've wiped everything through fastboot, recovery, and superwipe before flashing, and I've fully formatted and repartitioned through recovery, and I still get boot loops.
Any other ideas to fix boot loops?
HiddenShadow said:
I've wiped everything through fastboot, recovery, and superwipe before flashing, and I've fully formatted and repartitioned through recovery, and I still get boot loops.
Any other ideas to fix boot loops?
Click to expand...
Click to collapse
uhhhmmm maybe try re rooting...? maybe you just got a bad download file and it's acting screwy.. try link i recommended in first comment and feel free to ask me any questions.. im not sure what else would be ausing the problem..
Boot loops
I use to have similar problems. As for the froyo by laszlo, make sure that you have EXT4 partition.
If you still have problems, give me details about your radio and spl.
Well I tried rebooting this evening, no boot loop, but randomly I just lost all my contacts, but it did resync okay later
My radio is 2.22.28.25 and SPL is 1.33.0013d, and no I dont use a custom mtd
Heres a logcat:
http://pastebin.ca/2074938
Edit:
I used to have apps moving to sd-ext automatically, even when there was quite a bit of space on the internal, this isn't happening anymore, so maybe whatever the problem was, its now fixed. Heres what I did:
Formatted the sd card in ubuntu and made a fat32 and ext4 partition (both primary), and put the files I needed to flash while on ubuntu.
Then I flashed the orange-nbh on ezterry's 2708 radio post, rebooted.
After flashing, went into fastboot and did fastboot erase [system, userdata, cache, local, radio, recovery, boot]
Flashed radio, spl, recovery as per instructions
Flashed rom (and kernel if applicable)

Stuck at samsung logo after flashing to stock rom

Hi guys. Tried to root my Note but got stuck at samsung logo. so I went back to download mode and flashed back to N7000DXLP9 and tried a few other different stock roms as well. But I keep getting stuck at Samsung logo. Please help guys.
Simply go to recovery mode. Wipe catch / factory reset - reboot
chintamanijaipuri said:
Simply go to recovery mode. Wipe catch / factory reset - reboot
Click to expand...
Click to collapse
tried that many times but still stuck at samsung logo
any other suggestions?
Have Same Problem Brother
mee too got same problem any help would be appreciated..!
How long did you wait. I found that after installing a new rom or factory wipe that it would take up to 5 minutes to boot. It would just sit at the samsung logo with a pulsing glow for ages.
Maybe you just need to give it more time?
What tools and packages did you use?
zolakt said:
tried that many times but still stuck at samsung logo
Click to expand...
Click to collapse
Wipe cache, do a factory reset, wipe dalvik cache. If still stuck, it looks like a bad flash/kernel problem. Try flashing it again.
Finally succeed
It's work for me, I simply entered my galaxy S3 into recovery, make factory reset, wipe chache and then reboot and my S3 finally boot normally. Thank You all.
Make my thorough wipe as below when flashing a new ROM:
1) Wipe data
2) Wipe cache
3) Wipe dalvik cache
4) Format /system & /preload
5) Format internal sdcard (make sure you save anything you need before)
6) Flash ROM
7) Wipe cache again
8) Wipe dalvik cache again
9) Reboot
This way you ensure you flash your new ROM in a completely clean environment. Then when booting the new ROM, wait some time before saying it's stuck at the boot logo. As people already said, sometimes it takes a long time to display the setup screen (but should be less than 8 minutes in any case). I'm assuming you have CWM to do this; if you don't, try the equivalent in the stock recovery (but it doesn't have all these options), poweroff, boot in download mode, then flash using Odin.
ATTENTION: make sure you make the wipes using a brick-free kernel! Search the forums if you don't know what it is. If you don't, you may brick your phone. You should flash a brick-free kernel before anything, without any wipes (it can be done through Odin if you download a safe kernel in this format); then you are ready to go with the wipes and flashing a new ROM.
my j500h keeps on restarting just after displaying samsung logo. i have tried nearly everything but seem to be stuck on the same bootloop. any idea am so stressed up.

[Q] Updated to CM from Stock Need Help Restoring

I have an S5830D that I flash an CM7 rom to (APOCALYPSE-FINAL), I'm now looking at getting back to stock. I'm having trouble getting my CWM restore back. Now after doing some searching I realized I would need to flash a stock firmware version through odin. I went out and found what i believe is the correct firmware version for this Koodo model (the name is S5830DTLKI4_S5830DTLSKI4_S5830DTLKI4_HOME.tar.md5) and tried to flash it.
Everything in odin goes through fine up to the point where it restarts the phone, Ill attach a screenshot of what shows up for me. After the screen shows up is when I get stuck in a bootloop where the phone model shows, then the koodo bootanimation shows followed by the samsung logo. I should note though I still have complete access to recovery, the downloader mode, and even the CM rom when i restore that backup. The fact I have access to all those gives me hope as I'm sure this could be reversed.
Any advice on how I can restore this phone to stock would be greatly appreciated. I'm not very familiar with samsung devices so please try to be patient with me as I realize I have gotten into something over my head.
PS Sorry about the glare on the image its the best I could do as it disappears quickly.
Jeklund said:
I have an S5830D that I flash an CM7 rom to (APOCALYPSE-FINAL), I'm now looking at getting back to stock. I'm having trouble getting my CWM restore back. Now after doing some searching I realized I would need to flash a stock firmware version through odin. I went out and found what i believe is the correct firmware version for this Koodo model (the name is S5830DTLKI4_S5830DTLSKI4_S5830DTLKI4_HOME.tar.md5) and tried to flash it.
Everything in odin goes through fine up to the point where it restarts the phone, Ill attach a screenshot of what shows up for me. After the screen shows up is when I get stuck in a bootloop where the phone model shows, then the koodo bootanimation shows followed by the samsung logo. I should note though I still have complete access to recovery, the downloader mode, and even the CM rom when i restore that backup. The fact I have access to all those gives me hope as I'm sure this could be reversed.
Any advice on how I can restore this phone to stock would be greatly appreciated. I'm not very familiar with samsung devices so please try to be patient with me as I realize I have gotten into something over my head.
PS Sorry about the glare on the image its the best I could do as it disappears quickly.
Click to expand...
Click to collapse
If you have complete access to recovery mode, try wiping data and cache after flashing with Odin. That does the trick for me when I have a bootloop after flashing with Odin.
ImSoBored said:
If you have complete access to recovery mode, try wiping data and cache after flashing with Odin. That does the trick for me when I have a bootloop after flashing with Odin.
Click to expand...
Click to collapse
Agreed... reboot into recovery and clear cache and dalvik cache and then reboot.
So I've just completed a new flash with odin, I went in and flashed cwm then proceeded to factory reset, wipe cache, wipe dalvik, and I even do battery reset. Every wipe goes fine except for when I attempt to do the factory reset I received the following error:
Code:
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
Even after those wipes it still bootloops but thats most likely as the factory reset didn't work.
Jeklund said:
So I've just completed a new flash with odin, I went in and flashed cwm then proceeded to factory reset, wipe cache, wipe dalvik, and I even do battery reset. Every wipe goes fine except for when I attempt to do the factory reset I received the following error:
Code:
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
Even after those wipes it still bootloops but thats most likely as the factory reset didn't work.
Click to expand...
Click to collapse
Try not using CWM, or your SD card may be corrupt and you have to format it, I'm not sure though.
ImSoBored said:
Try not using CWM, or your SD card may be corrupt and you have to format it, I'm not sure though.
Click to expand...
Click to collapse
That did it, for some reason I had this thought in my head I had to flash cwm right away and clear stuff that way. Once odin finished I went in recovery and wiped data and cache through the stock recovery and it booted right up. Thanks for the help really appreciate it.

Boot loop after flashing rom

So I've been attempting to install a rom, ANY rom on my phone and the results always seem to be the same. I boot into TWRP, wipe then install the rom. On reboot, the phone loads up the initial (black) samsung screen. Then buzzes twice and reboots. It will do this infinitely. It happens with any rom I've tried flashing. It has to be something I am missing or doing wrong. Does anyone have an idea what it is? I've even gone as far as completely wiping, odin in a stock image and then adding TWRP again. I just can't seem to figure it out.
re: bootloops
Tharkys said:
So I've been attempting to install a rom, ANY rom on my phone and the results always seem to be the same. I boot into TWRP, wipe then install the rom. On reboot, the phone loads up the initial (black) samsung screen. Then buzzes twice and reboots. It will do this infinitely. It happens with any rom I've tried flashing. It has to be something I am missing or doing wrong. Does anyone have an idea what it is? I've even gone as far as completely wiping, odin in a stock image and then adding TWRP again. I just can't seem to figure it out.
Click to expand...
Click to collapse
You need to ODIN flash the stock original official COG2
firmware & odin flash cf-autoroot and the twrp recovery
before flashing the zip file rom.
Once that's done you can flash any N910T zip file rom in
twrp recovery without any issues.
Make sure to do a full wipe in twrp before you flash any
zip file rom to avoid bootloops and or getting stuck on
the samsung boot logo screen and be sure to do a full
and complete wipe which includes:
"System, Data, Cache, Dalvik Cache and last but not
least do a factory reset.
Good luck,
Have a great day!
Tharkys said:
So I've been attempting to install a rom, ANY rom on my phone and the results always seem to be the same. I boot into TWRP, wipe then install the rom. On reboot, the phone loads up the initial (black) samsung screen. Then buzzes twice and reboots. It will do this infinitely. It happens with any rom I've tried flashing. It has to be something I am missing or doing wrong. Does anyone have an idea what it is? I've even gone as far as completely wiping, odin in a stock image and then adding TWRP again. I just can't seem to figure it out.
Click to expand...
Click to collapse
i dont know if we are having the same problem but try installing the original firmware via odin and see if that works. if it does not then we have the same problem and i dont know how to fix it, now i am stuck with my S4 wait for help from someone to help me fix my note 4

Categories

Resources