Develop Bugs

Stuck in bootloop after messing with framework-res.apk

I was in the process of replacing framework-res.apk and missed the step of changing the permissions before replacing it. I found several threads on how to unbrick the phone by flashing a new ROM but I was hoping I can somehow fix the permissions on the framework file and be done. I installed adb and I already had the LG USB drivers installed but when I run adb devices it doesn't list anything. Windows 7 shows "LG AndroidNet Phone" and a removable disk under "Safely Remove Hardware" so I think I have the right drivers.
Is there hope that I can fix the file permissions?
BTW, I'm a newb so I may be missing something. And also scared of having to flash a ROM
I need help.

do you have CWM in the phone ? if so boot into that and run adb devices and see if it finds it their

No, I don't. Other than using DooMLoRD zergrush to root the phone a few months ago, I have not messed with anything else.

gabcon73 said:
No, I don't. Other than using DooMLoRD zergrush to root the phone a few months ago, I have not messed with anything else.
Click to expand...
Click to collapse
unless your phone will boot normaly to the home screen or you have CWM on it you will haveto flash the koren rom theirs no way to get it into recovery that i know of ... have you tryed a factory reset ?

I replied to you at another thread, so I'll repeat here.
What you need to do is re-root while it's looping. It might take you 100 tries before it succeed , but eventually it should succeed.
After that you can try fix the permissions, but if the new .apk file is not copied successfully first time it might get you in boot loop again, so I'd recommend at that point push the .apk again and then change the permissions.
I found that zergrush dated 2011-10-21 has more chances to succeed, because it has more retries before it gives up, the new version tries only few times and gives up too quickly.
I've attached the root I was using with 3 versions of zergrush.
Open CMD window and execute root.bat, let it copy all needed files to the phone. If it fails, try execute loop.bat, it will just execute zergrush indefinitely , so you can go do other stuff. You can check if root succeeded by opening another CMD window and type: adb shell
then, if it shows sign "$" type su, if it shows "#" you are good to go.
P.S.
This method only works with AT$T stock rom, if you are on LU6200 you are probably out of luck, as their root requires wifi and user interaction...
Having CWM is very handy in such situations, not only because you can restore backups, but because you'll have root access.

Thanks [email protected], I'll give it a try. And yes, I have the stock ROM.
I'm having problems downloading root.zip, I've tried two computers and different browsers, it only downloads 554 bytes.

Yeah, for some reason it was downloading 404 page...
I reuploaded it.

I let the loop.bat run overnight without success so I decided to call AT&T and have it replaced under warranty. The new phone arrived today and I've been busy reinstalling and reconfiguring. I may install CWM just so I can easily recover from a backup in case I do some other stupid thing to the phone.
Thanks guys

Problem with "cannot read update.bin" in 4.6.4 to 4.6.3 downgrade

I have 4.6.4 AT&T OS and I want to downgrade to 4.6.3 unlock OS. In recovery mode the phone is connected with computer, I see serial number and "sideload" next, the update.bin file is in ADB folder, but at next step I get the message
"cannot read update.bin" . I run Win 10 on computer, I try also on Win 7, same problem. I downloaded
4.6.3 unlock OS first with Microsoft Edge, it has .zip extension, then downloaded with Chrome it came with .bin extension, neither one work. Any ideas ? Because I ran out.

That sounds confusing and frustrating. Where did you get the .bin from? I downloaded the one linked in this post and had no problems: http://forum.xda-developers.com/showpost.php?p=62768812&postcount=2
You definitely want a .bin file, not a zip (the .bin should be around 1.2gb). There's also the distinct possibility that ADB is improperly installed. If that's the case, there should be more info in that link that will help you.
In my signature, I link to a walkthrough describing everything I did to get my phone downgraded, rooted, etc. Maybe take a look and see if you missed any steps.

munkymack said:
That sounds confusing and frustrating. Where did you get the .bin from? I downloaded the one linked in this post and had no problems: http://forum.xda-developers.com/showpost.php?p=62768812&postcount=2
You definitely want a .bin file, not a zip (the .bin should be around 1.2gb). There's also the distinct possibility that ADB is improperly installed. If that's the case, there should be more info in that link that will help you.
In my signature, I link to a walkthrough describing everything I did to get my phone downgraded, rooted, etc. Maybe take a look and see if you missed any steps.
Click to expand...
Click to collapse
I downloaded 4.6.3 OS from 3-4 diffrent links from forum including that in your post, also direct from amazon. With Microsoft Edge, Internet Explorer the file is downloaded with .zip, no matter the link I used, so I thought that's the problem so I used Mozzila and Chrome, it came with .bin extension. The .bin file seems to be ok, I can open and extract folders and files from it with WinRAR so it's not corrupt.
About ADB, I read before how to deal with it, seems to work correctly, I can connect the phone in windows with phone on, also in recovery mode the phone appear sideload like it should. So at this point I don't no what to do.

markmm said:
I have 4.6.4 AT&T OS and I want to downgrade to 4.6.3 unlock OS. In recovery mode the phone is connected with computer, I see serial number and "sideload" next, the update.bin file is in ADB folder, but at next step I get the message
"cannot read update.bin" . I run Win 10 on computer, I try also on Win 7, same problem. I downloaded
4.6.3 unlock OS first with Microsoft Edge, it has .zip extension, then downloaded with Chrome it came with .bin extension, neither one work. Any ideas ? Because I ran out.
Click to expand...
Click to collapse
Microsoft Edge and Internet Explorer downloaded the 4.6.3 update as a zip file for me also. I've had the same error (cannot read update.bin) once when trying to sideload an update.bin. I never could figure out what the problem was, so I downgraded my phone using Safestrap. It is not recommended that you use Safestrap to update or downgrade your phone, but a few people including me have updated or downgraded their phone with Safestrap without any problems.
You will need to root your phone if you want to use Safestrap for the downgrade:
See Installing Root, Safestrap, CM11 for how to root and install Safestrap on your phone. You do not need to install CM11.
Launch Safestrap and select Install Recovery.
Download the 4.6.3 flashable-stock-image you will need for the downgrade and put the file on your phone.
Power your phone off, then power it back on.
When Safestrap starts, select RECOVERY> Install>
Browse to and select ss_update-fire-phone-35.4.6.3_user_463001620.zip.
Swipe to the right Swipe to Confirm Flash.
When the flash is complete, select Reboot System> CONTINUE>.
If you don’t want your phone rooted, launch Safestrap and uninstall Recovery, launch Kingroot and unroot your phone. I would also do a factory reset.
Edited to add: To unroot Kingroot 4.0, launch Kinguser, tap gear icon> Root authorization settings> Remove Root permission> Clear>. For Kingroot 4.5, launch Kingroot, tap gear icon> Root authorization settings> Remove Root permission> Continue> OK>. Manually uninstall any Kingroot apps that are still installed on your phone.

jack9955 said:
Microsoft Edge and Internet Explorer downloaded the 4.6.3 update as a zip file for me also. I've had the same error (cannot read update.bin) once when trying to sideload an update.bin. I never could figure out what the problem was, so I downgraded my phone using Safestrap. It is not recommended that you use Safestrap to update or downgrade your phone, but a few people including me have updated or downgraded their phone with Safestrap without any problems.
You will need to root your phone if you want to use Safestrap for the downgrade:
See Installing Root, Safestrap, CM11 for how to root and install Safestrap on your phone. You do not need to install CM11.
Launch Safestrap and select Install Recovery.
Download the 4.6.3 flashable-stock-image you will need for the downgrade and put the file on your phone.
Power your phone off, then power it back on.
When Safestrap starts, select RECOVERY> Install>
Browse to and select ss_update-fire-phone-35.4.6.3_user_463001620.zip.
Swipe to the right Swipe to Confirm Flash.
When the flash is complete, select Reboot System> CONTINUE>.
If you don’t want your phone rooted, launch Safestrap and uninstall Recovery, launch Kingroot and unroot your phone. I would also do a factory reset.
Click to expand...
Click to collapse
Thank you for your reply, I read about root/safestrap method but initially I did not want to root the phone.
Now seems to be the only choice, so thank you for info about this.

If you just type "adb devices" on the PC with the phone connected, do you see the phone? If not, then you have a driver issue. If that is the issue, the Amazon Dev. Service "Connecting your device" page may help.

Yes, at adb devices command the phone appear with serial number........ sideload. Appear connected whith phone on, I can copy on it and also in recovery mode after "apply update from ADB" . I belive that's not the problem.

I'm having the same problem. Cannot read update.bin when trying to sideload 4.6.3.

vkramac said:
I'm having the same problem. Cannot read update.bin when trying to sideload 4.6.3.
Click to expand...
Click to collapse
See this post, on how you may be able to correct your problem.

jack9955 said:
See this post, on how you may be able to correct your problem.
Click to expand...
Click to collapse
Thanks for linking this post. Regrettably, it still doesn't work...no worries though

vkramac said:
Thanks for linking this post. Regrettably, it still doesn't work...no worries though
Click to expand...
Click to collapse
I have had the exact same problem when trying to install the 4.6.3 update (cannot read update.bin), I had to use Safestrap to downgrade my phone. When you downloaded the update, was the extension a .bin or a .zip? When you say "it still doesn't work", do mean Safestrap doesn't work as well?

jack9955 said:
I have had the exact same problem when trying to install the 4.6.3 update (cannot read update.bin), I had to use Safestrap to downgrade my phone. When you downloaded the update, was the extension a .bin or a .zip? When you say "it still doesn't work", do mean Safestrap doesn't work as well?
Click to expand...
Click to collapse
I've been trying to do this through stock recovery. The file extension was .bin retrieved from Amazon's website.
I'm not interested in using Safestrap.

vkramac said:
I've been trying to do this through stock recovery. The file extension was .bin retrieved from Amazon's website.
I'm not interested in using Safestrap.
Click to expand...
Click to collapse
Yep. Can't figure this out at all. Most adb commands are working fine. ADB kill-server. ADB start-server. ADB devices. ADB reboot recovery.
Its just the ADB sideload that gets the error. Cannot read update.bin.
I'm starting to think this is WIN 10 ****ing with me.

vkramac said:
Yep. Can't figure this out at all. Most adb commands are working fine. ADB kill-server. ADB start-server. ADB devices. ADB reboot recovery.
Its just the ADB sideload that gets the error. Cannot read update.bin.
I'm starting to think this is WIN 10 ****ing with me.
Click to expand...
Click to collapse
OK, should you find a solution to the "cannot read update.bin", please post how you was able to fix the problem, your fix may help others. From an internet search, I see the most common reason for the "cannot read . . ." error is the file has a double extension of .zip.zip, bin.bin, or bin.zip.

vkramac said:
Yep. Can't figure this out at all. Most adb commands are working fine. ADB kill-server. ADB start-server. ADB devices. ADB reboot recovery.
Its just the ADB sideload that gets the error. Cannot read update.bin.
I'm starting to think this is WIN 10 ****ing with me.
Click to expand...
Click to collapse
Maybe a stupid question- But did you change the name of the downloaded bin file to "update.bin"?

Years later, but maybe it'll help. For me, it was a combo of WIndows and Bitdefender: Under properties of the update file, it said access was blocked due to the file being from another PC - checking the box there and disabling Bitdefender (only one at a time didn't help) solves the issue.

jack9955 said:
Microsoft Edge and Internet Explorer downloaded the 4.6.3 update as a zip file for me also. I've had the same error (cannot read update.bin) once when trying to sideload an update.bin. I never could figure out what the problem was, so I downgraded my phone using Safestrap. It is not recommended that you use Safestrap to update or downgrade your phone, but a few people including me have updated or downgraded their phone with Safestrap without any problems.
You will need to root your phone if you want to use Safestrap for the downgrade:
See Installing Root, Safestrap, CM11 for how to root and install Safestrap on your phone. You do not need to install CM11.
Launch Safestrap and select Install Recovery.
Download the 4.6.3 flashable-stock-image you will need for the downgrade and put the file on your phone.
Power your phone off, then power it back on.
When Safestrap starts, select RECOVERY> Install>
Browse to and select ss_update-fire-phone-35.4.6.3_user_463001620.zip.
Swipe to the right Swipe to Confirm Flash.
When the flash is complete, select Reboot System> CONTINUE>.
If you don’t want your phone rooted, launch Safestrap and uninstall Recovery, launch Kingroot and unroot your phone. I would also do a factory reset.
Edited to add: To unroot Kingroot 4.0, launch Kinguser, tap gear icon> Root authorization settings> Remove Root permission> Clear>. For Kingroot 4.5, launch Kingroot, tap gear icon> Root authorization settings> Remove Root permission> Continue> OK>. Manually uninstall any Kingroot apps that are still installed on your phone.
Click to expand...
Click to collapse
i am facing the same issue but the problem is i cant turn my phone on because it get bricked when i was trying to install MIUI 7 in it. Now it is just stuck to the amazon logo and i tried to do all these stuff to download amazon latest and installing it through adb but in command prompt it says *cannot read update.bin i cant understand what is going over here please help me out to solve this issue or i will not be able to buy a new phone dew to some financial conditions.

hamza said:
i am facing the same issue but the problem is i cant turn my phone on because it get bricked when i was trying to install MIUI 7 in it. Now it is just stuck to the amazon logo and i tried to do all these stuff to download amazon latest and installing it through adb but in command prompt it says *cannot read update.bin i cant understand what is going over here please help me out to solve this issue or i will not be able to buy a new phone dew to some financial conditions.
Click to expand...
Click to collapse
Hi, I found out your computer may block files that appears to be malicious. See this thread for information on how to unblock it.

Got it to work
I was having the same problem. I kept getting the message" cannot read file"
I was able to get it to work by typing "adb sideload" and then dragging the file in the command window right behind "adb sideload". the string will look like this
"PS C:\Users\Ryan\Desktop> adb sideload C:\Users\Ryan\Desktop\update.bin.bin
and then press enter.

PurpleDrake fails on LG G3 (LG-D852)

I have a new LG-D852 (aka LG G3) running on Canadian provider Fido and I want to root it but PurpleDrake failed (running Linux):
Code:
Waiting for device... Found device!
Your phone is a [ LG-D852 ] on [ RGS ] running SW version [ V20d ] ...
Alright. We're ready to go. We're going to temproot your phone first. Press enter when you're ready!
Press [enter] to continue...
Rebooting phone...
Waiting for device... .................................... Found device!
Found device, checking if vulnerable...
ERROR: Your phone is not running a compatible software version. No vulnerable mode detected, rebooting phone.
We tried to temproot you, and it didn't work. This phone isn't vulnerable, it would appear.
Please post on XDA with your phone model, carrier, and SW version in the PurpleDrake thread and someone will take a look.
Your phone has been rebooted back to normal system mode, no changes have been made. Thanks for trying!
Is there a better or more effective way to root the phone?

Assuming V20d is Lollipop, try the first method (one-click script) from this thread...
[GUIDE][ROOT] Newest Root Method for LG devices
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
If the script fails, then run the commands from the second method. This after downloading and extracting the "New_LG_Root_v0.1_by_dig.zip" file from the OP.

None of the methods listed have worked for me. Is there something I'm missing?

Post a pic w/ the Command Prompt open, showing the results of each command run using the second method.

Since I don't have a Windows machine, the Windows tools won't work for me, so I should have been more specific in that the Linux-compatible tools aren't working for me. PurpleDrake says my phone isn't vulnerable. The other rooting methods listed in the spreadsheet fail as well saying my phone has been patched.
It's a D852 V20d, running Lollipop on Fido (which is the same as Rogers Canada now). If you have a Linux version of the Windows tools you can point me to, I'm happy to try again. As it stands, digital-bug's method is Windows-only.

LinuxSupahFly said:
Since I don't have a Windows machine, the Windows tools won't work for me, so I should have been more specific in that the Linux-compatible tools aren't working for me. PurpleDrake says my phone isn't vulnerable. The other rooting methods listed in the spreadsheet fail as well saying my phone has been patched.
It's a D852 V20d, running Lollipop on Fido (which is the same as Rogers Canada now). If you have a Linux version of the Windows tools you can point me to, I'm happy to try again. As it stands, digital-bug's method is Windows-only.
Click to expand...
Click to collapse
After some extensive Google exploitation, I discovered this thread which offers a Linux tool that does the same thing Send_Command.exe does, but using a Python script, and that worked. My phone is now successfully rooted.

additional information
Worked for me too, if anybody else finds this, I've combined the python script mentioned above with these instructions :
www DOT androidrooting DOT org SLASH new-root-method-to-easily-root-all-lg-devices (I'm a new user here and cant yet post true URL, sorry)
Replace any mention of adb.exe with your Linux version of adb (from the Android SDK, or elsewhere).
For Step 10, run "python qcdlcomm.py" script. It may not work the first time, I had to install pyserial (or python-serial) package, then unload / reload some kernel modules as specified by the script. Once you get the # prompt, you can enter the command line from Step 11 as-is.

How To Guide Installing OneUI 4 Beta / Android 12 on US Galaxy Z Fold 3 F926U/1

Updated with more compatible adb link!
This is what I did to get the new beta. Feel free to tell me how dumb I am for allowing noobies to try the beta, but the more the merrier and they should know the risks....
RISKS: Phone may not be as stable as before and you will lose all your apps and data. Camera is bugged for me
1. BACK UP YOUR CURRENT BUILD USING SMART SWITCH. THIS WILL WIPE DALVIK/CACHE/DATA. Get SmartSwitch for PC HERE
2. Download Samsung Drivers for ADB/ODIN HERE
3. If you are on firmware ending in AUI5 for the CSC version XAA then skip to step #6 . If you are not, then download the respective firmware HERE
Also Download Patched ODIN (Patched version will be less scrutinous) HERE
4. Unzip the firmware you just downloaded as well as the Patched Odin. Run ODIN and add the BL, AP, CP, Home_CSC from the unzipped firmware to the corresponding locations in ODIN
5. Turn off phone and boot into "Download Mode" by first holding Volume +/- buttons and then hold the Power button. Now plug in your phone to your PC and you will see the first small grey square in the upper left side of ODIN turn light blue (if it does not, you have issues with either the cable or drivers).
Proceed in flashing the device by simply clicking the "Start" button.
Once it is done and your phone has rebooted... Make sure that you complete the setup process just in case of authentication issues if the phone isn't already set up
6. Download the OneUI 4 Beta HERE and then follow the guide to install adb https://www.xda-developers.com/install-adb-windows-macos-linux/
7. Follow the XDA adb install guide and make sure to allow adb systemwide when asked by the program.
8. Turn off phone. Boot into device by holding Volume Up and then holding Power. This will take you into recovery mode, where you will see the option to "update via ADB sideload".
Use the volume down key to navigate down to that option and press power to initiate the adb sideload function
9. Open command prompt by pressing the Windows key and typing "cmd" (no quotes) and press ENTER.
10. Type into the command prompt (of course remove the quotes) "adb sideload C:\path\to\your\oneui4\zip\file" . For example if I download that file into my Downloads folder, I would then type "adb sideload C:\Users\MyPC\Downloads\949981470b3948c3aa05a19e8a2edbd3.zip"

Bro I have SM-F926B, I downloaded the correct CSC but can't install the beta, I got a message on smd says can't read. Any help please?

shadi90 said:
Bro I have SM-F926B, I downloaded the correct CSC but can't install the beta, I got a message on smd says can't read. Any help please?
Click to expand...
Click to collapse
This is for US Fold 3 models f926U/1. Sorry brotha. Basically you need to change the beta file you downloaded to this http://fota-secure-dn.ospserver.net...48:16&px-unum=&px-nb=UGtezEZ854jbmFcvWGxLEA== as well as flash AUJ7 firmware first. I hear UK with CSC BTE works fine. Get it at https://samfw.com/firmware/SM-F926B/BTE/F926BXXU1AUJ7 . After you replaced those files, just follow the instructions again

Thanks for this Guide. But i have issue with Adb sideload update.zip
I downgrade to AUI5 and been using XAA firmware since i bought T-mobile Zfold3.
And since beta was released, I'd been trying to register for OneUI4 in Samsung Memeber app but No Banner or under rBenefit tab.
So saw your guide here and tried to followed your direction but adb sideload fails i get CANNOT READ message.
when i typed adb Devices it shows my device so adb is working but cannot sideload.
when i downloaded the update it was .bin 949981470b3948c3aa05a19e8a2edbd3.bin so i renamed it to .zip, i got the CANNOT READ message then renamed it to update.zip still the same Cannot Read.
I am using windows 11.

Haven't logged in to XDA in years. Just wanted to say THANK YOU.

mha1021 said:
Thanks for this Guide. But i have issue with Adb sideload update.zip
I downgrade to AUI5 and been using XAA firmware since i bought T-mobile Zfold3.
And since beta was released, I'd been trying to register for OneUI4 in Samsung Memeber app but No Banner or under rBenefit tab.
So saw your guide here and tried to followed your direction but adb sideload fails i get CANNOT READ message.
when i typed adb Devices it shows my device so adb is working but cannot sideload.
when i downloaded the update it was .bin 949981470b3948c3aa05a19e8a2edbd3.bin so i renamed it to .zip, i got the CANNOT READ message then renamed it to update.zip still the same Cannot Read.
I am using windows 11.
Click to expand...
Click to collapse
Don't rename the file.
What I always do with adb related stuff is put it in the root of my C drive. So it would be
Code:
C:\adb\platform-tools\
Then put the .bin file in here as well.
After that open cmd and do
Code:
cd C:\adb\platform-tools\
and hit enter.
After that do adb sideload 94 and hit tab so it should autofill the name of the update file.
Let me know if you have any questions.

Thanks for the instructions as they worked for me. I did receive an error before it finished at "(~94%) adb: failed to read command: No error". Phone booted and the system is showing One UI version 4.0, Android Version 12.
QUESTION though. What is up with the difference in Baseband version? I am seeing the official release having the last 2 digits of "JF" but on the phone just flashed, it is showing "JH".
For reference, complete Baseband version: F929U1UEU1ZUJH after flashing. Might just be my ignorance but thought I would ask.
Thoughts? And thank you again!

AlexMartin00 said:
Thanks for the instructions as they worked for me. I did receive an error before it finished at "(~94%) adb: failed to read command: No error". Phone booted and the system is showing One UI version 4.0, Android Version 12.
QUESTION though. What is up with the difference in Baseband version? I am seeing the official release having the last 2 digits of "JF" but on the phone just flashed, it is showing "JH".
For reference, complete Baseband version: F929U1UEU1ZUJH after flashing. Might just be my ignorance but thought I would ask.
Thoughts? And thank you again!
Click to expand...
Click to collapse
The baseband is just something that gets updated, so ZUJH is the Android 12 beta firmware. Every time you update your firmware the baseband gets updated as well.
More technical: Baseband is firmware that controls all radio devices on the phone, including GPS, Wi-Fi, Bluetooth, NFC, cellular data, and more.

Will this work on att Galaxy fold 3 since I can't get update cause att blocks it.

Hero_is_Over said:
This is what I did to get the new beta. Feel free to tell me how dumb I am for allowing noobies to try the beta, but the more the merrier and they should know the risks....
RISKS: Phone may not be as stable as before and you will lose all your apps and data. Camera is bugged for me
1. BACK UP YOUR CURRENT BUILD USING SMART SWITCH. THIS WILL WIPE DALVIK/CACHE/DATA. Get SmartSwitch for PC HERE
2. Download Samsung Drivers for ADB/ODIN HERE
3. If you are on firmware ending in AUI5 for the CSC version XAA then skip to step #6 . If you are not, then download the respective firmware HERE
Also Download Patched ODIN (Patched version will be less scrutinous) HERE
4. Unzip the firmware you just downloaded as well as the Patched Odin. Run ODIN and add the BL, AP, CP, Home_CSC from the unzipped firmware to the corresponding locations in ODIN
5. Turn off phone and boot into "Download Mode" by first holding Volume +/- buttons and then hold the Power button. Now plug in your phone to your PC and you will see the first small grey square in the upper left side of ODIN turn light blue (if it does not, you have issues with either the cable or drivers).
Proceed in flashing the device by simply clicking the "Start" button.
Once it is done and your phone has rebooted... Make sure that you complete the setup process just in case of authentication issues if the phone isn't already set up
6. Download the OneUI 4 Beta HERE and then download the "15 Second ADB Installer" HERE
7. Install the 15 second adb installer and make sure to allow adb systemwide when asked by the program.
8. Turn off phone. Boot into device by holding Volume Up and then holding Power. This will take you into recovery mode, where you will see the option to "update via ADB sideload".
Use the volume down key to navigate down to that option and press power to initiate the adb sideload function
9. Open command prompt by pressing the Windows key and typing "cmd" (no quotes) and press ENTER.
10. Type into the command prompt (of course remove the quotes) "adb sideload C:\path\to\your\oneui4\zip\file" . For example if I download that file into my Downloads folder, I would then type "adb sideload C:\Users\MyPC\Downloads\949981470b3948c3aa05a19e8a2edbd3.zip"
Click to expand...
Click to collapse
hi I'm getting a status 1 error with my sideload

erneyone said:
hi I'm getting a status 1 error with my sideload
Click to expand...
Click to collapse
What does the error say?

I keep getting cannot read '949981470b3948c3aa05a19e8a2edbd3.bin and I do have the file on my ADB folder which is on the C drive i don't know if it matter but I'm using a windows 11 laptop

zimgir124 said:
What does the error say?
Click to expand...
Click to collapse
Status 1

Is there a mirror for the beta download anywhere? It looks like the link isn't working for me.

ElGuyarc said:
I keep getting cannot read '949981470b3948c3aa05a19e8a2edbd3.bin and I do have the file on my ADB folder which is on the C drive i don't know if it matter but I'm using a windows 11 laptop
Click to expand...
Click to collapse
was getting the cannot read error too.. the problem is the outdated adb version installed from the 15 second adb link in the op
download this:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com

Dick_Stickitinski said:
was getting the cannot read error too.. the problem is the outdated adb version installed from the 15 second adb link in the op
download this:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Click to expand...
Click to collapse
thank you so much...

I updated my SM-F926U1 with the Beta 4 its really buggy for me
Just want to get my facts straight. Can I just flash back to non-beta ?
What will happen to my Beta status will I still be able to OTA update when the next beta comes out ?

I have updated this with the newer adb binary install guide. I use the latest binaries from Android Studio and add them to path manually so I didnt know the 15 second installer was that outdated
Also yes you can downgrade by flashing the AUI5 that I posted in the guide

Hero_is_Over said:
I have updated this with the newer adb binary install guide. I use the latest binaries from Android Studio and add them to path manually so I didnt know the 15 second installer was that outdated
Also yes you can downgrade by flashing the AUI5 that I posted in the guide
Click to expand...
Click to collapse
Is it a good idea to wipe my data when doing an downgrade like this ?

Hero_is_Over said:
I have updated this with the newer adb binary install guide. I use the latest binaries from Android Studio and add them to path manually so I didnt know the 15 second installer was that outdated
Also yes you can downgrade by flashing the AUI5 that I posted in the guide
Click to expand...
Click to collapse
I thought you can't flash a previous version of Android once you're on the higher version?

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