Related
I installed "Eugene_2E_JK2_Froyo.tar.md5" on two of our Vibrants using odin. I have four strange anamolies that happened to both Vibrants as a result of this...
1) There is NO lock screen anymore.
2) The touch "home" and "search" keys are non-responsive.
3) Videos cannot be played.
4) The most disturbing is we cannot receive calls...but we can make them.
I currently have 2.2 froyo.uvjk2 installed on both vibrants.
As a result of these weird accurances, I tried installing several roms...such as Axura 204 and Onyx R42 Stock. I keep getting a signature error when the Vibrant boots in recovery mode. Do roms not work on 2.2?
I am using the current "One Click Lag Fix" and "Rom Manager".
What should I do to fix these Vibrants and why are the roms not working?
Any help would be greatly appreciated.
ams77 said:
I installed "Eugene_2E_JK2_Froyo.tar.md5" on two of our Vibrants using odin. I have four strange anamolies that happened to both Vibrants as a result of this...
1) There is NO lock screen anymore.
2) The touch "home" and "search" keys are non-responsive.
3) Videos cannot be played.
4) The most disturbing is we cannot receive calls...but we can make them.
I currently have 2.2 froyo.uvjk2 installed on both vibrants.
As a result of these weird accurances, I tried installing several roms...such as Axura 204 and Onyx R42 Stock. I keep getting a signature error when the Vibrant boots in recovery mode. Do roms not work on 2.2?
I am using the current "One Click Lag Fix" and "Rom Manager".
What should I do to fix these Vibrants and why are the roms not working?
Any help would be greatly appreciated.
Click to expand...
Click to collapse
make sure and disable the lag fix, and try the reboot to recovery option in rom manager. (so that your in clockwork recovery and not samsungs)
then try flashing the new rom from there.
also you probably know this, but just to be sure: make sure your flashing rom zips and not odin style roms.
otherwise odin should work especially if you've done it before, but be sure to flash a 2.1 kernel if your going to a 2.1 rom
theres some guides for that, if you decide to go that direction I can give you a link.
firefly6240 said:
make sure and disable the lag fix, and try the reboot to recovery option in rom manager. (so that your in clockwork recovery and not samsungs)
then try flashing the new rom from there.
also you probably know this, but just to be sure: make sure your flashing rom zips and not odin style roms.
otherwise odin should work especially if you've done it before, but be sure to flash a 2.1 kernel if your going to a 2.1 rom
theres some guides for that, if you decide to go that direction I can give you a link.
Click to expand...
Click to collapse
Can you tell me what this means...how do I disable the lag fix? I am extremely new to android (one week), so can you tell me more about how to flash a kernel and what that means? Is Axura 204 and Onyx R42 Stock 2.1 roms? Do I have to downgrade back to 2.1 in order to run those roms? If so, I'll take you up on that offer for the link for directions.
Thanks for all the help...
ams77 said:
Can you tell me what this means...how do I disable the lag fix? I am extremely new to android (one week), so can you tell me more about how to flash a kernel and what that means? Is Axura 204 and Onyx R42 Stock 2.1 roms? Do I have to downgrade back to 2.1 in order to run those roms? If so, I'll take you up on that offer for the link for directions.
Thanks for all the help...
Click to expand...
Click to collapse
try looking here: http://forum.xda-developers.com/showthread.php?t=849028
that should have most of your questions answered, anything you need more specifics on just pm me again and I'll explain further.
wow. dude. this is weird.
this same problem happened on my gf's nexus one out of the blue last month. there was no way to fix it (searched the entire internets!) other than doing a factory reset.
so i did that and it worked for 2 weeks. then bam, same ****ing problem again.
reset again, it did it again that same week.
called HTC and got a new SLCD nexus one mailed out to us free of charge.
EXACT same problems though, those two buttons haptic feedback but do nothing, no lock screen, and phone calls go straight to voicemail.
The bug in CWM that makes the phone boot to recovery when the USB charger is really annoying. So until Amon_RA makes a recovery for the Thunderbolt or CWM fixes their bugs, I'd like to remove it and reinstall the stock recovery.
So, with that said, if I'm not running a custom ROM (yet), do I need to use a custom recovery like CWM or Amon_RA just because I'm rooted? Or is that only necessary once you get into flashing ROMs?
Thanks!
I guess you wont be needing complete backups either incase you change something and cant go back in time. Unless you like flashing the ruu and rerooting everytime you made a booboo
personally i like backups and the fastboot fixes the charging thing anyhow
also i have to say im a bit confused at the number of folks that turn their phones off to charge
HOW DO YOU INTERNET WITHOUT POWER ON?!?!?
rizzomegav said:
HOW DO YOU INTERNET WITHOUT POWER ON?!?!?
Click to expand...
Click to collapse
Lol. I agree tho, I like being in touch with everything at all times. Thats why I have a smartphone. So my phone always stays on.
I'm not an android noob...
But just curiously browsing this forum because my sister is getting an Eris as a semi-permanent replacement for her crapberry that she lost.
I can't stand to see her stuck on cupcake...and she's given me the go-ahead to get her up to speed.
I plan on putting CM7 on there for her...
But I have a few questions.
Rooting:
Should I just use this application?
https://market.android.com/details?...1bGwsMSwyLDEsIm5ldC5hbmRpcmMuZXJpc3Jvb3RlciJd
And then to get CWM...
Rom Manager?
I see that CWM is bricking phones...why is that and how common is it?
Are there alternatives I should use instead (RZrecovery or similar?)
And as far as returning to stock...
We use SBF's with Motorola.
What is the alternative here?
Do I have to rely on Nandroids?
Can I restore a stock nandroid from CM7?
Jubakuba said:
I'm not an android noob...
But just curiously browsing this forum because my sister is getting an Eris as a semi-permanent replacement for her crapberry that she lost.
I can't stand to see her stuck on cupcake...and she's given me the go-ahead to get her up to speed.
I plan on putting CM7 on there for her...
But I have a few questions.
Rooting:
Should I just use this application?
https://market.android.com/details?...1bGwsMSwyLDEsIm5ldC5hbmRpcmMuZXJpc3Jvb3RlciJd
Click to expand...
Click to collapse
Yes. Install the app. Run the app. It will tell you to restart the phone - so, that means shut down the phone. Start it back up again. That will have installed Amon_RA recovery, which will allow you to Nandroid backup, install a custom ROM, etc.
(So, after that restart, you can shut the phone down, hold VolUp while powering on to get to Amon_RA recovery. You sound experienced enough to know what to do from there.)
By the way, the Eris by now should have Eclair (2.1), not cupcake (1.5). There should have been three OTAs that brought cupcake up to 2.1.
And then to get CWM...
Rom Manager?
I see that CWM is bricking phones...why is that and how common is it?
Are there alternatives I should use instead (RZrecovery or similar?)
Click to expand...
Click to collapse
As you have seen, many people running Clockwork Recovery as the default recovery have bricked their Erises. ROM Manager comes with almost all of the CM7 ROMs, but you can install it. From within ROM Manager you can have it flash Clockwork, which puts an update.zip file on the SD Card. Go into Amon_RA Recovery, Flash a zip from SD card, choose update.zip, and it will start Clockwork, if you prefer using that. (I actually always do this, as I prefer the Nandroid backup and wipe functions in Clockwork over Amon_RA.) Running Clockwork in this way is safe, as Amon_RA remains as the default recovery.
And as far as returning to stock...
We use SBF's with Motorola.
What is the alternative here?
Do I have to rely on Nandroids?
Can I restore a stock nandroid from CM7?
Click to expand...
Click to collapse
No SBF files for the Eris; however, user bftb0 created a ROM that you can flash that reinstalls stock Recovery and the stock 2.1 ROM. It's called Flashback_21v2, located here: http://forum.xda-developers.com/showthread.php?t=792026
The no radio version should be fine for this purpose.
Perfect.
And I even meant to ask if there was a way to boot into the custom recovery from a power-off state...which you already covered!
That's all I needed.
I appreciate the time you put into answering every question...most people tend to pick one and then the thread dies.
Thanks!
Edit:
Oh, and ya her phone hasn't arrived yet...
The HTC official website said Cupcake...wow that would have been out-of-date!
I recently installed the nightly build of ICS on my samsung vibrant. Today the phone had a error that said encryption cannot be completed phone must be erased. I let it do a factory reset . Then I got stuck in a endless boot cycle showing the vibrant logo and then the cynogen guy for a few seconds then reboot. I could still access the recovery menu but it refused to flash any roms I threw at it. I downloaded and ran odin 1 click recovery and it changed my tmobile phone to a att phone. And it lost the recovery mode. It just shows att screen first then samsung vibrant second and just reboots. I can still get into download mode and flash roms using odin 3 but no matter what rom I select or if I choose repartion or not the flash will go through successfully but then the phone reboots into same problem as before. I suspect the recovery files are gone since no button combination anymore gets me into recovery. Is there anything else I can do?
Man I am having the exact same problem. I really hope someone can figure something out soon. Did yours randomly get that error? Or did you actually try to encrypt your phone?
Sounds like you used the wrong Odin 1 Click. If it installed Captivate bootloaders, that would cause a problem.
This is your best shot I think
http://forum.xda-developers.com/showthread.php?p=24418319
Sent from my A500 using Tapatalk 2
It just happened
It happened on its own. Was working fine all day walked in my house as as soon as it hit wifi it started going crazy. I had the data plan turned off months ago. Maybe theres something to it connecting up to the net. I have found out if you install your sim you get a reduced menu of recovery options but without sim it just constantly reboots. it only gives option of reboot, reinstall packages,delete all user data, delete cache data. If you try reinstalling the packages theres nothing there. Deleting caches made no differance. ADB does work and responds while in this lesser form of recovery is there a easy way to use adb to force a full system flash?
Thanks
That link was perfect had a link to eugenes no brick froyo rom which fixed my problem. Dloaded that used its pit and tar files and repartioned and im back to stock. Going back to team whiskeys mod. If all ICS roms has bugs like that is unusable.
bfranklin1986 said:
This is your best shot I think
http://forum.xda-developers.com/showthread.php?p=24418319
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
Do you have access to BOTH your internal and external SD cards? The Encryption Bug is totally and completely random and does not discriminate. There is currently no known reason or solution. Several of us across a few different devices have been working on this for months.
Consider yourself luck if you have access to both SDs as you are the 2nd person to get in and out today. Many, many others have not been as fortunate.
If you could please pull up this thread and put as much information in there as possible, it would be greatly appreciated. Are you unlocked, what happened right before, what bootloaders are you on, what ROM were you trying to flash, what ROM did you end up getting booted,....those types of things. As much detail as you can muster together, after you catch your breath and relax a minute.
Guys DO NOT run ICS unless you have read up on the Encryption Unsuccessful bug and except the possible consequences! Every ICS T959 rom should have a warning IMO.
There is no known fix > just a work around. Odin / Heimdall / Jtag = useless
Update
I think I might have pulled the trigger to quick. While the link above did give me Eugenes rom which at least got me out of the boot cycle both internal and external sd shows 0 and I am unable to load anything on either card. I have tried differant microsd cards all of them show the same thing. So eugenes rom got me working kind of but cant store anything at all. That sucks loved my vibrant and its almost out of contract and planned on using on prepay.
Agreed 100 %
Had I of known would of stuck around on my team whiskey rom which never gave me any problems. Does this ICS bug affect amazon kindles? Ive put cynogen9 on 2 of them and am wondering if I shouldnt take it off before they turn into paper weights.
Moped_Ryder said:
Guys DO NOT run ICS unless you have read up on the Encryption Unsuccessful bug and except the possible consequences! Every ICS T959 rom should have a warning IMO.
There is no known fix > just a work around. Odin / Heimdall / Jtag = useless
Click to expand...
Click to collapse
chickenmon said:
Had I of known would of stuck around on my team whiskey rom which never gave me any problems. Does this ICS bug affect amazon kindles? Ive put cynogen9 on 2 of them and am wondering if I shouldnt take it off before they turn into paper weights.
Click to expand...
Click to collapse
I got tagged on a Nook Color with it. BUT, since the Nook Color has a feature that no others I think do (you can boot a ROM straight from an SD card and not mess with the oringinal OS at all), I was able to just pull my Microsd out and reformat it and then put CM7 on it for my wife.
So far from what I have seen and been working on:
Vibrant, Captivate, My wife's Nook Color, A few Transformers, SGSII,...
Anything I can do?
Anything I can do to get my partions right again? I can flash the twm 5.2.2 but none of the roms i throw at it including ics passion stays in a boot cycle. Only rom that works is eugenes froyo that does not brick and it doesnt allow internal or external mem to be seen.
chickenmon said:
... Only rom that works is eugenes froyo that does not brick and it doesnt allow internal or external mem to be seen.
Click to expand...
Click to collapse
You may want to bring up this issue directly in Merio90's thread. I believe Alex9090 went thru possibly similar issues and may be able to help you in that thread (unless she happens to pop in here).
I'm assuming you were trying to mount sdcard and emmc within recovery first (storage and mounts)? If you do have access to recovery again and can mount the external sdcard, maybe try repartitioning the card within recovery (using the parameters in Merio90's instructions)? Then transfer your rom zip and re-flash.
People have actually flashed Eugene's Froyo post-EU ... but without an ext sdcard. Quite an oddity. It's the only one (AFAIK) that'll fully boot up (even after losing int sdcard access due to EU) yet without an external sdcard in place.
Your assumptions are correct. I cannot mount emmc. I cannot flash any rom via 2.5 or 5.2 recovery only through odin and only eugenes rom still allows phone to boot but no mounting of internal or external sds. Ive spent about 3 days on this. There must be some hardcore adb commands to force a true factory reset partioning and all. Very annoying. Thanks for the help if I find any ways to fix it I will repost it here.
Might be bricked?
Ok, i will admit up front that I probably did something stupid and now am sending out a cry for help. Until yesterday I had ICS 4.0.3 successfully installed. I believe it was Euphoria flavor. But, I constantly had shortage of memory problems with the new force close language on apps running in bg - was laggy. Here is where it all went wrong - Decided to dl and install CM9 nightly to fix my laggy install. Recovery went fine, but rom failed, rebooted and sent error to cm. Tried new tactic - dl and installed Slim ICS - wrong, got stuck in boot loop - but could still get into download mode. Ran Odin to restore to stock. Ran fine but Failed - no explanation, just failed. Since it would not respond, finally turned it off - OFF has now become permanent! Power button does nothing. Charging does not light up screen. No download or recovery mode! Really fearful that this IS bad. Help, help, help!!
Open to suggestion. . .
JIM in FLA
Not related at all to my original problem.
tenantrep said:
Ok, i will admit up front that I probably did something stupid and now am sending out a cry for help. Until yesterday I had ICS 4.0.3 successfully installed. I believe it was Euphoria flavor. But, I constantly had shortage of memory problems with the new force close language on apps running in bg - was laggy. Here is where it all went wrong - Decided to dl and install CM9 nightly to fix my laggy install. Recovery went fine, but rom failed, rebooted and sent error to cm. Tried new tactic - dl and installed Slim ICS - wrong, got stuck in boot loop - but could still get into download mode. Ran Odin to restore to stock. Ran fine but Failed - no explanation, just failed. Since it would not respond, finally turned it off - OFF has now become permanent! Power button does nothing. Charging does not light up screen. No download or recovery mode! Really fearful that this IS bad. Help, help, help!!
Open to suggestion. . .
JIM in FLA
Click to expand...
Click to collapse
First of all, not to sound like a ****; but it's rude to hijack someone elses thread. You should've created your own thread for this.
Second; you might have fried your bootloader which in turn, yeah, that's bad and you might have bricked your phone.
Did you try to boot into recovery via the battery pull method. If not, try that and see how it works. I would link you to the instructions but I'm too lazy and tired right now to search for it and again, this is someone else's thread. Just do a search for it and you should find it.
If you need more help or guidance, create your own thread and start there.
Noticed your running Ice Cream Zenwich rc1.3. How do you like it. Ive installed slim 3 times today and twice I have gotten the encryption error within a hour. Needless to say not impressed major pain in the ass to have to do a million and half tricks with awm, adb, popping sd cards in and out etc.
Update
Also the current build of ics slim does not allow the imei information to be retrieved from sim for tmobile requiring a reflash of the modem. You have to download and install a new modem. I used csm5. The guide on the link in this post dow work but its a real pain and requires lots of trial and error. Wondering if google intentionally bricking these things knowing we all got gadget lust for the sIII now.
chickenmon said:
Noticed your running Ice Cream Zenwich rc1.3. How do you like it ...
Click to expand...
Click to collapse
ICZen_rc1.8.3 (AOKP #39, ICS 4.0.4) + subZero #144 (New Test Kernel just released in mr_pyscho's RootzWiki kernel thread) is Linaro infused ... and I've got to say the combo is THE fastest rom experience I've ever had on my Vibe. Whatever MP did in his new test kernel just blows the doors off the previous performance limits.
Btw .. you keep encountering EU again. Really odd unless possibly your external card wasn't partitioned correctly. Not a knock directly on you, but it is a common occurrence lately. FYI, I repartitioned mine directly from recovery.
Also ... Br1cK'd (ICZen) and mr_psycho (subZero) are aware of the EU situation and try to include safeguards in their builds. However, until we know the exact root cause of EU, we're all just shooting in the dark. Imo, it's at least comforting to use a rom & kernel where the dev's are at least mindful of EU.
Hello all,
I have a question that has not been answered after many hours of searching. Hopefully I'm just dumb, and my buddy's stock firmware and data isn't hosed. I'm trying to get his stock firmware running again so I can back it up safely.
What I've done:
Tried to flash CWM's update.zip via stock recovery (signature verification failed on the three different zip's I could find in the forums and various links)
Used Heimdall to push "cmenard-T959-CWM" zImage (this worked, and I get a different screen at boot)
The phone boots to the point of the T-Mobile splash screen with the annoying shriek sound, but goes to a black screen after. If i touch any of the soft buttons, they light up and remain lit. It'll stay like that for at least 20 minutes.
Is it possible to re-flash the system partition and not the data partitions using ODIN? Is that even feasible? Like I mentioned above, I'd like to get the stock firmware running such that I can make a good backup of it with all the user data intact. I haven't been able to because the CWM+root wouldn't flash.
Any suggestions or insight would be greatly appreciated.
thanks in advance!
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Toast6977 said:
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Click to expand...
Click to collapse
Thanks for the suggestion, Toast. I don't believe the internal SD has been messed with, and I don't plan to mess with it either. The thread you linked is not quite related to my issue, as far as I can tell.
I am able to get into Download Mode, and the Stock Recovery mode as well. However every time I try to flash an 'update.zip' with the Stock Recovery, I get an error about Signature Verification Failure.
After stepping back from it for a day, I think I've gained some clarity. Since all I've done is flash a different Kernel with Heimdall, I'm going to try to flash a stock kernel then see what happens.
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Toast6977 said:
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
Click to expand...
Click to collapse
Woodrube said:
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Click to expand...
Click to collapse
hahaha poltergeist!
Wow, so I'm glad I asked. I wouldn't have known about this issue, as I do not have any history with this device.
I know that the ROM is currently 2.2, and the Android System Recovery is showing "3e".
If I understand correctly, once I'm ready to flash up to ICS, I'll need to ODIN back to 2.1 to get Android System Recovery "2e", which will let me flash 'update.zip' packages freely. Then I flash an 'update.zip' to get CWM, then flash CM7, then CM9 (and CM9 is my intended destination).
The things mentioned in the thread you linked do appear to apply to my situation.
However I still want to get the stock OS booted and working, then do a Nandroid backup of it. (it's the computer tech/security pro in me. Since I'm new to this device, I -tried- to read up on everything first, and didn't want to make a change without being sure it would work.)
Does anyone happen to know if flashing a stock kernel over the 'cmenard' kernel will harm anything, and hopefully get a successful boot? Again, I'm trying to get the stock ROM booting again in order to verify I have everything I need off of it, then do a nandroid backup. Flashing to CM9 will come afterwards.
Ok, here are some things for you.
Here is a kernel pack that you can use. Read the OP because there are Froyo AND Gingerbread kernels in there.
[KERNELS] Moped_Ryder SGS Kernel Pack v2 [20+ Froyo/GB Kernels]
I really suggest using something like BaliX 1.2 or BaliUV kernels to make your back up. They are smooth, fast and OC/UV-able. To flash just Wipe /cache, /dalvik -> flash kernel -> Wipe /cache, /dalvik (I also fix permissions too bc that is the way that I learned and I just do it that way all the time). Reboot and Bam!! you should be able to get to the point that you can make a backup.
Look in my signature, there are downloads and flashables that are direct download linked. There is also an ICS install guide that can help your journey. Once you have your backup, then use Odin from the Toolbox in my signature and flash back to stock JFD. From there you will be able to follow my guide.
If you need any files, just let me know and I will upload them when I get home (won't be until late though, i have plans right after work).
Using HB, can I choose any theme? I am not so acquainted with the Theme chooser and boot animation of my phone. I flashed a boot animation zip yesterday and it was stuck in "ANDROID" screen. So I have to flash again. I never used any boot animation and themes in my phone yet. I want to know about them.
Sent from my SGH-T959 using xda app-developers app
Wrong thread. Put that question in the Jelly Bean Banter thread. No need to hijack this thread until we get OP up and running.
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
maxpeet said:
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
Click to expand...
Click to collapse
Wrong they are not the same. cwm can do the work without a PC beside you can erase, back up , restore and flash, which make our life easier, heimdall or Odin ," I prefer odin "are the last option when you can't fix it with cwm
To fix your phone use Odin or heimdall and go back to stock don't worry all your files, photo, music, will be safe. Then
1 get root on you , if you don't how ask
2 get cWm
3 do a nandroid back up
4 have fun flashing all roms you want lol
Sent from my SGH-T989 using xda app-developers app
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Toast6977 said:
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Click to expand...
Click to collapse
do no check de re-partition button and use a .pit file follow this tutorial and you will be fine
http://forum.xda-developers.com/showthread.php?t=848737