Okay, so I was on the Stock 2.3.4 GB rooted rom, I tried to flash Android Revolution but somehow I downloaded the Sensation one and tried to flash and it gave error Status 7 (4EXT).. So, I went back to stock 2.2.1 and perm-rooted and my S if still off, so I flashed recovery and tried to flash Runny Mede, it dosen't dare to pass the MyTouch 4G logo, and just starts a boot loop right there. Please help, I want to enjoy other roms just like you guys too! Also, everytime I mount my phone as a Disk Drive, windows asks me to Scan for errors, I do it (with both options checked) and it just immediately closes and goes into the root of my SD.. Please help me.
Make sure when flashing a new rom to wipe data/cache. I'd recommend wiping system too, just to make sure you don't run into other issues.
This comes from memory only, (Anyone- don't hesitate to correct me if I'm wrong) and I couldn't find any info about it to confirm, but I believe Status 7 simply means the installation of the zip file you attempted to flash was aborted, i.e. nothing was flashed. Many ROMs have checks in them to confirm you're flashing to the correct device, and if not, will refuse to proceed, and this may be what you encountered.
As for Windows asking you to scan for errors, this happens any time you disconnect your phone or unmount it without safely ejecting via Windows. It's unlikely you would actually have any disk problems or corruption unless you disconnected or unmounted while files were still being transferred or edited. Safely unmounting would be considered the best practice. When you're ready to disconnect your phone from your computer, or to unmount the SD card from Windows, look for an icon like this.
{
"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"
}
Click it and choose your device to safely remove it from your computer.
Going back to froyo and "re-rootong" was a complete waste of time.
Status 7 would indeed mean nothing was flashed (nice post by the way, to the guy above me).
All you needed to do was wipe system, data and cache a flash the correct ROM. Alternatively, you could have restored the backup that you should have made before you tried flashing ARHD.
Try holding Vol down at boot to get to bootloader. Once there select Recovery. That will get you on the right path. Remove PD15IMG from the root of your SD before you do this.
Edit: I just remembered that your recovery is stock if you flashed PD15IMG. You will need to flash a recovery.img with adb. The steps are in the clockworkmod thread that is stickied in the dev section. There used to be a PD15IMG of an older 4EXT recovery floating around. You might try locating that.
crawler9 said:
Make sure when flashing a new rom to wipe data/cache. I'd recommend wiping system too, just to make sure you don't run into other issues.
This comes from memory only, (Anyone- don't hesitate to correct me if I'm wrong) and I couldn't find any info about it to confirm, but I believe Status 7 simply means the installation of the zip file you attempted to flash was aborted, i.e. nothing was flashed. Many ROMs have checks in them to confirm you're flashing to the correct device, and if not, will refuse to proceed, and this may be what you encountered.
As for Windows asking you to scan for errors, this happens any time you disconnect your phone or unmount it without safely ejecting via Windows. It's unlikely you would actually have any disk problems or corruption unless you disconnected or unmounted while files were still being transferred or edited. Safely unmounting would be considered the best practice. When you're ready to disconnect your phone from your computer, or to unmount the SD card from Windows, look for an icon like this.
Click it and choose your device to safely remove it from your computer.
Click to expand...
Click to collapse
estallings15 said:
Going back to froyo and "re-rootong" was a complete waste of time.
Status 7 would indeed mean nothing was flashed (nice post by the way, to the guy above me).
All you needed to do was wipe system, data and cache a flash the correct ROM. Alternatively, you could have restored the backup that you should have made before you tried flashing ARHD.
Try holding Vol down at boot to get to bootloader. Once there select Recovery. That will get you on the right path. Remove PD15IMG from the root of your SD before you do this.
Edit: I just remembered that your recovery is stock if you flashed PD15IMG. You will need to flash a recovery.img with adb. The steps are in the clockworkmod thread that is stickied in the dev section. There used to be a PD15IMG of an older 4EXT recovery floating around. You might try locating that.
Click to expand...
Click to collapse
Thanks to both of you, I tried flashing TRAD v1 and it worked, made a nandroid, just flashed virtuous Affinity maybe 2 minutes ago and its booting. I guess I just panicked a bit. c:
It's easy to do if you aren't used to flashing. Those minor heart attacks aren't fun, either.
Tell me about it. : )
Related
Hi all,
Here's short history of the phone:
Friend of mine drop his on the concrete about June of last year and whole screen was cracked (not pretty). About month ago I found LCD Screen with Digitizer on ebay bought it and replaced it.
After turning it on everything was working except random reboots. Phone was not registered to any account so there was no internet only WI-FI.
So I started going into system updates and downloading HTC updates it did two of them and I think on the 3rd one it just starts to boot white HTC EVO 4G screen comes on and then it reboots.
Only pulling the battery will stop it.
This is all on stock HTC Sense ROM, rooting was never attempted!
I've searched thru the forums here but everything here relates to failed rooting process.
Can someone please make any suggestions?
Bellow is the pictures of boot loader.
Help is greatly appreciated!
{
"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 directions are for un-rooting, but should fix your phone:
http://forum.androidcentral.com/htc...19278-how-unroot-return-stock-ruu-method.html
Fazulka said:
These directions are for un-rooting, but should fix your phone:
http://forum.androidcentral.com/htc...19278-how-unroot-return-stock-ruu-method.html
Click to expand...
Click to collapse
Thank you!
Followed the instruction, run RUU and it starts to check the phone after this I get error[170]: USB connection error.
I've tried over 10 times.
Step 4 says "Make sure USB debugging is enabled on your phone."
I can't even log into Sense?
The only other thing you can do is find a PC36IMG.zip and put it on your microSD card, then reboot into the bootloader. It should find it and reflash everything, the same as using the RUU.
ffolkes said:
The only other thing you can do is find a PC36IMG.zip and put it on your microSD card, then reboot into the bootloader. It should find it and reflash everything, the same as using the RUU.
Click to expand...
Click to collapse
I've tried using this method found here
I placed PC36IMG.zip in root of the SD card. But when I boot into recovery I can see for about 3 seconds on the right side status bar how it checks PC36IMG.zip file but then it goes back to recovery. It never ask me if I want to update like it says in the above tutorial "Do you want to start update?"
Any other suggestions?
JohnnyBeGood113 said:
I've tried using this method found here
I placed PC36IMG.zip in root of the SD card. But when I boot into recovery I can see for about 3 seconds on the right side status bar how it checks PC36IMG.zip file but then it goes back to recovery. It never ask me if I want to update like it says in the above tutorial "Do you want to start update?"
Any other suggestions?
Click to expand...
Click to collapse
I had to unroot mine and I found that u have to have the right pc36img file. If you dont know what ver rom was running then you may need to try them all. But I had the same problem it just wouldent install the file. Keep trying and if you need help finding them Ill help ya.
I found this but its not the same place I got mine from. http://www.filecrop.com/htc-evo-4g-roms.html
Thanks for the reply!
Somewhat of a progress. I tried countless times and it always gives me USB connection error: Then I downloaded HTC Sync and and I think I went to Hboot and I heard sound on windows it seemed like phone got recognized and I was able to finish the processes. It was flashed using RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed. Then when I went to again in recovery it was again red triangle over the phone.
After that I just let it try to boot and it finally booted into HTC sense!
Turned on WI-FI and wanted to check if there's any updates and it said no updates?
This is what recoveries I've tried so far:
Amon RA 2.1.1
Amon RA 2.2.1
Amon RA 2.3 (Added 02/09/2011)
Stock Recovery 3.26.651.6 (Added 01/18/2011)
Stock Recovery 3.29.651.5 (Added 01/18/2011)
Stock Recovery 3.30.651.3 (Added 01/18/2011)
Stock Recovery 3.70.651.1 (Added 01/18/2011)
One by one I tried each one renaming to PC36IMG.zip and none of them asked me if I want to do the update. It just checks it and goes back to bootloader.
Why do I get red triangle?
What should I do now?
Help is appreciated!
!!This is NOT a boot up animation, it replaces the SAMSUNG logo BEFORE the animation, you will still have a boot up animation as seen in the youtube video!!
Alright, This has probably been covered for other phones or linked in threads when people asked, but I couldn't find a specific thread easily to do this 'mod'
I did it last night using a tutorial for the i9000 and it worked flawlessly.
For this tutorial it looks like you NEED to be on a Gingerbread Rom (or GB bootloaders), but i'd bet there are ways to do it for Froyo and god forbid Eclair...
Some things you will need:
Odin on your PC (I used Odin 1.61)
Working USB cable
Ability to boot into download mode!
GingerBread ROM (there are similar ways to do this for froyo)
Everything you need <<Download this!! Includes everything you need for this Modification, including Odin 1.82! Credit to connexion2005 for this Zip.
Optional:
Custom logo.jpg image (480x800, <100kb) the zip includes a few plus the one I installed on my phone! I can make custom versions of the one I used for my phone and add them to the .zip at request!!
!!!You can ALSO use this method if you upgraded to GB bootloaders and are still on Froyo!!!
Instructions (modified slightly from connexioon2005's)
Download the above .zip and extract everything into a folder of your choice.
ShutDown your phone and boot into Download mode (Hold 1 on the Slide-out KB and power)
Open ODIN (either 1.82 from the zip or your existing ODIN on your PC)
Connect your phone to the computer and make sure it shows up in a COM port in ODIN.
Make sure AutoReboot is selected and F.Reset time is NOT selected.
Under PDA, path to the "i9000_gb_param_LFS.tar" file in the folder you extracted the .zip to and click START. (This should run fairly quick and only push param.lfs in the 'working' box)
Your phone will reboot, keep it connected to the computer, but DO NOT mount the USB.
In the .zip file, there is a bunch of collected 'logos' to choose from; rename the one you want to use to logo.jpg. The 'logo.jpg' will be the one that is pushed to the phone and used during your boot up sequence.
After you have the logo.jpg that you need, you will run the "i9000_gb_boot_screen.bat" and this will push file to put the logo.jpg on your phone to be used as the boot splash. Follow the instructions (hit enter when asked, lol)
i!IMPORTANT!i Keep your screen active during this process, as SU will come up , asking for permissions! i!IMPORTANT!i
Reboot your phone and you should have your 'logo.jpg' where the Samsung splash was, followed by your sanim.zip (boot animation) and your phone will load.
Again, if you are going to use a custom image, it needs to be 480x800 and <100kb to work.
Some users of the i9000 reported a 'soft brick' where Odin hangs up, but all you need to do is reboot in Download, restart Odin and do it again, DO NOT WORRY!!
This process can be repeated as many times as you want, but you have to run the entire process again to replace your existing logo.jpg with a new one. you can't just run the .bat again because it will see the logo.jpg and say [FILE ALREADY EXISTS]
here is a video of my new boot up:
Dark Droid Designz Boot splash
I also added a crude (MS Paint) version of the dark droid splash without the text!
{
"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 added to the .zip file and as stated above, i can add different colored 'glow' around the droid and add text of your choice and update the .zip, JUST ASK!!!
Disclaimer: I, Turbosocks, am not responsible for any overjoyment, excitement, screaming from the sheer awesomeness, damage to your pet dog scooter, damage to your phone, loss of your job, your wife leaving you, etc. when you choose to do this modification.
Nice tutorial TS!
Sent from my SPH-D700 using XDA App
Awesome guide, I sense a qbking video soon lol
________________________________
Roll Tide Roll!
This should be in dev. But amazing job. May want to specifically mention this is NOT a boot-up animation, but before it
sent from my miui-ified epic
noted @ugothakid!!
added the note to the original post.. and my bad, this probably SHOULD be in the dev. forum. oooooops
nice tut, ill be trying it later tonight...
EDIT: just did it and everything went fine
I can't tell the difference between l and 1, nevermind.
anyone else try this? just want to make sure it works for everyone!
I would've, but I'm on ec05
________________________________
Roll Tide Roll!
Did Not Work
This Did Not Work For Me
I Think I Did The Process correctly
I have a Samsung Epic 4g on GingerBread 2.3.4 With SuperUser 3.0
I Use Odin3 1.8.5 With ClockWorkMod 3.1.01
I Made Sure I Met The Prerequisites
The Final Logo File Size Was 92 KB
I Booted To Download Mode And The Process Was A Success
Odin Did A Succesful Push
The Bat File Worked And I Gave it SU Permission
After That I Did A Reboot
The Result Was That No Image Showed Up And The Phone Wouldn't Boot
I Took The Battery Out And Put It Back In.
The Only Thing That Appeared Was The Charging Animation.
I Tried Booting Into ClockWork But Nothing.
Then I Took The Battery Out 2x More
After This, ClockWork Suddenly Appeared
I Was Pretty Happy And I Restored The System
* I Had Luckily Made A Nandroid The Same Day
I Rebooted The Phone And This Did Not Fix The Problem. There Was Still No . Image And The Phone Did Not Boot
I Repeated The Process And Got ClockWork To Start Again
I Did A Complete Restore.
I'm Still In Clockwork But I Realize That This Probably Won't Fix The Problem
I Don't Think ClockWork Messes With The Start Image Even Though It Is On The
Phone
Now I Realize That I Probably Have To Flash Something Through Odin.
I Have Read A Thread [How to] Restore a semi-bricked Epic or Bring it back from the brink! That Says
This has worked on numerous phone that have partition issues, intermittent booting issues, and many other file system issues. This also fixes the Samsung Logo disappearing from boot.
Click to expand...
Click to collapse
But Now I'm Scared Of Going Out Of ClockWork And Having A Bricked Phone
So
* Is There A Way To Boot Into Download Mode From ClockWork
* And Is Flashing In Odin The Solution
P.S.
I Can't Go To Sprint Because A Few Months Ago I Moved Out Of The Country And They Don't Sprint Here (They Don't Even Have My Phone Here)
Edit: Was Able To Go Into Download Mode And Restore To Stock
My tablet will not do a data factory reset at all , i tried 3 different methods each gives me some kind of error as if something on my tablet was causing the problem.
Ive tried doing it through CWM that gives me some kind of long lined error
Ive tried doing it with a tooth pick on the side of the tablet that boots into the kernel that seems like its doin the reset shortly after that becomes a failure
Last but not least Ive tried doin it when the tablet is booted.....same issue as stated above feels like its doing a reset then that red caution sigh appears. And not to mention my music wont play either , idk wats going on 500bux seem to be a waste can someone please help me or guide me in the right direction thank you
Have you tried re-flashing your rom?
Doing all three wipes? (data, cache, dalvik) before flashing?
Yes , I make sure I do that b4 flashing every ROM - still noting
Would it helped if I change my kernel?
Well, in this case, I would do the following;
Backup your sd, and format it to fat 32
(install back in tab with ONLY the copy if the rom you use. PLEASE make sure you are trying to flash a full rom, and not just the kernel. Because if you are trying to do that, on an empty system, it ain't gonna work.
So copy a rom to your SD, say Harkon. (you can change it later)
Now, try the 3 wipes, then try flashing the Harkon rom.
If it's not successful, then reboot into recovery,
goto Mounts and Storage, and do a format on those 3 (system, data and cache).
This will absolutely clean the system.
Then back out of it, and install zip from sd, try the Harkon again.
As sugested above.
Enter cwm recovery
Go to wipe menus wipe all
Go to mounts/storage format all but SD
reboot go back to format format allnsgain.
Install your rom
reboot into recovery.(do not let system boot)
go back into wipe menus and wipe all. Then boot device.
Do not allow Google tobrestore your data and settings it backed up (unchecked the boxes when awed while setting upngoogle account) .
I has a issue withbthis causing the issues you are having.
Good luck.
Chics can be geeky smart toolkit whoooweeee
thnx for both replies - that error is still there ,however all the others formated successfully heres pix on the error
the error reads as follows -
Code:
Error removing /data/data/com.FD.updater/shared_prefs/FDUpdater_Send_Report.xmIError formatting /data
{
"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"
}
You may want to post this error at Thor's site. He made the recovery.
Here is a link to his recovery forum, also, one other thing to check;
http://forum.tegraowners.com/viewtopic.php?f=8&t=83
He should have an answer for you, but keep in mind, he is a bit busy with ICS right now, so it may take a couple of days.
Sorry we couldn't get you going,
idk wth it could be ,from the error it seems like a update error or some sort and that link you gave me is the same thing that Ive been doin for the longest
ima sigh up on the site now and hopefully get a break through
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.