This article was translated using Google Translate, so some places are not very accurate, please forgive me. Original link:https://www.bilibili.com/read/cv3512926，And this post no connection with the @hikari_calyx‘s https://forum.xda-developers.com/windows-10-mobile/request-windows-10-mobile-oup-v6-help-t3695499
This article is only published on xda, Zhihu, Coolan, Baidu Post Bar, IT House, bilibili. It is forbidden to reprint or wash any other person or organization in any form, but welcome to share or forward the original link. My writing is not very good. There may be some things in this article that are not clearly expressed and typos and grammatical errors. You are welcome to point out or ask questions in comments or private messages. And this is the first article I wrote, so if you don't like it, please bear with me.
First of all, thanks to the @hikari_calyx for its contribution to this project. The original author of this project (Windows 10 Mobile Offline Update Package) is the @hikari_calyx.
Hello everyone, first of all, I think I need to explain the difference between the various versions of the win10m offline update package.
From v1 to v5.1 are optical card versions, used to update almost all wp8.1 devices to win10m 10586, also provide some wp8 updates to wp8.1 more troublesome second-generation machine update wp8.1 offline Update package; v10 to v11 version is grabbed by another person, you can update win10m10586 (1511) to 14393 (1607) version, not wp8.1 update to win10m.
Regarding the v6.0 version I released this time, I was originally prepared to release the version number of this update as v5.2, because after all, I just added the wp8.1 update to Huawei w1 (including gdr1 and gdr2) and Huawei w2. Support for wp8.1 gdr2 update. But I recently went to Shenzhen, just in time for the light card in Shenzhen, just have the opportunity to face the big face, I will inform the optical card plan to update the package v5.2 offline, and also try to obtain the authorization of the name. . The optical card agreed to release a new version, but let me re-detach a branch from the v5 branch, update the version number to v6, leave the v5 branch to the optical card, facilitate the future scam update, detailed branch information, Please see the picture below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok, next step into the topic, I will tell you about some of the precautions for this update and the twists and turns of my crawling package.
I bought 3 wp:Lumia1020, Huawei w1 and Huawei w2 at one time three months ago. In the process of tossing me before, Huawei w2 and Lumia1020 have been successfully pushed into the win10m system by me. The wp8.1 update of w2 is also benefited from the update package captured by the optical card. What worries me most is the wp8 of Huawei w1. How to get the .1 update. In the past two months, I have tried many methods. The earliest I tried to jailbreak the phone, but my computer is Windows 10 operating system, not compatible with reker's rkBreakout jailbreak tool, it becomes 9008 bricks after each jailbreak, even if the compatibility mode is turned on and the security center is closed. And at the time I didn't know how to save the bricks, because the emmcdownloader tool in the Qualcomm QTPS suite could not normally run normally in Windows10, but after a while I found that I can use the WindowsXP sp2 compatibility mode to force the brush, so In this way, the phone was brushed, but wp8.1 still has to rise. As I said before, the jailbreak tool can't run normally under the win10 system, so I didn't go jailbreak in the first place. I tried using the wp8.1 update package of other models. The result is a failure (affirmative, try Only, don't spray). So, this phone was temporarily put into the drawer and I was gray...
Three weeks later...
I just wanted to experience Windows 8, and the jailbreak tool was released in 2014. I wanted to fail to upgrade my phone's system, so I just got jailbroken. Unexpectedly, after the jailbreak, you can directly open the developer preview (emmm, I used to upgrade a Microsoft developer account), but the original model information can only be upgraded to 8.0.10521.155, after the query, you can Using Lumia 925 model information, but only upgrade to 8.0.153232.166, when I try to download wp8.1 update, each time the download fails, the software that caught the package flashed four or five packages.
After that, it will report 0x801881d0, and then delete the PhoneHardwareVariant and devOSpreviewEnable registry entries. Then I grabbed the bag. So this phone has been successfully upgraded to 8.10.14234. 375 version, this version can be successfully upgraded to win10m, but this still does not reach my goal, I mentioned above, I actually want to put this The device was upgraded to wp8.1gdr2, so I started to find a way to get the gdr2 update package, but since Microsoft has closed the mobile version of Windows insider, I can only try to use the curve to save the country to update wp8.1gdr2. First of all, I received a Hisense e260t+ in the past few days. This model can be upgraded to wp8.1gdr2, so I used the e260t+ model information on Huawei w1 to get the wp8.1gdr2 update, but it did not succeed. The error code is 0x8018830F. The official documentation explains that this package is based on the difference between the source version and the source version. Since this is just an update package, I thought there was no way to update to wp8.1gdr2. So the project didn't progress in a week...
PS: HIGH ENERGY FRONT! ! ! The content of the following content is completely independent of me, without any help and technical support from the third party, and no information (except IUTool error code)
After a week, I remember that Huawei w1 Guoxing Telecom first checked the updated version table after brushing the factory firmware.
I went to look at the PART0:8.0.10211.204 to 8.0.10517.150 and PART4:8.10.12393.890 to 8.10.14234.375 I found at the beginning and found all the upgrade packages.
Wp can actually push many batches of continuous upgrade packages together to go to the sky! However, this method also has some restrictions, for example, you can not directly upgrade to wp8.1 from the version before wp8.0.10532.166 (which should be the version of the device that Microsoft specifically promotes to wp8 for upgrading wp8.1).
So I merged the various packages I had captured into two big packages and tried to push them. As a result, it was completely ok, and it would save some time compared to one push (more than two restarts) And optimized time) and energy (you can knock the command line twice, and the waiting time is not as fragmented as before).
Next, let's talk about how I brought the wp8.1gdr2 update to Huawei w1 and w2.
The following events occurred within 24 hours.
First of all, mentioned above, the part4 update is a combination of multiple versions of the update, so I first manually analyzed it, found that the operating system source version of the gdr2 update package is 8.10.114.139.141, and the part4 update There is an update to the operating system version of 8.10.114.391.41, but the updated package is updated to the updated version, causing the update link to break. So just put the "updated package" to delete it.
However, although this method looks very simple, it is a bit difficult to implement. The first reason is that I started to capture the package under the win8 system. At the time, for the sake of convenience, the download tool I used was Thunder, the creation time and modification time of the downloaded file. It’s the time when I grabbed the update package, so that’s why I need to “sort manually” the packages, because there’s no way to use file creation time or modify time sorting (idm can choose to use service-provided creation) Time), this caused a lot of trouble. I have made two mistakes in this subcontracting. I accidentally mistyped a package, causing the error of 0x8018830F between the "one step to the sky" package of 8.0.10532.166 to 8.10.14219.341. I thought it was only one one for this package. Push, so go to the 4 batches of the big bag to extract, and in the package 8.10.12397.895 to 8.10.14157.200 accidentally deleted the Simplified Chinese language package, resulting in the update after the boot After the second screen, the black screen does not enter the system. After I checked it out, I found a problem when I pushed the 8.10.14.103.306 to 8.10.14219.341 package. I got the error 0x8018830F. It seems that the previous problem should be on this package. A check of one package found that I originally misclassified a package and allocated a package from 8.10.114.319.41 to 8.10.14234.375 to the package 8.10.14.103.306 to 8.10.14219.341. After I replace this package with the corresponding version of the package, I can push it normally. After finally merging them into a large package, it can also be pushed and installed normally, and it has reached the version of 8.10.14.139.375.
So this part of the work is finally completed, but I tried to push the dgdr2 update error 0x8018830F, because I deleted the updated operating system package when I deleted the part4 (updated package), the Mobile core package was not deleted, so I I went to the Mobile Core "updated version" update version of the package, and then re-introduced from the factory version, and then tried to push the wp8.1gdr2 update package I grabbed before, the final result is not As I expected, after the installation is successful, the version number becomes 8.10.151.137.48, which is gdr2, and after I delete the traditional Chinese language package, the update package can be successfully installed on the Huawei w2 mobile phone (Huawei). The w2 national version is only available in English and Jane. The wp8 and wp8.1 systems cannot install updates to language packs that do not exist on the phone. However, these two small mistakes have completely wasted my half-day time. If these two mistakes do not occur, I will not have to worry about it.
The things described in the above content occur within 24 hours.
Attached below is the interface about Huawei's w2-t01 update.
Huawei w2 update WP8.1GDR2 after the successful interface
Download link: https://pan.baidu.com/s/1vmz3DObDJcHE7c2EeVLQHw (Baidu network disk)
https://1drv.ms/u/s!AtZ7Lwagiuybhb8uDjLuIymwiEQYMA?e=7H1Hd4 (OneDrive) (Most of the files on this folder are in the V5.1 update package, I just merged my results)
For the update method, you can go online to search for the light card tutorial.
At the end of the article, I would like to suggest to anyone who likes to toss out the update packages of various systems. When downloading the update package, you must use idm to download and open the option to use the server to pass the time. It's more convenient to deal with, for example, the thing that happened to me is a living example.
Currently known issues:
1. Huawei w2 upgrade to wp8.1 after resetting the huge slow, about 90 minutes.
2. Huawei w1 and w2 upgrade to wp8.1 after initialization or reset the first time to open the second screen of the opportunity card, please refresh the battery after 20 minutes on the second screen, do not be eager to see the second screen In the case of a forced restart, this problem does not occur during normal startup. It will only happen once again if you reset it again, and will not affect normal use.
3. Huawei w1 latest firmware can not recognize the SD card inserted before booting after upgrading to wp8.1, only recognize the hot-swappable SD card after booting, but the Telecom 05800 firmware does not have this problem, Unicom version has not been tested, but you The oil can be tested by myself. I remember that the 5600 or 5800 firmware does not have this problem. If you know the oil, please leave a message in the comment area.
4. If the factory version of Huawei w1 Unicom version or the highest version number that can be upgraded is exactly 8.0.1021.204 or 8.0.151517.150, and the system built-in language is only Simplified Chinese, Traditional Chinese and English (US), then you can Directly use the offline upgrade package of Huawei w1 Telecom Edition, and also trouble you to test the oil and leave a message in the comment area.
Questions 1 and 2 have no solution, because these are firmware issues, not system issues, unless Huawei releases new firmware to fix these issues.
The next article title may update the V6.1 version or write a complete forced flash for Huawei w1. Anyway,I don't know when the article will be updated.
Related
Android 4.4 Reversing Camera Mirror With A10,A23,A33 CPU
These mirrors come in many different flavours now. At time of edit post A33 x5 quadcore is the latest with 16GB. This newer unit can be rooted with kingroot apk version. I find I lose root after reboot for some reason. I haven't found a firmware for this mirror version as of yet. For some reason my mirror does not have a wifi antenna attached so poor signal unless 4 meters line of sight. Please becareful as from experience from buying 3 mirrors now, there can be huge differences to build quality even thou they look the same.
I'm not updating this thread with RT01 firmware anymore. Please check Baidu link below
Also need this to load firmware to TF/microsd
PhoenixCard_V310_20130618.rar
To load new firm run Phoenixcard - Select image - Insert TF card/ Microsd - Choose burn (Try until magic) - Insert Tf Card into mirror and shutdown - After mirror firmware loaded you must format to normal or Tfcard will flash mirror again on reset
You may also find your firmware here. Let me know if you can't download it(use iPad to view)
http://pan.baidu.com/wap/share/home?uk=4026862827&third=0
Yfgo.apk - Radar program (you need mirror with radar function)
Yfgo.apk
Thx to nyinyiwale
How to get root access:
Download this settings.apk and run it! Thanks to Nick Nick
Setup.apk (A23)
Now you should have developer options - Enable usb debugging
Now install on windows machine http://pdanet.co/ for android
Then install kingo root http://www.kingoapp.com/android-root/download.htm
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Specifications
Processor - Allwinner A13 Cortex A8 1.2GHz Dual Core
Smart systems - Android 4.4 OS
Screen - 5.0 inch HD 5 point touch screen
Diplay resolution - 800X480 pixels
DDR - Built in 512MB DDR 3
Nand Flash - Built in 8GB (systems will occupy 1.72GB )
External storage - Support Maximum 64GB TF card(not included)
Image Sensor - 5.0 million pixel HD camera, 350 degree rotate front lens
Lens angle view - Front 140 degree +back 120 degree
Video Resolution - Front: 1920*1080(30f/s)/HD1280x720(30f/s) - Rear: 640X480 30f/s
Video format - MP4
Picture format - JPEG
Compression - H.264
Speaker - Built in
MIC - Built in
External I/O port
1*USB 2.0
1*TF card port:
1* GPS port
1*AV IN (support auto reverse function)
Dimensions - Main product size: 310x90x20mm (L x W x D)
Just got this item off eBay. Url removed
Screen looks great. Touch screen works a treat. Nice and bright and good angle also.
There are a few things different listed that the seller on eBay has not listed correct.
It comes with android 4.4.2 And not 4.0
Has a A23 dual core and not A10
Kernel version 3.4.39
And it has a battery which would last a couple of days with no use - make sure you turn off wifi when not on power
This is a true android with some very basic functions missing. Starting it has no google services. So no google play store, no where to login to google account in settings. The launcher looks good(you can't change it) expect there is no access to app list. You can click on navi button - which holds no navigation software funny enough. Once inside the navi button you can hold on the screen and then it brings you up a app selection screen giving you option to add icons(still no gps map softwares)
Once connected to Internet apps start updating when you open them which is pretty cool.. There is an update option under andriod version screen which fails to find any update with an error(searches Internet for update or you can local upload file).
Overall I'm pretty impressed with this device and its speed. I was able to install google maps by browser. But once I closed it I could not open it again cause no icon to click on. Google maps ran a little bit sluggish but was acceptable. I'm now chasing the seller for a solution to google play store as the play store ask won't open after installing.
I was able to side load apps quite easily with the browser. Seems most work if the don't depend on play store or accounts being setup in google settings.
Synic gps software won't work as it wants to use playstore to download more files.
Es explorer works fine.
I don't think I will be able to get root access as there is no developer menu, but after clicking on firmware build number says you are already a developer
i have this one and have Google playstore, i have installed nova launcher without problem, all is fine
Hi, is it model rt01?
Do you have the same firmware 4.4.2 and specs?
Does it have an option to add google account inside android OS?
As mentioned above no google account in my OS which means no history in google maps. Very frustrating.
Could I also grab the seller as I my have to purchase a new one
Thank you if you can help
hello, i bought mine to this seller from Aliexpress, received in 8 days via DHL
http://fr.aliexpress.com/item/5-inch-Android-Mirror-Monitor-GPS-1080P-Digital-Video-Recorder-Rear-view-Camera/2021095296.html
The item has exactly the spécifications as described from top of topic and is a rt01 model, else allwinner A23 Inside, android 4.4.2 KitKat Inside
i have in native Google playstore and i have created my account without problem as soon as i powered up for the firs time the mirror
best regards
Thanks for your help appreciated.
Need to try a scab a firmware update as my seller refuses to speak with me now.
Might just buy what you got I think.
you can try to communicate via aliexpress with the store, seller is Mr wilson cao and ask him for a firmware, it's a pleasant person who respond to me very fast, also after my purchase for details. Try to say you're a friend of me (Superboost) and have same miror and you want the same OS, give a try, good luck.
---------- Post added at 06:38 PM ---------- Previous post was at 06:32 PM ----------
at this time i'm trying to root for install some progs. Framaroot = KO, kingroot not able to connect at his cloud for exploit. At this time not result. If i can, also put a twrp or other and save firmware and tranfer to you? Have an idea of rooting ?
I have seen a update.zip file for root on the net. I was thinking doing it that way.
I'll give it another go as I was more focused on gapps.zip before.
Do you have development option to activate usb debugging? I don't have this option, so it makes it hard for me.
That's why I suggested an update.zip method.
If you have usb debugging (lucky you) then try http://www.shuame.com/en/root/
Also sent a msg to your seller. I think he would have to be very nice to give time for nothing being a business man
I have not the "usb debugging option" and no more the menu security for the possibility to "accept unknown sources" option. I think it will be impossible to root the item.....
tell me if you have a response from seller, have a good day
I was going to try to enable usb debugging by a terminal command but gave up after I couldn't install gapps
Try this maybe
http://forum.xda-developers.com/showthread.php?t=893434
hello, i have installed usb drivers of the mirror (hold down volume button and plug USB) and found an unknown device, i downloaded livesuit pack V1.9 and in the usb directory, it found the driver.
Now i can lauch livesuit but it wait for an .img image file for flash.... that's all for this time.... perhaps a way for future rooting?, have a good day
Your seller is very nice.
Thank you also.. Now have to work out how to install
This is a link I found on google
http://pan.baidu.com/wap/link?uk=4026862827&shareid=3212962299&third=0
Link from your seller
http://en.mail.qq.com/cgi-bin/ftnEx...1e4459433274&t=exs_ftn_download&code=231c0681
hello, happy for you, i expect you can flash this firmware and having opérationnal Google on it.
This seller is very nice, i put it a 5+++++ stars on aliexpress
have a good day
It's a puzzle..
You have an img file.. And Phoenixcard..
Putting in sdcard and selecting startup it puts the android OS on the sdcard and you boot from that so you can test the image I suppose.
Could not see any google account. Also I have alarm next to the radio icon. When I put this one on I got the browser instead.
Can I ask under settings about tablet is your build number 20150410 ?
in the info i have : rt01-eng 4.2.2 KVT49L 20150410 test-keys
It's seem that is the same build than downloaded
perhaps puting applications in "download" folder of the program will put them on the image for flashing ?
Thank you so much. You are a legend.
Its as I figured.
running the phoniexcard program you select Startup to run off sdcard.. which is way slow.
So I took the plunge and hit production and it setup my sdcard which in turn updated my unit.
Now its usable and I cant thank you enough!
have you all you want in ? Google account possible? the next challenge : rooting...
---------- Post added at 01:24 PM ---------- Previous post was at 12:45 PM ----------
Because it's difficult to find this firmware, i put it on a Mega download
https://mega.co.nz/#!ZEwxzAyJ!HzowmA3-bVbcCdZpY7tHsQ5sV2kLQ8d6lwX6Y4Q0IXY
It include the program Phoenixcard for generate the bootable SD card for update firmware
for someone else who search
Yes rooting is on the cards now...
Just enjoying play store for the moment..
Plus I've noticed a huge increase in speed.
Large improvement in firmware need to keep eye open for future releases
UPDATE!
since ms is releasing full rollups of windows 10 mobile in windows update catalog, i'll start to collect and post full rollup links.
TH2:
10586.873 (10.04.2017) (offline: 3944 downloads)
10586.916 (05.05.2017) (offline: 978 downloads)
10586.962 (12.06.2017)
10586.1007 (11.07.2017)
10586.1045 (07.08.2017)
10586.1106 (11.09.2017)
10586.1176 (09.10.2017)
RS1:
14393.1066 (11.04.2017)
14393.1198 (05.05.2017)
14393.1358 (12.06.2017)
14393.1480 (11.07.2017)
14393.1593 (07.08.2017)
14393.1715 (11.09.2017)
14393.1770 (09.10.2017)
14393.1884 (15.11.2017)
14393.1944 (11.12.2017)
14393.2007 (06.01.2018)
14393.2068 (14.02.2018)
14393.2126 (20.03.2018)
RS2:
15063.251 (24.04.2017)
15063.297 (09.05.2017)
Total Download Count: 23258+
the screenshot shows the structure after using my personal build sorting script (powershell):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
old post:
Code:
hi everyone.
please participate in collecting cab update links for more devices/builds and i will add your pastebin links here.
i am starting it and hope you'll help me. collect links with [URL="http://www.telerik.com/download/fiddler"]fiddler[/URL] (only works from wp8 to w10m).
you need to be running the exact build for the update on your phone.
download/open windows insider app and apply to fast ring.
check for updates to download the insider fast configuration update. when it is preparing for update, disable wifi.
after the installation of the preparation update (gears), you're ready to push the cabs.
they can be pushed to the phone with iutool.exe via admin cmd
command: "C:\Program Files (x86)\Windows Phone Kits\8.1\Tools\bin\i386>iutool.exe -v -p c:\cabs"
[URL="http://forum.xda-developers.com/windows-phone-8/development/tools-wdk-wpak-wpdk-cabs-building-wp8-t3183972"]WDK,WPAK,WPDK (containing iutool.exe)[/URL]
put cabs you want to push to c:\cabs folder (create it). only update step by step, build by build.
phone might spit out a error but you can see in settings->update that it is preparing to update and rebooting automatically afterwards.
if you face iutool connection problems, disconnect the device in devices&printers and unplug/plug in usb cable again.
if you want to participate, only enable [URL="http://www.telerik.com/download/fiddler"]fiddler[/URL] right before you hit the "download update button" (check with edge browser if it works first).
that means, when it is checking for updates, it shouldn't use proxy yet.
otherwise windows update can't find any updates and you won't be able to capture them duh..
for general connection problems, install [URL="http://go.microsoft.com/fwlink/?LinkID=525569"]windows device recovery tool[/URL] (contains wp8 device drivers).
to collect cabs easily, save pastebin content to a txt file and open the list with [URL="http://www.freedownloadmanager.org/download.htm"]free download manager[/URL] for example.
[B]warning: the cab update collections are chipset (SOC)/display resolution/language/softkeys dependent.
you might be able to collect all your needed soc/res/lang/softkeys cabs for a unlisted device if you select carefully.
the language files are resolution independent so you can take the ones your device needs from other devices too.
to find out which langs your device needs, capture the update progress once with [URL="http://www.telerik.com/download/fiddler"]fiddler[/URL] and write it down.
a alternative that does not involve downgrading again to wp81 would be to mount your device's ffu rom file to check langs/soc/res (sk should be obvious).
preparation updates can contain device specific packages so only apply them to the correct device.
it is possible that on branded devices, this procedure fails.[/B]
[B]qc8974[/B]
[B]1080x1920[/B]
[B]softkeys[/B]
[B]HTC One M8 for Windows (0P6B140_TMOUS)[/B]
14203-14219 -> [URL="http://pastebin.com/pxxGeBEY"]LINK[/URL] (preparation update)
14219-10536 -> [URL="http://pastebin.com/hY3CiQ2W"]LINK[/URL]
14219-10549 -> [URL="http://pastebin.com/srawxsbT"]LINK[/URL]
14219-10572 -> [URL="http://pastebin.com/SWR2VKwT"]LINK[/URL]
14219-10581 -> [URL="http://pastebin.com/LqGbSZdv"]LINK[/URL]
14219-10586.11 -> [URL="http://pastebin.com/2QRtURXL"]LINK[/URL]
[B]hardkeys[/B]
[B]Nokia Lumia 930 (RM1045_059W1K8_000-CH_MV)[/B]
14226-10166 -> [URL="http://pastebin.com/QjfH6fa6"]LINK[/URL]
14226-10536 -> [URL="http://pastebin.com/2zf0u4iw"]LINK[/URL]
14226-10549 -> [URL="http://pastebin.com/d83zSGH0"]LINK[/URL]
14226-10572 -> [URL="http://pastebin.com/0bAQnLtd"]LINK[/URL]
14226-10581 -> [URL="http://pastebin.com/5TBxd2DX"]LINK[/URL]
14226-10586.11 -> [URL="http://pastebin.com/dbLJ9qyM"]LINK[/URL]
[B]Nokia Lumia 1520 (RM-940_059T5X9_AT&T) (you can disregard any "attwifi" cabs if you're not on AT&T)[/B]
14219-10549 -> [URL="http://pastebin.com/DWnKF1aX"]LINK[/URL]
10572-10581 -> [URL="http://pastebin.com/CyzWHDsQ"]LINK[/URL]
[B]qc8960[/B]
[B]768x1280[/B]
[B]hardkeys[/B]
[B]Nokia Lumia 1020 (RM875_059T7V7_eu_euro2_332)[/B]
12393-14226 -> [URL="http://pastebin.com/RF79E2B8"]LINK[/URL] (preparation update)
14226-10166 -> [URL="http://pastebin.com/KwCJQ7R0"]LINK[/URL]
14226-10536 -> [URL="http://pastebin.com/p7bp4qha"]LINK[/URL]
14226-10549 -> [URL="http://pastebin.com/7BfPQfna"]LINK[/URL]
14226-10572 -> [URL="http://pastebin.com/aNPTwEJm"]LINK[/URL]
14226-10581 -> [URL="http://pastebin.com/P2tfRamJ"]LINK[/URL]
14226-10586.11 -> [URL="http://pastebin.com/YC6uLCrR"]LINK[/URL]
[B]qc8x26[/B]
[B]480x800[/B]
[B]softkeys[/B]
[B]Nokia Lumia 635 [512MB ram] (RM-974_059W747_000-CH)[/B]
14219-10536 -> [URL="http://pastebin.com/84uu2gTy"]LINK[/URL]
14219-10572 -> [URL="http://pastebin.com/YSFspNKh"]LINK[/URL]
14219-10581 -> [URL="http://pastebin.com/YjH6X1KR"]LINK[/URL]
14219-10586.11 -> [URL="http://pastebin.com/nN2TT2YR"]LINK[/URL]
[B]720x1280[/B]
[B]hardkeys[/B]
[B]Nokia Lumia 830 (RM-984_059X0J5_000-CH)[/B]
15148-10581 -> [URL="http://pastebin.com/6RdbXHE9"]LINK[/URL]
15148-10586.11 -> [URL="http://pastebin.com/hQzY4S7g"]LINK[/URL]
reserved post 2
Looks like the lumia 1520 and the M8 are the same all around... what are the odds I can use these cabs to get from 10166 to 10572?
i tried to update from 10536 to 10572 and it didn't work even if they are full canonical cabs (spkg).
from wp81 to w10m it should work. but if you have a branded device, it might fail.
HD2Owner said:
i tried to update from 10536 to 10572 and it didn't work even if they are full canonical cabs (spkg).
from wp81 to w10m it should work. but if you have a branded device, it might fail.
Click to expand...
Click to collapse
Eh, I can do that just by choosing fast ring. Trying to get to 10572 while preserving Astoria. Ah well, guess I have to wait to the next fast ring push, which should solve the upgrade bug.
Hi,
First thanks for making this thread and really need to track update logs.
But why you/other people's still are linking/downloading wp8.1 OEM kit ? Since Windows 10 Mobile OEM kit is public kit.
And 8.1 KIT is huge size of 4-5 GB.
Just grab the WDK 10, it's only 600 MB. (Included all most of the files even oem certs, Updated tools, like FFUTool for profile mode etc.)
I hope that help to you/all other peoples always.
Btw I've most interesting things/research base on these tools, bringing very soon.
EDIT: Links added
Windows Driver Kit for Windows 10:
Download
OR official Page for Download All other tools.
https://msdn.microsoft.com/en-us/windows/hardware/dn913721.aspx
djamol said:
Hi,
First thanks for making this thread and really need to track update logs.
But why you/other people's still are linking/downloading wp8.1 OEM kit ? Since Windows 10 Mobile OEM kit is public kit.
And 8.1 KIT is huge size of 4-5 GB.
Just grab the WDK 10, it's only 600 MB. (Included all most of the files even oem certs, Updated tools, like FFUTool for profile mode etc.)
I hope that help to you/all other peoples always.
Btw I've most interesting things/research base on these tools, bringing very soon.
Click to expand...
Click to collapse
Link?
Thanks! Maybe now I can complete the update of my 640 to build 10536. It looked like that was pulled from the Fast Ring after the release of 10549 and 10572, so any devices still on Slow Ring build 10166 were stuck in an endless update loop when going to the Fast Ring.
How can install this cab files? i have lumia 635 512mb ram please somebody help me
snickler said:
Link?
Click to expand...
Click to collapse
Updated previous post and added links.
djamol said:
Updated previous post and added links.
Click to expand...
Click to collapse
Yeah, I didn't realize.. I installed the AIK a while back, so I had the tools installed .
10581 links added
let me know if a build rollup with all cabs combined and sorted with descriptions would be appreciated.
i did that already for build 10581 now.
I'm getting error 0x80188302, google says it's E_PACKAGE_ALREADY_INSTALLED. Is there any way to track or ignore package collisons?
t4m4m0 said:
I'm getting error 0x80188302, google says it's E_PACKAGE_ALREADY_INSTALLED. Is there any way to track or ignore package collisons?
Click to expand...
Click to collapse
leave out the studyid package(s). those are the needed windows insider configuration updates.
you might have this/those installed already .
Saw this article after I did the update to 10581. Need file list for Lumia 920 (RM-820_nam_att_100) to restore astoria.
So how do I install a group of these cabs to get to 10536 from 8.1?
edit: Can I just use iutool from win 8.1? I haven't been in the win8m scene, just fooled around with win10m.
loudog3114 said:
So how do I install a group of these cabs to get to 10536 from 8.1?
Click to expand...
Click to collapse
yes. enable wifi and open windows insider app. when you see the ring selection (fast/slow),
disable wifi via notification center. then apply to fast ring. device will reboot.
then you should be ready to push cabs. after cab transfer, iutool says "update started".
then it will spit out a error but if you go to settings-> update, you can see that it is preparing for update.
the phone will automatically reboot after update preparation and apply the cabs (shows gears).
followed by migrating data as usual.
HD2Owner said:
yes. enable wifi and open windows insider app. when you see the ring selection (fast/slow),
disable wifi via notification center. then apply to fast ring. device will reboot.
then you should be ready to push cabs. after cab transfer, iutool says "update started".
then it will spit out a error but if you go to settings-> update, you can see that it is preparing for update.
the phone will automatically reboot after update preparation and apply the cabs (shows gears).
followed by migrating data as usual.
Click to expand...
Click to collapse
Awesome. I had resigned myself to having to use 10166 if I wanted astoria but I am going to give this a go now.
I thought i would start this thread, separate to the Jeep one as the Jeep thread is for the 8.4" uConnect and uses some different files to the 6.5" version.
The aim of the thread is to be able to gain some sort of 'root' access to the file system to be able to update the maps on the system. So far I know cm0002 and Leighm0 have done some great work with the 8.4" - Most of which we can use on the 6.5".....once we have access to the file system.
The problem we seem to be facing is finding a swdl.iso that is old enough to be modified for our 6.5" units.
Mission Accomplished.... mostly
Disclaimer: I can not be held responsible for any damages to your uConnect, Car or your hair falling out from running this modification.
That being said, if you do have a problem please contact me and I will see if I can help you fix it.
For all those people still on v17.07.46 or older uConnect 6.5 firmware I offer you a “jailbreak”, you can now update your maps to the latest versions (currently offering EU 2018Q3 / NA 2018Q1 in my pack). I have to warn you though, the process can take a lot of time!
For those of you who have updated your 6.5 uConnect to v17.35.41 or v18, I am still working on how to update those, FCA / Alfa changed the locks with that update!
For a Full EU / NA update, if you follow my instructions fully, it will take approx. 4hours during which time your uConnect must remain powered on. This time can be greatly reduced by only updating the country or countries you need, or if you are feeling brave, skipping Step 1.
Files / Items needed:
uConnect 6.5 running v17 or older firmware -Supporting Alfa, Fiat and Jeeps too!
At least 8gb USB Drive ***preferably with a flashing led light so you can see file access***
Files from
https://mega.nz/#F!kURhTCbJ!uJhKPMyGiESbvQSDb33CvQ
Stage 1 – Backup your files
Download:
1 Magic -Alfa pre UPD.zip -For Alfa
1 Magic -Fiat & Jeep pre UPD.zip -For Fiat / Jeep
2 Backup.zip
Process:
1. Download and expand “1 Magic -XXX.zip” and “2 Backup.zip”
2. Copy the content onto the root of the USB drive
3. Start car and let uConnect boot up (wait approx 5min for full boot up)
4. Plug in and WAIT, the uConnect will not appear to be doing anything but if you are using a USB with a light you should be able to see it flashing with file activity
5. After some time, in my case it took 1h25 to complete this stage, it should popup a window about there is a update that you MUST answer NO to
6. Pull USB, and power cycle the uConnect*
After that you now have a backup of all the system and map files we are going to change on your uConnect.
KEEP THEM SAFE!
Either use a second USB for stage 2, save the backup folder to your computer or if your like me and use a 16gb USB stick you can leave it where it is.
I have now uploaded copies of the official EU Map Packs from (A) 2013, 2015 and 2017, NA Map Packs (B) 2013, and ROW Map Packs (C) WIP that will function as a backup or official upgrade for anybody needing them, restoring your uConnect back to stock.
***If you have a newer set of Original Map files please contact me, and I can add them to the drive for all to benefit from***
Stage 2 – Modify your uConnect
Download:
1 Magic.zip --You should already have this if you completed Stage 1
D EU Custom 2018 HNEU2018Q3v2.zip --Full EU
E NA Custom 2018 HNNA2018Q1.zip --Full North America
Or
D UK Custom 2018 HNUK2018Q3.zip --UK Only
D FR Custom 2018 HNFR2018Q3.zip --France Only
D DE Custom 2018 HNDE2018Q3.zip --Germany Only
D IT Custom 2018 HNIT2018Q3.zip --Italy Only
***There will be other country / State only update packs soon***
Or
A EU 2013 Original NQEU2012Q4.zip --Stock 2013 Maps, Original EU Release
A EU Update 2017 HMEU2015Q4.zip --Newest Original Map files released 2017
B NA 2013 Original NQNA2013Q4.zip --Stock 2013 Maps, Original NA Release
Process:
1. Download and expand “1 Magic.zip” and “D XX Custom 2018 HN….zip”
2. Copy the content onto the root of the USB drive
3. Start car and let uConnect boot up (wait approx. 5min for full boot up)
4. Plug in and WAIT, the uConnect will not appear to be doing anything but if you are using a USB with a light you should be able to see it flashing with file activity
5. After some time, depending on file used - If country / State only pack approx. 15min if full EU then approx. 2h, it should popup a window about there is a update that you MUST answer NO
6. Pull USB, and power cycle the uConnect*
If all gone well you will now have a uConnect 6.5 with updated maps!
As I am sure you can understand, there are still some little bugs to work out;
Problems:
UK postcodes > Only 5 digit search
Speedcams > Not working at all
Anything else… you tell me
Fixed:
UK TMC now working
France TMC working again
Italy TMC (paid version) working
There may be other little problems, but I am unable to test them, please let me know and I will look into them and try to fix!
*To Power cycle:
Either remove key, lock car, wait 10min, unlock and restart)
Or use engineers menu to reset the uConnect (Press Radio, More and Browse until menu pops up, scroll down to Reset Radio, answer YES)
I have uploaded some of the files, more to come.
The URL:
https://mega.nz/#F!kMYjlSKB!MCC6U1jclb0_aHc-NdocrA
If you have anything else to share please message me.
So I have found a uConnect 6.5 update file with version no 15.18.xx. Uploaded to the mega share - now to figure out how to modify it!
Jeep Renegade
Hi.
It is possible in jeep?
SquithyX said:
So I have found a uConnect 6.5 update file with version no 15.18.xx. Uploaded to the mega share - now to figure out how to modify it!
Click to expand...
Click to collapse
any news?
Update....
The 15.18.xx file is ROW and after modifying it to work for any model, I get a authentication error on inserting the USB!!!!
Hi SquithyX,
Any chance to get the link for "Updated EU Maps (2018q1) formatted for the 6.5"??
Many Thanks in advance!
Hi,
I have a working Alfa 6.5" headunit with 14.X.X sw still installed on it. Does anyone know if it is possible to extract fw directly through JTAG? What kind of harware is needed to do such operation?
Icaro03 said:
Hi SquithyX,
Any chance to get the link for "Updated EU Maps (2018q1) formatted for the 6.5"??
Many Thanks in advance!
Click to expand...
Click to collapse
I can upload for you if you want, however until I hack has been found to be able to modify the system, they will not work!
Sent from my CLT-L09 using Tapatalk
andri98 said:
Hi,
I have a working Alfa 6.5" headunit with 14.X.X sw still installed on it. Does anyone know if it is possible to extract fw directly through JTAG? What kind of harware is needed to do such operation?
Click to expand...
Click to collapse
Not sure on JTAG, but if it is a early uConnect (Alfa 940 unit with More button) then the NAND chip is on a separate daughter board, that can be removed from the system. If a interface could be made for that then full disk access could be got.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my CLT-L09 using Tapatalk
it would be great to see some development on this system
SquithyX said:
Not sure on JTAG, but if it is a early uConnect (Alfa 940 unit with More button) then the NAND chip is on a separate daughter board, that can be removed from the system. If a interface could be made for that then full disk access could be got. View attachment 4611300
Click to expand...
Click to collapse
I found a datasheet searching JY455
It seems to be an eMMC Memory from Micron (MTFC??GLGDM) with a build in MMC-Interface
Maybe it works like an MMC-Card.
If someone build an adapter for the white connector and USB, maybe we can read and write the flash like an MMC-Card on an USB reader.
for you may this works for really? have a look for "Alfa Romeo Giulietta UConnect Apple CarPlay & Android Auto retrofit Kit" in a search engine. it's very expensive but they say you can use touch screen as well to interaction when usually all the video interface i have found say not possbile, only video signal. what do you think about this?
So close, but broken lol
Success......kind of, I have managed to modify a swdl.iso to enable loading of different / modified files, on my Alfa 6.5 uConnect running 17.07.55.
The problem now is I seem to have completely broken navigation!!!!!!
I used the idea from post #216 in the Rooted Jeep Cherokee thread and modified the manifest.lua file in the swdl.iso (17.07.55) to load a script from usb before running the update.
Process goes power on uConnect > wait for it to boot up and display "Hands free ...." > insert USB and wait...it seems like its not doing anything but the script is running in the background > after some time the do you want to update question and answer No.
The fact that is has asked if you want to update is confirmation that the script has finished, however unfortunately there is no indication that the script is being run or how long it will take unless you have a usb with a flashing light, then it will show you something is happening at least! **my usb does not have a flashing light
I tested it with a splash screen update.... that worked perfectly, so no more boring Alfa Romeo logo on silver background for me at start up, I then pushed the modified NaviServer2, nav.sh and navRestart.sh files and rebooted.... new splash screen working perfectly but on pressing Nav button I just end up on a screen saying "Activating Navigation"
I am in the process of uploading the modified files to the mega share if anybody whats to have a look or are feeling brave
Navigation now fixed! working on making a 2018q2 map pack for it now.
SquithyX said:
Navigation now fixed! working on making a 2018q2 map pack for it now.
Click to expand...
Click to collapse
Really????' you are the MAN! could you please share everything you have used and step by step? do you think even with firmware 18 installed is possible updating maps?
thanks
Ok, here is a test image (working with v17 and earlier.... unknown for v18).
https://mega.nz/#!IUZDQATI!o1OBd8qbA...mQ5lunDb0opDvs
For anybody wanting to try it, and let me know the outcome.
The script I have included will:
Backup your MAPS license files to the USB
Backup your original Alfa Splash Screen to the USB
Copy a dbver file to the USB, that should contain information about your version of MAPS installed
Push the modified Splash screen and set its properties on the uConnect
Steps:
1. Download and expand
2. Copy onto USB drive (at least 4gb) ***preferably with a flashing led light so you can see file access***
3. Start car and let uConnect boot up (wait approx 5min for full boot up)
4. Plug in and hope
5. After some time it should popup a window about there is a update (with v17) that you answer NO to. With v18 i dont know what it will do, it may popup a window saying newer version installed, Error or maybe not do anything at all.
If that is the case use the led on the usb to make sure no file access is going on and then maybe wait 5 min extra, just to make sure.
6. Pull usb, and power cycle the uConnect - either power off the car (lock car, wait 5min, unlock and restart) or use engineers menu to reset the uConnect
7. Watch it boot....the boot image will be different if success!!!!! (there will also be some new files on the usb)
It is very important NOT to let it run the update, if it offers
I am in the process of uploading my work to my mega share,
I am currently running 2018Q3 UK maps in my Alfa with WORKING tmc. Still trying to sort the speedcams and full postcode search though - they dont work....yet!
SquithyX said:
I am in the process of uploading my work to my mega share,
I am currently running 2018Q3 UK maps in my Alfa with WORKING tmc. Still trying to sort the speedcams and full postcode search though - they dont work....yet!
Click to expand...
Click to collapse
did you modify the swdl.iso? or just the script.lua?
sofro1988 said:
did you modify the swdl.iso? or just the script.lua?
Click to expand...
Click to collapse
I have used a modified 17.07.55 swdl.iso with a script.lua - if you download the test above it contains some of the modified files. The rest are currently being uploaded / are already available online.
I have done a very quick video of progress with the uConnect here:
https://youtu.be/ed0O-xXNHdg
Didn't see a thread, but I just checked the Members app and saw the OneUI 3.0 beta registration was finally on there for G975U1. Registered and am downloading now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Links:
BETA 1 - Android 10 ETJ3 -> ZTKI Update.zip link ( courtesy of @GreenDinoXD )
BETA 2 - ZTKI -> ZTL9 Update.zip link ( courtesy of @GreenDinoXD )
Rename .bin file to update.zip
Follow installation instructions from this thread:
Kapitein187 said:
ADB-method:
1. Download SDK platform tools from here https://developer.android.com/studio/releases/platform-tools
2. Extract them on your desktop.
3. Inside the extracted folder put the update.zip
4. Inside this folder, holding left shift, right click the mouse and select "open command prompt here". The command prompt will open.
5. Shutdown the phone.
6. Holding power+volume up buttons, enter into recovery mode.
7. Select "update via ADB". (you scroll down using the volume buttons and select using the power button).
8. Connect the phone to the PC using original samsung USB cable.
9. In the command prompt run the following command:
./adb devices
10. Wait to see that the daemon has started and that your device is found.
11. If you device is found, run the following command:
./adb sideload update.zip
The update process will start. You will see a percentage counting. First it will verify, then patch etc. Do not move the cable, disconnect the phone or power off the PC.
Once the process is completed (it takes some time) the phone will boot itself, update the apps and log into your home screen.
SD-card method:
1. Download the bin file and rename it to update.zip (by going to file options in win10 you can select to view the file extensions. This makes the renaming process much easier and safer, and avoids renaming the file to update.zip.zip)
2. Copy it to the root directory of your SDcard.
3. Shut down your phone.
4. Hold simultaneously Power+volume up buttons to get into stock recovery.
5. Using your volume keys navigate to "update via SdCard" and press power button to select it.
6. Again using volume keys navigate to the file "update.zip" and press power button to select it.
7. Update will start. Leave it till it completes. It will take some time.
8. Phone will reboot by itself and load android.
Click to expand...
Click to collapse
How to capture the update.zip file to share with other people:
1. Download HTTP canary app from playstore
2. Open HTTP Canary app
3. Start the update by pressing "download" and don't pause it
4. Go back to canary app and start it and it will grab the link for you
rikipy said:
How to capture the update.zip file to share with other people:
1. Download HTTP canary app from playstore
2. Open HTTP Canary app
3. Start the update by pressing "download" and don't pause it
4. Go back to canary app and start it and it will grab the link for you
Click to expand...
Click to collapse
Is it still possible to grab the link after it's finished downloading? It's finished but I haven't installed it yet.
jeston said:
Is it still possible to grab the link after it's finished downloading? It's finished but I haven't installed it yet.
Click to expand...
Click to collapse
Just redownload it.
Hello, please post update.zip file
please do you have the update.zip file , please share the link
is it for snapdragon?
Good day, anyone was able to download the zip file? My CSC is XXA. I tried to do the trick of taken out my sim card and restarting my phone to see the notice come up in the members app but cannot enrol because I do not have a us simcard in my phone.
Ackeem.Salmon said:
Good day, anyone was able to download the zip file? My CSC is XXA. I tried to do the trick of taken out my sim card and restarting my phone to see the notice come up in the members app but cannot enrol because I do not have a us simcard in my phone.
Click to expand...
Click to collapse
That's not how this works, unfortunately.
Some people END UP with Snapdragons outside US, i have a friend who i recently found out was on PIE.
It's logical that SIM Region and Actual Location match up.
The only way we can alleviate this is by finding out a way to spoof requests to Samsung's Servers (alla Frija) for OTA's with mocked locations, but i've never seen something like that.
That said, Snapdragon Beta testers seem to be as helpful as Samsung is to them, so far none of them have shared the package with us.
PlutoDelic said:
That's not how this works, unfortunately.
Some people END UP with Snapdragons outside US, i have a friend who i recently found out was on PIE.
It's logical that SIM Region and Actual Location match up.
The only way we can alleviate this is by finding out a way to spoof requests to Samsung's Servers (alla Frija) for OTA's with mocked locations, but i've never seen something like that.
That said, Snapdragon Beta testers seem to be as helpful as Samsung is to them, so far none of them have shared the package with us.
Click to expand...
Click to collapse
okay please if you hear any please let me know .. and thanks so much am grateful
I tried a manual Frija fetch with OP's information, just for the sake of it, and got some interesting results.
This is the latest XAA Android 10 Build in Auto shows:
SM-G975U1_1_20201020093603_5lxag3hh7k_fac.zip.enc4
So build date is 20th October 2020. And this is ETJ3 (November).
Manually looking up for XAA with:
PDA: G975U1UEU4ZTKI
CSC:G975U1OYM4ZTKI
Phone: G975U1UEU4ZTKI
Gives me this:
SM-G975U1_7_20201112155200_rpfk7uveqc_fac.zip.enc4
So, build date is 12th November 2020. Build Date and release dates can differ up to two-three weeks. Weirdly though it reports Android 7.1.1 (which this device never had).
OP (@jeston ) Can you just check if the build date matches with yours in Software Information?
PlutoDelic said:
I tried a manual Frija fetch with OP's information, just for the sake of it, and got some interesting results.
This is the latest XAA Android 10 Build in Auto shows:
SM-G975U1_1_20201020093603_5lxag3hh7k_fac.zip.enc4
So build date is 20th October 2020. And this is ETJ3 (November).
Manually looking up for XAA with:
PDA: G975U1UEU4ZTKI
CSC:G975U1OYM4ZTKI
Phone: G975U1UEU4ZTKI
Gives me this:
SM-G975U1_7_20201112155200_rpfk7uveqc_fac.zip.enc4
So, build date is 12th November 2020. Build Date and release dates can differ up to two-three weeks. Weirdly though it reports Android 7.1.1 (which this device never had).
OP (@jeston ) Can you just check if the build date matches with yours in Software Information?
Click to expand...
Click to collapse
Looks like the build date is November 30...
I can't be the only one in the beta, nobody else has been able to join and grab the update.zip?
jeston said:
Looks like the build date is November 30...
Click to expand...
Click to collapse
That's nice news, why is Frija able to download a November ROM when there isnt one built in that month (As i said, November release was built in October).
I could never do this before with Beta's or Test Firmwares on SamFirm or Frija, why is it suddenly reacting to the exact values of the Beta is a myth to me.
jeston said:
I can't be the only one in the beta, nobody else has been able to join and grab the update.zip?
Click to expand...
Click to collapse
There are quite a few on reddit, but no one sniffed the package. Bummer.
jeston said:
Is it still possible to grab the link after it's finished downloading? It's finished but I haven't installed it yet.
Click to expand...
Click to collapse
yes its still posible and me on insta: Mateuzs_95 so i can help you with the steps:
PlutoDelic said:
That's not how this works, unfortunately.
Some people END UP with Snapdragons outside US, i have a friend who i recently found out was on PIE.
It's logical that SIM Region and Actual Location match up.
The only way we can alleviate this is by finding out a way to spoof requests to Samsung's Servers (alla Frija) for OTA's with mocked locations, but i've never seen something like that.
That said, Snapdragon Beta testers seem to be as helpful as Samsung is to them, so far none of them have shared the package with us.
Click to expand...
Click to collapse
I actually get updates my latest being last month.
PlutoDelic said:
That's nice news, why is Frija able to download a November ROM when there isnt one built in that month (As i said, November release was built in October).
I could never do this before with Beta's or Test Firmwares on SamFirm or Frija, why is it suddenly reacting to the exact values of the Beta is a myth to me.
There are quite a few on reddit, but no one sniffed the package. Bummer.
Click to expand...
Click to collapse
I guess they were quite hasty so nobody thought about grabbing the update
I really hope someone grabs the update and upload the zip. Waiting for 3 months to get a feel of android 11 is just out of it.
Ackeem.Salmon said:
I really hope someone grabs the update and upload the zip. Waiting for 3 months to get a feel of android 11 is just out of it.
Click to expand...
Click to collapse
the guy that created this post can do it right know but i don't know if he want to do it. i can help him but he needs to contact me so i can tell him the steps
BETA 1 FOR G975U1.
Install guide found here I believe. I did not create that guide. I am not responsible for what you do with the file, I just grabbed it cause it seems people needed it.
GreenDinoXD said:
BETA 1 FOR G975U1.
Install guide found here I believe. I did not create that guide. I am not responsible for what you do with the file, I just grabbed it cause it seems people needed it.
Click to expand...
Click to collapse
Can anybody confirm that's the correct update.zip before I include the link in the OP?
This is the support thread of PixelFlasher
(PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features).
Note: This thread is meant for issues and problems faced in Google Pixel 6 Pro devices, generic issues that are device agnostic should be discussed in the main thread.
For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.
Troubleshooting:
If you need support or assistance, the best way to get is by generating a support file from within PixelFlasher.
You can hit that big Support button on the main screen, or select it from the Help menu.
The generated support.zip file is sanitized (redacted) to keep your sensitive information (username device id ...) private.
Placeholder
Placeholder
this is an interesting project.
can you add a way to flash all partition/boot slots easily for new users? I think that can resolve a ton of issues. (the flash tool doesn't do this, just reinstalls some of the images like bootloader and raidio).
Alekos said:
this is an interesting project.
can you add a way to flash all partition/boot slots easily for new users? I think that can resolve a ton of issues. (the flash tool doesn't do this, just reinstalls some of the images like bootloader and raidio).
Click to expand...
Click to collapse
There's some discussion ongoing in the main thread of PixelFlasher about advanced options.
Feel free to chime in there, as this point is not specific to Pixel 6 Pro and would help all devices if it is discussed in the main thread.
📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.
DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...
forum.xda-developers.com
badabing2003 said:
There's some discussion ongoing in the main thread of PixelFlasher about advanced options.
Feel free to chime in there, as this point is not specific to Pixel 6 Pro and would help all devices if it is discussed in the main thread.
📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.
DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...
forum.xda-developers.com
Click to expand...
Click to collapse
Done, check the new release.
New Release:
March 24, 2022 v1.2.0.1-alpha release.
Added Advanced Configuration menu which unlocks advanced features such as:
- Flashing to both slots
- Disabling Verity
- Disabling Verification
- (More features to come)
The UI will now display the chosen Android Platform Tool's version.
Added an option to toggle verbose console output (help troubleshooting, more verbosity to come).
Stability fixes.
New Release: (See full details here on xda or here at github)
April 03, 2022 v2.0.0.0-pre release.
Major refactoring
Added Advanced (Expert) mode UI.
Basic mode keeps UI simple and hides expert features.
Support for setting active slot.
Reboot options (recovery, system, bootloader)
Moved custom ROM options to expert mode.
Added custom flashing to expert mode, can now flash to live (temporary root), or custom flash any image to any partition.
Moved flashing to both slots, disabling verity / verification to expert mode.
Many other improvements, validations and checks.
Updated documentation.
Update:
Version 2.0.1 which includes a hotfix for issue reported here.
Flawless one click update. Thanks. This going to be my default update tool.
Just used it to flash April update on my 6 Pro. Worked like a charm. Thanks.
Also used this to get to April from February and it was one of the simplest things I've ever had to do. Excellent work on this.
It keeps saying magisk is not on my phone, but it is, and it's not hidden.
According to the logs it thinks my phone is not rooted, but it is.
Edit: Followed the instructions and it updated perfectly though, just weird it thinks my phone is not rooted. Awesome app my friend, will be using this as long as it works!
Zach Alt said:
It keeps saying magisk is not on my phone, but it is, and it's not hidden.
According to the logs it thinks my phone is not rooted, but it is.
Edit: Followed the instructions and it updated perfectly though, just weird it thinks my phone is not rooted. Awesome app my friend, will be using this as long as it works!
Click to expand...
Click to collapse
Thanks for bringing this up, I'll add it to the guide,
Shell would need root permission for it to be able to do detect and use magisk.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
badabing2003 said:
Thanks for bringing this up, I'll add it to the guide,
Shell would need root permission for it to be able to do detect and use magisk.
View attachment 5581317
Click to expand...
Click to collapse
Awesome, I'll enable it for next month's update. Again, thanks for this software, it's awesome.
I toggled root access for shell and now my phone shows as rooted in Pixel Flasher.
New Release:
April 06, 2022 v2.1.0 release
Setup dedicated profile directory.
Put logs in the profile directory and maintain log history.
Plumbing for Linux support (just the flashing part is left to do).
Plumbing for new workflow.
Bugfix to handle name conflict in ROM filename.
Various minor improvements.
Update documentation.
Forgot to mention this but I was running this last night and did a dry run before the real thing, it progressed but my cable was apparently faulty so it lost connection mid way (good thing I did dry run and thank you for having it). Anyway, when it lost connection it caused the app to lock up. I closed it in task manager but the files were stuck in use and I had to find and kill the processes still open to free them up before I could start again.
Suggestion: add a check for and close of any existing processes related to the pixel flasher program if it gets reopened to avoid things being stuck in use. I work in IT so I was fine poking around to kill those processes but not everyone will be.
If you can't, maybe just add the list of processes to the OP so people can kill them on their own.
wgrant said:
Forgot to mention this but I was running this last night and did a dry run before the real thing, it progressed but my cable was apparently faulty so it lost connection mid way (good thing I did dry run and thank you for having it). Anyway, when it lost connection it caused the app to lock up. I closed it in task manager but the files were stuck in use and I had to find and kill the processes still open to free them up before I could start again.
Suggestion: add a check for and close of any existing processes related to the pixel flasher program if it gets reopened to avoid things being stuck in use. I work in IT so I was fine poking around to kill those processes but not everyone will be.
If you can't, maybe just add the list of processes to the OP so people can kill them on their own.
Click to expand...
Click to collapse
The reason that happened is because PixelFlasher is running flash-all equivalent script, which has fastboot commands in it, most fastboot commands (aside from informational ones) are blocking, i.e. it waits for device.
Because your cable was faulty and your device was not appearing connected, it got blocked waiting for it.
It's a good idea to display a message and the PID of the spawned process, the user can kill it if they wish.
I really don't want to intervene with that spawned process as it is the one flashing your phone, any glitch in there and it could mess up the phone.
badabing2003 said:
The reason that happened is because PixelFlasher is running flash-all equivalent script, which has fastboot commands in it, most fastboot commands (aside from informational ones) are blocking, i.e. it waits for device.
Because your cable was faulty and your device was not appearing connected, it got blocked waiting for it.
It's a good idea to display a message and the PID of the spawned process, the user can kill it if they wish.
I really don't want to intervene with that spawned process as it is the one flashing your phone, any glitch in there and it could mess up the phone.
Click to expand...
Click to collapse
That's a good idea as well, better to not force a closure of the process and instead inform then give the user the information necessary to close it themselves. It was definitely the fastboot process that was holding the files. Once I killed that it was fine for me to proceed. Providing a pop up with the PID or even just the process name (unless the PID is always the same) and instructions in that pop up would certainly help someone get out of a jam without needing to reboot the computer.
I've done some stuff like this project with batch but this blows that completely out of the water. Excellent work, you should be proud of what you've given to the community.
can I also root my Pixel with that?