Related
Need help I installed midnight rom v2.2 today I did the recommended wipes as instructed. I had cwm 4.0.1.5 and did my backup twice. When I installed midnight every thing went good but then during reboot it just rebooted back into cwm 5.0.2.3 I've pulled the battery and nothing. I can't even get into my restore files ......did flashing the new cwm erase the backup?????I'm stuck what do I do???????
in the older 4.x cwm backups are on the internal sd card
in the newer 5.x cwm backups are on the external card.
(may be the other way around)
as long as you didnt format the actual sd cards your alright the backups are still there.
i think from cwm you can mount both to a pc and just copy the clockwork folder from one to the other. though i may be wrong.
might be easiest to odin a kernel that has the old 4x cwm
check the dev section there are a few floating around.
edit this kernel has the old cwm as both a flashable zip from inside cwm
and a .tar from odin
http://forum.xda-developers.com/showthread.php?t=1284092
sometimes it takes more than 1 wipe/format to fully clear or you could have a bad download.
there are also a few full system .tar files that will get you back up and running on a stock system.
Thanks I used Odin to reflash a kernel with the cwm I needed and was able to restore. Ill try to flash midnight against knowing I'm this now!
no prob.
may think about copying the backups to the other sd card too.
that way they are still there even on the newer 5x cwm if you have a problem.
Would it work if I upgrade to zedomax v6.02 it comes with cwm5 same as what comes in midnight rom2.2 that way I don't go through the same problem if it happens again?
it should but your best bet would be to update to that kernel with cwm5
then create a new backup before continuing.
If your phone boots into CWM after a battery pull, just select reboot system now and that will boot the phone up. I see that on my phone as well at times. Not sure what causes it but that always fixes it for me.
ptfdmedic said:
If your phone boots into CWM after a battery pull, just select reboot system now and that will boot the phone up. I see that on my phone as well at times. Not sure what causes it but that always fixes it for me.
Click to expand...
Click to collapse
I tried that about 5 times it just kept booting into cwm. Maybe a bad download im not sure, but ill try it again and see if it works this time around. Thanks!
Problem solved i just reflashed the rom and it booted up just fine. It works great. Very good rom!
Sent from my SPH-D710 using XDA App
Ok, so I've been flashing Roms since I first had the G1 but my step sons Galaxy S II is giving me fits as of late.
I've been working on it for over 2 days now and can not figure the problem even after reading through all the how to's and individual rom threads. I initialy rooted his phone back in April/May and had a early ICS phandroid rom on it. However I wanted to move him to JB. I've done the customary wipe data/cache but no matter what JB rom I flash it goes into what I believe is a bootloop. I've read several places it been said to let sit after flashing for 10 minutes so I let sit for 20 and it was still on boot (but no obvious point where you can tell it's looping).
When I went to restore his backup that would no longer boot at all, just a blank screen. So long story short I restored everything to stock then updated to ICS through keis. and tried the process again thinking it might need updated firmware/radio. Same thing happened and I had to restore stock and update through keis again. I am now at a complete loss as I update my phone (One S) and wifes (GSIII) atleast once a week on nightlies.
The one thing that I thought was odd is both on the original 2.3.6 and now 4.0.4 when I go into settings at search for update i get a message saying "no firmware". Not sure if that means anything but it didn't sound right to me.
Any help or suggestions would be overwhelmingly appreciated.
You will get different methods on here but for starters what recovery are you running. Thats problem 1 I guarantee for your bootloop. I use TWRP 2.3 which can be found by downloading goo.im and flashing it from the menu screen. You can also go to the forum here in development for the zip file.
When using TWRP or any touch recovery do not use the wipe scripts. Lets start there.... Since the method to flashing is basically the same all over its just the wiping procedure with the wrong recovery can be tricky
I'm using CWM 6.0.3 I believe he's at school so I don't have the phone to know the exact CWM version. It's also not the touch version. How should I go about wiping data/cache for his phone then? I've never used TWRP but going to assume if you've used one recovery it's pretty similar or self explanatory.
jhenson496 said:
I'm using CWM 6.0.3 I believe he's at school so I don't have the phone to know the exact CWM version. It's also not the touch version. How should I go about wiping data/cache for his phone then? I've never used TWRP but going to assume if you've used one recovery it's pretty similar or self explanatory.
Click to expand...
Click to collapse
I personally prefer that recovery and I'm running a cm 10 on my phone with no issues at never had anything. Yes it's rather simple to put on an even if you want to try the CWM touch recovery by all means go ahead
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Ok, I'll give TWRP a try when he gets home. I guess my next question would be is there a different way of wiping then with other phones?
Do I need the recovery to be touch (never heard of a recovery needing touch version)
Anything different then wiping dalvik, cashe and data? Also I've look around and do not see an actual JB radio. So I'm assuming the ULVH1 radio would work for ICS & JB.
I appreciate your help with this btw.
jhenson496 said:
Ok, I'll give TWRP a try when he gets home. I guess my next question would be is there a different way of wiping then with other phones?
Do I need the recovery to be touch (never heard of a recovery needing touch version)
Anything different then wiping dalvik, cashe and data? Also I've look around and do not see an actual JB radio. So I'm assuming the ULVH1 radio would work for ICS & JB.
I appreciate your help with this btw.
Click to expand...
Click to collapse
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
Click to expand...
Click to collapse
There is a lil something from the TWRP thread about the new recovery... basically its built off a JB which improves the features being used like wipes, fix permissions, backups etc. Its not that its solely touch but it was the direction most if not all recoveries have gone to basically preserve that power button and vol keys of our phones. It kinda makes sense...
So with updated technology just came a better way to use a recovery and since the SGII originally had wiping issues TWRP on this phone is made solely for this phone which cut out alot of issues. Now if you prefer a non touch may I suggest 5.0.2.7 w/darkside cache wipes and you would be ok as well. Honestly though I dont think anyone would be upset with TWRP its quite nice
TWRP Link - http://forum.xda-developers.com/showthread.php?t=1768742
Darkside Wipes - http://forum.xda-developers.com/showthread.php?t=1477955 (Only use with CWM 5.0.2.7)
CWM Touch(Latest) - http://forum.xda-developers.com/showthread.php?t=1844637
I would switch to Clockwork Recovery 5.0.2.7 which you can find in ROMmanager app. Thus, you can use TDJ's Darkside super wipe and cache wipe scripts which install very clean.
Finding his scripts might be a bit of a challenge but they are out there. I have them but not sure how i can get them to you... my dropbox isnt working.
if you do find those scripts, then the flash is simple...
reboot into recovery
Flash TDJ's Darkside SUPERWIPE
Flash your ROM or Gapps depending on what that OP says goes first
Flash Darkside CACHE wipe
Reboot, let is settle 10 mins reboot
That works with 5.0.2.7 where you have to mash the side buttons.. Ive installed a few JB and ICS roms this way, worked well for me.
Hit thanks if i helped
abesgs2 said:
I would switch to Clockwork Recovery 5.0.2.7 which you can find in ROMmanager app. Thus, you can use TDJ's Darkside super wipe and cache wipe scripts which install very clean.
Finding his scripts might be a bit of a challenge but they are out there. I have them but not sure how i can get them to you... my dropbox isnt working.
if you do find those scripts, then the flash is simple...
reboot into recovery
Flash TDJ's Darkside SUPERWIPE
Flash your ROM or Gapps depending on what that OP says goes first
Flash Darkside CACHE wipe
Reboot, let is settle 10 mins reboot
That works with 5.0.2.7 where you have to mash the side buttons.. Ive installed a few JB and ICS roms this way, worked well for me.
Hit thanks if i helped
Click to expand...
Click to collapse
My friend I linked the zips in the post right above yours
playya said:
CHANGELOG for 2.3.0.0:
There is a lil something from the TWRP thread about the new recovery... basically its built off a JB which improves the features being used like wipes, fix permissions, backups etc. Its not that its solely touch but it was the direction most if not all recoveries have gone to basically preserve that power button and vol keys of our phones. It kinda makes sense...
So with updated technology just came a better way to use a recovery and since the SGII originally had wiping issues TWRP on this phone is made solely for this phone which cut out alot of issues. Now if you prefer a non touch may I suggest 5.0.2.7 w/darkside cache wipes and you would be ok as well. Honestly though I dont think anyone would be upset with TWRP its quite nice
TWRP Link - http://forum.xda-developers.com/showthread.php?t=1768742
Darkside Wipes - http://forum.xda-developers.com/showthread.php?t=1477955 (Only use with CWM 5.0.2.7)
CWM Touch(Latest) - http://forum.xda-developers.com/showthread.php?t=1844637
Click to expand...
Click to collapse
Just saw that last part by Playa, sorry didnt mean to kang you haha... but hes got it down ^^^
I have always used CWM and currently use the touch version. I have had some problems with CWM lately like the no media mess up with ROM manager. And the other day when going to 4.2. Things I like about TWRP is the keyboard and file manager as well as being able to update to the newest touch recovery through goo manager. So before making the switch from my staple recovery is there anything I should know. I have heard TWRP may have issues with Cyanogen and might be a little slow?
Sent from my toroplus using xda app-developers app
I still use CWM, it does the job for me. Others swear by TWRP so you're better off trying them both
EddyOS said:
I still use CWM, it does the job for me. Others swear by TWRP so you're better off trying them both
Click to expand...
Click to collapse
Same here. Although the /0/ thing has me seriously considering switching to TWRP.
I don't mind trying both but I like all my backups to be easily accessible within my recovery. Plus I don't think I would run into anything for a while and don't want to invest making all my backups in TWRP then find out an issue that someone may have already encountered before me. Sorry of that comes off weird. I started this thread more as an opinion on what converts maybe like or dislike about TWRP.
Sent from my toroplus using xda app-developers app
I've had CWM for a long time(since the galaxy S days) but when i got my gnex off on ebay, It had the TWRP recovery installed, after trying it I decided that I will never go back to CWM. It's just a matter of user preference really, for all those years that I've used CWM I've never had any single issues with it. I can say the same for TWRP after using it for almost a year now.
Few things I love about TWRP:
-Swipe to confirm Install
-Full touch screen with big buttons(i know CWM has touch screen version too but I was only able to try the semi touch screen version and did not really like it)
-File Manager
-Ability to compress(don't know if CWM can do this but I've included it too) and rename/name backups
-You can queue the zips you want to install(maximum of 10), no more going back and forth between sdcard directories and recovery menus
Those are the ones that I could think of at the moment. I'm sure there's a lot more else to list down. If you ask me TWRP is a bit more user friendly because of the UI
Just switched to TWRP a couple of months ago, after having always used CWM. No real issues with CWM. I have just found TWRP to be more user friendly for me.
TWRP have more features than CWM, for example, file managing and the ability to name backups. Thats a great advantage if you ask me.
Recently switched to TWRP. Loving it so far. I especially like the Advanced -> ADB Sideload function so I can superwipe and flash without worrying about the internal storage.
I've always used CWM, but like others, because of /0/, I'm considering trying twrp. I just made a backup with CWM 6.0.1.9, but now that i've found it, i'm unsure of how to copy it to my computer. That is, my mac recognizes /data/media/0 via android file transfer, but i cannot transfer the backup from here. And I really dont want to move the backup and blobs folders twice just for the sake of copying. Any ideas? Also, whatever happened to navbar arrows in cwm touch?
I switched to TWRP because of the excessive number of blobs made by CWM.
It's a real pain having to copy over 2,000 files and folders over MTP to a computer.
I like to keep the most recent backup on my Gnex, while moving the older backups to my computer.
Consider this. I used cwr on my droid X and it worked fine. The day I got my Gnex and rooted it I ignored CWR and immediately installed TWRP. Never looked back. I always hear people say "I switched from CWR to TWRP and its great". Not once have I heard it the other way
Sent from my Galaxy Nexus using Tapatalk 2
I'm preaching to the choir here, I know, but one of the main reasons for rooting is a custom Recovery and the benefits that come with that. Both CWM and TWRP are included in the Note 2 Toolkit, but after an incident yesterday and over an hour of XDA reading since, I honestly don't know which Recovery to use anymore.
CWM EPIC-FAILED me yesterday when just trying to flash stock MA5 over stock LJC. I did a Nandroid, a full wipe, flashed the MA5 Firmware, flashed Stock Deodexed MA5, reflashed the MA5 firmware (like the OP said to do), rebooted, and BARF. Looping device activation, and after I chased my tail around in that for 4 or 5 cycles, it ended up in boot loop. I could get into Recovery as well as Download Mode, but restoring any of my six Nandroids via Recovery did not work and I also determined that CWM was wiping anything.
So I searched and found where another Note 2 user had the same wiping problem with CWM and was told to use TWRP. So I Odin'ed TWRP over replacing CWM, wiped everything via TWRP, and then Odin'ed CWM back over so I could (hopefully) do a restore. Soft brick...that looked scarily like a hard brick for a second or two as my phone would do NOTHING. I was finally able to convince it into Download Mode, so I flashed everything back to unrooted stock. Thankfully, I had a Titanium Backup of all my apps/data, but I still had to reconfigure the system settings all over again since I don't use TB for that (because...y'know...that's what Nandroids are for).
By the time that was all said and done it was 3AM, so this morning I immediately searched the forums for Recovery issues, and I have to say that I'm surprised and disappointed with what I've found. There doesn't seem to be a reliable Recovery available for the Note 2! I've found threads with far more problems with TWRP than CWM, but the few I found with CWM are real deal-killers like what I encountered (can't wipe, can't restore).
I'm not being a whiner -- it's a legit question. On all my previous and other current devices, I had my choice between at least two sometimes three or even four rock-solid Recoveries. Is the Note 2 really without a solid Recovery option? Because if it is, then my flashing days are pretty much over except during the rare times where I can potentially be without a phone for 24-48 hours in case a CLUSTER happens like my latest experience. Given my CWM issues, I've now switched to TWRP, but after reading everything in the forums, I can't say that I feel very warm/fuzzy about it.
internetpilot said:
I'm preaching to the choir here, I know, but one of the main reasons for rooting is a custom Recovery and the benefits that come with that. Both CWM and TWRP are included in the Note 2 Toolkit, but after an incident yesterday and over an hour of XDA reading since, I honestly don't know which Recovery to use anymore.
CWM EPIC-FAILED me yesterday when just trying to flash stock MA5 over stock LJC. I did a Nandroid, a full wipe, flashed the MA5 Firmware, flashed Stock Deodexed MA5, reflashed the MA5 firmware (like the OP said to do), rebooted, and BARF. Looping device activation, and after I chased my tail around in that for 4 or 5 cycles, it ended up in boot loop. I could get into Recovery as well as Download Mode, but restoring any of my six Nandroids via Recovery did not work and I also determined that CWM was wiping anything.
So I searched and found where another Note 2 user had the same wiping problem with CWM and was told to use TWRP. So I Odin'ed TWRP over replacing CWM, wiped everything via TWRP, and then Odin'ed CWM back over so I could (hopefully) do a restore. Soft brick...that looked scarily like a hard brick for a second or two as my phone would do NOTHING. I was finally able to convince it into Download Mode, so I flashed everything back to unrooted stock. Thankfully, I had a Titanium Backup of all my apps/data, but I still had to reconfigure the system settings all over again since I don't use TB for that (because...y'know...that's what Nandroids are for).
By the time that was all said and done it was 3AM, so this morning I immediately searched the forums for Recovery issues, and I have to say that I'm surprised and disappointed with what I've found. There doesn't seem to be a reliable Recovery available for the Note 2! I've found threads with far more problems with TWRP than CWM, but the few I found with CWM are real deal-killers like what I encountered (can't wipe, can't restore).
I'm not being a whiner -- it's a legit question. On all my previous and other current devices, I had my choice between at least two sometimes three or even four rock-solid Recoveries. Is the Note 2 really without a solid Recovery option? Because if it is, then my flashing days are pretty much over except during the rare times where I can potentially be without a phone for 24-48 hours in case a CLUSTER happens like my latest experience. Given my CWM issues, I've now switched to TWRP, but after reading everything in the forums, I can't say that I feel very warm/fuzzy about it.
Click to expand...
Click to collapse
I used the MA5 One Click and it flashed fine. Then I downloaded the Note II Took kit and flashed TWRP using Mobile Odin and it worked fine also.
Amigo, bad versions happen even with the best software.
Further MA5 is a leak and not official stable code....use it at your own risk.
MikeyLee said:
I used the MA5 One Click and it flashed fine. Then I downloaded the Note II Took kit and flashed TWRP using Mobile Odin and it worked fine also.
Click to expand...
Click to collapse
All that is risky business if you don't have a working Recovery to restore from. Have you tested that? You might want to.
I've been a flashing fool on all my other Android devices, and always been able to work my way out of any/all problems with a proper backup. I don't have that same level of confidence with the Note 2. Sure, I can always ODIN back to stock unrooted and start all over, but I don't have time for that and...really...who wants to do that?
Skripka said:
Amigo, bad versions happen even with the best software.
Click to expand...
Click to collapse
Well, that's true, but the TWRP issues span numerous versions, and since my backups were in CWM, I probably tried just about every version of CWM that's been released for the Note 2, since all I wanted to do was restore even just one of my six Nandroids (a basic function of Recovery). Even after restoring everything to stock and re-rooting (including the latest version of CWM), I still couldn't even restore my very first Nandroid (or any of the other five). Brand new latest tech phone, all this development going on, and unless I have the time to restore back to stock, re-root, reconfigure, etc., then I simply can't risk trying any it. This all by itself makes my ancient EVO4G the better phone, which is just ridiculous.
Hence my question, is there a reliable Recovery for the Note 2? In my experience, there isn't, but I would absolutely love to be wrong.
Skripka said:
Further MA5 is a leak and not official stable code....use it at your own risk.
Click to expand...
Click to collapse
My complaint isn't with MA5 at all. I've had plenty of failed flashes over the years on my devices for a variety of reasons including myself, but there's always been an easy way around any issue by simply restoring with Recovery.
I had some similiar but smaller problems and reluctantly flashed CWM 6.0.2.5 (I think) through the CWM Rom Manager app. I've gone through the app do backups, installs, etc and it has worked great. I also use Rom Toolbox and it doesn't like that recovery sometimes, but otherwise it's been good.
Sent from my SPH-L900 using xda app-developers app
I've only used TWRP since I got the phone in October.
Not even 1 problem yet so I recommend TWRP.
Sent from my SPH-L900 using xda premium
You are aware the twrp is not compatible with cwm backups? Also did you rename your cwm backup,( ive corupted my own backups through this) ?
Sent from my SPH-L900 using xda app-developers app
AndroidStephen said:
I had some similiar but smaller problems and reluctantly flashed CWM 6.0.2.5 (I think) through the CWM Rom Manager app. I've gone through the app do backups, installs, etc and it has worked great. I also use Rom Toolbox and it doesn't like that recovery sometimes, but otherwise it's been good.
Click to expand...
Click to collapse
Have you tried a restore yet? I didn't have any problems with CWM until I noticed it wasn't wiping and then none of my restores worked either.
devynbf said:
I've only used TWRP since I got the phone in October.
Not even 1 problem yet so I recommend TWRP.
Click to expand...
Click to collapse
Despite so many posts about problems with TWRP, I decided anything had to be better than what I was encountering with CWM, so I gave it several test backups and restores today, as well as wipes and flashing. Everything went without a hitch except that I encountered the "Unfortunately, Chameleon has stoppped" message, but that's was because things were so convoluted with LJC, LK8, and MA5 on my device. I finally got everything cleaned up and back on running LJC, and it would seem that I have some reliable, restorable backups now. I guess only time will tell.
irule9000 said:
You are aware the twrp is not compatible with cwm backups? Also did you rename your cwm backup,( ive corupted my own backups through this) ?
Click to expand...
Click to collapse
Of course -- this is why I had to use TWRP to wipe (when CWM wipe wasn't working), and then re-flash CWM so I could try to restore my CWM backups. I don't get any error messages when trying to do a CWM restore -- it runs through the whole restore process (taking as long as it should), but then when I reboot, I have running exactly what I had before the restore. I think my problem is more of a wipe issue than a restore issue, but it could also be a combination of both.
Don't really know who to report the problem to since there doesn't seem to be a CWM thread for the Sprint Note 2.
Anywho, it looks like I'll be going with TWRP (not that I have much choice). Unfortunately, this means that I'm now running three different recoveries on my devices -- CWM on the Nooks, Amon Ra on the Acer A500, and now TWRP on the Note 2.
I've had TWRP running flawlessly on my last device (Evo 3D) and my GNII. I'll continue to use it unless something better comes along. Its always been solid for me.
Sent from my Mackified Galaxy Note II using XDA Premium.
If you're having the chameleon error, thats not because twrp.
Go to sesrch and look for the EviL KoNCEPTz and garwynn fix for chameleon.
Theres a flashable zip that fixes the chameleon errors.
Sent from my SPH-L900 using xda premium
---------- Post added at 11:35 AM ---------- Previous post was at 11:33 AM ----------
Here.
Go to this page and flash the zip file on here for the chameleon fix.
http://forum.xda-developers.com/showthread.php?t=2086769
Sent from my SPH-L900 using xda premium
TWRP has never failed me on any device from ego to evo3d to evo 4g lte and finally my note 2. Stick with twrp and make your backup with twrp so it actually restores Just my input but twrp shouldn't give any problems.
I posted earlier that CWM had been working for me... well, today I tried to do a restore and got an error stating the md5 didn't match, so no go. Said the same thing for 3 seperate back-ups, and I was trying to do the restore with the same app that made the back-up. Soooo... TWRP, here I come.
Sent from my SPH-L900 using xda app-developers app
devynbf said:
If you're having the chameleon error, thats not because twrp.
Go to sesrch and look for the EviL KoNCEPTz and garwynn fix for chameleon.
Theres a flashable zip that fixes the chameleon errors.
Sent from my SPH-L900 using xda premium
---------- Post added at 11:35 AM ---------- Previous post was at 11:33 AM ----------
Here.
Go to this page and flash the zip file on here for the chameleon fix.
http://forum.xda-developers.com/showthread.php?t=2086769
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Thanks -- I did figure out that it had nothing to do with TWRP, but I found a thread on another forum that only had three posts on it (a lot less to wade through) and a different solution where you simply replace the Chameleon.apk file. Since I was running (not walking) back to LJC from MA5, it worked. I'll just wait for Samsung/Sprint to release an official update. The only thing I got out of LK8 and MA5 was soft-bricked phone and Chameleon/registration headaches.
I did some more testing with TWRP and it's looking good, so I'll just stick with it.
AndroidStephen said:
I posted earlier that CWM had been working for me... well, today I tried to do a restore and got an error stating the md5 didn't match, so no go. Said the same thing for 3 seperate back-ups, and I was trying to do the restore with the same app that made the back-up. Soooo... TWRP, here I come.
Click to expand...
Click to collapse
Y'know, I'm a very forgiving man when it comes ROMs, kernels, and other hacks to my phone, but I freely admit to being a demanding little whiny baby when it comes to Recovery -- it needs to work. Period. When it doesn't that makes my tech life hell. TWRP has been working for me fine over the past couple days of testing things, so I'm sticking with it it. I don't know why there are so many posts here with TWRP issues, but so far I haven't had any through multiple wipes, backups/restores, flashes, etc. Usually when I try to get something to break it breaks, but so far I haven't been able to do that with TWRP.
When I originally rooted CWM was installed. I then went to install the upgraded stock but had problems as CWM did not do a proper wipe. I then installed TWRP and have not had any problems.
Prior to the Note II I was using the original EVO 4G. I had CWM originally installed but again had issues with the wipe. I wound up using AmonRa Recovery which I loved. I wish there was one like it for the Note II as it was also able to restore nandroid backups made by CWM.
Doc
Yesterday I flashed a ROM for the first time. I went with CM 10.1 WFTN. I went from a problematic stock 4.0.4 FH13 build so I was loving my new ROM except I can't get MMS to work. I tried to edit build.prop to configure my APN to work. When I went to reboot it would show the Samsung Galaxy S2 logo splash then it would go to a black screen and not boot. I was terrified that I might've bricked my phone. I pulled battery and attempted to boot into recovery and was ecstatic it did. I wiped data wiped cache wiped system and installed CM10.1 and Gapps and now I'm okay. I think? Not sure what caused the no-boot. My questions are:
1) did I handle the situation correctly or should I have restored to my FH13 Nandroid backup?
2) Is having my Nandroid backup and having CWM custom recovery the only preventive measures I need to take to save myself from any future headaches or are there other things I should learn/know?
It was most likely the change before the reboot. I have never edited the apn so I will say maybe that was it. But yes you handled it correctly.
Sent from my SPH-L900 using Tapatalk 2
hackaveli said:
Yesterday I flashed a ROM for the first time. I went with CM 10.1 WFTN. I went from a problematic stock 4.0.4 FH13 build so I was loving my new ROM except I can't get MMS to work. I tried to edit build.prop to configure my APN to work. When I went to reboot it would show the Samsung Galaxy S2 logo splash then it would go to a black screen and not boot. I was terrified that I might've bricked my phone. I pulled battery and attempted to boot into recovery and was ecstatic it did. I wiped data wiped cache wiped system and installed CM10.1 and Gapps and now I'm okay. I think? Not sure what caused the no-boot. My questions are:
1) did I handle the situation correctly or should I have restored to my FH13 Nandroid backup?
2) Is having my Nandroid backup and having CWM custom recovery the only preventive measures I need to take to save myself from any future headaches or are there other things I should learn/know?
Click to expand...
Click to collapse
The problem most likely came from the ics to jb transition. Before flashing CM, op says wipe everything except sd card, so if you didn't do that, that may have caused the boot loop too. Having a good backup is crucial, but if your fh13 is problematic, I'd find a good stock that works flawlessly as my backup. That way, in a pinch, you will always have a working backup. Secondly, mms on wftn has began an issue for others as well, just read the thread. And changing build prop is tricky, you're better off trying to change it using the voice dialer. I would always keep a copy of Chris41g's EL26 cwm in both tar and zip form saved to both internal and external drives of your phone. And invest in mobile Odin pro. And have Odin on your laptop as well as the latest Sammy drivers. And have fun!
Edit: but no, having cwm in and of itself will not 100% protect you from bricking. Reading, reading, reading, and asking the right questions will go just as far! Good luck.
Sent from my SPH-D710 using xda premium