Related
Maybe this is by design and I'm just missing something. I got a new e4gt and proceeded to root it using instructions found on epic4gtouchroot.com. Basically I used odin to flash a stock EL29 ROM and then install team Rogue's CWM.
All went well with this process so I proceeded to the next step, which was to download and install a custom ROM. I installed the VeNuM ICE 5.5 since I'm a comic book nerd as well as a computer geek.
This wasn't my first time rooting. I've been rooting my EVO for a year of so, and I've rooted my Wife's Nook Tablet too, so I was a bit shocked to see that the Team Rogue CWM recovery program went bye-bye after flashing the VeNuM ROM.
I downloaded ROM manager and tried to flash the latest CWM recovery program from there, but that dind't work. I haven't tried to download the touch recovery, but I was able to reinstall the Rogue CWM recovery program, which then hosed up my ROM. I actually thought I bricked my phone for a minute, but I was able to go back into Rogue Recovery and re-flash the VeNuM ROM.
All went well and I'm back into my phone, but now again when I reboot into recovery mode, I have "Android System Recovery <3e>" like an abridged version of CWM. I don't have near as many options and wonder what's going on.
I never lost my recovery mode before when flashing a ROM. Is there some sort of custom recovery included with this ROM, or am I doing something wrong?
hi. im pretty new at this also, but i think i know the answer to this. well. not really the answer, but i know how to get clockwork recovery back onto the venum rom you are using now. you need Odin3-v1.85 (just google it) and the clockwork recovery StockCWM-EL26.tar (google). Then you put your phone in odin mode, volume down and power from powered off state, run the program, check the PDA option and browse for the stockcwm file, plug in usb and hit start. That'll put the recovery back on your phone.
But as I've been reading, a lot of times, you cannot just download the rom onto the phone or sd card and flash new roms using the cwm recovery. something about the gingerbread and ics and different kernels. .... =D
Please read the "How not to brick your e4gt" or how ever it goes in general. You need to stay away from rom manager and any touch recoveries. To answer your question, rogue recovery went away because the Venum ICE rom has the stock recovery packed in because of all the custom recovery/bricking issues we've been having with ICS. So the Dev left out custom recovery included with his rom
Sent from my SPH-D710 using Tapatalk
I'm not sure what recovery Venum comes with but this might be by design since custom CWM recovery is not installed by design on most ICS roms.
First of all read through this thread: http://forum.xda-developers.com/showthread.php?t=1525495
You chose to flash ICS; if you had chosen Gingerbread this would not be an issue so please read on... ROM manager should NOT be used with ICS. Since you are new, the only CWM recovery you should be using is the stockcwm-el26 posted here: http://chris41g.devphone.org/index.php?dir=EpicTouch/Stock+Repack/EL26/
Lastly and most important:
Flashing ICS can be a very dangerous thing for your phone if done improperly. Even flashing back to Gingerbread from ICS can go wrong.
Please do not do any further flashing of ICS without reading and understanding the process of flashing ICS safely!
Also, please feel free to ask lots of questions until you are comfortable with the entire process. That is why we are here.
Edit: Sorry for the very strict tone throughout. You have a very nice WORKING phone and we see a lot of newbies flashing over to ICS without a full understanding of what can go horribly wrong. We also see users asking for help here daily because they have bricked their phone (many times with no hope for repair or recovery).
Maybe I'm just lucky?
Ok, so I read a little more (two straight days of XDA has left me a bit un-productive at work) and I see now the difference between the Samsung phone and the HTC phone I had before. Samsung does partitioning a bit different, or maybe it's just ICS, but either way as you explained in your post, the recovery has to be packed into the ROM. Makes sense now. I was thinking that the recovery was a different eeProm chip, therfore flashing a ROM shouldn't affect the recovery, now I know that's not the case.
After I read, a bit more, I actually did what it's been suggested not to do, and that's install ROM manager. From ROM manager I installed the custom recovery and have successfully booted to this several times without incident, and in fact have flashed both another ROM (VeNuM Anakonda), a Theme for this Rom, and the S Voice update 4 exe file. I don't seem to be having any trouble using Rom manager to boot into recovery mode.
Venum ICE was a bit much for me, way too many bells and whistles that I could potentially blow up my phone with which still could happen. Anyway, I like the Anakonda rom and will probably stick with it a while. I can't get s Voice to stabalize, but that seems to be the only problem I've got, so I'll live with that.
BBJon said:
Ok, so I read a little more (two straight days of XDA has left me a bit un-productive at work) and I see now the difference between the Samsung phone and the HTC phone I had before. Samsung does partitioning a bit different, or maybe it's just ICS, but either way as you explained in your post, the recovery has to be packed into the ROM. Makes sense now. I was thinking that the recovery was a different eeProm chip, therfore flashing a ROM shouldn't affect the recovery, now I know that's not the case.
After I read, a bit more, I actually did what it's been suggested not to do, and that's install ROM manager. From ROM manager I installed the custom recovery and have successfully booted to this several times without incident, and in fact have flashed both another ROM (VeNuM Anakonda), a Theme for this Rom, and the S Voice update 4 exe file. I don't seem to be having any trouble using Rom manager to boot into recovery mode.
Venum ICE was a bit much for me, way too many bells and whistles that I could potentially blow up my phone with which still could happen. Anyway, I like the Anakonda rom and will probably stick with it a while. I can't get s Voice to stabalize, but that seems to be the only problem I've got, so I'll live with that.
Click to expand...
Click to collapse
Coming in late to this thread but I would like to re-iterate what was said about ROM manager and pretty much everything tdunham said. Because you have been, so far lucky, does not mean that luck will continue. Best advice is to remove it and not use it. If you read through some more posts you will see that the bricking doesn't always happen on the first, second, third flash. It can all of a sudden appear. We've had VERY experienced developers brick their phones, so to think you won't just because you've been lucky is not wise.
But some of the comanailities are clear - using ICS recovery to wipe/restore and using ROM manager. Just thought I'd point that out.
If you're coming over from a different phone (HTC etc) check out Qbking77's videos. They are very informative too.
Good luck and have fun.
I'm glad that the op did some reading and had some extra help here. Our phones can be confusing but with extra reading it can be figured out. We try to list the kernel that's in the rom and these are all listed in the development section in some form or another with explanations of what they have, ie cwm or rogue recovery... In addition most of our roms list a change log that you can read that will tell what each version of the rom has in it in case you would rather use an older version. And we keep the older roms posted too... anyway happy flashing !
I've bricked my phone a few time messing around with different ICS roms and kernals. I go back and odin EL29 rooted...start all over from scratch. Try using new recovey kernals posted on ACS. I'm on FE22 with the ACS recovery and am having no issues with flashing zips and making backups as well restoring.
Sent from my SPH-D710 using xda premium
There are some repacked recoveries that Steady used to make for ICS before he disappeared. Those were never and still aren't safe for flashing ROMs though. It's safest to Odin/Mobile ODIN CWM EL26 tar whenever you need recovery and then flash whatever and then reflash an ICS kernel without recovery so that your phone boots
Sent from my SPH-D710 using XDA
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
Just putting this out there for someone to help a few of us. I just purchased a new s3 for my son and was able to root it but when we Enter a custom recovery either cwm or twrp neither internal or external storage is recognized. Hoping if I spill this to the masses someone can help.
Sent from my SPH-L720 using XDA
I've seen this issue now posted in the TWRP thread as well as the CWM thread. I don't think there is a solution for it yet; has anyone gotten a log of what is happening? Is it only happening on the Sprint variants?
This has happened to me just recently only my external sd card was recognized & I tried to flash several ROMs and none would boot. Thank God that's where I place my ROMs. I ended up having to completely wipe my internal memory for it to boot... im ready for a new phone now smh
India85g said:
This has happened to me just recently only my external sd card was recognized & I tried to flash several ROMs and none would boot. Thank God that's where I place my ROMs. I ended up having to completely wipe my internal memory for it to boot... im ready for a new phone now smh
Click to expand...
Click to collapse
There are many threads on this issue. I know there are a few Devs working on modifying recovery to work with the new ones. Just hang in there. It'll come soon enough. Flashing a Rooted rom Via ODIN does work for atleast using root apps and bloat removal. It's not alot but atleast it's a start.
From our good buddy @CNexus http://forum.xda-developers.com/showthread.php?t=2183910&page=4
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Virgin Mobile variant
I also have this problem :/
I got my Virgin Mobile variant a couple days ago and flashed CWM without issue over Odin. But when I go into CWM it won't/can't mount anything. I figured it was an issue with Virgin Mobile's MD7 variant so I used rwilco's One-Click .exe to flash my phone to Rooted Sprint's MD4, again that went off without a hitch.
I then re-flashed CWM and same problem. I tried TWR as well with the same result. I'm stuck on Touchwiz until this problem gets sorted out
Please, someone smarter than me (this group is in abundance) figure this out...my head hurts.
nidpancho said:
I also have this problem :/
I got my Virgin Mobile variant a couple days ago and flashed CWM without issue over Odin. But when I go into CWM it won't/can't mount anything. I figured it was an issue with Virgin Mobile's MD7 variant so I used rwilco's One-Click .exe to flash my phone to Rooted Sprint's MD4, again that went off without a hitch.
I then re-flashed CWM and same problem. I tried TWR as well with the same result. I'm stuck on Touchwiz until this problem gets sorted out
Please, someone smarter than me (this group is in abundance) figure this out...my head hurts.
Click to expand...
Click to collapse
If you are on touchwiz, just download a rom over wifi...then boot into recovery and flash it. Just because you can't mount doesn't mean you can't flash.
lvpre said:
If you are on touchwiz, just download a rom over wifi...then boot into recovery and flash it. Just because you can't mount doesn't mean you can't flash.
Click to expand...
Click to collapse
You have to have something to flash it to. Since nothing will mount at all, there is no where to put the files.
I have this problem also, and you can't do anything in recovery. I even tried wiping from recovery and it says it can't mount anything to wipe!
---------- Post added at 01:39 PM ---------- Previous post was at 01:20 PM ----------
nidpancho said:
I also have this problem :/
I got my Virgin Mobile variant a couple days ago and flashed CWM without issue over Odin. But when I go into CWM it won't/can't mount anything. I figured it was an issue with Virgin Mobile's MD7 variant so I used rwilco's One-Click .exe to flash my phone to Rooted Sprint's MD4, again that went off without a hitch.
I then re-flashed CWM and same problem. I tried TWR as well with the same result. I'm stuck on Touchwiz until this problem gets sorted out
Please, someone smarter than me (this group is in abundance) figure this out...my head hurts.
Click to expand...
Click to collapse
There are others working on this: http://forum.xda-developers.com/showthread.php?p=44214994#post44214994
nidpancho said:
I also have this problem :/
I got my Virgin Mobile variant a couple days ago and flashed CWM without issue over Odin. But when I go into CWM it won't/can't mount anything. I figured it was an issue with Virgin Mobile's MD7 variant so I used rwilco's One-Click .exe to flash my phone to Rooted Sprint's MD4, again that went off without a hitch.
I then re-flashed CWM and same problem. I tried TWR as well with the same result. I'm stuck on Touchwiz until this problem gets sorted out
Please, someone smarter than me (this group is in abundance) figure this out...my head hurts.[/QUOTEforum
I just came over from the Evo 4g and could not flash a custom recovery because i didnt access full root . however i was told to use Flash image gui and it worked to get custom recovery on the evo ......but given the new security patches and the fact that i myself have no custom recovery if i brick my phone, i am a bit hesitant to try it on the gs3 .
Click to expand...
Click to collapse
You won't brick your device while installing the recovery. But the issue seems to be that Samsung or Sprint has done something to all new devices shipped over the last month which do not allow to mount the phones storage in recovery. You are able to root and flash via odin but recovery won't mount storage so you can't flash anything via recovery.
Sent from the future via Tapatalk 4
Please follow the CWM and TWRP threads in development for progress on this issue
Thanks
FNM
So my wifes i747 was running 4.0.4 so I decided to upgrade it for her a bit. Im not new to rooting and flashing roms so I figured why not just put a custom KK rom onto it in order to freshen it up a bit for her. I also have to add that it is a ATT S3 unlocked and being used on Tmobile network.
Came to the forums and downloaded SlimKat rom and installed CWM and flashed the new rom. Everything went fine, but in the end my wife didnt like the feel of it and just wanted a new phone. So I traded her my phone and got hers. Well i wasnt a huge fan of the SlimKat rom either, nothing particularly wrong I was just always a CyanogenMod fan. Im having issues right now because I cannot get it to flash any new ROMs without messing up. Ill either get an error in CWM saying it cant flash the new rom or it will Flash but then never leave the LOGO screen. Ive let it sit for 45mins before.
I was able to always restore to a backup and just keep using SlimKat, but just tonight Im no longer able to restore to the backup. CWM sits at "Restoring data... c7ac6bd9.0..." but never actually finishes the restore.
So am I bricked? or what should I try? and also can someone just tell me what Rom/Kernal/Modem I need to flash in order to get it working. Id really like to use the Cyanide L, with Shift kernal but im not sure which modem I need. Tmobile modem or Att modem and which number.
Any help would be great thanks.
Additional info: I wiped cache, dalvik, and system/data everytime I tried to flash new rom, I made a backup and saved to my external before the flash. It is carrier unlocked and rooted. model number is the i747. CWM is v6.0.1.2
Your CWM is outdated.
Flash the latest Philz tar.md5 file in Odin: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
The latest KK ROMs will also need an updated bootloader and modem to function properly.
So I was messing around with some ROMs to see which one I liked. But when I installed the SlimLP Rom my phone started acting weird. First it would just shut down and then I couldn't even get into recovery. I finally got into recovery after using ODIN and now I want to get rid of this ROM and im getting an error message that says this phone is an sghi727, MY PHONE IS DEFINATELY A sght989. Help me. Im so confused. This is all new to me.
akumar94 said:
So I was messing around with some ROMs to see which one I liked. But when I installed the SlimLP Rom my phone started acting weird. First it would just shut down and then I couldn't even get into recovery. I finally got into recovery after using ODIN and now I want to get rid of this ROM and im getting an error message that says this phone is an sghi727, MY PHONE IS DEFINATELY A sght989. Help me. Im so confused. This is all new to me.
Click to expand...
Click to collapse
Did you try going into your recovery and wiping data/factory reset, cache, and dalvick. Then flashing a new rom or did you just dirty flash?
Restore to stock rom is one option.
See this thread : http://forum.xda-developers.com/showthread.php?t=2541783
The reason it might have that model number in build.prop is because most ROMs from the AT&T S2 work just fine on the T-Mobile S2 and the ROM dev doesn't make two ROMs with the only difference being the model number. If you can get into recovery, you can do a full wipe and install another ROM. Make sure you are using the latest recovery. I recommend TWRP, as it is touch screen and very user friendly.
jrc2