Just received this fine device. However, all apps on it are in chinese - they don't respond to language change.
Code:
A0001
A0001_12_150511
ColorOS 1.2.0
Baseband Q_V1_P14
So I immediately started looking into flashing a custom ROM.
However, I'm not sure if I can just go ahead and do it.
I found this guide. Does it apply to all OPO versions?
For future reference: yes, the guide applies.
I successfully installed TWRP and migrated from 4.3 to 5.1 ROM (installed 5.1 radio too, naturally), all in one go.
Lots of anxiety in between though
Related
Hi,
I have a the WiFi only Xoom (MZ604), which came with the "Build H.6.2-24 for Retail Other International" ROM (got it on Amazon) on it. I flashed it with the US ROM, and rooted it using this guide. I was looking around, trying to find a way to get my Android version from 3.0.1 to 3.2.1 (which I had on there before the initial US-ROM flash, and I found this guide.
My question is, can I use this guide to upgrade my Android version (preferably without losing all my data)? Or would I have to flash back to the original US ROM before I begin?
I'm kinda new to Android and tablets, but I do know my way around a command line just fine..
With your link, it's an update so you won't lose data.
Although, I'd recommend flashing us stock (like you did) and upgrading via OTA .. then rooting afterwards. You'll probably be on ICS. Seems like the most hassle-free solution to me.
Yup, that's pretty much what I did.. Flashed it back to the original US stock, updated OTA all the way to 4.0.3, then r00ted. Thanks for your reply
Excuse my ignorance but this is the first device I have rooted, installed twrp (find it easier than cwm) and installed a custom rom. I successfully rooted days ago and decided to see what all the hype about the omega rom was about. I installed v10 for my gt19505 s4. It worked perfectly (after I installed the wifi fix) and I absolutely love the rom. Then a new release v11 came out a couple of days later. Now I was sceptical about flashing this new version because it says it is based on firmware ZHUMDH6. Now this is where my inexperience shows. I installed v10 because it was based on firmware XXUBMH1. when I type the code *#1234# into my phone this is what it states I have. I thought that had to be the file I downloaded to exactly match my phone. Than I went on to read comments by people stating they installed v9 than v10 and so on so I started thinking maybe they are all for the gt19505 and just BASED on the firmware and not a requirement for you phone to match that firmware.
Is this correct?? As I stated it is working well (occasional pause and stutter at first but nothing that a reboot didn't fix- and wifi is working without the fix) So do I need to match the roms exactly to what that code stated (*#1234#) or just my model - ie gt-19505 international
Hope this makes sense
Hello all,
tl;dr: Location-UK. Rooted MotoG and installed CM11, found that the mobile network connectivity is gone. Flashed EU spec stock 5.0.2, still no luck. Status says Radio is off. What can I do to salvage it? (Still shows the correct IMEI).
Long story:
- I had a terribly slow, practically unusable (GB Retail spec) Moto G running on 5.0. So I decided to roll back to 4.4.
- Unlocked the bootloader successfully, but couldn't root it following the easy procedures listed widely everywhere. In the process, somehow rendered the 'sdcard' storage read-only.
- Rooted successfully using another method specifically written for Lollipop MotoG. A restart after that made the 'sdcard' read-write again.
- Installed TWRP from Playstore and tried backing up the ROM, but after backing up, the phone went into a boot-loop.
- Tried flashing a US Retail spec 4.4 to get out of the boot-loop, didn't work.
- Flashed TWRP via fastboot, pushed CM11 with adb and flashed. Finally it worked!
- But, no network. If I search manually for networks, it throws up an error. Sometimes even the Networks option was grayed out.
- Tried flashing the GB spec radio zip, no change.
- Wiped it all, tried flashing stock 4.4.4 GB retail ROM, it failed for some reason. No idea why.
- Wiped it again, flashed EU retail spec 5.0, it flashed fine, but still no mobile network. Tried with multiple SIMs, and tried reflashing CM11 and 5.0 multiple times; no luck.
- IMEI number is not reset to '0', still shows the correct IMEI, verified it against the battery cover.
Please advise. I would be much grateful! Thank you all in advance.
It's possibly Bootloader corruption - /userdata becoming read-only being a symptom. Bootloader and Kernel are inter-related, and Kernel plays a role in how Radio functions on many newer Android devices.
Flashing another motoboot.img does not appear to resolve this, however the 'Hard Unbrick' method might - once it supports Lollipop Bootloader.
Related: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
EDIT: It might be worth trying custom ROMs other than those based on CyanogenMOD - with possibly differing implementations of RIL/Radio Interface Layer.
lost101 said:
It's possibly Bootloader corruption - /userdata becoming read-only being a symptom. Bootloader and Kernel are inter-related, and Kernel plays a role in how Radio functions on many newer Android devices.
Flashing another motoboot.img does not appear to resolve this, however the 'Hard Unbrick' method might - once it supports Lollipop Bootloader.
Related: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
EDIT: It might be worth trying custom ROMs other than those based on CyanogenMOD - with possibly differing implementations of RIL/Radio Interface Layer.
Click to expand...
Click to collapse
Thanks for the advice. Do you have any specific ROMs in mind? I tried the stock 5.0.2 back, as mentioned in my OP, but that didn't help. Also tried BissPop ROM to no avail, but that's based on CM12, so that might be the reason. I have just downloaded an Unofficial AOKP ROM. Is that a non-CM one that you have in mind?
I also flashed the UK radio zip multiple times, no luck again. Everything else is working just fine.
hashdoom said:
Thanks for the advice. Do you have any specific ROMs in mind? I tried the stock 5.0.2 back, as mentioned in my OP, but that didn't help. Also tried BissPop ROM to no avail, but that's based on CM12, so that might be the reason. I have just downloaded an Unofficial AOKP ROM. Is that a non-CM one that you have in mind?
Click to expand...
Click to collapse
I was thinking of some of SlimSaber, or Dirty Unicorns.
Tried both SlimSaber and DirtyUnicorns and didn't work. Finally, used this method (http://forum.xda-developers.com/showthread.php?t=2542219) to reflash to stock 4.4.4 and everything is working fine now. Hurray!
Thanks for all the suggestions and help!
I have purchased a OnePlus 7 Pro from a friend of mine. He has already changed it from the T-Mobile to the International version via MSM. The current build number is 9.5.3.GM21AA and model number GM1915. I have currently installed TWRP 3.3.1-0 and rooted with Magisk 20.4. As I am new to OnePlus, I am confused as to go about updating the stock firmware, if I will lose root, updating to a custom rom. I have done this with other phones, Nexus 6P, 5X, Pixel 1 and Essential PH-1, but this seems different as I have a build number that is not necessarily meant for the T-Mobile version of this phone. I have read multiple guides and instructions throughout this forum, but don't seem to find the answers for my specific phone. Any help and direction would be very helpful.
If the phone has been updated to the international version then that's a REALLY old version, the latest version for International (Global) is 10.3.5, have you checked for an update via the phone already?
Update settings are in Settings > System > System Updates
If you want to upgrade manually, you can do that via Settings > System > System Updates > (Top Right) > Local Upgrade (Make sure the zip is in the main storage folder though or it won't be listed)
However, If you want to upgrade and keep root then you need to upgrade TWRP first, the latest is 3.4.0-0 from here : https://twrp.me/oneplus/oneplus7pro.html
Flash that first.
I've uploaded both the most recent versions onto my Android File Host :
Oxygen OS - Android 10.3.5 - Global - OnePlus 7 Pro (GM21AA) : https://www.androidfilehost.com/?fid=8889791610682950702
Oxygen OS - Android 10.0.8 - EU - OnePlus 7 Pro (GM21BA) : https://www.androidfilehost.com/?fid=8889791610682950715
My Android 10 Folder : https://www.androidfilehost.com/?w=files&flid=296897
So....
Grab the international version (which is the full rom)
Download the latest TWRP and Magisk
Reboot to TWRP (3.4.0-0)
Flash the full rom build (do not reboot yet)
Flash TWRP 3.4.0-0 (before rebooting) then reboot back into recovery
Flash latest Magisk then clear cache (not data)
Reboot
Check the Magisk version with the app : https://github.com/topjohnwu/Magisk/releases
I would suggest choosing the beta release in the app as Magisk 21.0 is available and works fine (see attached)
If it shows that the phone is not rooted then just reboot back into TWRP and flash Magisk again and reboot.
-----------------
If you're going to install a custom rom then ensure you read the first posts in the thread first as the dev will usually advise pre-requisites (i.e. A specific stock rom version to have installed first, a specific version of TWRP to use, etc)
(Also, try to use paragraphs, makes your post a lot more legible)
Thank you for the information, it is very helpful!!
I am currently on 9.3.5 which is how I got it from my friend. I was thankfully for it. I will review the files and upgrade when I get home from work and then look into crDroid 6.10. It has worked great on my PH-1.
In the event I need to reflash to stock, do I just Fastboot back?
njsges said:
Thank you for the information, it is very helpful!!
I am currently on 9.3.5 which is how I got it from my friend. I was thankfully for it. I will review the files and upgrade when I get home from work and then look into crDroid 6.10. It has worked great on my PH-1.
In the event I need to reflash to stock, do I just Fastboot back?
Click to expand...
Click to collapse
No, if you change rom you should really clear data so make sure you do backups before moving from rom to rom. As long as you still have TWRP you should be able to move between them.
djsubterrain said:
No, if you change rom you should really clear data so make sure you do backups before moving from rom to rom. As long as you still have TWRP you should be able to move between them.
Click to expand...
Click to collapse
Thank you again for your help!! The more I've used the Oxygen OS, it seems to have everything the custom roms have that I might need.
I did get an update message on Oxygen Updater app to install 10.0.3, also an older version. Per what you wrote previously, I am going to bypass that to 10.3.5.
njsges said:
Thank you again for your help!! The more I've used the Oxygen OS, it seems to have everything the custom roms have that I might need.
I did get an update message on Oxygen Updater app to install 10.0.3, also an older version. Per what you wrote previously, I am going to bypass that to 10.3.5.
Click to expand...
Click to collapse
Check this thread first : https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947
Especially the part labelled *Future proofing Update*, the OPS file is part of the MSM fix.
You should really check in that thread first to confirm how to update properly. The process might be different since you're changing firmware.
djsubterrain said:
Check this thread first : https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947
Especially the part labelled *Future proofing Update*, the OPS file is part of the MSM fix.
You should really check in that thread first to confirm how to update properly. The process might be different since you're changing firmware.
Click to expand...
Click to collapse
Thank you. The phone has already been switched from T-Mobile to Global. I'm not sure if the OPS patcher was done yet. I will text my friend and ask him. I wonder if it is detrimental to do it again while I am still on 9.3.5?
UPDATE: My friend flashed the ops file with the MSM tool download
SUCCESS!! Thank you for all of your help!!
*SOLVED: see reply*
The ROM I used before was LineageOS [10.0] and used a custom ROM with Android 9 before that. Needed to unlock my phone, and couldn't do that on Lineage, and had troubles flashing firmware with Odin, so I ended up using FrankensteinS6. The Stock kernel seems to let me input the NCK, and unlock the phone. So that's luckily finally over.
For about 4 days now I've been formatting phone and trying again and again. FrankensteinS6 works, some other 6.0/7.0 ROMs work. But LineageOS now enters a bootloop, and Pixel Experience (9.0 and 10.0) and Evolution X 10.0 don't detect the SIM. The ones that don't detect SIM also show no IMEI, which was worrying at first because I though I lost a partition.
Possibly related, the ROM of Pixel Experience Android 10.0 for G920W8 will not install because (paraphrasing) "This device is zeroflte, this file is for zerofltecan, zeroflte***, zeroflte***" claiming that my phone isn't one of those models. I got this S6 from Bell Canada, and I still have even the sticker that says it is a G920W8, not G920F. However, the Pixel Experience ROM for G920F flashes fine (sans the main problem).
I don't know the exact LineageOS ROM I used before, but I've tried all of their 10.0 releases, tried redownloading, and I get the bootloop every time. I see some info online of flashing modem firmware, but... I don't even know where to start with that. As I mentioned at the start, Odin is crapping out. I couldn't flash firmware with it, because it would reject the phone right after I started flashing. Anything I could do within TWRP would be great. I moved it back to FrankensteinS6 for my sanity, I started doing this Sunday and I'm starting to repeat steps over and over hoping that it just solves itself.
I tried to keep this straightforward, and I'm sure I did a bad job. I can extrapolate on what I have attempted. Please tell me what I have to do to get an android 10 ROM working on this old beauty again.
I do not have all the solutions. As per my tests with my SM-G920W8. I have managed to find ROMS and try them out. I have only seen Nougat 7.0 ROMS to work almost flawlessly. NOT 7.1.2, important, 7.0 only.
I have also tested some Pie and v10 ROMS like Pixel Experience. The ROMS boot nicely but since I do not use a SIM card to call as I use SIP phone numbers and require WiFi. But that left asside, I came upon serious camera issues no matter what I try. Up to now, SamStock ROM is pretty much the best Stock ROM I found but I always need to run the Magisk UNINSTALLER before re-installing the latest Magisk version..
As for Kernels, well, Anything that is oriented with Lineage OS, I've had camera issues even with Nougat v7.0. So basically, the only ROMS I found good, as of today, for now, are stock ROMS v7.0. But, to do your tests, Even if you have a 920F ROM, you can download a 920W8 kernel as long as you download a kernel which supports your installed Android version. Also make sure to download the proper Stock or AOSP kernel (AOSP for LineageOS). There's not many but there's a few ones that work properly.
Another option is to download an AOSP ROM that works for W8 phones, unzip the file and grab the boot file inside corresponding to the W8 or T-Mobile version. You simply unzip your real ROM you want top install, replace the boot file for the one you got and rezip it. This made my phone boot properly for some F version ROMS but again, not without issues. That's why, I really suggest v7.0 Srock ROMS. I hope this helps you a bit. Again, you can have your own tests and other users may have other answers, but this is based off over 30 bootloops in my case of trying to mod a ROM for the W8 model. It's not easy to find a good one for Canada, I admit!!!
I flashed TWRP years ago, and I found out that I had a G920F version flashed. I don't know why Lineage allowed me to use SIM before, but rectifying this issue seems to made the SIM work in newer versions.
I don't know what the S6's predisposition to having crashing cameras is, but I have avoided this in the past by using custom camera apps, like Open Camera. This has saved me every time.
As for the boot loops... I think another thing that helped is that "format data" doesn't wipe the OS. When you are in recovery, having issues with bootloops in various ROMs, try advanced wipe, and wipe the system. It didn't fix right away, but the time I got Pixel Experience 10 up and running that was the trick.