Related
I have a SGH-I337M S4 via Koodo in Canada. I've spent 15 hours on this so far and am now really confused.
History: I installed Cyanogenmod a couple years ago. Recently wanted to change from that so I decided to install stock first via SamMobile for SGH-I337M Koodo. I downloaded 5.0.1 from here sammobile
I had it installed fine and then went to root, so I used Odin, enabled USB debugging - and installed CF Auto Root. That worked.
Then I went to install Clockwork Recovery mod and it errored out and I don't recall exactly what happened but now I'm stuck with the yellow exclamation point saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
In the TOP LEFT of screen is says:
ODIN MODE
PRODUCT NAME: SGH-I337M
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX KERNEL: LOCK: 0X0
KNOX WARRANTY VOID: 0X1
CSB-CONFIG-LSB: 0X30
SECURE DOWNLOAD: ENABLE
WRITE PROTECTION: ENABLE
eMMC BURST MODE: enabled
1) I tried to do emergency recovery through KIES but my phone isn't being recognized in Kies.
2) I uninstalled Samsung USB drivers and tried just KIES alone
3) I tried just USB drivers with flashing stock firmware via Odin in download mode - it errors out and says no partition found or says FAIL in red.
I've read a lot but i'm not that technical when it comes to this.. not sure what to do at this point. I can get into download mode but I can't get anything to work.
Is the phone ruined??
No, the phone is definitely not ruined.
Are you using the original Samsung USB cable that came with phone? Tried different USB ports? Tried different versions of Odin?
With the phone on the "encountered and error screen", connect the phone to Odin and try to flash.
If Odin can't pull the partition information, you'll need to flash stock with a lit file for the phone. Your phone has 16 gb of internal memory?
audit13 said:
No, the phone is definitely not ruined.
Are you using the original Samsung USB cable that came with phone? Tried different USB ports? Tried different versions of Odin?
With the phone on the "encountered and error screen", connect the phone to Odin and try to flash.
If Odin can't pull the partition information, you'll need to flash stock with a lit file for the phone. Your phone has 16 gb of internal memory?
Click to expand...
Click to collapse
Hi Audit,
Thank you for the reply. I was able to try the original USB cable now and loaded the stock Koodo firmware through Odin and it worked flawlessly. Once loaded and rebooted, it went right to the homescreen and skipped past all the normal setup stages, so I assume something on the phone was there already but just corrupted on a bad upgrade.
Never again using an older USB cable.
Whew, that was a learning lesson. Now I'd like to:
1) re-root again
2) Install custom recovery (clockwork?)
3) Install the marshmallow OS via Broken I believe.
I will keep the thread posted for others who need help and for my own reference.
Don't use cwm, use twrp and flash supersu via twrp to get toot. This has method has always worked with me. Also, I am sticking with twrp 2.8.7.1 for now as that is what works for me.
Root is not required to install a custom recovery or custom rom.
The data files were still on the phone because flashing with Odin doesn't normally overwrite the data partition.
I suggest using twrp to backup your phones efs partition and keep it safe in case it gets corrupted during a bad flash.
Alternatively, you could have flashed twrp from the error screen with Odin, performed a full wipe in twrp, and flashed the custom rom of your choice.
audit13 said:
Don't use cwm, use twrp and flash supersu via twrp to get toot. This has method has always worked with me. Also, I am sticking with twrp 2.8.7.1 for now as that is what works for me.
Root is not required to install a custom recovery or custom rom.
The data files were still on the phone because flashing with Odin doesn't normally overwrite the data partition.
I suggest using twrp to backup your phones efs partition and keep it safe in case it gets corrupted during a bad flash.
Alternatively, you could have flashed twrp from the error screen with Odin, performed a full wipe in twrp, and flashed the custom rom of your choice.
Click to expand...
Click to collapse
I did not know that. I thought I required root first and then had to install a custom ROM. Interesting.
Ok, so the plan then is to find twrp for my phone model and install that first... I'll search and try to do that now.
Flash the tar version of twrp in Odin as that is the easiest way in my opinion.
audit13 said:
Flash the tar version of twrp in Odin as that is the easiest way in my opinion.
Click to expand...
Click to collapse
Done. I used the latest one for the tar and I have v2.8.4.0 right now. I held volume up and power and it went to Teamwin with a bunch of options. Install/wipe/backup/restore/mount/settings/advacned/reboot
On the TWRP website it says: "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
1) I'm not sure what it means by typing that. I'd like to keep TWRP as I install my custom rom. I have the custom rom on an external SD card along with GApps. Should I insert the sd card and then boot to recovery, wipe all data and install from zip on sd card? Is that correct?
2) How do I keep TWRP from not getting overwritten?
Thanks so much for the help. Really appreciate it after a weekend of terror.
I backed up the EFS portion and it wrote it to the internal storage of the phone I believe... data/TWRP something. I did not have my external card in when I did that. Is that the correct way and how would I access that backup if I needed to?
Sorry for the questions. Trying to learn without running in circles.
After I backed up the EFS it also asked me to install SuperSU and I did that - then it rebooted automatically.
If you flash twrp and then just boot the phone to the rom, the boot process will restore stock recovery. If you flash twrp, you need to boot into twrp before booting the stock room for the first time after flashing twrp.
Copy files to internal memory or sd card. If using an sd card, place card into the phone, boot to twrp, and flash.
If twrp doesn't detect root, it will try to root the phone for you. I always choose no so I can flash supersu.
Btw, upgrade to 2.8.7.1 as you may get errors because the recovery is too old.
While in twrp, connect the phone to the computer and use explorer to drag and drop the twrp backup files to your computer.
audit13 said:
If you flash twrp and then just boot the phone to the rom, the boot process will restore stock recovery. If you flash twrp, you need to boot into twrp before booting the stock room for the first time after flashing twrp.
Copy files to internal memory or sd card. If using an sd card, place card into the phone, boot to twrp, and flash.
If twrp doesn't detect root, it will try to root the phone for you. I always choose no so I can flash supersu.
Btw, upgrade to 2.8.7.1 as you may get errors because the recovery is too old.
While in twrp, connect the phone to the computer and use explorer to drag and drop the twrp backup files to your computer.
Click to expand...
Click to collapse
I'm not sure if I can post links due to the new account, but the latest files for me are found on dl.twrp.me/jfltecan/ and the only tar image is twrp-2.8.4.0-jfltecan.tar
I will have to go over your other comments on my own to see the functionality. As of now, this is what I have:
1) Stock firmware
2) TWRP installed
3) TWRP asked if I wanted to root (I said yes, figuring that's what you meant)
4) TWRP installed SuperSu and rebooted
5) I downloaded Root Checker and it verified root.
I did just test it by powering off phone and then booting into recovery. Teamwin came up - so I assume that it's all working correctly and the stock ROM did not overwrite anything?
Questions:
1) Now I can boot into recovery mode and install the custom ROM via a zip file on sdcard?
2) Do I install GApps via recovery mode after I install a custom ROM?
3) Should I wipe/format before installing and if so, which one - "Advanced" or "Format" buttons?
I did a factory reset via TWRP then installed the custom ROM. Seems to be working quite well. Maybe I will try it a couple times in order to get the hang of it.
In order to determine that TWRP is the default recovery - it should load when I go into recovery mode correct?
If the phone boots to twrp once, it should not revert to stock recovery in the future.
Is there a stable ROM for a S4 i337m that is newer? I'm having some trouble finding a solid list that is known to work. I don't want to install a wrong version and mess up. I did try the "broken" ROM but 50% of time when someone phones me, they can't hear me speaking so I'm going to have to go back to stock firmware for now.
You could try ROMs made for the 9505 and i337.
so i just doing a clean install of the beta 3 rom, i did follow the instruction that written in the thread but some how after installing the update when i'm about to reboot into system it keeps rebooting into the recovery. so i decided to clean wipe and re-flash the rom, and some how it says that there's no rom installed. i've tried to install other custom rom like, LOS 15 and Liquid Remix, but it's still the same, keep booting to recovery and showing that there's no rom installed. plz help...
Go to twrp > wipe > format data > yes
Then transfer oos OB 3 to your phone, use adb push command is better than copy paste(not sure why because sometimes i copy pasted into phone, sometime it bootloop or storage not recognised)
Flash it, then flash magisk 15.2. then reboot. It should work fine. Unless you use a not compatible twrp version.
thanks for ur solution before, but can u tell me the compatible twrp is, cuz i'm using the twrp 3.2.1 by blu spark and it keeps booting into recovery
You need to flash no verity zip. If you are decrypted.
"You need to flash no verity zip. If you are decrypted. "
Thanks god for this comment, use about 2 hours digging around forums and re-flashing, wiping, trying diffrent TWRPs, different roms. And when I found this comment I just isntalled the zip and it worked within 10 seconds.
Guys this is help less.
After rooting my device I followed some instructions to get the Lineage 14. I flashed a BootLoader and a Modem as instructed and went forth to mount USB in order to transfer the custom rom into the device. But this is where the problem is.
It says E: Cant find partition to mount storage. I've tried to reboot, wide, data, storage, system and cache and repair the partition I don't know what else to do.
Anyone else can help? Btw I am fairly new to this stuff so please dumb it down for me.
Another thing, when I go to reboot my recovery it says my device isn't rooted and asks to install superSu, however it was rooted before I entered download mode and started installing bootloader and modem.
Now I have no operating system in the device so i can literally only use Recovery or download mode.
Is my device bricked? I don't know. :crying: :crying:
Pobi123 said:
Guys this is help less.
After rooting my device I followed some instructions to get the Lineage 14. I flashed a BootLoader and a Modem as instructed and went forth to mount USB in order to transfer the custom rom into the device. But this is where the problem is.
It says E: Cant find partition to mount storage. I've tried to reboot, wide, data, storage, system and cache and repair the partition I don't know what else to do.
Anyone else can help? Btw I am fairly new to this stuff so please dumb it down for me.
Another thing, when I go to reboot my recovery it says my device isn't rooted and asks to install superSu, however it was rooted before I entered download mode and started installing bootloader and modem.
Now I have no operating system in the device so i can literally only use Recovery or download mode.
Is my device bricked? I don't know. :crying: :crying:
Click to expand...
Click to collapse
If you can boot recovery, all is not lost.
First, are you sure that you flashed the correct bootloader/modem for your s5 model (G900 T, P, V, F, etc? Odin should not let you flash the wrong one, but anything is possible.
If Bl/modem is correct, them the next thing is to get the custom rom onto the phone.
-make sure you have downloaded everything you need (rom, root method(pref Magisk), gapps if wanted)
- boot into recovery, I'm recommending and assuming that you are using the latest Twrp, if not, d/l official Twrp for your model, and flash that with Odin
-In twrp select wipe, format data, just in case.
-now you should be able to mount usb storage, using the option in twrp
- now you should be able to mount your phone to your PC and transfer the rom, put it somewhere easy to find on the phone. also copy gapps and Magisk zips
-now, still in twrp, select install, select rom zip, select add more, select Magisk zip, also flash gapps at this time if you want to use them.
-click the button to flash
-click wipe cache/dalvik
-click reboot
-pray ?
BlueCyclone said:
If you can boot recovery, all is not lost.
First, are you sure that you flashed the correct bootloader/modem for your s5 model (G900 T, P, V, F, etc? Odin should not let you flash the wrong one, but anything is possible.
If Bl/modem is correct, them the next thing is to get the custom rom onto the phone.
-make sure you have downloaded everything you need (rom, root method(pref Magisk), gapps if wanted)
- boot into recovery, I'm recommending and assuming that you are using the latest Twrp, if not, d/l official Twrp for your model, and flash that with Odin
-In twrp select wipe, format data, just in case.
-now you should be able to mount usb storage, using the option in twrp
- now you should be able to mount your phone to your PC and transfer the rom, put it somewhere easy to find on the phone. also copy gapps and Magisk zips
-now, still in twrp, select install, select rom zip, select add more, select Magisk zip, also flash gapps at this time if you want to use them.
-click the button to flash
-click wipe cache/dalvik
-click reboot
-pray ?
Click to expand...
Click to collapse
Hey man! Thank you so much for your reply. I installed CPE1 bootloader and modem driver, honestly I don't even know what they do. Was this a wrong thing to do?
I rooted my device using cf auto root, then flashed the bootloader and modem using Odin. After that I (stupidly) tried to boot my stock OS and it was stuck in a bootloop.
Unfortunately I won't be able to try your instructions this till tomorrow evening but I'll keep you posted!! do you mind if I pm?
Edit: I was using twrp 2.8.7 I believe, could this have been the problem? Also I updated twrp to latest and tried micro sd as storage and flashed a Rom but the phone is still bootlooping
Pobi123 said:
Hey man! Thank you so much for your reply. I installed CPE1 bootloader and modem driver, honestly I don't even know what they do. Was this a wrong thing to do?
I rooted my device using cf auto root, then flashed the bootloader and modem using Odin. After that I (stupidly) tried to boot my stock OS and it was stuck in a bootloop.
Unfortunately I won't be able to try your instructions this till tomorrow evening but I'll keep you posted!! do you mind if I pm?
Edit: I was using twrp 2.8.7 I believe, could this have been the problem? Also I updated twrp to latest and tried micro sd as storage and flashed a Rom but the phone is still bootlooping
Click to expand...
Click to collapse
Ok I see you have S5 plus. I'm not familiar with that device to know which baseband it should be.
One thing you might try is to boot recovery and clear cache/dalvik and then try booting the custom rom.
If all else fails, you might try Samfirm
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
That should give you a stock firmware file to flash with odin.
You can pm if you need to, I don't own an S5+, nor am I a veteran flasher but I will try to help if I can.
BlueCyclone said:
Ok I see you have S5 plus. I'm not familiar with that device to know which baseband it should be.
One thing you might try is to boot recovery and clear cache/dalvik and then try booting the custom rom.
If all else fails, you might try Samfirm
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
That should give you a stock firmware file to flash with odin.
You can pm if you need to, I don't own an S5+, nor am I a veteran flasher but I will try to help if I can.
Click to expand...
Click to collapse
Ive tried the suggestion you gave me, no success. However I honestly dont know if it could be my fault. I'm gonna flash the stock firmware and restart the whole root process.
Thanks for your help man!
Pobi123 said:
Ive tried the suggestion you gave me, no success. However I honestly dont know if it could be my fault. I'm gonna flash the stock firmware and restart the whole root process.
Thanks for your help man!
Click to expand...
Click to collapse
Ok sorry I couldn't be more help
Oh, you don't need to use of cfautoroot anymore, you can just flash Magisk after the rom, and then use Magisk manager to manage all your root permissions.
So if you are going back to stock, I would:
-Flash stock in Odin
-probably boot stock once to verify (first boot takes long)
-odin flash latest twrp(uncheck auto-reboot, just battery pull after it says pass)
-power on phone with key combo to boot recovery
- format data
-flash rom/gapps?/Magisk
-wipe cache/dalvik
-reboot system (first boot will take long)
Hope you get your phone working again
BlueCyclone said:
Ok sorry I couldn't be more help
Oh, you don't need to use of cfautoroot anymore, you can just flash Magisk after the rom, and then use Magisk manager to manage all your root permissions.
So if you are going back to stock, I would:
-Flash stock in Odin
-probably boot stock once to verify (first boot takes long)
-odin flash latest twrp(uncheck auto-reboot, just battery pull after it says pass)
-power on phone with key combo to boot recovery
- format data
-flash rom/gapps?/Magisk
-wipe cache/dalvik
-reboot system (first boot will take long)
Hope you get your phone working again
Click to expand...
Click to collapse
Good News! Phone is back in full working order after flashing stock firmware. It was kinda scary though, I had to fix an error in Odin and then the phone wouldn't even boot up! Left it over night, booted it again and it worked fine Thanks a lot for your help, I'll try not to soft brick my device again
I have installed custom ROMs on several other tablets but the Samsung Tab A has me stumped.
1) started with the most recent Samsung Rom from SamMobile. Used ODEN, skipped all setup steps to the end. opened Developer Mode and set OEM unlock to YES.
2) PWR+VolUp+Hm to stock recovery, Factory reset.
3) Pwr+VolDn+Hm to download mode. Used ODIN to flash TWRP 3.3.1. Rebooted directly back into recovery not system which was TWRP as expected.
4) Rebooted back to download mode and used ODIN to flash Stock ROM again, again no setups and OEM Unlock Yes
5) Went into Download mode. Reflashed TWRP. Rebooted straight into TWRP again
6) Reformatted Data drive YES and validated drive > 0
7) Flashed Magisk with TWRP
8) Reboot into system. Stock ROM works perfectly and Magisk is working fine.
9) Reboot back into recovery and wiped data and cache
10) Flashed 3 different custom roms (1 after following all the steps above) and I cannot get any of them to progress beyond the animation bootloop.
I have read just about all of the references and others have success following a similar approach.
I am probably missing one small step. Please let me know of any ideas.
Thanks as I really want to move up to a Pie Rom
++++++
Ignore - it looks like all custom roms are for the t580 not p580. sorry.
don502 said:
I have installed custom ROMs on several other tablets but the Samsung Tab A has me stumped.
1) started with the most recent Samsung Rom from SamMobile. Used ODEN, skipped all setup steps to the end. opened Developer Mode and set OEM unlock to YES.
2) PWR+VolUp+Hm to stock recovery, Factory reset.
3) Pwr+VolDn+Hm to download mode. Used ODIN to flash TWRP 3.3.1. Rebooted directly back into recovery not system which was TWRP as expected.
4) Rebooted back to download mode and used ODIN to flash Stock ROM again, again no setups and OEM Unlock Yes
5) Went into Download mode. Reflashed TWRP. Rebooted straight into TWRP again
6) Reformatted Data drive YES and validated drive > 0
7) Flashed Magisk with TWRP
8) Reboot into system. Stock ROM works perfectly and Magisk is working fine.
9) Reboot back into recovery and wiped data and cache
10) Flashed 3 different custom roms (1 after following all the steps above) and I cannot get any of them to progress beyond the animation bootloop.
I have read just about all of the references and others have success following a similar approach.
I am probably missing one small step. Please let me know of any ideas.
Thanks as I really want to move up to a Pie Rom
++++++
Ignore - it looks like all custom roms are for the t580 not p580. sorry.
Click to expand...
Click to collapse
Have you had any luck finding a solution to this?
I am also looking for a working custom ROM for the Tab
Hello,
I do have some questions about upgrading LOS from 16 to 17, maybe someone can help me bringing a little light into this upgrading process.
- Is the sideload way the correct way to do this? ( https:// wiki.lineageos.org /devices /fajita /upgrade)
- What´s about the play services, I dont have any installed ( ..."If you did not have Google Apps installed, you must wipe the Data partition (or perform a factory reset) to install them"...) So if later on I want to install e.g. opengapps I have to wipe all my data after upgrading to 17??? (How? TWRP - wipe -advanced wipe - data and cache ???)
and what´s with all may data? I have titanium backup pro (no SD card), so I backup may phone, put it to my PC, upgrade to 17, wipe all data, put the backup back to phone and reboot?
Or do I have to install Magisk.zip and titanium.zip from within TWRP again first
- What do I do if the sideload fails?
- Can I do the upgrad process with TWRP too? (copying and installing from within TWRP?)
- And what about with the A/B slots, no installing twice on both slots?
As you see, I am unsure on how to do things right and I only did this once before as I installed Lineage OS.
(This would be the way I would do this:
- backup all data to PC
- Boot into TWRP
- copy LOS17.zip. Magisk.zip and Titaniumbackup-pro.zip into internal storage
- install LOS17 and boot into TWRP
- wipe data and cache
- install magisk and TB
- copy all data back and restore? (only user data or the system data too??))
Maybe someone can help me with this. Thanks!
My guide for installing Lineage maybe helpful: Guide Installing Lineage
I would recommend a clean install. Most that have tried to follow that wiki have had issues (if you look in the LOS thread). I haven't used. TB zip, but I did use my TB data from the app without issues. If you dont use Gapps, just dont install them. Skip that step. You still have to reboot to recovery to install Magisk though. I dont think I would try a TB zip until after the first boot.
Installing twice is for the intial install to get the same thing on both slots. You dont want Android 9 on one slot and Android 10 on another, or LOS 17 on one and OOS on another. Once you have LOS 17 on both slots and go to update you will just flash once. See my guide about doing an update.
Thank you for your reply,
so if I got your answer right, I should install the LOS17 like the LOS16 before, as a clean,fresh install.
Seems reasonable to me
I will do the same steps as you gave me before https://forum.xda-developers.com/oneplus-6t/help/instructions-installing-lineage-t3949628
- Backup everything to the PC, so you will need to copy all your data over.
- Sync all your accounts, etc.
- In TWRP format data. Reboot recovery
- Factory Reset.
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Lineage (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Flash TWRP Installer (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Reboot to Recovery (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Flash Gapps
- Flash Magisk
- Reboot to System.
- Then you should be able to setup the device, copy everything back over. Restore your data.
Will do the flash on weekend, then I will let you know....
Thanks.
KKF32 said:
Thank you for your reply,
so if I got your answer right, I should install the LOS17 like the LOS16 before, as a clean,fresh install.
Seems reasonable to me
I will do the same steps as you gave me before https://forum.xda-developers.com/oneplus-6t/help/instructions-installing-lineage-t3949628
- Backup everything to the PC, so you will need to copy all your data over.
- Sync all your accounts, etc.
- In TWRP format data. Reboot recovery
- Factory Reset.
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Lineage (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Flash TWRP Installer (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Reboot to Recovery (This is only the first time, to get the *** rom on both slots, only do this for the first install)
- Flash Gapps
- Flash Magisk
- Reboot to System.
- Then you should be able to setup the device, copy everything back over. Restore your data.
Will do the flash on weekend, then I will let you know....
Thanks.
Click to expand...
Click to collapse
How did it go?
badpanda said:
How did it go?
Click to expand...
Click to collapse
To put it short: a disaster
What I did:
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Magisk
- Flash TB
- Reboot to System.
What I got was a "Qualcom Crashdump Mode" kind of report
What I used: lineage-17.1-20200418-nightly-fajita-signed / twrp-installer-3.3.1-1-fajita / Magisk-v20.4
So I thought maybe the "no factory reset" at the beginning may caused this problem, so I started the whole flashing again.
Long story short: Being distracted I once forgt to flash TWRP after the LOS and now I am stuck in fastboot.
Cant get anymore into TWRP, "fastboot boot TWRP.img" always throws me into fastboot forever wait
Tried to flash TWRP direct from fastboot "fastboot flash recovery twrp.img", always get a write error.
So, at the moment all I can get in is the bootloader, and I have no clou how to get TWRP up and running again.
Edit: Managed to get into TWRP again, but this double flash + Magisk always gives me this "Qualcomm Crashdump Mode"
Help would very much appreciated!
KKF32 said:
To put it short: a disaster
What I did:
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Lineage
- Flash TWRP Installer
- Reboot to Recovery
- Flash Magisk
- Flash TB
- Reboot to System.
What I got was a "Qualcom Crashdump Mode" kind of report
What I used: lineage-17.1-20200418-nightly-fajita-signed / twrp-installer-3.3.1-1-fajita / Magisk-v20.4
Click to expand...
Click to collapse
So you tried to go straight to LOS 17, used an old version of TWRP, and never wiped data while going between Android 9 and 10? None of that will work. I think didn't make it clear, you need you need to be on the OOS 10 firmware first. Flash OOS 10 to both slots, at this point using the fastboot ROM would be my suggestion, like my [Guide]Installing Lineage.
Once you have Android 10 in place one both slots, then start your OS 17 install. Note there is a cliff notes version of that guide in the second post, if you don't want all the "wordy" details.
Oh my, I really didn´t understood the step with "get OOS10 on both slots first"
I am often a little sloppy with details, bad habit, will take some time tomorrow and do the reading and the flashing then.
Thanks again.
KKF32 said:
Oh my, I really didn´t understood the step with "get OOS10 on both slots first"
I am often a little sloppy with details, bad habit, will take some time tomorrow and do the reading and the flashing then.
Thanks again.
Click to expand...
Click to collapse
Make sure you use the"unofficial" version of TWRP, linked to in that guide, rather than the outdated official one you used before as well.
OhioYJ said:
Make sure you use the"unofficial" version of TWRP, linked to in that guide, rather than the outdated official one you used before as well.
Click to expand...
Click to collapse
So, LOS17 is up and running, I did it the long way but good to know the fastboot Rom method now. I confess some part of this thread would not have been necessary if had read your installations instruction carefully....
So let me thank you for patience und help, "Reading broadens the mind", I often tell others, will remind myself nexttime