Database Develop

[SOLVED] I need everyones help! Easy Solution to get the USA WIFI Upgrade!

After screwing around for hours I have been able to get the Official dell upgrade (workaround). I realize that some want to upgrade in specific ways. But for those of us that are interested in just getting a factory upgrade here is what I have found. I believe it is a simple case of connecting the dots. All I needed was someone to provide the USA upgrade path Thanks (TheManii) For your wisdom.
So here is what worked for me. Make sure you use NVFLASH and downgrade to Froyo 2.2.2 USA WIFI.
Then with your Streak 7 connected to the internet enter the following URL in your android web browser.
http://mobileupdate.dell.com/?version=GLUNB1A334430&servicetag=PPPPPPP
Your service tag will remain as it was before the upgrade as TheManii Stated. All we needed was the correct upgrade path. Remember this has only been tested on a tablet that has been downgraded with the Froyo USA wifi Rom provided on these forums.
This will start your official update via the download page. When it is finished just click on the downloaded file and this will allow you to get the Honeycomb 3.2 Goodness youve been waiting for simply and reliably!
Enjoy,
Stingerrray

Firstly you dont need your service tag, it only depends on your installed rom.
Secondly all it does is lead your to the download page to the pkgs,
all known available pkgs are available here or on the update guide I linked to.
If you dont get a notification you wouldnt be able to update anyway, as it will check before install if you're compatable.
The currently available upgrade paths are
EU Wifi: 340/344 -> 507
EU 3g: 340/344 -> 507
US wifi: 340/344 -> 506
EU wifi submodel: 1A3
EU 3g submodel: 1A2
US wifi submodel: 1A3
The device string is constructed as:
GxxxByyyzzzaa-bbb
xxxx is always LUN as this is it's codename (The dell codename for the s7 was "looking glass", the qisda codename was "luna")
yyy is the submodel number listed above
zzz is the current rom version
aa is the region.
bbb is not valid on the S7, but on the S5 and venue this is your modem region (either US, EU, or AWS)
So the upgrade paths are:
EU Wifi:
GLUNB1A334000 -> GLUNB1A350700
GLUNB1A334400 -> GLUNB1A350700
EU 3g:
GLUNB1A234000 -> GLUNB1A250700
GLUNB1A234400 -> GLUNB1A250700
US Wifi:
GLUNB1A334030 -> GLUNB1A350630
GLUNB1A334430 -> GLUNB1A350630
For the moment the US roms 325, 340 are not canidates to update, so they're either stuck on 2.2 or have to manually update.
Until the tmo update actually comes out I'm going under the assumption that it's not currently planned to come out.
(There is also the US 4G 322/333 -> 338, but it's very old)
This covers every publically available roms. Roms that are not publicly available will never recieve update notifications.
This system is identical to the one used on the Streak 5, 10 and venue
all the links do is link to the update pkgs and the update page. If you cant acces the update page to download them you wont be able to install them anyway.

http://mobileupdate.dell.com/?version=GLUNB1A334430&servicetag=PPPPPPP
So if P is replaced with your service tag it wont work either?
Will you get a version mismatch?
I'm trying right now thanks for your help. It is DL now.
Stingerrray

your rom must EXACTLY match one of the above ones
AND your device must not have clockwork
AND must not have a custom rom installed
for it to update sucessfully though "check for updates"
If "check for updates" doesnt give an update, you will get a fota mismatch
---------- Post added at 11:41 PM ---------- Previous post was at 11:40 PM ----------
Also, all known pkgs are already listed on Dell Streak 7- xda wiki
The only things missing are older rom versions. Many of which were recently reported during the HC rollout

OK if it is too simple it usually does not work. Ill keep rooting around. I like to try and find an easy upgrade path for the masses.
Thanks,
Stingerrray

The right was is to flash the matching recovery and use the pkg, assuming you're not on honeystreak.
Tegra2 device users are far too reliant on nvflash to do the work for them.

In my case it is not being reliant. But just trying to find the path of least resistance. Thanks for the info you did indeed allow me to get the USA upgrade. All i thought I needed was the OEM VERSION Numbers that were being rolled out. So I will change this to a simple guide.
Thanks,
Stingerrray

Essentially any user who decides to root their (android) device and/or install a custom rom/modify the system paritition should have fastboot properly installed and usable for their device.
This is rarely the case as I've seen for Streak 5 and 7 users. If that were the case updating to the correct rom even if yours isnt a valid upgrade path is only 4 steps:
1) Download the recovery and pkg
2) copy the pkg to the 'sdcard'
3) flash the recovery
4) do a 'install from pkg'
Excluding the downloading step, this is nominally 3 minutes of work.
If you dont modify your device at all this is essentially 1 step as "check for updates" does all this for you

So can I use that link to install it on my streak with 338 that is wifi only?
Sent from my LG-P999 using XDA App

yes you can.
Stingerrray

I believe 338 can update to to 506 by merely copying the update.pkg to it's 'sdcard' and flashing. Assuming you havnt modified your device

Yes as you stated that will work nicely. But if you have 338 all you need to do as an alternative method is paste the URL (from the main topic post) into the Froyo 2.2.2 web browser and that will start the official update download as well.
Thanks again TheManii for helping us with this extra easy solution!
Stingerrray

Stingerrray said:
After screwing around for hours I have been able to get the Official dell upgrade (workaround). I realize that some want to upgrade in specific ways. But for those of us that are interested in just getting a factory upgrade here is what I have found. I believe it is a simple case of connecting the dots. All I needed was someone to provide the USA upgrade path Thanks (TheManii) For your wisdom.
So here is what worked for me. Make sure you use NVFLASH and downgrade to Froyo 2.2.2 USA WIFI.
Then with your Streak 7 connected to the internet enter the following URL in your android web browser.
http://mobileupdate.dell.com/?version=GLUNB1A334430&servicetag=PPPPPPP
Your service tag will remain as it was before the upgrade as TheManii Stated. All we needed was the correct upgrade path. Remember this has only been tested on a tablet that has been downgraded with the Froyo USA wifi Rom provided on these forums.
This will start your official update via the download page. When it is finished just click on the downloaded file and this will allow you to get the Honeycomb 3.2 Goodness youve been waiting for simply and reliably!
Enjoy,
Stingerrray
Click to expand...
Click to collapse
Nope doesnt work on my 4g streak. Anyway funny story i jus had a confress call with tmobile and dell and according to the dell repthe 4g tmobile model will recieve the android hc update on friday. So idk how true this is. But hey i can dream right i mean lets see what happens im mean dell did release the 3g update in the uk so y not the 4g us version right. Well all i can do is wait, im not holding my breath tho.

It wont work on the US 4G model because it's a different region, that link is only valid for US wifi models

It is for USA wifi model only. It is untested on all others.
Stingerrray

Thank-you Stingerray! After playing with all the other techniques here to get the US Wifi version on my device, your process WORKED! Smoothly I might add!
I was worried as my device ID is: GLUNB1A133830 and none of the update packages seemed to apply to a 1A1 device .. but I tried it anyway, and now I have Honeycomb up and running on my streak 7!
So Again, THANK-YOU!

dblml320 said:
Thank-you Stingerray! After playing with all the other techniques here to get the US Wifi version on my device, your process WORKED! Smoothly I might add!
I was worried as my device ID is: GLUNB1A133830 and none of the update packages seemed to apply to a 1A1 device .. but I tried it anyway, and now I have Honeycomb up and running on my streak 7!
So Again, THANK-YOU!
Click to expand...
Click to collapse
I have a GLUNB1A133830 as well. Why no love for 338's, Dell? I'll try the link if there's no upgrade by Friday night.

Update done on 338
vtinmanv said:
I have a GLUNB1A133830 as well. Why no love for 338's, Dell? I'll try the link if there's no upgrade by Friday night.
Click to expand...
Click to collapse
TheManii said:
I believe 338 can update to to 506 by merely copying the update.pkg to it's 'sdcard' and flashing. Assuming you havnt modified your device
Click to expand...
Click to collapse
I had the 338 build and all I had to do was type in the following link and it updated without any issue. Note that I left off my Service Tag for the update and I'm working fine...
http://mobileupdate.dell.com/?version=GLUNB1A334430

TheManii said:
your rom must EXACTLY match one of the above ones
AND your device must not have clockwork
AND must not have a custom rom installed
for it to update sucessfully though "check for updates"
If "check for updates" doesnt give an update, you will get a fota mismatch
Click to expand...
Click to collapse
That's not exactly true, my build was 1A13 something, checked for the update when I got home from work last night and had no update available. Clicked the link you had posted to the US wifi pkg, downloaded and installed perfectly, no clockwork just the standard update.

Exactly what I did and no issues as well.

Update failed, flashed stock, now no updates

So the lollipop update failed on my phone, so I flashed back to stock. Now the update won't show up. Is this normal, did l get pushed to the end of the line for the update?

EYEramid said:
So the lollipop update failed on my phone, so I flashed back to stock. Now the update won't show up. Is this normal, did l get pushed to the end of the line for the update?
Click to expand...
Click to collapse
Same thing happened here.

colarosen said:
Same thing happened here.
Click to expand...
Click to collapse
Im gonna try reflashing back to stock again, in a couple of days. If you figure it out let me know

Will do.
Just to add some other info... current build is KXA21.12-L1.26.1, files obtained from the motorola support site, I wiped all data when I flashed. Now when checking for updates I am told the software is up to date.

colarosen said:
Will do.
Just to add some other info... current build is KXA21.12-L1.26.1, files obtained from the motorola support site, I wiped all data when I flashed. Now when checking for updates I am told the software is up to date.
Click to expand...
Click to collapse
That's exactly what I did too

ok. So if you obtained the file VZW_212.55.26.ghost_verizon.Verizon.en.US from the moto support site, it will lead you to build KXA21.12-L1.26.1 and will not lead you to any further updates. You must flash build KXA21.12-L1.26 obtained from VZW_XT1060_4.4.4-KXA21.12-L1.26_CFC_1FF.xml This file is posted in a number of threads; still - - - http://motofirmware.center/files/category/11-moto-x-1st-generation/
Side note-- I happened to have had this file from last year when I flashed it to get to 4.4.4 originally. In the time between then and now, I obtained the stock files directly from moto support- just to have on hand. When my initial attempts at taking 5.1 failed, I assumed the files from moto support were identical to the ones I had and went ahead and used them to flash to stock. Yet apparently the images from moto support will not lead you to further upgrades (at least at this time). Moral of the story, you must start from L1.26 and NOT L1.26.1. See http://forum.xda-developers.com/showpost.php?p=62839998&postcount=518
It will now go through all three ota's (the first one brings you to L1.26.3 -- this is where we started--- the build after the ota earlier this summer, then the final two to 5.1).

colarosen said:
ok. So if you obtained the file VZW_212.55.26.ghost_verizon.Verizon.en.US from the moto support site, it will lead you to build KXA21.12-L1.26.1 and will not lead you to any further updates. You must flash build KXA21.12-L1.26 obtained from VZW_XT1060_4.4.4-KXA21.12-L1.26_CFC_1FF.xml This file is posted in a number of threads; still - - - http://motofirmware.center/files/category/11-moto-x-1st-generation/
Side note-- I happened to have had this file from last year when I flashed it to get to 4.4.4 originally. In the time between then and now, I obtained the stock files directly from moto support- just to have on hand. When my initial attempts at taking 5.1 failed, I assumed the files from moto support were identical to the ones I had and went ahead and used them to flash to stock. Yet apparently the images from moto support will not lead you to further upgrades (at least at this time). Moral of the story, you must start from L1.26 and NOT L1.26.1. See http://forum.xda-developers.com/showpost.php?p=62839998&postcount=518
It will now go through all three ota's (the first one brings you to L1.26.3 -- this is where we started--- the build after the ota earlier this summer, then the final two to 5.1).
Click to expand...
Click to collapse
Cool, I'll try this tonight, thanks

How to switch to correct update tree (to get OTA updates)?

(Please don't ask me to search the forum--that isn't working right now, it just gives an error.)
Several months ago, I bought a Nexus 6 phone, used from eBay. I have been using it with an AT&T SIM card for several months. However, it is stuck on build MOB30I and patch level "May 1, 2016". I thought that AT&T was simply months behind on updates, but today I learned the real problem: AT&T uses the MMB update tree, whereas my phone is (for some reason) on the MOB update tree. Apparently:
- My phone will not accept AT&T's MMB updates because the phone is on a different update tree
- My phone will not accept MOB updates (from Project Fi or Sprint or whomever) because an AT&T SIM card has been installed.
I tried removing the AT&T SIM card and checking for an update, but got nothing.
How do I switch to an update tree that will actually give me updates? I'd rather not install adb and sideload. In fact, rather than do that, I would instead enroll in the Android Beta program, install Android 7.0 beta, and let Google itself update me to Android 7.0 final when the time comes.

lgmayka said:
(Please don't ask me to search the forum--that isn't working right now, it just gives an error.)
Several months ago, I bought a Nexus 6 phone, used from eBay. I have been using it with an AT&T SIM card for several months. However, it is stuck on build MOB30I and patch level "May 1, 2016". I thought that AT&T was simply months behind on updates, but today I learned the real problem: AT&T uses the MMB update tree, whereas my phone is (for some reason) on the MOB update tree. Apparently:
- My phone will not accept AT&T's MMB updates because the phone is on a different update tree
- My phone will not accept MOB updates (from Project Fi or Sprint or whomever) because an AT&T SIM card has been installed.
I tried removing the AT&T SIM card and checking for an update, but got nothing.
How do I switch to an update tree that will actually give me updates? I'd rather not install adb and sideload. In fact, rather than do that, I would instead enroll in the Android Beta program, install Android 7.0 beta, and let Google itself update me to Android 7.0 final when the time comes.
Click to expand...
Click to collapse
Any reason not to use a Google Factory image? It looks like MMB29V is the most recent.

According to the instructions, installing a "Google Factory Image" would be a lot of risky work, and would erase all my data and apps. I was hoping for something simpler and safer. As I mentioned, joining the Android Beta program actually seems to be the easiest solution, if the current beta (NPD30G) is stable enough.
Frankly, I am surprised that Google/Motorola/AT&T (or any cell phone designer/manufacturer/carrier) allows a working cell phone to get into this state where the phone refuses to accept security updates.

For the Nexūs 6, the beta is quite stable (I didn't update my daily driver until I was sure it was stable on my other devices). You should be fine and back on track with NPD90G.

That's half the fun of owning a Nexus, not waiting for updates. Dl the factory image, unzip it and the zip file inside and flash the system. IMG only and you'll lose nothing but root. If, of course, you are rooted.

http://forum.xda-developers.com/showthread.php?p=59561445/ You may give it a try..... prerooted lite stock rom.

lgmayka said:
According to the instructions, installing a "Google Factory Image" would be a lot of risky work, and would erase all my data and apps. I was hoping for something simpler and safer.
Click to expand...
Click to collapse
As already suggested, just install the system image. The simplest way to do that is via fastboot. Nothing gets erased unless you flash the userdata.img. Using Google's script to flash everything would overwrite the userdata partition.
The version you are on (MMB) is released to provide updates without updating the radio. The MOB release is the same as the equivalent MMB plus the package includes the updated radio. This is a requirement of the carriers who want to approve the radio before it's released.
You will be unable to take any *incremental* OTA if there is any differential between what's on your system partition and what the OTA is expecting. You can not hop over incremental OTA updates. They must be sequentially applied. Therefore, the safest way to get to a known state is with a factory image.
If fastbooting a factory image is unacceptably risky, then maybe an eBay phone wasn't a great choice.
Or, as you say, you go straight to N. If the beta program is still available now that N is released.

stevemw said:
For the Nexūs 6, the beta is quite stable (I didn't update my daily driver until I was sure it was stable on my other devices). You should be fine and back on track with NPD90G.
Click to expand...
Click to collapse
I decided to do this. NPD90G is running well enough for me, and before long Google will release Android 7.0 Final.

Marshmallow Released

After more than 10 months after release, BLU has promised on delivering the marshmallow update. I just saw the notification today at around 4:00PM CMT.
Currently updating!

9000RPM said:
After more than 10 months after release, BLU has promised on delivering the marshmallow update. I just saw the notification today at around 4:00PM CMT.
Currently updating!
Click to expand...
Click to collapse
Screen Shots Please....

I just updated last night. Everything running smoothly. I had the phone rooted previously but the one click root app got removed in the update process. If anyone has success rooting after the upgrade, I'd love to know about it.

I upgraded this morning and I've been having lots of issues with my installed apps, like Facebook, Messenger, Whatsapp and more, and of course I lost Root which was previously accomplished by KingRoot which doesn't work anymore.
Also I noticed that during the update process, particularly while flashing the firmware, it was flashed using my TWRP recovery and afterwards it got removed.
I'm sure that if I start fresh by performing a factory reset, all will be fluid and in working order, minus TWRP and Root of course, at least for the time being.
All in all, the update to Mashmellow seems to be awesome, some new features.
Cheers!

I'm having issues with the update. It downloads just fine and when I go ahead and try to install...it just spins around on "unzipping" and then proceeds to restart..or turn off for that matter. The phone turned off...I didn't do anything to it just let it sit there for a while and then I saw the charge icon show up (the one you see when the phone is off and charging) at which point I started the phone up. The phone did not update and I can basically repeat the process. There is 4.30 GB of space free and no SD card. What do I do?
EDIT:
So I tried again, kept at it and it eventually worked. Updated just fine but now there are doubles of all folders in the phone. When I plug it into my computer, all the folders (Music, Download etc etc) are showing up twice with the same contents in the each of them...
What...is...going...on?

Was pretty laggy at first. Decided back up my files and do a factory reset. Works much better now.

disChapo said:
Was pretty laggy at first. Decided back up my files and do a factory reset. Works much better now.
Click to expand...
Click to collapse
Yeah, mine is working flawlessly after a factory reset! Much improvement compared to Lollypop!
Anyone found a Root for Marshmellow yet?

Unless Blu changed something other than the interface I'd guess TWRP won't be working on MM anytime soon. It's a problem seen in the Gionee phone and I would expect the same to happen to the Blu. As for root and a custom recovery (although not a great one) you could try following these instructions: https://forum.hovatek.com/thread-15270.html
I've played a bit with the Gionee Marshmallow firmware on my Vivo XL during the past month or so, and one thing that really bugs me is that it seems to be shipping with a kernel that is way older than it should be on an MM release. And the OTA service that is known for leaking info also seemed to still be present in the updated firmware.
Can someone who's got the Blu update check if these two things are the same for the Blu release please? Enter device info in the settings menu and check the Kernel version for me. And, if you guys manage to get root, check if AdupOTA is still lurking in there.

batoussai said:
Can someone who's got the Blu update check if these two things are the same for the Blu release please? Enter device info in the settings menu and check the Kernel version for me.
Click to expand...
Click to collapse
Kernel Version: 3.18.19
Build Number: MRA58k
Custom build version: BLU_V0030UU_V07_GENERICM14-11-2016

Does anybody with TWPR/root upgraded to official 6.0 successfully? What's exact procedure/steps?
I have my Blu Vivo XL with TWRP now, in last (small) OTA update a few months ago, I tried flashing back to original recovery and rom, but still failed OTA.

CC /w GTV (Sabrina) NEW OTA & Factory Image Dump

Previous version: https://forum.xda-developers.com/t/chromecast-with-googletv-sabrina-ota-dump.4178163/
This time when I went to pull the new OTA, I also discovered what I believe is the full factory image too
New OTA: https://drive.google.com/file/d/1zAAPbymAO1Mxb_g0w8YMfDo240ROdxgG/view?usp=sharing
Full Factory: https://drive.google.com/file/d/1ZSoR7U9gjJW8yFlh_Fxv0kZs6BUe9olX/view?usp=sharing
Kernel Version: 4.9.180
Anroid TV OS Build: QTS2.200918.015.6966301

great find, how do you usually pull the images?

micallan_17 said:
great find, how do you usually pull the images?
Click to expand...
Click to collapse
I just look at the logs while I'm updating. There's an ota url that gets set right before an update happens, and then right after it happens it gets nulled during the first boot.
Usually it's just an ota with a partial update. Around 60MB or so. For whatever reason I looked at the logs before I went to update this time and noticed the url was set - so I downloaded it and discovered it was much much larger so I grabbed it. When I went to go do a system update though it changed to a smaller ota, and I grabbed that one too.

thank you very much for the explanation, definitely very helpful info.

I don't think it's useful right now, but i've successful dumped the full factory image thar you sent
Here the link of the dump
Files · sabrina_prod_stable-user-10-QTS2.200918.015-6966301-release-keys · Giovanni Ricca / dumpyara
git.rip
git.rip

oh wow awesome find, i am going to try and get this to boot on my s905x device a port should be possible as i have done on s905x, s905w and s912 and the mi box s firmware

Hello guys.
Another user and I are experiencing issues updating our brand new Chromecast with GTV as seen in this thread: https://forum.xda-developers.com/t/chromecast-with-gtv-update-recovery-error.4274509/
My device comes with build QTS1.200625.002.A5.6686931
I guess the OTA that it is downloading is having a hard time updating from a build that is so old?
Do you think there's a way I can flash the full factory image posted by OP?
I think, by doing that, the device could then update to latest (April 2021) version.
Could that be a solution?
Do you have any other ideas?