[Q] tried to root my phone and failed miserably - T-Mobile, Samsung Galaxy SIII

I'm sure there's multiple questions about how to fix their phone for this reason or that reason. I am on the verge of crawling up in a ball and rocking back and forth... (maybe it's a bit over dramatic) but I've tried to fix this based on my experiences in the past.
I have a galaxy s3 sgh-t999. I followed instructions to install CMW 5.0.5.4 and used odin, when I finished, I tried flashing a rom and got an error saying that the rom was for dr2tmo not for the device dr2spr. I thought that didn't sound right. I re-did the install of the cmw but used philz touch http://forum.xda-developers.com/showthread.php?t=2310081
I then wiped everything, the factory reset, the cache, battery. I then installed Hellfire for my phone, and the google apps, and now I'm stuck at the boot animation for the rom. I looked into resetting it back to stock, but Odin can't because the count is higher then 1 and I can't find somewhere to reset the phone's count without getting into a rom, which I haven't found one that works.
I appreciate any advice you guys can give, and please let me know if i missed a rule or something and I'll change what I can. Thank you.

I have no clue on how to pull logs either. I'm sorry for not getting too involved before I got that far.

awaj2006 said:
I'm sure there's multiple questions about how to fix their phone for this reason or that reason. I am on the verge of crawling up in a ball and rocking back and forth... (maybe it's a bit over dramatic) but I've tried to fix this based on my experiences in the past.
I have a galaxy s3 sgh-t999. I followed instructions to install CMW 5.0.5.4 and used odin, when I finished, I tried flashing a rom and got an error saying that the rom was for dr2tmo not for the device dr2spr. I thought that didn't sound right. I re-did the install of the cmw but used philz touch http://forum.xda-developers.com/showthread.php?t=2310081
I then wiped everything, the factory reset, the cache, battery. I then installed Hellfire for my phone, and the google apps, and now I'm stuck at the boot animation for the rom. I looked into resetting it back to stock, but Odin can't because the count is higher then 1 and I can't find somewhere to reset the phone's count without getting into a rom, which I haven't found one that works.
I appreciate any advice you guys can give, and please let me know if i missed a rule or something and I'll change what I can. Thank you.
Click to expand...
Click to collapse
My advice would be to get the Cyanogenmod for the d2tmo. If you are already at 4.3 use the 10.2 version. Otherwise probably use 10.1. Don't use the 10.2 unless you have to, it has some security stuff in it that makes rooting/modifying the phone a bit more restricted (IMO).
You can flash the zip for it in CWM or TWRP. http://download.cyanogenmod.org/?device=d2tmo
Once that is done you can use triangle away to reset your counter. Then use odin to get back to stock. Stock can be found at sammobile It'll be a long download, but worth it if you want stock. Again I do not reccomend going 4.3 unless you have already upgraded to it. If you have already upgraded to it you won't have a choice, but until someone finds a way to truly override KNOX and the bootloader security, I personally advise to stay away from it.
I hope this helps

I did do the update for 4.3 while it was available before samsung pulled it. I'll start with 10.1 tomorrow morning and hopefully I can post with good news after it's done. I'll probably stick with what ever I end up with getting to work for a while, whether it's CM 10.1 or 10.2.

You should try with CF method
Sent from my SGH-T999 using xda app-developers app

the CF method?

I got the following error
assert failed: getprop("ro.product.device") =="d2tmo" || getprop("ro.build.product") == ""d2tmo" E: error in /storage/sdcard1/cm-10.1.3-dtmo(1).zip
(status7)
I'll look more into the CF method.

I got CF for tmobile t999 and used odin, it CM came up rather quickly. I'm going through the initial set-up and then I'll try making a phone call. thank you for the help

Related

[Q] Ll3 update fails no matter what

I have been trying to get my S3 to take the update from LG8 to Ll3, and it fails no matter what I try. I am running totally stock LG8 that I rooted using the toolkit posted in the development section. I don't have any APKs that I altered, but every time I try to flash the update, I get a "status 7" error. I tried it on both internal and external SD using CWM recovery. I tried flashing stock recovery via Odin and then let the phone download it over the air and attempt to install itself, and I even tried running the update in TWRP. Every time I get the same status 7 error.
I am coming from HTC phones and have never had these kinds of issues, so I'm pulling out my hair. Can anyone offer any suggestions? I know it must be something stupid I'm overlooking, but I've searched everywhere and can't seem to find the answer.
Sounds like a bad DL. Just grab it from here. http://forum.xda-developers.com/showthread.php?t=1743923
Or here http://forum.xda-developers.com/showthread.php?t=1904099
Or odin flash LI3- http://forum.xda-developers.com/showthread.php?t=1919919
A lot less stressful
The procedure that myn posted over here is pretty staight forward and foolproof too.
Have you solved your issue yet?
I am getting the status 7 error as well even with Myn's procedure. Others are having the problem. Only thing I can think of is the current image file has changed enough to not allow the update to go through. However, I have not removed or modified any stock apks and backed my whole system up with TB right after rooting so no reason for mine to not work. Binary file should be good since it is working for other S3 users.
It's not a bad download. I have tried downloading it multiple times from several sources, and I get the same status 7 failure every time. It even fails when the phone itself downloads the update and it tries to install with the stock recovery.
cfonte100 said:
It's not a bad download. I have tried downloading it multiple times from several sources, and I get the same status 7 failure every time. It even fails when the phone itself downloads the update and it tries to install with the stock recovery.
Click to expand...
Click to collapse
I was able to get mine to work using Myn's method. Seems flashing newest CWM recovery did the trick. Was trying to flash via TWRP and didn't think it would matter but apparently it does. Just followed his post and all upgraded without issue.
Back to your issue.....what state is your phone at currently? What recovery is installed and what version are you running? Surely we can get this resolved for you.
what does the log say when it fails? I mean in addition to status 7. If you don't see anything go under advance>show log. it's probably a failure in the checks it does before the flash. Have u modified your build.prop? is your baseband and build both lg8? That log will tell you what's wrong.or as I mentioned above you could follow 1 of my links and avoid tha headache

[Q] Official stock rom Help?

First of all, yes, I am an idiot, and yes, I have looked through the forums but just have to make sure I am downloading the correct thing.
So, a while ago, I rooted my t-mobile galaxy s3.
Today, I wanted to download a root-compatible app, it didn't work, turns out that my root somehow became disabled ( I might have accidentally wiped the superuser binaries)
So, I try to re-root my phone...several times. I finally think I have it rooted (using the official xda guide on how to root), and everything was fine, until i try to use superuser and it turns out that I am not rooted...for whatever reason. I do a hard reset a couple of times, it still shows that I am running alternate software and cannot update. I try to flash a stock rom to my phone, and that just simply fails on odin.
Now, I have completely formatted the SD and internal storage (probably very stupid), and I am just wondering how I could possibly flash a stock rom onto my phone, and if you could please link one because I believe the one I tried was not for my device.
If not, please provide some suggestions on what I should do. My device works, so it's not really time-sensitive, but I do want to re-root my android after I revert to stock roms, properly this time.
Thank you for your time and help!
Fixed
Fixed the problem, will be posting tutorial in the morning for anyone who might have the same issues!
Waiting for u!!

What the What?!

Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.
kojam said:
Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
Bass_Man25 said:
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
Click to expand...
Click to collapse
Thanks bud.
Oh, I got the phone up and running on the Cyanogen dated dec/2013.
ODIN? Never thought of it. Been such a long time. I do need to get stock on here so I can all the latest official radios etc, then put custom ROMs.
Been such a loooooong time since used ODIN though. Shouldn't be hard to get back on the horse.
Thanks for the suggestion!!!
any idea why this happened? anyone?
as an fyi, I tried to put the lastest SlimROM on but same difference. (i'm really pressed for time always. so I decided this is the quickest thing to try). seems the only thing that will flash is my Cyanogen from December. Strange...
Will have to give ODIN a try if I can ever get the time some day..
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!
DocHoliday77 said:
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!
Click to expand...
Click to collapse
What's up, Doc? Sorry for that...
I downloaded Odin this morning. I should have gotten the link from XDA. The site i got it from looked official, however, tons of endless pop-ups after I installed it. Freak!!!
Then found the xda links. Not sure which version to get because i didn't see which one handles the S3. The latest version (3.09) should, no?
As well, where do i get the stock ROM from? Forgive me for all these questions. Been extremely busy with work these past few months. No time to play around with my phone everything. I'm forgetting more than I know.
A full wipe was done. In TWRP, system was check (it's always checked) automatically when wiping to flash a new ROM.
Thanks again!
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
DocHoliday77 said:
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
Click to expand...
Click to collapse
Thanks!
S.O.S!!!
kojam said:
Thanks!
Click to expand...
Click to collapse
Downloaded the rooted firmware from your link and the ODIN (3.09)...
Flashed the firmware (making sure to get the correct one for WIND)...ODIN did it's thing...got a green pass...the phone rebooted...got the Samsung symbol, little swoosh animation, and the accompanying sound effect that goes with the swoosh-thing...THE PHONE NEVER BOOTED UP AN O/S!
Did it at about 11:30 last night, left it, got up this morn, and phone STILL in same status!
Found out that site where I downloaded the firmware had an issue last night. They posted this morn, apologizing to people about a D.O.D attack that may have caused dropped downloads. I downloaded the firmware again this morn, flashed with ODIN, got a pass....SAME THING!!! Phone
Had to quickly pack up my laptop to bring with me to the office. Will try the official, non-rooted firmware to see if I can get it to go.
Problems' that my team went from 12 to 2 people...my partner's off today...and I got a LOUD MOUTH across from me who WILL NOT leave me alone, no matter what I say or do. LOL.
Any suggestions?
In the words of George Costanza:
"I'm BACK, babyyyyyyy!!!!!"
The official firmware worked!
Phone's back online. Thanks for all your help. Will have to see about rooting later...as well, want to see how the battery operates on stock firmware. I've tried EVERYTHING under the sun to preserve batt life and NOTHING worked!!!
Tried EVERY KERNEL noted to be good on battery life, tried TONS of apps that were supposed to help, turned off as much as I could, etc....
batt still not good. I give up. Every diagnostic app says batt is very good. I dunno...
Earplugs! Lol! I definitely feel for you about your work status! Been there!
About the firmware though, if the download had been corrupted, it would've failed the initial check done by Odin. You are probably ok. Dont worry just yet!
If it is hanging up at the Samsung screen, you probably just need to factory reset. Almost always fixes this. (It happens due to incompatible data left from your previous rom)
This will wipe internal sdcard though, so if you haven't backed up yet, the next thing to fo is flash TWRP via Odin. You can then use its built in file manager to copy whst you need first. Or you can then flash an insecure kernel and use adb if you're familiar with that.
The Doc is in!
if the download had been corrupted, it would've failed the initial check done by Odin
Click to expand...
Click to collapse
That's EXACTLY my thought too. That was really perplexing...
I am up again...
Facotry Reset? How do I do that if stuck at the Samsung splash though?
Now that i know the official firmware works, maybe i'll, try again with the rooted firmware, try to factory reset when stuck, and continue to flash TWRP as you described above. Don't mind factory resetting. I've taken everything I need.
Oh!!!!
I noticed that all the apps I had before flashing the firmware are STILL on my phone. I would have thought that they would have been wiped out completely when lord ODIN was doing her thing.
....and battery life is STILL pretty bad...
Phone's been charging...became fully charged...unplugged it..it was down to 84% after only about 30/mins.
Will see how it goes after doing the factory wipe.
Again, how do i do a factory wipe if stuck at the Samsung swoosh after I re-flash the rooted firmware ?
Maybe your battery is dying. it happens. That would explain a big drop from the start.
To factory reset if you're stuck at boot up, turn the phone off, then boot up into recovery. Hold volume up, home and power. After it vibrates, release power only, continue holding the other two until you see recovery booting up.
If stock recovery is installed, choose factory reset.
In TWRP (probably similar in cwm) go to Wipe and choose factory reset there. In TWRP and CWM, factory resetting does not wipe your internal sdcard. Stock recovery will.
And as for Odin, it doesn't actually touch the user data partition, so all your apps and data are preserved. This is great when just upgrading from one build to the next, but is the reason a factory reset is required if coming from a non touchwiz rom.
---------- Post added at 03:59 PM ---------- Previous post was at 03:53 PM ----------
How old is your battery? The S3 is at the age where people who bought it when it was first released will start to notice the battery is beginning to degrade.
You can also get an app called Better Battery Stats here on xda (paid version in the play store). Its the goto utility for investigating problems with battery drain. Run it for a day after a full charge and then check its logs for persistent wakelocks. The app thread should explain its use better than I can, but if you are having trouble you can always post your bbs log here for one of us to look over. (This isnt my strongest area, but there are a few others around that may also be able to help. )

Tried rooting S3, didn't work, need help.

I am very new at this, so I apologize in advance. I have the Virgin Mobile Galaxy S3 SPH-L710 running 4.3.
I simply wanted to root it so i could get rid of the bloatware and install Sixaxis and play emulators, but I didn't really know where to start, so I started looking around and found this
http://forum.xda-developers.com/showthread.php?t=2546505
So I basically did everything on there. I used Odin to install PhilZ Touch 6 Recovery (CWM 6.0.4.7) Did factory reset, wiped cache/dalvik. then installed the Odexed MK5 stock rooted zip, wifi fix zip, SuperSU update zip, and then the knox app remover zip.
Everything flashed just fine and it started right up. It had the Super Su app, but when I tried to install apps that need root permission it would say I don't have root access. I couldn't delete bloat apps and Super Su didn't show any apps and there isn't much I can do with it. So I guess it didn't work? Either way I wanted to try a different rom. Was gonna give Cyanogenmod a try. But every time I try to install it I get the little "Android bot laying on his back" thing and it says status 7. I tried to flash CM10, CM10.1, CM10.2, CM11. Nothing worked, same thing every time. Even tried different SD cards just in case of a mess up.
The phone itself works fine for now, calls and text work, wifi works. And it says there is an update, but when i hit accept, it reboots to recovery mode, does the "android fallen over" then boots back up.
Now here is my stupid part, I didn't backup the original cause the guide didn't say to. (Not blaming them, i should have know better) So I am assuming I have a messed up version of 4.3 and Cyanogenmod doesn't know what to do with me. I'm not sure. Here is where I am stumped and I have no idea where to go from here.
I posted this by accident in the wrong forum here
http://forum.xda-developers.com/galaxy-s3/help/tried-rooting-s3-didnt-help-t2879278
But someone decided to help me anyways (thank you so much). They said all i need to do is update my recovery. so I went here
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
And now I am running PhilZ 6.48.4, but I am still getting status 7 when I try to install CM11. I have tried CM10, CM10.1, CM10.2 and CM10.2.1 as well. I have been at this for days and i am going crazy because nothing I do seems to work. Does anyone have any idea what is wrong with my phone? Thank you so much in advance.
Mumonk said:
I am very new at this, so I apologize in advance. I have the Virgin Mobile Galaxy S3 SPH-L710 running 4.3.
I simply wanted to root it so i could get rid of the bloatware and install Sixaxis and play emulators, but I didn't really know where to start, so I started looking around and found this
http://forum.xda-developers.com/showthread.php?t=2546505
So I basically did everything on there. I used Odin to install PhilZ Touch 6 Recovery (CWM 6.0.4.7) Did factory reset, wiped cache/dalvik. then installed the Odexed MK5 stock rooted zip, wifi fix zip, SuperSU update zip, and then the knox app remover zip.
Everything flashed just fine and it started right up. It had the Super Su app, but when I tried to install apps that need root permission it would say I don't have root access. I couldn't delete bloat apps and Super Su didn't show any apps and there isn't much I can do with it. So I guess it didn't work? Either way I wanted to try a different rom. Was gonna give Cyanogenmod a try. But every time I try to install it I get the little "Android bot laying on his back" thing and it says status 7. I tried to flash CM10, CM10.1, CM10.2, CM11. Nothing worked, same thing every time. Even tried different SD cards just in case of a mess up.
The phone itself works fine for now, calls and text work, wifi works. And it says there is an update, but when i hit accept, it reboots to recovery mode, does the "android fallen over" then boots back up.
Now here is my stupid part, I didn't backup the original cause the guide didn't say to. (Not blaming them, i should have know better) So I am assuming I have a messed up version of 4.3 and Cyanogenmod doesn't know what to do with me. I'm not sure. Here is where I am stumped and I have no idea where to go from here.
I posted this by accident in the wrong forum here
http://forum.xda-developers.com/galaxy-s3/help/tried-rooting-s3-didnt-help-t2879278
But someone decided to help me anyways (thank you so much). They said all i need to do is update my recovery. so I went here
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
And now I am running PhilZ 6.48.4, but I am still getting status 7 when I try to install CM11. I have tried CM10, CM10.1, CM10.2 and CM10.2.1 as well. I have been at this for days and i am going crazy because nothing I do seems to work. Does anyone have any idea what is wrong with my phone? Thank you so much in advance.
Click to expand...
Click to collapse
only thing i can think of Is Odin the stock rom and start all over with trying to root......
I don't know how to explain it, but now everything is working perfectly....
I went back to the first site I posted about, Redownloaded everything, did the whole thing over, and root worked just fine. So I thought I would try my luck with CM11 and BOOM, working perfectly.
I have been tearing my hair out trying to get this to work for days and days and now, poof, it's all working. I dunno how, but I will take it. Thanks for the advice in both threads.
Mumonk said:
I don't know how to explain it, but now everything is working perfectly....
I went back to the first site I posted about, Redownloaded everything, did the whole thing over, and root worked just fine. So I thought I would try my luck with CM11 and BOOM, working perfectly.
I have been tearing my hair out trying to get this to work for days and days and now, poof, it's all working. I dunno how, but I will take it. Thanks for the advice in both threads.
Click to expand...
Click to collapse
Get towelroot, is an apk that root your phone with one click, after that just download your favorite super user from the market and done.

[Q] Bricked my phone... Need Help.

Like I'm sure this topic hasn't come up before, but I've searched for hours and I'm probably just making things worse. I also just accidentally deleted this post halfway through. It's too late and I'm too tired and I have no working phone.
Bought an SGH-I747 on E-Bay. Got a Straight Talk SIM card kit, activated it, so far so good.
Rooted it with CF-Auto-Root. Worked pretty well, took a lot of reboots, upgraded the SU from the Play Store and it got rid of Knox. So far so good. Got everything all set up the way I like it. Happy.
It was running 4.4.2. I'm assuming it was the release prior to the November 12th OTA release, but I can't say for sure.
Phone downloaded and installed an upgrade automatically. Now, it won't boot. I get the SAMSUNG logo, then the Samsung Galaxy S III logo then nothing.
I retried the CF-Auto-Root, no change.
I booted into recovery (volume up, home and power on), did factory reset, no change.
Started looking around for a way to return it to stock. Found an upgrade43.zip file somewhere (I'm sorry I can't find where I got that now). Put it on the sdcard card and tried installing it with the recovery and it fails part way through.
At this point, I think I probably need to completely overwrite everything with something stock. I just don't know how to do that. I see posts on such subjects but they all have warnings that make me think I'm going to totally brick the phone, so I'm hoping someone can point me the right way. I'm not all that Android savvy, as you can tell.
Help.
Since your phone was running 4.4.2, do not attempt to flash any ROMs using that attempt to downgrade your bootloader to anything prior to 4.4.2.
Try this to get your phone up and running:
download the latest CM11 for the d2lte and save it to an external SD card: https://download.cyanogenmod.org/?device=d2lte
dowload the latest tar.md5 version of Philz Touch for the d2lte from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
boot phone in download mode, open Odin 3.07, do not check anything except f.reset.time, flash Philz via PDA box, remove USB cable when you see the word Reset appear in the status window, remove battery, replace battery, boot into recovery, format system, Dalvik, data, and cache, flash cm11, and reboot.
Thank you for your reply. There are a few things in there I don't quite understand, but I think I can figure it out.
I was going to attempt this...
http://forum.xda-developers.com/showthread.php?t=2658486
In fact, I did attempt it with TWRP last night after I posted here and new I still wasn't going to sleep. I kept getting an error about a bad ZIP file.
Is that stock restore a bad idea?
Do not attempt to flash an older bootloader. The mjb bootloader is from 4.3 and attempting to flash it could hard brick your phone.
I suggest doing what I suggested so you can confirm the bootloader and modem installed on your phone.
OK. Thanks. Probably a good thing I couldn't get it to work then.
Thank you so much. I have a working phone again. Now I just have to get it all set back up the way I like it.
I have to say, and it's probably words straight from the devils mouth, that I kind of wish I could have restored the Samsung stock software. It's just what I'm used to. But I will take what I can get.
A few questions. I like having root. But root is what got me in trouble in the first place. Is this going to be rooted now, or will I have to do that or am I better off just leaving it alone.
Second, I'm probably going to have questions since this is so different than what I'm used to (like I already can't find the Play store). Where is the best place to ask?
If you want root, one of the easiest ways to get it is to flash supersu from your custom recovery. Most ROMs are pre-rooted.
Many custom ROMs do not include Gapps. Just download and install the Gapps version for your ROM.
If you like the TW look, flash a TW-based ROM. Check out the development threads for different ROMs.
here is a thread for Q's that has some pretty good/friendly helpers on it if you need.
http://forum.xda-developers.com/showthread.php?t=2257421
"all i can really do , is stay out of my own way and let the will of heaven be done"
How to save in to external SD card
How do you save the file into the external SD card? I am having the same brick issue with my GS3.
To save a file to an external SD card, just put the card into a card reader and save the ROM to the SD card.

Categories

Resources