This update came out 3 days ago, myself and about 3 other people i know with the same Verizon LTE Galaxy Tab SCH-I905 all had this update fail. It downloads fine and then reboots only to have it quickly fail and show the Android guy next to a triangle with a ! in it. My tablet is rooted and has the latest LTE kernel by pershoot (which is excellent by the way). Has anyone else had this problem? I have heard a bunch of ideas, some of them are that it is trying to update verizon bloatware that has been deleted possibly? Any ideas or work around would be greatly appreciated.
Thanks
I think you're expert in Galaxy tab 4G LTE...
Can I unlock this device to use by another carrier?(out side U.S)
Can I use 3G sim or 3G network on it?
I'm waiting your answer dude...
alsatea said:
I think you're expert in Galaxy tab 4G LTE...
Can I unlock this device to use by another carrier?(out side U.S)
Can I use 3G sim or 3G network on it?
I'm waiting your answer dude...
Click to expand...
Click to collapse
Huh? Dude this has absolutely nothing to do with my question at all. And im sure you could find this answer elsewhere. My answer though is no, it cannot be unlocked or work on another carrier, it is carrier specific. Now back to the question I asked..... If anyone knows I would be very grateful. On a side note does anyone know where the OTA updates get downloaded to before they are installed? Is there a temp or cache directly i can pull it from?
punkydudey101 said:
This update came out 3 days ago, myself and about 3 other people i know with the same Verizon LTE Galaxy Tab SCH-I905 all had this update fail. It downloads fine and then reboots only to have it quickly fail and show the Android guy next to a triangle with a ! in it. My tablet is rooted and has the latest LTE kernel by pershoot (which is excellent by the way). Has anyone else had this problem? I have heard a bunch of ideas, some of them are that it is trying to update verizon bloatware that has been deleted possibly? Any ideas or work around would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
I'm having the exact same problem you are, I wish I knew the answer. You said you're using the latest kernel from pershoot for the LTE tab????? Do you have a link for it, I can't find it anywhere. TIA
Ya the problem is very frusterating, are you just rooted with no after market kernel? Here is the link the Pershoots kernel, works great!
http://droidbasement.com/galaxy/ker...cm_2636.4_lte-oc-xtra-vfpv3-d16_fp-091311.zip
Any way that you can go back to stock kernel. I have my LTE rooted, but the only thing I've done is the Netflix "patch". I got the EH04 update 2 days ago and it updated without any problems.
I'm assuming the reason why this update fails for everyone is because you are all using CWM, and not the stock recovery. The update needs to have the stock recovery in order to successfully install.
emplox said:
I'm assuming the reason why this update fails for everyone is because you are all using CWM, and not the stock recovery. The update needs to have the stock recovery in order to successfully install.
Click to expand...
Click to collapse
I've been trying to get back to stock since the update failed. I've tried everything I could find online. I'm using a Verizon Galaxy 10.1 same as the original poster with the same exact setup. I found and tried this
http://forum.xda-developers.com/showthread.php?p=12864252#post12864252
by lexriley but no go. I get errors.
If someone could provide a link in the right direction to return to stock recovery or a workaround to get this EH04 patch installed we would all be grateful. Thanks!
emplox said:
I'm assuming the reason why this update fails for everyone is because you are all using CWM, and not the stock recovery. The update needs to have the stock recovery in order to successfully install.
Click to expand...
Click to collapse
Emplox I think you may be right! Thinking about it, it does make complete sense what you are saying. Yes im using CWM. So any ideas how to get rid of it temporarily and get the stock recovery on their so I can get the update?
Thanks again!
jpstiehl said:
I've been trying to get back to stock since the update failed. I've tried everything I could find online. I'm using a Verizon Galaxy 10.1 same as the original poster with the same exact setup. I found and tried this
http://forum.xda-developers.com/showthread.php?p=12864252#post12864252
by lexriley but no go. I get errors.
If someone could provide a link in the right direction to return to stock recovery or a workaround to get this EH04 patch installed we would all be grateful. Thanks!
Click to expand...
Click to collapse
I'm too
I get stock recovery for 4g lte from here http://forum.xda-developers.com/showthread.php?p=16804945#post16804945 ,unroot my lte device with adb command,do wipe data/factory reset,but it still error when i update to eh04.Error i have :
assert failed : apply_patch_check("emmc:/dev/block/mmcblk0p3:4050944.....)
Error in /tmp/sideload/package.zip (status 7)
Can someone help me fix this ? Thanks
Sr for my english
---------- Post added at 10:58 PM ---------- Previous post was at 10:22 PM ----------
eXiled Killah said:
Any way that you can go back to stock kernel. I have my LTE rooted, but the only thing I've done is the Netflix "patch". I got the EH04 update 2 days ago and it updated without any problems.
Click to expand...
Click to collapse
May you backup your recovery mode,kernel and upload for me?Thanks
I did a little looking around. I have a rooted 4G LTE but with the stock ROM.
My update was in /cache and was called 86bb1913cfe9.update.bin. It's a zip file so you can pull it with adb, rename it, then unzip it. The update script looks like it's verifying each file plus the recovery plus the boot to make sure they are the original files. It updates the radio, then patches each file (not just replacing with new versions.) It also deletes some files (that shouldn't have been included in the retail build?), and adds a few new ones. Then it updates recovery and boot.
Here's the first part:
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p4", "/system");
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "samsung/SCH-I905/SCH-I905:3.1/HMJ37/EG01:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "samsung/SCH-I905/SCH-I905:3.1/HMJ37/EH04:user/release-keys");
assert(getprop("ro.product.device") == "SCH-I905" ||
getprop("ro.build.product") == "SCH-I905");
ui_print("Verifying current system...");
show_progress(0.100000, 0);
assert(apply_patch_check("/system/app/AngryGPS.apk", "f83190da0a30b15b3652b84dbffcde99bbdb6dd9", "61b30e6f16feb44aa454f451ce7a998300a1df40"));
set_progress(0.000347);
assert(apply_patch_check("/system/app/AngryGPS.odex", "5225f46ea76215434812deca94de5404370ea2d0", "6ea9c477c5ac7d78076a5b14193d7e8f2a91cc29"));
set_progress(0.000865);
Here's the first part of the update part:
Code:
show_progress(0.800000, 0);
ui_print("Updating CP Modem...");
assert(package_extract_file("modem_delta.bin", "/tmp/modem_delta.bin"),
p4lte_update_cdma_bp("/tmp/modem_delta.bin", "modem_delta.bin"),
delete("/tmp/modem_delta.bin"));
set_progress(0.001027);
ui_print("Removing unneeded files...");
delete("/system/app/VZWAPNLib.apk", "/system/app/VZWAPNService.apk",
"/system/app/VZWSaSSOClient.apk", "/system/bin/ip6tables",
"/system/etc/permissions/vzwapnlib.xml", "/system/lib/libmotricity.so",
"/system/framework/am.jar", "/system/framework/android.policy.jar",
"/system/framework/android.test.runner.jar",
"/system/framework/bmgr.jar", "/system/framework/bouncycastle.jar",
"/system/framework/com.android.location.provider.jar",
"/system/framework/core-junit.jar", "/system/framework/ime.jar",
"/system/framework/input.jar", "/system/framework/javax.obex.jar",
"/system/framework/monkey.jar", "/system/framework/pm.jar",
"/system/framework/sec_feature.jar", "/system/framework/seccamera.jar",
"/system/framework/sechardware.jar",
"/system/framework/secmediarecorder.jar",
"/system/framework/services.jar", "/system/framework/sqlite-jdbc.jar",
"/system/framework/svc.jar", "/system/default.prop",
"/system/recovery.img");
ui_print("Patching system files...");
apply_patch("/system/app/AngryGPS.apk", "-",
f83190da0a30b15b3652b84dbffcde99bbdb6dd9, 67746,
61b30e6f16feb44aa454f451ce7a998300a1df40, package_extract_file("patch/system/app/AngryGPS.apk.p"));
set_progress(0.001372);
apply_patch("/system/app/AngryGPS.odex", "-",
5225f46ea76215434812deca94de5404370ea2d0, 100984,
6ea9c477c5ac7d78076a5b14193d7e8f2a91cc29, package_extract_file("patch/system/app/AngryGPS.odex.p"));
set_progress(0.001886);
apply_patch("/system/app/ApplicationsProvider.apk", "-",
5d9d5fad16ee9fc3c97d97e3857680d287ca4db7, 6112,
0050f2088acd33de7bec7ab06d219bfaac77376c, package_extract_file("patch/system/app/ApplicationsProvider.apk.p"));
set_progress(0.001917);
apply_patch("/system/app/ApplicationsProvider.odex", "-",
f3b58b003aadfb1e930313099e7f41a0c50732ff, 23592,
379aaba5085bfb4ccc76b1fc49de07d5fcebd974, package_extract_file("patch/system/app/ApplicationsProvider.odex.p"));
And here's the end:
Code:
ui_print("Patching LTE image...");
apply_patch("EMMC:/dev/block/mmcblk0p9:10747904:48b8ffc6c66d5e0487ed822b28e144be69e176e1:10747904:cbbc8fb2b864c5513513ccce5aa35bced0e443a3",
"-", cbbc8fb2b864c5513513ccce5aa35bced0e443a3, 10747904,
48b8ffc6c66d5e0487ed822b28e144be69e176e1, package_extract_file("patch/lte.img.p"));
set_progress(0.979318);
ui_print("Patching boot image...");
apply_patch("EMMC:/dev/block/mmcblk0p3:4050944:21bf2e3576ddb89d0eb94ce7103a1e1c9c5c7bfe:4061184:bec5b9c1d11ff42d2a313913c33637c222ee38bf",
"-", bec5b9c1d11ff42d2a313913c33637c222ee38bf, 4061184,
21bf2e3576ddb89d0eb94ce7103a1e1c9c5c7bfe, package_extract_file("patch/boot.img.p"));
set_progress(1.000000);
delete("/system/recovery-from-boot.p",
"/system/etc/install-recovery.sh");
show_progress(0.100000, 10);
ui_print("Unpacking new files...");
package_extract_dir("system", "/system");
ui_print("Unpacking new recovery...");
package_extract_dir("recovery", "/system");
ui_print("Symlinks and permissions...");
If I shouldn't have posted that mods feel free to delete or modify it as necessary.
trb-
emplox said:
I'm assuming the reason why this update fails for everyone is because you are all using CWM, and not the stock recovery. The update needs to have the stock recovery in order to successfully install.
Click to expand...
Click to collapse
Aight here is an update...
I flashed back to stock recovery then wiped it clean. Had to wait until it was 20% charged and then tried the update only to get the Android dude with a yellow triangle and exclamation point. MOFOER! This is just plain ass lame. What does this thing want from me to install the EH04 update! My first born? So currently the only thing that's not stock is the kernel. I'm still using pershoot O.C. kernel. Maybe I need to flash the stock kernel too? This is so dumb. I'll look for an update log tonight to see if I can make sense of this and let you all know. Peace!
---------- Post added at 11:47 PM ---------- Previous post was at 11:33 PM ----------
Hey trbayth, any chance you can pull those updated/patched files so we can push them with adb or help us out in any other way? Thanks for looking into this. I can't find log files or the update on my tab after downloading and having a failed install.
If someone that has already installed the update successfully could simply dump /system, recovery, boot and the kernel and package it up in a tar, we could just odin the update. Matt somebody did that for the EG01 build.
Sent from my SCH-I905 using Tapatalk
i get the update error 3,4 times Error(status 7).After that,i found the way to update successful.
1/I follow this link http://forum.xda-developers.com/showthread.php?t=1195861&page=2 .Get to post #17,download backup of mattj949 and flash with odin.I get the "root" system 4g LTE with CWM mode is 4.0.1.4 but root is not reason for update failed.
2/i continue follow this link http://forum.xda-developers.com/showthread.php?t=1205639&page=2 .Go to post #14,download stockrec.zip put in to the tab on the root of sdcard.Restart tablet,go to recovery mode,move to install zip on sdcard,chose stockrec.zip and go....
3/And i get the update via OTA and successfull update to EH04.
BTW if anyone receive the message update to EH04 and update failed.The update downloaded place in /cache and call 86bb1913cfe9.update.bin..Just rename to update.zip.And go to recovery mode,chose install zip on sdcard,and go(after flash stockrec.zip)
Hope this help for someone.Sr for my english
---------- Post added at 03:18 PM ---------- Previous post was at 02:51 PM ----------
kidserious said:
If someone that has already installed the update successfully could simply dump /system, recovery, boot and the kernel and package it up in a tar, we could just odin the update. Matt somebody did that for the EG01 build.
Sent from my SCH-I905 using Tapatalk
Click to expand...
Click to collapse
Please tell me a way to create a backup system,kernel,recovery file useful with odin.Thanks.
kyo113 said:
i get the update error 3,4 times Error(status 7).After that,i found the way to update successful.
1/I follow this link http://forum.xda-developers.com/showthread.php?t=1195861&page=2 .Get to post #17,download backup of mattj949 and flash with odin.I get the "root" system 4g LTE with CWM mode is 4.0.1.4 but root is not reason for update failed.
2/i continue follow this link http://forum.xda-developers.com/showthread.php?t=1205639&page=2 .Go to post #14,download stockrec.zip put in to the tab on the root of sdcard.Restart tablet,go to recovery mode,move to install zip on sdcard,chose stockrec.zip and go....
3/And i get the update via OTA and successfull update to EH04.
BTW if anyone receive the message update to EH04 and update failed.The update downloaded place in /cache and call 86bb1913cfe9.update.bin..Just rename to update.zip.And go to recovery mode,chose install zip on sdcard,and go(after flash stockrec.zip)
Hope this help for someone.Sr for my english
---------- Post added at 03:18 PM ---------- Previous post was at 02:51 PM ----------
Please tell me a way to create a backup system,kernel,recovery file useful with odin.Thanks.
Click to expand...
Click to collapse
This worked perfectly, thank you very much!
punkydudey101 said:
This worked perfectly, thank you very much!
Click to expand...
Click to collapse
Do you get the triangle on boot logo after update?i have one....is it a bug?how we remove it?
I changed the name in /cache to update.zip and somehow it disappeared after reboot. The tablet did revert to stalk recovery but says it is the most current version which is EGO1. Anyone have 86bb1913cfe9.update.bin?
Thanks
Psean said:
I changed the name in /cache to update.zip and somehow it disappeared after reboot. The tablet did revert to stalk recovery but says it is the most current version which is EGO1. Anyone have 86bb1913cfe9.update.bin?
Thanks
Click to expand...
Click to collapse
Yes, when I downloaded it the last time, I pulled it from my tab to my PC. I'll dropbox it for you when I get home.
Sent from my SCH-I500 using Tapatalk
Psean said:
I changed the name in /cache to update.zip and somehow it disappeared after reboot. The tablet did revert to stalk recovery but says it is the most current version which is EGO1. Anyone have 86bb1913cfe9.update.bin?
Thanks
Click to expand...
Click to collapse
For those who need the update file or can't get it to redownload, here you go: http://dl.dropbox.com/u/20070269/86bb1913cfe9.update.bin place this file in /cache and hopefully the tab will recognize it and prompt you to restart and install. I haven't tried this so let me know how it goes.
Psean said:
I changed the name in /cache to update.zip and somehow it disappeared after reboot. The tablet did revert to stalk recovery but says it is the most current version which is EGO1. Anyone have 86bb1913cfe9.update.bin?
Thanks
Click to expand...
Click to collapse
you must copy your update.zip and paste in /sdcard.then you will see it in recovery mode.
Ps: anyone have the triangle on boot logo samsung tab after update to eh04?please help me to fix this issue.thanks
Sent from my SCH-I905 using XDA App
Related
Earlier this week I bought a Samsung Galaxy S III for ATT. It already had Ice Cream Sandwich 4.0.4 on it and so I rooted it. Well the day after rooting it I get a message in my notification bar that there's a new software update available from ATT. Am I safe to do this update since my phone is rooted? I doubt the update is anything major, but does that make a difference?
fa7592 said:
Earlier this week I bought a Samsung Galaxy S III for ATT. It already had Ice Cream Sandwich 4.0.4 on it and so I rooted it. Well the day after rooting it I get a message in my notification bar that there's a new software update available from ATT. Am I safe to do this update since my phone is rooted? I doubt the update is anything major, but does that make a difference?
Click to expand...
Click to collapse
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1768826
You can apply the update if you're rooted using the method in that thread or by installing OTA Rootkeeper before you apply the OTA. If you apply the OTA directly, you'll need to go back to stock recovery, then install CWM again when it's done. You'll also probably want to backup the Google Search widget (I forget the exact .apk -- search the forums) and restore it after to avoid losing Universal Search.
But the easiest way is to just flash the zip in the thread above through your CWM recovery.
As for the contents of the OTA: It updates the kernel, bootloader, lots of applications, some system libraries, wpa_supplicant and it's firmware (I think that's for wifi), and the modem. I've got it installed and didn't notice a huge difference, but you might. The thread above also includes separate flash files for the kernel and modem in case you want to try just those.
Good luck!
drothenberger said:
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1768826
You can apply the update if you're rooted using the method in that thread or by installing OTA Rootkeeper before you apply the OTA. If you apply the OTA directly, you'll need to go back to stock recovery, then install CWM again when it's done. You'll also probably want to backup the Google Search widget (I forget the exact .apk -- search the forums) and restore it after to avoid losing Universal Search.
But the easiest way is to just flash the zip in the thread above through your CWM recovery.
As for the contents of the OTA: It updates the kernel, bootloader, lots of applications, some system libraries, wpa_supplicant and it's firmware (I think that's for wifi), and the modem. I've got it installed and didn't notice a huge difference, but you might. The thread above also includes separate flash files for the kernel and modem in case you want to try just those.
Good luck!
Click to expand...
Click to collapse
Thank you very much. I appreciate the quick response and the help.
drothenberger said:
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1768826
You can apply the update if you're rooted using the method in that thread or by installing OTA Rootkeeper before you apply the OTA. If you apply the OTA directly, you'll need to go back to stock recovery, then install CWM again when it's done. You'll also probably want to backup the Google Search widget (I forget the exact .apk -- search the forums) and restore it after to avoid losing Universal Search.
But the easiest way is to just flash the zip in the thread above through your CWM recovery.
As for the contents of the OTA: It updates the kernel, bootloader, lots of applications, some system libraries, wpa_supplicant and it's firmware (I think that's for wifi), and the modem. I've got it installed and didn't notice a huge difference, but you might. The thread above also includes separate flash files for the kernel and modem in case you want to try just those.
Good luck!
Click to expand...
Click to collapse
would I just have to reflash the kernel I'm on now if I were to update that way?
Sent from my SAMSUNG-SGH-I747 using xda premium
jrbaker624 said:
would I just have to reflash the kernel I'm on now if I were to update that way?
Click to expand...
Click to collapse
No. There's a zip file there with the OTA but with the bootloader and kernel updates removed. You can flash that to keep your kernel. There's another zip file there with just the bootloader if you want to update that, too. Just flash both (No Bootloader No Kernel, the Bootloader).
drothenberger said:
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1768826
You can apply the update if you're rooted using the method in that thread or by installing OTA Rootkeeper before you apply the OTA. If you apply the OTA directly, you'll need to go back to stock recovery, then install CWM again when it's done. You'll also probably want to backup the Google Search widget (I forget the exact .apk -- search the forums) and restore it after to avoid losing Universal Search.
But the easiest way is to just flash the zip in the thread above through your CWM recovery.
As for the contents of the OTA: It updates the kernel, bootloader, lots of applications, some system libraries, wpa_supplicant and it's firmware (I think that's for wifi), and the modem. I've got it installed and didn't notice a huge difference, but you might. The thread above also includes separate flash files for the kernel and modem in case you want to try just those.
Good luck!
Click to expand...
Click to collapse
UPDATE:
okay so I followed the steps in the thread you provided, and when I go to flash the update zip in recovery mode, i get an error and it aborts the installation. Heres the error:
assert failed: getprop("ro.product.device") =="
d2att" | | getprop("ro.build.product") =="
d2att"
E:Error in /emmc/I747UCALG1_OTA.zip
(status 0)
Installation aborted.
Any idea as to what this may mean?
I am also getting same error I was on team epics recovery then saw it wouldn't work for that recovery so I flashed a new recovery and still get the same error.
Tried flashing the no boot loader zip. And the no boot loader and no kernel zip
Sent from my SAMSUNG-SGH-I747 using xda premium
fa7592 said:
assert failed: getprop("ro.product.device") =="
d2att" | | getprop("ro.build.product") =="
d2att"
E:Error in /emmc/I747UCALG1_OTA.zip
(status 0)
Installation aborted.
Any idea as to what this may mean?
Click to expand...
Click to collapse
It means you're using the Team Epic recovery and not the one from clockworkmod.com. Try installing the 5.8.4.5 version of clockworkmod.com recovery from here: http://forum.xda-developers.com/showthread.php?p=28612095. That link has zip files you can flash from your current CWM recovery.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
drothenberger said:
It means you're using the Team Epic recovery and not the one from clockworkmod.com. Try installing the 5.8.4.5 version of clockworkmod.com recovery from here: http://forum.xda-developers.com/showthread.php?p=28612095. That link has zip files you can flash from your current CWM recovery.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Oh I see. So should I just download that file and replace the CWM zip file thats already on my phone. Or do I have to do something in Odin again?
fa7592 said:
Oh I see. So should I just download that file and replace the CWM zip file thats already on my phone. Or do I have to do something in Odin again?
Click to expand...
Click to collapse
Download OTA Rootkeeper from the play store, save root, then install the OTA. Reboot and OTA rootkeeper restore root.
drothenberger said:
It means you're using the Team Epic recovery and not the one from clockworkmod.com. Try installing the 5.8.4.5 version of clockworkmod.com recovery from here: http://forum.xda-developers.com/showthread.php?p=28612095. That link has zip files you can flash from your current CWM recovery.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Downloaded that one instead of the third one you had linked all together and it worked. Thank you
Sent from my SAMSUNG-SGH-I747 using xda premium
Download the zip file for recovery, apply it using your current recovery, reboot recovery from the advanced menu, then apply the OTA zip.
Or use OTA Rootkeeper as also suggested. I prefer my OTA zip personally, but either way will work.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
drothenberger said:
Download the zip file for recovery, apply it using your current recovery, reboot recovery from the advanced menu, then apply the OTA zip.
Or use OTA Rootkeeper as also suggested. I prefer my OTA zip personally, but either way will work.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Okay. Wow. So after a lot of trial and error (i think i bricked my phone somehow in the middle of everything, but its okay I found out how to fix it) I have managed to get that update applied. Theres one last problem though. I applied the update by flashing it in CWM recovery. I know I have the update installed because now under baseband version instead of saying I747UCLEM it says I747UCLG1. And Ive tested the google search widget and it's still giving me local search results so that's all good. The problem is that in my notification bar the ATT software update notification is still there. I have currently postponed it for 8 hours, but its still there and the only button I'm able to press is the continue button. I dont want to press this because im afraid the normal ATT update will install over the modded one and the google search widget will mess up and stop displaying the local search results. Also under about device, when I click software update the option for "check for update" is grayed out. Any thoughts on this?
fa7592 said:
Okay. Wow. So after a lot of trial and error (i think i bricked my phone somehow in the middle of everything, but its okay I found out how to fix it) I have managed to get that update applied. Theres one last problem though. I applied the update by flashing it in CWM recovery. I know I have the update installed because now under baseband version instead of saying I747UCLEM it says I747UCLG1. And Ive tested the google search widget and it's still giving me local search results so that's all good. The problem is that in my notification bar the ATT software update notification is still there. I have currently postponed it for 8 hours, but its still there and the only button I'm able to press is the continue button. I dont want to press this because im afraid the normal ATT update will install over the modded one and the google search widget will mess up and stop displaying the local search results. Also under about device, when I click software update the option for "check for update" is grayed out. Any thoughts on this?
Click to expand...
Click to collapse
What does it say under build number? IMM76D.I747UCALG1? If not, then somehow you only got the modem installed.
I have the update applied, but I had frozen AT&T Software Update in Titanium Backup, so I wasn't getting the notification. I just tried unfreezing it and checking for an update and was surprised when it said there was one! I postponed it, did a Wipe Data for AT&T Software Update in TiBu, then rebooted and now all is well. When I check for an update now it says I'm up-to-date. So try that.
drothenberger said:
What does it say under build number? IMM76D.I747UCALG1? If not, then somehow you only got the modem installed.
I have the update applied, but I had frozen AT&T Software Update in Titanium Backup, so I wasn't getting the notification. I just tried unfreezing it and checking for an update and was surprised when it said there was one! I postponed it, did a Wipe Data for AT&T Software Update in TiBu, then rebooted and now all is well. When I check for an update now it says I'm up-to-date. So try that.
Click to expand...
Click to collapse
Yeah, under build number it says IMM76D.I747UCALG1.
I'll give what you said a shot and see what happens. But one thing first, what's TiBu? And also, I'm about to flash a custom ROM on my phone, so is the update issue something that can wait, or should I take care of that before I put on a custom ROM?
fa7592 said:
Yeah, under build number it says IMM76D.I747UCALG1.
I'll give what you said a shot and see what happens. But one thing first, what's TiBu? And also, I'm about to flash a custom ROM on my phone, so is the update issue something that can wait, or should I take care of that before I put on a custom ROM?
Click to expand...
Click to collapse
Sorry, "TiBu" is my shorthand for Titanium Backup. Chances are any custom ROM you install will remove the AT&T Software Update application, so you won't need to worry about this anymore.
drothenberger said:
Sorry, "TiBu" is my shorthand for Titanium Backup. Chances are any custom ROM you install will remove the AT&T Software Update application, so you won't need to worry about this anymore.
Click to expand...
Click to collapse
Oh okay. In that case I'll go ahead and put in that custom ROM and report back when everything is done. Again, thanks for the help and patience.
Okay, so I have applied the ROM and everything is good! Well for the most part. At times when there isn't a WiFi signal available and it has to use mobile data, the 4G LTE doesn't work. It will connect to HSPA or 3G. And it happens in areas I know has 4G LTE available. But other than that everything seems to be working good. Just thought I'd share in case anyone was thinking of using the AOKP ROM.
http://phandroid.com/2012/08/13/t-mobile-springboard-getting-android-4-0-4-this-wednesday/
Sent from my HUAWEI OsiMood MediaPad using Tapatalk 2
How about mediapad?
Is it has a ics 4.0.4 too?
ZEII said:
How about mediapad?
Is it has a ics 4.0.4 too?
Click to expand...
Click to collapse
Huawei had released ICS for media pad a while ago. Check the development section.
Sent from my HUAWEI OsiMood MediaPad using Tapatalk 2
but only 4.0.3, not 4.0.4
441Excelsior said:
but only 4.0.3, not 4.0.4
Click to expand...
Click to collapse
True.
Sent from my HUAWEI OsiMood MediaPad using Tapatalk 2
From tmonews, it's 4.0.3 and not 4.0.4. I think 4.0.3 is the correct one. Anyway, we will know it soon enough.
Would somebody be so kind and try to keep the update.zip for those of us who have problems getting back to stock?
ICS is now released and my Springboard is downloading the update!
Here is the ZIP file update for anyone that want to grab it to extract and play...
http://www.gamefront.com/files/22180781/Springboard-ics-update.zip
Update:
OTA failed for me right away. I got the update to manually install with the following steps:
1) Created a folder on root of my SDcard, dload
2) Copied the update ZIP file above into dload and renamed it to update.zip
3) Created a zero length file unlmt.cfg in the dload folder
Rebooted with normal VOL+ key held down to start a SD install.
Note: After upgrade completed the Launcher would not start and kept repeating "Unfortunately Launcher has stopped".
To fix, click Ok and quickly bring up the Statusbar menu by swiping it at the bottom of the screen and click on the clock/date, next enter Settings->Apps->All->Launcher, then clear data.
Looks like a full update So everyone who flashed the Springboard to MediaPad could go back now, if wanted.
Best feature in this update for me is, the startup T-mobile sound is about 1/4 the old volume!
:fingers-crossed:
Does this T-mobile ICS seem to support the phone function?
vicfuze said:
ICS is now released and my Springboard is downloading the update!
.......
Click to expand...
Click to collapse
Thanks for the info and link vicfuze!
Update worked great, and I got it rooted without problems.
Have been eagerly awaiting this.
vicfuze said:
Here is the ZIP file update for anyone that want to grab it to extract and play...
Click to expand...
Click to collapse
Much appreciated but it would have been even nicer if you could have posted the original URL from Google
I'm downloading it now. I think I might try to flash just the radio files and see if that improves things for me. I'm otherwise satisfied with the international ICS firmware.
---------- Post added at 10:36 PM ---------- Previous post was at 10:35 PM ----------
vicfuze said:
Best feature in this update for me is, the startup T-mobile sound is about 1/4 the old volume!
:fingers-crossed:
Click to expand...
Click to collapse
You can remove that sound with root. I think it's:
/cust/tmobile/us/media/animationsounds/bootSound.ogg
Rename or delete it.
---------- Post added at 10:51 PM ---------- Previous post was at 10:36 PM ----------
Question: What's the baseband version post-update?
Hi,
does anybody know, if I can run this update on the German Version of the Mediapad or shall I better refrain from trying?
Thank you
Made some Mirrors...
Mirror 1
Mirror 2
Happy Flashing !
springboard root
Does the springboard have to be rooted before the update to get root? I used the update but it is not rooted now nor was it before and I would like to get root.
whgarner said:
Does the springboard have to be rooted before the update to get root? I used the update but it is not rooted now nor was it before and I would like to get root.
Click to expand...
Click to collapse
Nope the update is a full wipe. So you will need to root after the update.
http://www.modaco.com/topic/354579-...-mediapad-t-mobile-springboard-orange-tahiti/
nightanole said:
Nope the update is a full wipe. So you will need to root after the update.
http://www.modaco.com/topic/354579-...-mediapad-t-mobile-springboard-orange-tahiti/
Click to expand...
Click to collapse
Here is a mirror of the SU installer pkg from that post for US folks.
http://www.gamefront.com/files/22185176/Huawei+MediaPad+ROOT+ICS+Android+4.0.x.rar
vicfuze said:
Here is a mirror of the SU installer pkg from that post for US folks.
http://www.gamefront.com/files/22185176/Huawei+MediaPad+ROOT+ICS+Android+4.0.x.rar
Click to expand...
Click to collapse
Have you actually got this root method to work for the non-Mediapad Springboard with the T-Mobile firmware? I run Linux and so the command script in this package will not exactly execute on my machine. I tried manually sequentially entering the adb commands contained in the command script, and got stuck at a 'permission denied' error within the first several commands. If this does work for the Springboard, and not just the Mediapad, then there might be something about the embedded windows drivers and software for the device that allows it to work...because I sure can't get it to fly on Ubuntu.
xdajunkman said:
Have you actually got this root method to work for the non-Mediapad Springboard with the T-Mobile firmware? I run Linux and so the command script in this package will not exactly execute on my machine. I tried manually sequentially entering the adb commands contained in the command script, and got stuck at a 'permission denied' error within the first several commands. If this does work for the Springboard, and not just the Mediapad, then there might be something about the embedded windows drivers and software for the device that allows it to work...because I sure can't get it to fly on Ubuntu.
Click to expand...
Click to collapse
I actually used the below method to install root again on ICS. I believe there is a fastboot for Linux if you cannot find a DOS/Windows machine.
Only issue I was my Springboard was recovery booting off of "recovery2" partition so I needed to flashboot that partition to get CWM recovery to boot. Since the Official Springboard ICS zip package contains the stock recovery.img file you really can flash both recovery/recovery2 partitions and revert back later if needed.
http://forum.xda-developers.com/showthread.php?t=1850367
And to clarify, for booting into Fastboot, you hold the power button and the VOL closest to it down at the same time.
To boot recovery/CWM hold the power button and VOL key furthur away from the power button (its VOL Up) for some reason.
Also, don't try to use the Touch recovery (TWM) package, it froze up on me when trying to run the root zip installer, but luckily reverting to the basic CWM recovery, I was able to re-install and fix my boot looping.
I have a Singapore T6UL running on 4.3 S-OFF, Bootloader unlocked, rooted. When the 4.4.2 OTA came, I tried installing using the stock recovery. But it is complaining about HtcSoundRecorder.apk and Weixin.apk and abort the installation.Problem is HTCSoundRecorder is removed automatically when I unlocked the bootloader. Can anyone help to provide me with these 2 apk? :crying:
Here is the soundrecorder - http://forum.xda-developers.com/showpost.php?p=48759137&postcount=2
---------- Post added at 10:52 PM ---------- Previous post was at 10:50 PM ----------
lowtengbeng said:
I have a Singapore T6UL running on 4.3 S-OFF, Bootloader unlocked, rooted. When the 4.4.2 OTA came, I tried installing using the stock recovery. But it is complaining about HtcSoundRecorder.apk and Weixin.apk and abort the installation.Problem is HTCSoundRecorder is removed automatically when I unlocked the bootloader. Can anyone help to provide me with these 2 apk? :crying:
Click to expand...
Click to collapse
Do you have a screen shot for us ? that sounds pretty interesting to look at.
I have never heard of anything beibg removed with unlocking thr bootloader. It is possible unlocking the bootloader makes some apps not function properly (or even show up) but the apk should definitely still be there.
I tried using the HtcSoundRecorder.apk that pradeepvizz provides, Still same issue. Complaining about "\data\preload\HtcSoundRecorder.apk has unexpected contents Installation aborted" Tried with the apk extracted from a couple of roms in the dev section. Same issue,
The original doesn't have the "\data\preload" directory. So I thought that creating that directory and copying in the apk should work but it doesn't.
It seems that the \data\preload folder is removed after I unlocked the bootloader via htcdev...
Any ideas?
I am on software version: 1.23.707.1 Any kinds soul have the backup for this version? :highfive:
Jiggity Janx said:
I have never heard of anything beibg removed with unlocking thr bootloader.
Click to expand...
Click to collapse
lowtengbeng said:
It seems that the \data\preload folder is removed after I unlocked the bootloader via htcdev...
Click to expand...
Click to collapse
I do still learn something new every day...
---------- Post added at 11:04 PM ---------- Previous post was at 10:50 PM ----------
So I thought we had a preload partition vice the preload folder? Unless I am just thinking of my samsung devices. Cant look up the partitions right at this second but that would make sense to me (and why I thought nothing was deleted from system or data).
Trying to update from 1.23.707.1 to 2.61.707.1
Tried factory reset. Still doesn't bring back that folder for me...
Funny for HTC to remove those stuff after unlocking bootloader.
lowtengbeng said:
Trying to update from 1.23.707.1 to 2.61.707.1
Tried factory reset. Still doesn't bring back that folder for me...
Funny for HTC to remove those stuff after unlocking bootloader.
Click to expand...
Click to collapse
Did you miss a OTA in the middle like 1.54 or something?
pradeepvizz said:
Did you miss a OTA in the middle like 1.54 or something?
Click to expand...
Click to collapse
I don't think so. I didn't get any software update prompt except for the latest 4.2.2 update since I bought the Max on day 1 launch in Singapore.
Some options that I am thinking:
Option 1: Edit the ota update script to remove checks for sound recorder and weixin. This will make the zip to be unsigned and I am thinking whether this can be flashed using TWRP or CWM as stock recovery shouldn't allow it to be flashed due to unsigned package.
Option 2: Lock the bootloader. Factory reset. I am wondering if this can bring back to 100% stock state. I am from the Windows CE world and this works on CE as it will reload everything from the ROM image.
lowtengbeng said:
I tried using the HtcSoundRecorder.apk that pradeepvizz provides, Still same issue. Complaining about "\data\preload\HtcSoundRecorder.apk has unexpected contents Installation aborted" Tried with the apk extracted from a couple of roms in the dev section. Same issue,
The original doesn't have the "\data\preload" directory. So I thought that creating that directory and copying in the apk should work but it doesn't.
It seems that the \data\preload folder is removed after I unlocked the bootloader via htcdev...
Any ideas?
Click to expand...
Click to collapse
did you try to extract the apk from virtuous ROM? that was only the ROM which i remember to have these files. the Apk files that i had linked were collected it from various posts on XDA, so that could be something causing the mismatch
I am not sure if CWM/TWRP can flash a edited zip using "install update.zip" but i think you can do that via adb sideload in TWRP/CWM.
Do you have the OTA link or the file, can you please upload so that the experts here can use it / help you with it?
pradeepvizz said:
did you try to extract the apk from virtuous ROM? that was only the ROM which i remember to have these files. the Apk files that i had linked were collected it from various posts on XDA, so that could be something causing the mismatch
I am not sure if CWM/TWRP can flash a edited zip using "install update.zip" but i think you can do that via adb sideload in TWRP/CWM.
Do you have the OTA link or the file, can you please upload so that the experts here can use it / help you with it?
Click to expand...
Click to collapse
Yep. I tried with the apk from virtuous ROM having the same issue. I checked the sha-1 of 5 copies of the apk from different sources and none of them has the matching sha-1 that the update script is asking for.
Can you share what is the differences between flashing via adb sideload and "install update.zip"?
I will try to upload the ota file when I get back from work tonight, :highfive:
HTC is spending theiir resources at the wrong place!
lowtengbeng said:
Yep. I tried with the apk from virtuous ROM having the same issue. I checked the sha-1 of 5 copies of the apk from different sources and none of them has the matching sha-1 that the update script is asking for.
Can you share what is the differences between flashing via adb sideload and "install update.zip"?
I will try to upload the ota file when I get back from work tonight, :highfive:
HTC is spending theiir resources at the wrong place!
Click to expand...
Click to collapse
i understand your frustration, but i believe this is part of Google's security improvement in the OTA process.
i am not sure on the difference between adb sideload and update.zip, just did a little bit of Google and found that TWRP may work with the OTA - http://forum.xda-developers.com/showthread.php?t=2573565
Hope something works out.
I just extracted this apk from OTA_T6_UL_JB43_SENSE55_HTC_Europe_1.54.401.1-1.19.401.2_release_341451bchda87kitj44eh9.zip
This is the EURO OTA from 1.19 to 1.54, not sure if that will help you.
i checked the update-script on this OTA and it seemed to all good and should work with CWM / TWRP if all the executables are there..
Hope for the best!
Jiggity Janx said:
So I thought we had a preload partition vice the preload folder?
Click to expand...
Click to collapse
Has anyone looked at this possibility? I thought someone posted all the partitions for the Max but havent come across it yet to check.
pradeepvizz said:
I just extracted this apk from OTA_T6_UL_JB43_SENSE55_HTC_Europe_1.54.401.1-1.19.401.2_release_341451bchda87kitj44eh9.zip
This is the EURO OTA from 1.19 to 1.54, not sure if that will help you.
i checked the update-script on this OTA and it seemed to all good and should work with CWM / TWRP if all the executables are there..
Hope for the best!
Click to expand...
Click to collapse
Thanks for your help. Tried this same issue. :crying:
Later going to try out the lock bootloader and factory reset method. Will keep the progress updated.
This is the ota that I am trying to flash.
https://drive.google.com/file/d/0BwoPVL5J45ITdjUxcXY2Q3FNRk0/edit?usp=sharing
I confirmed that locking bootloader + factory reset does not bring back the \data\preload folder and contents. HTC post load it on top of the rom.
lowtengbeng said:
I confirmed that locking bootloader + factory reset does not bring back the \data\preload folder and contents. HTC post load it on top of the rom.
Click to expand...
Click to collapse
Well, if you are able to find an RUU for your phone, that can be the only clean way to do it.
you can edit the script and removed the lines which specifies soundrecorder apk and then flash it with TWRP / CWM.
pradeepvizz said:
Well, if you are able to find an RUU for your phone, that can be the only clean way to do it.
you can edit the script and removed the lines which specifies soundrecorder apk and then flash it with TWRP / CWM.
Click to expand...
Click to collapse
There is no RUU released for this version yet.
I tried the script editing method and use trwp n cwm. Both failed. Trwp gave an update binary error
So out of curiosity I went to the ZTE USA website and checked when the next batch of Axon 7's would ship as I wanted to buy another one (don't judge) and I go down to Support, Software updates, and I see this(attached):
Is this the stock image that ZTE said they would post? It sure looks like it as its almost 2GB in size
Link: https://www.zteusa.com/axon-7
Thanks for the heads-up. Interesting that they would post an image for B20, not one of a later version.
xtermmin said:
Thanks for the heads-up. Interesting that they would post an image for B20, not one of a later version.
Click to expand...
Click to collapse
What's interesting is that they haven't announced it yet
This looks like the factory image of the B20 pre-bootloader. I'm downloading the zip now, so we'll know more after analysts. So much about getting B27 or B29 as factory, but makes sense since that's where the sig change happened. And it specifically mentions it as image for fixing OTA failures because of B20_Boot OTA
It could be what we have been hoping for - at least that is a factory image. We can always use their OTA system to update from there
---------- Post added at 09:26 PM ---------- Previous post was at 08:56 PM ----------
DrakenFX - check this out here. I just downloaded it and took a look at the updater script in it. This may help with an instruction set for turning future OTA updates into TWRP flashable zips.
we need to get this updated here:
http://forum.xda-developers.com/axon-7/development/axon-7-chinese-stock-roms-t3436817
Well what do you know its announced: https://community.zteusa.com/thread/13133
bkores said:
Well what do you know its announced: https://community.zteusa.com/thread/13133
Click to expand...
Click to collapse
So with this image, how would you flash it to a bricked phone? Do you have to have access to recovery to use the file as posted?
Nice find @bkores , posted on the 10/26 .....still this can be very helpful
imp3r10 said:
So with this image, how would you flash it to a bricked phone? Do you have to have access to recovery to use the file as posted?
Click to expand...
Click to collapse
I guess you do as you have to update from the sd card. I don't know why they couldn't have made it fastboot flashable but you should be able to flash the boot and recovery inside the zip with fastboot. As for the system I think you can convert the system.new.dat to system.img with some program and then flash. Someone feel free to correct me on this.
Can devs start "cooking" this? Removing stock apps etc etc?
bkores said:
I guess you do as you have to update from the sd card. I don't know why they couldn't have made it fastboot flashable but you should be able to flash the boot and recovery inside the zip with fastboot. As for the system I think you can convert the system.new.dat to system.img with some program and then flash. Someone feel free to correct me on this.
Click to expand...
Click to collapse
This is basically a full (not-OTA) update file for B20 version. It is really only good for downgrades to fix soft brick where your recovery is still accessible or to get OTAs. It will not help with bricks where phone won't boot past ZTE logo or into fastboot. It will also not help with stock mods since zip file is signed. And it cannot be flashed via EDL or DFU mode. I hope this is not the thing they were talking about when they posted that meme with brick wall and stock market recovery.
For fastboot restore, we would need new fastboot image, since i think there is a flash (or pull) limit on file size in the current one around 500MB or so IIRC
---------- Post added at 03:49 PM ---------- Previous post was at 03:41 PM ----------
nsane said:
Can devs start "cooking" this? Removing stock apps etc etc?
Click to expand...
Click to collapse
Since this is a signed zip, there is no modifying it. Flashing modded rom would still require TWRP and could already be done since we have full /system dumps. And to use this to save you from bad flash, you will need to have access to recovery. TWRP could flash it i guess, but if you are in bootloader loop then not much help
This will remove the unlocked bootloader from your device at this time
Click to expand...
Click to collapse
I'm guessing this is because it replaces the emmc_appsboot.mbn / aboot file? Wonder if one can just delete that line from the flashing script to keep it unlocked.
peramikic said:
This is basically a full (not-OTA) update file for B20 version. It is really only good for downgrades to fix soft brick where your recovery is still accessible or to get OTAs. It will not help with bricks where phone won't boot past ZTE logo or into fastboot. It will also not help with stock mods since zip file is signed. And it cannot be flashed via EDL or DFU mode. I hope this is not the thing they were talking about when they posted that meme with brick wall and stock market recovery.
For fastboot restore, we would need new fastboot image, since i think there is a flash (or pull) limit on file size in the current one around 500MB or so IIRC
---------- Post added at 03:49 PM ---------- Previous post was at 03:41 PM ----------
Since this is a signed zip, there is no modifying it. Flashing modded rom would still require TWRP and could already be done since we have full /system dumps. And to use this to save you from bad flash, you will need to have access to recovery. TWRP could flash it i guess, but if you are in bootloader loop then not much help
Click to expand...
Click to collapse
If you are stuck on the ZTE logo on a bootloop, couldn't you use tenfar's tool to flash stock recovery and then use this full image to flash stock B20? It does have a boot.img in it that it installs during this process.
peramikic said:
This is basically a full (not-OTA) update file for B20 version. It is really only good for downgrades to fix soft brick where your recovery is still accessible or to get OTAs. It will not help with bricks where phone won't boot past ZTE logo or into fastboot. It will also not help with stock mods since zip file is signed. And it cannot be flashed via EDL or DFU mode. I hope this is not the thing they were talking about when they posted that meme with brick wall and stock market recovery.
For fastboot restore, we would need new fastboot image, since i think there is a flash (or pull) limit on file size in the current one around 500MB or so IIRC
---------- Post added at 03:49 PM ---------- Previous post was at 03:41 PM ----------
Since this is a signed zip, there is no modifying it. Flashing modded rom would still require TWRP and could already be done since we have full /system dumps. And to use this to save you from bad flash, you will need to have access to recovery. TWRP could flash it i guess, but if you are in bootloader loop then not much help
Click to expand...
Click to collapse
I am bootloader unlock and have TWRP.
I hope that Devs start "cooking" stock ROMS. Taking out system apps. Bloat etc etc
Kernel development would also be nice
*fingers crossed*
I'm really happy that they did something, but why couldn't they have just compressed the boot, recovery, and system img files into a tar file like Google does with their Nexus/Pixel devices? That way we would've been able to flash them in fastboot mode which could've fixed almost any brick with the exception of EDL/DFU mode in which case we could have used tenfar's tool.
If you remove this from the updater-script inside the update.zip, it is even flashable with TWRP takes some time to flash but it works!
Code:
getprop("ro.product.device") == "ailsa_ii" || abort("This package is for \"ailsa_ii\" devices; this is a \"" + getprop("ro.product.device") + "\".");
assert(getprop("ro.product.name") == "P996A01");
ui_print("Target: ZTE/P996A01/ailsa_ii:6.0.1/MMB29M/20160707.171254:user/release-keys");
show_progress(0.850000, 180);
i believe i mention this somewhere, been crazy busy for me today
* You can either Flashed using TWRP or Install using Stock System Update app or Install using Stock recovery.
but that B20 update.zip will get you to Complete B20 software.
Click to expand...
Click to collapse
beside that here are a few good point of what is going to happen :
-However you will not be able to update to newer builds just yet.
-SD card update will erase everything on your device. (but i'm sure External Storage (SDCard) is safe )
-We recommend only users with advanced skills use this file.
Click to expand...
Click to collapse
so anyone who want to use that file need to take that in consideration.
DrakenFX said:
i believe i mention this somewhere, been crazy busy for me today
beside that here are a few good point of what is going to happen :
so anyone who want to use that file need to take that in consideration.
Click to expand...
Click to collapse
You can just remove the format line inside the updater-script to keep your data
bkores said:
You can just remove the format line inside the updater-script to keep your data
Click to expand...
Click to collapse
LoL, just notice that line ....haven't had time to bother and check the file , but yeah just need to remove
Code:
format("ext4", "EMMC", "/dev/block/bootdevice/by-name/userdata", "0", "/data");
but still, internal storage will be is safe but you'll still need to wipe data and reinstall app (Encryption thing)
Hey, Here is a link to the Android Oreo OTA
https://samsung.firmware.science/download?url=48993/1488/SS-N950USQS2BQK2-to-U2CQL1-UP
https://drive.google.com/open?id=1xTtsn6gcg4JEX2dYKPiXTWVhPiGPzIBn
Before you can do this build you will need to be on 2BQK2, so to get to that you need this build: https://samsung.firmware.science/download?url=48993/1488/SS-N950USQU2BQJA-to-S2BQK2-UP
ODIN for BQK2: https://androidfilehost.com/?fid=889964283620771190
this file for BQJA is on SamMobile, SamFirm, and Updato. These are OTA updates besides the flashing required in that.
UPDATE! New build has been released. It is CQL7. To get to that, flash BQK2 with Odin (linked above) then OTA from BQK2 to BQL5 then another OTA from BQL5 to CQL7.
BQK2 to BQL5: https://samsung.firmware.science/download?url=48993/1488/SS-N950USQS2BQK2-to-S2BQL5-UP
BQL5 to CQLB: https://samsung.firmware.science/download?url=48993/1488/SS-N950USQS2BQL5-to-U2CQLB-UP
BRA8 to CRB8 https://samsung.firmware.science/download?url=48993/1488/SS-N950USQS3BRA8-to-U3CRB8-UP
THIS WILL UPDATE YOUR BOOTLOADER TO V3, YOU CAN NOT DOWNGRADE
BQL5 Odin: https://samsung-firmware.org/download/Galaxy__Note8__/c7o0/VZW/N950USQS2BQL5/N950UOYN2BQL5/
Oh just a side note, this may be unstable and crash, you have been warned.
This is a discord server with things as they come out. discord.gg/4uxusu8
thanks to thesbros for making the website
(https://i.imgur.com/oBT3bTA.jpg)
(https://i.imgur.com/f8CU1IP.jpg)
mweinbach said:
Hey, Here is a link to the Android Oreo OTA
https://samsung.firmware.science/download?url=48993/1488/SS-N950USQS2BQK2-to-U2CQL1-UP
Before you can do this build you will need to be on 2BQK2, so to get to that you need this build: https://samsung.firmware.science/download?url=48993/1488/SS-N950USQU2BQJA-to-S2BQK2-UP
ODIN for BQK2: https://drive.google.com/uc?id=19gW_CxUf2HdL4UYyxTkyOnBY8cluRIVS&export=download
this file for BQJA is on SamMobile, SamFirm, and Updato. These are OTA updates besides the flashing required in that.
I currently have an S8 on the Oreo beta and will be buying a Note8 this weekend because of this. I AM SO EXCITED!
Oh just a side note, this may be unstable and crash, you have been warned.
Click to expand...
Click to collapse
How does one go about flashing this? I'm currently on Sprints latest update
mweinbach said:
Hey, Here is a link to the Android Oreo OTA
https://samsung.firmware.science/download?url=48993/1488/SS-N950USQS2BQK2-to-U2CQL1-UP
Before you can do this build you will need to be on 2BQK2, so to get to that you need this build: https://samsung.firmware.science/download?url=48993/1488/SS-N950USQU2BQJA-to-S2BQK2-UP
ODIN for BQK2: https://drive.google.com/uc?id=19gW_CxUf2HdL4UYyxTkyOnBY8cluRIVS&export=download
this file for BQJA is on SamMobile, SamFirm, and Updato. These are OTA updates besides the flashing required in that.
I currently have an S8 on the Oreo beta and will be buying a Note8 this weekend because of this. I AM SO EXCITED!
Oh just a side note, this may be unstable and crash, you have been warned.
Click to expand...
Click to collapse
And again thanks to ..... lol
This is the unlocked version ???
Sent from my SM-N950U1 using Tapatalk
Del
powerstroke said:
How does one go about flashing this? I'm currently on Sprints latest update
Click to expand...
Click to collapse
1. Download Odin and flash this https://drive.google.com/uc?id=19gW_CxUf2HdL4UYyxTkyOnBY8cluRIVS&export=download
1.5 In CSC use HOME_CSC to keep data, normal to wipe
2. Download this file: https://samsung.firmware.science/download?url=48993/1488/SS-N950USQS2BQK2-to-U2CQL1-UP
3. If you have an SD card, transfer that to your Sd carz
4. Boot into recovery
5.SD: select update from sd card then select your OTA called update.zip
5.ADB: on your phone select sideload over adb then type adb sideload update.zip (replace that update.zip with full file directory)
nexus6r3plicant01 said:
This is the unlocked version ???
Sent from my SM-N950U1 using Tapatalk
Click to expand...
Click to collapse
N950U, so kinda but no, not really. If you set your CSC to A then yah, if not it has carrier bloat.
mweinbach said:
1. Download Odin and flash this https://drive.google.com/uc?id=19gW_CxUf2HdL4UYyxTkyOnBY8cluRIVS&export=download
1.5 In CSC use HOME_CSC to keep data, normal to wipe
2. Download this file: https://samsung.firmware.science/download?url=48993/1488/SS-N950USQS2BQK2-to-U2CQL1-UP
3. If you have an SD card, transfer that to your Sd carz
4. Boot into recovery
5.SD: select update from sd card then select your OTA called update.zip
5.ADB: on your phone select sideload over adb then type adb sideload update.zip (replace that update.zip with full file directory)
Click to expand...
Click to collapse
I'm already on sprints latest. That ok or do I need to downgrade before doing update.zip in recovery? Any mirrors for U2CQL1? Every time I try to download, it fails
powerstroke said:
I'm already on sprints latest. That ok or do I need to downgrade before doing update.zip in recovery? Any mirrors for U2CQL1? Every time I try to download, it fails
Click to expand...
Click to collapse
You need to be on BQK2 as linked in OP
Been downloading that ota file for 15 min and only at 1 percent lol. Thanks for this tho. Can't wait to see if this works.
jaceypoo said:
Been downloading that ota file for 15 min and only at 1 percent lol. Thanks for this tho. Can't wait to see if this works.
Click to expand...
Click to collapse
Uploading a mirror as i type this.
jaceypoo said:
Been downloading that ota file for 15 min and only at 1 percent lol. Thanks for this tho. Can't wait to see if this works.
Click to expand...
Click to collapse
I seriously just got to about 750 mb downloaded of the file and it just stops and starts over. Can't get it downloaded? What the heck lol
I was at 12 percent and the same thing happened to me lol. I'll just wait for the mirror.
Somehow, after 4 attempts at downloading, it worked and only took ~5 mins. everything appears to be in the zip file. I loaded the BK2 file (never got cell signal, and had a lot of strange things in settings) and am applying the update now. Hopefully this doesn't screw up anything. with the BK2 my settings showed custom for the status though, so not sure if I just screwed myself out of Knox stuff.
---------- Post added at 10:14 PM ---------- Previous post was at 09:35 PM ----------
Looks like it's working, some things I noted:
I had a few strange apps in my service folder (BoA and some games)
Samsung connect was causing a bunch of force closures.
Even though I was on unlocked before this, I ended up on Verizon (my carrier).
Everything else seems normal, and had I done a wipe I'd probably be in even better shape. Might to a whole tomorrow.
Sent from my SM-N950U using Tapatalk
damn, this was sniffed out from the AT&T servers?
_Dennis_ said:
Somehow, after 4 attempts at downloading, it worked and only took ~5 mins. everything appears to be in the zip file. I loaded the BK2 file (never got cell signal, and had a lot of strange things in settings) and am applying the update now. Hopefully this doesn't screw up anything. with the BK2 my settings showed custom for the status though, so not sure if I just screwed myself out of Knox stuff.
---------- Post added at 10:14 PM ---------- Previous post was at 09:35 PM ----------
Looks like it's working, some things I noted:
I had a few strange apps in my service folder (BoA and some games)
Samsung connect was causing a bunch of force closures.
Even though I was on unlocked before this, I ended up on Verizon (my carrier).
Everything else seems normal, and had I done a wipe I'd probably be in even better shape. Might to a whole tomorrow.
Click to expand...
Click to collapse
Can u post some screenshots? Anything new in settings or design?
note3userr said:
Can u post some screenshots? Anything new in settings or design?
Click to expand...
Click to collapse
Settings is new some screen shots of it here
https://www.imgur.com/a/c0MJ2
Sent from my SM-N950U using Tapatalk
where is the odin for this? The link does not have Odin
technicalvampire said:
where is the odin for this? The link does not have Odin
Click to expand...
Click to collapse
Don't need odin for this, it's an OTA.
Just put it on your phone, and go to recovery mode and flash from update.zip or whatever.
Longcat14 said:
Don't need odin for this, it's an OTA.
Just put it on your phone, and go to recovery mode and flash from update.zip or whatever.
Click to expand...
Click to collapse
First part does...