Related
this was originally leaked by Football, here
Schubert S Europe 5.10.401.04
Model: HTC HD7 T9292
Software: Windows Phone 7.5
OS version: 7.10.7720.68
Firmware revision number: 2250.21.51004.401
Radio software version: 5.71.09.02a_22.51.50.21U
Bootloader version: 5.10.2250.0(132968)
Click to expand...
Click to collapse
Football's download link -> here
sh4d0w86 said:
this was originally leaked by Football, here
Football's download link -> here
if anybody flashes this, could you please inform me of the exact Bootloader version? thank you.
Click to expand...
Click to collapse
Thanks for this, is it true that flashing this ROM will permanently change the CID and is this the official unbranded European ROM?
Snow Monkey said:
Thanks for this, is it true that flashing this ROM will permanently change the CID and is this the official unbranded European ROM?
Click to expand...
Click to collapse
according to the tools i have, CID and DEV ids remain the same.
but, for whatever reason, the Bootloader still can't be downgraded, to my knowledge.
if you are interested in the Radio, i uploaded it to the Wiki. link in my signature.
sh4d0w86 said:
according to the tools i have, CID and DEV ids remain the same.
but, for whatever reason, the Bootloader still can't be downgraded, to my knowledge.
if you are interested in the Radio, i uploaded it to the Wiki. link in my signature.
Click to expand...
Click to collapse
I downloaded the radio several times, but it seems that the archive is damage or broken. I always get error in extracting. Used winrar and 7zip no go
Can you check it out pls
ginjamaka said:
I downloaded the radio several times, but it seems that the archive is damage or broken. I always get error in extracting. Used winrar and 7zip no go
Can you check it out pls
Click to expand...
Click to collapse
I downloaded and unzipped - everything is fine.
sh4d0w86 said:
this was originally leaked by Football, here
Football's download link -> here
if anybody flashes this, could you please inform me of the exact Bootloader version? thank you.
Click to expand...
Click to collapse
Just put this ROM on and details are below:
OS version: 7.10.7720.68
Firmware revision number: 2250.21.51004.401
Hardware Revision Number 0002
Radio software version: 5.71.09.02a_22.51.50.21U
Radio Hardware Version A.102.0.D4
Bootloader version: 5.10.2250.0(132968)
Chip SOC version 2.2.5.0
Mat be a stupid question but how do I check the CID?
ginjamaka said:
I downloaded the radio several times, but it seems that the archive is damage or broken. I always get error in extracting. Used winrar and 7zip no go
Can you check it out pls
Click to expand...
Click to collapse
downloads and unzips fine for me.
make sure you have the latest version of 7zip.
used a new(er), better compression type.
Snow Monkey said:
Just put this ROM on and details are below:
...
Mat be a stupid question but how do I check the CID?
Click to expand...
Click to collapse
thanks for that information.
only way i know how is to dump the ROM and look.
i used nbhTool and OsBuilder.
sh4d0w86 said:
downloads and unzips fine for me.
make sure you have the latest version of 7zip.
used a new(er), better compression type.
Click to expand...
Click to collapse
Thanks used a newer version, it worked
Since this is the official signed rom do you still need to hardspl to install and does it come with internet sharing
Just checked from the original thread no hardspl required
livingspring said:
Since this is the official signed rom do you still need to hardspl to install and does it come with internet sharing
Just checked from the original thread no hardspl required
Click to expand...
Click to collapse
as you discovered...
no need for XSPL, as long as you have the European HD7 T9292.
and yes, it does include Internet Sharing.
I have the TMOUS version of the HD 7 running on Mango RTM final
what would be the correct procedure for flashing this ROM?
Is it possible to downgrade to earlier versions of Mango if need be?
OS version 7.10.7720.68
Firmware;2250.21.40503.531
Bootloader;4.5.2250.0(129966)
livingspring said:
I have the TMOUS version of the HD 7 running on Mango RTM final
what would be the correct procedure for flashing this ROM?
Is it possible to downgrade to earlier versions of Mango if need be?
OS version 7.10.7720.68
Firmware;2250.21.40503.531
Bootloader;4.5.2250.0(129966)
Click to expand...
Click to collapse
you would need XSPL to flash this ROM.
but if you flash this ROM you'll be unable to revert unless via Zune back-up because of OSPL.
i suggest to just XSPL, then flash a Custom ROM based on this ROM.
tutorial how to XSPL and flash Custom ROMs in my signature.
Thanks a lot
Sent from my GT-I9100 using xda premium
Ok if the official ROM is leaked then it's only a matter of time before the ICS driver update is rolled out to existing HD7s via Zune?
sh4d0w86 said:
you would need XSPL to flash this ROM.
but if you flash this ROM you'll be unable to revert unless via Zune back-up because of OSPL.
i suggest to just XSPL, then flash a Custom ROM based on this ROM.
tutorial how to XSPL and flash Custom ROMs in my signature.
Click to expand...
Click to collapse
What u mean by xspl?
I am have 5.0 boot loader.
5.0 allow u to flash test 7004 or unshipped rom?
---------- Post added at 02:13 PM ---------- Previous post was at 02:10 PM ----------
livingspring said:
I have the TMOUS version of the HD 7 running on Mango RTM final
what would be the correct procedure for flashing this ROM?
Is it possible to downgrade to earlier versions of Mango if need be?
OS version 7.10.7720.68
Firmware;2250.21.40503.531
Bootloader;4.5.2250.0(129966)
Click to expand...
Click to collapse
If u are using 4.5 bootliader, then dont flash these roms here. Yr device will be permanently locked .
What u should do is flash a lower nodo rom, apply dft and then flash one of those custom roms based on 5.0 firmware.
And do not ever update in zune after this
Magpir said:
What u mean by xspl?
I am have 5.0 boot loader.
5.0 allow u to flash test 7004 or unshipped rom?
---------- Post added at 02:13 PM ---------- Previous post was at 02:10 PM ----------
If u are using 4.5 bootliader, then dont flash these roms here. Yr device will be permanently locked .
What u should do is flash a lower nodo rom, apply dft and then flash one of those custom roms based on 5.0 firmware.
And do not ever update in zune after this
Click to expand...
Click to collapse
What will happen if u do upate via zune?
Sent from my HD7 T9292 using XDA Windows Phone 7 App
livingspring said:
Thanks a lot
Click to expand...
Click to collapse
you're welcome.
wheresmybeaver said:
Ok if the official ROM is leaked then it's only a matter of time before the ICS driver update is rolled out to existing HD7s via Zune?
Click to expand...
Click to collapse
i am unsure, sorry.
Magpir said:
What u mean by xspl?
I am have 5.0 boot loader.
5.0 allow u to flash test 7004 or unshipped rom?
If u are using 4.5 bootliader, then dont flash these roms here. Yr device will be permanently locked .
What u should do is flash a lower nodo rom, apply dft and then flash one of those custom roms based on 5.0 firmware.
And do not ever update in zune after this
Click to expand...
Click to collapse
XSPL is R/HSPL.
no downgrading from 5.xx, yet.
permanently no? no, just at the time being until a fix is found.
already said this... why not just link to the tutorial? simpler. it is in my signature.
ginjamaka said:
What will happen if u do upate via zune?
Click to expand...
Click to collapse
not sure why Magpir said don't ever update via Zune...
but if device is unbranded, i don't believe updates will be received, so wouldn't matter.
I am having wifi issues with this radio driver, once phone goes sleep mode and after waking up the phone wifi does not work. I always need to turn off wifi and back on to make it work. Dunno if you guys have the same problem. Seems i am stuck too on this damn bootloader.
Sent from my HD7 T9292 using XDA Windows Phone 7 App
ginjamaka said:
What will happen if u do upate via zune?
Sent from my HD7 T9292 using XDA Windows Phone 7 App
Click to expand...
Click to collapse
Zune will update yr bootloader to 5.0 and thats the end.
---------- Post added at 06:03 AM ---------- Previous post was at 06:00 AM ----------
sh4d0w86 said:
you're welcome.
i am unsure, sorry.
XSPL is R/HSPL.
no downgrading from 5.xx, yet.
permanently no? no, just at the time being until a fix is found.
already said this... why not just link to the tutorial? simpler. it is in my signature.
not sure why Magpir said don't ever update via Zune...
but if device is unbranded, i don't believe updates will be received, so wouldn't matter.
Click to expand...
Click to collapse
when will a fix be found? i am not banking on this.
device can still update if u flashed an earlier stock branded rom
Magpir said:
Zune will update yr bootloader to 5.0 and thats the end.
---------- Post added at 06:03 AM ---------- Previous post was at 06:00 AM ----------
when will a fix be found? i am not banking on this.
device can still update if u flashed an earlier stock branded rom
Click to expand...
Click to collapse
u can flash a nodo rom with earlier SPL .
just installing a custom rom/ cab sender is better .
Hello.
I just downloaded the OTA update from the google servers (VQ8PQk_V.zip) and applied it.
My baseband version appeared as "Unknown", so, in my infinite wisdom, I decided to flash the XXKF1-GRK39F radio through fastboot.
The problem is that it's been stuck at "writing 'radio'..." for more than 15 mins now. What should I do?
EDIT:
I have a NANDROID backup from just before the update. If I pull out the battery and restore it, will my radio restore, too?
...why don't you flash radio via recovery ?
Ok, I solved it. Here's how:
-since I was stuck at "writing 'radio'..." I did a battery pull.
-installed the Android 2.3.6/GRK39F/XXKF1 Radio/KA3 Bootloader Flashable rom from the ALL-OTA thread.
-restored my nandroid backup
Everything's back to normal and I'm back on 2.3.6. Gonna wait for the official i9023. For a moment there, I thought I ruined my phone.
I have tried a couple of custom roms since I got this phone, but I'm not completely comfortable with everything.
huh....funny enough, I applied the update again, and this time the radio updated properly. everything works fine
Hi
I am using a Nexus S I9023 (India). I just updated my phone to 4.0.3 using the ROM file downloaded from XDA today. Now, there is no signal, it doesn't even read my sim card. It says the same msg under Baseband version, "unknown". except this everything else seems to work fine. I have not taken any back also before the upgrade.
Please help.
I do have the same problem: My Nexus S i9023 had 2.3.6 Stock ROM and after the Update, the Baseband/Network/IMEI/etc is UNKNOWN. How can I get back 2.3.6.?
rajkumar2000 said:
Hi
I am using a Nexus S I9023 (India). I just updated my phone to 4.0.3 using the ROM file downloaded from XDA today. Now, there is no signal, it doesn't even read my sim card. It says the same msg under Baseband version, "unknown". except this everything else seems to work fine. I have not taken any back also before the upgrade.
Please help.
Click to expand...
Click to collapse
Use fastboot to flash custom recovery. And then flash the full stock 2.3.6 and await the OTA.
Mopkorn said:
I do have the same problem: My Nexus S i9023 had 2.3.6 Stock ROM and after the Update, the Baseband/Network/IMEI/etc is UNKNOWN. How can I get back 2.3.6.?
Click to expand...
Click to collapse
The ota you are flashing patches the radio KF1, you guys are probably are on a different radio and the radio doesn't patch correctly.
This is the full rom ota 4.0.3, just flash and everything will work http://android.clients.google.com/packages/ota/google_crespo/ZD3PyN0t.zip[/QUOTE]
Sent from my Nexus S using xda premium
Ok I installed Custom Recovery and the .zip you posted, it seems working, thank you very much!
reddv1 said:
The ota you are flashing patches the radio KF1, you guys are probably are on a different radio and the radio doesn't patch correctly.
This is the full rom ota 4.0.3, just flash and everything will work http://android.clients.google.com/packages/ota/google_crespo/ZD3PyN0t.zip
Click to expand...
Click to collapse
Sent from my Nexus S using xda premium[/QUOTE]
you sir are correct. Fixes my signal issues
Sorry for the noob question as I can't seem to easily find the answer through search but how do you flash the this other 4.0.3 rom? Running ICS already from the other rom (VQ8PQk_V.zip).
Can I just do this again using the fastboot? Although I've tried going back to recovery and it doesn't work, as has been stated in the forum. The fixes for the recovery look complicated and require rooting (I think). I haven't rooted my i9023 yet.
jpacs2007 said:
Sorry for the noob question as I can't seem to easily find the answer through search but how do you flash the this other 4.0.3 rom? Running ICS already from the other rom (VQ8PQk_V.zip).
Can I just do this again using the fastboot? Although I've tried going back to recovery and it doesn't work, as has been stated in the forum. The fixes for the recovery look complicated and require rooting (I think). I haven't rooted my i9023 yet.
Click to expand...
Click to collapse
Yeah, fastboot should work.
Sent from my Nexus S using XDA App
oh my god....
i have upgrade my gingerbread to ICS today.
but my IMEII is missing. di don' know why.
i have nandroid backup but i don't have EFS Backup.
so, how can i get that IMEII back.
just restore backup from nandroid??
--> sorry if my english is bad..
athani said:
Use fastboot to flash custom recovery. And then flash the full stock 2.3.6 and await the OTA.
Click to expand...
Click to collapse
Thanks for the reply, the first sign of hope for my phone in 2 days!!!
I am not so familiar with these things. Can you please tell me how to do a fastboot and post a link to the 2.3.6 update that I need to use.
Thank you so much once again.
---------- Post added at 12:19 PM ---------- Previous post was at 12:12 PM ----------
Mopkorn said:
Ok I installed Custom Recovery and the .zip you posted, it seems working, thank you very much!
Click to expand...
Click to collapse
Hey
I understand that your problem is fixe. I have the same problem still can you please guide me on how to solve this problem please.
Thanks.
Hello, same problem for me but and I don't understand what is the solution...
Some says flash custom recovery, some just flash with the ZD3PyN0t.zip... and I don't even know what flashing is (if it requires rooting or not) mine is not as you can imagine...
Can someone guide me a little please ? Don't want to break my phone more than it is !
For those of us who are rooted, don't want to update parts of the OS, who want to stay on an older versions of updated OS files, or just are on a custom ROM, here is a flashable of the firmware updates (which include bootloader).
This updates your bootloader to version 3.15.
Freeza, you rule... Just saying
Sent from my Nexus 7 using Tapatalk 4
Nice work!
Quick question for you, will the bootloader and firmware updates persist after custom ROM updates or will I need to reflash each time?
for example, I'm running CarbonRom at the moment which is based on JSS15Q - I've flashed this zip without any problems but will I need to reflash it when I install the next nightly?
Cheers
Macca
It will persist. No need to reflash.
sfhub said:
It will persist. No need to reflash.
Click to expand...
Click to collapse
Cheers, that's what I thought but there was no harm in checking
BigMacca said:
Cheers, that's what I thought but there was no harm in checking
Click to expand...
Click to collapse
I should be more clear, in the example you gave, it will persist, but if you do something that will flash the bootloader like factory restore or its updates, the bootloader could change
sfhub said:
I should be more clear, in the example you gave, it will persist, but if you do something that will flash the bootloader like factory restore or its updates, the bootloader could change
Click to expand...
Click to collapse
Yeah, I should have been clearer as well - I was basically checking that custom roms don't flash the bootloader (I'd assumed that a factory restore / ota update would)
Nice to see ya here Freeza!
I am currently on [JSS15Q] - CleanROM 1.6 I am wondering if this would work with my current rom as a dirty flash? anyone tired while on CleanRom 1.6?
DC_MTP said:
Nice to see ya here Freeza!
I am currently on [JSS15Q] - CleanROM 1.6 I am wondering if this would work with my current rom as a dirty flash? anyone tired while on CleanRom 1.6?
Click to expand...
Click to collapse
No problems here DC.
D
everything seems to be going well (using FLO Kangs cm10.2 Sep 5 build) will update if anything bad happens
Does firmware mean the audio driver, sensor driver, wifi driver etc?
bland.life said:
Does firmware mean the audio driver, sensor driver, wifi driver etc?
Click to expand...
Click to collapse
No, it means bootloader, resource power manager, trusted zone.
Quick queastion , I was on JSS15J when stock, flashed ROM that says now JLS36C. If I flash this will it erase everything and do I even need to? Thanks for the help.
It won't erase any user data. Whether you want to flash is up to you. You'll get it automatically if you wait for jls36g ota.
Why is the 3.15 bootloader not available as .img file in the google recovery as always? I normally flash bootloader ONLY by using fastboot?!
Awesome!
I flashed this and my dead gold fish came back to life!
You're the man, OP!
freeza said:
For those of us who are rooted, don't want to update parts of the OS, who want to stay on an older versions of updated OS files, or just are on a custom ROM, here is a flashable of the firmware updates (which include bootloader).
This updates your bootloader to version 3.15.
Click to expand...
Click to collapse
Will this work on stock? I can't get the ota to install.
Still JSS15Q after flashing?
freeza said:
For those of us who are rooted, don't want to update parts of the OS, who want to stay on an older versions of updated OS files, or just are on a custom ROM, here is a flashable of the firmware updates (which include bootloader).
This updates your bootloader to version 3.15.
Click to expand...
Click to collapse
After successful flashing this zip-file on my rooted JSS15Q version with TWRP the Android version is still JSS15Q. That's right? I expected JSS15R.
Greetings
Zorro16
relaxxer said:
Why is the 3.15 bootloader not available as .img file in the google recovery as always? I normally flash bootloader ONLY by using fastboot?!
Click to expand...
Click to collapse
If you want the 3.15 bootloader .img to flash in fastboot, I added it to the download section of this thread:
http://forum.xda-developers.com/showthread.php?t=2448015
Zorro16 said:
After successful flashing this zip-file on my rooted JSS15Q version with TWRP the Android version is still JSS15Q. That's right? I expected JSS15R.
Greetings
Zorro16
Click to expand...
Click to collapse
This is just the bootloader that came with 15R. If you want 15R, download and flash the full rom package.
Sent from my Nexus 7 using XDA Premium 4 mobile app
So I found this on the XDA home page. It says SM-935A is required (I have SM-935U) BUT I thought that model number mostly applies to which carrier you're using...So if I flash the lates AT&T version via Odin can I then update to this Oreo build? Here's the article:
https://www.xda-developers.com/how-to-install-pre-release-android-oreo-on-the-att-samsung-galaxy-s7-s7-edge/
Thanks
KLit75 said:
So I found this on the XDA home page. It says SM-935A is required (I have SM-935U) BUT I thought that model number mostly applies to which carrier you're using...So if I flash the lates AT&T version via Odin can I then update to this Oreo build? Here's the article:
https://www.xda-developers.com/how-to-install-pre-release-android-oreo-on-the-att-samsung-galaxy-s7-s7-edge/
Thanks
Click to expand...
Click to collapse
On what firmware build are you now?
norbarb said:
On what firmware build are you now?
Click to expand...
Click to collapse
Im running the latest update on U firmware from January (ending in BRA1)
My carrier IS AT&T so I just thought I might be able to flash AT&T firmware then get the update.
KLit75 said:
Im running the latest update on U firmware from January (ending in BRA1)
My carrier IS AT&T so I just thought I might be able to flash AT&T firmware then get the update.
Click to expand...
Click to collapse
I asked the same question . I'm running the same firmware but I wont risk it.
Now im flashing the sm-g935a firmware
mhdsweidan said:
I asked the same question . I'm running the same firmware but I wont risk it.
Now im flashing the sm-g935a firmware
Click to expand...
Click to collapse
Cool. Let me know how you make out.
KLit75 said:
Im running the latest update on U firmware from January (ending in BRA1)
My carrier IS AT&T so I just thought I might be able to flash AT&T firmware then get the update.
Click to expand...
Click to collapse
You need to get to AT&T firmware first , and then flash this update.
norbarb said:
You need to get to AT&T firmware first , and then flash this update.
Click to expand...
Click to collapse
Thanks. I might hold off till there's a more stable build. If I didn't need to wipe everything I might give it a try.
But in case I change my mind, you extract the update.zip and apply update from sdcard, right?
KLit75 said:
Thanks. I might hold off till there's a more stable build. If I didn't need to wipe everything I might give it a try.
But in case I change my mind, you extract the update.zip and apply update from sdcard, right?
Click to expand...
Click to collapse
Yes, you are correct on sdcard but do not extract , just apply from sdcard
Sent from my SM-N950U using XDA Premium HD app
So I currently have it installed. The only issue I'm having so far is that the light on my heart beat sensor is lighting up whenever anything gets extremely close to it.
Dr_Liquid said:
So I currently have it installed. The only issue I'm having so far is that the light on my heart beat sensor is lighting up whenever anything gets extremely close to it.
Click to expand...
Click to collapse
Look in the oreo ota thread under guide, etc. section there is a fix posted their as well as some other fixes.
https://forum.xda-developers.com/showthread.php?t=3749891
The most recent update PPWS29.116-11-13 has OTA downloaded, but failed to install (even after factory reset). All previous updates had always installed without any problem.
I have XT1926-7 "Evert" (from Amazon) with unlocked BL, but otherwise stock un-rooted, unmodified PPWS29.116-11-11.
Could unlocked BL be a reason?
The unlocked BL can't be the reason for this. Try flash the 116-11-11 FW and just boot your device without any changes. Then you will be able to install the update.
WoKoschekk said:
flash the 116-11-11 FW
Click to expand...
Click to collapse
Why? Wha's the rationale here? It's already 116-11-11
rybshik said:
Why? Wha's the rationale here? It's already 116-11-11
Click to expand...
Click to collapse
Moto OTA update s have been failing for many model s
Seems like the only solution is to reflash the current version of firmware that phone and try OTA again
Or see is new version is posted on
https://mirrors.lolinet.com/firmware/moto
Just download the correct software channel version.
Flash with Rsd lite or fastboot.exe
Sent from my mata using XDA Labs
sd_shadow said:
reflash the current version of firmware that phone....
https://mirrors.lolinet.com/firmware/moto
Click to expand...
Click to collapse
Will EVERT_RETAIL_9.0_PPWS29.116-11-11 be good for AT&T and T-mobile frequency bands?
I do not care too much about LTE though
sd_shadow said:
Seems like the only solution is to reflash the current version of firmware that phone and try OTA again
Click to expand...
Click to collapse
I flashed "EVERT_RETAIL_9.0_PPWS29.116-11-11" with fastboot and then device OTA updated to PPWS29.116-11-13.
It works OK.
However, if go to System updates, I get the following:
System integrity is compromised
Android version: 9
Current version: PPWS29.116-11-13
Security patch: November 1, 2019
As your device system integrity is compromised is compromised, it is no longer eligible for software updates
Click to expand...
Click to collapse
So I am wondering if it might be because of (possibly) incorrect software channel? My original device software channel was and still is "retla".
Or because of the unlocked BL?
I have not made any other FW modifications nor did I root
rybshik said:
I flashed "EVERT_RETAIL_9.0_PPWS29.116-11-11" with fastboot and then device OTA updated to PPWS29.116-11-13.
It works OK.
However, if go to System updates, I get the following:
So I am wondering if it might be because of (possibly) incorrect software channel? My original device software channel was and still is "LA".
Or because of the unlocked BL?
I have not made any other FW modifications nor did I root
Click to expand...
Click to collapse
I'm not sure.
Someone else posted same warning, that had unlocked bootloader.
It's not a normal warning.
Sent from my Cosmo_Communicator using XDA Labs
sd_shadow said:
Someone else posted same warning, that had unlocked bootloader.
Click to expand...
Click to collapse
so folks need to be careful when updating to PPWS29.116-11-13
rybshik said:
I flashed "EVERT_RETAIL_9.0_PPWS29.116-11-11" with fastboot and then device OTA updated to PPWS29.116-11-13.
It works OK.
However, if go to System updates, I get the following:
So I am wondering if it might be because of (possibly) incorrect software channel? My original device software channel was and still is "retla".
Or because of the unlocked BL?
I have not made any other FW modifications nor did I root
Click to expand...
Click to collapse
Install Magisk and this message will disappear.
This a normal warning screen caused by a corrupted AVB due to your unlocked bootloader. Magisk will fix it by the AVB 2.0/dm-verity option.
WoKoschekk said:
This a normal warning screen caused by a corrupted AVB due to your unlocked bootloader..
Click to expand...
Click to collapse
Yet, there is no such warning with earlier FW versions, for example, PPWS29.116-11-11
rybshik said:
Yet, there is no such warning with earlier FW versions, for example, PPWS29.116-11-11
Click to expand...
Click to collapse
Yes, there is. Everytime I flashed a new FW and Magisk wasn't installed the system showed me this warning. As soon as Magisk is installed this error will disappear. Just try it.
Since the moto g6 plus was updated to Pie you got this error.
rybshik said:
Yet, there is no such warning with earlier FW versions, for example, PPWS29.116-11-11
Click to expand...
Click to collapse
Yes I think this is a new thing.
Sent from my mata using XDA Labs