Related
Hello everybody, so I noticed a lot of people struggling with marshmallow + autorec hard bricks (symptoms: no download mode, no recovery, black screen)
Just to make sure: I'm not responsible for any damages done. This worked for me perfectly, should work for you too. Use it only if you bricked D855 30B!!! (Marshmallow)
Here's what you have to do to fix that:
First follow this amazing guide by senior member l33tlinuxh4x0r, big thanks to him. ---> LINK TO GUIDE
Important stuff: You need to install qualcomm drivers (windows 8, 10 users need to disable driver signature enforcement), you need to short the circuit of your phone, like it's shown in that guide, by shorting it correctly and plugging it in you immediately get connection (keep note of that, there's no need to wait for something, no sound - redo.)
Instead of extracting tot, like it's shown there, use attached files (target Dir). Then again, flash them like it's shown in the tutorial. You should be good to go.
DOWNLOAD HERE
Didn't know where to upload, so sorry for using this abomination
hi...please help~
catercousin said:
Hello everybody, so I noticed a lot of people struggling with marshmallow + autorec hard bricks (symptoms: no download mode, no recovery, black screen)
Just to make sure: I'm not responsible for any damages done. This worked for me perfectly, should work for you too. Use it only if you bricked D855 30B!!! (Marshmallow)
Here's what you have to do to fix that:
First follow this amazing guide by senior member l33tlinuxh4x0r, big thanks to him. ---> LINK TO GUIDE
Important stuff: You need to install qualcomm drivers (windows 8, 10 users need to disable driver signature enforcement), you need to short the circuit of your phone, like it's shown in that guide, by shorting it correctly and plugging it in you immediately get connection (keep note of that, there's no need to wait for something, no sound - redo.)
Instead of extracting tot, like it's shown there, use attached files (target Dir). Then again, flash them like it's shown in the tutorial. You should be good to go.
DOWNLOAD HERE
Didn't know where to upload, so sorry for using this abomination
Click to expand...
Click to collapse
i don't get what the meaning "use attached files (target Dir). Then again, flash them like it's shown in the tutorial. You should be good to go. "
can u explain how to done this step???
is this hard brick the result of using the Autorec MM or the old Lollipop one?
shun95 said:
i don't get what the meaning "use attached files (target Dir). Then again, flash them like it's shown in the tutorial. You should be good to go. "
can u explain how to done this step???
Click to expand...
Click to collapse
Select the attached download folder as "Target DIR" in the application, it will load the files and let you flash them like it's shown in the tutorial
Broloff said:
is this hard brick the result of using the Autorec MM or the old Lollipop one?
Click to expand...
Click to collapse
The Lollipop one
Hi thank you for this post
catercousin said:
Hello everybody, so I noticed a lot of people struggling with marshmallow + autorec hard bricks (symptoms: no download mode, no recovery, black screen)
Just to make sure: I'm not responsible for any damages done. This worked for me perfectly, should work for you too. Use it only if you bricked D855 30B!!! (Marshmallow)
Here's what you have to do to fix that:
First follow this amazing guide by senior member l33tlinuxh4x0r, big thanks to him. ---> LINK TO GUIDE
Important stuff: You need to install qualcomm drivers (windows 8, 10 users need to disable driver signature enforcement), you need to short the circuit of your phone, like it's shown in that guide, by shorting it correctly and plugging it in you immediately get connection (keep note of that, there's no need to wait for something, no sound - redo.)
Instead of extracting tot, like it's shown there, use attached files (target Dir). Then again, flash them like it's shown in the tutorial. You should be good to go.
DOWNLOAD HERE
Didn't know where to upload, so sorry for using this abomination
Click to expand...
Click to collapse
I've the same problem as you describe here.After I upgraded g3 to marshmallow I applied autorec and my device became hard brick.now my phone under com ports as Qualcomm 9008.
from this point I'm confused that which way to go the first your description 'Instead of extracting tot, like it's shown there, use attached files (target Dir)', Then again, flash them like it's shown in the tutorial'',the second tot file of the rom that we were running. (not older not newer same version).The first way I did not understand attached files where are they ?
if I follow the second way how can I find tot of my rom D855 30B!!! (Marshmallow)?
thank you waiting your help
Instead of tot you use the files from the download link in my post since you don't need to extract tot now, just mark that folder in "target dir" and follow the second guilde, as you call it. Good luck!
Help
catercousin said:
Hello everybody, so I noticed a lot of people struggling with marshmallow + autorec hard bricks (symptoms: no download mode, no recovery, black screen)
Just to make sure: I'm not responsible for any damages done. This worked for me perfectly, should work for you too. Use it only if you bricked D855 30B!!! (Marshmallow)
Here's what you have to do to fix that:
First follow this amazing guide by senior member l33tlinuxh4x0r, big thanks to him. ---> LINK TO GUIDE
Important stuff: You need to install qualcomm drivers (windows 8, 10 users need to disable driver signature enforcement), you need to short the circuit of your phone, like it's shown in that guide, by shorting it correctly and plugging it in you immediately get connection (keep note of that, there's no need to wait for something, no sound - redo.)
Instead of extracting tot, like it's shown there, use attached files (target Dir). Then again, flash them like it's shown in the tutorial. You should be good to go.
DOWNLOAD HERE
Didn't know where to upload, so sorry for using this abomination
Click to expand...
Click to collapse
The link is DEAD...
Maybe someone can reupload? I messed up and didn't save it in my computer, didn't think I'd need it anymore. Oops.. Or create them yourself
You need do extract .kdz, then .dz,
use this guide to create partition.txt
http://forum.xda-developers.com/lg-g2/general/how-to-create-partition-txt-file-kdz-t3109859
and rename files to ****.mbn
i just had my phone back to normal after marshmallow autorec brick
Get the right tools from scamex only..
U going to need :
Qdloader hs-usb driver for your pc 32/64bit
Install it
Then get smart boot diagnostic tool
Along that also get ap-chip dll and att
Then extract it the ap folder inside smart boot diagnostic tool
Get document to shows how to flash a "dead boot"
Then run thr smart boot diagnostic tool
Then follow instruction from the document and pay attention on page 14, 15 & 16
After recovering qfprom anti-roolback issue.
Your phone should be back to normal as before the autorec root hardbrick
catercousin said:
Maybe someone can reupload? I messed up and didn't save it in my computer, didn't think I'd need it anymore. Oops.. Or create them yourself
You need do extract .kdz, then .dz,
use this guide to create partition.txt
http://forum.xda-developers.com/lg-g2/general/how-to-create-partition-txt-file-kdz-t3109859
and rename files to ****.mbn
Click to expand...
Click to collapse
hey, the guide from the link is gone. do you happen to remember how to get partition.txt from .kdz ...or do you have one?
Hey!
Can anyone reupload the files from the OP?
Thanks!
Link is dead, can someone reupload the files please!?
unbelieveable.
every single link is dead for this
GET DROPBOX.
shoaibiftekhar said:
hey, the guide from the link is gone. do you happen to remember how to get partition.txt from .kdz ...or do you have one?
Click to expand...
Click to collapse
Still the case.
Could anyone help, please?
I found a guide to create "partition.txt" (maybe a copy the original guide here) but that's for the G2.
Any help is greatly appreciated :crying:
Hello everyone,
Here are some step by step guides for those of you who need detailed instructions for rooting and un-rooting the T-mobile LG G5.
The guides are short and to the point and are meant to be followed one after the other (STEP#1 --> STEP#2 --> STEP#3).
For the step#3 guide, you must choose one out of the three available guides below:
Guides:
Tmobile-LGG5_pre_flash_MM_6_0_1_requirements_STEP_1
Tmobile-LGG5_pre_flash_MM_6_0_1_requirements_STEP_2
Tmobile-LGG5_flash_root_with_stock_MM_6_0_1_Re-install_STEP_3 <------ If you want to re-install stock MM 6.0.1 with root
Tmobile-LGG5_flash_root_with_stock_MM_6_0_1_Upgrade_only_STEP_3 <------ If you want to root current stock MM 6.0.1
Tmobile-LGG5_flash_Stock_UnRoot_MM_6_0_1_STEP_3 <------ If you want to have stock MM 6.0.1 only (no root, use this if you want to return the phone or sell it)
They will walk you through:
Downloading and Installing the necessary drivers / tools
Unlocking your bootloader
Flashing the stock .kdz file
Flashing the rooted .TOT file
Using TWRP to gain root status
I assume the following:
You are using a Microsoft Windows operating system (Windows 7 or above)
You understand that all data on your phone will be deleted
You understand that your warranty is now gone
You understand that YOU MUST follow the guides one after the other (1 -> 2 -> 3). If you deviate from this YOU WILL NOT be successful in rooting your phone
You understand that YOU MUST follow the steps in the guides one after the other (1 -> 2 -> 3). If you deviate from this YOU WILL NOT be successful in rooting your phone
Your phone's USB PC Connection (mode your phone is in when connected to your PC) is on File Transfer mode. ADB and Fastboot commands to the device WILL NOT work if device is not on this mode
You read the Useful tips & information for the T-mobile LG G5 post
You read the Changelog + News & Additions post
***Un-root***
If you want to "un-root" your device (go back to default stock) use the Tmobile-LGG5_flash_Stock_UnRoot_MM_6_0_1_STEP_3 guide.
(Keep in mind that this WILL DELETE all data on the phone)
***Disclaimer***
I take no responsibility in what you do to your phone
The step-by-step guides in this thread were made with the assumption that you will strictly follow them one after the other.
(If you don't, YOU WILL brick your phone!)
If you run into an problem, verify that you have correctly completed all the steps for each guide before posting to this thread. Most problems come from guides / steps that were skipped.
If possible use a laptop that is fully charged and plugged in to an outlet instead of a regular PC (unless it has a UPS attached to it) just in case you lose power during the flashing process.
(If you use a regular PC without a UPS attached to it and you lose power during the flashing process, YOU WILL brick your phone!)
I would like to thank the following people for making all of this possible:
tungkick
wolfu11
arjuna_
Your work and dedication does not go unnoticed, thank you. I would also like to thank anyone else not mentioned here that allowed the rest of us to get root on our beloved LG G5 phones. The android community is awesome!!!
Sections:
Post#1: Main introduction & Files
Post#2: Useful tips & information for the T-mobile LG G5
Post#3: Changelog + New & Additions
Please leave a thank you if you find any of this helpful
**Useful tips & information for the T-mobile LG G5**
How to install xposed: (Keep in mind that versions will change over time)
Download the latest xposed framework currently (xposed-v85-sdk23-arm64.zip):
- Go to the following web address: http://dl-xda.xposed.info/framework/
- Click on the sdk23 link
- Click on the arm64 link
- Download the latest xposed zip file currently xposed-v85-sdk23-arm64.zip
Download the latest xposed installer currently (xposedInstaller_3.0_alpha4.apk):
- Go to the following web address (xda thread): http://forum.xda-developers.com/showthread.php?t=3034811
- Scroll down to the "Attached Files" section and download the latest xposed installer currently (xposedInstaller_3.0_alpha4.apk)
Copy both files to the SD-CARD of your phone
Restart your phone into TWRP
Click on the INSTALL button
Flash the xposed framework file (xposed-v85-sdk23-arm64.zip)
Restart your phone and let it start normally
Go to Settings -> General Tag -> Fingerprints & security, Scroll down to the Phone Administration category and make sure there is a check mark next to Unknown Sources option
Open a file manager
Go to the location of the xposed apk
Install the xposed installer .apk file (xposed Installer 3.0 Alpha 4 apk)
Go to Settings -> General Tag -> Fingerprints & security, Scroll down to the Phone Administration category and remove the check mark next to Unknown Sources option
Start the xposed app
How to enter download mode
Power off the phone
Press and hold the VOLUME UP key
Connect the phone while holding the VOLUME UP key to your PC (use a USB-C cable)
Keep holding the VOLUME UP key until you boot into download mode
How to fix the Fastboot device driver issue (no devices detected)
Visit the following website and follow the instructions: Manually installing Android ADB USB Driver
**Changelog + News & Additions**
Changelog (for the guides only):
7.16.16 - All guides have been updated to reflect the new 10d .kdz and .tot files. All links to tools, .kdz, and .tot files have been updated as well.
News & Additions:
7.16.16 - Multiple updates
A modified H83010d rooted .tot file has been released (thanks to Tungkick & wolfu11)
Guides are safe to use again. All links in all the guides have been updated to reflect the new H83010d files
If TWRP is not showing the internal storage but only the external SD-card take a look at post 24
7.9.16 - There is a new firmware update (H83010d) for the LG G5 (T-mobile) which is not compatible with firmware (H83010a) the .TOT files used in this thread have
If you upgrade to this new firmware, you will lose root.
There is no current way to get root on the new H83010d firmware unless the modified .TOT / KDZ files are released with TWRP included
There is an anti-rollback feature in the LG G5 (t-mobile) phone that prevents you from flashing back the H83010a firmware after you upgrade to the H83010d firmware. Attempting to do this WILL BRICK your phone!
Do not attempt to use the guides which are using H8301a .tot / kdz files if you have updated to H8301d. I will be updating the guides as soon as the H83010d modified .tot / kdz files come out.
5.29.16 - LG G5 & LG V10 possible driver issue: First reported on Post#6
If you own an LG V10 and have used your PC to root it, you most likely installed drivers, tools, and or files specific for the V10. What this means is that you may have to uninstall those drivers, tools, and or files prior to installing anything to be used for rooting the G5. This does not include the ADB program which can work for both.
i just felt the need to post and say thanks for this even though i dont need it. Great effort pulling these together, they look good and are very clear. Thanks! :good:
mallman said:
i just felt the need to post and say thanks for this even though i dont need it. Great effort pulling these together, they look good and are very clear. Thanks! :good:
Click to expand...
Click to collapse
Thank you.
Thank you for the walk through. I had a little trouble with drivers and had to uninstall all drivers and reinstall exactly as you have it written here for it to work. I have a LG V10 which probably caused some conflict.
Two questions:
1) Does this automatically encrypt the phone? After flashing both the no verity and the SU it boots in to "encrypting" with no other option. I have not had this happen with any other device. Did I mess something up?
2) The password at the beginning of TWRP is requested every time, even after flashing the no verity zip. What did I do wrong?
Click to expand...
Click to collapse
ETA:
Something wasn't right about the No Verity app. I redid entire process and was able to get it to work with root being successful. Left this up for others - I Believe my mistake was using an external SD to install SU first and then no verity. For some reason they were NOT showing in TWRP on the internal SD even though I KNOW they were there.
skyfox99 said:
Thank you for the walk through. I had a little trouble with drivers and had to uninstall all drivers and reinstall exactly as you have it written here for it to work. I have a LG V10 which probably caused some conflict.
ETA:
Something wasn't right about the No Verity app. I redid entire process and was able to get it to work with root being successful. Left this up for others - I Believe my mistake was using an external SD to install SU first and then no verity. For some reason they were NOT showing in TWRP on the internal SD even though I KNOW they were there.
Click to expand...
Click to collapse
Thank you for your input skyfox99. Your solution to the issues you faced will help others avoid them. You made me think of something I did not anticipate which is what happens when you attempt to root your G5 using the same PC you used to root a V10. I am definitely adding a service announcement to the Changelog (post#3) to address this possible issue.
When I get to step 13: Verify that the LGUP Tool works... the progress frame never shows up, even after restarting my PC. Am I missing something? Please help
bigchuq said:
When I get to step 13: Verify that the LGUP Tool works... the progress frame never shows up, even after restarting my PC. Am I missing something? Please help
Click to expand...
Click to collapse
Are you booting into download mode?
---------- Post added at 12:56 PM ---------- Previous post was at 12:56 PM ----------
skyfox99 said:
Thank you for the walk through. I had a little trouble with drivers and had to uninstall all drivers and reinstall exactly as you have it written here for it to work. I have a LG V10 which probably caused some conflict.
ETA:
Something wasn't right about the No Verity app. I redid entire process and was able to get it to work with root being successful. Left this up for others - I Believe my mistake was using an external SD to install SU first and then no verity. For some reason they were NOT showing in TWRP on the internal SD even though I KNOW they were there.
Click to expand...
Click to collapse
Your internal storage gets wiped. That's why they weren't there.
mikeyinid said:
Are you booting into download mode?
---------- Post added at 12:56 PM ---------- Previous post was at 12:56 PM ----------
Your internal storage gets wiped. That's why they weren't there.
Click to expand...
Click to collapse
No I was not, I'll give it a shot. Thanks
mikeyinid said:
Are you booting into download mode?
---------- Post added at 12:56 PM ---------- Previous post was at 12:56 PM ----------
Your internal storage gets wiped. That's why they weren't there.
Click to expand...
Click to collapse
i believe i'm having the same issue, no files show up in the explorer in TWRP regardless. I've been using a usb thumb drive with a usb c adapter to flash files from twrp. i followed directions perfectly and i still see the warning encryption message and read-only message when starting twrp every time.
i have root tho and everything seems to be working fine
snowlin said:
i believe i'm having the same issue, no files show up in the explorer in TWRP regardless. I've been using a usb thumb drive with a usb c adapter to flash files from twrp. i followed directions perfectly and i still see the warning encryption message and read-only message when starting twrp every time.
i have root tho and everything seems to be working fine
Click to expand...
Click to collapse
Anyone find a fix to this? I'm stuck in the same spot, I've gone through the entire process twice now, including resetting the phone back to 6. No matter what I try it seems TWRP won't mount my internal storage!
thoward3 said:
Anyone find a fix to this? I'm stuck in the same spot, I've gone through the entire process twice now, including resetting the phone back to 6. No matter what I try it seems TWRP won't mount my internal storage!
Click to expand...
Click to collapse
I guess I'm having trouble understanding exactly what your issue is. Are you saying that when you boot into TWRP and you go to the INSTALL section to flash the encryption zip and the superSU zip you don't see the files? Can you attach a few screenshots so that I can better understand what you are going through. Thank you.
mikeyinid said:
Your internal storage gets wiped. That's why they weren't there.
Click to expand...
Click to collapse
No, I copied after wipe so they were there. Computer recognized them and so does file manager.
jun19inf said:
I guess I'm having trouble understanding exactly what your issue is. Are you saying that when you boot into TWRP and you go to the INSTALL section to flash the encryption zip and the superSU zip you don't see the files? Can you attach a few screenshots so that I can better understand what you are going through. Thank you.
Click to expand...
Click to collapse
TWRP has trouble mounting.
thoward3 said:
Anyone find a fix to this? I'm stuck in the same spot, I've gone through the entire process twice now, including resetting the phone back to 6. No matter what I try it seems TWRP won't mount my internal storage!
Click to expand...
Click to collapse
There is a TWRP bootloop set of instructions in another thread, run those commands and see if it resolves it, maybe?
snowlin said:
i believe i'm having the same issue, no files show up in the explorer in TWRP regardless. I've been using a usb thumb drive with a usb c adapter to flash files from twrp. i followed directions perfectly and i still see the warning encryption message and read-only message when starting twrp every time.
i have root tho and everything seems to be working fine
Click to expand...
Click to collapse
I had to reflash no verity a few times, before installing SU. There seems to be a problem with TWRP.
Sent from my LG-H830 using Tapatalk
I didn't have any of the issues you guys are reporting in this thread. TWRP sees both internal storage and SD card. And has since I originally rooted.
Will unlocking the bootloader and rooting my phone or if I install a ROM take away my sim unlock?
Sent from my LG-H830 using XDA-Developers mobile app
shaneg79 said:
Will unlocking the bootloader and rooting my phone or if I install a ROM take away my sim unlock?
Sent from my LG-H830 using XDA-Developers mobile app
Click to expand...
Click to collapse
This is a good question and I unfortunately do not know the answer. I truly don't think your sim will be affected but I am not sure. Sorry.
jun19inf said:
This is a good question and I unfortunately do not know the answer. I truly don't think your sim will be affected but I am not sure. Sorry.
Click to expand...
Click to collapse
It's ok I found out it doesn't affect it thanks for your answer.
Sent from my LG-H830 using XDA-Developers mobile app
I'm having the same issue that some of you had. When I boot into recovery, I can't find the zip files anywhere. Was anybody able to figure it out??
rebelde80 said:
I'm having the same issue that some of you had. When I boot into recovery, I can't find the zip files anywhere. Was anybody able to figure it out??
Click to expand...
Click to collapse
It's a very weird problem and unfortunately the only thing I can think off is that TWRP might not be compatible with the SD-Card you are using.
Today, my phone got bricked after I installed Magisk, am i am looking for a way of sorting it out. The phone was running Android 9 DP3 when rooted, and I was following HighOnAndroids root guide on Youtube for reference,
I unlocked my bootloader and successfully installed TWRP. After this, I installed Magisk, which went throuygh perfectly fine. However, after rebooting the phone, I am stuck on the google splash screen, with a small progress bar that stays for the duration of the time on this screen. After about 2 minutes, the phone reboots into TWRP again.
Does anyone know how I could return to stock Android or at least escape this issue?
Many thanks
James
Jameswebb97 said:
Today, my phone got bricked after I installed Magisk, am i am looking for a way of sorting it out. The phone was running Android 9 DP3 when rooted, and I was following HighOnAndroids root guide on Youtube for reference,
I unlocked my bootloader and successfully installed TWRP. After this, I installed Magisk, which went throuygh perfectly fine. However, after rebooting the phone, I am stuck on the google splash screen, with a small progress bar that stays for the duration of the time on this screen. After about 2 minutes, the phone reboots into TWRP again.
Does anyone know how I could return to stock Android or at least escape this issue?
Many thanks
James
Click to expand...
Click to collapse
Use duces script to flash June google factory image.
jlokos said:
Use duces script to flash June google factory image.
Click to expand...
Click to collapse
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Jameswebb97 said:
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
You need this information (the stuff I made bold + the hyperlink):
Code:
If you are having issues with this script:
Download the latest fastboot and adb Platform Tools UPDATED Dec. 22, 2017!!! This is the most common problem!!!
Download/Update Google USB Drivers
Video: Force-Installing the Android USB Drivers Fastboot & ADB
[B]Verify you have the [URL="https://wiki.lineageos.org/adb_fastboot_guide.html"]environment variable (path)[/URL] set for adb and fastboot[/B]
Try a different USB port
Try a different cable
Format Userdata in Stock Recovery
Try to boot stock before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
Jameswebb97 said:
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
umph....hate to tell you, but you have a long way to go...
so before going on this "journey", I would suggest you booting into TWRP again, and try installing (not adb sideloading, just in case you're doing that) Magisk again. Also, be sure you are using the latest (might be considered "beta") 16.4 for taimen... I'm thinking your boot.img or dtbo.img simply may have gotten glitchy and repatching (by installing Magisk again) might fix it...
Also, if you want to go a step further, you might want to consider using the official Magisk uninstaller. Since Magisk makes a copy of your stock boot and dtbo image, it may put that back so you can get it in working order to get into the system (although without root), and then figure things out and/or reinstall Magisk (through TWRP is best) while all things Magisk was removed...
Good luck and hope this helps....
Make sure you are trying to open from the correct location, and put .\fastboot
EvilDobe said:
You need this information (the stuff I made bold + the hyperlink):
Code:
If you are having issues with this script:
Download the latest fastboot and adb Platform Tools UPDATED Dec. 22, 2017!!! This is the most common problem!!!
Download/Update Google USB Drivers
Video: Force-Installing the Android USB Drivers Fastboot & ADB
[B]Verify you have the [URL="https://wiki.lineageos.org/adb_fastboot_guide.html"]environment variable (path)[/URL] set for adb and fastboot[/B]
Try a different USB port
Try a different cable
Format Userdata in Stock Recovery
Try to boot stock before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
Click to expand...
Click to collapse
Ive tried all of this now, i got the script working, but now the phne says it is corrupt and i cannot get into recovery. Is this game over do you think?
simplepinoi177 said:
umph....hate to tell you, but you have a long way to go...
so before going on this "journey", I would suggest you booting into TWRP again, and try installing (not adb sideloading, just in case you're doing that) Magisk again. Also, be sure you are using the latest (might be considered "beta") 16.4 for taimen... I'm thinking your boot.img or dtbo.img simply may have gotten glitchy and repatching (by installing Magisk again) might fix it...
Also, if you want to go a step further, you might want to consider using the official Magisk uninstaller. Since Magisk makes a copy of your stock boot and dtbo image, it may put that back so you can get it in working order to get into the system (although without root), and then figure things out and/or reinstall Magisk (through TWRP is best) while all things Magisk was removed...
Good luck and hope this helps....
Click to expand...
Click to collapse
This is good advice, thanks. i have a new problem (ugh), where i got the script working through changing the paths, but now the phone says that it is corrupt and i cannot access TWRP. Game over?
Jameswebb97 said:
Ive tried all of this now, i got the script working, but now the phne says it is corrupt and i cannot get into recovery. Is this game over do you think?
Click to expand...
Click to collapse
With the unlocked bootloader it'll always say the device is corrupt. Manually put the device into the bootloader & flash the DeucesScript. You're basically starting over at this point but it is possible to get up & going again.
Jameswebb97 said:
This is good advice, thanks. i have a new problem (ugh), where i got the script working through changing the paths, but now the phone says that it is corrupt and i cannot access TWRP. Game over?
Click to expand...
Click to collapse
EvilDobe said:
With the unlocked bootloader it'll always say the device is corrupt. Manually put the device into the bootloader & flash the DeucesScript. You're basically starting over at this point but it is possible to get up & going again.
Click to expand...
Click to collapse
EvilDobe might be right...but I have a bit to offer before maybe starting all over...
I doubt you needed to edit the script and "change the paths." Most likely you merely did not have the images (you extracted from the .zip of the Full Factory image you got from the Google Developers site) inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders.
In any case, I suggest you get the TWRP image file [.img] (NOT the installer .zip necessarily), put the .img file "... inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders." (I've seen some users simply cut and paste those 2 .exe files only to the extracted folder -- this is why I state it this way) Then, power down your device. After it's off, hold down the Volume Down button and press & hold the Power button (this is the manual way to get into the Bootloader Mode). Once there, plug your phone into your computer (USB-A to USB-C would be best) and open a command prompt/powershell ("run as administrator" or with administrative priveleges) and direct it to the platform-tools folder (i.e. if I put it on my desktop, it would be "C:\Users\MyName\Desktop\platform-tools"), you can temporarily boot into TWRP via command
Code:
fastboot boot twrp-3.2.1-2-taimen.img
When in TWRP (hopefully), I suggest trying to do what I advised before -- try either Magisk installer to repatch the boot and dtbo image, or Magisk Uninstaller to attempt to replace your boot and dtbo to stock.
*NOTE: Of course, this is assuming you are running Microsoft Windows (if not, you will need to input .\ as @naiku suggested) and also the whole "device is corrupt" is due to "funky" boot image issues. If not, I/we can guide you to flashing the Full Factory back onto the phone (hopefully without losing data and settings)...
Good luck and hope this helps...
simplepinoi177 said:
EvilDobe might be right...but I have a bit to offer before maybe starting all over...
I doubt you needed to edit the script and "change the paths." Most likely you merely did not have the images (you extracted from the .zip of the Full Factory image you got from the Google Developers site) inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders.
In any case, I suggest you get the TWRP image file [.img] (NOT the installer .zip necessarily), put the .img file "... inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders." (I've seen some users simply cut and paste those 2 .exe files only to the extracted folder -- this is why I state it this way) Then, power down your device. After it's off, hold down the Volume Down button and press & hold the Power button (this is the manual way to get into the Bootloader Mode). Once there, plug your phone into your computer (USB-A to USB-C would be best) and open a command prompt/powershell ("run as administrator" or with administrative priveleges) and direct it to the platform-tools folder (i.e. if I put it on my desktop, it would be "C:\Users\MyName\Desktop\platform-tools"), you can temporarily boot into TWRP via command
Code:
fastboot boot twrp-3.2.1-2-taimen.img
When in TWRP (hopefully), I suggest trying to do what I advised before -- try either Magisk installer to repatch the boot and dtbo image, or Magisk Uninstaller to attempt to replace your boot and dtbo to stock.
*NOTE: Of course, this is assuming you are running Microsoft Windows (if not, you will need to input .\ as @naiku suggested) and also the whole "device is corrupt" is due to "funky" boot image issues. If not, I/we can guide you to flashing the Full Factory back onto the phone (hopefully without losing data and settings)...
Good luck and hope this helps...
Click to expand...
Click to collapse
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Jameswebb97 said:
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Click to expand...
Click to collapse
I wouldn't go that far with staying away. When I come across people IRL that want to start doing this stuff I always tell them to read the instructions, step through them, read the instructions again, ask questions (as you did here) BEFORE you get started, read the instructions again, and only when you're confident start messing with your device. This is a fun, and at times stressful, hobby. It's great when everything goes according to plan but it's an omg omg omg omg omg omg moment when you mess something up.
Start with baby steps. The straight upgrade to P is fairly simple provided your device is unlocked. Get that working & you'll be set. I have root on my DP3 & the only thing I've done so far is delete some apps from system that I know I don't want/need. If your main goal is to just enjoy your phone, test out Android P, and maybe go back... root isn't needed. Once everything is squared away & you're running for a day or so you can always fastboot to recovery, make a backup, and then try to add root. I hope you don't shy away & get deeper into the hobby. It truly starts to get fun when you begin to understand more of what is going on.
Jameswebb97 said:
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Click to expand...
Click to collapse
Hey I'm so glad you got it working! Leave me a "Thanks!" would make it up to me ... I'm always happy to help out and get things figured out...yet I don't get the satisfaction of knowing if it does end up helping a lot of the time because a good number don't come back with their experience...so thanks for that! Glad you got it going...
EvilDobe said:
I wouldn't go that far with staying away. When I come across people IRL that want to start doing this stuff I always tell them to read the instructions, step through them, read the instructions again, ask questions (as you did here) BEFORE you get started, read the instructions again, and only when you're confident start messing with your device. This is a fun, and at times stressful, hobby. It's great when everything goes according to plan but it's an omg omg omg omg omg omg moment when you mess something up.
Start with baby steps. The straight upgrade to P is fairly simple provided your device is unlocked. Get that working & you'll be set. I have root on my DP3 & the only thing I've done so far is delete some apps from system that I know I don't want/need. If your main goal is to just enjoy your phone, test out Android P, and maybe go back... root isn't needed. Once everything is squared away & you're running for a day or so you can always fastboot to recovery, make a backup, and then try to add root. I hope you don't shy away & get deeper into the hobby. It truly starts to get fun when you begin to understand more of what is going on.
Click to expand...
Click to collapse
And it's as @EvilDobe means.....
I remember back in the days of the Motorola Droids (OG Droid1, Droid 3, & Droid 4) where you could really mess things up and come out with a big ol' "brick" "paperweight" as there were many instances where you could not come back from (i.e. updating to a certain point, then attempting to downgrade when Google/Motorola/Verizon put blocks that breaks it). But this isn't the case these days. @Jameswebb97, at least with the Pixel 2's, Oreo and/or P(Android OS 9), it's actually more difficult than easy to get that too far gone. The only reason why I can help so many troubleshooting their issues is because I, myself, have wrecked my current device in some serious ways! So I can relate and have experience in helping in the same situations. I've gotten it to where it says "device is corrupt," (which isn't all that uncommon), BUT with the added desperate troubleshooting where I had to wipe/erase, changing partition types, format several partitions, even go about "resizing" the partition to match the "target extraction size" of the Full Factory flash, and even as far as learning to manually flash the various system partitions and that there are two (system_a & system_b) but, in Google's infinite wisdom(?), one flashes to system_a and the other to system_other!!! And I haven't even started on reading others' issues when going after the Slot A and Slot B complications -- I didn't even attempt to touch this in that troubleshooting story.
My point is: I think I've broken my device farther than most people and got it so close to the brink, and yet I was able to bring it back and am still using that same device today (most people would usually, at that point, go and get a RMA replacement). Honestly, as long as you have access to Bootloader Mode (which Google, in their infinite wisdom, seems to have placed it in the main board memory or separate memory rather than storage as to make it always accessible which makes it hard to "lose"), you have a really good (seemingly perfect) "safety net" in which you can always flash back to a working, stock state -- which is why it's the best policy to just make good backups before experimenting so, if anything, you get back to this state and restore all your data. I'm not trying to convince you to root or to try custom ROMs or anything -- even though there are many great reasons and capabilities of rooting -- I am simply appealingl to your sense of curiosity and reassure you so you aren't held back and you don't restrict and limit yourself if you don't want to, but are to fearful to experiment.
I hope you don't take this post as "lecturing" or anything, just some thoughts I hope you consider...
Glad it worked out in the end for you!
Someone was "helping" me root my Mi Mix2. I can't be 100% sure what went wrong, but he managed to get it stuck in Fastboot mode, such that no matter what I do (i.e. any combination of power offs, or simultaneous button presses, or commands from terminal). I suspect he did not understand me when I said Magisk was tool best suited...he may have used some more familiar or standard tool like SuperSU or something to try and root.
Assuming I have sufficiently described my problem, is there anything I can do to get the phone back into a usable state?
Is your bootloader unlocked? If yes try to flash ROM using miflash tool.
I appreciate the response/suggestion.
fotocreaman said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Yes. I double checked with "fastboot oem device-info" commmand
fotocreaman said:
If yes try to flash ROM using miflash tool.
Click to expand...
Click to collapse
On your advice I did that, including downloading current (?) version and current(?) version of stock ROM. I received a message to effect that a flash script (.bat) file was missing (or at least not found).
Other threads regarding this error suggest unzipping something (?) twice but I didn't see a file inside the original zip file that could be additionally unzipped, and certainly nothing with a .bat extension.
Can you put here the exact error message and when it exactly occurs? Describe the steps you did to get to that point
Hi aa040371
1- download fastboot rom for your phone and unzip it twice , put folder in C:\ storage http://update.miui.com/updates/v1/fullromdownload.php?d=chiron_global&b=F&r=global&n=
2- Look at the tutorial to use miflashtool https://c.mi.com/thread-1857937-1-1.html
regards
I'm Still Here...
So, after more than a few detours and distractions, I have my phone (Mi Mix 2S, not the plain "2" I originally indicated!) basically back to stock...good frustration-tolerance building exercise.
I am currently in the process of trying to get TWRP to remain after booting to OS. I have researched/read numerous threads on this -- e.g. boot into TWRP, flash TWRP, reboot directly into TWRP again -- but somehow none of them do the trick. Every time I boot into the OS, the Recovery partition gets overwritten and I am back to the stock recovery tool. If I can trust/believe what at least one person has indicated online, this appears to be due to a script in /system/bin, but I can't get at that file to rename or delete it. In fact, I can't even see it in the file system as that area is completely locked down. I know it is there as a Find command executed via ADB shell lists it even though it indicates it is off-limits.
So I turned my attention to loading a rooting app/tool instead hoping that would let me get TWRP to hang around for long term...another excursion in futility. My phone model is M1803D5XA, so according to one more forum thread somewhere, I am supposed to be using SuperSU rather than Magisk? Whatever...it seems impossible: most of the zip files I located don't pass security/file-signing check. The one I found that at least starts to load/install (SR5-SuperSU-v2.82-SR5-20171001224502) works fine right up until it fails while trying to update "sepolicy" files. For some reason I have to sideload SuperSU from TWRP because I am not allowed to push a file even to my SDcard via ADB.
I just don't get why this all has to be so difficult, as in each and every step along the way. I feel like Sisyphus or Job or someone similar...sigh Any thoughts or suggestions still welcome...thanks.
aa040371 said:
So, after more than a few detours and distractions, I have my phone (Mi Mix 2S, not the plain "2" I originally indicated!) basically back to stock...good frustration-tolerance building exercise.
I am currently in the process of trying to get TWRP to remain after booting to OS. I have researched/read numerous threads on this -- e.g. boot into TWRP, flash TWRP, reboot directly into TWRP again -- but somehow none of them do the trick. Every time I boot into the OS, the Recovery partition gets overwritten and I am back to the stock recovery tool. If I can trust/believe what at least one person has indicated online, this appears to be due to a script in /system/bin, but I can't get at that file to rename or delete it. In fact, I can't even see it in the file system as that area is completely locked down. I know it is there as a Find command executed via ADB shell lists it even though it indicates it is off-limits.
So I turned my attention to loading a rooting app/tool instead hoping that would let me get TWRP to hang around for long term...another excursion in futility. My phone model is M1803D5XA, so according to one more forum thread somewhere, I am supposed to be using SuperSU rather than Magisk? Whatever...it seems impossible: most of the zip files I located don't pass security/file-signing check. The one I found that at least starts to load/install (SR5-SuperSU-v2.82-SR5-20171001224502) works fine right up until it fails while trying to update "sepolicy" files. For some reason I have to sideload SuperSU from TWRP because I am not allowed to push a file even to my SDcard via ADB.
I just don't get why this all has to be so difficult, as in each and every step along the way. I feel like Sisyphus or Job or someone similar...sigh Any thoughts or suggestions still welcome...thanks.
Click to expand...
Click to collapse
Recovery will get overwritten by dm-verity, you have to flash either magisk or another mod that disables dm-verity, but personally I suggest to use a custom rom if you don't care about miui
HrX said:
Recovery will get overwritten by dm-verity, you have to flash either magisk or another mod that disables dm-verity, but personally I suggest to use a custom rom if you don't care about miui
Click to expand...
Click to collapse
Hello...thanks. I definitely don't care about MIUI...in fact the whole exercise I am struggling through is so I can get LineageOS onto my phone. I've probably read 50+ threads/posts on 6-7 different forums regarding unbricking/unlocking/rooting/TWRPing/customROMing my particular phone, but this is the first time I've seen mention of DM-Verity. I'll look into it...not really hopeful, though. But anyway...thanks again.
The phone must be installed TWRP Recovery. Use at your own risk, I'm not responsible for bricking your device.
Installation Instructions:
1. Enter TWRP Recovery Mode: Turn power off; Press and hold Volume Up key + Power key, when samsung logo appears release power key only, keep pressing volume up until TWRP recovery appears
2. Select Wipe - Format Data - type "yes" and confirm
3. Copy GSI ROM to your phone
4. Install - Install Image - select lineage-17.1-20200413-UNOFFICIAL-treble_arm64_bvN.img - select System Image and Confirm to flash.
5. Select Reboot - System ( boot without magisk )
6. Setup the Phone
7. INSTALL GAPPS: Enter TWRP Recovery Mode
8. Copy GAPPS zip file from PC to Phone
9. Select Wipe - Advanced Wipe - select "System" - Repair or Change File System - Resize File System - Confirm to Resize.
10. Select Install - select open_gapps-arm64-10.0-nano-20200408.zip and Confirm Flash
11. Reboot - System
12. ROOTING: Enter TWRP Recovery Mode
13. Copy magisk manager apk from pc to phone
14. Reboot to Recovery ( boot with magisk )
15. Connect the phone to internet
16. Install magisk manager
Done!
Download:
LineageOS 17.1 ROM
Open Gapps
WATCH VIDEO HOW TO INSTALL IT: https://youtu.be/u9gDx6VEORo
Thanks. So this is GSI? Bugs?
Youtube comments mention:
Fingerprint not working.
MTP not working.
Face lock also not working.
but also he say's; "This is Generic GSI ROM, it means. it has some basic feature and limitations"
---
Edit: I couldnt get this to install, followed the how-to and when i tried to reboot i got "no OS installed" in twrp. tried 3 times, but no joy, A505FN
Hello everyone
iam in the Process of considering to put LOS on my device.
But the i saw the remarks from InFam0us-1985
Is it therefor not adviceable to use this on a Samsung Galaxy A505FN because this is exactly what i have
Saludos from Spain
DId i Brick my Samsung Galaxy A505FN?
Hello one Question:
"did i Brick my device if for some reason after Trying to flash TWRP it fell back in to OEM-locked and i’ am now in a Boot Loop, ore is the any Hope?
I used Heimdal and at first it did the Job but then it would not start again as expected.
After some attempts to flash it Properly it suddenly fell back in to OEM-Locked!
Pleas if you now some advice it be greatly aprichiatet
My device is a Samsung Galaxy A505FN (Spain)
I found a way to Unbrick my device
Just to let anyone that pass her know i finally found a way to unbrick my device here it is:
After it falls back in to OEM-Lock i found you can unlock it again by doing whats explained in the Video.
Have fun be Careful when messing around with rooting
Saludos Hans
hans2020 said:
Just to let anyone that pass her know i finally found a way to unbrick my device here it is:
After it falls back in to OEM-Lock i found you can unlock it again by doing whats explained in the Video.
Have fun be Careful when messing around with rooting
Saludos Hans
Click to expand...
Click to collapse
AFAIA, OEM locked you can always flash stock?
I’ am not sure if thats True
InFam0us-1985 said:
AFAIA, OEM locked you can always flash stock?
Click to expand...
Click to collapse
All i know in case of my Samsung Galaxy A50 it is Possible!
To lift the OEM-Lock mode again.
i do not know if that is true for every Device.
Ultimately i was successful to install full Root-access!
I had great difficulty tho to use Heimdall ore any tool on Linux so i ended up using Odin in a VirtuelBox with WinXPpro
but do to no support of Long file names i had to trick there, to to make it work.
I just shorten the Names of every .tar to the first 2 letters.
I was able to successfully flash TWRP with Heimdall but not the Android ROM for my Phone.
I still wonder how to make it work!
There was one Thing i Noticed when Using Odin it seams in the Process he flashes vbmeta.img twice.
That impossible with Heimdall it creates a error message.
Well if anyone - that passes here - knows how to flash a Android 10 ROM of a Samsung Galaxy A50 using Heimdall let me know i tried very very hard to no avail.
I was surprised to learn there is no Good Tool for Linux-user doing this Task.
i only found Old Tutorials!
Is it truly possible that Heimdall dose not support modern Phone-flashing anymore properly?
As of now if a Linux-user ask me about Rooting i would advice him/her to do it in a VritualBox with windows installed.
If you have a License of a Windows Version Higher then XP good otherwise you have to Shorten File names if the very long to make it work.
I scarcely use windows anymore that why i only have a old WinXPpro legally in my Possession.
Unbelievable that the Linux-Community should not have a modern Flash Tool!???
Saludos
Hans
---------- Post added at 12:38 PM ---------- Previous post was at 12:18 PM ----------
Hello to @everyone
I had great difficulty to do this as a Linux User using Heimdall and eventually had to give up (after trying for 3 full days)!
I ended up doing it using Windows out of a VirtualBox!
It was Possible tho to successfully flash TWRP using Heimdall!
It also showed Success when Flashing Android 10 Version for my Phone but would not work.
Using the same Firmware with Odin it worked just fine.
When i compared the Flash-Protocol of Odin with what i did i only Noticed that Odin would flash vbmeta.img twice in the Process something that cant be done with Heimdall as it produces the duplicate error.
I wonder if this is the Reason it would not work.
I was also surprised to Learn, that there is virtual now Tutorial out there using Heimdall on a Modern Phone (last 12 Month ore less).
Is it truly Possible that There is now good solution for Linux Users?
I also Looked in to Fastboot and ADB and other Tools for Linux Platform and they all seam to be outdated!
Also all this Tools could not accomplish the task at hand.
Now if its me and anyone knows how to make it Work on Heimdall let me know as it is a Pretty good tool after all and by now i know it well. I would gladly start to make a tutorial and provide it here for free if i know how to make it work.
I have a txt file where i made a complete Protocol of all i tried if someone is curious ill send it to you.
Saludos Hans
##################################################################
I send some more Details of my Challenge in hope someone my know what it is i have to change!
My Device:
Samsung Galaxy A505FN
I created a .txt file protocol of all i did, i gladly provide it if someone ants to see it.
I analyzed the Whole Firmware-archive and the Pit file of my Phone to eventually find the Problem.
Note:
The Firmware was the correct one as it worked just fine using Odin!!
Analyzing all this, i only noticed two things:
First:
There are 3 seemingly identical files in the Archive and two so called
fota.zip files witch are not Identical
(one in the AP-Packet and one in the CSC-Packet)
Those where:
– cache.img one in the AP-Packet and one in the BL-Packet
– vbmeta.img one in the AP-Packet and one in the BL-Packet
– product.img one in the AP-Packet and one in the BL-Packet
Second:
Once i used Odin to finally flash successfully i noticed that in the Flash-protocol of Odin it seams Odin flashes the vbmeta.img twice in the process!?
Heimdall would not allow me to do so giving me the “Duplicate Error message”
Furthermore i tried one more thing in my desperation to make it work:
i thort: “maybe the order in wish the files a flashed chronologically matters”
So i did exactly that, trying to flash in the same chronological sequence as Odin did.
Note:
Every time i flashed, Heimdall would successfully finish the process but the Phone would not start with android
no matter what i tried.
ALSO i did successfully flash TWRP to my Phone using Heimdall
SO Heimdall works just fine on my system!
I spend a Long Time searching the Internet for a workable Tutorial or glue’s as to what is missing and how i could make it work.
I really want to succeed doing this, as i want to provide my folks offer her in Germany and also English and Spanish speaking Linux-Community with a Tutorial to do this!
I did also drop this Question and Challenge i face in some other Forums no useful answer returned so far
The latest Governmental Abuses and infringement on Peoples Privacy using Corona as excuse, makes it abundantly clear how important this kind a work is!
As for now i think, the only true option for a Linux-User is to run Odin from a Virtual-Box Windows installation, given
you have a legal copy in you're possession and have higher then Windows XP
(else you must change the Filenames of the .tar archives as WIndows XP and lower did not support excessively long filenames.)
Also you have to Install you're Phone USB drivers and have them up and running properly!
Internet access to you're VB makes it all more comfortable, but you can also use Shared folders with the Host-System to do the job.
Note:
I did indeed tried the "WINE-plugin-environment" (Windows 10) under Linux. i could not get it to work.
It was to much messing around make it recognize the USB-connection to the Phone!
I could not get it to work, I don't know if you can?
I guess that would be a nice way for Linux-users if it could be made to work!
What do you guys think, can this be solved?
Pleas let me know if you know the answer to my Challenge!
You're help is not only needed but would be greatly appreciated
Sincerely yours
Hans from Germany
well I Found this from 2017;
Yes you can do fastboot and adb cmd in Linux but you have to install adb and fastboot drivers to Linux by using
1) sudo add-apt-repository ppahablet-team/tools && sudo apt-get update
2) sudo apt-get install android-tools-adb android-tools-fastboot
That's it you get your fastboot and adb cmd’s all the cmds are same just as windows just you need to add sudo in front if not in root
Click to expand...
Click to collapse
source: https://www.quora.com/Can-I-flash-Android-devices-using-Linux
so maybe have a read of this too; https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/
Well i do know
Of course i know how to Install a Software on Linux and i did indeed installed those Two
But both of them would not even Detect my device jet Heimdall and Odin had no problem doing that.
Anyhow i might go about and try those Two harder.
And no Iam not confused
thank you anyway
Saludos Hans
InFam0us-1985 said:
well I Found this from 2017;
source: https://www.quora.com/Can-I-flash-Android-devices-using-Linux
so maybe have a read of this too; https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/
Click to expand...
Click to collapse
I cant call or receive call and send and receive messages via sim
Please help
I cannot call and receive calls
Cannot send and receive messages ,one time passwords, through message
Cannot login through whatssapp .
volte is not enabled
And no option for it to enable
I am from India using jio sim card .
Please help.
If any custom rom is used in my SM-A505F i cant do calls or receive calls nor send or receive messages.
country id : INS
Original firmware of A50 : Atb6
Will this image work with the SM-A505G version?
USB File Transfer Does Not Work
After flashing the ROM, when I connect my phone to my PC with the USB cable to transfer files, it does not work. No errors on my PC. I tries switching between modes and back to File Transfer as some suggested, but no luck.
Has anyone experienced this and if so, any solution?
OmariCelestine said:
After flashing the ROM, when I connect my phone to my PC with the USB cable to transfer files, it does not work. No errors on my PC. I tries switching between modes and back to File Transfer as some suggested, but no luck.
Has anyone experienced this and if so, any solution?
Click to expand...
Click to collapse
This is what you get with a GSI, finger print wont work either.
InFam0us-1985 said:
This is what you get with a GSI, finger print wont work either.
Click to expand...
Click to collapse
Actually it's the only Custom ROM where the finger print works. My only problem was with the USB File Transfer.
OmariCelestine said:
Actually it's the only Custom ROM where the finger print works. My only problem was with the USB File Transfer.
Click to expand...
Click to collapse
Try with a custom kernel
the project is down? Because I love LineageOs, but the A50 is abandoned :/
---------- Post added at 06:06 AM ---------- Previous post was at 05:57 AM ----------
OmariCelestine said:
Actually it's the only Custom ROM where the finger print works. My only problem was with the USB File Transfer.
Click to expand...
Click to collapse
you need to run into Twrp and it work. But only in TWRP
hey man, the project is being upgraded? Tanks for your time
InFam0us-1985 said:
Youtube comments mention:
Fingerprint not working.
MTP not working.
Face lock also not working.
but also he say's; "This is Generic GSI ROM, it means. it has some basic feature and limitations"
---
Edit: I couldnt get this to install, followed the how-to and when i tried to reboot i got "no OS installed" in twrp. tried 3 times, but no joy, A505FN
Click to expand...
Click to collapse
Got the same problem here. i guess i'm staying on the stock firmware
I have installed lineage-17.1-20210212-UNOFFICIAL-treble_arm64_bvS.
Fingerprint and MTP working.