My wife's phone has the v3 leak on it, and I want update her to the MR4 update. I found a copy of it at ...
http://www.androidcentral.com/droid-eris-ota-fixes-rolling-out-manual-install-link-available-too
Is it ok to go ahead and update using the file there? Is there anything I need to know first?
Yes, it should be fine to apply that update to a Leak-V3 phone. This update is designed specifically for the original OTA2.1, which - as we all know by now - is essentially identical to Leak-V3.
What you need to know:
1) You can get the download directly from Google's servers with this URL:
http://android.clients.google.com/p...Verizon_WWE_2.37.605.4_2.36.605.1_release.zip
2) When you have finished downloading it:
- Make sure the phone is well charged.
- Copy it to the root folder of the phone's SD card. (After copying, check the file size, down to the last byte to make sure it is copied successfully)
- Rename it (on the SD card) to "update.zip"
- Power the Eris off
- Turn the Eris on by holding down the Vol-Up & End/Power buttons simultaneously, until the screen lights up
- Wait an additional 12-15 seconds; you should see a recovery "splash screen" after the 3 skating droids
- For a 2nd time, press Vol-Up & End/Power simultaneously
- You should see a brief menu appear; choose the item labeled "sdcard:update.zip" or some such.
- WAIT! Don't interrupt the phone, it takes a little while. Just let the phone do it's thing. It will automatically reboot when it is finished.
This update does not perform a factory reset - if you want, you could try and make backups of sorts, but you probably won't need them.
bftb0
If I do this with root will it remove root?
I did that last night, but it errored when i tried to apply the update. Not sure why. Maybe I'll try again.
I got the MR4 applied to my 2.1v3 Eris this morning before I left for work. Went thru the same steps as listed in the previous post, flawless. No problems. I have noticed a slight boost in the performance of the phone, not a huge change really. After the update I did have about 20MB more free space on my phone, the update cleaned something up for sure.
Is there a way to apply the update to the v1 leak? or a way to update to the v3 leak and then apply this update? I tried renaming the v3 to update.zip and applying and it errors out saying authentication. Any help would be greatly appreciated as this update is for my wife's phone.
I upgraded from v1 to v3 then applied MR4 without problem. If you get the error screen (triangle with !) Press up volume then power key to continue. I got stuck there twice.
Sent from my Eris using XDA App
superbalde said:
Is there a way to apply the update to the v1 leak? or a way to update to the v3 leak and then apply this update? I tried renaming the v3 to update.zip and applying and it errors out saying authentication. Any help would be greatly appreciated as this update is for my wife's phone.
Click to expand...
Click to collapse
You can't apply the MR4 to v1 or v2, you have to flash to v3 first. Don't change the name to update.zip. it has to keep the same name. i think it's like pb31img.zip or something. Keep in mind that this won't just be an update. It is flashing the phone. Your apps and settings will be gone.
Turns out I was on v2, not v3, and I just didn't realize it. Not sure how that happened. Oh well. I flashed to v3, then ran the mr4 update w/o any problems. Then I rooted. Now I'm trying to find a good kernel to use w/stock ROM so I can overclock. Any suggestions?
Can someone that's currently running stock with the new update please go to settings>aboutphone and post their phones following specs please? It would save me quite a bit of time and I would greatly appreciate it.
Model Number
Android Version
Baseband Version
Kernel Version
Mod Version
Build Number
I'm having to get a replacement and they want to confirm i've installed the latest update. I'm rooted though and don't want to go through the process of unrooting/installing update/rerooting and then loading everything back on the phone when it gets here in three days.
Here's the newest (July 2010 OTA)
Firmware version 2.1
Baseband version 2.42.01.04.27
Kernel version 2.6.29-8a03cb9a [email protected] #1
Build number 2.37.605.4 CL185970 release-keys
Software number 2.37.605.4
Browser version WebKit 3.1
PRI Version 2.11_002
PRL Version 58003
ERI Version 5
You don't really need to unroot anymore, since root can be gained even with a 1.49.0000 S-ON bootloader.
If you want a factory phone with the July 2010 OTA update, I would just nuke the phone by overwriting it with either the Leak-V3 PB00IMG.ZIP or the "Official" RUU (same thing as the Leak-V3), and then download the July 2010 OTA from the google link, rename it to update.zip (on the root folder of the SD card), and apply by booting into the (stock) recovery menu.
bftb0
bftb0 said:
Here's the newest (July 2010 OTA)
Firmware version 2.1
Baseband version 2.42.01.04.27
Kernel version 2.6.29-8a03cb9a [email protected] #1
Build number 2.37.605.4 CL185970 release-keys
Software number 2.37.605.4
Browser version WebKit 3.1
PRI Version 2.11_002
PRL Version 58003
ERI Version 5
You don't really need to unroot anymore, since root can be gained even with a 1.49.0000 S-ON bootloader.
If you want a factory phone with the July 2010 OTA update, I would just nuke the phone by overwriting it with either the Leak-V3 PB00IMG.ZIP or the "Official" RUU (same thing as the Leak-V3), and then download the July 2010 OTA from the google link, rename it to update.zip (on the root folder of the SD card), and apply by booting into the (stock) recovery menu.
bftb0
Click to expand...
Click to collapse
Thanks a ton! I'll nuke it with the RUU when my new phone gets here. I just didn't want to have to do it before I got it just to get the information.
No, really, THANKS AGAIN!
bftb0 said:
Here's the newest (July 2010 OTA)
Firmware version 2.1
Baseband version 2.42.01.04.27
Kernel version 2.6.29-8a03cb9a [email protected] #1
Build number 2.37.605.4 CL185970 release-keys
Software number 2.37.605.4
Browser version WebKit 3.1
PRI Version 2.11_002
PRL Version 58003
ERI Version 5
You don't really need to unroot anymore, since root can be gained even with a 1.49.0000 S-ON bootloader.
If you want a factory phone with the July 2010 OTA update, I would just nuke the phone by overwriting it with either the Leak-V3 PB00IMG.ZIP or the "Official" RUU (same thing as the Leak-V3), and then download the July 2010 OTA from the google link, rename it to update.zip (on the root folder of the SD card), and apply by booting into the (stock) recovery menu.
bftb0
Click to expand...
Click to collapse
Just for clarification purpose so I don't mess anything up, I am rooted running the KaosFroYo ROM. All I need to do to unroot and send back to VZW is to simply download the 2.1 ROM, flash it. Then download the July update and then flash that. Root is gone, correct?
Does anyone have a new link to the update?
It seems as though Google removed it
Related
Since I will be starting work next week and activating my Thunderbolt I had to return to stock & unroot
After following the instructions below....
http://forum.xda-developers.com/showthread.php?t=1009423
I noticed after the first flash, that when I shutdown and started up in bootloader it automatically asked if I wanted to update and did so almost instantaneously....
I just wanted to know if there is anyway I can confirm that I'm back to stock and unrooted... Also will I be able to get the recent update from Verizon now that I returned to stock MR1?
ace2525 said:
Since I will be starting work next week and activating my Thunderbolt I had to return to stock & unroot
After following the instructions below....
http://forum.xda-developers.com/showthread.php?t=1009423
I noticed after the first flash, that when I shutdown and started up in bootloader it automatically asked if I wanted to update and did so almost instantaneously....
I just wanted to know if there is anyway I can confirm that I'm back to stock and unrooted... Also will I be able to get the recent update from Verizon now that I returned to stock MR1?
Click to expand...
Click to collapse
Boot to bootloader and make sure S-on and no custom recovery.
Check rom for Superuser.apk
Make sure baseband matches mr1 baseband.
If bootloader wanted to update immediately, you probably left a radio PG05IMG.zip file on your sdcard. Delete it.
Yes, after returning to stock you should get the OTA. You can manually force a software update to check for OTA too.
after doing the first step, i removed the first pg05img and replaced it with the next steps file...so like i said, it just took an update and completed in seconds. I assume that was the restoring of the original bootloader. No superuser so no more root
I cant restart just yet to check if S is back ON b/c OTA update is taking FOREVER to download....setting up my screens in the meantime. Thanks bro
baseband updated?
Another quick question....
my baseband is 1.39.00.0627r, 0.01.69.0625r meanwhile this ad for the OTA verizon update has a different baseband listed, 1.39.00.0613w, 0.01.69.0613w_1
source:
http://www.techwafer.com/wp-content/uploads/2011/07/HTC-ThunderBolt-software-update.jpg
Do i have the latest, whats the deal?
THANKS in advance!
bump...anyone??? above post
ace2525 said:
Another quick question....
my baseband is 1.39.00.0627r, 0.01.69.0625r meanwhile this ad for the OTA verizon update has a different baseband listed, 1.39.00.0613w, 0.01.69.0613w_1
source:
http://www.techwafer.com/wp-content/uploads/2011/07/HTC-ThunderBolt-software-update.jpg
Do i have the latest, whats the deal?
THANKS in advance!
Click to expand...
Click to collapse
The first baseband is the OTA MR2 Radio. I'm not sure about the other one.
Source:
http://support.vzw.com/system_update/thunderbolt.html
Hit "Benefits of Software Update" and it will show you the baseband.
On or about Nov. 2nd I received an update from Verizon. The update was automatic and occurred while I was at work. I lost root and I was going to re-root my TBolt and then I got another update. So, I figured that I would wait a couple of days. I tried to re-root my phone on Nov. 6 and the update failed. I rebooted the phone and now I have no service. I am assuming that this is a radio problem.
My technical info is;
- Software name - 2.11.605.5
- Status - update successful
- Code - 200
- Date - 11/2/2011
- Time - 2:33pm
Under the phones identity tab, everything is "unknown" or "not available" other than the model number and the serial number.
Android version - 2.3.4
HTC Sense ver. - 2.1
Software No. - 2.11.605.5
Kernal - 2.6.35.10-g00f8966
Baseband version - Unknown
Build No. - 2.11.605.5CL178661 release-keys
ERI or PRL are either not ready or not available
I used TB_Auto_Root several time in the past without any problems as this is my third time rooting (or trying to in this case) my TBolt
What is the best course to take
Thank you all in advance
MP
Download the latest RUU and install it on your phone. Download the RUU, NOT the root version. this is to ensure you got a clean initial install of the software plus the latest radios.
http://forum.xda-developers.com/showthread.php?t=1312193&highlight=thunderbolt+RUU
Then, try using the Revolutionary method...
http://www.youtube.com/watch?v=-UK_CiB2SYk
Very easy.
Hi guys... hope that this post reads also someone from development. If it should be placed there, please move it.
So, here is my problem:
I`m having rooted Razr and OTA update comes to my region. I downloaded update and tried to update, but it failed. I didn't uninstall any of bloatware, just frozen it, but even after unfreezing it won't do update as well. I red some manuals and so on, so i removed bootstrap recovery also but still the same. Looks, that I need to re-install original FW to make it working - right?
I checked possibilities and there are not too many. RAZR utility 1.6 it is not possible download anywhere - links are mostly broken and 1.7 is for ICS only, so only options is using of RSDLite. I found following "tutorial" about RSDLite. I'm almost sure, that after update there wouldn't be possibility to update for a while, so I kept original downloaded OTA update ZIP, but do not know what to do with.
Could somebody say, if it is correct way how to update to ICS? Do I really needs to reflash original ROM and than try to update it to ICS via OTA? Is there some easy way to update if I have downloaded OTA update ZIP?
Some ideas?
Sorry for English...
System version: 651.73.30.XT910.NonEFIGSRetail.en.EU
Android: 2.3.5
Baseband: U_03.1C.85P
Greetings:
I own a Verizon Samsung Galaxy Note 2 S. I rooted it and used TWRP which is running along with superuser and busy box. Still the stock ROM though and I am happy with it that way.
The latest OTA update was pushed out and every 5 days the device asks me to update or defer. I have tried updating several times but it always begins the process then TWRP opens after going through the opening screens and it says the update failed.
I did some reading and learned that if I accept this update I will lose Foxfi, which I use heavily. (I work for a school system that does not let us use the wireless, so I use my device as my hotspot.
Can anyone help me? I would either : a. like to accept the update while keeping the root and Fox Fi. Or b. Stop the update notices. (It's also weird because I was asked to set up a lock screen password and can't figure out how that happened. I'd like to remove it too since it's such a huge pain in the butt.
Is there any way to use TWRP to take the OTA update and still keep root and Fox Fi capability?
Device info: Android VErsion 4.1.2 Baseband i605VRAMC3 Kernel 3.0.31-4144933 [email protected]#1 SMP PREEMPT Sun Oct 28 13:34:23 KST 2012 Build Number JZO54K.I605VRAMC3
I am no where near tech savy enough to know what any of the above means, so would appreciate someone helping me!
Thanks
I must say that this is so far not possible....You can try 4.3 rom released by beans.... It's the same except the knox and locked bootloader.
Thanks,
Nikhil k Dhand
Chat: [email protected]
kalyanamitras said:
Greetings:
I own a Verizon Samsung Galaxy Note 2 S. I rooted it and used TWRP which is running along with superuser and busy box. Still the stock ROM though and I am happy with it that way.
The latest OTA update was pushed out and every 5 days the device asks me to update or defer. I have tried updating several times but it always begins the process then TWRP opens after going through the opening screens and it says the update failed.
I did some reading and learned that if I accept this update I will lose Foxfi, which I use heavily. (I work for a school system that does not let us use the wireless, so I use my device as my hotspot.
Can anyone help me? I would either : a. like to accept the update while keeping the root and Fox Fi. Or b. Stop the update notices. (It's also weird because I was asked to set up a lock screen password and can't figure out how that happened. I'd like to remove it too since it's such a huge pain in the butt.
Is there any way to use TWRP to take the OTA update and still keep root and Fox Fi capability?
Device info: Android VErsion 4.1.2 Baseband i605VRAMC3 Kernel 3.0.31-4144933 [email protected]#1 SMP PREEMPT Sun Oct 28 13:34:23 KST 2012 Build Number JZO54K.I605VRAMC3
I am no where near tech savy enough to know what any of the above means, so would appreciate someone helping me!
Thanks
Click to expand...
Click to collapse
If I was you, I would not accept the update. I would install the newest TWRP from here:
http://forum.xda-developers.com/showthread.php?t=2045829
Then I would make a back up of your current ROM. Then download a 4.3 ROM from here, (If you want the purest stock it would be Beans Rom that he posted, stock, rooted, no knox stuff). Also, download the Wifi/Modem MJ9 package he posted. Wipe clean x3, then install his 4.3 ROM, then boot to make sure it works, reboot into download mode, Open Odin 3.07, check the PDA box, the select file to place into PDA box (MJ9radio.tar), hit go, wait for it to finish and say pass. The wipe clean again x3, then boot into rom and your baseband for say MJ9 and Build Number should say 4.3. To make sure the MJ9 modem was accepted, you will have service and WIfi will work. If not you will see "Unknown Baseband"
Beans Thread: http://forum.xda-developers.com/showthread.php?t=2578458
Casual Root: http://forum.xda-developers.com/showthread.php?t=2272066
Guide: http://forum.xda-developers.com/showthread.php?t=2024207
To stop the OTA updater you need to rename or delete the following two files under /system/app and then reboot phone.
FWupgrade.apk to FWupgrade.bak
SDM.apk to SDM.bak
After a roll back updating ota is no longer possible. Is it possible to flash firmware manually?
You can contact Amazon support to place you back in the regular OTA pool.
Otherwise, you could try doing it manually. You'd want to download the BIN file and place it in the root of the internal storage directory. Then, just go into the menu where you usually check for updates, press the button, and it should say that it's ready to install.
Amazon say once downgraded you can't receive OTA again. Where would I find .BIN files for HDX 7
slugger09 said:
Amazon say once downgraded you can't receive OTA again. Where would I find .BIN files for HDX 7
Click to expand...
Click to collapse
The OTA block is applied on their side; it's based on your device's serial number (FSN). So, they can obviously undo it if you request it.
As for that BIN file, you can find the latest one as of right now here: http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813
It worked with the bin file. However I'm no soon updated until a system update has started downloading. It's 3.2.7 again.
slugger09 said:
It worked with the bin file. However I'm no soon updated until a system update has started downloading. It's 3.2.7 again.
Click to expand...
Click to collapse
You can read here about the OTA verification steps.
There are 3 ways to pass the version check:
1) use a OTA with a higher version number
2) remotely set a flag that disables the version check (guess you can exploit this by using bug 17356824 - poc here)
3) trick the verification system as I did
The problem is actually with the bootloader checks. As the OTA flashes a complete bootloader chain, the SBL1 version number will change. If it goes down, you end up with a brick (as I did).
I suspect the 3.2.7 OTA that Amazon has pushed for downgrading is a special build that has both a higher version number in build.prop and also on the SBL1 stage. This would explain why the 3.2.7 OTA keeps showing up even after upgrading to 4.5.x.
LE
While rooted you could try changing the version number in build.prop to the 4.5.1 one. This should trick the update system into downloading the 3.2.7 OTA. As you have root you could access the OTA bin and upload it. This way people wouldn't have to contact Amazon and request a downgrade.
Actually there is also a flag that disables SSL certificate verification. You could set this flag and then MITM the download.