Develop Bugs

Stuck at 7.5.1.0

I have a Chinese max, 32gb. It’s currently on miui 7.5.1.0 stable. When I click check for updates it says no updates available. I’m in china if that makes any difference.
How can I upgrade to a newer software? Can I change to global rom?
I don’t have a windows computer and most guides seems to require windows. Also I don't want a custom rom.
Alternatively, how can I get native update function the to work?
Thanks for help to push mein the right direction.

Screenshot of about phone?
Sent from my Xiaomi MI MAX using XDA Labs

here is the screenshot

nick5000 said:
I have a Chinese max, 32gb. It’s currently on miui 7.5.1.0 stable. When I click check for updates it says no updates available. I’m in china if that makes any difference.
How can I upgrade to a newer software? Can I change to global rom?
I don’t have a windows computer and most guides seems to require windows. Also I don't want a custom rom.
Alternatively, how can I get native update function the to work?
Thanks for help to push mein the right direction.
Click to expand...
Click to collapse
Well, without a pc you have less options, users of miui are on nougat (beta) but in your case must be sure of these things; download (easier) an app from playstore about developer options, open and check at USB debugging, allow, now download a global version from official Miui page for Hydrogen (device name) must be in .zip format and try going to /settings/about device/system update you`ll see four dots upper right and option "select update package", navigate to your downloaded file and try to flash

Thanks. So I downloaded it, went to updater and chose the file, and it says couldn't verify update package.
Tried to download to recovery mode, but then I just get to a screen with the symbol to connect USB cable to computer.

nick5000 said:
Thanks. So I downloaded it, went to updater and chose the file, and it says couldn't verify update package.
Tried to download to recovery mode, but then I just get to a screen with the symbol to connect USB cable to computer.
Click to expand...
Click to collapse
If from this option doesn`t flash your zip either do from mi recovery. Version for China probably is from a phone company if you live there. You need a pc at least to install TWRP (it takes two minutes) and from here you must install last version official beta v8 7.1.19 but you need unlock bootloader

So this is not possible to do with a MAC? what about the terminal commands, can I install a rom from the CLI ?

nick5000 said:
So this is not possible to do with a MAC? what about the terminal commands, can I install a rom from the CLI ?
Click to expand...
Click to collapse
I know this isn't the quickest workaround, but if you're stuck on a Mac you can always bootcamp it for free. Just download Windows 10 (around a 5GB download I think) and install via bootcamp. You don't need a serial to officially install or run WIndows 10 and you can just remove the installation when you're finished.

nick5000 said:
So this is not possible to do with a MAC? what about the terminal commands, can I install a rom from the CLI ?
Click to expand...
Click to collapse
You can use other advance phone (cause this will be busy) like a viewfinder of .img in your computer, with an app from Play Store called DriveDroid, you place some .img in your sdcard and to arrange computer select usb (it`s like a virtual machine) or burn an image in a usb with a linux distro, here is a rescue cd that contain a virtual Windows XP called Hiren`s Boot (500 mb aprox.) but really I don`t know if all that works on a mac.
First read that post, it seems is possible use fastboot on a mac according that: http://htc-one.gadgethacks.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/

SubwayChamp said:
You can use other advance phone (cause this will be busy) like a viewfinder of .img in your computer, with an app from Play Store called DriveDroid, you place some .img in your sdcard and to arrange computer select usb (it`s like a virtual machine) or burn an image in a usb with a linux distro, here is a rescue cd that contain a virtual Windows XP called Hiren`s Boot (500 mb aprox.) but really I don`t know if all that works on a mac.
First read that post, it seems is possible use fastboot on a mac according that: http://htc-one.gadgethacks.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
Click to expand...
Click to collapse
I tried using fastboot commands on mac to to update, but didn't work.
I guess I'll have to stick with 7.5.10 until I get a new phone.
However wonder why the OTA update doesn't work.

nick5000 said:
I tried using fastboot commands on mac to to update, but didn't work.
I guess I'll have to stick with 7.5.10 until I get a new phone.
However wonder why the OTA update doesn't work.
Click to expand...
Click to collapse
What did you type in fastboot?, zip version is not for fastboot, must be download correct version, but go for the first step, probably you must
unlock bootloader, request to xiaomi, sometimes you got it in 6 hours, depends, probably device is rooted, for this reason don't update ota. Here you have other thread to apply fastboot with other method https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755

tried both the flash all except storage.sh and the flashboot flash system commands. it said device it locked. I applied to unlock bootloader, no reply yet, but does that also require a Windows program to unlock the bootloader?
Device is not rooted, but I installed google play, maybe that's what broke the OTA

nick5000 said:
tried both the flash all except storage.sh and the flashboot flash system commands. it said device it locked. I applied to unlock bootloader, no reply yet, but does that also require a Windows program to unlock the bootloader?
Device is not rooted, but I installed google play, maybe that's what broke the OTA
Click to expand...
Click to collapse
No, Google Play can't do that. In my little corner of the world we say "all the roads lead to Rome", I think you need a pc, There is other shorter way of two steps root first with a pc and then download from Google Play an app called "flashfire" you may flash a zip rom from this app. Also you may use a virtual cd or usb with a linux distro like ubuntu or debian running on your mac to arrange computer like a live cd or usb without install on your mac or if you prefer install it on your mac, there's a world of options just root device and can flash any you want and be the real owner of your phone

google pixel xl wont update to android 8.0

hello - ive got a google pixel xl on android 7.1.2 i can see from the system update that i can update to Android oreo 8.0, when i click to "download and install" it downloads the 950.7MB file, starts to install , but then stops with message "coouldnt update - installation problem"..any ideas ? ta

goofy gorilla said:
hello - ive got a google pixel xl on android 7.1.2 i can see from the system update that i can update to Android oreo 8.0, when i click to "download and install" it downloads the 950.7MB file, starts to install , but then stops with message "coouldnt update - installation problem"..any ideas ? ta
Click to expand...
Click to collapse
Is your storage near full?

sliding_billy said:
Is your storage near full?
Click to expand...
Click to collapse
no mate...i have nothing on my phone as i recently got it...its about 23GB free

goofy gorilla said:
no mate...i have nothing on my phone as i recently got it...its about 23GB free
Click to expand...
Click to collapse
Sounds like the download is getting a corrupted file. I would either DL and install the factory image (if BL unlocked) with the -w removed from the flashall file or sideload the OTA (if not unlocked).

sorry mate - im not that techy but knowing me ill probaly brick my phone..what is bl, and -w ????? ...sorry not techy

https://developers.google.com/android/images
Straight from the source with detailed instructions.

Since he is not unlocked, he should sideload the full OTA from here
https://developers.google.com/android/ota

I would recommend a full system install given that you purchased the phone from someone. Wouldn't want anything malicious on the phone that the previous owner might have left in.

yes i would do that but not very techy, its still under warranty for another 15 days i think as i have the receipt, but the back glass is cracked , hence google say warranty is void..seems to reboot all by itself and sometimes just switches off..

richii0207 said:
I would recommend a full system install given that you purchased the phone from someone. Wouldn't want anything malicious on the phone that the previous owner might have left in.
Click to expand...
Click to collapse
i would do that but i dont have a clue as to where and how to do this ?

ok found this site to reflash to factory settings..HERE
ive downloaded the files but dont understand where to put the files, the instructions are below but not sure what they mean..it says "computer’s system partition" ???..is that drive C ?
where do i put the image that ive downloaded...into the folder called " Platform-tools folder"
what about the google usb drivers ?....do i put the actual usb folder or its contents into the "platform-tools folder"?
its confusing ..
what do they mean by this "Go to Platform-tools folder. Here you need to launch a Command Prompt / Terminal window with administrative rights."
how do i do that ?
Here’s how to do it:
Download the Platform-Tools zip corresponding to your computer’s operating system:
– for Windows PC click here.
– for Mac OS click here.
– for Linux click here.
unzip the file after the download is complete.
you will obtain the Platform-Tools files, save them all on your computer’s system partition.
– make sure to leave the Platform-Tools name as the default folder name.
next, download the Google USB drivers from here.
Next you can continue to the tutorial and learn how to flash a factory image for your device.
How to install Android 7.1.2 Factory Image for Google Pixel XL:
Download the Android 7.1.2 Nougat factory image file from here.
Extract the archived contents and save them on your PC.
Place all the extracted files in the Platform-tools folder.
– that’s the folder obtained using the steps above the tutorial.

well..somehow it managed to update to android oreo 8.0......after trying all day, will see how the phone performs...its rebooted byitself once already, dont know if that was because it was installling something but update has been done....still think this phone has some hardware problem as the screen froze when i was entering my google play details.....weird phone...

NOST - Improved Version of OST LA 6.0.4 (v0.6, 02. Mar 2019)

"NOST" - short for "No Service Tool" (or "Nokia Service Tool" but that sounds too official and boring ) is a small hobby project I've been working on in the last couple of days.
It aims to make the service tool for Nokia 8 (and HMD Phones in general) more useable, user-friendly, and straigtforward to use, and after having to test it myself, and also
making a small beta test in the Telegram group for Nokia 8, I feel like posting it here so others can try it out too if they want.
First, to be clear: NOST is not completely my work. It is based on OST LA 6.0.4, which was made by HMD/Foxconn. Unlike the previous OST Patches, NOST does not replace
the executable with a hacked one, but instead wraps it and patches the methods that need patching at runtime. The result is that the changes are completely opensource
and readable by others, while the underlying OST files are not modified at all. I tried to base it on a different (i.e. newer) version of OST, but those are pretty much unpatchable,
at least not with a serious amount of reverse engineering, which brings not only time issues but legal ones as well.
NOST changes a couple of things, compared to the unmodified OST LA:
It removes the need for authentification against HMD/FIH servers (really, shoutout to the one who made the original hack, even though I could not use their code)
Moved the logs folder to the same folder as the application, as opposed to somewhere on the system to make debugging easier
The options for flashing firmware images appear reliable now. (At least for me they only appeared sometimes if not never on the original OST).
Removed one of the options that if it appeared crashed the flashing process ("Check System AP Status")
One user of the Telegram group had issues where OST would crash because it detects an invalid locale setting in Windows. NOST just catches that issue and defaults to english
Removed the "Edit Phone Information" button. It never worked and it's only purpose was to make the "Next" button appear, which works like it should now as well.
NOST refuses to flash your phone if your bootloader isn't unlocked critically. The old OST would just try to flash but never make any progress which confuses inexperienced users.
Perhaps the most important change: NOST allows to flash modified firmware images without the need to extract and modify them by hand.
With the original OST, people who wanted to reflash their phone had to download a firmware bundle, extract and edit it to be able to use it with OST LA 6.0.4, since the newer versions
had unpatchable issues that prevent using them. Repacking the images in a format OST expects wasn't possible either since that enabled some sort of signature algorithm on the modified
images and caused the flashing to fail. NOST solves this problem by allowing the use of a different packaging format. Those binaries still need to be extracted but it is done transparently in
the background without the user having to download any other tools. The formats that can be used in images are .zip and .qlz
.zip Firmwares:
.zip firmware files are simply archives of the (edited) files that would normally be extracted from an .nb0 file. This means, if you extract a .nb0 with the extractor found on XDA, the contents
of the *_unpacked folder it creates should be the contents of your .zip.
.qlz Firmwares:
.qlz files are based on QuickLZ compression, which gives them a small size but also a low decompression time.
The tool to generate them is called exdupe. Generating these images is pretty straigtforward. Assuming you are on windows, download the exdupe
tool from the link above (or take it from the NOST Tools/ folder) and copy it into the folder that contains the unpacked .nb0.
Code:
- exdupe.exe
- <nb0 name>_unpacked/
- <nb0 name>.mlf
- ....
Open a commandline in that folder, and run the following command:
Code:
exdupe.exe <name of the folder to compress> <name of the firmware file>.qlz
You should already see how fast it compresses the firmware folder now. As a reference: Compressing the latest Nokia 8 firmware (about 4GB) takes maybe 30 seconds and yields a 2GB file.
Repacked Firmware Bundles:
I created .qlz images of the May and November firmwares, as well as one of the various Pie Maintainance Releases.
You can find them here: https://tmsp.io/fs/xda/nb1/firmware
I already successfully reverted from December Security Patch to November using NOST, and then updated back using OTA Sideloading without problems.
As always when working with flashing tools, proceed with caution!
How to unlock to critical:
KonikoO said:
For those who wonder how to unlock into critical state :
Reboot into bootloader download mode and execute those commands :
fastboot flash unlock *unlock .bin*
fastboot flashing unlock_critical
Afterwards you should be able to flash provided .qlz with NOST.
Click to expand...
Click to collapse
Download:
The actual tool: https://github.com/StollD/NOST/releases
Drivers: https://github.com/StollD/nokia-driver-installer/tree/master/out
Source Code: https://github.com/StollD/NOST
License:
OST LA 6.0.4 is copyrighted by the respective authors. It is not modified permanently.
The custom NOST code is licensed under the GNU General Public License.
Icon by Freepik © Flaticon

I tried this is working,nice tool.
Thanks dev.

Thank you THMSP! very cool?
Sent from my TA-1004 using XDA Labs

Can flash the May and November update but cannot flash latest Pie with this tool. I flashed Pie but returned back to November update?

Lee Castro said:
Can flash the May and November update but cannot flash latest Pie with this tool. I flashed Pie but returned back to November update?
Click to expand...
Click to collapse
Yes, you can revert back from Pie to Oreo using this. What is the issue with Pie for you?

THMSP said:
Yes, you can revert back from Pie to Oreo using this. What is the issue with Pie for you?
Click to expand...
Click to collapse
What I mean is if I flash the Pie file you provided I just returned back to Android 8.1 Novemeber update no changes at all. Maybe there something wrong with the Pie file you uploaded. But the rests are all working fine with the tool.

Lee Castro said:
What I mean is if I flash the Pie file you provided I just returned back to Android 8.1 Novemeber update no changes at all. Maybe there something wrong with the Pie file you uploaded. But the rests are all working fine with the tool.
Click to expand...
Click to collapse
Thanks for the hint, I will take a look. Probably just derped when pulling partitions and renaming the images (might have worked in my November folder by accident).
EDIT: I repulled the images from Pie (I indeed somehow worked in my November folder when making the image), repackaged them and updated the version in the drive folder. You should now be able to flash Pie. Sorry for the mistake.

THMSP said:
Thanks for the hint, I will take a look. Probably just derped when pulling partitions and renaming the images (might have worked in my November folder by accident).
EDIT: I repulled the images from Pie (I indeed somehow worked in my November folder when making the image), repackaged them and updated the version in the drive folder. You should now be able to flash Pie. Sorry for the mistake.
Click to expand...
Click to collapse
Thanks again,This is really a big help.

Wow, this is something we've been all seeking for a long time now ! For those who wonder how to unlock into critical state :
Reboot into bootloader download mode and execute those commands :
fastboot flash unlock *unlock .bin*
fastboot flashing unlock_critical
Afterwards you should be able to flash provided .qlz with NOST.

hey there! wonderful tool to have. Thank u so much

Not working in my laptop say a software need a to update

Blackhacker07 said:
Not working in my laptop say a software need a to update
Click to expand...
Click to collapse
If you have dependency issues I would suggest to install OST LA 6.0.4 first, so you get its dependencies, until I can make a proper installer for NOST.

THMSP said:
If you have dependency issues I would suggest to install OST LA 6.0.4 first, so you get its dependencies, until I can make a proper installer for NOST.
Click to expand...
Click to collapse
Could you perhaps figure out how to get rid of the unlocked bootloader message?

ironman38102 said:
Could you perhaps figure out how to get rid of the unlocked bootloader message?
Click to expand...
Click to collapse
Are you talking about the error message that appears when you press the Next button to start flashing?
If yes, your bootloader needs to be unlocked to critical, then the message won't appear.
If you are unsure if your bootloader is unlocked to critical, do "fastboot oem device-info", it will tell you.
If you mean the message that your phone displays when booting with an unlocked bootloader then sorry, I doubt that's possible (I think it is embedded into the bootloader).

THMSP said:
Are you talking about the error message that appears when you press the Next button to start flashing?
If yes, your bootloader needs to be unlocked to critical, then the message won't appear.
If you are unsure if your bootloader is unlocked to critical, do "fastboot oem device-info", it will tell you.
If you mean the message that your phone displays when booting with an unlocked bootloader then sorry, I doubt that's possible (I think it is embedded into the bootloader).
Click to expand...
Click to collapse
Actually its in splash.img that can be dumped. Its the hex editing possibly that might be a problem for someone not familiar with it

How to flash it's says this...

Blackhacker07 said:
How to flash it's says this...
Click to expand...
Click to collapse
What do you mean?

KonikoO said:
Wow, this is something we've been all seeking for a long time now ! For those who wonder how to unlock into critical state :
Reboot into bootloader download mode and execute those commands :
fastboot flash unlock *unlock .bin*
fastboot flashing unlock_critical
Afterwards you should be able to flash provided .qlz with NOST.
Click to expand...
Click to collapse
Thank you so much for this advice. I wouldn't have ever figured out how to unlock critical on my own and that was the thing that was preventing me from flashing. I tried searching the other OST LA flashing threads as well but this info seemed to have been missing, or then i completely missed it. Thank you so much anyways. If anybody else is trying to figure out why their OST LA or NOST is giving them the se_err_adb_cmd_get_fail_result error, this should help. I just used the unlock.key in place of the *unlock.bin* in your command and it worked.

Can you please upload Oreo December update stock and patched boot image. TIA

Yesterday I noticed that my Pie Image was still not quite useable, since it contained a corrupted system partition.
This seems to have happened because of my Magisk Setup and me only replacing the boot partition image and not uninstalling Magisk completely.
I rebuilt the image, to be fully stock, and also included the latest B07 update that @hikari_calyx uploaded yesterday. You can get it from the drive link in the OP.

[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.

Teclast M40 Pro Discoveries

Teclast M40 Pro Discoveries​Various helpful points of knowledge to unlock your bootloader, to root, and use your tablet.
Problem: Where can I obtain the official firmware?
Solution: Teclast Website
Usage: type M1A3 in search
Problem How can I unpack "pac" files?
Solution: Build C utility divinebird / pacextractor
Solution: Download pre built Linux executable pacextractor.zip
Usage: >./pacextractor Firmware.pac
Bash:
git clone https://github.com/divinebird/pacextractor
cd pacextractor
make
Problem: I need tools to flash my device
Solution: Download the latest SPD Upgrade Flash Tool SPD_Upgrade_Tool
Problem: msvcr100.dll missing error in Windows whilst running SPD (Factory/Research/Upgrade) Tools
Solution: Download and install 2010 Visual C++ Distribution
Problem: I want to unlock my bootloader. (Window and Linux kit)
Solution: Download TeclastM40Pro_Unisoc_UnlockTools.zip
Usage: Read readme file.
Problem: How can I remove the dm_verify warning on boot up after unlocking the bootloader?
Untested Solution: digitally sign the vbmeta partition and write it back. See [Tutorial] How to create a custom signed vbmeta.img
Problem: I want to root my device.
Solution: Modify boot.img with Magisk, then sign.
Usage: Upload to your device's download directory, the current boot.img read from your device, or from the same version firmware. Then install Magisk app from here. Use Magisk to patch the boot.img. Sign the partition. Then flash back the signed magisk version of boot.img to "boot_a" partition. Guide to flashing single partition at Hovatek Website
Problem: I need to emergency flash my device?
Solution: Currently only from Windows, use SPD Upgrade Tools to reflash firmware.
Usage: From the tablet powered off, or if boot looping. Hold down the power-button and volume-down for five seconds, release the power-button, and keep the volume-down button still held for another five seconds, then release or release if the detected earlier. Windows and SPD tools should then detect your device to flash.
Problem: I want to improve my Telcast M40 Pro
Solution: List of suggested apps below;
FDroid App Store F-Droid Website
Aurora > via FDroid. App store allowing the direct download from Google Playstore, without your own account.
Lawnchair > via FDroid. Fast open source sophisticated launcher.
AdAway > via FDroid. Removes adverts whilst using apps.
TrackerControl > via FDroid. Manages apps access to internet, and blocks spyware and trackers.
.

Problem: I want root mode without the effort of hacking a rom partition.
Solution: For those with World version Teclast M40 Pro device, here is a signed rooted boot partition I created. Read the readme file inside the zip. You will require an unlocked device, windows setup with USB drivers for Teclast, the complete firmware from Teclast website, and SPD Update Tools installed. If you're successful, then on rooting you will need to install Magisk app to get root active. Magisk will reboot once to finalise.
Download : TeclastM40Pro_ROW__v1p0_signedboot_magiskrooted.zip
Download : TeclastM40Pro_ROW__v1p2_signedboot_magiskrooted.zip

SPD Upgrade Tools is closing while trying to flash stock firmware, both with M40 Pro locked and unlocked bootloader. What should i do?

laurorual said:
SPD Upgrade Tools is closing while trying to flash stock firmware, both with M40 Pro locked and unlocked bootloader. What should i do?
Click to expand...
Click to collapse
Sorry for replying late. I got no indication of the response. To the problem, I can only suggest getting a different version of SPD or m aking sure your computer system is properly updated. I hope you've already solved the issue!
Maybe you're experiencing, "Problem: msvcr100.dll missing error in Windows whilst running SPD (Factory/Research/Upgrade) Tools" See above for solution.

I've noticed a new ROM for world edition, "M40 Pro(M1A3)_Android 11.0_ROW V1.02_20220525", but not getting any system update options for OTA. People flashing their systems may want the latest firmware!

Thanks to your Magisk file I was able to root my tablet, but when updating to the latest version it goes into bootloop, I have tried updating the original firmware image again, but it also goes into bootloop.
Is there any way to install Magisk modules?
Thanks for your post, it helped me a lot to unlock my tablet.
Edit: My version is the M1A1 firmware V1.03_20210804
Edit 2: Finally, when updating my tablet with the root file that is in the post, it did not allow me to install any Magisk module, the solution is to download version 24.3, and update automatically, without changing to a higher version of Magisk

Glad you worked it out Miny !!! Sorry the warning emails for new posts have been going to a gmail account I no longer use.
Also your hardware maybe different and require it's own unique firmware and boot images. It seems the cracking in similar though.

Some questions:
Do I need to unlock my bootloader in order to be able to get root with magisk?
The tools for unlocking the bootloader uses
Code:
fastboot flashing unlock_bootloader
. My version of fastboot (33.0.3p1-android-tools) doesn't have that command. The included one (0.0.0-09219) does, but I wan't to be careful about running softwar from untrusted sources. Where is that version of fastboot from?
Does any of the steps necessary to get root access delete my data?

Hi there.
I have a m40pro (M1A1) running android 11, do you know if I can install firmware Z3A1 to get android 12? Or will be bricked?
Thanks in advance

rubsbcn said:
I have a m40pro (M1A1) running android 11, do you know if I can install firmware Z3A1 to get android 12? Or will be bricked? Thanks in advance
Click to expand...
Click to collapse
To tell you the truth, not sure. Most SoC are impossible or near impossible to brick. They usually allow for an injection or have a read only boot section. Other words you could test. Also research difference in hardware between models, and that may indlicate if something may not work. The kernel/drivers are the improtant aspect.

jorkusjorkus said:
Some questions:
Do I need to unlock my bootloader in order to be able to get root with magisk?
The tools for unlocking the bootloader uses
Code:
fastboot flashing unlock_bootloader
. My version of fastboot (33.0.3p1-android-tools) doesn't have that command. The included one (0.0.0-09219) does, but I wan't to be careful about running softwar from untrusted sources. Where is that version of fastboot from?
Does any of the steps necessary to get root access delete my data?
Click to expand...
Click to collapse
What OS are you using? Google is constantly changing Android Studio and the added modules. Then others may build with options removed. Personally I use Archlinux and load up standalone android-tools from the community repository. Currently v33.0.3-3
Try fastboot --help
Your version may have
Code:
fastboot flashing unlock_critical

minyfriki said:
Thanks to your Magisk file I was able to root my tablet, but when updating to the latest version it goes into bootloop, I have tried updating the original firmware image again, but it also goes into bootloop.
Click to expand...
Click to collapse
What I found works, is when using SPD Research Tool, load up the firmware.pac and then go into settings and click "Select All Files" and again to unselect, which leaves the default required items.
Then manually change BOOT to the Magisk img. Then click on all VBMETA types, and UBOOT_LOADER (may not be required though). Then flash.
You should get bootable tablet (no looping). Warning: UserData partition is written over.
I'll share my Magisk image for v1.2

e8hffff said:
What OS are you using? Google is constantly changing Android Studio and the added modules. Then others may build with options removed. Personally I use Archlinux and load up standalone android-tools from the community repository. Currently v33.0.3-3
Try fastboot --help
Your version may have
Code:
fastboot flashing unlock_critical
Click to expand...
Click to collapse
I'm using the same version as you on the same OS. After some research it seems like unlock_bootloader was removed in this commit from 2018. From what I can tell, unlock_critical does something else (unlock_bootloader runs
Code:
fb_queue_download("unlock_message", data, sz); fb_queue_command("flashing unlock_bootloader", "unlocking bootloader");
while unlock_critical runs
Code:
do_oem_command("flashing", "unlock_critical" and doesn't take the signature argument);
)
I'll see if I can compile the older version with the needed command.
What about my other questions?

Issue: Android not starting. I had the infinite restart when plugged in the usb. I tried to reload the installation package (succeeded), but didn't fixed the issue. Battery was not charging yet. When I started the Teclast M40 pro, the logo showed up, but the tablet turned off again.
Solution: I have disassembled the cover, unplugged the 5 pin plug from the battery for half hour and plugged again. When I tried to turn it on, everything was fine.

dougcwb said:
Solution: I have disassembled the cover, unplugged the 5 pin plug from the battery for half hour and plugged again. When I tried to turn it on, everything was fine.
Click to expand...
Click to collapse
Wow that's weird Doug. Remember this, if you don't already know, that you can do a cold start by holding down the power button for over 10 seconds, on most devices.
I guess you're running now on rooted tablet !!!

e8hffff said:
Wow that's weird Doug. Remember this, if you don't already know, that you can do a cold start by holding down the power button for over 10 seconds, on most devices.
I guess you're running now on rooted tablet !!!
Click to expand...
Click to collapse
I did the installation package process that the Teclast sent me. The last thing they told me to do was keep trying to install the package (wft?). Well, I just open the tablet, unplugged the battery for a while and after that it worked.
Maybe this resolved 2 things:
1-the battery was not properly connected in the first place, so when I plugged the 5 pin to the board it connected as it should.
2- Maybe there is a "memory" in the board attached to the battery that was bricked (or something like that) when I pulled off the plug, this memory was reseted.
BTW, when the tablet came to life again, the battery was at 87%.