This is just for a simple discussion. I've tried flashing the open beta, and since Developer Preview 4 I've not been able to get service. Flashing other modem versions ends up breaking the phone. The new modem is also ~ half the size of the old versions.
Anyone had any luck?
I'm on DP4, should I back up my modem before updating?
Edit: It works perfectly for me on TMobile converted.
Dameon87 said:
This is just for a simple discussion. I've tried flashing the open beta, and since Developer Preview 4 I've not been able to get service. Flashing other modem versions ends up breaking the phone. The new modem is also ~ half the size of the old versions.
Anyone had any luck?
Click to expand...
Click to collapse
Did you flash Global 10.5.12 first?
I can't get any 5G with global or beta. Might need to see what's going on when I return to stock.
shaneg79 said:
Did you flash Global 10.5.12 first?
Click to expand...
Click to collapse
Yes, I flashed 10.5.12 first then did a local upgrade to open beta 1. No service at all on reboot.
Dameon87 said:
Yes, I flashed 10.5.12 first then did a local upgrade to open beta 1. No service at all on reboot.
Click to expand...
Click to collapse
Did you backup your modem before?
shaneg79 said:
Did you backup your modem before?
Click to expand...
Click to collapse
No, I've tried flashing the modem from 10.5.12 from fastboot as extracted from the payload.bin
Dameon87 said:
No, I've tried flashing the modem from 10.5.12 from fastboot as extracted from the payload.bin
Click to expand...
Click to collapse
Then you will have to flash back to the T-Mobile firmware and upgrade to 10.5.20 then reunion bootloader backup your modem and everything then covert
I have my tmobile op8 on the open beta and this was the only way I was able to have service.
1. Msm to tmobile 10.5.7
2. Flash unlock token
3. Unlock bootloader
4. Flash global 10.5.7 (I still had service at this point, and I did not flash any modem)
5. Downloaded oxygen updater apk from chrome (to avoid restoring everything from the Google play store just yet)
6. Updated to 10.5.12
7. Switched oxygen updater settings to download open beta and then flashed from system settings (still had service, no modem flash)
8. Reset the phone from settings (to go through set up and restore all my data from play store)
This was just what I had done and it did work for me so good luck if you decide to try. I only did the chrome apk file for oxygen updater to avoid having a bunch of data on my phone when going to the beta. I haven't had any weird bugs and it's been smooth for me
Not sure why some are having this issue, I have signal with no issues on beta. I was on .12 and went to beta.
I had this issue on my other OnePlus 8, a data wipe fixed my signal entirely.
Dameon87 said:
Yes, I flashed 10.5.12 first then did a local upgrade to open beta 1. No service at all on reboot.
Click to expand...
Click to collapse
That sucks. I was on 10.5.12 a couple nights ago. Decided to try DP4 because all the hype about copying OneUI was making me interested. I loved OneUI on all my Samsung devices. Missed it actually!
When I flashed DP4 I loved it. I checked this morning for Beta 1 OTA after seeing it was out. It downloaded and installed. No issues at all. I have not rooted or anything else.
The only thing I did diff was I was on DP4 before OB1. However, this really should not matter. The beta is expected to be flashed from 10.5.x AFAIK so that should not be the problem.
What's weird about this phone though, I am always seeing people reporting issues with signal after flashing. I dont get it. I have yet to loose signal. Not to say I have not had ****ty signal, thats just T-Mobile where I am at. But I can say with the latest T-MO update and the latest Beta 1 I can hit almost 100 megs down. Before these updates I was getting about 10 megs. ON all devices in my house on all carriers known to man. Occasionally I could get 11 megs down
pro_granade said:
I'm on DP4, should I back up my modem before updating?
Edit: It works perfectly for me on TMobile converted.
Click to expand...
Click to collapse
Yep, me too! I was pretty happy to have good speeds, and the latest OOS.
Ok I'm on 10.5.20 do I need to downgrade first or can I flash straight to global 10.5.12
Related
I modified some files for @LeeDroid rom for sprint support prior to sprints nougat ota and posted the download link in his thread but I'm not sure how often other sprint users check his thread being that sprint support wasn't available. If interested in testing to verify before the edits get fully implemented into the rom build please let me know if there are any issues.
***Thread has been updated for Sprint Oreo Support. This thread is for sprint users to report bugs with the sprint specific components of the ROM for me to troubleshoot to lessen the work on Lee since he isn't on the Sprint network. Also with new Sprint updates I will post test zips here because devices act differently and I want to be sure that the fixes/tests I build work for everyone.***
DISCLAIMER
I, nor any of the developers involved, are not liable for any damages that may occur to your device as a result of flashing. Flash at your own risk. I have this version running currently and have had no issues.
Big thanks to @LeeDroid for putting up with my pestering for sprint support and for challenging me to get it done
Thanks to @Captain_Throwback for file location guidance and for the use of his apktool when mine was being fussy, and for the use of his Sprint APNs.
Download Test 1 - Failed attempt, thanks to all who tested and let me know that it was broken. Don't use this one
https://www.androidfilehost.com/?fid=529152257862696764
MD5 6495ccb05ec3886306aad7dbc7088f28
Test 2 was never publicly released. I had multiple test 2's
Download Test 3 - Fresh out the oven. Clean flashed (format data in twrp) and booted, restored most of my settings over mobile data without having to edit any apns, didn't have statusbar clock for a little bit which was weird but it showed up, maybe it was taking a nap . Give it a try and let me know.
https://www.androidfilehost.com/?fid=673368273298925530
MD5 0a61e3fbdad51e4fa3d0ada511606f72
Install procedure
1. Clean start in twrp (full wipe)
2. Flash sprint test zip
3. In aroma select Sprint
This is where I edited the necessary files for sprint data to connect
4. Make selections in aroma for options as you normally would
5. Let install finish
6. Reboot
6.5 Don't worry about the boot animation, personally I prefer the stock Android so that's what it is
7. Wait
8. Wait
9. Profit? Hopefully
gstanke said:
I modified some files for @LeeDroid rom for sprint support prior to sprints nougat ota and posted the download link in his thread but I'm not sure how often other sprint users check his thread being that sprint support wasn't available. If interested in testing to verify before the edits get fully implemented into the rom build please let me know if there are any issues.
<c> <b> DISCLAIMER </b> </c>
I, not any of the developers involved, are not liable for any damages that may occur to your device as a result of flashing. Flash at your own risk. I have this version running currently and have had no issues.
Big thanks to @LeeDroid for putting up with my pestering for sprint support and for challenging me to get it done
Thanks to @Captain_Throwback for file location guidance and for the use of his apktool when mine was being fussy
Click to expand...
Click to collapse
Sprint user here. Will test soon as I get a chance.. what TWRP version is necessary? Does it matter what firmware I'm currently on? Thanks!
Lurien said:
Sprint user here. Will test soon as I get a chance.. what TWRP version is necessary? Does it matter what firmware I'm currently on? Thanks!
Click to expand...
Click to collapse
I haven't updated firmware to most recent yet since it was a security update I didn't feel the need and currently my twrp version is 3.0.2-6 I believe
gstanke said:
I haven't updated firmware to most recent yet since it was a security update I didn't feel the need and currently my twrp version is 3.0.2-6 I believe
Click to expand...
Click to collapse
Great! Thanks again..
gstanke said:
I haven't updated firmware to most recent yet since it was a security update I didn't feel the need and currently my twrp version is 3.0.2-6 I believe
Click to expand...
Click to collapse
Sprint here as well, I will test too, thanks!
GROOVYJOSHCLARK said:
Sprint here as well, I will test too, thanks!
Click to expand...
Click to collapse
Should flash fine and provide a working data connection
gstanke said:
Install procedure
1. Clean start in twrp (full wipe)
2. Flash sprint test zip
3. In aroma select <b> US UNLOCKED </b>
This is where I edited the necessary files for sprint data to connect
4. Make selections in aroma for options as you normally would
5. Let install finish
6. Reboot
6.5 Don't worry about the boot animation, personally I prefer the stock Android so that's what it is
7. Wait
8. Wait
9. Profit? Hopefully
Click to expand...
Click to collapse
dude!!! awesome!! ive been waiting and wishing ice or leedroid would support sprint with their N builds! trying this now
deakelem said:
dude!!! awesome!! ive been waiting and wishing ice or leedroid would support sprint with their N builds! trying this now
Click to expand...
Click to collapse
Any update? Hopefully everything is good to go
Sprint User Too
I'm a sprint user as well and have been waiting for something like this (impatient waiting for sprint upgrade) will test and post results.
JhoonB51 said:
I'm a sprint user as well and have been waiting for something like this (impatient waiting for sprint upgrade) will test and post results.
Click to expand...
Click to collapse
I finished the edits last night and so far have had no issues but since Lee doesn't have a sprint device for testing I figured this was the best way, if everything is good the edits will be merged into the main rom
I'll try it later but the download speed is poop. Says I have 5 days left. I'll try to download later.
gstanke said:
Any update? Hopefully everything is good to go
Click to expand...
Click to collapse
I flashed like the directions said but the phone sat at the "android" boot logo for at least 30 minutes before i restored a backup. I tried flashing a second time too with certain options not selected (such as using the stock kernel this time) and the same thing happened. should i wait longer?
deakelem said:
I flashed like the directions said but the phone sat at the "android" boot logo for at least 30 minutes before i restored a backup. I tried flashing a second time too with certain options not selected (such as using the stock kernel this time) and the same thing happened. should i wait longer?
Click to expand...
Click to collapse
I did not have that issue.
Try flashing, letting sit at Android screen again if it doesn't boot try dirty flashing over top
I had formatted data through twrp and run unencrypted
Also what selections did you choose? Mmfirmware? Root method?
gstanke said:
I did not have that issue.
Try flashing, letting sit at Android screen again if it doesn't boot try dirty flashing over top
I had formatted data through twrp and run unencrypted
Also what selections did you choose? Mmfirmware? Root method?
Click to expand...
Click to collapse
hmmm.. so i selected the MM firmware options but the only thing i did different from you was I selected encryption each time. I will try again while setting encryption to disabled.
deakelem said:
hmmm.. so i selected the MM firmware options but the only thing i did different from you was I selected encryption each time. I will try again while setting encryption to disabled.
Click to expand...
Click to collapse
Format data in twrp beforehand to be able to run unencrypted, which version of twrp are you using
gstanke said:
Format data in twrp beforehand to be able to run unencrypted, which version of twrp are you using
Click to expand...
Click to collapse
yup yup, did that already. just flashed and now its booting.
Update: just an update, it is still booting and is at the android logo, 15 mins so far. I will continue to wait another 30 mins or so
deakelem said:
yup yup, did that already. just flashed and now its booting.
Update: just an update, it is still booting and is at the android logo, 15 mins so far. I will continue to wait another 30 mins or so
Click to expand...
Click to collapse
same results after 30 mins. I even tried not selecting any options other than us unlocked and the stock kernel, and disabled encryption, still had the same result. It sits at the android logo during boot up for a while and will reboot once and sit there again. Anyone else seeing any problems like this?
deakelem said:
yup yup, did that already. just flashed and now its booting.
Update: just an update, it is still booting and is at the android logo, 15 mins so far. I will continue to wait another 30 mins or so
Click to expand...
Click to collapse
I am having the same results, stayed at android logo for well over an hour and would go no further. I chose mm firmware, run unencrypted (been unencrypted long time) twrp 3.0.3....went back to 2.71
Based on the comments I wasn't alone in this issue but I haven't seen a fix. I even went so far as to use the MSM tool to no avail. Any suggestions on how I can get this thing back to life?
Flash lineage over 10.0.3 oos. Or one of the betas. It's weird it's like after I msm tool back to 9.5.3 I don't have or won't have cell service until I updated regular way to 10.0.3. and regular way I mean by system - system update. Or do the load local in system update
amaroney55 said:
Flash lineage over 10.0.3 oos. Or one of the betas. It's weird it's like after I msm tool back to 9.5.3 I don't have or won't have cell service until I updated regular way to 10.0.3. and regular way I mean by system - system update. Or do the load local in system update
Click to expand...
Click to collapse
Whenever I flash a rom an I ain't got no wifi or cell sign I can usually jus flash a custom Kernel an get it all back works Everytime for me
billyt1 said:
Whenever I flash a rom an I ain't got no wifi or cell sign I can usually jus flash a custom Kernel an get it all back works Everytime for me
Click to expand...
Click to collapse
Ok when you say custom kernell are you meaning like the Smurf kernel, ummm sky dragon in that sort. I haven't really had a chance to ask til now. Why I ask is for 2 reasons I have read where some call a partition a kernel. And when I first got my 7 pro last yr right before the q beta came. Tmo I was doing the international msm tool but I found away and til this day I can msm tool my other 7 pro with 9.5.3 and it will keep the network everything. But now I can not find the xda forum I read it at. And can't member what I did to make it stick like that. Our 7 pro forum has came along way.
amaroney55 said:
Ok when you say custom kernell are you meaning like the Smurf kernel, ummm sky dragon in that sort. I haven't really had a chance to ask til now. Why I ask is for 2 reasons I have read where some call a partition a kernel. And when I first got my 7 pro last yr right before the q beta came. Tmo I was doing the international msm tool but I found away and til this day I can msm tool my other 7 pro with 9.5.3 and it will keep the network everything. But now I can not find the xda forum I read it at. And can't member what I did to make it stick like that. Our 7 pro forum has came along way.
Click to expand...
Click to collapse
Yeah a custom kernel. The kernel will have its own partition jus like system ,data, modem, etc,etc, they are all partitions of the device. It would be more like kernel partition system partition data partition. You'd jus leave out the partition part so you didn't have to say 10 times
Hey guys, has anybody tried the new OOS12 on a tmobile variant yet and works fine?
I tried the first oos12 on my globally converted tmobile and it wont read the sim card at all.
Thanks!
infamousvincci said:
Hey guys, has anybody tried the new OOS12 on a tmobile variant yet and works fine?
I tried the first oos12 on my globally converted tmobile and it wont read the sim card at all.
Thanks!
Click to expand...
Click to collapse
C39 is really nice. Need to be on Beta 1 and updated to latest. Super stable and battery life has been the best I've seen on this 9 yet. Faced UI issues while watching Netflix. Dual hole punch out at top of screen on either side and near halfway bleeding black arches. Once Netflix closes it stays on screen for a few seconds then goes away. That's really the only issue I had on C39. BTW, 9(non pro) TMobile converted to Global. Everything works fine,no data issues or anything
avid_droid said:
C39 is really nice. Need to be on Beta 1 and updated to latest. Super stable and battery life has been the best I've seen on this 9 yet. Faced UI issues while watching Netflix. Dual hole punch out at top of screen on either side and near halfway bleeding black arches. Once Netflix closes it stays on screen for a few seconds then goes away. That's really the only issue I had on C39. BTW, 9(non pro) TMobile converted to Global. Everything works fine,no data issues or anything
Click to expand...
Click to collapse
Are you rooted or youre running stock? Im thinking of jumping straight to it from oos 11.
infamousvincci said:
Are you rooted or youre running stock? Im thinking of jumping straight to it from oos 11.
Click to expand...
Click to collapse
Are you running 11.2.9.9?
TMO EU MSM conversion back to stock,
Speed through set up and Unlock bootloader ,
Update to 11.2.9.9
Install OB1 and use wifi to update to C.39,
Understand that data will be iffy the first 2 Betas but should catch later during install,
Once updated to C.39,factory reset(optional) and let sit. Data will catch after a moment.
Every reboot data will stick,just takes a bit.
I run it rooted with patching boot.img and run magisk v23 no issues
No need to use TMO MSM anymore. I haven't used it in a long time. I always stay converted so I use the conversion MSM always
avid_droid said:
No need to use TMO MSM anymore. I haven't used it in a long time. I always stay converted so I use the conversion MSM always
Click to expand...
Click to collapse
Hmmm. Gotcha gotcha! Lemme try it tomorrow. Ill try to update through the official way haha. Thanks man!
infamousvincci said:
Hmmm. Gotcha gotcha! Lemme try it tomorrow. Ill try to update through the official way haha. Thanks man!
Click to expand...
Click to collapse
No problem
As the title says OnePlus open beta 2 has been released. However on ob1 the Verizon users lost data/internet. My question is. Is anyone out here on an Na op9 using a Verizon sim and getting data. Last ob1 build was righteous and am excited for oxygen 13 they call it. But requires a data wipe if not, the rollback package that is. I hate starting over.
https://community.oneplus.com/thread?id=1184353608213725185 [OxygenOS 13 Open Beta 2 for the OnePlus 9/9 Pro]
I m using ob2 still data not working without magisk fix
Maybe you should back up and factory reset. I have everything working on Ob2. 5g ,Volte,almost all apps fine now. Only play store update broken still. I don't care about that. I love new OOs so much better than what they handed us for A12
mattie_49 said:
Maybe you should back up and factory reset. I have everything working on Ob2. 5g ,Volte,almost all apps fine now. Only play store update broken still. I don't care about that. I love new OOs so much better than what they handed us for A12
Click to expand...
Click to collapse
Yes my data is working too but at start i lost all signals but working good right now will keep testing if there is any issue with mobile data or signals then i will finalize
Hi,
My Xiaomi 12 still hasn't gotten an new update and is stuck on MIUI 13.0.27.0( SLCEUXM) with security patch of oktober 2022.
I would like to get to the latest miui 14 and would like to know what is the best way to manually update this safely with a original ROM?
Should I do this incrementally start at MIUI 13.2.6.0 and then go to the next till I get to the latest or can I just update to the latest MIUI 14 directly?
Tnx
Gradually is the safest method.
Skipped the Beta stables.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Thank you for the quick response.
I downloaded the MIUI downloader app are those ROMS good to?
I need to choose for a recovery ROM and then I can install it with the updater app right? So starting with version MIUI 13.2.6.0 would be the safest?
Downloaded from the site I told you, if the downloaded choice 'incremental update in yellow'.
Then go to OTA, 3 points at the top right, install update (if this does not appear, tap the Miui logo several times).
If it works, try OTA first.
NOSS8 said:
Downloaded from the site I told you, if the downloaded choice 'incremental update in yellow'.
Then go to OTA, 3 points at the top right, install update (if this does not appear, tap the Miui logo several times).
If it works, try OTA first.
Click to expand...
Click to collapse
You mean this one right?
It says it's only around 80mb is that correct?
When it's for a update from Android 12 to Android 13.
Error on my part, take the full rom.
it's the first A13 before yours.
If that doesn't work, download the incremental update of the current rom and then check if an update is offered.
NOSS8 said:
Error on my part, take the full rom.
it's the first A13 before yours.
If that doesn't work, download the incremental update of the current rom and then check if an update is offered.
Click to expand...
Click to collapse
So I tried to install the stable recovery ROM MIUI 13.2.6.0.TLCEUXM but it didn't work I keep getting this message "can't verify update can't flash this stable rom"
Then I tried a newer version recovery ROM MIUI 14.0.5.0.TLCEUXM but same message.
Also tried your suggestion to use the incremental update of the current ROM V13.0.27.0 but then I got the message "can't verify update can't downgrade ROM version"
Do you have any other ideas on how to fix this problem?
Try to change region (Belgium/Usa/change continent/country) and restart afterwards.
Then turn on WiFi and check for updates.
====================================
or unlock the bootloader and you can install any stock or custom rom.
NOSS8 said:
Try to change region (Belgium/Usa/change continent/country) and restart afterwards.
Then turn on WiFi and check for updates.
====================================
or unlock the bootloader and you can install any stock or custom rom.
Click to expand...
Click to collapse
Tried changing the continent/country and turn wifi back on after restart but no updates were found.
I really didn't want to try messing with the bootloader because of the warranty. I also read somewhere Google play services and bank apps not working when its unlocked.
Anything more I could try without unlocking?
Jappie3 said:
Tried changing the continent/country and turn wifi back on after restart but no updates were found.
I really didn't want to try messing with the bootloader because of the warranty. I also read somewhere Google play services and bank apps not working when its unlocked.
Anything more I could try without unlocking?
Click to expand...
Click to collapse
Nope, you can re-lock the bootloader after installing the stock rom.
No need with a Xiaomi Eu rom (certified play store, everything works).
NOSS8 said:
Error on my part, take the full rom.
it's the first A13 before yours.
If that doesn't work, download the incremental update of the current rom and then check if an update is offered.
Click to expand...
Click to collapse
Only thing I haven't tried, is using the incremental update of that version V13.2.6.0 because it was only 80 mb. If I try this update and it works will it then download the ROM information on it's own or something?
Jappie3 said:
Only thing I haven't tried, is using the incremental update of that version V13.2.6.0 because it was only 80 mb. If I try this update and it works will it then download the ROM information on it's own or something?
Click to expand...
Click to collapse
Nope,only solution unlock the bootloader.
Just to be sure I downloaded the 2 latest versions that I hadn't tried yet.
The recovery ROM of version MIUI 14.0.7.0.TLCEUXM and 14.0.8.0.TLCEUXM.
And they both seem to work
Since I'm still on Android 12 now and missed so many updates in-between these 2 latest versions. Would it be safe to install one of these?
Doesn't matter, it will work or not.
Note that if you have a bootloop afterwards, with the bootloader locked you will have to pay to recover your phone (this sometimes happens).
NOSS8 said:
Doesn't matter, it will work or not.
Note that if you have a bootloop afterwards, with the bootloader locked you will have to pay to recover your phone (this sometimes happens).
Click to expand...
Click to collapse
So it's not safe to just install one of these recovery versions manually with the updater?
Jappie3 said:
So it's not safe to just install one of these recovery versions manually with the updater?
Click to expand...
Click to collapse
Never at 100% with forcing.
EDIT:moreover, even regular updates via OTA can lead to a bootloop.
NOSS8 said:
Never at 100% with forcing.
EDIT:moreover, even regular updates via OTA can lead to a bootloop.
Click to expand...
Click to collapse
So it's just a risk of updating no matter what version I use. I never had a boot loop before.
Jappie3 said:
So it's just a risk of updating no matter what version I use. I never had a boot loop before.
Click to expand...
Click to collapse
Zero risk does not exist and this risk increases when you force the update by skipping versions.
NOSS8 said:
Zero risk does not exist and this risk increases when you force the update by skipping versions.
Click to expand...
Click to collapse
Oke, yeah I wanted to do it step by step till I got to the latest miui 14 and still don't get why the older versions don't work.
The only older version I could find that also worked was version V13.0.33.0.SLCEUXM but can't find much about that update.
Logical sequence