Tried Bonsai and Syndicate first, neither flashed properly first time, seemed to work on the second flash, but eventually they would start freezing occasionaly when the screen was off, had to pull out battery to reboot. Tried flashing to stock di18 then flashing to Midnight, it seemed to work for a day or so, and now its freezing a few times a day when the screen turns off. I read somewhere that in odin you only need the victory8g.pit (not sure the exact file name) if you are flashing a custom rom, and I'm only ever flashing a stock rom, then rooting and flashing from the sd card. I've always used the .pit file im odin, and I've eventualy had problems with all custom roms.
Any ideas?
Skimp Killah said:
Tried Bonsai and Syndicate first, neither flashed properly first time, seemed to work on the second flash, but eventually they would start freezing occasionaly when the screen was off, had to pull out battery to reboot. Tried flashing to stock di18 then flashing to Midnight, it seemed to work for a day or so, and now its freezing a few times a day when the screen turns off. I read somewhere that in odin you only need the victory8g.pit (not sure the exact file name) if you are flashing a custom rom, and I'm only ever flashing a stock rom, then rooting and flashing from the sd card. I've always used the .pit file im odin, and I've eventualy had problems with all custom roms.
Any ideas?
Click to expand...
Click to collapse
What version of the ROMs are you trying to use?
If you start with di18 and tried to use a dk28 ROM you would have to odin the new modem.
If you're trying the EB13 ROMs, then you want to odin the EB13 tar that is stock + recovery + ext4; then flash an EB13 ROM of your choosing.
Also, you have to be sure to wipe 3x (factory reset, cache partition and davlik cache)
Be sure to follow each and every step on the first few pages of the ROM thread your going to flash, also read some into the thread too. that will give you a heads up as to what others have experienced and what might be a problem and its fix.
Good luck!!
With syndicate and bonsai I flashed the stock eb13 first, then cwm, then flashed the rom in recovery mode, midnight I flashed from stock di18, followed all instructions. Just tried midnight again, except I didnt used the victory8g.pit file or whatever, just the di18 tar, then cwm then flashed the rom.
I think me using the pit file may be what the problem was, unless you are supposed to use the pit file even when flashing a stock rom, in odin.
Are you using setcpu? Do you have a screen off profile? Are you running your phone at 1.2ghz?
Sent from my SPH-D700 using Tapatalk
Are you using setcpu? Do you have a screen off profile? Are you running your phone at 1.2ghz?
I'm not sure the answer to any of those questions, so I'm assuming no. I think the MidnightROM can run the cpu faster, but you have to download some app to turn that function on or off. I'm pretty much running MidnightRom with the regular **** on it right now. I'm thinking my problem may have been using the victory8g.pit file in odin every time I flashed to a stock rom before running clock work and flashing to a custom rom. I'm running the latest midnight off a clean flash of di18 without the victory8g.pit file, so far that seem to be the only thing I can find that would cause all the custom roms to eventualy crash...
Im going on a few hours with out a crash, but the first time it took a day or so, then started doing it more often.
Skimp Killah said:
Are you using setcpu? Do you have a screen off profile? Are you running your phone at 1.2ghz?
I'm not sure the answer to any of those questions, so I'm assuming no. I think the MidnightROM can run the cpu faster, but you have to download some app to turn that function on or off. I'm pretty much running MidnightRom with the regular **** on it right now. I'm thinking my problem may have been using the victory8g.pit file in odin every time I flashed to a stock rom before running clock work and flashing to a custom rom. I'm running the latest midnight off a clean flash of di18 without the victory8g.pit file, so far that seem to be the only thing I can find that would cause all the custom roms to eventualy crash...
Im going on a few hours with out a crash, but the first time it took a day or so, then started doing it more often.
Click to expand...
Click to collapse
What kernel is midnight using? The reason I ask the questions I'm asking is cause not every phone can be over clocked and it causes data locks. That's what it sounds like that's happening to you. there is nothing to the pit. All the pit is mapping information nothing actually gets flashed from the pit. The full tar as that information in it so its not making any changes.
Another question I have is since you keep coming from stock are you flashing the rom twice? On the first flash wipe data, cache, dalvik and on the second flash only wipe cache, and dalvik.
Sent from my SPH-D700 using Tapatalk
I'm pretty sure Midnightnight uses the Bonsai Kernel. On the about phone section it say 2.6.32.9 for kernel version. When I did bonsai and syndicate I usually data reset 3 times and cache and dalvik or whatever, once, each time I flashed it, which was usually twice.
okay, in the phone it says Bonsai/Kernal-v3.0.0
Obviously I'm on an epic 4g. When it freezes its always when the screen is off, never during actual use. I'm not sure if that helps narrow it down. And I had an epic with a cracked screen, same freezing problems, now on a new epic, still same thing, but I assumed it was the custom roms doing it because the problem only started after that.
MidnightROM and bonsai didn't require a wipe, when I tried syndicate i wiped as per the instructions, except I did the factory reset 3 times on the second flash as well.
Skimp Killah said:
I'm pretty sure Midnightnight uses the Bonsai Kernel. On the about phone section it say 2.6.32.9 for kernel version. When I did bonsai and syndicate I usually data reset 3 times and cache and dalvik or whatever, once, each time I flashed it, which was usually twice.
Click to expand...
Click to collapse
Is the bonsia kernel oced to 1.2 ghz out the box?
Try this when you get a chance.
1) odin eb13 full tar
2) run the cwm3.0.0.6 one click
3) reboot into recovery and let the auto conversion do its thing.
4) flash your rom of choose (after wiping data, cache, dalvik 3 times)
5) let the phone boot all the way up.
6) reboot into recovery again
7) flash the rom again (after wiping cache, dalvik 3 times)
8) let the phone boot
9) install setcpu and see where your clocked at
Sent from my SPH-D700 using Tapatalk
Skimp Killah said:
okay, in the phone it says Bonsai/Kernal-v3.0.0
Obviously I'm on an epic 4g. When it freezes its always when the screen is off, never during actual use. I'm not sure if that helps narrow it down. And I had an epic with a cracked screen, same freezing problems, now on a new epic, still same thing, but I assumed it was the custom roms doing it because the problem only started after that.
MidnightROM and bonsai didn't require a wipe, when I tried syndicate i wiped as per the instructions, except I did the factory reset 3 times on the second flash as well.
Click to expand...
Click to collapse
Theres gonna be problems coming from stock cause of there back up there script performs. Follow the instructions I just posted and lets go from there
Sent from my SPH-D700 using Tapatalk
Flashed to EB13
Ran oneclick CWM 3.0.0.6
Converted.
wiped data, cache and dalvik, 3 times each
Flashed MidnightROM
it did the whole random vibrations flashing two screens thing.
removed battery and booted into recovery
wiped cache and dalvik 3 times each
flashed MidnightROM again
After the second flash it went to the intial start up screen welcoming me to the phone, that was odd, never had it do that before.
Booted to recovery again and installed market and other standard apps.
Downloaded cpu master cause im cheap,
phone is clocked at 1000
I'll let you know if i have any more problems, the whole welcoming me to the phone thing was new, ive never had it bring that screen up any of the other times i flashed a custom rom, hopefully this is a sign of good things
Skimp Killah said:
Flashed to EB13
Ran oneclick CWM 3.0.0.6
Converted.
wiped data, cache and dalvik, 3 times each
Flashed MidnightROM
it did the whole random vibrations flashing two screens thing.
removed battery and booted into recovery
wiped cache and dalvik 3 times each
flashed MidnightROM again
After the second flash it went to the intial start up screen welcoming me to the phone, that was odd, never had it do that before.
Booted to recovery again and installed market and other standard apps.
Downloaded cpu master cause im cheap,
phone is clocked at 1000
I'll let you know if i have any more problems, the whole welcoming me to the phone thing was new, ive never had it bring that screen up any of the other times i flashed a custom rom, hopefully this is a sign of good things
Click to expand...
Click to collapse
Some rom devs have that enabled while others don't. If your flashing the same rom you have been and haven't seen that before I bet your good
Fyi: setcpu is free to xda users you just need to find it as I can't post links from my phone
Sent from my SPH-D700 using Tapatalk
from midnight i flashed to cm7, then wiped installed google apps and re-booted, so far so good
gingerbread
Related
I've tried to install midNIGHT rom 6 times now with the same result. I cannot install any apps from the market, titanium backup, or from sdcard. It will vibrate once at the beginning of install than again 2 or 3 times. My phone will then show the bootup animation and return to the homescreen. Ive odined back to stock and rerooted 4 times and wiped everything 3x each time. Each time I get the same result. Ive also tried reformatting my sd card and starting with a fresh download. Other roms work, just not this one. I dont have enough posts to reply to the midnight thread, so what should I try next to make it work?
acburnett said:
I've tried to install midNIGHT rom 6 times now with the same result. I cannot install any apps from the market, titanium backup, or from sdcard. It will vibrate once at the beginning of install than again 2 or 3 times. My phone will then show the bootup animation and return to the homescreen. Ive odined back to stock and rerooted 4 times and wiped everything 3x each time. Each time I get the same result. Ive also tried reformatting my sd card and starting with a fresh download. Other roms work, just not this one. I dont have enough posts to reply to the midnight thread, so what should I try next to make it work?
Click to expand...
Click to collapse
what rom did u have before that workd ??
i had acs with ext then flashed to rooted ec05 with rfs. had several eclair roms installed.
acburnett said:
i had acs with ext then flashed to rooted ec05 with rfs. had several eclair roms installed.
Click to expand...
Click to collapse
MAYBE YOUR flashing the wrong rom to update from the midnight ex: if you use dk28 ... i dnt think thats gets the proper update ec05
so lets see if you flash a dI18 or better get eb13 stick rom ... now u can either flash the ec05 modem or as my phone did when i used the stock eb13 it sent me the update for ec05 then i rooted w 3.0.6 clockworkmod then i went to BONSAI .. i left BONSAi to midnight ... i wiped factory data 3x - cache petition 3x and davlik cache 3x ... then i installed the zip MIDNIGHT V5.2 JOURNALING ON .... THEN AFTER IT BOOTED .... i went back into RECOVERY and flash the ZIP EXTRAS .. bang it was magic ... lol'
but basically im tryn to give you steps that maybe something might help u or give u and idea ..... IT WORKED FOR ME .....
DISCLAIMER : im not a professional if something major goes wrong i dnt not claim responsibility ...
I have the same problem. Worked the first time I installed it but I restored back to stock. Now when I install I can't install from market. Tried odin back to stock but It still doesn't work. Haven't seen a solution in the midnight thread besides going to EXT.
I am having issues as well and cannot post a reply. I have wiped and re installed 3x but my phone will randomly turn off and I have to pull the battery to reset device. If the device stays plugged in I do not have this issue. Any ideas or suggestions would be greatly appreciated!!
You note that this version is the one with journaling enabled... have you tried the version without journaling? You can manually re-enable it by making a CWM Nandroid backup and then restoring that backup immediately after.
acburnett said:
i had acs with ext then flashed to rooted ec05 with rfs. had several eclair roms installed.
Click to expand...
Click to collapse
On the instructions for midNIGHT 5.2 with Journaling On it says not to start with a pre-rooted EC05. Start with stock EC05 and then root with CWM 2.5.5 for RFS or 3.0.0.6 if you are wanting to use the EXT4 one. There is a link for a stock EC05 on the instructions in the thread for the ROM
And how to check if the journaling is actually on or off.
dito33 said:
And how to check if the journaling is actually on or off.
Click to expand...
Click to collapse
I'm not sure if there's a quick and easy way to detect this through the Terminal Emulator. I tried a line of code that I believed would tell me but I didn't get the answer I was looking for. Someone else may have the answer.
The quick and dirty way, however, is to make a Nandroid backup through Clockworkmod, as you should generally just have one at all times anyway. Now turn your phone on, and pull the battery out. If when you turn your phone back on you don't encounter any FC's, then your journaling is on and your data is protected. If not, then restore your Nandroid backup you just made and that will enable journaling.
If you installed a no-journaling rom, rest assured, journaling is off if you haven't restored. Either way you should have a Nandroid backup just in case.
Note: This process has been documented and posted many many many times across XDA at this point.
I was also having this issue so I installed the EXT4 Journal On version and problem solved. No one knows why LOL.
I'm having problems flashing roms at this point. the only rom that has consistently been a go to and stable everytime has been bonsai 3.0.1. SRF of any kind typically wont flash without a reflash over the top of it and then there seems to always be random issues. So now the file that i have for bonsai 3.0.1 that i flash through clockwork seems to not work. i flash it, it to boots up right the first time, then i do the the three button reset and then it reboots with google serveices framework, swype, etc...FC's. this never happened before when i flashed between roms and flashed back. Is it possible the file ive been using for clockwork has in turn become corrupt and have to download a new file? i laso set everything up did the start up wizard and all that and then i did the three button reset and the setup wizard popped up again like i had just flashed the phone again? whats going on?
TorelliB said:
I'm having problems flashing roms at this point. the only rom that has consistently been a go to and stable everytime has been bonsai 3.0.1. SRF of any kind typically wont flash without a reflash over the top of it and then there seems to always be random issues. So now the file that i have for bonsai 3.0.1 that i flash through clockwork seems to not work. i flash it, it to boots up right the first time, then i do the the three button reset and then it reboots with google serveices framework, swype, etc...FC's. this never happened before when i flashed between roms and flashed back. Is it possible the file ive been using for clockwork has in turn become corrupt and have to download a new file?
Click to expand...
Click to collapse
It sounds like you are restoring corrupted data. Do you have an older backup you can use? You may also want to enable journaling. Which Clockwork version are you using? You can do a Factory data reset and redownload your apps and reset up your accounts and syncs.
To enable journaling on Bonsai 3.0.1 using CWM 3.0.0.6 just make a nand backup and then restore it.
I was running Starburst v1.9 and saw a thread on Themes & Apps with ICS transitions. I downloaded both just in case (ICS Transitions & Revert back to stock). I went into Root Explorer and checked my Clockwork/Backup and saw that I had a backup in there. I booted into Recovery and flashed the theme transitions for ICS zip and thus problem began.
I then went to restore to restore the backup and it seems like that file was corrupted because it wouldn't restore. I ended up flashing the revert zip file and wiping my rom. It doesn't boot but I can still get into recovery. I believe that the issue is that the theme was made for the v1.9.5 and I had v1.9 of Starburst.
I was messing around with it and I was able to boot back in and click on the Android to set it up. After a while the phone will go crazy and the screen will flicker on and off. The buttons at the bottom became useless. How can I recover from this.
** I used my friend's Sensation and downloaded v.1.9.5 and threw it on my SD. I booted into Recovery and flashed the ROM and it still won't boot up. Any suggestions? **
The phone booting up I think was a luck of the draw thing. Since then the phone has not been able to boot into the actual ROM. I've been without a phone since yesterday and I'm planning on going into the Sprint store and getting it swapped.
Did you wipe system, data, cache, and dalvik?
THEN reflash the rom?
Yes. I was a flashaholic on my Evo.
I notice another thread in q&a with people the same issue as mines. I'm lost and haven't had my phone working for two days now.
Here's what I did:
Delete system, wipe factory reset, cache and dalvik, flashed ROM.
Could it be kernel related? I'm confused. I have a wedding tomorrow and this couldn't have happened at a worse time. Coincidentally something happened on my At&t dumb phone so I'm phoneless.
stupid suggestion...is your battery low?
with the evo it would see corrupted if the battery was low. may not apply, but hey its a shot.
if you cant figure out, theres always Odin to cure your issues
ReDL the ROM and reflash. Try mounting USB storage while in recovery. Alternatively, Odin the stock .tar for a full refresh.
If you've already retired reflashing I'd go with odin back to stock
Sent from my SPH-D710 using xda premium
here is the link for a format all then you can try and flash a rom again if you like. If not I would do like previously suggested and flash return to stock in Odin- link here
playya said:
here is the link for a format all then you can try and flash a rom again if you like. If not I would do like previously suggested and flash return to stock in Odin- link here
Click to expand...
Click to collapse
Awesome. The wedding made me forget about my phone but now that it's over I'm missing it.
I will flash to stock and re-root.
Sent from my Nexus S 4G using XDA App
Posting this here because it wont let me post in the development forum.
Downloaded Legendary Rom 2.2, rebooted into Clockwork, wiped cache and Dalvik x3 each, installed Rom, rebooted....just sits at Samsung logo. I gave it a while in case it was just slow or something and then pulled battery, went back into clockwork, and tried installing a different kernel (the newest Samurai) in case that was the problem. Same thing happens except there is now a blue progress bar below the samsung logo. any suggestions to get it to work? I am installing legendary 2.1 now to see if that works.
DaveWW00 said:
Posting this here because it wont let me post in the development forum.
Downloaded Legendary Rom 2.2, rebooted into Clockwork, wiped cache and Dalvik x3 each, installed Rom, rebooted....just sits at Samsung logo. I gave it a while in case it was just slow or something and then pulled battery, went back into clockwork, and tried installing a different kernel (the newest Samurai) in case that was the problem. Same thing happens except there is now a blue progress bar below the samsung logo. any suggestions to get it to work? I am installing legendary 2.1 now to see if that works.
Click to expand...
Click to collapse
Reflash the rom again. If still the same issue, then download the rom from a computer and compare the MD5 checksums to make sure you have the entire file. Read a few pages back in that thread to get the MD5 checksum and use something like: http://portableapps.com/apps/utilities/winmd5sum_portable
The progress bar appeared at the Samsung screen after your kernel update because that particular kernel added that.
What did you have installed prior to installing Legendary ROM, some people have reported issues if they weren't on gingerbread prior to flashing. Try flashing back to stock, upgrading to gingerbread ota, reroot with Odin and then reflash. I'm working on Legendary ROM 2.2, works well, but have some issues with the screen turning off and not coming back on. 2.1 was flawless for me though. Might go back.
njett said:
What did you have installed prior to installing Legendary ROM, some people have reported issues if they weren't on gingerbread prior to flashing. Try flashing back to stock, upgrading to gingerbread ota, reroot with Odin and then reflash. I'm working on Legendary ROM 2.2, works well, but have some issues with the screen turning off and not coming back on. 2.1 was flawless for me though. Might go back.
Click to expand...
Click to collapse
I think that is a Samurai 3.0 kernel issue. Try Shadow kernel.
Sent from my SPH-D700 using XDA App
i must relay this...shadowkernel is awsome. as they have said above. odin back to ec05 and start from scratch. it sound like you have a semi-soft brick issue.
I get that when I try copying the ROM file through my network or a slow connection, meaning a bad file. Another person got this almost everytime because his sd card was going bad and needed reformatting. Everytime he flashed it transmitted bad data through recovery. He reformatted sd card and no more problems. But first try a redownload as suggested.
Hi xda,
I ran into a problem I've never faced today. Before you start assuming, I've done my research. I've searched all over the forums, tried multiple solutions (none worked) and... potentially permabricked it?
Rooted for 7 months, running Jedi Mind Tricks v5.1 Android 4.0.3
How it happened: Today I noticed my phone running really wierdly. It would crash apps constantly, which didn't happen yesterday. So I put it on *close all apps after exiting* on developer options and limited it to run 2 background apps. Throughout the day, my phone would just restart out of absolutely nowhere: in the middle of a text, after unlocking my phone. Each time progressively got shorter between the restarts. It would also freeze a lot of the time. This never happened before today. Maybe a freeze or two, but not this bad.
Did a few battery pulls, no dice. Then this is where it gets worse. The time between boot loops were from 1-2 minutes now. I was getting pissed, so I decided I needed to wipe it and install a new rom. I enter recovery mode CMW 5.0 and do an initial factory reset. Half way through, it crashes again. Now all it does is vibrate constantly until I turned it back on into recovery. Launches recovery. I try to super wipe it. Half way through, crashes again. I try this several times in conjunction with battery pulls. Doesn't work.
I pull sim card, SD card and battery out, let it rest before I reset it.
Then I tried to Odin its ass. I bricked it into the yellow warning screen about a updated system error because I fail with Odin. I searched around to find a solution. I redid Odin to stock kernel it. When it revived, it went into the loading screen. Yes! Progress! It was 99% done with loading when it froze on it. Fml. Battery pull, reboot, and it goes back into its habitual boot loop pattern. I can still access CMW, but it still crashes when I try to super wipe/wipe it.
I have to fix this because, well I bought this from someone with no warranty and using a no contract provider.
Help?
UPDATE: I was able to successfully superwipe my phone, then reinstall Mind Tricks as the rom of choice onto it. It doesn't freeze. Simply bootloops again and again. I don't know what to do.
eaudexs said:
UPDATE: I was able to successfully superwipe my phone, then reinstall Mind Tricks as the rom of choice onto it. It doesn't freeze. Simply bootloops again and again. I don't know what to do.
Click to expand...
Click to collapse
Firstly I suggest upgrading your recovery to 6.x via odin. Then superwipe. Redownload mind trick fresh, flash mind trick, wipe data/factory reset via recovery and try to boot letting it settle for about five minutes. If this fails, flash back to stock via Odin to rule out hardware faults.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
elesbb said:
Firstly I suggest upgrading your recovery to 6.x via odin. Then superwipe. Redownload mind trick fresh, flash mind trick, wipe data/factory reset via recovery and try to boot letting it settle for about five minutes. If this fails, flash back to stock via Odin to rule out hardware faults.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I've been looking through some how-to's but I can't seem to find how to upgrade recovery using odin. I can only find the .img file and instructions on how to do it via command lines. Any advice?
Thanks
Good suggestion but better yet ...... I had the same issue on cwm.... get twrp 2.2 look for the flashable download....... 2.3 has a few bugs so stick wit .2
Sent from my SGH-T989 using xda app-developers app
Definitely get twrp on it. Flashing twrp solved 99% of my problems running cm10. Zero rr in weeks. If I were you I would go back to stock for your device. After confident its running like it should. Then root and and go nuts.
I've personally never really had to pull the battery, very rarely. I'm worried about your ram. Could it b corrupted? A short somewhere? All unrecoverable.
I wonder if you could somehow mount your device using Linux. And run memory tests or drive diagnostics.(just thinking out loud).
Twrp is definitely a must. Good luck
Sent from my cm_tenderloin using xda app-developers app
Try doing complete wipes and reflashing a different more stable rom and see if it happens again. There are scripts to do complete and total wipes just to make sure you get a clean install (kind of like the others suggested) atleast yours can turn on so your not hard-bricked.
That's great how you guys are saying twrp solved your issues! It's really funny when cm10 supports cwm recovery. But op, let me see if I still have mine.
Sent from my SGH-T999 using Tapatalk 2
Thank you guys for all the suggestion. I was able to finally install CMW 5.5 on Odin, then go to 6.0 through flashing it. Then I super wiped it several times, normal wipe data/user settings, Darkside super wipe, then install Jedi Mind Trick X, super cache wipe, mount system, then rebooted. It worked for several minutes before locked on boot loop again.
Can someone post the link to TWRP touch for flash? That would be awesome.
I've also been thinking if it could be an external hardware problem and not a software problem. How could I run the diagnostics like you had suggested?
Thanks!
eaudexs said:
Thank you guys for all the suggestion. I was able to finally install CMW 5.5 on Odin, then go to 6.0 through flashing it. Then I super wiped it several times, normal wipe data/user settings, Darkside super wipe, then install Jedi Mind Trick X, super cache wipe, mount system, then rebooted. It worked for several minutes before locked on boot loop again.
Can someone post the link to TWRP touch for flash? That would be awesome.
I've also been thinking if it could be an external hardware problem and not a software problem. How could I run the diagnostics like you had suggested?
Thanks!
Click to expand...
Click to collapse
my sgs2 did this last month i did the same you did. after no fix i installed a cwmtouch through odin just to be able to restore a back up and worked flawlessly. After that i switched to TWRP again flashed it with no problem through odin and my s2 has been working fine ever since, but fyi i updated twrp to its 2.3.1.1 version and now i get errors can still restore but cant flash jb roms and can only do dirty flashes of ics roms
I'm currently in the process of trying to flash twrp. Is it uncommon that when I went into recovery, it also boot looped on me several time?
eaudexs said:
I'm currently in the process of trying to flash twrp. Is it uncommon that when I went into recovery, it also boot looped on me several time?
Click to expand...
Click to collapse
what version of TWRP are you trying to use? NO it does not bootloop
I did a full wipe, script wipe, with Darkside using CMW6 and restored an old backup. It still crashes. I'm starting to think it's hardware problems. I haven't gone to TWRP because I can't find a flashable 2.2 version.
eaudexs said:
I did a full wipe, script wipe, with Darkside using CMW6 and restored an old backup. It still crashes. I'm starting to think it's hardware problems. I haven't gone to TWRP because I can't find a flashable 2.2 version.
Click to expand...
Click to collapse
Nah my man you do not use the script with CWM6 thats your problem right there
---------- Post added at 03:39 PM ---------- Previous post was at 03:38 PM ----------
eaudexs said:
I did a full wipe, script wipe, with Darkside using CMW6 and restored an old backup. It still crashes. I'm starting to think it's hardware problems. I haven't gone to TWRP because I can't find a flashable 2.2 version.
Click to expand...
Click to collapse
Come on now the flashable version is in the thread...tisk tisk tisk also there are a few version in flashable form in there as well my friend. Got to get your hands dirty sometimes.... LOL Good luck
http://forum.xda-developers.com/showpost.php?p=32984410&postcount=380
Thank you my friend. I was able to finally find a 2.2 TWRP and I flashed it via odin. Did full wipes, full cache wipes, flashed a rom. Fixed permission and all that good stuff. Left it off for 10 minutes. Came back, it started running through initialization. About 4 minutes in, it crashes again. I'm starting to think this could be hardware problem.
eaudexs said:
Thank you guys for all the suggestion. I was able to finally install CMW 5.5 on Odin, then go to 6.0 through flashing it. Then I super wiped it several times, normal wipe data/user settings, Darkside super wipe, then install Jedi Mind Trick X, super cache wipe, mount system, then rebooted. It worked for several minutes before locked on boot loop again.
Can someone post the link to TWRP touch for flash? That would be awesome.
I've also been thinking if it could be an external hardware problem and not a software problem. How could I run the diagnostics like you had suggested?
Thanks!
Click to expand...
Click to collapse
Do not use scripts with the new CWM 6 as it will cause this. Manually wipe everything and do not use scripts. You can use scripts with twrp but not the latest cwm
Sent from my SAMSUNG-SGH-T989 using xda premium