Hi All,
I am at my wit's end with my Galaxy S3 at this point. I was running CM11 M12 snapshot, but I was getting reboots at least once per hour. I decided to try to dirty flash the latest nightly, but the boot loop started then. Here's what happens:
Cold start:
1. Samsung Logo flashes
2. Galaxy S3 Cyanogenmod Logo screen, 10-20s
3. CM11 Boot animation (spinning arrow gets stuck sometimes)
4. Reboot after arrow stops
I want to format /data to try a clean flash. However, CWM reboots during this process. I can format /cache and clear the dalvik cache. I can mount and unmount /data in CWM.
Is there another way to try to format /data? It seems something is seriously corrupted (probably why I was getting reboots when I could actually load CM). Any help would be greatly appreciated.
Side note: I made a nandroid backup before all of this, but CWM is giving me the classic MD5 mismatch error, so I need to fix that before restoring the backup (assuming it's not just corrupted...).
Thanks for your help.
EDIT: I followed this guide and this comment to flash back to stock.
I originally thought I had a bad emmc block, but after checking them manually (through adb shell dd in recovery) and through a CWM flashable scanning tool, I could not find a bad block. So I went back to rooted stock. Now I am deciding if I should just de-bloat stock 4.0.4 TouchWiz (it's very ugly) or try another custom ROM...
ScheissSchiesser said:
Hi All,
I am at my wit's end with my Galaxy S3 at this point. I was running CM11 M12 snapshot, but I was getting reboots at least once per hour. I decided to try to dirty flash the latest nightly, but the boot loop started then. Here's what happens:
Cold start:
1. Samsung Logo flashes
2. Galaxy S3 Cyanogenmod Logo screen, 10-20s
3. CM11 Boot animation (spinning arrow gets stuck sometimes)
4. Reboot after arrow stops
I want to format /data to try a clean flash. However, CWM reboots during this process. I can format /cache and clear the dalvik cache. I can mount and unmount /data in CWM.
Is there another way to try to format /data? It seems something is seriously corrupted (probably why I was getting reboots when I could actually load CM). Any help would be greatly appreciated.
Side note: I made a nandroid backup before all of this, but CWM is giving me the classic MD5 mismatch error, so I need to fix that before restoring the backup (assuming it's not just corrupted...).
Thanks for your help.
Click to expand...
Click to collapse
Can you get into recovery?
Sent from my Nexus 5
ShapesBlue said:
Can you get into recovery?
Click to expand...
Click to collapse
Thanks for the reply. Yes, I can get into CWM recovery.
ScheissSchiesser said:
Thanks for the reply. Yes, I can get into CWM recovery.
Click to expand...
Click to collapse
Alright. Are on you on the latest version of cwm?
Sent from my Nexus 5
ShapesBlue said:
Alright. Are on you on the latest version of cwm?
Click to expand...
Click to collapse
Yes. ClockworkMod Recovery v6.0.4.5.
Thanks for the response. Anything I should try?
ScheissSchiesser said:
Thanks for the response. Anything I should try?
Click to expand...
Click to collapse
I'm not completely familiar with CWM, I've always ran either twrp or Philz. I'd maybe suggest switching to another recovery. It's personal preference but to each there own. You should be able to flash it via Odin
Sent from my Nexus 5
Thanks for looking into this. See my edit in the OP for my solution. I'm still not sure WHY it happened, but I have a working (Stock Rooted 4.0.4 TouchWiz) phone again.
Related
Tried this and rogue recovery, but I want to get up JB. So.. I used the easyoneclick and got rogue installed, then tried to flash the latest EOS4 at the time. That put me at the boot screen (4 color any boot animation) and never got any further.
So... I used the easy one click to restore stock, and that got me back to good for a few days, but still no JB.
So then I tried Goo manager and oddly enough it couldn't push the "recovery script" or what is actually twrp recovery. I was able to boot into recovery and push the GM downloaded twrp though.
So, now I have updated twrp (sort of through GM), and nightly EOS4 - but still stuck on boot animation - left it for 4 hours before I decided it wasnt' going to work. Any ideas? I was reading some about frameworks and I'm thinking that might be my problem, but I'm not finding any really good walkthroughs or advice. What can I try next? Any help greatly appreciated - Thanks!
Did you wipe the cache, Davlik, system and factory reset before flashing?
frederuco said:
Did you wipe the cache, Davlik, system and factory reset before flashing?
Click to expand...
Click to collapse
I did, but I can try again!
Bigscout79 said:
I did, but I can try again!
Click to expand...
Click to collapse
And... I'm very grateful! That seemed to work! I might not have been wiping the system.
Thanks!
Glad it is all sorted.
i flashed a rom and than i stuck at the boot screen " Samsung Galaxy note 10.1". i have no idea what happen. i already tried to restore back to stock rom but it still the same or even i try to flash another rom. any help pls?
reddevilboyz said:
i flashed a rom and than i stuck at the boot screen " Samsung Galaxy note 10.1". i have no idea what happen. i already tried to restore back to stock rom but it still the same or even i try to flash another rom. any help pls?
Click to expand...
Click to collapse
Perhaps you could tell us what you flashed - it might help
bad sign, if you can't boot into recovery I'd say call Samsung
jaydubbbbs said:
bad sign, if you can't boot into recovery I'd say call Samsung
Click to expand...
Click to collapse
i could flash into recovery mode CWM darkman or other CWM or even odin. i even wipe cache , factory reset and dartik cache. but its still stuck at the boot screen.
Bulbous said:
Perhaps you could tell us what you flashed - it might help
Click to expand...
Click to collapse
basically i try to flash every roms to see if any rom work to solve the prolem. when i ry to mount efs it said error. and after i use odin to flash back to stock. i saw current binary-Samsung but the system status still stuck at custom. any idea?
You should boot to the bootloader (Volume down and power button) and do a factory reset. This'll wipe all your data and - very likely - your Note 10.1 will boot again!
I had the same problem a while ago, and this worked for me.
edit:
Oops, I didn't saw that you tried this already...
reddevilboyz said:
i could flash into recovery mode CWM darkman or other CWM or even odin. i even wipe cache , factory reset and dartik cache. but its still stuck at the boot screen.
Click to expand...
Click to collapse
haven't seen anyone truly remedy this situation, and I wouldn't risk sharing efs files
http://forum.xda-developers.com/showthread.php?p=37465299#post37465299
please help!!!!!
hi am using a gionee e3. i changed my phone font last night using the "my font" app (not the first time), i was prompted to reboot my device, the device comes on displaying the gionee smartphone screen but doesn't boot any further than this.help needed
did you make a cwm backup? if yes, then go to recovery and restore. if no, then m sorry my friend you have flash stock, or another ROM through cwm
Gilbert_vanguard said:
did you make a cwm backup? if yes, then go to recovery and restore. if no, then m sorry my friend you have flash stock, or another ROM through cwm
Click to expand...
Click to collapse
Sometimes if you get stuck on the boot logo and it never fully boots, simply clearing the cache and dalvik cache in CWM or TWRP can fix it. (Might throw in fixing permissions as well.)
mcgrabowski said:
Sometimes if you get stuck on the boot logo and it never fully boots, simply clearing the cache and dalvik cache in CWM or TWRP can fix it. (Might throw in fixing permissions as well.)
Click to expand...
Click to collapse
yup that's one possible solution. but usually bootloop spells doom
thanks guys
thanks guys, apparently it was doom afterall, nothing worked. had to reinstall the os. lost everything
My galaxy tab was rooted and i Just installed clock work mod recovery and i tried to flash a custom ROM that was proven to work and now its stuck in a boot loop were i just see the galaxy tab logo on start up, then it shuts off. I have tried at least 5 different roms with no success. Does anyone know a fix to this? One of the roms was a aosp ROM and it got the furthest. it got past the galaxy tab logo and to its android loading logo, but it froze and restarted. This is really frustrating and i would just like a fix. anyone?
Thanks,
Zach
supertzag said:
My galaxy tab was rooted and i Just installed clock work mod recovery and i tried to flash a custom ROM that was proven to work and now its stuck in a boot loop were i just see the galaxy tab logo on start up, then it shuts off. I have tried at least 5 different roms with no success. Does anyone know a fix to this? One of the roms was a aosp ROM and it got the furthest. it got past the galaxy tab logo and to its android loading logo, but it froze and restarted. This is really frustrating and i would just like a fix. anyone?
Thanks,
Zach
Click to expand...
Click to collapse
my brother almost rom for proper functionality before flashing requires you to wipe cache and factory reset and dalvik cache wipe
i think you did not perform it
also as now you are on boot loop if you are able to boot into recovery you can try to do these things it may work or you may boot in rom
also if not possible you can then flash stock rom through odin
also after flashing stock rom you will stuck o samsng logo so dont panic and reboot into recovery and wipe factory reset and cache partiiton and reboot { just these two things }
hope i helped and you tab gets working again :good::good:
aditya rathee said:
my brother almost rom for proper functionality before flashing requires you to wipe cache and factory reset and dalvik cache wipe
i think you did not perform it
also as now you are on boot loop if you are able to boot into recovery you can try to do these things it may work or you may boot in rom
also if not possible you can then flash stock rom through odin
also after flashing stock rom you will stuck o samsng logo so dont panic and reboot into recovery and wipe factory reset and cache partiiton and reboot { just these two things }
hope i helped and you tab gets working again :good::good:
Click to expand...
Click to collapse
Hi, I whenever i perform a factory reset and device wipe, it restarts the tablet. Im not exactly sure how to flash a ROM through odin, I have used it tho.
Also, all the links to my tablets (p5113) roms are broken. Do you know of any working ones?
Thanks,
Zach:laugh:
For P5113 you can use P5110 Rom´s - IR included to support P5113
For KitKat-Roms you need to use one of the latest recovery´s - else you´ll get "Error 7".
And don´t forget
"format /system" before flashing too
Android-Andi said:
For P5113 you can use P5110 Rom´s - IR included to support P5113
For KitKat-Roms you need to use one of the latest recovery´s - else you´ll get "Error 7".
And don´t forget
"format /system" before flashing too
Click to expand...
Click to collapse
Am i suppose to format the system in CWM? whenever i do this, the tablet shuts off.
Is that suppose to happen?
Thanks,
Zach
Android-Andi said:
For P5113 you can use P5110 Rom´s - IR included to support P5113
For KitKat-Roms you need to use one of the latest recovery´s - else you´ll get "Error 7".
And don´t forget
"format /system" before flashing too
Click to expand...
Click to collapse
Sorry if I'm intruding (I own the P5100) I have the same problem of bootloop, I've done the reset (also the / system) but as soon as I install the latest nightly of CM 11 7 gives me this error (Error 7), what should I do?
All of this has happened to me for a simple update to version
ilMartiniano said:
Sorry if I'm intruding (I own the P5100) I have the same problem of bootloop, I've done the reset (also the / system) but as soon as I install the latest nightly of CM 11 7 gives me this error (Error 7), what should I do?
All of this has happened to me for a simple update to version
Click to expand...
Click to collapse
Error 7 means your recovery needs to be updated. Look at Android-Andi's signature, he has links to proper recoveries.
njstein said:
Error 7 means your recovery needs to be updated. Look at Android-Andi's signature, he has links to proper recoveries.
Click to expand...
Click to collapse
Thanks, Problem solved
Help
Hello, I have been trying to work with formating data and stuff but whenever i do cwm crashes so i tried switching to TWRP and it also crashes when trying todo anything with storage.
Any fixes?
I just want some type of android back on my tablet.
Disregard above. I am now able to format and install roms but whenever i reboot it goes back into TWRP. Any ideas why?
Thanks,
Zach
What device do you own?
Wipe Data factory reset
wipe cache
wipe dalvic cache
format /system
flash rom
reboot
First things first, I'm a newbie when it comes to all these.
I installed CM11 after much effort, but some things didn't work out well so afterwards, I installed CM12.1* (FXP-cm-11-20150301-UNOFFICIAL-taoshan).* But then I decided that I wanted to change my Gapps Package, so I went to recovery mode once again to wipe my phone and install CM12 all over again.
The thing is that for some reason I just couldn't wipe it (no error message) but I was able to log in back to the system (CM12).
I messed around with a few settings and finally I decided to install twrp 2.8.7.0 through the flashify app. I rebooted to recovery, tried to wipe again my phone and then, all hell broke loose.
I realized that I cannot wipe internal memory of all things, and cannot install any new ROM. Can't flash another recovery either through windows flashtool like CWM 6.0 Philz touch, for example. Well, it does flash but my phone keeps on logging into the twrp recovery. I also can't flash my original fft (obviously). I can't do really anything besides messing around with twrp options (and I've messed a lot with them). I'm all out of ideas, so please someone help. When trying to wipe internal storage, the following message appears:
E:mkdosfs /dev/block/mmcblk0p32 process ended with ERROR=1
E:Unable to wipe '/sdcard'.
E:Unknown MTP message type: 1
E:Unable to wipe '/sdcard'
I have the whole log, for anyone interested.
Please help and remember, I'm a newbie.
Thank you.
immortalwind said:
First things first, I'm a newbie when it comes to all these.
I installed CM11 after much effort, but some things didn't work out well so afterwards, I installed CM12.1*(FXP-cm-11-20150301-UNOFFICIAL-taoshan).* But then I decided that I wanted to change my Gapps Package, so I went to recovery mode once again to wipe my phone and install CM12 all over again.
The thing is that for some reason I just couldn't wipe it (no error message) but I was able to log in back to the system (CM12).
I messed around with a few settings and finally I decided to install twrp 2.8.7.0 through the flashify app. I rebooted to recovery, tried to wipe again my phone and then, all hell broke loose.
I realized that I cannot wipe internal memory of all things, and cannot install any new ROM. Can't flash another recovery either through windows flashtool like CWM 6.0 Philz touch, for example. Well, it does flash but my phone keeps on logging into the twrp recovery. I also can't flash my original fft (obviously). I can't do really anything besides messing around with twrp options (and I've messed a lot with them). I'm all out of ideas, so please someone help. When trying to wipe internal storage, the following message appears:
E:mkdosfs /dev/block/mmcblk0p32 process ended with ERROR=1
E:Unable to wipe '/sdcard'.
E:Unknown MTP message type: 1
E:Unable to wipe '/sdcard'
I have the whole log, for anyone interested.
Please help and remember, I'm a newbie.
Thank you.
Click to expand...
Click to collapse
try wipe->advanced wipe -> change fs -> ext4
SdtBarbarossa said:
try wipe->advanced wipe -> change fs -> ext4
Click to expand...
Click to collapse
Thank you for your answer my friend, but I actually managed to fix my problem just moments before you posted your answer! What I did was to flash the cm12.1 recovery nightly which logged me into this recovery (although it seemed all messed up and.. broken). Nevertheless, I managed to flash the CM12.1 ROM from there and everything worked fine!
Bro #immortalwind.. I'm having the same problem exactly what you had. Seriously fu***d up with all with boot loop @ recovery. Could not able to hard reset / factory reset at neither CWM nor TWRP. Tried all knows possible ways. Please could you help me here. Any1 who can halp me here pls...
P.S: literally not moving from the boot load, so flashing a ROM could not be possible i think. any other suggestions please.....
RaamXperiaL said:
Bro #immortalwind.. I'm having the same problem exactly what you had. Seriously fu***d up with all with boot loop @ recovery. Could not able to hard reset / factory reset at neither CWM nor TWRP. Tried all knows possible ways. Please could you help me here. Any1 who can halp me here pls...
P.S: literally not moving from the boot load, so flashing a ROM could not be possible i think. any other suggestions please.....
Click to expand...
Click to collapse
Try this out
RaamXperiaL said:
Bro #immortalwind.. I'm having the same problem exactly what you had. Seriously fu***d up with all with boot loop @ recovery. Could not able to hard reset / factory reset at neither CWM nor TWRP. Tried all knows possible ways. Please could you help me here. Any1 who can halp me here pls...
P.S: literally not moving from the boot load, so flashing a ROM could not be possible i think. any other suggestions please.....
Click to expand...
Click to collapse
Just reflash stock ftf. You'll be good to go. If that fails, check drivers and downgrade flashtool. After that, normally, install a boot image with a recovery, install your rom gapps, reboot.
Managed to flash.ftf... Thanks for the help friends.
Sent from my C2104 using XDA Free mobile app