Related
HOLD ON UPDATING!!! There are a bunch of people having data and wifi issues with this release. I have not had them but that doesn't mean you won't. Update at your OWN risk. You've been warned.
If you would like to update the software but not the baseband (probable cause for data/wifi issues) then just use my Nandroid linked below and leave your current baseband.
To everyone that keeps trying to relock their phones and flash the RUU to get the update it will NOT work. If you look at your software version you will see that it has added and R2 in it. I don't know why it does this, maybe it's a why for HTC to screw over the hackers yet again. Here is how to get the update.
There are 2 ways to get the update.
First: Use my Stock Rooted 1.84 Nandroid that I posted here. Simple but you will have to flash the radio separate.
Second: More steps but worked for me. NOTE: Only works if your on stock rooted phone. Will not work on custom ROM. Get Stock 1.53 Nandroid here. Credit to Reviewers for posting.
This will NOT wipe your phone nor do you need to wipe your phone if you are on Stock Rooted.
1a - This step only needed if you are on a custom ROM. If your on Stock Rooted then proceed to step 1b.
Download the above linked Nandroid (for 1.53) and restore it in Recovery. Reboot.
1b - Download this tool and use it to flash stock recovery. It will auto reboot your phone into bootloader so just start with your phone normally booted.
Credit goes to hasoon2000 for creating the tool!
2 - Your phone will reboot, once booted back up go to Settings>About Phone>Software Update. It will find the update and download then prompt to install. Select yes and let your phone update and reboot.
3 - Fire up the tool from step 1b again and this time flash CWM Recovery (whichever you prefer).
4 - After reboot is complete reboot again back into recovery and flash this to restore SU permissions (seems the update breaks them, at least for me).
Credit goes to Chainfire for creating this!
5 - Reboot, Done.
Any way to force the update if you have already received it once? I downloaded it yesterday but it failed because I had CWM installed at the time. I've flashed back to stock recovery but when I check for an update it says one isn't available.
I wonder if I could call T-Mobile and have them push it again?
DigitalMonk said:
Any way to force the update if you have already received it once? I downloaded it yesterday but it failed because I had CWM installed at the time. I've flashed back to stock recovery but when I check for an update it says one isn't available.
I wonder if I could call T-Mobile and have them push it again?
Click to expand...
Click to collapse
Did you totally wipe your phone? If not then the update is in your " download" folder
Sent from my HTC One S
Yeah, I know it's in Download, I posted about that in another thread yesterday. But is there some way to flash it now from that file? I thought from reading the other threads there was no flashable version yet, or was that only if you are running CWM?
DigitalMonk said:
Yeah, I know it's in Download, I posted about that in another thread yesterday. But is there some way to flash it now from that file? I thought from reading the other threads there was no flashable version yet, or was that only if you are running CWM?
Click to expand...
Click to collapse
Try deleting that file and checking again. Back it up to your computer first of course.
setzer715 said:
Try deleting that file and checking again. Back it up to your computer first of course.
Click to expand...
Click to collapse
Didn't work for me. I got about 2 downloads out of the servers, and then they aren't sending it anymore. Weak.
No go so far. Copied it to my PC, deleted it from my Download folder, re-booted and then checked for an update 3 different times and nothing so far.
With all of the people having wifi and data issues TMO may have stopped sending it until they figure out what is going on. I do know for a fact that TMO tests any software update the send so something may have gone haywire with it. Maybe got radio mixed up.
DigitalMonk said:
I thought from reading the other threads there was no flashable version yet, or was that only if you are running CWM?
Click to expand...
Click to collapse
Wait.. I didn't know this. You mean even if we "unroot" and flash stock recovery (and using stock ROM of course), we cannot flash this ourselves?
I currently have the CWM touch recovery and root, u/l bootloader, etc., and TMO has sent me 2 updates, both were in the Downloads folder. I didn't notice that it updated (as I never confirmed) but they obviously didn't install.
But I would have done the above if I had known we couldn't just flash it ourselves. WTF T-mobile?? Those of us who know how to flash a file should at least not be prevented from doing so (especially since we need to have the original recovery installed).
Sent from my HTC One-S (rooted), stock ROM
I found this thread and since i am a newbie when i read it a few questions came on my mind
Alternative Firmware update Method
1. Decompress downloaded .zip file (it will be another .zip)
2. Rename it to EP201_768_SDUPDATE.zip
3. Format FAT32 the MicroSD card that you will be using for the update process
4. Copy the file to (the root directory of) your MicroSD
5. Insert it into the tablet
6. Shutdown (power off) the tablet
7. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
8. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button until you see Android logo and process bar
9. Wait patiently for 10 minutes or so
10. Enjoy!
Also remember that you will probably need to use RootKeeper to regain root privileges and reinstall BusyBox too (firmware update changes the /system partition).
That's the thread i have read and the questions that came to my mind are:
1.Do i use the same method for any update?
2.Is it a safe way to update my firmware because after you unlock bootloader no OTA update but only manual update is possible.So is this the right way to manually update any version of firmware update from now on?
3.Is there any other way to manually update my Asus?
4.Do i have to follow another way of installing the update because of the custom recovery that i have installed? (TWRP)
5.If i format the SD Card using exFAT will this method work or not?
I appreciate any help you could give me since i am a noob and some things seem really scary to me due to the fear of bricking my device,
Thank you in advance for your patience reading my questions:angel:
Help with OTA
Dino,
I have a few quesitons for you (just to verify).
Is your boot loader unlocked?
If so, are you running a custom recovery?
If not, then why don't you just use the over the air update?
If your boot loader is unlocked, and you are running a custom recovery (which I understand you are), then yes, you will likely need to update from SD Card from here on out. Once you unlock the boot loader you can no longer get OTA updates. I would recommend following this thread: http://forum.xda-developers.com/showthread.php?t=1915079
If you are already rooted then you can use SuperSU, and OTA Rootkeeper to regain root after the update. There are tons of threads that discuss this. If you are doing root for the first time, you should read this: http://forum.xda-developers.com/showthread.php?t=1916762
The SD Card format needs to be FAT32. In regards to being a "noob" and scared, you should be. Did you make a recovery image using NvFlash before you touched your tablet in the first place? If not, then I would recommend that once you get to JB that you never attempt to load anything on your tablet ever again, at least not until you are no longer a "noob", and you are understanding and accepting of the fact that you may hard brick your tablet some day.
dinothenino said:
I found this thread and since i am a newbie when i read it a few questions came on my mind
Alternative Firmware update Method
1. Decompress downloaded .zip file (it will be another .zip)
2. Rename it to EP201_768_SDUPDATE.zip
3. Format FAT32 the MicroSD card that you will be using for the update process
4. Copy the file to (the root directory of) your MicroSD
5. Insert it into the tablet
6. Shutdown (power off) the tablet
7. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
8. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button until you see Android logo and process bar
9. Wait patiently for 10 minutes or so
10. Enjoy!
Also remember that you will probably need to use RootKeeper to regain root privileges and reinstall BusyBox too (firmware update changes the /system partition).
That's the thread i have read and the questions that came to my mind are:
1.Do i use the same method for any update?
2.Is it a safe way to update my firmware because after you unlock bootloader no OTA update but only manual update is possible.So is this the right way to manually update any version of firmware update from now on?
3.Is there any other way to manually update my Asus?
4.Do i have to follow another way of installing the update because of the custom recovery that i have installed? (TWRP)
5.If i format the SD Card using exFAT will this method work or not?
I appreciate any help you could give me since i am a noob and some things seem really scary to me due to the fear of bricking my device,
Thank you in advance for your patience reading my questions:angel:
Click to expand...
Click to collapse
droidhaxxor said:
Dino,
I have a few quesitons for you (just to verify).
Is your boot loader unlocked?
If so, are you running a custom recovery?
If not, then why don't you just use the over the air update?
If your boot loader is unlocked, and you are running a custom recovery (which I understand you are), then yes, you will likely need to update from SD Card from here on out. Once you unlock the boot loader you can no longer get OTA updates. I would recommend following this thread: http://forum.xda-developers.com/showthread.php?t=1915079
If you are already rooted then you can use SuperSU, and OTA Rootkeeper to regain root after the update. There are tons of threads that discuss this. If you are doing root for the first time, you should read this: http://forum.xda-developers.com/showthread.php?t=1916762
The SD Card format needs to be FAT32. In regards to being a "noob" and scared, you should be. Did you make a recovery image using NvFlash before you touched your tablet in the first place? If not, then I would recommend that once you get to JB that you never attempt to load anything on your tablet ever again, at least not until you are no longer a "noob", and you are understanding and accepting of the fact that you may hard brick your tablet some day.
Click to expand...
Click to collapse
Thank you very much for your kind reply.I am rooted but still have not unlocked Bootloader. After i've read several threads i was too scared to unlock my bootloader,that's why i was waiting for some answers in order to do it. Basically the only reason for me to unlock the bootloader is the fact that i can keep a backup of my whole device (nandroid if i say it correctly) by using a custom recovery, that's it and that is for me the only reason to do it. I am not interested in flashing custom ROMs just Backup my device.
So what is your suggestion for me to do, with the fact in mind that i want to backup my device.
As for the other thing that you mentioned "nVFlash" i don't know how to do it and although i have read some threads about it i am still very confused how to do it. If you could guide me through it, in simple steps, i would be very grateful. I am on .26 version if that helps.
So to sum up,I got my Asus rooted, locked bootloader, firmware version .26, stock recovery, help is always appreciated !!!
Thank you again in advance,
dinothenino said:
Basically the only reason for me to unlock the bootloader is the fact that i can keep a backup of my whole device (nandroid if i say it correctly) by using a custom recovery, that's it and that is for me the only reason to do it. I am not interested in flashing custom ROMs just Backup my device.
So what is your suggestion for me to do, with the fact in mind that i want to backup my device.
Click to expand...
Click to collapse
If you really just want to backup all your apps and your data, you do not need to unlock or install a custom recovery at all. Just use something like Titanium Backup and that's it. Everything else (kernel, system and recovery) can be restored from the official Asus firmware image.
dinothenino said:
So to sum up,I got my Asus rooted, locked bootloader, firmware version .26, stock recovery,
Click to expand...
Click to collapse
That's exactly the same as I have (locked, rooted, .26), and I am still not sure whether I want to unlock my bootloader and void my warranty. I am at least interested in trying some custom ROMs later, but first I need to understand what exactly the locked bootloader prevents me to do (flashing and loading custom recovery/kernel images and using fastboot - anything else?).
_that said:
If you really just want to backup all your apps and your data, you do not need to unlock or install a custom recovery at all. Just use something like Titanium Backup and that's it. Everything else (kernel, system and recovery) can be restored from the official Asus firmware image.
That's exactly the same as I have (locked, rooted, .26), and I am still not sure whether I want to unlock my bootloader and void my warranty. I am at least interested in trying some custom ROMs later, but first I need to understand what exactly the locked bootloader prevents me to do (flashing and loading custom recovery/kernel images and using fastboot - anything else?).
Click to expand...
Click to collapse
You pretty much say it all, with unlocked bootloader, you could flash, custom recovery, kernel, rom, using fastboot, scripts excepted for boot animation for now, cause you need a kernel that supporting it, once we have a custom kernel that support boot animation, you could do that too.
Back to the OP topic, if you have locked bootloader, rooted and running .26 build, you have 2 options to upgrade, but first make sure you read the thread about how to make a backup of your bootloader using NVFLASH before upgrade to .30 or JB. This is extremely important and since you're still at .26, consider yourself a lucky one. Next make sure you have Voodoo OTA installed and make a backup of your root. Also verify that indeed you do have root by download "root checker" from the market. Also use Titinum backup and backup your device. Finally, you have 2 easy options to upgrade.
A. OTA,(incremental upgrade), automatic download and upgrade your device push out by Asus.(No brainer)
B. Manual upgrade, if you prefer to do a full version (fresh install). It is recommended that you do a factory reset before and after the upgrade.
1) Download the correct latest firmware from Asus site, for JB the firmware called US_epad_user_10_4_4_16_UpdateLauncher.zip (this is US version).
2) Extract the .zip file, it will be another .zip file. This zip named EP201_768_SDUPDATE.zip.
3) Copy the file EP201_768_SDUPDATE.zip from your PC to the root of your MicroSD card.
4) Insert the MicroSD card in your tablet and use this button combination to go to recovery --> Start the tablet by pressing Volume Down and POWER together for 5 seconds ,a message will inform you that you have 5 seconds to enter the recovery,press Volume UP before the 5 seconds expire. At this point the device will go in recovery and should start updating your firmware.
5. If you upgrade from .30 to JB, you could skip step 4 and after step 3, just reboot your device and it should find and prompt you to update.
Thats it ..profit!!
There are couple more, but mainly used if you soft brick or issue, like extract the blog file from Asus download and use fastboot to push etc..but I don't think we need that right now.
I'd like to know more about the details of using fastboot and the blob file. Can you link me to a thread that shows that?
johnlgalt said:
I'd like to know more about the details of using fastboot and the blob file. Can you link me to a thread that shows that?
Click to expand...
Click to collapse
Here you go:
http://forum.xda-developers.com/showthread.php?t=1915598
I found that using fastboot from your pc is working bit better.
Actually, quite funny as I was just reading that. I'm attempting to downgrade to 9.4.5.30 now so I can root and then Keep Root and then re-upgrade and see if I can repair root.
I suppose this would be a bad time to think about 'blobbing' the tablet to JB
I would be more worried about the process except for the fact that I checked the binary-script file and all it does it put the blob on the device. No stupid patching like in Motorola devices. Makes like easier to deal with (in terms of applying updates) but a heck of a lot more bandwidth used (in terms of OTAs).
Speaking of which, are the OTAs the same files, full on blob installs, or are they patches? Just curious....
johnlgalt said:
Speaking of which, are the OTAs the same files, full on blob installs, or are they patches? Just curious....
Click to expand...
Click to collapse
The OTAs contain patches for files in /system, and a blob for kernel, bootloader, recovery (EBT, SOS, LNX).
Hey guys so i got a used Atrix 2 AT&T (MB865) running 2.3.6. Every time i reboot the phone all the data seems to get wiped and the android setup screen appears. I tried to FXZ to 2.3.5 using RSDLite and the correct replacement packages and the phone goes through the process but when it says its done the phone goes into stock recovery. I try rebooting out of stock recovery and the phone boots back into 2.3.6 with the setup screen but the problem is still there. Also, when i try to OTA to ICS the update installs, but the phone goes to stock recovery after reboot. Please help
Atrix 2
(MB865)
Android version 2.3.6
system version 55.13.25.MB865.ATT.en.US
Baseband version 2011-11-16 23:52 Off.Bld
LUD_EDISION_R1D7_PATCH_36_111116_2336
Webtop version WT-1.3.0-176
Kernel version [email protected] #1
Build number 5.5.1-175_EDMR1.25
Try doing a factory reset or stock recovery reset and see if that sticks through a reboot.
ΧΔΑ Fraternity's Godfather. Read About Our History!
Apex_Strider said:
Try doing a factory reset or stock recovery reset and see if that sticks through a reboot.
ΧΔΑ Fraternity's Godfather. Read About Our History!
Click to expand...
Click to collapse
Sorry man i tried both and its still stuck on 2.3.6 and wipes on reboot
Popwii said:
Sorry man i tried both and its still stuck on 2.3.6 and wipes on reboot
Click to expand...
Click to collapse
Charge your battery up, and try using RSD to flash the Official ICS image. Maybe something isn't getting patched or overwritten in the upgrade to ICS.
The ICS image can be found here, and if you don't know how to use RSDlite, check the noob guide. All the details are there.
41rw4lk said:
Charge your battery up, and try using RSD to flash the Official ICS image. Maybe something isn't getting patched or overwritten in the upgrade to ICS.
The ICS image can be found here, and if you don't know how to use RSDlite, check the noob guide. All the details are there.
Click to expand...
Click to collapse
Tried flashing the ics file and it stops at 4/19 and says Failed mbmloader is not returning Help
Popwii said:
Tried flashing the ics file and it stops at 4/19 and says Failed mbmloader is not returning Help
Click to expand...
Click to collapse
First, make sure your drivers and RSDlite are up to date. This isn't totally necessary, but you might as well have a clean slate to go from. So make sure your phone is unplugged from your pc, uninstall MotoDeviceManager, reboot, then install it again from here.
RSDlite 6 is here
After everything is fresh, connect your phone and give it a few minutes to detect and install your drivers. Once that's done, boot into fastboot and verify that it sees your device, if you're already in fastboot then just verify.
Code:
fastboot devices
On your phone screen it should tell you what bootloader version you have, it should say 0A.72, if not, then stop and post back what it says. Otherwise, open RSDlite, and try to flash the Official ICS FXZ you downloaded previously. By the way, the FXZ should be named InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip and the MD5sum should be 2BF9CCD528C05D26523ACC5B38AC76C6 if neither of those match, you need to make sure you have the right FXZ and make sure that the MD5sum matches what I posted.
So, if all is well and everything checks out, point RSDlite to the FXZ and start the flash, be patient. If it still fails, then you might try this. It's a way to flash the Official AT&T ICS FXZ without RSDlite, just download it, extract it, and follow the simple instructions in the readme.txt. Make sure RSDlite is closed before you run the .bat file. If you have to resort to this method, and it works for you, make sure you find Alteredlikeness around here and thank him, he put the script together.
If none of that works, then post back and we'll go from there.
Ok so i booted into fastboot and it says the bootloader is 0A.65
Popwii said:
Ok so i booted into fastboot and it says the bootloader is 0A.65
Click to expand...
Click to collapse
Alright, your bootloader is still for 2.3.6, obviously the OTA attempt never flashed the new one, or it never went properly. You might download the 2.3.6 FXZ here the MD5 sum for it is FCC0FBFDEDEAE084F90E34BF2523EB27
Flash it with RSDlite, that will hopefully get you on a clean and stable GB 2.3.6 After that, if you want to get on ICS and need some help, post back, or if getting back to 2.3.6 doesn't work, post back.
Um ok so i tried flashing that file and it stopped at 3/20 flash mbmloader mbmloader.bin phone return fail
Popwii said:
Um ok so i tried flashing that file and it stopped at 3/20 flash mbmloader mbmloader.bin phone return fail
Click to expand...
Click to collapse
How did you get into the state you're in originally? Did you try to flash something? A rom? A FXZ? You said you got a used Atrix2, was it messed up from the get go? Anyway, download this unzip it and follow the directions in the readme.txt. You'll need to unzip the Official ICS 4.0.4 FXZ that you downloaded previously as well. Basically unzip the ICS FXZ on your desktop (not the 2.3.6), then unzip the restore script and put everything in your unzipped 4.0.4 FXZ, put your phone into fastboot mode and run the restore-to-ics.bat file. Post back with results.
*Note - keep an eye on your bootloader version, if it changes from 0A.65 do NOT try and flash anything Gingerbread, you'll have to stick strictly to ICS if that changes.
Alright so i copied the batch files into the ics fxz and when i try flashing after the bootloader flashes the atrix2 says flash faliure at the top and when the entire flash is done it just returns to fastboot as if nothing happened. Also, when i reboot the phone the first time after the flash it boots into stock recovery
Popwii said:
Alright so i copied the batch files into the ics fxz and when i try flashing after the bootloader flashes the atrix2 says flash faliure at the top and when the entire flash is done it just returns to fastboot as if nothing happened. Also, when i reboot the phone the first time after the flash it boots into stock recovery
Click to expand...
Click to collapse
I'm running out of ideas. Since you can get into recovery, maybe try putting the ICS OTA on your SDcard. From the recovery, do a factory reset, wipe the cache, then try updating from external storage.
If all of that doesn't work, you might try another USB port, or another computer, and try RSDlite and the ICS FXZ again. According to your bootloader, you're still on 2.3.6, so the ICS FXZ should work and just replace everything. Maybe Jim or someone can help you along.
Here is a link to the 1st ICS leak, you can put that on your SDcard and flash it from recovery. Also, since it is the 1st leak build, you can restore to GB using a specific method outlined here. But if you can at least get the ICS leak to flash, you still have an option to update to the Official ICS.
Do not try to flash GB once you update. If you manage to get on ICS leak 1, it is possible to flash GB, but it is a modified version. Just to be clear.
41rw4lk said:
I'm running out of ideas. Since you can get into recovery, maybe try putting the ICS OTA on your SDcard. From the recovery, do a factory reset, wipe the cache, then try updating from external storage.
If all of that doesn't work, you might try another USB port, or another computer, and try RSDlite and the ICS FXZ again. According to your bootloader, you're still on 2.3.6, so the ICS FXZ should work and just replace everything. Maybe Jim or someone can help you along.
Here is a link to the 1st ICS leak, you can put that on your SDcard and flash it from recovery. Also, since it is the 1st leak build, you can restore to GB using a specific method outlined here. But if you can at least get the ICS leak to flash, you still have an option to update to the Official ICS.
Do not try to flash GB once you update. If you manage to get on ICS leak 1, it is possible to flash GB, but it is a modified version. Just to be clear.
Click to expand...
Click to collapse
It seems that he previous owner put ubuntu on the phone because when i use root file explorer i see folders like /osh so i was wondering could that be conflicting also it says 2.6 gb available out of 7 gb so maybe something else is installed that is protecting from fxzing
Popwii said:
It seems that he previous owner put ubuntu on the phone because when i use root file explorer i see folders like /osh so i was wondering could that be conflicting also it says 2.6 gb available out of 7 gb so maybe something else is installed that is protecting from fxzing
Click to expand...
Click to collapse
Most likely seeing directories from webtop, and ICS does away with webtop, so it shouldn't affect FXZing. What state is the phone in currently? Can it boot? (I assume yes because you mentioned a root file explorer). Did you try to update through the stock recovery? If it can boot, I would try and get it back to as stock as possible, factory reset and all that, wipe cache, dalvik. Double check your software version, model, kernel. firmware, all that and verify that you have a 2.3.6 AT&T device.
41rw4lk said:
Most likely seeing directories from webtop, and ICS does away with webtop, so it shouldn't affect FXZing. What state is the phone in currently? Can it boot? (I assume yes because you mentioned a root file explorer). Did you try to update through the stock recovery? If it can boot, I would try and get it back to as stock as possible, factory reset and all that, wipe cache, dalvik. Double check your software version, model, kernel. firmware, all that and verify that you have a 2.3.6 AT&T device.
Click to expand...
Click to collapse
Yes the phone boots but needs to be re activated every boot and after 2-3 it reboots by itself. Also, the factory reset doesnt seem to work because it just restarts my phone when done through android and when doing the hard reset way through stock recovery it doesnt fix the problem
Popwii said:
Yes the phone boots but needs to be re activated every boot and after 2-3 it reboots by itself. Also, the factory reset doesnt seem to work because it just restarts my phone when done through android and when doing the hard reset way through stock recovery it doesnt fix the problem
Click to expand...
Click to collapse
Install a custom recovery if you don't have one, I'll attach Atrix2Bootstrap just in case. Reboot into custom recovery, and try to factory reset from there. Even if that doesn't work, try to wipe the cache, the dalvik, and your battery stats, then fix permissions. Post back with what worked or didn't work, and make sure the battery is charged up.
41rw4lk said:
Install a custom recovery if you don't have one, I'll attach Atrix2Bootstrap just in case. Reboot into custom recovery, and try to factory reset from there. Even if that doesn't work, try to wipe the cache, the dalvik, and your battery stats, then fix permissions. Post back with what worked or didn't work, and make sure the battery is charged up.
Click to expand...
Click to collapse
I dont think i can install a custom recovery because everytime i root it reboots and the root isnt installed.
Popwii said:
I dont think i can install a custom recovery because everytime i root it reboots and the root isnt installed.
Click to expand...
Click to collapse
Since you can at least boot in android, you should verify some info.
Go to Settings > About Phone and note
System version -
Model number -
Firmware-
etc -
Post back with all of your info, be specific.
Download superuser from the market and install it.
Open your command prompt and type
Code:
adb shell
su
See if you get a permission denied, or if you get root #
Post all of the requested info.
41rw4lk said:
Since you can at least boot in android, you should verify some info.
Go to Settings > About Phone and note
System version -
Model number -
Firmware-
etc -
Post back with all of your info, be specific.
Download superuser from the market and install it.
Open your command prompt and type
Code:
adb shell
su
See if you get a permission denied, or if you get root #
Post all of the requested info.
Click to expand...
Click to collapse
(MB865)
Android version 2.3.6
system version 55.13.25.MB865.ATT.en.US
Baseband version 2011-11-16 23:52 Off.Bld
LUD_EDISION_R1D7_PATCH_36_111116_2336
Webtop version WT-1.3.0-176
Kernel version [email protected] #1
Build number 5.5.1-175_EDMR1.25
Popwii said:
(MB865)
Android version 2.3.6
system version 55.13.25.MB865.ATT.en.US
Baseband version 2011-11-16 23:52 Off.Bld
LUD_EDISION_R1D7_PATCH_36_111116_2336
Webtop version WT-1.3.0-176
Kernel version [email protected] #1
Build number 5.5.1-175_EDMR1.25
Click to expand...
Click to collapse
You should try to downgrade to 2.3.5 and start from the beginning. Since your system is borked and you can't update, hopefully downgrading will at least get you to something stable that you can work with. The noob guide will tell you how to downgrade from 2.3.6 to 2.3.5, just pay attention because you'll most likely have to replace some FXZ files since the 2.3.6 you're on is most likely from an OTA.
About 1/3rd of the way down the page you'll see "How to flash the FXZ once applying the OTA update and get back to 2.3.5", follow those instructions.
I'm really confused about something and before I get flamed for not searching before posting, let me preface by saying that I have and still can't find a definitive answer given that nobody seems to reference the problem I'm having - at least it doesn't show up in my attempts to search.
My Question: Once I'm rooted, what is the process for accepting an OTAs (over the air updates) from Verizon? Whenever I download and install them, I get the "Custom" Lock Icon during bootup.
Here are the steps I've followed:
1. Flashed back to stock 4.1.1
2. Flashed the VRALEC bootchain
3. Flashed CWMR
4. Booted into CWMR recovery and ran the SuperSU_Bootloader_FIXED.zip (Note: no message appeared asking me about locking
5. Flashed the 4.1.1 bootchain
6. Downloaded and it auto rebooted to install the OTA (I wanted to see what it's like the NEXT time verizon pushes out an OTA so I know what the process is once all my apps are installed)
7. When finished applying the update it asks me: A. Do I want to Disable recovery flash? and B. Do I want to preserve root?
At first I tried answering both questions with yes and yes since I saw the message about that here: http://forum.xda-developers.com/showthread.php?t=2046439
My Problem: As soon as I rebooted, I get the custom lock icon message during bootup. So then I repeated the entire process and answered No and No to those questions. And again, I get the custom lock icon message during bootup.
Yes, I realize, I can and probably should install the OTA and then root the device. But that's not my point. I want to understand what to do the NEXT time Verizon pushes out an OTA. Do I have to flash back to stock every time I install the OTA and root the device only after installing the OTA just to avoid getting the custom lock icon? If not, how do I accept the OTA without getting the custom lock icon? (Obviously I can't seem to figure out how to do it now, so I won't be able to do it the next time an OTA rolls around - thus the reason for my question).
Thanks,
Jonathan
you might have to flash a custom ROM to block Verizon from pushing OTA.
http://forum.xda-developers.com/showthread.php?t=1762709
Reference section 5 for me. It looks like you already know how to get to that point. It has great instructions for recovering to stock from the triangle.
As far as disabling updates go I would recommend titanium backup, and freezing the update service. "FWUpgrade" as well as "SDM" are the names. You can also uninstall it, but freezing it in Titanium is my recommendation.... This will prevent your phone from pinging OTA updates in the future even when big red pushes them.
Honestly, if you want the new feature just wait a day or two after the release. There is always a lovely developer waiting to debloat, deodex, and optimize the official OTA update for your use without breaking root access.
Have I helped with your question? Or have I misinterpreted your needs?
First, thanks for the replies!
ManiakalSealion said:
http://forum.xda-developers.com/showthread.php?t=1762709
Reference section 5 for me. It looks like you already know how to get to that point. It has great instructions for recovering to stock from the triangle.
Click to expand...
Click to collapse
I think you misunderstood me on this point. When installing an OTA after root, I never get the yellow triangle, so there is no need to recover. The problem I'm having is that on the very first screen that appears when you first power on the phone (after installing the OTA on top of a rooted version of Android) it adds a large lock icon with the word "CUSTOM" to black screen (think it says Samsung but I don't recall) to indicate that Verizon has detected something custom about the phone.
I was trying to determine if after having rooted my phone if there was a way to accept the OTA and still maintain root - rather than having to flash back to stock or flash an update using ODIN. It's a pain to have to always flash something at home - I'd like to be able to accept the OTA if possible while I'm away from home. I tried OTA Rootkeeper but that didn't seem to do anything for me - perhaps I'm not using it correctly???
ManiakalSealion said:
http://forum.xda-developers.com/showthread.php?t=1762709
As far as disabling updates go I would recommend titanium backup, and freezing the update service. "FWUpgrade" as well as "SDM" are the names. You can also uninstall it, but freezing it in Titanium is my recommendation.... This will prevent your phone from pinging OTA updates in the future even when big red pushes them.
Click to expand...
Click to collapse
So if I understand correctly, an app such as OTA Rootkeeper is useless for Verizon Galaxy S3 - the only way to get root and the Verizon OTA is to either 1. flash back to stock, install all OTAs and then re-root OR else 2. flash the custom OTA from a forum member, is that correct? In other words, once I've rooted, I always have to use ODIN to get an update - there is no other option?
jkrueger2020 said:
First, thanks for the replies!
I think you misunderstood me on this point. When installing an OTA after root, I never get the yellow triangle, so there is no need to recover. The problem I'm having is that on the very first screen that appears when you first power on the phone (after installing the OTA on top of a rooted version of Android) it adds a large lock icon with the word "CUSTOM" to black screen (think it says Samsung but I don't recall) to indicate that Verizon has detected something custom about the phone.
Click to expand...
Click to collapse
I'll suggest using EZ Unlock v1.2, just tap to lock then immediately tap to unlock your bootloader and you'll hear an audio confirmation upon pressing unlock. I think that should take care of the custom lock when booting up.
I was trying to determine if after having rooted my phone if there was a way to accept the OTA and still maintain root - rather than having to flash back to stock or flash an update using ODIN. It's a pain to have to always flash something at home - I'd like to be able to accept the OTA if possible while I'm away from home. I tried OTA Rootkeeper but that didn't seem to do anything for me - perhaps I'm not using it correctly???
Click to expand...
Click to collapse
I'll say this, most custom roms block Verizon OTA's from installing so you'll just have to accept that you need to flash back to stock to accept an OTA OR just stick to a rooted OTA based rom. There's at least seven of these, one per OTA or leak that we've seen to date.
So if I understand correctly, an app such as OTA Rootkeeper is useless for Verizon Galaxy S3 - the only way to get root and the Verizon OTA is to either 1. flash back to stock, install all OTAs and then re-root OR else 2. flash the custom OTA from a forum member, is that correct? In other words, once I've rooted, I always have to use ODIN to get an update - there is no other option?
Click to expand...
Click to collapse
Absolutely correct. Can I ask you something? Do you intend on using custom roms or do you just want to use rooted stock OTA's? Cuz you're inquiring an awful lot about OTA's for someone who would be using custom roms. That said, XDA devs have posted a rooted version of each OTA available. Each is in the dev section, they'll be titled something like "Stock Root JB 4.1.2 - I535VRBMB1 Official Update". You could easily just flash any one of these then pull down an OTA since these are left untouched with the only addition being SuperUser. Even still, you would need to re-root after accepting an OTA since OTA's wipe out root so you'll be doing this for as long as we see updates on this phone.
If you're rooted you can use OTA Rootkeeper to back up root, install OTA and then use it again to restore root. I just did this for the current OTA without any issues. Just make sure you also have stock recovery reinstalled if you installed TWRP or CWM, and relock the boot loader first.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
I'll suggest using EZ Unlock v1.2, just tap to lock then immediately tap to unlock your bootloader and you'll hear an audio confirmation upon pressing unlock. I think that should take care of the custom lock when booting up.
Click to expand...
Click to collapse
Yes! That removed the lock icon. So my next question is, when my phone booted back up and said the OTA failed (yet still shows the incremented version number making it appear like the update actually was successful) was there anything that got messed up as part of the upgrade? Or would I be better off going the route of another person's reply which said I should lock the bootloader and flash back to stock recovery first before accepting the OTA?
SlimSnoopOS said:
I'll suggest using EZ Unlock v1.2
Can I ask you something? Do you intend on using custom roms or do you just want to use rooted stock OTA's?
Click to expand...
Click to collapse
Currently I'm not really looking for custom ROMS - my experience with ROMS with my original Galaxy S was just a buggy experience (i.e. call volumes that kept reverting to max for every call, etc) and was not very enjoyable. As long as I stay rooted and current with Android I'm happy at this point (of course that could change down the road).
mav3rick478 said:
If you're rooted you can use OTA Rootkeeper to back up root, install OTA and then use it again to restore root. I just did this for the current OTA without any issues. Just make sure you also have stock recovery reinstalled if you installed TWRP or CWM, and relock the boot loader first.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thank you!!!! That was exactly what I was hoping to find! I tried this out just for kicks to see if it would work for me and it did!
For anyone interested, here are the steps I took with my rooted device :
1. Lock the boot loader using EZ-Unlock 1.2
2. Using EZ-Recovery 2.2, I flashed the stock recovery
3. Backed up root access using OTA Root Keeper
4. Downloaded and installed the OTA
Note: The lock icon appeared still
5. Used EZ-Recovery 2.2. to flash CWM recovery in place of the stock recovery (I couldn't get it to flash the same tar.md5 file I used with ODIN though - don't know what kind of file EZ-Recovery needs - so I used the version of CMWR that it provided)
6. Restored root access using OTA Root Keeper (needs reboot I think for this step)
7. Unlocked boot loader using EZ-Unlock 1.2
I may have gotten these steps slightly out of order but this successfully allowed me to install the OTA (with a successful install message too) and got rid of my lock icon!!!
jkrueger2020 said:
Thank you!!!! That was exactly what I was hoping to find! I tried this out just for kicks to see if it would work for me and it did!
For anyone interested, here are the steps I took with my rooted device :
1. Lock the boot loader using EZ-Unlock 1.2
2. Using EZ-Recovery 2.2, I flashed the stock recovery
3. Backed up root access using OTA Root Keeper
4. Downloaded and installed the OTA
Note: The lock icon appeared still
5. Used EZ-Recovery 2.2. to flash CWM recovery in place of the stock recovery (I couldn't get it to flash the same tar.md5 file I used with ODIN though - don't know what kind of file EZ-Recovery needs - so I used the version of CMWR that it provided)
6. Restored root access using OTA Root Keeper (needs reboot I think for this step)
7. Unlocked boot loader using EZ-Unlock 1.2
I may have gotten these steps slightly out of order but this successfully allowed me to install the OTA (with a successful install message too) and got rid of my lock icon!!!
Click to expand...
Click to collapse
Almost worked flawlessly... I had to reboot from SuperSU to get root again.
I found the sdm thing to freez
smalrus said:
Almost worked flawlessly... I had to reboot from SuperSU to get root again.
Click to expand...
Click to collapse
I found the sdm thing to freez but could not find the fwupgrade one. I was also not able to fine the ez unlocker is that in the play store?
I am not sure if the sdm will block the update but now when I go to about phone and select software update it errors out. Also I am only rooted do I realy need to worry about the update? Also looking for a good stable rom. If anyone wants recomend one. Just got my phone like a week ago. Thank you guys. Xda has been great help.
joker66599 said:
I found the sdm thing to freez but could not find the fwupgrade one. I was also not able to fine the ez unlocker is that in the play store?
I am not sure if the sdm will block the update but now when I go to about phone and select software update it errors out. Also I am only rooted do I realy need to worry about the update? Also looking for a good stable rom. If anyone wants recomend one. Just got my phone like a week ago. Thank you guys. Xda has been great help.
Click to expand...
Click to collapse
Re-read the thread to find EZ Unlock, I'm fairly certain someone posted a link. I will say it's been removed from the Play Store for awhile now.
Freezing sdm 1.0 is all you really need to do. That's normal that it errors out now. You froze that setting so it won't be polling for an OTA nor allow you to manually search for an OTA. Whether you want the OTA or not is on you, there isn't much present that we do not already have in custom roms plus the OTA has already been rooted.
Sent from my SCH-I535 using xda app-developers app
This is what worked for me except I reversed step 5 and 6 (I edited the quote below to match what I did). Thanks!
jkrueger2020 said:
Thank you!!!! That was exactly what I was hoping to find! I tried this out just for kicks to see if it would work for me and it did!
For anyone interested, here are the steps I took with my rooted device :
1. Lock the boot loader using EZ-Unlock 1.2
2. Using EZ-Recovery 2.2, I flashed the stock recovery
3. Backed up root access using OTA Root Keeper
4. Downloaded and installed the OTA
5. Restored root access using OTA Root Keeper
6. Used EZ-Recovery 2.2. to flash TWRP recovery in place of the stock recovery
7. Unlocked boot loader using EZ-Unlock 1.2
I may have gotten these steps slightly out of order but this successfully allowed me to install the OTA (with a successful install message too) and got rid of my lock icon!!!
Click to expand...
Click to collapse
Stock rooted MB1 here w/ TWRP. Tried to update earlier and completely soft bricked my phone. Had to do some fancy work to get it back and restore.
Now I tried this process:
1. Lock the boot loader using EZ-Unlock 1.2
2. Using EZ-Recovery 2.2, I flashed the stock recovery
3. Backed up root access using OTA Root Keeper
4. Downloaded and installed the OTA
5. Restored root access using OTA Root Keeper
6. Used EZ-Recovery 2.2. to flash TWRP recovery in place of the stock recovery
7. Unlocked boot loader using EZ-Unlock 1.2
and when I get to the step of actually installing the OTA - it reboots into stock recovery - and about 15 seconds in it fails and shows the android guy on his back. lol
It actually boots back into the phone properly & says that the update failed. Status page shows the baseband got updated, but not the ROM. Any ideas?
thanks
Edit: Bah. It's the stupid 'E: Error in /tmp/sideload/package.zip error.' According to my searches there's no easy fix.
Edit #2: I just wound up dirty flashing the full stock root package from Scott & Beans. That worked.
I'm running the MD3 on the stock ROM and rooted. Now when I originally rooted my phone (using this guide: http://forum.xda-developers.com/showthread.php?t=2046439), I'm fairly confident that I did NOT unlock the bootloader and also installed the CWM Touch recovery. After the process was over I had an unlocked padlock image show up on my phone every time it booted.
Now, I tried to install the new update via OTA (I defrosted all apps I had frozen) and when the phone re-booted to start the update, I received the warning message "System software not authorized by Verizon...." and in the upper left hand corner it says in red, "Secure: Kernel". The phone will continue to boot to this message. When I try to boot into recovery, it goes to this message, not the CWM recovery. The only way to get out of that message is to boot into Odin mode and hit Vol DOWN to cancel.
SO.....what do I need to do in order to install this new update?
UPDATE: I unlocked via EZ Unlock and rebooted into recovery and this time I was able to get into my CWM recovery and updated the zip file posted on another thread in the general forum. All is well now.
Can I upgrade OTA after root but on STOCK ROM?
So if I'm rooted, but still running one of the VERIZON's STOCK ROM,
1. Can I upgrade OTA?
2. Will suck OTA upgrade unroot my phone?
Thanks
mandar_h said:
So if I'm rooted, but still running one of the VERIZON's STOCK ROM,
1. Can I upgrade OTA?
2. Will suck OTA upgrade unroot my phone?
Thanks
Click to expand...
Click to collapse
As of this moment, yes to both. The newest ota is VRBMF1 and you can still root/unlock that version just as easy as any other.
OK, so the MotoDev team advised me to return my phone to stock before installing JB, which will be pushed to my phone tomorrow morning...
What do I need to insure my system won't crash?
I have an unlocked bootloader, and am rooted. I already did a factory reset on my device. Some system apps are gone though, as I have deleted them (mostly Google stuff though, nothing crucial). Will I be good to go? (And yes, I will save the SBF and post it, no worries, have a Dev Host account and will upload).
In order to get official OTA updates from Sprint I've always needed to do 2 things:
-Remove Root (eith via OTA Rootkeeper or stock kernel)
-Flash Stock Recovery (OTA has never worked for me w/ custom recovery)
I'd recommend wiping and flashing both stock images in the thread below via fastboot to avoid bootloops and other hassles.
http://forum.xda-developers.com/showthread.php?t=1856456
hope things go well! :good:
hagforz said:
In order to get official OTA updates from Sprint I've always needed to do 2 things:
-Remove Root (eith via OTA Rootkeeper or stock kernel)
-Flash Stock Recovery (OTA has never worked for me w/ custom recovery)
I'd recommend wiping and flashing both stock images in the thread below via fastboot to avoid bootloops and other hassles.
http://forum.xda-developers.com/showthread.php?t=1856456
hope things go well! :good:
Click to expand...
Click to collapse
Thank you, I will do exactly as you directed...hope things go well also, it's about damn time for JB!
Moto Q stock with Arrrghhh's kernel v.0.10
galacticservant said:
Thank you, I will do exactly as you directed...hope things go well also, it's about damn time for JB!
Moto Q stock with Arrrghhh's kernel v.0.10
Click to expand...
Click to collapse
If you want to grab the update package and save it you should prevent it from being deleted. I know that twrp could not install asa14 OTA update when I got it so it was just hanging there in /cache along with md5 (or sha1, I can't remeber) checksum file.
I do not know if there are other ways of saving the update package nor if devs actually need it. But ASA14 got to my bootloader unlocked, gsm modded, rooted stock rom and after booting to recovery it just stayed there, no install happend (I installed it manually) because twrp did not pass the command properly or what ever the reason.
This update is coming from motorola directly, not sprint, right?
Anyway, perhaps someone can give you more accurate details. I personally would flash twrp and see if updated arrives. Because /cache is wiped by the update installer after installation. All automated process. After device boots to recovery it installs the package, wipes caches and reboots, if I am not mistaken.
I believe for the past updates we had the best luck by reverting the recovery back to stock as well. You have missing APKs that you removed so those will very likely be looked for by the update and will fail the update process if missing.
So if all goes well this should be the bare minimum I'd say for getting the update to work:
MAKE A BACKUP, don't want to have a bricked phone yeah? I mean you could have Jelly Bean on it finally... but still bricked...
Revert the recovery to stock if you installed TWRP or ClockworkMod, adb reboot bootloader | fastboot flash recovery recovery.img
Restore any and all apps you deleted from the stock image, either by restoring fully to stock or putting them back manually, wouldn't hurt to do another update check in the play store for them as well.
Temp unroot with OTA Rootkeeper
Download the update, reboot it, do a song and dance, ???, profit.
Now, you might try to restore root asap, it may or may not work, we won't know till we try.... I'm using Superuser 3.1.3 and on their website it claims its for arm devices 2.0-4.1 so maybe it'll work. Your bootloader should still be unlocked I'd imagine, so you can reflash your custom recovery and make a new backup.