-Screwed up somewhere as my goal was to install LineageOS and try to use it on an At&t mvno.
-Package was unopened for months, so it still had the older firmware.
-Everything seemed okay after I unlocked the bootloader.
-Then I installed TWRP.
-Did a backup of everything using TWRP before I was going to try and root the device.
-I knew something was wrong when no verity opt encrypt and Magisk gave some error message and failed.
-Now whenever I boot the device, I get a N/A in the top left corner and then goes into TWRP.
-Restoring the backup using TWRP did nothing.
-I thought this would be the solution (dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1M), but I get the bad key first and then N/A before going back to TWRP.
https://forum.xda-developers.com/moto-e4/help/moto-e4-metro-variant-rebooting-to-twrp-t3825841
What should I do now?
Any help would be appreciated. Even links to other posts that dealt with this issue is fine. Be aware that my skill level is only a little better than following Youtube videos.
Thank you.
N/A is normal. It will be there forever after you unlock bootloader. Did you format data in TWRP and type yes to format?
Thanks for the reply.
As far as I know, I did not format within TWRP. Is that my next step? If not, please advice what should be done next.
My concern is something is wrong because both the suggestions you gave in that other thread did not result in the phone booting to Android properly.
ah-le-le said:
Thanks for the reply.
As far as I know, I did not format within TWRP. Is that my next step? If not, please advice what should be done next.
My concern is something is wrong because both the suggestions you gave in that other thread did not result in the phone booting to Android properly.
Click to expand...
Click to collapse
once you flash TWRP you have to flash a no verity zip and probably magisk and definitely format data to remove encryption for your phone to boot.
Installing no verity zip and magisk produced the following. Did I do this properly because there looks like multiple errors?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ah-le-le said:
Installing no verity zip and magisk produced the following. Did I do this properly because there looks like multiple errors?
Click to expand...
Click to collapse
I can't read that, LoL. Maybe... Failed toount data? That's because you're still encrypted.
Put the zips on external storage. Format data, type yes.
Now reboot recovery (not system) then flash the zips.
And you can take screenshots in TWRP.
Thanks so much.
I followed your instructions plus the one from the other thread. Phone is now able to boot to the stock Android. I guess my next step is doing a little more research before trying to install LineageOS to see if the phone works well enough on a USA GSM mvno.
One more question please.
On the E4, are the system firmware updates mandatory? I read that users are first notified and then forced to take the update even if you Disable Automatic System Updates.
Is that true? I wish to stay with the old firmware because people have posted that the new firmware eliminates any chance of using a USA GSM sim on a Boost 1766.
Thanks.
ah-le-le said:
Thanks so much.
I followed your instructions plus the one from the other thread. Phone is now able to boot to the stock Android. I guess my next step is doing a little more research before trying to install LineageOS to see if the phone works well enough on a USA GSM mvno.
Click to expand...
Click to collapse
ah-le-le said:
One more question please.
On the E4, are the system firmware updates mandatory? I read that users are first notified and then forced to take the update even if you Disable Automatic System Updates.
Is that true? I wish to stay with the old firmware because people have posted that the new firmware eliminates any chance of using a USA GSM sim on a Boost 1766.
Thanks.
Click to expand...
Click to collapse
Use caution going with a custom ROM on this device, especially with a mvno. You may score far more hurt than benefit. Also consider what you are trying to accomplished going with custom ROMs given the clean stability of Moto stock ROMs. Toss in Xposed framework and a few modules like Gravitybox for full control/customization.
OTA updates can not be processed with a custom recovery (one of several prerequisites that your device no longer meets). You may get notified but the update won't install; you'll be dumped into TWRP. You can easily disable the update engine and corresponding notifications on a rooted device.
Related
GO GO GO!
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
YOU NEED YOUR BOOTLOADER UNLOCKED TO CARRY OUT THIS PROCESS. It's easy using fastboot, which is included in the download below. The instructions on the Motorola site are very straightforward - visit this page to get started. Unlocking the bootloader will wipe your device.
This Superboot installs SuperSU version 1.80. Note that rooting may affect your ability to receive future OTAs, reverting back to stock is easy enough. We'll cross that bridge when we come to it.
Click to expand...
Click to collapse
Full Guide
http://www.modaco.com/topic/366771-superboot-moto-g-root-solution/ (Thanks to helinhof)
http://t.co/7icWLuTwSW (Thanks to munchy_cool)
"PaulOBrien 3h
Nobody has rooted the Moto G yet? Well that won't do will it. Superboot uploading now... pic.twitter.com/6B9qcA6kfs"
"Moto G root tool online soon. It's my usual process, a Superboot image..."
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://twitter.com/PaulOBrien
Greaatt.. wainting for this..
bgochoa said:
Greaatt.. wainting for this..
Click to expand...
Click to collapse
We are two!
Moto G - Rooted
Here we go guys!
http://www.modaco.com/topic/366771-superboot-moto-g-root-solution/
its a go http://t.co/7icWLuTwSW
http://www.modaco.com/topic/366771-superboot-moto-g-root-solution/
Nice one...I´ve been waiting for this...the process took less than 10secs. Thanks!
Does it works in the german version?
FighterFX said:
Does it works in the german version?
Click to expand...
Click to collapse
It worked for me on my German Retail Moto G.
alex1301 said:
It worked for me on my German Retail Moto G.
Click to expand...
Click to collapse
Mine too, 14.71.8.Retail.en.DE
has anyone got this to work with the tesco version?
so how much space is there for system and for the apps
on 8 gb version
Props and thanks to [email protected], i can now consider buying this phone
i have a problem .... mmy cel is unblock but no rooting u.u
Rooted successfully, but I can't encrypt my phone now; it says "Encryption unsuccessful" and offers to erase everything. I reboot the phone instead without erasing and it boots normally.
Any ideas on how to solve it? It's kind of critical, since i can't use my email without encryption
can confirm that this is working, done in under a minute
burma said:
Rooted successfully, but I can't encrypt my phone now; it says "Encryption unsuccessful" and offers to erase everything. I reboot the phone instead without erasing and it boots normally.
Any ideas on how to solve it? It's kind of critical, since i can't use my email without encryption
Click to expand...
Click to collapse
I was able to get it working only after reflashing stock http://forum.xda-developers.com/showthread.php?t=2542219&page=3 then encrypting and then reflashing superboot.
So maybe it is worth updating instructions:
1) Unlock bootloader (wiping all data)
2) Encrypt your phone
3) Flash superboot
Thanks! only a question... If i unlock the bootloader and root the moto g, will I still receive the kitkat OTA update?
still not rooting
unlocked the boot loader, tried to root with super boot, but didnt work, flashed to generic uk, tried to root again and it still wont say rooted or show the su app, please can someone help?!
Rooted...wireless tether working with wifi router app. However, I got notified of 4.4 update today and it downloads, starts install, then fails.
Hello hello,
First time poster as I don't know crap to help folks since I'm just learning *ahem*, and I've come across an issue that has me completely stumped with a recently purchased refurbished Moto G4...
([Edit/Update]: So apparently new users can't embed links, and so it appears that my Imgur photos are also not posting...?)
TLDR: OTA to Nougat refuses to install on XT1625...because Consumer Celluar?
So here's the long version... Bought a refurbished Moto G4 XT1625 (not amazon) with the intention of using it as a learning aid for unlocking, rooting, etc.
Unlocked the bootloader, flashed TWRP, backed up, rooted via Magisk, backed up. After a couple days, up pops the OTA notification. "Yay" I thought. Then "Oh wait, I heard root + OTA can be difficult". So I read. A lot.
Fast forward and of course the OTA failed when I just accepted it. However, I captured the file, pulled up the stock ROM download from the official Moto website after checking that the build numbers matched, and proceeded to unroot and reflash that stock ROM (except for bootloader and gpt files). I booted back up, got the notification again, and hit OK. Fail. So I booted into recovery and tried to sideload OTA (using "Blur_Version.24.31.65.athene.retail.en.US.zip" pulled from "com.motorola.ccc.ota-20171028-062630.tar.gz"). Fail.
Maybe somehow I misread the multiple how-tos out there, and I'm screwing something up in the process here?
After numerous rinse and repeats of the above steps, I cannot for the life of me get past this damn error which (assuming my inexperienced eyes are reading it properly) seems to say that the current CCMyConsumer.apk on my phone is somehow wrong (corrupted/incorrect/missing?), and so the OTA's response to me is a big FU.
Verifying current system...
E3005: "/oem/app/CCMyConsumer/CCMyConsumer.apk" has unexpected contents.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This seems.......weird to me? If I have both the stock ROM and am using the actual OTA, why would a random provider's app be screwed up, much less screwing up the update.
Also, if it matters at all, here's that particular directory tree in a file manager...an apk file doesn't appear to even be there?
Could a lack of existence be the "unexpected contents?"
So, the question as in the TLDR, any ideas on what the cause or solution to this error or overall OTA issue could be? I'm at a loss.
The only other item I noticed is that my "Settings" now crashes if I attempt to navigate into "Apps" within its menu. However, if I navigate directly into an App's info page via the app drawer, I can access those. Not saying this is related, I have no idea, but being the only other oddity, and since it persists through flashes, I figured I'd mention it (even if unrelated, I am still curious what could be going on there too...).
Thanks in advance for any help, education, or peace of mind. =P
NobodyByChoice said:
Hello hello,
First time poster as I don't know crap to help folks since I'm just learning *ahem*, and I've come across an issue that has me completely stumped with a recently purchased refurbished Moto G4...
([Edit/Update]: So apparently new users can't embed links, and so it appears that my Imgur photos are also not posting...?)
Unlocked the bootloader, flashed TWRP, backed up, rooted via Magisk, backed up. After a couple days, up pops the OTA notification. "Yay" I thought. Then "Oh wait, I heard root + OTA can be difficult". So I read. A lot.
Fast forward and of course the OTA failed when I just accepted it.
Click to expand...
Click to collapse
Do you still have TWRP installed? You cannot flash an OTA update with TWRP installed. You'll have to find and flash the original Nougat ROM which will remove TWRP. Then accept the OTA update and let it install. Then, if you need TWRP, flash it again. I know because I was in the same boat when I accidentally accepted the OTA update with the Sept security patch and it screwed up my phone (XT1625) royally. Check out this thread which describes my process.
https://forum.xda-developers.com/mo...boots-twrp-t3701768/post74463378#post74463378
Link to XT1625 firmware: https://androidfilehost.com/?fid=673368273298984458
lmacmil said:
Do you still have TWRP installed? You cannot flash an OTA update with TWRP installed. You'll have to find and flash the original Nougat ROM which will remove TWRP. Then accept the OTA update and let it install. Then, if you need TWRP, flash it again. I know because I was in the same boat when I accidentally accepted the OTA update with the Sept security patch and it screwed up my phone (XT1625) royally. Check out this thread which describes my process.
https://forum.xda-developers.com/mo...boots-twrp-t3701768/post74463378#post74463378
Link to XT1625 firmware: https://androidfilehost.com/?fid=673368273298984458
Click to expand...
Click to collapse
Thanks for the advice, sorry for the late reply as I was out of the country. I do understand the need to get rid of TWRP first, but I'll read through your recommended threads and see what happens!
So, pretty much a long time lurker and much lover of this site. I do quite a few roots on various devices for my job (computer forensics) and I've rooted a Galaxy S8 and its stuck on the Samsung boot logo and I desperately need to get it out without wiping the data on it!
The annoying part, is I did this a few days earlier to a test S8, all the same apart from the build number and it was bloody flawless. I got root access. Did it to another device and it crapped out.
I used cfar_samsung_sm-g950f_dreamltexx_nrd90m.g950fxxu1aqi7_adt0.zip direct from firmware.mobi (for both devices - first was obviosuly a different build number).
I'm in a bit of a panic mode at the moment. I tried this:
https://forum.xda-developers.com/v20/how-to/how-to-fix-twrp-bootloop-t3513580
After attempting root on my replacement phone, I could NOT boot to system. Each time I rebooted to "System", it would boot straight to TWRP over and over. I tried reflashing stock files. No verity patching.. etc.
The Fix:
Download the latest version of TWRP specific to your device here https://build.nethunter.com/test-builds/twrp/lge/
Flash the file and the device should now be able to boot to system. If that doesn't work try another version.
I spoke to @jcadduono about my problems and he believes there may have been something weird going on in the misc partition. Reflashing TWRP will/should fix the problem.
Thanks @jcadduono for all the support.
Click to expand...
Click to collapse
But it did not work. I can get into TWRP Recovery with it (and into Download mode) but TWRP wont kick it out of the boot loader issue. I've tried installing super user and all sorts, but I can't mount Data to actually achieve anything?
Please, any help is much appreciated. If there is anything obvious I'm missing please tell me.
Thanks,
DG.
First of all, I would like to ask for mod/s to have this move to proper thread section.
What is the exact model of your S8?
What is your TWRP version you installed?
@DanGlee
Can you show us the picture of twrp error you get?
You mentioned this
"but I can't mount Data to actually achieve anything?"
Can you send us the exact error of twrp and post it in here? It could be that data partition is corrupted, and if it is, then there's no way we could get your data back.
But if you can get /data partition mounted, then you could make a backup in twrp and reflash everything to stock.
Apologies for not posting this in the correct place. It's a minefield of threads.
I don't have the phone infront of me at the no, bit will do it first thing in the morning.
Thanks.
you cannot mount data if you don't FORMAT DATA first
batuzai04123 said:
First of all, I would like to ask for mod/s to have this move to proper thread section.
...
Click to expand...
Click to collapse
DanGlee said:
Apologies for not posting this in the correct place. It's a minefield of threads.
...
Click to expand...
Click to collapse
Thread moved :good:
Wood Man
Forum Moderator
manups4e said:
you cannot mount data if you don't FORMAT DATA first
Click to expand...
Click to collapse
Yes , forgot about that.
If data mounted is inaccessible, your only option is to format data partition, which sadly, erase all your data from your phone.
Sorry @DanGlee you won't be able to retrieve your data anymore.
Thanks for the replies.
Its definitely not sounding good.
As an update as promised anyway, here are some details requested.
Its an Galaxy S8 SM-950F (UK) with Build Version ending ...AQI7
(Running Android 7)
I've put TWRP 3.1.0-1 on it.
I can't really see any error codes or anything, but here are some images of it failing to install SuperUser.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for the responses. You guys genuinely are helpful and if you say its FUBAR then I trust your diagnosis. (I think I was just clutching at straws that I might be able to salvage something!)
Thanks,
DG.
Edit, I can't upload images. XDA is being an arse. I just want to put in this link [insert_https_here]://imgur.com/gallery/Teceb
DanGlee said:
Thanks for the replies.
Its definitely not sounding good.
As an update as promised anyway, here are some details requested.
Its an Galaxy S8 SM-950F (UK) with Build Version ending ...AQI7
(Running Android 7)
I've put TWRP 3.1.0-1 on it.
I can't really see any error codes or anything, but here are some images of it failing to install SuperUser.
Thanks for the responses. You guys genuinely are helpful and if you say its FUBAR then I trust your diagnosis. (I think I was just clutching at straws that I might be able to salvage something!)
Thanks,
DG.
Edit, I can't upload images. XDA is being an arse. I just want to put in this link [insert_https_here]://imgur.com/gallery/Teceb
Click to expand...
Click to collapse
Unlucky i don't think you can recover your file. I took a look and didn't find anything. Please pay attention at what you do when rooting or doing anything to your phone. First you need to see all the steps to avoid problems like this!
If can help i used this very simple guide to root my phone [YOUTUBE]https://www.youtube.com/watch?v=L_lsVsbujYg
[/YOUTUBE]
please help me.
I have completely wiped my device. nothing is there in internal storage. Just the TWRP folder.
it has unlocked bootloader and twrp installed
but it is the unrooted device.
so please tell me what is best for me?
shall I root it or can I directly go to stock Oero?
I have already downloaded stock file '8.1.0 (OPM6.171019.030.E1, Jul 2018)- angler-opm6.171019.030.e1-factory-1abcb2f1.zip'
I am confused, how should I proceed?
please explain me stepwise, so I can save my phone.
smartpreet said:
please help me.
I have completely wiped my device. nothing is there in internal storage. Just the TWRP folder.
it has unlocked bootloader and twrp installed
but it is the unrooted device.
so please tell me what is best for me?
shall I root it or can I directly go to stock Oero?
I have already downloaded stock file '8.1.0 (OPM6.171019.030.E1, Jul 2018)- angler-opm6.171019.030.e1-factory-1abcb2f1.zip'
I am confused, how should I proceed?
please explain me stepwise, so I can save my phone.
Click to expand...
Click to collapse
You will be fine I wipe my internal from time to time. Just make sure you update your bootloader and vendor. If you use the flash all I'm pretty sure it's done for you but if using fastboot method follow the steps in the hiesenberg guide. Just so you know once on the latest Oreo builds from what I've read can no longer downgrade. I haven't verified or read up on it myself but maybe look into if you think you might want to go back to nougat .
Exodusche said:
You will be fine I wipe my internal from time to time. Just make sure you update your bootloader and vendor. If you use the flash all I'm pretty sure it's done for you but if using fastboot method follow the steps in the hiesenberg guide. Just so you know once on the latest Oreo builds from what I've read can no longer downgrade. I haven't verified or read up on it myself but maybe look into if you think you might want to go back to nougat .
Click to expand...
Click to collapse
i have tried that earlier, but still i got the red triangle.
since i failed to go to stock today i installed latest twrp-3.2.2-0-angler using latest SDK tool.
then i flashed Magisk-v16.0 and then ResurrectionRemix-M-v5.7.4-20161008-angler and it immediately went to google logo and stuck there.
just use this to get back to stock https://developers.google.com/android/images
all you do is boot in to fast boot plug into pc and run flash all
there are ways to save data but you already wiped so no need
if your still confused just look up a guide of how to flash factory images and install the usb drivers
billycar11 said:
just use this to get back to stock https://developers.google.com/android/images
all you do is boot in to fast boot plug into pc and run flash all
there are ways to save data but you already wiped so no need
if your still confused just look up a guide of how to flash factory images and install the usb drivers
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
these are my files.
as you said i I had connected the phone and double-click the flashall
the process started and finish but still i am on google logo.it keeps booting to logo. nothing else is happening
smartpreet said:
these are my files.
as you said i I had connected the phone and double-click the flashall
the process started and finish but still i am on google logo.it keeps booting to logo. nothing else is happening
Click to expand...
Click to collapse
What did the command line windows say when it was flashing
billycar11 said:
What did the command line windows say when it was flashing
Click to expand...
Click to collapse
smartpreet said:
Click to expand...
Click to collapse
It looks good but didn't seem to flash radio and bootloader maybe just not in screen shot should boot but if it still won't boot in to the stock recovery and factory reset might help
You could have the bad big cores try flashing one of the 4 core fixes. Also I wait to flash magisk until after first boot. It can hang you on the Google screen .
Hi
I recently completed installing official LineageOS 17 on my 6T using TWRP, not the recovery on Lineage wiki page. Restarted the phone a few times and playing with it for a couple of days. Things seem to be working well. I do have a few doubts though:-
(1) About the A/B partition thing. I did a simple wipe prior to installation and I am not sure I have installed it on the correct partition. How can I check to make sure ? Can I copy partitions now and if so, how ?
(2) I do not plan to use payment apps on the phone but I do plan to use the protonmail apk which I have already installed. How safe is it to leave the bootloader unlocked especially when the "Automatic System Updates" is on ?
Thanks
1. There is no wrong partition. Every update / installs will alternate between A/B partition. If it boots don't worry about it.
2. You can't lock the boot loader unless you make your own build and sign it. So it must remain unlocked. There is a guide for doing this if you want in the guide section.
OhioYJ said:
1. There is no wrong partition. Every update / installs will alternate between A/B partition. If it boots don't worry about it.
Click to expand...
Click to collapse
Thanks so much for allaying my fears. I read somewhere that in case of issue with Lineage partition, the mobile will try to boot up the other partition which might have older version of Android OS, causing a brick.
I was thinking of configuring my gmail account on the stock email app and was apprehensive that an unlocked bootloader might cause a safety block from Google.
anuk221 said:
Thanks so much for allaying my fears. I read somewhere that in case of issue with Lineage partition, the mobile will try to boot up the other partition which might have older version of Android OS, causing a brick.
I was thinking of configuring my gmail account on the stock email app and was apprehensive that an unlocked bootloader might cause a safety block from Google.
Click to expand...
Click to collapse
On a clean / first install of Lineage you would typically install it twice to get it on both A/B partitions. The other option is to use the copy partitions zip. The zip is mentioned in the Lineage wiki I believe
It's not a safety block, you just will come up as not certified, which likely is already the case. This will not cause you any problems other than certain apps won't appear in the play store. (Such as Netflix, things like that).
I have a installing Lineage guide here. See the section on Magisk about getting the device to be certified again. There is a cliff notes version in the second post as well, you can see my Install method and update method.
The other partition would only try and boot if Lineage failed to boot. If you didnt install it twice, it would be an easy fix now to just install it again, or use the copy partitions zip. Usually I just update or install without worry, but I would backup just to be safe in this case since your steps are a little out of order. Always better to be safe than sorry.
OhioYJ said:
I have a installing Lineage guide here. See the section on Magisk about getting the device to be certified again. There is a cliff notes version in the second post as well, you can see my Install method and update method.
Click to expand...
Click to collapse
Thanks for the link. I had checked your guide amongst others prior to installation.
I was getting the following startup screen on boot and it didnt lead into TWRP recovery or bootloader even when I used the "volume up+power" combination at startup :-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Which is what led me to think that I hadnt done a clean/proper install. I had used "Tool ALL IN One" to unlock the bootloader and I had deviated from wiki and gone the TWRP route for recovery since I was not sure if selecting "Apply Update" in recovery and then "Apply from ADB" would work.
Anyways, I redid the whole thing again last night using Lineage OS recovery. I still get the above screen at startup but now when I select the power button, it takes me into LineageOS recovery.
Again everything seems to be working well prima facie, except that this time when I insert a Sandisk USB C Dual Drive, I get a message "Issue with Sandisk USB Drive. Tap to fix". The drive works fine on my 8T !
anuk221 said:
Thanks for the link. I had checked your guide amongst others prior to installation.
Click to expand...
Click to collapse
Different devices have different kernels with different things enabled / disabled, giving them different capabilities. Honestly I've never tried thumb drives on my phones, I guess I could try one on my 6T and 8T and see what I get later. I'll see if I can find an adapter cable, as I don't have a USB C drive.
You do have to let go of the power button for a moment to get into fastboot. It will pause when it gets to that bootloader unlocked screen. At least that's always been my experience.
Every time you install LOS on the 6T it replaces TWRP with LOS recovery. TWRP must be re-flashed everytime if that's what you prefer to use. That's why that step is in my guide.
OhioYJ said:
Different devices have different kernels with different things enabled / disabled, giving them different capabilities.
Click to expand...
Click to collapse
That is correct. The drive in question is a 64GB drive formatted in exFAT. I tried another drive, 32GB formatted in NTFS and it was being detected by both the 6T and the 8T ! Probably an issue with the exFAT kernels as you pointed out.
I am surprised though that some very basic features which I had assumed would be available seem to be missing - No option of ungrouping/declubbing sms conversations, no option of exporting to SIM, no option of getting timestamp in call log. In that sense LOS appears to be more of a de-googled version of android than a standalone OS.