TWRP showing weird folders. HELP!! (OnePlus 6) - OnePlus 6 Questions & Answers

Yesterday, I wanted to switch from Evolution X rom to Pixen os on my OnePlus 6. So, I was following the normal procedure .i.e., Flash oos and twrp on both slots, reboot, and then flash pixen. Okay. I successfully flashed oos and twrp on one slot. But, when i rebooted to recovery to flash it again in the other slot, when I went to the "Install" section, I wasn't able to find any of my files! It showed all weird folders like "HGgjajhzYHjwg" . Luckily, since I wasn't able to flash oos on the other slot, I was able to boot to system on the other one, which booted to evolution x (Now I'm currently booted in slot B). What should I do? (I have seen many threads like this, but haven't found a thread on OnePlus 6). Please Help!!

format data when switching to different roms

JohnnyMwanza said:
format data when switching to different roms
Click to expand...
Click to collapse
Now if i format my data, will i be able to boot back to my current rom, evo x? (Sorry, but im a noob)

Backup your data and then oxygen os via fastboot....this worked for me.

MAX TEN said:
Backup your data and then oxygen os via fastboot....this worked for me.
Click to expand...
Click to collapse
You mean, boot to "twrp.img" and then flash oos?

Anmol45 said:
Yesterday, I wanted to switch from Evolution X rom to Pixen os on my OnePlus 6. So, I was following the normal procedure .i.e., Flash oos and twrp on both slots, reboot, and then flash pixen. Okay. I successfully flashed oos and twrp on one slot. But, when i rebooted to recovery to flash it again in the other slot, when I went to the "Install" section, I wasn't able to find any of my files! It showed all weird folders like "HGgjajhzYHjwg" . Luckily, since I wasn't able to flash oos on the other slot, I was able to boot to system on the other one, which booted to evolution x (Now I'm currently booted in slot B). What should I do? (I have seen many threads like this, but haven't found a thread on OnePlus 6). Please Help!!
Click to expand...
Click to collapse
That's actually your internal storage still encrypted, this is a common issue, my recommendation is to try to boot normally after flashing the zips with adb sideload, if your internal storage is still intact then there you go, otherwise reboot to twrp and format internal storage.

Anmol45 said:
Yesterday, I wanted to switch from Evolution X rom to Pixen os on my OnePlus 6. So, I was following the normal procedure .i.e., Flash oos and twrp on both slots, reboot, and then flash pixen. Okay. I successfully flashed oos and twrp on one slot. But, when i rebooted to recovery to flash it again in the other slot, when I went to the "Install" section, I wasn't able to find any of my files! It showed all weird folders like "HGgjajhzYHjwg" . Luckily, since I wasn't able to flash oos on the other slot, I was able to boot to system on the other one, which booted to evolution x (Now I'm currently booted in slot B). What should I do? (I have seen many threads like this, but haven't found a thread on OnePlus 6). Please Help!!
Click to expand...
Click to collapse
Always remove your phone password when changing rom...and always keep backup on your pc or hard drive or somewhere else...and avoid going from one security patch to another... especially when going from new security update to an old one...but mainly remove your password...imo that should help avoiding the data encryption and file corruption

Related

OnePlus 7 Pro Flashing doesn't work properly

Hey guys,
so first of all I wanna let you know that my device is not bricked or something (it was a couple of times though).
But let's get started with my issue. For me, personally, I have experienced that the slot system (A/B Slot) doesn't work that good. I had a OnePlus 3T before and I never had any problems with flashing, but now...
My impression is that it's a lot easier to brick its' device than before. Every time I want to flash a new OS I gotta use the msmtool.
1. I boot to recovery mode through the OS
2. I boot to fastboot trough the OOS stock recovery
3. I try to flash TWRP to erase the system
4. Flashing works, but I can no longer boot into recovery mode
5. I have a bootloop (fastboot mode only)
6. I have to use that msmtool
7. I have some old OOS (9.5.5 or something)
8. I unlock the bootloader through the OS & fastboot
9. I boot into TWRP, delete everything and flash another ROM
10. Everything works and the cicle begins again​
I really don't know why I'm always stuck in that bootloop... Maybe you guys could help me and give me your personal opinion on the slot system?
I totally know that feeling. I started with a tmo op7p, flashed international, unlocked bootloader, try to boot TWRP, and nope. Switch slot, it works. Flash it, great. Make a backup with TWRP of my working system, flash ROMaur, won't do anything but boot to TWRP. Open TWRP file manager and every file on internal storage is a ton of folders with jumbled strings of letters and numbers for names. MSM tool back to intl stock, try lineage... Nope. Keeps telling me to do a factory reset. I did, but I do another and still boot loop. MSM to intl, try other roms, same outcome.
I can unlock my bootloader and root it and run intl stock but that's it.
oxadedzn said:
Hey guys,
so first of all I wanna let you know that my device is not bricked or something (it was a couple of times though).
But let's get started with my issue. For me, personally, I have experienced that the slot system (A/B Slot) doesn't work that good. I had a OnePlus 3T before and I never had any problems with flashing, but now...
My impression is that it's a lot easier to brick its' device than before. Every time I want to flash a new OS I gotta use the msmtool.
1. I boot to recovery mode through the OS
2. I boot to fastboot trough the OOS stock recovery
3. I try to flash TWRP to erase the system
4. Flashing works, but I can no longer boot into recovery mode
5. I have a bootloop (fastboot mode only)
6. I have to use that msmtool
7. I have some old OOS (9.5.5 or something)
8. I unlock the bootloader through the OS & fastboot
9. I boot into TWRP, delete everything and flash another ROM
10. Everything works and the cicle begins again
I really don't know why I'm always stuck in that bootloop... Maybe you guys could help me and give me your personal opinion on the slot system?
Click to expand...
Click to collapse
Doing it wrong.
If you are currently rooted and a new OS comes out you can do the following and you don't need to flash with TWRP or use a computer.
1. Download the full OTA. You can use Oxygen updater to do that or use a link in the stock ROM section on this site.
2. Make sure you have the Magisk and the TWRP zip on the phone.
3. Do a local update in the system area but do not reboot.
4. Launch Magisk manager and select install.
5. Use the OTA install option to inactive slot.
6. Now you can reboot. You have installed the new OS and root also.
7. Once rebooted do another local install. This will install in the slot that you were just running. It will fail the first time, but work the second time.
8. Repeat 4.
9. Repeat 5.
10 . Repeat 6.
You now have both slots with the same OS and rooted.
If you want to install TWRP.
Launch Magisk and install the TWRP zip.
Reboot into recovery. This is important because you cannot boot in slot with TWRP unless Magisk in installed.
Now flash the Magisk image file.
Now in TWRP select the other slot and reboot into recovery.
In recovery install Magisk image to this slot.
Now you have TWRP and Magisk in both slots.
I have done it that way since 9.5.7 and have not had an issue.
tech_head said:
Doing it wrong.
If you are currently rooted and a new OS comes out you can do the following and you don't need to flash with TWRP or use a computer.
1. Download the full OTA. You can use Oxygen updater to do that or use a link in the stock ROM section on this site.
2. Make sure you have the Magisk and the TWRP zip on the phone.
3. Do a local update in the system area but do not reboot.
4. Launch Magisk manager and select install.
5. Use the OTA install option to inactive slot.
6. Now you can reboot. You have installed the new OS and root also.
7. Once rebooted do another local install. This will install in the slot that you were just running. It will fail the first time, but work the second time.
8. Repeat 4.
9. Repeat 5.
10 . Repeat 6.
You now have both slots with the same OS and rooted.
If you want to install TWRP.
Launch Magisk and install the TWRP zip.
Reboot into recovery. This is important because you cannot boot in slot with TWRP unless Magisk in installed.
Now flash the Magisk image file.
Now in TWRP select the other slot and reboot into recovery.
In recovery install Magisk image to this slot.
Now you have TWRP and Magisk in both slots.
I have done it that way since 9.5.7 and have not had an issue.
Click to expand...
Click to collapse
Irrelevant ISH, but ever had that one bootloop where it only bootloops at the "Warning Bootloader unlocked screen" constantly? When I try to access fastboot, it'll just go straight to recovery without even waiting for input (to my luck, of course, until I had to uninstall magisk in full, reinstall, make sure TWRP was reflashed and did the "Fix recovery bootloop", though that wasn't the seemingly the issue). The issue got resolved, but it was very scary for that to have happened as soon as i enabled sudohide (I always had it work, but with huge problems, but never enough to bootloop me to death)
JhinCuatro said:
Irrelevant ISH, but ever had that one bootloop where it only bootloops at the "Warning Bootloader unlocked screen" constantly? When I try to access fastboot, it'll just go straight to recovery without even waiting for input (to my luck, of course, until I had to uninstall magisk in full, reinstall, make sure TWRP was reflashed and did the "Fix recovery bootloop", though that wasn't the seemingly the issue). The issue got resolved, but it was very scary for that to have happened as soon as i enabled sudohide (I always had it work, but with huge problems, but never enough to bootloop me to death)
Click to expand...
Click to collapse
If you install TWRP on a 7 Pro without installing Magisk you will absolutely boot loop. If you wipe the system in one slot and have a differing ROM from the active slot you can in fact boot loop. Although the systems are different, the settings between the systems are shared.
Sorry to say, but nothing about those steps is correct. Follow some guides in the guides section to get aquatinted with the A/B system
Arden144 said:
Sorry to say, but nothing about those steps is correct. Follow some guides in the guides section to get aquatinted with the A/B system
Click to expand...
Click to collapse
You are absolutely incorrect.
When going from 9.5.10 to 9.5.11 and all my previous upgrades it has been:
1. Local install of the new OS with a full OTA since I am rooted.
2. Do not reboot.
3. Install Magisk to inactive slot.
4. Reboot (Slot will automatically switch to the one recently updated).
5. Local install of OS into the other slot, fails first time, do it again.
6. Install Magisk into inactive slot.
7. Reboot. (Slot will switch to recently updated slot).
8. Both slots now have latest OS and are rooted.
You can also install TWRP if you like.
No computer needed.
This works.
tech_head said:
You are absolutely incorrect.
When going from 9.5.10 to 9.5.11 and all my previous upgrades it has been:
1. Local install of the new OS with a full OTA since I am rooted.
2. Do not reboot.
3. Install Magisk to inactive slot.
4. Reboot (Slot will automatically switch to the one recently updated).
5. Local install of OS into the other slot, fails first time, do it again.
6. Install Magisk into inactive slot.
7. Reboot. (Slot will switch to recently updated slot).
8. Both slots now have latest OS and are rooted.
This works.
Click to expand...
Click to collapse
That's completely unnecessary and just avoiding the purpose of the a/b system.
All it would take is:
1. Local install
2. Install magisk to inactive slot

I'm so confused. Two version of OOS installed

I ran into a problem with my phone the other day. I ended up having the use the MsmDownloadToolV4.0InternationalVersionOxygenOS5.1.5 to restore to stock. After updating to 9.0.9, I kept having trouble installing TWRP. After messing with it for days, I discovered that though I have 9.0.9 installed on my phone, if I switch slots, I have 10 installed on that slot. I'm thinking that when I'm installing TWRP, it's having a problem because I have two different version installed on the phone. Is that possible? Some of the guides I've seen indicate that when you boot to TWRP, then flash it through recovery, it somehow flashes both slots. If that's the case, it would only be the right version of TWRP for one slot, not the other. I'm so confused.
I'm trying to get both slots to be 10 so I can try OmniROM or LineageOS. But at this point, I'd be happy if I could get twrp installed and my phone rooted. I've literally been trying to get TWRP installed for three days straight. It fails every time.
Try to flash OOS 10 with this tool https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
You can save your data by removing the "-w" from the bat file when flashing it but try the tool and it should install empty both slots and install OOS 10.
Xenomorphs said:
Try to flash OOS 10 with this tool https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
You can save your data by removing the "-w" from the bat file when flashing it but try the tool and it should install empty both slots and install OOS 10.
Click to expand...
Click to collapse
Thank you. I'll try that. I've already lost my data. Luckily, I made a backup not long before this.
Well, that worked, but.....
When I switched over to the other slot, that would no longer boot. Both slots did boot correctly right before I ran flash-all.bat. After doing that, the second one just sat on the spinning boot logo. I don't understand why what I do on slot B should impact what's going on with slot A.
Yippee38 said:
Well, that worked, but.....
When I switched over to the other slot, that would no longer boot. Both slots did boot correctly right before I ran flash-all.bat. After doing that, the second one just sat on the spinning boot logo. I don't understand why what I do on slot B should impact what's going on with slot A.
Click to expand...
Click to collapse
Did you try the flasher with "-w" or without? Also, see if you can uninstall magisk from your phone. And try to go into stock recovery mode and resetting the system data and stuff. (not your data)

Help, I can flash and boot LineageOS but not OxygenOS

Hi, as the title explains I can flash and boot into lineage os but when I try to flash a stock OxygenOS signed flashable zip from this thread (https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244)
and when I boot to system, the screen doesn't show a boot logo, it just goes black for a few seconds before rebooting back to twrp (also if it helps, when it goes to twrp all the files are gibberish, I have to shut off the phone and boot into it from fastboot or I can't see any files).
This all started because I misunderstood the instructions and tried to flash an ota package which then broke the system, it's working now but I'd much rather use OOS as Lineage is missing a lot of the features I'm used to on Oxygen.
I've also tried the "flash-all-partitins-fastboot" from https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 but unfortunately that gave the same issue, it just went back to recovery and wouldn't load OOS.
If anyone has any ideas on how to get back to oxygen that'd be super helpful! I'm considering using the MSM tool but I'd rather not have to start from scratch and lose all my files.
I'm just guessing, but there might be something wrong with your TWRP, did you try re-flashing it?
mati11233 said:
I'm just guessing, but there might be something wrong with your TWRP, did you try re-flashing it?
Click to expand...
Click to collapse
I should've clarified in the post, I mean all the files are gibberish (as in not decrypted I think?) but when I
Code:
fastboot boot twrp.img
it works fine and I can see all the files.
I've probably tried flashing it 4 times through twrp but every time it just does the same thing, boot to system just shows a black screen for a few seconds then reboots to twrp.
I'd love to use blu_spark like everyone recommends but I can't find the blu_spark recovery for the op6, only their kernel.
The reason why it's gibberish is because your device is encrypted and you need to input the password in the twrp to be able to access it. Seems the twrp doesn't detect the encryption correctly so there might be something wrong with it.
Here is the bluespark twrp https://github.com/engstk/android_device_oneplus_enchilada/releases
mati11233 said:
The reason why it's gibberish is because your device is encrypted and you need to input the password in the twrp to be able to access it. Seems the twrp doesn't detect the encryption correctly so there might be something wrong with it.
Here is the bluespark twrp https://github.com/engstk/android_device_oneplus_enchilada/releases
Click to expand...
Click to collapse
I just tried with blu_spark and the same thing happens but I realised something else, twrp only doesn't work on slot A.
If I see that it didn't decrypt the files, I can set B to active, reboot to recovery, and it works perfectly.
I noticed after one of the failed boots it switched the active slot to B even though I had set it to A before flashing. So every time it doesn't show the logo or anything, it sets the active slot from A to B and reboots to recovery.
Also I just looked and from the Backup page, it shows 2.7 GB for system on slot A and 1.7GB on slot B so I'm going to try wiping both and reflashing the flashable signed zip on each then twrp.
UPDATE: Just did that and the twrp installer was giving an error saying unsupported android version so I looked and system is only 4MB after flashing that package (OnePlus6Oxgygen_22_OTA_034_all_...zip), I'm trying an older one (...OTA_026...zip) to see if that actually works.
So I tried with the older one and lineage and they both still left the system partition at 4MB and the blu_spark twrp installer isn't detecting an android version. The system image partition is at 2.6GB if that means anything.
Oh wait more update, I'm dumb and shut off the phone while taking the case off (got stuck and it was pushing the power button) and even though the twrp installer couldn't detect anything and twrp said No OS installed when trying to boot to system, lineage just started up, no problem. I am very confused I miss when there was one system partition.
How are you flashing the OS?
mati11233 said:
How are you flashing the OS?
Click to expand...
Click to collapse
I'm using twrp, blu_spark and normal, and both have the same result. They can flash lineage and it runs fine, but oxygen refuses to boot and just switches the active slot and goes to recovery instead.
I also tried the fastboot rom flashing thing from the thread I linked to in the OP and it's the same thing, just goes back to recovery and wont boot.
P.S. I'm currently copying over /sdcard to an external drive and if I can't figure out how to fix this by the time that's done, I'll just use MsmDownloadTool and start over.
And you are wiping each time before flashing it, right? If it is the case then the download tool is probably the easiest way to go about it, rather than spending days troubleshooting it.
mati11233 said:
And you are wiping each time before flashing it, right? If it is the case then the download tool is probably the easiest way to go about it, rather than spending days troubleshooting it.
Click to expand...
Click to collapse
I've tried it with and without wiping and it always seems to do the same thing either way, works with LOS not with OOS. Thanks for the help! but yeah I think I'm just going to end up using the download tool once everything's over.

Can't flash custom ROMs

I got my phone yesterday, and I can't flash custom roms. My phone gets stuck on the boot screen (the animation is working as expected) for over thirty minutes, then I give up. I am/was rooted on the latest stock image. In the Download folder, I put the ROM (I have tried with crDroid and Bliss), twrp.zip, nano gapps, and Magisk. I flash the ROM and TWRP and reboot into recovery. Whenever I do this, I no longer have a Downloads folder or files. So, not knowing what to do, I sideload gapps and Magisk and reboot system. Then, I inevitably get stuck on the boot screen animation. What am I doing wrong?
Hello have you try to format data before or after flash custom rom? Some rom don’t work if not do.
Are you familiar with A/B slot partitions and their related behaviors? It's markedly different from single slot systems.
c3drik 67 said:
Hello have you try to format data before or after flash custom rom? Some rom don’t work if not do.
Click to expand...
Click to collapse
I tried this. Unfortunately, no luck.
Dungeon47 said:
Are you familiar with A/B slot partitions and their related behaviors? It's markedly different from single slot systems.
Click to expand...
Click to collapse
I am not familiar with A/B slot partitions. I followed a guide step-by-step, so I wasn't too concerned about my ignorance. Should I be doing something special? Thanks.
Kama45 said:
I tried this. Unfortunately, no luck.
I am not familiar with A/B slot partitions. I followed a guide step-by-step, so I wasn't too concerned about my ignorance. Should I be doing something special? Thanks.
Click to expand...
Click to collapse
Yes. A lot. Get very familiar with how A/B slots work. It changes many things about the whole flashing process. Trying to do things the same way as before leads to exactly what you're experiencing.
Kama45 said:
I got my phone yesterday, and I can't flash custom roms. My phone gets stuck on the boot screen (the animation is working as expected) for over thirty minutes, then I give up. I am/was rooted on the latest stock image. In the Download folder, I put the ROM (I have tried with crDroid and Bliss), twrp.zip, nano gapps, and Magisk. I flash the ROM and TWRP and reboot into recovery. Whenever I do this, I no longer have a Downloads folder or files. So, not knowing what to do, I sideload gapps and Magisk and reboot system. Then, I inevitably get stuck on the boot screen animation. What am I doing wrong?
Click to expand...
Click to collapse
Same thing happened to me, I had to forced the phone off (Volume + and Power) without plug-in the USB after is off I went into EDL mode (Volume +- together and Power) then immediately plug in to your ready PC with msm already ready to go.
You might have to try it a few times...
That's what I did a while back.

very frustrating to install lineage

i just need to know which steps to take, in which order.
i can later add details to the steps.
but every f*&(^*( time i have to upgrade phone (ota doesnt work to upgrade to guacamole)
i have to rediscover which order.... finally i'm on a quest to log it all
1) install fastboot/adb on pc/linux/mac
2) unlock phone
3) fastboot flash boot twrp.img
4) reboot to recovery (should go to twrp)
5) flash twrp.zip
6) flash magisk
7) flash lineage_nightly.zip
8) reboot to os
Lineage will finally load... "about phone" says i'm in 17.1 guacamole doing this now my sim card won't read.... & i can't rotate screen (a problem i've had when the last lineage 16.? worked)
i can't flash oxygen.. cuz an error comes up
i need help
(i did wipe all data etc.. but i need to place the wipes in the order above)
(after flashing to lineage, the settings say im encrypted(maybe that matters))
EDIT: to make matters easier.. i can get into fastboot mode now, and my linux pc recognizes the phone
how can i fix this
Did you also FORMAT your data?
Use MSM Tool
csmooth2001 said:
i just need to know which steps to take, in which order.
i can later add details to the steps.
but every f*&(^*( time i have to upgrade phone (ota doesnt work to upgrade to guacamole)
i have to rediscover which order.... finally i'm on a quest to log it all
1) install fastboot/adb on pc/linux/mac
2) unlock phone
3) fastboot flash boot twrp.img
4) reboot to recovery (should go to twrp)
5) flash twrp.zip
6) flash magisk
7) flash lineage_nightly.zip
8) reboot to os
Lineage will finally load... "about phone" says i'm in 17.1 guacamole doing this now my sim card won't read.... & i can't rotate screen (a problem i've had when the last lineage 16.? worked)
i can't flash oxygen.. cuz an error comes up
i need help
(i did wipe all data etc.. but i need to place the wipes in the order above)
(after flashing to lineage, the settings say im encrypted(maybe that matters))
EDIT: to make matters easier.. i can get into fastboot mode now, and my linux pc recognizes the phone
how can i fix this
Click to expand...
Click to collapse
Same thing happened to me, I went from locked boot loader to unlock + lineage. When I tried to go back, the error kept popping up and the only thing that worked was fastboot.
Use MSM tool linked below and you should be good.
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Note : IMPORTANT ! msm tool will also relock your bootloader, so you will lose any data you might have on your phone.
csmooth2001 said:
i just need to know which steps to take, in which order.
i can later add details to the steps.
but every f*&(^*( time i have to upgrade phone (ota doesnt work to upgrade to guacamole)
i have to rediscover which order.... finally i'm on a quest to log it all
1) install fastboot/adb on pc/linux/mac
2) unlock phone
3) fastboot flash boot twrp.img
4) reboot to recovery (should go to twrp)
5) flash twrp.zip
6) flash magisk
7) flash lineage_nightly.zip
8) reboot to os
Lineage will finally load... "about phone" says i'm in 17.1 guacamole doing this now my sim card won't read.... & i can't rotate screen (a problem i've had when the last lineage 16.? worked)
i can't flash oxygen.. cuz an error comes up
i need help
(i did wipe all data etc.. but i need to place the wipes in the order above)
(after flashing to lineage, the settings say im encrypted(maybe that matters))
EDIT: to make matters easier.. i can get into fastboot mode now, and my linux pc recognizes the phone
how can i fix this
Click to expand...
Click to collapse
Wrong order. First flash LOS, then TWRP Installer and then Magisk. When you flash LOS after TWRP and Magisk, your TWRP and root will be gone.
n2851991m said:
Same thing happened to me, I went from locked boot loader to unlock + lineage. When I tried to go back, the error kept popping up and the only thing that worked was fastboot.
Use MSM tool linked below and you should be good.
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Note : IMPORTANT ! msm tool will also relock your bootloader, so you will lose any data you might have on your phone.
Click to expand...
Click to collapse
crap... my link is old.. may not work.. i'll try yours.... fingers crossed
csmooth2001 said:
Lineage will finally load... "about phone" says i'm in 17.1 guacamole doing this now my sim card won't read.... & i can't rotate screen (a problem i've had when the last lineage 16.? worked)
Click to expand...
Click to collapse
I can confirm the auto rotate issue with 17.1. In my situation, this was with a tmo 1915 variant. When I loaded OOS 9.5.13 and LOS 16, no mobile data but rotation. If I loaded OOS 10.3.1 firmware with LOS 17.1, had mobile data but no rotation. I even flashed the modem from OOS 10.3.1 into 9.5.13 that produced mobile data but no rotaion. No matter which firmware I tried which was many, I could never have both mobile data and rotation!! I wound up returning the tmo 1915 and ordered a 1917. .Have not received it yet. Maybe better luck with the international variant.
As a side note, luk1337, one of the los 17.1 maintainers for guac, is using the EU 1913 variant and confirmed that los 17.1 was not tested with the 1915 variant. So if you gots a tmo 1915, lots of luck. Searching around, they are supposed to be the same hardware but due to tmo locking tihs down, I dont know.
As for flashing, the thing to remember is that when you flash roms, you are flashing to the OTHER slot. When you are flashing mods, you are flashing to the CURRENT slot. Flashing roms and mods in recovery without changing the slot between will hose your install.
Official install method from maintainers:
1. Download the latest build
2.. Boot to recovery (the current slot. Could be A or B)
3. Flash the latest build
4. Boot to recovery again (now you are in the other slot)
5. Flash magisk
6. Reboot
Hope that helps.
razorshiv said:
I can confirm the auto rotate issue with 17.1. In my situation, this was with a tmo 1915 variant. When I loaded OOS 9.5.13 and LOS 16, no mobile data but rotation. If I loaded OOS 10.3.1 firmware with LOS 17.1, had mobile data but no rotation. I even flashed the modem from OOS 10.3.1 into 9.5.13 that produced mobile data but no rotaion. No matter which firmware I tried which was many, I could never have both mobile data and rotation!! I wound up returning the tmo 1915 and ordered a 1917. .Have not received it yet. Maybe better luck with the international variant.
As a side note, luk1337, one of the los 17.1 maintainers for guac, is using the EU 1913 variant and confirmed that los 17.1 was not tested with the 1915 variant. So if you gots a tmo 1915, lots of luck. Searching around, they are supposed to be the same hardware but due to tmo locking tihs down, I dont know.
As for flashing, the thing to remember is that when you flash roms, you are flashing to the OTHER slot. When you are flashing mods, you are flashing to the CURRENT slot. Flashing roms and mods in recovery without changing the slot between will hose your install.
Official install method from maintainers:
1. Download the latest build
2.. Boot to recovery (the current slot. Could be A or B)
3. Flash the latest build
4. Boot to recovery again (now you are in the other slot)
5. Flash magisk
6. Reboot
Hope that helps.
Click to expand...
Click to collapse
so if I boot to recovery in the current slot A
so if i flash a ROM, it will install to B ?
ok ok ok.. i was told that i have to flash a rom, then twrp.zip then magisk
but according to you (i think)
i flash a rom, reboot to recovery.. then flash twrp.zipo then magisk?
im guessing big time
is there a forum just for GM1915 ??? anywhere in the world...
csmooth2001 said:
so if I boot to recovery in the current slot A
so if i flash a ROM, it will install to B ?.
Click to expand...
Click to collapse
yes.
ok ok ok.. i was told that i have to flash a rom, then twrp.zip then magisk
but according to you (i think)
i flash a rom, reboot to recovery.. then flash twrp.zipo then magisk?
Click to expand...
Click to collapse
flash rom, flash twrp, reboot recovery, flash magisk.
is there a forum just for GM1915 ??? anywhere in the world..
Click to expand...
Click to collapse
They are scattered around the op7pro forum. Just do a search for tmo or tmobile.
boot to other slot & sim will work

Categories

Resources