Related
A few months ago, I loaded 2.3.6 firmware on phone. It is stock gingerbread with root from oden file all_in_one_odin_ep4d. Last week I received an OTA update. The update fails to load and leaves me at the screen with the white triangle with yellow exclamation point. I pulled the battery and rebooted. Today, the update came back. Still no go. I think the update is incompatible with the software on the phone.
Can someone tell me:
1. What is in the update? Is it going to remove root and allow Verizon to see that I 3rd party tether? Are they suddenly going to slap a tether package on my bill? Is it even worth installing?
2. If it’s not worth installing, can I tell my phone that I don’t want it by making it think that the update is already installed?
3. If the update is worth installing, should I wait for an oden install that contains the update or do I do something to the phone to allow it to receive the OTA update? If I do opt for the OTA what must I do to allow it to load?
Being somewhat novice when it comes to loading software on phones, is there a good FAQ out there that lists all the different loads, with what they contain and explanations of those components. Right now, voodoo, Peanut butter and jelly… buzzwords.
beavermjr said:
A few months ago, I loaded 2.3.6 firmware on phone. It is stock gingerbread with root from oden file all_in_one_odin_ep4d. Last week I received an OTA update. The update fails to load and leaves me at the screen with the white triangle with yellow exclamation point. I pulled the battery and rebooted. Today, the update came back. Still no go. I think the update is incompatible with the software on the phone.
Can someone tell me:
1. What is in the update? Is it going to remove root and allow Verizon to see that I 3rd party tether? Are they suddenly going to slap a tether package on my bill? Is it even worth installing?
2. If it’s not worth installing, can I tell my phone that I don’t want it by making it think that the update is already installed?
3. If the update is worth installing, should I wait for an oden install that contains the update or do I do something to the phone to allow it to receive the OTA update? If I do opt for the OTA what must I do to allow it to load?
Being somewhat novice when it comes to loading software on phones, is there a good FAQ out there that lists all the different loads, with what they contain and explanations of those components. Right now, voodoo, Peanut butter and jelly… buzzwords.
Click to expand...
Click to collapse
All in one package that you installed came with custom kernel. You need to flash a FP1 debloated/bloated/rooted rom and the FP1 kernel. Since you have the custom rom+kernel you can not use OTA update. Some people (like me) prefer to do it clean by go back to stock EP4d rom, then do the full update to FP1, then flash what ever custom rom out there, like Eclipse or debloated etc...More on how to do it here:
http://forum.xda-developers.com/showthread.php?t=1560117
Sooner or later you should be on the latest version any way specially for support from XDA.
Thanks for setting me straight. Let’s see if I understand your info.
1. I have a custom ROM and need to use the stock one to be able to get the update to install.
2. Once I install the stock ROM and get the update, I could reinstall the same custom ROM I have now.
3. Returning my phone to stock will remove root access so I can get the update
How do I get back to stock everything, update the phone and then add only root access. I don’t know enough about stock ROMs to know why I’d want or need one.
beavermjr said:
Thanks for setting me straight. Let’s see if I understand your info.
1. I have a custom ROM and need to use the stock one to be able to get the update to install.
2. Once I install the stock ROM and get the update, I could reinstall the same custom ROM I have now.
3. Returning my phone to stock will remove root access so I can get the update
How do I get back to stock everything, update the phone and then add only root access. I don’t know enough about stock ROMs to know why I’d want or need one.
Click to expand...
Click to collapse
1. Yes, you need EP4D stock rom to get OTA update.
2. Yes, once you on stock FP1, you can use flash eclipse 2.0 (which build from FP1 rom). Once done you will have FP1 eclipse with FP1 stock kernel.
3. If you have pure stock EP4D and rooted, you can take the OTA, but yours is not.
You have 2 Options to upgrade:
1. Flash back to pure stock EP4D, OTA upgrade to FP1 then flash pre-rooted FP1 eclipse 2.0 rom. Then flash cwm.
2. Flash FP1 pre-rooted eclipse 2.0 rom, flash cwm, flash FP1 kernel, flash FP1 radio.
Hope this help, don't hesitate to ask if you have more questions.
Ok. That makes sense, sort of…
I’m going to give #1 a try since I found the stock EP4D load on the page you recommended. I will then be able to get the OTA update and have a stock phone with FP1.
I will then follow #5 on that page to root my pure stock FP1 and make CWM stick after reboot. Do you know if there is a free program that will let me change the file permissions of “install-recovery.sh” like root explorer?
beavermjr said:
Ok. That makes sense, sort of…
I’m going to give #1 a try since I found the stock EP4D load on the page you recommended. I will then be able to get the OTA update and have a stock phone with FP1.
I will then follow #5 on that page to root my pure stock FP1 and make CWM stick after reboot. Do you know if there is a free program that will let me change the file permissions of “install-recovery.sh” like root explorer?
Click to expand...
Click to collapse
root browser lite or ES file explorer. Both you can get from the Market (google play).
Thanks for the help. I got the phone updated successfully. I ended up having to load eclipse ROM on the phone after the OTA update as the other method with superuser update and superuser fixer failed to deliver root access.
couple of questions:
1. I can no longer set multi-screen wallpaper. How do I restore this functionality?
2. I can't answer my phone using the puzzle pieces. what am I missing?
Mike
PS thanks again for all the help. Sometimes I just need a push in the right direction.
Now that i've had a chance to play with the phone... The market keeps crashing. Anyone know what to do?
Sent from my SCH-I510 using XDA
FIX: settings/applications/market/clear data Reboot
I have been searching on the forum and Google but no answer. I had a Sprint Galaxy S3 and it was rooted with custom recovery Clockworkmod. After an update was available I could not install the update, failing with the message "verification failed" when trying to apply the official update file. I couldn't find an answer so I went back to stock recovery.
Now I have a verizon S3 and I would like to back up an image of my phone with clockworkmod but I would like to be able to update, especially with the looming jellybean update coming soon. Did I miss a way to install the updates to the official rom with clockworkmod? Or was it simply not possible.
moreisbetter said:
I have been searching on the forum and Google but no answer. I had a Sprint Galaxy S3 and it was rooted with custom recovery Clockworkmod. After an update was available I could not install the update, failing with the message "verification failed" when trying to apply the official update file. I couldn't find an answer so I went back to stock recovery.
Now I have a verizon S3 and I would like to back up an image of my phone with clockworkmod but I would like to be able to update, especially with the looming jellybean update coming soon. Did I miss a way to install the updates to the official rom with clockworkmod? Or was it simply not possible.
Click to expand...
Click to collapse
With most custom Roms...being able to do OTA updates is blocked because it could interfere with the rooted Rom you are running...its more or less a safety feature for that purpose. If you want to get the new Jelly Bean OTA update, you will have to flash your device back to unrooted stock and it should work just fine...as long as ur rooted, you wont be able to, if im not mistaken.
Thats true, and there is the whole bootloader thing! Now that we have all hacked away our bootloaders, the OTA just won't happen. Hopefully an easy relock becomes available for the vzws3 before that update is released, but I wouldn't panic - big red will probably release it to us after everyone else has gotten it and out phones are outdated! In general though, within a week or two of an official large release, the amazing devs on this site will have a downloadable version available for us to manually install.
If you have modded your phone, never try to take a OTA update. At the least you will lose root abilities. At the worst, potential bricking of your device.
Usually before, lol, if not just after a OTA, the devs have working release for our devices.
Take it easy, relax.
I'm using the default ROM for my One X and I'd like to update it (I haven't since I got it 6 month ago); do I need to re-lock the bootloader and unroot it before I can use the OTA update? Also it's been a while since I even fiddled with my phones software so I forgot anything else I may have done, is there a way I can check to see what else has been done and if it's safe to update it?
Currently I have:
Android Version: 4.0.3
HTC Sense Version: 4.0
Software Number: 1.73.631.1
HTC SDK API Level: 4.11
HTC Extension Version: HTCExtension_403_1_HA_4
What firmware are u on currently for starters
Sent from my HTC One XL using xda app-developers app
I added the info to the original post
bman3k said:
do I need to re-lock the bootloader and unroot it before I can use the OTA update?
Click to expand...
Click to collapse
Your phone should be factory default before performing OTA updates or results may be unexpected.
Most OTA updates are patch file based and require the files to be exactly what is expected.
There have been known issues with root being detected and the OTA failing.
Rooted phones progressing with an update but root lost after the update.
System files being modified and the OTA failing.
Recovery must be factory; not TWRP or CWM.
CID and MID must suit OTA.
The only modification I would consider safe through all OTA's so far has been SuperCID.
If you have any interest in rooting and flashing custom ROMs, I would suggest rooting and unlocking the bootloader now, while you are on 1.73, and not updating via OTA. The latest 2.20 update will also update your hboot, which plugs the holes by which kernels and radios can be flashed from recovery.
Since you're with att you can expect the jelly bean update any time from now till the end of the world which isn't fun waiting for .. I'd suggest if you were rooted download goo manager flash twrp....than flash a solid ics Rom if your prefer ice sense or you can go venture into the jb realms
omario8484 said:
Since you're with att you can expect the jelly bean update any time from now till the end of the world which isn't fun waiting for .. I'd suggest if you were rooted download goo manager flash twrp....than flash a solid ics Rom if your prefer ice sense or you can go venture into the jb realms
Click to expand...
Click to collapse
Agree. If you are already BL unlocked and rooted, why go through the hassle of relocking the BL and returning to stock, just to wait for the OTA?
Just flash a JB ROM, as there are already stock and custom JB ROMs posted in Development.
Plus, until the OTA actually hits, we don't know if it will even be rootable. They have plugged the existing root exploits with every successive AT&T OTA for this phone so far. No reason to think any different for the JB update.
Just flash a JB ROM and stay rooted.
Ya I really like viper xl v3 . Just apply fix listed on op and you should be good to go
Sent from my HTC One XL using xda premium
Stock OTA is not WORTH IT IMO, been there
Reselling the phone is probably the only reason i'd revert to stock.
Ok, so I tried to flash Android Revolution HD 18.0 instead of going back to stock. I used TWRP, but it said "unable to read zip file" and the flash failed, now my phone won't start up it just shows the HTC screen with "this build is for development purposes..." and continuously turns on and off.
bman3k said:
Ok, so I tried to flash Android Revolution HD 18.0 instead of going back to stock. I used TWRP, but it said "unable to read zip file" and the flash failed, now my phone won't start up it just shows the HTC screen with "this build is for development purposes..." and continuously turns on and off.
Click to expand...
Click to collapse
Ok you're really lucky you didn't just brick your phone.... You want to stay in the att one x forums.... Notice theres a title diff. You're lucky it didn't succesfully flash or your phone would be dead... That's an international one x rom
bman3k said:
Ok, so I tried to flash Android Revolution HD 18.0 instead of going back to stock. I used TWRP, but it said "unable to read zip file" and the flash failed, now my phone won't start up it just shows the HTC screen with "this build is for development purposes..." and continuously turns on and off.
Click to expand...
Click to collapse
Stick to the ROM's in our forum, I never heard of anything like that ROM for our phone sorry. Lucky you didn't brick it
O damn I feel very stupid now...
Can someone recommend me a JB ROM?
Also how would I even install one now? The AR HD one was the only ROM I had on my SD card
Edit: I figured out the Mount function in TWRP, so I know how to add new ROMs now
bman3k said:
O damn I feel very stupid now...
Can someone recommend me a JB ROM? Also how would I even install one now? The AR HD one was the only ROM I had on my SD card
Click to expand...
Click to collapse
Try them all, they are all good, the time it takes to ask for other peoples opinions you could have test driven them all yourself.
Are you looking for jb sense?
omario8484 said:
Are you looking for jb sense?
Click to expand...
Click to collapse
I'm just going to try a couple like wrecker suggested now that I've figured out how to flash ROM's properly
Thanks for your guys' helps
Is there a way to back up my apps/texts and stuff when flashing ROM's? I totally forgot about that and lost all of it, I didn't have anything particularly important, but it'd be a hassle to redownload everything everytime. I had Titanium Backup, but that's not a recovery for if you reflash right?
bman3k said:
I'm just going to try a couple like wrecker suggested now that I've figured out how to flash ROM's properly
Thanks for your guys' helps
Is there a way to back up my apps/texts and stuff when flashing ROM's? I totally forgot about that and lost all of it, I didn't have anything particularly important, but it'd be a hassle to redownload everything everytime. I had Titanium Backup, but that's not a recovery for if you reflash right?
Click to expand...
Click to collapse
Funny that you bring titanium up...titanium helps you back up apps it also backs up your app data...and for sms just download something from the market here's one download the app super backup and you can backup your sms
So I installed Cyanogen 10.0.0 but it didn't come with Google Play so I installed Gapps as well; now I keep getting the "Android Keyboard ASOP has stopped working" and I can't do anything. I've tried multiple versions of Gapps but they all give the error. I've also tried installing a keyboard apk on it's own but I am still unable to type anything.
Edit: Also when I downloaded Google Play as an apk separately it would crash immediately, but when I installed it from Gapps it was ok.
bman3k said:
So I installed Cyanogen 10.0.0 but it didn't come with Google Play so I installed Gapps as well; now I keep getting the "Android Keyboard ASOP has stopped working" and I can't do anything. I've tried multiple versions of Gapps but they all give the error. I've also tried installing a keyboard apk on it's own but I am still unable to type anything.
Edit: Also when I downloaded Google Play as an apk separately it would crash immediately, but when I installed it from Gapps it was ok.
Click to expand...
Click to collapse
You did a full wipe before hand right?
I did the factory, system, cache and dalvik cache wipes
Edit: I got it to work, not really sure what I did different =/
Being my first smartphone, of course I wanted to fiddle with it, so the first thing I did want upgrade to ICS (Android 4.0.4, got the link from Samsung's site). All that rooting stuff kinda made me gun-shy, at first...but, after getting up the nerve, I got Odin, the pit and tar files, and fired for effect. However...during the process, I got some sort of device driver error from my laptop ("not successfully installed" or some such, which was rectified since), and after rooting attempt, my phone wouldn't get past the welcome screen. Did the unroot (many thanks to k0nane), and was back to stock...or so I thought. Baseband still shows T769UVMB1, which I was told by T-Mobile tech support was the latest update; "About Phone" shows Android 2.3.6, Kernel v.2.6.35.11, Gingerbread UVLB7. "Software Updates" show none available. I recall the Menu being different when I had 4.0.4, though, much better than what I have now. I tried the root process again, was successful, and DLed Superuser and Titanium Backup to get rid of a lot of clutter. Phone runs like a champ, and I love it, but there's always room for improvement. Oh, and the link that *was* on Samsung's site for the upgrade is now "Page Not Found".
So...am I running the latest software/OS/updates? If not, how can I get 4.0.4 back?
ElGorditoMagnifico said:
Being my first smartphone, of course I wanted to fiddle with it, so the first thing I did want upgrade to ICS (Android 4.0.4, got the link from Samsung's site). All that rooting stuff kinda made me gun-shy, at first...but, after getting up the nerve, I got Odin, the pit and tar files, and fired for effect. However...during the process, I got some sort of device driver error from my laptop ("not successfully installed" or some such, which was rectified since), and after rooting attempt, my phone wouldn't get past the welcome screen. Did the unroot (many thanks to k0nane), and was back to stock...or so I thought. Baseband still shows T769UVMB1, which I was told by T-Mobile tech support was the latest update; "About Phone" shows Android 2.3.6, Kernel v.2.6.35.11, Gingerbread UVLB7. "Software Updates" show none available. I recall the Menu being different when I had 4.0.4, though, much better than what I have now. I tried the root process again, was successful, and DLed Superuser and Titanium Backup to get rid of a lot of clutter. Phone runs like a champ, and I love it, but there's always room for improvement. Oh, and the link that *was* on Samsung's site for the upgrade is now "Page Not Found".
So...am I running the latest software/OS/updates? If not, how can I get 4.0.4 back?
Click to expand...
Click to collapse
Baseband T769UVMB1 is a radio, not the rom. Android 2.3.6 is Gingerbread, so no, it does not look like you are on ICS. Looks like you have Root. Do you have (if not you should get) Clockword Mod Recovery - once you have a recovery, you can do a complete Nandroid backup of your currently running rom; then you are free to try any of the custom roms and if there is a problem you can flash backwards to your old rom. So get a recovery and nandroid first, then flash away!
LBN1 said:
Baseband T769UVMB1 is a radio, not the rom. Android 2.3.6 is Gingerbread, so no, it does not look like you are on ICS. Looks like you have Root. Do you have (if not you should get) Clockword Mod Recovery - once you have a recovery, you can do a complete Nandroid backup of your currently running rom; then you are free to try any of the custom roms and if there is a problem you can flash backwards to your old rom. So get a recovery and nandroid first, then flash away!
Click to expand...
Click to collapse
Thanks, I'll bone up more on this stuff & see what happens.
Update: I installed Odin 3.07 and did a flash with *SGH-T769_TMB_T769UVLH5_T769TMBLH5_Original.zip*, but it failed to root. Did a reflash, the updates, and I'm back in business again. It's late; I'm going to bed...I'll work on rooting this later...
CWM Recovery weirded out
Well, I tried the 4.0.4 root (as per Beastmode's guide)...and when I downloaded the ClockWorkMod Recovery file, it showed up in WinZip as recovery.img & tried to open in Paint Shop Pro. PSP did *not* like it, and told me so, refusing to open, 'cuz it wasn't an image file. Weird.
hey there,
I have a rooted One Mini which runs on Android 4.3 at the moment. A few days ago, I have recieved the update info for Kitkat 4.4.2.
Now I know that I can not use the regular update on a rooted phone and for the time beeing, I don't even feel the need to upgrade. However, I was wondering about the general problem:
First, I thought about doing a full backup (Nandroid), then flashing back to stock, getting the official update and then flashing the nandroid backup back. However, I realized that makes no sense, since a nandroid backup contains all partitions and therefore would simply overwrite the updated system...right?
Now the question is: what is the most convenient way to stay updated on a rooted phone? Do I really need to flash back to stock, do the update and then go through the root process again each time?
thanks for any info and clarifying!
brokaaa
normally the devs here are much faster in providing an updated ROM then many carriers are with giving you an OTA
I'd go back to stock and take the update. 4.3 was a mistake in my opinion. Att skipped it completely and went from 4.2.2 to 4.4.2 all in one update. Lol or just flash cm11 which is a better choice yet seeing as its already pretty stable and very fast.
Sent from my One Mini using Tapatalk