Greetings,
I rooted my note using Da_G's process which worked great. I then tried to "unroot" it using the kernel pda-odin-att-stock-kernel.tar and it appears to be still rooted (Titanum Backup still gets root privs). Do I need to flash the 400MB .rar to remove root?
Thanks,
Bugly
I believe you need to follow the instructions here: http://forum.xda-developers.com/showthread.php?t=1506330
Don't forget the factory reset at the end.
Thanks for the reply...
I did use that particular process but since I only flashed the kernel to root it shouldn't I only have to flash the stock kernel to unroot?
Bugly
bugly said:
Thanks for the reply...
I did use that particular process but since I only flashed the kernel to root it shouldn't I only have to flash the stock kernel to unroot?
Bugly
Click to expand...
Click to collapse
No because a kernal by itself doesn't provide root. If you read Da_G's original post it says that the kernal runs an auto-root script on /system. That is where the root takes place. That is why when you flash only the kernal your system is still rooted. You must flash stock system as well.
Okay... that explains it...
Thanks for the help...
One more question if I might... If I just flash the kernel does this set things up for a successful OTA upgrade?
Thanks...
It's only guaranteed you will get OTA updates if the phone is completely stock. Sometimes rooting alone will still allow you to get OTA updates, but from what I've heard, it's very hit or miss.
However, if the trend continues from what was done with the Samsung Captivate, then any serious update for the phone will be via Kies and not OTA anyway.
Related
Help.
So, my boss asks me to root his thunderbolt, so I do. Then, he goes and tries to install an OTA update on the thunderbolt and wonders why it won't work. I get into work this morning and he says, "I need you to unroot my phone so I can install OTA updates"???
I'm very confused, but hey, he wants it unrooted. Problem is, I can pull the battery, startup like normal, boot into the rooted OS and immediately the thing shuts down and tries to install the OTA update he installed.
This results in the android guy and the triangle with an exclamation point in it showing and I can't go any further.
ADB DOES see the device when I do adb devices.
How do I push the stock ROM back on to the phone and have it update that back to stock?
Help.
WHY he wants the phone unrooted or even decided to update it with an OTA ROM is beyond me.
Please and thank you in advance.
Wrong section but if the bootloader still has s-off, I would install custom recovery again and flash the rooted ota rom.
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=1009423
You should be able to flash the latest ota by booting into bootloader. If adb is working then I believe you can...
adb reboot bootloader
here is a link to the file you will need with instructions...
how to flash the latest ota
1. I realized too late it was the wrong section, apologies.
2. I don't need to flash a ROOTED ROM, he wants this device back to being stock UNROOTED.
Can I, using recovery, flash PG05IMG_MR1_no_hboot.zip over what is there now and go back to unroot and stock?
I use an Evo and can do almost anything on that, but the thunderbolt is a little new to me. Not my device, shouldn't have offered to root it for my boss without knowing he was going to try to install an OTA update.
Any help with unrooting and reflashing the Stock OTA would be very helpful.
It's one of the big issues with running stock rooted. Nothing stopping it from trying to update itself and screw the pooch
Honestly, if he wants OTAs just for the latest goodies/stability and battery improvements he'd be better off with something cooked... Just my opinion though
Sent from my ADR6400L using XDA App
sanjsrik said:
2. I don't need to flash a ROOTED ROM, he wants this device back to being stock UNROOTED.
Any help with unrooting and reflashing the Stock OTA would be very helpful.
Click to expand...
Click to collapse
Hmmm - not sure why you didn't just use the link that I provided? I will quote from there...
Code:
Using this RUU will wipe all data on your device!
Please make a backup of all sensitive data before
proceeding. Similarly, you will [B]LOOSE ROOT IF
YOU FLASH THIS[/B]. It is unclear right now
whether or not this version is easily rootable.
[B]PROCEED WITH CAUTION[/B]
This is not a link to a rooted rom.
thepolishguy said:
Hmmm - not sure why you didn't just use the link that I provided? I will quote from there...
Code:
Using this RUU will wipe all data on your device!
Please make a backup of all sensitive data before
proceeding. Similarly, you will [B]LOOSE ROOT IF
YOU FLASH THIS[/B]. It is unclear right now
whether or not this version is easily rootable.
[B]PROCEED WITH CAUTION[/B]
This is not a link to a rooted rom. It is a link to the full unrooted ota ruu that has been put in a flashable (from hboot) PG05IMG.zip.
Click to expand...
Click to collapse
Update: Worked like a charm.
Thanks, polishguy, that wasn't clear originally, will follow your link. Much appreciated.
sanjsrik said:
Thanks, polishguy, that wasn't clear originally, will follow your link. Much appreciated.
Click to expand...
Click to collapse
No problem. It wasn't clear originally bc I am not sure how XDA views links to "this sort of file". As in a "Romeo Uniform Uniform"
thepolishguy said:
No problem. It wasn't clear originally bc I am not sure how XDA views links to "this sort of file". As in a "Romeo Uniform Uniform"
Click to expand...
Click to collapse
I would guess it's fine considering there are an abundance of RUU links in the dev section.
Hello All. I had installed SHOStock 3.0.1. Then I somehow thought that I will back ROM and that reminds me of ROM Manager which I installed ages back . Clicked on backup which restarted the phone and then phone didnt start ever. So I put back Stock Gingerbread UCKH7. But now after that when I am trying to update using AT&T software update, it is giving me error that software cannot be installed due to interrupation. When I try to install from Kies, office laptop does not recongnize my phone. Home laptop do recongnize the phone but gives message that this version of Android is not supported to upgrade by Kies. I dont know how shall I proceed. When I try to install stock ICS downlaoded from some XDA thread using ODIN, it is not doing anything. Tried to use Exynos Abuse to root but not working. Any other tool to root? Is it ok to directly install some Jelly Bean ROM after root on Gingerbread or shall I go for ICS first then JB? PS: Tried to read thr' all stickies and Q & A but could not find proper answer. Thanks in Advance.
I hope you didn't do any permanent damage by using rom manager. If you did all the reading you mentioned, you probably saw, after the fact, the sticky thread warning not to use rom manager.
First, you can not do an over the air update any longer; the only way to update officially is via kies. Not sure what is blocking kies, but you might try entering 3e recovery and performing a wipe data/factory reset, then see if kies will install the update. You do have to be bone stock for kies to work, I think. Rooted may be ok. Not sure exactly what elements causes kies to fail.
I mention the possibility of damage because you say:
When I try to install stock ICS downlaoded from some XDA thread using ODIN, it is not doing anything.
Click to expand...
Click to collapse
You should be able to flash any of the stock firmware via Odin.
If you want to go the custom firmware route, you can install a custom kernel, then use ClockworkMod Recovery to install your custom firmware. You should be able to do this from any version, Gingerbread, ICS or JB.
You can root by flashing one of the stock plus root packages. Exynos Abuse only worked with 4.0.3 I think. The exploit was patched. People have been using Framaroot to root stock 4.1.2, and I believe someone mentioned using it successfully on ICS as well. Results posted here have been mixed but generally successful.
There are several resources in the Download Repository. See the link in my signature.
Will try tonight
creepyncrawly said:
I hope you didn't do any permanent damage by using rom manager. If you did all the reading you mentioned, you probably saw, after the fact, the sticky thread warning not to use rom manager.
First, you can not do an over the air update any longer; the only way to update officially is via kies. Not sure what is blocking kies, but you might try entering 3e recovery and performing a wipe data/factory reset, then see if kies will install the update. You do have to be bone stock for kies to work, I think. Rooted may be ok. Not sure exactly what elements causes kies to fail.
I mention the possibility of damage because you say:
You should be able to flash any of the stock firmware via Odin.
If you want to go the custom firmware route, you can install a custom kernel, then use ClockworkMod Recovery to install your custom firmware. You should be able to do this from any version, Gingerbread, ICS or JB.
You can root by flashing one of the stock plus root packages. Exynos Abuse only worked with 4.0.3 I think. The exploit was patched. People have been using Framaroot to root stock 4.1.2, and I believe someone mentioned using it successfully on ICS as well. Results posted here have been mixed but generally successful.
There are several resources in the Download Repository. See the link in my signature.
Click to expand...
Click to collapse
Thanks. I will try tonight at home.
Try this to root if not already.. Framaroot.apk
http://forum.xda-developers.com/showthread.php?t=2130276
Sent from my SGH-I777 using xda app-developers app
It worked
creepyncrawly said:
I hope you didn't do any permanent damage by using rom manager. If you did all the reading you mentioned, you probably saw, after the fact, the sticky thread warning not to use rom manager.
First, you can not do an over the air update any longer; the only way to update officially is via kies. Not sure what is blocking kies, but you might try entering 3e recovery and performing a wipe data/factory reset, then see if kies will install the update. You do have to be bone stock for kies to work, I think. Rooted may be ok. Not sure exactly what elements causes kies to fail.
I mention the possibility of damage because you say:
You should be able to flash any of the stock firmware via Odin.
If you want to go the custom firmware route, you can install a custom kernel, then use ClockworkMod Recovery to install your custom firmware. You should be able to do this from any version, Gingerbread, ICS or JB.
You can root by flashing one of the stock plus root packages. Exynos Abuse only worked with 4.0.3 I think. The exploit was patched. People have been using Framaroot to root stock 4.1.2, and I believe someone mentioned using it successfully on ICS as well. Results posted here have been mixed but generally successful.
There are several resources in the Download Repository. See the link in my signature.
Click to expand...
Click to collapse
It worked.
I used your root to official ICS. Then I rooted Exynos to root. Thank you. Do I still need to have CWM after this? I am planning to install Helly Bean please let me know.,
guru1212 said:
It worked.
I used your root to official ICS. Then I rooted Exynos to root. Thank you. Do I still need to have CWM after this? I am planning to install Helly Bean please let me know.,
Click to expand...
Click to collapse
Assuming that Helly Bean uses a CWM flashable zip file, as almost all rom's do, then you will need to install a custom kernel containing a CWM recovery. You can not flash rom's from stock recovery or Odin.
Hello,
I have an LG Optimus L9 and I'm on Ice Cream Sandwich right now, the stock firmware that was there when I bought the phone. Now what I want to do, is backup the current ROM in its full state, then upgrade to Jelly Bean via the OTA updater from LG.
Then I want to return to my previously backed up ROM whenever I'll want to, and get the same state of ICS that I had before upgrading.
Is it even possible? I don't mind if I have to root it.
Thanks in advance.
Everything you mentioned is possible, but there's still trade-offs:
1) if you want EVERYTHING to be the same as now (ICS), including radio, u-boot, and x-boot, then you can always using fastboot to flash the u-boot, and x-boot, and then using offline flashing KDZ to restore STOCK ICS (with root) and then use ClockworkMod ROM Manager to Recovery your current backup;
2) I personally don't see the need for you to have radio, u-boot, and x-boot to come back to it's current state: JB radio, u/x-boot works fine with ICS ROM. So the simple thing to do for you is:
a) ROOT your current ICS
b) install ClockworkMod ROM Manager
c) backup (using CWM)
d) update to JB (keep root and CWM)
e) restore the backup from step c whenever you prefer
mrmathematica said:
Everything you mentioned is possible, but there's still trade-offs:
1) if you want EVERYTHING to be the same as now (ICS), including radio, u-boot, and x-boot, then you can always using fastboot to flash the u-boot, and x-boot, and then using offline flashing KDZ to restore STOCK ICS (with root) and then use ClockworkMod ROM Manager to Recovery your current backup;
2) I personally don't see the need for you to have radio, u-boot, and x-boot to come back to it's current state: JB radio, u/x-boot works fine with ICS ROM. So the simple thing to do for you is:
a) ROOT your current ICS
b) install ClockworkMod ROM Manager
c) backup (using CWM)
d) update to JB (keep root and CWM)
e) restore the backup from step c whenever you prefer
Click to expand...
Click to collapse
Yeah, I guess if keeping it in the same state is too complicated, restoring to the factory ICS would be fine too.
I'm still wondering though, if I do your process mentioned at step 2 above, will I get my bootloader unlocked? I'm a newbie in that kind of stuff, but I've seen articles mentioning something, that you can only unlock the bootloader when being on Jelly Bean.
Thanks again.
Voodoo rootkeeper is needed for you to retain root via ota. Or you can riot again if it's no problem.
Sent from my LG-P769 using xda app-developers app
YPwn said:
Hello,
I have an LG Optimus L9 and I'm on Ice Cream Sandwich right now, the stock firmware that was there when I bought the phone. Now what I want to do, is backup the current ROM in its full state, then upgrade to Jelly Bean via the OTA updater from LG.
Then I want to return to my previously backed up ROM whenever I'll want to, and get the same state of ICS that I had before upgrading.
Is it even possible? I don't mind if I have to root it.
Thanks in advance.
Click to expand...
Click to collapse
It's possible but rooting L9 ICS is not an easy one-click process. If you want to try, take a look here http://forum.xda-developers.com/showthread.php?t=2173465.
For what you want to do you should
1. Try to offline flash your current stock rom first. This make sure that you familair with offline flash and you can flash stock rom back if rooting process go wrong. Refer to http://forum.xda-developers.com/showthread.php?t=2085344
This process don't delete your data if you do it right.
2. Get modified .bin file for your rom if any. If there're no modified .bin for your rom, you must make one. It require editing binary file with hex editor. There're some thread about this somewhere in the forum.
3. Root your phone with http://forum.xda-developers.com/showthread.php?t=2173465. Almost same process as offline flash but you need to add some stuff to your phone and replace some files while flashing kdz.
YPwn said:
Yeah, I guess if keeping it in the same state is too complicated, restoring to the factory ICS would be fine too.
I'm still wondering though, if I do your process mentioned at step 2 above, will I get my bootloader unlocked? I'm a newbie in that kind of stuff, but I've seen articles mentioning something, that you can only unlock the bootloader when being on Jelly Bean.
Thanks again.
Click to expand...
Click to collapse
No you won't get your bootloader unlocked. It is true that only official P760 JB supports bootloader-unlocking, but that is an option, not a necessity (which you can deal later if you want to).
Also artit is right that ROOT ICS is not one-click process. I followed cmahendra's excellent tutorial and get things done on first try, but things differ for different person.
Root for JB
If you don't want to do the complicated root method for ICS then just wait until you upgrade to jelly bean and then go here. ICS was a bit difficult to root but once you do it then you can get it done with your eyes closed. Cmahendra has a great tutorial along with Lelus method it's great! Good luck!!
Nathan.7118391 said:
If you don't want to do the complicated root method for ICS then just wait until you upgrade to jelly bean and then go here. ICS was a bit difficult to root but once you do it then you can get it done with your eyes closed. Cmahendra has a great tutorial along with Lelus method it's great! Good luck!!
Click to expand...
Click to collapse
Yeah, I guess it's not that hard, I'll try to do it. It's similar to the method for flashing an LG KM900 which I had before (non Android). I'll try it and report here.
I hope I can find a KDZ matching by current firmware, though.
(P76010g-EUR-XX)
http://forum.xda-developers.com/showthread.php?t=2107971
Good luck!
Sent from my LG-P769(20F) using the xda-developers app. If I helped you please hit the "thanks" button.
Okay, so I managed to root ICS and install the recovery then backup my firmware.
Although when I installed the Voodoo OTA Rootkeeper and made a temporary unroot, I immediately went to the Software Update option on my phone. It downloaded the update and rebooted. Then soon after a while I got an error "Err:0x13e", then it rebooted back into Android and said something like "unexpected error occured while upgrading" (not precise message).
I'm stuck at this point. What should I do now? Has anyone experienced this before?
Thanks.
So are you saying your phone is dead or what? Did it reboot and die? More details please. And you weren't suppose to make a temp unroot, you were suppose to protect root.
Sent from my LG-P769(v20f) using the xda-developers app. Hit the thanks bottom, makes me feel good!
Nathan.7118391 said:
So are you saying your phone is dead or what? Did it reboot and die? More details please. And you weren't suppose to make a temp unroot, you were suppose to protect root.
Sent from my LG-P769(v20f) using the xda-developers app. Hit the thanks bottom, makes me feel good!
Click to expand...
Click to collapse
No, it's not dead. It throws an error "Err:0x13e" during the "Upgrading Firmware" stage, then it fails and reboots back to Android.
I tried everything in Voodoo OTA Rootkeeper, it still didn't work.
YPwn said:
No, it's not dead. It throws an error "Err:0x13e" during the "Upgrading Firmware" stage, then it fails and reboots back to Android.
I tried everything in Voodoo OTA Rootkeeper, it still didn't work.
Click to expand...
Click to collapse
The reason i't snot working is because of the custom recovery. you have to delete cwm so that the upgrade can boot to original recovery and upgrade your phone. Be sure to get into Voodoo and protect root. That will be important after you upgrade.
After the upgrade go into google play and install Voodoo then recover root.
Nathan.7118391 said:
The reason i't snot working is because of the custom recovery. you have to delete cwm so that the upgrade can boot to original recovery and upgrade your phone. Be sure to get into Voodoo and protect root. That will be important after you upgrade.
After the upgrade go into google play and install Voodoo then recover root.
Click to expand...
Click to collapse
Thanks, I see now. Though I decided to flash a Jelly Bean KDZ instead, then do a factory restore. Both my root and CWM were gone, so I rooted again using the LGPwn method, which worked just fine. Afterwards, I installed the same recovery I had on ICS, and now everything is working fine. :laugh:
I guess I don't have any more questions regarding my topic.
I've been on stock rooted ROM (MDK) for longest time w/ CWM recovery. I decided I wanted to get back on the update track after this recent update came out and is already rooted. I defrosted all apps, unrooted the device with Voodoo OTA rootkeeper, and uninstalled SuperSU. I then flashed stock firmware with Odin as explained here: http://forum.xda-developers.com/showthread.php?t=2301259
This didn't work. I get an error during install every time. After this I noticed when going into recovery (now stock) it would have an error immediately but then went into recovery. It would not let me clear the cache (after searching this seems to be common.) So I then did factory reset multiple times (didn't help) and next flashed a stock firmware that wipes my data. This had the same results as before. Do I have a corrupt recovery of some kind? Shouldn't flashing the stock firmware fix this? Do I need to get a new phone? Help!
zregnier said:
I've been on stock rooted ROM (MDK) for longest time w/ CWM recovery. I decided I wanted to get back on the update track after this recent update came out and is already rooted. I defrosted all apps, unrooted the device with Voodoo OTA rootkeeper, and uninstalled SuperSU. I then flashed stock firmware with Odin as explained here: http://forum.xda-developers.com/showthread.php?t=2301259
This didn't work. I get an error during install every time. After this I noticed when going into recovery (now stock) it would have an error immediately but then went into recovery. It would not let me clear the cache (after searching this seems to be common.) So I then did factory reset multiple times (didn't help) and next flashed a stock firmware that wipes my data. This had the same results as before. Do I have a corrupt recovery of some kind? Shouldn't flashing the stock firmware fix this? Do I need to get a new phone? Help!
Click to expand...
Click to collapse
i dont think you can update with an unlocked recovery... if you have cwm you have an unlocked recovery and i dont think you can relock it.
also you dont need to update if you have cwm then all you need to do is flash a MI1 rom (once they come out) and youre good. there is NO reason you would need to ACTUALLY update. you can flash pretty much everything whilst still keeping unlocked recovery under actual MDK firmware but with MI1 (or ME7) rom kernel and radios.
zregnier said:
I've been on stock rooted ROM (MDK) for longest time w/ CWM recovery. I decided I wanted to get back on the update track after this recent update came out and is already rooted. I defrosted all apps, unrooted the device with Voodoo OTA rootkeeper, and uninstalled SuperSU. I then flashed stock firmware with Odin as explained here: http://forum.xda-developers.com/showthread.php?t=2301259
This didn't work. I get an error during install every time. After this I noticed when going into recovery (now stock) it would have an error immediately but then went into recovery. It would not let me clear the cache (after searching this seems to be common.) So I then did factory reset multiple times (didn't help) and next flashed a stock firmware that wipes my data. This had the same results as before. Do I have a corrupt recovery of some kind? Shouldn't flashing the stock firmware fix this? Do I need to get a new phone? Help!
Click to expand...
Click to collapse
I would try using the me7 factory image that wipes everything and then try the upgrade.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
---------- Post added at 09:21 PM ---------- Previous post was at 09:19 PM ----------
reinaldistic said:
i dont think you can update with an unlocked recovery... if you have cwm you have an unlocked recovery and i dont think you can relock it.
also you dont need to update if you have cwm then all you need to do is flash a MI1 rom (once they come out) and youre good. there is NO reason you would need to ACTUALLY update. you can flash pretty much everything whilst still keeping unlocked recovery under actual MDK firmware but with MI1 (or ME7) rom kernel and radios.
Click to expand...
Click to collapse
There is no unlocked bootloader on the s4 what allows the installation of custom recovery is the loki exploit and its reversible.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
hexitnow said:
[/COLOR]
There is no unlocked bootloader on the s4 what allows the installation of custom recovery is the loki exploit and its reversible.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Click to expand...
Click to collapse
Thus the word think but thanks for the info...
hook the guy up with the link for reversing loki then
reinaldistic said:
Thus the word think but thanks for the info...
hook the guy up with the link for reversing loki then
Click to expand...
Click to collapse
There is no link or post on it really. Its a patched recovery and boot image so when you odin back to a factory image they get replaced with the non patched versions
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
zregnier said:
I've been on stock rooted ROM (MDK) for longest time w/ CWM recovery. I decided I wanted to get back on the update track after this recent update came out and is already rooted. I defrosted all apps, unrooted the device with Voodoo OTA rootkeeper, and uninstalled SuperSU. I then flashed stock firmware with Odin as explained here: http://forum.xda-developers.com/showthread.php?t=2301259
This didn't work. I get an error during install every time. After this I noticed when going into recovery (now stock) it would have an error immediately but then went into recovery. It would not let me clear the cache (after searching this seems to be common.) So I then did factory reset multiple times (didn't help) and next flashed a stock firmware that wipes my data. This had the same results as before. Do I have a corrupt recovery of some kind? Shouldn't flashing the stock firmware fix this? Do I need to get a new phone? Help!
Click to expand...
Click to collapse
I to am having same exact problem but im on me7 and was safstrapped????????
The advice from @hexitnow worked! I downloaded ME7 image here http://forum.xda-developers.com/showthread.php?t=2357235
It worked fine then I took the latest OTA. Thanks guys!:good:
Quick Qestion
I have a quick question, and i dont want to make a who new thread about it. But since we already talkin about it on here, is it worth it to do this Verizon update?? I just did a Verizon update 2 days ago. And now to me i think it just aggitated me. My Email are different now. My delete button moved and it added more buttons. And my task manager seems a lil different. Cant seem to put my finger on it.. But its weird. What else has changed? Was it even worth doing an update?
The first step for flashing Alliance was making sure i have the 4.3 firmware. Flashed via Odin.
I experfienced some trouble with a bootloop issue so i changed cables and then partitioned with the .pit file.
All's well now, it at least runs the stock firmware just fine. Now i'm strugglling with the most basic simple part IMO... how do i install the custom Rom without the recovery??
sduffy89 said:
The first step for flashing Alliance was making sure i have the 4.3 firmware. Flashed via Odin.
I experfienced some trouble with a bootloop issue so i changed cables and then partitioned with the .pit file.
All's well now, it at least runs the stock firmware just fine. Now i'm strugglling with the most basic simple part IMO... how do i install the custom Rom without the recovery??
Click to expand...
Click to collapse
You are rooted still correct? Easiest way I guess is to just download Rom Manager or GooManager depending on using TWRP or CWM.
KuNiT said:
You are rooted still correct? Easiest way I guess is to just download Rom Manager or GooManager depending on using TWRP or CWM.
Click to expand...
Click to collapse
I chose to bump up my android version cuz i friend another SIM card. I tether for my Hulu, Netflix, Amazon Prime, and whatever else, thankfully my laptop can get weak unsecured internet signals, but i'm walking my Note around the apartment trying to get good 1x reception Problems may be overlapping but next step is something basic from the Play Store to verify root.
I read of some luck with root for 4.3, just not bootloader. Am i correct?
KuNiT said:
You are rooted still correct? Easiest way I guess is to just download Rom Manager or GooManager depending on using TWRP or CWM.
Click to expand...
Click to collapse
Not rooted. it sounds like rooting is still an option, just not custom recovery?
Is using ODIN to flash stock rooted an option? No valuable files on phone currently.
(Fortunately I'm at work right now so I have time to make well informed decisions. Thanks for your help)
sduffy89 said:
Not rooted. it sounds like rooting is still an option, just not custom recovery?
Is using ODIN to flash stock rooted an option? No valuable files on phone currently.
(Fortunately I'm at work right now so I have time to make well informed decisions. Thanks for your help)
Click to expand...
Click to collapse
I believe if you took/flashed the OTA update, your kinda out of luck and stuck now. I'm not 100% certain of this though but I think it probably relocked the bootloader and the only thing to do is wait for someone to root/unlock 4.3.
KuNiT said:
I believe if you took/flashed the OTA update, your kinda out of luck and stuck now. I'm not 100% certain of this though but I think it probably relocked the bootloader and the only thing to do is wait for someone to root/unlock 4.3.
Click to expand...
Click to collapse
Correct. If you took the OTA it relocked your bootloader and you are stuck. You can still root the official 4.3 but you are stuck waiting until someone unlocks the bootloader. This means no custom ROMs/Recovery.
Which 4.3 firmware did you flash? If its the OTA then yes you're outta luck.
If you did follow the Alliance's rom thread. There is a 4.3 MJ9 firmware you need to flash. It doesn't have the locked bootloader. You are then able to boot up in the basic recovery and then flash either TWRP or CWM recovery.