Develop Bugs

02 root cwm to el29 last few questions please

OK, i used auto root for rooting 02 and installing cwm recovery. then i installed the hotspot mod. perfect, everything working as expected. well now im getting the update nag. sorry for asking repetitive questions, but i want to be sure i have this correct first.
so if i run preroot el29 one click and preserve user data, it will be like the ota update but with root?? then i need to go back into the autoroot option c to get cwm recovery installed again??
will the nag screen go away then for the update??
doing these steps will get me back to root, cwm, and the latest "ota" update?
thanks so much for the time,
Joel

You got it! If you do exactly what you said you will be stock el29 rooted with cwm and you won't get nagged to install an update anymore.

If you'd like to test it out, I put together a rooted EL29 OTA update.
http://forum.xda-developers.com/showthread.php?t=1473538
The advantage is it will patch your existing ROM rather than overwrite your ROM.
There are 2 versions provided. One is rooted. The other is rooted+CWM.
Keep in mind the only repacked EL29+CWM available is Rogue, which supports custom boot animations. The way it is configured, it uses the default Android logo boot animation. Nothing was changed on your ROM, the Sprint 4G animation is still there, just the initialization of the bootanimation was changed.

thanks guys, the rooted el29 and guide is in the sig odin el29 correct??
[ODIN][TAR] SPH-D710.EL29_CL852097 (EL29 Modem/Kernel/ROM - Full Restore - Rooted) ??
the rooted update sounds good, will that keep my cwm, or i need to reinstall it??
where can i find the update to patch my rom?? will i loose my root or cwm or anything with that one?? just need el29 to hotspot again, and root.
thanks again,
Joel
a14) EL29 OTA (patch EK02->EL29) - Sprint OTA [stock recovery] is that the patch method ?? then if i run the check and go that route, i loose root and cwm??
does rootkeeper work for going from 02 to 29 ??
ok found the [CWM][OTA][EK02->EL29] Rooted EL29 OTA update (patches your existing ROM) thread. soooo do i want the cwm option?? i will loose my old one or does this update it??
k, ran compliance check and failed system/framework.framework jar and odex and service odex. does that eliminate the patch?? i think the only thing was installing the hotspot hack.
42 years on the planet and i feel like its 42 days sometimes. heh

JS_racer said:
ok found the [CWM][OTA][EK02->EL29] Rooted EL29 OTA update (patches your existing ROM) thread. soooo do i want the cwm option?? i will loose my old one or does this update it??
Click to expand...
Click to collapse
Yes, that is the one, I forgot to put the link earlier.
There is only one CWM repacked with EL29 right now. It is Rogue CWM. You could run CWM repacked with an earlier kernel if you'd like, but if you want the EL29 kernel, there is just one choice. They also have a recompiled kernel based on EL29.

k, ran compliance check and failed system/framework.framework jar and odex and service odex. does that eliminate the patch?? i think the only thing was installing the hotspot hack

JS_racer said:
k, ran compliance check and failed system/framework.framework jar and odex and service odex. does that eliminate the patch?? i think the only thing was installing the hotspot hack
Click to expand...
Click to collapse
Well if you put the old ones back in place either because you backed up the file or did a nandroid backup prior to installing the hotspot hack, then you could put those back in place and run the rooted OTA. Otherwise go with one of the full updates that don't care what you currently have.

thanks so much, did the one click el29, still up and running so thats good.
was there anything funny with the cwm el29 from autoroot option c?? bootlogo or anything or it will look just like before. i have the hotspot files to transfer, guess just the jar files. should i do them by hand or install the cwm and install from sd and backup again ??
thanks so much for everything, much appreciated
Joel

Rogue CWM supports custom boot animation and it is initialized with the standard android bootlogo by default. That's the only stock EL29 repacked with CWM right now.
If it bothers you, you could run stock El29 and just install CWM when you need it, or you could install EL26+CWM (chris41gs repack) or I could dig up something to use the Sprint 4g animation. All the files are still there, just the initialization changed.

damn that was spooky, got stuck at the galaxy logo after a botched copy file operation. guess i need cwm to update the hotspot.
hit the oneclick 29 again, and it worked, damn.

EL29 unroot and then re-rooting

I searched and didn't get exact answer to easy my mind.
If I want to upgrade to EL29 I am rooted on stock EK02, I need to unroot and then re-root correct?
I have read some are seeing better wifi strength with EL29.
So my questions are:
(1) Is it worth it to go to EL29?
(2) Is it a simple process to unroot, do the update, then root again with the EL29 root one click? Is is the same steps as EK02

You don't need to unroot, if that is all you did. If, using your root powers, you installed CWM, uninstalled bloat, otherwise made changes to your ROM, then those would need to be undone *if* you wanted to apply an OTA patch-style update to get EL29.
EL29 plugged the exploit that was being used by Auto Root to root your phone, so EL29 cannot be directly rooted right now. However there are alternatives:
1) you could use the pre-rooted EL29 ODIN One-Click in my signature. After it is installed, use Option C in Auto Root to install CWM if you want it
2) you could use the rooted EL29 OTA udpate, also in my signature. Instructions are in the thread
3) you could flash the rooted EL29 update.zip that Calkulin put out, then flash the modem by hand. I don't have the link handy. Search the dev section.

sfhub said:
You don't need to unroot, if that is all you did. If, using your root powers, you installed CWM, uninstalled bloat, otherwise made changes to your ROM, then those would need to be undone *if* you wanted to apply an OTA patch-style update to get EL29.
EL29 plugged the exploit that was being used by Auto Root to root your phone, so EL29 cannot be directly rooted right now. However there are alternatives:
1) you could use the pre-rooted EL29 ODIN One-Click in my signature. After it is installed, use Option C in Auto Root to install CWM if you want it
2) you could use the rooted EL29 OTA udpate, also in my signature. Instructions are in the thread
3) you could flash the rooted EL29 update.zip that Calkulin put out, then flash the modem by hand. I don't have the link handy. Search the dev section.
Click to expand...
Click to collapse
I was about to respond.. but man sfhub, you are always on top of these type of posts! I've learned a lot from reading your posts. You're always very clear on instructions and don't assume everyone knows everything.

Am I clear that if I am stock rooted and accept the OTA, in order to root again I wud need a modified ROM... I wud not be able to root for just wifi tether??
sfhub said:
You don't need to unroot, if that is all you did. If, using your root powers, you installed CWM, uninstalled bloat, otherwise made changes to your ROM, then those would need to be undone *if* you wanted to apply an OTA patch-style update to get EL29.
EL29 plugged the exploit that was being used by Auto Root to root your phone, so EL29 cannot be directly rooted right now. However there are alternatives:
1) you could use the pre-rooted EL29 ODIN One-Click in my signature. After it is installed, use Option C in Auto Root to install CWM if you want it
2) you could use the rooted EL29 OTA udpate, also in my signature. Instructions are in the thread
3) you could flash the rooted EL29 update.zip that Calkulin put out, then flash the modem by hand. I don't have the link handy. Search the dev section.
Click to expand...
Click to collapse
Sent from my SPH-D710 using XDA App

dw0d said:
Am I clear that if I am stock rooted and accept the OTA, in order to root again I wud need a modified ROM... I wud not be able to root for just wifi tether??
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
There's no sense in accepting OTA updates anymore if you are rooted. We get it here on xda faster than sprint pushes them out. It will just break root anyway (assuming you haven't modified any system files, delete bloatware, ect). If you modified some stuff, the update would fail. I wouldn't bother with it. The easiest way would be to ODIN the pre-rooted EL29 stock in sfhub's signature. It'll update the modem, rom and stuff to EL29. Use the 'no-data' version if you want to keep all your data intact. That's what I did, coming from a stock EK02, only rooted.

Thx I will give a shot... XDA rocks
Sent from my SPH-D710 using XDA App

dw0d said:
Am I clear that if I am stock rooted and accept the OTA, in order to root again I wud need a modified ROM... I wud not be able to root for just wifi tether??
Click to expand...
Click to collapse
If you use the pre-rooted EL29 ODIN One-Click in my signature "modified ROM" is really just the addition of 3 files to the ROM to root it. Everything else is stock. It is exactly the same as if you ran Option A on your own ROM. It is just done for you. In fact, you could actually use Option B in Auto Root to unroot your phone and it would be 100% stock.
Same goes for the rooted EL29 OTA in my signature.

sfhub....Thanks for the tips. You showed me how to root a couple weeks ago and it has been great. I'm still cautious and didn't do many tweaks. I did freeze a few apps including voice command so I didn't have to use that every time I wanted to bluetooth dial.
So if I haven't made any major changes to the stock rooted EK02 I can just use the option #2 you said, right? And just pull it from your sig?

dw0d said:
Thx I will give a shot... XDA rocks
Click to expand...
Click to collapse
And this is why I love XDA.
Sent from my calculator watch.

jkhawk said:
I did freeze a few apps including voice command so I didn't have to use that every time I wanted to bluetooth dial.
So if I haven't made any major changes to the stock rooted EK02 I can just use the option #2 you said, right? And just pull it from your sig?
Click to expand...
Click to collapse
Yes, freezing is fine. Only uninstalling or modifying would cause the OTA to fail.
In the instructions for the EL29 OTA there will be an optional step to run the EK02->EL29 OTA Compliance Check. Just run that and it will tell you if anything is missing or changed. Takes around a minute. SHA1FAIL for kernel/zImage is expected. Any other MISSING or SHA1FAIL would need to be addressed.

[GUIDE] AT&T CWM-flashable UCALG1 update | no wipe, leaves root and universal search

[GUIDE] AT&T CWM-flashable UCALG1 update | no wipe, leaves root and universal search
I've put together a zip file with the I747UCLG1 AT&T OTA update that can be flashed using CWM. This file
does not trip the flash counter
preserves root
does not include the Google search update to remove universal search
does not wipe /data
does require removing all themes and modifications
Standard disclaimer: I am not responsible if this bricks your phone, destroys your IMEI or kills your kids.
Prerequisites: You have to be on stock I747UCALEM for this to work. It may be rooted, but all the standard AT&T and Samsung bloatware must be there with no modifications. It's okay if some of the apps are frozen with Titanium Backup. You must not have any other mods or themes applied. The updater will check this stuff and abort if anything is wrong. I personally restored a nandroid backup I made right after rooting. If you didn't make one, you can use Odin and the instructions here to go back to stock.
To apply it:
Boot into recovery and make a nandroid backup.
Go back to AT&T UCALEM rooted stock if necessary (see above). If you're already on stock UCALEM but have framework-res.apk modications applied, you can flash this zip to restore framework-res.apk to UCALEM stock.
Make sure CWM recovery from clockworkmod.com is installed. The recovery from Team Epic will not work. You can get a zip file to flash in your current recovery to install v5.8.4.5 from here. Use one of the first two files; the ones that start with "recovery-clockwork". After you flash the zip, restart recovery through the "advanced" menu. Your recovery should say "ClockworkMod Recovery" at the top and not "CWM-based Recovery".
Put one of the zip files from below on your internal or external SD card.
Boot into recovery
Wipe cache and dalvik cache (optional?)
Flash the attached zip
(Optional) Go to Backup and Restore, Advanced Restore and restore the /data from the nandroid backup you made in step 1. If you used a nadroid backup in step 2, this should restore your data and apps. If you used Odin to flash the rooted UCALEM image, this step isn't necessary.
Reboot
Open Settings / Application Manager. Choose All tab. Click on AT&T Software update. Clear "Clear data". If you were getting OTA notifications before, this will prevent them from recurring. After doing this, your phone will know it's up-to-date.
This worked for me. I checked that my flash counter is still at 0 and Google search is still finding local stuff like apps. I still have root.
DOWNLOADS:
I747UCALG1_OTA.zip: This is the full OTA, with kernel and bootloader. You must be using the stock UCALEM kernel for this to work.
I747UCALG1_OTA_No_Bootloader.zip: This is the full OTA without the bootloader.
I747UCALG1_OTA_No_Bootloader_No_Kernel.zip: This is the OTA without the bootloader or the kernel. You can use this if you're already running a non-stock kernel.
I747UCALG1_OTA_Bootloader.zip: This is just the bootloader. You can apply this along with the "no kernel no bootloader" zip above in case you want everything but the kernel.
MODS:
This process requires the stock framework-res.apk, so at this point you'll need to reapply any mods you already applied. Here are some mods that I've rebuilt against LG1. Both are zip files you can apply through recovery.
Tether and Cell Standby Fix: This includes the mod to enable native Bluetooth and WiFi tethering from here and the fix for the incorrect reporting of Cell Standby time from here.
Tether, Cell Standby Fix, Increase Autobrightness: The same as above, but also with a mod to bump up autobrightness levels from here.
No Increasing Ring: This removes the increasing ringtone volume. The mod is from here.
OTHER PIECES:
Kernel: The UCALG1 kernel and kernel modules.
UCLG1 Modem: Just the modem from the OTA.
UCLEM Modem: The modem from the stock UCALEM firmware.
UCALG1 Bootloader
UCALG1 Bootloader (no checks): This is the LG1 bootloader will all the checks for AT&T ROMs removed from the flashing script. This can be flashed even if you're running a non AT&T ROM, but only flash it on AT&T phones!
UCALEM Bootloader
UCALEM Bootloader (no checks): This is the LEM bootloader will all the checks for AT&T ROMs removed from the flashing script. This can be flashed even if you're running a non AT&T ROM, but only flash it on AT&T phones!
LIST OF CHANGES IN OTA:
A full list of the files and partitions changed by the OTA is attached to this post.

Only 10MB? Wonder what they updated... not much need for it for me, Im on AOKP, but downloading anyways, and thanx button hit TWICE LOL
Let us know if it's a lockdown flash...

B-Naughty said:
Let us know if it's a lockdown flash...
Click to expand...
Click to collapse
Doesn't seem to be. I still have my CWM recovery and I was able to flash the KT747 Sammy kernel. The OTA did flash aboot (the bootloader?) though. It tried to flash a new recovery, but I removed that part.

drothenberger said:
Doesn't seem to be. I still have my CWM recovery and I was able to flash the KT747 Sammy kernel. The OTA did flash aboot (the bootloader?) though. It tried to flash a new recovery, but I removed that part.
Click to expand...
Click to collapse
Hmmm... guess we'll just to see what users report, but for the wise, to all, use the zip provided just in case... AND FOLLOW THE OP

when i try to do this I'm getting an error assert failed: apply_patch_check("/system/app/Flipboard.apk" E: error in sdcard/I747UCLG1_OTA.zip

dave1977nj said:
when i try to do this I'm getting an error assert failed: apply_patch_check("/system/app/Flipboard.apk" E: error in sdcard/I747UCLG1_OTA.zip
Click to expand...
Click to collapse
Did you remove Flipboard or install an update?
You have to be on stock UCALEM. The OTA applies binary patches to a bunch of apps (including Flipboard.apk), so they have to be in a specific starting state for the OTA to apply correctly.

drothenberger said:
Did you remove Flipboard or install an update?
You have to be on stock UCALEM. The OTA applies binary patches to a bunch of apps (including Flipboard.apk), so they have to be in a specific starting state for the OTA to apply correctly.
Click to expand...
Click to collapse
yes backed up from day 1 it may have auto updated can someone tell me the stock version # of flipboard or an apk would be great! so i can install it?
Thanks

dave1977nj said:
yes backed up from day 1 it may have auto updated can someone tell me the stock version # of flipboard or an apk would be great! so i can install it?
Thanks
Click to expand...
Click to collapse
Here you go.

drothenberger said:
Here you go.
Click to expand...
Click to collapse
tried that still the same error message need some help please....

Hmm, may want to consider removing the bootloader parts from the CWM until it's verified what exactly our friends at ATT had Samsung add to this. Updating bootloaders never is a good thing when it comes to ATT

dave1977nj said:
tried that still the same error message need some help please....
Click to expand...
Click to collapse
What recovery are you using? Maybe give the CWM 5.8.4.5 a try (in the OP) if you're not already using it.

pinoymutt said:
Hmm, may want to consider removing the bootloader parts from the CWM until it's verified what exactly our friends at ATT had Samsung add to this. Updating bootloaders never is a good thing when it comes to ATT
Click to expand...
Click to collapse
I've put a version without a bootloader in the OP. Worked for me after I flashed stock rooted UCALEM with Odin.

drothenberger said:
I've put a version without a bootloader in the OP. Worked for me after I flashed stock rooted UCALEM with Odin.
Click to expand...
Click to collapse
So if I'm on stock LG1 I flash rooted LEM and then flash your zip? Does your update include the baseband update ?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

mobilehavoc said:
So if I'm on stock LG1 I flash rooted LEM and then flash your zip?
Click to expand...
Click to collapse
I don't think I understand. You're already on UCALG1, but you want to apply the OTA to go from LEM to LG1? Why?
If you do want to do that, you do need to flash the rooted LEM tar through Odin. Then follow the rest of the instructions in the OP.
Does your update include the baseband update ?
Click to expand...
Click to collapse
Yup. It includes everything except the Google search update, recovery, and (optionally) the bootloader.

I"m a bi confused too, but from a different perspective.
I am completely stock; got upgraded today to UCALG1. I am interested in rooting (and then possibly applying a kernel from this forum), but not sure which method I should use based on teh fact I am now on lg1.

Odin back to pure stock working fine.. some of my apps fore close though

drothenberger said:
I've put a version without a bootloader in the OP. Worked for me after I flashed stock rooted UCALEM with Odin.
Click to expand...
Click to collapse
Many thanks! You never know what kind of goodies they like to through in new bootloaders, so better safe than sorry!

ewingr said:
I"m a bi confused too, but from a different perspective.
I am completely stock; got upgraded today to UCALG1. I am interested in rooting (and then possibly applying a kernel from this forum), but not sure which method I should use based on teh fact I am now on lg1.
Click to expand...
Click to collapse
I think there are only two ways to get rooted LG1: Start with rooted LEM and use OTA Rootkeeper to keep root when you apply the OTA or use the method in the OP. In your case, you'd have to Odin back to the rooted LEM to get root, then if you want to go back to LG1, follow the OP steps.

ewingr said:
I"m a bi confused too, but from a different perspective.
I am completely stock; got upgraded today to UCALG1. I am interested in rooting (and then possibly applying a kernel from this forum), but not sure which method I should use based on teh fact I am now on lg1.
Click to expand...
Click to collapse
Depends which method of rooting you want to use. If you are interested in the method that does not trip the counter, then yes you would flash that through ODIN (which will technically revert you back to UCLEM with root injected) and then apply the update in the OP here and in the end you should be on a a rooted UCALG1 w/o a tripped counter.

Anyone wanna pull just the baseband for cwm zip?

Rooting a E4GT (SPH-D710) from Sprint

There is almost too much information on this forum!
All I would like to do is root my (wife's) phone in order to remove bloatware and install Ad Blocker, ideally without losing personal data. The phone's firmware was updated to FH13 yesterday using Kies and I am comfortable using Odin.
I read the entirety of this post, http://forum.xda-developers.com/showthread.php?t=1835033, along with several of the linked posts, and am still a bit confused. The OC upgrades are rather large and do not seem necessary since I am already running FH13. I downloaded the [ODIN] FH13 Kernel TAR.MD5, and can easily install this, but is there anything else I need in order to have root after installing this kernel?
Thank you.

Welcome to the E4GT.
Never too much information.
If as you've said you've already rooted the phone to FH13 and you are comfortable using Odin (I am hoping you mean you understand where to place the proper files and not just the 'one-clicks' - placing an update/tar/pit file in the wrong slot WILL kill your phone) you should probably grab Agat's latest safe kernel 5.4 here http://forum.xda-developers.com/showthread.php?t=1767421
Grab the tar and use Odin. Then you'll have a stock rooted phone with a safe kernel with recovery (CWM)
Seriously though taking a little time reading the stickies and how-tos will provide you with loads of information that can/will keep you from bricking your phone and save even more time being frustrated. Along with the added benefit of not being the one who killed your wife's phone.
Do you wife's phone right; have it all just work and be bullet proof and you'll be a hero. Kill it and you'll probably never hear the end of it.
Good luck.

leaderbuilder,
Thanks for taking time to reply.
To be clear, I have not yet rooted the phone - that is what I am trying to accomplish. I downloaded the kernel you referenced and loaded it using Odin. Upon reboot, I saw the yellow diamond with the exclamation point. Once the phone was up-and-running, I tried Root Checker and it indicated that the phone was not rooted. What step did I miss?
Thanks.

You have a couple of choices from the point at which you are at.
You can get the supersu zip, and flash in the phones recovery to root. http://forum.xda-developers.com/showthread.php?p=28086976
From here, you'll need to get triangle away and use to reset the flash count and clear the triangle.
You can also go ahead and use the rooted no data one click that you saw but didn't want to use to root, then use triangle away. But then you'll lose the recovery you just did and you'll have to do again.
Sent from my SPH-D710 using Xparent SkyBlue Tapatalk 2

MoHoGalore,
I was just reading another post in which you were helping a novice like me.
I removed the triangle by reverting to a stock kernel - so i am back where I started. What i don't understand is this: The kernel is ~8 MB, but the one-click download is ~285 MB. Since rooting seems to be related to a small (?) change in the kernel, and since the phone is already running FH13, what else is included in the OC that is being installed to the phone?

groston said:
MoHoGalore,
I was just reading another post in which you were helping a novice like me.
I removed the triangle by reverting to a stock kernel - so i am back where I started. What i don't understand is this: The kernel is ~8 MB, but the one-click download is ~285 MB. Since rooting seems to be related to a small (?) change in the kernel, and since the phone is already running FH13, what else is included in the OC that is being installed to the phone?
Click to expand...
Click to collapse
Howdy - and well, you have removed the triangle but you may not have reset the binary counter.. more on that in a min..
And having a custom kernel doesn't mean you're rooted. A custom kernel is a tool for rooted rom's. That is what a one click can do for you, or you can do, with that first step you took.. (And the one click is the "core" of the build that you're replacing, that is rooted. If that makes sense.)
So, here's a few line ups that I would do if I were you;
1. Odin a rooted rom tar (Crawrj has these avalible in current updates) http://forum.xda-developers.com/showthread.php?t=1844109 check out the first few posts, tells you all you need to do this. (The link is FH13. FH23 is said to be a dev build and has issues that are, well, going to be there..)
2.Odin a custom kernel (Which you did, and I guess now you're back stock) I had to change the order as I first posted. The rom tar will place stock recovery/kernel back. So you want to odin the custom kernel after the rom.
Or
1. Odin custom kernel. (Which you did, and I guess now you're back stock)
2. Using either superuser or supersu, root your rom (There are flash-able zips and tars for Odin)
3. Using triangle away, clear the triangle and reset binary counter.
Or
1. Get Garwynns One click no data and complete the operation in a few steps. (You can find that in RWilco's thread in post #2 - http://forum.xda-developers.com/showthread.php?t=1835033)
At the point that you do get rooted, and your on ICS, you need to run triangle away and confirm binary flash count if you ever want to send your phone in for service and want it not to show you flashed anything.. Just my suggestion.

[Q] Official 4.3 Upgrade Issues

I was on stock, un-rooted firmware version MD5. Went ahead with the official 4.3 upgrade through KIES. Don't like it, want to go back to stock MD5. Trying to ODIN back with official FW file (not the first time I've used this) and when I start, it fails and what is weird is that it appears the bootloader is changed as well from the 4.3 update. It has 2 new lines in the upper left corner (Warranty Bit: 0 and BOOTLOADER RP SWREV: 1) Now, once the ODIN failed, another line, in all red letters on the download screen underneath those previous mentioned lines, states
SW REV CHECK FAIL : Fused 1 > Binary 0. Any ideas? Phone works 100% on this new 4.3 from TMO, just cant seem to ODIN back to 4.1.2. Any help would be super. Thanks!

phoenix98 said:
I was on stock, un-rooted firmware version MD5. Went ahead with the official 4.3 upgrade through KIES. Don't like it, want to go back to stock MD5. Trying to ODIN back with official FW file (not the first time I've used this) and when I start, it fails and what is weird is that it appears the bootloader is changed as well from the 4.3 update. It has 2 new lines in the upper left corner (Warranty Bit: 0 and BOOTLOADER RP SWREV: 1) Now, once the ODIN failed, another line, in all red letters on the download screen underneath those previous mentioned lines, states
SW REV CHECK FAIL : Fused 1 > Binary 0. Any ideas? Phone works 100% on this new 4.3 from TMO, just cant seem to ODIN back to 4.1.2. Any help would be super. Thanks!
Click to expand...
Click to collapse
Is not possible for right now, until devs will create a new root app or something like superSU or I don't know ! :crying: Same to me ...

Your Boot loader is probably secured.
Try Root66 image and get back to UVDMD5 Rooted. From there, use Doc Holiday's thread to get 4.3 upgrade.

As it stands, right now if you flashed the official firmware or OTA, you will not be able to Odin flash any previous firmware. Maybe if you were never rooted....
For now though, you shoukd still be able to flash cwm/twrp and flash another rom. you will be limited to the 4.3 modem, but otherwise should be ok to run a 4.1.2 rom.
We are working on it.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2

I had the same problem
I just had this same problem and was lucky enough to fix it!!!!

vTizzle said:
I just had this same problem and was lucky enough to fix it!!!!
Click to expand...
Click to collapse
How/ What did you do you fix it? I'm stuck in a rut :l

I was trying to few things. But essentially I was trying to get back to a custom recovery so that I can flash a compatible rom. try flashing a recovery in Odin, stay away from the CWM. Flash to TW RP or something like that. I will try to help out more as soon as I get to my laptop
Sent from behind you

vTizzle said:
I was trying to few things. But essentially I was trying to get back to a custom recovery so that I can flash a compatible rom. try flashing a recovery in Odin, stay away from the CWM. Flash to TW RP or something like that. I will try to help out more as soon as I get to my laptop
Sent from behind you
Click to expand...
Click to collapse
Hm... Interestingly enough it worked! I flashed CWM 6.3.0 though, sent me straight into stock hehe :good::good: Though I'm still curious how long until I can root it

Have you tried the auto root course??
Sent from behind you

Boot recovery, then reboot system. It should ssk if you want to root.
Better yet, flash one of our roms. Or, download the supersu zip file from chainfires thread. (Or in my sig, but its not up to date)
---------- Post added at 09:12 PM ---------- Previous post was at 09:11 PM ----------
There are several ways to root. But if you don't get rid of knox iits almost pointless.

Co-author root didn't work, and nor did Root66

I'm on the same boat
Same here,
Mine was rooted, then
I Updated to Factory 4.3
Same red letters and can't get it back,
I want to 'cause it's unstable and
it has weird partition, "emulated/0"
Any Help Please !!

This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.

DocHoliday77 said:
This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.
Click to expand...
Click to collapse
If I did softbrick it, is there anyway to restore it?

You can try first wiping just dalvik and cache, then try factory reset.

Other ROMs
DocHoliday77 said:
This is why everyone should try to search for information on anything and everything before flashing it to your device. Even if its an official update.
As stated many, many times, once you flash the 4.3 update, you cannot flash older firmware again. Roms are ok, older firmware can brick you. Your weird folder is androids implementation of user profiles if I understand it right. May as well get used to it now, I don't think its going away.
And for those interested, the root66 firmware works fine now as far as I can tell.
If you experience instability, you need to factory reset.
Click to expand...
Click to collapse
Thank you Doc , It has been said ..Over and over and over.. OTA 4.3 update means you cannot flash older firmware again! I was one of the lucky that waited and installed you ROM and it has been stable . I placed a few Mods like Apps For 4.3 TW
For those just refused to READ and have NOT done a OTA update to 4.3 Like DocHoliday77 and and many have said .. here goes one more time..
WARNING!!!
If you have NOT updated via the official firmware or OTA update, it is highly recommended that you do NOT do so at this time!
You can still run these roms and gain every advantage, with none of the problems!
There so many other 4.3 ROMs to play with DocHolidays, Sarahai, mrRobinson and now aamir123. . YOu just to READ before run in head first into the OTA.

I have been trying to keep up with all the 4.3 update stuff but its just so hard with 15 different threads and it being updated everyday. I stupidly updated OTA 4.3 before coming on here and reading and it blows! Samsung is stupid for releasing such a unpolished update. But besides the point, I have been having a problem with out going calls, and battery life. When I will press to call someone the call ends instantly and I have to restart phone for it to allow me to call out. Has anyone else had this problem?
Also, are we any closer to getting 4.3 rooted? I know developers are having problems with Knox etc? If not is there anything I can do to make this update better or do I just have to suck it up? Thanks for the help guys.
I alrdy talked to people at samsung and complained beyond belief, but I dont think the out sourced help desk person understood me.

I made it !!
How ?
1. Uninstall KNOX with Titanium.
2. Flash CWM twice (first one failed), Now I have CWM.
3. Download T999UVDMD5 (Deodexed)
4. Flash it via CWM.
5. Voilà !!
Now It has the partition as it comes from Factory !.
It's there a version similar to this one, running on Android 4.3 (Stock Deodexed, Without KNOX) ?

DocHoliday77 said:
You can try first wiping just dalvik and cache, then try factory reset.
Click to expand...
Click to collapse
So I have a question Doc, I know I posted about this in the CM11 unofficial thread as well, but I am running your Non-Knox, CiQ free version and I have CWM installed, and I'm perfectly rooted after I updated SuperSU from the Play Store, but when I try to CWM Flash a rom it throws an error about the ro.bootloader and it lists out all the older bootloaders. So what I guess I'm getting to is what would it take to use the new bootloaders with any of the ROMs?

bentheexo said:
So I have a question Doc, I know I posted about this in the CM11 unofficial thread as well, but I am running your Non-Knox, CiQ free version and I have CWM installed, and I'm perfectly rooted after I updated SuperSU from the Play Store, but when I try to CWM Flash a rom it throws an error about the ro.bootloader and it lists out all the older bootloaders. So what I guess I'm getting to is what would it take to use the new bootloaders with any of the ROMs?
Click to expand...
Click to collapse
If you have updated to official 4.3 by any means then don't try to downgrade your boot loader and rom as it may brick device
If you have not taken official update then it depends what is your current boot loader and what rom you are trying to flash
So if you are sure that you haven't gone for official update then you flash dmd5 firmware then try to flash rom
Be sure before doing anything
Sent from my SGH-T999 using Tapatalk