Related
I have a question I'm hoping an expert can answer. I pretty new to the Android world so I'm trying to wrap my head around a few things..
So I bought a (prepaid/locked) S5830T from a store over here, and proceeded to unlock and upgrade to the latest
stock Gingerbread firmware (2.3.6). So now when I boot up, instead of S5830T, I get S5830. All good.
Now the phone runs fine, but I have an issue with 3G data in particular.
The "T" suffix appears to relate to the 'Telstra network' (which the phone was originally locked to).
According to this link - http://whirlpool.net.au/wiki/mobile_phone_frequencies
Telstra operates on 900Hz / 1800hz for 2G and 850hz / 2100hz for 3G.
The carrier I am on (Optus) operates on 900Hz / 1800hz for 2G and 900hz / 2100hz for 3G.
So I've flash the modem file from the Optus firmware package (Modem_S5830_XWKT3) hoping that that would enable
the 3G band that is currently not working.
(What happens ins 2G/"H" works fine, but when the phone switches to "3G" I lose all data connections)
But Alas, I still have the same problem..
So I'm wondering is there hardware in the phone that is preventing connection to the network, or do I need to find a more
appropriate Modem file that operates on the frequencies above?
Many Thanks!
BrikHaus
BrikHaus said:
I have a question I'm hoping an expert can answer. I pretty new to the Android world so I'm trying to wrap my head around a few things..
So I bought a (prepaid/locked) S5830T from a store over here, and proceeded to unlock and upgrade to the latest
stock Gingerbread firmware (2.3.6). So now when I boot up, instead of S5830T, I get S5830. All good.
Now the phone runs fine, but I have an issue with 3G data in particular.
The "T" suffix appears to relate to the 'Telstra network' (which the phone was originally locked to).
According to this link - http://whirlpool.net.au/wiki/mobile_phone_frequencies
Telstra operates on 900Hz / 1800hz for 2G and 850hz / 2100hz for 3G.
The carrier I am on (Optus) operates on 900Hz / 1800hz for 2G and 900hz / 2100hz for 3G.
So I've flash the modem file from the Optus firmware package (Modem_S5830_XWKT3) hoping that that would enable
the 3G band that is currently not working.
(What happens ins 2G/"H" works fine, but when the phone switches to "3G" I lose all data connections)
But Alas, I still have the same problem..
So I'm wondering is there hardware in the phone that is preventing connection to the network, or do I need to find a more
appropriate Modem file that operates on the frequencies above?
Many Thanks!
BrikHaus
Click to expand...
Click to collapse
Can you find the original Telstra firmware, extract the modem from that and flash it?
Can you get hold of a Telstra SIM and see if you still have the same issues?
The T doesn't necessarily signify Telstra but just a slightly different version of the S5830
It's the same with SGS2 there is a GT-i9100 and GT-i9100T (I have the T version purchased in Thailand so nothing to do with Telstra)
Because I have used this phone in Australia also, I've noticed that T modems perform better on my SGS2 than non-T versions.
I've found Optus coverage (in Melbourne) to be pathetic so I always have to ensure I'm using a T modem when I'm there.
ApriliaM3 said:
Can you find the original Telstra firmware, extract the modem from that and flash it?
Can you get hold of a Telstra SIM and see if you still have the same issues?
The T doesn't necessarily signify Telstra but just a slightly different version of the S5830
It's the same with SGS2 there is a GT-i9100 and GT-i9100T (I have the T version purchased in Thailand so nothing to do with Telstra)
Because I have used this phone in Australia also, I've noticed that T modems perform better on my SGS2 than non-T versions.
I've found Optus coverage (in Melbourne) to be pathetic so I always have to ensure I'm using a T modem when I'm there.
Click to expand...
Click to collapse
Hey, Thanks for the reply ApriliaM3.
Yeah I know the T doesn't necessarily mean Telstra, but was pretty sure it meant there was a different modem to stock (as with your SGS2).
Which is why I reverted back to stock. I thought that may have been more accommodating of all frequencies..
That's very interesting what you say regarding your T modem.
I believe I can extract the modem from my base backup, so will give that a try.
As for the Telstra sim, that might be a little harder, but I'll try the modem first and then try to get a sim.
Thanks for the info!
BrikHaus said:
Hey, Thanks for the reply ApriliaM3.
Yeah I know the T doesn't necessarily mean Telstra, but was pretty sure it meant there was a different modem to stock (as with your SGS2).
Which is why I reverted back to stock. I thought that may have been more accommodating of all frequencies..
That's very interesting what you say regarding your T modem.
I believe I can extract the modem from my base backup, so will give that a try.
As for the Telstra sim, that might be a little harder, but I'll try the modem first and then try to get a sim.
Thanks for the info!
Click to expand...
Click to collapse
I get the impression that my requirement for a T modem when I'm in Melbourne has more to do with Optus and their pathetic coverage than it has to do with the modem. When I'm in Thailand, it doesn't seem to matter what modem I use... they all get good signals and I have no problem with data either. I'm also a member on Whirlpool but I rarely go there any more... still it's quite a handy and informative site for many things
Hi all,
I am currently on stock 4.1.2 JB build of this years January.
Whenever I start my phone, the internet/data connectivity is a G, so GSM rather than H/3G. That is, until I search for networks and set it to my carrier (being 3 IRL) BUT the thing is it is actually already on 3 IRL, so it definitely isn't roaming. Why does this happen? Do I have to live with it? It never occured with a previous stock build, or Maclaws CM10.2. It's not major, it just gets really annoying. Cheers!
Aneuryst said:
Hi all,
I am currently on stock 4.1.2 JB build of this years January.
Whenever I start my phone, the internet/data connectivity is a G, so GSM rather than H/3G. That is, until I search for networks and set it to my carrier (being 3 IRL) BUT the thing is it is actually already on 3 IRL, so it definitely isn't roaming. Why does this happen? Do I have to live with it? It never occured with a previous stock build, or Maclaws CM10.2. It's not major, it just gets really annoying. Cheers!
Click to expand...
Click to collapse
Make sure Network mode is set to Auto mode or WCDMA in Settings -> More settings -> Mobile networks -> Network mode.
ImproAptoVictum said:
Make sure Network mode is set to Auto mode or WCDMA in Settings -> More settings -> Mobile networks -> Network mode.
Click to expand...
Click to collapse
It is.
Aneuryst said:
It is.
Click to expand...
Click to collapse
GSM seems to be prefered when Mobile data is off. Unless it doesnt swtich to 3G/H while using Mobile data (e.g. browsing the internet) there shouldnt be any problem.
ImproAptoVictum said:
GSM seems to be prefered when Mobile data is off. Unless it doesnt swtich to 3G/H while using Mobile data (e.g. browsing the internet) there shouldnt be any problem.
Click to expand...
Click to collapse
No, see, I permanently have my mobile data on. I have my phone off over night. When I turn it on, it is always on GSM no matter what, until I manually search networks and switch it back to 3G/H (by selecting my network)
So theoretically, GSM isn't preferred because I have 3-4 bars of 3G/H.
Aneuryst said:
No, see, I permanently have my mobile data on. I have my phone off over night. When I turn it on, it is always on GSM no matter what, until I manually search networks and switch it back to 3G/H (by selecting my network)
So theoretically, GSM isn't preferred because I have 3-4 bars of 3G/H.
Click to expand...
Click to collapse
What is your phones current baseband version, kernel version and build number?
ImproAptoVictum said:
What is your phones current baseband version, kernel version and build number?
Click to expand...
Click to collapse
Baseband version- XXAMI1
Kernel version- 3.0.31
Build number- JZO54K.I8190NXXAMJ2
Aneuryst said:
Baseband version- XXAMI1
Kernel version- 3.0.31
Build number- JZO54K.I8190NXXAMJ2
Click to expand...
Click to collapse
You might try to flash baseband from Ireland (Three) instead of the one (i assume) you are using at the moment, as it is specifically for Three.
ImproAptoVictum said:
You might try to flash baseband from Ireland (Three) instead of the one (i assume) you are using at the moment, as it is specifically for Three.
Click to expand...
Click to collapse
Alright, downloading that one now. I used that one before but had a bug where my SMS would disappear...
It's just, yes I am using that one right now, but I flashed a Three specific modem.
Aneuryst said:
Alright, downloading that one now. I used that one before but had a bug where my SMS would disappear...
It's just, yes I am using that one right now, but I flashed a Three specific modem.
Click to expand...
Click to collapse
I fully flashed (updated to) the newest firmware (ANB1) for I8190N myself without any issues with mobile network or what so ever, even it being VNZ (New Zealand Vodafone) region despite my phones initial Nordic region.
ImproAptoVictum said:
I fully flashed (updated to) the newest firmware (ANB1) for I8190N myself without any issues with mobile network or what so ever, even it being VNZ (New Zealand Vodafone) region despite my phones initial Nordic region.
Click to expand...
Click to collapse
Well, I also read that all XX firmwares work in any part of Europe regardless. I'm going to try to flash the latest AMJ2 modem now and see.
Aneuryst said:
Well, I also read that all XX firmwares work in any part of Europe regardless. I'm going to try to flash the latest AMJ2 modem now and see.
Click to expand...
Click to collapse
Yes, XX is 'international' and should work with all regions apart from Asia (ZS).
ImproAptoVictum said:
Yes, XX is 'international' and should work with all regions apart from Asia (ZS).
Click to expand...
Click to collapse
Well I just flashed the modem and the problem is still there.
If I flash that firmware with Odin, do I need to wipe data? Or can you update stock roms with a dirty flash too?
Aneuryst said:
Well I just flashed the modem and the problem is still there.
If I flash that firmware with Odin, do I need to wipe data? Or can you update stock roms with a dirty flash too?
Click to expand...
Click to collapse
Flashing it on top of stock rom with Odin would be like updating (normally no user data/apps lost), but you would however lose root and potentially custom recovery (post reboot after flash). Taking a nandroid backup prior this is advised, as always.
ImproAptoVictum said:
Flashing it on top of stock rom with Odin would be like updating (normally no user data/apps lost), but you would however lose root and potentially custom recovery (post reboot after flash). Taking a nandroid backup prior this is advised, as always.
Click to expand...
Click to collapse
Well, I have no problem rerooting and reflashing CWM as it only takes 5 minutes anyway.
I'll post the results once it's downloaded and flashed
ImproAptoVictum said:
Flashing it on top of stock rom with Odin would be like updating (normally no user data/apps lost), but you would however lose root and potentially custom recovery (post reboot after flash). Taking a nandroid backup prior this is advised, as always.
Click to expand...
Click to collapse
Alright, now it's roaming every time I reboot.. until I manually switch to 3G.
Aneuryst said:
Alright, now it's roaming every time I reboot.. until I manually switch to 3G.
Click to expand...
Click to collapse
National roaming, that is?
ImproAptoVictum said:
National roaming, that is?
Click to expand...
Click to collapse
Yes, my roaming carrier is Vodafone IE, so on boot it's always set to that instead of 3 IRL. I have it on auto mode, but theoretically WCDMA should be preferred since I have 4 bars of H right now.
Aneuryst said:
Yes, my roaming carrier is Vodafone IE, so on boot it's always set to that instead of 3 IRL. I have it on auto mode, but theoretically WCDMA should be preferred since I have 4 bars of H right now.
Click to expand...
Click to collapse
Tried choosing 3 IRL (as prefered) insted of having it select automatically in Settings -> More settings -> Mobile networks -> Network operators (-> Search networks)?
ImproAptoVictum said:
Tried choosing 3 IRL (as prefered) insted of having it select automatically in Settings -> More settings -> Mobile networks -> Network operators (-> Search networks)?
Click to expand...
Click to collapse
That's what I always have to do.
I just got my wife a Nexus 6 from Craigslist. I foolishly didn't 100% test the phone and I think I got a lemon or something.
Her phone has never connected to LTE. I've tried manually changing APNs, swapping SIM cards with my phone to see if the card is bad, checking the phone settings by dialing *#*#4636#*#*, etc... And everything is identical to my Nexus 6 with no luck. I went to a T-Mobile store just now and they couldn't figure anything out.
Two questions:
1. Is there anything else I can do to get LTE activated?
2. Can an LTE radio be damaged or disabled somehow?
I'm at my wit's end here... I'm hoping y'all can help me get it fixed.
Thanks!
1st is the phone running stock or a custom rom? .second try to reset your apn setting to default and using the setting that the phone provides in apn
It is stock, no customization or rooting.
I'll try the default when my wife gets back from the store and report back.
Reset APN to default settings, no luck.
The previous owner was on a smaller carrier, like a Metro PCS or something similar... Can't remember, but I don't know if their settings are different than T-Mobile's.
Yes their settings are diff... metro is fast.metropcs.com for apn inside and tmobile is fast.t-mobile.com. You can try clicking the apn make sure its fast.t-mobile.com and check the ipv and set to ipv6 and ipv4 for roaming. Then at the very bottom under MVNO select None. Then restart phone. If your still not pulling up data you may want to push a radio image to the device possibly and maybe the radio firmware is screwed up since your not original owner of the device.
All the APN settings are correct and identical to my working Nexus 6.
Are there tutorials on how to push a radio image and where to get said radio image?
https://www.androidpit.com/how-to-update-nexus-5-bootloader-and-radio - Nexus 5 instructions but they are the same just download nexus 6 files instead from here
https://dl.google.com/dl/android/aosp/shamu-mob30i-factory-21357b09.tgz - MOB30I Latest Marshmallow files...
When you follow that guide you could just flash-all command it and flash marshmallow stock in its entirety... it would flash latest bootloader and modem with it or you can extract the modem and bootloader files from the file and follow the guide. If you dont care whats on device you may want to just flash the whole thing and skip the extracting the modem and bootloader parts.
**Obviously since you'd be replacing the nexus 5 files with 6 files aka shamu instead of hammerhead change the names in the commands you type in fastboot. Just a reminder.
Thanks so much for the help!
I'll try this later and let you know if it works.
hermunn123 said:
Thanks so much for the help!
I'll try this later and let you know if it works.
Click to expand...
Click to collapse
No problem and best of luck on it.
hermunn123 said:
I'm at my wit's end here... I'm hoping y'all can help me get it fixed.
Click to expand...
Click to collapse
Enter into the bootloader and check the Product/Variant information within. For the US, it should read "shamu XT1103" followed by the memory size and a hexadecimal string. If it reads "shamu XT1100", you have the international model, which would explain the trouble you're having. Another possible explanation, especially if the model is "shamu XT1103", is that the device is blocked on T-Mobile.
To answer your questions:
1. If you have an international model, you may be able to activate the missing bands necessary to support LTE here in the US. Otherwise, flash the latest ROM from Google, as there are settings in the services menu you accessed which once selected cannot be changed unless a new ROM image is flashed.
2. LTE radios can both be damaged and disabled. The LTE could be disabled in the service menu, or the hardware is damaged.
Strephon Alkhalikoi said:
Enter into the bootloader and check the Product/Variant information within. For the US, it should read "shamu XT1103" followed by the memory size and a hexadecimal string. If it reads "shamu XT1100", you have the international model, which would explain the trouble you're having. Another possible explanation, especially if the model is "shamu XT1103", is that the device is blocked on T-Mobile.
To answer your questions:
1. If you have an international model, you may be able to activate the missing bands necessary to support LTE here in the US. Otherwise, flash the latest ROM from Google, as there are settings in the services menu you accessed which once selected cannot be changed unless a new ROM image is flashed.
2. LTE radios can both be damaged and disabled. The LTE could be disabled in the service menu, or the hardware is damaged.
Click to expand...
Click to collapse
I have same problem. I have XT1100 on T-Mobile, but I can only use 3G. How to see which LTE bands on this devices are activated?
If you have an XT1100 in the US you're missing bands 2, 4, 12 and 17. Of those, bands 2 and 4 are the most important as AT&T and T-Mobile both use those bands extensively. And unlike the US model, Verizon and Sprint won't work at all. Search the General forum, as there is a thread on how to add bands to the radio. Be warned however. When I attempted it on my Galaxy S4 I nearly bricked the device.
Also (and I know its basic) but check under settings ---> mobile ---> preferred network type and make sure it says LTE (just on the off chance it was switched somehow)
Hi I have lost signal due to accidentally selecting USA Band in *#*#4636#*#* menu. There is no other option other than USA band in the select radio band menu under phone info . I have tried factory reset as well as flashing the ROM after a complete wipe. I have even tried the hard brick recovery procedure. I have a one plus 3 T A3003 model from India and the phone is not being able to lock on to 2g and 3g bands only 4g seems to be working with only data and no voice. please help . thanks ?
Only way to get functions back is by changing bands again just like to did to break it, as these settings are stored in the NV registry, non of the factory restore methods will be able to restore the values back to defaults.
Update: Okey, I just went into that menu and I see three options. Auto, Europe and United States. And your saying you only see the last after you manually choose it?
I have an a3003 as well (German)
The menu on my phone shows on us frequenz
Tipping on it does not break anything 2/3/4G still works
I'm not rooted
Stock 4.0.1 OOS
pitrus- said:
Only way to get functions back is by changing bands again just like to did to break it, as these settings are stored in the NV registry, non of the factory restore methods will be able to restore the values back to defaults.
Update: Okey, I just went into that menu and I see three options. Auto, Europe and United States. And your saying you only see the last after you manually choose it?
Click to expand...
Click to collapse
Yes I only see US. I am on stock 4.0 nougat . you are on which rom ?
I also went back to 3.5.4 where i could see options like band 30, band 31 etc. but choosing any of them did not help.
thanks
ask77 said:
Yes I only see US. I am on stock 4.0 nougat . you are on which rom ?
I also went back to 3.5.4 where i could see options like band 30, band 31 etc. but choosing any of them did not help.
thanks
Click to expand...
Click to collapse
I'm on Lineage OS 14.1, but with OxygenOS 4 firmware/bootloader base.
Ok I have found a solution. I reverted back to os 3.5.1 using the unbrick guide from https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306 . Now there are options such as band 31 , band 32 etc. in addition to u.s. band now I started applying each and every band, the trick here is that the applying each band takes at least 1 - 2 mins. so you have to wait after each operation to see if the problem is corrected or not. Finally the problem got corrected on applying band 43 , so band 43 seems to be the correct configuration at least here in India . now 2g,3g and 4g all are working. the strange part is that in nougat service menu this is missing while it is present in the earlier rom's . Thanks
Band 28 can be force enabled via Network Signal Guru and works, but it does not persist upon exiting the app.
Is there any method to do so permanently?
So far:
1) "EfsTools.exe setModemConfig -p lte.json" does not work with either the WW or CN+b28 configs.
2) QPST 2.7 does not read the modem configs properly
3) QXDM does not read the LTE files, returns an error. Also the newest version on xda appears to be from 2009.
4) DFS tools fails to do anything. It reads all bands as active and setting bands to write didnt do anything
5) network signal guru settings do not persist upon exiting the app, but can be used to temporarily enable b28 for testing purposes. For best results, disable all other LTE bands.
6) /policyman/ files do not contain anything pending to band28, using "<include> 28 </include>" in carrier_policy_original.xml_Subscription01 does nothing.
7) band 28 is apparently enabled by default on SIM2 (thanks @attachsnow ), but this is incompatible with homerSP's VoLTE/VoWi-FI guide???
I suspect there's a hidden file that temporarily overwrites the main config files every boot, bit i lack the skill to find out. Either that, or SIM1 has some special configs or hardware issues with B28 that SIM2 does not
Have the same problem here. I found that sim 2 can use band 28 but not in sim 1.
Could you share more information for this?
Maybe we can found some files in vendor folder that is the same as country value.
attachsnow said:
Have the same problem here. I found that sim 2 can use band 28 but not in sim 1.
Could you share more information for this?
Maybe we can found some files in vendor folder that is the same as country value.
Click to expand...
Click to collapse
I'm no android developer, just a "power user" at best. I merely tested every guide for enabling VoLTE or bands for any android phone on xda I could find. I wouldn't have the skill to make up a new method.
Band 28 is detected on SIM2 without needing network guru app's lock, but i cannot get the VoLTE guide to work with it. Guess it's still something, maybe we can force volte on sim2.
I've tried a bunch of things to enable bands myself, including band 28, but I have yet to find a solution - anything I do just seems to revert when rebooting and I have no clue what causes that.
I have updated EfsTools to allow writing the settings for the second SIM, you can find it here: https://github.com/HomerSp/EfsTools/releases/tag/0.10-modded-1.2.
Simply download that, and run this, and you should be good to go on the second SIM slot (no need to re-run the other commands):
Code:
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -s 1
Now I'm wondering what restrictions are on SIM2 as it appears to only detect 3g b5 and 4g b28? I will test a bit further
deltarz said:
Now I'm wondering what restrictions are on SIM2 as it appears to only detect 3g b5 and 4g b28? I will test a bit further
Click to expand...
Click to collapse
Seems to work fine here, though I get the same exact bands enabled as I do on SIM1, so there's sadly no difference there.
Small update: I'm not entirely sure we can completely trust the list of LTE bands listed Network Signal guru. I say this because toggling the bands there doesn't seem to do anything, but more importantly, I modified /policyman/carrier_policy.xml and removed the LTE band I'm usually connected to (B1) and rebooted. After booting again it would no longer connect to LTE, but this wasn't reflected at all in Network Signal Guru - it still had all bands except 28 ticked.
As a test you could try writing this to efs:
https://gist.github.com/dc57c830fef5a0690709b3a95842bafa
Code:
EfsTools.exe writeFile -i carrier_policy.xml -o /policyman/carrier_policy.xml
That will disable all bands except B28. My carrier doesn't support that band, so I can't check if it works myself.
Here's the stock carrier_policy.xml if you want to restore it after testing:
https://gist.github.com/cb4cd5114013add0432eeb1afdc26ce9
HomerSp said:
Small update: I'm not entirely sure we can completely trust the list of LTE bands listed Network Signal guru. I say this because toggling the bands there doesn't seem to do anything, but more importantly, I modified /policyman/carrier_policy.xml and removed the LTE band I'm usually connected to (B1) and rebooted. After booting again it would no longer connect to LTE, but this wasn't reflected at all in Network Signal Guru - it still had all bands except 28 ticked.
As a test you could try writing this to efs:
https://gist.github.com/dc57c830fef5a0690709b3a95842bafa
Code:
EfsTools.exe writeFile -i carrier_policy.xml -o /policyman/carrier_policy.xml
That will disable all bands except B28. My carrier doesn't support that band, so I can't check if it works myself.
Here's the stock carrier_policy.xml if you want to restore it after testing:
https://gist.github.com/cb4cd5114013add0432eeb1afdc26ce9
Click to expand...
Click to collapse
I agree. Well, it's not that important anymore but, Network Signal Guru's bands do not apply to SIM2. It still shows B28 as disabled. Forcing toggles do nothing to anything in SIM2 besides forcing a reconnect on both SIMs. That and how the bands never persist upon exiting the app for SIM1 does imply that it can't be trusted whenever things are changed.
Anyway, I can connect to b 3,5,7 & 28 for 4G just fine, which is all of Telstra. They do have some rare b1 & b8 sites but I don't know where they are to test that. However, I would assume they work. 3G is harder to test as they only use B3.
If you need any further testing on B28 matters, let me know.
For now, the SIM2 workaround is good enough. Highly doubt there'll come a time where the SIM2 slot dies before anything else breaks or the phone is replaced, or the situational requirement of two B28 SIMs.
If we use Network Signal guru to check B28 only on sim 1 slot, use NetMonster app that it shows B28 is connected.
But there is no CA with B28. So it has a little difference with sim 2 slot.
Is there any update?
If I root my phone, will network guru open band 20 on my UK version phone?
On kimovil site they say the tencent ultimate version (512gb/12gb) ram has all bands, including 28 and MiMO 4x4. Anyone can confirm this, please? Thanks in advance! ROG Phone 2 512gb/12gb on Kimovil
Had B28 working with WW rom on Tencent phone in second sim slot. Now updated to Android 10 second slot fix is broken, that band is gone now.
I fastboot back to Android 9 with raw rom and that didn't bring back b28. Have no idea where to go from here, I was relieved to finally have 4G where I live.
onlyadequate said:
Had B28 working with WW rom on Tencent phone in second sim slot. Now updated to Android 10 second slot fix is broken, that band is gone now.
I fastboot back to Android 9 with raw rom and that didn't bring back b28. Have no idea where to go from here, I was relieved to finally have 4G where I live.
Click to expand...
Click to collapse
Yes, I found that android 10 will let second slot missing Band 28. Could you share your flash back android 9 method? Are you using one raw file or 21 img file? Thank you.
attachsnow said:
Yes, I found that android 10 will let second slot missing Band 28. Could you share your flash back android 9 method? Are you using one raw file or 21 img file? Thank you.
Click to expand...
Click to collapse
Went to this thread and downloaded the first WW raw https://forum.xda-developers.com/rog-phone-2/how-to/1910-64-ww-update-t4021947 put phone into fastboot mode, flashall_AFT.cmd back to Android 9. Note that my bootloader is locked, but from looking around it seemed like I didn't need to unlock it to roll back.
Sorry don't know what 21 image file is, I'm new to this stuff.
onlyadequate said:
Went to this thread and downloaded the first WW raw https://forum.xda-developers.com/rog-phone-2/how-to/1910-64-ww-update-t4021947 put phone into fastboot mode, flashall_AFT.cmd back to Android 9. Note that my bootloader is locked, but from looking around it seemed like I didn't need to unlock it to roll back.
Sorry don't know what 21 image file is, I'm new to this stuff.
Click to expand...
Click to collapse
Could you please provide fastboot.log file after you rollback?
Maybe we could see which file cannot flash back.
attachsnow said:
Could you please provide fastboot.log file after you rollback?
Maybe we could see which file cannot flash back.
Click to expand...
Click to collapse
Here's the log file
https://pastebin.com/acCDD66i
onlyadequate said:
Here's the log file
https://pastebin.com/acCDD66i
Click to expand...
Click to collapse
Hi, just a guess. Have you ever try flash CN android 9 Rom again then flash back to WW?
attachsnow said:
Hi, just a guess. Have you ever try flash CN android 9 Rom again then flash back to WW?
Click to expand...
Click to collapse
I've thought about flashing back to cn, but haven't done it yet. Use a different phone now but I'll try your idea sometime