Related
I've got DU 12.2 OFFICIAL installed on my phone now and am having some problems, Any gapps i try to install fails, i can receive calls but cant make any using data or wifi, my memory card works fine in the phone but doesn't show up on the computer, when i hook my phone up to the computer i cant get into download/fastboot mode, shows no devices on the devices command. i have to boot into fastboot by powering off the phone and doing the volume down + power then everything works fine. Any ideas what I may have done wrong or what the problem might be?? I was on stock Oreo 8.0 rooted w/twerp installed, done a full wipe a couple times before i flashed just to be safe..
Gapps are preinstalled. Do not flash any. I haven't had any calling issues with Sprint. Memory card shows up with adb disabled for windows and enabled for Linux. Adb reboot-bootloader works for me on both windows 7 and Linux. APM works as well from developer options (Advanced Power Menu).
Just my experiences running DU for the past two months
Uzephi said:
Gapps are preinstalled. Do not flash any. I haven't had any calling issues with Sprint. Memory card shows up with adb disabled for windows and enabled for Linux. Adb reboot-bootloader works for me on both windows 7 and Linux. APM works as well from developer options (Advanced Power Menu).
Just my experiences running DU for the past two months
Click to expand...
Click to collapse
Hi, what steps did you take to flash the rom?? I tried to reflash again with the same results. I wiped everything except OEM and micro SD card. did you flash the official or one of the weeklies?? this is the version ive been trying to flash: du_nash-v12.2-20180511-0850-OFFICIAL
blake .l said:
I've got DU 12.2 OFFICIAL installed on my phone now and am having some problems, Any gapps i try to install fails, i can receive calls but cant make any using data or wifi, my memory card works fine in the phone but doesn't show up on the computer, when i hook my phone up to the computer i cant get into download/fastboot mode, shows no devices on the devices command. i have to boot into fastboot by powering off the phone and doing the volume down + power then everything works fine. Any ideas what I may have done wrong or what the problem might be?? I was on stock Oreo 8.0 rooted w/twerp installed, done a full wipe a couple times before i flashed just to be safe..
Click to expand...
Click to collapse
I can give you my experience with DU. I ran the RC version which had recently had the issue with sdcard fixed. Like Uzephi said, no need for gapps, they're already baked in. As for adb/fastboot, you just need to reinstall the drivers, and manually add the moto adb driver when your device is in charge only mode. Then you should be able to run those commands just like always. I can elaborate more on that if you need. As far as flashing, I followed the flashing instructions for the AOSiP rom and flashed the 27.1 prep zip as well. Though the prep zip might be unnecessary if you have oreo on both slots. Uzephi would know better than I as far as that goes. I know the RCs and weeklies are signed differently, so no dirty flashing between the two. It might be better to flash the prep zip to have a clean slate on both slots.
Anyway, that was my experience. Hope that answers some of your questions.
blake .l said:
Hi, what steps did you take to flash the rom?? I tried to reflash again with the same results. I wiped everything except OEM and micro SD card. did you flash the official or one of the weeklies?? this is the version ive been trying to flash: du_nash-v12.2-20180511-0850-OFFICIAL
Click to expand...
Click to collapse
I use RC since I live on the wild side (I have tried to hard brick this phone so many times, only thing I won't try is locking BL since that's a stupid way to hard brick.) Airwalk says it perfectly. If you have Oreo on both slots, no need for the prep zip. I flash twrp.zip after booting into twrp, reboot recovery, flash rom, flash twrp again, reboot recovery, flash my kernel, flash magisk, reboot bootloader, fastboot -w, then boot to system.
Obviously I take more steps than needed. That's to flash my kernel, root and twrp after the flash before booting which isn't advised (wild child over here), you should fully boot first, then do the flashing of root, kernel, twrp, etc.
41rw4lk said:
I can give you my experience with DU. I ran the RC version which had recently had the issue with sdcard fixed. Like Uzephi said, no need for gapps, they're already baked in. As for adb/fastboot, you just need to reinstall the drivers, and manually add the moto adb driver when your device is in charge only mode. Then you should be able to run those commands just like always. I can elaborate more on that if you need. As far as flashing, I followed the flashing instructions for the AOSiP rom and flashed the 27.1 prep zip as well. Though the prep zip might be unnecessary if you have oreo on both slots. Uzephi would know better than I as far as that goes. I know the RCs and weeklies are signed differently, so no dirty flashing between the two. It might be better to flash the prep zip to have a clean slate on both slots.
Anyway, that was my experience. Hope that answers some of your questions.
Click to expand...
Click to collapse
You beat me to it! I think we have a race going on here, lol. You are correct 100% though
41rw4lk said:
I can give you my experience with DU. I ran the RC version which had recently had the issue with sdcard fixed. Like Uzephi said, no need for gapps, they're already baked in. As for adb/fastboot, you just need to reinstall the drivers, and manually add the moto adb driver when your device is in charge only mode. Then you should be able to run those commands just like always. I can elaborate more on that if you need. As far as flashing, I followed the flashing instructions for the AOSiP rom and flashed the 27.1 prep zip as well. Though the prep zip might be unnecessary if you have oreo on both slots. Uzephi would know better than I as far as that goes. I know the RCs and weeklies are signed differently, so no dirty flashing between the two. It might be better to flash the prep zip to have a clean slate on both slots.
Anyway, that was my experience. Hope that answers some of your questions.
Click to expand...
Click to collapse
Good deal brother thanks for the info.... I will give it a try for sure.....
blake .l said:
Good deal brother thanks for the info.... I will give it a try for sure.....
Click to expand...
Click to collapse
Let us know how it goes
Uzephi said:
Let us know how it goes
Click to expand...
Click to collapse
Well guys I followed the the flashing instructions for the install guide from the AOSiP ROM to the "T" going from stock 27.1 Oreo 4 different times today to no avail, I came up with the same outcome as before. No calling, mem card not showing up on computer, having to manually boot into fastboot and so on. I downloaded Los 15.1 and followed the same procedure as with DU and it works like a charm. I just hope now it keeps getting updates Thanks again for your help and suggestions guys
blake .l said:
Well guys I followed the the flashing instructions for the install guide from the AOSiP ROM to the "T" going from stock 27.1 Oreo 4 different times today to no avail, I came up with the same outcome as before. No calling, mem card not showing up on computer, having to manually boot into fastboot and so on. I downloaded Los 15.1 and followed the same procedure as with DU and it works like a charm. I just hope now it keeps getting updates Thanks again for your help and suggestions guys
Click to expand...
Click to collapse
Try the RC from 0509. I have been running it since the 9th with no issues.
I've tried to follow the instructions here (https://plus.google.com/communities...5/stream/2a745c1e-aae6-4b50-93dd-14417258d7ce).
I did a huge mistake of thinking that flashing for slot a and slot b was the same of step (2/2) I saw in the screen.
I was coming from Stock Nougat (7.1.1) and, most probably, I finished having oreo in one slot and nougat in the other.
I reflashed TWRP as per instructions.
When I tried to reboot, phone got dead (no charge, no turning on, and no bootloader...). This scared me totally. I unbrick some Asus, Google and Samsung before. But this time it was too premature and having no bootloader is unbelievable.
Will the AOSiP guide will work now for me? I'm with Oreo (don't know how to check if on both slots...), but if a new phone.
Does anybody know why we can't have a DU thread here in xda?
Technical said:
I've tried to follow the instructions here (https://plus.google.com/communities...5/stream/2a745c1e-aae6-4b50-93dd-14417258d7ce).
I did a huge mistake of thinking that flashing for slot a and slot b was the same of step (2/2) I saw in the screen.
I was coming from Stock Nougat (7.1.1) and, most probably, I finished having oreo in one slot and nougat in the other.
I reflashed TWRP as per instructions.
When I tried to reboot, phone got dead (no charge, no turning on, and no bootloader...). This scared me totally. I unbrick some Asus, Google and Samsung before. But this time it was too premature and having no bootloader is unbelievable.
Will the AOSiP guide will work now for me? I'm with Oreo (don't know how to check if on both slots...), but if a new phone.
Does anybody know why we can't have a DU thread here in xda?
Click to expand...
Click to collapse
See this thread for my experience with a similar issuehttps://forum.xda-developers.com/z2-force/help/gotta-super-slim-brick-t3798403
mookiexl said:
See this thread for my experience with a similar issuehttps://forum.xda-developers.com/z2-force/help/gotta-super-slim-brick-t3798403
Click to expand...
Click to collapse
Posted there, thanks. But I'm not sure if it is all the same, for all Z2 models. I can't find a DU step by step tutorial. There are some details that expert people are not writing and I'm new to Motorola, slot a/b, etc. I'm not a newbie, just that this phone has a lot of peculiarities...
Technical said:
Posted there, thanks. But I'm not sure if it is all the same, for all Z2 models. I can't find a DU step by step tutorial. There are some details that expert people are not writing and I'm new to Motorola, slot a/b, etc. I'm not a newbie, just that this phone has a lot of peculiarities...
Click to expand...
Click to collapse
My AOSiP instructions is how I installed to the T. I did no other steps. I did that on every install from stock to an AOSP based ROM. I have not yet bricked to 9008 mode to try blank flashing yet to verify instructions on how to do that.
Uzephi said:
My AOSiP instructions is how I installed to the T. I did no other steps. I did that on every install from stock to an AOSP based ROM. I have not yet bricked to 9008 mode to try blank flashing yet to verify instructions on how to do that.
Click to expand...
Click to collapse
Thanks. I've moved to https://forum.xda-developers.com/showpost.php?p=76754449&postcount=24 to ask you about .zip preparation file for XT1789-05 model.
Uzephi said:
Try the RC from 0509. I have been running it since the 9th with no issues.
Click to expand...
Click to collapse
Well I tried the RC from 05/09/18 and the newest version of RC, followed the same flashing guide to the "T"and got the same results, phone can receive calls but cant make any, cant boot to fastboot through computer etc. went back to Los and all works fine. I dont know what the problem is wit DU and my phone..
blake .l said:
Well I tried the RC from 05/09/18 and the newest version of RC, followed the same flashing guide to the "T"and got the same results, phone can receive calls but cant make any, cant boot to fastboot through computer etc. went back to Los and all works fine. I dont know what the problem is wit DU and my phone..
Click to expand...
Click to collapse
They tell you need to flash to both slots. Here on xda, devs say we need to flash ROM just to one slot. Of course, I'm not sure this is the problem. Just trying to imagine myself at DU.
By the way, are there any settings (customization) present in DU that AOSIP does not have?
Technical said:
They tell you need to flash to both slots. Here on xda, devs say we need to flash ROM just to one slot. Of course, I'm not sure this is the problem. Just trying to imagine myself at DU.
By the way, are there any settings (customization) present in DU that AOSIP does not have?
Click to expand...
Click to collapse
A few things, yes. Mainly the dirty tweaks in settings
Didn't really care for the DU. Although it does have working 4g on sprint(much props there). I just didn't personally like the "feel" of it. I'm rockin the unofficial LOS 15.1 right now and its pretty lovely. I'm limited to ROMs b/c of sprint but so far LOS kicks ass.
Hi, I'm replacing a lost Moto G3 TE with a Moto G5 (xt1671 dual sim) that should be coming in the mail on Monday. I'd like to do whatever mods I want to my phone right away, before activating my google account on it and everything. So, I'd really like any advice any of you can give as to preferred custom rom with root that I should put on my new phone, so I can get to it right away. I've already found the thread to unlock it (same process as in past mostly), and I've found the guides for putting on TWRP (either 32-bit or 64-bit). So, now I just need to decide which custom ROM to use. Please advise!
I've also had a Moto G2 in the past. I've unlocked and used custom roms and root on all my phones so far, from Cyanogenmod 12.1 to AOSP Extended, ViperOS, and LineageOS. My wife's Moto G2 has Oreo on it (through AEX) and we're enjoying it (I had her add me as an account until I get my new phone). So, I'd like to continue using an Oreo system if possible, and I'd even prefer AEX, but it seems that it's discontinued for the Moto G5. Is that correct?
My overall goals for a custom rom are, in order of priority: reliability, speed/performance, battery life, and customization options. I found that AEX balanced all of that well on our past phones. Is the discontinued AEX for this phone reliable, or not? I've also seen the LineageOS thread and the KAOSP thread and have glanced at a few others. I use google accounts and half their apps for sure (so I'll want to install a GApps package with it). And I see there's a possibility to unlock RAW/DNG files for the camera, which I'd really like to try (as I prefer raw file editing instead of JPGs). And the customizations I like (if still possible) are mainly involving the way the launcher responds - I like having the navigation buttons hide, or to swipe up to get them back, I like being able to modify the status bar, etc.... typical customizations that were usually available in AEX that I've used. I also use root for file explorer and a few other functions - I used to always use SuperSU in the past, but just recently started using Magisk (on the Moto G2) and it seems good, though I'm open to any recommendation about which root to use.
So, please fire away! Please give your suggestion as to which currently available custom ROMs are stable, have good performance, good battery life, and offer standard customization, plus which I can root. I appreciate any suggestions and any advice you can give, especially regarding if there's a recommended rom but if it has known issues and any known workarounds. Also, I'd appreciate advice anytime today or tomorrow (since it'll likely be the afternoon or evening of Monday +3 GMT time - Madagascar - that I'm able to start working on unlocking it, installing custom recovery, etc.). But even if the advice is late, I might still be able to use it. I know this is a bit much to ask, but please give your own opinions freely!
Oh, by the way, do I need updated Motorola drivers, or will the motorola drivers and adb/fastboot I installed last time (for the Moto G3 TE) keep working with the new phone? The unlock thread I've found here doesn't say anything about motorola drivers or adb/fastboot. Thanks in advance!
the best stable rom is stock rooted
woozie.2007 said:
the best stable rom is stock rooted
Click to expand...
Click to collapse
Thanks for the response! Is there a stock oreo available? And is stock rooted still customizable (like with AEX or something - can I install some sort of thing to let me customize it more?). And is there a debloated version of the stock rom available? I saw one thread on here about a debloated stock rom, but it looked like it was still nougat.
If it's possible to customize the stock rom further, please point me in the right direction. And if not possible to customize it further... then are you suggesting that any of the custom roms available aren't very stable to be used well for a daily driver?
Again, thanks for your response and also for any more feedback you can give!
So, I have my phone now and it came with stock Nougat. I've unlocked it, and I'm currently working on getting TWRP, Dm-verity thing on it, and then magisk. After that can I still update it to Oreo or not? Please advise. Thank you!
madagascaradam said:
So, I have my phone now and it came with stock Nougat. I've unlocked it, and I'm currently working on getting TWRP, Dm-verity thing on it, and then magisk. After that can I still update it to Oreo or not? Please advise. Thank you!
Click to expand...
Click to collapse
no, you have to update oreo first, after that install twrp and magisk for root it
woozie.2007 said:
no, you have to update oreo first, after that install twrp and magisk for root it
Click to expand...
Click to collapse
Crud, that sucks! I was already finished rooting and everything on magisk, then I let the OTA update download and when it restarted my phone, it just automatically sends it into recovery (TWRP) every time now! I tried to install this TWRP stock Oreo (dirtying flashing it) hoping it would fix the boot-loop-to-TWRP-recovery problem, but it didn't. So now I need to figure out a way to get back to the original, so I can start over and try again.
I'm trying to do a factory reset and try again, but in TRWP it says ""Failed to mount '/data' (Device or resource busy)'" This sucks! Any ideas where I can go or what I can do (such as some fastboot commands or something) to get it all working again?
EDIT: It does reboot to bootloader though, so it's not hardbricked. Just need to figure out what to do from here. Thanks for any help!
try to flash via fastboot only boot, recovery, oem and system from oreo, then aply update, then root
Thanks! I downloaded the firmware (for latest Nougat) from this thread: https://forum.xda-developers.com/g5/development/stock-upgrade-to-official-stock-oreo-8-t3823598
Then I flashed everything they said through fastboot (ignoring the modem stuff) because I'm still downloading the oreo firmware right now anyway (my connection is quite slow). At first the bootloader got stuck and said "error" and I was freaking out thinking I'd hard-bricked it. But I turned it off and on again anyway and it loaded fine back into nougat for that latest version.
So now I'm downloading the latest stock Oreo and I'll probably try to ADB sideload it.
Which root do you recommend? I have the Magisk I did for nougat that worked great - 11.6 But there's this thread here (https://forum.xda-developers.com/g5/how-to/guide-how-to-root-stock-oreo-8-1-soak-t3832347) that talks about what seems like a complicated way of doing Magisk 15.3 and then getting it up to 16. What do you suggest?
magisk 17.1 its ok, but you have to flash only partition that i said, not full firmware, and DONT flash the bootloader and GPT partition
---------- Post added at 06:11 PM ---------- Previous post was at 06:10 PM ----------
better let the phone to update ota for latest security patch, dont flash via fastboot
OK, I installed the stock oreo through ADB sideload (it wouldn't read my storage for some reason).... then I reinstalled TWRP, no problem... then installed Magisk 17.1 (per your suggestion) and then the apk for the manager. Everything's working great! Didn't even need that dm-verity thing.
I'm still looking into the mods I can do to it now that it's rooted (such as changing boot logo and boot animation, adding that 'camera 2' setting, etc.) So I'm not sure I'm at a finished product yet, but I'm definitely at a stable rooted oreo with all my regular stuff installed, so that's a good place to start! I've made a nandroid backup here in case any of my further experimenting messes it up.
Thanks again for your help! And if you can give any suggestions towards the best way to customize the look (for example - is nova launcher still the best way to do that?) or other aspects of the system UI, while still being on this stock rom, then please let me know. I'll look up how to get that better camera mode working.
woozie.2007 said:
magisk 17.1 its ok, but you have to flash only partition that i said, not full firmware, and DONT flash the bootloader and GPT partition
---------- Post added at 06:11 PM ---------- Previous post was at 06:10 PM ----------
better let the phone to update ota for latest security patch, dont flash via fastboot
Click to expand...
Click to collapse
Could you help me with this: if I backup my system (everything) with TWRP.... can I then switch to a custom rom to try it out (in case I want a different user interface, more tweaks, etc.) and if I don't like it can I easily switch back to the stock rom nandroid backup I have saved in TWRP (thus restoring my previous state, but without having to start from factory reset)? Or would it be difficult to switch back - like would I have to redo it through fastboot or something and factory reset, etc.?
I'm asking because in the past I never used the stock rom much and I definitely never switched between a custom rom and the stock rom. Once I went for custom rom, I didn't go back - so I don't know if it's as simple as restoring a nandroid backup or if it's much more effort. Please let me know. Thanks a lot!
you must be very carefully because most of the custom roms need twrp on 64 bits, now you have official twrp 32. When you come back from custom roms 64bit to previous nandroid backup, you must install 32 bits twrp, otherwise you may lose the imei of the phone, just read very well when you want to do something risky
woozie.2007 said:
you must be very carefully because most of the custom roms need twrp on 64 bits, now you have official twrp 32. When you come back from custom roms 64bit to previous nandroid backup, you must install 32 bits twrp, otherwise you may lose the imei of the phone, just read very well when you want to do something risky
Click to expand...
Click to collapse
OK, thanks a lot for that helpful info! So just to clarify to be sure: basically, if I want to switch back and forth, I'll install the 64-bit twrp first, then the custom rom(s). Then if I want to come back to my stock image backup, I re-install the 32-bit twrp (like the one I'm currently using) and then I can just restore my nandroid backup I took of the stock and all is well? And it's not risky if I do it like that?
yes, its correct that
Hey everyone,
I've been trying to install Lineage OS on my Moto Z2 Force for about two months now and I'm starting to get pretty desperate
Every time I try to sideload Lineage via ADB (after flashing TWRP), the sideload fails at 47% stating "Total xfer: 1.00x". I tried half a dozen different versions of Lineage nightly for nash (15 and 16) but the result was always the same. I wasn't able to find a solution to my problem on the internet so I'd love for you to share your thoughts on this!
vincetoxicum said:
Hey everyone,
I've been trying to install Lineage OS on my Moto Z2 Force for about two months now and I'm starting to get pretty desperate
Every time I try to sideload Lineage via ADB (after flashing TWRP), the sideload fails at 47% stating "Total xfer: 1.00x". I tried half a dozen different versions of Lineage nightly for nash (15 and 16) but the result was always the same. I wasn't able to find a solution to my problem on the internet so I'd love for you to share your thoughts on this!
Click to expand...
Click to collapse
Awhile back I tried los, but I was having trouble with sideload too. I ended up just flashing it in twrp like a regular rom. Others who use los more and have more experience with it might have a better answer for you, but that worked for me. Just make sure that you have the base firmware required installed, and don't forget to format data.
Normally working fine. Read carefully the manual from lineage.org and learning by doing. Read the changelogs, too. That's helpful and read so much ypu can about A/B partion and if then working, don't update over Updater for few days. There is a bug, which is in the next days be fixed. So, you must invest some time to understand all. Here it was not easy, too. Maybe 2 days to learn from mistakes. Then you get it working.
41rw4lk said:
Awhile back I tried los, but I was having trouble with sideload too. I ended up just flashing it in twrp like a regular rom. Others who use los more and have more experience with it might have a better answer for you, but that worked for me. Just make sure that you have the base firmware required installed, and don't forget to format data.
Click to expand...
Click to collapse
Thank you for your reply! So what exactly would you propose I do? Wipe with TWRP first, then return to Fastboot and flash los from there?
Before booting I'd like to install an open gapps package which must be done before booting los for the first time. Could I do that via Fastboo as well?
vincetoxicum said:
Hey everyone,
I've been trying to install Lineage OS on my Moto Z2 Force for about two months now and I'm starting to get pretty desperate
Every time I try to sideload Lineage via ADB (after flashing TWRP), the sideload fails at 47% stating "Total xfer: 1.00x". I tried half a dozen different versions of Lineage nightly for nash (15 and 16) but the result was always the same. I wasn't able to find a solution to my problem on the internet so I'd love for you to share your thoughts on this!
Click to expand...
Click to collapse
Just flash it through twrp like a normal rom I have never heard of anyone sideloading a custom rom. If you're using a carrier variant of the Moto Z2 Force that may give you some issues too.
Hybrid Theory said:
Just flash it through twrp like a normal rom I have never heard of anyone sideloading a custom rom. If you're using a carrier variant of the Moto Z2 Force that may give you some issues too.
Click to expand...
Click to collapse
The wiki says to sideload for a reason -- you can bungle up FBE encryption keys by storing stuff in TWRP on a device where FBE decruption in TWRP is attempted (nash).
vincetoxicum said:
Thank you for your reply! So what exactly would you propose I do? Wipe with TWRP first, then return to Fastboot and flash los from there?
Before booting I'd like to install an open gapps package which must be done before booting los for the first time. Could I do that via Fastboo as well?
Click to expand...
Click to collapse
Follow the wiki description - it's a TWRP bug that sideload only goes to 47% - though it has actually suceeded. It would turn red and say "Failed" if it failed.
41rw4lk said:
Awhile back I tried los, but I was having trouble with sideload too. I ended up just flashing it in twrp like a regular rom. Others who use los more and have more experience with it might have a better answer for you, but that worked for me. Just make sure that you have the base firmware required installed, and don't forget to format data.
Click to expand...
Click to collapse
See above - it didn't fail.
Because of the A/B partition, you can only install through a temporary twrp. If you try permanent twrp, you won’t be able to boot
Same problem with Lineage Recovery. Followed exactly the wiki but it stays the same 15.1 version.
I'm on T-Mobile and I ALWAYS had that problem, totally forgot about it at this point. Just ignore it, the rom is flashes successfully anyway
Dany XP said:
I'm on T-Mobile and I ALWAYS had that problem, totally forgot about it at this point. Just ignore it, the rom is flashes successfully anyway
Click to expand...
Click to collapse
Well, but after reboot the new rom is not flashed or active (might be in one of A/B but no switch of slots).
carlos22b said:
Well, but after reboot the new rom is not flashed or active (might be in one of A/B but no switch of slots).
Click to expand...
Click to collapse
You might be right but last time I fastboot flashed anything was some time ago. Maybe after flashing I had to manually switch slot? I don't remember. I'm in Lineage 16 and is working great
Dany XP said:
You might be right but last time I fastboot flashed anything was some time ago. Maybe after flashing I had to manually switch slot? I don't remember. I'm in Lineage 16 and is working great
Click to expand...
Click to collapse
Ok. How can I change the slot manually?
carlos22b said:
Ok. How can I change the slot manually?
Click to expand...
Click to collapse
Of course, there Is a fastboot command for that, very simple. Just google it
Changed it so slot b - now bootloop in both a and b
This A/B system is really no help for custom roms...
Now try to flash with temporary twrp.
Same here.
Device: sweet TWRP: 3.6.1 and 3.6.2
Bash:
adb sideload CARBON-CR-9.0-R-WEEKLY-sweet-20230501-0124.zip
serving: 'CARBON-CR-9.0-R-WEEKLY-sweet-20230501-0124.zip' (~47%)
adb: failed to read command: Success
ROM flashed, booted, and seem to work fine.
EDIT:
It is normal. Found this:
https://www.reddit.com/r/LineageOS/comments/af12lu/_/edvwaex
That's an ADB issue, nothing is wrong with the device, cable, PC or the installation process.
If I remember correctly (from a discussion long ago), Google's ROMs are transferred about 2.2 times across the sideload. To make the progress bar add up to 100%, they said "2.2 times the file size equals 100%". Our ZIPs are transferred just once, so the final progress is at about 47% with a success. The xfer seems to show the transferred data compared to the file size. Ours clocks in at x1.00 or x1.01, while Google's is about x2.something.
Click to expand...
Click to collapse
So I had rooted my Tab S back in 2016 or so (if you check the forums here you'll see my posts for this...). Have had that working for a while now. It tripped the Knox (I didn't personally care about this) except now I want to install a couple streaming apps on the tablet and the OS is too old to handle it
I had loaded TWRP onto the Tab S and rooted it with Lollipop stock ROM and loaded it with SuperSU. It has worked like a charm up till now, issues with Link2SD notwithstanding (I have ZERO intentions of going back to that app).
My question is: what do I need to do to install the newest possible version of Android that the tablet can take? I know it's an older tablet now but I still use it for reading and other stuff, and I'd like to keep it alive a bit longer by installing a new Android OS and ROM on it.
(aside: I did remove a bunch of stuff once I rooted it, so I am not sure how much this may interfere with any attempt to update it to a newer version of Android)
(aside #2: I never updated SuperSU through the app store as I was afraid it would break the root process, so I left that app alone and eventually it stopped showing up in my update list on google play. I'd have to check the tablet to see what version of it I have installed at present)
Funny, I just updated my Tab S this weekend. Same as you, was running into apps that no longer support older OS. I updated mine to Lineage 14.1 version. So far working fine. I know there is a newer version but after reading the threads, this version seemed to be reported as working better. Just follow the instructions in the thread to upgrade.
cbb77 said:
Funny, I just updated my Tab S this weekend. Same as you, was running into apps that no longer support older OS. I updated mine to Lineage 14.1 version. So far working fine. I know there is a newer version but after reading the threads, this version seemed to be reported as working better. Just follow the instructions in the thread to upgrade.
Click to expand...
Click to collapse
Hey thanks for your reply!
Do you need to update the android version to get Lineage OS installed?
No you do not. You just have to update the bootloader. Instructions are in the thread on how to as well as to have to confirm.
Hi again,
Sorry could you point me in the direction of said thread?
cbb77 said:
No you do not. You just have to update the bootloader. Instructions are in the thread on how to as well as to have to confirm.
Click to expand...
Click to collapse
Wait I think I found it. Was this it?
https://forum.xda-developers.com/galaxy-tab-s/development/rom-lineageos-14-1-sm-t800-t3545080
bsquared938 said:
Wait I think I found it. Was this it?
https://forum.xda-developers.com/galaxy-tab-s/development/rom-lineageos-14-1-sm-t800-t3545080
Click to expand...
Click to collapse
Yes, that is the correct thread.
cbb77 said:
Yes, that is the correct thread.
Click to expand...
Click to collapse
Perfect. Will also update this table to give it a further lease on life .
Thanks man!
cbb77 said:
Yes, that is the correct thread.
Click to expand...
Click to collapse
@cbb77
Cannot find the Lineage OS ROM image, I think it may have been removed from their site given the age.
Do you have a working download link for this?
Edit: please ignore post, I found it as soon as I posted this -.-
T800 https://download.exynos5420.com/LineageOS-14.1-Deathly/chagallwifi/
Pretty bood performance and battery,also GPU OC.Load this with Gapps.
Trung Gs said:
T800 https://download.exynos5420.com/LineageOS-14.1-Deathly/chagallwifi/
Pretty bood performance and battery,also GPU OC.Load this with Gapps.
Click to expand...
Click to collapse
I assume I have to load the marshmallow bootloader before I do anything?
bsquared938 said:
I assume I have to load the marshmallow bootloader before I do anything?
Click to expand...
Click to collapse
Personally I like the Resurrection Remix rom. https://forum.xda-developers.com/ga...om-resurrection-remix-n-sm-t800-wifi-t3606243
Just do the standard stuff. You've got TWRP installed, so you're most of the way there. Back up whatever you want to back up, and then:
1. Wipe System, Data, Cache, and Dalvik Cache.
2. Install OS.
3. Install Magisk (if you want to use Magisk for your rooting needs. It seems to be the popular root tool now. It's pretty boss.)
4. Reboot into system, then back into recovery, and:
5. Install GApps or whatever. I like NanoDroid myself. It's the alternative to GAPPS. There are a few odd programs that just plain won't work with it yet, but the official Google apps have an annoying habit of wasting processing power on pointless background nonsense, so I prefer the alternative. Also there's an Xposed module that improves compatibility. https://nanolx.org/nanolx/nanodroid
Hmm I'll take a look at this other ROM
Currently, I have a rooted stock ROM (SuperSU ad root manager), and interested in moving to a custom ROM that is well supported
My only 2 concerns before starting are:
1) Do I need to update SuperSu
2) Do I need to update the bootloader before doing anything else (even the ROM that you suggested @FailSafeNow ? )
Anyone who was wondering what happened:
Process I used (done 2 days ago as of this post):
0) transferred all relevant files to device for the operation, backed up stuff I wanted
1) Updated bootloader to marshmallow via ODIN
2) Updated TWRP to 3.x (forgot exact version) from within TWRP
3) Wiped system + data + cache (I could have probably wiped internal memory but there wasn't much there anyways)
4) Installed Lineage OS 14.1 and Nano Gapps from within TWRP (in that order)
( full disclosure: I had wrong Gapps .zip file the first time and had to get the right one afterwards)
While I had the superSU package, I decided not to root the tablet again. I don't think I need the customization that root offers this time around especially since Lineage OS is already so lightweight compared to the stock ROM I just replaced...
Thanks all for your help!!
Over and out
Thanks all! Nice super fast tablet with amazing battery life now
bsquared938 said:
Anyone who was wondering what happened:
Process I used (done 2 days ago as of this post):
0) transferred all relevant files to device for the operation, backed up stuff I wanted
1) Updated bootloader to marshmallow via ODIN
2) Updated TWRP to 3.x (forgot exact version) from within TWRP
3) Wiped system + data + cache (I could have probably wiped internal memory but there wasn't much there anyways)
4) Installed Lineage OS 14.1 and Nano Gapps from within TWRP (in that order)
( full disclosure: I had wrong Gapps .zip file the first time and had to get the right one afterwards)
While I had the superSU package, I decided not to root the tablet again. I don't think I need the customization that root offers this time around especially since Lineage OS is already so lightweight compared to the stock ROM I just replaced...
Thanks all for your help!!
Over and out
Thanks all! Nice super fast tablet with amazing battery life now
Click to expand...
Click to collapse
I know this is a somewhat old thread. I have a T800 myself and am looking for a ROM. Want to try Lineage OS 14.1 like you have tried. Was curious as to whether you still have it and if you still liked it? If so, what version are you running now and how is your battery life compared to stock? Thanks so much! :good:
Hi,
Some weeks ago I've got a LG V20 and followed some tutorials I found (without reading enough) to install LOS 17.1 with Twrp, Magisk and Viper4Android.
Then I was so dumb to enable LOS' encryption...now the problems start: I cannot install OTA Updates anymore. Twrp says "Decryption failed, cannot mount".
So...in short...how do I get updates now?
Some hours ago I installed LOS' recovery - but it also seems to be not working as expected: when I select " install update" in Lineage, it reboots into recovery - and thats it. No update is installed automatically as Twrp did normally. Can I use this with my already installed Magisk etc and encryption turned on at all? Or do I def need to use Twrp?
It would be very cool if someone here could help to get the decryption in Twrp work...that would be the best way for all and future users in my opinion.
However, I am stuck now with an encrypted phone, installed Magisk - and do not really know how to get an update of LOS the best way.
Many thanks already for every help
Ms0206 said:
Hi,
Some weeks ago I've got a LG V20 and followed some tutorials I found (without reading enough) to install LOS 17.1 with Twrp, Magisk and Viper4Android.
Then I was so dumb to enable LOS' encryption...now the problems start: I cannot install OTA Updates anymore. Twrp says "Decryption failed, cannot mount".
So...in short...how do I get updates now?
Some hours ago I installed LOS' recovery - but it also seems to be not working as expected: when I select " install update" in Lineage, it reboots into recovery - and thats it. No update is installed automatically as Twrp did normally. Can I use this with my already installed Magisk etc and encryption turned on at all? Or do I def need to use Twrp?
It would be very cool if someone here could help to get the decryption in Twrp work...that would be the best way for all and future users in my opinion.
However, I am stuck now with an encrypted phone, installed Magisk - and do not really know how to get an update of LOS the best way.
Many thanks already for every help
Click to expand...
Click to collapse
There are many v20 variants. Are you sure, you selected the correct version? In your case i would start with a clean installation following the official lineageOS guide.
kurtn said:
There are many v20 variants. Are you sure, you selected the correct version? In your case i would start with a clean installation following the official lineageOS guide.
Click to expand...
Click to collapse
Yes, I am sure...its a Vs995.
The way youre asking is interesting and I wonder a bit why...it implicates to me that either Twrp should work with encrypted LOS 17.1 - or Lineage its recoverymode with Magisk, Viper / my installed stuff.
I'll now take a look into the official LOS guide...
Edit: i don't get it. I assume sideload through Twrp does not work (encryption !). Recoverymode of LOS does not even ask for the password so I assume it also does not work with encryption turned on. Or does it? If so, how??
Is there any readme/wiki for the LOS-recoverymode?
Again, my device is encrypted. Magisk and other things are installed.
So how to update without any available recoverymode that is able to decrypt?
Ms0206 said:
Yes, I am sure...its a Vs995.
The way youre asking is interesting and I wonder a bit why...it implicates to me that either Twrp should work with encrypted LOS 17.1 - or Lineage its recoverymode with Magisk, Viper / my installed stuff.
I'll now take a look into the official LOS guide...
Edit: i don't get it. I assume sideload through Twrp does not work (encryption !). Recoverymode of LOS does not even ask for the password so I assume it also does not work with encryption turned on. Or does it? If so, how??
Is there any readme/wiki for the LOS-recoverymode?
Again, my device is encrypted. Magisk and other things are installed.
So how to update without any available recoverymode that is able to decrypt?
Click to expand...
Click to collapse
Your data Partition is encrypted. Sideload does not touch data partition. Follow the guide
As if I didn't know it before, following the official guides producing the same errors as using Twrp.
I tried so many things...using official recovery does not install OTA automatically.
Sideload producing the same errors as using Twrp - "Magisk addond.d failed, cannot find Magisk binaries, reflash OTA Form decrypted recovery or reflash Magisk".