Develop Bugs

Honor 7X with installed TWRP bricked by OTA update ... any help?

Hi,
the first time after years of installation of custom roms ... seems it happens to everyone once a while. What happened? I installed TWRP and Magisk with a bit of trouble but finally it worked well. Put the box aside to finalize installation a day later. During the night an OTA update came in together with a Magisk v15 update. So in the morning not really fresh in my head I looked on the display, thought it was my son's 7X (which is untouced on stock rom) and accepted installation and reboot ... BAMMM ... only the line "Your device is booting now ..." gets added to the unlock message screen, that's it. TWRP can still be reached, it is the only mean of shutting the box down, since holding down the power button until shutdown gets it back to the boot screen.
AH ... just for completeness: It is a BND-L21 ... or at least it has been one.
Update: After another night just laid down and switched off even TWRP is gone, now the EMUI recovery gets booted. No way to shut down the device besides let it drain the battery. I have no idea what this piece of crap will do after next reboot.
Already checked: There is currently no way to download the stock rom. And also the EMUI recovery can't locate a downloadable package on the servers.
Second Update: I still can reach TWRP by pressing all 3 buttons together during boot. By this I can get to bootloader and it gets recognized by fastboot on connected PC. But the EMUI resore kicked in again and now TWRP is again on just Vol+ together with PWR. TWRP is not able to save the settings (e.g. TZ). Is there a corrupted file system responsible for some of the issues? Power off initited by TWRP can only be reached if no charging USB cable is connected.
Any help or any idea? Tnx in advance. :good:

ZB2016 said:
Hi,
the first time after years of installation of custom roms ... seems it happens to everyone once a while. What happened? I installed TWRP and Magisk with a bit of trouble but finally it worked well. Put the box aside to finalize installation a day later. During the night an OTA update came in together with a Magisk v15 update. So in the morning not really fresh in my head I looked on the display, thought it was my son's 7X (which is untouced on stock rom) and accepted installation and reboot ... BAMMM ... only the line "Your device is booting now ..." gets added to the unlock message screen, that's it. TWRP can still be reached, it is the only mean of shutting the box down, since holding down the power button until shutdown gets it back to the boot screen.
AH ... just for completeness: It is a BND-L21 ... or at least it has been one.
Update: After another night just laid down and switched off even TWRP is gone, now the EMUI recovery gets booted. No way to shut down the device besides let it drain the battery. I have no idea what this piece of crap will do after next reboot.
Already checked: There is currently no way to download the stock rom. And also the EMUI recovery can't locate a downloadable package on the servers.
Second Update: I still can reach TWRP by pressing all 3 buttons together during boot. By this I can get to bootloader and it gets recognized by fastboot on connected PC. But the EMUI resore kicked in again and now TWRP is again on just Vol+ together with PWR. TWRP is not able to save the settings (e.g. TZ). Is there a corrupted file system responsible for some of the issues? Power off initited by TWRP can only be reached if no charging USB cable is connected.
Any help or any idea? Tnx in advance. :good:
Click to expand...
Click to collapse
Restoring the backup is the only solution it seems.

Yes ... hmmm ... backup ... that was what I intended to do that morning when the BAMMMM happened. I really had a bad start with the 7X ...
So in case someone has a backup of a clean or nearly clean system partition, please send me a PN. Tnx in advance!

Normal make a Backup in Twrp before modify the System Partition.
Make not an Official Ota Update with Rooted and Twrp installed Rom

Its not the phones mistake that you mess up and wakeup and take the phone for a spin in half sleep
and bamm, i really dont know what that meant. i would say go to the honor care center and get it to them to work.
the procedure which i know of is tough and things like bamm happening might worsen things like TWRP not starting at all.
i have seen people bricking their phones but its never the phones fault.
i would never recommend doing a "BAMM" thing doing and flashing all the stuff randomly cz i dont think magisk is supported fully yet to our phone and you flashed it without asking anyone.
the other russian forums are flashing chinese stock firmware which is the only original firmware available, but the task to change the settings to work for other variant is a huge stock which i gave link to a few people but for you i wont recommend that cz obviously your situation is totally different so go to the honor center and explain them and they would help you.
good luck! next time verify and be careful before flashing anything at random cause its not the phones fault.

Thanks for help, guys. Really ... even though it helped me not a single bit.
My activity has obviously not been on purpose. 2 phones, both looking exactly the same and they are without any apps so far. Since TWRP installation did not went smooth I will not tweak my son's device, therefore even if I have a second device more or less available, I will not touch it to get a system backup. And yes, TWRP backup should be the first thing to do but I have not had the time at that moment. So ... it is the way it is. Magisk is been described as a recommendation at another site, therefore I put it in also for the root hide functionality (my son loves Pokemon go, which will not run on rooted phones), because I wanted to try it first on my phone. Bad luck I would say.
And yes, I'm quite clear about the fact, that the computer just does what you tell it to do ... if you ruin the areas where the OS is located, then it is your own fault and not the device's. Nevertheless it freaks me a bit.
I am really looking forward for a nice AOSP or LineageOS version for the 7X. Oreo or Nougat, I'm fine with any of those. But I would expect, that this will take some time.

ZB2016 said:
Thanks for help, guys. Really ... even though it helped me not a single bit.
My activity has obviously not been on purpose. 2 phones, both looking exactly the same and they are without any apps so far. Since TWRP installation did not went smooth I will not tweak my son's device, therefore even if I have a second device more or less available, I will not touch it to get a system backup. And yes, TWRP backup should be the first thing to do but I have not had the time at that moment. So ... it is the way it is. Magisk is been described as a recommendation at another site, therefore I put it in also for the root hide functionality (my son loves Pokemon go, which will not run on rooted phones), because I wanted to try it first on my phone. Bad luck I would say.
And yes, I'm quite clear about the fact, that the computer just does what you tell it to do ... if you ruin the areas where the OS is located, then it is your own fault and not the device's. Nevertheless it freaks me a bit.
I am really looking forward for a nice AOSP or LineageOS version for the 7X. Oreo or Nougat, I'm fine with any of those. But I would expect, that this will take some time.
Click to expand...
Click to collapse
I have sent you the pm for a procedure i know of been tested by members of the other forums but since their language is russian i was skeptical and i asked a few devs to test it but none have tried it yet.. Im sending u the link and use google translate but obv.. No one from xda can help you if its from another forum.. Test if you want to at your own risk.. Good luck.. Or wait for a release

sid21 said:
I have sent you the pm for a procedure i know of been tested by members of the other forums but since their language is russian i was skeptical and i asked a few devs to test it but none have tried it yet.. Im sending u the link and use google translate but obv.. No one from xda can help you if its from another forum.. Test if you want to at your own risk.. Good luck.. Or wait for a release
Click to expand...
Click to collapse
Thanks a lot, you made my day. Iwill at least try to investigate the content of the articles. If the translation leads to confusing sections, I will hand over the phone to the care center as you suggested earlier. Again ... YOU REALLY MADE MY DAY!

ZB2016 said:
Thanks a lot, you made my day. Iwill at least try to investigate the content of the articles. If the translation leads to confusing sections, I will hand over the phone to the care center as you suggested earlier. Again ... YOU REALLY MADE MY DAY!
Click to expand...
Click to collapse
I am in contact with the user who posted the article and tested it himself and requested a proper one in english language but he is busy so it hasnt proceeded.. But soon he ll be free to write one up for me so i will post it on XDA..

I'm in a very similar boat. The Magisk v15 update bricked my L24. I had another one available and have made back ups through twrp to restore on the bricked one. It actually boots, but all I get is a black screen with the menu, home, and back buttons now. Holding power gives me the options to restart and power off. Hope they release the stock rom soon, or custom roms be available soon.

root your son's 7x, make a boot and system backup and restore that in your phone.
reboot

Kindly refer to my thread for the procedure in order to unbrick or flash the stock firmware : Link to the thread

Sudeep Duhoon said:
root your son's 7x, make a boot and system backup and restore that in your phone.
reboot
Click to expand...
Click to collapse
As long as the 7X behaves unusual compared to other phones that I know (entered Android's world with Gingerbred), I will not customize my son's device.

sid21 said:
Kindly refer to my thread for the procedure in order to unbrick or flash the stock firmware : Link to the thread
Click to expand...
Click to collapse
Back to life ... at least about 80%. Rooting leads to corrupt system partition (unable to boot afterwards) and bootloader can only be reached while a USB cable is connected (unusual behaviour). Nevertheless ... got it running. SID ... you are my hero of the day. Will PM you regarding comments for your thread.

ZB2016 said:
As long as the 7X behaves unusual compared to other phones that I know (entered Android's world with Gingerbred), I will not customize my son's device.
Click to expand...
Click to collapse
i think i have to write a guide now. this was the first but more can come soon enough. may be today i'll write a guide to backup your phone (all 48 partitions) and then root so you always have all the necessary files to restore it back to life.

sid21 said:
Kindly refer to my thread for the procedure in order to unbrick or flash the stock firmware : Link to the thread
Click to expand...
Click to collapse
Plz give link of custom rom for honor 7x

dhananjay 007 said:
Plz give link of custom rom for honor 7x
Click to expand...
Click to collapse
Who made custom rom for the phone?

sid21 said:
Who made custom rom for the phone?
Click to expand...
Click to collapse
I don't know
---------- Post added at 11:00 AM ---------- Previous post was at 10:59 AM ----------
sid21 said:
Who made custom rom for the phone?
Click to expand...
Click to collapse
I have honor 7x.

dhananjay 007 said:
I don't know
---------- Post added at 11:00 AM ---------- Previous post was at 10:59 AM ----------
I have honor 7x.
Click to expand...
Click to collapse
So why are you even asking me for a custom rom?
If you know no one has made yet

UPDATE ... got it back to life, at least partly. The only thing is, that constantly the android adaptions of Huawei is making it unnecessary complex or is stopping progress at all. This is the log of my actual tasks. Key to progress was the unlocking of the system fs, which has some inconsistencies in the file system. In general, it gives me a 7X, that boots and I can install apps via HiSuite. Nevertheless I have no idea how to deal with Gapps. If I install opengapps, I will not be able to register an account - just hangs for a long period and then comes back (are there any logs written on the device to analyze a bit deeper?). Gapps without an account maks no sense. So I tried it without opengapps but with installing play services via HiSuite, granting rights, rebooting twice, installing Playstore, granting rights, rebooting twice, but starting Playstore after this procedure just tells me, that gms has to be installed (which in fact is already).
Any hint?
- prep like described by SID21 including HiSuite-Installation
- optional: download Nova Launcher, Firefox and Total Commander from "apkmirror.com"
- boot into TWRP
- mount system r/w
- format data
- wipe all partitions besides external SD
- mount vendor
- install image VENDOR.IMG
- reboot to bootloader​- USB-connect to PC
- kill HiSuite in case it comes up
- Start MultiTools
- Click on "Unbrick" in upper list
- enter Path to prepared folder in grey field
- Validate: at least 4 checked boxes
- Click on Box labeled "Unbrick"
- Validate messages: "Completed", "All images are flashed successfully"
- Click "Recovery" in upper list
- in frame labeled "Flash custom Recovery/eRecovery":
- Click Button labelde "Select image" and navigate to file twrp_Honor_7x.img and select
- Click button "Flash Recovery"
- in Popup window select "Restart from fastboot" and unplug the phone from USB​- Stop Multitools
- Wait for first restart, phone comes up
- Adapt phone settings:
- Security & Privacy/Additional Settings:
- set "Unknown sources"
- set "Allow HiSuite to use HDB"​ - About phone:
- Click 7 times in a row on "Build number" to activate developer options​ - Developer options:
- Activate "USB debugging"
- optional: Activate "Allow ADB debugging in charge only mode"​ - WiFi:
- connect to your WiFi network​- USB-connect phone
- Phone popup: set "Allow access to device data?" to "Yes, allow access"
- Phone popup: set "Allow connection in HDB mode?" to "Yes, allow access"
- Phone popup: set "Allow USB debugging?" to "Ok"
- PC HiSuite Popup to inform about installation of services to manage device
- optional: PC HiSuite Apps:
- Install a proper Launcher (e.g. Nova Launcher) and make it the default launcher
- Install a proper file manager (e.g. Total Commander)
- install a browser (e.g. firefox)
- Download opengapps from opengapps.org and save to sd card​- USB-disconnect phone
- Restart phone into TWRP
- do not get access to system partition
- Mount: Validate: system is not mounted at all
- Advanced/Terminal:
- enter "ls -l /dev/block/platform/hi_mci.0/by-name/system"
- validate: the filesystem points to /dev/block/mmcblk0p44
- ONLY DO THE FOLLOWING IF YOU KNOW WHAT YOU ARE DOING!!!
- enter "resize2fs /dev/block/mmcblk0p44"
- Validate Message: The Filesystem is now 1200128 blocks long.
- enter "e2fsck /dev/block/mmcblk0p44"
- Validate message: system clean, ...​ - Mount:
- check "system"
- uncheck "Mount system partition read-only" and swype in next screen to get access to system
- check "system"​ - Install:
- Select storage: Micro SDCard
- install SuperSU (I've chosen 2.82)
- Wipe Cache/Dalvik​ - Reboot:
- reboot to system
- do not install TWRP app​- Reboot takes long time
- During boot animation another reboot occurs
- Boot animations gets finalized, phones comes up normally

Bricked Phone After Magisk Install

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!

[ANDROID 10]Galaxy A80 Root➕Unlock Bootloader➕Flash Official Firmware (13 March 2020)

WARNING: You can't downgrade anymore once you flashed U4/S4 March update !
https://samfrew.com/model/SM-A805F/
SM-A8050
SM-A805F
SM-A805N you can't unlock bootloader on this variant! (R1Q_KOR_SINGLE.pit)
You will need:
-Odin v3.14.1
https://dl2018.sammobile.com/Odin3-v3.14.1.zip
-Galaxy A80 Latest USB Driver
https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
You want to download latest firmware directly from server? (fast download)
Samfirm 0.4.1 or Frija 1.4.2
https://samfirmtool.com/samfirm-v0-4-1
https://github.com/wssyncmldm/frija/releases
Frija not working ? install both vcredist_x00 for your device !
(Check your windows settings to know which version to install).
(Microsoft Visual C++ 2010 Redistributable Package) and (Microsoft Visual C++ 2008 Redistributable Package)
-https://www.microsoft.com/en-US/download/details.aspx?id=29 (x86) 2008
-https://www.microsoft.com/en-US/download/details.aspx?id=5555 (x86) 2010
-https://www.microsoft.com/en-US/download/details.aspx?id=15336 (64bit) 2008
-https://www.microsoft.com/en-US/download/details.aspx?id=14632 (64bit) 2010
-Open Frija and type in your model (mine is SM-A805F) and your CSC : (mine is LUX).
(All CSC's and models on Samfrew: https://samfrew.com/model/SM-A805F/).
-Download and extract SM-A805XX_1_00000000000000_xxxxxxxxxx_fac.zip
On your device:
If you want to unlock bootloader:
-Go to Settings then to About phone and find your build number.
-Tap on your build number 6 times until you see “You’re now a developer”.
-Go in Developer options > enable OEM unlocking.
-Connect the device to your PC.
-Power off your device with POWER and volume DOWN and directly hold volume UP and DOWN together!
-Device will boot in DOWNLOAD MODE.
-Long press volume UP to unlock the bootloader. This will wipe your data and automatically reboot your device!
If you dont want to unlock bootloader:.
-Download and extract Odin and open it as administrator.
Still in DOWNLOAD MODE:
-Click on BL and select BL_A805FXXXU4AXXX_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT.tar.md5
-Click on AP and select AP_A805FXXXU4AXXX_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar.md5
-Click on CP and select CP_A805FXXXU4AXXX_CP14483800_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT.tar.md5
(If you want to keep your data don't flash CSC).
-Click on CSC and select CSC_OMC_OXM_A805FXOXM1AXXX_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT.tar.md5
-Click on USERDATA and select HOME_CSC_OMC_OXM_A805FXOXM1AXXX_CL16843479_QB27603640_REV00_user_low_ship_MULTI_CERT.tar.md5
-Click on START and wait for installation, when done you can unplug your device.
ROOT​Your KNOX status will be tripped if you follow this tutorial...​What's knox ? : https://www.google.com/search?q=samsung+knox+explained
-Download the latest stock firmware for your Samsung Galaxy A80 with Samfirm/Frija app (faster) or Samfrew/Sammobile website (way slower).
https://samfrew.com/model/SM-A805F/
-Extract the SM-A805XX_1_EXAMPLE_0000000000_fac.zip file with 7zip or any other unzipper.
-Copy the (AP_A805XXXXU1XXXX_CL00000000_QB00000000_REV00_user_low_ship_MULTI_CERT_meta_OS10.tar.md5) file and transfer it to your internal storage.
-Download and install Magisk Manager APK https://github.com/topjohnwu/Magisk/releases/download/manager-v7.5.1/MagiskManager-v7.5.1.apk
-Open Magisk Manager and go to Install > Install > Select and Patch a file.
-Navigate through the storage and select the extracted AP file.
The firmware will be patched and will be found in Internal Storage/Download/magisk_patched.tar.
-Transfer the patched file to your PC.
-Turn OFF your device and boot into DOWNLOAD MODE.
-In Odin, click on AP and select the patched tar file, Uncheck “Auto Reboot” and click on Install.
The tool will flash Magisk V20 on your Samsung Galaxy A80.
To boot in recovery or boot the system with Magisk installed:
1. Powering up normally → System without Magisk
2. Power + Volume Up → Bootloader warning → Release all buttons → System with Magisk
3. Power + Volume Up → Bootloader warning → Keep holding volume up → Actual recovery

My storage was reduced from 128gb to 32gb after doing this. Is there a fix?

any improvement..? could anyone confirm thats this way work corectly
edited: i hv tried still on unlock bootloader without root capability.. unfortunately there's not suitable magisk work on this device whatever try to patched method but still null
damn samsung device i hv ever owned

haanz85 said:
any improvement..? could anyone confirm thats this way work corectly
edited: i hv tried still on unlock bootloader without root capability.. unfortunately there's not suitable magisk work on this device whatever try to patched method but still null
damn samsung device i hv ever owned
Click to expand...
Click to collapse
Just fixed mine by doing the bootloader unlock and root steps above,
setup the phone without Google but with debug mode enabled,
flash twrp,
format data (the one that makes you type yes),
setup the phone with Google and debug mode, then
reflash the firmware with Odin (stock BL, magisk_patched AP, stock CP, and HOME_CSC).
Now I have 108gb storage with root! I just have to hold volume up+power button every time I boot, though.

Nazato said:
Just fixed mine by doing the bootloader unlock and root steps above,
setup the phone without Google but with debug mode enabled,
flash twrp,
format data (the one that makes you type yes),
setup the phone with Google and debug mode, then
reflash the firmware with Odin (stock BL, magisk_patched AP, stock CP, and HOME_CSC).
Now I have 108gb storage with root! I just have to hold volume up+power button every time I boot, though.
Click to expand...
Click to collapse
what version twrp u used? doesn't you have problems in reading internal storage or USB MTP/ connect pc? Does all run normally? please gv link the worked twrp if u have..

Could you please be more detailed in this steps?? I got this problems too. plz help.

hosheaxu said:
Could you please be more detailed in this steps?? I got this problems too. plz help.
Click to expand...
Click to collapse
read carefully every step bro. after flashing magisk patched then setup phone from beginning without setup google acount just skip, then check again by activating developer menu & usb debugging on. at the end reset from about menu..then phone's should reboot, after that install magisk manager then follow until finished process. & now after reboot u already got rooted beloved phone . congrats

haanz85 said:
what version twrp u used? doesn't you have problems in reading internal storage or USB MTP/ connect pc? Does all run normally? please gv link the worked twrp if u have..
Click to expand...
Click to collapse
Only the latest version from blackbuga, and yes, I can't access my internal storage through USB when in twrp. It doesn't bother me that much, because I only needed twrp to format the data so the storage goes back to 108gb from 32gb. Everything's been running fine so far.

Nazato said:
Only the latest version from blackbuga, and yes, I can't access my internal storage through USB when in twrp. It doesn't bother me that much, because I only needed twrp to format the data so the storage goes back to 108gb from 32gb. Everything's been running fine so far.
Click to expand...
Click to collapse
but why u need twrp just for get normal storage.. while my storage going fine without twrp & i just try reset in finalizing process then install magisk at the end & everything looks good.
right now I'm just curious why there's no more dev interest in working on custom recovery & roms which is in other hand there's plenty developer working on galaxy s series with snapdragon soc with great support for official/unofficial builds whether twrp or cust roms. so sad considering the device is quite a potential to be developed

haanz85 said:
but why u need twrp just for get normal storage.. while my storage going fine without twrp & i just try reset in finalizing process then install magisk at the end & everything looks good.
right now I'm just curious why there's no more dev interest in working on custom recovery & roms which is in other hand there's plenty developer working on galaxy s series with snapdragon soc with great support for official/unofficial builds whether twrp or cust roms. so sad considering the device is quite a potential to be developed
Click to expand...
Click to collapse
I just followed op's instructions in his A70 topic lol I get you. I came from iOS and I was really excited when I got the phone, but after seeing the development scene... I don't know, maybe it just has something to do with the phone's price being expensive and all that.

Nazato said:
I just followed op's instructions in his A70 topic lol I get you. I came from iOS and I was really excited when I got the phone, but after seeing the development scene... I don't know, maybe it just has something to do with the phone's price being expensive and all that.
Click to expand...
Click to collapse
yeah it's possible for sensitive pricing from first launching. in my country first launching price going around $705 then after few month until approaching new device release info to be released in February. on new years then the price going down until just left $549,50 then i decided to bought it :victory:
maybe many people's thinking like me, wait & see before grab this phone's :laugh:

Nazato said:
I don't know, maybe it just has something to do with the phone's price being expensive and all that.
Click to expand...
Click to collapse
.
Actually, the truth is something else and the price range is not relevant at all.
If you have A series, it is low price range of Sammy phones and if you owned previously Iphone, you jumped "from horse to donkey".
Here you can find android ultra expensive devices successfuly rooted and in everyday ongoing development.
As pricey device is, more support you have ( All S,S+ and Note series, for example).
I have very expensive Galaxy Fold device...successfully rooted with regulary ongoing development, therefore, price is not relevant at all.
There on IOS is missing crucial users inteligence, knowledge and developers on IOS users market.
Simply said...they don't have and don't need developer oriented users and no quality devices to be upgraded or "pushed" further more.
Also...IOS is CLOSED SOURCE system not opened for free development because Apple can't make profit of that.

tin2404 said:
.
Actually, the truth is something else and the price range is not relevant at all.
If you have A series, it is low price range of Sammy phones and if you owned previously Iphone, you jumped "from horse to donkey".
Here you can find android ultra expensive devices successfuly rooted and in everyday ongoing development.
As pricey device is, more support you have ( All S,S+ and Note series, for example).
I have very expensive Galaxy Fold device...successfully rooted with regulary ongoing development, therefore, price is not relevant at all.
There on IOS is missing crucial users inteligence, knowledge and developers on IOS users market.
Simply said...they don't have and don't need developer oriented users and no quality devices to be upgraded or "pushed" further more.
Also...IOS is CLOSED SOURCE system not opened for free development because Apple can't make profit of that.
Click to expand...
Click to collapse
but what about this device? are u still make exception from regular ongoing development.. until now there's no famous developer that saw it for builds known roms out there although this doll already succesfully rooted, but none of them build us twrp with fully support & maybe one or two working cust roms

Android 10 is released.
https://samfrew.com/model/SM-A805F/
A805FXXU4BTC3

BK said:
Android 10 is released.
https://samfrew.com/model/SM-A805F/
A805FXXU4BTC3
Click to expand...
Click to collapse
Is This only for france devices?

android 10
Thanks for your help..
i want ask we can do the root and TWRP recovery for android 10 i wanna update my phone but dont know if its ok or not i need the root and dont want lose it
can you help please if its ok or not ???
thanks

uae.coool said:
Thanks for your help..
i want ask we can do the root and TWRP recovery for android 10 i wanna update my phone but dont know if its ok or not i need the root and dont want lose it
can you help please if its ok or not ???
thanks
Click to expand...
Click to collapse
go right ahead I'm rooted on Android 10 right now just follow the instructions again

i rooted all went ok but when i transfer my all data i find out no root and i tried to install TWRP but i really cand do this and every time fall
please help

uae.coool said:
i rooted all went ok but when i transfer my all data i find out no root and i tried to install TWRP but i really cand do this and every time fall
please help
Click to expand...
Click to collapse
just flash everything again (magisk patched AP) with HOME_CSC. DON'T WIPE

Nazato said:
just flash everything again (magisk patched AP) with HOME_CSC. DON'T WIPE
Click to expand...
Click to collapse
ok thanks will try it now
other things is losing the memory showing 32gb after the root and when wipe no root ???
and one more things please how to install TWRP i tried many time but stack in the samaung logo ???
thanks again

[GUIDE] LineageOS 17.1 ROM for Galaxy A50 Android 10 Q

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.

Nexus 7 (2013) unlocked with custom recovery but with dead usb - how to flash or root at least?

Need help, folks:
my old Nexus7/2013 has dead USB port but long time ago I unlocked boot and flashed teamwin recovery 3.2.1.0
Problem: at this moment it has Marshmallow 6.0.1 (MOB30X) which is NOT rooted...
Is it possible - without adb / without connection to PC since USB port is dead - to flash it with old kitkat 4.4.4 (preferred) , or at least how to root it's current marshmallow 6.0.1?
/my original post had been edited for clarity

Nexus7-2013 said:
Need help, folks: my old Nexus7/2013 has dead USB port but long time ago I unlocked boot and flashed teamwin recovery 3.2.1.0 Problem: at this moment it has Marshmallow 6.0.1 (MOB30X) which is NOT rooted... Is it possible - without adb / without connection to PC since USB port is dead - to flash it with old kitkat 4.4.4 (preferred) , or at least how to root it's current marshmallow 6.0.1? /my original post had been edited for clarity
Click to expand...
Click to collapse
To root it is very simple, get Magisk, save it into the SDCARD folder, boot TWRP and install it. That's all.
Better yet, fix the damn USB port, it takes only a few minutes, then you can proceed as usual - https://forum.xda-developers.com/t/...r-request-failed.3493322/page-2#post-83468773

k23m said:
To root it is very simple, get Magisk, save it into the SDCARD folder, boot TWRP and install it. That's all.
Better yet, fix the damn USB port, it takes only a few minutes, then you can proceed as usual - https://forum.xda-developers.com/t/...r-request-failed.3493322/page-2#post-83468773
Click to expand...
Click to collapse
First of all, thank you for replying.
Yes I have tried latest Magisk 20.4, it starts and all good until this part:
...
- Checking ramdisk status
! Boot image patched by unsupported programs
! Please restore back to stock boot image
- Unmounting partititions
Update process ended with ERROR.... blah blah blah
Click to expand...
Click to collapse
Well, it is partially correctly beaching because previously I did have tried rooting with some outdated versions of supersu and magisk too, before I realized they're damn old (it was very late at night)
So, what's your suggestion in this case?
Oh, and for fixing USB port I will do it eventually, no problems here soldering anything, but i'm really not good with prying plastic covers... To cut it short, I already destroyed 2 covers and 1 screen on a nexus 6p and on another similarly held-by-glue-and-spit poorly designed device in the past when I was trying to open them. If it isn't hold together by screws I rather don't do it, at least not until I would really have to. Since this tablet is still working fine and is very useful for reading books or watching videos in bed before sleep, the only hardware-wise inconvenience is using damn wireless charger.
Yes, I am planning to fix USB port (and yes again - by resoldering whatever pins broke out there, and not by swapping entire usb daughter-board) but I want to do it when tablet's battery will start to give up too. That's when I will have no other choice but to open it up... But right now battery still gets 4-5hrs SoT, which is more than enough for me.

Nexus7-2013 said:
...I did have tried rooting with some outdated versions of supersu and magisk too, before I realized they're damn old (it was very late at night) So, what's your suggestion in this case?
....similarly held-by-glue-and-spit poorly designed device in the past when I was trying to open them. If it isn't hold together by screws I rather don't do it
Click to expand...
Click to collapse
I suggest to reflash the boot image. Get mob30x and unpack it completely to access this file:
Restock2\data\razor-mob30x\image-razor-mob30x.zip\boot.img
If the unpacking was done on a PC then transfer the boot.img to N7 via WiFi first.
Next boot TWRP, in the Install function switch to image mode and flash boot.img.
As for N7 disassembly, there is no glue involved, easy.

k23m said:
I suggest to reflash the boot image. Get mob30x and unpack it completely to access this file:
Restock2\data\razor-mob30x\image-razor-mob30x.zip\boot.img
If the unpacking was done on a PC then transfer the boot.img to N7 via WiFi first.
Next boot TWRP, in the Install function switch to image mode and flash boot.img.
Click to expand...
Click to collapse
I didn't realized you're the same person who posted "restock" (your path to img file ticked me off) that I read about in another thread! Thank you very much for making it and sharing it, though I can't use it yet obviously, but I have found in restock thread your mob30x-fix zip, which I have used on my N7 - just FYI it worked great and cleared all the old Goo junk apps when I tried it. Very useful tool. Thank you!
(also: leaving old Google Music app was excellent choice since it is useful for local files; and making skip button active on initial wifi setup screen is really very nice touch! You have no idea how many times I cursed damn Goo devs for greying out this option)
OK, mob30x image downloaded from Goo (terrible - they removed all the previous kitkat and lollipop images!), boot.img extracted and installed, rebooted, installed Magisk 20.4 . All went flawlessly.
So I guess - with your help - I have rooted mob30x without adb
Thank you again!
(root confirmed - i just installed my fav Android Firewall and it was granted superuser access - woo hoo! Now I can block ipv6 connections too)
Now, what about flashing kitkat on this tablet without usb port ... ?

Nexus7-2013 said:
Now, what about flashing kitkat on this tablet without usb port ... ?
Click to expand...
Click to collapse
It seems doable but I have not fully tested it. If you make a mistake you may be finally forced to fix the port ...
This method will not work with Android 5+:
- get razor-ktu84p-factory-2482a7d5.zip and extract boot.img and system.img to /sdcard/
- copy the attached android4-system-flash.zip to /sdcard/
- boot TWRP, do Wipe and flash the boot.img as usual
- in TWRP install android4-system-flash.zip which I estimate would take around 70 minutes
The image needs to be processed on the fly. It was so slow, I gave up and only did a partial flash...
Code:
dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system ibs=1 obs=4M skip=40 count=10M
10485760+0 records in
2+1 records out
10485760 bytes (10.0MB) copied, 57.214905 seconds, 179.0KB/s
We need to remove 40 bytes from the beginning of system.img. The existing dd function has a subset of features and a faster option is not available. You could mod the image on PC and flash it much faster with an altered install zip:
dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system bs=4M
Cheers!
EDIT
I have noticed a filesystem error with this method but there is another way. PM me if you really need it.