I tried flashing two different roms (synergy and chemistry) on my sprint galaxy s3. It turns on but then wont go past the "galaxy s III" logo. I just restored my backup and all is well but I really want to get multi window on this thing so I could really use some help as to what is not letting me boot up all the way. The last thing i messed around with rooting was my DroidX and with that it really mattered a lot which version of android you were flashing from. I have 4.1.2 the most recent update. Is that why these roms are not working? Any help would be much appreciated I am very excited to get a killer rom on this bad boy.
Did you clear /data, /system, cache, and dalvik cache before flashing? If not, what is your flashing procedure?
But no, the current version should not make any difference when flashing because you are clearing everything anyway
CNexus said:
Did you clear /data, /system, cache, and dalvik cache before flashing? If not, what is your flashing procedure?
But no, the current version should not make any difference when flashing because you are clearing everything anyway
Click to expand...
Click to collapse
I boot into recovery after i put the rom on to my sd card. Then wipe the factory data, cache partition, and delvik cache. I do those steps twice, then install the rom. The install seems to go fine, it always says successful at the end, it just wont go past that screen. Does it mater which version of clockworkmod I use?
You need to wipe /system too. A factory reset only clears app data, and thats no help if you're not wiping the OS as well because you're installing the new one on top of the old without cleaning up first...and thats why it wont boot because different pieces are getting mixed and not together with the files it should be with
It should say something like "format /system"
CNexus said:
You need to wipe /system too. A factory reset only clears app data, and thats no help if you're not wiping the OS as well because you're installing the new one on top of the old without cleaning up first...and thats why it wont boot because different pieces are getting mixed and not together with the files it should be with
It should say something like "format /system"
Click to expand...
Click to collapse
Thank you so much for your quick response. As far as I can tell, I am wiping everything I should be. I use clockwork recovery mod version: and the choices it gives you are: Wipe data/factory reset, wipe cache partition, and wipe dalvik cache. From all the instructional threads I've read, those are the only things you need to clear out before the install. My clockwork version is v5.5.0.4 which i think might be really old. Could that be my issue? Does it matter how I rooted it? I just tryed to put jellybomb v14 on it and it didn't even give me the galaxy s III logo. Luckily it booted back into recovery though. I really don't want to hard brick this thing.
Which recovery are you using?
For TWRP, I generally recommend formating system too.
Also, make sure to flash the rom zip and THEN the gapps.
A-Shin said:
Which recovery are you using?
For TWRP, I generally recommend formating system too.
Also, make sure to flash the rom zip and THEN the gapps.
Click to expand...
Click to collapse
clockworkmod v5.5.0.4
cchrisrollins said:
clockworkmod v5.5.0.4
Click to expand...
Click to collapse
Make the switch to TWRP v2.3.1.0 (newer ones I've heard have problems) but you will be thanking me later. It's way easier and much better than CWM... just an FYI for ya!
cchrisrollins said:
clockworkmod v5.5.0.4
Click to expand...
Click to collapse
I suggest trying a flash with TWRP. If you are unsure how to install TWRP, just download the Goomanager app, then choose install Open Recovery Script. But, before you install or change anything, look around a bit on how to install it. Make sure you follow directions step by step. After you have installed TWRP, try flashing again. Good luck!
Haha, so it looks like switching to twarp is something that i need to do, I'll start researching how to do that. I don't thing clockwork is causing the issues im having, but I could certainly be wrong. Since my phone is rooted, that also means the bootloader is unlocked rite?
cchrisrollins said:
Haha, so it looks like switching to twarp is something that i need to do, I'll start researching how to do that. I don't thing clockwork is causing the issues im having, but I could certainly be wrong. Since my phone is rooted, that also means the bootloader is unlocked rite?
Click to expand...
Click to collapse
Samsung bootloaders come unlocked by default, so yes
Easiest way to switch is to download Goo manager from the Play Store and have it install TWRP for you
Generally speaking, CWM is great on most devices, but for the S3 it's TWRP that's the best and easiest to use
And when flashing new roms, make sure to always format system, it prevents corrupted files from showing up because you would be installing the new system right on top of the old one if you don't
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
cchrisrollins said:
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you made a nandroid backup in TWRP (I'd recommend to put it on the external memory, but that's just me), you should be good to try any ROM you want (only Sprint ROMS). Just follow CNexus's post (linked for posterity). Wipe system as well as factory reset, cache, and dalvik, prior to installing the ROM.
cchrisrollins said:
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you've already rooted, re-rooting isn't going to fix anything, so no need to go there.
As previously explained and detailed, do a full system wipe, and you'll be good to go.
Thank you guys so much for your very quick responses, thank you for bearing with my noobishness too haha. I am going to tryn reflash jellybomb tonight, I'll post on this thread how it goes (hopefully good).
So unfortunately it was the same result with the TWRP. Tryed doing it with a few different roms. Some roms will boot to the "Galaxy s III" logo and others like jellbomb wont even get that far. It just flashed the Samsung logo and that was it. It's gotta be something simple that im missing here, but I can't figure out what it is. On the jellybomb install afterwards TWRP did come up with a message that said something along the lines of: your phone doesn't appear to be rooted, would like to install bla bla bla. So that doesn't make sense, because I know that I do have root access. Feeling pretty frustrated because I'm doing everything the correct way. HELP!
cchrisrollins said:
So unfortunately it was the same result with the TWRP. Tryed doing it with a few different roms. Some roms will boot to the "Galaxy s III" logo and others like jellbomb wont even get that far. It just flashed the Samsung logo and that was it. It's gotta be something simple that im missing here, but I can't figure out what it is. On the jellybomb install afterwards TWRP did come up with a message that said something along the lines of: your phone doesn't appear to be rooted, would like to install bla bla bla. So that doesn't make sense, because I know that I do have root access. Feeling pretty frustrated because I'm doing everything the correct way. HELP!
Click to expand...
Click to collapse
It took me like 4-5 months to personally figure out that the problem was the kernel. You need to flash a kernel right after you flash the ROM. Either the stock kernels or better kernels like Anthrax will do. I know that for jellybomb, there's a kernel included in the Rom but for some reason,it got stuck on the gs 3 logo if I didn't flash another kernel.
Oh thank goodness there is something else I can try, I was out of ideas. Thank you!
Sent from my SPH-L710 using xda app-developers app
cchrisrollins said:
Oh thank goodness there is something else I can try, I was out of ideas. Thank you!
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
No prob, just hit dat thanks button do you know where to get the kernels?
Zin0 said:
No prob, just hit dat thanks button do you know where to get the kernels?
Click to expand...
Click to collapse
I tryed the KT47 AOSP Jellbean kernel after flashing jelly bomb and it did the same thing it did before, black screen after flashing the samsung logo
Now I did go into fix permissions and it did say failed, is that abnormal?
This is my exact procces:
1. boot into TWRP
2. factory reset
3. system wipe
4. cache wipe
5. Dalvik wipe
6. Install from external SD: jellybomb v14
7. Wipe cache/Dalvik
8. Install Kt47 kernel
9. Wipe cache/Dalvik
Anything wrong there?
Related
Everytime I install a custom rom on rom manager, it has corrupted my phone and each and everytime I'd have to restore it. Is there any way to fix it? I've seen comments on the custom roms and people have commented that it works fine on the DHD.
Hi drkhrsy
Kindly explain further by your meaning of corrupt? This would allow us here to clearly understand the problems you're facing. Thanks.
Well I first installed cyanogenmod 7 and that gave me the boot loop. After restoring the phone I thought I'd try another ROM, so I went to download the TB 7.0.3 ROM and that booted up the phone but I had constant popups on HTC sense force closing and couldn't do anything else so I had to restore the phone again. So yeh, I'm not really sure what I'm doing wrong here.
drkhrsy said:
Well I first installed cyanogenmod 7 and that gave me the boot loop. After restoring the phone I thought I'd try another ROM, so I went to download the TB 7.0.3 ROM and that booted up the phone but I had constant popups on HTC sense force closing and couldn't do anything else so I had to restore the phone again. So yeh, I'm not really sure what I'm doing wrong here.
Click to expand...
Click to collapse
Did you do a full wipe before flashing those roms, multiple fcs normally indicate that you didn't try a full wipe then reflash either of your chosen roms.
Full wipe as in factory settings?
Well I've installed a new RUU after the boot loop problem, isn't that considered as a full wipe? or should I just do a wipe again now?
I had that horrible boot loop aswell after installing Rom.manager but I fixed it with a ruu
Sent from my Desire HD using XDA App
Installing a new RUU does not constitute that you have full wipe any data and cache. As the ROM you tend to flash is, in a small or large extent, relatively different from that of RUU. That why we always advised to do a full wipe whenever we wish to flash ROMs. Else it will cause some issues such as Force Close issues.
You have to boot into recovery and select Wipe Data and Wipe Cache. That you will consider yourself that you have wipe those data and caches. Then now you can flash the desired ROM in your list.
In addition, before flashing is best to do a Nandroid back-up.
Also do check on your recovery version before you flash any ROMs as different ROMs need/may require different version in order to be flashed successfully(i.e. no or minimal issues)
Cheers mate.
aiight sweet, I'll give that a go.
Cheers!
You're most welcome.
drkhrsy said:
aiight sweet, I'll give that a go.
Cheers!
Click to expand...
Click to collapse
Memory serving EVERY ROM says you MUST perform a wipe of data and cache if coming from a different ROM. This is custom ROM 101. Please read instructions thoroughly before doing things like this. The ROM devs don't spend their free time writing instructions just for the hell of it.
Regarding ROM Manager, don't you get asked if you want to wipe data and cache when you flash a new ROM (or is that not an option on the free version)?
Yeh I do get asked for wiping data and cache, I do that and it just seems to still screw up. Also backing up my files through clockwork seems to make my phone get stuck on the HTC boot up screen which requires me to reformat using the RUU file.
I would suggest re-flashing the recovery.img file.
Also, are you using the same cwm-r version to restore as used to create backup? For example, If version 2.x.x.x was used to backup you can't use 3.x.x.x to restore.
Sent using witchcraft via XDA Developers Premium App.
I've just checked my CWM-R version and its recovery version is at 3.0.2.6 hmm now I cant get into the recovery boot screen :S. I'd just most likely restore the phone again and try root the phone again. but thanks anyway
nvm I got in the recovery boot. Yeh the CWM-R are the same version.
drkhrsy said:
nvm I got in the recovery boot. Yeh the CWM-R are the same version.
Click to expand...
Click to collapse
I think you miss understand. I don't mean do they match wherever you look.
Did you make the original backups using version 3.0.0.x or 2.5.x.x?
Sent using witchcraft via XDA Developers Premium App.
drkhrsy said:
I'd just most likely restore the phone again and try root the phone again.
Click to expand...
Click to collapse
You don't need to do that, just redo the recovery.img
Sent using witchcraft via XDA Developers Premium App.
I was running CM9 and then went to MIUI and then back to CM9. Ever since I have not been able to do a proper update to the CM9. Got fed up with it and tried to roll it back to one of the Nandroid backups. It got stuck for hours. Pulled the battery. Tried to go through the process of installing CM9 again fresh. Used Darkside SuperWipe and it kept freezing on "Wiping Cache" and the same thing when I use CWM (v6.0.1.4)! I have attached two screen shots. It reads:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
Then when I ask it to format the cache it get frozen.
How can I fix the cache? I cannot boot into CM9 or anything for that matter. I just get the awesome little Cyan Dude and the warp background flying at me continually until I pull the battery. Can anyone help? Is there any way to get ADB to work with out turning on USB Debugging on the phone?
Same issue with Clockworkmod Recovery
Sorry to say I can't answer your question, but actually just downloaded cm9 and was trying to factory reset in order to prepare to flash it and ran into the same cache issue. I tried everything and still couldn't get around it, almost bricked my phone, got stuck in a loop. Hadn't even done anything yet, except download the cm9 Rom. Also freezes when trying to wipe cache and when trying to restore a backup when it gets to the cache. I'll be keeping an eye on your post, and Ill let you know if I figure anything out as well.
I hate to say it but... use TWRP. It looks and works better. Trust me.
Sent from my SGH-T989 using xda app-developers app
whatiznt said:
I hate to say it but... use TWRP. It looks and works better. Trust me.
Click to expand...
Click to collapse
I trust you but on the Team Win Recovery Project's changelog you can see that it has not been updated in almost a year! CWM is updated much more frequently and also I enjoy having the touch version! Very convenient.
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
jalight27 said:
Just downloaded cm9 and was trying to factory reset in order to prepare to flash it and ran into the same cache issue. I tried everything and still couldn't get around it, almost bricked my phone, got stuck in a loop. Hadn't even done anything yet, except download the cm9 Rom. Also freezes when trying to wipe cache and when trying to restore a backup when it gets to the cache. I'll be keeping an eye on your post, and Ill let you know if I figure anything out as well.
Click to expand...
Click to collapse
Thank you my friend. What you describe is exactly what happened to me. Tell me, what version of CWM Recovery do you have? Were you coming from stock? Which CM9 was it? Nightly, stable?
mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
Please pardon my ignorance as I am relatively new at all this. How do you downgrade CWM? I am unable to boot the phone into the ROM. Can it be done through Recovery? ODIN?
I've looked around but I can't find a download for 5.0.2.7-- at least not one that's labeled specifically for our phone. It can be done in many different ways, flashing via recovery or Odin would definitely work, just need to find the right file.
Same version as you've got. Was actually coming from Jedi Mind Trick v8 and was going with the nighty. I loaded a backup of my stock ICS, which of course froze during the restore once it got to the cache, but I let it sit for like 15 min or so and then reset it and surprisingly it loaded up fine despite the fact that I had to reset it during the restore. I'm trying to follow up with the advice these two guys gave me on my post (really the same thing they've told you). With my extremely limited knowledge in this field I'm still working it all out and trying to make sure I ask the stupid questions so as not to mess anything up, well at least not too bad, lol.
mintharis said:
I've looked around but I can't find a download for 5.0.2.7-- at least not one that's labeled specifically for our phone. It can be done in many different ways, flashing via recovery or Odin would definitely work, just need to find the right file.
Click to expand...
Click to collapse
Go into rom manager and scroll down to previous versions
VoiD_Dweller said:
Go into rom manager and scroll down to previous versions
Click to expand...
Click to collapse
I don't have ROM manager installed. Does it provide a tar that can be flashed via Odin?
Newer Recovery
Clockworkmod 6 doesn't need the Darkside tools anymore. I had a similar problem but it was causing my phone to lock up. Just try using the regular cache wipe and dalvik cache wipe and see if that works for you.
mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
I can confirm this, I have a samsung galaxy S II and I was having HUGE problems with the newer version of CWM. Cache would not clear at all even with darksides super wipe. My CM9 was stuck in a boot loop because I had forgotten to clear my cache and factory reset, and I was not able to do this at all, so i thought i was screwed.
However what i did was flash an older version of CWM (5.0.2.7) through odin, and BAM I was able to clear all my data with no problem and reflash CM9. Works perfectly now.
Pugnap00 said:
I can confirm this, I have a samsung galaxy S II and I was having HUGE problems with the newer version of CWM. Cache would not clear at all even with darksides super wipe. My CM9 was stuck in a boot loop because I had forgotten to clear my cache and factory reset, and I was not able to do this at all, so i thought i was screwed.
However what i did was flash an older version of CWM (5.0.2.7) through odin, and BAM I was able to clear all my data with no problem and reflash CM9. Works perfectly now.
Click to expand...
Click to collapse
Can you please provide a link for the 5.0.2.7 tar you flashed?
mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
CWM v6.0.1.4 has pretty much made my phone useless. When in Recovery I can't even scroll down or up. I even tried restarting my phone to downgrade but I have no response from my MENU, HOME, BACK or SEARCH button.
WORD OF ADVICE. PLEASE STAY AWAY FROM CWM v6.0.1.4.
EdwardLThompson said:
I was running CM9 and then went to MIUI and then back to CM9. Ever since I have not been able to do a proper update to the CM9. Got fed up with it and tried to roll it back to one of the Nandroid backups. It got stuck for hours. Pulled the battery. Tried to go through the process of installing CM9 again fresh. Used Darkside SuperWipe and it kept freezing on "Wiping Cache" and the same thing when I use CWM (v6.0.1.4)! I have attached two screen shots. It reads:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
Then when I ask it to format the cache it get frozen.
How can I fix the cache? I cannot boot into CM9 or anything for that matter. I just get the awesome little Cyan Dude and the warp background flying at me continually until I pull the battery. Can anyone help? Is there any way to get ADB to work with out turning on USB Debugging on the phone?
Click to expand...
Click to collapse
Simple Solution is that the Cache in your device is large, it has to be cleaned, For this use Darkside cache wipe. It Solves the problem.
suffuciently hungeom
mintharis said:
Can you please provide a link for the 5.0.2.7 tar you flashed?
Click to expand...
Click to collapse
Here you go,
Look at step 6, it will have links to the tar based on your carrier. Its actually 5.0.2.6, works just the same though.
http://theunlockr.com/2011/12/01/how-to-root-the-samsung-galaxy-s-ii-all-versions/
I hope this helps you!
That happened to me as well when I was going to update to CM10. The faq for CM10 says you need to update to a Touch version of CWM which ROM Manager really wanted to install the Touch version. CWM shows it's version 6 and the menus were different but when I was finally able to get a ROM to boot in Safe Mode it reported CWM as being version 5.x. I could not mount or dismount the Cache in CWM. ODIN brought it back to stock but I messed around with the partition checkbox and hard bricked it. Otherwise it looked as tho things would have been ok after using ODIN to start over.
Darkside's wipe wouldn't work (either version) in this case.
screw cwm im going to twrp
ok same thing happened to me..but there are files i need in the phone and i dont think i want to use cwm after this...so can i use odin to flash it to twrp and recover my files through the twrp usb mount?
(lol nvm, i flashed a older version of cwm through odin and then recovered my files then got twrp)
mintharis said:
I've been reading that CWM v6.0.1.4 is causing problems with our phone. Would advise downgrading back to 5.0.2.7 and use the darkside scripts to wipe. I haven't had an issue with this version since it was released (other than needing to use darkside scripts lol).
Click to expand...
Click to collapse
Like I said in my earlier post had your exact problem and did exactly what was recommend here, and it worked beautifully. Solved all my problems, no residual effects to speak of. Now I can flash my roms in peace.
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
Hello all just bought a new Samsung Galaxy SII from craigslist already rooted with 4.0.3 Jedi Mind Trick. After reading for what seems 4-5 hours i have been trying to put together how to properly without bricking switching it to 10.0.0 Stable as i use to use Cyanogenmod 2-3 years ago on my devices. Seem alot of things have changed and there is a cluster**** of stuff out there now. If you could direct me to a how to or show me how to do it i would greatly appreciate it!
Thanks all!
Assuming you have nothing personal to back up that you can't just download from google play or your google account again: download cyanogen 10 and it's gapps. reboot into recovery mode. factory reset, wipe data, wipe system, wipe cache, wipe dalvik. pick the install zip from sd card or so option, browse to cyanogen, then install gapps the same way. wipe dalvik again and reboot.
I was thinking of doing this myself JMT to CM10. I didn't think there was anything special to do same as flashing from any other ROM to CM10. If there is a special requirement I would think they'd post in in with the ROM post information.
Alawishis said:
I was thinking of doing this myself JMT to CM10. I didn't think there was anything special to do same as flashing from any other ROM to CM10. If there is a special requirement I would think they'd post in in with the ROM post information.
Click to expand...
Click to collapse
so I attempted to install it and got stuck on the boot logo for 20 minutes or so. So I bricked it lol... Anyway I just flashed it with Odin to 2.3.5 but the link to download file for root capabilities is broken. What can i do? Do i have to go to ics first before i reattempt to go to 10.0.0?
melvinator said:
so I attempted to install it and got stuck on the boot logo for 20 minutes or so. So I bricked it lol... Anyway I just flashed it with Odin to 2.3.5 but the link to download file for root capabilities is broken. What can i do? Do i have to go to ics first before i reattempt to go to 10.0.0?
Click to expand...
Click to collapse
honestly - i backed up everything to my external and then formatted the internal when i went from TW to AOSP for the last time. well worth it. nice folder clean up and then you can just manually take all the stuff you want back.
and you should just be able to odin on cwm or twrp - then flash the rom of your choice.
new ion? said:
honestly - i backed up everything to my external and then formatted the internal when i went from TW to AOSP for the last time. well worth it. nice folder clean up and then you can just manually take all the stuff you want back.
and you should just be able to odin on cwm or twrp - then flash the rom of your choice.
Click to expand...
Click to collapse
trying to look up how to do that now .... Searching the forum now... Might you be able to tell me real quick how? I already Downloaded the 5.2 file they suggest to use but can't find a working toturial that is just for flashing the cwm.
melvinator said:
so I attempted to install it and got stuck on the boot logo for 20 minutes or so. So I bricked it lol... Anyway I just flashed it with Odin to 2.3.5 but the link to download file for root capabilities is broken. What can i do? Do i have to go to ics first before i reattempt to go to 10.0.0?
Click to expand...
Click to collapse
If you get stuck at the boot logo, it's called a soft brick. You don't have to use ODIN or go back to ICS. Just make sure the ROM zip you downloaded isn't corrupt (check the size/m5d if possible), wipe everything, and reboot into recovery to try installing again.
arcsine said:
If you get stuck at the boot logo, it's called a soft brick. You don't have to use ODIN or go back to ICS. Just make sure the ROM zip you downloaded isn't corrupt (check the size/m5d if possible), wipe everything, and reboot into recovery to try installing again.
Click to expand...
Click to collapse
I already used Odin to go back to 2.3.5
Btw I appreciate the help
My woman's is waiting that I fail to say I told you so -_-
melvinator said:
I already used Odin to go back to 2.3.5
Btw I appreciate the help
My woman's is waiting that I fail to say I told you so -_-
Click to expand...
Click to collapse
You won't fail. Follow the guidelines step by step. Print it out, make notes. Anything. Read. The step by step guide works... that'll get you with cwm. Then, you can flash the zip you will put on your phone... either a SU zip or just a rooted ROM. Follow flashing instructions.
Just realized - you'll be way better off if, once you have cwm on, just format the internal ONCE YOU HAVE A ROM ON AN EXTERNAL SD CARD. then flash CM10. THEN you'll have a fresh AOSP install.
Sent from my SAMSUNG-SGH-T989 using xda premium
new ion? said:
You won't fail. Follow the guidelines step by step. Print it out, make notes. Anything. Read. The step by step guide works... that'll get you with cwm. Then, you can flash the zip you will put on your phone... either a SU zip or just a rooted ROM. Follow flashing instructions.
Just realized - you'll be way better off if, once you have cwm on, just format the internal ONCE YOU HAVE A ROM ON AN EXTERNAL SD CARD. then flash CM10. THEN you'll have a fresh AOSP install.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
how long does the boot logo stay on for?
Had 2.3.5 - rooted via odin and have recovery 5.2.6 - did everything in proper order and wiping properly.
what am i skipping here? Still spinning taunting me, wish there was a way it would tell me if i did something wrong.
melvinator said:
how long does the boot logo stay on for?
Had 2.3.5 - rooted via odin and have recovery 5.2.6 - did everything in proper order and wiping properly.
what am i skipping here? Still spinning taunting me, wish there was a way it would tell me if i did something wrong.
Click to expand...
Click to collapse
Go back, format system, and then reinstall.
Sent from my SAMSUNG-SGH-T989 using xda premium
Update your recovery to twrp or cwm 6+ and don't use dark side scripts
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Please excuse my harshness but this is not as hard as many make it seem. I would say if it takes you more than a couple attempts maybe it is just not for you. I only say this because I would hate to see you mess up your phone. Now if you think a bootloop is a brick then we need to do things at a slower pace with you.
If you already have your phone rooted then
1.download goomanager from the playstore and then
2.open it up and allow it to grant permission from CM
3.hit menu button while goo manager is open
4.click on install OpenRecoveryScript
5.let it do its thing
6.reboot into your new TWRP recovery
7.Wipe/Data Factory Reset
8.Flash Rom
9.Flash Gapps
10.Reboot
You can throw in a backup of files somewhere in there if you like.... Your choice
melvinator said:
how long does the boot logo stay on for?
Had 2.3.5 - rooted via odin and have recovery 5.2.6 - did everything in proper order and wiping properly.
what am i skipping here? Still spinning taunting me, wish there was a way it would tell me if i did something wrong.
Click to expand...
Click to collapse
I had a bootloop when using CWM v6.0.1.5. So a friend of mine told me he had success with CWM v6.0.1.5 Touch. So I switched to the touch recovery and... SUCCESS.
Here's the link to CWM touch and non-touch:
http://forum.xda-developers.com/showthread.php?t=1893464
A boot loop could mean a bad download or bad flash but it is most definitely NOT a bricked device. All you needed to do was get a fresh download and move it to your SD card by mounting it in recovery. Then, wipe EVERYTHING but the SD. EVERYTHING. Then flash the ROM, Gapps and whatever radio. I go from CM to AOKP to other random TW roms all the time and never have issues.
The 2 best recoveries are twrp or my favorite because I'm used to it is cwm 6.0.1.5. http://forum.xda-developers.com/showthread.php?t=1844637
Also if your phone boot loops don't freak out' just either reboot to see if that works out first and if not reboot into recovery. Also with these new recoveries do not use dark side scripts.
Factory reset
Format system
Format cache
Format data
Flash ROM
Flash gapps
Reboot and enjoy
Sent from my SAMSUNG-SGH-T989 using xda premium
This did it!
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Sorry for the necro on the thread, but I didn't want it to be stated I didn't look around some either.
I am going from JMT to CM and want to make sure it's as seamless as possible. I use CWM and usually usually use darkside complete wipes, but I read in a previous post not to use darkside. Is there a reason for this? I can't see why this wouldn't work as it's just a wipe.
Also I use Titanium Backup. Is it possible to backup my apps and data and restore them since its not TW any longer? I want to be able to restore as much of my data as possible and make sure I don't lose it.
P.S. - If thread necroing is not appreciated, I apologize.
I really hate to start a new thread but I really can't find a reason/solution to this issue. It's just as the title says. I tried flashing the MIUI ROM just as any ROM and got a failed error. Then went to do my nandroid restore and it just hangs on the splash screen (boot screen). Anyway I thought there could be a bad download so I took out the SD and redownloaded synergy on my laptop, then put it back in the phone and nothing but the nandroid should let me restore. I even tried moving the files to the internal SD and nothing. The only thing I can think of is to Odin back to stock? Is it the same method as rooting? I'm sure I can find that out, but I'm just confused why it seems TWRP doesn't want to work. Thanks for any help, it's 4 a.m. here and I'm dog tired.
Are you on the latest TWRP?
If all else fails you could go back to stock and root again.
DarkManX4lf said:
Are you on the latest TWRP?
If all else fails you could go back to stock and root again.
Click to expand...
Click to collapse
I think so. Yeah, just didn't want to go throught it all, and didn't know why.
jtadak said:
I think so. Yeah, just didn't want to go throught it all, and didn't know why.
Click to expand...
Click to collapse
Can I just reflash recovery from the state I'm in, or do I still need to unroot? I've moved some of my files to the ext SD within recovery but some things won't move and I really don't want to wipe it.
jd14771 said:
Try wiping everything 3X, then go to the reboot menu, and reboot system, wipe both the cache and dalvik cache and try to restore.
Click to expand...
Click to collapse
Do you mean reboot recovery? I can't reboot system. Sorry, not trying to split hairs, just trying to be specific.
Odin back to stock seems like the best option.
Sent from a galaxy note 2 far far away...
are you able to flash a different rom, say a stock rom? It's possible you got a corrupted TWRP download.
Since they just released another update 2.4.3, you might want to try and download the zip file, wipe cashe and davick (may want to do it three times). Reboot back into TWRP 2.4.3 and see if it gives you some better luck.
I've had Nandroid backup that didn't work for whatever reason. I didn't test it prior to needing it, and got burned. It just wouldn't show up in the restore menu.
On a side note, what error did you get when you tried flashing MIUI?
Try rebooting recovery when you are in recovery already once before flashing/restoring anything anything.
mexiking713 said:
Odin back to stock seems like the best option.
Sent from a galaxy note 2 far far away...
Click to expand...
Click to collapse
Yes, that's what I did. I'm just bummed I had to wipe storage. Oh well, it's inevedible... I dig that sig though, with phone line up.
lovekeiiy said:
are you able to flash a different rom, say a stock rom? It's possible you got a corrupted TWRP download.
Since they just released another update 2.4.3, you might want to try and download the zip file, wipe cashe and davick (may want to do it three times). Reboot back into TWRP 2.4.3 and see if it gives you some better luck.
I've had Nandroid backup that didn't work for whatever reason. I didn't test it prior to needing it, and got burned. It just wouldn't show up in the restore menu.
On a side note, what error did you get when you tried flashing MIUI?
Click to expand...
Click to collapse
I tried multiple ROMs, but not a stock one. Hmm, I was on 2.3.2.3. I did'nt get a special error, just said a red message saying failed.
Evo_Shift said:
Try rebooting recovery when you are in recovery already once before flashing/restoring anything anything.
Click to expand...
Click to collapse
Tried that. Did'nt work.
jd14771 said:
no, i meant reboot system, the recovery will warm you that there is no os installed but go fourth with it, it will turn off and reboot back to recovery. at that point in time, wipe cashe/dalvik cache and try to install.
Click to expand...
Click to collapse
Ok, I was'nt sure. I just went back to stock. I just wanted to know what exactly was going on and why.
The only thing different on my phone is I got a 32 gig SD card. I transfed some of my files a couple days before doing anything of this. That's the only thing I can think of. Even after root/unroot it STILL won't do my nandroid restore. I had so much time and work into the apps I set up, games, ect. Really freakin sucks. I even went into the the TWRP backup folder and made sure the backup files were there before doing anything. I never even got to flash many ROMs, I kinda just stayed on Jellybomb.
I had the uTorrent app installed and I noticed that it changed a lot of files with the "u" in front that the uTorrent app has. Anyone know why that is?
Sent from my SPH-L900 using xda app-developers app
This is what it did to a lot of my files. But not the ones I tried to flash.
Sent from my SPH-L900 using xda app-developers app