Related
Samsung just released the first firmware update today... i installed it but cant find any info online anywhere about what all it changed/fixed? anyone have more info on this?
There's a post in general about it coming soon. I haven't gotten it yet, anyway to extract it and host it? just in case they release it in phases. According to the other post, you can install it via OTA, Store, or home computer, so it should be available to the masses soon.
Always the same first question... Does it kill root?
Sent from my SPH-D700 using Tapatalk
Same usual first question: Does it kill root?
Roger
Sent from my SPH-D700 using Tapatalk
Sorry about the double post. Got an fc and then didn't show.
I got the update a bit ago. Phone rebooted to install...there was an error but I didn't get to see what it was. Phone rebooted again and is going fine now. Titanium backup still shows root. I went to about phone and it shows 2.1_update 1. I read media hub was supposed to be enabled but mine still says check later...I'm wondering if my phone didn't actually update. I will see what others say about their updates.
Oh and my specs...one click rooted with andromeda kernel and adw launcher...pretty much stock other than that
Sent from my Epic 4G using Tapatalk Pro
i have had 2.1 update one since i first got my phone... :-( i was soo excited about an update ... I want the puzzle unlock
Firmware version 2.1-update1 has been out for weeks. It was on my phone when I bought it at the beginning of the month.
done12many2 said:
Firmware version 2.1-update1 has been out for weeks. It was on my phone when I bought it at the beginning of the month.
Click to expand...
Click to collapse
This is what I thought too. I knew I saw the update 1 on my phone when I got it...Well anyway, an update was pushed to my phone this morning and it looks like the installation failed. I try to update firmware again, but nothing. I wonder if root is keeping it from installing. I haven't done anything else to the phone that would stop an update. Might have to side load the update when it comes out on the website.
done12many2 said:
Firmware version 2.1-update1 has been out for weeks. It was on my phone when I bought it at the beginning of the month.
Click to expand...
Click to collapse
Different update. This is di07, phone came with dg27
Sent from my SPH-D700 using XDA App
JojoSteez said:
This is what I thought too. I knew I saw the update 1 on my phone when I got it...Well anyway, an update was pushed to my phone this morning and it looks like the installation failed. I try to update firmware again, but nothing. I wonder if root is keeping it from installing. I haven't done anything else to the phone that would stop an update. Might have to side load the update when it comes out on the website.
Click to expand...
Click to collapse
Probably the custom kernel. I haven't even rooted yet, want to wait to see of this blocks root, but probably won't, at least not entirely. May reset root, but it should be rootable again. I thought the root method was a general 2.1 exploit, not really specific to the epic.
Sent from my SPH-D700 using XDA App
rufflez2010 said:
Probably the custom kernel. I haven't even rooted yet, want to wait to see of this blocks root, but probably won't, at least not entirely. May reset root, but it should be rootable again. I thought the root method was a general 2.1 exploit, not really specific to the epic.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
That's what I figured...I could flash back to stock I guess, but might be moot if the phone can't find the update again. It was pushed to me to begin with and now it's like it never happened...
rufflez2010 said:
Different update. This is di07, phone came with dg27
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I still have dg27 so it seems my update just failed. It's gotta be the custom kernel then. hmm...what to do, ha
Well, update: I was trying to use Odin to flash the stock kernel back on and I bricked the phone, haha. It wouldn't boot after trying to flash with Odin. IT was stuck on a screen with a picture of a phone, a computer and a caution sign in between. I looked around and it seems the only option is to flash back to stock. That worked like a charm in Odin...dunno who the stock kernel wouldnt flash...oh well. So now everything works again. Took like 5 min to flash and reboot, then another 20 to put it all back like I had it. ADW, Dropbox, and Appbrain are my friends, ha.
Anyway, with the stock kernel the update pushed again and installed fine. I have access to media hub now and whatever else was pushed with this update. It seems the update didn't like the kernel. But all is good now, I just have to root again. I think I'm gonna leave the stock kernel this time though.
JojoSteez said:
Well, update: I was trying to use Odin to flash the stock kernel back on and I bricked the phone, haha. It wouldn't boot after trying to flash with Odin. IT was stuck on a screen with a picture of a phone, a computer and a caution sign in between. I looked around and it seems the only option is to flash back to stock. That worked like a charm in Odin...dunno who the stock kernel wouldnt flash...oh well. So now everything works again. Took like 5 min to flash and reboot, then another 20 to put it all back like I had it. ADW, Dropbox, and Appbrain are my friends, ha.
Anyway, with the stock kernel the update pushed again and installed fine. I have access to media hub now and whatever else was pushed with this update. It seems the update didn't like the kernel. But all is good now, I just have to root again. I think I'm gonna leave the stock kernel this time though.
Click to expand...
Click to collapse
Let us know if battery life is any better.
Sent from my SPH-D700 using Tapatalk
Samsung's build number is always easy to read.
A, B, C, D, ... : month.
January, February, March, etc. G means July, therefore.
27 means July 27th: the date of kernel/firmware build.
So DI07 means September 07, which is fairly new.
http://community.sprint.com/baw/message/213524
Here is a Sprint Admin talking about it. It is an official release as of today. He has all the fixes listed too.
it is a 2.1 exploit through adb actually so this shouldnt be of any worries to us
Just got a pop up on my phone about the update. Accepted it and told it to apply. Phone rebooted, then showed an error when trying to apply the update. Hit the Home button and phone rebooted. No further notifications now about the update. Went in and manually checked and it tells me none are available. So,..I guess you only get one shot at the update and then you're skipped??
anyone that is rooted with stock kernel able to update and keep root?
wait what update? i checked for an update but there wasnt one.
Okay first off, i know this is the wrong section. I can not post in development because I am new here, but I am in need of help desperately. Okay so I am rooted on 1.85 and the bootloader is NOT unlocked. Well i decided today to take the update to 4.0.4 before I did research. (Stupid me eh?) Well I start the OTA and then do some research. I learn that the update to 4.0.4 might be harmful to rooted users. So I disconnect from WiFi knowing it will pause the download. Well now I have a download that is just paused in the notification bar, and any time i connect to wifi it will continue the download. While the download is paused, can i unroot and take the update safely? I have seriously been searching for hours on end to find someone with a situation that I am in and i can not.
If you do a factory reset the update will go away. But that would also make you loose root. You should unlock the bootloader, then flash the rooted 2.20 update from the dev section.
Sent from my HTC One XL using xda app-developers app
Yep, get that bootloader unlocked immediately and flash a rooted stock ROM or a custom ROM. Make sure you backup all your stuff with Titanium because the bootloader unlock will wipe your phone.
Also, just so you know, this thread most definitely did NOT belong in development, which is reserved for ROMs and kernels and root guides and the like ONLY. Threads like this belong in Q+A but nobody is gonna kill you for posting it in General.
After the download, you should get a prompt to either Install, Postpone, or you can press the "back" capacitive button to cancel. Cancel should stop the update notifications. At least this is how its worked on past HTC OTAs. I personally can't verify, as I haven't gotten the notification yet. But others seem to verify this: http://forum.xda-developers.com/showthread.php?t=1817429
But if you want to be safe, you should SuperCID and unlock bootloader first, as others have suggested. Pressing the wrong button for the method I suggested above will be catastrophic otherwise (lose the ability to root and unlock BL).
Thanks for your help guys!
I just did a factory data reset on my phone. Honestly, I've gotten myself into trouble with rooting. I really need to read up before i continue with things of this sort. So since i did a factory data reset, am i 100% unrooted? Will i be safe to take the OTA now? Thanks for your help guys!
If you were stock 1.85, and rooted using the one-click or "manual" method (which you must be, if you you are still BL locked), then you are now unrooted. You are either rooted or not, there is no "percentage" of rooted.
What kind of trouble have you gotten into rooting, and what do you typically use root for?
I've been debating on whether or not to just go ahead and install the OTA to 2.2. The only thing I've used for root was for WiFi-Tether and I don't even use that anymore so I think I don't even necessarily NEED root anymore. I'm just tired of the updater telling me there's a new update to install - frankly very annoying. I've been just using the back capacitive button to cancel it. BUT, the last time I did this when 1.73 went to 1.85, I was just stock rooted, no unlocked BL (just like I am now), when I tried to install the OTA, went to that error with the triangle and exclamation point and wouldn't let me install it. I had to reflash to stock RUU because it was giving me a bootloop. I just don't want that to happen again... What does that triangle and exclamation point even really mean? I can't find a definitive answer on it. Shouldn't the OTA just install as normal, but it'll remove root in the process?
extol1337 said:
BUT, the last time I did this when 1.73 went to 1.85, I was just stock rooted, no unlocked BL (just like I am now), when I tried to install the OTA, went to that error with the triangle and exclamation point and wouldn't let me install it. I had to reflash to stock RUU because it was giving me a bootloop. I just don't want that to happen again... What does that triangle and exclamation point even really mean? I can't find a definitive answer on it. Shouldn't the OTA just install as normal, but it'll remove root in the process?
Click to expand...
Click to collapse
Red triangle and exclamation point is the stock recovery. This appears if something about the ROM is missing or corrupted. Not sure why this happened to you in that particular case. But installing OTAs on rooted phones is always a crap shoot. Sometimes it works, and you just lose root. Sometimes you boot loop or other things.
redpoint73 said:
Red triangle and exclamation point is the stock recovery. This appears if something about the ROM is missing or corrupted. Not sure why this happened to you in that particular case. But installing OTAs on rooted phones is always a crap shoot. Sometimes it works, and you just lose root. Sometimes you boot loop or other things.
Click to expand...
Click to collapse
That's what I was afraid of. Actually, I remember trying to install the 2.2 OTA a few days ago as well. Same red triangle and exclamation point. This time wasn't a boot loop and I just rebooted again and ever since, just kept canceling the update. Not sure what's going on...
extol1337 said:
That's what I was afraid of. Actually, I remember trying to install the 2.2 OTA a few days ago as well. Same red triangle and exclamation point. This time wasn't a boot loop and I just rebooted again and ever since, just kept canceling the update. Not sure what's going on...
Click to expand...
Click to collapse
Is the update actually downloaded to your phone? You may need to locate and delete it.
It may be trying to install the OTA from recovery, which makes sense. Don't actually know what happens when an OTA installs.
I've never installed an OTA! I'm always rooted, always will be!!!!
Just to be sure.
I did a factory data reset the night of the problem, been good ever since! I have not done anything to the phone except install a few apps. Should i be okay to take the OTA now? Sorry i just really want to be sure. This is my 3rd phone is 3 months so... no second chances.
SOLVED
Okay, so i took a chance on the update. It worked! I will not be rooting anymore until i read up. Sorry guys if you feel this thread was unnecessary. Just an FYI to any who are worried about taking the newest update after a factory data reset, don't be! Thank you to all:highfive:
Did everyone got an update ?
I still do not see update notification
From beast called HTC One X
It's a little late for this probably but for future reference if you are rooted and want to stop receiving OTA updates remove/rename/delete HtcOMADM_ATT.apk and HtcOMADM_ATT.odex from system/apps, wipe cache and dalvik. If you want to remove "AT&T software update" from the "Settings" then remove HtcOMADM_SettingsPlugin_ATT.apk and HtcOMADM_SettingsPlugin_ATT.odex from system/apps, wipe cache and dalvik.
wantabe said:
It's a little late for this probably but for future reference if you are rooted and want to stop receiving OTA updates remove/rename/delete HtcOMADM_ATT.apk and HtcOMADM_ATT.odex from system/apps, wipe cache and dalvik. If you want to remove "AT&T software update" from the "Settings" then remove HtcOMADM_SettingsPlugin_ATT.apk and HtcOMADM_SettingsPlugin_ATT.odex from system/apps, wipe cache and dalvik.
Click to expand...
Click to collapse
Excellent info!
ssteven232 said:
Okay, so i took a chance on the update. It worked! I will not be rooting anymore until i read up. Sorry guys if you feel this thread was unnecessary. Just an FYI to any who are worried about taking the newest update after a factory data reset, don't be! Thank you to all:highfive:
Click to expand...
Click to collapse
Looks like you will not be rooting anymore for a while now, since there is no method to root the 2.2 update. AT&T / HTC made sure the current rooting method won't work on it. Hopefully, the devs will eventually crack this one too.
I hope you knew that before making the dive ... I would have just unlocked the bootloader and flashed a ROM with the update baked into it to get the best of both worlds. But that's just me. I can't own an android without root access. To reach his own.
Sent from my HTC One X using xda app-developers app
borets.boris said:
Looks like you will not be rooting anymore for a while now, since there is no method to root the 2.2 update. AT&T / HTC made sure the current rooting method won't work on it. Hopefully, the devs will eventually crack this one too.
I hope you knew that before making the dive ... I would have just unlocked the bootloader and flashed a ROM with the update baked into it to get the best of both worlds. But that's just me. I can't own an android without root access. To reach his own.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yeah, I hear what you're saying and you are right. The current rooting method does not work with the new hboot. But.... If you have your bootloader unlocked beforehand you can still still get root after taking the OTA... And you can still flash a custom rom afterwards, from what I understand you would just need to fastboot flash the boot.img. I haven't personally tried it because I like staying fairly stock, just seriously cleaned up with some mods (init.d support, wifi/usb tethering, missing apps replaced). One thing I am curious about and to be honest I haven't spent any time researching the answer, what kernel are the roms using that are based on the 2.23 (4.0.4) Asian RUU? I wonder because I know the combination of the AT&T 2.20 (4.0.4) update with the new kernel and radio is working very, very well on my phone! My quadrant went up 800 points and battery life is still ridiculously good! I also have to agree with "I can't own an android without root access" especially on AT&T. Personally I'm good to go until the Jelly Bean update! Decisions, decisions! :laugh:
wantabe said:
Yeah, I hear what you're saying and you are right. The current rooting method does not work with the new hboot. But.... If you have your bootloader unlocked beforehand you can still still get root after taking the OTA... And you can still flash a custom rom afterwards, from what I understand you would just need to fastboot flash the boot.img. I haven't personally tried it because I like staying fairly stock, just seriously cleaned up with some mods (init.d support, wifi/usb tethering, missing apps replaced).
Click to expand...
Click to collapse
I've never installed an OTA, so I wouldn't know either. Honestly, I don't know why one would do that, when the awesome devs here post ROMs with the latest OTAs and root prebaked into them. There are "modded" ROMs and "stock" (or close to stock) ROMs available to everyone's taste.
wantabe said:
One thing I am curious about and to be honest I haven't spent any time researching the answer, what kernel are the roms using that are based on the 2.23 (4.0.4) Asian RUU? I wonder because I know the combination of the AT&T 2.20 (4.0.4) update with the new kernel and radio is working very, very well on my phone!
Click to expand...
Click to collapse
Right now, I'm running CleanROM 4.5, which is based on the 2.23 RUU. I did install the 2.20 radio, thinking it would work better, since I'm on AT&T. I took a screenshot of the kernel screen for you.
wantabe said:
My quadrant went up 800 points and battery life is still ridiculously good!
Click to expand...
Click to collapse
Where was your improvement? Did the increase happen in the aspect/area that directly affects your daily use, or in some esoteric algorithm that the phone all of a sudden processes faster? I used to go crazy on quadrant scores, but now I don't really understand their value/accuracy. As long as the phone feels buttery smooth while lasting 5+ hours of screen time, I'm happy!
Since you're interested in the scores, I installed quadrant and ran it, so you can compare.
Sent from my HTC One X using xda app-developers app
in admiration, totally confused!
borets.boris said:
Right now, I'm running CleanROM 4.5, which is based on the 2.23 RUU. I did install the 2.20 radio, thinking it would work better, since I'm on AT&T. I took a screenshot of the kernel screen for you.
Click to expand...
Click to collapse
Hi, do you think you could point me in the right direction for this? I found the general thread on radios, but am at a total loss about what it means or what to do with it!
You knew this was the wrong section but posted here anyway? Not a good way to start your membership on XDA. First rule of thumb is to search before creating a thread. Google is a great source for information. For future reference, all questions belong in the Q&A section, where coincidentally, this is being moved to.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my HTC One X, using XDA Premium.
I was laying in bed (with food poisoning) trying to get some sleep, when I noticed my phone vibrated and randomly rebooted.
After it booted up to the Andy firmware update image, and finally to the home screen with the update message I knew I was screwed.
THIS WAS A FORCED UPDATE BY VERIZON. I NEVER ACCEPTED OR DECLINED ANYTHING (re: food poisoning)!
You WILL lose root, on device app searching (Apple legal bs), and probably your unlock!
The perfect end to a perfect night! THANKS Verizon! /sarcasm
mcduck$ said:
I was laying in bed (with food poisoning) trying to get some sleep, when I noticed my phone vibrated and randomly rebooted.
After it booted up to the Andy firmware update image, and finally to the home screen with the update message I knew I was screwed.
THIS WAS A FORCED UPDATE BY VERIZON. I NEVER ACCEPTED OR DECLINED ANYTHING (re: food poisoning)!
You WILL lose root, on device app searching (Apple legal bs), and probably your unlock!
The perfect end to a perfect night! THANKS Verizon! /sarcasm
Click to expand...
Click to collapse
What ROM were you running? It should have disable OTA's thats why I ask.
Brian Gove said:
What ROM were you running? It should have disable OTA's thats why I ask.
Click to expand...
Click to collapse
The title says rooted stock.
I was runing the stock touchwiz rom (with the VRGL2 or 1 baseband) rooted, stock recovery, and the bootloader unlocked.
I just checked the EZ unlocker app and it claims that the bootloader is still unlocked. I have no way of verifying this, but if true, I'm only half screwed until somebody finds a root method for the new firmware.
If/when that happens I'll be more than happy to flash away from Verizon's bs nonsense.
Grrr...
mcduck$ said:
I was runing the stock touchwiz rom (with the VRGL2 or 1 baseband) rooted, stock recovery, and the bootloader unlocked.
I just checked the EZ unlocker app and it claims that the bootloader is still unlocked. I have no way of verifying this, but if true, I'm only half screwed until somebody finds a root method for the new firmware.
If/when that happens I'll be more than happy to flash away from Verizon's bs nonsense.
Grrr...
Click to expand...
Click to collapse
Did you try re-rooting using current methods?
mcduck$ said:
I was runing the stock touchwiz rom (with the VRGL2 or 1 baseband) rooted, stock recovery, and the bootloader unlocked.
I just checked the EZ unlocker app and it claims that the bootloader is still unlocked. I have no way of verifying this, but if true, I'm only half screwed until somebody finds a root method for the new firmware.
If/when that happens I'll be more than happy to flash away from Verizon's bs nonsense.
Grrr...
Click to expand...
Click to collapse
Wow rooted stock with stock recovery. Why not custom recovery? That probably the reason the update went through. Still ridiculous though, don't get me wrong. I'm guessing you weren't doing a lot of flashing.
Sent from my Nexus 7 using Tapatalk 2
Zalithian said:
Did you try re-rooting using current methods?
Click to expand...
Click to collapse
Negative. I currently feel like crap (see OP) and don't feel like messing with my Windows laptop to try it.
Do you think there's any chance I could brick my phone when I attempt it? Or is it simply a will work/won't work thing?
mcduck$ said:
Negative. I currently feel like crap (see OP) and don't feel like messing with my Windows laptop to try it.
Do you think there's any chance I could brick my phone when I attempt it? Or is it simply a will work/won't work thing?
Click to expand...
Click to collapse
Pretty sure it will just work or fail, but I'd wait for confirmation from someone else first - better safe than sorry.
Can you supply your new Baseband Version number?
I just froze sdm 1.0. I went to the software update and it crashed. I so let's hope that stops the update...
Sent from Land Line using pay phone
epikos said:
Can you supply your new Baseband Version number?
Click to expand...
Click to collapse
I535VRLG7
epikos said:
Can you supply your new Baseband Version number?
Click to expand...
Click to collapse
marcucci217 said:
Wow rooted stock with stock recovery. Why not custom recovery? That probably the reason the update went through. Still ridiculous though, don't get me wrong. I'm guessing you weren't doing a lot of flashing.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I was going to play around with flashing different roms eventually, but after upgrading from a decrepit half working ICS flashed Droid X I was just happy to have fully working phone again. Unfortunately I was under the false impression that the jerks at Verizon would have given me the option to accept their so-called upgrade.
Didn't they already remove local search on Verizon? My phone came that way. Of course I didn't stay on stock once we were freed...
rooting with the rootdebugfs tool should still work!
I woke up to a failed update message. Ran the update again to see why it failed and it fails because it reboots into custom recovery. Rooted, unlocked, stock. Just have some apps disabled or frozen.
Can anyone point out where the in the directory the downloaded update zip would go to?
I didn't get an update message but I did check for one it was available for me. So I ticked ok and it downloaded but failed to update as expected because of the custom recovery I have in place.
But I can't find where the zip file download to.
I wanted to try and see if Chainfire's Mobile ODIN Pro would root the updated zip as it claims.
Cache>fota>update zip...you'll see it
sent from my freed beast...&ikiller
Yes my laziness allowed verizon to update both of my SGS3 to I535VRLG7. I hope I can reroot when I get a chance later.
I was running stock root on both devices.
Sent from my SCH-I535 using xda premium
Successful OTA Flash using Mobile Odin Pro and Kept Root/Unlocked Status
Hulk0069 said:
Cache>fota>update zip...you'll see it
sent from my freed beast...&ikiller
Click to expand...
Click to collapse
Thanks, running a backup now before I try Mobile ODIN Pro. Will update this post:
Edit: Ok, it seems I have a successful flash using Mobile ODIN Pro.
Mobile Odin Pro gave me some Warnings in advance before continuing the Flash.
1) EverRoot may need to remove Google Maps during the flash to free up some space... yadda yadda..
2) The Modem Image on your device does not match the signature check....yadda yadda..
3) 5 out of 499 system files do not match the signature checks in the OTA zip... yadda yadda..
NOTE: I disabled signature checks on both warnings before proceeding.
But you do that AT YOUR OWN RISK!!
From what I gather, Mobile Odin made its own OTA zip from the target file before flashing it
I"ve uploaded some screen shots.
IMPORTANT!
PLEASE RUN A BACK UP before attempting anything risky like this.
ALSO! and VERY IMPORTANT!!
If you are using CWM as your recovery PLEASE PLEASE PLEASE check the size of your backup before proceeding with the update.
It seems CWM is not working properly on my SGSIII because the backup file sizes were only about 22 MB's large.. and thats is SO NOT GOOD!!
I went into GooManager and Flashed TWRP over CWM and ran a backup via TWRP and checked the file size to be in the range of 2.34GB's and thats what it should be (IMO). The only thing that bugs me about both recoveries is the date is 1979-12-31.. and thats definately wrong..
Anyways, my way of checking for root after an OTA is to run Titanium Backup because it always asks for SuperUser Rights before loading.
So all is well with that and checking to see if the Bootloader on my device was still Unlocked with EZ-Unlock said it still was..
Thats all I can think for now..
Hulk0069 said:
Cache>fota>update zip...you'll see it
sent from my freed beast...&ikiller
Click to expand...
Click to collapse
Stock rooted & it tried & failed 2x to do the update and there is nothing in /fota/
I still have root
Second attempt it booted into recovery & I just restarted as it had a fail error
I have a rooted, unlocked SG3 running stock ROM and as of a couple weeks ago, continue to get prompted to install the OTA update (VRAGL7 I believe). Unsurprisingly the install fails when I try to apply it.
My question is, do I have to restore in order to apply this update? And if so, is it possible to instead defer the update indefinitely (since I dont want to restore and there doesnt appear to be anything useful in this update according to their site).
Im also sure someone else must have asked this before, but after browsing the last few pages and searching, I couldnt find anything. Feel free to direct me to a previous response if I missed it.
Thanks in advance!
This has been covered numerous times, but, here you go. If you want to take the update, lock your bootloader, Odin back to stock, take the OTA update, reroot, unlock, etc.
If you don't want to do that, freeze SDM 1.0 with Titanium and the message will stop. One thing though, you will not be able to update OTA until you restore SDM. Which, you shouldn't be updating a rooted phone to begin with unless you want a world of problems.
Good luck!
Sent from my SCH-I535 using xda premium
So to be clear, absolutely no way to apply the update without going back to stock first, correct?
Sorry for posting up whats probably been asked 100 times, but really couldnt track it down with a search and browse of the last few pages.
Thanks again.
timofcourse said:
So to be clear, absolutely no way to apply the update without going back to stock first, correct?
Sorry for posting up whats probably been asked 100 times, but really couldnt track it down with a search and browse of the last few pages.
Thanks again.
Click to expand...
Click to collapse
I did not have to do all that...
I used Mobile Odin Pro to Pre-Inject Root into the OTA Update before flashing it, then I flashed the latest modem immediately after flashing the OTA update.
I didn't lose Root or Unlocked Bootloader status..
Best part of it was... I didn't need my PC to do any of it...
The following thread is the one you should read in detail..
http://forum.xda-developers.com/showthread.php?t=1887741
Perfect. Exactly what I was looking for.
Thanks again.
timofcourse said:
Perfect. Exactly what I was looking for.
Thanks again.
Click to expand...
Click to collapse
Glad to help..
tekrhino said:
I did not have to do all that...
I used Mobile Odin Pro to Pre-Inject Root into the OTA Update before flashing it, then I flashed the latest modem immediately after flashing the OTA update.
I didn't lose Root or Unlocked Bootloader status..
Best part of it was... I didn't need my PC to do any of it...
The following thread is the one you should read in detail..
http://forum.xda-developers.com/showthread.php?t=1887741
Click to expand...
Click to collapse
Make sure that you read it and pay attention very carefully. I tried to do the same exact thing and had problems. Had to Odin back to stock. I think my problem was that I was running a custom kernel. Anyway I got the unauthorized software message and could only get into stock recovery and download mode.
Guess I will read the thread myself and see where I screwed up at.
Sent from my SCH-I535 using xda premium
Ok so I never messed around with rooting until my phone got the 4.3 update the other night. I decided I hated the update so much that I did the saferoot method, and I'm now rooted.
Only after I did that did I discover that my bootloader is perma-locked and I can't try to unroot or rollback the android version or I'll hardbrick. I can't do roms. Essentially I can't fix what I rooted in order to fix, and trying to enter recovery mode and odin mode lights me up with a verizon warning. So:
1. Just what can I do SAFELY now that I'm rooted? I've already used titanium to uninstall the verizon apps, but I don't know what I'm doing beyond that to remove bloatware/make this thing faster.
2. Will there be a time in the future when I'll be able to totally unlock my phone and escape Verizon's tyranny even though I took the 4.3 OTA? I want to make it look like stock nexus android.
Thanks for any and all help!
1. That's about it. Maybe use Xposed and the Greenify module to hibernate apps that typically drain your battery. Can't do much more besides remove apps on TW 4.3.
2. Possibly or possibly never. Nobody knows if the Knox Bootloader and extra security checks put forth by Verizon will be overcome.
Sent from my SCH-I535 using Tapatalk 4
I use Greenify to hibernate apps I sometimes use and titanium backup to freeze apps I never use. I don't uninstall them just in case. It's running great for me, much better than 4.1.2
I know you can't downgrade from 4.3, but you can't unroot either?
Sent from my SCH-I535
The Arbiter said:
Ok so I never messed around with rooting until my phone got the 4.3 update the other night. I decided I hated the update so much that I did the saferoot method, and I'm now rooted.
Only after I did that did I discover that my bootloader is perma-locked and I can't try to unroot or rollback the android version or I'll hardbrick. I can't do roms. Essentially I can't fix what I rooted in order to fix, and trying to enter recovery mode and odin mode lights me up with a verizon warning. So:
1. Just what can I do SAFELY now that I'm rooted? I've already used titanium to uninstall the verizon apps, but I don't know what I'm doing beyond that to remove bloatware/make this thing faster.
2. Will there be a time in the future when I'll be able to totally unlock my phone and escape Verizon's tyranny even though I took the 4.3 OTA? I want to make it look like stock nexus android.
Thanks for any and all help!
Click to expand...
Click to collapse
go back to this forum: http://forum.xda-developers.com/showthread.php?t=2565758 Lots of comments on how to unroot if that is what you want. and give the DEVs some time, there will be a method, there is usually one found after a while. OR stick with what you have for a while, i can make mine look just like my rooted version with little variation, and stock isn't too bad, so far.
be patient grasshopper...
Would I be able to Odin back to 4.1.2 so I can re root, unlock bootloader and flash custom ROM's again? Thanks
bmatty14 said:
Would I be able to Odin back to 4.1.2 so I can re root, unlock bootloader and flash custom ROM's again? Thanks
Click to expand...
Click to collapse
No. If you took the 4.3 OTA you are stuck on it. You will hard brick your device if you try to Odin back to 4.1.2. Been mentioned tons of times in numerous threads.
Sent from the Shark Tank using XDA Premium 4 mobile app
The Arbiter said:
Ok so I never messed around with rooting until my phone got the 4.3 update the other night. I decided I hated the update so much that I did the saferoot method, and I'm now rooted.
Only after I did that did I discover that my bootloader is perma-locked and I can't try to unroot or rollback the android version or I'll hardbrick. I can't do roms. Essentially I can't fix what I rooted in order to fix, and trying to enter recovery mode and odin mode lights me up with a verizon warning. So:
1. Just what can I do SAFELY now that I'm rooted? I've already used titanium to uninstall the verizon apps, but I don't know what I'm doing beyond that to remove bloatware/make this thing faster.
2. Will there be a time in the future when I'll be able to totally unlock my phone and escape Verizon's tyranny even though I took the 4.3 OTA? I want to make it look like stock nexus android.
Thanks for any and all help!
Click to expand...
Click to collapse
Same situation...I flashed Stock_rooted_4.3 after taking the OTA and my phone said unauthorized software detected, take to Verizon. Luckily I found the original image and it flashed back to totally stock 4.3 build ML1.
Basic root would be fine for now so would you please link me to the method you used if you are also on ML1?
Thanks
LordAlexx said:
Same situation...I flashed Stock_rooted_4.3 after taking the OTA and my phone said unauthorized software detected, take to Verizon. Luckily I found the original image and it flashed back to totally stock 4.3 build ML1.
Basic root would be fine for now so would you please link me to the method you used if you are also on ML1?
Thanks
Click to expand...
Click to collapse
here you go: http://forum.xda-developers.com/showthread.php?t=2565758
saferoot is discovered for Galaxy S4 but can be use safely on S3 also.
buhohitr said:
here you go: http://forum.xda-developers.com/showthread.php?t=2565758
saferoot is discovered for Galaxy S4 but can be use safely on S3 also.
Click to expand...
Click to collapse
OK cool...just wanted to be sure; I am subscribed to that thread. Just gotta get ADB to see the phone. Everything else works via USB in all modes, kinda odd.
Thanks!