[Q] Questions About 2.3.3 Upgrading - Motorola Droid X2

I am running 2.2.2. I have rooted, and completely removed some of the bloat, but I uninstalled it, I did not freeze it.
If I do a hard reset, will that restore the phone to it's factory condition complete with the software I removed? I removed the VCast stuff and most of the included Verizon garbage.
It is 10:24pm EST on July 31, and I have still not gotten the 2.3.3 update. I am manually checking about every 30 minutes.

No, you would need to download the SBF file and restore the phone back to factory condition. There are countless tutorials on how to do it on here. Good luck!
Sent from my DROID X2 using XDA Premium App

SBF installed correctly, all the bloat is back and the phone is no longer rooted, although all of my settings seem the same. I cannot get it to root again. I did a wipe and *228 then reinstalled Gingerbreak 1.2.0 which allowed me to root again. I am unsure of where to go from here. Something about a bootstrap and then update.zip on external sd card to update to the pre-rooted 2.3.3?

Yes download the bootstrap, and p3droids pre rooted gb. Once you get in recovery flash the .Zip. they have more detailed instructions in other threads
Sent from my DROID X2 using XDA App

So from the recovery app I choose which option? I know it isn't going to be Charge, so it is either "Install Recovery" or the second option.
When choosing the second option, my phone does nothing except sit at the "Dual Core Technology" splash screen. I have placed the pre-rooted GB update on the root of my external SD card (not internal) and renamed it "update.zip". It didn't give me an option to install from SD card or anything, just sits there.
It appears to be doing absolutely nothing....just sitting at the dual core logo screen.
I don't want to yank the battery or press any buttons because I am unsure of what the phone is doing and do not want to brick it.
Thanks for all your help BTW. I am an old fart in a tech world, and this is my first Android phone. I love it.
Edit: AHA! I didn't hit "Install Recovery" first! I should have read the screen but I have been reading so many posts and threads I missed it.
View attachment 673039

I got the assert fail message, rebooted, and SUCCESS!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I Like Hearing Success Stories. Thanks Dude.

Now I just hope we can get a stock 2.3.3 SBF...

y0himba said:
Now I just hope we can get a stock 2.3.3 SBF...
Click to expand...
Click to collapse
Gotta Have A Dev. Make An Exploit To Gain Root Off That. Right Now We're Coming Into Gingerbread With Patched Files.

I'm amazed at how easy this was once I actually sat down and did it. In fact, I did it on two phones today.

y0himba said:
Now I just hope we can get a stock 2.3.3 SBF...
Click to expand...
Click to collapse
That would be a terrible thing, unless you don't want to root, then it's a great thing.
Sent from my DROID X2 using XDA Premium App

"SUPER-NOOB" Question of the Day
I am in Orlando and have yet to receive the OTA GB update. I do run LauncerPro Plus on my X2 - would this in any way hamper receiving the OTA update?
Told ya...."Super Noob" question
Many thanks,
Doug

If you aren't rooted you should get the ota update no issues, if you ARE rooted you don't want the ota update
Sent from my DROID X2 using XDA App

EvilTim said:
If you aren't rooted you should get the ota update no issues, if you ARE rooted you don't want the ota update
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
That actually depends on what you changed, just root itself won't stop the OTA, modifying system apps and files will though.
Sent from my DROID X2 using XDA Premium App

juhde said:
That actually depends on what you changed, just root itself won't stop the OTA, modifying system apps and files will though.
Sent from my DROID X2 using XDA Premium App
Click to expand...
Click to collapse
Reread it, I didn't say having root would stop it, I said you don't want it, you want the prerooted file
Sent from my DROID X2 using XDA App

You want the pre-rooted file, without a doubt. However, we will eventually need a 2.3.3 stock SBF to revert for further updates.
I installed the patched 2.3.3, I wonder if it can be unrooted if necessary.
I am new to this, so excuse the paranoia, but how can I be sure that this update, the pre-rooted patch, is actually 2.3.3? The system info can easily be edited to say it is 2.3.3...
It is running fine, however with the Internet the way it is today there is no telling what we just installed on our phones.

y0himba said:
You want the pre-rooted file, without a doubt. However, we will eventually need a 2.3.3 stock SBF to revert for further updates.
I installed the patched 2.3.3, I wonder if it can be unrooted if necessary.
I am new to this, so excuse the paranoia, but how can I be sure that this update, the pre-rooted patch, is actually 2.3.3? The system info can easily be edited to say it is 2.3.3...
It is running fine, however with the Internet the way it is today there is no telling what we just installed on our phones.
Click to expand...
Click to collapse
We don't need a 2.3.3 sbf because the current one still works. For future updates you'd just sbf back to 2.2.2 then pull any updates from settings. At least that's how we do it for the OG Droid.
For your paranoia cure, lots of ways. The new battery stats menu, phone bars turing colours when internet connection is established, new blur icons. The fact the phone actually runs well without modding the memory settings. All these are telling you it's gingerbread. Plus why would a respected dev like P3Droid want to lie?
Sent from my DROID X2 using XDA Premium App

Oh I agree, and I don't think he would lie, but I am old, and new to Android as well as this being the first time I have done an update in this way. I was around Windows Mobile for a LONG time, and in a lot of ways it was more simple to flash a ROM there.
This was easier however, and retained my settings for the most part. The guides here, while being a bit confusing due to grammar for me, are exactly what I need to get the job done.
How long until I need to worry about updates again?

Knowing motorola. 6 months.
Of course there will be a lot of custom ROMs out in the next few weeks based off gingerbread that you might want to try.
Sent from my DROID X2 using XDA Premium App

Related

AT&T SGSII Update - Failed?

Just checked for update under settings and there was an update, but when the phone restarts and tries to install the update, it fails. Anyone else?
"Software Update: Install Interrupted - The software update could not be installed at this time."
Are you on a completely stock phone?
Sent from my SAMSUNG-SGH-I777 using Tapatalk
^yup, complete stock phone.
I checked for updates and there was one, downloaded, update failed.
Just bought my I777 from ATT and powered it up. Completely stock and experienced the same failure.
Same here. Completely stock. Tried my Girlfriends SGS2.....same deal.
Guess I wasn't the only one with the failure.. lol.. wonder what's the update about..
Mine failed also, completely stock as well. Out of curiosity what is this update include?
OTA updates probably aren't a good thing for you to try and do. They have been known to brick the og gs line. If there is an update you should try over Samsung Kies
Sent from my SAMSUNG-SGH-I777 using Tapatalk
CB650 Wolf said:
OTA updates probably aren't a good thing for you to try and do. They have been known to brick the og gs line. If there is an update you should try over Samsung Kies
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Click to expand...
Click to collapse
I just tried Kies. No update there.
Same thing here, just tried on my wifes phone and after restart says update failed.
Just talked to AT&T. The rep said there wasn't an update for the I-777 only for the Skyrocket.
Samsung also says there is no update.
Same old stuff........AT&T says talk to Samsung......Samsung says talk to AT&T.Should have know that's how it would go.
lol, so AT&T pushed the update to the wrong devices or something?
I think what happened was that the update application glitched out. Or maybe they're testing the machines for a bigger update. Maybe KK6 or whatever just came out.
It seems like everyone at at&t has left the original GS2 And just focused on the skyrocket.. (Noting that at&t announced the skyrocket would be updated to ICS but have yet to say anything on the original gs2..)
- At&t Galaxy S II Running
***ICScrewD V1.3***
Unless, my searches and searches have just missed over something completely hahah. Inform me if I'm wrong!
- At&t Galaxy S II Running
***ICScrewD V1.3***
It's just AT&T trying to secretly install CIQ on the phones.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
^Possibly xD
I ran into this problem too, but after 3 attempts (2 fails and 1 success) to install the update, I got it to work!
First of all, this update is NOT the SkyRocket's... after all, we are on the Orignal SGS2, and the SkyRocket and OSGS2 have COMPLETELY different model numbers.
Second of all, the update brings the phone to 2.3.6 and firmware I777UCKK6. If I am correct, 2.3.6 is also supposed to have better battery life
So, to get the update to work, here is what I did:
*NOTE* I too was 100% stock, but rooted and removed some of the bloatware on the phone. It seems that this may have caused the update failure.
1) Flash one of the kernels found on Entropy512's post on how to return to stock. It seems that whether you choose the rooted or non-rooted one does not matter (EX: I was already rooted and installed the non-rooted Kernel, but remained rooted afterwards). This will return all bloatware to the phone.
2) Wait 24Hrs OR change the date forward a day
3) look for an update again and install
4) Enjoy the update!
5) If rooted, then you will need to root again
6) Once rooted, you can remove the bloatware again. I recommend copying it to a separate folder so that future OTA updates can be done by simply copying the apk files back to system/apps.
I hope this works for everyone else too
spexwood said:
I ran into this problem too, but after 3 attempts (2 fails and 1 success) to install the update, I got it to work!
First of all, this update is NOT the SkyRocket's... after all, we are on the Orignal SGS2, and the SkyRocket and OSGS2 have COMPLETELY different model numbers.
Second of all, the update brings the phone to 2.3.6 and firmware I777UCKK6. If I am correct, 2.3.6 is also supposed to have better battery life
So, to get the update to work, here is what I did:
*NOTE* I too was 100% stock, but rooted and removed some of the bloatware on the phone. It seems that this may have caused the update failure.
1) Flash one of the kernels found on Entropy512's post on how to return to stock. It seems that whether you choose the rooted or non-rooted one does not matter (EX: I was already rooted and installed the non-rooted Kernel, but remained rooted afterwards). This will return all bloatware to the phone.
2) Wait 24Hrs OR change the date forward a day
3) look for an update again and install
4) Enjoy the update!
5) If rooted, then you will need to root again
6) Once rooted, you can remove the bloatware again. I recommend copying it to a separate folder so that future OTA updates can be done by simply copying the apk files back to system/apps.
I hope this works for everyone else too
Click to expand...
Click to collapse
Or just flash UnNamed 2.0
Well, yeah, but some prefer to stay on official stock firmwares... like myself lol.

[CDMA] ICS Installer v1.2 is released! 6.14.84.xt912 LEAK [USE AT YOUR OWN RISK]

UPDATE 8:56 PM 4/27/12: THERE ARE REPORTS OF THE LATEST LEAK MAKING IT IMPOSSIBLE TO RETURN TO .173 or .181
UPDATE 6:18 PM 4/27/12: There is a new version of ICS out for our phones and its ready to be installed with ICS Installer v1.2
UPDATE 9:43 AM 4/27/12: Updated patch! There was an error with ADB in the Motofail root section of the utility, my tests weren't catching it because I have ADB on my path. Sorry everyone!
UPDATE 12:57 PM 4/25/12: seems there was a problem with the first option, I have fixed it in a patch. Download it and the bottom of this post and replace the ICSInstaller.bat file in the zip with this one. Sorry everyone.
UPDATE 4/25/12: New version of my utility is OUT NOW! I have included RSD Lite in the zip file and the fastboot file that is required to make the switch to ICS. I have updated and thoroughly tested my instructions, and if followed EXACTLY as written, you will retain root after your installation. It is almost 100% fool proof. Enjoy the update! It will be posted as soon as it uploads to google!
Updated:
the root exploit to use latest Superuser.apk and su bin
the process to install ICS
style and layout of utility for usability
full instructions to fix your phone if you do something wrong
added the full 6.12.173 fastboot file
added RSDLite installer with instructions for use(just in case)
added instructions to retain root through ICS install (has worked 100%)
- no terminal app needed
Overall I feel it is much easier to follow, and much harder to screw something up. I just gave it to someone that has no idea what they are doing and they were able to gain root, preserve root, install ICS and regain root access. It is pretty much fool proof
UPDATE: Going though the posts i can see some people are having trouble with the instructions. Sorry I wasn't clearer. You need to have never used bootstrap or safestrap. Rule of thumb is if you've done anything besides just getting root, you're gonna have a bad time.
CDMA ONLY
I know that a bunch of you wanna get your hands on the ICS leak, but can't/don't want to go through all the steps to do so. I have a solution.
I have written a small utility to automate the process.
I am trying to get in touch with mattlegroff to add it to his utility, but in the meantime, I will release a standalone version.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
INSTRUCTIONS:
1. Make sure your phone is completely stock 6.12.181 (it's ok if it has been rooted)
2. Make sure you have NEVER installed bootstrap, safestrap, or cwm. (If you have used these, skip option 1 and use RSDLite 5.6)
3. Unzip ICSInstallerv1.2.rar to an empty folder
4. Double click the ICSInstaller.bat file
5. Please READ and FOLLOW all instructions! (you will retain root)
6. You now have ICS!
ONLY WORKS IN WINDOWS!
DOWNLOAD THE USB DRIVERS FIRST!
DRIVERS​
Please like if this helps you out!
GET IT HERE ICS Utility v1.2USE AT OWN RISK
TORRENT: ICS Utility v1.2USE AT OWN RISK
For anyone having trouble...
DETAILED INSTRUCTIONS:
1. Use option 1 or RSD to get to .173
2. Use option 5 to get OTA walkthrough
3. Use option 2 to root
4. Use option 4 to preserve root
5. Use option 7 to upgrade to ICS 6.14.84.xt912
6. Use option 8 to regain root after upgrade
REMEMBER TO READ ALL INSTRUCTIONS AFTER PRESSING ENTER TO CONTINUE!
Guess I will be the first one to try this on my wife's phone. What you did is just put the soak leak into an installer package just to be clear?
Sweet!
Sent from my SCH-I510 using xda premium
Will this work for non root users?
Sent from my DROID RAZR using xda premium
johnny0911 said:
Will this work for non root users?
Sent from my DROID RAZR using xda premium
Click to expand...
Click to collapse
Yes. You can root using his installer, but I am having issues with root. It would allow somethings access and not others. I reinstalled root with OTA rootkeeper app and it completely screwed my root. Not saying it is due to the installer because it worked perfectly. Just something with ICS I assume. I will try to get root back somehow and install my bootstrap recovery because without that, I can't install zip packages through CWM.
Edit: Chances are the root loss is because of ICS. It is a known issue and there are terminal emulator steps that can help regain root if it is lost. And upon further testing I still don't have root access for bootstrap, ROM toolbox and others. I would not say it is directly related to the installer but something is going on to not allow me root access. I have root and full SU access on my phone which I updated the long way from the other forum. Not sure what is up with this.
Yes you must root first before using the ICS installer.
Also:
ICS leak sometimes has an issue with previous root methods. Mine worked fine, but 3/5 of the test phones I used had troubles after the install. Use the terminal emulator or adb shell to run the commands.
To Restore Root on the Ics Leak (Edited 4/2/12 @ 12:39PM PT):
Download Android Terminal Emulator for free from the market.
Enter the following commands EXACTLY as you see them listed here:
/system/su-backup
mount -o rw,remount -t yaffs2 /dev/block/system /system
cp /system/su-backup /system/bin/su
​Exit terminal & reboot.
Root should be restored at this point!
Again, you can use the terminal emulator or ADB shell to do these commands.
EDIT: you can also update the Superuser.apk and su binary by going to this page:
SUPERUSER
That's what i did and it would not allow root to my apps. I am going to start over and do the long way and see what happens.
Sent from my DROID RAZR using Tapatalk 2
flashman2002 said:
That's what i did and it would not allow root to my apps. I am going to start over and do the long way and see what happens.
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
The key is to update your SU binary BEFORE you use voodoo. The standard motofail installs an old version that isn't compatible with ICS, update SU = rooted ics.
Sent from my DROID RAZR using xda premium
Ronin3178 said:
The key is to update your SU binary BEFORE you use voodoo. The standard motofail installs an old version that isn't compatible with ICS, update SU = rooted ics.
Sent from my DROID RAZR using xda premium
Click to expand...
Click to collapse
I didn't have to do that on my personal phone when I updated to ICS using the method outlined on the other forum.
It works only for the cdma right?
Probably a dumb question, but is this a stock, unrooted ICS then?
Root is required for this install to work
Sent from my DROID RAZR using xda premium
So this method is safe it just screws with your root access with no other consequence than losing root access? But there are terminal emulator commands to fix this effectively?
Sorry, I just want to get this right before I try this on my phone;I want to make sure that most everything goes just fine.
Edit: What are the consequences of downloading this early? Will we be able to download the official update with no hassle? And if we decide that we don't like it how hard is it to flash back? I've heard some people saying that they almost bricked their phones going back to Gingerbread.
I personally did not lose root. I flashed back to stock and wiped everything. I have heard that there isn't an issue with going back to GB if you do it correctly.
Edit: there aren't any consequences. When it comes out, just go back to stock and OTA like normal.
Sent from my DROID RAZR using xda premium
Rouxe41 said:
CDMA ONLY
I know that a bunch of you wanna get your hands on the ICS leak, but can't/don't want to go through all the steps to do so. I have a solution.
I have written a small utility to automate the process.
I am trying to get in touch with mattlegroff to add it to his utility, but in the meantime, I will release a standalone version.
INSTRUCTIONS:
1. Unzip to a folder
2. Double click the .bat file
3. ???
4. Profit!
Click to expand...
Click to collapse
Beautiful. Everything you need in one spot, thank you for your work sir!
Has anyone tried this does it work? And when i install this will it wipe my SD Cards?
It works. I will caution that in my instance, going back to .173 took about 7 hours because nothing through Matt's utility or RSD wanted to flash. Finally got it to flash .173 so I could redo the process using the ROM manager method and it worked flawlessly, root kept and everything. Again, this utility did work... but I had issues getting back to stock because my root did not work properly.
Will this work if I have bootstrap cwm? Has anyone used this and suddenly had tether?
Sent from my Iconia A500 using XDA
ICS Installer problem
I get a mkdir failed because permission is denied. Didn't install ICS
Worked flawlessly for me. Followed all instructions 100% and didn't have any issues. Once the actual OTA is confirmed and a date is released, I'll use this utility to revert back to .173 stock.

OTA Update failed

My girlfriend has her Photon stock rooted and locked but her OTA update continues to fail. Anyone know why?
It's probably because it's rooted.
Sent from my Xoom using xda app-developers app
Root shouldn't matter (at least it didn't used to). Has she deleted any system apps? The update looks for them, and if they're gone the update fails.
Sent from my MB855 using xda app-developers app
MikeyLee said:
My girlfriend has her Photon stock rooted and locked but her OTA update continues to fail. Anyone know why?
Click to expand...
Click to collapse
I had trouble with my Photon 4G and this latest update. I rooted mine using the One Click Root (OCR) method. I kept getting the "Software Update Failed" message for the 2.3.5 update. My wife's phone which is 100% factory updated just fine on the first try (go figure... :silly.
As you always see on here, PERFORM THIS AT YOUR OWN RISK. I do NOT take responsibility for any issues caused by following this process. It is sad that this even has to be stated on a forum for developers.
Here's what I did to get mine to update properly:
1) Perform a full contacts, application, and system backup using Titanium Backup (or use whatever backup you want) Just in case.
2) Download the latest version of RSD Lite you can find. This was one of the hardest steps as copies of it can be difficult to locate. Ask Google and ye shall receive... I actually found it using Bing, though. I would love to just go to Motorola and say "here's my money" for this, like I did with flashing/modding software back in the Razr V3 days.
3) Download the appropriate Motorola USB drivers I was able to locate End User Driver Installation 5.9.0 for 64bit. This is another ask Google, Bing ...
4) Use RSD Lite to reflash the exact same SBF you are currently using. I got the SBF from this post. This did NOT delete or reset any contacts, however it does require reauthentification to the network.
5) After your phone resets after the SBF has flashed successfully, attempt the "Update Motorola Software" action under Settings--> About phone--> System updates.
6) If you want to re-root, use the Photon Torpedo method. This is EASY and I should have just done it this way to begin with instead of being lazy and using OCR. OCR is nice, but would not do it again based on my experience with it. The simplest way isn't always the best.
I hope this helps.
I also heard the ota update doesn't like 198_7.
I am still waiting on updating, crossing fingers the devs break some serious ground.
Sent from my MB855 using xda premium

new update i545vrsgpl1

Hi everyone. I just got this update showing up on the phone. didn't install it cause I was on rooted of1 it looked like that its a new update that came out today. Anyone have some idea about it? I'll be uploading the update.zip file soon. my internet sucks and upload takes an hour X(...
Update: I took a look in the zip file, and looked at the metadata file under Meta-INF/com/android/. and it said
post-build=Verizon/jfltevzw/jfltevzw:5.0.1/LRX22C/I545VRSGPL1:user/release-keys
post-timestamp=1481263333
pre-build=Verizon/jfltevzw/jfltevzw:5.0.1/LRX22C/I545VRUGOF1:user/release-keys
pre-device=jfltevzw
so... im guessing that means the new update is still android 5.0.1?
update
heres the link for hte update zip
https://drive.google.com/open?id=0Bw35VbWkMyAhMzA0RUNYVC1sWDA
bangdosa said:
Hi everyone. I just got this update showing up on the phone. didn't install it cause I was on rooted of1 it looked like that its a new update that came out today. Anyone have some idea about it? I'll be uploading the update.zip file soon. my internet sucks and upload takes an hour X(...
Update: I took a look in the zip file, and looked at the metadata file under Meta-INF/com/android/. and it said
post-build=Verizon/jfltevzw/jfltevzw:5.0.1/LRX22C/I545VRSGPL1:user/release-keys
post-timestamp=1481263333
pre-build=Verizon/jfltevzw/jfltevzw:5.0.1/LRX22C/I545VRUGOF1:user/release-keys
pre-device=jfltevzw
so... im guessing that means the new update is still android 5.0.1?
Click to expand...
Click to collapse
Most likely just a security update.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well ill try to hold off, because last time i took an OTA update i was stuck for months with no root and wifi hotspot.
Still Android 5.0.1 Lollipop
I completed the update this morning. This is still Android 5.0.1 Lollipop.
edboyd59 said:
I completed the update this morning. This is still Android 5.0.1 Lollipop.
Click to expand...
Click to collapse
Any noticeable differences?
Did you loose root after update?
bangdosa said:
Hi everyone. I just got this update showing up on the phone. didn't install it cause I was on rooted of1 it looked like that its a new update that came out today. Anyone have some idea about it? I'll be uploading the update.zip file soon. my internet sucks and upload takes an hour X(...
Update: I took a look in the zip file, and looked at the metadata file under Meta-INF/com/android/. and it said
post-build=Verizon/jfltevzw/jfltevzw:5.0.1/LRX22C/I545VRSGPL1:user/release-keys
post-timestamp=1481263333
pre-build=Verizon/jfltevzw/jfltevzw:5.0.1/LRX22C/I545VRUGOF1:user/release-keys
pre-device=jfltevzw
so... im guessing that means the new update is still android 5.0.1?
update
heres the link for hte update zip
https://drive.google.com/open?id=0Bw35VbWkMyAhMzA0RUNYVC1sWDA
Click to expand...
Click to collapse
bilgerryan said:
Most likely just a security update.
Click to expand...
Click to collapse
Is it just me? That's a new bootloader version isn't it? OF1 - PL1.
https://forum.xda-developers.com/verizon-galaxy-s5/general/update-pl1-potential-problem-t3528505
rooted device now bricked
I had rooted my device on OF1 using kingroot, and processed this update. I'm now bricked. It just hangs on the Samsung custom splash screen...
Any advice?
nic boles said:
I had rooted my device on OF1 using kingroot, and processed this update. I'm now bricked. It just hangs on the Samsung custom splash screen...
Any advice?
Click to expand...
Click to collapse
Flash stock with Odin. Follow my stickied thread in this Sub-Forum. If it updated your bootloader you might be hosed. Until the firmware is released.
Just so you know, you're supposed to unroot and then take the update
Ok, I'll try reflashing stock with odin.
I thought I did unroot it, using the kingroot instructions. I went into settings, told it to unroot, and restarted... then applied the update. Unless there was something else I was supposed to do?
nic boles said:
Ok, I'll try reflashing stock with odin.
I thought I did unroot it, using the kingroot instructions. I went into settings, told it to unroot, and restarted... then applied the update. Unless there was something else I was supposed to do?
Click to expand...
Click to collapse
Kingroot sets itself as a system app. Any alteration to the system partition and an OTA will Bork it.
Hey guys, I just got bricked by the OTA as well. 6 months or so ago I flashed the old kernel (OC1 I believe?) and then rooted with kingoroot or whatever. That was a mistake... all kinds of security notices and other weird sh*t that i didn't have time to deal with. So I used kingoroot to remove the root and flashed back OF1 or whatever was current. Still had the custom boot screen which was annoying but I thought I was back to normal... evidently that wasn't the case. Kind of salty right now because I probably just lost all of my data...I guess that's my lesson for getting a Samsung and attempting to make it usable. Currently I cannot get into safe or recovery mode: when i press the volume up and power it just takes me back to the "installing system update" and then "error!!". If anyone knows a way for me to get back in it would be greatly appreciated. If not, does anyone know which version firmware to install and where I could find it?
JoshTehSquash said:
Hey guys, I just got bricked by the OTA as well. 6 months or so ago I flashed the old kernel (OC1 I believe?) and then rooted with kingoroot or whatever. That was a mistake... all kinds of security notices and other weird sh*t that i didn't have time to deal with. So I used kingoroot to remove the root and flashed back OF1 or whatever was current. Still had the custom boot screen which was annoying but I thought I was back to normal... evidently that wasn't the case. Kind of salty right now because I probably just lost all of my data...I guess that's my lesson for getting a Samsung and attempting to make it usable. Currently I cannot get into safe or recovery mode: when i press the volume up and power it just takes me back to the "installing system update" and then "error!!". If anyone knows a way for me to get back in it would be greatly appreciated. If not, does anyone know which version firmware to install and where I could find it?
Click to expand...
Click to collapse
You need to hold volume down and power, then use Odin to reflash to OF1. That is what I just did.
sammobile(dot)com/firmwares/download/53590/I545VRUGOF1_I545VZWGOF1_VZW/
how to unroot?
I rooted using the wondershare method last year.
How do i un root so i can update it without bricking my device? Any help or links would be appreciated.
update: nic boles, that last post worked like a charm,,thanks!
I'll wait a while to try to root again.
foxfi seems to work and that's the most important thing to me.
Has anyone tried rooting on the new update?
bama9393 said:
Has anyone tried rooting on the new update?
Click to expand...
Click to collapse
Maybe I read it wrong, but I think the person that tried said they were bricked.
bilgerryan said:
Maybe I read it wrong, but I think the person that tried said they were bricked.
Click to expand...
Click to collapse
you have to unroot before the update
If you were rooted and made even the slightest change to /system, the update will hose you.
If you want the update, best to Odin back to OF1 stock first, then OTA.
bg260 said:
If you were rooted and made even the slightest change to /system, the update will hose you.
If you want the update, best to Odin back to OF1 stock first, then OTA.
Click to expand...
Click to collapse
Now can i root after the update with wonershare or kingroot?
edwardnizz said:
Now can i root after the update with wonershare or kingroot?
Click to expand...
Click to collapse
I wouldn't try it.
I mirrored the firmware here btw. Like 6 months ago.

Any way to block tmobile system update?

I see the system update notification on my v30, are there any way to block it? since i've rooted my phone and have TWRP installed, i don't think i can update over the air.
T-MOBILE H932 SYSTEM UPDATE FREEZE/DISABLE
zrzhu said:
I see the system update notification on my v30 (H932), are there any way to block it? since i've rooted my phone and have TWRP installed, i don't think i can update over the air.
Click to expand...
Click to collapse
No, you cannot take inferior partial image OTA updates, since you are not fully stock (you have custom recovery). If you try it will just boot to TWRP.
Freeze the carrier software update files in Titanium Backup.
ChazzMatt said:
T-MOBILE H932 SYSTEM UPDATE FREEZE/DISABLE
No, you cannot take inferior partial image OTA updates, since you are not fully stock (you have custom recovery). If you try it will just boot to TWRP.
Freeze the carrier software update files in Titanium Backup.
Click to expand...
Click to collapse
I've frozen all the apps (see screenshot) yesterday, but I still saw the notification this morning.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://drive.google.com/file/d/1DsubXijulcW5mRh2iG1eBtWr8fZN3M30/view
zrzhu said:
I see the system update notification on my v30, are there any way to block it? since i've rooted my phone and have TWRP installed, i don't think i can update over the air.
Click to expand...
Click to collapse
You can't update over the air. Just follow the directions here and update your phone without losing TWRP. Once you're up to date, you won't get the notification.
https://forum.xda-developers.com/lg-v30/development/rom-h932-oreo-v20o-stock-twrp-t3863202
jsgraphicart said:
You can't update over the air. Just follow the directions here and update your phone without losing TWRP. Once you're up to date, you won't get the notification.
https://forum.xda-developers.com/lg-v30/development/rom-h932-oreo-v20o-stock-twrp-t3863202
Click to expand...
Click to collapse
I'm not planning to update to the latest security patch (12/5) over the air. i did install 20o already following the link after I first rooted my phone, but I still see the notification even frozen all the update related apps.
zrzhu said:
I'm not planning to update to the latest security patch (12/5) over the air. i did install 20o already following the link after I first rooted my phone, but I still see the notification even frozen all the update related apps.
Click to expand...
Click to collapse
Oh. I guess there is a new update that came out recently. I didn't know. I haven't gotten a notification yet. Sorry. We'll just have to wait for the next update zip to be made for us.
---------- Post added at 07:56 AM ---------- Previous post was at 07:45 AM ----------
zrzhu said:
I'm not planning to update to the latest security patch (12/5) over the air. i did install 20o already following the link after I first rooted my phone, but I still see the notification even frozen all the update related apps.
Click to expand...
Click to collapse
Also, just a theory, you may still be getting the notification because the update file might have already been downloaded to your device and waiting for you to tell it to update. I don't know where those are stored but if it's on your device and you can delete it, that may cause the notification to go away.
jsgraphicart said:
Oh. I guess there is a new update that came out recently. I didn't know. I haven't gotten a notification yet. Sorry. We'll just have to wait for the next update zip to be made for us.
---------- Post added at 07:56 AM ---------- Previous post was at 07:45 AM ----------
Also, just a theory, you may still be getting the notification because the update file might have already been downloaded to your device and waiting for you to tell it to update. I don't know where those are stored but if it's on your device and you can delete it, that may cause the notification to go away.
Click to expand...
Click to collapse
i think you are probably right. I did remember see "...install..." in the notification. Well, I'll wait for the flashable update then.
zrzhu said:
i think you are probably right. I did remember see "...install..." in the notification. Well, I'll wait for the flashable update then.
Click to expand...
Click to collapse
I just got the notification this morning. Just in case you still are wondering how to get rid of the notification, you can long press the notification and turn the system update notifications off so you don't see it anymore.
jsgraphicart said:
I just got the notification this morning. Just in case you still are wondering how to get rid of the notification, you can long press the notification and turn the system update notifications off so you don't see it anymore.
Click to expand...
Click to collapse
That will not do much since you only ignore the notification. At some point the phone will be forced to install it.
Sent from my LG-H932 using XDA Labs
BROKEN1981 said:
That will not do much since you only ignore the notification. At some point the phone will be forced to install it.
Click to expand...
Click to collapse
Updates install automatically? I thought you had to hit the update button manually? Either way, the update should fail anyway since I'm rooted and have TWRP installed, right? So it shouldn't matter
jsgraphicart said:
Updates install automatically? I thought you had to hit the update button manually? Either way, the update should fail anyway since I'm rooted and have TWRP installed, right? So it shouldn't matter
Click to expand...
Click to collapse
For people with unrooted phones, OEMs/carriers can force updates no matter what you choose. They own the phone, not you. They are the admin, not you. Samsung proved that a couple years ago with the Galaxy Note forced brick fiasco. OEM/carrier forced update on all unrooted phones to brick it on purpose.
Yes, since you have TWRP installed, the OTA update may try but it will fail.
ChazzMatt said:
For people with unrooted phones, OEMs/carriers can force updates no matter what you choose. They own the phone, not you. They are the admin, not you. Samsung proved that a couple years ago with the Galaxy Note forced brick fiasco. OEM/carrier forced update on all unrooted phones to brick it on purpose.
Yes, since you have TWRP installed, the. OTA update may try but it will fail.
Click to expand...
Click to collapse
That's what I figured. So I just turned off the notification for the update for the time being. And if it tries, I have nothing to worry about.
Since the OTA is probably a large file, I'd say you should look for it and delete it. This should prevent whatever it is in the OS that is trying to apply it. Of course, it may re-download, but then you can keep looking for the app that's causing that to happen?
BROKEN1981 said:
That will not do much since you only ignore the notification. At some point the phone will be forced to install it.
Sent from my LG-H932 using XDA Labs
Click to expand...
Click to collapse
I've seen this happen a lot to people. They don't install, then it starts installing anyway. They hit cancel, and that works a couple of times. Then even cancel doesn't work.
Usually happens to people procrastinating unlocking their bootloader and rooting -- and then some update prevents them from doing that. Verizon was really bad about that with the Droid Turbo phones, when the Sunshine devs found exploit to unlock bootloader. "Forced" update would prevent Sunshine from working. Sometimes would be two or three months before exploit app was updated, but there was never any guarantee it would ever be. Cat and mouse for awhile, and finally Verizon stopped caring when they stopped giving updates for Droid Turbo...
We kept telling people, just go ahead and unlock your bootloader! Verizon can't lock it BACK, but they CAN stop you from unlocking it in the first place. Stop procrastinating and just do it!
schwinn8 said:
Since the OTA is probably a large file, I'd say you should look for it and delete it. This should prevent whatever it is in the OS that is trying to apply it. Of course, it may re-download, but then you can keep looking for the app that's causing that to happen?
Click to expand...
Click to collapse
I tried to find the file, but didn't find it. If anyone knows, i'll happy to delete the downloaded update file.
zrzhu said:
I tried to find the file, but didn't find it. If anyone knows, i'll happy to delete the downloaded update file.
Click to expand...
Click to collapse
I don't have any specific advice, but if you use FX file explorer, it has a "cleanup" function which can scan the entire phone for the largest files. That might be a fast/easy way to see where it is?
mistake
if you're rooted and just want the notification gone, I was able to achieve that on my V20 and now V30 using FOTAKill.
drop FOTAKill.apk into /system/app/FOTAKill.apk perm 644, and it should do the rest by itself. It does not have a UI, but from what I gather, it intercepts the fota ota update message and notification and kills/hides it. It does more than just that I'm pretty sure because the update.zip never downloads either.
.
Sent from my LG-LS998 using XDA Labs

Categories

Resources